Public bug reported:
Currently there is a force_config_drive config item for each compute
node. A VM migrated from host w/ force_config_drive to a host w/o it
will lost the config_drive, this is not so good. Currently it's ok
because most of the config drive information is only used at launch
time.
According to the comments , it's be better to be based on image
property.
One thing need consider is rebuild. A image is changed when rebuilding,
and I think if new image has no property for config drive, there should
be no config drive for it. Thus we have to distinguish between the
config_drive requirement from user and from image property.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1285880
Title:
force_config_drive should be based on image property
Status in OpenStack Compute (Nova):
New
Bug description:
Currently there is a force_config_drive config item for each compute
node. A VM migrated from host w/ force_config_drive to a host w/o it
will lost the config_drive, this is not so good. Currently it's ok
because most of the config drive information is only used at launch
time.
According to the comments , it's be better to be based on image
property.
One thing need consider is rebuild. A image is changed when
rebuilding, and I think if new image has no property for config drive,
there should be no config drive for it. Thus we have to distinguish
between the config_drive requirement from user and from image
property.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1285880/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
