system-config/launch
Jeremy Stanley b44cae0233 Check launched server for x86-64-v2/sse4_2 support
The "UBI" that the latest Keycloak images are based on has a glibc
compiled to only work on x86-64-v2 systems, and in some regions we
seem to sometimes get hypervisors reporting older processor
architectures where it won't work. Check CPU flags for sse4_2
support as an indicator, and abort launching if it's not present.

Change-Id: Ib0f482a939f94e801c82f3583e0a58dc4ca1f35c
2024-02-08 18:42:20 +00:00
..
src/opendev_launch Check launched server for x86-64-v2/sse4_2 support 2024-02-08 18:42:20 +00:00
pyproject.toml Merge "launch: Automatically do RAX rdns updates when launching nodes" 2022-12-21 23:09:39 +00:00
README.rst launch-node : make into a small package 2022-11-21 16:29:22 +11:00

Create Server

The commands in this section should be run as root on the bastion host.

To launch a node in the OpenStack CI account (production servers):

export OS_CLOUD=openstackci-rax
export OS_REGION_NAME=DFW
export FLAVOR="8 GB Performance"
export FQDN=servername01.opendev.org

/usr/launcher-venv/bin/launch-node $FQDN --flavor "$FLAVOR" \
  --cloud=$OS_CLOUD --region=$OS_REGION_NAME

Manually add the hostname to DNS (the launch script does not do so automatically, but it prints the commands to run). Note that for *.opendev.org hosts you'll only be able to add the reverse dns records via the printed commands. Forward A and AAAA records should be added to opendev/zone-opendev.org/zones/opendev.org/zone.db.

We need to add the host to our static inventory file so that the ansible runs see the new host. The launch script prints out the appropriate lines to add to opendev/system-config:inventory/openstack.yaml.

In order for Ansible to work, you also need to accept the root SSH key for the new server. Once the new DNS entries have propagated, as root on the bastion server:

ssh root@$FQDN

Verify the fingerprint of the new server and type "yes" to accept. Then you can log out.

Add DNS Records

The launch-node script will print the commands needed to be run to configure DNS for a newly launched server. To see the commands for an existing server, run:

/usr/launcher-venv/bin/show-dns $FQDN