Enable deployment of availability monitoring
TripleO should have a possibility to automatically setup and install the availability monitoring stack (Sensu and Uchiwa) to service the overcloud.
All components of the availability monitoring will be deployed by TripleO using Heat+Puppet. The sensu-server, sensu-api and uchiwa services will be deployed on a stand alone node deployed by the undercloud, with a dedicated purpose for all optools (not only availability monitoring, but also performance monitoring and centralized logging in future).
The Optools node will be deployed as a separate Heat stack to the overcloud stack.
The sensu-client service will be deployed as a composable role on the overcloud stack. Sensu checks will be configured as subscription checks (see [1] for details). Each composable service will have it's own subscription string, which will ensure that checks are run on the correct overcloud nodes.
[1] https:/
Blueprint information
- Status:
- Complete
- Approver:
- Steven Hardy
- Priority:
- Medium
- Drafter:
- Martin Mágr
- Direction:
- Approved
- Assignee:
- Martin Mágr
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Emilien Macchi
- Completed by
- Emilien Macchi
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
(shardy) +1 on the general ideas here, but I think there are some interactions between the current undercloud sensu integration, composable services and custom roles which would benefit from some discussion, could you please draft a spec where we can discuss this in a bit more detail please?
Gerrit topic: https:/
Addressed by: https:/
Availability monitoring agents support
Gerrit topic: https:/
Addressed by: https:/
[WIP] Heat stack for monitoring/logging node
Gerrit topic: https:/
Addressed by: https:/
Revert "Deploy Monitoring on the undercloud with Puppet"
