Allow config drive to be disabled
Bug #1468514 reported by
Bjoern
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Medium
|
Kevin Carter | ||
Juno |
Fix Released
|
Medium
|
Christopher H. Laco | ||
Kilo |
Fix Released
|
Medium
|
Jesse Pretorius | ||
Trunk |
Fix Released
|
Medium
|
Kevin Carter |
Bug Description
Currently we set the parameter force_config_drive to always which will create a config drive for every instance.
Unfortunately nova does not support live migration (actually a libvirt limitation) so I would propose to set this to none, like the default setting in nova.
That will leave the customer with the option to enable config drives per flavor or boot request (--config-drive) instead of enforcing it and limiting other important features like live migration
Changed in openstack-ansible: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Kevin Carter (kevin-carter) |
milestone: | none → 11.0.4 |
summary: |
- Disable default nova config drive enforcing + Allow config drive to be disabled |
To post a comment you must log in.
Some background info : http:// docs.openstack. org/admin- guide-cloud/ content/ section_ configuring- compute- migrations. html