openstack
/
ironic-specs
Code Issues Proposed changes

Update OOB RAID for iLO5 based HPE Proliant Servers 

This commit is to update OOB raid spec to add additional clean
step ``read_configuration`` for out-of-band raid creation to
get the raid config from the system.

Change-Id: Ibb820b624faca275f8266f6b9d18efb2a83326f8
This commit is contained in:
Anshul Jain 2018-01-02 22:08:30 -06:00
parent 4a70c871ab
commit 89ee32937a
1 changed files with 58 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

78
specs/approved/ilo-oob-raid.rst
View File

@ -16,8 +16,12 @@ for ILO managed HPE Proliant servers.
Problem description
===================
Ilo5 based HPE Proliant Gen10 servers provide support to perform out-of-band
RAID configuration which was not there in Gen9 and below servers.
In the current scenario where RAID configuration on HPE Proliant servers is
done only via inband cleaning, Ilo5 based HPE Proliant Gen10 servers provide
support to perform out-of-band RAID configuration which was not there in Gen9
and below servers. However, the raid creation or deletion will take into effect
only when the system reaches POST stage. Hence, creation or deletion of RAID
needs to be accompanied by a reboot.
Proposed change
===============
@ -26,6 +30,15 @@ This spec proposes to implement out-of-band RAID configuration as described
by the parent spec [1]. This will require the implementation of a new hardware
type ``Ilo5Hardware`` and a new raid interface for ilo as ``IloRAID``.
OOB RAID configuration will be a four step process.
1. delete_configuration - delete the current raid config from the system.
2. read_configuration - get the updated raid config from system and update
the node properties accordingly.
3. create_configuration - create the raid config which set by the user in
target_raid_config of node properties.
4. read_configuration - get the updated raid config from system and update
the node properties accordingly.
List of changes required:
* The following would be the composition of ``Ilo5Hardware``:
@ -34,41 +47,66 @@ List of changes required:
+ Ilo5Hardware will inherit all interfaces of parent class IloHardware.
+ Ilo5Hardware will support the new interface ``IloRAID``.
+ Ilo5Hardware will support the new RAID interface ``IloRAID``.
* The following would be the composition of ``IloRAID``:
+ IloRAID will inherit RAIDInterface of base class.
+ ``create_configuration`` - This will create the RAID configuration on
the bare metal node.
- It will create an IloClient object from proliantutils library to do
operations on the iLO. This will make call to create_raid_configuration
of proliantutils library to create the logical drives on the system.
+ ``delete_configuration`` - This will delete the RAID configuration on
the bare metal node.
- Since a reboot is required for changes to get reflected, this function
will be decorated with additional argument `reboot_required` with
value set to `True`.
- It will create an IloClient object from proliantutils library to do
operations on the iLO. This will make call to delete_raid_configuration
of proliantutils library to delete the logical drives on the system.
+ ``_create_configuration_final`` - This will be called after the clean
step ``IloRAID.create_configuration`` is completed. This method will call
``update_raid_info`` with the actual RAID configuration returned by ilo
object.
+ ``create_configuration`` - This will create the RAID configuration on
the bare metal node.
+ ``_delete_configuration_final`` - This will be called after
``IloRAID.delete_configuration`` is completed. This will set
``node.raid_config`` to ``None``.
- Since a reboot is required for changes to get reflected, this function
will be decorated with additional argument `reboot_required` with
value set to `True`.
- It will create an IloClient object from proliantutils library to do
operations on the iLO. This will make call to create_raid_configuration
of proliantutils library to place a request to firmware to create the
logical drives on the system.
+ ``read_configuration`` - This will read the RAID configuration on
the bare metal node.
- It will create an IloClient object from proliantutils library to do
operations on the iLO. This will make call to read_raid_configuration
of proliantutils library to get the logical drives on the system.
Hence, it will update the node properties with the actual RAID
configuration when called after ``create_configuration`` and to ``None``
when called after ``delete_configuration``.
* The following would be the updates required in cleaning architecture in
ironic to support post reboot operation if required any clean step.
+ Addition a new boolean positional argument ``reboot_required`` to
clean_step function of BaseInterface. Default is set to ``False`` for
this parameter.
NOTE: The same approach is being used in inband cleaning for steps
that require reboot.
+ Update ironic/conductor/manager.py:_do_next_clean_step() for each
step to call prepare_cleaning() if reboot_required is set to True
and result of the last command interface.execute_clean-step() is
not ``clean wait``.
Alternatives
------------
One can perform in-band raid configuration to achieve the same result.
However, The ramdisk to be used in such case should have proliant-tools
element as part of the image.
element that bundles 'ssacli' utility required for RAID operations as
part of the image.
Data model impact
-----------------
@ -156,8 +194,8 @@ Work Items
Dependencies
============
The current proliantutils version 2.4.1 does not support OOB Raid. It is under
development and will be supported in the coming release.
Support for OOB RAID in proliantutils is under development and is yet to be
released.
Testing