HyperCloud Setup

Warning

If you are reusing nodes from an existing HyperCloud cluster or plan to repurpose nodes from a legacy HyperDrive cluster then all the nodes must first be reset to factory state before continuing.

The HyperCloud cluster is configured in stages:

Boot the static nodes
Boot any remaining storage nodes
Boot the compute nodes
Configure the HyperCloud Dashboard

Tip

To allow faster cluster convergence on an initial build, it is recommended to set the hardware clock from the UEFI to a time and date as closely together as possible. If the node clocks are too far apart then cluster convergence may take several hours.

Boot the Static Nodes

Attach a serial console cable to the first static node and power up (serial baud rate 115200)
- Select Boot HyperCloud Static Node 1
- If this is the first time booting the node will determine if the system time has been configured and may prompt the user to manually set the system time:
```
The current system time is:

16:24:33 2023/10/25

Please choose one of the following:
1: Change the system time
2: Keep the current system time
> 1
Enter a new system time with the format:

hour:minute:seconds year/month/day

For example:

23:08:41 2023/09/21

The system time must be UTC
> 16:25:30 2023/10/25
New system time is : 16:25:30 2023/10/25

Would you like to apply the new system time?
1: Apply the new system time
2: Change the new system time
> 1
```
- Once the user either confirms the system time or manually inputs the time in the specific format, the system will record this time and no longer prompt for this information in future boots.
- Wait for the boot to complete and HyperCloud to perform system checks.
- Verify release information:
```
lsb_release -a
```
Attach a serial console cable to the second static node and power up
- Select Boot HyperCloud Static Node 2
Attach a serial console cable to the third static node and power up
- Select Boot HyperCloud Static Node 3
Watch for the OSDs to be created
- Run ceph -s to verify

Boot the Storage Nodes

Boot any remaining Storage Nodes one by one, ensuring they PXE boot
Watch for the OSDs to be created
- Run ceph -s to verify

Boot the Compute Nodes

Power up the Compute Nodes one by one, ensuring they PXE boot

Tip

There is no need to wait for them to boot fully.

Setup HyperCloud Dashboard

Once all three static nodes are up use one to set the following information using:

hypercloud-manage

Parameter	Value
Compute (KVM) VLAN ID	3369 (unless changed in Interconnect Setup)
Storage VLAN ID	3368 (unless changed in Interconnect Setup)
Dashboard system VLAN ID	optional
Dashboard system IP Address	optional
Dashboard system netmask	recommended value: 255.255.255.0
Dashboard system default gateway	optional
Dashboard system DNS servers	optional
Dashboard system Syslog servers	optional
Dashboard system NTP servers	optional

Tip

The Dashboard system IP Address set above is the same IP address used by Glasshouse the management GUI

Check that the HyperCloud dashboard comes up.
Tip
- On the first compute node you should see the dashboard with virsh list.
- You can connect to the command line of the dashboard with hypercloud-dashboard-console from that hostname.

Retrieve Admin Credentials

You can obtain the admin:password login from the HyperCloud dashboard:
```
cat /var/lib/one/.one/one_auth
```

Open Glasshouse

Using your web browser of choice, navigate to the URL which points to your HyperCloud Dashboard e.g. https://<dashboard IP>. This will open Glasshouse, the HyperCloud management GUI (Graphical User Interface). Glasshouse is used administer the cluster and to create, manage, and share Virtual Machines.

Tip

The dashboard IP & cluster admin password are specified in the dashboard configuration step above.
Log in with the Admin Credentials
This is a good opportunity to add SSH keys to the Cluster SSH Authorized Keys