From 3c7a6ef6a3f699a882c34fc21103a264ae907293 Mon Sep 17 00:00:00 2001
From: Mark Goddard <mark@stackhpc.com>
Date: Fri, 8 Nov 2019 12:43:00 +0000
Subject: [PATCH] Document requirements for BIOS and RAID configuration
Ideally we will fix these issues, but documenting them is a good first
step.
Change-Id: I9a840005d62b974f0681ac39e1ff02ae3ff0120e
Story: 2004967
Task: 29410
---
doc/source/deployment.rst | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/doc/source/deployment.rst b/doc/source/deployment.rst
index 6f4ee6af..23697aec 100644
--- a/doc/source/deployment.rst
+++ b/doc/source/deployment.rst
@@ -285,6 +285,11 @@ BIOS and RAID Configuration
BIOS and RAID configuration may require one or more power cycles of the
hardware to complete the operation. These will be performed automatically.
+.. note::
+
+ Currently, BIOS and RAID configuration of overcloud hosts is supported for
+ Dell servers only.
+
Configuration of BIOS settings and RAID volumes is currently performed out of
band as a separate task from hardware provisioning. To configure the BIOS and
RAID::
@@ -297,6 +302,14 @@ properties and root device hints. To perform manual hardware inspection::
(kayobe) $ kayobe overcloud hardware inspect
+There are currently a few limitations to configuring BIOS and RAID:
+
+* The Ansible control host must be able to access the BMCs of the servers being
+ configured.
+* The Ansible control host must have the ``python-dracclient`` Python module
+ available to the Python interpreter used by Ansible. The path to the Python
+ interpreter is configured via ``ansible_python_interpreter``.
+
Provisioning
------------
--
GitLab