Provision Host#
The Provision Host feature allows you to provision an OS profile onto a previously onboarded host.
Go to the Infrastructure tab, click Hosts on the left menu and select the Onboarded tab:
Find a host in Onboarded state.
Go to the Actions column and click the three-dot icon for the desired host, then click Provision:
You will enter the Host Provisioning flow now. This flow has two steps - Configure All Hosts and Review and Customize. Any configuration that you make in the Configure All Hosts step will be applied to all hosts. Individual host configurations can be edited in the Review and Customize step.
Search and select the site that the host is connected to.
Select the required OS Profile from the drop-down menu.
If you came to this stepper flow from the Register Edge Nodes in Edge Manageability Framework page and you selected Create Single-host Clusters, you can pick the required Cluster Template and Version now. Otherwise, these two dropdowns will not be shown.
Click Advanced Options to see more options that you can configure. This includes:
vPro: Enable or disable vPro on the host. The default option is disabled.
Secure Boot and Full Disk Encryption: Enable or disable secure boot and full disk encryption. The default option is disabled.
SSH Key Name: Select an SSH public key for login. It is optional to add an SSH key. However, you must have submitted the public key to the web UI using the instructions in Remote SSH Access.
Host Labels: Add any optional host labels to the host.
Click Next to proceed to the Review and Customize step. Here, you can review the configuration for all hosts and customize individual host configurations. You can expand each host to see more details.
If you want to customize the configuration for a specific host, click the three-dot icon next to the host, and then the Edit option.
This will open a drawer with the saved host configurations. You can edit individual configurations as needed and click Save to apply the changes.
Click Provision to finish the provisioning process.
Once the host is provisioned, you can find it in the Provisioned tab. You can check the host details from this tab by using the drop-down menu for the host:
For details on the host status, hover over the status in the Host Status to bring up a menu showing the breakdown of the overall host status:
Delete the host if you want to remove it from this page:
Note
To create a cluster for an individual host, see Create Cluster.
Operating System Profile#
Operating System Profile refers to the resources that describe the installation sources used. They are used for performing initial installations as well as propagating updates to the installed operating systems. They include information about the Operating System installation process, such as:
kernel command parameters and options
upstream packages and sources
security features
architecture
Additionally:
Intel-provided packages, such as edge node Agents.
Where and how updates to the OS can be obtained (update sources).
Digests for integrity checks.
User-defined names and descriptions.
profile-name, which is used by the provisioning components.
Note
Profile-name is a unique identifier in the system.
Update sources is repeated free-form text, OS-dependent.
Note
Only Debian-style OSs are currently supported by this software version. Each repeated text must be in the DEB822 format, which can embed the GNU Privacy Guard (GPG) key with the “Signed-By:” line.
For more information on OS and OS profiles, refer to View OS Profiles.
Host Label#
The Host Label refers to additional host-specific metadata. This option allows you to specify constraints for which Kubernetes Pods are deployed to specific hosts through automated deployment. Note that this is specified in the application’s Helm chart.
You can use them as a slicing mechanism. For example, if you want your solar plant controller Pod to be scheduled only on the hosts connected to the plants, you can specify this constraint as a special label identifying a subset of the hosts with this label. Hosts without this label would not receive this Pod.
In this example, target=solar-plant is specified as Host Label. For more information on leveraging the node labels and selectors in Kubernetes, see the Kubernetes documentation.