Open Stack

On 8 May 2013 15:09, Russell Bryant <rbryant at redhat.com> wrote:
> On 05/08/2013 03:32 AM, Robert Collins wrote:
>> On 8 May 2013 19:03, Michael Still <mikal at stillhq.com> wrote:
>>> However, I do think you need to support configdrive if you're not
>>> doing file injection. I say this because some deployments cannot use
>>> metadata server (for example, network policy may not allow instances
>>> to talk to infrastructure nodes). So, I think having that would be
>>> good.

+1 for config drive
Baremetal (and many others) can use the metadata service

> grep says libvirt, xenapi, and hyperv all support configdrive.  Is that
> right?

>From the XenAPI perspective, we have the agent, config_drive and
metadata service to do file injection, so lets kill direct file
injection.

I am looking to make sure the agent doesn't conflit with config drive
and cloud-init work as part of this:
https://blueprints.launchpad.net/nova/+spec/xenapi-guest-agent-cloud-init-interop

The only other thing XenAPI does with the guest disk (off the top of
my head) is the resizing of the partitions and filesystem
(auto_disk_config). Of course, moving to things like
cloud-initiramfs-growroot should help with that.

John