What I crave is a communication channel between nova and running
instances. There was discussion at some point about extending the
metadata api to have this ability.
Having a solid config drive standard seems like a good idea, but it
won't get me run-time interaction, will it?
-Andrew
On 4/10/12 11:40 AM, Eric Windisch wrote:
I maintain my stance from pre-Diablo, that the configuration drive
should be exported as a virtual cdrom device with an ISO9660
filesystem. We can generate the filesystem without root access and the
filesystem is well-supported. Additionally, it lacks the
patent-related issues associated with the other many-platform
filesystems (i.e. FAT).
Also, doing the above happens to make the configuration-drive
surprisingly similar to the optional sub-feature of OVF. I'm not sure
what priority OVF is for Nova (it is a low priority for me), but it
might be worth considering, especially since Glance seems to advertise
some OVF support.
--
Eric Windisch
On Tuesday, April 10, 2012 at 11:52 AM, Scott Moser wrote:
On Tue, 10 Apr 2012, Andrew Bogott wrote:
I'm reviving this ancient thread to ask: Will there be a code summit
session
about this? And/or are there plans to start developing a standard set of
guest agents for Folsom?
http://summit.openstack.org/sessions/view/100
_______________________________________________
Mailing list: https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
Post to : openstack@lists.launchpad.net
<mailto:openstack@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
