d50c384cee
Remove the section on launching nodes in the jenkins tenant. That never happens. Remove the bits about groups and sudo, as they aren't relevant any more. Remove the unused os_client_config import. Change-Id: I676bb7450ec80df73b76ee7841f78eadbe179183
38 lines
1.2 KiB
Plaintext
38 lines
1.2 KiB
Plaintext
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
|