Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitoring of OVN Controlplane #16

Open
1 of 13 tasks
fkr opened this issue Apr 7, 2022 · 0 comments
Open
1 of 13 tasks

Monitoring of OVN Controlplane #16

fkr opened this issue Apr 7, 2022 · 0 comments
Assignees
Labels
epic Issues that are spread across multiple sprints IaaS Issues or pull requests relevant for Team1: IaaS Ops Issues or pull requests relevant for Team 3: Ops Tooling

Comments

@fkr
Copy link
Member

fkr commented Apr 7, 2022

As a SCS Operator, I want to make sure that the OVN Controlplane is monitored, so that I'm alerted if the controlplane malfunctions.
In order for that to happen, upstream needs to include the required prometheus exporter.
Once the exporter is included upstream, the necessary alertmanager rules as well as Grafana dashboards need to be roled out by kolla-ansible, as such we need to make sure these are included upstream as well.

Open Items

  • Write out User-Stories for Exporter, Alertmanager as well as Grafana + support tasks such as researching wether Zed or Yoga backport
  • Is OpenStack Zed the proper release to be targeted or is a backport feasible upstream?

Definition of Ready:

  • Acceptance criteria are defined
  • Acceptance criteria are clear and understood by the whole team

Definition of Done:

  • Prometheus exporter is included upstream
  • Alertmanager rules have been merged upstream in kolla-ansible
  • Grafana Dashboards for OVN have been merged upstream in kolla-ansible
  • Targeted release is clear
  • All acceptance criteria are met
  • Changes have been reviewed
  • CI tests have run successfully
  • Documentation has been updated
  • Release Notes have been updated
@fkr fkr added Ops Issues or pull requests relevant for Team 3: Ops Tooling epic Issues that are spread across multiple sprints labels Apr 7, 2022
@fkr fkr self-assigned this Apr 7, 2022
@itrich itrich added this to the v4.0.0 milestone Apr 7, 2022
@fkr fkr mentioned this issue Apr 11, 2022
11 tasks
@fkr fkr modified the milestones: R3 (v4.0.0), R4 (v5.0.0) Oct 4, 2022
@tibeer tibeer mentioned this issue Mar 29, 2023
@fkr fkr removed this from the R4 (v5.0.0) milestone Apr 27, 2023
@fkr fkr added the IaaS Issues or pull requests relevant for Team1: IaaS label Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Issues that are spread across multiple sprints IaaS Issues or pull requests relevant for Team1: IaaS Ops Issues or pull requests relevant for Team 3: Ops Tooling
Projects
Status: Blocked / On hold
Development

No branches or pull requests

2 participants