opendev/system-config

History

Monty Taylor ebae022d07 Use project-config from zuul instead of direct clones We use project-config for gerrit, gitea and nodepool config. That's cool, because can clone that from zuul too and make sure that each prod run we're doing runs with the contents of the patch in question. Introduce a flag file that can be touched in /home/zuulcd that will block zuul from running prod playbooks. By default, if the file is there, zuul will wait for an hour before giving up. Rename zuulcd to zuul To better align prod and test, name the zuul user zuul. Change-Id: I83c38c9c430218059579f3763e02d6b9f40c7b89		2020-04-15 12:29:33 -05:00
..
dns.py	launch.py : fix typo calling legacy dns print function	2019-05-20 13:37:07 +10:00
launch-node.py	Use project-config from zuul instead of direct clones	2020-04-15 12:29:33 -05:00
README.rst	Make small tweaks to launch node README	2020-02-12 08:42:32 -06:00
sshclient.py	launch-node.py: More verbose logging	2016-08-24 11:06:57 +10:00
utils.py	Add base playbooks and roles to bootstrap a new server	2018-08-01 14:57:44 -07:00

README.rst

Create Server

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:

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:

./dns.py $FQDN