Hi, Michael, I created a bug at https://bugs.launchpad.net/nova/+bug/1285880 and please have a look.
Thanks --jyh > -----Original Message----- > From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com] > Sent: Thursday, February 27, 2014 1:35 PM > To: OpenStack Development Mailing List (not for usage questions); > yunhong jiang > Subject: Re: [openstack-dev] [Nova] why force_config_drive is a per > comptue node config > > > > > -----Original Message----- > > From: Michael Still [mailto:mi...@stillhq.com] > > Sent: Thursday, February 27, 2014 1:04 PM > > To: yunhong jiang > > Cc: OpenStack Development Mailing List > > Subject: Re: [openstack-dev] [Nova] why force_config_drive is a per > > comptue node config > > > > On Fri, Feb 28, 2014 at 6:34 AM, yunhong jiang > > <yunhong.ji...@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. > > So would it make sense to keep it as image property, instead of compute > node config? > > > > > > 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. > > Thanks, and I can cook a patch for it. Still I think it will be better if we > use > image property? > > --jyh > > > > > Michael > > > > -- > > Rackspace Australia > > > > _______________________________________________ > > OpenStack-dev mailing list > > OpenStackemail@example.com > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > _______________________________________________ > OpenStack-dev mailing list > OpenStackfirstname.lastname@example.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev