StarlingX/Docs and Infra/InstallationGuides/virtual-Controllers-and-Computes
Contents
- 1 Deployment Diagram
- 2 Physical Host Requirements
- 3 Preparing the Virtual Environment and Servers
- 4 StarlingX Kubernetes
- 4.1 Installing StarlingX Kubernetes
- 4.1.1 Install Software on Controller-0
- 4.1.2 Bootstrap System on Controller-0
- 4.1.3 Configure Controller-0
- 4.1.4 Unlock Controller-0
- 4.1.5 Install Software on Controller-1 and Compute Nodes
- 4.1.6 Configure Controller-1
- 4.1.7 Unlock Controller-1
- 4.1.8 Configure Compute Nodes
- 4.1.9 Unlock Compute Nodes
- 4.2 Accessing StarlingX Kubernetes
- 4.1 Installing StarlingX Kubernetes
- 5 StarlingX OpenStack
Deployment Diagram
Standard Deployment Diagram
Physical Host Requirements
ToDo - Same as AIO-SIMPLEX
Hardware Requirements
ToDo - Same as AIO-SIMPLEX
Software Requirements
ToDo - Same as AIO-SIMPLEX
Setting up the Host
ToDo - Same as AIO-SIMPLEX
Preparing the Virtual Environment and Servers
Setup virtual platform networks for virtual deployment:
bash setup_network.sh
Create the XML definitions for the virtual servers required by this configuration option.
This will create the XML virtual server definition for:
- controllerstorage-controller-0
- controllerstorage-controller-1
- controllerstorage-compute-0
- controllerstorage-compute-1
The following command will also start the X-based graphical virt-manager application; if their is no X-server present then errors will occur.
The following command will also start/virtually-powered-on the 'duplex-controller-0' virtual server.
bash setup_configuration.sh -c controllerstorage -i ./bootimage.iso
StarlingX Kubernetes
Installing StarlingX Kubernetes
Install Software on Controller-0
The controller-0 virtual server, 'duplex-controller-0', has been started/virtually-powered-on by the previous 'setup_configuration.sh' command.
Attach to the console of virtual controller-0 and select the appropriate installer menu options in order to start the non-interactive install of StarlingX software on controller-0.
When entering the console it is very easy to miss the first installer menu selection; use ESC to go to previous menus, in order to ensure you are at the first installer menu selection.
virsh console duplex-controller-0
Installer Menu Selections:
- First Menu
- Select 'All-in-one Controller Configuration'
- Second Menu
- Select 'Graphical Console'
- Third Menu
- Select 'Standard Security Profile'
Wait for non-interactive install of software to complete and server to reboot.
This can take 5-10 mins depending on performance of HOST machine.
Bootstrap System on Controller-0
Login with username / password of sysadmin / sysadmin.
When logging in for the first time, you will be forced to change the password.
Login: sysadmin Password: Changing password for sysadmin. (current) UNIX Password: sysadmin New Password: (repeat) New Password:
External connectivity is required to run the Ansible bootstrap playbook.
export CONTROLLER0_OAM_CIDR=10.10.10.3/24 export DEFAULT_OAM_GATEWAY=10.10.10.1 sudo ip address add $CONTROLLER0_OAM_CIDR dev enp7s1 sudo ip link set up dev enp7s1 sudo ip route add default via $DEFAULT_OAM_GATEWAY dev enp7s1
Ansible is used to bootstrap StarlingX on Controller-0:
- The default Ansible inventory file, /etc/ansible/hosts, contains a single host, localhost.
- The Ansible bootstrap playbook is at /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml .
- The default configuration values for the bootstrap playbook are in /usr/share/ansible/stx-ansible/playbooks/bootstrap/host_vars/default.yml .
- By default Ansible looks for and imports user configuration override files for hosts in the sysadmin home directory ($HOME), e.g. $HOME/<hostname>.yml .
Specify the user configuration override file for the ansible bootstrap playbook, by copying the above default.yml file to $HOME/localhost.yml and edit the configurable values as desired, based on the commented instructions in the file.
or
Simply create the minimal user configuration override file as shown below:
cd ~ cat <<EOF > localhost.yml system_mode: duplex dns_servers: - 8.8.8.8 - 8.8.4.4 external_oam_subnet: 10.10.10.0/24 external_oam_gateway_address: 10.10.10.1 external_oam_floating_address: 10.10.10.2 external_oam_node_0_address: 10.10.10.3 external_oam_node_1_address: 10.10.10.4 admin_username: admin admin_password: <sysadmin-password> ansible_become_pass: <sysadmin-password> EOF
Run the Ansible bootstrap playbook:
ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml
Wait for Ansible bootstrap playbook to complete.
This can take 5-10 mins depending on performance of HOST machine.
Configure Controller-0
Acquire admin credentials:
source /etc/platform/openrc
Configure the OAM and MGMT interfaces of controller-0 and specify the attached networks:
OAM_IF= enp7s1 MGMT_IF= enp7s2 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 $OAM_IF -c platform system interface-network-assign controller-0 $OAM_IF oam 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:
In virtual environment this can sometimes cause Ceph’s clock skew alarms. Moreover, clock of virtual instances is synchronized with the host clock so it is not absolutely required to configure NTP here..
system ntp-modify ntpservers=0.pool.ntp.org,1.pool.ntp.org
OpenStack-specific Host Configuration
The following configuration is only required if the OpenStack application (stx-openstack) will be installed.
For OpenStack ONLY, assign OpenStack host labels to controller-0 in support of installing the stx-openstack manifest/helm-charts later.
system host-label-assign controller-0 openstack-control-plane=enabled
For OpenStack ONLY, a vSwitch is required.
- The default vSwitch is containerized OVS that is packaged with the stx-openstack manifest/helm-charts. StarlingX provides the option to use OVS-DPDK on the host, however in the virtual environment OVS-DPDK is NOT supported, only OVS is supported. Therefore simply use the default OVS vSwitch here.
Unlock Controller-0
Unlock controller-0 in order to bring it into service:
system host-unlock controller-0
Controller-0 will reboot in order to apply configuration change and come into service.
This can take 5-10 mins depending on performance of HOST machine.
Install Software on Controller-1 and Compute Nodes
Power on the controller-1 virtual server, 'controllerstorage-controller-1', and force it to network boot by pressing F12 and selecting 'lan' as the alternative boot option.
virsh start controllerstorage-controller-1
Attach to the console of virtual controller-1:
virus console controllerstorage-controller-1
As controller-1 VM boots, a message appears on its console instructing you to configure the personality of the node.
On console of controller-0,
list hosts to see newly discovered controller-1 host, i.e. host with hostname of None:
system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | None | None | locked | disabled | offline | +----+--------------+-------------+----------------+-------------+--------------+
Using the host id, set the personality of this host to 'controller':
system host-update 2 personality=controller
This initiates the install of software on controller-1.
This can take 5-10 mins depending on performance of HOST machine.
While waiting on this, repeat the same procedure for 'controllerstorage-compute-0' and 'controllerstorage-compute-1', except for setting the personality to 'worker' and assigning a unique hostname, e.g.:
system host-update 3 personality=worker hostname=compute-0 system host-update 4 personality=worker hostname=compute-1
Wait for the install of software on controller-1, compute-0 and compute-1 to all complete, all virtual servers to reboot and to all show as locked/disabled/online in 'system host-list'.
system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | controller-1 | controller | locked | disabled | online | | 3 | compute-0 | compute | locked | disabled | online | | 4 | compute-1 | compute | locked | disabled | online | +----+--------------+-------------+----------------+-------------+--------------+
Configure Controller-1
Configure the OAM and MGMT interfaces of controller-0 and specify the attached networks:
(Note that the MGMT interface is partially setup automatically by the network install procedure.)
OAM_IF= enp7s1 MGMT_IF= enp7s2 system host-if-modify controller-1 $OAM_IF -c platform system interface-network-assign controller-1 $OAM_IF oam system interface-network-assign controller-1 $MGMT_IF cluster-host
OpenStack-specific Host Configuration
The following configuration is only required if the OpenStack application (stx-openstack) will be installed.
For OpenStack ONLY, assign OpenStack host labels to controller-1 in support of installing the stx-openstack manifest/helm-charts later.
system host-label-assign controller-1 openstack-control-plane=enabled
Unlock Controller-1
Unlock controller-1 in order to bring it into service:
system host-unlock controller-1
Controller-1 will reboot in order to apply configuration change and come into service.
This can take 5-10 mins depending on performance of HOST machine.
Configure Compute Nodes
Add the third Ceph monitor to compute-0: (The first two Ceph monitors are automatically assigned to controller-0 and controller-1.)
system ceph-mon-add compute-0
Wait for the compute node monitor to complete configuration:
system ceph-mon-list +--------------------------------------+-------+--------------+------------+------+ | uuid | ceph_ | hostname | state | task | | | mon_g | | | | | | ib | | | | +--------------------------------------+-------+--------------+------------+------+ | 64176b6c-e284-4485-bb2a-115dee215279 | 20 | controller-1 | configured | None | | a9ca151b-7f2c-4551-8167-035d49e2df8c | 20 | controller-0 | configured | None | | f76bc385-190c-4d9a-aa0f-107346a9907b | 20 | compute-0 | configured | None | +--------------------------------------+-------+--------------+------------+------+
Assign the cluster-host network to the MGMT interface for the compute nodes:
(Note that the MGMT interfaces are partially setup automatically by the network install procedure.)
for COMPUTE in compute-0 compute-1; do system interface-network-assign $COMPUTE mgmt0 cluster-host done
Configure data interfaces for compute nodes:
DATA0IF=eth1000 DATA1IF=eth1001 PHYSNET0='physnet0' PHYSNET1='physnet1' SPL=/tmp/tmp-system-port-list SPIL=/tmp/tmp-system-host-if-list # configure the datanetworks in sysinv, prior to referencing it # in the ``system host-if-modify`` command'. system datanetwork-add ${PHYSNET0} vlan system datanetwork-add ${PHYSNET1} vlan for COMPUTE in compute-0 compute-1; do echo "Configuring interface for: $COMPUTE" set -ex system host-port-list ${COMPUTE} --nowrap > ${SPL} system host-if-list -a ${COMPUTE} --nowrap > ${SPIL} DATA0PCIADDR=$(cat $SPL | grep $DATA0IF |awk '{print $8}') DATA1PCIADDR=$(cat $SPL | grep $DATA1IF |awk '{print $8}') DATA0PORTUUID=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $2}') DATA1PORTUUID=$(cat $SPL | grep ${DATA1PCIADDR} | awk '{print $2}') DATA0PORTNAME=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $4}') DATA1PORTNAME=$(cat $SPL | grep ${DATA1PCIADDR} | awk '{print $4}') DATA0IFUUID=$(cat $SPIL | awk -v DATA0PORTNAME=$DATA0PORTNAME '($12 ~ DATA0PORTNAME) {print $2}') DATA1IFUUID=$(cat $SPIL | awk -v DATA1PORTNAME=$DATA1PORTNAME '($12 ~ DATA1PORTNAME) {print $2}') system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} system host-if-modify -m 1500 -n data1 -c data ${COMPUTE} ${DATA1IFUUID} system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} ${PHYSNET0} system interface-datanetwork-assign ${COMPUTE} ${DATA1IFUUID} ${PHYSNET1} set +ex done
OpenStack-specific Host Configuration
The following configuration is only required if the OpenStack application (stx-openstack) will be installed.
For OpenStack ONLY, assign OpenStack host labels to the compute nodes in support of installing the stx-openstack manifest/helm-charts later.
for NODE in compute-0 compute-1; do system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled system host-label-assign $NODE sriov=enabled done
Unlock Compute Nodes
When it completes, your Kubernetes Cluster is up and running.
Accessing StarlingX Kubernetes
Use Local/Remote CLIs, GUIs and/or REST APIs to access and manage StarlingX Kubernetes and hosted containerized applications. See details on accessing the StarlingX Kubernetes Cluster here.
StarlingX OpenStack
Install StarlingX OpenStack
Other than the OpenStack-specific configurations required in the underlying StarlingX/Kubernetes infrastructure done in the above installation steps for the StarlingX Kubernetes Platform, the installation of containerized OpenStack is independent of deployment configuration and can be found here.
Access StarlingX OpenStack
Use Local/Remote CLIs, GUIs and/or REST APIs to access and manage StarlingX OpenStack and hosted virtualized applications. See details on accessing StarlingX OpenStack here.