system-config

History

Jeremy Stanley ce70bde4de Use environment file in sample reverse DNS command With Ansible-based launch-node.py now using clouds.yaml, we're no longer setting up the environment variables expected by the rackdns utility for setting PTR resource records. Add a line to the example commands sourcing the appropriate variables into the environment first. Change-Id: Ia96296a8fac803d514e49eeeedaeebc76585d6fd		2016-03-23 14:37:52 +00:00
..
dns.py	Use environment file in sample reverse DNS command	2016-03-23 14:37:52 +00:00
launch-node.py	Don't pass OS_CLOUD and OS_REGION_NAME to expand-groups	2016-03-22 19:33:42 -05:00
README	Retire old launch-node.py	2016-03-09 14:23:54 -06:00
sshclient.py	Set hostname in launch node	2016-02-24 10:05:28 -08:00
utils.py	Remove interpret_puppet_exitcodes	2016-03-10 09:31:50 -06:00

README

Create Server
=============

Note that these instructions assume you're working from this
directory on an updated local clone of the repository on the
puppetmaster, and that your account is a member of the admin
and puppet groups for access to their respective keys::

  sudo adduser $(whoami) admin
  sudo adduser $(whoami) puppet

(Remember to log out and back into your shell if you add yourself
to a group.)

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

  export OS_CLOUD=openstackci-rax
  export OS_REGION=DFW
  export FLAVOR="8 GB Performance"
  export FQDN=servername.openstack.org
  cd /opt/system-config/production/launch/
  ./launch-node.py $FQDN --flavor "$FLAVOR" \
    --cloud=$OS_CLOUD --region=$OS_REGION

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

  export OS_CLOUD=openstackjenkins-rax
  export OS_REGION=DFW
  export FQDN=slavename.slave.openstack.org
  openstack image list
  export IMAGE='Ubuntu 12.04 LTS (Precise Pangolin) (PVHVM)'
  openstack flavor list
  export FLAVOR="8 GB Performance"
  ./launch-node.py $FQDN --image "$IMAGE" --flavor "$FLAVOR" \
     --cloud=$OS_CLOUD --region=$OS_REGION

Manually add the hostname to DNS (the launch script does not do so
automatically). Note that this example assumes you've already
exported a relevant FQDN and sourced the appropriate API credentials
above.

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 the puppetmaster:

  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