Thanks for the suggestions Saminda. I agree that we should start off by have an admin service for configuring gateways. We would need to add functions to the thrift interface. Some of these functions could be:
addGateway - to add a new Gaetway updateGateway - to update details pertaining to a gateway deleteGateway - to delete an existing gateway disableGateway - to disable an existing gateway reenableGateway - to re-enable a disabled gateway authenticateGateway - to set up authentication for a gateway to use Airavata enableUser - to enable a user for a gateway disableUser - to disable a user for a gateway enableResource - to enable a resource for a gateway disableResource - to disable a resource for a gateway setCredentials - to set up community credentials or certificates for a gateway. In the data models, we would need to add some structures. Some of these could include: gatewayData - holding all required information pertaining to a gateway, like currentStatus (enabled/disabled), id, enabledUsers etc. userData - holding all required information pertaining to a user like id, enabledGateways etc. resourceData - holding all required information pertaining to a resource, like id, fields describing the resource, enabledGateways etc. Thanks, Nadeem. On Sat, May 24, 2014 at 2:09 PM, Saminda Wijeratne <[email protected]> wrote: > 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 >> > >
