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

OVNKubernetes: introduce OVS anti-selector #357

Merged
merged 2 commits into from Jan 8, 2020
Merged

OVNKubernetes: introduce OVS anti-selector #357

merged 2 commits into from Jan 8, 2020

Conversation

mmirecki
Copy link

OVNKubernetes is shipped with its own openvswitch service running
as a separate daemonset. However, in some cases we may want to use
an external openvswitch running on the host (e.g. to use it for
host networking). In order to support a mixed environment where some
hosts have this external service and some don't, we introduce an
openvswitch anti-selector:

network.operator.openshift.io/external-openvswitch

Note that this selector has to be set before the operator is started.
Otherwise, the label would not take effect on already scheduled
pods.

Related to:
#346

@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 21, 2019
@openshift-ci-robot
Copy link
Contributor

Hi @mmirecki. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Oct 21, 2019
Copy link
Member

@phoracek phoracek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also don't see the node affinity anywhere

bindata/network/ovn-kubernetes/ovs-node.yaml Outdated Show resolved Hide resolved
bindata/network/ovn-kubernetes/ovs-node.yaml Outdated Show resolved Hide resolved
@dcbw
Copy link
Member

dcbw commented Oct 21, 2019

@phoracek @mmirecki Whats the case where some nodes will have system OVS and others will have containerized OVS? Why wouldn't this be consistent across the entire cluster?

@phoracek
Copy link
Member

@dcbw in case you have RHCOS8 masters and RHEL7 workers, where you want to use OVS SLB bonding for workload. I know, very specific. It is easy to install external OVS on RHEL, very hard to have it on RHCOS.

@mmirecki
Copy link
Author

/test e2e-aws-ovn-kubernetes

@openshift-ci-robot
Copy link
Contributor

@mmirecki: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test e2e-aws-ovn-kubernetes

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@danwinship
Copy link
Contributor

/ok-to-test
/retest

@openshift-ci-robot openshift-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 23, 2019
@squeed
Copy link
Contributor

squeed commented Oct 24, 2019

/test e2e-aws-own-kubernetes

@mmirecki
Copy link
Author

/test e2e-aws-ovn-kubernetes

1 similar comment
@mmirecki
Copy link
Author

/test e2e-aws-ovn-kubernetes

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 30, 2019
OVNKubernetes is shipped with its own openvswitch service running
as a separate daemonset. However, in some cases we may want to use
an external openvswitch running on the host (e.g. to use it for
host networking). In order to support a mixed environment where some
hosts have this external service and some don't, we introduce an
openvswitch anti-selector:

network.operator.openshift.io/external-openvswitch

Note that this selector has to be set before the operator is started.
Otherwise, the label would not take effect on already scheduled
pods.
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 30, 2019
@mmirecki
Copy link
Author

/test e2e-aws-ovn-kubernetes

@mmirecki
Copy link
Author

/retest

@mmirecki
Copy link
Author

Documented in PR 375

@phoracek
Copy link
Member

phoracek commented Dec 2, 2019

@squeed similar patch landed for OpenShiftSDN, could we move this one through the finish line?

@mmirecki
Copy link
Author

mmirecki commented Dec 6, 2019

The OpenShiftSDN equivalent PR 346 is merged.
Can we proceed with this one?

Copy link
Contributor

@pecameron pecameron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@squeed Since we are moving ovs to host do we need this?
CC: @JacobTanenbaum @dcbw

@phoracek
Copy link
Member

phoracek commented Dec 6, 2019

@pecameron we'd appreciate if this got in, so we can start initial testing of OVN with external OVS before your patches land.

@squeed
Copy link
Contributor

squeed commented Dec 10, 2019

Okay, now that 4.4 has cut, we can try and merge this. @JacobTanenbaum , can you review please?

@pecameron
Copy link
Contributor

@danwinship @dcbw @JacobTanenbaum PTAL after rebase.

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 7, 2020
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 8, 2020
@mmirecki
Copy link
Author

mmirecki commented Jan 8, 2020

Rebased, please review

@knobunc
Copy link
Contributor

knobunc commented Jan 8, 2020

/lgtm
/approve

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 8, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: knobunc, mmirecki, phoracek

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 8, 2020
@openshift-merge-robot openshift-merge-robot merged commit 3860290 into openshift:master Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants