On Tue, 2011-07-19 at 15:55 +0100, Mark McLoughlin wrote:
> > > * Aeolus Orchestrator: A way to manage clumps of instances in an
> > > organized way. Users should be able to automatically bring up a set
> > > of different instances on a single cloud or spanning multiple
> > > clouds, configure them, and tell them about each other.
> >
> > On the above note, it's not clear to me what component(s) Orchestrator
> > maps to. (Or maybe I just haven't had my coffee yet.) It sounds like
> > this is a blend of Warehouse, Condor, and Conductor, though Conductor is
> > already mentioned above.
>
> This is definitely just a "conceptual split" at the moment.
>
> I suggest it because the concepts of deployables, deployments, config
> server and audrey are the part of the architecture that addresses this
> "clumps of instances" problem.
>
> If those pieces were together a more cleanly separated project, perhaps
> we'd see the folks working on those pieces iterating on ideas a lot more
> freely rather than worrying too much about integration issues.
>
> And also, if our solution is to become compelling, it should also be
> compelling if you use it on top of a standalone deltacloud. There's no
> particular reason why you shouldn't be able to just use it with EC2.
>
> There's an obvious problem with this idea - the deployables and
> deployments concepts are wedged pretty firmly in conductor. To separate
> them out would mean making a separate app just for dealing with
> deployables and deployments and then, much later, trying to figure out
> how to bring that functionality back into a unified UI.
Okay, I've taken a first stab at this:
https://github.com/markmc/aeolus-orch
The README explains the idea.
Basically, it's a simple server for hacking on the deployable concept
which only requires deltacloud and config server.
And it's also a library which Conductor can use for turning a deployable
XML into a set of deltacloud instance descriptions and for interacting
with config server as it launches those instances.
I've made it a separate repo for now, but it probably belongs in the
audrey repo.
Thoughts?
I suggest we get Greg Blomquist to look at the two and combine them into one
place; whether that ends up being aeolus-orch or audrey makes no difference to
me.
--
Chris Lalancette