이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 3. Preparing environment for Satellite Server installation
Ensure that your network environment is ready for the Satellite Server installation.
3.1. Opening required ports 링크 복사링크가 클립보드에 복사되었습니다!
By opening the required ports, you ensure that the components of Satellite architecture can communicate. You must also ensure that the required network ports are open on any network-based firewalls.
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.
Procedure
Open the ports for clients on Satellite Server:
# firewall-cmd \ --add-port="8000/tcp" \ --add-port="9090/tcp"Allow access to services on Satellite Server:
# firewall-cmd \ --add-service=dns \ --add-service=dhcp \ --add-service=tftp \ --add-service=http \ --add-service=https \ --add-service=puppetmasterMake the changes persistent:
# firewall-cmd --runtime-to-permanent
Verification
View all firewall zones and allowed services:
# firewall-cmd --list-all
3.2. Verifying DNS resolution 링크 복사링크가 클립보드에 복사되었습니다!
Verify the full forward and reverse DNS resolution using a fully-qualified domain name to prevent issues while installing Satellite.
Procedure
Ensure that the host name and local host resolve correctly:
# ping -c1 localhost # ping -c1 `hostname -f` # my_system.domain.comSuccessful name resolution results in output similar to the following:
# ping -c1 localhost PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.043 ms --- localhost ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.043/0.043/0.043/0.000 ms # ping -c1 `hostname -f` PING hostname.gateway (XX.XX.XX.XX) 56(84) bytes of data. 64 bytes from hostname.gateway (XX.XX.XX.XX): icmp_seq=1 ttl=64 time=0.019 ms --- localhost.gateway ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.019/0.019/0.019/0.000 msTo avoid discrepancies with static and transient host names, set all the host names on the system by entering the following command:
# hostnamectl set-hostname nameWarningName resolution is critical to the operation of Satellite. If Satellite cannot properly resolve its fully qualified domain name, tasks such as content management, subscription management, and provisioning will fail.
3.3. Preparing Satellite for using external databases 링크 복사링크가 클립보드에 복사되었습니다!
By default, the Satellite installation process includes installing a PostgreSQL database on the same host as Satellite Server. However, in certain Satellite deployments, using external databases instead of the default local databases can help with the server load or have other benefits.
Prerequisites
- You have considered whether using an external database is beneficial for your use case. For more information, see PostgreSQL as an external database considerations in Administering Red Hat Satellite.
Procedure
- Install PostgreSQL on an external database host you prepared. For more information, see Installing PostgreSQL in Administering Red Hat Satellite.
Next steps
- To set up an external database when installing Satellite, see Section 4.6, “Configuring Satellite Server”.