opendev/system-config
Code Issues Proposed changes
f57a5aa61b
system-config/launch/README.rst
Ian Wienand ed7083ed88
launch-node : make into a small package 
This turns launch-node into an installable package.  This is not meant
for distribution, we just encapsulate the installation in a virtualenv
on the bastion host.  Small updates to documentation and simple
testing are added (also remove some spaces to make test_bridge.py
consistent).

Change-Id: Ibcb4774114d73600753ca155ed277d775964bc79
2022-11-21 16:29:22 +11:00

1.4 KiB
Raw Blame History

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