Installing IPA on RHEL 7 and utilizing an Active Directory Trust

This document is dependent on the following assumptions:

  • NetBIOS names of the IPA domain and AD domain must be different.
    • In addtion, NetBIOS names of the IPA server and AD DC server must be different.
  • Encoredev.local is the AD domain
    • encoredev1.encoredev.local will host this domain and associated DNS
  • Linux.local is the IPA domain
    • ipa1.linux.local will host this domain and associated DNS records
  • The /etc/hosts file is configured
  • The servers hostname is configured correctly
  • The server┬áhas firewalld disabled or the appropriate firewall ports have been opened.
  • NS1/NS2 =
  • Windows Domain = encoredev.local
  • IPA domain = linux.local
  • Active Directory Linux Admins Group = LinuxAdmins
  • NFS Server = nfs.linux.local
    • nfs.linux.local has been added as an IPA Client

Continue reading “Installing IPA on RHEL 7 and utilizing an Active Directory Trust”

Using Puppet to manage virt-who to map virtual guests to physical hosts in Satellite 6.1

The virt-who package allows you to map virtual machines to the physical host so that you can take advantage of RedHat Virtual Data Center licensing when using Satellite 6.1. It allows you to use your Hypervisor Host (in this case VMware ESXi) as a content host within Satellite. Therefore allowing you to assign RHEL licenses to the hosts directly, rather than individually on the virtual machine.

To do this, I’m going to leverage Puppet. In my puppet manifest I have:
file { '/etc/virt-who.d/vcenter.conf':
ensure => file,
owner => 'root',
mode => 644,
group => 'root',
source => "puppet:///modules/profiles/center"

And on the puppet server in: /etc/puppet/modules/profiles/files/

I have a file called vcenter, it looks like this:

With this configuration, my ESX hosts will show up under Satellite > Hosts > Content Hosts

virt-who content hosts

Here you can see that Satellite now can identify the VM’s then running on the Hypervisor Host