[openstack-dev] [Nova] why force_config_drive is a per comptue node config

Michael Still mikal at stillhq.com
Thu Feb 27 21:03:59 UTC 2014


On Fri, Feb 28, 2014 at 6:34 AM, yunhong jiang
<yunhong.jiang at linux.intel.com> wrote:
> Greeting,
>         I have some questions on the force_config_drive configuration options
> and hope get some hints.
>         a) Why do we want this? Per my understanding, if the user want to use
> the config drive, they need specify it in the nova boot. Or is it
> because possibly user have no idea of the cloudinit installation in the
> image?

It is possible for a cloud admin to have only provided images which
work with config drive. In that case the admin would want to force
config drive on, to ensure that instances always boot correctly.

>         b) even if we want to force config drive, why it's a compute node
> config instead of cloud wise config? Compute-node config will have some
> migration issue per my understanding.

That's a fair point. It should probably have been a flag on the api
servers. I'd file a bug for that one.

Michael

-- 
Rackspace Australia



More information about the OpenStack-dev mailing list