The "PVHVM" image appears to have disappeared from RAX, replaced with a "Cloud" image. Maybe I haven't looked in the right place, but I can't find any info on if, why or when this was updated. But I started a server with the "Cloud" image and it seems the same as the PVHVM image to me; hdparm showed read speads the same as a older server and dd writes to a file were the same speed (recorded below for posterity). ianw@nb04:~$ dd if=/dev/zero of=testfile bs=1G count=1 oflag=direct 1+0 records in 1+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.21766 s, 206 MB/s ianw@nb04:~$ sudo hdparm -Tt /dev/xvda /dev/xvda: Timing cached reads: 16428 MB in 1.99 seconds = 8263.05 MB/sec Timing buffered disk reads: 752 MB in 3.00 seconds = 250.65 MB/sec From looking at dmesg it has [ 0.000000] DMI: Xen HVM domU, BIOS 4.1.5 11/28/2013 [ 0.000000] Hypervisor detected: Xen HVM [ 0.000000] Xen version 4.1. [ 0.000000] Xen Platform PCI: I/O protocol version 1 [ 0.000000] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs. [ 0.000000] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks. which, if  is anything to go by suggests it is in PVHVM mode anyway. tl;dr seems like the image name changed.  https://xen-orchestra.com/blog/debian-pvhvm-vs-pv/ Change-Id: I4ff14e7e36f59a9487c32fdc6940e8b8a93459e6
|2 weeks ago|
|README.rst||1 month ago|
|dns.py||10 months ago|
|launch-node.py||2 weeks ago|
|sshclient.py||3 years ago|
|utils.py||1 year ago|
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_NAME
Manually 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:
Verify the fingerprint of the new server and type "yes" to accept. Then you can log out.
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: