Jump to: navigation, search

StarlingX/Docs and Infra/InstallationGuides/virtual-AIO-Duplex

< StarlingX‎ | Docs and Infra‎ | InstallationGuides
Revision as of 00:40, 15 August 2019 by Greg-waines (talk | contribs) (StarlingX Kubernetes)

Deployment Diagram

(Simple w/ deploy 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:

  • duplex-controller-0
  • duplex-controller-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 'duplex-controller-0' virtual server.
bash setup_configuration.sh -c duplex -i ./bootimage.iso      




StarlingX Kubernetes

Installing the StarlingX Kubernetes Platform

Install Software on Controller-0

Todo - Same as AIO-SIMPLEX
EXCEPT: change 'simplex-controller-0' to 'duplex-controller-0'

Bootstrap System on Controller-0

Todo -

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

admin_username: admin
admin_password: <sysadmin-password>
ansible_become_pass: <sysadmin-password>
EOF


...

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 Node

Todo

Configure Controller-1

Todo

Unlock Controller-1

Todo


When it completes, your Kubernetes Cluster is up and running.



Accessing StarlingX Kubernetes

ToDo


StarlingX OpenStack

ToDo

Installing StarlingX OpenStack

ToDo

Accessing StarlingX OpenStack

ToDo