453051aafb
There is a bug in OCC that causes an envvars cloud to be created when the only two env vars are the selectors OS_CLOUD and OS_REGION_NAME. So exclude them from the envionment when running the group creation command. Also, there is a bug in the invocation of the hostname playbook, in that it was passing in the UUID as the target to run against, but we're writing out a name-based inventory. Change-Id: I0b524dc43ec96c6645ae82a090744eab463e7fb9 |
||
---|---|---|
.. | ||
dns.py | ||
launch-node.py | ||
README | ||
sshclient.py | ||
utils.py |
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