Improve the special charm procedures page

Improve wording on the special charm procedures page
(it currently is at odds with channeled charms) and
streamline the reference back to the rest of the
upgrade pages.

Change-Id: I4f39e75fdda968a280f230283cf3ea41d7397c51
This commit is contained in:
Peter Matulis 2022-05-24 16:44:15 -04:00
parent 2fa962231e
commit 06d91d4d2b
1 changed files with 6 additions and 14 deletions

View File

@ -2,17 +2,13 @@
Special charm procedures
========================
The OpenStack charms are designed to accommodate every supported series and
OpenStack release wherever possible. However, upgrades (of either of the three
types) may occasionally introduce unavoidable challenges. For instance, it
could be that a charm is replaced by an entirely new charm on a new series or a
new charm is needed to accommodate a new service on a new OpenStack release.
These kinds of special procedures are documented on this page.
Upgrades, of either of the three types, may occasionally introduce unavoidable
challenges. For instance, it could be that a charm is replaced by an entirely
new charm on a new series or a new charm is needed to accommodate a new service
on a new OpenStack release. These kinds of special procedures are documented
on this page.
The items on this page are distinct from those found on the following pages:
* the `Various issues`_ page
* the dedicated `Upgrade issues`_ page
See the :doc:`upgrade-overview` page for general upgrade information.
Procedures
----------
@ -22,7 +18,3 @@ Procedures
* :doc:`placement charm: OpenStack upgrade to Train <placement-charm-upgrade-to-train>`
* :doc:`ceph charm: migration to ceph-mon and ceph-osd <ceph-charm-migration>`
* :doc:`All charms: migration to channels <charmhub-migration>`
.. LINKS
.. _Various issues: various-issues.html
.. _Upgrade issues: upgrade-issues.html