How can we help?
Searching in {{docApp.searchFilterBySpecificBookTitle}}
{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}}
in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.
You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
-
{{resultItem.title}}
{{resultItem.url}}
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
Linux Package Management
Control/automate management of Red Hat RPM Software Packages
Package Details
- Vendor: Linux
- Target Platform: Linux
- Package Type: Server and Workstation Management
Why use this
Reduce IT ops workloads with quick/automated control over Red Hat packages
Empower IT ops and your service desk with direct remote control over Red Hat RPM packages. Automate routine IT ops workloads (such as package updates) to give teams more time for new technology projects.
Benefits
- Automate mass updates to reduce effort by up to 95%
- Eliminate human errors
- Reduce call times by empowering service desk agents with control over Red Hat packages
How to get it
- You can try out ITOM for free (not for production use, limited runs) by installing the ITOM application from the Hornbill App Store.
- If you would like to explore ITOM and consider subscribing, please contact your account manager here.
Requirements
- Install the Hornbill Site Integration Server inside your firewall (if you don’t already have it).
Authentication
When creating jobs for operations contained within this package, they need to be run on the target machine as a user who has the correct privileges within your environment. To create and securely store keys:
- In the Configuration area of your Hornbill instance, navigate to Platform Configuration > Security > KeySafe;
- Click on the + Create New Key button, then select Username + Password;
- Give the KeySafe Key a Title (this is the name/identifier for the Active Directory account as you will see it when creating an IT Automation Job, or adding an IT Automation node to a Workflow);
- Optionally add a Description;
- Populate the Username field with the username for the account being used on the target machine;
- Populate the Password field with the password for the above account;
- Select Create Key to save.
Once you have created your KeySafe Key, you can then use it to populate the Credentials > Admin or Run As inputs when creating IT Automation Jobs from this package.
Credentials
Except for the Is Package Installed operation, Accounts used when executing jobs against operations contained within this package must adhere to the following requirements:
- The target machine must have a local admin user that will be used for running the operations;
- SSH Remote Login must be enabled for the user above user
- Configuration for the user must be added to the sudoers file on the target machine, to allow the above user to sudo without a password (example: someadminuser ALL = (ALL) NOPASSWD:ALL).
Package Automations
Operation | Description |
---|---|
Auto Remove Packages | Remove packages installed to meet the dependencies of other packages, but are |
Clean Package Cache | Removes the content of the yum cache (yum clean). The type of data must be specified (default is packages), with the full list of options are: all / headers / metadata / packages. |
Install Package | Install a package using yum install. |
Is Package Installed | Confirm the installation of a package using yum info, if installed the package version is returned. |
Remove Package | Remove a package using yum remove. |
Upgrade All Packages | Update package database and upgrade all installed packages. (yum update ) |
See also
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}