hurricane.server
¶
hurricane.server.django
¶
-
class
hurricane.server.django.
DjangoHandler
(application: tornado.web.Application, request: tornado.httputil.HTTPServerRequest, **kwargs: Any)[source]¶ This handler transmits all standard requests to django application. Currently it uses WSGI Container based on tornado WSGI Container.
-
class
hurricane.server.django.
DjangoLivenessHandler
(application: tornado.web.Application, request: tornado.httputil.HTTPServerRequest, **kwargs: Any)[source]¶ This handler runs with every call to the probe endpoint which is supposed to be used
-
class
hurricane.server.django.
DjangoProbeHandler
(application: tornado.web.Application, request: tornado.httputil.HTTPServerRequest, **kwargs: Any)[source]¶ Parent class for all specific probe handlers.
-
class
hurricane.server.django.
DjangoReadinessHandler
(application: tornado.web.Application, request: tornado.httputil.HTTPServerRequest, **kwargs: Any)[source]¶ This handler runs with every call to the probe endpoint which is supposed to be used with Kubernetes ‘Readiness Probes’. The DjangoCheckHandler calls Django’s Check Framework which can be used to determine the application’s health state during its operation.
-
class
hurricane.server.django.
DjangoStartupHandler
(application: tornado.web.Application, request: tornado.httputil.HTTPServerRequest, **kwargs: Any)[source]¶ This handler runs with every call to the probe endpoint which is supposed to be used with Kubernetes ‘Startup Probes’. It returns 400 response for post and get requests, if StartupTimeMetric is not set, what means that the application is still in the startup phase. As soon as StartupTimeMetric is set, this handler returns 200 response upon request, which indicates, that startup phase is finished and Kubernetes can now poll liveness/readiness probes.