Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9C4CD113D8 for ; Tue, 24 Jun 2014 20:44:13 +0000 (UTC) Received: (qmail 3743 invoked by uid 500); 24 Jun 2014 20:44:13 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 3693 invoked by uid 500); 24 Jun 2014 20:44:13 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 3683 invoked by uid 99); 24 Jun 2014 20:44:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jun 2014 20:44:13 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of eroma.abeysinghe@gmail.com designates 209.85.216.47 as permitted sender) Received: from [209.85.216.47] (HELO mail-qa0-f47.google.com) (209.85.216.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jun 2014 20:44:07 +0000 Received: by mail-qa0-f47.google.com with SMTP id hw13so730324qab.20 for ; Tue, 24 Jun 2014 13:43:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=B6irmfsNuoAwYCfjGXMbOleqQ7y4UdSEJiGr7bTd5Js=; b=LJ1XGOkB5wU1EMZo8YPLJ9KAItu4ziVF/q4FKGCg1PwDmLcikmgsA76lXHJmQPFW20 I+K8sS2m1qBBkrybuAeMauZU/jZBOXlm21RLfZ4yDyPltY9tTtXsHrbG4JfcIkRxO9qa DV+pq1Hua693+1VBfUugv1Cwl59WZQR9grebwISMpCT8BsXDZNdqwtwsxJIgRg19fBSU lw6BFQi9t5M0r5tTdU+S3y3U1Ognz2Kzh7pxvvHDMyxc5nxZeSaAiQJLzZii49jMvyJe Ttm2c0Mj/iKw7u/9lEzohibHvLjaW/Hzxghdv2TfiRMSQ0EuNr7jE71kvVJcMNNAh10G L78g== X-Received: by 10.140.21.101 with SMTP id 92mr5224137qgk.57.1403642627009; Tue, 24 Jun 2014 13:43:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.37.232 with HTTP; Tue, 24 Jun 2014 13:43:26 -0700 (PDT) From: Eroma Abeysinghe Date: Tue, 24 Jun 2014 16:43:26 -0400 Message-ID: Subject: Airavata Admin Module API To: dev@airavata.apache.org Content-Type: multipart/alternative; boundary=001a11c130e62d3e7504fc9b041a X-Virus-Checked: Checked by ClamAV on apache.org --001a11c130e62d3e7504fc9b041a Content-Type: text/plain; charset=UTF-8 Hello Devs, Hello, Summarizing the offline discussion had with Saminda on Admin module of Airavata. *Open for discussion* Devs, please add anything i have missed out and we need to decide what we are going to add into the gateway admin API and provide UIs in PHP reference gateway in phase I (by the time for XSEDE). In Airavata there are two Admin levels; Airavata admin level & Gateway Admin level. Airavata admin level (user) being the highest level; should be able to create ; 1. Gateways in Airavata 2. Gateway admin users in Airavata for Airavata admin IMO we don't need to provide any UI but providing an API would be sufficient. For Gateway Admin users; 1. Create & maintain gateway users and user roles (e.g. Airavata admin, Gateway admin, standard user, etc...) 2. Create & manage resources 3. Create & manage resource level credentials 4. Create and manage projects 5. Create and manage applications (app catalog) - Assumption: App catalog is managed and records created at gateway admin level. 6. View all experiments in the gateway and their current statuses. Admin user should also be able to terminate/cancel experiments (manage experiments) created by other users. 7. View audit logs and other logs related to experiment executions 8. Statistical report generations - on experiments, users, projects, resources, applications,etc.... -- Thank You, Best Regards, Eroma --001a11c130e62d3e7504fc9b041a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Devs,

Hello,

Summarizing the offline discussion had = with Saminda on Admin module of Airavata.=C2=A0
Open= for discussion
Devs, please add anything i have missed out and we need to dec= ide what we are going to add into the gateway admin API and provide UIs in = PHP reference gateway in phase I (by the time for XSEDE).
In Airav= ata there are two Admin levels;=C2=A0
Airavata admin level & Gateway Admin level.=C2=A0

Airavata admin level (user) being the = highest level; should be able to create ;
  1. Gateways in Airavata
  2. Gateway admin users in Airavata
for Airavata admin IMO we don't need to provide any UI but providi= ng an API would be sufficient.

For Gateway Admin users;
  1. Create & maintain gateway users an= d user roles (e.g. Airavata admin, Gateway admin, standard user, etc...)
  2. Create & manage resources
  3. Create & manage resource level credentials
  4. Create and manage projects
  5. Create and manage applications (app catalog) - Assumption: App catalog is m= anaged and records created at gateway admin level.
  6. View all experiments in the gateway and their current statuses. = Admin user should also be able to terminate/cancel experiments (manage expe= riments) created by other users.
  7. View audit logs and other logs related = to experiment executions
  8. Statistical rep= ort generations - on experiments, users, projects, resources, applications,= etc....

--
Thank You,
Best Regards,
Eroma
--001a11c130e62d3e7504fc9b041a--