20d2643f74
On the old bridge node we had some unmanaged venv's with a very old, now unmaintained RAX DNS API interaction tool. Adding the RDNS entries is fairly straight forward, and this small tool is mostly a copy of some of the bits for our dns api backup tool. It really just comes down to getting a token and making a post request with the name/ip addresses. When the cloud the node is launched as is identified as RAX, this will automatically add the PTR records for the ip4 & 6 addresses. It also has an entrypoint to be called manually. This is added and hacked in, along with a config file for the appropriate account (I have added these details on bridge). I've left the update of openstack.org DNS entries as a manual procedure. Although they could be set automatically with small updates to the tool (just a different POST) -- details like CNAMES, etc. and the relatively few servers we start in the RAX mangaed DNS domains means I think it's easier to just do manually via the web ui. The output comment is updated. Change-Id: I8a42afdd00be2595ca73819610757ce5d4435d0a
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