The Ambari Server uses Version Definition Files (VDF) to understand which product and component versions are included in a release. In order 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 the our HDP 3.1.5 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 Hortonworks Repositories

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

<repository-info>
    <os family="redhat7">
      <package-version>3_0_0_0_*</package-version>
      <repo>
 <baseurl>http://public-repo-1.hortonworks.com/HDP/centos7/3.x/updates/3.1.5.6091</baseurl>
        <repoid>hdp_3.1.5.6091</repoid>
        <reponame>HDP</reponame>
        <unique>true</unique>
      </repo>
      <repo>
 <baseurl>http://public-repo-1.hortonworks.com/HDP-GPL/centos7/3.x/updates/3.1.5.6091</baseurl>
        <repoid>hdp_3.1_gpl</repoid>
        <reponame>HDP-GPL</reponame>
        <unique>true</unique>
        <tags>
          <tag>GPL</tag>
        </tags>
      </repo>
      <repo>
 <baseurl>http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.22/repos/centos7</baseurl>
        <repoid>hdp_utils_1.1.0.22</repoid>
        <reponame>HDP-UTILS</reponame>
        <unique>false</unique>
      </repo>
    </os>
  </repository-info>

Next Step

Import the custom VDF into Ambari