openstack/ironic
Code Issues Proposed changes

docs: More legacy version references removals

Browse Source 
Change-Id: I4c989f48473dc0755b0e477562ea17c26415f050
Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
This commit is contained in:
Julia Kreger
2025-09-26 11:38:59 -07:00
parent d13ffb4ff5
commit 3e38b1bf78
3 changed files with 10 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/install/configure-nova-flavors.rst
View File

@@ -90,10 +90,10 @@ Note how ``baremetal.with-GPU`` in the node's ``resource_class`` field becomes
Scheduling based on traits
--------------------------
Starting with the Queens release, the Compute service supports scheduling based
on qualitative attributes using traits. Starting with Bare Metal REST API
version 1.37, it is possible to assign a list of traits to each bare metal
node. Traits assigned to a bare metal node will be assigned to the
The Compute service supports scheduling based on qualitative attributes
using traits. Starting with Bare Metal REST API version 1.37,
it is possible to assign a list of traits to each bare metal node.
Traits assigned to a bare metal node will be assigned to the
corresponding resource provider in the Compute service placement API.
When creating a flavor in the Compute service, required traits may be specified

8
doc/source/install/configure-pxe.rst
View File

@@ -482,10 +482,10 @@ be aborted, and the node will be moved to the ``deploy failed`` state, after
the deploy callback timeout. This timeout can be changed via the
:oslo.config:option:`conductor.deploy_callback_timeout` configuration option.
Starting with the Train release, the Bare Metal service can retry PXE boot if
it takes too long. The timeout is defined via
:oslo.config:option:`pxe.boot_retry_timeout` and must be smaller than the
``deploy_callback_timeout``, otherwise it will have no effect.
The Bare Metal service can retry PXE boot if it takes too long.
The timeout is defined via :oslo.config:option:`pxe.boot_retry_timeout`
and must be smaller than the ``deploy_callback_timeout``,
otherwise it will have no effect.
For example, the following configuration sets the overall timeout to 60
minutes, allowing two retries after 20 minutes:

5
doc/source/install/enabling-drivers.rst
View File

@@ -12,9 +12,8 @@ in a vendor-specific way. There are generic **hardware types** (eg.
``irmc``).
.. note::
Starting with the Rocky release, the terminologies *driver*,
*dynamic driver*, and *hardware type* have the same meaning
in the scope of Bare Metal service.
The terminologies *driver*, *dynamic driver*, and *hardware type*
have the same meaning in the scope of Bare Metal service.
.. _enable-hardware-types: