Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Received-SPF: pass (athena.apache.org: domain of samindaw@gmail.com designates
 209.85.217.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACZTvVs1F2u=07yCo3a98-deYevq6cJwf0-wOkg5v2c4v4wh3A@mail.gmail.com>
References: 
 <CACZTvVv_uuRj0nY=f-jTp-T7rDSCNV88szvAO3hX7Y4yZrS2mQ@mail.gmail.com>
 <CACZTvVs1F2u=07yCo3a98-deYevq6cJwf0-wOkg5v2c4v4wh3A@mail.gmail.com>
From: Saminda Wijeratne <samindaw@gmail.com>
Date: Sat, 24 May 2014 01:39:38 -0700
Message-ID: 
 <CANotcz4iQ5yhOUujj+nuiOFqxvNAO_TGfNEvvyLp=84AjBSNjg@mail.gmail.com>
Subject: Re: Administrative API for Airavata
To: dev <dev@airavata.apache.org>
Content-Type: multipart/alternative; boundary=001a11346dde93fa8804fa214a6f

--001a11346dde93fa8804fa214a6f
Content-Type: text/plain; charset=UTF-8

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 <nadeem.cs.iit@gmail.com>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
>

--001a11346dde93fa8804fa214a6f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Thanks Nadeem for starting a discussion this. <b=
r><br>I see 2 perspectives for an Administrative API,<br><br></div>(1) Admi=
nistrative API for setting up/configuring gateways: <br>for example,<br><ul=
>

<li>adding/updating/removing/disabling a new gateway</li><li>setting up aut=
hentication for a gateway to use Airavata</li><li>setup gateway users for a=
 gateway</li><li>enable/disable users/resources for a gateway<br></li>
<li>
setup community credentials/certificates for gateway</li><li>etc.</li></ul>=
<p>Some of these can be mitigated to the gateway itself. But I do not think=
 we need to draw the line at this stage. <br></p>(2) Administrative API for=
 configuring Airavata:<br>

</div>(we are probably not ready for this yet) I&#39;d think this will incl=
ude managing most of the settings we have in the airavata-server.properties=
 and configurations supporting future implementations of load-balancing, sc=
aling, fault tolerance, policy management etc.<br>

<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On =
Sat, May 24, 2014 at 1:09 AM, Nadeem Anjum <span dir=3D"ltr">&lt;<a href=3D=
"mailto:nadeem.cs.iit@gmail.com" target=3D"_blank">nadeem.cs.iit@gmail.com<=
/a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><p dir=3D"ltr">Hi All,</p>
<p dir=3D"ltr">We are planning to have an administrative API for airavata. =
Some features could include authorizing users for gateways, loading the req=
uired data as a service rather than having to do it manually.</p>
<p dir=3D"ltr">We need to compile a list of required features. Please post =
your suggestions on this thread.</p>
<p dir=3D"ltr">Thanks,<br>
Nadeem.<br>
-----------------------------------<br>
Sent from my Nexus 4</p>
</blockquote></div><br></div>

--001a11346dde93fa8804fa214a6f--