Chapter 2. Administering Hosts

Procedure

1. In the Satellite web UI, click Hosts > Create Host.
2. On the Host tab, enter the required details.
3. Click the Ansible Roles tab, and from the Ansible Roles list, select one or more roles that you want to add to the host. Use the arrow icon to manage the roles that you add or remove.
4. On the Puppet Classes tab, select the Puppet classes you want to include.

5. On the Interfaces tab:

   1. For each interface, click Edit in the Actions column and configure the following settings as required:

      • Type — For a Bond or BMC interface, use the Type list and select the interface type.
      • MAC address — Enter the MAC address.
      • DNS name — Enter the DNS name that is known to the DNS server. This is used for the host part of the FQDN.
      • Domain — Select the domain name of the provisioning network. This automatically updates the Subnet list with a selection of suitable subnets.
      • IPv4 Subnet — Select an IPv4 subnet for the host from the list.
      • IPv6 Subnet — Select an IPv6 subnet for the host from the list.
      • IPv4 address — If IP address management (IPAM) is enabled for the subnet, the IP address is automatically suggested. Alternatively, you can enter an address. The address can be omitted if provisioning tokens are enabled, if the domain does not manage DNS, if the subnet does not manage reverse DNS, or if the subnet does not manage DHCP reservations.
      • IPv6 address — If IP address management (IPAM) is enabled for the subnet, the IP address is automatically suggested. Alternatively, you can enter an address.
      • Managed — Select this checkbox to configure the interface during provisioning to use the Capsule provided DHCP and DNS services.
      • Primary — Select this checkbox to use the DNS name from this interface as the host portion of the FQDN.
      • Provision — Select this checkbox to use this interface for provisioning. This means TFTP boot will take place using this interface, or in case of image based provisioning, the script to complete the provisioning will be executed through this interface. Note that many provisioning tasks, such as downloading packages by anaconda or Puppet setup in a %post script, will use the primary interface.

      • Virtual NIC — Select this checkbox if this interface is not a physical device. This setting has two options:

        • Tag — Optionally set a VLAN tag. If unset, the tag will be the VLAN ID of the subnet.
        • Attached to — Enter the device name of the interface this virtual interface is attached to.
   2. Click OK to save the interface configuration.
   3. Optionally, click Add Interface to include an additional network interface. For more information, see Chapter 5, Adding Network Interfaces.
   4. Click Submit to apply the changes and exit.
6. On the Operating System tab, enter the required details. For Red Hat operating systems, select Synced Content for Media Selection. If you want to use non Red Hat operating systems, select All Media, then select the installation media from the Media Selection list. You can select a partition table from the list or enter a custom partition table in the Custom partition table field. You cannot specify both.

7. On the Parameters tab, click Add Parameter to add any parameter variables that you want to pass to job templates at run time. This includes all Puppet Class, Ansible playbook parameters and host parameters that you want to associate with the host. To use a parameter variable with an Ansible job template, you must add a Host Parameter.

   When you create a Red Hat Enterprise Linux 8 host, you can set system purpose attributes. System purpose attributes define what subscriptions to attach automatically on host creation. In the Host Parameters area, enter the following parameter names with the corresponding values. For the list of values, see Configuring System Purpose using the subscription-manager command-line tool in Automatically installing RHEL 8.

   • syspurpose_role
   • syspurpose_sla
   • syspurpose_usage
   • syspurpose_addons

   If you want to create a host with pull mode for remote job execution, add the enable-remote-execution-pull parameter with type boolean set to true. For more information, see Section 12.4, “Transport Modes for Remote Execution”.

8. On the Additional Information tab, enter additional information about the host.
9. Click Submit to complete your provisioning request.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. In the Actions menu, click Clone.
3. On the Host tab, ensure to provide a Name different from the original host.
4. On the Interfaces tab, ensure to provide a different IP address.
5. Click Submit to clone the host.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources.
2. Select a compute resource.
3. On the Virtual Machines tab, click Associate VM from the Actions menu.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click the name of the host you want to modify.
3. On the Overview tab, click Edit on the System purpose card.
4. Select the system purpose attributes for your host.
5. Click Save.

CLI procedure

1. Log in to the host and edit the required system purpose attributes. For example, set the usage type to Production, the role to Red Hat Enterprise Linux Server, and add the addon add on. For the list of values, see Configuring System Purpose using the subscription-manager command-line tool in Automatically installing RHEL 8.

   # subscription-manager syspurpose set usage 'Production'
   # subscription-manager syspurpose set role 'Red Hat Enterprise Linux Server'
   # subscription-manager syspurpose add addons 'your_addon'

2. Verify the system purpose attributes for this host:

   # subscription-manager syspurpose

3. Automatically attach subscriptions to this host:

   # subscription-manager attach --auto

4. Verify the system purpose status for this host:

   # subscription-manager status

Procedure

1. In the Satellite web UI, navigate to Hosts > Content Hosts and select Red Hat Enterprise Linux 8 hosts that you want to edit.
2. Click the Select Action list and select Manage System Purpose.

3. Select the system purpose attributes that you want to assign to the selected hosts. You can select one of the following values:

   • A specific attribute to set an all selected hosts.
   • No Change to keep the attribute set on the selected hosts.
   • None (Clear) to clear the attribute on the selected hosts.
4. Click Assign.
5. In the Satellite web UI, navigate to Hosts > Content Hosts and select the same Red Hat Enterprise Linux 8 hosts to automatically attach subscriptions based on the system purpose.
6. Click the Select Action list and select Manage Subscriptions.
7. Click Auto-Attach to attach subscriptions to all selected hosts automatically based on their system role.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click the name of the host you want to modify.
3. Click the Content tab, then click the Module streams tab.
4. Click the vertical ellipsis next to the module and select the action you want to perform. You get a REX job notification once the remote execution job is complete.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts and select a host.
2. Select the Content tab, then select Repository sets.
3. From the dropdown, you can filter the Repository type column to Custom.
4. Select the desired number of repositories or click the Select All checkbox to select all repositories, then click the vertical ellipsis, and select Override to Enabled.

Procedure

1. In the Satellite web UI, navigate to Configure > Host Groups and click Create Host Group.
2. If you have an existing host group that you want to inherit attributes from, you can select a host group from the Parent list. If you do not, leave this field blank.
3. Enter a Name for the new host group.
4. Enter any further information that you want future hosts to inherit.
5. Click the Ansible Roles tab, and from the Ansible Roles list, select one or more roles that you want to add to the host. Use the arrow icon to manage the roles that you add or remove.

6. Click the additional tabs and add any details that you want to attribute to the host group.

   Note

   Puppet fails to retrieve the Puppet CA certificate while registering a host with a host group associated with a Puppet environment created inside a Production environment.

   To create a suitable Puppet environment to be associated with a host group, manually create a directory:

   # mkdir /etc/puppetlabs/code/environments/example_environment

7. Click Submit to save the host group.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click the name of the host you want to modify.
3. Click Edit.
4. Select the host group from the Host Group list.
5. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click the name of the host you want to modify.
3. Click Edit.
4. Select the new host group from the Host Group list.
5. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click the name of the host you want to modify.
3. In the Host collections card, click the vertical ellipsis and select Add host to collections.
4. Select the host collection.
5. Click Add.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click the name of the host you want to modify.
3. Click the vertical ellipsis icon next to the Edit button and select Change content source.
4. Select Content Source, Lifecycle Content View, and Content Source from the lists.

5. Click Change content source.

   Note

   Some lifecycle environments can be unavailable for selection if they are not synced on the selected content source. For more information, see Adding Lifecycle Environments to Capsule Servers in Managing Content.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click the name of the host you want to modify.
3. Click the vertical ellipsis in the Content view details card and select Edit content view assignment.
4. Select the environment.
5. Select the content view.
6. Click Save.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click the name of the host you want to modify.
3. Click Edit.
4. Click Manage host or Unmanage host to change the host’s status.
5. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click the name of the host you want to modify.
3. On the Traces tab, click Enable Traces.
4. Select the provider to install katello-host-tools-tracer from the list.
5. Click Enable Tracer. You get a REX job notification after the remote execution job is complete.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click the name of the hosts you want to modify.
3. Select the Traces tab.
4. Select applications that you want to restart.
5. Select Restart via remote execution from the Restart app list. You will get a REX job notification once the remote execution job is complete.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Select the checkbox of the host you want to change.
3. From the Select Action list, select Assign Organization. A new option window opens.

4. From the Select Organization list, select the organization that you want to assign your host to. Select the checkbox Fix Organization on Mismatch.

   Note

   A mismatch happens if there is a resource associated with a host, such as a domain or subnet, and at the same time not associated with the organization you want to assign the host to. The option Fix Organization on Mismatch will add such a resource to the organization, and is therefore the recommended choice. The option Fail on Mismatch will always result in an error message. For example, reassigning a host from one organization to another will fail, even if there is no actual mismatch in settings.

5. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Select the checkbox of the host you want to change.
3. From the Select Action list, select Assign Location. A new option window opens.

4. Navigate to the Select Location list and choose the location that you want for your host. Select the checkbox Fix Location on Mismatch.

   Note

   A mismatch happens if there is a resource associated with a host, such as a domain or subnet, and at the same time not associated with the location you want to assign the host to. The option Fix Location on Mismatch will add such a resource to the location, and is therefore the recommended choice. The option Fail on Mismatch will always result in an error message. For example, reassigning a host from one location to another will fail, even if there is no actual mismatch in settings.

5. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Hosts > Content Hosts
2. Click the content host you want to view.
3. Select the Details tab to see the host details page.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click Manage columns.

3. Select columns that you want to display. You can select individual columns or column categories. Selecting or deselecting a category selects or deselects all columns in that category.

   Note

   Some columns are included in more than one category, but you can display a column of a specific type only once. By selecting or deselecting a specific column, you select or deselect all instances of that column.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts or Hosts > Content Hosts. Note that there is no difference from what page you remove a host, from All Hosts or Content Hosts. In both cases, Satellite removes a host completely.
2. Select the hosts that you want to remove.
3. From the Select Action list, select Delete Hosts.
4. Click Submit to remove the host from Satellite permanently.