OpenStack: Use config-drive by default and metadata API as fallback #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
openstack: use config-drive by default and metadata API as fallback
Related: coreos/afterburn#462
OpenStack: Use config-drive by default and metadata API as fallback
Use afterburn
openstack
provider implemented on coreos/afterburn#462 to use config-drive first and metadata API as a fallback mechanism.Solves flatcar/Flatcar#1445
How to use
Build OpenStack image based on flatcar/scripts#2009 to validate it does not bring regression on OpenStack platform.
Testing done
To be performed on flatcar/scripts#2009.
changelog/
directory (user-facing change, bug fix, security fix, update)/boot
and/usr
size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.