Currently some config tooling is provide along with the Audrey Start code. In the future more could be added. If a conflict arises between user provided config tooling and Audrey provided for a particular service the user provided tooling will be used and the Audrey provided tooling will be ignored.
If the user provides a Top-Level configuration tooling
executable all other tooling will be ignored."
This section does not seem correct. only case I can think of here is if the image came from an OVA source and has the OVA activation daemon. Then Audry should be able to run the OVA activation daemon, and then it's boot config. We should also be able to tell it to skip calling OVA activation daemon if required.
Greg Blomquist and I have put together an Audrey design document for the 0.4.0 effort. It can be found here: http://www.aeolusproject.org/page/Audrey-Conductor_Integration_0.4.0 Although we would appreciate input from anyone I'm requesting review feedback from the following people: John Dunning Hugh Brock Chris Lalancette Mark McLoughlin Carl Trieloff Brian Kearney I am asking that all feedback be provided by COB one week from today, August 3, 2011. We are already moving forward with some development according to the presented design so direction changing feedback would be greatly appreciated as early as possible. If anyone needs more time please let us know. I tried to provide XML examples that align with the format outlined in past discussion. If I missed that please let me know. Thank you, Joe and Greg _______________________________________________ aeolus-devel mailing list firstname.lastname@example.org https://fedorahosted.org/mailman/listinfo/aeolus-devel