Skip to content

Add Blackbox monitoring for backend endpoints #1332

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

Merged
merged 1 commit into from
Nov 8, 2024

Conversation

Alex-Welsh
Copy link
Member

@Alex-Welsh Alex-Welsh commented Oct 15, 2024

Adding backend blackbox endpoint monitoring.

Some service do not support TLS at all (e.g. Blazar)
Some services do support TLS, and they have a globally-scoped variable (e.g. Neutron, neutron_enable_tls_backend)
Some services do support TLS, but have locally scoped variables, so must use the generic kolla_enable_tls_backend (e.g. Nova)

This is a precursor to proper support in Kolla-Ansible, which I'm planning on doing with file-based service discovery

@Alex-Welsh Alex-Welsh requested a review from a team as a code owner October 15, 2024 15:45
@Alex-Welsh
Copy link
Member Author

For context, this has been tested in a Multinode.

Confirmed working:

  • barbican
  • cinder
  • designate
  • glance
  • heat
  • heat_cfn
  • horizon
  • magnum
  • neutron
  • nova
  • octavia
  • placement

Untested (not deployed by multinode):

  • blazar
  • gnocchi
  • manila
  • ironic
  • ironic inspector
  • swift

Example templated content:

targets:
    - cinder_backend_rockyovnfqdncontroller01:os_endpoint:https://192.168.37.3:8776
    - cinder_backend_rockyovnfqdncontroller02:os_endpoint:https://192.168.37.4:8776
    - cinder_backend_rockyovnfqdncontroller03:os_endpoint:https://192.168.37.5:8776
    - designate_backend_rockyovnfqdncontroller01:os_endpoint:http://192.168.37.3:9001
    - designate_backend_rockyovnfqdncontroller02:os_endpoint:http://192.168.37.4:9001
    - designate_backend_rockyovnfqdncontroller03:os_endpoint:http://192.168.37.5:9001

@Alex-Welsh
Copy link
Member Author

Updated to include a warning about having separate monitoring nodes

@Alex-Welsh Alex-Welsh force-pushed the backend-blackbox-caracal branch from 220ec7f to 7b0d822 Compare October 21, 2024 15:06
@Alex-Welsh Alex-Welsh force-pushed the backend-blackbox-caracal branch from 7b0d822 to af3d1c9 Compare October 21, 2024 15:09
dougszumski
dougszumski previously approved these changes Oct 25, 2024
Copy link
Member

@dougszumski dougszumski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Alex!

@Alex-Welsh
Copy link
Member Author

@dougszumski I've fixed that typo, could you do a quick re-review?

Copy link
Member

@dougszumski dougszumski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Alex!

@Alex-Welsh Alex-Welsh merged commit fc5dc49 into stackhpc/2024.1 Nov 8, 2024
19 checks passed
@Alex-Welsh Alex-Welsh deleted the backend-blackbox-caracal branch November 8, 2024 11:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants