[doc] Add document for StarlingX AIO installtion

Added images and steps for StarlingX AIO Virtual to make installation process bit
easier, images are added to understand screen menu selection and post ansible
command.

Steps are added to verify network configuration and to verify controller status
before locking/unlocking.

Removing the line 'security profile selection', as this option is not
available during StarlingX AIO virtual installation.

Change-Id: I2b7c0dcacf3394789493dc60327b9c02084df782
Signed-off-by: Ritu Raj <ritu1.raj@intel.com>
This commit is contained in:
Ritu Raj 2020-04-03 12:05:55 +02:00
parent 29516db3bf
commit 70518bf7e5
4 changed files with 110 additions and 2 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

View File

@ -36,6 +36,17 @@ Make the following menu selections in the installer:
#. First menu: Select 'All-in-one Controller Configuration' #. First menu: Select 'All-in-one Controller Configuration'
#. Second menu: Select 'Serial Console' #. Second menu: Select 'Serial Console'
.. figure:: ../figures/starlingx-aio-controller-configuration.png
:alt: starlingx-controller-configuration
*Figure 1: StarlingX Controller Configuration*
.. figure:: ../figures/starlingx-aio-serial-console.png
:alt: starlingx--serial-console
*Figure 2: StarlingX Serial Console*
Wait for the non-interactive install of software to complete and for the server Wait for the non-interactive install of software to complete and for the server
to reboot. This can take 5-10 minutes, depending on the performance of the host to reboot. This can take 5-10 minutes, depending on the performance of the host
machine. machine.
@ -68,6 +79,20 @@ On virtual controller-0:
sudo ip link set up dev enp7s1 sudo ip link set up dev enp7s1
sudo ip route add default via $DEFAULT_OAM_GATEWAY dev enp7s1 sudo ip route add default via $DEFAULT_OAM_GATEWAY dev enp7s1
Check the configured network:
::
localhost:~$ ifconfig
enp7s1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.10.10.3 netmask 255.255.255.0 broadcast 0.0.0.0
inet6 fe80::5054:ff:feb6:10d6 prefixlen 64 scopeid 0x20<link>
ether 52:54:00:b6:10:d6 txqueuelen 1000 (Ethernet)
RX packets 10 bytes 1151 (1.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 94 bytes 27958 (27.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
#. Specify user configuration overrides for the Ansible bootstrap playbook. #. Specify user configuration overrides for the Ansible bootstrap playbook.
Ansible is used to bootstrap StarlingX on controller-0. Key files for Ansible Ansible is used to bootstrap StarlingX on controller-0. Key files for Ansible
@ -121,7 +146,8 @@ On virtual controller-0:
Refer to :doc:`/deploy_install_guides/r3_release/ansible_bootstrap_configs` Refer to :doc:`/deploy_install_guides/r3_release/ansible_bootstrap_configs`
for information on additional Ansible bootstrap configurations for advanced for information on additional Ansible bootstrap configurations for advanced
Ansible bootstrap scenarios. Ansible bootstrap scenarios, such as docker-proxies when deploying behind a
firewall, etc.
#. Run the Ansible bootstrap playbook: #. Run the Ansible bootstrap playbook:
@ -132,6 +158,15 @@ On virtual controller-0:
Wait for Ansible bootstrap playbook to complete. Wait for Ansible bootstrap playbook to complete.
This can take 5-10 minutes, depending on the performance of the host machine. This can take 5-10 minutes, depending on the performance of the host machine.
The image below shows a typical successful run.
.. figure:: ../figures/starlingx-release3-ansible-bootstrap-simplex.png
:alt: ansible bootstarp install screen
:width: 800
*Figure 3: StarlingX Ansible Bootstrap*
---------------------- ----------------------
Configure controller-0 Configure controller-0
---------------------- ----------------------
@ -144,6 +179,17 @@ On virtual controller-0:
source /etc/platform/openrc source /etc/platform/openrc
#. At this stage, you can see the controller status, it will be in the locked state.
::
[sysadmin@localhost ~(keystone_admin)]$ system host-list
+----+--------------+-------------+----------------+-------------+--------------+
| id | hostname | personality | administrative | operational | availability |
+----+--------------+-------------+----------------+-------------+--------------+
| 1 | controller-0 | controller | locked | disabled | online |
+----+--------------+-------------+----------------+-------------+--------------+
#. Configure the OAM interface of controller-0 and specify the attached network #. 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 as "oam". Use the OAM port name, for example eth0, that is applicable to your
deployment environment: deployment environment:
@ -279,8 +325,70 @@ Unlock virtual controller-0 to bring it into service:
Controller-0 will reboot to apply configuration changes and come into Controller-0 will reboot to apply configuration changes and come into
service. This can take 5-10 minutes, depending on the performance of the host machine. service. This can take 5-10 minutes, depending on the performance of the host machine.
.. note::
Once the controller comes back up, check the status of controller-0. It should
now show "unlocked", "enabled", "available" and "provisioned".
::
[sysadmin@controller-0 ~(keystone_admin)]$ system host-list
+----+--------------+-------------+----------------+-------------+--------------+
| id | hostname | personality | administrative | operational | availability |
+----+--------------+-------------+----------------+-------------+--------------+
| 1 | controller-0 | controller | unlocked | enabled | available |
+----+--------------+-------------+----------------+-------------+--------------+
[sysadmin@controller-0 ~(keystone_admin)]$
===============================================
[sysadmin@controller-0 ~(keystone_admin)]$ system host-show controller-0
+-----------------------+------------------------------------------------------------ ----------+
| Property | Value |
+-----------------------+------------------------------------------------------------ ----------+
| action | none |
| administrative | unlocked |
| availability | available |
| bm_ip | None |
| bm_type | none |
| bm_username | None |
| boot_device | /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0 |
| capabilities | {u'stor_function': u'monitor', u'Personality': u'Controller-Active'} |
| clock_synchronization | ntp |
| config_applied | 03e22d8b-1b1f-4c52-9500-96afad295d9a |
| config_status | None |
| config_target | 03e22d8b-1b1f-4c52-9500-96afad295d9a |
| console | ttyS0,115200 |
| created_at | 2020-03-09T12:34:34.866469+00:00 |
| hostname | controller-0 |
| id | 1 |
| install_output | text |
| install_state | None |
| install_state_info | None |
| inv_state | inventoried |
| invprovision | provisioned |
| location | {} |
| mgmt_ip | 192.168.204.2 |
| mgmt_mac | 00:00:00:00:00:00 |
| operational | enabled |
| personality | controller |
| reserved | False |
| rootfs_device | /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0 |
| serialid | None |
| software_load | 19.12 |
| subfunction_avail | available |
| subfunction_oper | enabled |
| subfunctions | controller,worker |
| task | |
| tboot | false |
| ttys_dcd | None |
| updated_at | 2020-03-09T14:10:42.362846+00:00 |
| uptime | 991 |
| uuid | 66aa842e-84a2-4041-b93e-f0275cde8784 |
| vim_progress_status | services-enabled |
+-----------------------+------------------------------------------------------------ ----------+
---------- ----------
Next steps Next steps
---------- ----------
.. include:: ../kubernetes_install_next.txt .. include:: ../kubernetes_install_next.txt