0d7c02f132
We ran into this when fixing the zuul02 swap partition. Essentially parted complained that our alignments weren't optimal. After some googling the Internet said that using multiples of 8 tends to be safe. We shifted the offset from 1MB to 8MB to start the partition and the warnings went away. Add this change into make_swap.sh to automate this for future servers. Change-Id: Iad3ef40cf2c1e064482d49bd722c3de4354ec74d
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.opendev.org
cd /opt/system-config/launch/
./launch-node.py $FQDN --flavor "$FLAVOR" \
--cloud=$OS_CLOUD --region=$OS_REGION_NAMEManually add the hostname to DNS (the launch script does not do so automatically, but it prints the commands to run). Note that for *.opendev.org hosts you'll only be able to add the reverse dns records via the printed commands. Forward A and AAAA records should be added to opendev/zone-opendev.org/zones/opendev.org/zone.db.
We need to add the host to our static inventory file so that the ansible runs see the new host. The launch script prints out the appropriate lines to add to opendev/system-config:inventory/openstack.yaml.
In order for Ansible to work, you also need to accept the root SSH key for the new server. Once the new DNS entries have propagated, 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
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