ff45b12412
As pointed out by clarkb in review of prior change I06995027a4b80133bdac91c263d7a92fd495493b the hostname handling here is a bit wonky. Use "host" instead of "hostname" since we use that in the rest of the file. The print_dns() function doesn't need a cloud argument, remove it. The print_sshfp_records was incorrectly splitting the host/domain for nodes like "mirror.rax.iad.openstack.org" -- simply pass only the host for the bind record from the print_dns() function. Change-Id: I3d851902ef52588a69294b02e22f4b4667454629 |
||
|---|---|---|
| .. | ||
| src/opendev_launch | ||
| pyproject.toml | ||
| 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_NAMEManually 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@$FQDNVerify 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