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 running container to mapped network #745

Open
hickeng opened this issue May 20, 2016 · 3 comments
Open

Add running container to mapped network #745

hickeng opened this issue May 20, 2016 · 3 comments
Labels
component/portlayer/network component/tether severity/4-minor Low usability or functional impact. Often has an easy workaround.

Comments

@hickeng
Copy link
Member

hickeng commented May 20, 2016

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.

@stuclem stuclem added the impact/doc/user Requires changes to official user documentation label May 20, 2016
@stuclem stuclem removed the impact/doc/user Requires changes to official user documentation label May 30, 2016
@mdubya66 mdubya66 added this to the VIC GA Release milestone Jul 1, 2016
@hmahmood hmahmood changed the title Add mapped network to running container Add running container to mapped network Aug 3, 2016
@mdubya66 mdubya66 removed this from the VIC GA Release milestone Sep 19, 2016
@mdubya66 mdubya66 added the impact/doc/note Requires creation of or changes to an official release note label Sep 20, 2016
@stuclem
Copy link
Contributor

stuclem commented Nov 7, 2016

Already in the release notes, so removing the kind/note tag.

@hickeng hickeng removed the impact/doc/note Requires creation of or changes to an official release note label Nov 7, 2016
@hmahmood hmahmood removed their assignment Jan 17, 2017
@mhagen-vmware
Copy link
Contributor

This is too big to be in the backlog and needs to be decomposed more

@zjs
Copy link
Member

zjs commented Mar 5, 2019

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.

@zjs zjs added severity/4-minor Low usability or functional impact. Often has an easy workaround. and removed priority/p2 labels Mar 5, 2019
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.
Projects
None yet
Development

No branches or pull requests

6 participants