diff options
| author |   Tim Rozet <trozet@redhat.com> | 2016-11-30 11:03:02 -0500 |
|---|---|---|
| committer | Tim Rozet <trozet@redhat.com> | 2016-12-20 21:16:31 +0000 |
| commit | 4e1320c4235476d7e2a0a90f80997e8371c5f399 (patch) | |
| tree | fb3414be4be572f83327720c097308f06510abb6 /docs/installationprocedure | |
| parent | a90e29d412664322bb5b0602ae4870439a0ed038 (diff) | |
Adds declaring disk device to use on overcloud nodes
Now in inventory file a user can declare 'disk_device' which will allow
the user to specify which disk on their overcloud server to use for
installation. The variable can be a comma delimited list, which will
search in order post-introspection for the first device on the node that
exists. The default disk used will be sda for deployments.
Currently defining a per node disk is not supported by OSCLI, so
although defined that way in Apex inventory, only the last definition
will be used for all nodes.
Other changes include:
- Various fixes in inventory parsing
- Makes bash writing a common function
- Introspection now enabled for baremetal deployments
JIRA: APEX-296
Change-Id: I330d91eb17408ccfceb7a99c25edbae5ce6d848d
Signed-off-by: Tim Rozet <trozet@redhat.com>
Diffstat (limited to 'docs/installationprocedure')
| -rw-r--r-- | docs/installationprocedure/baremetal.rst | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/installationprocedure/baremetal.rst b/docs/installationprocedure/baremetal.rst index 15c80c3b..83cda326 100644 --- a/docs/installationprocedure/baremetal.rst +++ b/docs/installationprocedure/baremetal.rst @@ -202,6 +202,7 @@ IPMI configuration information gathered in section - ``cpus``: (Introspected*) CPU cores available - ``memory``: (Introspected*) Memory available in Mib - ``disk``: (Introspected*) Disk space available in Gb + - ``disk_device``: (Opt***) Root disk device to use for installation - ``arch``: (Introspected*) System architecture - ``capabilities``: (Opt**) Node's role in deployment values: profile:control or profile:compute @@ -213,6 +214,14 @@ IPMI configuration information gathered in section ** If capabilities profile is not specified then Apex will select node's roles in the OPNFV cluster in a non-deterministic fashion. + \*** disk_device declares which hard disk to use as the root device for + installation. The format is a comma delimited list of devices, such as + "sda,sdb,sdc". The disk chosen will be the first device in the list which + is found by introspection to exist on the system. Currently, only a single + definition is allowed for all nodes. Therefore if multiple disk_device + definitions occur within the inventory, only the last definition on a node + will be used for all nodes. + Creating the Settings Files --------------------------- |