[nova][all] Adding /healthcheck support in Nova, and better healthcheck in every projects

Mohammed Naser mnaser at vexxhost.com
Thu Nov 18 01:03:02 UTC 2021

On Wed, Nov 17, 2021 at 5:52 PM Thomas Goirand <zigo at debian.org> wrote:

> On 11/17/21 10:54 PM, Dan Smith wrote:
> >> I don't think we rely on /healthcheck -- there's nothing healthy about
> >> an API endpoint blindly returning a 200 OK.
> >>
> >> You might as well just hit / and accept 300 as a code and that's
> >> exactly the same behaviour.  I support what Sean is bringing up here
> >> and I don't think it makes sense to have a noop /healthcheck that
> >> always gives a 200 OK...seems a bit useless imho
> >
> > Yup, totally agree. Our previous concerns over a healthcheck that
> > checked all of nova returning too much info to be useful (for something
> > trying to figure out if an individual worker is healthy) apply in
> > reverse to one that returns too little to be useful.
> >
> > I agree, what Sean is working on is the right balance and that we should
> > focus on that.
> >
> > --Dan
> >
> That's not the only thing it does. It also is capable of being disabled,
> which is useful for maintenance: one can gracefully remove an API node
> for removal this way, which one cannot do with the root.

I feel like this should be handled by whatever layer that needs to drain
requests for maintenance, otherwise also it might just be the same as
turning off the service, no?

> Cheers,
> Thomas Goirand (zigo)
> --
Mohammed Naser
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20211117/73e7bc23/attachment-0001.htm>

More information about the openstack-discuss mailing list