Enable config_drive by default
In many situations metadata service is either not usable or not practical. config_drive provides a practical alternative to configure VMs in these situations. We should enable force_config_drive so that VMs launched from nova and horizon have config_drive support by default (and users with a corner case that can't launch with config_drive can still use nova to boot without it) but expose a parameter to disable it for users who don't want config_drive in their cluster
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- rakshith
- Definition:
- Approved
- Series goal:
- Accepted for grizzly
- Implementation:
-
Implemented
- Milestone target:
-
g.2
- Started by
- rakshith
- Completed by
- Mark T. Voelker
Related branches
Related bugs
Sprints
Whiteboard
Daneyon Hansen
I added config_drive support to the nova module a few weeks back. We need to expose the force_config_drive parameter to the openstack::compute class and pass it to our top-level manifests.
Here is an example on how the openstack-
https:/
https:/
force_config_drive is needed to spawn instances from within Horizon. Otherwise, the nova client can be used with the --config-drive=true flag in the boot command.
Someone is working on adding config_drive to the puppet-openstack module: https:/
We should contribute here and add support within our grizzly manifests.
Pull request here: https:/
This requires 41173 as mentioned above, but 41173 is in master rather than stable branch. We'll need to cherry pick it back into stable/grizzly before PR 139 can merge. An upstream review has been submitted for the cherry pick here:
https:/
Work Items
Work items:
research config_drive: DONE
implement change: DONE
Cherry pick upstream's 41173 into stable/grizzly: DONE
Merge upstream puppet-openstack: DONE
