Feature #10782
closed
Add global status for hosts
Added by Tomáš Strachota over 9 years ago.
Updated over 6 years ago.
Description
As a support for OpenScap reports and other future types of reports, we need to add a global status to hosts.
Host will have one generic overall status (error, warning, ok) and it's transitions will be caused by other specific statuses. Statuses (e.g. puppet status) will be extracted to separate entity and will be
changed when puppet report is imported (by PuppetReportImporter). This means we need a way to register new report types and importers from plugin (exactly the same we have for facts now). Reports will probably only differ in metrics and their own statuses, therefore we should make metrics optional and mapping to global status should be different per specific status.
User stories:
- As a developer I want to have global host state with developer API allowing me to change it easily.
- As a developer I want to register new host status type and define mapping between it and host global state.
- As a user I want to be able to search based on host global status.
- As a user I want to see the overall host status derived from all report types statuses.
- Related to Feature #4151: Add STI to reports and allow for registering new report types added
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2580 added
- Pull request deleted (
)
- Assignee changed from Tomáš Strachota to Marek Hulán
- Translation missing: en.field_release set to 63
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Feature #11699: Use new ConfigurationStatus for Salt report importing added
- Related to Bug #11704: Configuration no report appears as "green" icon added
- Related to Bug #11707: Unmanaged host detail status table is broken added
- Related to Bug #11708: New status code broke discovery plugin API added
- Related to Bug #11771: Saving host without particular status fails added
- Related to Bug #11834: host status migration is very slow added
- Related to Bug #11835: db migration fail on report status added
- Related to Feature #11872: Add a compliance status using Foreman 1.10 API added
- Related to Feature #12213: Support for preferring a particular host status in the global view added
- Related to Bug #13456: Different Icon for Pending changes ? added
- Related to Bug #13939: API v1 hosts rabl references deprecated puppet_status call added
- Related to Bug #14501: Global status icon does not indicate active or pending configuration status added
- Related to Bug #15213: DHCP conflict detection fails with exception if proxy is unavailable added
- Related to Bug #15362: Global status audit display status numbers instead of label added
- Related to Refactor #15849: Improve performance of host global status updates added
- Related to Bug #17897: Response of the api to get host status in the apidoc is incorrect with the actuals added
Also available in: Atom
PDF