-
Notifications
You must be signed in to change notification settings - Fork 105
/
mappingfile.rst
44 lines (25 loc) · 1.54 KB
/
mappingfile.rst
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
mapping
--------------
Manually collect PXE NIC information for target servers and manually define them to Omnia using a mapping file using the below format:
**pxe_mapping_file.csv**
::
MAC,Hostname,IP
xx:yy:zz:aa:bb:cc,server,10.5.0.101
aa:bb:cc:dd:ee:ff,server2, 10.5.0.102
The following parameters need to be populated in ``input/provision_config.yml`` to discover target nodes using a mapping file.
.. caution::
* ``admin_nic_subnet``, ``ib_nic_subnet`` and ``bmc_nic_subnet`` should have the same subnet mask (Omnia only supports /16 subnet masks currently).
* Do not remove or comment any lines in the ``input/provision_config.yml`` file.
* **THE ROCKY LINUX OS VERSION ON THE CLUSTER WILL BE UPGRADED TO THE LATEST 8.x VERSION AVAILABLE IRRESPECTIVE OF THE PROVISION_OS_VERSION PROVIDED IN PROVISION_CONFIG.YML.**
.. csv-table:: Parameters
:file: ../../../Tables/mapping.csv
:header-rows: 1
.. caution:: The IP address *192.168.25.x* is used for PowerVault Storage communications. Therefore, do not use this IP address for other configurations.
.. note::
The ``input/provision_config.yml`` file is encrypted on the first run of the provision tool:
To view the encrypted parameters: ::
ansible-vault view provision_config.yml --vault-password-file .provision_vault_key
To edit the encrypted parameters: ::
ansible-vault edit provision_config.yml --vault-password-file .provision_vault_key
To continue to the next steps:
* `Provisioning the cluster <../installprovisiontool.html>`_