Added bastion host option for Openstack builder #608
+47
−3
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is the problem that this PR is trying to fix?
Using a jump host to allow SSH to dynamically created VM for image creation. Using jump host allows us to restrict number of public IPs for the Openstack setup. Although usage of bastion host is kept optional to cater both OSU and PDC. Also updated example.env file to reflect additional configurable parameters for bastion host, ssh keys and v3 API. We would like to drive image creation using SSH keys both in OSU and PDC.
What approach did you choose and why?
Tested over PDC Openstack setup.
How can you test this?
What feedback would you like, if any?
Please review and let us know your comments. Thanks !