Search This Blog

Requirements

Software Requirements

Base operating system
Red Hat Network Satellite is supported with Red Hat Enterprise Linux 5 and 6. The operating system can be installed from disc, local ISO image, kickstart, or any of the methods supported by Red Hat. Red Hat Enterprise Linux installations require the @Base package group with no other package-set modifications, and without third-party configurations or software that is not directly necessary for the direct operation of the server. This restriction includes hardening or other non-Red Hat security software. If such software is required in your infrastructure, firstinstall and verify a complete working Satellite first, and then make a backup of the system before adding any non-Red Hat software.

When installing a new Red Hat Network Satellite, it is recommended that the latest supported update to Red Hat Enterprise Linux is installed.

Satellite can be installed on Red Hat Enterprise Linux 5 or 6 in any virtualized environment supported by Red Hat, including Xen, KVM, and VMware. Functional support for virtualized environments does not always equal the same performance of running on physical hardware. Make sure to consider your virtualized environment's performance and implement any recommended tuning guidelines.

When installing Red Hat Enterprise Linux 5 or 6 from CD or ISO image, there is no need to select any package groups, only the base install is required. When installing either operating system via kickstart, select the @Basepackage group.

Satellite installation disc or ISO
This contains the Satellite Installer. All packages required in order to support Satellite are installed automatically, and require no intervention from the user.
Channel content

All software packages and data exported for all entitled Red Hat channels. This content is loaded directly on the Satellite after installation using the Red Hat Network Satellite Synchronization Tool.

Stand-Alone Database Requirements

The Stand-Alone Database version of Red Hat Network Satellite requires certain hardware considerations. This section specifies these hardware requirements when installing a Red Hat Network Satellite server and connecting to an external database.

Intel Core processor, 2.4GHz, 512K cache or equivalent
Intel multi-core processor, 2.4GHz dual processor, 512K cache or equivalent

2 GB of memory
8 GB of memory

5 GB storage for base install of Red Hat Enterprise Linux
At least 30 GB storage per software channel (including Base and child channels), in /var/satellite/, configurable at install

s/390 Hardware Requirements for Stand-Alone Database Installations


1 IFL, either in LPAR configuration or shared through z/VM
2+ IFLs on z9 or earlier, 1+ IFL on z10
2 GB of memory
8 GB of memory
1 GB swap on ECKD DASD
512 MB swap on VDISK + 1 GB swap on ECKD DASD
1xMod3 ECKD DASD or ≥ 2 GB FCP SCSI LUN for OS install
1xMod9 ECKD DASD or ≥ 2 GB multipathed FCP SCSI LUN for Red Hat Enterprise Linux installation
At least 30 GB storage per software channel (including Base and child channels), in /var/satellite/, configurable at install
z/VM 5.3 or later[a]
VSWITCH or Hipersocket LAN for high speed connections to guests

Database Requirements for Stand-Alone Database Installations

Red Hat supports Satellite installations on a Stand-Alone Database using Oracle Database 10g Release 2 Standard and Enterprise Edition or Oracle 11g. Ensure the Stand-Alone Database runs on a different server to the Red Hat Network Satellite.

A single 12 GB tablespace is recommended for most installations, although many customers will find it possible to function with a smaller tablespace. Have an experienced Oracle database administrator (DBA) assess your sizing requirements. Use the following formula to determine the required size of your database:
  • 250 KiB per client system
  • 500 KiB per channel, plus 230 KiB per package in the channel (so a channel with 5000 packages would require 1.1 Gib) 
For instance, an Red Hat Network Satellite containing four channels and serving 10,000 systems would require 2.5 GiB for its clients and 11 GiB for its channels. If custom channels are to be established for testing and staging of packages, they must be included in this formula.
Keep in mind that the database storage needs may grow rapidly, depending upon the variance of the following factors:
  • The number of public Red Hat packages imported (typical: 5000)
  • The number of private packages to be managed (typical: 500)
  • The number of systems to be managed (typical: 1000)
  • The number of packages installed on the average system (typical: 500)

The precise access levels required by the Oracle user are as follows:
  1. ALTER SESSION
  2. CREATE SEQUENCE
  3. CREATE SYNONYM
  4. CREATE TABLE
  5. CREATE VIEW
  6. CREATE PROCEDURE
  7. CREATE TRIGGER
  8. CREATE TYPE
  9. CREATE SESSION
Additional database requirements include:
  • Security Identifier (SID)
  • Listener Port
  • Username
  • UTF-8 character set

Two additional suggested recommendation for user's default tablespace include:
  1. Uniform Extent Size
  2. Auto Segment Space Management