Bug 1498360

Summary: OPS Tools | Availability Monitoring | Health checks representation in Uchiwa should be redone because of containers introduction in osp12.
Product: Red Hat OpenStack Reporter: Leonid Natapov <lnatapov>
Component: opstools-ansibleAssignee: Lars Kellogg-Stedman <lars>
Status: ON_DEV --- QA Contact: Leonid Natapov <lnatapov>
Severity: high Docs Contact:
Priority: unspecified    
Version: 12.0 (Pike)CC: cjanisze, jbadiapa, karatecletus323, lars, mmagr, mrunge, rmccabe
Target Milestone: ---Keywords: Tracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Leonid Natapov 2017-10-04 06:51:03 UTC
Health checsk representation in Uchiwa should be redone because of containers introduction in osp12.

In OSP11 we had checks for each service and each service was shown in Uchiwa along with its status (active,not active,etc).

In OSP12 with introduction of the containers we have one single check docker_health_check that shows unhealthy containers under its "output" which looks very user unfriendly and really hard to understand what is going on.

Here is the example of how it looks like: 

--------------
output:
/nova_vnc_proxy (71529e4ffa5e): There is no nova-novncproxy process with opened RabbitMQ ports (5671,5672) running in the container /ceilometer_agent_central (3493da8311b5): There is no ceilometer-poll process with opened RabbitMQ ports (5671,5672) running in the container /aodh_evaluator (00fa97538ae5): There is no aodh-evaluator process with opened RabbitMQ ports (5671,5672) running in the container
-------------

We have to show in Uchiwa a list of containers each one shows its status (healthy/unhealthy)

Comment 1 Martin Magr 2017-11-08 11:46:24 UTC
*** Bug 1505321 has been marked as a duplicate of this bug. ***

Comment 2 Martin Magr 2017-11-08 11:49:39 UTC
*** Bug 1510409 has been marked as a duplicate of this bug. ***

Comment 3 Martin Magr 2017-11-22 18:30:49 UTC
*** Bug 1510408 has been marked as a duplicate of this bug. ***