Agility, speed, and simplicity
are mandatory when undertaking digital transformation.
HPE GreenLake for Private Cloud Enterprise
gives cloud operators the flexibility to deploy virtual machines,
containers, or bare metal resources to meet the specific needs of different apps
and workloads.
In this demo, we are going to create a compute instance on bare metal.
Bare metal can provide greater performance for heavy workloads.
To begin, click on the HPE GreenLake for Private Cloud Enterprise tile.
From the HPE GreenLake for Private Cloud Enterprise dashboard,
let’s select Bare Metal.
Now we are on the Compute Groups screen
where we can see a list of compute groups previously created,
as well as the consumption and health of our bare metal environment.
Let’s click on the Engineering group we created in the previous demo.
Here we can see when this compute group was created
and get information about restricted instance types and resource limits.
Let's create a Private Network by clicking on the relevant tab.
Private networks allow compute instances within a compute group
to communicate with each other.
These networks do not connect to external networks
and are only visible to instances within the same compute group.
This provides privacy and isolation from compute instances in other groups.
Click on Create Network.
We will give our private network the name ‘BackupEngineering.’
There are optional fields to add a Description
or change the Network Use Policy field,
but we will leave these with the default values.
Click on the Purpose field and select Backup.
Once complete, click Create.
The new private network has been created successfully.
Click on IP Pools to find the automatically created IP Pool information.
Now that all the prerequisite resources are created,
we are ready to provision a Bare Metal compute instance.
Select the Compute Instances tab…
…and click on Create Compute Instance.
For this demo,
we will add the compute instance name of ‘AppDeveloperInstance001.’
The description is optional.
Next, select an available Instance Type…
For our purposes, we will choose ‘G2i.’
Next, select an image.
From the dropdown menu, we can see several available OS images,
such as VMware ESXI, RHEL, and Ubuntu.
For this demo, we are going to select VMware ESXI image.
Next, we will create an SSH Key.
Click on Name and enter ‘MySSHKey.’
Paste the SSH key generated from the local computer.
Now press the Create SSH Key button at the bottom.
We now see the newly created SSH key in the list.
Next, select the networks that the compute instance should connect to.
A list of Networks may be automatically populated,
depending on how the Cloud Operator has set up the bare metal infrastructure.
Networks that are mandatory cannot be deselected.
In this example ‘Toronto Foundation Services External Network’ is mandatory
because it typically provides external internet access to the compute instance.
In this step, let’s select the network we just created, ‘BackupEngineering.’
Finally, the Network for Default Route indicates which one of the selected
networks should be the default route for the compute instance.
This is typically the primary network with connections to a border gateway
or router.
Select ‘BackupEngineering.’
Lastly, we will create a volume.
Volumes are network-attached storage that can be provisioned
and attached to computer instances to provide dedicated
or shared storage volumes.
We can pre-create volumes first,
or we can create one when creating compute instances like this example.
Click in the field for Name and enter ‘Volume1.’
Click on the Volume Capacity field, then set the size to 10.
Click on Volume Type…
...and select Block Storage – Standard (Bs).
Storage volumes may be created for a specific compute instance
or shared among multiple compute instances within a compute group.
In this demo we will not make this volume shareable.
Click on Create Volume.
Now that the compute instance configuration is complete,
click on the Create Instance button.
The instance creation takes a few minutes.
Once successfully created, the compute instance is visible in the Instances list.
It will display its OS imaging state,
steps, and a progress bar indicating the progress of the imaging process.
With intuitive self-service menus and automation,
HPE GreenLake for Private Cloud Enterprise
makes it easy for cloud operators to spin up the bare metal resources
their heavy workloads demand.