Red Hat Satellite-6.4-Installing Satellite Server From A Connected Network-en-US
Red Hat Satellite-6.4-Installing Satellite Server From A Connected Network-en-US
Red Hat Satellite-6.4-Installing Satellite Server From A Connected Network-en-US
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons
Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is
available at
http://creativecommons.org/licenses/by-sa/3.0/
. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must
provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert,
Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity
logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other
countries.
Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.
XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States
and/or other countries.
MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and
other countries.
Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to
or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks
or trademarks/service marks of the OpenStack Foundation, in the United States and other countries
and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or
sponsored by the OpenStack Foundation, or the OpenStack community.
Abstract
This guide describes how to install Red Hat Satellite from a connected network, perform initial
configuration, and configure external services.
Table of Contents
Table of Contents
.CHAPTER
. . . . . . . . .1.. .PREPARING
. . . . . . . . . . .YOUR
. . . . . .ENVIRONMENT
. . . . . . . . . . . . . .FOR
. . . .INSTALLATION
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . .
1.1. SYSTEM REQUIREMENTS 4
1.2. STORAGE REQUIREMENTS AND GUIDELINES 5
1.2.1. Storage Requirements 5
1.2.2. Storage Guidelines 6
1.3. SUPPORTED OPERATING SYSTEMS 7
1.4. SUPPORTED BROWSERS 7
1.5. PORTS AND FIREWALLS REQUIREMENTS 8
1.6. ENABLING CONNECTIONS FROM A CLIENT TO SATELLITE SERVER 11
1.7. VERIFYING FIREWALL SETTINGS 11
1.8. VERIFYING DNS RESOLUTION 11
1.9. CHANGING DEFAULT SELINUX PORTS 12
.CHAPTER
. . . . . . . . .2.. .INSTALLING
. . . . . . . . . . . SATELLITE
. . . . . . . . . . SERVER
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
...........
2.1. INSTALLING SATELLITE SERVER FROM A CONNECTED NETWORK 14
2.1.1. Registering to Red Hat Subscription Management 15
2.1.2. Identifying and Attaching the Satellite Subscription to the Host 15
2.1.3. Configuring Repositories 17
2.1.4. Installing the Satellite Server Packages 17
2.1.5. Downloading and Installing Packages Manually 18
2.2. PERFORMING THE INITIAL CONFIGURATION 18
2.2.1. Synchronizing Time 19
2.2.2. Installing the SOS Package on the Host Operating System 19
2.2.3. Specifying Installation Options 19
2.2.3.1. Performing the Initial Configuration Manually 20
2.2.3.2. Performing the Initial Configuration Automatically using an Answer File 21
2.2.4. Creating a Subscription Allocation in Customer Portal 21
2.2.5. Adding Subscriptions to an Allocation 22
2.2.6. Exporting a Subscription Manifest from the Customer Portal 22
2.2.6.1. Importing a Subscription Manifest into the Satellite Server 22
.CHAPTER
. . . . . . . . .3.. .PERFORMING
. . . . . . . . . . . . ADDITIONAL
. . . . . . . . . . . . CONFIGURATION
. . . . . . . . . . . . . . . .ON
. . . SATELLITE
. . . . . . . . . . SERVER
. . . . . . . . . . . . . . . . . . . . . . . . . . .24
...........
3.1. INSTALLING THE SATELLITE TOOLS REPOSITORY 24
3.2. CONFIGURING SATELLITE SERVER WITH AN HTTP PROXY 25
3.3. USING AN HTTP PROXY FOR ALL SATELLITE HTTP REQUESTS 26
3.4. ENABLING POWER MANAGEMENT ON MANAGED HOSTS 27
3.5. CONFIGURING DNS, DHCP, AND TFTP ON SATELLITE SERVER 27
3.6. DISABLING DNS, DHCP, AND TFTP FOR UNMANAGED NETWORKS 29
3.7. CONFIGURING SATELLITE SERVER FOR OUTGOING EMAILS 30
3.8. CONFIGURING SATELLITE SERVER WITH A CUSTOM SERVER CERTIFICATE 32
3.8.1. Obtain an SSL Certificate for the Satellite Server 32
3.8.2. Validate the Satellite Server’s SSL Certificate 34
3.8.3. Run the Satellite Installer with Custom Certificate Parameters 35
3.8.4. Install the New Certificate on all Hosts Connected to the Satellite Server 36
3.9. USING EXTERNAL DATABASES WITH SATELLITE 36
3.9.1. MongoDB as an External Database Considerations 37
3.9.2. PostgreSQL as an External Database Considerations 37
3.9.3. Overview 38
3.9.4. Installing MongoDB 38
3.9.5. Installing PostgreSQL 39
3.10. RESTRICTING ACCESS TO MONGOD 41
1
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
.CHAPTER
. . . . . . . . .4.. .CONFIGURING
. . . . . . . . . . . . . EXTERNAL
. . . . . . . . . . SERVICES
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
...........
4.1. CONFIGURING SATELLITE WITH EXTERNAL DNS 43
4.2. VERIFYING AND STARTING THE DNS SERVICE 45
4.3. CONFIGURING SATELLITE SERVER WITH EXTERNAL DHCP 45
4.4. CONFIGURING SATELLITE SERVER WITH EXTERNAL TFTP 49
4.4.1. Configuring the Firewall for External Access to TFTP 50
4.5. CONFIGURING SATELLITE OR CAPSULE WITH EXTERNAL IDM DNS 50
4.5.1. Configuring Dynamic DNS Update with GSS-TSIG Authentication 51
4.5.2. Configuring Dynamic DNS Update with TSIG Authentication 55
4.5.3. Reverting to Internal DNS Service 57
. . . . . . . . . .5.. .UNINSTALLING
CHAPTER . . . . . . . . . . . . . .SATELLITE
. . . . . . . . . .SERVER
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
...........
.CHAPTER
. . . . . . . . .6.. .RUNNING
. . . . . . . . .RED
. . . .HAT
. . . . SATELLITE
. . . . . . . . . . .ON
. . .AMAZON
. . . . . . . . WEB
. . . . .SERVICES
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
...........
6.1. USE CASE CONSIDERATIONS 60
6.1.1. Use Cases Known to Work 60
6.1.2. Use Cases that Do Not Work 61
6.2. DEPLOYMENT SCENARIOS 61
6.3. PREREQUISITES 64
6.3.1. Amazon Web Service Assumptions 64
6.3.2. Red Hat Cloud prerequisites 65
6.3.3. Red Hat Satellite-specific prerequisites 65
6.3.4. Preparing for the Red Hat Satellite Installation 65
6.4. INSTALLING SATELLITE SERVER ON AWS 66
6.5. INSTALLING CAPSULE ON AWS 66
6.6. REGISTERING HOSTS TO SATELLITE USING THE BOOTSTRAP SCRIPT 66
. . . . . . . . . . A.
APPENDIX . . .LARGE
. . . . . . DEPLOYMENT
. . . . . . . . . . . . . CONSIDERATIONS
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
...........
. . . . . . . . . . B.
APPENDIX . . .APPLYING
. . . . . . . . . CUSTOM
. . . . . . . . .CONFIGURATION
. . . . . . . . . . . . . . . TO
. . . RED
. . . . .HAT
. . . .SATELLITE
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
...........
B.1. HOW TO RESTORE MANUAL CHANGES OVERWRITTEN BY A PUPPET RUN 71
2
Table of Contents
3
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
64-bit architecture
A unique host name, which can contain lower-case letters, numbers, dots (.) and hyphens (-)
Full forward and reverse DNS resolution using a fully-qualified domain name
Before you install Satellite Server or Capsule Server, ensure that your environment meets the
requirements for installation.
Satellite Server must be installed on a freshly provisioned system that serves no other function except to
run Satellite Server.
NOTE
The Red Hat Satellite Server and Capsule Server versions must match. For example, a
Satellite 6.2 Server cannot run a 6.4 Capsule Server and a Satellite 6.4 Server cannot run
a 6.2 Capsule Server. Mismatching Satellite Server and Capsule Server versions results in
the Capsule Server failing silently.
NOTE
If you have a large number of content hosts, see Large Deployment Considerations to ensure that your
environment is set up appropriately.
For more information on scaling your Capsule Servers, see Capsule Server Scalability Considerations.
Certified hypervisors
Red Hat Satellite is fully supported on both physical systems and virtual machines that run on
hypervisors that are supported to run Red Hat Enterprise Linux. For more information about certified
hypervisors, see Which hypervisors are certified to run Red Hat Enterprise Linux?
4
CHAPTER 1. PREPARING YOUR ENVIRONMENT FOR INSTALLATION
In the following two tables, the runtime size was measured with Red Hat Enterprise Linux 5, 6, and 7
repositories synchronized.
/var/cache/pulp/ 1 MB 20 GB
/var/lib/pulp/ 1 MB 500 GB
/var/lib/mongodb/ 3.5 GB 50 GB
/var/log/ 10 MB 250 MB
/var/lib/pgsql/ 100 MB 10 GB
/var/spool/squid/ 0 MB 10 GB
/var/cache/pulp/ 1 MB 20 GB (Minimum)
/var/lib/pulp/ 1 MB 500 GB
5
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
/var/lib/mongodb/ 3.5 GB 50 GB
Because most Satellite and Capsule Server data is stored within the /var directory, mounting
/var on LVM storage can help the system to scale.
The /var/lib/qpidd/ directory uses slightly more than 2 MB per Content Host managed by
the goferd service. For example, 10 000 Content Hosts require 20 GB of disk space in
/var/lib/qpidd/.
Using the same volume for the /var/cache/pulp/ and /var/lib/pulp/ directories can
decrease the time required to move content from /var/cache/pulp/ to /var/lib/pulp/
after synchronizing.
Use the XFS file system for Red Hat Satellite 6 because it does not have the inode limitations
that ext4 does. Because Satellite uses a lot of symbolic links it is likely that your system might
run out of inodes if using ext4 and the default number of inodes.
Do not use NFS with MongoDB because MongoDB does not use conventional I/O to access
data files and performance problems occur when both the data files and the journal files are
hosted on NFS. If required to use NFS, mount the volume with the following options in the
/etc/fstab file: bg, nolock, and noatime.
Do not use the GFS2 file system as the input-output latency is too high.
If NFS share is already mounted, remount it using the above configuration and enter the following
command:
6
CHAPTER 1. PREPARING YOUR ENVIRONMENT FOR INSTALLATION
Duplicated Packages
Packages that are duplicated in different repositories are only stored once on the disk. Additional
repositories containing duplicate packages require less additional storage. The bulk of storage resides in
the /var/lib/mongodb/ and /var/lib/pulp/ directories. These end points are not manually
configurable. Ensure that storage is available on the /var file system to prevent storage problems.
Temporary Storage
The /var/cache/pulp/ directory is used to temporarily store content while it is being synchronized.
For content in RPM format, a maximum of 5 RPM files are stored in this directory at any time. After each
file is synchronized, it is moved to the /var/lib/pulp/ directory. Up to 8 RPM content synchronization
tasks can run simultaneously by default, with each using up to 1 GB of metadata.
Software Collections
Software collections are installed in the /opt/rh/ and /opt/theforeman/ directories.
Write and execute permissions by the root user are required for installation to the /opt directory.
Symbolic links
You cannot use symbolic links for /var/lib/pulp/ and /var/lib/mongodb/,
Red Hat Satellite Server and Red Hat Satellite Capsule Server require Red Hat Enterprise Linux
installations with the @Base package group with no other package-set modifications, and without third-
party configurations or software not directly necessary for the direct operation of the server. This
restriction includes hardening and other non-Red Hat security software. If you require such software in
your infrastructure, install and verify a complete working Satellite Server first, then create a backup of the
system before adding any non-Red Hat software.
It is recommended that the Satellite Server be a freshly provisioned system. It is also recommended that
Capsule Servers be freshly provisioned systems and not registered to the Red Hat CDN. Using the
system for anything other than running Satellite is not supported.
If any of the following exist on the system, they must be removed before installation:
Additional yum repositories other than those explicitly required in this guide for installation
7
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
The following web browsers are partially supported. The Satellite web UI interface functions correctly but
certain design elements may not align as expected:
Firefox version 38
Chrome version 27
NOTE
The web UI and command-line interface for Satellite Server supports English, Portuguese,
Simplified Chinese, Traditional Chinese, Korean, Japanese, Italian, Spanish, Russian,
French, and German.
The following tables indicate the destination port and the direction of network traffic. Use this information
to configure any network-based firewalls. Note that some cloud solutions must be specifically configured
to allow communications between machines because they isolate machines similarly to network-based
firewalls. If you use an application-based firewall, ensure that the application-based firewall permits all
applications that are listed in the tables and known to your firewall. If possible, disable the application
checking and allow open port communication based on the protocol.
Integrated Capsule
Satellite Server has an integrated Capsule and any host that is directly connected to Satellite Server is a
Client of Satellite in the context of these tables. This includes the base system on which a Capsule
Server is running.
Clients of Capsule
Hosts which are clients of Capsules, other than Satellite’s integrated Capsule, do not need access to
Satellite Server. For more information on Satellite Topology, see Capsule Networking in Planning for Red
Hat Satellite 6.
Except in the case of a disconnected Satellite, Satellite Server needs access to the Red Hat CDN. For a
list of IP addresses used by the Red Hat CDN (cdn.redhat.com), see the Knowledgebase article Public
CIDR Lists for Red Hat on the Red Hat Customer Portal.
8
CHAPTER 1. PREPARING YOUR ENVIRONMENT FOR INSTALLATION
9
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
Any managed host that is directly connected to Satellite Server is a client in this context because it is a
client of the integrated Capsule. This includes the base system on which a Capsule Server is running.
10
CHAPTER 1. PREPARING YOUR ENVIRONMENT FOR INSTALLATION
Use this section to configure the host-based firewall on the Red Hat Enterprise Linux 7 system that
Satellite is installed on, to enable incoming connections from Clients, and to make the configuration
persistent across system reboots. For more information on the ports used, see Section 1.5, “Ports and
Firewalls Requirements”.
1. To open the ports for Client to Satellite communication, enter the following command on the base
system that you want to install Satellite on:
# firewall-cmd \
--add-port="53/udp" --add-port="53/tcp" \
--add-port="67/udp" --add-port="69/udp" \
--add-port="80/tcp" --add-port="443/tcp" \
--add-port="5000/tcp" --add-port="5647/tcp" \
--add-port="8000/tcp" --add-port="8140/tcp" \
--add-port="9090/tcp"
# firewall-cmd --runtime-to-permanent
# firewall-cmd --list-all
For more information, see Getting Started with firewalld in the Red Hat Enterprise Linux 7 Security Guide.
Ensure that the host name and local host resolve correctly.
11
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
To avoid discrepancies with static and transient host names, set all the host names on the system by
entering the following command:
For more information, see the Configuring Host Names Using hostnamectl in the Red Hat Enterprise
Linux 7 Networking Guide.
WARNING
For example, if you change the Satellite web UI ports (HTTP/HTTPS) to 8018/8019, you need to add
these port numbers to the httpd_port_t SELinux port type.
This change is also required for target ports. For example, when Satellite 6 connects to an external
source, like Red Hat Virtualization or Red Hat OpenStack Platform.
You only need to make changes to default port assignments once. Updating or upgrading Satellite has
no effect on these assignments. Updating only adds default SELinux ports if no assignments exist.
SELinux must be enabled and running in permissive or enforcing mode before installing
Satellite. For more information, see the Red Hat Enterprise Linux 7 SELinux User’s and
Administrator’s Guide.
12
CHAPTER 1. PREPARING YOUR ENVIRONMENT FOR INSTALLATION
1. To change the port from the default port to a user-specified port, execute the commands using
values that are relevant to your environment. These examples use port 99999 for demonstration
purposes.
5000 on Red Hat Enterprise Linux 7 semanage port -a -t commplex_main_port_t -p tcp 99999
13
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
Red Hat Satellite 6.4 uses Puppet 5 by default. Review and update your Puppet modules to support
Puppet 5. For more information about updating your Puppet modules to support Puppet 5, see the
Upgrading Puppet section in the Satellite 6.4 Upgrading and Updating Red Hat Satellite guide.
NOTE
Ensure you have completed upgrading your Puppet modules to support Puppet 4 while
on Red Hat Satellite 6.3. For information on upgrading Puppet modules to Puppet 4, see
the Upgrading Puppet section in the Satellite 6.3 Upgrading and Updating Red Hat
Satellite guide.
Connected:
You can obtain the packages required to install Satellite Server directly from the Red Hat Content
Delivery Network (CDN). Using the CDN ensures that your system always receives the latest updates.
Disconnected:
You must use an external computer to download an ISO image of the packages and copy the packages
to the system you want to install Satellite Server on. Use an ISO image only if you require a
disconnected environment. The ISO image might not contain the latest updates.
NOTE
Note that the Satellite 6 installation script is based on Puppet, which means that if you run the installation
script more than once, it might overwrite any manual configuration changes. To avoid this and
determine which future changes apply, use the --noop argument when you run the installation script.
This argument ensures that no actual changes are made. Potential changes are written to
/var/log/katello-installer.log.
Files are always backed up and so you can revert any unwanted changes. For example, in the katello-
installer logs, you can see an entry similar to the following about Filebucket:
/Stage[main]/Dhcp/File[/etc/dhcp/dhcpd.conf]: Filebucketed
/etc/dhcp/dhcpd.conf to puppet with sum 622d9820b8e764ab124367c68f5fa3a1
14
CHAPTER 2. INSTALLING SATELLITE SERVER
# puppet filebucket -l \
restore /etc/dhcp/dhcpd.conf 622d9820b8e764ab124367c68f5fa3a1
Register your system with the Red Hat Content Delivery Network, entering your Customer Portal user
name and password when prompted:
# subscription-manager register
# subscription-manager register
Username: user_name
Password:
The system has been registered with ID: 541084ff2-44cab-4eb1-9fa1-
7683431bcf9a
This command performs a case-insensitive search of all available subscriptions' fields, including
Subscription Name and Provides, matching any instances of Red Hat Satellite.
Subscriptions are classified as available if they are not already attached to a system. The search
string may also contain the wildcards ? or * to match a single character or zero or more
characters, respectively. The wildcard characters may be escaped with a backslash to represent
a literal question mark or asterisk. Likewise, to represent a backslash, it must be escaped with
another backslash.
If you are unable to find an available Satellite subscription, see the Red Hat Knowledgebase
solution How do I figure out which subscriptions have been consumed by clients registered
under Red Hat Subscription Manager? to run a script to allow you to see if your subscription is
being consumed by another system.
If the output is too long, pipe it into a pager utility, such as less or more, so that you can look
over the output one screenful at a time.
15
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
2. Make a note of the Pool ID so that you can attach it to your Satellite host. Your Pool ID is
different than the example provided.
3. To attach your subscription to your Satellite Server, enter the following command, using your
Pool ID:
4. To verify that the subscriptions are successfully attached, enter the following command:
+-------------------------------------------+
Consumed Subscriptions
+-------------------------------------------+
Subscription Name: Red Hat Satellite
Provides: Red Hat Satellite
Red Hat Enterprise Linux Server
Red Hat Software Collections (for RHEL Server)
Red Hat Satellite
Red Hat Satellite 6
Red Hat Software Collections (for RHEL Server)
Red Hat Satellite Capsule
Red Hat Enterprise Linux Load Balancer (for RHEL
Server)
Red Hat Satellite with Embedded Oracle
Red Hat Satellite Capsule
Red Hat Enterprise Linux High Availability (for
RHEL Server)
SKU: MCT0370
Contract: 10293569
Account: 5361051
16
CHAPTER 2. INSTALLING SATELLITE SERVER
Serial: 1653856191250699363
Pool ID: 8a85f9874152663c0541943739717d11
Active: True
Quantity Used: 1
Service Level: Premium
Service Type: L1-L3
Status Details:
Starts: 10/08/2013
Ends: 10/07/2014
System Type: Physical
2. Enable the Red Hat Satellite, Red Hat Enterprise Linux, and Red Hat Software Collections
repositories.
NOTE
If you are installing Red Hat Satellite as a virtual machine hosted on Red Hat
Virtualization (RHV), you also need to enable the Red Hat Common repository,
and install RHV guest agents and drivers. For more information, see Installing the
Guest Agents and Drivers on Red Hat Enterprise Linux in the Virtual Machine
Management Guide for more information.
3. Ensure that Red Hat Subscription Manager is not set to use a specific operating system release.
4. Clear out any metadata left from any non-Red Hat yum repositories.
17
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
# yum update
3. Go to Section 2.2, “Performing the Initial Configuration” to run the installation script and perform
the initial configuration of your Satellite Server.
2. Click DOWNLOADS.
4. Ensure that you have the correct product and version for your environment.
Version is set to the latest minor version of the product you are using as the base system.
5. On the Packages tab, enter the name of the package required in the Search box.
7. Copy the package to the Satellite base system or another accessible storage device:
# cd /path-to-package/
Before you continue, consider which manifests or packages are relevant for your environment. For more
information on manifests, see Managing Subscriptions in the Red Hat Satellite Content Management
Guide.
18
CHAPTER 2. INSTALLING SATELLITE SERVER
Two NTP based time synchronizers are available: chronyd and ntpd. The chronyd implementation is
specifically recommended for systems that are frequently suspended and for systems that have
intermittent network access. The ntpd implementation should only be used when you specifically need
support for a protocol or driver not yet supported by chronyd.
For more information about the differences between ntpd and chronyd, see Differences Between ntpd
and chronyd in the Red Hat Enterprise Linux 7 System Administrator’s Guide.
1. Install chronyd.
Automatic Configuration - This method is performed by using an answer file to automate the
configuration process when running the installation script. An answer file is a file containing a list
of parameters that are read by a command or script. The default Satellite answer file is
/etc/foreman-installer/scenarios.d/satellite-answers.yaml. The answer file in
use is set by the answer_file directive in the /etc/foreman-
installer/scenarios.d/satellite.yaml configuration file.
To perform the initial configuration using the installation script with an answer file, see
Section 2.2.3.2, “Performing the Initial Configuration Automatically using an Answer File”.
Manual Configuration - This method is performed by running the installation script with one or
19
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
more command options. The command options override the corresponding default initial
configuration options and are recorded in the Satellite answer file. You can run the script as often
as needed to configure any necessary options.
To perform the initial configuration using the installation script with command-line options, see
Section 2.2.3.1, “Performing the Initial Configuration Manually”.
NOTE
Depending on the options that you use when running the Satellite installer, the
configuration can take several minutes to complete. An administrator is able to view the
answer file to see previously used options for both methods.
This initial configuration procedure creates an organization, location, user name, and password. After the
initial configuration, you can create additional organizations and locations if required. The initial
configuration also installs MongoDB and PostgreSQL databases on the same server. Depending on your
deployment, using external databases can benefit performance.
The installation process can take tens of minutes to complete. If you are connecting remotely to the
system, consider using a utility such as screen that allows suspending and reattaching a
communication session so that you can check the installation progress in case you become
disconnected from the remote system. The Red Hat Knowledgebase article How to use the screen
command describes installing screen; alternately see the screen manual page for more information. If
you lose connection to the shell where the installation command is running, see the log at
/var/log/foreman-installer/satellite.log to determine if the process completed
successfully.
By default, all configuration files configured by the installer are managed by Puppet. When satellite-
installer runs, it overwrites any manual changes to the Puppet managed files with the initial values.
By default, Satellite Server is installed with the Puppet agent running as a service. If required, you can
disable Puppet agent on Satellite Server using the --puppet-runmode=none option.
If you want to manage DNS files and DHCP files manually, use the --foreman-proxy-dns-
managed=false and --foreman-proxy-dhcp-managed=false options so that Puppet does not
manage the files related to the respective services. For more information on how to apply custom
configuration on other services, see Appendix B, Applying Custom Configuration to Red Hat Satellite.
If you want to use external databases with Satellite, before you run the satellite installer tool, you must
set up and point to external databases. For more information, see Using External Databases with
Satellite in Installing Satellite Server from a Connected Network.
20
CHAPTER 2. INSTALLING SATELLITE SERVER
--foreman-admin-username admin_user_name \
--foreman-admin-password admin_password \
--foreman-proxy-dns-managed=false \
--foreman-proxy-dhcp-managed=false
If you have been installing in a disconnected environment, unmount the ISO images.
# umount /media/sat6
# umount /media/rhel7-server
You can use answer files to automate installations with customized options. The initial answer file is
sparsely populated and after you run the satellite-installer script the first time, the answer file is
populated with the standard parameter values for installation. If you have already installed
Satellite Server using the method described in Section 2.2.3.1, “Performing the Initial Configuration
Manually”, then you do not need to use this method. You can, however, use it to make changes to the
configuration of Satellite Server at any time.
You should use the FQDN instead of the IP address where possible in case of network changes.
# cp /etc/foreman-installer/scenarios.d/satellite-answers.yaml \
/etc/foreman-installer/scenarios.d/my-answer-file.yaml
3. Open your copy of the answer file, edit the values to suit your environment, and save the file.
:answer_file: /etc/foreman-installer/scenarios.d/my-answer-file.yaml
6. If you have been installing in a disconnected environment, unmount the ISO images.
# umount /media/sat6
# umount /media/rhel7-server
21
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
You can access your subscription information on the Red Hat Customer Portal. You can also assign
subscriptions for use in on-premise management applications, such as Red Hat Satellite, using
subscription allocations.
1. Open https://access.redhat.com/ in your browser and log in to your Red Hat account.
6. From the Type list, select the type and version that corresponds to your Satellite Server.
7. Click Create.
5. A list of your Red Hat product subscriptions appears. Enter the Entitlement Quantity for each
product.
When you have added subscriptions to the allocation, export the manifest file.
From the Details tab, under the Subscription section, by clicking the Export Manifest button.
When the manifest is exported, the Customer Portal encodes the selected subscriptions certificates and
creates a .zip archive. This is the Subscription Manifest, which can be uploaded into the Satellite Server.
Both the Red Hat Satellite 6 Web UI and CLI provide methods for importing the manifest.
22
CHAPTER 2. INSTALLING SATELLITE SERVER
3. Click Manage Manifest to display the manifest page for the organization.
4. Click Choose file, select the Subscription Manifest, then click Upload.
When you complete this section, you can enable repositories and import Red Hat content. This is a
prerequisite for some of the following procedures. For more information, see Importing Red Hat Content
in the Red Hat Satellite Content Management Guide.
23
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
1. In the Satellite web UI, navigate to Content > Red Hat Repositories.
2. Use the Search field to enter the following repository name: Red Hat Satellite Tools 6.4 (for
RHEL 7 Server) (RPMs).
3. In the Available Repositories pane, click on Red Hat Satellite Tools 6.4 (for RHEL 7 Server)
(RPMs) to expand the repository set.
If the Red Hat Satellite Tools 6.4 items are not visible, it may be because they are not included
in the Subscription Manifest obtained from the Customer Portal. To correct that, log in to the
Customer Portal, add these repositories, download the Subscription Manifest and import it into
Satellite.
4. For the x86_64 entry, click the Enable icon to enable the repository.
Enable the Satellite Tools repository for every supported major version of Red Hat Enterprise Linux
running on your hosts. After enabling a Red Hat repository, a Product for this repository is automatically
created.
2. Click the arrow next to the product content to view available content.
24
CHAPTER 3. PERFORMING ADDITIONAL CONFIGURATION ON SATELLITE SERVER
excluding
The following procedure configures a proxy only for downloading content for Satellite.
Authentication Methods
Only basic authentication is supported: add your user name and password information to the --
katello-proxy-url option, or use the --katello-proxy-username and --katello-proxy-
password options.
1. Verify that the http_proxy, https_proxy, and no_proxy variables are not set.
# unset http_proxy
# unset https_proxy
# unset no_proxy
3. Verify that Satellite Server can connect to the Red Hat CDN and can synchronize its
repositories.
a. On the network gateway and the HTTP Proxy, enable TCP for the following host names:
25
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
Satellite Server communicates with the Red Hat CDN securely over SSL. Use of an SSL
interception proxy interferes with this communication. These hosts must be whitelisted on
the proxy.
For a list of IP addresses used by the Red Hat CDN (cdn.redhat.com), see the
Knowledgebase article Public CIDR Lists for Red Hat on the Red Hat Customer Portal.
1. To verify the ports that are permitted by SELinux for the HTTP cache, enter a command as
follows:
2. To configure SELinux to permit a port for the HTTP cache, for example 8088, enter a command
as follows:
For more information on SELinux port settings, see Section 1.9, “Changing Default SELinux ports”.
26
CHAPTER 3. PERFORMING ADDITIONAL CONFIGURATION ON SATELLITE SERVER
Note that if you are using compute resources for provisioning, and you want to use a different HTTP
proxy with the compute resources, the proxy that you set for all Satellite communication takes
precedence over the proxies that you set for compute resources.
To set an HTTP proxy for all outgoing HTTP connections from Satellite, complete the following steps:
2. In the HTTP(S) proxy row, select the adjacent Value column and enter the proxy URL.
To exclude one or more hosts from communicating through the proxy, complete the following steps:
2. In the HTTP(S) proxy except hosts row, select the adjacent Value column and enter the names
of one or more hosts that you want to exclude from proxy requests.
The BMC service enables you to perform a range of power management tasks. The underlying protocol
for this feature is IPMI; also referred to as the BMC function. IPMI uses a special network interface on
the managed hardware that is connected to a dedicated processor that runs independently of the host’s
CPUs. In many instances the BMC functionality is built into chassis-based systems as part of chassis
management (a dedicated module in the chassis).
For more information on the BMC service, see Configuring an Additional Network Interface in Managing
Hosts.
All managed hosts must have a network interface, with type BMC. Satellite uses this NIC to pass
the appropriate credentials to the host.
27
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
If you want to configure external services, see Configuring External Services for more information.
If you want to disable these services in Satellite in order to manage them manually, see Disabling DNS,
DHCP, and TFTP for Unmanaged Networks for more information.
Contact your network administrator to ensure that you have the correct settings.
DNS information
Use the FQDN instead of the IP address where possible in case of network changes.
NOTE
The information in the task is an example. You should use the information relevant to your
own environment.
For more information about configuring DHCP, DNS, and TFTP services, see the Configuring
Network Services section in the Provisioning Guide.
28
CHAPTER 3. PERFORMING ADDITIONAL CONFIGURATION ON SATELLITE SERVER
NOTE
Any changes to the settings require running satellite-installer again. You can run the
script multiple times and it updates all configuration files with the changed values.
2. On the Capsules tab, ensure that there is no DHCP Capsule or TFTP Capsule associated by
setting the drop-down list to None.
b. On the Domain tab, setting the DNS Capsule drop-down list to None.
b. On the Capsules tab, setting the Reverse DNS Capsule drop-down list to None.
5. Optional: If you use a DHCP service supplied by a third party, configure your DHCP server to
pass the following options:
NOTE
Satellite 6 does not perform orchestration when a Capsule is not set for a given subnet
and domain. When enabling or disabling Capsule associations, orchestration commands
for existing hosts can fail if the expected records and configuration files are not present.
When associating a Capsule in order to turn orchestration on, make sure the required
DHCP and DNS records as well as the TFTP files are in place for existing Satellite 6
managed hosts in order to prevent host deletion failures in the future.
29
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
Prerequisites
If you have upgraded from a previous release, rename or remove the configuration file
/usr/share/foreman/config/email.yaml and restart the httpd service. For example:
# mv /usr/share/foreman/config/email.yaml \
/usr/share/foreman/config/email.yaml-backup
# systemctl restart httpd
2. Click the Email tab and set the configuration options to match your preferred delivery method.
The changes have an immediate effect.
a. The following example shows the configuration options for using an SMTP server:
SMTP port 25
The SMTP username and SMTP password specify the login credentials for the SMTP
server.
30
CHAPTER 3. PERFORMING ADDITIONAL CONFIGURATION ON SATELLITE SERVER
Sendmail arguments -i -t -G
The Sendmail arguments specify the options passed to the sendmail command. The
default value is -i -t. For more information see the sendmail 1 man page.
3. If you decide to send email using an SMTP server which uses TLS authentication, also perform
one of the following steps:
Mark the CA certificate of the SMTP server as trusted. To do so, execute the following
commands on Satellite Server:
# cp mailca.crt /etc/pki/ca-trust/source/anchors/
# update-ca-trust enable
# update-ca-trust
Alternatively, in the web UI, set the SMTP enable StartTLS auto option to No.
4. Click Test email to send a test message to the user’s email address to confirm the configuration
is working. If a message fails to send, the web UI displays an error. See the log at
/var/log/foreman/production.log for further details.
31
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
NOTE
For information on configuring email notifications for individual users or user groups, see
Configuring Email Notifications in Administering Red Hat Satellite.
NOTE
Obtain custom SSL certificates for the Satellite Server and all external Capsule Servers
before starting this procedure.
3. Section 3.8.3, “Run the Satellite Installer with Custom Certificate Parameters”
4. Section 3.8.4, “Install the New Certificate on all Hosts Connected to the Satellite Server”
5. If you have external Capsule Servers registered to the Satellite Server, proceed to Configuring
Capsule Server with a Custom Server Certificate in the Installing Capsule Server guide to
configure the Capsule Servers to use a custom certificate.
IMPORTANT
NOTE
If you already have a custom SSL Certificate for the Satellite Server, skip this procedure.
1. Create a directory to contain all the source certificate files, accessible to only the root user.
In these examples, the directory is /root/sat_cert.
# mkdir /root/sat_cert
# cd /root/sat_cert
32
CHAPTER 3. PERFORMING ADDITIONAL CONFIGURATION ON SATELLITE SERVER
2. Create a private key with which to sign the Certificate Signing Request (CSR).
NOTE
If you already have a private key for the Satellite Server, skip this step.
NOTE
The certificate’s Common Name (CN) must match the fully-qualified domain
name (FQDN) of the server on which it is used. If you are requesting a certificate
for a Satellite Server, this is the FQDN of the Satellite Server. If you are
requesting a certificate for a Capsule Server, this is the FQDN of the
Capsule Server.
33
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
1. Validate the custom SSL certificate input files. Change the files' names to match your files.
# katello-certs-check \
-c /root/sat_cert/satellite_cert.pem \ 1
-k /root/sat_cert/satellite_cert_key.pem \ 2
-b /root/sat_cert/ca_cert_bundle.pem 3
1 Certificate file for the Satellite Server, signed by your Certificate Authority
Validation succeeded.
34
CHAPTER 3. PERFORMING ADDITIONAL CONFIGURATION ON SATELLITE SERVER
run:
There is a minor variation to this step, depending on whether or not the Satellite Server is already
installed. If it is already installed, the existing certificates must be updated with those in the certificates
archive.
The commands in this section are output by the katello-certs-check command, as detailed in
Section 3.8.2, “Validate the Satellite Server’s SSL Certificate”, and can be copied and pasted into a
terminal.
a. If Satellite is already installed, enter the following command on the Satellite Server:
35
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
NOTE
For all files in the satellite-installer command, use full path names,
not relative path names. The installer records all files' paths and names, and
if you enter the installer again, but from a different directory, it may fail as it is
unable to find the original files.
b. If Satellite is not already installed, enter the following command on the Satellite Server:
NOTE
For all files in the satellite-installer command, use full path names,
not relative path names. The installer records all files' paths and names, and
if you enter the installer again, but from a different directory, it may fail as it is
unable to find the original files.
2. Verify the certificate has been successfully installed on the Satellite Server before installing it on
hosts. On a computer with network access to the Satellite Server, start a web browser, navigate
to the URL https://satellite.example.com and view the certificate’s details.
3.8.4. Install the New Certificate on all Hosts Connected to the Satellite Server
Now that the custom SSL certificate has been installed on the Satellite Server, it must also be installed
on every host registered to the Satellite Server. Enter the following commands on all applicable hosts.
Depending on your requirements, you can use external databases for either MongoDB or PostgreSQL
database, or both.
Red Hat does not provide support or tools for external database maintenance. This includes backups,
upgrades, and database tuning. Customers using an external database require their own database
administrator to support and maintain the database.
36
CHAPTER 3. PERFORMING ADDITIONAL CONFIGURATION ON SATELLITE SERVER
If your Satellite deployment requires external databases, use the following information to set up and point
to external databases from Satellite.
Flexibility to tune the MongoDB server’s system without adversely affecting Satellite operations
If either the Satellite or the Mongo database server suffers a hardware or storage failure,
Satellite is not operational
If there is latency between the Satellite and the external database server, performance can
suffer
If you suspect that your Mongo database is slow, you can work with Red Hat Support to troubleshoot.
You might be encountering a configuration problem or existing performance problems with Satellite 6
that moving to an external database server might not help. Red Hat Support can examine existing known
issues and also work with the Satellite Engineering team to determine the root cause.
Flexibility to set shared_buffers on the PostgreSQL database to a high number without the
risk of interfering with other services on Satellite
Flexibility to tune the PostgreSQL server’s system without adversely affecting Satellite
operations
If either Satellite or the PostgreSQL database server suffers a hardware or storage failure,
Satellite is not operational
37
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
If there is latency between the Satellite server and database server, performance can suffer
If you suspect that the PostgreSQL database on your Satellite is causing performance problems, use the
information in Satellite 6: How to enable postgres query logging to detect slow running queries to
determine if you have slow queries. Queries that take longer than one second are typically caused by
performance issues with large installations, and moving to an external database might not help. If you
have slow queries, contact Red Hat Support.
3.9.3. Overview
To create and use a remote database for Satellite, you must complete the following procedures:
1. Use Section 1.2, “Storage Requirements and Guidelines” to plan the storage requirements for
your external databases
2. Prepare PostgreSQL with databases for Foreman and Candlepin and dedicated users owning
them
4. Follow the initial steps to install Satellite and ensure that the databases are accessible from
Satellite
5. Edit the parameters of satellite-installer to point to the new databases, and run
satellite-installer
Subscriptions for Red Hat Software Collections and Red Hat Enterprise Linux do not provide the correct
service level agreement for using Satellite with external databases. You must also attach a Satellite
subscription to the base system that you want to use for the external database.
1. Use the instructions in Identifying and Attaching the Satellite Subscription to the Host to attach a
Satellite subscription to your server.
2. To install MongoDB and PostgreSQL servers on Red Hat Enterprise Linux Server 7, you must
disable all repositories and enable only the following repositories:
38
CHAPTER 3. PERFORMING ADDITIONAL CONFIGURATION ON SATELLITE SERVER
# mongo pulp_database \
--eval "db.createUser({user:'pulp',pwd:'pulp_password',roles:
[{role:'dbOwner', db:'pulp_database'},{ role: 'readWrite', db:
'pulp_database'}]})"
bindIp: your_mongodb_server_bind_IP,::1
security:
authorization: enabled
# firewall-cmd --add-port=27017/tcp
# firewall-cmd --runtime-to-permanent
8. Test the connection from Satellite to the external MongoDB for database pulp_database:
2. To initialize, start, and enable PostgreSQL service, enter the following commands:
39
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
# postgresql-setup initdb
# systemctl start postgresql
# systemctl enable postgresql
# vi /var/lib/pgsql/data/postgresql.conf
listen_addresses = "*"
# vi /var/lib/pgsql/data/pg_hba.conf
# firewall-cmd --add-service=postgresql
# firewall-cmd --runtime-to-permanent
$ su - postgres -c psql
10. Create two databases and dedicated roles, one for Satellite and one for Candlepin:
11. From Satellite Server, test that you can access the database:
12. To install and configure the remote database for Satellite, enter the following command:
40
CHAPTER 3. PERFORMING ADDITIONAL CONFIGURATION ON SATELLITE SERVER
--foreman-db-password Foreman_Password \
--foreman-db-database foreman \
--katello-candlepin-db-host postgres.example.com \
--katello-candlepin-db-name candlepin \
--katello-candlepin-db-password Candlepin_Password \
--katello-candlepin-manage-db false \
--katello-pulp-db-username pulp \
--katello-pulp-db-password pulp_password \
--katello-pulp-db-seeds mongo.example.com:27017 \
--katello-pulp-db-name pulp_database
You can query the status of your databases. For example, enter the following command with the --
only and add postgresql or rh-mongodb34-mongod:
Restrict access to mongod on Satellite and Capsule Servers using the following commands.
41
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
# firewall-cmd --runtime-to-permanent
42
CHAPTER 4. CONFIGURING EXTERNAL SERVICES
If you want to disable these services in Satellite in order to manage them manually, see Disabling DNS,
DHCP, and TFTP for Unmanaged Networks for more information.
1. Deploy a Red Hat Enterprise Linux Server and install the ISC DNS Service.
# cat /etc/named.conf
include "/etc/rndc.key";
controls {
inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { "capsule";
};
inet 192.168.38.2 port 953 allow { 192.168.38.1; 192.168.38.2; }
keys { "capsule"; };
};
options {
directory "/var/named";
forwarders { 8.8.8.8; 8.8.4.4; };
};
include "/etc/named.rfc1912.zones";
zone "38.168.192.in-addr.arpa" IN {
type master;
file "dynamic/38.168.192-rev";
update-policy {
grant "capsule" zonesub ANY;
};
};
zone "virtual.lan" IN {
type master;
file "dynamic/virtual.lan";
update-policy {
grant "capsule" zonesub ANY;
};
};
43
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
The inet line must be entered as one line in the configuration file.
# ddns-confgen -k capsule
4. Copy and paste the output from the key section into a separate file called /etc/rndc.key.
# cat /etc/rndc.key
key "capsule" {
algorithm hmac-sha256;
secret "GeBbgGoLedEAAwNQPtPh3zP56MJbkwM84UJDtaUS9mw=";
};
IMPORTANT
This is the key used to change DNS server configuration. Only the root user
should read and write to it.
# cat /var/named/dynamic/virtual.lan
$ORIGIN .
$TTL 10800 ; 3 hours
virtual.lan IN SOA service.virtual.lan.
root.virtual.lan. (
9 ; serial
86400 ; refresh (1 day)
3600 ; retry (1 hour)
604800 ; expire (1 week)
3600 ; minimum (1 hour)
)
NS service.virtual.lan.
$ORIGIN virtual.lan.
$TTL 86400 ; 1 day
capsule A 192.168.38.1
service A 192.168.38.2
# cat /var/named/dynamic/38.168.192-rev
$ORIGIN .
$TTL 10800 ; 3 hours
38.168.192.in-addr.arpa IN SOA service.virtual.lan.
root.38.168.192.in-addr.arpa. (
4 ; serial
86400 ; refresh (1 day)
3600 ; retry (1 hour)
604800 ; expire (1 week)
3600 ; minimum (1 hour)
)
44
CHAPTER 4. CONFIGURING EXTERNAL SERVICES
NS service.virtual.lan.
$ORIGIN 38.168.192.in-addr.arpa.
$TTL 86400 ; 1 day
1 PTR capsule.virtual.lan.
2 PTR service.virtual.lan.
# named-checkconf -z /etc/named.conf
4. Test that the DNS service can resolve the new host.
6. Configure the firewall for external access to the DNS service (UDP and TCP on port 53).
To configure the DHCP server and share the DHCP configuration and lease files
1. Deploy a Red Hat Enterprise Linux Server and install the ISC DHCP Service and Berkeley
Internet Name Domain (BIND).
45
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
The above command can take a long time, for less-secure proof-of-concept deployments you
can use a non-blocking random number generator.
This creates the key pair in two files in the current directory.
4. Edit the dhcpd configuration file for all of the subnets and add the key as in the example:
# cat /etc/dhcp/dhcpd.conf
default-lease-time 604800;
max-lease-time 2592000;
log-facility local7;
omapi-port 7911;
key omapi_key {
algorithm HMAC-MD5;
secret "jNSE5YI3H1A8Oj/tkV4...A2ZOHb6zv315CkNAY7DMYYCj48Umw==";
};
omapi-key omapi_key;
5. Delete the two key files from the directory where you created them.
8. Determine the UID and GID numbers of the foreman user on the Satellite Server.
46
CHAPTER 4. CONFIGURING EXTERNAL SERVICES
# id -u foreman
993
# id -g foreman
990
9. Create the same user and group with the same IDs on the DHCP server.
10. To make the configuration files readable, restore the read and execute flags.
12. Export the DHCP configuration and leases files using NFS.
13. Create the DHCP configuration and leases files to be exported using NFS.
14. Add the following line to the /etc/fstab file to create mount points for the newly created
directories.
# mount -a
/exports
192.168.38.1(rw,async,no_root_squash,fsid=0,no_subtree_check)
/exports/etc/dhcp
192.168.38.1(ro,async,no_root_squash,no_subtree_check,nohide)
/exports/var/lib/dhcpd
192.168.38.1(ro,async,no_root_squash,no_subtree_check,nohide)
47
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
# exportfs -rva
18. Configure the firewall for the DHCP omapi port 7911 for the Satellite Server.
# firewall-cmd --add-port="7911/tcp" \
&& firewall-cmd --runtime-to-permanent
4. Verify communication with the NFS server and RPC communication paths.
# showmount -e your_DHCP_server_FQDN
# rpcinfo -p your_DHCP_server_FQDN
your_DHCP_server_FQDN:/exports/var/lib/dhcpd /mnt/nfs/var/lib/dhcpd
nfs
ro,vers=3,auto,nosharecache,context="system_u:object_r:dhcpd_state_t
:s0" 0 0
# mount -a
48
CHAPTER 4. CONFIGURING EXTERNAL SERVICES
# su foreman-proxy -s /bin/bash
bash-4.2$ cat /mnt/nfs/etc/dhcp/dhcpd.conf
bash-4.2$ cat /mnt/nfs/var/lib/dhcpd/dhcpd.leases
bash-4.2$ exit
8. Run the satellite-installer script to make the following persistent changes to the
/etc/foreman-proxy/settings.d/dhcp.yml file.
# satellite-installer --foreman-proxy-dhcp=true \
--foreman-proxy-dhcp-provider=remote_isc \
--foreman-proxy-plugin-dhcp-remote-isc-dhcp-config
/mnt/nfs/etc/dhcp/dhcpd.conf \
--foreman-proxy-plugin-dhcp-remote-isc-dhcp-leases
/mnt/nfs/var/lib/dhcpd/dhcpd.leases \
--foreman-proxy-plugin-dhcp-remote-isc-key-name=omapi_key \
--foreman-proxy-plugin-dhcp-remote-isc-key-
secret=jNSE5YI3H1A8Oj/tkV4...A2ZOHb6zv315CkNAY7DMYYCj48Umw== \
--foreman-proxy-plugin-dhcp-remote-isc-omapi-port=7911 \
--enable-foreman-proxy-plugin-dhcp-remote-isc \
--foreman-proxy-dhcp-server=your_DHCP_server_FQDN
11. Go to Infrastructure > Capsules. Locate the appropriate Capsule Server and from the Actions
drop-down list, select Refresh. The DHCP feature should appear.
12. Associate the DHCP service with the appropriate subnets and domain.
You can use TFTP services through NAT, for more information see Using TFTP services through NAT in
the Provisioning guide.
You should have already configured NFS and the firewall for external access to NFS. See
Configuring Satellite Server with External DHCP.
49
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
# mkdir -p /var/lib/tftpboot/{boot,pxelinux.cfg,grub2}
# cp /usr/share/syslinux/{pxelinux.0,menu.c32,chain.c32} \
/var/lib/tftpboot/
# mkdir -p /exports/var/lib/tftpboot
# mount -a
/exports
192.168.38.1(rw,async,no_root_squash,fsid=0,no_subtree_check)
/exports/var/lib/tftpboot
192.168.38.1(rw,async,no_root_squash,no_subtree_check,nohide)
The first line is common to the DHCP configuration and therefore should already be present if
the previous procedure was completed on this system.
# exportfs -rva
# firewall-cmd --add-port="69/udp" \
&& firewall-cmd --runtime-to-permanent
50
CHAPTER 4. CONFIGURING EXTERNAL SERVICES
Red Hat Satellite can be configured to use a Red Hat Identity Management (IdM) server to provide the
DNS service. Two methods are described here to achieve this, both using a transaction key. For more
information on Red Hat Identity Management, see the Linux Domain Identity, Authentication, and Policy
Guide.
The first method is to install the IdM client which automates the process with the generic security service
algorithm for secret key transaction (GSS-TSIG) technology defined in RFC3645. This method requires
installing the IdM client on the Satellite Server or Capsule’s base system and having an account created
by the IdM server administrator for use by the Satellite administrator. See Section 4.5.1, “Configuring
Dynamic DNS Update with GSS-TSIG Authentication” to use this method.
The second method, secret key transaction authentication for DNS (TSIG), uses an rndc.key for
authentication. It requires root access to the IdM server to edit the BIND configuration file, installing the
BIND utility on the Satellite Server’s base system, and coping the rndc.key to between the systems.
This technology is defined in RFC2845. See Section 4.5.2, “Configuring Dynamic DNS Update with
TSIG Authentication” to use this method.
NOTE
You are not required to use Satellite to manage DNS. If you are using the Realm
enrollment feature of Satellite, where provisioned hosts are enrolled automatically to IdM,
then the ipa-client-install script creates DNS records for the client. The following
procedure and Realm enrollment are therefore mutually exclusive. For more information
on configuring Realm enrollment, see External Authentication for Provisioned Hosts in
Administering Red Hat Satellite.
Network 192.168.55.0/24
51
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
1. Confirm the IdM server is deployed and the host-based firewall has been configured correctly.
For more information, see Port Requirements in the Linux Domain Identity, Authentication, and
Policy Guide.
2. Obtain an account on the IdM server with permissions to create zones on the IdM server.
4. Confirm that the Satellite or external Capsule are currently working as expected.
5. In the case of a newly installed system, complete the installation procedures in this guide first. In
particular, DNS and DHCP configuration should have been completed.
6. Make a backup of the answer file in case you have to revert the changes. See Specifying
Installation Options for more information.
# kinit idm_user
Where idm_user is the account created for you by the IdM administrator.
2. Create a new Kerberos principal for the Satellite or Capsule to use to authenticate to the IdM
server.
2. Configure the IdM client by running the installation script and following the on-screen prompts.
# ipa-client-install
# kinit admin
# rm /etc/foreman-proxy/dns.keytab
# ipa-getkeytab -p capsule/satellite.example.com@EXAMPLE.COM \
-s idm1.example.com -k /etc/foreman-proxy/dns.keytab
52
CHAPTER 4. CONFIGURING EXTERNAL SERVICES
NOTE
When adding a keytab to a standby system with the same host name as the
original system in service, add the r option to prevent generating new credentials
and rendering the credentials on the original system invalid.
6. Set the group and owner for the keytab file to foreman-proxy as follows.
b. Select Add and enter the zone name. In this example, example.com.
d. On the Settings tab, in the BIND update policy box, add an entry as follows to the semi-
colon separated list.
b. Select Add.
c. Select Reverse zone IP network and add the network address in CIDR format to enable
reverse lookups.
e. On the Settings tab, in the BIND update policy box, add an entry as follows to the semi-
colon separated list:
53
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
Configure the Satellite or Capsule Server Managing the DNS Service for the Domain.
2. For each Capsule to be updated, from the Actions drop-down menu, select Refresh.
b. On the Domain tab, ensure DNS Capsule is set to the Capsule where the subnet is
connected.
54
CHAPTER 4. CONFIGURING EXTERNAL SERVICES
c. On the Domains tab, ensure the domain to be managed by the IdM server is selected.
d. On the Capsules tab, ensure Reverse DNS Capsule is set to the Capsule where the
subnet is connected.
IP address 192.168.25.1
IP address 192.168.25.2
1. Confirm the IdM Server is deployed and the host-based firewall has been configured correctly.
For more information, see Port Requirements in the Linux Domain Identity, Authentication, and
Policy Guide.
4. Confirm that the Satellite or external Capsule are currently working as expected.
5. In the case of a newly installed system, complete the installation procedures in this guide first. In
particular, DNS and DHCP configuration should have been completed.
6. Make a backup of the answer file in case you have to revert the changes. See Specifying
Installation Options for more information.
1. On the IdM Server, add the following to the top of the /etc/named.conf file.
55
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
controls {
inet 192.168.25.2 port 953 allow { 192.168.25.1; } keys { "rndc-
key"; };
};
####################################################################
####
3. In the IdM web UI, go to Network Services > DNS > DNS Zones. Select the name of the zone.
On the Settings tab:
4. Copy the /etc/rndc.key file from the IdM server to Satellite’s base system as follows.
5. Ensure that the ownership, permissions, and SELinux context are correct.
# restorecon -v /etc/rndc.key
# chown -v root:named /etc/rndc.key
# chmod -v 640 /etc/rndc.key
6. On Satellite Server, run the installation script as follows to use the external DNS server.
2. Ensure the key in the /etc/rndc.key file on Satellite Server is the same one as used on the
IdM server.
key "rndc-key" {
algorithm hmac-md5;
56
CHAPTER 4. CONFIGURING EXTERNAL SERVICES
secret "secret-key==";
};
3. On Satellite Server, create a test DNS entry for a host. For example, host test.example.com
with an A record of 192.168.25.20 on the IdM server at 192.168.25.1.
Name: test.example.com
Address: 192.168.25.20
5. To view the entry in the IdM web UI, go to Network Services > DNS > DNS Zones. Select the
name of the zone and search for the host by name.
The above nslookup command fails and outputs the SERVFAIL error message if the record
was successfully deleted.
On the Satellite or Capsule Server that is to manage DNS for the domain.
If you backed up the answer file before the change to external DNS, restore the answer file and
then run the installation script:
# satellite-installer
If you do not have a suitable backup of the answer file, back up the answer file now, and then run
the installation script on Satellite and Capsules as described below.
See Specifying Installation Options for more information on the answer file.
# satellite-installer \
57
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
--foreman-proxy-dns=true \
--foreman-proxy-dns-managed=true \
--foreman-proxy-dns-provider=nsupdate \
--foreman-proxy-dns-server="127.0.0.1" \
--foreman-proxy-dns-tsig-
principal="foremanproxy/satellite.example.com@EXAMPLE.COM" \
--foreman-proxy-dns-tsig-keytab=/etc/foreman-proxy/dns.keytab
See Configuring DNS, DHCP, and TFTP on Capsule Server for more information.
2. For each Capsule to be updated, from the Actions drop-down menu, select Refresh.
b. On the Domain tab, ensure DNS Capsule is set to the Capsule where the subnet is
connected.
c. On the Domains tab, ensure the domain to be managed by the Satellite or Capsule is
selected.
d. On the Capsules tab, ensure Reverse DNS Capsule is set to the Capsule where the
subnet is connected.
58
CHAPTER 5. UNINSTALLING SATELLITE SERVER
Uninstalling Satellite Server erases all applications used on the target system. If you use any
applications or application data for purposes other than Satellite Server, you should back up the
information before the removal process.
WARNING
This script erases many packages and config files, such as the following important
packages:
httpd (apache)
mongodb
tomcat6
puppet
ruby
rubygems
# katello-remove
59
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
Use the Deployment Scenarios section to understand the different architecture setups that are available
for Satellite and Capsule installation on AWS.
Use the Prerequisites section to prepare your Red Hat and Amazon Web resources for the Red Hat
Satellite installation.
Subscriptions
Not all subscriptions are eligible to run in public cloud environments. For more information about
subscription eligibility, see the Cloud Access Page. You can create additional organizations and then
import additional manifests to the organizations. For more information, see Creating an Organization in
the Content Management Guide.
Subscription Management
Content Management
Errata Management
Configuring Hosts
Provisioning Containers
OpenSCAP
Remote Execution
60
CHAPTER 6. RUNNING RED HAT SATELLITE ON AMAZON WEB SERVICES
You must do this when Satellite Server or Capsule Server has different internal and external DNS host
names and there is no site-to-site VPN connection between the locations where you deploy Satellite
Server and Capsule Server.
For more information, see Importing Red Hat Content in the Content Management Guide.
PXE Provisioning
Per-host ISO
Generic ISO
Full-host ISO
61
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
The least complex configuration of Satellite Server in Amazon Web Services consists of both the Satellite
Server and the content hosts residing within the same region and within the Virtual Private Cloud (VPC).
It is also possible to use the external host name of Satellite Server when you register the instance which
runs Capsule Server.
Option 1: Site-to-Site VPN connection between the AWS region and the On-Premise Datacenter
62
CHAPTER 6. RUNNING RED HAT SATELLITE ON AMAZON WEB SERVICES
If you do not establish a site-to-site VPN connection, use the external DNS host name when you register
the instance that runs Capsule Server to the Satellite Server.
NOTE
Most Public Cloud Providers do not charge for data being transferred into a region, or
between availability zones within a single region; however, they do charge for data
leaving the region to the Internet.
63
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
6.3. PREREQUISITES
Before you can install and register Red Hat Satellite and Capsule, you must set up accounts with
Amazon Web Services (AWS) and create and start Red Hat Enterprise Linux instances on AWS.
64
CHAPTER 6. RUNNING RED HAT SATELLITE ON AMAZON WEB SERVICES
Launching instances
To install Satellite and Capsule in an AWS environment, you must ensure that your AWS set up meets
the Section 1.1, “System Requirements” for Satellite and Capsule.
For more information about Amazon Web Services and terminology, see Amazon Elastic Compute Cloud
Documentation.
For more information about Amazon Web Services Direct Connect, see What is AWS Direct Connect?
Create an AWS instance and deploy a Red Hat Enterprise Linux virtual machine to the instance.
Ensure that your subscriptions are eligible for transfer to Red Hat Cloud. For more information,
see Red Hat Cloud Access Program Details.
For more information about deploying Red Hat Enterprise Linux in AWS, see How to Locate Red Hat
Cloud Access Gold Images on AWS EC2.
Use Chapter 1, Preparing your environment for installation to understand and assign the correct
storage to your AWS EBS volumes.
Store the synced content on an EBS volume that is separate to the boot volume.
Mount the synced content EBS volume separately in the operating system.
Optional: store other data, for example, the mongodb directory on a separate EBS volume.
If you want the Satellite Server and Capsule Server to communicate using external DNS
hostnames, open the required ports for communication in the AWS Security Group that is
associated with the instance.
65
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
If you use a Red Hat Gold Image, remove the RHUI client and set the enabled parameter in the
product-id.conf to 1.
2. Install Capsule Server. For more information, see Installing Capsule Server.
For more information about using the bootstrap script, see Registering Hosts to Satellite Using The
Bootstrap Script in the User Guide.
Install the Katello Agent. For more information, see Installing the katello Agent.
66
APPENDIX A. LARGE DEPLOYMENT CONSIDERATIONS
[Service]
LimitNOFILE=65536
# systemctl daemon-reload
[Service]
LimitNOFILE=65536
# systemctl daemon-reload
# systemctl restart qpidd.service
work_mem = 4MB
shared_buffers = 256MB
67
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
1. Adjust the maximum passenger pool size to 1.5 times the physical CPU cores available to the
Satellite Server.
For example, if you have a Satellite Server with 16 cores, then the maximum passenger pool
size is 24. This number is referenced as an example and you should use the number applicable
to your environment.
<IfModule mod_passenger.c>
PassengerRoot /usr/share/gems/gems/passenger-
4.0.18/lib/phusion_passenger/locations.ini
PassengerRuby /usr/bin/ruby
PassengerMaxPoolSize 24
PassengerMaxRequestQueueSize 200
PassengerStatThrottleRate 120
</IfModule>
PassengerAppRoot /usr/share/foreman
PassengerRuby /usr/bin/tfm-ruby
PassengerMinInstances 6
PassengerStartTimeout 90
PassengerMaxPreloaderIdleTime 0
PassengerMaxRequests 10000
PassengerPreStart https://example.com
PassengerMinInstances 6
PassengerStartTimeout 90
PassengerMaxPreloaderIdleTime 0
PassengerMaxRequests 10000
PassengerPreStart https://example.com:8140
max_connections = 500
68
APPENDIX A. LARGE DEPLOYMENT CONSIDERATIONS
1. Calculate the required maximum number of open files, using the following equation.
For example, with 1020 content hosts, the new maximum should be set to 3160 ((3 x 1020) +
100).
[Service]
LimitNOFILE=maximum_number_of_files
# systemctl daemon-reload
By default, the Linux kernel uses the /dev/random device as the source of random numbers. This is a
blocking device, which means it stops supplying numbers when it determines that the amount of entropy
is insufficient for generating a properly random output. It is this wait time which causes the delay in
registering hosts. To resolve this issue, use the /dev/urandom device, as this is a non-blocking device.
Some hardware servers have processors which include hardware random number generators. For those
that are supported by the Red Hat Enterprise Linux kernel, you can use that as the source of random
numbers. For more information, see the hardware vendor’s documentation.
If Satellite is hosted on a virtual machine, note that some hypervisors make the hardware server’s
random number generator available to the virtual machines it hosts. Red Hat Virtualization features the
virtio RNG (Random Number Generator) device that provides KVM virtual machines access to entropy
from the Red Hat Virtualization Host. On guests running Red Hat Enterprise Linux 7.0, you must install
and configure rngd. On guests running Red Hat Enterprise Linux 7.1 and later, the guest kernel fetches
entropy from the host as required. If a host’s random number generator is shared by guests, use of a
hardware random number generator is recommended.
69
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
For more information about random number generators for guests, see Random Number Generator
Device in the Red Hat Enterprise Linux 7 Virtualization Deployment and Administration Guide. For other
hypervisors, see the vendor’s documentation.
For more information about the random number generator daemon, rngd, see Using the Random
Number Generator in the Red Hat Enterprise Linux 7 Security Guide.
70
APPENDIX B. APPLYING CUSTOM CONFIGURATION TO RED HAT SATELLITE
To view all installer flags available for custom configuration, run satellite-installer --scenario
satellite --full-help. Some Puppet classes are not exposed to the Satellite installer. To manage
them manually and prevent the installer from overwriting their values, specify the configuration values by
adding entries to configuration file /etc/foreman-installer/custom-hiera.yaml. This
configuration file is in YAML format, consisting of one entry per line in the format of <puppet class>::
<parameter name>: <value>. Configuration values specified in this file persist across installer
reruns.
For Apache, to set the ServerTokens directive to only return the Product name:
apache::server_tokens: Prod
apache::server_signature: Off
pulp::num_workers: 8
The Puppet modules for the Satellite installer are stored under /usr/share/foreman-
installer/modules and /usr/share/katello-installer-base/modules. Check the .pp files
(for example: moduleName/manifests/example.pp) to look up the classes, parameters, and values.
Alternatively, use the grep command to do keyword searches.
Setting some values may have unintended consequences that affect the performance or functionality of
Red Hat Satellite. Consider the impact of the changes before you apply them, and test the changes in a
non-production environment first. If you do not have a non-production Satellite environment, run the
Satellite installer with the --noop and --verbose options. If your changes cause problems, remove the
offending lines from custom-hiera.yaml and rerun the Satellite installer. If you have any specific
questions about whether a particular value is safe to alter, contact Red Hat support.
71
Red Hat Satellite 6.4 Installing Satellite Server from a Connected Network
1. Copy the file you intend to restore. This allows you to compare the files to check for any
mandatory changes required by the upgrade. This is not common for DNS or DHCP services.
# cp /etc/dhcp/dhcpd.conf /etc/dhcp/dhcpd.backup
2. Check the log files to note down the md5sum of the overwritten file. For example:
# journalctl -xe
...
/Stage[main]/Dhcp/File[/etc/dhcp/dhcpd.conf]: Filebucketed
/etc/dhcp/dhcpd.conf to puppet with sum
622d9820b8e764ab124367c68f5fa3a1
...
4. Compare the backup file and the restored file, and edit the restored file to include any mandatory
changes required by the upgrade.
72