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

Using ovs network plugin #1167

Closed
iwarapter opened this Issue Jul 24, 2017 · 9 comments

Comments

Projects
None yet
8 participants
@iwarapter
Copy link

iwarapter commented Jul 24, 2017

Is it possible to use the ovs network plugins with minishift? I'd like to use ovs-multitenant and ovs-networkpolicy, i have patched the config into the openshift config:

minishift openshift config set --patch '{"networkConfig": {"networkPluginName": "redhat/openshift-ovs-multitenant"}}'

I'm using the centos base image and have installed openvswitch, but not sure how best to configure it to get this all working :(

@gbraad

This comment has been minimized.

Copy link
Member

gbraad commented Jul 24, 2017

@jorgemoralespou

This comment has been minimized.

Copy link
Contributor

jorgemoralespou commented Jul 24, 2017

@iwarapter

This comment has been minimized.

Copy link

iwarapter commented Jul 26, 2017

Hi guys, thanks for your answer, i ended up using the vagrant ansible containerized openshift deployment in the end for this, but following from the bug report you linked do you know if anyone is actively working on it? I'd be happy to contribute to help get the feature in minishift if possible.

@csrwng

This comment has been minimized.

Copy link

csrwng commented Jul 26, 2017

On the origin side side, we want to move to using openshift-ansible playbooks for cluster up, that way we can leverage the existing playbook codebase. I don't see us putting the effort to add ovs before that happens.

@jorgemoralespou

This comment has been minimized.

Copy link
Contributor

jorgemoralespou commented Jul 27, 2017

In minishift we could easily create an addon to do this.

@csrwng oc cluster up + ansible? Where did we leave the "oc cluster up is the fastest way to soon up a cluster, not to do an installation?"

Maybe it's time to fork 😂😂😂

@csrwng

This comment has been minimized.

Copy link

csrwng commented Jul 27, 2017

@jorgemoralespou it may not be as bad as you think ... an openshift master should be running fairly quickly, but there's no reason to duplicate the provisioning code inside the cluster up command and in the openshift-ansible repo.

@stale

This comment has been minimized.

Copy link

stale bot commented Oct 14, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale label Oct 14, 2017

@coolbrg

This comment has been minimized.

Copy link
Member

coolbrg commented Oct 16, 2017

Still under discussion.

@stale stale bot removed the status/stale label Oct 16, 2017

@coolbrg coolbrg added this to the v1.9.0 milestone Oct 16, 2017

@hferentschik hferentschik modified the milestones: v1.9.0, v1.10.0 Oct 30, 2017

@LalatenduMohanty LalatenduMohanty modified the milestones: v1.10.0, v1.11.0 Nov 27, 2017

@LalatenduMohanty LalatenduMohanty modified the milestones: v1.11.0, v1.12.0 Dec 12, 2017

@LalatenduMohanty LalatenduMohanty modified the milestones: v1.12.0, v1.13.0 Jan 4, 2018

@LalatenduMohanty

This comment has been minimized.

Copy link
Member

LalatenduMohanty commented Jan 22, 2018

Closed this issue as we do not have any plan to address this.

@LalatenduMohanty LalatenduMohanty modified the milestones: v1.13.0, v1.12.0 Jan 22, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment