Jump to: navigation, search

Difference between revisions of "StarlingX/Docs and Infra/InstallationGuides/virtual-Controllers-and-Computes-with-Storage-Cluster"

(Installing StarlingX Kubernetes)
(Installing StarlingX Kubernetes)
Line 50: Line 50:
 
== Installing StarlingX Kubernetes ==
 
== Installing StarlingX Kubernetes ==
 
=== Install Software on Controller-0 ===
 
=== 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.<br />
 +
<br />
 +
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.<br />
 +
<br />
 +
{{caution|header=WARNING|body=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.}}
 +
<pre>
 +
virsh console duplex-controller-0
 +
</pre>
 +
Installer Menu Selections:
 +
* First Menu
 +
** Select 'All-in-one Controller Configuration'
 +
* Second Menu
 +
** Select 'Graphical Console'
 +
* Third Menu
 +
** Select 'Standard Security Profile'
 +
<br />
 +
Wait for non-interactive install of software to complete and server to reboot.<br />
 +
This can take 5-10 mins depending on performance of HOST machine.
 +
<br />
 +
<br />
  
 +
=== Bootstrap System on Controller-0 ===
 +
Login with username / password of sysadmin / sysadmin.<br />
 +
When logging in for the first time, you will be forced to change the password.
 +
<pre>
 +
Login: sysadmin
 +
Password:
 +
Changing password for sysadmin.
 +
(current) UNIX Password: sysadmin
 +
New Password:
 +
(repeat) New Password:
 +
</pre>
 
<br />
 
<br />
 +
External connectivity is required to run the Ansible bootstrap playbook.<br />
 +
<pre>
 +
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
 +
</pre>
 
<br />
 
<br />
 +
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 .
 +
<br />
 +
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.<br />
 +
or <br />
 +
Simply create the minimal user configuration override file as shown below:
 +
<pre>
 +
cd ~
 +
cat <<EOF > localhost.yml
 +
system_mode: duplex
  
=== Bootstrap System on Controller-0 ===
+
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
 +
</pre>
 +
Run the Ansible bootstrap playbook:
 +
<pre>
 +
ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml
 +
</pre>
 +
Wait for Ansible bootstrap playbook to complete.<br />
 +
This can take 5-10 mins depending on performance of HOST machine.<br />
 
<br />
 
<br />
 
<br />
 
<br />
  
 
=== Configure Controller-0 ===
 
=== Configure Controller-0 ===
 +
Acquire admin credentials:
 +
<pre>
 +
source /etc/platform/openrc
 +
</pre>
 +
Configure the OAM interface of controller-0:
 +
<pre>
 +
OAM_IF=enp7s1
 +
system host-if-modify controller-0 $OAM_IF -c platform
 +
system interface-network-assign controller-0 $OAM_IF oam
 +
</pre>
 +
Configure NTP Servers for network time synchronization:
 +
{{caution|header=Warning|body= 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..}}
 +
<pre>
 +
system ntp-modify ntpservers=0.pool.ntp.org,1.pool.ntp.org
 +
</pre>
 +
<br />
 +
Configure data interfaces for controller-0:
 +
<pre>
 +
DATA0IF=eth1000
 +
DATA1IF=eth1001
 +
export COMPUTE=controller-0
 +
PHYSNET0='physnet0'
 +
PHYSNET1='physnet1'
 +
SPL=/tmp/tmp-system-port-list
 +
SPIL=/tmp/tmp-system-host-if-list
 +
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 datanetwork-add ${PHYSNET0} vlan
 +
system datanetwork-add ${PHYSNET1} vlan
 +
 +
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}
 +
</pre>
 +
Add an OSD on controller-0 for ceph:
 +
<pre>
 +
echo ">>> Add OSDs to primary tier"
 +
system host-disk-list controller-0
 +
system host-disk-list controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {}
 +
system host-stor-list controller-0
 +
</pre>
 +
<br />
 +
 +
==== OpenStack-specific Host Configuration ====
 +
{{caution|header=OpenStack-ONLY|body=The following configuration is only required if the OpenStack application (stx-openstack) will be installed.}}
 +
 +
<span style="color: red;">
 +
'''For OpenStack ONLY,''' assign OpenStack host labels to controller-0 in support of installing the stx-openstack manifest/helm-charts later.
 +
</span>
 +
<pre style="color: red;">
 +
system host-label-assign controller-0 openstack-control-plane=enabled
 +
system host-label-assign controller-0 openstack-compute-node=enabled
 +
system host-label-assign controller-0 openvswitch=enabled
 +
system host-label-assign controller-0 sriov=enabled
 +
</pre>
 +
<br />
 +
<span style="color: red;">
 +
'''For OpenStack ONLY,''' a vSwitch is required.<br />
 +
</span>
 +
: <span style="color: red;">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.</span><br />
 +
<br />
 +
<span style="color: red;">
 +
'''For OpenStack Only,''' setup disk partition for nova-local volume group, needed for stx-openstack nova ephemeral disks.
 +
</span>
 +
<pre style="color: red;">
 +
export COMPUTE=controller-0
  
 +
echo ">>> Getting root disk info"
 +
ROOT_DISK=$(system host-show ${COMPUTE} | grep rootfs | awk '{print $4}')
 +
ROOT_DISK_UUID=$(system host-disk-list ${COMPUTE} --nowrap | grep ${ROOT_DISK} | awk '{print $2}')
 +
echo "Root disk: $ROOT_DISK, UUID: $ROOT_DISK_UUID"
 +
 +
echo ">>>> Configuring nova-local"
 +
NOVA_SIZE=34
 +
NOVA_PARTITION=$(system host-disk-partition-add -t lvm_phys_vol ${COMPUTE} ${ROOT_DISK_UUID} ${NOVA_SIZE})
 +
NOVA_PARTITION_UUID=$(echo ${NOVA_PARTITION} | grep -ow "| uuid | [a-z0-9\-]* |" | awk '{print $4}')
 +
system host-lvg-add ${COMPUTE} nova-local
 +
system host-pv-add ${COMPUTE} nova-local ${NOVA_PARTITION_UUID}
 +
sleep 2
 +
 +
echo ">>> Wait for partition $NOVA_PARTITION_UUID to be ready."
 +
while true; do system host-disk-partition-list $COMPUTE --nowrap | grep $NOVA_PARTITION_UUID | grep Ready; if [ $? -eq 0 ]; then break; fi; sleep 1; done
 +
</pre>
 
<br />
 
<br />
 
<br />
 
<br />
  
 
=== Unlock Controller-0 ===
 
=== Unlock Controller-0 ===
 
+
Unlock controller-0 in order to bring it into service:
 +
<pre>
 +
system host-unlock controller-0
 +
</pre>
 +
Controller-0 will reboot in order to apply configuration change and come into service.<br />
 +
This can take 5-10 mins depending on performance of HOST machine. <br />
 
<br />
 
<br />
 
<br />
 
<br />

Revision as of 10:58, 15 August 2019

Deployment Diagram

Standard with Storage Cluster 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:

  • dedicatedstorage-controller-0
  • dedicatedstorage-controller-1
  • dedicatedstorage-storage-0
  • dedicatedstorage-storage-1
  • dedicatedstorage-compute-0
  • dedicatedstorage-compute-1


Caution icon.svg CAUTION

The following command will also start the X-based graphical virt-manager application; if their is no X-server present then errors will occur.
Caution icon.svg NOTE

The following command will also start/virtually-powered-on the 'simplex-controller-0' virtual server.
bash setup_configuration.sh -c dedicatedstorage -i ./bootimage.iso      



StarlingX Kubernetes

ToDo

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.

Caution icon.svg WARNING

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 interface of controller-0:

OAM_IF=enp7s1
system host-if-modify controller-0 $OAM_IF -c platform
system interface-network-assign controller-0 $OAM_IF oam

Configure NTP Servers for network time synchronization:

Caution icon.svg Warning

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


Configure data interfaces for controller-0:

DATA0IF=eth1000
DATA1IF=eth1001
export COMPUTE=controller-0
PHYSNET0='physnet0'
PHYSNET1='physnet1'
SPL=/tmp/tmp-system-port-list
SPIL=/tmp/tmp-system-host-if-list
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 datanetwork-add ${PHYSNET0} vlan
system datanetwork-add ${PHYSNET1} vlan

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}

Add an OSD on controller-0 for ceph:

echo ">>> Add OSDs to primary tier"
system host-disk-list controller-0
system host-disk-list controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {}
system host-stor-list controller-0


OpenStack-specific Host Configuration

Caution icon.svg OpenStack-ONLY

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
system host-label-assign controller-0 openstack-compute-node=enabled
system host-label-assign controller-0 openvswitch=enabled
system host-label-assign controller-0 sriov=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.


For OpenStack Only, setup disk partition for nova-local volume group, needed for stx-openstack nova ephemeral disks.

export COMPUTE=controller-0

echo ">>> Getting root disk info"
ROOT_DISK=$(system host-show ${COMPUTE} | grep rootfs | awk '{print $4}')
ROOT_DISK_UUID=$(system host-disk-list ${COMPUTE} --nowrap | grep ${ROOT_DISK} | awk '{print $2}')
echo "Root disk: $ROOT_DISK, UUID: $ROOT_DISK_UUID"

echo ">>>> Configuring nova-local"
NOVA_SIZE=34
NOVA_PARTITION=$(system host-disk-partition-add -t lvm_phys_vol ${COMPUTE} ${ROOT_DISK_UUID} ${NOVA_SIZE})
NOVA_PARTITION_UUID=$(echo ${NOVA_PARTITION} | grep -ow "| uuid | [a-z0-9\-]* |" | awk '{print $4}')
system host-lvg-add ${COMPUTE} nova-local
system host-pv-add ${COMPUTE} nova-local ${NOVA_PARTITION_UUID}
sleep 2

echo ">>> Wait for partition $NOVA_PARTITION_UUID to be ready."
while true; do system host-disk-partition-list $COMPUTE --nowrap | grep $NOVA_PARTITION_UUID | grep Ready; if [ $? -eq 0 ]; then break; fi; sleep 1; done



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, Storage Nodes and Compute Nodes

Todo


Configure Controller-1

Todo


Unlock Controller-1

Todo


Configure Storage Nodes



Unlock Storage Nodes



Configure Compute Nodes



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.