Add APIs for pull model

[vkuznet]

The pull model needs approval API on an agent. Here is a list of APIs:

• transfer request
• delete request
• approve request
• list all requests

[vkuznet]

What we need is to introduce the following:

• request status, e.g. requested, approved, in transfer, success, failed
• request priority
• persistent storage for requests
• request API should allow users to place a request via web/REST calls
• approve API should allow site-admin to approve list of request
• delete API should allow to kill request

Along with web interface we need to develop REST APIs such that we can use any CLI tool to place or approve requests.

[rishiloyola]

Can you tell me more about request priority? Will it depend upon site-admin priorities?

[vkuznet]

We should support different priorities for transfer requests because some can be urgent. Let's say that site admin get requests from few users and from production team. The users requests can wait until production team one will be fulfilled. So, to answer your question, it is not related to site-admin, instead we (as collaboration) may prefer that certain data will appear first on certain site. The interface should allow priority changes, but only certain people will have such privileges.

…

On 0, Rishi ***@***.***> wrote: Can you tell me more about request priority? Will it depend upon site-admin priorities? -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #15 (comment)

[rishiloyola]

General Outline:

I will design request buffer in such a way that we can sort request by some parameters also I will assign a unique id to each request to perform some operations on it.

Note: I will add bulk operation after implementing basic functionality of pull base model.

[vkuznet]

Rishi, this looks fine and you can start coding this.