15.2. Configuring the Satellite Capsule Discovery Plug-in

Ensure the foreman_url setting exists in the Satellite Capsule configuration file. The setting can appear as follows:
# grep foreman_url /etc/foreman-proxy/settings.yml
:foreman_url: https://satellite.example.com
The capsule-installer command configures this variable automatically, but Red Hat recommends that you check that the host responds correctly and there are no firewall rules blocking communication.

15.2.1. Configuring Discovery Subnets

You need to configure all subnets with discovered hosts to communicate through the Satellite Capsule. In the Satellite web UI, navigate to InfrastructureSubnets and select the required Capsule for each subnet that needs to perform host discovery and ensure it is connected to the Discovery Capsule.
To verify that a Capsule has the Discovery plug-in enabled, navigate to InfrastructureCapsules. The Discovery plug-in should appear in the list of features associated with the Capsule. Click Refresh features to ensure that the list is up-to-date.

15.2.2. Using Hammer with the Discovery Plug-in

To use the hammer command with the Discovery plug-in, you need to enable the Discovery plug-in in /etc/hammer/cli.modules.d/foreman_discovery.yml as follows:
:foreman_discovery:
  :enable_module: true
See hammer configuration directories[5] for more information about the files and directories that hammer uses.

15.2.3. Reviewing User Permissions

When it first starts, the Satellite Capsule Discovery plug-in creates a role called Discovery. You can assign this role to non-administrative users to allow them to use the Discovery plug-in. Alternatively, assign the perform_discovery permission to an existing role. For more information on roles and permissions, see Section 17.3, “Creating and Managing Roles”.