Reviewing hosts in orcharhino management UI
You can review hosts in the orcharhino management UI to see them in one place and select the columns you need for daily work. When SUSE Linux Enterprise Server lifecycle data is available, check it in the same views to plan patches and track compliance.
Browsing hosts in orcharhino management UI
In the orcharhino management UI, you can browse all hosts recognized by orcharhino, grouped by type.
The following host types are available when browsing hosts in the orcharhino management UI:
-
All Hosts – a list of all hosts recognized by orcharhino.
-
Discovered Hosts – a list of bare-metal hosts detected on the provisioning network by the Discovery plugin.
-
Host Collections – a list of user-defined collections of hosts used for bulk actions such as errata installation.
-
Search for a host: Type in the Search field, and use an asterisk (*) to perform a partial string search. For example, if searching for a host named
server.example.com, click the All Hosts page and typeserver*in the Search field. Alternatively,*ver*will also find the hostserver.example.com.orcharhino Server is listed as a host itself even if it is not self-registered. Do not delete orcharhino Server from the list of hosts.
-
Navigate between hosts: Click ⇄ next to the hostname. This displays a list of hosts in alphabetical order with a pagination arrow and a search bar to find the host you are looking for.
|
During host provisioning, you have to set a Content Source, a Lifecycle Environment, and a Content View to ensure that your host has access to orcharhino Client for SUSE Linux Enterprise Server repositories. Note that you cannot solely set Content Source because provisioning templates expect either no Content Source or values for all three fields. |
Selecting host columns
You can select what columns you want to see in the host table on the Hosts > All Hosts page.
|
It is not possible to deselect the Name column. The Name column serves as a primary identification method of the host. |
-
In the orcharhino management UI, navigate to Hosts > All Hosts.
-
Click Manage columns.
-
Select columns that you want to display. You can select individual columns or column categories. Selecting or deselecting a category selects or deselects all columns in that category.
Some columns are included in more than one category, but you can display a column of a specific type only once. By selecting or deselecting a specific column, you select or deselect all instances of that column.
-
You can now see the selected columns in the host table.
Host global status overview
You can use the host global status in orcharhino to see at a glance whether a host is OK, needs attention (Warning), or has errors. The status appears on the Hosts Overview page and helps you prioritize which hosts to investigate.
The host global status can have one of three possible values: OK, Warning, or Error. You can find global status on the Hosts Overview page. The status displays a small icon next to the host name and has a color that corresponds with the status. Hovering over the icon renders a tooltip with sub-status information to quickly find out more details. To view the global status for a host, in the orcharhino management UI, navigate to Hosts > All Hosts.
- OK
-
No errors were reported by any sub-status. This status is highlighted with the color green.
- Warning
-
While no error was detected, some sub-status raised a warning. For example, there are no configuration management reports for the host even though the host is configured to send reports. It is a good practice to investigate any warnings to ensure that your deployment remains healthy. This status is highlighted with the color yellow.
- Error
-
Some sub-status reports a failure. For example, a run contains some failed resources. This status is highlighted with the color red.
If you want to search for hosts according to their status, use the syntax for searching in orcharhino that is outlined in the Searching and Bookmarking in Administering orcharhino, and then build your searches out by using the following status-related examples:
To search for hosts that have an OK status:
global_status = ok
To search for all hosts that deserve attention:
global_status = error or global_status = warning
Host sub-status overview
You can use host sub-statuses in orcharhino to see the status of specific areas of a host, such as configuration, build, or content. Sub-statuses feed into the global host status and help you pinpoint what needs attention.
To view the sub-statuses of a host, in the orcharhino management UI, navigate to Hosts > All Hosts and click on the host whose full status you want to inspect. You can view the global host status next to the name of the host and the host sub-statuses on the Host status card.
Each sub-status has its own set of possible values that are mapped to the three global status values. With any change of a sub-status, the global status is recalculated and the result is determined by the statuses of all sub-statuses.
The following sub-statuses are available in orcharhino:
- Configuration
-
This sub-status is only relevant if orcharhino uses a configuration management system like Ansible, Puppet, or Salt.
Possible values:
Label Global host status Alerts disabled
OK
Active
OK
Pending
OK
No changes
OK
No reports
OK / Warning
Out of sync
Warning
Error
Error
Additional information about the values of this sub-status:
-
Active: During the last configuration, some resources were applied.
-
Pending: During the last configuration, some resources would be applied but your configuration management integration was configured to run in
noopmode. -
No changes: During the last configuration, nothing changed.
-
No reports: This can be both a Warning or OK status. When there are no reports but the host uses an associated orcharhino Proxy for configuration management or the
always_show_configuration_statussetting is set totrue, it maps to Warning. Otherwise it maps to OK. -
Error: This indicates an error during configuration. For example, a configuration run failed to install a package.
-
Out of sync: A configuration report was not received within the expected interval, based on the
outofsync_intervalsetting. Reports are identified by an origin and can have different intervals based upon it.
-
- Build
-
This sub-status is only relevant for hosts provisioned from orcharhino or hosts registered through global registration.
Possible values:
Label Global host status Number value Installed
OK
0
Pending installation
OK
1
Token expired
Error
2
Installation error
Error
3
- Compliance
-
Indicates if the host is compliant with OpenSCAP policies.
Possible values:
Label Global host status Number value Compliant
OK
0
Inconclusive
Warning
1
At least one incompliant
Error
2
- Execution
-
Status of the last completed remote execution job.
Possible values:
Label Global host status Number value Last execution succeeded / No execution finished yet
OK
0
Last execution failed
Error
1
Unknown execution status
OK
2 or 3
Last execution cancelled
OK
4
- Inventory
-
Indicates if the host is synchronized to Red Hat Hybrid Cloud Console. orcharhino Server performs the synchronization itself but only uploads basic information to Red Hat Hybrid Cloud Console.
Only applies if you have the Red Hat Cloud plugin installed.
Possible values:
Label Global host status Number value Host was not uploaded to your RH cloud inventory
Warning
0
Successfully uploaded to your RH cloud inventory
OK
1
- Insights
-
Indicates if the host is synchronized to Red Hat Hybrid Cloud Console. This synchronization is performed by the host. The host uploads more information than the orcharhino Server.
Possible values:
Label Global host status Number value Reporting
OK
0
Not reporting
Error
1
- Errata
-
Indicates if Errata is available on the host.
Possible values:
Label Global host status Number value Up to date
OK
0
Unknown
Warning
1
Needed errata
Error
2
Needed security errata
Error
3
- Traces
-
Indicates if the host needs a reboot or a process restart.
Possible values:
Label Global host status Number value Unknown
Warning
-1
Up to date
OK
0
Required process restart
Error
1
Required reboot
Error
2
If you want to search for hosts according to their sub-status, use the syntax for searching in orcharhino that is outlined in the Searching and Bookmarking chapter of the Administering orcharhino guide, and then build your searches out by using the following status-related examples:
You search for hosts' configuration sub-statuses based on their last reported state.
For example, to find hosts that have at least one pending resource:
status.pending > 0
To find hosts that restarted some service during last run:
status.restarted > 0
To find hosts that have an interesting last run that might indicate something has happened:
status.interesting = true
|
The text and illustrations on this page are licensed by ATIX AG under a Creative Commons Attribution Share Alike 4.0 International ("CC BY-SA 4.0") license. This page also contains text from the official Foreman documentation which uses the same license ("CC BY-SA 4.0"). |