Demo: Provision bare metal on OpenStack

Provision bare metal on OpenStack through the Horizon management dashboard.

In the following video, we’ll demonstrate provisioning of bare-metal servers using the OpenStack Horizon Portal and the command line tools. We’ll also demonstrate how hybridization, or the seamless blend of virtual and bare metal, works within our OpenStack environment.

Step-by-step: Provisioning bare-metal servers

  1. From the Horizon dashboard, enter in the API username and password in order to sign in. Select the facility at the top of the list. This brings you to the appropriate cloud region that contains both virtual and bare metal.
  2. Select Instances from the left column and then to the right and select Launch Instance. Enter the instance name, which is also the host name. In the OpenStack flavor list, you see both virtual machine instances and bare-metal configurations.
  3. Select Boot Source, boot from an image, and then select from one of the three operating systems available currently.
  4. From the Access and Security tab, select an RSA key pair for SSH or enter in the administrative or root user password.
  5. There are two networking options, although there will be 10 VLANs available for bare-metal configurations. There is a WAN, or public VLAN interface, and a LAN, or private networking interface. This is for inter-server communication.
  6. Select Launch Instance.
  7. Click on Access and Security and API Access. You get a list of API endpoints that you can use for interacting with the OpenStack command line tools or the OpenStack API. For using command line tools, you will need to download a configuration file or create it manually.
  8. Click the Download button. Open the terminal window and load the OpenStack configuration file.
  9. Let’s view the active instances, or you can use Nova List to view all instances. You can also view our OpenStack flavors, or bare metal configurations. There are four bare-metal configurations, or you can use the Image List command to view the available disk images.
  10. Using the Network List command, you can view the available networks. This shows the WAN and LAN interfaces we saw earlier in the Horizon portal.
  11. Launch a virtual machine server instance. Using the Nova Boot command, you can specify the virtual machine configuration, the disk image, and the networks assigned to this virtual machine.
  12. When you return to the portal, you can view the instances, and you see both the bare-metal configuration and the virtual machine configuration.
  13. You can see the cloud instance, the network configuration, including the public IP address, the fact that it’s active and the power state is running.
  14. Let’s return to the terminal window and ping that IP address. Now, let’s go to the second terminal window, let’s SSH into the virtual machine we created. As you can see, we are now logged into Cloud-01.
  15. Returning to the portal, you can see the public IP address for our bare-metal configuration, that the server is active and it is running.
  16. Let’s return to the terminal windows and ping the server. Let’s open up a third terminal window and let’s SSH into the box. We are now successfully connected to two servers, virtual and bare metal.
  17. Let’s ping the bare-metal server from the virtual machine. Let’s obtain the virtual machine’s IP address and ping it from bare metal. You can also see that they’re participating on the same IP network block. This demonstrates Internap’s commitment to hybridization between virtual and bare metal.
  18. Since we’re logged into the bare-metal server, let’s view the network interfaces. As you can see, there are two network interfaces and we bond the NICs in order to provide higher throughput, failover and reliability.

View available configurations and choose your bare-metal AgileSERVER.