To launch a node in the OpenStack CI account (production servers)::

  . openstackci-rs-nova.sh

To launch a node in the OpenStack Jenkins account (slave nodes)::

  . openstackjenkins-rs-nova.sh

Then::

  puppet cert generate servername.openstack.org
  ./launch-node.py servername.openstack.org --cert servername.openstack.org.pem

If you are launching a replacement server, you may skip the generate
step and specify the name of an existing puppet cert (as long as the
private key is on this host).

The server name and cert names may be different.

Manually add the hostname to DNS (the launch script does not do so
automatically).

DNS
===

There are no scripts to handle DNS at the moment due to a lack of
library support for the new Rackspace Cloud DNS (with IPv6).  To
manually update DNS, you will need the hostname, v4 and v6 addresses
of the host, as well as the UUID.  The environment variables used in
the URL should be satisfied by sourcing the "openstackci-rs-nova.sh"
script (or jenkins, as appropriate).

  . ~/rackdns-venv/bin/activate
  . openstackci-rs-nova.sh

  rackdns rdns-create --name HOSTNAME.openstack.org --data IPV6ADDR --server-href https://$OS_REGION_NAME.servers.api.rackspacecloud.com/v2/$OS_TENANT_NAME/servers/UUID --ttl 300
  rackdns rdns-create --name HOSTNAME.openstack.org --data IPV4ADDR --server-href https://$OS_REGION_NAME.servers.api.rackspacecloud.com/v2/$OS_TENANT_NAME/servers/UUID --ttl 300

  . openstack-rs-nova.sh
  rackdns record-create --name HOSTNAME.openstack.org --type AAAA --data IPV6ADDR --ttl 300 openstack.org
  rackdns record-create --name HOSTNAME.openstack.org --type A --data IPV4ADDR --ttl 300 openstack.org