Installing orcharhino Proxy

The documentation refers to orcharhino Server and orcharhino Proxies to describe the machines running orcharhino, for example orcharhino.example.com, and their attached orcharhino Proxies, for example orcharhino-proxy.network2.example.com. Both orcharhino Server and orcharhino Proxy incorporate smart proxy functionality depending on their configuration.

orcharhino Proxies allow you to manage hosts in additional networks. You can configure your orcharhino Proxy to deliver content to managed hosts by either mirroring synchronized content from your orcharhino Server or by streaming content from orcharhino Server as requested by content hosts. Your orcharhino Proxy can also function as DNS, DHCP, and TFTP server and provide CA capabilities.

The term Smart Proxy is used throughout the orcharhino management UI. It describes the smart proxy functionality present on both your orcharhino Server and orcharhino Proxies.

When looking at the upstream documentation for Foreman and Katello, you might come across the terms Smart Proxy, Foreman proxy, or Katello proxy. These terms are used ambiguously to describe the software component or the attached host with smart proxy functionality in different variations. By contrast, Red Hat names their Foreman downstream product Satellite and any attached smart proxies Capsules.

Additionally, there are HTTP proxies as a way of relaying network traffic from one machine to another. They are often part of more advanced internal network architectures.

This guide describes the installation of an orcharhino Proxy to go along with your orcharhino Server. If you want to use orcharhino to manage hosts in additional networks, you need an orcharhino Proxy installed in each network you want to manage. This allows you to orchestrate the process of managing hosts in different networks, that is networks spanning across different data centres and regions.

Your orcharhino Server comes bundled with internal smart proxy functionality. It is sufficient for managing hosts in the same network your orcharhino Server is in.

Usage Scenario

There are different reasons on why to use an orcharhino Proxy:

To manage infrastructure that is not part of the same network as your orcharhino Server.
To manage traffic across firewalls so as to deploy hosts into isolated networks. This helps you simplifying firewall rules and therefore making it more robust, as only the orcharhino Proxy needs to be accessible from outside its network.
To centrally manage infrastructure differentiated by location.
To reduce traffic and latency.

There are two ways on how to deliver content to managed hosts from orcharhino Proxies. An orcharhino Proxy can either mirror the synchronized content from orcharhino Server or relay requested content. This results in a trade-off between storage space and network traffic:

By default, orcharhino Proxies mirror the synchronized content from your orcharhino Server. Synchronized content implies that your orcharhino Proxy has a mirrored version of the content from orcharhino Server stored locally. This results in the need for additional storage capacity analogue to your orcharhino Server. On the other hand, there is significantly less traffic between orcharhino Proxies and your orcharhino Server.
Optionally, you can enable the streamed download policy for your orcharhino Proxy. orcharhino Proxies download content as requested from content hosts without storing it locally. Instead, all content comes directly from your orcharhino Server and is purely relayed to the managed hosts in its network. This results in additional traffic between your orcharhino Server and orcharhino Proxy, but orcharhino Proxies do not need to cache the content locally using up additional disk space. For more information, see Changing the Download Policy for orcharhino Proxies.

Optionally, your orcharhino Proxy can also handle DHCP and DNS for its network.

System and Network Requirements

Your orcharhino Proxy depends on a working orcharhino Server installation. ATIX AG recommends using the same operating system for orcharhino Server as well as orcharhino Proxy itself. subscription-manager needs to be installed on both machines and an activation key needs to be available.

This guide presumes a working orcharhino installation as well as a suitable host for the orcharhino Proxy. Regardless of whether it will run on virtualised hardware or on bare metal, the orcharhino Proxy machine must meet the following requirements:

Minimum Recommended

	Minimum	Recommended
OS	Alma Linux 8, Oracle Linux 8, Red Hat Enterprise Linux 8, or Rocky Linux 8 For more information, see OS requirements.
CPU	4 cores	8 cores
RAM	20 GiB	32 GiB
HDD 1 (`/`)	30 GiB	50 GiB
HDD 2 (`/var`)	~ 40 GiB for each Enterprise Linux distribution ~ 80 GiB for each Debian or Ubuntu distribution	~ 500 GiB (or as appropriate) if you plan to maintain additional repositories or keep multiple versions of packages

Alma Linux 8, Oracle Linux 8, Red Hat Enterprise Linux 8, or Rocky Linux 8

For more information, see OS requirements.

CPU

4 cores

8 cores

RAM

20 GiB

32 GiB

HDD 1 (/)

30 GiB

50 GiB

HDD 2 (/var)

~ 40 GiB for each Enterprise Linux distribution

~ 80 GiB for each Debian or Ubuntu distribution

~ 500 GiB (or as appropriate) if you plan to maintain additional repositories or keep multiple versions of packages

If you use streamed as download policy for your orcharhino Proxy, a second disk for /var can be as small as 10 GiB.

ATIX AG does not support using third party repositories on your orcharhino Server or orcharhino Proxies. Resolving package conflicts or other issues due to third party or custom repositories is not part of your orcharhino support subscription. Please contact us if you have any questions.

Using Multiple DNS Names

If your orcharhino Proxy has different DNS names for orcharhino Server and managed hosts, you have to ensure that hostname -f shows the FQDN towards orcharhino Server. Generate the certificates archive for your orcharhino Proxy on orcharhino Server and specify all FQDNs when creating the certificates using foreman-proxy-certs-generate --foreman-proxy-fqdn My_FQDN_Towards_orcharhino_Server --foreman-proxy-cname My_FQDN_Towards_Managed_Hosts --certs-tar /root/orcharhino-proxy-certs.tar.

On your orcharhino Proxy, ensure that:

hostname -f shows the FQDN towards orcharhino Server.
Add the --foreman-proxy-registration-url parameter to the orcharhino-installer command and set it to the FQDN used by managed hosts.
Use --certs-cname My_FQDN_Towards_Managed_Hosts or modify the foreman-proxy-content-answers.yaml file to add additional cnames.

In addition to the system requirements, your orcharhino Proxy also needs its own domain and subnet, which you can set up in the orcharhino management UI. The network configuration and firewall rules must allow for communication from your orcharhino Server to your orcharhino Proxy and vice versa. For more information, see Ports and Firewalls Requirements for orcharhino Server.

Table 1. Managed Hosts to orcharhino Proxy
Port	Protocol	SSL	Required for
53	TCP & UDP	no	DNS Services
67	UDP	no	DHCP Service
69	UDP	no	PXE boot
80	TCP	no	Anaconda, yum, templates, iPXE
443	TCP	yes	yum, Katello
5000	TCP	yes	Katello for Docker registry
5647	TCP	yes	Deprecated (has been used by Qpid for Katello agent)
8000	TCP	yes	Anaconda for downloading Kickstart templates, iPXE
8140	TCP	yes	Puppet agent to Puppet master
8443	TCP	yes	Subscription Management
9090	TCP	yes	OpenSCAP reports

orcharhino Server and orcharhino Proxy need to be reachable by name. If they are not yet resolvable through DNS, ensure to add them to each others /etc/hosts file as follows. If you are using an HTTP proxy, ensure it is properly configured as well.

This guide uses the network1 (192.168.50.0) for your orcharhino Server (called orcharhino), and network2 (192.168.60.0) for your orcharhino Proxy (called orcharhino-proxy). orcharhino Server is the 192.168.50.10 and orcharhino Proxy the 192.168.60.10 in the default scenario and 192.168.70.10 in network3 when opting for streamed content.

To do so, edit the etc/hosts file on both your orcharhino Server and your orcharhino Proxy and add the following lines:

192.168.50.10 orcharhino.network1.example.com
192.168.60.10 orcharhino-proxy.network2.example.com orcharhino-proxy

In case your orcharhino Server uses an HTTP proxy itself, it is necessary to add your orcharhino Proxy to the no_proxy entries.

Edit the last line in /etc/sysconfig/httpd:

no_proxy='localhost,127.0.0.1,orcharhino.network1.example.com,orcharhino,.network1.example.com,orcharhino-proxy.network2.example.com,.network2.example.com'

Edit the last line in /etc/sysconfig/foreman-proxy:

no_proxy='localhost,127.0.0.1,orcharhino.network1.example.com,orcharhino,.network1.example.com,orcharhino-proxy.network2.example.com,.network2.example.com'

Edit the settings in orcharhino:

To do so, click on Administer > Settings and edit HTTP(S) proxy except hosts:

[ localhost, 127.0.0.1, orcharhino.network1.example.com, orcharhino, *.network1.example.com, orcharhino-proxy.network2.example.com, *.network2.example.com ]

If there are persisting problems, check your networking and firewall settings.

Preparing Content for orcharhino Proxy

There are two ways to configure your orcharhino Proxy: You can either edit foreman-proxy-content-answers.yaml or pass arguments to the orcharhino-installer command.

Your orcharhino Proxy requires the same packages as orcharhino Server. You can get a list of repositories be running subscription-manager repos --list-enabled on your orcharhino Server. Add these repositories to products and publish them as a composite content view. This content must be available on the host you are installing your orcharhino Proxy on.

Alternatively, you can run a script on orcharhino Server to automatically create the necessary content view. It bundles the required repositories and content credentials to a product specifically made for orcharhino Proxies and creates an activation key. The script takes repositories from /etc/yum.repos.d/redhat.repo and reuses HTTP proxy settings.

Ensure that you have the necessary Oracle Linux or Red Hat Enterprise Linux subscription if you want to install orcharhino Proxy on Oracle Linux or Red Hat Enterprise Linux. Your orcharhino subscription does not include any Oracle Linux or Red Hat Enterprise Linux subscriptions. Please contact us if you need help obtaining the relevant subscriptions or have questions on how to use your existing subscriptions.

Procedure

Optional: Change the download policy or mirroring policy for the content for your orcharhino Proxy:
```
# vim /etc/orcharhino-ansible/or_orcharhino_proxy_content_vars.yaml
```

On your orcharhino Server, run the following script:

# /opt/orcharhino/automation/play_orcharhino_proxy_content.sh

Optional: In the orcharhino management UI, navigate to Content > Products and verify that the Smart Proxy Atix product contains the packages required to install orcharhino Proxies.

This section describes the steps necessary to attach an orcharhino Proxy to your orcharhino. It consists of five steps: installing Katello, creating a .tar file containing certificates, copying the certificates to the orcharhino Proxy, installing the orcharhino Proxy, and setting the appropriate organization and location context.

Installing the orcharhino Proxy Packages

Procedure

Enable the dnf modules on your orcharhino Proxy:

# dnf module switch-to ruby:2.7 -y
# dnf module enable pki-core -y
# dnf module enable python36 python38 python39 -y
# subscription-manager repo-override \
--repo ATIX_Smart_Proxy_Atix_ATIX_orcharhino_Server_EL8_orcharhino_6_6 \
--add module_hotfixes:1

Install the orcharhino-proxy meta package to pull in the required dependencies:
```
# dnf install orcharhino-proxy
```

Create a tar file with certificates. In case your organization already has certificates in place, you will need the following four files on your orcharhino:

A private key: proxy.key
A certificate: proxy.cert
A certificate signing request: proxy.csr

The authority’s certificate: proxy.ca

In case you have no certificate signing request, you may create one with the private key and certificate by running the following command:

# openssl x509 -x509toreq -in orcharhino-proxy.cert -out orcharhino-proxy.csr -signkey orcharhino.key

Run the following command to compile the tar file:

# foreman-proxy-certs-generate \
--certs-tar "/root/orcharhino-proxy.network2.example.com-certs.tar" \
--foreman-proxy-fqdn "orcharhino-proxy.network2.example.com" \
--server-ca-cert /root/certs/orcharhino-proxy.ca \
--server-cert /root/certs/orcharhino-proxy.cert \
--server-cert-req /root/certs/orcharhino-proxy.csr \
--server-key /root/certs/orcharhino-proxy.key

In case there are no existing certificates, you can create them by running the following command on your orcharhino:

# foreman-proxy-certs-generate \
--certs-tar "orcharhino-proxy.network2.example.com-certs.tar" \
--foreman-proxy-fqdn "orcharhino-proxy.network2.example.com"

Save the standard output describing how to import certificates. This helps later on when installing the orcharhino Proxy.

Copy the generated certificates from your orcharhino Server to your orcharhino Proxy. This allows for a secure certificate based connection:

# scp /root/orcharhino-proxy.network2.example.com-certs.tar root@orcharhino-proxy.network2.example.com:/root/orcharhino-proxy.network2.example.com-certs.tar

On your orcharhino Server, extract the OAuth token for orcharhino Proxy:

# grep oauth_consumer_ /etc/foreman-installer/scenarios.d/katello-answers.yaml | sort -u

Install orcharhino Proxy with the proper certificates:

# orcharhino-installer \
--certs-tar-file "/root/orcharhino-proxy.network2.example.com-certs.tar" \
--foreman-proxy-foreman-base-url "https://orcharhino.network1.example.com" \
--foreman-proxy-oauth-consumer-key "mGZxEukJVvdL89ySA6Ymk3bAuGSF7jJj" \
--foreman-proxy-oauth-consumer-secret "g2tNnBR7qNHg9Gptt4XMcsFnh9c3kDSg" \
--foreman-proxy-register-in-foreman "true" \
--foreman-proxy-trusted-hosts "orcharhino-proxy.network2.example.com" \
--foreman-proxy-trusted-hosts "orcharhino.network1.example.com" \
--puppet-server-foreman-url "https://orcharhino.network1.example.com" \
--scenario foreman-proxy-content

Set the organization and location context.

To add the organization and location to the orcharhino Proxy, go to Infrastructure > Smart Proxies and select orcharhino-proxy.network2.example.com.

Add Organization: your organization
Add Location: your location
Add Lifecycle Environment: Production

Download Policy: Immediate

One way to distinguish between orcharhino administrators and regular users is to place your orcharhino Server and any attached orcharhino Proxies into a separate location and/or organization context.

Alternatively, you can achieve a fine grained permissions concept using roles and filters.

If you want to manage hosts running Debian or Ubuntu through your orcharhino Proxy, copy the public pulp_deb_signing.key key from orcharhino Server to your orcharhino Proxy:
```
# scp /var/www/html/pub/pulp_deb_signing.key root@orcharhino-proxy.network2.example.com:/var/www/html/pub/pulp_deb_signing.key
```

By now, you have a fully functional orcharhino Proxy. Optionally, you can now activate DHCP and DNS services on your orcharhino Proxy.

Optional: Installing Puppet on orcharhino Proxies

Puppet is an optional plug-in for orcharhino Server and orcharhino Proxies. If you use Puppet to configure hosts, you need to install the Puppet plug-in on your orcharhino Proxies. For more information, see Enabling Puppet Integration with orcharhino.

Optional: Removing Puppet on orcharhino Proxies

Puppet is an optional plug-in for orcharhino Server and orcharhino Proxies. If you do not use Puppet to configure hosts, you can remove the Puppet plug-in from your orcharhino Proxies.

Prerequisite

You can only remove the Puppet plug-in if it is installed on your orcharhino Proxy.

Procedure

Connect to your orcharhino Proxy using SSH:

# ssh root@orcharhino-proxy.network2.example.com

Rerun the orcharhino-installer to disable the Puppet plug-in:

# orcharhino-installer \
--foreman-proxy-puppet false \
--foreman-proxy-puppetca false

Changing the Download Policy for orcharhino Proxies

There are four ways on how orcharhino Proxies handle the download of content from the orcharhino Server.

Immediate: Synchronize content immediately from orcharhino Server onto orcharhino Proxies.
On Demand: Download content at time of request by a managed host onto orcharhino Proxies.
Inherit from Repository: Synchronize content as specified on a per-repository basis onto orcharhino Proxies.
Streamed: Relay content requested by content hosts from orcharhino Server without saving it on orcharhino Proxies.

Procedure

Navigate to Infrastructure > Smart Proxies.
Select an orcharhino Proxy and click Edit.
On the Smart Proxy tab, adjust the Download Policy.
Click Submit to save your changes.

Depending on your setting of Sync Smart Proxies after Content View promotion, content is automatically synchronized to orcharhino Proxies after promoting a content view. Alternatively, you can manually synchronize content from orcharhino Server to orcharhino Proxies:

Procedure

Navigate to Infrastructure > Smart Proxies.
Select your orcharhino Proxy.
On the Overview tab, click Synchronize.
- Select Optimized Sync to bypass any unnecessary synchronization steps.
- Select Complete Sync to synchronize repositories even if the meta data appears to be unchanged.

Optional: Activating DHCP, DNS, and TFTP

ATIX AG recommends having orcharhino Proxies provide DHCP, DNS, and TFTP services on their respective networks.

This subsection describes the steps necessary to activate DHCP, DNS, and TFTP on orcharhino Proxies. You can enable TFTP capabilities on your orcharhino Proxy using the following command:

# orcharhino-installer --foreman-proxy-tftp true

This activates TFTP capabilities on your orcharhino Proxy which is necessary for provisioning hosts using PXE.

To activate DHCP and DNS on your orcharhino Proxy, configure /etc/foreman-installer/scenarios.d/foreman-proxy-content-answers.yaml. Ensure that you active DHCP and DNS simultaneously. This is a sample configuration:

#DHCP:
dhcp: true
dhcp_gateway: 192.168.60.254
dhcp_range: 192.168.60.50 192.168.60.200
dhcp_option_domain: network2.example.com

#DNS:
dns: true
dns_zone: network2.example.com
dns_reverse:
- 60.168.192.in-addr.arpa
dns_forwarder:
- 192.168.50.10

Rerun orcharhino-installer to automatically fetch the configuration from the edited yaml file. After that, you can set up your orcharhino Proxy as DHCP and DNS server for the corresponding subnet and domain.

Navigate to Infrastructure > Domains and select network2.example.com. Select the new orcharhino Proxy orcharhino-proxy.network2.example.com.

On Infrastructure > Subnets, select vlan60 and change the primary DNS to 192.168.60.10 with IPAM to DHCP and Boot Mode to DHCP. Under Proxies, set everything but the last to orcharhino-proxy.network2.example.com.

Optional: Activating Remote Execution via SSH

On orcharhino Server, the remote execution plug-in is installed by default. You can install it on orcharhino Proxies as follows:

Install the plug-in on your orcharhino Proxy:

# orcharhino-installer --enable-foreman-proxy-plugin-remote-execution-script

In the orcharhino management UI, navigate to Infrastructure > Subnets and select the subnet of your orcharhino Proxy.
On the Remove Execution tab, activate the orcharhino Proxy and click the Submit button. You can now schedule remote jobs on hosts in the subnet of your orcharhino Proxy.

Configuring Remote Execution for Pull Client

By default, Remote Execution uses SSH as the transport mechanism for the Script provider. However, Remote Execution also offers pull-based transport, which you can use if your infrastructure prohibits outgoing connections from orcharhino Proxy to hosts.

This is comprised of pull-mqtt mode on orcharhino Proxy in combination with a pull client running on hosts. Configure the pull-mqtt mode to migrate from Katello Agent, which is a deprecated method of pull-based transport.

The pull-mqtt mode works only with the Script provider. Ansible and other providers will continue to use their default transport settings.

The mode is configured per orcharhino Proxy. Some orcharhino Proxies can be configured to use pull-mqtt mode while others use SSH. If this is the case, it is possible that one remote job on a given host will use the pull client and the next job on the same host will use SSH. If you wish to avoid this scenario, configure all orcharhino Proxies to use the same mode.

Procedure

Enable the pull-based transport on each relevant orcharhino Proxy:

 # orcharhino-installer \
--foreman-proxy-plugin-remote-execution-script-mode pull-mqtt

Configure the firewall to allow MQTT service on port 1883:

# firewall-cmd --add-port="1883/tcp"
# firewall-cmd --runtime-to-permanent

In pull-mqtt mode, hosts subscribe for job notifications to the orcharhino Proxy through which they are registered. Therefore, it is recommended to ensure that orcharhino Server sends remote execution jobs to that same orcharhino Proxy. To do this, in the orcharhino management UI, navigate to Administer > Settings. On the Content tab, set the value of Prefer registered through orcharhino Proxy for remote execution to Yes.
After you set up the pull-based transport on orcharhino Proxy, you must also configure it on each host. For more information, see Transport Modes for Remote Execution in Managing Hosts.

Managing DHCP Using orcharhino Proxy

orcharhino can integrate with a DHCP service using your orcharhino Proxy. A orcharhino Proxy has multiple DHCP providers that you can use to integrate orcharhino with your existing DHCP infrastructure or deploy a new one. You can use the DHCP module of orcharhino Proxy to query for available IP addresses, add new, and delete existing reservations. Note that your orcharhino Proxy cannot manage subnet declarations.

Available DHCP providers

dhcp_infoblox – For more information, see Using Infoblox as DHCP and DNS Providers in Provisioning Hosts.
dhcp_isc – ISC DHCP server over OMAPI. For more information, see Configuring DNS, DHCP, and TFTP on orcharhino Proxy in Installing orcharhino Proxy.
dhcp_remote_isc – ISC DHCP server over OMAPI with leases mounted through networking. For more information, see Configuring an External DHCP Server to Use with orcharhino Proxy in Installing orcharhino Proxy.
dhcp_libvirt – dnsmasq DHCP via libvirt API
dhcp_native_ms – Microsoft Active Directory using API

Configuring dhcp_libvirt

The dhcp_libvirt plugin manages IP reservations and leases using dnsmasq through the libvirt API. It uses ruby-libvirt to connect to the local or remote instance of libvirt daemon.

Procedure

You can use orcharhino-installer to configure dhcp_libvirt:

foreman-installer \
--foreman-proxy-dhcp true \
--foreman-proxy-dhcp-provider libvirt \
--foreman-proxy-libvirt-network default \
--foreman-proxy-libvirt-network qemu:///system

dhcp_isc Settings

The dhcp_isc provider uses a combination of the ISC DHCP server OMAPI management interface and parsing of configuration and lease files. This requires it to be run on the same host as the DHCP server. The following settings are defined in dhcp_isc.yml:

Configuring the path to the config and leases files:

:config: /etc/dhcp/dhcpd.conf
:leases: /var/lib/dhcpd/dhcpd.leases

Securing the DHCP server with an omapi_key

:key_name: My_OMAPI_Key
:key_secret: My_Key_Secret

Setting a port on which the DHCP server listens

:omapi_port: My_DHCP_Server_Port  # default: 7911

The server is defined in dhcp.yml:

Setting the host on which the DHCP server runs on

:server: My_DHCP_Server_FQDN

DHCP Options for Network Configuration

--foreman-proxy-dhcp: Enables the DHCP service. You can set this option to true or false.
--foreman-proxy-dhcp-managed: Enables Foreman to manage the DHCP service. You can set this option to true or false.
--foreman-proxy-dhcp-gateway: The DHCP pool gateway. Set this to the address of the external gateway for hosts on your private network.
--foreman-proxy-dhcp-interface: Sets the interface for the DHCP service to listen for requests. Set this to eth1.
--foreman-proxy-dhcp-nameservers: Sets the addresses of the nameservers provided to clients through DHCP. Set this to the address for orcharhino Server on eth1.
--foreman-proxy-dhcp-range: A space-separated DHCP pool range for Discovered and Unmanaged services.
--foreman-proxy-dhcp-server: Sets the address of the DHCP server to manage.
--foreman-proxy-dhcp-subnets: Sets the subnets of the DHCP server to manage. Example: --foreman-proxy-dhcp-subnets 192.168.205.0/255.255.255.128 or --foreman-proxy-dhcp-subnets 192.168.205.128/255.255.255.128

Run orcharhino-installer --help to view more options related to DHCP and other orcharhino Proxy services.

Securing the dhcpd API

orcharhino Proxy interacts with DHCP daemon using the dhcpd API to manage DHCP. By default, the dhcpd API listens to any host without access control. You can add an omapi_key to provide basic security.

Procedure

Install the required packages:
```
# dnf install bind-utils
```

Generate a key:

# dnssec-keygen -r /dev/urandom -a HMAC-MD5 -b 512 -n HOST omapi_key
# cat Komapi_key.+*.private | grep ^Key|cut -d ' ' -f2-

Use orcharhino-installer to secure the dhcpd API:

# orcharhino-installer \
--foreman-proxy-dhcp-key-name "My_Name" \
--foreman-proxy-dhcp-key-secret "My_Secret"

Managing DNS Using orcharhino Proxy

orcharhino can manage DNS records using your orcharhino Proxy. DNS management contains updating and removing DNS records from existing DNS zones. A orcharhino Proxy has multiple DNS providers that you can use to integrate orcharhino with your existing DNS infrastructure or deploy a new one.

After you have enabled DNS, your orcharhino Proxy can manipulate any DNS server that complies with RFC 2136 using the dns_nsupdate provider. Other providers provide more direct integration, such as dns_infoblox for Infoblox.

Available DNS Providers

dns_dnscmd – Static DNS records in Microsoft Active Directory.
dns_infoblox – For more information, see Using Infoblox as DHCP and DNS Providers in Provisioning Hosts.
dns_libvirt – Dnsmasq DNS via libvirt API. For more information, see configuring dns libvirt.
dns_nsupdate – Dynamic DNS update using nsupdate. For more information, see Using Infoblox as DHCP and DNS Providers in Provisioning Hosts.
dns_nsupdate_gss – Dynamic DNS update with GSS-TSIG. For more information, see configuring dynamic dns update with gss tsig authentication.
dns_powerdns – PowerDNS. For more information, see configuring dns powerdns.

Configuring dns_libvirt

The dns_libvirt DNS provider manages DNS records using dnsmasq through the libvirt API. It uses ruby-libvirt gem to connect to the local or a remote instance of libvirt daemon.

Procedure

You can use orcharhino-installer to configure dns_libvirt:

# orcharhino-installer \
--foreman-proxy-dns true \
--foreman-proxy-dns-provider libvirt \
--foreman-proxy-libvirt-network default \
--foreman-proxy-libvirt-url qemu:///system

Note that you can only use one network and URL for both dns_libvirt and dhcp_libvirt.

The text and illustrations on this page are licensed by ATIX AG under a Creative Commons Attribution–Share Alike 3.0 Unported ("CC-BY-SA") license. This page also contains text from the official Foreman documentation which uses the same license ("CC-BY-SA").