Skip to content
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

Docs: reinforce warning against using networks not available to all hosts #1189

Closed
stuclem opened this issue Nov 30, 2017 · 5 comments
Closed
Assignees
Labels
area/pub/vsphere Published documentation for vSphere administrators area/pub Published documentation for end-users product/engine Related to the vSphere Integrated Containers Engine

Comments

@stuclem
Copy link
Contributor

stuclem commented Nov 30, 2017

Per vmware/vic-ui#73 (comment) we need to reinforce the warning in the docs about not using networks that are not available to all hosts in the cluster.

@stuclem stuclem added product/engine Related to the vSphere Integrated Containers Engine area/pub Published documentation for end-users priority/high area/pub/vsphere Published documentation for vSphere administrators labels Nov 30, 2017
@stuclem stuclem self-assigned this Nov 30, 2017
@stuclem
Copy link
Contributor Author

stuclem commented Dec 12, 2017

Beefed up the note that all hosts must be able to access all DPGs in:

@hmahmood is this OK? Thanks!

@stuclem
Copy link
Contributor Author

stuclem commented Dec 29, 2017

@hmahmood can you please review the following note?:


IMPORTANT: All hosts in a cluster must be attached to the port groups that you use for the VCH networks and for any mapped container networks.


Also, can you please take another look at the entire section on Networking Requirements for VCH Deployment? Thanks!

@hmahmood
Copy link
Contributor

Shouldn't this be a recommendation instead of a requirement? That note makes it seems like it is a requirement.

From the section on Networking: "If you use the Create Virtual Container Host wizard to deploy VCHs, you must create and use a port group for the public network." Is this a requirement when using the wizard only or in general? It seems like this should again be a recommendation and we should caution against it, not be an absolute requirement.

@stuclem
Copy link
Contributor Author

stuclem commented Jan 8, 2018

Thanks @hmahmood, I only just saw this. In the UI, public network is mandatory and it is a requirement to create a DPG for it. In the CLI, if you don't specify --public-network, then it defaults to VM Network. So, it's a requirement in the UI and a recommendation in the CLI.

For the note about all hosts being attached to PGs, I downgraded it to "All hosts should...." rather than "must".

@stuclem
Copy link
Contributor Author

stuclem commented Jan 18, 2018

Merged in #1259

@stuclem stuclem closed this as completed Jan 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/pub/vsphere Published documentation for vSphere administrators area/pub Published documentation for end-users product/engine Related to the vSphere Integrated Containers Engine
Projects
None yet
Development

No branches or pull requests

2 participants