Added private_network_only flag to private vsi #1
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.
The expectation for this solution is that one of the virtual servers that gets created is private only since it's only connected to a private VLAN (see arch diagram in readme)
Unfortunately I'm able to connect to the private VSI over the public network & a public IP is assigned to the virtual server. From the VSI's configuration properties it looks like a public VLAN was auto-assigned to it
The problem here is that the resource needs the private_network_only flag.
I've done high level test (provisioned VSI successfully, no public IP exposed & no public vlan attached). I haven't tested to make sure file storage is correctly mounted to the VSI. Please comment if additional tests are necessary