Provision Virtual Machines with an Open Source Physical Infrastructure Solution

Rob Hirschfeld, CEO/Co-Founder, RackN created a new Digital Rebar Provision (DRP) video highlighting the creation of virtual machines within the standard automation process. Highlights:

  • Create a New Virtual Machine from the Physical Provisioning Tool – DRP
  • VirtualBox IMPI Plugin – Preview of Pre-Release Tool
  • RackN Portal will inventory virtual machines available on network for management
  • Packet IMPI Plugin – enable creation of VMs on Packet cloud hardware

This expansion to virtual machines allows DRP users to not only provision physical infrastructure but virtual as well both locally and in clouds.

More information on the Digital Rebar community and Digital Rebar Provision:

RackN Portal Management Connection to the 10 Minute Demo

In my previous blog, I provided step by step directions to install Digital Rebar Provision on a new endpoint and create a new node using Packet.net for users without a local hardware setup. (Demo Tool on GitHub) In this blog, I will introduce the RackN Portal and connect it to the active setup running on Packet.net at the end of the demo process.

NOTE – You will need to run the demo process again to have both the DRP installation and endpoint active on Packet.net.

Current Status

There will be two machines running in Packet:

  • Digital Rebar Provision running on an Endpoint
  • A new physical node provided by DRP

In order to have run the process in the previous blog, you will have created a RackN Portal account to get the RackN code to add into the Secrets file.

Steps to Connect RackN Portal

When you first go to the RackN Portal you will see the following screen:

The first step is to enter the Endpoint Address which will come from the Packet.net Endpoint server setup in the previous blog. To get the address go to the “Configure DRP” step and you will see the following which contains the Endpoint http address:

running ACTION:  drp-setup-demo
+ set +x
+ drpcli –endpoint=https://147.##.##.63:8092 bootenvs uploadiso centos-7-install
{
 “Path”: “CentOS-7-x86_64-Minimal-1708.iso”,

“Size”: 830472192
}
+ set +x
{
 “centos-7-install”: “packet-ssh-keys:Success”,

“discover”: “packet-discover:Success”,
“packet-discover”: “centos-7-install:Reboot”,
“packet-ssh-keys”: “complete-nowait:Success”
}

Enter the following https address https://147.##.##.63:8092 into the Endpoint Address and press the blue arrow. You will then be taken to the login screen where you enter the standard login info:

Select “Defaults” to have the system fill in the Login information. If you need more information on this screen, please review the Install Guide.

RackN Portal Tour

After completing the login your RackN Portal screen will look like this:

At this point, we want to see the new node that was created in the final step of our demo process. Select “Machines” on the left-hand navigation below SYSTEM and you will see the new machine that was created. NOTE – The Red X next to Subnets is appropriate for Packet.net infrastructure.

You can confirm this machine name with the name of the machine in the last stage of the process. Both the RackN Portal and the data below indicate that I have created a new node called “spectordemo-machines-ewr1-01“.

Selecting the newly created machine you will see the following information:

In the next blog, we will use the RackN Portal to create a second node and look at the Workflow process to install an operating system on both nodes.

If you have any questions or would like to get started learning more about Digital Rebar Provision and RackN please join the Slack community.