Skip to content

Conversation

@luis5tb
Copy link
Contributor

@luis5tb luis5tb commented Jun 15, 2020

This PR describe the steps to performan an amphora to ovn-octavia
migration when using Kuryr. This allows to avoid the problem of
generating one VM per services when using Kuryr as CNI.

This PR describe the steps to performan an amphora to ovn-octavia
migration when using Kuryr. This allows to avoid the problem of
generating one VM per services when using Kuryr as CNI.
@maxwelldb
Copy link
Contributor

@luis5tb

  1. Is there a BZ or something for this?
  2. How urgent of a PR is it?

@maxwelldb maxwelldb added this to the Next Release milestone Jun 15, 2020
@luis5tb
Copy link
Contributor Author

luis5tb commented Jun 15, 2020

@luis5tb

1. Is there a BZ or something for this?

https://bugzilla.redhat.com/show_bug.cgi?id=1846862

2. How urgent of a PR is it?

Not urgent at the moment, as we still need to do the backport to 4.5 (of the support itself)

@maxwelldb
Copy link
Contributor

Thanks!

@maxwelldb
Copy link
Contributor

Note to self: This will probably have to be broken out into its own assembly. NBD, but will require restructuring the PR.

@rlobillo
Copy link

/lgtm upgrade worked perfectly fine following the instructions

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 26, 2020
@maxwelldb maxwelldb self-requested a review June 26, 2020 16:40
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 29, 2020
@maxwelldb
Copy link
Contributor

Thoughts on 34e8a3d, @luis5tb?

@maxwelldb maxwelldb self-assigned this Jul 2, 2020
@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 2, 2020
Copy link
Contributor

@maxwelldb maxwelldb left a comment

Choose a reason for hiding this comment

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

How's this, now, @luis5tb?

----
<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.
Copy link
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"

@maxwelldb
Copy link
Contributor

@luis5tb Made a few more changes based on your comments. I also moved the topic into the Networking section, as it seems like this task must task place post-installation. Thoughts?

http://file.rdu.redhat.com/mbridges/Jul03/octavia-upgrade/networking/load-balancing-openstack.html

@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 3, 2020
@luis5tb
Copy link
Contributor Author

luis5tb commented Jul 3, 2020

@luis5tb Made a few more changes based on your comments. I also moved the topic into the Networking section, as it seems like this task must task place post-installation. Thoughts?

http://file.rdu.redhat.com/mbridges/Jul03/octavia-upgrade/networking/load-balancing-openstack.html

I like the idea of having it as a different section, but not the naming of it. This is specific to Kuryr and ovn-octavia, and it is not mentioned on the title or link. It could be misleading. Perhaps in the same way as there is a section there named "Using SCTP", we can call this one "Using OVN-Octavia loadbalancer with Kuryr SDN"

@maxwelldb
Copy link
Contributor

@luis5tb My thought is to make an OSP load balancing space now, with this topic as the sole section in it. Later, it would also contain more general OSP load balancing information (there's a topic that was pulled a few releases ago that might be fit for inclusion).

So, it would end up like:
Networking -> Load balancing with OpenStack -> Using the OVN Octavia load balancer with Kuryr SDN

Does that seem sensible?

@luis5tb
Copy link
Contributor Author

luis5tb commented Jul 6, 2020

@luis5tb Made a small change that I thought made sense for the title. See preview here: http://file.rdu.redhat.com/mbridges/Jul06/octavia-upgrade/networking/load-balancing-openstack.html

/lgtm

@openshift-ci-robot
Copy link

@luis5tb: you cannot LGTM your own PR.

Details

In response to this:

@luis5tb Made a small change that I thought made sense for the title. See preview here: http://file.rdu.redhat.com/mbridges/Jul06/octavia-upgrade/networking/load-balancing-openstack.html

/lgtm

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.

@maxwelldb
Copy link
Contributor

Thanks!

@luis5tb Did you work with any QE folks on this who'd know it best and could ack this PR, or should I just mention a bunch of Kuryr QE team folks here? 😁

@luis5tb
Copy link
Contributor Author

luis5tb commented Jul 6, 2020

Thanks!

@luis5tb Did you work with any QE folks on this who'd know it best and could ack this PR, or should I just mention a bunch of Kuryr QE team folks here?

@rlobillo already tested this

@maxwelldb
Copy link
Contributor

Cool. Just need a +1 from him here and it's ready for peer review.

@maxwelldb maxwelldb requested a review from rlobillo July 6, 2020 16:16
@rlobillo
Copy link

rlobillo commented Jul 7, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2020
@maxwelldb maxwelldb added the peer-review-needed Signifies that the peer review team needs to review this PR label Jul 7, 2020
@maxwelldb
Copy link
Contributor

@openshift/team-documentation PTAL. Large change.

@bobfuru bobfuru self-requested a review July 7, 2020 15:39
Copy link
Contributor

@bobfuru bobfuru left a comment

Choose a reason for hiding this comment

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

Some nitpicks based on guidelines and don't forget to squash commits. Otherwise, LGTM.

@bobfuru bobfuru added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Jul 7, 2020
@maxwelldb maxwelldb self-requested a review July 7, 2020 17:50
@openshift-ci-robot
Copy link

New changes are detected. LGTM label has been removed.

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2020
@maxwelldb maxwelldb removed the request for review from rlobillo July 7, 2020 20:08
@maxwelldb maxwelldb merged commit ee1a159 into openshift:master Jul 7, 2020
maxwelldb added a commit to maxwelldb/openshift-docs that referenced this pull request Jul 7, 2020
…ft#22878)

This PR adds a procedure for upgrading from an amphora to ovn-octavia provider driver when using OCP + Kuryr on OSP. 

Co-authored-by: Max Bridges <mbridges@redhat.com>
maxwelldb added a commit that referenced this pull request Jul 7, 2020
[enterprise-4.5] Kuryr: Add information about amphora to ovn-octavia upgrades (#22878)
@yuvalk yuvalk mentioned this pull request Mar 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.5 peer-review-done Signifies that the peer review team has reviewed this PR 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.

5 participants