Configuring Ambari with RedHat Satellite or Spacewalk

You can use the following advanced repository option to configure Ambari with RedHat Satellite or Spacewalk.

Use RedHat Satellite/Spacewalk: This option is enabled when you plan to use a Local Repository. When you choose this option for the software repositories, you are responsible for configuring the repository channel in Satellite/Spacewalk and confirming the repositories for the selected stack version are available on the hosts in the cluster.

Using a local RedHat Satellite or Spacewalk Repository

Many Ambari users use RedHat Satellite or Spacewalk to manage Operating System repositories in their cluster. The general process to configure Ambari to work with your Satellite or Spacewalk infrastructure is to:

1. Ensure you have created channels for the public repositories that correspond to the products you intend to use.
2. Ensure the created channels are available on all machines in the cluster.
3. Install the Ambari Server and start it.
4. Before starting a cluster install, update Ambari so it knows not to delegate repository management to Satellite or Spacewalk, and use the appropriate channel names when installing or upgrading packages.

Note Please have the names of your channels on hand before proceeding.

Configuring Ambari to use RedHat Satellite or Spacewalk

The Ambari Server uses Version Definition Files (VDF) to understand which product and component versions are included in a release. For Ambari to work well with Satellite or Spacewalk, you must create a custom VDF file for the specific Operating System versions in your cluster that tells Ambari which RedHat Satellite or Spacewalk channel names to use when installing or upgrading the cluster.

To create a custom VDF file, we recommend downloading an existing VDF from our ODP 3.3.6.2-1 Repositories table to your local desktop. Once downloaded, open the VDF file in your preferred editor and change the tags for each repository to match the Satellite or Spacewalk channel names previously configured. For this example, I’ve created the following channels in Satellite or Spacewalk:

Table 6.1. Example Channel Names for Acceldata Repositories

If LZO compression is going to be used in your cluster, see Configuring LZO Compression for more information.

XML

<repository-info> 

 <os family="redhat8"> 

 <package-version>3_3_6_2_*</package-version> 

 <repo> 

 <baseurl> </baseurl> 

 <repoid>ODP_3.3.6.2-1</repoid> 

 <reponame>ODP</reponame> 

 <unique>true</unique> 

 </repo> 

 <repo> 

 <baseurl> </baseurl> 

 <repoid>ODP_3.3.6.2-1_gpl</repoid> 

 <reponame>ODP-GPL</reponame> 

 <unique>true</unique> 

 <tags> 

 <tag>GPL</tag> 

 </tags> 

 </repo> 

 <repo> 

 <baseurl> </baseurl> 

 <repoid>ODP-UTILS_1.1.0.22</repoid> 

 <reponame>ODP-UTILS</reponame> 

 <unique>false</unique> 

 </repo> 

 </os> 

 </repository-info>