system-config

History

Prevent launch-node from breaking generated groups

There are potentially two related issues here which can result in
an empty generated groups file. The first is that if there are OS_
environment variables set, then os-client-config can create an 'environ'
cloud. That cloud then, in most cases here, will not be a valid cloud
since it won't be a full config, so iterating over all existing clouds
to get their server will fail, meaning that the inventory will be empty
meaning that generated groups will then be generated empty.

To deal with that, we can consume the newer upstream option that allows
the inventory to not bail out if it has a bad cloud, but instead get all
of the resources from the clouds that do work.

Additionally though, we can do an explicit inventory run so that we can
look to see if the inventory run failed, and if so, avoid running the
expand-groups.sh script, since we'd be fairly assured that it would be
running on top of a bad inventory cache.

Change-Id: Ib18987b3083f6addc61934b435d7ecb14aa1d25a

2016-07-07 11:21:14 -05:00

dns.py

Use environment file in sample reverse DNS command

2016-03-23 14:37:52 +00:00

launch-node.py

Prevent launch-node from breaking generated groups

2016-07-07 11:21:14 -05:00

README

Use an ordinal server naming pattern

2016-05-23 19:42:18 +00: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=servername01.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=slavename01.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