force_config_drive should be based on image property
Bug #1285880 reported by
jiang, yunhong
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Low
|
jiang, yunhong | ||
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.
Revision history for this message
| jiang, yunhong (yunhong-jiang) wrote | #1 |
| tags: | added: api compute |
| Changed in nova: | |
| importance: | Undecided → Low |
| assignee: | nobody → jiang, yunhong (yunhong-jiang) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #2 |
| Changed in nova: | |
| status: | New → In Progress |
Revision history for this message
| Joe Gordon (jogo) wrote | #3 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → juno-rc1 |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
See http://<email address hidden>