Bug 806008

Summary:	[REST API] healt-check url for application is missing
Product:	OKD	Reporter:	Andre Dietisheim <adietish>
Component:	Pod	Assignee:	Krishna Raman <kraman>
Status:	CLOSED DUPLICATE	QA Contact:	libra bugs <libra-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.x	CC:	mfisher, xcoulon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-23 09:35:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andre Dietisheim 2012-03-22 16:41:35 UTC

In the legacy service, one would get a health-check url. This url is the url at which the client library may wait for the application to become reachable (all internal setups were successfull, the app is ready). The typical setup (when using the legacy service) was:

1) request app creation
2) poll the healt-url until it reports 200 OK (and "1" in the response body).

We need the beforementioned attribute at which the readyness-service may be queried or an alternative approach. I guess that it would be ideal to be able to query the application resource and have a state property in the response.

Comment 1 Andre Dietisheim 2012-03-22 18:01:32 UTC

The beforementioned approach to report the application state when GET'ing the application resource is filed in https://bugzilla.redhat.com/show_bug.cgi?id=805989

Comment 2 Andre Dietisheim 2012-03-23 09:35:35 UTC

We suggest that the response to a GET on the application resource would hold a property that reports the application state. This state could report the creation state:

CREATING -> STARTING -> STARTED

I therefore close this issue and add our requirement to https://bugzilla.redhat.com/show_bug.cgi?id=805989

*** This bug has been marked as a duplicate of bug 805989 ***