[nycbug-talk] Cron management
brian.gupta at gmail.com
Tue Oct 6 02:20:29 EDT 2009
If you store your puppet configs in a version control system, you should be
able to use creative commit ACLs to come up with a scheme that will
accomplish what you are trying to do. (I haven't tested this, or had anyone
ask for it but it should be doable, as most SCMs, including SVN and Git
support directory level ACLs.)
- Brian Gupta
New York City user groups calendar:
On Tue, Sep 29, 2009 at 1:07 PM, Matt Juszczak <matt at atopia.net> wrote:
> Hi All,
> I have a setup that is using puppet for system management/configuration,
> including crons. It works well, except that many of the devs have
> requested access to add/edit/delete crons (95% of our crons are
> unfortunately for site-related code and DB related tasks).
> There are two options I have:
> - Give every dev access to our puppet server and access to change puppet
> configuration (not really something I want to do).
> - Setup a single cron inside puppet that runs every minute, and then
> somehow setup a "task management system" that can execute multiple tasks
> using that single cron.
> Are there such systems as the last one I mentioned, perhaps web and
> mysql/php based, where the dev's could create new "tasks" to run, and a
> single cron running every minute would execute those tasks when needed?
> talk mailing list
> talk at lists.nycbug.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the talk