Jump to: navigation, search

Difference between revisions of "StarlingX/Docs and Infra/InstallationGuides/baremetal-AIO-Simplex"

(Configure Controller-0)
Line 1: Line 1:
<span style="color: red;"><big>'''DEPRECATED - Please do not edit.'''</big></span>

Latest revision as of 23:44, 20 August 2019

DEPRECATED - Please do not edit.

Deployment Diagram

(Simple w/ deploy diagram)

Hardware Requirements

The recommended minimum requirements for the Bare Metal Servers for the various host types are:

Minimum Requirement All-in-one Controller Node
Number of Servers 1
Minimum Processor Class Dual-CPU Intel® Xeon® E5 26xx Family (SandyBridge) 8 cores/socket
Single-CPU Intel Xeon D-15xx Family, 8 cores
(low-power/low-cost option)
Minimum Memory 64 GB
Primary Disk 500 GB SDD or NVMe
Additional Disks 1 or more 500 GB (min. 10K RPM) for Ceph OSD.
( Recommend, but not required,
1 or more SSDs or NVMe drives for Ceph journals (min. 1024 MiB per OSD journal))

For OpenStack, recommend 1 or more 500 GB (min. 10K RPM) for VM local ephemeral storage
Minimum Network Ports OAM: 1x1GE
Data: 1 or more x 10GE
BIOS Settings Hyper-Threading technology enabled
Virtualization technology enabled
VT for directed I/O enabled
CPU power and performance policy set to performance
CPU C state control disabled
Plug & play BMC detection disabled

Preparing Servers

ToDo - same as bare metal 2x Controllers, 2x Storage and 2x Computes

StarlingX Kubernetes

Installing StarlingX Kubernetes

Create a bootable USB with the StarlingX ISO

Get the StarlingX ISO. This can be from a private StarlingX build or, as shown below, from the public Cengen StarlingX build off 'master' branch:

wget http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_build/outputs/iso/bootimage.iso

Create a bootable USB with the StarlingX ISO:

# Insert USB stick

# Identify USB in mounted filesystems
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 16432268 0 16432268 0% /dev
tmpfs 3288884 26244 3262640 1% /run
/dev/mapper/md0_crypt 491076512 9641092 456420380 3% /
tmpfs 16444408 105472 16338936 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 16444408 0 16444408 0% /sys/fs/cgroup
/dev/sdc1 122546800 124876 116153868 1% /boot
tmpfs 3288880 24 3288856 1% /run/user/119
tmpfs 3288880 72 3288808 1% /run/user/1000
/dev/sdd1 1467360 1467360 0 100% /media/vivek/data

# Unmount
$ sudo umount /media/vivek/data

# Use 'dd' to copy StarlingX bootimage.iso to USB
$ sudo dd if=artful-desktop-amd64.iso of=/dev/sdd bs=1M status=progress

Install Software on Controller-0

Insert the bootable USB into a bootable USB port on the host you are configuring as controller-0.

Power on the host.

Attach to a console, ensure the host boots from the USB and wait for the StarlingX Installer Menus.

Installer Menu Selections:

  • First Menu
    • Select 'Standard Controller Configuration'
  • Second Menu
    • Select 'Graphical Console' or 'Textual Console' depending on your terminal access to the console port
  • 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 server.

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
Changing password for sysadmin.
(current) UNIX Password: sysadmin
New Password:
(repeat) New Password:

External connectivity is required to run the Ansible bootstrap playbook. The StarlingX boot image will DHCP out all interfaces so if a DHCP server is present in your environment, the server may have obtained an IP Address and have external IP connectivity by these means; check with 'ip add' and 'ping'.

Otherwise, manually configure an IP Address and Default IP Route.
Use the PORT, IP-ADDRESS/SUBNET-LENGTH and GATEWAY-IP-ADDRESS applicable to your deployment environment.

sudo ip address add <IP-ADDRESS>/<SUBNET-LENGTH> dev <PORT>
sudo ip link set up dev <PORT>
sudo ip route add default via <GATEWAY-IP-ADDRESS> dev <PORT>

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.
Simply create the minimal user configuration override file as shown below, using the OAM IP SUBNET and IP ADDRESSing applicable to your deployment environment.

cd ~
cat <<EOF > localhost.yml 
system_mode: standard


external_oam_subnet: <OAM-IP-SUBNET>/<OAM-IP-SUBNET-LENGTH>
external_oam_gateway_address: <OAM-GATEWAY-IP-ADDRESS>
external_oam_floating_address: <OAM-FLOATING-IP-ADDRESS>
external_oam_node_0_address: <OAM-CONTROLLER-0-IP-ADDRESS>
external_oam_node_1_address: <OAM-CONTROLLER-1-IP-ADDRESS>

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

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:
(Use the OAM and MGMT port names, e.g. eth0, applicable to your deployment environment.)

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}
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:

system ntp-modify ntpservers=0.pool.ntp.org,1.pool.ntp.org

OPTIONALLY for Kubernetes, i.e. if planning on using SRIOV network attachments in application containers, or
REQUIRED for OpenStack,
configure data interfaces for controller-0: (Use the DATA port names, e.g. eth0, applicable to your deployment environment.)

# For Kubernetes SRIOV network attachments

# configure SRIOV device plugin
system host-label-assign controller-0 sriovdp=enabled
# If planning on running DPDK in containers on this hosts, configure number of 1G Huge pages required on both NUMA nodes
system host-memory-modify controller-0 0 -1G 100
system host-memory-modify controller-0 1 -1G 100

# For both Kubernetes and OpenStack

export COMPUTE=controller-0
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}')

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, configure the system setting for the vSwitch.

StarlingX has OVS (kernel-based) vSwitch configured as default:

  • Running in a container; defined within the helm charts of stx-openstack manifest.
  • Shares the core(s) assigned to the Platform.

If you require better performance, OVS-DPDK should be used:

  • Running directly on the host (i.e. NOT containerized).
  • Requires that at least 1 core be assigned/dedicated to the vSwitch function.

To deploy the default containerized OVS:

system modify --vswitch_type none

I.e. do not run any vSwitch directly on the host, and use the containerized OVS defined in the helm charts of stx-openstack manifest.

To deploy OVS-DPDK (OVS with the Data Plane Development Kit, which is supported only on bare metal hardware, run the following command:

system modify --vswitch_type ovs-dpdk
system host-cpu-modify -f vswitch -p0 1 controller-0

Once vswitch_type is set to OVS-DPDK, any subsequent nodes created will default to automatically assigning 1 vSwitch core for AIO Controllers and 2 vSwitch cores for Computes.

When using OVS-DPDK, Virtual Machines must be configured to use a flavor with property: hw:mem_page_size=large.

Caution icon.svg Important

After controller-0 is unlocked, changing vswitch_type would require locking and unlocking all computes (and/or AIO Controllers) in order to apply the change.

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_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.

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.