1. Mac Tools Air Hammer
2. Mac Option Key

How to use Hammer Time! For PC and MAC You can run all Android games and applications on your PC or MAC computer. Using a free software called Bluestacks, you don't need to purchase anything but games or applications it self if it isn't free. Download Bluestacks from.

Install BlueStacks from installation file with following the on-screen instructions. Once Bluestacks is installed add your Google account in it. Type Hammer Time! In Search bar and install it. Now you can use Hammer Time!

Sep 14, 2015 - Anyways, my question is, as stated in the title, is Hammer Editor Mac. I tried setting up Wineskin like Mudpie did but I couldn't be arsed trying. If you want to explore the options Hammerspoon offers, check out the Getting. Have iTunes automatically start playing when your Mac detects you are in Paris.

On your PC or MAC.

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 for more information.

Create the file /.hammer/cliconfig.yml and add the following contents to the file::foreman::host: ':username: 'username':password: 'password' Replace the example values with your own details. Do not use tabs in the file, always use indentation by spaces.

To protect your password, make sure the file is readable only by the current user: $ chmod 600 /.hammer/cliconfig.yml. Save and close the file. Now when you start hammer it will use the credentials in the /.hammer/cliconfig.yml file. 1.4. Setting a Default Organization Many hammer commands are organization specific. You can set a default organization, as well as location, for hammer commands so that you do not have to specify it every time using the -organization-id parameter.

To do so, issue: $ hammer defaults add -param-name organizationid -param-value Find in the output of the hammer organization list command. Similarly, you can set the default location as follows: $ hammer defaults add -param-name locationid -param-value To view the currently specified default settings, issue the following command: $ 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. 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, 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/cliconfig.yml. Note that these directives affect only the current user and are not applied globally.:loglevel: 'warning':logsize: 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.

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 Output in CSV format is useful for example when you need to parse IDs and use them in a for loop (see or ). Several other formatting options are available with the -output option: $ hammer -output organization list Replace with one of. 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: $ hammer ping candlepin: Status: ok Server Response: Duration: 22ms candlepinauth: Status: ok Server Response: Duration: 17ms pulp: Status: ok Server Response: Duration: 41ms pulpauth: Status: ok Server Response: Duration: 23ms foremantasks: Status: ok Server Response: Duration: 33ms.

is the name of the organization. This parameter is required. 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). is a short description of the organization.

Mac Tools Air Hammer

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. 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 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 This approach is used in examples in this guide. If you mostly manage a single organization, store its ID as a default parameter, for example: $ hammer defaults add -param-name organizationid -param-value 1 With the above setting, organization specific commands will assume -organization-id 1 is specified, so you no longer have to type it.

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 ' ' -name ' ' -organization-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).

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: $ hammer sync-plan create -name ' ' -enabled=true -interval -organization-label -sync-date ' ' Replace with hourly, daily, or weekly. Replace with the date and time of the initial synchronization in the form of 'YYYY-MM-DD HH:MM:SS'. The following command creates a daily synchronization schedule for the ACME organization, that runs at 3 a.m., starting from 15 January 2016: $ hammer sync-plan create -name 'daily sync at 3 a.m.' -enabled=true -interval daily -organization $ORG -sync-date '2016-01-15 03:00:00' To associate the synchronization plan with a product, issue the following command: $ hammer product set-sync-plan -organization-label -name ' ' -sync-plan ' '.

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 ' ' -organization-label The following command creates a new repository under the custom product: $ hammer repository create -name ' ' -organization-label -product ' ' -content-type -publish-via-http true -url ' ' Replace the example values with your own details, in particular. specifies the type of content in the repository, choose one of yum, puppet, or docker. 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 ' ' -organization-label -id ' ' -path Replace with the path to the directory with content (RPM packages, Puppet modules, or Docker images) to be added to the custom repository. 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 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 The output of the above command can look as follows: - - - ID NAME PRIOR - - - 2 Library 5 Development Library 6 Testing Development - - - 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 -repository-ids, -description ' ' -organization-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.

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 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.name -organization-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 -name -repository-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.

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: $ hammer content-view filter create -type rpm -name exclude-emacs -description 'Excluding emacs package' -inclusion false -organization $ORG -repository-ids 1,2,3 -content-view cv-rhel7-server 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 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. 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. Create a filter for the Content View as follows: $ hammer content-view filter create -type erratum -name limit-errata-by-date -description 'Excluding errata by date' -inclusion false -organization $ORG -repository-ids 1,2,3 -content-view cv-rhel7-server Create a rule to exclude errata with a name starting with 'emacs' and add it to the filter as follows: $ hammer content-view filter rule create -end-date -organization $ORG -content-view cv-rhel7-server -content-view-filter limit-errata-by-date -types enhancement,bugfix,security. 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 -organization-label -async Find the 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. 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 -packages, -lifecycle-environment-ids,. 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 ).

For more information on working with incremental updates issue hammer content-view version incremental-update -help. Find the Content View your host is registered to as well as its life cycle environment by executing: $ hammer content-host info -name auth01.example.com -organization $ORG. Then find the current version of the Content View (assuming Content View name RHEL7Infra): $ hammer content-view info -name 'RHEL7Infra' -organization $ORG. Find the IDs of errata you want to apply in the list of applicable errata in Library: $ hammer erratum list -content-view 'RHEL7Infra' -organization $ORG $ hammer host errata list -host auth01.example.com.

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. 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. Activation key with the exact set of subscriptions – hosts using the activation key are associated with all subscriptions specified in the activation key. 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 -organization-label -content-view -lifecycle-environment 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 -subscription-id To find the activation key ID, use hammer activation-key list; to find the subscription ID, use hammer subscription list. 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 Add a subscription to the activation key: $ 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. 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 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. 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: $ hammer subnet create -name -organization-ids.boot-mode -network -mask -ipam Here, is one of Static or DHCP, 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.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 -organization-ids.provider Here, 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 To add a new medium, issue the following command: $ hammer medium create -name -path 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 To create a new partition table, issue the following command: $ hammer partition-table create -name -file -os-family See the output of the hammer partition-table -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 To create a new operating system, issue the following command: $ hammer os create -name -major 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. 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: $ hammer hostgroup create -name ' ' -environment ' ' -architecture ' ' -domain -subnet -puppet-proxy -puppet-ca-proxy -operatingsystem ' ' -partition-table ' ' -medium ' ' -organization-ids. See hammer hostgroup create -help for the full list of configurable options.

There are two settings that cannot be configured during host group creation. 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: $ hammer host create -name ' ' -hostgroup ' ' -interface='primary=true, provision=true, mac=, ip= ' -organization-id -location-id -ask-root-password yes 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. If you decide to create a host without host group membership, specify additional options described in.

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 for reference. Keys Description type Defines the interface type, one of Nic::Managed, Nic::BMC, Nic::Bond. Name, identifier Identification of the interface. Mac, ip, domain (or domainid), subnet (or subnetid) Network settings, domain and subnet identification can be inherited from the host group. Primary, provision, managed, virtual Accept true or false. Managed hosts needs to have one primary and provisioning interface.

Specific to virtual interfaces tag VLAN tag, this attribute has precedence over the subnet VLAN ID. Attachedto Identifier of the interface to which the virtual interface belongs, for example eth1. Specific to bonded interfaces mode Bonding mode, one of balance-rr, active-backup, balance-xor, broadcast, 802.3ad, balance-tlb, balance-alb. Specific to BMC interfaces provider BMC provider, set to IPMI.

Username, password BMC access credentials. Specific to hosts provisioned on Libvirt computetype Interface type, one of bridge, network. Computenetwork or computebridge Specifies interface name, pick one depending on the interface type. Computemodel One of virtio, rtl8139, ne2kpci, pcnet, e1000. Specific to hosts provisioned on RHEV computename Interface name, for example eth0. Computenetwork Select one of the available networks for a cluster, use UUID from RHEV. Specific to hosts provisioned on VMware computetype Type of the network adapter, depends on your version of vSphere.

Mac Option Key

Computenetwork Network ID form VMware. Provider Keys Keys for the -compute-attributes option EC2 flavorid, imageid, availabilityzone, securitygroupids, managedip GCE machinetype, imageid, network, externalip Libvirt cpus, memory, start OpenStack flavorref, imageref, tenantid, securitygroups, network RHEV cluster, template, cores, memory, start VMware cpus, corespersocket, memorymb, cluster, path, guestid, scsicontrollertype, hardwareversion, start Keys for the -volume option Libvirt pollname, capacity, formattype RHEV sizegb, storagedomain, bootable VMware datastore, name, sizegb, thin, eagerzero. The following example shows how to create a host with a bonded interface pair. For more information on interface bonding see the. $ hammer host create -name bondtest -hostgroup-id 1 -ip=192.168.100.123 -mac=52:54:00:14:92:2a -subnet-id=1 -managed true -interface='identifier=eth1, mac=52:54:00:62:43:06, managed=true, type=Nic::Managed, domainid=1, subnetid=1' -interface='identifier=eth2, mac=52:54:00:d3:87:8f, managed=true, type=Nic::Managed, domainid=1, subnetid=1' -interface='identifier=bond0, ip=172.25.18.123, type=Nic::Bond, mode=active-backup, attacheddevices=eth1,eth2, managed=true, domainid=1, subnetid=1' -organization-id 1 -location-id 1 -ask-root-password yes. 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 -name To add hosts to a host collection, issue the following command: $ hammer host-collection add-host -id -host-ids.

Run the following command to associate a host collection with an activation key (see for details on activation keys): $ hammer activation-key add-host-collection -id -host-collection 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 manage software packages or start a Puppet process on remote hosts. For more information about remote execution on Satellite, see the section of the Host Configuration Guide. To use this feature in Hammer, install the remote execution CLI module by executing the following command as root: # yum install tfm-rubygem-hammercliforemanremoteexecution To list job templates available, issue: $ hammer job-template list To create a job template using a template-definition file, use a command as follows: $ hammer job-template create -file ' ' -name ' ' -provider-type SSH -job-category ' ' Replace with the path to the file containing the template definition. Specify a custom 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 ' ' -inputs =' ', =' '.search-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 with the filter expression defining which hosts will be affected (for example 'name rex01'). 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' To monitor the job output, issue: $ hammer job-invocation output -id -host Find the 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. 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: $ hammer user create -login -password -mail -auth-source-id 1 -organization-ids. 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 To add a user to a user group, issue the following command: $ hammer user-group add-user -user -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 To view permissions associated with a role, issue the following command: $ hammer role filters -id Here, 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 Add a permission filter to the role with the following command: $ hammer filter create -role -permission-ids. 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. 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 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 in the Satellite Server Administration Guide for more information. 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 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' For more information on syntax used in the -search option, refer to the.

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 Replace 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. 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 the. In Red Hat Satellite, you can deploy containers only on a compute resource of the Docker provider type. See the for instructions on how to prepare a container host.

To register this host as a compute resource, issue the following command: $ hammer compute-resource create -name -organization-ids.url -provider docker Use the following syntax to provision a container on the compute resource: $ hammer docker container create -name -compute-resource-id -repository-name -tag -command Find the compute resource ID in the output of hammer compute-resource list. Replace 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 ), or the official Red Hat image repository. If you provision from a Content View, replace with the name of the Content View. See 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 For the full list of container related options, see the output of the hammer docker container -help command.