Configuring provisioning resources

Click Any Organization and select the organization.

Click Any Location and select the location to use.

In the orcharhino management UI, navigate to Hosts > Operating systems and click New Operating system.

In the Name field, enter a name to represent the operating system entry.

In the Major field, enter the number that corresponds to the major version of the operating system.

In the Minor field, enter the number that corresponds to the minor version of the operating system.

In the Description field, enter a description of the operating system.

From the Family list, select the operating system’s family.

From the Root Password Hash list, select the encoding method for the root password.

From the Architectures list, select the architectures that the operating system uses.

Click the Partition table tab and select the possible partition tables that apply to this operating system.

Click the Installation Media tab and enter the information for the installation media source. For more information, see Adding Installation Media to orcharhino.

Click the Templates tab and select a PXELinux template, a Provisioning template, and a Finish template for your operating system to use. You can select other templates, for example an iPXE template, if you plan to use iPXE for provisioning.

On the Parameters tab, add the or_client_repo_url parameter, select the string type, and enter the value http://orcharhino.example.com/pulp/content/_My_Organization_/Library/custom/centos_Client/centos_Client_centos/.

Click Submit to save your provisioning template.

On orcharhino Server, run the following Bash script:

PARTID=$(hammer --csv partition-table list | grep "Kickstart default," | cut -d, -f1)
PXEID=$(hammer --csv template list --per-page=1000 | grep "Kickstart default PXELinux" | cut -d, -f1)
SATID=$(hammer --csv template list --per-page=1000 | grep "provision" | grep ",Kickstart default" | cut -d, -f1)

for i in $(hammer --no-headers --csv os list | awk -F, {'print $1'})
do
   hammer partition-table add-operatingsystem --id="${PARTID}" --operatingsystem-id="${i}"
   hammer template add-operatingsystem --id="${PXEID}" --operatingsystem-id="${i}"
   hammer os set-default-template --id="${i}" --config-template-id=${PXEID}
   hammer os add-config-template --id="${i}" --config-template-id=${SATID}
   hammer os set-default-template --id="${i}" --config-template-id=${SATID}
done

Display information about the updated operating system to verify that the operating system is updated correctly:

$ hammer os info --id 1

In the orcharhino management UI, navigate to Hosts > Provisioning Setup > Architectures.

Click Create Architecture.

In the Name field, enter a name for the architecture.

From the Operating Systems list, select an operating system. If none are available, you can create and assign them under Hosts > Provisioning Setup > Operating Systems.

Click Submit.

In the orcharhino management UI, navigate to Hosts > Provisioning Setup > Hardware Models.

Click Create Model.

In the Name field, enter a name for the hardware model.

Optionally, in the Hardware Model and Vendor Class fields, you can enter corresponding information for your system.

In the Info field, enter a description of the hardware model.

Click Submit to save your hardware model.

Add the synchronized Kickstart repository that you want to use to the existing content view, or create a new content view and add the kickstart repository.

Publish a new version of the content view where the Kickstart repository is added and promote it to a required lifecycle environment. For more information, see Managing content views in Managing Content.

When you create a host, in the Operating System tab, for Media Selection, select the Synced Content checkbox.

In the orcharhino management UI, navigate to Hosts > Provisioning Setup > Installation Media.

Click Create Medium.

In the Name field, enter a name to represent the installation media entry.

In the Path enter the URL that contains the installation tree. You can use following variables in the path to represent multiple different system architectures and versions:

From the Operating system family list, select the distribution or family of the installation medium. CentOS belongs to the Red Hat family.

Click the Organizations and Locations tabs, to change the provisioning context. orcharhino Server adds the installation medium to the set provisioning context.

Click Submit to save your installation medium.

In the orcharhino management UI, navigate to Hosts > Templates > Partition Tables.

Click Create Partition Table.

In the Name field, enter a name for the partition table.

Select the Default checkbox if you want to set the template to automatically associate with new organizations or locations.

Select the Snippet checkbox if you want to identify the template as a reusable snippet for other partition tables.

From the Operating System Family list, select the distribution or family of the partitioning layout. CentOS belongs to the Red Hat family.

In the Template editor field, enter the layout for the disk partition. For example:

zerombr
clearpart --all --initlabel
autopart

In the Audit Comment field, add a summary of changes to the partition layout.

Click the Organizations and Locations tabs to add any other provisioning contexts that you want to associate with the partition table. orcharhino adds the partition table to the current provisioning context.

Click Submit to save your partition table.

Before you create a partition table with the CLI, create a plain text file that contains the partition layout. This example uses the ~/My_Partition_Table file.

Create the installation medium using the hammer partition-table create command:

$ hammer partition-table create \
--file "~/My_Partition_Table" \
--locations "My_Location" \
--name "My_Partition_Table" \
--organizations "My_Organization" \
--os-family "Redhat" \
--snippet false

In the orcharhino management UI, navigate to Hosts > Templates > Provisioning Templates and click Create Template.

In the Name field, enter a name for the provisioning template.

Fill in the rest of the fields as required. The Help tab provides information about the template syntax and details the available functions, variables, and methods that can be called on different types of objects within the template.

Before you create a template with the CLI, create a plain text file that contains the template. This example uses the ~/my-template file.

Create the template using the hammer template create command and specify the type with the --type option:

$ hammer template create \
--file ~/my-template \
--locations "My_Location" \
--name "My_Provisioning_Template" \
--organizations "My_Organization" \
--type provision

In the orcharhino management UI, navigate to Hosts > Templates > Provisioning Templates.

Find the template that you want to use.

Click Clone to duplicate the template.

In the Name field, enter a name for the provisioning template.

Select the Default checkbox to set the template to associate automatically with new organizations or locations.

In the Template editor field, enter the body of the provisioning template. You can also use the Template file browser to upload a template file.

In the Audit Comment field, enter a summary of changes to the provisioning template for auditing purposes.

Click the Type tab and if your template is a snippet, select the Snippet checkbox. A snippet is not a standalone provisioning template, but a part of a provisioning template that can be inserted into other provisioning templates.

From the Type list, select the type of the template. For example, Provisioning template.

Click the Association tab and from the Applicable Operating Systems list, select the names of the operating systems that you want to associate with the provisioning template.

Optionally, click Add combination and select a host group from the Host Group list or an environment from the Environment list to associate provisioning template with the host groups and environments.

Click the Organizations and Locations tabs to add any additional contexts to the template.

Click Submit to save your provisioning template.

In the orcharhino management UI, navigate to Hosts > Templates > Provisioning Templates and click Create Template.

In the Name field, enter a name for your custom provisioning snippet. The name has to start with the name of a provisioning template that supports including custom provisioning snippets:

On the Type tab, select Snippet.

Click Submit to create your custom provisioning snippet.

Before you create a template with the CLI, create a plain text file that contains your custom snippet.

Create the template using hammer:

$ hammer template create \
--file "/path/to/My_Snippet" \
--locations "My_Location" \
--name "My_Template_Name_custom_pre" \
--organizations "_My_Organization" \
--type snippet

In the orcharhino management UI, navigate to the host group you are using to provision your host.

Add a parameter with name redhat_install_host_tracer_tools, type boolean, and value true.

In the orcharhino management UI, navigate to the provisioning template you are using to provision your host.

Ensure to reference the snippet to install katello-host-tools-tracer:

<%= snippet 'redhat_register' %>

In the orcharhino management UI, navigate to Monitor > Jobs.

Click Run Job.

In the Job category drop down menu, select Commands.

In the Job template drop down menu, select Run Command - SSH Default.

In the Search Query field, filter your managed hosts, for example all hosts running CentOS:

os = CentOS

In the Command field, enter the command to install the katello-host-tools-tracer package:

$ dnf install -y katello-host-tools-tracer

Click Submit to install the package.

In the orcharhino management UI, navigate to Infrastructure > Compute Profiles and click Create Compute Profile.

In the Name field, enter a name for the profile.

Click Submit. A new window opens with the name of the compute profile.

In the new window, click the name of each compute resource and edit the attributes you want to set for this compute profile.

Create a new compute profile:

$ hammer compute-profile create --name "My_Compute_Profile"

Set attributes for the compute profile:

$ hammer compute-profile values create \
--compute-attributes "flavor=m1.small,cpus=2,memory=4GB,cpu_mode=default \
--compute-resource "My_Compute_Resource" \
--compute-profile "My_Compute_Profile" \
--volume size=40GB

Optional: To update the attributes of a compute profile, specify the attributes you want to change. For example, to change the number of CPUs and memory size:

$ hammer compute-profile values update \
--compute-resource "My_Compute_Resource" \
--compute-profile "My_Compute_Profile" \
--attributes "cpus=2,memory=4GB" \
--interface "type=network,bridge=br1,index=1" \
--volume "size=40GB"

Optional: To change the name of the compute profile, use the --new-name attribute:

$ hammer compute-profile update \
--name "My_Compute_Profile" \
--new-name "My_New_Compute_Profile"

Generate an encrypted password:

$ python3 -c 'import crypt,getpass;pw=getpass.getpass(); print(crypt.crypt(pw)) if (pw==getpass.getpass("Confirm: ")) else exit()'

Copy the password for later use.

In the orcharhino management UI, navigate to Administer > Settings.

On the Settings page, select the Provisioning tab.

In the Name column, navigate to Root password, and click Click to edit.

Paste the encrypted password, and click Save.

On your orcharhino Server, configure the firewall to allow VNC service on ports 5900 to 5930.

$ firewall-cmd --add-port=5900-5930/tcp
$ firewall-cmd --add-port=5900-5930/tcp --permanent

In the orcharhino management UI, navigate to Infrastructure > Compute Resources and select the name of a compute resource.

In the Virtual Machines tab, select the name of your virtual machine. Ensure the machine is powered on and then select Console.