On 07/26/2011 04:30 AM, Mark McLoughlin wrote:
[...]
You know, after all this, I think you're actually only disagreeing with
a minor part of the proposal.
Here's all I'm saying:
- Deployable parsing and interpretation, config server and the audrey
guest agent could be a fairly self-contained effort under the
Aeolus umbrella.
I agree that the parsing and interpretation of deployables is something
that could be broken out and housed in an Audrey library called on by
Conductor.
- At this early stage, keeping it fairly self-contained will give the
effort a better chance of success because it becomes easier to
iterate on the design.
Agree. I'm already a fair bit down the road of being fully integrated
with Conductor, though. So, I suggest that I keep down that path until
I have the proof of concept integration working, then circle back to
refactor it out if that's the right next step.
- A bunch of the code Conductor needs for handling deployables and
talking to config sever should live in a library outside of
Conductor and developed as part of the Audrey effort.
This seems achievable, under the same caveat as above.
- Audrey is interesting in its own right and should have its own
simple stateless API/UI server which you can run against any
deltacloud instance.
This is where you throw me. I'm not sure what you mean by running
against a deltacloud instance. I can't see this working without
reproducing a bunch of code already in Conductor. Unless you're seeing
this from a different angle.
- This is a subtly different way of thinking about Audrey. With the
benefit of hindsight, I think we integrated this stuff too early
into Conductor. If we had understood how both pieces could live
independently, I think we would have kept them separate until
the Audrey concept had proven itself out.
What are your thoughts here? I can see audrey being packaged as some
library code that conductor can interact with...but, I'm not seeing the
standalone concept. I'm sure there's more to this, and I'd like to
understand it.
- Hindsight is one thing. Deciding that we should now remove
deployables again from Conductor is a whole different thing. I
think it's worth discussing once standalone Audrey is better
established, but it's certainly neither the first step nor
obviously the best choice.
Cheers,
Mark.
_______________________________________________
aeolus-devel mailing list
aeolus-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/aeolus-devel