On Mon, Jul 16, 2012 at 01:04:36PM -0400, Chris Alfonso wrote:
On 16/07/12 18:57 +0200, Ivan Nečas wrote:
>
>With funzo, we're trying to figure out how the Aeolus + Katello could
>better integrate together.
>
>The templates in Katello are going to be replaced with component outlines. In
>discussion about Foreman integration, it was not mentioned, that the
>Compontent Outline will contain the list of packages (System Template
>like we know it today has it). This is not required by Foreman (Foreman
>solves it with Puppet), but Aeolus is able to take the list of
>packages and install it into the built image, if I understand it
>correctly. Was it meant to be this way, or we just skipped it when
>talking about Foreman. It seems quite valuable Aeolus feature to me.
>
>Another thing to solve is how to call back to Katello after the
>instance was deployed by Aeolus (if we're not satisfied with the
>current status of setting the script manually in deployable, which I
>guess we're not). It seems for now that Audrey is the only way how to
>run some scripts after the image was deployed. Will there we some other
>way for running scripts after deployment in Cloud Engine. If not, it
>seems that we will need to run Audrey and Puppet side by side. Maybe
>it's ok, just asking, if its acceptable to have two config servers run
>against the same machine?
>
An alternative the greg blomquist mentioned was to build the image with cloud-init
installed and pass in parameters to complete a registration. Doing so would git us the
ability to not wire the VM up to a config server.
>Ohad:
>
>How does Foreman solve the EC2 deployment against Foreman?
>
>--
>Ivan
>
I love the idea of not *having to have* a config server unless you
really need it, for I think obvious reasons...
--Hugh
--
== Hugh Brock, hbrock(a)redhat.com ==
== Engineering Manager, Cloud BU ==
== Aeolus Project: Manage virtual infrastructure across clouds. ==
==
http://aeolusproject.org ==
"I know that you believe you understand what you think I said, but I’m
not sure you realize that what you heard is not what I meant."
--Robert McCloskey