User Guide

Procedure 3.1. Creating an Organization

1. Click the Administer → Organizations menu on the top right hand corner.
2. Click the New Organization button.
3. Type in the name of the new organization in the Name field.
4. Type in the label of the new organization in the Label field.
5. Type in a description of the new organization in the Description field.
6. Click the Submit button.
7. Select the hosts to assign to the new organization.
   • Click the Assign All button to assign all hosts with no organization to the new organization.
   • Click the Manually Assign button to manually select and assign the hosts with no organization.
   • Click the Proceed to Edit button to skip assigning hosts.

Procedure 3.2. Creating a New Organization Debug Certificate

1. Click the Administer → Organizations menu on the upper right corner.
2. Select an existing organization from the list on the left.
3. Click the Generate and Download button. This generates a debug certificate. Save the certificate in a secure location.

Procedure 3.3. Editing an Organization

1. Click the Administer → Organizations menu on the top right hand corner.
2. Click the name of the organization to be edited.
3. Select the resource to edit from the list on the left.
4. Click the name of the desired items to add them to the Selected Items list.
5. Click the Submit button.

Procedure 3.4. Removing an Organization

1. Click the Administer → Organizations menu on the top right hand corner.
2. Select Delete from the drop down menu to the right of the name of the organization you want to remove.
3. An alert box appears:

   Delete Organization Name?

4. Click the OK button.

Procedure 3.5. Creating a Location

1. Click the Administer → Locations menu on the top right hand corner.
2. Click the New Location button.
3. Type in the name of the new location in the Name field and click the Submit button.
4. Select the hosts to assign to the new location.
   • Click the Assign All button to assign all hosts with no location to the new location.
   • Click the Manually Assign button to manually select and assign the hosts with no location.
   • Click the Proceed to Edit button to skip assigning hosts.

Procedure 3.6. Editing a Location

1. Click the Administer → Locations menu on the top right hand corner.
2. Click the name of the location to be edited.
3. Select the resource to edit from the list on the left.
4. Click the name of the desired items to add them to the Selected Items list.
5. Click the Submit button.

Procedure 3.7. Removing a Location

1. Click the Administer → Locations menu on the top right hand corner.
2. Select Delete from the drop down menu to the right of the name of the location you want to remove.
   An alert box appears:

   Delete Location Name

3. Click the OK button.

Procedure 3.8. To Create a Life Cycle Environment:

1. On the main menu, click Content → Life Cycle Environments and then click New Environment Path.
2. Enter a name and label for the life cycle environment. The Description field is optional.
3. Click Save to create the environment.

Procedure 3.9. To Promote a Content View:

1. On the main menu, click Content → Content Views.
2. In the Name column, click the name of the content view that you want to promote.
3. On the Versions tab, identify the latest version, and click Promote.
4. Identify the promotion path where you want to promote the content view, select the appropriate life cycle environment, and click Promote Version.

   Note

   You can only promote content views to the next environment in the promotion path. You cannot skip environments.
5. After the promotion has completed, the Versions tab updates to display the new status of your content views.

Procedure 3.10. To Remove a Life Cycle Environment:

1. On the main menu, click Content → Life Cycle Environments.
2. Click the name of the life cycle environment that you want to remove, and then click Remove Environment.
3. In the confirmation dialog box, click Remove to remove the environment.

Procedure 4.11. To Configure a Host to Synchronize and Export Content from the Red Hat CDN:

1. Use Red Hat Subscription Manager to register the synchronization host to RHN.
2. List all the available subscriptions to find the correct Red Hat Satellite product to allocate to your system:

   # subscription-manager list --available --all

   This command displays output similar to the following:

   +-------------------------------------------+
       Available Subscriptions
   +-------------------------------------------+
   
   
   ProductName:        Red Hat Satellite
   ProductId:          SKU123456
   PoolId:             e1730d1f4eaa448397bfd30c8c7f3d334bd8b
   Quantity:           10
   Multi-Entitlement:  No
   Expires:            08/20/2013
   MachineType:        physical
   

   Note

   The SKU and Pool ID depend on the Red Hat Satellite product type that corresponds to your system version and product type.
3. Subscribe to the pool using the following command:

   # subscription-manager subscribe --pool=Red_Hat_Satellite_Pool_Id
   # subscription-manager subscribe --pool=Red_Hat_Enterprise_Linux_Pool_Id
   # subscription-manager subscribe --pool=Red_Hat_Enterprise_Linux_Software_Collections_Pool_Id
   

4. Disable all existing repositories:

   # subscription-manager repos --disable "*"
   

5. Enable the Red Hat Satellite and Red Hat Enterprise Linux and Red Hat Software Collections repositories. Ensure the Red Hat Enterprise Linux repository matches the specific version you are using.

   # subscription-manager repos --enable rhel-6-server-rpms \
   --enable rhel-server-rhscl-6-rpms \
   --enable rhel-6-server-satellite-6.0-rpms
   

   Note

   The commands above are based on Red Hat Enterprise Linux 6. If you are using a different version of Red Hat Enterprise Linux, change the repository based on your specific version.
6. Install katello-utils and associated RPMs:

   # yum install python-qpid-qmf python-qpid  qpid-cpp-server katello-utils
   

   katello-utils includes the katello-disconnected utility that is required to set up repositories for import while qpid related packages are necessary for pulp configuration.
7. Generate a secret 32-character alphanumeric string for the oauth_secret entry in the /etc/pulp/server.conf file:

   # tr -dc "[:alnum:]" < /dev/urandom | head -c 32
   randomly_generated_value

8. In the /etc/pulp/server.conf, uncomment the [oauth] entry and add the randomly generated value from the previous step as the oauth_secret value:

   [oauth]
   enabled: true
   oauth_key: katello
   oauth_secret: randomly_generated_value

9. Disable authentication in /etc/qpid/qpidd.conf:

   # Configuration file for qpidd. Entries are of the form:
   #   name=value
   #
   # (Note: no spaces on either side of '=').
   # Run "qpidd --help" or see "man qpidd" for more details.
   
   auth=no
   

   All incoming connections authenticate using the Satellite's default realm.
10. Configure the connection from katello-disconnected to Pulp with the previously generated value as your --oauth-secret option:

    # katello-disconnected setup --oauth-key=katello --oauth-secret=randomly_generated_value

    This places a configuration value in ~/.katello-disconnected.
11. Configure Pulp on the Synchronization Server:

    sudo service qpidd start
    sudo chkconfig qpidd on
    sudo service mongod start
    sleep 10
    sudo chkconfig mongod on
    sudo -u apache pulp-manage-db
    sudo service httpd restart
    sudo chkconfig pulp_workers on
    sudo service pulp_workers start
    sudo chkconfig pulp_celerybeat on
    sudo service pulp_celerybeat start
    sudo chkconfig pulp_resource_manager on
    sudo service pulp_resource_manager start
    

12. Import the manifest:

    # katello-disconnected import -m ./manifest.zip
    

    Importing the manifest sets up the list of available repositories to synchronize to based on the subscriptions you selected.

1. Disable all repositories:

   # katello-disconnected disable --all
   

   katello-disconnected enables all repositories by default.
2. Choose which repositories you wish to sync by listing all available repositories from the manifest:

   # katello-disconnected list --disabled
   rhel-5-server-debug-rpms-5Server-i386
   rhel-5-server-debug-rpms-5Server-ia64
   rhel-5-server-debug-rpms-5Server-x86_64
   rhel-5-server-debug-rpms-5_7-i386
   rhel-5-server-debug-rpms-5_7-ia64
   rhel-5-server-debug-rpms-5_7-x86_64
   rhel-5-server-debug-rpms-5_8-i386
   rhel-5-server-debug-rpms-5_8-ia64
   rhel-5-server-debug-rpms-5_8-x86_64
   rhel-5-server-debug-rpms-5_9-i386
   rhel-5-server-debug-rpms-5_9-ia64
   rhel-5-server-debug-rpms-5_9-x86_64
   rhel-5-server-isos-5Server-i386
   

3. Enable the chosen repositories for synchronization:

   # katello-disconnected enable -r rhel-6-server-sam-rpms-6_4-x86_64
   

4. Create the repositories and push them to Pulp to allow synchronization:

   # katello-disconnected configure
   

   Note

   The configure option for katello-disconnected reads the manifest, creates pulp repositories, and generates scripts before synchronization. It needs to be run each time a repository is enabled or disabled.
5. Synchronize the repositories:

   # katello-disconnected sync
   

   You can use the watch option to monitor the synchronization process.

   # katello-disconnected watch
   Watching sync... (this may be safely interrupted with Ctrl+C)
   running:
   rhel-6-server-sam-rpms-6_4-x86_64 
   
   running:
   rhel-6-server-sam-rpms-6_4-x86_64 
   ...
   finished:
   rhel-6-server-sam-rpms-6_4-x86_64 
   
   
   Watching finished
   

1. Export the synchronized repositories:

   # katello-disconnected export -t /var/tmp/export
   

   The output will look similar to:

   
   # katello-disconnected export -t /var/tmp/export
   # katello-disconnected watch
   Watching sync... (this may be safely interrupted with Ctrl+C)
   running:
   rhel-6-server-sam-rpms-6_4-x86_64
   
   finished:
   rhel-6-server-sam-rpms-6_4-x86_64
   Watching finished
   Done watching ...
    Copying content to /var/tmp/export
    Archiving contents of /var/tmp/export into 4600M tar archives.
    NOTE: This may take a while.
   tar: Removing leading `/' from member names
   
   Done exporting content, please copy /var/tmp/export/* to your disconnected host
   

   This operation will create the following files in /var/tmp/export:

   # ls /var/tmp/export/
   content-export-00 content-export-01 content-export-02 expand_export.sh
   

2. Copy the files from /var/tmp/export into the external media.

   Note

   If the files are too big for your external media, the files can be copied sequentially in a series of DVDs.

1. Copy ALL of the Satellite Content ISOs to a directory that the Satellite can access. This example uses /root/isos.
2. Create a local directory that will be shared via httpd on the Satellite. This example uses /var/www.html/sat-import/.

   # mkdir -p /var/www/html/sat-import/
   

3. Recursively copy the contents of the first ISO to the local directory:

   # mount -o loop /root/isos/first iso /mnt/iso
   # cp -ruv /mnt/iso/* /var/www/html/sat-import/
   # umount /mnt/iso
   

4. Repeat the above step for each ISO until you have copied all the data from the series of ISOs into the local directory /var/www/html/sat-import/.
5. Ensure that the SELinux contexts is correct:

   # restorecon -rv /var/www/html/sat-import/
   

6. Change the CDN URL to reference the loaction that the ISOs were copied to. This example uses the Satellite fully qualified domain name (FQDN) server.example.com, so the URL is:

   http //server.example.com/sat-import/
   

   Note

   The Satellite is now acting as its own CDN with the files located in http://localhost/content. This is not a requirement. The CDN can be hosted on a different machine inside the same disconnected network as long as it is accessible to the Satellite server via HTTP.
7. Add the CDN address to the Satellite web interface:
   1. Log in to the Satellite web interface.
   2. Click Content → Red Hat Subscriptions and then click Manage Manifest.
   3. On the Subscription Manifest information screen, scroll to Red Hat Provider Details. Click the edit icon on the Repository URL entry and change the entry to the CDN's repository URL.
   4. Click Browse to choose the manifest file.
   5. Click Upload to import your manifest.
8. Enable the repositories from the local CDN:
   1. Click Content → Red Hat Repositories
   2. Enable the repositories that were enabled and synchronized in the Synchronizing Content section.
9. Click Content → Sync Status.
10. Select the repositories you want to synchronize and click Synchronize Now.

Procedure 5.1. Creating a Filter

1. Click Content → Content Views.
2. Select the Content View you wish to filter.
3. Click the Content → Filters subtab.
4. Click on the +New Filter button.
5. Type in the name of the new filter in the Name field.
6. Choose a content type from the Content Type drop down menu.
7. Choose whether the filter includes or excludes the selected content type by selecting the Type drop down menu.
8. Optionally, enter a description in the Description field.
9. Click the Save button to save your new filter.

1. Click Content → Content Views.
2. Select the Content View you wish to filter.
3. Click the Content → Filters subtab.
4. Click a created package filter's name. Depending on the type of filter selected, the readout will be different.
   1. If the filter is made for Packages:
      1. Enter a package name and select a Detail value from the dropdown menu. Click +Add to add the package to the filter.
      2. Under the Affected Repositories subtab, choose whether the filter will affect all or a subset of repositories. If you choose a subset of repositories, then choose the desired repositories and click Update Repositories.
   2. If the filter is made for package groups:
      1. Click on the Add subtab, and choose the desired package group. Click the +Add Package Group button.
      2. Under the Affected Repositories subtab, choose whether the filter will affect all or a subset of repositories. If you choose a subset of repositories, then choose the desired repositories and click the Update Repositories button.
   3. If the filter is made for Errata:
      1. Click on the Add subtab. Check the desired boxes for the Errata type, whether is be Security, Enhancement, or Bugfix. Then choose a start date and end date. Click the +Add Errata button.
      2. Under the Affected Repositories subtab, choose whether the filter will affect all or a subset of repositories. If you choose a subset of repositories, then choose the desired repositories and click the Update Repositories button.
   4. If the filter is made for Errata - Date and Type:
      1. Under the Erratum Date Range subtab, check the desired boxes for the Errata type, whether is be Security, Enhancement, or Bugfix. Then choose a start date and end date. Click the Save button.
      2. Under the Affected Repositories subtab, choose whether the filter will affect all or a subset of repositories. If you choose a subset of repositories, then choose the desired repositories and click the Update Repositories button.
5. Click the Publish New Version button. Enter a comment if desired, then click the Save button.

1. Click Content → Content Views.
2. Select the Content View you wish to filter.
3. Click the Content → Filters subtab.
4. Click a created package filter's name. Depending on the type of filter selected, the readout will be different.
   1. If the filter is made for Packages:
      1. Click the Packages subtab then click the Package Name checkbox next to the package to remove. Click the Remove Packages button to remove the package from the filter.
      2. Under the Affected Repositories subtab, choose whether the filter will affect all or a subset of repositories. If you choose a subset of repositories, then choose the desired repositories and click the Update Repositories button.
   2. If the filter is made for package groups:
      1. Click the List/Remove subtab then click the Name checkbox next to the package group to remove. Click the Remove Package Group button to remove the package group from the filter.
      2. Under the Affected Repositories subtab, choose whether the filter will affect all or a subset of repositories. If you choose a subset of repositories, then choose the desired repositories and click the Update Repositories button.
   3. If the filter is made for Errata:
      1. Click the List/Remove subtab then click the Errata ID checkbox next to the errata to remove. Click the Remove Errata button to remove the errata from the filter.
      2. Under the Affected Repositories subtab, choose whether the filter will affect all or a subset of repositories. If you choose a subset of repositories, then choose the desired repositories and click the Update Repositories button.
   4. If the filter is made for Errata - Date and Type:
      1. Under the Erratum Date Range subtab, check the desired boxes for the Errata type, whether is be Security, Enhancement, or Bugfix. Then edit the start date and end date. Click the Save button.
      2. Under the Affected Repositories subtab, choose whether the filter will affect all or a subset of repositories. If you choose a subset of repositories, then choose the desired repositories and click the Update Repositories button.
5. Click the Publish New Version button. Enter a comment if desired, then click the Save button.

Procedure 5.2. Remove a Filter

1. Click Content → Content Views.
2. Select the Content View you wish to filter.
3. Click the Content → Filters subtab.
4. Click the checkbox next to the name of the package filter you wish to remove.
5. Click the Remove Filters button.

Procedure 8.1. Creating a Container

1. Navigate to Containers → New Container. Alternatively, navigate to Containers → All Containers and click New container.
2. In the Preliminary stage of container creation configure the following settings:
   • On the Compute resource tab, select the compute resource from the Deployed on drop-down menu. See Section 11.3.4, “Compute Resources” for more information on compute resources.
   • On the Locations tab, select the locations where the new container will be available.
   • On the Organizations tab, select the organizations where the new container will be available.
   Click Next to proceed.
3. In the Image stage of container creation import an image that will act as a base for your container. This can be a platform image, or a previously created layered image. Select from one of the following options:
   • Select the Satellite tab to import an image from a life cycle environment. Specify the life cycle environment, content view, repository, tag, and Capsule Server.
   • Select the Docker hub tab to import an image from the Docker Hub registry. Once you type an image name to the Search field, Satellite automatically searches the compute resource first. Click the looking glass icon to search the Docker Hub. If the image is found, Satellite displays the image metadata and populates the Tag field with tags available for the selected image name.
   • Select the External registry tab to import an image from an existing registry. Select the registry from the drop-down menu, and search it by the image name. Satellite populates the Tag field with tags available for the selected image name. See Section 8.3, “Adding an External Registry” for details.
   Click Next to proceed.
4. In the Configuration stage of container creation set the following parameters:
   • Select a name for the container.
   • Specify a command to run inside the container.
   • Specify an entrypoint, which is a command that is executed automatically as soon as the container starts. The default entrypoint is /bin/sh -c.
   • Assign CPUs to the container. For example, 0-2,16 represents CPUs 0, 1, 2, and 16.
   • Define the relative share of CPU time for the container.
   • Specify a memory limit for the container. For example, 512m limits the container memory usage to 512 MB.
   Click Next to proceed.
5. In the final stage of container creation named Environment, select if you want to allocate a pseudo-tty, attach STDIN, STDOUT, and STDERR to the container. Click Add environment variable to create a custom environment variable for the container.
6. Click Submit to create the container.

Procedure 8.2. Investigating a Container

1. Navigate to Containers → All Containers.
2. On the Containers page, every Docker compute resource has a dedicated tab. Each of these tabs contains the table of available containers together with selected parameters of each container. Select the tab of the compute resource you want to inspect.
3. To view the container metadata, click the name of the container you want to inspect. Satellite displays the table of container properties.
4. On the Processes tab, you can view processes that are currently running in the container. Click on the process name to view the metadata of the process.
5. If the container is running, you can view its standard output in the Logs tab. If you selected the allocate a pseudo-tty check box when creating a container, the console is interactive. Otherwise, it displays only the initial standard output produced when the container started.

Procedure 8.3. Starting and Stopping a Container

1. Navigate to Containers → All Containers to view the list of available containers.
2. Click Power On next to the container you want to start. After starting the container, the button changes to Power Off, which allows for stopping the container. These actions are equivalent to the docker start and docker stop commands.

Procedure 8.4. Committing a Container

1. Navigate to Containers → All Containers to view the list of available containers.
2. Click the name of the container you want to commit.
3. Click Commit. Satellite then prompts you to provide the following information:
   • Specify a repository name. This can be a single name or combined with the user name, for example user/my-rhel-image.
   • Assign a tag to the image.
   • Provide your contact information.
   • Provide an informative comment about the image.
4. Click Submit.

Procedure 8.5. Removing a Container

1. Navigate to Containers → All Containers to view the list of available containers.
2. Click the name of the container you want to delete.
3. Click Delete.
4. In the alert box, click OK to remove the container.

Procedure 8.6. Uploading Images to a Repository

1. Navigate to Content → Products
2. Select the product that contains the repository you want to update.
3. Navigate to the Repositories tab and select the docker repository you want to update.
4. Click Browse.
5. Navigate to the location of the image you want to upload. Click Open.
6. Click Upload

Procedure 9.3. To Add a Subscription to an Activation Key:

1. Click Content → Activation Keys.
2. Click the name of the activation key that you want to add subscriptions to.
3. Click Subscriptions → Add.
4. From the list of available subscriptions, select the subscriptions you want to add and then click Add Selected.

Procedure 9.4. To Add Host Collections to an Activation Key:

1. Click Content → Activation Keys.
2. Click the activation key that you want to add a host collection to.
3. Click Host Collections and then click Add to display the list of available host collections.
4. Select the host collections you want to add, and then click Add Selected to add the host collections to the activation key.

Procedure 9.5. Remove Subscriptions from an Activation Key

1. Click Content → Activation Keys.
2. A list of activation keys is displayed. Click the activation key you wish to remove subscriptions from.
3. Click the Subscriptions subtab.
4. A list of subscriptions is displayed. Select the subscriptions you wish to remove.
5. Click the Remove Selected button to remove subscriptions from the activation key.

Procedure 9.6. Remove Host Collections from the Activation Key

1. Click Content → Activation Keys.
2. A list of activation keys is displayed. Click the activation key you wish to remove host collections from.
3. Click the Host Collections subtab.
4. A list of host collections attached to the Activation Key is displayed. Tick the checkbox of the host collections you wish to remove.
5. Click the Remove Selected button to remove host collections from the activation key.

1. Click Configure → Global Parameters.
2. Click the New Parameter button.
3. Type a Name for the parameter's key.
4. Type a Value for the parameter.
5. Click the Submit button.

1. Click Configure → Puppet Classes.
2. Click the New Puppet class button.
3. Type a Name for the Puppet Class.
4. Type a Puppet Environments for the Puppet Class.
5. Select one or more Host groups that own the Puppet Class.
6. Click Submit.

Procedure 11.2. To configure smart parameters

1. Click Configure → Puppet Classes.
2. Select a class from the list.
3. Click the Smart Variables tab. This displays a new screen. The left section contains a list of possible parameters the class supports. The right section contains the configuration options for the parameter selected. Click the Add Variable to add a new parameter. Otherwise, select a parameter from the left-hand list.
4. Type a name for the Parameter field.
5. Edit the Description text box to add any plain text notes.
6. Select the Parameter type of data to pass. This is most commonly a string, but other data types are supported.
7. Type a Default Value for the parameter.
8. Use the Optional Input Validator section to restrict the allowed values for the parameter. Choose a Validator type (either a list of comma separated values or a regular expression, regexp) and input the allows values or regular expression code in the Validator rule field.
9. The Override Value For Specific Hosts section at the bottom of the page provides options for overriding values based upon conditional arguments known as Matchers. Define the Order that the host values resolve, then click Add Matcher-Value to add your conditional argument.
   For example, if desired value of the parameter is test for any host with a fully qualified domain name of www.example.com, then specify the Match as fqdn=www.example.com and the Value as test.
10. Click Submit to save your changes.

Procedure 11.3. To import parameterized classes

1. Click Configure → Puppet Classes.
2. Click Import from Host Name to import parameterized classes from your Puppet Master.
3. The Puppet Classes page displays with the new classes listed.

Procedure 11.4. To configure parameterized classes

1. Click Configure → Puppet Classes.
2. Select a class from the list.
3. Click the Smart Class Parameter tab. This displays a new screen. The left section contains a list of possible parameters the class supports. The right section contains the configuration options for the parameter selected.
4. Select the a parameter from the left-hand list.
5. Edit the Description text box to add any plain text notes.
6. Click the Override checkbox to allow Satellite control over this variable. If the checkbox is not selected, Satellite does not pass this variable to Puppet.
7. Select the Parameter type of data to pass. This is most commonly a string, but other data types are supported.
8. Type a Default Value for the parameter.
9. The Override Value For Specific Hosts section at the bottom of the page provides options for overriding values based upon conditional arguments known as Matchers. Define the Order that the host values resolve, then click Add Matcher-Value to add your conditional argument.
   For example, if desired value of the parameter is test for any host with a fully qualified domain name of www.example.com, then specify the Match as fqdn=www.example.com and the Value as test.
10. Click Submit to save your changes.

1. Take note of the Red Hat Satellite hostname or the fully qualified domain name (fqdn).
2. Open a terminal console and login as root on the command line.
3. Download and install a copy of the CA Certificate for Red Hat Satellite:

   yum -y --nogpgcheck install http://[hostname]/pub/katello-ca-consumer-latest.noarch.rpm
   

   Important

   yum in Red Hat Enterprise Linux 5 does not support installation via HTTP. If registering a Red Hat Enterprise Linux 5 client, download the RPM package first and then run yum on the package. For example:

   # wget http://[hostname]/pub/katello-ca-consumer-latest.noarch.rpm
   # yum -y --nogpgcheck install katello-ca-consumer-latest.noarch.rpm
   

   Note

   katello-ca-consumer-[hostname]-1.0-1.noarch.rpm is an additional katello-ca-consumer rpm available that contains the server's hostname. The katello-ca-consumer-latest.noarch.rpm rpm will always reflect the most updated version. Both serve the same purpose.

1. Make the following changes in /etc/rhsm/rhsm.conf:

   [server]
   hostname =[satellite_fqdn]
   
   
   [rhsm]
   baseurl=https://[fqdn_pulp]/pulp/repos/
   repo_ca_cert = %(ca_cert_dir)scandlepin-local.pem
   ca_cert_dir = /etc/rhsm/ca/
   

2. Change directories to the ca directory, remote copy and move the candlepin-ca.crt certificate:

   # cd /etc/rhsm/ca
   scp  [satellite.fqdn]:/etc/candlepin/certs/candlepin-ca.crt .
   mv candlepin-ca.crt candlepin-local.pem
   

Procedure 12.2. Adding a Physical Interface

1. Navigate to Hosts → All hosts to view available hosts.
2. Click Edit next to the host you want to edit.
3. On the Network tab, click Add Interface.
4. Keep the Interface option selected in the Type menu.
5. Specify a MAC address of the additional interface. This setting is required.
6. Specify the device Identifier, for example eth0 or eth1.1. Identifier is used for bonded interfaces (in the Attached devices field, see Procedure 12.4, “Adding a Bonded Interface”), VLANs and aliases (in the Attached to field, see Procedure 12.3, “Adding a Virtual Interface”).
7. Specify the DNS name associated with the host's IP address. Satellite saves this name in the "DNS A" and "DNS PTR" fields in the Capsule Server associated with the selected subnet. A single host can therefore have several DNS entries.
8. Select a domain from the Domain drop-down menu. To create and manage domains, navigate to Infrastructure → Domains.
9. Select a subnet from the Subnet drop-down menu. To create and manage subnets, navigate to Infrastructure → Subnets.
10. Specify the interface IP address. Managed interfaces with assigned DHCP Capsule Server require this setting for creating a DHCP lease. DHCP-enabled managed interfaces provide an automatic suggestion of IP address.
11. Decide if the interface will be managed. If the Managed check box is selected, the interface configuration is pulled from the associated Capsule Server during provisioning, and DNS and DHCP entries are created.
12. Select the Virtual NIC check box to create a virtual interface. See Section 12.4.2, “Adding a Virtual Interface” for details.
13. Click OK to save the interface configuration, and then click Submit to apply the changes to the host.

Procedure 12.3. Adding a Virtual Interface

1. Navigate to Hosts → All hosts to view available hosts.
2. Click Edit next to the host you want to edit.
3. On the Network tab, click Add Interface.
4. Keep the Interface option selected in the Type menu.
5. Specify the general interface settings. The applicable configuration options are the same as for the physical interfaces described in Section 12.4.1, “Adding a Physical Interface”. Specify MAC address for managed virtual interfaces so that the configuration files for provisioning are generated correctly. However, MAC address is not required for virtual interfaces that are not managed. If creating a VLAN, specify ID in the form of eth1.10 in the Identifier field. If creating an alias, use ID in the form of eth1:10.
6. Select the Virtual NIC check box. Additional configuration options specific to virtual interfaces are appended to the form:
   • Tag: You can specify tags per interface to provide a higher-level segmentation of the network. If left blank, managed interfaces inherit the tag form the VLAN ID of the associated subnet, given that this subnet has the VLAN ID specified. User-specified entries from this field are not applied on alias interfaces.
   • Attached to: Specify the identifier of the physical interface to which the virtual interface belongs, for example eth1. This setting is required.
7. Click OK to save the interface configuration. Then click Submit to apply the changes to the host.

Procedure 12.4. Adding a Bonded Interface

1. Navigate to Hosts → All hosts to view available hosts.
2. Click Edit next to the host you want to edit.
3. On the Network tab, click Add Interface.
4. Select Bond from the Type menu. Additional type-specific configuration options are appended to the form.
5. Specify the general interface settings. The applicable configuration options are the same as for the physical interfaces described in Section 12.4.1, “Adding a Physical Interface”. Bonded interfaces use IDs in the form of bond0 in the Identifier field. It is sufficient if you specify just a single MAC address in the MAC address field.
6. Specify the configuration options specific to bonded interfaces:
   • Mode: Select the bonding mode that defines a policy for fault tolerance and load balancing. See Table 12.1, “Bonding Modes Available in Red Hat Satellite” for a brief description of individual bonding modes.
   • Attached devices: Specify a comma separated list of identifiers of attached devices. These can be physical interfaces or VLANs.
   • Bond options: Specify a space separated list of configuration options, for example miimon=100. There are several configuration options you can specify for the bonded interface, see Red Hat Enterprise Linux 7 Networking Guide for details.
7. Click OK to save the interface configuration. Then click Submit to apply the changes to the host.

Procedure 12.5. Adding a BMC Interface

1. Navigate to Hosts → All hosts to view available hosts.
2. Click Edit next to the host you want to edit.
3. On the Network tab, click Add Interface.
4. Select BMC from the Type menu. Type-specific configuration options are appended to the form.
5. Specify the general interface settings. The applicable configuration options are the same as for the physical interfaces described in Section 12.4.1, “Adding a Physical Interface”.
6. Specify the configuration options specific to BMC interfaces:
   • Username, Password: Here you can specify authentication credentials required by BMC.
   • Provider: Specify the BMC provider, currently the only supported provider is the Intelligent Platform Management Interface (IPMI).
7. Click OK to save the interface configuration. Then click Submit to apply the changes to the host.

Procedure 12.6. Registering Systems

1. Open a terminal console and login as root on the command line.
2. Clear old system data in preparation for registering. This makes sure that your updated system data is uploaded correctly.

   subscription-manager clean
   

3. Register the system using the Red Hat Subscription Manager (RHSM):

   # subscription-manager register --org [your_org_name] --activationkey [your_activation_key]
   

   Note

   Activation keys will allow you to add environments, provisioning templates and dictate what subscriptions are available and should be applied to the registering system.

   There are various options that may be added. For more information, use the command man subscription-manager.

1. Open a terminal console and log in as root on the command line.
2. Install the katello-agent using the following command:

   # yum install katello-agent
   

Procedure 12.7. Installing and Enabling the Puppet Agent

1. Open a terminal console and log in as root.
2. Install the Puppet agent:

   # yum install puppet
   

3. Configure the puppet agent to start at boot:
   • On Red Hat Enterprise Linux 6:

     # chkconfig puppet on

   • On Red Hat Enterprise Linux 7:

     # systemctl enable puppet

Procedure 12.8. Configuring the Puppet Agent

1. Configure the Puppet agent by changing the /etc/puppet/puppet.conf file:

   # vi /etc/puppet/puppet.conf
   

   [main]
       # The Puppet log directory.
       # The default value is '$vardir/log'.
       logdir = /var/log/puppet
   
       # Where Puppet PID files are kept.
       # The default value is '$vardir/run'.
       rundir = /var/run/puppet
   
       # Where SSL certificates are kept.
       # The default value is '$confdir/ssl'.
       ssldir = $vardir/ssl
   
   [agent]
       # The file in which puppetd stores a list of the classes
       # associated with the retrieved configuratiion.  Can be loaded in
       # the separate ``puppet`` executable using the ``--loadclasses``
       # option.
       # The default value is '$confdir/classes.txt'.
       classfile = $vardir/classes.txt
       pluginsync = true
       report = true
       ignoreschedules = true
       daemon = false
       ca_server = satellite.example.com
       server = satellite.example.com
   
       # Where puppetd caches the local configuration.  An
       # extension indicating the cache format is added automatically.
       # The default value is '$confdir/localconfig'.
       localconfig = $vardir/localconfig
   

2. Run the Puppet agent on the host:

   # puppet agent -t --server satellite.example.com

3. Sign the SSL certificate for the puppet client through the Satellite Server web interface:
   1. Log in to the Satellite Server through the web interface.
   2. Select Infrastructure → Capsules.
   3. Click Certificates to the right of the required host.
   4. Click Sign.

Procedure 14.3. Adding Packages to Host Collections

1. Click Hosts → Host Collections.
2. Click the host collection where the package should be added.
3. Click the Collection Actions subtab.
4. Click the Package Installation, Removal, and Updates link.
5. In the field provided, type in the package or package group name. Then click:
   • Install ‐ if you wish to install a new package
   • Update ‐ if you wish to update an existing package in the host collection

Procedure 14.4. Adding Errata to Host Collections

1. Click Hosts → Host Collections.
2. Choose the host collection where the errata should be added.
3. Click the Collection Actions subtab.
4. Click the Errata Installation link.
5. Choose the errata you wish to push to the host collection and click Install Selected.

Procedure 15.2. To Enable BMC Power Management on an Existing Capsule:

1. Add the following lines to the /etc/foreman-proxy/settings.d/bmc.yml file. Create the file if necessary.

   :enabled: true
   :bmc_default_provider: your_bmc_provider

2. Restart the foreman-proxy service:

   # service foreman-proxy restart

3. Refresh the features for the Capsule.
   1. Log in to the Satellite web UI, and navigate to Infrastructure → Capsules.
   2. Identify the Capsule whose features you need to refresh. In the drop-down list on the right, click Refresh features. The list of features in the Features column should now include BMC.

Procedure 16.2. To Create a User:

1. Navigate to Administer → Users and then click New User.
2. Enter the required details on the User tab.
3. On the Locations tab, select the required locations for this user.
4. On the Organizations tab, select the required organizations for this user.
5. On the Roles tab, select the required roles for this user. Active roles are displayed in the right panel.
6. Click Submit to create the user.

Procedure 16.3. To Edit an Existing User:

1. Navigate to Administer → Users.
2. Click the user name of the user to be altered. General information about the user will appear on the right.
3. You can modify the user's username, first name, surname, email address, default location, default organization, language, and password in the User tab.
4. You can modify the user's assigned locations in the Locations tab.
5. You can modify the user's assigned organizations in the Organizations tab. If no organization is selected, the user can access all available organizations.
6. You can modify the user's assigned roles in the Roles tab.
7. Click Save to save your changes.

Procedure 16.4. To Assign a Role to a User:

1. Navigate to Administer → Users.
2. Click the user name of the user that you want to modify. General information about the user appears on the right.
3. Click the Roles tab to display the list of available role assignments.
4. Select role you want to assign to the user in the Roles list. The list contains the predefined roles, as well as any custom roles, see Table 16.1, “Predefined Roles Available in Red Hat Satellite”. Alternatively, select the Administrator check box to assign all available permissions to the selected user.
5. Click Save.

Procedure 16.5. To Remove a User:

1. On the main menu, click Administer → Users to open the Users page.
2. Click the Delete link to the right of the username you want to delete.
3. In the alert box, click OK to delete the user.

Procedure 16.6. To Create a Role:

1. Navigate to Administer → Roles.
2. Click New Role.
3. Provide a Name for the role.
4. Click Submit to save your new role.

Procedure 16.7. To Add Permissions to a Role:

1. Navigate to Administer → Roles.
2. Select Add Permission from the drop-down list to the right of the required role.
3. Select the Resource type from the drop-down list. The (Miscellaneous) group gathers permissions that are not associated with any resource group.
4. Click the permissions you want to select from the Permission list.
5. Select whether the permission is Unlimited. This option is selected by default, which means that the permission is applied on all resources of the selected type. When you disable the Unlimited check box, the Search field activates. In this field you can specify further filtering with use of the Red Hat Satellite 6 search syntax. See Section 16.4, “Granular Permission Filtering” for details.
6. Click Next.
7. Click Submit to save changes.

Procedure 16.8. To View Permissions of a Role:

1. Navigate to Administer → Roles.
2. Click Filters to the right of the required role to get to the Filters page.

Procedure 16.9. To Remove a Role:

1. Navigate to Administer → Roles.
2. Select Delete from the drop-down list to the right of the role to be deleted.
3. In an alert box that appears, click OK to delete the role.

Procedure 19.1. Viewing Import History

1. Click Content → Red Hat Subscriptions.
2. Click the Manage Manifest button.
3. Click the Import History tab.

Procedure 19.2. Updating Your Red Hat Satellite Configuration After an FQDN Change

1. Verify that the FQDN is being properly repored and reflects the hostname/FQDN:

   # facter fqdn

2. Update the katello-installer answer file to replace the old FQDN with the new one:

   # sed -i "s/$OLD_FQDN/$NEW_FQDN/g" /etc/katello-installer/answers.katello-installer.yaml
   

   Where:
   1. $OLD_is the Satellite Server's previous FQDN.
   2. $NEW_FQDN is the Satellite Server's new FDQN.
3. Delete the amqp-client certificate from the NSS database:

   # certutil -D -d '/etc/pki/katello/nssdb' -n 'amqp-client'
   

4. Regenerate the server certificates by running katello-installer:

   # katello-installer --certs-update-all
   

5. On client systems registered to the Red Hat Satellite Server, uninstall the existing katello-ca-consumer package since it contains the existing SSL certificate with the old FQDN information and update the package from the new FQDN:

   # rpm -e $(rpm -qa "katello-ca-consumer*")
   #rpm -Uvh http://NEW_FQDN/pub/katello-ca-consumer-latest.noarch.rpm