Fix instructions for dist-cloud install

Fix the install instructions for distributed cloud:
- Add needed detail/clarification to subcloud section
- Clarify AIO-Simplex install on subcloud (WIP)

Patch set 2: Wording correction per feedback.
Patch set 3: Wording corrections and add in clarification for
AIO-Simplex config for dist cloud

Closes-Bug:1858481

Change-Id: I939d1f938ea912a05bc72be83ab161f3f2040c78
Signed-off-by: Kristal Dale <kristal.dale@intel.com>
This commit is contained in:
Kristal Dale 2020-01-07 15:12:21 -08:00
parent 08b467944e
commit 3bf2b2de5e
2 changed files with 37 additions and 7 deletions

View File

@ -158,8 +158,8 @@ Configure controller-0
source /etc/platform/openrc
#. Configure the OAM interface of controller-0 and specify the attached network
as "oam". Use the OAM port name, for example eth0, that is applicable to your
deployment environment:
as "oam". Use the OAM port name that is applicable to your deployment
environment, for example eth0:
::
@ -167,6 +167,29 @@ Configure controller-0
system host-if-modify controller-0 $OAM_IF -c platform
system interface-network-assign controller-0 $OAM_IF oam
#. If the system is a subcloud in a distributed cloud environment, then the mgmt
network and cluster-host networks must be configured on an actual interface
and not left on the loopback interface.
.. important::
Complete this step only if the system is a subcloud in a distributed cloud
environment!
For example:
::
MGMT_IF=<MGMT-PORT>
system host-if-modify controller-0 lo -c none
IFNET_UUIDS=$(system interface-network-list controller-0 | awk '{if ($6=="lo") print $4;}')
for UUID in $IFNET_UUIDS; do
system interface-network-remove ${UUID}
done
system host-if-modify controller-0 $MGMT_IF -c platform
system interface-network-assign controller-0 $MGMT_IF mgmt
system interface-network-assign controller-0 $MGMT_IF cluster-host
#. Configure NTP Servers for network time synchronization:
::

View File

@ -204,9 +204,9 @@ At the subcloud location:
RTNETLINK answers: File exists
Adding route to System Controller... DONE
At the SystemController:
At the System Controller:
1. Create a ``bootstrap-values.yml`` overrides file for the subcloud, for
1. Create a ``bootstrap-values.yml`` override file for the subcloud. For
example:
.. code:: yaml
@ -215,15 +215,21 @@ At the SystemController:
name: "subcloud1"
description: "Ottawa Site"
location: "YOW"
management_subnet: 192.168.101.0/24
management_start_address: 192.168.101.2
management_end_address: 192.168.101.50
management_gateway_address: 192.168.101.1
external_oam_subnet: 10.10.10.0/24
external_oam_gateway_address: 10.10.10.1
external_oam_floating_address: 10.10.10.12
systemcontroller_gateway_address: 192.168.204.101
.. important:: The `management_*` entries in the override file are required
for all installation types, including AIO-Simplex.
2. Add the subcloud using the CLI command below:
.. code:: sh
@ -273,7 +279,10 @@ At the SystemController:
- For Standard with dedicated storage nodes:
`Bare metal Standard with Dedicated Storage Installation R3.0 <https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/dedicated_storage.html>`_
5. Add routes from the subcloud to the controller management network:
On the active controller for each subcloud:
#. Add a route from the subcloud to the controller management network to enable
the subcloud to go online. Use the following command:
.. code:: sh
@ -285,5 +294,3 @@ At the SystemController:
.. code:: sh
system host-route-add 1 enp0s8 192.168.204.0 24 192.168.101.1
Repeat this step for each host of the subcloud.