system-config/launch
Ian Wienand 908e6cfd86 launch-node.py : add timeout option
Some clouds may be a little slower than others building images and to
override the create_server default timeout of 3 minutes (180) you have
to hand edit -- add a global timeout option and use that consistently.

Change-Id: I66032ef929746739d07dca3fd178b8c43bb8174c
2018-09-12 12:32:29 +10:00
..
README Update launch README for bridge 2018-09-06 14:38:25 -07:00
dns.py Add base playbooks and roles to bootstrap a new server 2018-08-01 14:57:44 -07:00
launch-node.py launch-node.py : add timeout option 2018-09-12 12:32:29 +10: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.openstack.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).

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.

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