system-config

History

Monty Taylor eb6c3c2f1a Add global inventory to launch_node Passing the -i to the jobdir means we're overriding the inventory. This means variables that come from the /etc/ansible vars, like sysadmins, are missing. Add the global inventory to the command line for ansible-playbook. We have --limit specified from '-l' - so we should still only run on the host in question. Change-Id: Ia67e65d25a1d961b619aa445303015fd577dee57		2019-03-08 17:53:28 +00:00
..
dns.py	Print yaml inventory instructions	2019-02-28 18:21:20 +00:00
launch-node.py	Add global inventory to launch_node	2019-03-08 17:53:28 +00:00
README	Update launch docs for opendev and static inventory	2019-02-15 10:59:56 -08: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

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 openstack-infra/zone-opendev.org/zones/opendev.org/zone.db.

In order for Ansible to be able to send out the Puppet updates,
you also need the puppetmaster to accept the root SSH key for the
new server. So 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.

Finally we need to add the host to our static inventory file so that
the periodic ansible runs (which can run puppet) see the new host.
Update openstack-infra/system-config/inventory/openstack.yaml to
include the appropriate hostname and IP address details.

Add DNS Records
===============

There are no scripts to automatically handle DNS at the moment due to
a lack of library support for the new Rackspace Cloud DNS (with IPv6).
However, 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