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

Add signpost text to the bridge network settings that explicitly notes this should be an isolated L2 broadcast domain #60

Closed
zjs opened this issue Nov 16, 2017 · 3 comments
Assignees
Labels
component/plugin/h5c The plugin for the vSphere HTML5 client kind/enhancement Behavior that was intended, but we want to make better team/lifecycle

Comments

@zjs
Copy link
Member

zjs commented Nov 16, 2017

Additionally, we could say that it should be a VXLAN or should be configured with a VLAN ID.

@zjs zjs added component/plugin/h5c The plugin for the vSphere HTML5 client kind/enhancement Behavior that was intended, but we want to make better team/lifecycle labels Nov 16, 2017
@cristianfalcone cristianfalcone self-assigned this Nov 21, 2017
@jak-atx jak-atx added this to the Sprint 22 Lifecycle milestone Nov 22, 2017
@zjs
Copy link
Member Author

zjs commented Nov 29, 2017

This is a very low priority, but could be included in the release if it is a simple text change that can be made without sacrificing something else.

@lweitzman
Copy link

I suggest: "Bridge networks are the network or networks that container VMs use to communicate with each other. Every virtual container host (VCH) must have a unique bridge network. Do not use the bridge network for any other VM workloads, or as a bridge for more than one VCH."
@pdaigle @hickeng @zjs

@stuclem
Copy link
Contributor

stuclem commented Dec 4, 2017

@cristianfalcone, the proposed text from @lweitzman looks good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/plugin/h5c The plugin for the vSphere HTML5 client kind/enhancement Behavior that was intended, but we want to make better team/lifecycle
Projects
None yet
Development

No branches or pull requests

5 participants