Skip to content

Added private_network_only flag to private vsi#1

Open
rbustami wants to merge 1 commit intoibm-cloud-architecture:masterfrom
rbustami:master
Open

Added private_network_only flag to private vsi#1
rbustami wants to merge 1 commit intoibm-cloud-architecture:masterfrom
rbustami:master

Conversation

@rbustami
Copy link
Copy Markdown

@rbustami rbustami commented Sep 29, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant