It’s pretty damn simple to boot a virtual machine using the Openstack API. In this case I want to boot an image that is the same identical reference as the base image that a customer of ours is using that is getting some bad Cloud Block Storage performance. Being able to replicate the circumstances precisely is important when trying to recreate the symptoms of the customer. Configuring a new boot is really easy to do thru the API using supernova.
supernova customer boot testing-cbs-lon --image 9g46rb-79d6-45eb-9505-fb0bf31556d7 --flavor performance1-4
The above command is using my ‘customer’ auth user configuration (single API user, as opposed to admin API). I have asked API to boot a performance server with 4GB ‘performance1-4’ Using the image id ‘9g46rb-79d6-45eb-9505-fb0bf31556d7’ which is a customers image reference running windows. I tell the API I want to call the server testing-cbs-lon, and here is what I get back after running it
+--------------------------------------+-------------------------------------------------------------------+
| Property | Value |
+--------------------------------------+-------------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | - |
| OS-EXT-STS:vm_state | building |
| RAX-PUBLIC-IP-ZONE-ID:publicIPZoneId | e1cc4036fc52d50ca8ac2e90ff57e6b8c38d850bf6e3bd608e800971 |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | censoredforsecurity |
| config_drive | |
| created | 2015-09-17T08:23:25Z |
| flavor | 4 GB Performance (performance1-4) |
| hostId | |
| id | d23cc039-ecc7-442a-81ad-b6bbb7a8c8e9 |
| image | Windows Server 2008 R2 SP1 (8f39aeb0-79d6-45eb-9505-fb0bf31556d7) |
| key_name | - |
| metadata | {} |
| name | testing-cbs-lon |
| progress | 0 |
| status | BUILD |
| tenant_id | 10045567 |
| updated | 2015-09-17T08:23:26Z |
| user_id | 05b18e859cad42bb9a5a35ad0a6fba2f |
+--------------------------------------+-------------------------------------------------------------------+
So it’s building, lets presume I want to check on the status of the server now. The id of the server, we can see is ‘d23cc039-ecc7-442a-81ad-b6bbb7a8c8e9’. So lets ask supernova to show the details for this server again for us.
supernova customer show d23cc039-ecc7-442a-81ad-b6bbb7a8c8e9
[SUPERNOVA] Running nova against customer...
+--------------------------------------+-------------------------------------------------------------------+
| Property | Value |
+--------------------------------------+-------------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | spawning |
| OS-EXT-STS:vm_state | building |
| RAX-PUBLIC-IP-ZONE-ID:publicIPZoneId | e1cc4036fc52d50ca8ac2e90ff57e6b8c38d850bf6e3bd608e800971 |
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2015-09-17T08:23:25Z |
| flavor | 4 GB Performance (performance1-4) |
| hostId | d9a81c37f8f8aba51cd30a04151d99d2bdd60ad4504d4c95f4a3f609 |
| id | d23cc039-ecc7-442a-81ad-b6bbb7a8c8e9 |
| image | Windows Server 2008 R2 SP1 (8f39aeb0-79d6-45eb-9505-fb0bf31556d7) |
| key_name | - |
| metadata | {} |
| name | testing-cbs-lon |
| private network | 10.1.1.1 |
| progress | 80 |
| public network | 134.1.1.1 , 2a00:1a48:7810:101:be76:4eff:fe08:1f5d |
| status | BUILD |
| tenant_id | 10045567 |
| updated | 2015-09-17T08:28:28Z |
| user_id | 05b18e859cad42bb9a5a35ad0a6fba2f |
+--------------------------------------+-------------------------------------------------------------------+
As we can see the server is still building but it has started to get it’s network added.
If I wanted to see all the different flavors available (GB ram , disk, etc) we could run a
supernova customer flavor-list [SUPERNOVA] Running nova against customer... +------------------+-------------------------+-----------+------+-----------+------+-------+-------------+-----------+ | ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | +------------------+-------------------------+-----------+------+-----------+------+-------+-------------+-----------+ | 2 | 512MB Standard Instance | 512 | 20 | 0 | 512 | 1 | 80.0 | N/A | | 3 | 1GB Standard Instance | 1024 | 40 | 0 | 1024 | 1 | 120.0 | N/A | | 4 | 2GB Standard Instance | 2048 | 80 | 0 | 2048 | 2 | 240.0 | N/A | | 5 | 4GB Standard Instance | 4096 | 160 | 0 | 2048 | 2 | 400.0 | N/A | | 6 | 8GB Standard Instance | 8192 | 320 | 0 | 2048 | 4 | 600.0 | N/A | | 7 | 15GB Standard Instance | 15360 | 620 | 0 | 2048 | 6 | 800.0 | N/A | | 8 | 30GB Standard Instance | 30720 | 1200 | 0 | 2048 | 8 | 1200.0 | N/A | | compute1-15 | 15 GB Compute v1 | 15360 | 0 | 0 | | 8 | 1250.0 | N/A | | compute1-30 | 30 GB Compute v1 | 30720 | 0 | 0 | | 16 | 2500.0 | N/A | | compute1-4 | 3.75 GB Compute v1 | 3840 | 0 | 0 | | 2 | 312.5 | N/A | | compute1-60 | 60 GB Compute v1 | 61440 | 0 | 0 | | 32 | 5000.0 | N/A | | compute1-8 | 7.5 GB Compute v1 | 7680 | 0 | 0 | | 4 | 625.0 | N/A | | general1-1 | 1 GB General Purpose v1 | 1024 | 20 | 0 | | 1 | 200.0 | N/A | | general1-2 | 2 GB General Purpose v1 | 2048 | 40 | 0 | | 2 | 400.0 | N/A | | general1-4 | 4 GB General Purpose v1 | 4096 | 80 | 0 | | 4 | 800.0 | N/A | | general1-8 | 8 GB General Purpose v1 | 8192 | 160 | 0 | | 8 | 1600.0 | N/A | | io1-120 | 120 GB I/O v1 | 122880 | 40 | 1200 | | 32 | 10000.0 | N/A | | io1-15 | 15 GB I/O v1 | 15360 | 40 | 150 | | 4 | 1250.0 | N/A | | io1-30 | 30 GB I/O v1 | 30720 | 40 | 300 | | 8 | 2500.0 | N/A | | io1-60 | 60 GB I/O v1 | 61440 | 40 | 600 | | 16 | 5000.0 | N/A | | io1-90 | 90 GB I/O v1 | 92160 | 40 | 900 | | 24 | 7500.0 | N/A | | memory1-120 | 120 GB Memory v1 | 122880 | 0 | 0 | | 16 | 5000.0 | N/A | | memory1-15 | 15 GB Memory v1 | 15360 | 0 | 0 | | 2 | 625.0 | N/A | | memory1-240 | 240 GB Memory v1 | 245760 | 0 | 0 | | 32 | 10000.0 | N/A | | memory1-30 | 30 GB Memory v1 | 30720 | 0 | 0 | | 4 | 1250.0 | N/A | | memory1-60 | 60 GB Memory v1 | 61440 | 0 | 0 | | 8 | 2500.0 | N/A | | performance1-1 | 1 GB Performance | 1024 | 20 | 0 | | 1 | 200.0 | N/A | | performance1-2 | 2 GB Performance | 2048 | 40 | 20 | | 2 | 400.0 | N/A | | performance1-4 | 4 GB Performance | 4096 | 40 | 40 | | 4 | 800.0 | N/A | | performance1-8 | 8 GB Performance | 8192 | 40 | 80 | | 8 | 1600.0 | N/A | | performance2-120 | 120 GB Performance | 122880 | 40 | 1200 | | 32 | 10000.0 | N/A | | performance2-15 | 15 GB Performance | 15360 | 40 | 150 | | 4 | 1250.0 | N/A | | performance2-30 | 30 GB Performance | 30720 | 40 | 300 | | 8 | 2500.0 | N/A | | performance2-60 | 60 GB Performance | 61440 | 40 | 600 | | 16 | 5000.0 | N/A | | performance2-90 | 90 GB Performance | 92160 | 40 | 900 | | 24 | 7500.0 | N/A | +------------------+-------------------------+-----------+------+-----------+------+-------+-------------+-----------+
On the left are the names to use for the first command we entered. So we can spin up a whole host of different servers. If we wanted to know details about a specific flavor, then we can run a flavor-show command like so:
[SUPERNOVA] Running nova against customer...
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Property | Value |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| OS-FLV-EXT-DATA:ephemeral | 900 |
| OS-FLV-WITH-EXT-SPECS:extra_specs | {"number_of_data_disks": "3", "resize_policy_class": "performance_flavor", "class": "performance2", "disk_io_index": "70", "policy_class": "performance_flavor"} |
| disk | 40 |
| extra_specs | {"number_of_data_disks": "3", "resize_policy_class": "performance_flavor", "class": "performance2", "disk_io_index": "70", "policy_class": "performance_flavor"} |
| id | performance2-90 |
| name | 90 GB Performance |
| ram | 92160 |
| rxtx_factor | 7500.0 |
| swap | |
| vcpus | 24 |
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+
A lot of information about the avaialble ram, 90GB, The primary disk and ephemeral (data) disk are shown. This is handy way to get information about virtualised servers, and ends this brief tutorial on using the rackspace openstack API with supernova.