-
Notifications
You must be signed in to change notification settings - Fork 175
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 running container to mapped network #745
Labels
component/portlayer/network
component/tether
severity/4-minor
Low usability or functional impact. Often has an easy workaround.
Comments
This was referenced May 20, 2016
Already in the release notes, so removing the kind/note tag. |
This is too big to be in the backlog and needs to be decomposed more |
In addition to the above, this is blocked by vSphere guestinfo volatility bug (fixed in 6.5U1, possibly backported to a 6.0 update release). This can be considered once we no longer support versions that are impacted by this bug. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component/portlayer/network
component/tether
severity/4-minor
Low usability or functional impact. Often has an easy workaround.
Where #743 adds a bridge network to a running container, this adds mapped vSphere networks that require PCI hotadd of a new vNIC. The workflow in the portlayer should be identical to the pseudo-code in #743. The network.Join operation adding a DeviceChange entry for the new NIC should be invisible to the callers.
On the tether side this requires hotadd and configuration of the new vNIC. This may not require #742 as the hotadd event itself can be used as a trigger, as such I do not consider it a dependency for this work.
The text was updated successfully, but these errors were encountered: