On 02/28/2013 10:13 PM, Tomas Lestach wrote:
The only part of code, that generates the repodata is the taskomatic reporegen
worker. I'd suggest to set the state to 'in progress' after a generation
starts, to set it to 'failed' if the worker throws an exception (we saw some
out of memory exceptions in case of large channels) and to 'completed', when
the worker succeeds.
Yes, but then I need persistence for the state, which is what I have
been avoiding until now.
Initial state may be set according to the presence of the repomd.xml file in
the appropriate directory to either unknown(/missing) or completed.
I wouldn't consider a 'scheduled' state due to the need to periodically query
the rhnRepoRegenQueue table.
Why would that be a problem?
--
Duncan Mac-Vicar P. - http://www.suse.com/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix
Imendörffer, HRB 16746 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
