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 bridge network to running container #743

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

Add bridge network to running container #743

hickeng opened this issue May 20, 2016 · 3 comments
Labels
area/vsphere Intergration and interoperation with vSphere component/portlayer/network component/tether kind/enhancement Behavior that was intended, but we want to make better severity/4-minor Low usability or functional impact. Often has an easy workaround.

Comments

@hickeng
Copy link
Member

hickeng commented May 20, 2016

Where #703 covers the personality portion of network connect and the application to stopped containers, this issue adds support for running containers. The workflow is:

// pseudo-code for adding two networks (although this isn't likely supported via the client cli constructs)
netA := network.Get(netAID)
netB := network.Get(netBID)
handle := execution.Get(id)
handle = network.Join(handle, netA)
handle = network.Join(handle, netB)
handle = network.Bind(handle)

This issue is for doing so with the IPAM segregation based bridge networks only, not the mapped vSphere networks that require a PCI hotadd of a new vNIC.

@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 self-assigned this 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 and needs to be decomposed

@zjs
Copy link
Member

zjs commented Mar 5, 2019

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. area/vsphere Intergration and interoperation with vSphere kind/enhancement Behavior that was intended, but we want to make better 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
area/vsphere Intergration and interoperation with vSphere component/portlayer/network component/tether kind/enhancement Behavior that was intended, but we want to make better severity/4-minor Low usability or functional impact. Often has an easy workaround.
Projects
None yet
Development

No branches or pull requests

6 participants