From 778662acbee7aa227c85502a78efc27f8b34d387 Mon Sep 17 00:00:00 2001 From: Dao Cong Tien Date: Mon, 2 Jul 2018 18:02:07 +0700 Subject: [PATCH] Remove doc of classic drivers from the admin guide This patch removes pieces of doc of classic drivers from the admin guide (doc/source/admin dir). upgrade-to-hardware-types.rst is excluded from the patch as it is used in the upgrade guide. Change-Id: Id7ca290fa03efec4c64d8e7f2e64194e14f9619b --- doc/source/admin/interfaces/boot.rst | 3 +-- doc/source/admin/interfaces/deploy.rst | 11 ++--------- doc/source/admin/raid.rst | 5 ++--- 3 files changed, 5 insertions(+), 14 deletions(-) diff --git a/doc/source/admin/interfaces/boot.rst b/doc/source/admin/interfaces/boot.rst index f6c27736f3..b68c26c1c3 100644 --- a/doc/source/admin/interfaces/boot.rst +++ b/doc/source/admin/interfaces/boot.rst @@ -33,8 +33,7 @@ understanding of the whole deployment process. architectures that do not have BIOS support at all. The ``pxe`` boot interface is used by default for many hardware types, -including ``ipmi``, and for all classic drivers with names starting with -``pxe_``. Some hardware types, notably ``ilo`` and ``irmc`` have their +including ``ipmi``. Some hardware types, notably ``ilo`` and ``irmc`` have their specific implementations of the PXE boot interface. Additional configuration is required for this boot interface - see diff --git a/doc/source/admin/interfaces/deploy.rst b/doc/source/admin/interfaces/deploy.rst index 550a0a8974..fd5d8bc9f0 100644 --- a/doc/source/admin/interfaces/deploy.rst +++ b/doc/source/admin/interfaces/deploy.rst @@ -24,9 +24,6 @@ when creating or updating a node:: openstack baremetal node create --driver ipmi --deploy-interface iscsi openstack baremetal node set --deploy-interface iscsi -The ``iscsi`` deploy interface is also used in all of the *classic drivers* -with names starting with ``pxe_`` and ``iscsi_``. - .. _iSCSI: https://en.wikipedia.org/wiki/ISCSI .. _direct-deploy: @@ -46,14 +43,10 @@ You can specify this deploy interface when creating or updating a node:: openstack baremetal node create --driver ipmi --deploy-interface direct openstack baremetal node set --deploy-interface direct -The ``direct`` deploy interface is also used in all *classic drivers* -whose names include ``agent``. - .. note:: For historical reasons the ``direct`` deploy interface is sometimes called - ``agent``, and some *classic drivers* using it are called ``agent_*``. - This is because before the Kilo release **ironic-python-agent** used to - only support this deploy interface. + ``agent``. This is because before the Kilo release **ironic-python-agent** + used to only support this deploy interface. .. _ansible-deploy: diff --git a/doc/source/admin/raid.rst b/doc/source/admin/raid.rst index 4b724aa5e4..d0178be621 100644 --- a/doc/source/admin/raid.rst +++ b/doc/source/admin/raid.rst @@ -66,8 +66,7 @@ If the ``target_raid_config`` is an empty dictionary, it unsets the value of done on the node. Each dictionary of logical disk contains the desired properties of logical -disk supported by the hardware type or classic driver. These properties are -discoverable by:: +disk supported by the hardware type. These properties are discoverable by:: openstack baremetal --os-baremetal-api-version 1.15 driver raid property list @@ -244,7 +243,7 @@ Workflow ======== * Operator configures the bare metal node with a hardware type that has - a ``RAIDInterface`` other than ``no-raid`` (``None`` for classic drivers). + a ``RAIDInterface`` other than ``no-raid``. * For in-band RAID configuration, operator builds an agent ramdisk which supports RAID configuration by bundling the hardware manager with the