Make small tweaks to launch node README
First of all, we're using RST syntax, so rename it to README.rst. More importantly, remove menitons of puppetmaster - and puppet in general, as they are distracting. When reading the file, my eyes scanned and hit puppetmaster and I almost skipped the section with the assumption it was out of date. Change-Id: I294bf17084be7dad46e075ad2a3ef2674276c018
|1 week ago|
|README.rst||5 days ago|
|dns.py||9 months ago|
|launch-node.py||6 months ago|
|sshclient.py||3 years ago|
|utils.py||1 year ago|
The commands in this section should be run as root.
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 cd /opt/system-config/launch/ ./launch-node.py $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 bridge.openstack.org:
Verify the fingerprint of the new server and type "yes" to accept. Then you can log out.
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: