Bug 1309415

Summary:	Allow callback URLs on API endpoints
Product:	Red Hat Ceph Storage	Reporter:	Alfredo Deza <adeza>
Component:	Ceph-Installer	Assignee:	Christina Meno <gmeno>
Status:	CLOSED NOTABUG	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.0	CC:	adeza, anharris, aschoen, ceph-eng-bugs, japplewh, kdreyer, mkarnik, nthomas, sankarshan
Target Milestone:	rc
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-29 13:16:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Alfredo Deza 2016-02-17 18:12:37 UTC

Description of problem:
A client making a request requires a way to be notified once a task completes with all possible available metadata about the task (stdout, stderr, timestamps, exit codes, actual command ran) with an HTTP request done to a provided URL.



Additional info:
Each API endpoint will allow an optional "callback" key with a URL value. That URL will be triggered when a task has finished (this includes error, success, or failure states).

The request for the callback URL will be an HTTP POST with the full JSON metadata of the task.

Comment 1 Alfredo Deza 2016-02-17 18:15:39 UTC

We would need confirmation from the Storage Controller Team if they will be able to commit to implementing the receiving end for this feature.

Callbacks are not yet implemented, the current approach requires a "polling" mechanism to track tasks as they complete.

Comment 3 Mrugesh Karnik 2016-03-01 05:56:04 UTC

(In reply to Alfredo Deza from comment #1)
> We would need confirmation from the Storage Controller Team if they will be
> able to commit to implementing the receiving end for this feature.
> 
> Callbacks are not yet implemented, the current approach requires a "polling"
> mechanism to track tasks as they complete.

Nishanth would be able to comment upon this. Adding him.

Comment 4 Nishanth Thomas 2016-03-12 06:09:16 UTC

We would like to go with polling approach in 1.0. Post 1.0 we will see how to implement the call back fetaure

Comment 6 Christina Meno 2016-12-07 05:53:27 UTC

We discussed this requirement being dropped. Was that from rhscon-3 or should we close won't fix?

Comment 7 Jeff Applewhite 2017-02-21 15:29:29 UTC

once we have a build that removes the calamari fork we will be in a better position to evaluate the performance situation that. Need input from Mrugesh on the ultimate disposition of this one.