Consider a separate charm-contrail-service-checks

[sudeephb]

Contrail exposes many API endpoints from various ports. Some can be http or https, but the service checks surrounding those are limited.

perhaps a separate charm to check specifically for contrail apis is worth while.

here's a few api endpoints to support: keepalived bind-definitions contrail ui dashboard

---

Imported from Launchpad using lp2gh.

• date created: 2020-05-28T13:30:38Z

• owner: addyess

• assignee: None

• the launchpad url

[sudeephb]

(by aluria) The current deployment has: """ contrail-haproxy/0* active idle 6/lxd/0 10.X.X.X 8081/tcp,8082/tcp,8143/tcp Unit is ready external-policy-routing/9 active idle 10.X.X.X Unit ready keepalived/0 active idle 10.X.X.X VIP ready landscape-client/54 active idle 10.X.X.X System successfully registered nrpe-container/12 active idle 10.X.X.X icmp,5666/tcp ready """

• keepalived has port 8143, and is related to contrail-haproxy (contrail-haproxy:juju-info <-> keepalived:juju-info)
• contrail-haproxy is related to contrail-controller over http-services (8082) and https-services (8143).
• contrail-haproxy is related to contrail-analytics over http-services (8081)

OTOH,

• charm-openstack-service-checks can already monitor port 8081 if contrail_analytics_vip Juju parameter is set to the keepalive VIP.

We would need something similar to the OpenStack API endpoint nrpe checks, via the check_http tool. Checking if "-e Unauthorized" is found should be enough.

As suggested by Adam, having charm-contrail-service-checks would avoid polluting charm-openstack-service-checks.

[sudeephb]

(by xavpaice) Marking this as wishlist, as it's a request not just for a new feature but an entirely new charm/project, which needs a proper spec and design.

[sudeephb]

(by eric-chen) This charm is no longer being actively maintained. Please consider using the new Canonical Observability Stack instead. (https://charmhub.io/topics/canonical-observability-stack) I will close this feature request