-
Notifications
You must be signed in to change notification settings - Fork 23
Add docs for upgrading to Caracal #1250
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -35,6 +35,64 @@ Notable changes in the |current_release| Release | |
There are many changes in the OpenStack |current_release| release described in | ||
the release notes for each project. Here are some notable ones. | ||
|
||
RabbitMQ SLURP upgrade | ||
---------------------- | ||
|
||
Because this is a SLURP upgrade, RabbitMQ must be upgraded manually from 3.11, | ||
to 3.12, then to 3.13 on Antelope before the Caracal upgrade. This upgrade | ||
should not cause an API outage (though it should still be considered "at | ||
risk"). | ||
|
||
There are two prerequisites: | ||
|
||
1. Kolla-Ansible should be upgraded to the latest version: | ||
|
||
.. code-block:: bash | ||
|
||
cd $KOLLA_SOURCE_PATH | ||
git fetch && git pull | ||
$KOLLA_VENV_PATH/bin/pip install . | ||
Comment on lines
+52
to
+54
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
|
||
2. The RabbitMQ container image tag must be equal to or newer than | ||
``20240823T101942``. Check the timestamps in | ||
``etc/kayobe/kolla-image-tags.yml``. | ||
Comment on lines
+56
to
+58
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would it make sense to do this after updating to latest antelope? (L212) Then this would always be true. |
||
|
||
Once complete, upgrade RabbitMQ: | ||
|
||
.. code-block:: bash | ||
|
||
kayobe overcloud service configuration generate --node-config-dir /tmp/ignore -kt none | ||
kayobe kolla ansibe run "rabbitmq-upgrade 3.12" | ||
kayobe kolla ansibe run "rabbitmq-upgrade 3.13" | ||
Comment on lines
+65
to
+66
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
|
||
RabbitMQ quorum queues | ||
---------------------- | ||
|
||
In Caracal, quorum queues are enabled by default for RabbitMQ. This is | ||
different to Antelope which used HA queues. Before upgrading to Caracal, it is | ||
strongly recommended that you migrate from HA to quorum queues. The migration | ||
is automated using a script. | ||
|
||
.. warning:: | ||
This migration will stop all services using RabbitMQ and cause an | ||
extended API outage while queues are migrated. It should only be | ||
performed in a pre-agreed maintenance window. | ||
|
||
Set the following variables in your kolla globals file (i.e. | ||
``$KAYOBE_CONFIG_PATH/kolla/globals.yml`` or | ||
``$KAYOBE_CONFIG_PATH/environments/$KAYOBE_ENVIRONMENT/kolla/globals.yml``): | ||
|
||
.. code-block:: yaml | ||
|
||
om_enable_rabbitmq_high_availability: false | ||
om_enable_rabbitmq_quorum_queues: true | ||
|
||
Then execute the migration script: | ||
|
||
.. code-block:: bash | ||
|
||
$KAYOBE_CONFIG_PATH/../../tools/rabbitmq-quorum-migration.sh | ||
Alex-Welsh marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
Heat disabled by default | ||
------------------------ | ||
|
||
|
@@ -54,6 +112,24 @@ using Heat, and disable the service. | |
|
||
TODO: guide for disabling Heat | ||
|
||
Designate sink disabled by default | ||
---------------------------------- | ||
|
||
Designate sink is optional designate service which listens for event | ||
Notifications, primarily from Nova and Neutron. It is disabled by default (when | ||
designate is enabled) in Caracal. It is not required for Designate to function. | ||
Comment on lines
+118
to
+120
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Designate sink is an optional Designate service which listens for event |
||
|
||
If you still wish to use it, you should set the flag manually: | ||
|
||
.. code-block:: yaml | ||
:caption: ``kolla/globals.yml`` | ||
|
||
designate_enable_notifications_sink: true | ||
|
||
If you are using Designate and do not make this change, the Antelope | ||
``designate-sink`` container will remain on the controllers after the upgrade. | ||
It must be removed manually. | ||
MoteHue marked this conversation as resolved.
Show resolved
Hide resolved
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Kolla-ansible so lazy :D |
||
|
||
Grafana Volume | ||
-------------- | ||
The Grafana container volume is no longer used. If you wish to automatically | ||
|
@@ -85,7 +161,16 @@ configuration must change the names of those files in | |
Known issues | ||
============ | ||
|
||
* None! | ||
* OVN breaks on Rocky 9 deployments where hostnames are FQDNs. | ||
Before upgrading, you must make sure no compute or controller nodes have any | ||
``.`` characters in their hostnames. Run the command below to check: | ||
|
||
.. code-block:: bash | ||
|
||
kayobe overcloud host command run --command "grep -v \'\.\' /etc/hostname" --show-output | ||
|
||
There is currently no known fix for this issue aside from reprovisioning. A | ||
patch will be developed soon. | ||
|
||
Security baseline | ||
================= | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This feels like it's in the wrong section (Notable changes in the |current_release| Release)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps it should go into prerequisites?