Skip to content

Kuryr: Add information about amphora to ovn-octavia upgrades #22878

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.

Sign up for GitHub

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

Merged
maxwelldb merged 8 commits into from
Jul 7, 2020
Merged

Kuryr: Add information about amphora to ovn-octavia upgrades #22878

Changes from 4 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
afa2c60
Kuryr: Add information about amphora to ovn-octavia upgrades
luis5tb Jun 15, 2020
1a07f9e
Merge branch 'master' into octavia-upgrades
luis5tb Jun 29, 2020
34e8a3d
Editing pass
maxwelldb Jun 29, 2020
a77739f
Changes from dev comments
maxwelldb Jul 2, 2020
2a5d089
Dev feedback tweak
maxwelldb Jul 3, 2020
fef0d7c
Some rewording, then moving content to Networking
maxwelldb Jul 3, 2020
a4af1a0
Reshuffling and relabeling
maxwelldb Jul 6, 2020
c582b35
Addressing peer review feedback
maxwelldb Jul 7, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
96 changes: 96 additions & 0 deletions modules/installation-osp-kuryr-octavia-configuration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -240,3 +240,99 @@ If Kuryr uses `ovn` instead of Amphora, it offers the following benefits:
* Reduced network latency.
* Increased service creation speed by using OpenFlow rules instead of a VM for each Service.
* Distributed load balancing actions across all nodes instead of centralized on Amphora VMs.


[id="installation-osp-kuryr-octavia-driver_upgrade_{context}"]
== Upgrading Octavia provider drivers after installation

You can upgrade a cluster that is deployed on {rh-openstack-first} from the Octavia Amphora
Comment thread
maxwelldb marked this conversation as resolved.
Outdated
provider driver to the Octavia OVN provider driver.

[IMPORTANT]
====
Kuryr replaces existing load balancers after you change provider drivers. This process
results in some downtime.
====

.Prerequisites

* Install the {rh-openstack} CLI, `openstack`.

* Install the {product-title} CLI, `oc`.

* Verify that the Octavia OVN driver on {rh-openstack} is enabled.
+
[TIP]
====
To view a list of available Octavia drivers, on a command line, enter `openstack loadbalancer provider list`.
You should see the `ovn` driver in the command's output.
====

.Procedure

To change from the Octavia Amphora provider driver to Octavia OVN:

. Open the `kuryr-config` ConfigMap. On a command line, enter:
+
----
$ oc -n openshift-kuryr edit cm kuryr-config
----

. In the ConfigMap, delete the line that contains `kuryr-octavia-provider: default`. For example:
+
----
...
kind: ConfigMap
metadata:
annotations:
networkoperator.openshift.io/kuryr-octavia-provider: default <1>
...
----
<1> Delete this line. The cluster will regenerate it with `ovn` as the value.
+
After making this modification, wait for the `kuryr-controller` and `kuryr-cni` pods to redeploy. This process may take several minutes.

@luis5tb luis5tb Jul 3, 2020

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

this should be "wait until the Cluster Network Operator detects the modification and redeploy the kuryr-controller and kuryr-cnis"


. Verify that the `kuryr-config` ConfigMap annotation is present with `ovn` as its value. On a command line, enter:
+
----
$ oc -n openshift-kuryr edit cm kuryr-config
----
+
The `ovn` provider value should be present in the output:
+
----
...
kind: ConfigMap
metadata:
annotations:
networkoperator.openshift.io/kuryr-octavia-provider: ovn
...
----

. Verify that {rh-openstack} recreated its load balancers.

.. On a command line, type:
+
----
$ openstack loadbalancer list | grep amphora
----
+
You should see a single Amphora load balancer. For example:
+
----
a4db683b-2b7b-4988-a582-c39daaad7981 | ostest-7mbj6-kuryr-api-loadbalancer | 84c99c906edd475ba19478a9a6690efd | 172.30.0.1 | ACTIVE | amphora
----

.. Then, type:
+
----
$ openstack loadbalancer list | grep ovn
----
+
The remaining load balancers should be the `ovn` type. For example:
+
----
2dffe783-98ae-4048-98d0-32aa684664cc | openshift-apiserver-operator/metrics | 84c99c906edd475ba19478a9a6690efd | 172.30.167.119 | ACTIVE | ovn
0b1b2193-251f-4243-af39-2f99b29d18c5 | openshift-etcd/etcd | 84c99c906edd475ba19478a9a6690efd | 172.30.143.226 | ACTIVE | ovn
f05b07fc-01b7-4673-bd4d-adaa4391458e | openshift-dns-operator/metrics | 84c99c906edd475ba19478a9a6690efd | 172.30.152.27 | ACTIVE | ovn
----