[openstack-dev] [Heat] HOT software configuration refined after design summit discussions
Mike Spreitzer
mspreitz at us.ibm.com
Wed Nov 20 23:08:45 UTC 2013
Regarding my previous email:
> Steve Baker <sbaker at redhat.com> wrote on 11/19/2013 03:40:54 PM:
> ...
> > How to define and deliver this agent is the challenge. Some options
are:
> > 1) install it as part of the image customization/bootstrapping (golden
> > images or cloud-init)
>
> > 2) define a (mustache?) template in the SoftwareConfig which
> > os-collect-config transforms into the agent script, which
> > os-collect-config then executes
>
> I do not follow what you mean here. Can you please elaborate a little?
>
> > 3) a CM tool specific implementation of SoftwareApplier builds and
> > delivers a complete agent to os-collect-config which executes it
>
> Could instead the agent be a package that the applier templates asks
> to be installed?
We may not need to active agent to be CM tool specific. I think the
remarks about os-collect-config show this. Maybe all we need is a CM tool
specific package to be installed to supply the (I use the singular because
of our earlier conversation that affirmed the expectation of only one CM
tool per VM) hook that os-collect-config calls.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131120/699eed65/attachment.html>
More information about the OpenStack-dev
mailing list