openstack
/
charm-deployment-guide
Code Issues Proposed changes

Merge "Move Octavia upgrade note to issues page"

This commit is contained in:
Zuul 2022-04-19 22:11:22 +00:00 committed by Gerrit Code Review
parent 17913e8d1a 8706a17dc3
commit 47e26fc74c
2 changed files with 18 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
deploy-guide/source/upgrade-issues.rst
View File

@ -10,7 +10,12 @@ The items on this page are distinct from those found on the following pages:
* the `Various issues`_ page
* the `Special charm procedures`_ page
The issues are organised by upgrade type.
The issues are organised by upgrade type:
.. contents::
:local:
:depth: 2
:backlinks: top
Charm upgrades
--------------
@ -264,6 +269,17 @@ Prior to upgrading to Victoria users of FWaaS should remove any existing
firewall groups to avoid the possibility of orphaning active firewalls (see the
`FWaaS v2 CLI documentation`_).
Octavia
~~~~~~~
An Octavia upgrade may entail an update of its load balancers (amphorae) as a
post-upgrade task. Reasons for doing this include:
* API incompatibility between the amphora agent and the new Octavia service
* the desire to use features available in the new amphora agent or haproxy
See the upstream documentation on `Rotating amphora images`_.
Series upgrades
---------------
@ -300,6 +316,7 @@ error can be resolved with:
.. _21.10 Release Notes: https://docs.openstack.org/charm-guide/latest/2110.html
.. _FWaaS v2: https://docs.openstack.org/neutron/ussuri/admin/fwaas.html
.. _FWaaS v2 CLI documentation: https://docs.openstack.org/python-neutronclient/ussuri/cli/osc/v2/firewall-group.html
.. _Rotating amphora images: https://docs.openstack.org/octavia/latest/admin/guides/operator-maintenance.html#rotating-the-amphora-images
.. BUGS
.. _LP #1825999: https://bugs.launchpad.net/charm-nova-compute/+bug/1825999

11
deploy-guide/source/upgrade-openstack.rst
View File

@ -353,16 +353,6 @@ charm's OpenStack service will be updated.
ovn-central upgrade and the completion of the nova-compute upgrade. They are
deliberately placed in close proximity to each other for this reason.
.. note::
An Octavia upgrade may entail an update of its load balancers (amphorae) as
a post-upgrade task. Reasons for doing this include:
* API incompatibility between the amphora agent and the new Octavia service
* the desire to use features available in the new amphora agent or haproxy
See the upstream documentation on `Rotating amphora images`_.
.. _perform_the_upgrade:
Perform the upgrade
@ -574,7 +564,6 @@ explicit steps used to upgrade a basic cloud.
.. _Release Notes: https://docs.openstack.org/charm-guide/latest/release-notes.html
.. _Ubuntu Cloud Archive: https://wiki.ubuntu.com/OpenStack/CloudArchive
.. _Upgrades: https://docs.openstack.org/operations-guide/ops-upgrades.html
.. _Rotating amphora images: https://docs.openstack.org/octavia/latest/admin/guides/operator-maintenance.html#rotating-the-amphora-images
.. _Percona strict mode: https://www.percona.com/doc/percona-xtradb-cluster/LATEST/features/pxc-strict-mode.html
.. BUGS