A Capsule Server mirrors content from Satellite Server to provide content federation and localized services in remote geographical locations. Host systems pull content and configuration from Capsule Server in their location. Additional Capsule Servers can be created to provide managed host scaling in a local or remote location, or to provide managed host isolation.

Figure 1.2: Capsule Server components

A Capsule Server provides these content-related features, which are further discussed in a later chapter:

A Capsule Server provides these infrastructure and host management services, which are further discussed in a later chapter:

Capsule Servers facilitate scaling your Satellite environment as the number of managed host systems increases. Capsule Servers decrease the load on the central Satellite Server, increase redundancy, and reduce bandwidth usage.

Similar to other Red Hat products that have fully featured graphical and command-line interfaces, Satellite administrators can use whichever tool they prefer. Red Hat recommends the web UI for new learners, and for candidates who are practicing for the Red Hat Certified Specialist in Deployment and Systems Management (EX403) exam, because it can be easier to achieve product competency with the graphical interface.

Satellite Server web UI is based on Cockpit technology, similar to the RHEL web console. Managed host web consoles can be enabled and configured for access through the Satellite Server web UI. The web console provides a single interface for almost all systems management, configuration management, and provisioning tasks for Satellite-managed hosts.

To work effectively in the Satellite Server web UI, set your screen resolution to 1600 x 1200 or higher. Red Hat recommends a minimum screen resolution of 1920 x 1080.

Figure 1.3: Satellite Server web UI screen resolution required

Red Hat recommends the Hammer CLI for experienced Satellite administrators, and for those who need to scale tasks in organizations with many managed hosts. You can efficiently scale your systems management by gaining familiarity with Hammer functions and adding scripting skills and integration with other programming languages.

Compared to navigating the web UI, using Hammer can result in faster interaction with the Satellite Server. You can also incorporate Hammer commands into reusable scripts for automating tasks of varying complexity. Output from hammer commands can be redirected to other tools, which allows for integration with your existing environment. The hammer command provides the -d option to test responses to API calls before using them in scripts. Hammer also provides an interactive shell.

Typically, Hammer commands are issued directly on the base operating system host that runs Red Hat Satellite. A Satellite user must provide Satellite credentials for authentication when entering hammer commands. A user can provide credentials on each command, or once per session if the Foreman session feature is enabled. Alternatively, store your credentials in the ~/.hammer/cli.modules.d/foreman.yml configuration file in this format:

:foreman:
 :username: 'username'
 :password: 'password'

Hammer provides many subcommands to interact with your Satellite Server. The hammer --help command is a comprehensive resource for viewing options, subcommands, and syntax requirements.

[root@satellite ~]# hammer --help
Usage:
    hammer [OPTIONS] SUBCOMMAND [ARG] ...
...output omitted...

Subcommands:
 activation-key                Manipulate activation keys
 admin                         Administrative server-side tasks
 ansible                       Manage foreman ansible
 ...output omitted...

Options:
 --[no-]use-defaults           Enable/disable stored defaults. Enabled by default
 --autocomplete LINE           Get list of possible endings
 --csv                         Output as CSV (same as --output=csv)
...output omitted...

The --help option also views extended syntax requirements for subcommands. For example, for syntax help to create an activation key, use the following command:

[root@satellite ~]# hammer activation-key create --help
Usage:
    hammer activation-key create [OPTIONS]

Options:
 --auto-attach AUTO_ATTACH           Auto attach subscriptions upon registration
                                     One of true/false, yes/no, 1/0.
 --content-view[-id]                 Content view name/id
 --description DESCRIPTION           Description
 --environment[-id]                  (--environment-id is deprecated: Use --lifecycle-environment-id instead)
 --lifecycle-environment[-id]        Name/Id of associated lifecycle environment
  ...output omitted...