openstack/kayobe
Code Issues Proposed changes

Remove outdated upgrade step

Browse Source 
Migrating to Ironic hardware types was required in Rocky. This can now
be removed from upgrading instructions.

Change-Id: I0510db9fd1b8dd72540c83173267491b32728330
This commit is contained in:
Pierre Riteau 2021-06-17 16:10:57 +02:00
parent 2445ec740e
commit bca2369894
1 changed files with 0 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
doc/source/upgrading.rst
View File

@ -271,29 +271,6 @@ locally::
In order to push images to a registry after they are built, add the ``--push``
argument.
Migrating to Ironic Hardware Types
----------------------------------
Classic drivers in ironic were `deprecated
<https://docs.openstack.org/releasenotes/ironic/queens.html#relnotes-10-1-0-stable-queens-deprecation-notes>`__
in the Queens release, and `removed
<https://docs.openstack.org/releasenotes/ironic/rocky.html#relnotes-11-0-0-stable-rocky-upgrade-notes>`__
in the Rocky release. Nodes registered with ironic in Pike and earlier releases
of Bifrost use the classic drivers by default, and will need to be migrated to
use the new hardware types. The :ironic-doc:`ironic documentation
<admin/upgrade-to-hardware-types.html>` provides details for how to do this,
but for the default case of the ``agent_ipmitool`` driver the following
procedure may be used, replacing ``<node>`` with the name of the host to
migrate:
.. code-block:: console
$ docker exec -it bifrost_deploy bash
(bifrost_deploy) $ export OS_CLOUD=bifrost
(bifrost_deploy) $ baremetal node maintenance set <node>
(bifrost_deploy) $ baremetal node set <node> --driver ipmi
(bifrost_deploy) $ baremetal node maintenance unset <node>
Upgrading Containerised Services
--------------------------------