History

When bringing up a new server, scan the ssh-keys of the remote IP and
add them automatically to the inventory output.

c.f. I4863425d5b784d0cdf118e1252414ca78fd24179

Change-Id: I2120fd476aa89e207ab76a1fc0faeeb5a0fb55ce

2022-12-01 11:29:36 +11:00

src/opendev_launch

launch: add ssh keys to inventory

2022-12-01 11:29:36 +11:00

pyproject.toml

launch: Automatically do RAX rdns updates when launching nodes

2022-12-01 11:26:32 +11:00

README.rst

launch-node : make into a small package

2022-11-21 16:29:22 +11:00

README.rst

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