-
Notifications
You must be signed in to change notification settings - Fork 1.1k
openstack: read the dynamic metadata group vendor_data2.json #777
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
b169d2c
openstack: read the dynamic metadata group vendor_data2.json
f67324a
Merge branch 'master' into vendor_data2
andrewbogott c5c3c42
Merge branch 'master' into vendor_data2
andrewbogott 7a89399
Revert "ssh_util: handle non-default AuthorizedKeysFile config (#586)…
OddBloke 8feacec
integration_tests: log image serial if available (#772)
OddBloke ea45f7a
Add antonyc to .github-cla-signers (#747)
chaporgin eee7b69
Use proper spelling for Red Hat (#778)
dankenigsberg 6bde21b
doc: avoid two warnings (#781)
dankenigsberg 7c80e78
Adding self to cla signers (#776)
andrewbogott 66bb59e
flake8 fixes
40831d4
Merge branch 'vendor_data2' of github.com:andrewbogott/cloud-init int…
64a89c5
Merge branch 'master' into vendor_data2
andrewbogott dc778cf
Another flake8 fix because I'm hopeless
5679729
Refactor _store_userdata/_store_vendordata/_store_vendordata2 to be D…
9f4ff70
Make _consume_vendordata/_consume_vendordata2 DRYer
1dd2b8a
Add some docs for OpenStack dynamic vendordata (aka vendordata2)
555d671
Merge branch 'master' into vendor_data2
andrewbogott 9588785
More linter fixes
a72442f
Use lazy % formatting in a logline
381bacc
flake8 fix
fdb9541
_store_processeddata: remove an unneeded typecast
andrewbogott 1f87a28
Fix misplaced vi hint in openstack.rst
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should not have been put here. A single datasource (openstack) has a thing called 'vendordata2'. Shouldn't the change have been made in openstack datasource rather than propagating up to the base class?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @smoser. I'm looking at how to move this handling into openstack-specific code and it's starting to seem like a pretty big refactor. It's easy enough to move the things from init.py into DataSourceOpenStack.py but then the vendordata2 handlers in stages.py will need to be made aware of which subclasses do or don't support vendordata2; failing that we could subclass things in stages.py but as best I can tell that isn't currently done anywhere so would require some additional scaffolding.
If you still want me to go ahead with refactoring I can work on it but I welcome your thoughts about how to avoid littering the existing code with checks :) It might also be worth creating a new bug to track.
(Of course when I wrote the initial patchset I was imagining that this might be a feature that other datasources would want to implement but that may not be realistic.)
-Andrew
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused as to how that would be any different than
vendor datato cloud-init.As far as rework, i would have thought that you would just change the datasource to say : If there is vendor-data2, present it as vendor-data, otherwise use vendor-data.