Hi all,
First off, sorry for not replying to the posts from before - I just now joined this
mailing list. I wanted to propose an idea for a way to implement workflow/approvals for
launching new instances. I know there is currently a proposal along these lines
(
https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Launch_request...).
Looking at that, I see the suggestion is to build all the approval directly into
Conductor. What I'm thinking about instead is sending out a message (e.g. Qpid,
HornetQ, ActiveMQ) with the launch request information. Conductor wouldn't be
responsible for managing the workflow other than keeping track of PENDING_APPROVAL
deployments. Instead, the workflow would be managed by an external third-party system. I
suppose Conductor could supply a default/minimal approval UI, but the real power is in
making the workflow extensible. Imagine a large enterprise IT department that hooks up
the workflow notifications to a business rules engine for more advanced approval logic.
(As an aside, a similar approach could be used for events such as instance started,
instance stopped, etc. Other external systems could consume these events to provide
services like billing/chargebacks that wouldn't necessarily need to be features of
Aeolus.)
What do you all think?
Andy