Thanks Nadeem for starting a discussion this. I see 2 perspectives for an Administrative API,
(1) Administrative API for setting up/configuring gateways: for example, - adding/updating/removing/disabling a new gateway - setting up authentication for a gateway to use Airavata - setup gateway users for a gateway - enable/disable users/resources for a gateway - setup community credentials/certificates for gateway - etc. Some of these can be mitigated to the gateway itself. But I do not think we need to draw the line at this stage. (2) Administrative API for configuring Airavata: (we are probably not ready for this yet) I'd think this will include managing most of the settings we have in the airavata-server.properties and configurations supporting future implementations of load-balancing, scaling, fault tolerance, policy management etc. On Sat, May 24, 2014 at 1:09 AM, Nadeem Anjum <[email protected]>wrote: > Hi All, > > We are planning to have an administrative API for airavata. Some features > could include authorizing users for gateways, loading the required data as > a service rather than having to do it manually. > > We need to compile a list of required features. Please post your > suggestions on this thread. > > Thanks, > Nadeem. > ----------------------------------- > Sent from my Nexus 4 >
