此内容没有您所选择的语言版本。
Hammer CLI Guide
Using Hammer, the Satellite's CLI tool
Abstract
Chapter 1. Introduction to Hammer 复制链接链接已复制到粘贴板!
Hammer is a powerful command-line tool provided with Red Hat Satellite 6. You can use Hammer to configure and manage a Red Hat Satellite Server either through CLI commands or automation in shell scripts. Hammer also provides an interactive shell.
Hammer compared to Satellite web UI
Compared to navigating the web UI, using Hammer can result in much faster interaction with the Satellite Server, as common shell features such as environment variables and aliases are at your disposal. You can also incorporate Hammer commands into reusable scripts for automating tasks of various complexity. Output from Hammer commands can be redirected to other tools, which allows for integration with your existing environment. You can issue Hammer commands directly on the base operating system running Red Hat Satellite.
Access to Satellite Server’s base operating system is required to issue Hammer commands, which can limit the number of potential users compared to the web UI. Although the parity between Hammer and the web UI is almost complete, the web UI has development priority and can be ahead especially for newly introduced features.
Hammer compared to Satellite API
For many tasks, both Hammer and Satellite API are equally applicable. Hammer can be used as a human friendly interface to Satellite API, for example to test responses to API calls before applying them in a script (use the -d option to inspect API calls issued by Hammer, for example hammer -d organization list). Changes in the API are automatically reflected in Hammer, while scripts using the API directly have to be updated manually.
In the background, each Hammer command first establishes a binding to the API, then sends a request. This can have performance implications when executing a large number of Hammer commands in sequence. In contrast, a script communicating directly with the API establishes the binding only once. See the API Guide for more information.
1.1. Getting Help 复制链接链接已复制到粘贴板!
View the full list of hammer options and subcommands by executing:
hammer --help
$ hammer --help
Use --help to inspect any subcommand, for example:
hammer organization --help
$ hammer organization --help
You can search the help output using grep, or redirect it to a text viewer, for example:
hammer | less
$ hammer | less
1.2. Authentication 复制链接链接已复制到粘贴板!
A Satellite user must prove their identity to Red Hat Satellite when entering hammer commands. Hammer commands can be run manually or automatically. In either case, hammer requires Satellite credentials for authentication. There are three methods of hammer authentication:
- Hammer authentication session
- Storing credentials in the hammer configuration file
- Providing credentials with each hammer command
The hammer configuration file method is recommended when running commands automatically. For example, running Satellite maintenance commands from a cron job. When running commands manually, the hammer authentication session and providing credentials with each command are recommended.
1.2.1. Hammer Authentication Session 复制链接链接已复制到粘贴板!
Hammer authentication session is a cache that stores your credentials, and you have to provide them only once, at the beginning of the session. This method is suited to running several hammer commands in succession, for example a script containing hammer commands. In this scenario, you enter your Satellite credentials once, and the script runs as expected. By using the hammer authentication session, you avoid storing your credentials in the script itself and in the ~/.hammer/cli.modules.d/foreman.yml hammer configuration file.
See the instructions on how to use the sessions:
To enable sessions, add
:use_sessions: trueto the~/.hammer/cli.modules.d/foreman.ymlfile::foreman: :use_sessions: true
:foreman: :use_sessions: trueCopy to Clipboard Copied! Toggle word wrap Toggle overflow Note that if you enable sessions, credentials stored in the configuration file will be ignored.
To start a session, enter the following command:
hammer auth login
# hammer auth loginCopy to Clipboard Copied! Toggle word wrap Toggle overflow You are prompted for your Satellite credentials, and logged in. You will not be prompted for the credentials again until your session expires.
The default length of a session is 60 minutes. You can change the time to suit your preference. For example, to change it to 30 minutes, enter the following command:
hammer settings set --name idle_timeout --value 30 Setting [idle_timeout] updated to [30]
# hammer settings set --name idle_timeout --value 30 Setting [idle_timeout] updated to [30]Copy to Clipboard Copied! Toggle word wrap Toggle overflow To see the current status of the session, enter the following command:
hammer auth status
# hammer auth statusCopy to Clipboard Copied! Toggle word wrap Toggle overflow To end the session, enter the following command:
hammer auth logout
# hammer auth logoutCopy to Clipboard Copied! Toggle word wrap Toggle overflow
1.2.2. Hammer Configuration File 复制链接链接已复制到粘贴板!
If you ran the Satellite installation with --foreman-admin-username and --foreman-admin-password options, credentials you entered are stored in the ~/.hammer/cli.modules.d/foreman.yml configuration file, and hammer does not prompt for your credentials.
You can also add your credentials to the ~/.hammer/cli.modules.d/foreman.yml configuration file manually:
:foreman: :username: 'username' :password: 'password'
:foreman:
:username: 'username'
:password: 'password'
Use only spaces for indentation in hammer configuration files. Do not use tabs for indentation in hammer configuration files.
1.2.3. Command Line 复制链接链接已复制到粘贴板!
If you do not have your Satellite credentials saved in the ~/.hammer/cli.modules.d/foreman.yml configuration file, hammer prompts you for them each time you enter a command. You can specify your credentials when executing a command as follows:
hammer -u username -p password subcommands
$ hammer -u username -p password subcommands
Examples in this guide assume having saved credentials in the configuration file, or using a hammer authentication session.
1.3. Using Standalone Hammer 复制链接链接已复制到粘贴板!
You can install hammer on a host that has no Satellite Server Server installed, and use it to connect the host to a remote Satellite.
Prerequisites
- Ensure that you register the host to Satellite Server or Capsule Server. For more information, see Registering a Host in the Provisioning Guide.
Ensure that you synchronize the following repositories on Satellite Server or Capsule Server. For more information, see Synchronizing Red Hat Repositories in the Content Management Guide.
-
rhel-7-server-rpms -
rhel-server-rhscl-7-rpms -
rhel-7-server-satellite-tools-6.3-rpms
-
Procedure
On a host, complete the following steps to install hammer:
Enable the Red Hat Enterprise Linux, Red Hat Software Collections and Red Hat Satellite Tools repositories:
subscription-manager repos --enable=rhel-7-server-rpms \ --enable=rhel-server-rhscl-7-rpms \ --enable=rhel-7-server-satellite-tools-6.3-rpms
# subscription-manager repos --enable=rhel-7-server-rpms \ --enable=rhel-server-rhscl-7-rpms \ --enable=rhel-7-server-satellite-tools-6.3-rpmsCopy to Clipboard Copied! Toggle word wrap Toggle overflow Install
hammer:yum install tfm-rubygem-hammer_cli_katello
# yum install tfm-rubygem-hammer_cli_katelloCopy to Clipboard Copied! Toggle word wrap Toggle overflow Edit the
:host:entry in the/etc/hammer/cli.modules.d/foreman.ymlfile to include the Satellite IP address or FQDN.:host: 'https://satellite.example.com'
:host: 'https://satellite.example.com'Copy to Clipboard Copied! Toggle word wrap Toggle overflow
1.4. Setting a Default Organization 复制链接链接已复制到粘贴板!
Many hammer commands are organization specific. You can set a default organization for hammer commands so that you do not have to specify it every time using the --organization or --organization-id parameter. To set a default organization, enter one of the following commands:
hammer defaults add --param-name organization --param-value org_name hammer defaults add --param-name organization_id --param-value org_ID
$ hammer defaults add --param-name organization --param-value org_name
$ hammer defaults add --param-name organization_id --param-value org_ID
You can find org_ID in the output of the hammer organization list command.
Similarly, you can set the default location by specifying its name or ID. To do so, enter one of the following commands:
hammer defaults add --param-name location --param-value loc_name hammer defaults add --param-name location_id --param-value loc_ID
$ hammer defaults add --param-name location --param-value loc_name
$ hammer defaults add --param-name location_id --param-value loc_ID
To view the currently specified default settings, enter the following command:
hammer defaults list
$ hammer defaults list
Specifying a default organization is useful when you mostly manage a single organization, as it makes your commands shorter. However, when switching to a different organization, you still have to use a command-line option to specify it. Examples in this guide do not assume a saved default organization, instead they use the shell variable approach described in Section 2.1.2, “Identifying an Organization in a Hammer Command”.
1.5. Configuring Hammer 复制链接链接已复制到粘贴板!
The default location for global hammer configuration is:
-
/etc/hammer/cli_config.yml for general
hammersettings. - /etc/hammer/cli.modules.d/ for CLI module configuration files.
You can set user specific directives for hammer (in ~/.hammer/cli_config.yml) as well as for CLI modules (in respective .yml files under ~/.hammer/cli.modules.d/).
To see the order in which configuration files are loaded, as well as versions of loaded modules, issue:
hammer -d --version
$ hammer -d --version
Loading configuration for many CLI modules can slow down the execution of hammer commands. In such a case, consider disabling CLI modules that are not regularly used.
Apart from saving credentials as described in Section 1.2, “Authentication”, you can set several other options in the ~/.hammer/ configuration directory. For example, you can change the default log level and set log rotation with the following directives in ~/.hammer/cli_config.yml. Note that these directives affect only the current user and are not applied globally.
:log_level: 'warning' :log_size: 5 #in MB
:log_level: 'warning'
:log_size: 5 #in MB
Similarly, you can set the number of lines displayed at once in the hammer output (equivalent of the --per-page option):
:per-page: 30
:per-page: 30
1.6. Configuring Hammer Logging 复制链接链接已复制到粘贴板!
You can set hammer to log debugging information for various Satellite components.
You can set debug or normal configuration options for all Satellite components.
After changing hammer’s logging behavior, you must restart Satellite services.
katello-service restart
# katello-service restart
To set debug level for all components, use the following command:
hammer admin logging --all --level-debug katello-service restart
# hammer admin logging --all --level-debug # katello-service restartCopy to Clipboard Copied! Toggle word wrap Toggle overflow To set production level logging, use the following command:
hammer admin logging --all --level-production katello-service restart
# hammer admin logging --all --level-production # katello-service restartCopy to Clipboard Copied! Toggle word wrap Toggle overflow To list the currently recognized components, that you can set logging for:
hammer admin logging --list
# hammer admin logging --listCopy to Clipboard Copied! Toggle word wrap Toggle overflow To list all available logging options:
hammer admin logging --help Usage: hammer admin logging [OPTIONS]# hammer admin logging --help Usage: hammer admin logging [OPTIONS]Copy to Clipboard Copied! Toggle word wrap Toggle overflow
1.7. Invoking the Hammer Shell 复制链接链接已复制到粘贴板!
You can issue hammer commands through the interactive shell. To invoke the shell, issue the following command:
hammer shell
$ hammer shell
In the shell, you can enter subcommands directly without typing "hammer", which can be useful for testing commands before using them in a script. To exit the shell, type exit or press [Ctrl + D].
1.8. Generating Formatted Output 复制链接链接已复制到粘贴板!
You can modify the default formatting of the output of hammer commands to simplify the processing of this output by other command line tools and applications. For example, to list organizations in a CSV format with a custom separator (in this case a semicolon), issue the following command:
hammer --csv --csv-separator ";" organization list
$ hammer --csv --csv-separator ";" organization list
Output in CSV format is useful for example when you need to parse IDs and use them in a for loop (see Example 2.6, “Synchronizing All Repositories in ACME Organization” or Example 2.8, “Assigning a Synchronization Plan to Multiple Products”).
Several other formatting options are available with the --output option:
hammer --output output_format organization list
$ hammer --output output_format organization list
Replace output_format with one of:
-
table— generates output in the form of a human readable table (default). -
base— generates output in the form of key-value pairs. -
yaml— generates output in the YAML format. -
csv— generates output in the Comma Separated Values format. To define a custom separator, use the--csvand--csv-separatoroptions instead. -
json— generates output in the JavaScript Object Notation format. -
silent— suppresses the output.
1.9. Troubleshooting with Hammer 复制链接链接已复制到粘贴板!
You can use the hammer ping command to check the status of core Satellite services. Together with the katello-service status command, this can help you to diagnose and troubleshoot Satellite issues. If all services are running as expected, the output looks as follows:
You can use hammer to create, edit, and manage organizations, locations, and repositories. For web UI equivalents of the following procedures see Creating Organizations and Importing Red Hat Content in the Content Management Guide.
2.1. Organizations 复制链接链接已复制到粘贴板!
Organization in Red Hat Satellite is an isolated collection of systems, content, and other functionality within a Satellite deployment. This section shows how to create and modify organizations using hammer.
2.1.1. Creating an Organization 复制链接链接已复制到粘贴板!
Use the following command to create an organization:
hammer organization create \ --name "org_name" \ --label "org_label" \ --description "org_description"
$ hammer organization create \
--name "org_name" \
--label "org_label" \
--description "org_description"
Where:
- org_name is the name of the organization. This parameter is required.
-
org_label is the organization label used in command-line applications such as
subscription-manager. Labels cannot contain white space and you cannot change them later. If not specified, label is generated automatically from the organization name (white space is replaced with underscores). - org_description is a short description of the organization. This parameter is not required, but it can help you to manage a large number of organizations.
You can fully configure an organization while creating it (issue hammer organization create --help to see the options). Also, you can modify an existing organization using the hammer organization update command.
Example 2.1. Creating and Updating ACME Organization
The following example shows how to create an organization named ACME:
ORG="ACME" hammer organization create \ --name $ORG \ --description "Example_organization"
$ ORG="ACME"
$ hammer organization create \
--name $ORG \
--description "Example_organization"
This command assigns a compute resource to the organization:
hammer organization update \ --name $ORG \ --compute-resource-ids 1
$ hammer organization update \
--name $ORG \
--compute-resource-ids 1
2.1.2. Identifying an Organization in a Hammer Command 复制链接链接已复制到粘贴板!
Many tasks you can perform in the Satellite Server are specific to an organization. Hammer commands provide three ways to identify an organization: by using the organization, organization-label, or organization-id option. To find the organization ID, use the following command:
hammer organization list
$ hammer organization list
If your organization name is long, consider storing it in a shell variable. You can use this variable in Hammer commands. For example:
ORG = "Red Hat Enterprise Linux Developer Team" hammer product list --organization $ORG
$ ORG = "Red Hat Enterprise Linux Developer Team"
$ hammer product list --organization $ORG
This approach is used in examples in this guide.
If you mostly manage a single organization, you can set it as default. For information on how to do that, see Section 1.4, “Setting a Default Organization”.
2.1.3. Uploading a Manifest 复制链接链接已复制到粘贴板!
A Subscription Manifest transfers subscriptions from the Red Hat Customer Portal to Satellite Server. First, generate the manifest on the Red Hat Customer portal as described in the Creating a Subscription Manifest in the Content Management Guide. Then upload the manifest to the organization as follows:
hammer subscription upload \ --organization-label org_label \ --file path_to_manifest
$ hammer subscription upload \
--organization-label org_label \
--file path_to_manifest
Example 2.2. Uploading a Manifest to ACME Organization
The following example shows how to upload a Subscription Manifest file to the ACME organization (assuming the organization name is stored in a shell variable):
hammer subscription upload --organization $ORG --file /tmp/manifest.zip
$ hammer subscription upload --organization $ORG --file /tmp/manifest.zip
To view the subscriptions imported with the manifest, issue:
hammer subscription list --organization $ORG
$ hammer subscription list --organization $ORG
2.2. Locations 复制链接链接已复制到粘贴板!
Location in Red Hat Satellite is collection of default settings that represent a physical place. This section shows how to create locations using hammer.
2.2.1. Creating a Location 复制链接链接已复制到粘贴板!
Use the following command to create a location:
hammer location create --name location_name
$ hammer location create --name location_name
Example 2.3. Creating Multiple Locations Using a Script
The following Bash script creates three locations (london, munich, boston), and assigns them to the ACME organization.
Run hammer location --help to view all possible location related operations.
2.3. Repositories 复制链接链接已复制到粘贴板!
Repository provides storage for a collection of content. This section shows how to enable and synchronize repositories using hammer.
2.3.1. Enabling a Repository 复制链接链接已复制到粘贴板!
Before enabling a Red Hat repository, you need to know its name, the name of the product it provides, the base architecture, and the release version. Use the following command to enable a repository:
Example 2.4. Enabling a Red Hat Enterprise Linux Repository
The following command enables the Red Hat Enterprise Linux 7 Server repository for the organization:
Run hammer repository-set --help to view all possible repository related operations. Also see hammer repository --help.
2.3.2. Synchronizing a Repository 复制链接链接已复制到粘贴板!
By synchronizing a repository you pull its content from Red Hat Customer Portal to the Satellite Server. To synchronize a repository you need to specify its name and a product name:
hammer repository synchronize \ --product "product_name" \ --name "repo_name" \ --organization-label org_label \ --async
$ hammer repository synchronize \
--product "product_name" \
--name "repo_name" \
--organization-label org_label \
--async
Note that if you have created Content Views, multiple repositories with the same name can exist within a single organization. In such a case, use the --id option to identify the repository you want to synchronize (issue hammer repository list to find repository IDs).
Example 2.5. Synchronizing a Red Hat Enterprise Linux Repository
The following command performs a single synchronization of the Red Hat Enterprise Linux 7 Server repository in the organization:
hammer repository synchronize \ --product "Red Hat Enterprise Linux Server" \ --name "Red Hat Enterprise Linux 7 Server (RPMs)" \ --organization $ORG \ --async
$ hammer repository synchronize \
--product "Red Hat Enterprise Linux Server" \
--name "Red Hat Enterprise Linux 7 Server (RPMs)" \
--organization $ORG \
--async
The task ID is displayed after executing the above command:
Repository is being synchronized in task 640bb71f-0ce5-40a3-a675-425a4acacceb
Repository is being synchronized in task 640bb71f-0ce5-40a3-a675-425a4acacceb
To view the progress of the task, issue:
hammer task progress --id 640bb71f-0ce5-40a3-a675-425a4acacceb
$ hammer task progress --id 640bb71f-0ce5-40a3-a675-425a4acacceb
After finishing the first synchronization, the repository is added to the list of repositories mirrored on Satellite Server. Execute the following command to see the list:
hammer repository list --organization $ORG
$ hammer repository list --organization $ORG
You can also synchronize all repositories within a product as follows:
hammer product synchronize \ --organization-label org_label \ --name "product_name" \ --async
$ hammer product synchronize \
--organization-label org_label \
--name "product_name" \
--async
With the --async option, the repository synchronization runs in the background, which for example allows you to enable and synchronize several repositories in parallel.
Example 2.6. Synchronizing All Repositories in ACME Organization
The following Bash script synchronizes all repositories within the ACME organization.
2.3.3. Creating a Synchronization Plan 复制链接链接已复制到粘贴板!
Product in Red Hat Satellite is a collection of repositories that acts as the smallest unit of the synchronization process. You can create a synchronization plan to automatically update repositories of a selected product in a given time interval.
To define a synchronization plan, issue the following command:
Replace repetition_interval with hourly, daily, or weekly. Replace initial_sync with the date and time of the initial synchronization in the form of "YYYY-MM-DD HH:MM:SS".
Example 2.7. Creating a Synchronization Plan
The following command creates a daily synchronization schedule for the ACME organization, that runs at 3 a.m., starting from 15 January 2016:
To associate the synchronization plan with a product, issue the following command:
hammer product set-sync-plan \ --organization-label org_label \ --name "product_name" \ --sync-plan "sync_plan_name"
$ hammer product set-sync-plan \
--organization-label org_label \
--name "product_name" \
--sync-plan "sync_plan_name"
Example 2.8. Assigning a Synchronization Plan to Multiple Products
The following Bash script selects the products in the ACME organization that have been synchronized at least once and contain at least one repository and assigns them a synchronization plan named "daily sync at 3 a.m.".
After executing the script, issue the following command to see which products have been assigned the synchronization plan:
hammer product list --organization $ORG --sync-plan "daily sync at 3 a.m."
$ hammer product list --organization $ORG --sync-plan "daily sync at 3 a.m."
To view synchronization plans available for a selected organization, issue the following command:
hammer sync-plan list --organization-label org_label
$ hammer sync-plan list --organization-label org_label
For more details on working with products and synchronization plans see the output of hammer sync-plan --help and hammer product --help.
2.3.4. Creating a Custom Repository 复制链接链接已复制到粘贴板!
After enabling a Red Hat repository, the corresponding product is created automatically. To enable a repository with custom packages, you first need to manually create a product for this repository.
Use the following command to create a custom product:
hammer product create --name "product_name" --organization-label org_label
$ hammer product create --name "product_name" --organization-label org_label
The following command creates a new repository under the custom product:
Replace the example values with your own details, in particular:
-
cont_type specifies the type of content in the repository, choose one of
yum,puppet, ordocker. - repo_url specifies the URL on which the repository will be available, valid only if ` --publish-via-http` is enabled.
To upload packages to a custom repository, issue the following command:
hammer repository upload-content \ --product "product_name" \ --organization-label org_label \ --id "repo_id" \ --path path_to_dir
$ hammer repository upload-content \
--product "product_name" \
--organization-label org_label \
--id "repo_id" \
--path path_to_dir
Replace path_to_dir with the path to the directory with content (RPM packages, Puppet modules, or Docker images) to be added to the custom repository.
Chapter 3. Managing Content Life Cycle 复制链接链接已复制到粘贴板!
This section shows how to use hammer to create Content Views and to promote them through life cycle environments.
3.1. Creating a Life Cycle Environment 复制链接链接已复制到粘贴板!
Life cycle environments represent stages of the content life cycle. This section shows how to view and create life cycle environments with hammer. By default, the Library environment is present for each organization. Use the following syntax to create a new life cycle environment:
hammer lifecycle-environment create \ --name env_name \ --description "env_description" \ --organization-label org_label \ --prior prior_env_name
$ hammer lifecycle-environment create \
--name env_name \
--description "env_description" \
--organization-label org_label \
--prior prior_env_name
Example 3.1. Creating a Life Cycle Environment
This example shows how to create a new environment based on Library for the ACME organization (assuming the organization name is stored in a shell variable):
hammer lifecycle-environment create \ --name Development \ --description "Initial testing" \ --organization $ORG \ --prior Library
$ hammer lifecycle-environment create \
--name Development \
--description "Initial testing" \
--organization $ORG \
--prior Library
You can create another life cycle environment based on Development using the --prior option.
To view existing life cycle environments, issue the following command:
hammer lifecycle-environment list --organization-label org_label
$ hammer lifecycle-environment list --organization-label org_label
The output of the above command can look as follows:
For more information on commands related to life cycle environments, see the output of hammer lifecycle-environment --help.
3.2. Creating a Content View 复制链接链接已复制到粘贴板!
Content Views are subsets of content from the Library created by intelligent filtering. You can publish and promote Content Views into life cycle environments that make content available for different uses (typically Dev, QA, and Production). To create a Content View, issue the following command:
hammer content-view create \ --name cv_name \ --repository-ids repo_ID1,repo_ID2,repo_ID3 \ --description "cv_description" \ --organization-label org_label
$ hammer content-view create \
--name cv_name \
--repository-ids repo_ID1,repo_ID2,repo_ID3 \
--description "cv_description" \
--organization-label org_label
The --repository-ids option adds the selected repositories to the Content View, use the hammer repository list command to find the IDs. It is also possible to omit this option to create an empty Content View that you can modify later using the update or add-repository subcommands.
Example 3.2. Creating a Content View
The following example creates a Content View under the ACME organization and assigns it three repositories:
hammer content-view create \ --name cv-rhel7-server \ --repository-ids 1,2,3 \ --description "Initial CV for RHEL 7" \ --organization $ORG
$ hammer content-view create \
--name cv-rhel7-server \
--repository-ids 1,2,3 \
--description "Initial CV for RHEL 7" \
--organization $ORG
Example 3.3. Creating a Composite Content View
A Composite Content View is comprised of one or more Content Views. This example shows how to create a Composite Content View from two existing Content Views:
hammer content-view create \ --name ccv-rhel7-server-scl \ --description "CCV for RHEL7 and Software Collections" \ --organization $ORG \ --composite --component-ids 2,6
$ hammer content-view create \
--name ccv-rhel7-server-scl \
--description "CCV for RHEL7 and Software Collections" \
--organization $ORG \
--composite --component-ids 2,6
Find the IDs for the --component-ids option by executing hammer content-view list.
There are three content types you can add to the Content View: RPM packages, Puppet modules, and Docker images.
3.2.1. Adding Repositories to a Content View 复制链接链接已复制到粘贴板!
Use the following command to add repositories to an existing Content View:
hammer content-view update \ --repository-ids repo_ID1,repo_ID2... \ --name cv_name \ --organization-label org_label
$ hammer content-view update \
--repository-ids repo_ID1,repo_ID2... \
--name cv_name \
--organization-label org_label
The above command is useful for populating an empty Content View with repositories. Note that it will overwrite any existing repositories, therefore to increase the number of repositories in a Content View, use:
hammer content-view add-repository \ --organization-label org_label \ --name cv_name \ --repository-id repo_ID
$ hammer content-view add-repository \
--organization-label org_label \
--name cv_name \
--repository-id repo_ID
Similarly, you can use the remove-repository subcommand to remove a repository from the Content View. Use hammer content-view info to inspect repositories in a Content View.
Example 3.4. Filtering Packages for a Content View – Excluding a Package
Filters allow you to select a subset of packages from a repository (either by including or excluding) to create customized Content Views. This example shows how to create a filter to exclude the emacs package from the cv-rhel7-server Content View.
First create a filter for the Content View in the organization:
Find the repository IDs by executing hammer repository list. Create a rule to exclude packages with name starting with "emacs" and add it to the filter as follows:
hammer content-view filter rule create \ --name "emacs*" \ --organization $ORG \ --content-view cv-rhel7-server \ --content-view-filter exclude-emacs
$ hammer content-view filter rule create \
--name "emacs*" \
--organization $ORG \
--content-view cv-rhel7-server \
--content-view-filter exclude-emacs
As a result, hosts using the cv-rhel7-server Content View will not have access to the emacs package. You can add multiple rules to a filter, see the output hammer content-view rule create --help for the full list of filtering parameters. To inspect rules present in a filter, issue the following command:
hammer content-view filter rule list \ --content-view cv-rhel7-server \ --content-view-filter exclude-emacs \ --organization $ORG
$ hammer content-view filter rule list \
--content-view cv-rhel7-server \
--content-view-filter exclude-emacs \
--organization $ORG
Example 3.5. Filtering Packages for a Content View – Limiting Errata by Date
This example shows how to create a filter to exclude errata released before a specific date from the cv-rhel7-server Content View. For more information on errata management see Chapter 8, Managing Errata. Create a filter for the Content View as follows:
Create a rule to exclude errata with a name starting with "emacs" and add it to the filter as follows:
3.2.2. Adding Puppet Modules to a Content View 复制链接链接已复制到粘贴板!
To add a Puppet module to a Content View, first upload this module to a Puppet repository within a custom product. Use the commands from Section 2.3.4, “Creating a Custom Repository” to create a product with a repository, and to upload a Puppet module to the repository.
To add a Puppet module to a Content View, issue the following command:
hammer content-view puppet-module add \ --content-view cv_name \ --name module_name
$ hammer content-view puppet-module add \
--content-view cv_name \
--name module_name
Example 3.6. Adding a Puppet Module to a Content View
This example shows how to add a Puppet module from an external source to the cv-rhel7-server Content View.
Download the concat module (that constructs files from multiple text fragments) from Puppet Forge:
wget -O /tmp/puppetlabs-concat-1.2.5.tar.gz https://forgeapi.puppetlabs.com /v3/files/puppetlabs-concat-1.2.3.tar.gz
$ wget -O /tmp/puppetlabs-concat-1.2.5.tar.gz https://forgeapi.puppetlabs.com /v3/files/puppetlabs-concat-1.2.3.tar.gzCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create a Puppet repository under the ACME-puppet product and upload the module to this repository (the example assumes repository ID is 6):
hammer product create \ --name "ACME-puppet" \ --organization $ORG
$ hammer product create \ --name "ACME-puppet" \ --organization $ORGCopy to Clipboard Copied! Toggle word wrap Toggle overflow Copy to Clipboard Copied! Toggle word wrap Toggle overflow hammer repository upload-content \ --organization $ORG \ --product ACME-puppet \ --id 6 \ --path /tmp/puppetlabs-concat-1.2.5.tar.gz
$ hammer repository upload-content \ --organization $ORG \ --product ACME-puppet \ --id 6 \ --path /tmp/puppetlabs-concat-1.2.5.tar.gzCopy to Clipboard Copied! Toggle word wrap Toggle overflow Add the module to the Content View using the
id,name, orauthorparameters. To find the exact values, enter:Copy to Clipboard Copied! Toggle word wrap Toggle overflow To add the module to the Content View, issue:
hammer content-view puppet-module add \ --name concat \ --content-view cv-rhel7-server \ --organization $ORG
$ hammer content-view puppet-module add \ --name concat \ --content-view cv-rhel7-server \ --organization $ORGCopy to Clipboard Copied! Toggle word wrap Toggle overflow To verify if the module has been added successfully, issue the following command:
hammer content-view puppet-module list \ --content-view cv-rhel7-server \ --organization $ORG
$ hammer content-view puppet-module list \ --content-view cv-rhel7-server \ --organization $ORGCopy to Clipboard Copied! Toggle word wrap Toggle overflow
3.2.3. Adding Docker Images to a Content View 复制链接链接已复制到粘贴板!
You can upload Docker images directly to the dedicated repository as follows:
hammer repository upload-content --path image_archive --id repo_id
$ hammer repository upload-content --path image_archive --id repo_id
Replace image_archive with a path to the archive containing the Docker image. Use repo_id to identify the repository of docker content type. Then you can add this repository to the Content View.
3.3. Publishing a Content View 复制链接链接已复制到粘贴板!
By publishing a Content View you make it visible and usable by hosts. Use the following command to publish a selected Content View:
hammer content-view publish \ --id cv_ID \ --organization-label org_label \ --async
$ hammer content-view publish \
--id cv_ID \
--organization-label org_label \
--async
Find the cv_ID of the Content View to be published in the output of the hammer content-view list command. Published Content Views become available in the Library environment. To verify the Content View status, issue the following command:
hammer content-view info --id cv_ID
$ hammer content-view info --id cv_ID
3.4. Promoting a Content View 复制链接链接已复制到粘贴板!
Promoting is the act of moving a Content View from one life cycle environment to another. To do so, issue the following command.
hammer content-view version promote \ --content-view cv_name \ --organization-label org_label \ --to-lifecycle-environment env_name
$ hammer content-view version promote \
--content-view cv_name \
--organization-label org_label \
--to-lifecycle-environment env_name
Here, env_name stands for the name of target life cycle environment.
Example 3.7. Promoting a Content View Through the Life Cycle Environment Path
The following Bash script promotes the selected Content View from Library through all life cycle environments in the ACME organization:
To verify if the Content View has been promoted correctly, issue the following command:
hammer content-view version info --id 1
$ hammer content-view version info --id 1
3.5. Performing an Incremental Update of a Content View 复制链接链接已复制到粘贴板!
Incremental updates enable modifying a published Content View without the need to promote a new Content View version through the life cycle environment. As a result of the incremental update, a new minor Content View version is created. Incremental updates are useful for fast emergency updates, you can use them to add errata, packages, or Puppet modules.
To create an incremental update adding new packages to a Content View, issue:
hammer content-view version incremental-update \ --content-view-version-id cv_ID \ --packages pkg_name1,pkg_name2 \ --lifecycle-environment-ids env_ID1, env_ID2,... \ --organization-id org_ID
$ hammer content-view version incremental-update \
--content-view-version-id cv_ID \
--packages pkg_name1,pkg_name2 \
--lifecycle-environment-ids env_ID1, env_ID2,... \
--organization-id org_ID
Find the Content View version ID in the output of hammer Content View version list. Instead of supplying packages with the --packages option, you can add Puppet modules with --puppet-modules, or errata with --errata-ids (see Example 3.8, “Adding Errata to a Content View using an Incremental Update”). For more information on working with incremental updates issue hammer content-view version incremental-update --help.
Example 3.8. Adding Errata to a Content View using an Incremental Update
This example shows how to apply an erratum to a host (named auth01.example.com) by creating an incremental update of its Content View:
hammer content-view version incremental-update \ --content-view-version-id 4 \ --errata-ids 8c3801f6-12a7-4a62-83f4-addbb1f34ce6 \ --lifecycle-environments Infrastructure \ --organization $ORG
$ hammer content-view version incremental-update \
--content-view-version-id 4 \
--errata-ids 8c3801f6-12a7-4a62-83f4-addbb1f34ce6 \
--lifecycle-environments Infrastructure \
--organization $ORG
To find the required information for the above command, perform the following steps:
Find the Organization ID and name by executing:
hammer organization list
$ hammer organization listCopy to Clipboard Copied! Toggle word wrap Toggle overflow Find the Content View your host is registered to as well as its life cycle environment by executing:
hammer host info --name auth01.example.com
$ hammer host info --name auth01.example.comCopy to Clipboard Copied! Toggle word wrap Toggle overflow Then find the current version of the Content View (assuming Content View name RHEL7_Infra):
hammer content-view info --name "RHEL7_Infra" --organization $ORG
$ hammer content-view info --name "RHEL7_Infra" --organization $ORGCopy to Clipboard Copied! Toggle word wrap Toggle overflow Find the IDs of errata you want to apply in the list of applicable errata in Library:
hammer erratum list --content-view-version-id 4 --organization $ORG hammer host errata list --host auth01.example.com
$ hammer erratum list --content-view-version-id 4 --organization $ORG $ hammer host errata list --host auth01.example.comCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Chapter 4. Managing Activation Keys 复制链接链接已复制到粘贴板!
Activation keys define the subscription properties of a host. Using an activation key improves the speed of host registration. For web UI equivalents of the following procedures see Managing Activation Keys in the Content Management Guide.
There are three possible use cases for activation keys:
-
Activation key with no subscriptions specified – hosts using the activation key search for the best fitting subscription. This is akin to running
subscription-manager --auto-attach. See Example 4.1, “Creating an Empty Activation Key”. - Activation key providing a custom subscription pool for auto attach – hosts using the activation key select the best fitting subscription from the list specified in the activation key. See Example 4.2, “Creating an Activation Key with Custom Subscription Pool”.
- Activation key with the exact set of subscriptions – hosts using the activation key are associated with all subscriptions specified in the activation key. See Example 4.3, “Creating an Activation Key with Mandatory Subscription List”.
Activation keys are only used when hosts are registered. If changes are made to an activation key, it is only applicable to hosts that are registered with the amended activation key in the future. The changes are not made to existing hosts.
To create an activation key, issue the following command:
hammer activation-key create --name ak_name \ --organization-label org_label \ --content-view cv_name \ --lifecycle-environment lc_name
$ hammer activation-key create --name ak_name \
--organization-label org_label \
--content-view cv_name \
--lifecycle-environment lc_name
Note that the Content View has to be published. To see the full list of operations related to activation keys, use the hammer activation-key --help command.
To add a subscription to the activation key, issue the following command:
hammer activation-key add-subscription \ --id ak_ID \ --subscription-id sub_ID
$ hammer activation-key add-subscription \
--id ak_ID \
--subscription-id sub_ID
To find the activation key ID, use hammer activation-key list; to find the subscription ID, use hammer subscription list.
Example 4.1. Creating an Empty Activation Key
This example shows how to create an activation key that directs the associated hosts to automatically attach a best fitting subscription:
hammer activation-key create \ --name "automatically attach key" \ --organization $ORG \ --content-view cv-rhel7-server \ --lifecycle-environment Testing
$ hammer activation-key create \
--name "automatically attach key" \
--organization $ORG \
--content-view cv-rhel7-server \
--lifecycle-environment Testing
As a result, hosts registered in the cv-rhel7-server Content View are associated with this activation key.
Example 4.2. Creating an Activation Key with Custom Subscription Pool
This example shows how to create an activation key that will direct the associated hosts to automatically attach a best fitting subscription from the list specified in the activation key.
First create an empty activation key:
hammer activation-key create \ --name "custom pool key" \ --organization $ORG \ --content-view cv-rhel7-server \ --lifecycle-environment Testing
$ hammer activation-key create \
--name "custom pool key" \
--organization $ORG \
--content-view cv-rhel7-server \
--lifecycle-environment Testing
Add a subscription to the activation key:
hammer activation-key add-subscription \ --name "custom pool key" \ --subscription-id 1
$ hammer activation-key add-subscription \
--name "custom pool key" \
--subscription-id 1
Keep repeating this step to add all required subscriptions to the activation key.
Example 4.3. Creating an Activation Key with Mandatory Subscription List
This example shows how to create an activation key that will direct the associated hosts to attach all subscriptions specified in the activation key.
First, create an activation key and add all required subscriptions to it. Follow the steps from Example 4.2, “Creating an Activation Key with Custom Subscription Pool”.
Then disable the auto-attach property of the activation key:
hammer activation-key update \ --organization $ORG \ --name "mandatory subs key" \ --auto-attach false
$ hammer activation-key update \
--organization $ORG \
--name "mandatory subs key" \
--auto-attach false
You can assign several activation keys to a Content View. In case of conflicting settings, the values from the last specified key take precedence. You can specify the order of precedence by setting a host group parameter as follows:
hammer hostgroup set-parameter \ --name kt_activation_keys \ --value name_of_first_key, name_of_second_key,... \ --hostgroup hostgroup_name
$ hammer hostgroup set-parameter \
--name kt_activation_keys \
--value name_of_first_key, name_of_second_key,... \
--hostgroup hostgroup_name
Chapter 5. Configuring Provisioning Environment 复制链接链接已复制到粘贴板!
This section shows how to configure various stages of your provisioning environment using hammer. For web UI equivalents of the following procedures see Configuring Provisioning Resources in the Provisioning Guide.
5.1. Domains 复制链接链接已复制到粘贴板!
Domains in Red Hat Satellite represent DNS zones. Satellite has the ability to assign domain names with Red Hat Satellite Capsule Server DNS. This provides users with a means to group and name hosts within a particular domain and associate them with parameters and Puppet variables.
To create a new domain, issue the following command:
hammer domain create --name domain_name
$ hammer domain create --name domain_name
You can associate the newly created domain to organizations and locations using the hammer organization add-domain or hammer location add-domain commands. To view the status of a domain, issue the following command:
hammer domain info --name domain_name
$ hammer domain info --name domain_name
5.2. Subnets 复制链接链接已复制到粘贴板!
Subnets in Red Hat Satellite define networks specified for groups of systems. Subnets use standard IP-address settings to define the network and use the Red Hat Satellite Capsule Server’s DHCP features to assign IP addresses to systems within the subnet. The following command contains the minimal set of options required for subnet creation:
Here, boot_mode is one of Static or DHCP, ipam is one of DHCP, Internal DB, or None. If using DHCP, you can set the IP range with the --from and --to options. For the full list of configurable options, see the output of the hammer subnet create --help command.
5.3. Architectures 复制链接链接已复制到粘贴板!
Architecture in Satellite represents a logical grouping of hosts and operating systems. To view the architectures, issue the following command:
hammer architecture list
$ hammer architecture list
Architectures are created by Satellite automatically when hosts are registered in Puppet, therefore it is rarely needed to create them manually (even though hammer provides this option).
5.4. Compute Resources 复制链接链接已复制到粘贴板!
Compute resources are hardware abstractions from virtualization and cloud providers. Satellite uses compute resources to provision virtual machines and containers. Run the following command to create a compute resource:
hammer compute-resource create \ --name cr_name \ --organization-ids org_ID1,org_ID2... \ --location-ids loc_ID1,loc_ID2... \ --provider provider
$ hammer compute-resource create \
--name cr_name \
--organization-ids org_ID1,org_ID2... \
--location-ids loc_ID1,loc_ID2... \
--provider provider
Here, provider is one of: RHEV, RHEL OpenStack Platform, Libvirt, Docker, Rackspace, Google, EC2, or VMware. Depending on the provider type, other options such as --url, or --user may be required. See the output of the hammer compute-resource create --help command for details.
5.5. Installation Media 复制链接链接已复制到粘贴板!
Installation media (ISO images) provide content for kickstart trees and new host installations in Red Hat Satellite. To list the media, issue the following command:
hammer medium list
$ hammer medium list
To add a new medium, issue the following command:
hammer medium create --name medium_name --path path_to_medium
$ hammer medium create --name medium_name --path path_to_medium
You can make the medium available to organizations and locations directly when adding it (see the output of the hammer medium create --help command), or later by using the hammer organization add-medium or hammer location add-medium commands.
5.6. Partition Tables 复制链接链接已复制到粘贴板!
Partition tables define the partitions and file system layout for new installations when provisioning systems. Red Hat Satellite provides default partition tables associated with operating system families, to view them, issue the following command:
hammer partition-table list
$ hammer partition-table list
To create a new partition table, issue the following command:
hammer partition-table create \ --name table_name \ --file path_to_layout_file \ --os-family os_family
$ hammer partition-table create \
--name table_name \
--file path_to_layout_file \
--os-family os_family
See the output of the hammer partition-table --help command for other subcommands.
5.7. Provisioning Templates 复制链接链接已复制到粘贴板!
Provisioning templates provide the systematic means to run unattended installations. To view the provisioning templates provided by Satellite, issue the following command:
hammer template list
$ hammer template list
To add a new template, issue the following command:
hammer template create --name template_name --file path_to_template_file
$ hammer template create --name template_name --file path_to_template_file
See the output of the hammer template --help command for other subcommands.
5.8. Operating Systems 复制链接链接已复制到粘贴板!
Operating systems define combinations of installation methods and media and are grouped within families. As a default, Red Hat Satellite uses a Red Hat family. Families allow Satellite to change certain behaviors when provisioning hosts. To list operating systems, issue the following command:
hammer os list
$ hammer os list
To create a new operating system, issue the following command:
hammer os create --name os_name --major version_number
$ hammer os create --name os_name --major version_number
Then you can add architectures, partition tables, installation media, and configuration templates to the operating system. See the output of the hammer os --help command for details.
Example 5.1. Updating Multiple Operating Systems
The following Bash script assigns each operating system a partition table (Kickstart default), configuration template (Kickstart default PXELinux), and provisioning template (Satellite Kickstart Default).
You can add grep commands to the for statement to further specify the affected operating systems. To verify if the assignment was performed correctly, use the hammer os info command.
5.9. Parameters 复制链接链接已复制到粘贴板!
Parameters define the behavior of Red Hat Satellite during provisioning. There are several types of parameters, see Parameters in the Puppet Guide for details. Use the following example to set a global parameter:
hammer global-parameter set --name param_name --value param_value
$ hammer global-parameter set --name param_name --value param_value
Example 5.2. Setting a Global Parameter to Disable the Firewall
Run the following command to set the firewall global option to disabled:
hammer global-parameter set --name firewall --value --disabled
$ hammer global-parameter set --name firewall --value --disabled
To verify the setting, issue the following command:
Similarly, you can use hammer to set other parameter types:
- To set domain parameters, use:
hammer domain set-parameter \ --name param_name \ --value param_value \ --domain domain_name
$ hammer domain set-parameter \
--name param_name \
--value param_value \
--domain domain_name
- To set host group parameters, use:
hammer hostgroup set-parameter \ --name param_name \ --value param_value \ --hostgroup hg_name
$ hammer hostgroup set-parameter \
--name param_name \
--value param_value \
--hostgroup hg_name
- To set host parameters, use:
hammer host set-parameter \ --name param_name \ --value param_value \ --host h_name
$ hammer host set-parameter \
--name param_name \
--value param_value \
--host h_name
- To update smart class parameters, use:
hammer sc-param \ --name param_name \ --default-value param_value
$ hammer sc-param \
--name param_name \
--default-value param_value
Chapter 6. Managing Hosts 复制链接链接已复制到粘贴板!
Host refers to any physical or virtual system Red Hat Satellite manages. This section shows how to create and configure hosts and host groups using hammer. For web UI equivalents of the following procedures see Managing Hosts.
6.1. Creating a Host Group 复制链接链接已复制到粘贴板!
A host group is a collection of hosts or host groups. It is recommended to create host groups to hold shared host parameters. Members of the host group inherit these parameters, therefore you do not have to set them individually during host creation. Note that you can nest host groups in a hierarchical manner.
The following command demonstrates a basic set of options for creating a host group:
See hammer hostgroup create --help for the full list of configurable options. There are two settings that cannot be configured during host group creation:
- An activation key has to be added afterwards using:
hammer hostgroup set-parameter \ --hostgroup "hostgroup_name" \ --name "kt_activation_keys" \ --value key_name
$ hammer hostgroup set-parameter \
--hostgroup "hostgroup_name" \
--name "kt_activation_keys" \
--value key_name
Run hammer activation-key list to find the activation key name (see Chapter 4, Managing Activation Keys for details on activation keys).
- The root password has to be specified when adding a host to the host group.
Example 6.1. Creating Host Groups for Multiple Content Views
The following Bash script creates a host group for each life cycle environment.
6.2. Creating a Host 复制链接链接已复制到粘贴板!
It is recommended to set general parameters in a host group to reduce the number of required options when creating a host. The following command creates a basic host associated to a host group:
After executing the above command you will be prompted to specify the root password. It is required to specify the host’s IP and MAC address, other properties of the primary network interface can be inherited from the host group or set using the subnet, and domain parameters. You can set additional interfaces using the --interface option, which accepts a list of key-value pairs. For the list of available interface settings, see Table 6.1, “Available Keys for the --interface Option”.
If you decide to create a host without host group membership, specify additional options described in Section 6.1, “Creating a Host Group”. There is a wide range of available host parameters, for details see the output of hammer host create --help. The value of certain parameters depends on the type of compute resource the host is provisioned on, see Table 6.2, “Host Options Specific to Provider” for reference.
| Keys | Description |
|---|---|
| type |
Defines the interface type, one of |
| name, identifier | Identification of the interface. |
| mac, ip, domain (or domain_id), subnet (or subnet_id) | Network settings, domain and subnet identification can be inherited from the host group. |
| primary, provision, managed, virtual |
Accept |
| Specific to virtual interfaces | |
| tag | VLAN tag, this attribute has precedence over the subnet VLAN ID. |
| attached_to | Identifier of the interface to which the virtual interface belongs, for example eth1. |
| Specific to bonded interfaces | |
| mode |
Bonding mode, one of |
| Specific to BMC interfaces | |
| provider |
BMC provider, set to |
| username, password | BMC access credentials. |
| Specific to hosts provisioned on Libvirt | |
| compute_type |
Interface type, one of |
| compute_network or compute_bridge | Specifies interface name, pick one depending on the interface type. |
| compute_model |
One of |
| Specific to hosts provisioned on RHEV | |
| compute_name | Interface name, for example eth0. |
| compute_network | Select one of the available networks for a cluster, use UUID from RHEV. |
| Specific to hosts provisioned on VMware | |
| compute_type | Type of the network adapter, depends on your version of vSphere. |
| compute_network | Network ID form VMware. |
| Provider | Keys |
|---|---|
| Keys for the --compute-attributes option | |
| EC2 | flavor_id, image_id, availability_zone, security_group_ids, managed_ip |
| GCE | machine_type, image_id, network, external_ip |
| Libvirt | cpus, memory, start |
| OpenStack | flavor_ref, image_ref, tenant_id, security_groups, network |
| RHEV | cluster, template, cores, memory, start |
| VMware | cpus, corespersocket, memory_mb, cluster, path, guest_id, scsi_controller_type, hardware_version, start |
| Keys for the --volume option | |
| Libvirt | poll_name, capacity, format_type |
| RHEV | size_gb, storage_domain, bootable |
| VMware | datastore, name, size_gb, thin, eager_zero |
Example 6.2. Creating a Host with a Bonded Interface Pair
The following example shows how to create a host with a bonded interface pair. For more information on interface bonding see Configure Network Bonding in the Red Hat Enterprise Linux Networking Guide.
6.3. Creating a Host Collection 复制链接链接已复制到粘贴板!
A host collection in Red Hat Satellite is a group of hosts. The following command shows the minimal set of options required to create a host collection:
hammer host-collection create \ --organization-label org_label \ --name hc_name
$ hammer host-collection create \
--organization-label org_label \
--name hc_name
To add hosts to a host collection, issue the following command:
hammer host-collection add-host \ --id hc_ID \ --host-ids ch_ID1,ch_ID2...
$ hammer host-collection add-host \
--id hc_ID \
--host-ids ch_ID1,ch_ID2...
Run the following command to associate a host collection with an activation key (see Chapter 4, Managing Activation Keys for details on activation keys):
hammer activation-key add-host-collection \ --id ak_ID \ --host-collection hc_name
$ hammer activation-key add-host-collection \
--id ak_ID \
--host-collection hc_name
Hosts grouped in the host collection now inherit the configuration from the activation key.
6.4. Running Remote Jobs on Hosts 复制链接链接已复制到粘贴板!
The remote execution feature enables defining arbitrary commands on the Satellite Server and executing them on remote hosts. Commands are defined in job templates that are similar to provisioning templates. Several job templates are included by default, you can use them or define a custom template for example to manipulate software packages or start a Puppet process on remote hosts. To use this feature in Hammer, install the remote execution CLI module by executing the following command as root:
yum install tfm-rubygem-hammer_cli_foreman_remote_execution
# yum install tfm-rubygem-hammer_cli_foreman_remote_execution
To list job templates available, issue:
hammer job-template list
$ hammer job-template list
To create a job template using a template-definition file, use a command as follows:
hammer job-template create \ --file "template" \ --name "template_name" \ --provider-type SSH \ --job-category "category_name"
$ hammer job-template create \
--file "template" \
--name "template_name" \
--provider-type SSH \
--job-category "category_name"
Replace template with the path to the file containing the template definition. Specify a custom category_name or select one of the existing categories (Commands, Katello, Packages, Power, Puppet, or Services). See the output of hammer job-template create --help for information on other available parameters.
To invoke a job with custom parameters, issue:
hammer job-invocation create \ --job-template "template_name" \ --inputs key1="value",key2="value",... \ --search-query "query"
$ hammer job-invocation create \
--job-template "template_name" \
--inputs key1="value",key2="value",... \
--search-query "query"
Specify the template name you want to use for the remote job. Specify inputs as a comma separated list of key-value pairs. Run hammer job-template info to see what parameters are required by your template. Replace query with the filter expression defining which hosts will be affected (for example "name ~ rex01").
Example 6.3. Starting the httpd Service on Selected Hosts
This example shows how to execute a remote job based on the default Service Action - SSH Default template, that will start the httpd service on hosts that have a name that contains "target".
hammer job-invocation create \ --job-template "Service Action - SSH Default" \ --inputs service="httpd",action="start" \ --search-query "name ~ target"
$ hammer job-invocation create \
--job-template "Service Action - SSH Default" \
--inputs service="httpd",action="start" \
--search-query "name ~ target"
To monitor the job output, issue:
hammer job-invocation output \ --id job_ID \ --host host_name
$ hammer job-invocation output \
--id job_ID \
--host host_name
Find the job_ID in the output of hammer job-invocation list. For more information on executing remote commands with hammer, issue hammer job-template --help or hammer job-invocation --help.
Chapter 7. Managing Users and Permissions 复制链接链接已复制到粘贴板!
For the administrator, Red Hat Satellite provides the ability to create, modify, and remove users. Also, it is possible to configure access permissions through assigning roles to users. This section shows how to perform these tasks using hammer. For web UI equivalents of the following procedures see Managing Users and Roles in Administering Red Hat Satellite.
7.1. Creating Users 复制链接链接已复制到粘贴板!
User in Red Hat Satellite defines a set of details for individuals using the system. To configure a user in Red Hat Satellite, hammer provides the user create and user update commands. Create a new user with the following command:
The --auth-source-id 1 setting means that the user is authenticated internally, you can specify an external authentication source as an alternative. Add the --admin option to grant administrator privileges to the user. Specifying organization IDs is not required, you can modify the user details later using the update subcommand.
For more information on user related subcommands see the output of hammer user --help.
7.2. Creating User Groups 复制链接链接已复制到粘贴板!
You can manage permissions of several users at once by organizing them into user groups. User groups themselves can be further grouped to create a hierarchy of permissions. Use the following command to create a new user group:
hammer user-group create --name usergroup_name
$ hammer user-group create --name usergroup_name
To add a user to a user group, issue the following command:
hammer user-group add-user --user user_name --id usergroup_id
$ hammer user-group add-user --user user_name --id usergroup_id
Find the user group ID by executing hammer user-group list. Similarly, you can add user groups using the add-user-group subcommand. For more information on operations related to user groups see the output of hammer user-group --help.
7.3. Creating Roles 复制链接链接已复制到粘贴板!
Roles in Red Hat Satellite define a set of permissions and access levels. Satellite provides a number of predefined roles, to view them, enter the following command:
hammer role list
$ hammer role list
To view permissions associated with a role, issue the following command:
hammer role filters --id role_id
$ hammer role filters --id role_id
Here, role_id is the ID of the role from the output of hammer role list.
To create a custom role, issue the following command:
hammer role create --name role_name
$ hammer role create --name role_name
Add a permission filter to the role with the following command:
hammer filter create \ --role role_name \ --permission-ids perm_ID1,perm_ID2...
$ hammer filter create \
--role role_name \
--permission-ids perm_ID1,perm_ID2...
Find the permissions to be added to the role by using hammer filter available-permissions. For details on roles and permissions see the output of hammer role --help and hammer filter --help.
Example 7.1. Granular Permission Filtering
Red Hat Satellite provides the ability to limit the configured user permissions to selected instances of a resource type. Use the --search option to limit permission filters, for example:
hammer filter create \ --permission-ids 91 \ --search "name ~ ccv*" \ --role qa-user
$ hammer filter create \
--permission-ids 91 \
--search "name ~ ccv*" \
--role qa-user
The above command adds to the qa-user role a permission to view, create, edit, and destroy Content Views that only applies to Content Views with name starting with ccv. See Granular Permission Filtering in Administering Red Hat Satellite for more information.
7.4. Assigning Roles to Users 复制链接链接已复制到粘贴板!
To assign a role to a user, issue the following command:
hammer user add-role --id user_id --role role_name
$ hammer user add-role --id user_id --role role_name
Similarly, you can assign a role to a user group:
hammer user-group add-role --id usergroup_id --role role_name
$ hammer user-group add-role --id usergroup_id --role role_name
7.5. Adding SSH Keys to a User 复制链接链接已复制到粘贴板!
The following steps show how to add public SSH keys to an existing user using the hammer. To create SSH keys or for more information, see Generating Key Pairs in the Red Hat Enterprise Linux 7 System Administrator’s Guide.
For web UI equivalents of the following procedures see Adding SSH keys to a User in Administering Red Hat Satellite.
Prerequisite
You need either the path to the public SSH key file, or the content of the public SSH key copied to the clipboard.
If you have the public SSH key file:
hammer user ssh-keys add --user-id user_id --name key_name --key-file ~/.ssh/id_rsa.pub
$ hammer user ssh-keys add --user-id user_id --name key_name --key-file ~/.ssh/id_rsa.pub
If you have the content of the public SSH key:
hammer user ssh-keys add --user-id user_id --name key_name --key ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNtYAAABBBHHS2KmNyIYa27Qaa7EHp+2l99ucGStx4P77e03ZvE3yVRJEFikpoP3MJtYYfIe8k 1/46MTIZo9CPTX4CYUHeN8= host@user
$ hammer user ssh-keys add --user-id user_id --name key_name --key ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNtYAAABBBHHS2KmNyIYa27Qaa7EHp+2l99ucGStx4P77e03ZvE3yVRJEFikpoP3MJtYYfIe8k 1/46MTIZo9CPTX4CYUHeN8= host@user
7.6. Deleting SSH Keys from a User 复制链接链接已复制到粘贴板!
To delete an SSH key from a user:
hammer user ssh-keys delete --id key_id --user-id user_id
$ hammer user ssh-keys delete --id key_id --user-id user_id
7.7. Viewing SSH Keys of a User 复制链接链接已复制到粘贴板!
To view an SSH key attached to a user:
hammer user ssh-keys info --id key_id --user-id user_id
$ hammer user ssh-keys info --id key_id --user-id user_id
To list SSH keys attached to a user:
hammer user ssh-keys list --user-id user_id
$ hammer user ssh-keys list --user-id user_id
Chapter 8. Managing Errata 复制链接链接已复制到粘贴板!
Software packages in Red Hat products are subject to updates, referred to as errata, that are released at regular intervals as well as asynchronously. This section shows how to inspect and apply errata using hammer. For web UI equivalents of the following procedures see Managing Errata in the Content Management Guide.
8.1. Inspecting Available Errata 复制链接链接已复制到粘贴板!
To view errata that are available for all organizations, issue the following command:
hammer erratum list
$ hammer erratum list
Example 8.1. Filtering Errata
The hammer erratum list command provides numerous options for filtering and ordering the output list. For example, to find an erratum that contains a specific security fix, issue:
hammer erratum list --cve CVE-2014-0453
$ hammer erratum list --cve CVE-2014-0453
The following command displays applicable errata for the selected product that contain the specified bugs ordered so that the security errata are displayed on top:
hammer erratum list \ --product-id 7 \ --search "bug = 1213000 or bug = 1207972" \ --errata-restrict-applicable 1 \ --order "type desc"
$ hammer erratum list \
--product-id 7 \
--search "bug = 1213000 or bug = 1207972" \
--errata-restrict-applicable 1 \
--order "type desc"
For more information on syntax used in the --search option, see Inspecting Available Errata in the Content Management Guide. For more information on filtering options implemented in hammer, see the output of hammer erratum list --help.
To view details of a specific erratum, issue the following command:
hammer erratum info --id erratum_ID
$ hammer erratum info --id erratum_ID
Replace erratum_ID with a unique identifier of the erratum found in the output of the hammer erratum list command. You can identify errata also by name and repository name, see the output of hammer erratum info --help for details.
8.2. Applying Errata to a Host 复制链接链接已复制到粘贴板!
To list errata available for a host, issue the following command:
hammer host errata list --host hostname
$ hammer host errata list --host hostname
To apply selected errata to the host, issue the following command:
hammer host errata apply \ --host hostname \ --errata-ids erratum_ID1,erratum_ID2...
$ hammer host errata apply \
--host hostname \
--errata-ids erratum_ID1,erratum_ID2...
Example 8.2. Applying All Available Errata to a Host
The following Bash script applies all errata available to a host (auth01.example.com):
HOST="auth01.example.com"
for i in $(hammer --csv host errata list --host $HOST | grep -vi '^ID' | awk -F, {'print $2'})
do
hammer host errata apply --host $HOST --errata-ids $i
done
HOST="auth01.example.com"
for i in $(hammer --csv host errata list --host $HOST | grep -vi '^ID' | awk -F, {'print $2'})
do
hammer host errata apply --host $HOST --errata-ids $i
done
Example 8.3. Applying a Security Advisory
This example shows how to apply a security fix to hosts using hammer:
Find the erratum that contains a fix for a selected issue (CVE-2015-3238):
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Verify if the security erratum (RHSA-2015:1640) is applicable for your host (auth01.example.com):
hammer host errata list \ --host auth01.example.com \ --search "RHSA-2015:1640"
$ hammer host errata list \ --host auth01.example.com \ --search "RHSA-2015:1640"Copy to Clipboard Copied! Toggle word wrap Toggle overflow Apply the erratum to the host:
hammer host errata apply \ --host auth01.example.com \ --errata-ids "RHSA-2015:1640"
$ hammer host errata apply \ --host auth01.example.com \ --errata-ids "RHSA-2015:1640"Copy to Clipboard Copied! Toggle word wrap Toggle overflow
You can use the following Bash script to apply a security erratum (for example RHSA-2015:1640) to all hosts where it is applicable:
To see if errata were applied successfully, find the corresponding task in the output of the following command:
hammer task list
$ hammer task list
To review the state of a selected task, issue the following command:
hammer task progress --id task_ID
$ hammer task progress --id task_ID
8.3. Applying Errata to a Host Collection 复制链接链接已复制到粘贴板!
To apply selected errata to a Host Collection, enter a command as follows:
hammer host-collection erratum install \ --errata "erratum_ID1,erratum_ID2,..." \ --name "my-collection" --organization $ORG
$ hammer host-collection erratum install \
--errata "erratum_ID1,erratum_ID2,..." \
--name "my-collection" --organization $ORG
This command is available in Red Hat Satellite 6.2.8 or later.
Chapter 9. Managing Docker Containers 复制链接链接已复制到粘贴板!
A Docker container is a sandbox for isolating applications. The container image stores the configuration for the container. This section shows how to use hammer to provision Docker containers. For web UI equivalents of the following procedures see Managing Containers in Managing Hosts.
In Red Hat Satellite, you can deploy containers only on a compute resource of the Docker provider type. See Preparing Container Hosts in Managing Hosts for instructions on how to prepare a container host. To register this host as a compute resource, issue the following command:
Use the following syntax to provision a container on the compute resource:
Find the compute resource ID in the output of hammer compute-resource list. Replace repo_name with the name of the synchronized repository that contains your docker images. This can be a custom repository pointing to Docker Hub or your internal registry (see Section 2.3.4, “Creating a Custom Repository”), or the official Red Hat image repository. If you provision from a Content View, replace repo_name with the name of the Content View. See Section 3.2.3, “Adding Docker Images to a Content View” for details on adding images to a Content View.
By starting a container you start the process specified with the --command option during the container creation. To start a container, issue the following command:
hammer docker container start --id container_ID
$ hammer docker container start --id container_ID
For the full list of container related options, see the output of the hammer docker container --help command.
Chapter 10. Reference 复制链接链接已复制到粘贴板!
This chapter provides a list of Hammer usage statements. These usage statements were current to the versions of Hammer and its components released for Satellite 6.3.
10.1. hammer activation-key 复制链接链接已复制到粘贴板!
Manipulate activation keys.
10.1.1. hammer activation-key add-host-collection 复制链接链接已复制到粘贴板!
Associate a resource
10.1.2. hammer activation-key add-subscription 复制链接链接已复制到粘贴板!
Add subscription
10.1.3. hammer activation-key content-override 复制链接链接已复制到粘贴板!
Override product content defaults
10.1.4. hammer activation-key copy 复制链接链接已复制到粘贴板!
Copy an activation key
10.1.5. hammer activation-key create 复制链接链接已复制到粘贴板!
Create an activation key
10.1.6. hammer activation-key delete 复制链接链接已复制到粘贴板!
Destroy an activation key
10.1.7. hammer activation-key host-collections 复制链接链接已复制到粘贴板!
List associated host collections
10.1.8. hammer activation-key info 复制链接链接已复制到粘贴板!
Show an activation key
10.1.9. hammer activation-key list 复制链接链接已复制到粘贴板!
List activation keys
10.1.10. hammer activation-key product-content 复制链接链接已复制到粘贴板!
List associated products
10.1.11. hammer activation-key remove-host-collection 复制链接链接已复制到粘贴板!
Disassociate a resource
10.1.12. hammer activation-key remove-subscription 复制链接链接已复制到粘贴板!
Remove subscription
10.1.13. hammer activation-key subscriptions 复制链接链接已复制到粘贴板!
List associated subscriptions
10.1.14. hammer activation-key update 复制链接链接已复制到粘贴板!
Update an activation key
10.2. hammer admin 复制链接链接已复制到粘贴板!
Administrative server-side tasks
10.2.1. hammer admin logging 复制链接链接已复制到粘贴板!
Logging verbosity level setup
10.3. hammer architecture 复制链接链接已复制到粘贴板!
Manipulate architectures.
10.3.1. hammer architecture add-operatingsystem 复制链接链接已复制到粘贴板!
Associate an operating system
10.3.2. hammer architecture create 复制链接链接已复制到粘贴板!
Create an architecture
10.3.3. hammer architecture delete 复制链接链接已复制到粘贴板!
Delete an architecture
10.3.4. hammer architecture info 复制链接链接已复制到粘贴板!
Show an architecture
10.3.5. hammer architecture list 复制链接链接已复制到粘贴板!
List all architectures
10.3.6. hammer architecture remove-operatingsystem 复制链接链接已复制到粘贴板!
Disassociate an operating system
10.3.7. hammer architecture update 复制链接链接已复制到粘贴板!
Update an architecture
10.4. hammer arf-report 复制链接链接已复制到粘贴板!
Manipulate compliance reports
10.4.1. hammer arf-report delete 复制链接链接已复制到粘贴板!
Delete an ARF Report
10.4.2. hammer arf-report download 复制链接链接已复制到粘贴板!
Download bzipped ARF report
10.4.3. hammer arf-report download-html 复制链接链接已复制到粘贴板!
Download ARF report in HTML
10.4.4. hammer arf-report info 复制链接链接已复制到粘贴板!
Show an ARF report
10.4.5. hammer arf-report list 复制链接链接已复制到粘贴板!
List ARF reports
10.5. hammer auth 复制链接链接已复制到粘贴板!
Foreman connection login/logout.
10.5.1. hammer auth login 复制链接链接已复制到粘贴板!
Set credentials
10.5.2. hammer auth logout 复制链接链接已复制到粘贴板!
Wipe your credentials
Usage:
hammer auth logout [OPTIONS]
Options:
-h, --help print help
Usage:
hammer auth logout [OPTIONS]
Options:
-h, --help print help
10.5.3. hammer auth status 复制链接链接已复制到粘贴板!
Information about current connections
Usage:
hammer auth status [OPTIONS]
Options:
-h, --help print help
Usage:
hammer auth status [OPTIONS]
Options:
-h, --help print help
10.6. hammer auth-source 复制链接链接已复制到粘贴板!
Manipulate auth sources.
10.6.1. hammer auth-source ldap 复制链接链接已复制到粘贴板!
Manage LDAP auth sources.
10.6.1.1. hammer auth-source ldap create 复制链接链接已复制到粘贴板!
Create an LDAP authentication source
10.6.1.2. hammer auth-source ldap delete 复制链接链接已复制到粘贴板!
Delete an LDAP authentication source
10.6.1.3. hammer auth-source ldap info 复制链接链接已复制到粘贴板!
Show an LDAP authentication source
10.6.1.4. hammer auth-source ldap list 复制链接链接已复制到粘贴板!
List all LDAP authentication sources
10.6.1.5. hammer auth-source ldap update 复制链接链接已复制到粘贴板!
Update an LDAP authentication source
10.7. hammer bootdisk 复制链接链接已复制到粘贴板!
Download boot disks
10.7.1. hammer bootdisk generic 复制链接链接已复制到粘贴板!
Download generic image
10.7.2. hammer bootdisk host 复制链接链接已复制到粘贴板!
Download host image
10.7.3. hammer bootdisk subnet 复制链接链接已复制到粘贴板!
Download subnet generic image
10.8. hammer capsule 复制链接链接已复制到粘贴板!
Manipulate capsule
10.8.1. hammer capsule content 复制链接链接已复制到粘贴板!
Manage the capsule content
Add lifecycle environments to the capsule
List the lifecycle environments not attached to the capsule
10.8.1.3. hammer capsule content cancel-synchronization 复制链接链接已复制到粘贴板!
Cancel running capsule synchronization.
10.8.1.4. hammer capsule content info 复制链接链接已复制到粘贴板!
Get current capsule synchronization status
10.8.1.5. hammer capsule content lifecycle-environments 复制链接链接已复制到粘贴板!
List the lifecycle environments attached to the capsule
Remove lifecycle environments from the capsule
10.8.1.7. hammer capsule content synchronization-status 复制链接链接已复制到粘贴板!
Get current capsule synchronization status
10.8.1.8. hammer capsule content synchronize 复制链接链接已复制到粘贴板!
Synchronize the content to the capsule
10.8.2. hammer capsule create 复制链接链接已复制到粘贴板!
Create a capsule
10.8.3. hammer capsule delete 复制链接链接已复制到粘贴板!
Delete a capsule
10.8.4. hammer capsule import-classes 复制链接链接已复制到粘贴板!
Import puppet classes from puppet Capsule.
10.8.5. hammer capsule info 复制链接链接已复制到粘贴板!
Show a capsule
10.8.6. hammer capsule list 复制链接链接已复制到粘贴板!
List all capsules
10.8.7. hammer capsule refresh-features 复制链接链接已复制到粘贴板!
Refresh capsule features
10.8.8. hammer capsule update 复制链接链接已复制到粘贴板!
Update a capsule
10.9. hammer compute-resource 复制链接链接已复制到粘贴板!
Manipulate compute resources.
10.9.1. hammer compute-resource create 复制链接链接已复制到粘贴板!
Create a compute resource
10.9.2. hammer compute-resource delete 复制链接链接已复制到粘贴板!
Delete a compute resource
10.9.3. hammer compute-resource image 复制链接链接已复制到粘贴板!
View and manage compute resource’s images
10.9.3.1. hammer compute-resource image available 复制链接链接已复制到粘贴板!
Show images available for addition
10.9.3.2. hammer compute-resource image create 复制链接链接已复制到粘贴板!
Create an image
10.9.3.3. hammer compute-resource image delete 复制链接链接已复制到粘贴板!
Delete an image
10.9.3.4. hammer compute-resource image info 复制链接链接已复制到粘贴板!
Show an image
10.9.3.5. hammer compute-resource image list 复制链接链接已复制到粘贴板!
List all images for a compute resource
10.9.3.6. hammer compute-resource image update 复制链接链接已复制到粘贴板!
Update an image
10.9.4. hammer compute-resource info 复制链接链接已复制到粘贴板!
Show a compute resource
10.9.5. hammer compute-resource list 复制链接链接已复制到粘贴板!
List all compute resources
10.9.6. hammer compute-resource networks 复制链接链接已复制到粘贴板!
Show available networks
10.9.7. hammer compute-resource update 复制链接链接已复制到粘贴板!
Update a compute resource
10.10. hammer config-group 复制链接链接已复制到粘贴板!
Manipulate config groups.
10.10.1. hammer config-group create 复制链接链接已复制到粘贴板!
Create a config group
10.10.2. hammer config-group delete 复制链接链接已复制到粘贴板!
Delete a config group
10.10.3. hammer config-group info 复制链接链接已复制到粘贴板!
Show a config group
10.10.4. hammer config-group list 复制链接链接已复制到粘贴板!
List of config groups
10.10.5. hammer config-group update 复制链接链接已复制到粘贴板!
Update a config group
10.11. hammer content-view 复制链接链接已复制到粘贴板!
Manipulate content views.
10.11.1. hammer content-view add-repository 复制链接链接已复制到粘贴板!
Associate a resource
10.11.2. hammer content-view add-version 复制链接链接已复制到粘贴板!
Add a content view version to a composite view
10.11.3. hammer content-view component 复制链接链接已复制到粘贴板!
View and manage components
10.11.3.1. hammer content-view component add 复制链接链接已复制到粘贴板!
Add components to the content view
10.11.3.2. hammer content-view component list 复制链接链接已复制到粘贴板!
List components attached to this content view
10.11.3.3. hammer content-view component remove 复制链接链接已复制到粘贴板!
Remove components from the content view
10.11.3.4. hammer content-view component update 复制链接链接已复制到粘贴板!
Update a component associated with the content view
10.11.4. hammer content-view copy 复制链接链接已复制到粘贴板!
Copy a content view
10.11.5. hammer content-view create 复制链接链接已复制到粘贴板!
Create a content view
10.11.6. hammer content-view delete 复制链接链接已复制到粘贴板!
Delete a content view
10.11.7. hammer content-view filter 复制链接链接已复制到粘贴板!
View and manage filters
10.11.7.1. hammer content-view filter add-repository 复制链接链接已复制到粘贴板!
Associate a resource
10.11.7.2. hammer content-view filter create 复制链接链接已复制到粘贴板!
create a filter for a content view
10.11.7.3. hammer content-view filter delete 复制链接链接已复制到粘贴板!
delete a filter
10.11.7.4. hammer content-view filter info 复制链接链接已复制到粘贴板!
show filter info
10.11.7.5. hammer content-view filter list 复制链接链接已复制到粘贴板!
list filters
10.11.7.6. hammer content-view filter remove-repository 复制链接链接已复制到粘贴板!
Disassociate a resource
10.11.7.7. hammer content-view filter rule 复制链接链接已复制到粘贴板!
View and manage filter rules
# ===== hammer content-view filter rule create
Create a filter rule. The parameters included should be based upon the filter type.
# ===== hammer content-view filter rule delete
Delete a filter rule
# ===== hammer content-view filter rule info
Show filter rule info
# ===== hammer content-view filter rule list
List filter rules
# ===== hammer content-view filter rule update
Update a filter rule. The parameters included should be based upon the filter type.
10.11.7.8. hammer content-view filter update 复制链接链接已复制到粘贴板!
update a filter
10.11.8. hammer content-view info 复制链接链接已复制到粘贴板!
Show a content view
10.11.9. hammer content-view list 复制链接链接已复制到粘贴板!
List content views
10.11.10. hammer content-view publish 复制链接链接已复制到粘贴板!
Publish a content view
10.11.11. hammer content-view puppet-module 复制链接链接已复制到粘贴板!
View and manage puppet modules
10.11.11.1. hammer content-view puppet-module add 复制链接链接已复制到粘贴板!
Add a puppet module to the content view
10.11.11.2. hammer content-view puppet-module list 复制链接链接已复制到粘贴板!
List content view puppet modules
10.11.11.3. hammer content-view puppet-module remove 复制链接链接已复制到粘贴板!
Remove a puppet module from the content view
10.11.12. hammer content-view purge 复制链接链接已复制到粘贴板!
Delete old versions of a content view
10.11.13. hammer content-view remove 复制链接链接已复制到粘贴板!
Remove versions and/or environments from a content view and reassign systems and keys
10.11.14. hammer content-view remove-from-environment 复制链接链接已复制到粘贴板!
Remove a content view from an environment
10.11.15. hammer content-view remove-repository 复制链接链接已复制到粘贴板!
Disassociate a resource
10.11.16. hammer content-view remove-version 复制链接链接已复制到粘贴板!
Remove a content view version from a composite view
10.11.17. hammer content-view update 复制链接链接已复制到粘贴板!
Update a content view
10.11.18. hammer content-view version 复制链接链接已复制到粘贴板!
View and manage content view versions
10.11.18.1. hammer content-view version delete 复制链接链接已复制到粘贴板!
Remove content view version
10.11.18.2. hammer content-view version export 复制链接链接已复制到粘贴板!
Export a content view version
Perform an Incremental Update on one or more Content View Versions
10.11.18.4. hammer content-view version info 复制链接链接已复制到粘贴板!
Show content view version
10.11.18.5. hammer content-view version list 复制链接链接已复制到粘贴板!
List content view versions
10.11.18.6. hammer content-view version promote 复制链接链接已复制到粘贴板!
Promote a content view version
Forces a republish of the version’s repositories' metadata.
10.12. hammer csv 复制链接链接已复制到粘贴板!
import to or export from a running foreman server
10.12.1. hammer csv activation-keys 复制链接链接已复制到粘贴板!
import or export activation keys
10.12.2. hammer csv content-hosts 复制链接链接已复制到粘贴板!
import or export content hosts
10.12.3. hammer csv export 复制链接链接已复制到粘贴板!
export into directory
10.12.4. hammer csv import 复制链接链接已复制到粘贴板!
import by directory
10.12.5. hammer csv settings 复制链接链接已复制到粘贴板!
import or export settings
10.12.6. hammer csv subscriptions 复制链接链接已复制到粘贴板!
import or export subscriptions
10.13. hammer defaults 复制链接链接已复制到粘贴板!
Defaults management
10.13.1. hammer defaults add 复制链接链接已复制到粘贴板!
Add a default parameter to config
10.13.2. hammer defaults delete 复制链接链接已复制到粘贴板!
Delete a default param
10.13.3. hammer defaults list 复制链接链接已复制到粘贴板!
List all the default parameters
Usage:
hammer defaults list [OPTIONS]
Options:
-h, --help print help
Usage:
hammer defaults list [OPTIONS]
Options:
-h, --help print help
10.13.4. hammer defaults providers 复制链接链接已复制到粘贴板!
List all the providers
Usage:
hammer defaults providers [OPTIONS]
Options:
-h, --help print help
Usage:
hammer defaults providers [OPTIONS]
Options:
-h, --help print help
10.14. hammer discovery 复制链接链接已复制到粘贴板!
Manipulate discovered hosts.
10.14.1. hammer discovery auto-provision 复制链接链接已复制到粘贴板!
Auto provision a host
10.14.2. hammer discovery delete 复制链接链接已复制到粘贴板!
Delete a discovered host
10.14.3. hammer discovery facts 复制链接链接已复制到粘贴板!
List all fact values
10.14.4. hammer discovery info 复制链接链接已复制到粘贴板!
Show a discovered host
10.14.5. hammer discovery list 复制链接链接已复制到粘贴板!
List all discovered hosts
10.14.6. hammer discovery provision 复制链接链接已复制到粘贴板!
Provision a discovered host
10.14.7. hammer discovery reboot 复制链接链接已复制到粘贴板!
Reboot a host
10.14.8. hammer discovery refresh-facts 复制链接链接已复制到粘贴板!
Refresh the facts of a host
10.15. hammer discovery-rule 复制链接链接已复制到粘贴板!
Manipulate discovered rules.
10.15.1. hammer discovery-rule create 复制链接链接已复制到粘贴板!
Create a discovery rule
10.15.2. hammer discovery-rule delete 复制链接链接已复制到粘贴板!
Delete a rule
10.15.3. hammer discovery-rule info 复制链接链接已复制到粘贴板!
Show a discovery rule
10.15.4. hammer discovery-rule list 复制链接链接已复制到粘贴板!
List all discovery rules
10.15.5. hammer discovery-rule update 复制链接链接已复制到粘贴板!
Update a rule
10.16. hammer docker 复制链接链接已复制到粘贴板!
Manipulate docker content
10.16.1. hammer docker container 复制链接链接已复制到粘贴板!
Manage docker containers
10.16.1.1. hammer docker container create 复制链接链接已复制到粘贴板!
Create a container
10.16.1.2. hammer docker container delete 复制链接链接已复制到粘贴板!
Delete a container
10.16.1.3. hammer docker container info 复制链接链接已复制到粘贴板!
Show a container
10.16.1.4. hammer docker container list 复制链接链接已复制到粘贴板!
List all containers
10.16.1.5. hammer docker container logs 复制链接链接已复制到粘贴板!
Show container logs
10.16.1.6. hammer docker container start 复制链接链接已复制到粘贴板!
Power a container on
10.16.1.7. hammer docker container status 复制链接链接已复制到粘贴板!
Run power operation on a container
10.16.1.8. hammer docker container stop 复制链接链接已复制到粘贴板!
Power a container off
10.16.2. hammer docker manifest 复制链接链接已复制到粘贴板!
Manage docker manifests
10.16.2.1. hammer docker manifest info 复制链接链接已复制到粘贴板!
Show a docker manifest
10.16.2.2. hammer docker manifest list 复制链接链接已复制到粘贴板!
List docker_manifests
10.16.3. hammer docker registry 复制链接链接已复制到粘贴板!
Manage docker registries
10.16.3.1. hammer docker registry create 复制链接链接已复制到粘贴板!
Create a docker registry
10.16.3.2. hammer docker registry delete 复制链接链接已复制到粘贴板!
Delete a docker registry
10.16.3.3. hammer docker registry info 复制链接链接已复制到粘贴板!
Show a docker registry
10.16.3.4. hammer docker registry list 复制链接链接已复制到粘贴板!
List all docker registries
10.16.3.5. hammer docker registry update 复制链接链接已复制到粘贴板!
Update a docker registry
10.16.4. hammer docker tag 复制链接链接已复制到粘贴板!
Manage docker tags
10.16.4.1. hammer docker tag info 复制链接链接已复制到粘贴板!
Show a docker tag
10.16.4.2. hammer docker tag list 复制链接链接已复制到粘贴板!
List docker_tags
10.17. hammer domain 复制链接链接已复制到粘贴板!
Manipulate domains.
10.17.1. hammer domain create 复制链接链接已复制到粘贴板!
Create a domain
10.17.2. hammer domain delete 复制链接链接已复制到粘贴板!
Delete a domain
10.17.3. hammer domain delete-parameter 复制链接链接已复制到粘贴板!
Delete parameter for a domain.
10.17.4. hammer domain info 复制链接链接已复制到粘贴板!
Show a domain
10.17.5. hammer domain list 复制链接链接已复制到粘贴板!
List of domains
10.17.6. hammer domain set-parameter 复制链接链接已复制到粘贴板!
Create or update parameter for a domain.
10.17.7. hammer domain update 复制链接链接已复制到粘贴板!
Update a domain
10.18. hammer environment 复制链接链接已复制到粘贴板!
Manipulate environments.
10.18.1. hammer environment create 复制链接链接已复制到粘贴板!
Create an environment
10.18.2. hammer environment delete 复制链接链接已复制到粘贴板!
Delete an environment
10.18.3. hammer environment info 复制链接链接已复制到粘贴板!
Show an environment
10.18.4. hammer environment list 复制链接链接已复制到粘贴板!
List all environments
10.18.5. hammer environment sc-params 复制链接链接已复制到粘贴板!
List all smart class parameters
10.18.6. hammer environment update 复制链接链接已复制到粘贴板!
Update an environment
10.19. hammer erratum 复制链接链接已复制到粘贴板!
Manipulate errata
10.19.1. hammer erratum info 复制链接链接已复制到粘贴板!
Show an erratum
10.19.2. hammer erratum list 复制链接链接已复制到粘贴板!
List errata
10.20. hammer fact 复制链接链接已复制到粘贴板!
Search facts.
10.20.1. hammer fact list 复制链接链接已复制到粘贴板!
List all fact values
10.21. hammer file 复制链接链接已复制到粘贴板!
Manipulate files
10.21.1. hammer file info 复制链接链接已复制到粘贴板!
Show a file
10.21.2. hammer file list 复制链接链接已复制到粘贴板!
List files
10.22. hammer filter 复制链接链接已复制到粘贴板!
Manage permission filters.
10.22.1. hammer filter available-permissions 复制链接链接已复制到粘贴板!
List all permissions
10.22.2. hammer filter available-resources 复制链接链接已复制到粘贴板!
List available resource types.
Usage:
hammer filter available-resources [OPTIONS]
Options:
-h, --help print help
Usage:
hammer filter available-resources [OPTIONS]
Options:
-h, --help print help
10.22.3. hammer filter create 复制链接链接已复制到粘贴板!
Create a filter
10.22.4. hammer filter delete 复制链接链接已复制到粘贴板!
Delete a filter
10.22.5. hammer filter info 复制链接链接已复制到粘贴板!
Show a filter
10.22.6. hammer filter list 复制链接链接已复制到粘贴板!
List all filters
10.22.7. hammer filter update 复制链接链接已复制到粘贴板!
Update a filter
10.23. hammer foreign-input-set 复制链接链接已复制到粘贴板!
Manage foreign input sets
10.23.1. hammer foreign-input-set create 复制链接链接已复制到粘贴板!
Create a foreign input set
10.23.2. hammer foreign-input-set delete 复制链接链接已复制到粘贴板!
Delete a foreign input set
10.23.3. hammer foreign-input-set info 复制链接链接已复制到粘贴板!
Show foreign input set details
10.23.4. hammer foreign-input-set list 复制链接链接已复制到粘贴板!
List foreign input sets
10.23.5. hammer foreign-input-set update 复制链接链接已复制到粘贴板!
Update a foreign input set
10.24. hammer full-help 复制链接链接已复制到粘贴板!
Print help for all hammer commands
10.25. hammer global-parameter 复制链接链接已复制到粘贴板!
Manipulate global parameters.
10.25.1. hammer global-parameter delete 复制链接链接已复制到粘贴板!
Delete a global parameter
10.25.2. hammer global-parameter list 复制链接链接已复制到粘贴板!
List all global parameters.
10.25.3. hammer global-parameter set 复制链接链接已复制到粘贴板!
Set a global parameter.
10.26. hammer gpg 复制链接链接已复制到粘贴板!
Manipulate GPG Key actions on the server
10.26.1. hammer gpg create 复制链接链接已复制到粘贴板!
Create a gpg key
10.26.2. hammer gpg delete 复制链接链接已复制到粘贴板!
Destroy a gpg key
10.26.3. hammer gpg info 复制链接链接已复制到粘贴板!
Show a gpg key
10.26.4. hammer gpg list 复制链接链接已复制到粘贴板!
List gpg keys
10.26.5. hammer gpg update 复制链接链接已复制到粘贴板!
Update a repository
10.27. hammer host 复制链接链接已复制到粘贴板!
Manipulate hosts.
10.27.1. hammer host create 复制链接链接已复制到粘贴板!
Create a host
10.27.2. hammer host delete 复制链接链接已复制到粘贴板!
Delete a host
10.27.3. hammer host delete-parameter 复制链接链接已复制到粘贴板!
Delete parameter for a host.
10.27.4. hammer host errata 复制链接链接已复制到粘贴板!
Manage errata on your hosts
10.27.4.1. hammer host errata apply 复制链接链接已复制到粘贴板!
Schedule errata for installation
10.27.4.2. hammer host errata info 复制链接链接已复制到粘贴板!
Retrieve a single errata for a host
10.27.4.3. hammer host errata list 复制链接链接已复制到粘贴板!
List errata available for the content host
10.27.5. hammer host facts 复制链接链接已复制到粘贴板!
List all fact values
10.27.6. hammer host info 复制链接链接已复制到粘贴板!
Show a host
10.27.7. hammer host interface 复制链接链接已复制到粘贴板!
View and manage host’s network interfaces
10.27.7.1. hammer host interface create 复制链接链接已复制到粘贴板!
Create an interface on a host
10.27.7.2. hammer host interface delete 复制链接链接已复制到粘贴板!
Delete a host’s interface
10.27.7.3. hammer host interface info 复制链接链接已复制到粘贴板!
Show an interface for host
10.27.7.4. hammer host interface list 复制链接链接已复制到粘贴板!
List all interfaces for host
10.27.7.5. hammer host interface update 复制链接链接已复制到粘贴板!
Update a host’s interface
10.27.8. hammer host list 复制链接链接已复制到粘贴板!
List all hosts
10.27.9. hammer host package 复制链接链接已复制到粘贴板!
Manage packages on your hosts
10.27.9.1. hammer host package install 复制链接链接已复制到粘贴板!
Install packages remotely
10.27.9.2. hammer host package list 复制链接链接已复制到粘贴板!
List packages installed on the host
10.27.9.3. hammer host package remove 复制链接链接已复制到粘贴板!
Uninstall packages remotely
10.27.9.4. hammer host package upgrade 复制链接链接已复制到粘贴板!
Update packages remotely
10.27.9.5. hammer host package upgrade-all 复制链接链接已复制到粘贴板!
Update packages remotely
10.27.10. hammer host package-group 复制链接链接已复制到粘贴板!
Manage package-groups on your hosts
10.27.10.1. hammer host package-group install 复制链接链接已复制到粘贴板!
Install packages remotely
10.27.10.2. hammer host package-group remove 复制链接链接已复制到粘贴板!
Uninstall packages remotely
10.27.11. hammer host puppet-classes 复制链接链接已复制到粘贴板!
List all Puppet classes
10.27.12. hammer host puppetrun 复制链接链接已复制到粘贴板!
Force a Puppet agent run on the host
10.27.13. hammer host reboot 复制链接链接已复制到粘贴板!
Reboot a host
10.27.14. hammer host rebuild-config 复制链接链接已复制到粘贴板!
Rebuild orchestration related configurations for host
10.27.15. hammer host reports 复制链接链接已复制到粘贴板!
List all reports
10.27.16. hammer host sc-params 复制链接链接已复制到粘贴板!
List all smart class parameters
10.27.17. hammer host set-parameter 复制链接链接已复制到粘贴板!
Create or update parameter for a host.
10.27.18. hammer host smart-variables 复制链接链接已复制到粘贴板!
List all smart variables
10.27.19. hammer host start 复制链接链接已复制到粘贴板!
Power a host on
10.27.20. hammer host status 复制链接链接已复制到粘贴板!
Get configuration status of host
10.27.21. hammer host stop 复制链接链接已复制到粘贴板!
Power a host off
10.27.22. hammer host subscription 复制链接链接已复制到粘贴板!
Manage subscription information on your hosts
10.27.22.1. hammer host subscription attach 复制链接链接已复制到粘贴板!
Add a subscription to a host
10.27.22.2. hammer host subscription auto-attach 复制链接链接已复制到粘贴板!
Trigger an auto-attach of subscriptions
10.27.22.3. hammer host subscription content-override 复制链接链接已复制到粘贴板!
Override product content defaults
10.27.22.4. hammer host subscription product-content 复制链接链接已复制到粘贴板!
List associated products
10.27.22.5. hammer host subscription register 复制链接链接已复制到粘贴板!
Register a host with subscription and information.
10.27.22.6. hammer host subscription remove 复制链接链接已复制到粘贴板!
10.27.22.7. hammer host subscription unregister 复制链接链接已复制到粘贴板!
Unregister the host as a subscription consumer
10.27.23. hammer host update 复制链接链接已复制到粘贴板!
Update a host
10.28. hammer host-collection 复制链接链接已复制到粘贴板!
Manipulate host collections
10.28.1. hammer host-collection add-host 复制链接链接已复制到粘贴板!
Add host to the host collection
10.28.2. hammer host-collection copy 复制链接链接已复制到粘贴板!
Copy a host collection
10.28.3. hammer host-collection create 复制链接链接已复制到粘贴板!
Create a host collection
10.28.4. hammer host-collection delete 复制链接链接已复制到粘贴板!
Destroy a host collection
10.28.5. hammer host-collection erratum 复制链接链接已复制到粘贴板!
Manipulate errata for a host collection
10.28.5.1. hammer host-collection erratum install 复制链接链接已复制到粘贴板!
Install errata on content hosts contained within a host collection
10.28.6. hammer host-collection hosts 复制链接链接已复制到粘贴板!
List all hosts
10.28.7. hammer host-collection info 复制链接链接已复制到粘贴板!
Show a host collection
10.28.8. hammer host-collection list 复制链接链接已复制到粘贴板!
List host collections
10.28.9. hammer host-collection package 复制链接链接已复制到粘贴板!
Manipulate packages for a host collection
10.28.9.1. hammer host-collection package install 复制链接链接已复制到粘贴板!
Install packages on content hosts contained within a host collection
10.28.9.2. hammer host-collection package remove 复制链接链接已复制到粘贴板!
Remove packages on content hosts contained within a host collection
10.28.9.3. hammer host-collection package update 复制链接链接已复制到粘贴板!
Update packages on content hosts contained within a host collection
10.28.10. hammer host-collection package-group 复制链接链接已复制到粘贴板!
Manipulate package-groups for a host collection
10.28.10.1. hammer host-collection package-group install 复制链接链接已复制到粘贴板!
Install package-groups on content hosts contained within a host collection
10.28.10.2. hammer host-collection package-group remove 复制链接链接已复制到粘贴板!
Remove package-groups on content hosts contained within a host collection
10.28.10.3. hammer host-collection package-group update 复制链接链接已复制到粘贴板!
Update package-groups on content hosts contained within a host collection
10.28.11. hammer host-collection remove-host 复制链接链接已复制到粘贴板!
Remove hosts from the host collection
10.28.12. hammer host-collection update 复制链接链接已复制到粘贴板!
Update a host collection
10.29. hammer hostgroup 复制链接链接已复制到粘贴板!
Manipulate hostgroups.
10.29.1. hammer hostgroup create 复制链接链接已复制到粘贴板!
Create a host group
10.29.2. hammer hostgroup delete 复制链接链接已复制到粘贴板!
Delete a host group
10.29.3. hammer hostgroup delete-parameter 复制链接链接已复制到粘贴板!
Delete parameter for a hostgroup.
10.29.4. hammer hostgroup info 复制链接链接已复制到粘贴板!
Show a host group
10.29.5. hammer hostgroup list 复制链接链接已复制到粘贴板!
List all host groups
10.29.6. hammer hostgroup puppet-classes 复制链接链接已复制到粘贴板!
List all Puppet classes
10.29.7. hammer hostgroup sc-params 复制链接链接已复制到粘贴板!
List all smart class parameters
10.29.8. hammer hostgroup set-parameter 复制链接链接已复制到粘贴板!
Create or update parameter for a hostgroup.
10.29.9. hammer hostgroup smart-variables 复制链接链接已复制到粘贴板!
List all smart variables
10.29.10. hammer hostgroup update 复制链接链接已复制到粘贴板!
Update a host group
10.30. hammer job-invocation 复制链接链接已复制到粘贴板!
Manage job invocations
10.30.1. hammer job-invocation create 复制链接链接已复制到粘贴板!
Create a job invocation
10.30.2. hammer job-invocation info 复制链接链接已复制到粘贴板!
Show job invocation
10.30.3. hammer job-invocation list 复制链接链接已复制到粘贴板!
List job invocations
10.30.4. hammer job-invocation output 复制链接链接已复制到粘贴板!
View the output for a host
10.31. hammer job-template 复制链接链接已复制到粘贴板!
Manage job templates
10.31.1. hammer job-template create 复制链接链接已复制到粘贴板!
Create a job template
10.31.2. hammer job-template delete 复制链接链接已复制到粘贴板!
Delete a job template
10.31.3. hammer job-template dump 复制链接链接已复制到粘贴板!
View job template content
10.31.4. hammer job-template export 复制链接链接已复制到粘贴板!
Export a template including all metadata
10.31.5. hammer job-template import 复制链接链接已复制到粘贴板!
Import a job template from ERB
10.31.6. hammer job-template info 复制链接链接已复制到粘贴板!
Show job template details
10.31.7. hammer job-template list 复制链接链接已复制到粘贴板!
List job templates
10.31.8. hammer job-template update 复制链接链接已复制到粘贴板!
Update a job template
10.32. hammer lifecycle-environment 复制链接链接已复制到粘贴板!
Manipulate lifecycle_environments on the server
10.32.1. hammer lifecycle-environment create 复制链接链接已复制到粘贴板!
Create an environment
10.32.2. hammer lifecycle-environment delete 复制链接链接已复制到粘贴板!
Destroy an environment
10.32.3. hammer lifecycle-environment info 复制链接链接已复制到粘贴板!
Show an environment
10.32.4. hammer lifecycle-environment list 复制链接链接已复制到粘贴板!
List environments in an organization
10.32.5. hammer lifecycle-environment paths 复制链接链接已复制到粘贴板!
List environment paths
10.32.6. hammer lifecycle-environment update 复制链接链接已复制到粘贴板!
Update an environment
10.33. hammer location 复制链接链接已复制到粘贴板!
Manipulate locations.
10.33.1. hammer location add-compute-resource 复制链接链接已复制到粘贴板!
Associate a compute resource
10.33.2. hammer location add-config-template 复制链接链接已复制到粘贴板!
Associate a configuration template
10.33.3. hammer location add-domain 复制链接链接已复制到粘贴板!
Associate a domain
10.33.4. hammer location add-environment 复制链接链接已复制到粘贴板!
Associate an environment
10.33.5. hammer location add-hostgroup 复制链接链接已复制到粘贴板!
Associate a hostgroup
10.33.6. hammer location add-medium 复制链接链接已复制到粘贴板!
Associate a medium
10.33.7. hammer location add-organization 复制链接链接已复制到粘贴板!
Associate an organization
10.33.8. hammer location add-smart-proxy 复制链接链接已复制到粘贴板!
Associate a smart proxy
10.33.9. hammer location add-subnet 复制链接链接已复制到粘贴板!
Associate a subnet
10.33.10. hammer location add-user 复制链接链接已复制到粘贴板!
Associate an user
10.33.11. hammer location create 复制链接链接已复制到粘贴板!
Create a location
10.33.12. hammer location delete 复制链接链接已复制到粘贴板!
Delete a location
10.33.13. hammer location delete-parameter 复制链接链接已复制到粘贴板!
Delete parameter for a location.
10.33.14. hammer location info 复制链接链接已复制到粘贴板!
Show a location
10.33.15. hammer location list 复制链接链接已复制到粘贴板!
List all locations
10.33.16. hammer location remove-compute-resource 复制链接链接已复制到粘贴板!
Disassociate a compute resource
10.33.17. hammer location remove-config-template 复制链接链接已复制到粘贴板!
Disassociate a configuration template
10.33.18. hammer location remove-domain 复制链接链接已复制到粘贴板!
Disassociate a domain
10.33.19. hammer location remove-environment 复制链接链接已复制到粘贴板!
Disassociate an environment
10.33.20. hammer location remove-hostgroup 复制链接链接已复制到粘贴板!
Disassociate a hostgroup
10.33.21. hammer location remove-medium 复制链接链接已复制到粘贴板!
Disassociate a medium
10.33.22. hammer location remove-organization 复制链接链接已复制到粘贴板!
Disassociate an organization
10.33.23. hammer location remove-smart-proxy 复制链接链接已复制到粘贴板!
Disassociate a smart proxy
10.33.24. hammer location remove-subnet 复制链接链接已复制到粘贴板!
Disassociate a subnet
10.33.25. hammer location remove-user 复制链接链接已复制到粘贴板!
Disassociate an user
10.33.26. hammer location set-parameter 复制链接链接已复制到粘贴板!
Create or update parameter for a location.
10.33.27. hammer location update 复制链接链接已复制到粘贴板!
Update a location
10.34. hammer medium 复制链接链接已复制到粘贴板!
Manipulate installation media.
10.34.1. hammer medium add-operatingsystem 复制链接链接已复制到粘贴板!
Associate an operating system
10.34.2. hammer medium create 复制链接链接已复制到粘贴板!
Create a medium
10.34.3. hammer medium delete 复制链接链接已复制到粘贴板!
Delete a medium
10.34.4. hammer medium info 复制链接链接已复制到粘贴板!
Show a medium
10.34.5. hammer medium list 复制链接链接已复制到粘贴板!
List all installation media
10.34.6. hammer medium remove-operatingsystem 复制链接链接已复制到粘贴板!
Disassociate an operating system
10.34.7. hammer medium update 复制链接链接已复制到粘贴板!
Update a medium
10.35. hammer model 复制链接链接已复制到粘贴板!
Manipulate hardware models.
10.35.1. hammer model create 复制链接链接已复制到粘贴板!
Create a hardware model
10.35.2. hammer model delete 复制链接链接已复制到粘贴板!
Delete a hardware model
10.35.3. hammer model info 复制链接链接已复制到粘贴板!
Show a hardware model
10.35.4. hammer model list 复制链接链接已复制到粘贴板!
List all hardware models
10.35.5. hammer model update 复制链接链接已复制到粘贴板!
Update a hardware model
10.36. hammer organization 复制链接链接已复制到粘贴板!
Manipulate organizations
10.36.1. hammer organization add-compute-resource 复制链接链接已复制到粘贴板!
Associate a compute resource
10.36.2. hammer organization add-config-template 复制链接链接已复制到粘贴板!
Associate a configuration template
10.36.3. hammer organization add-domain 复制链接链接已复制到粘贴板!
Associate a domain
10.36.4. hammer organization add-environment 复制链接链接已复制到粘贴板!
Associate an environment
10.36.5. hammer organization add-hostgroup 复制链接链接已复制到粘贴板!
Associate a hostgroup
10.36.6. hammer organization add-location 复制链接链接已复制到粘贴板!
Associate a location
10.36.7. hammer organization add-medium 复制链接链接已复制到粘贴板!
Associate a medium
10.36.8. hammer organization add-smart-proxy 复制链接链接已复制到粘贴板!
Associate a smart proxy
10.36.9. hammer organization add-subnet 复制链接链接已复制到粘贴板!
Associate a subnet
10.36.10. hammer organization add-user 复制链接链接已复制到粘贴板!
Associate an user
10.36.11. hammer organization create 复制链接链接已复制到粘贴板!
Create organization
10.36.12. hammer organization delete 复制链接链接已复制到粘贴板!
Delete an organization
10.36.13. hammer organization delete-parameter 复制链接链接已复制到粘贴板!
Delete parameter for an organization.
10.36.14. hammer organization info 复制链接链接已复制到粘贴板!
Show organization
10.36.15. hammer organization list 复制链接链接已复制到粘贴板!
List all organizations
10.36.16. hammer organization remove-compute-resource 复制链接链接已复制到粘贴板!
Disassociate a compute resource
10.36.17. hammer organization remove-config-template 复制链接链接已复制到粘贴板!
Disassociate a configuration template
10.36.18. hammer organization remove-domain 复制链接链接已复制到粘贴板!
Disassociate a domain
10.36.19. hammer organization remove-environment 复制链接链接已复制到粘贴板!
Disassociate an environment
10.36.20. hammer organization remove-hostgroup 复制链接链接已复制到粘贴板!
Disassociate a hostgroup
10.36.21. hammer organization remove-location 复制链接链接已复制到粘贴板!
Disassociate a location
10.36.22. hammer organization remove-medium 复制链接链接已复制到粘贴板!
Disassociate a medium
10.36.23. hammer organization remove-smart-proxy 复制链接链接已复制到粘贴板!
Disassociate a smart proxy
10.36.24. hammer organization remove-subnet 复制链接链接已复制到粘贴板!
Disassociate a subnet
10.36.25. hammer organization remove-user 复制链接链接已复制到粘贴板!
Disassociate an user
10.36.26. hammer organization set-parameter 复制链接链接已复制到粘贴板!
Create or update parameter for an organization.
10.36.27. hammer organization update 复制链接链接已复制到粘贴板!
Update organization
10.37. hammer os 复制链接链接已复制到粘贴板!
Manipulate operating system.
10.37.1. hammer os add-architecture 复制链接链接已复制到粘贴板!
Associate an architecture
10.37.2. hammer os add-config-template 复制链接链接已复制到粘贴板!
Associate a configuration template
10.37.3. hammer os add-ptable 复制链接链接已复制到粘贴板!
Associate a partition table
10.37.4. hammer os create 复制链接链接已复制到粘贴板!
Create an operating system
10.37.5. hammer os delete 复制链接链接已复制到粘贴板!
Delete an operating system
10.37.6. hammer os delete-default-template 复制链接链接已复制到粘贴板!
10.37.7. hammer os delete-parameter 复制链接链接已复制到粘贴板!
Delete parameter for an operating system.
10.37.8. hammer os info 复制链接链接已复制到粘贴板!
Show an operating system
10.37.9. hammer os list 复制链接链接已复制到粘贴板!
List all operating systems
10.37.10. hammer os remove-architecture 复制链接链接已复制到粘贴板!
Disassociate an architecture
10.37.11. hammer os remove-config-template 复制链接链接已复制到粘贴板!
Disassociate a configuration template
10.37.12. hammer os remove-ptable 复制链接链接已复制到粘贴板!
Disassociate a partition table
10.37.13. hammer os set-default-template 复制链接链接已复制到粘贴板!
10.37.14. hammer os set-parameter 复制链接链接已复制到粘贴板!
Create or update parameter for an operating system.
10.37.15. hammer os update 复制链接链接已复制到粘贴板!
Update an operating system
10.38. hammer ostree-branch 复制链接链接已复制到粘贴板!
Manipulate ostree branches
10.38.1. hammer ostree-branch info 复制链接链接已复制到粘贴板!
Show an ostree branch
10.38.2. hammer ostree-branch list 复制链接链接已复制到粘贴板!
List ostree_branches
10.39. hammer package 复制链接链接已复制到粘贴板!
Manipulate packages.
10.39.1. hammer package info 复制链接链接已复制到粘贴板!
Show a package
10.39.2. hammer package list 复制链接链接已复制到粘贴板!
List packages
10.40. hammer package-group 复制链接链接已复制到粘贴板!
Manipulate package groups
10.40.1. hammer package-group info 复制链接链接已复制到粘贴板!
Show a package group
10.40.2. hammer package-group list 复制链接链接已复制到粘贴板!
List package_groups
10.41. hammer partition-table 复制链接链接已复制到粘贴板!
Manipulate partition tables.
10.41.1. hammer partition-table add-operatingsystem 复制链接链接已复制到粘贴板!
Associate an operating system
10.41.2. hammer partition-table create 复制链接链接已复制到粘贴板!
Create a partition table
10.41.3. hammer partition-table delete 复制链接链接已复制到粘贴板!
Delete a partition table
10.41.4. hammer partition-table dump 复制链接链接已复制到粘贴板!
View partition table content.
10.41.5. hammer partition-table info 复制链接链接已复制到粘贴板!
Show a partition table
10.41.6. hammer partition-table list 复制链接链接已复制到粘贴板!
List all partition tables
10.41.7. hammer partition-table remove-operatingsystem 复制链接链接已复制到粘贴板!
Disassociate an operating system
10.41.8. hammer partition-table update 复制链接链接已复制到粘贴板!
Update a partition table
10.42. hammer ping 复制链接链接已复制到粘贴板!
Get the status of the server
Usage:
hammer ping [OPTIONS]
Options:
-h, --help print help
Usage:
hammer ping [OPTIONS]
Options:
-h, --help print help
10.43. hammer policy 复制链接链接已复制到粘贴板!
Manipulate policies
10.43.1. hammer policy create 复制链接链接已复制到粘贴板!
Create a Policy
10.43.2. hammer policy delete 复制链接链接已复制到粘贴板!
Delete a Policy
10.43.3. hammer policy info 复制链接链接已复制到粘贴板!
Show a Policy
10.43.4. hammer policy list 复制链接链接已复制到粘贴板!
List Policies
10.43.5. hammer policy update 复制链接链接已复制到粘贴板!
Update a Policy
10.44. hammer product 复制链接链接已复制到粘贴板!
Manipulate products.
10.44.1. hammer product create 复制链接链接已复制到粘贴板!
Create a product
10.44.2. hammer product delete 复制链接链接已复制到粘贴板!
Destroy a product
10.44.3. hammer product info 复制链接链接已复制到粘贴板!
Show a product
10.44.4. hammer product list 复制链接链接已复制到粘贴板!
List products
10.44.5. hammer product remove-sync-plan 复制链接链接已复制到粘贴板!
Delete assignment sync plan and product.
10.44.6. hammer product set-sync-plan 复制链接链接已复制到粘贴板!
Assign sync plan to product.
10.44.7. hammer product synchronize 复制链接链接已复制到粘贴板!
Sync all repositories for a product
10.44.8. hammer product update 复制链接链接已复制到粘贴板!
Updates a product
10.45. hammer proxy 复制链接链接已复制到粘贴板!
Manipulate smart proxies.
10.45.1. hammer proxy content 复制链接链接已复制到粘贴板!
Manage the capsule content
Add lifecycle environments to the capsule
List the lifecycle environments not attached to the capsule
10.45.1.3. hammer proxy content cancel-synchronization 复制链接链接已复制到粘贴板!
Cancel running capsule synchronization.
10.45.1.4. hammer proxy content info 复制链接链接已复制到粘贴板!
Get current capsule synchronization status
10.45.1.5. hammer proxy content lifecycle-environments 复制链接链接已复制到粘贴板!
List the lifecycle environments attached to the capsule
Remove lifecycle environments from the capsule
10.45.1.7. hammer proxy content synchronization-status 复制链接链接已复制到粘贴板!
Get current capsule synchronization status
10.45.1.8. hammer proxy content synchronize 复制链接链接已复制到粘贴板!
Synchronize the content to the capsule
10.45.2. hammer proxy create 复制链接链接已复制到粘贴板!
Create a capsule
10.45.3. hammer proxy delete 复制链接链接已复制到粘贴板!
Delete a capsule
10.45.4. hammer proxy import-classes 复制链接链接已复制到粘贴板!
Import puppet classes from puppet Capsule.
10.45.5. hammer proxy info 复制链接链接已复制到粘贴板!
Show a capsule
10.45.6. hammer proxy list 复制链接链接已复制到粘贴板!
List all capsules
10.45.7. hammer proxy refresh-features 复制链接链接已复制到粘贴板!
Refresh capsule features
10.45.8. hammer proxy update 复制链接链接已复制到粘贴板!
Update a capsule
10.46. hammer puppet-class 复制链接链接已复制到粘贴板!
Search puppet modules.
10.46.1. hammer puppet-class info 复制链接链接已复制到粘贴板!
Show a Puppet class
10.46.2. hammer puppet-class list 复制链接链接已复制到粘贴板!
List all Puppet classes
10.46.3. hammer puppet-class sc-params 复制链接链接已复制到粘贴板!
List all smart class parameters
10.46.4. hammer puppet-class smart-variables 复制链接链接已复制到粘贴板!
List all smart variables
10.47. hammer puppet-module 复制链接链接已复制到粘贴板!
View Puppet Module details.
10.47.1. hammer puppet-module info 复制链接链接已复制到粘贴板!
Show a puppet module
10.47.2. hammer puppet-module list 复制链接链接已复制到粘贴板!
List puppet_modules
10.48. hammer realm 复制链接链接已复制到粘贴板!
Manipulate realms.
10.48.1. hammer realm create 复制链接链接已复制到粘贴板!
Create a realm
10.48.2. hammer realm delete 复制链接链接已复制到粘贴板!
Delete a realm
10.48.3. hammer realm info 复制链接链接已复制到粘贴板!
Show a realm
10.48.4. hammer realm list 复制链接链接已复制到粘贴板!
List of realms
10.48.5. hammer realm update 复制链接链接已复制到粘贴板!
Update a realm
10.49. hammer recurring-logic 复制链接链接已复制到粘贴板!
Recurring logic related actions.
10.49.1. hammer recurring-logic cancel 复制链接链接已复制到粘贴板!
Cancel recurring logic
10.49.2. hammer recurring-logic info 复制链接链接已复制到粘贴板!
Show recurring logic details
10.49.3. hammer recurring-logic list 复制链接链接已复制到粘贴板!
List recurring logics
Usage:
hammer recurring-logic list [OPTIONS]
Options:
-h, --help print help
Usage:
hammer recurring-logic list [OPTIONS]
Options:
-h, --help print help
10.50. hammer remote-execution-feature 复制链接链接已复制到粘贴板!
Manage remote execution features
10.50.1. hammer remote-execution-feature info 复制链接链接已复制到粘贴板!
Show remote execution feature
10.50.2. hammer remote-execution-feature list 复制链接链接已复制到粘贴板!
List remote execution features
Usage:
hammer remote-execution-feature list [OPTIONS]
Options:
-h, --help print help
Usage:
hammer remote-execution-feature list [OPTIONS]
Options:
-h, --help print help
10.50.3. hammer remote-execution-feature update 复制链接链接已复制到粘贴板!
Update a job template
10.51. hammer report 复制链接链接已复制到粘贴板!
Browse and read reports.
10.51.1. hammer report delete 复制链接链接已复制到粘贴板!
Delete a report
10.51.2. hammer report info 复制链接链接已复制到粘贴板!
Show a report
10.51.3. hammer report list 复制链接链接已复制到粘贴板!
List all reports
10.52. hammer repository 复制链接链接已复制到粘贴板!
Manipulate repositories
10.52.1. hammer repository create 复制链接链接已复制到粘贴板!
Create a custom repository
10.52.2. hammer repository delete 复制链接链接已复制到粘贴板!
Destroy a custom repository
10.52.3. hammer repository export 复制链接链接已复制到粘贴板!
Export content from a repository to the configured directory
10.52.4. hammer repository info 复制链接链接已复制到粘贴板!
Show a repository
10.52.5. hammer repository list 复制链接链接已复制到粘贴板!
List of enabled repositories
10.52.6. hammer repository remove-content 复制链接链接已复制到粘贴板!
Remove content from a repository
10.52.7. hammer repository synchronize 复制链接链接已复制到粘贴板!
Sync a repository
10.52.8. hammer repository update 复制链接链接已复制到粘贴板!
Update a repository
10.52.9. hammer repository upload-content 复制链接链接已复制到粘贴板!
Upload content into the repository
10.53. hammer repository-set 复制链接链接已复制到粘贴板!
Manipulate repository sets on the server
10.53.1. hammer repository-set available-repositories 复制链接链接已复制到粘贴板!
Get list of available repositories for the repository set
10.53.2. hammer repository-set disable 复制链接链接已复制到粘贴板!
Disable a repository from the set
10.53.3. hammer repository-set enable 复制链接链接已复制到粘贴板!
Enable a repository from the set
10.53.4. hammer repository-set info 复制链接链接已复制到粘贴板!
Get info about a repository set
10.53.5. hammer repository-set list 复制链接链接已复制到粘贴板!
List repository sets for a product.
10.54. hammer role 复制链接链接已复制到粘贴板!
Manage user roles.
10.54.1. hammer role clone 复制链接链接已复制到粘贴板!
Clone a role
10.54.2. hammer role create 复制链接链接已复制到粘贴板!
Create a role
10.54.3. hammer role delete 复制链接链接已复制到粘贴板!
Delete a role
10.54.4. hammer role filters 复制链接链接已复制到粘贴板!
List all filters
10.54.5. hammer role info 复制链接链接已复制到粘贴板!
Show a role
10.54.6. hammer role list 复制链接链接已复制到粘贴板!
List all roles
10.54.7. hammer role update 复制链接链接已复制到粘贴板!
Update a role
10.55. hammer sc-param 复制链接链接已复制到粘贴板!
Manipulate smart class parameters.
10.55.1. hammer sc-param add-override-value 复制链接链接已复制到粘贴板!
Create an override value for a specific smart variable
10.55.2. hammer sc-param info 复制链接链接已复制到粘贴板!
Show a smart class parameter
10.55.3. hammer sc-param list 复制链接链接已复制到粘贴板!
List all smart class parameters
10.55.4. hammer sc-param remove-override-value 复制链接链接已复制到粘贴板!
Delete an override value for a specific smart variable
10.55.5. hammer sc-param update 复制链接链接已复制到粘贴板!
Update a smart class parameter
10.56. hammer scap-content 复制链接链接已复制到粘贴板!
Manipulate SCAP contents
10.56.1. hammer scap-content create 复制链接链接已复制到粘贴板!
Create SCAP content
10.56.2. hammer scap-content delete 复制链接链接已复制到粘贴板!
Deletes an SCAP content
10.56.3. hammer scap-content download 复制链接链接已复制到粘贴板!
Show an SCAP content as XML
10.56.4. hammer scap-content info 复制链接链接已复制到粘贴板!
Show an SCAP content
10.56.5. hammer scap-content list 复制链接链接已复制到粘贴板!
List SCAP contents
10.56.6. hammer scap-content update 复制链接链接已复制到粘贴板!
Update an SCAP content
10.57. hammer settings 复制链接链接已复制到粘贴板!
Change server settings.
10.57.1. hammer settings list 复制链接链接已复制到粘贴板!
List all settings
10.57.2. hammer settings set 复制链接链接已复制到粘贴板!
Update a setting
10.58. hammer shell 复制链接链接已复制到粘贴板!
Interactive shell
Usage:
hammer shell [OPTIONS]
Options:
-h, --help print help
Usage:
hammer shell [OPTIONS]
Options:
-h, --help print help
10.59. hammer smart-variable 复制链接链接已复制到粘贴板!
Manipulate smart variables.
10.59.1. hammer smart-variable add-override-value 复制链接链接已复制到粘贴板!
Create an override value for a specific smart variable
10.59.2. hammer smart-variable create 复制链接链接已复制到粘贴板!
Create a smart variable
10.59.3. hammer smart-variable delete 复制链接链接已复制到粘贴板!
Delete a smart variable
10.59.4. hammer smart-variable info 复制链接链接已复制到粘贴板!
Show a smart variable
10.59.5. hammer smart-variable list 复制链接链接已复制到粘贴板!
List all smart variables
10.59.6. hammer smart-variable remove-override-value 复制链接链接已复制到粘贴板!
Delete an override value for a specific smart variable
10.59.7. hammer smart-variable update 复制链接链接已复制到粘贴板!
Update a smart variable
10.60. hammer subnet 复制链接链接已复制到粘贴板!
Manipulate subnets.
10.60.1. hammer subnet create 复制链接链接已复制到粘贴板!
Create a subnet
10.60.2. hammer subnet delete 复制链接链接已复制到粘贴板!
Delete a subnet
10.60.3. hammer subnet delete-parameter 复制链接链接已复制到粘贴板!
Delete parameter for a subnet.
10.60.4. hammer subnet info 复制链接链接已复制到粘贴板!
Show a subnet
10.60.5. hammer subnet list 复制链接链接已复制到粘贴板!
List of subnets
10.60.6. hammer subnet set-parameter 复制链接链接已复制到粘贴板!
Create or update parameter for a subnet.
10.60.7. hammer subnet update 复制链接链接已复制到粘贴板!
Update a subnet
10.61. hammer subscription 复制链接链接已复制到粘贴板!
Manipulate subscriptions.
10.61.1. hammer subscription delete-manifest 复制链接链接已复制到粘贴板!
Delete manifest from Red Hat provider
10.61.2. hammer subscription list 复制链接链接已复制到粘贴板!
List organization subscriptions
10.61.3. hammer subscription manifest-history 复制链接链接已复制到粘贴板!
obtain manifest history for subscriptions
10.61.4. hammer subscription refresh-manifest 复制链接链接已复制到粘贴板!
Refresh previously imported manifest for Red Hat provider
10.61.5. hammer subscription upload 复制链接链接已复制到粘贴板!
Upload a subscription manifest
10.62. hammer sync-plan 复制链接链接已复制到粘贴板!
Manipulate sync plans
10.62.1. hammer sync-plan create 复制链接链接已复制到粘贴板!
Create a sync plan
10.62.2. hammer sync-plan delete 复制链接链接已复制到粘贴板!
Destroy a sync plan
10.62.3. hammer sync-plan info 复制链接链接已复制到粘贴板!
Show a sync plan
10.62.4. hammer sync-plan list 复制链接链接已复制到粘贴板!
List sync plans
10.62.5. hammer sync-plan update 复制链接链接已复制到粘贴板!
Update a sync plan
10.63. hammer tailoring-file 复制链接链接已复制到粘贴板!
Manipulate Tailoring files
10.63.1. hammer tailoring-file create 复制链接链接已复制到粘贴板!
Create a Tailoring file
10.63.2. hammer tailoring-file delete 复制链接链接已复制到粘贴板!
Deletes a Tailoring file
10.63.3. hammer tailoring-file download 复制链接链接已复制到粘贴板!
Show a Tailoring file as XML
10.63.4. hammer tailoring-file info 复制链接链接已复制到粘贴板!
Show a Tailoring file
10.63.5. hammer tailoring-file list 复制链接链接已复制到粘贴板!
List Tailoring files
10.63.6. hammer tailoring-file update 复制链接链接已复制到粘贴板!
Update a Tailoring file
10.64. hammer task 复制链接链接已复制到粘贴板!
Tasks related actions.
10.64.1. hammer task list 复制链接链接已复制到粘贴板!
List tasks
10.64.2. hammer task progress 复制链接链接已复制到粘贴板!
Show the progress of the task
10.64.3. hammer task resume 复制链接链接已复制到粘贴板!
Resume all tasks paused in error state
10.65. hammer template 复制链接链接已复制到粘贴板!
Manipulate config templates.
10.65.1. hammer template add-operatingsystem 复制链接链接已复制到粘贴板!
Associate an operating system
10.65.2. hammer template build-pxe-default 复制链接链接已复制到粘贴板!
Update the default PXE menu on all configured TFTP servers
Usage:
hammer template build-pxe-default [OPTIONS]
Options:
-h, --help print help
Usage:
hammer template build-pxe-default [OPTIONS]
Options:
-h, --help print help
10.65.3. hammer template clone 复制链接链接已复制到粘贴板!
Clone a provision template
10.65.4. hammer template create 复制链接链接已复制到粘贴板!
Create a provisioning template
10.65.5. hammer template delete 复制链接链接已复制到粘贴板!
Delete a provisioning template
10.65.6. hammer template dump 复制链接链接已复制到粘贴板!
View provisioning template content.
10.65.7. hammer template info 复制链接链接已复制到粘贴板!
Show provisioning template details
10.65.8. hammer template kinds 复制链接链接已复制到粘贴板!
List available provisioning template kinds.
Usage:
hammer template kinds [OPTIONS]
Options:
-h, --help print help
Usage:
hammer template kinds [OPTIONS]
Options:
-h, --help print help
10.65.9. hammer template list 复制链接链接已复制到粘贴板!
List provisioning templates
10.65.10. hammer template remove-operatingsystem 复制链接链接已复制到粘贴板!
Disassociate an operating system
10.65.11. hammer template update 复制链接链接已复制到粘贴板!
Update a provisioning template
10.66. hammer template-input 复制链接链接已复制到粘贴板!
Manage template inputs
10.66.1. hammer template-input create 复制链接链接已复制到粘贴板!
Create a template input
10.66.2. hammer template-input delete 复制链接链接已复制到粘贴板!
Delete a template input
10.66.3. hammer template-input info 复制链接链接已复制到粘贴板!
Show template input details
10.66.4. hammer template-input list 复制链接链接已复制到粘贴板!
List template inputs
10.67. hammer user 复制链接链接已复制到粘贴板!
Manipulate users.
10.67.1. hammer user add-role 复制链接链接已复制到粘贴板!
Assign a user role
10.67.2. hammer user create 复制链接链接已复制到粘贴板!
Create a user
10.67.3. hammer user delete 复制链接链接已复制到粘贴板!
Delete a user
10.67.4. hammer user info 复制链接链接已复制到粘贴板!
Show a user
10.67.5. hammer user list 复制链接链接已复制到粘贴板!
List all users
10.67.6. hammer user remove-role 复制链接链接已复制到粘贴板!
Remove a user role
10.67.7. hammer user ssh-keys 复制链接链接已复制到粘贴板!
Managing User SSH Keys.
10.67.7.1. hammer user ssh-keys add 复制链接链接已复制到粘贴板!
Create an SSH key for a user
10.67.7.2. hammer user ssh-keys delete 复制链接链接已复制到粘贴板!
Delete an SSH key for a user
10.67.7.3. hammer user ssh-keys info 复制链接链接已复制到粘贴板!
Show an SSH key from a user
10.67.7.4. hammer user ssh-keys list 复制链接链接已复制到粘贴板!
List all SSH keys for a user
10.67.8. hammer user update 复制链接链接已复制到粘贴板!
Update a user
10.68. hammer user-group 复制链接链接已复制到粘贴板!
Manage user groups.
10.68.1. hammer user-group add-role 复制链接链接已复制到粘贴板!
Assign a user role
10.68.2. hammer user-group add-user 复制链接链接已复制到粘贴板!
Associate an user
10.68.3. hammer user-group add-user-group 复制链接链接已复制到粘贴板!
Associate an user group
10.68.4. hammer user-group create 复制链接链接已复制到粘贴板!
Create a user group
10.68.5. hammer user-group delete 复制链接链接已复制到粘贴板!
Delete a user group
10.68.6. hammer user-group external 复制链接链接已复制到粘贴板!
View and manage user group’s external user groups
10.68.6.1. hammer user-group external create 复制链接链接已复制到粘贴板!
Create an external user group linked to a user group
10.68.6.2. hammer user-group external delete 复制链接链接已复制到粘贴板!
Delete an external user group
10.68.6.3. hammer user-group external info 复制链接链接已复制到粘贴板!
Show an external user group for user group
10.68.6.4. hammer user-group external list 复制链接链接已复制到粘贴板!
List all external user groups for user group
10.68.6.5. hammer user-group external refresh 复制链接链接已复制到粘贴板!
Refresh external user group
10.68.6.6. hammer user-group external update 复制链接链接已复制到粘贴板!
Update external user group
10.68.7. hammer user-group info 复制链接链接已复制到粘贴板!
Show a user group
10.68.8. hammer user-group list 复制链接链接已复制到粘贴板!
List all user groups
10.68.9. hammer user-group remove-role 复制链接链接已复制到粘贴板!
Remove a user role
10.68.10. hammer user-group remove-user 复制链接链接已复制到粘贴板!
Disassociate an user
10.68.11. hammer user-group remove-user-group 复制链接链接已复制到粘贴板!
Disassociate an user group
10.68.12. hammer user-group update 复制链接链接已复制到粘贴板!
Update a user group
10.69. hammer virt-who-config 复制链接链接已复制到粘贴板!
Manage Virt Who configurations
10.69.1. hammer virt-who-config create 复制链接链接已复制到粘贴板!
Create a virt-who configuration
10.69.2. hammer virt-who-config delete 复制链接链接已复制到粘贴板!
Delete a virt-who configuration
10.69.3. hammer virt-who-config deploy 复制链接链接已复制到粘贴板!
Download and execute script for the specified virt-who configuration
10.69.4. hammer virt-who-config fetch 复制链接链接已复制到粘贴板!
Renders a deploy script for the specified virt-who configuration
10.69.5. hammer virt-who-config info 复制链接链接已复制到粘贴板!
Show a virt-who configuration
10.69.6. hammer virt-who-config list 复制链接链接已复制到粘贴板!
List of virt-who configurations
10.69.7. hammer virt-who-config update 复制链接链接已复制到粘贴板!
Update a virt-who configuration