[katello-devel] Orchestration-ng thoughts

[Dmitri Dolguikh]

Thanks, Ivan, for the work on the orchestration NG and the demo today. 
This is a big improvement over the current implementation, and it's 
actually testable!

I would like to figure out if the orchestration approach is something we 
want to stick with, or should we switch to a messaging-based 
(amqp?)approach? We would if not completely get rid of orchestration, 
but at the very least significantly reduce the amount of it.

One of the possible approaches is where Katello  is a producer of 
messages (reliable, persisted, and delivery-acked), with pulp, 
candlepin, and foreman acting as subscribers. The subscriber 
functionality can be extracted into plugins/rails engines.


Thoughts?
-d
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/katello-devel/attachments/20130429/2ebc8c88/attachment.htm>