[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Pulp-list] Repo Sync Scheduling

On Wed, 2010-06-16 at 11:31 -0400, seth vidal wrote:
> you could have the pulp web site write the info you want out to a db
> then have a process which comes along when the db is changed and
> writes
> out (as root or whatever) the info to /etc/cron.d/
> That way you avoid system calls to crontab which is just pain.
> So the process looks like:
> user logs into webinterface
> user requests some repo be synced
> pulp writes this to a db
> that info is plucked out and written to /etc/cron.d
> that way you're:
> 1. not writing directly to a potentially dangerous path from an apache
> process
> 2. not relying on anything in pulp running - since cron should be
> running all the time
> 3. using the existing system infrastructure 

I think writing into /etc/cron.d is a fine solution, conceptually. But I
thought we were brainstorming on alternatives to this, as apache doesn't
have write permissions to that directory.

If we're going to go this route, it seems to me that the last step has
to be executed by process that has write permissions to that directory.

Personally, I don't really care where this stuff is stored. Only that
tasks gets executed reliably when the customer expects them to.

On another note, I do see a potential caveat with using crontab. We have
to be careful about cleaning up entries if the administrator shuts down
the web services or even removes pulp all together.

Jason L Connor
Senior Software Engineer
Systems Management and Cloud Enablement
Red Hat, Inc.
Freenode: linear

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]