openstack team mailing list archive
Mailing list archive
Re: nova/puppet blueprint, and some questions
Sorry for the slow response on this. There has been a lot to do for e-3. In any case, here are my thoughts on the subject. I am really not convinced that configuration management needs to be part of nova at all. This is stuff that should be built on top of nova. We have a bit of work to do cleaning up and improving metadata to make this type of thing easier, but I don't see any big needs for this to be in nova. A horizon plugin that handles this seems like it would be much more interesting.
On Jan 26, 2012, at 10:25 AM, Andrew Bogott wrote:
> Happy tag day, everyone!
> The next thing I'm going to work on (for Nova/Folsom) is adding an API to assist with Puppet configuration on nova instances. The blueprint for that is here:
> I welcome comments on that proposal.
> There's a fair bit of hand-waving in the Implementation section when it comes to the question of how exactly Nova will communicate puppet config to an instance. Ideally I would like to use file injection to drop a site.pp file directly onto the instance. My fear, though, is that file injection is not supported widely enough for me to rely on it. Is that right? Are there plans to support file injection on non-Xen hypervisors (most importantly, on KVM?)
> If I can't rely on file injection, then I probably need to use metadata instead. Is metadata injection more widely supported than file injection? And, is there any kind of 'standard' pattern for instance daemons that notice and respond to metadata changes (e.g. the guest agents module), or would I just adlib that part?
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp