Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

Determine bridge and container network interface requirements #1421

Closed
1 task
awh opened this issue Sep 14, 2015 · 2 comments
Closed
1 task

Determine bridge and container network interface requirements #1421

awh opened this issue Sep 14, 2015 · 2 comments
Labels
Milestone

Comments

@awh
Copy link
Contributor

awh commented Sep 14, 2015

In certain types of deployment (e.g. CNI) weave will not be in charge of creating bridge devices and container network interfaces. An analysis of weave must be performed to identify specific problems and document them as issues for resolution.

@awh awh added the feature label Sep 14, 2015
@awh awh added this to the 1.2.0 milestone Sep 14, 2015
@awh awh changed the title Work with existing bridges and container network interfaces Determine bridge and container network interface requirements Sep 14, 2015
@awh awh added chore and removed feature labels Sep 14, 2015
@rade rade modified the milestone: 1.2.0 Oct 16, 2015
@rade rade added this to the 1.3.0 milestone Oct 29, 2015
@awh awh removed this from the 1.3.0 milestone Nov 9, 2015
@bboreham
Copy link
Contributor

bboreham commented Aug 3, 2016

I think when this was filed the thinking was that we could piggy-back on the CNI 'bridge' plugin. Since then we have implemented our own Weave Net CNI plugin which does create and set up veths.

We tell people to use this after calling weave launch, which will create the bridge, so that part of the premise also bears re-considering.

@bboreham
Copy link
Contributor

Closing: it's been a long time since anyone asked about working with an existing bridge.

@brb brb added this to the n/a milestone Feb 21, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants