airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nipurn Doshi <nido...@umail.iu.edu>
Subject App catalog considerations
Date Wed, 03 Dec 2014 03:22:19 GMT
Hi Devs,

I have been developing Laravel version of the Gateway interface since about
two months now. It now incorporates features of the old interface with
respect to Projects and Experiments. It now also contains UI for the Admins
for managing Compute resources and App Catalog( App Modules, App Interfaces
and App Deployments ).

The link to that is the interface is here -
 test-drive.airavata.org/pga/public/
<http://test-drive.airavata.org/pga/public/>

Sudhakar and I had a discussion about the Admin management today evening
and he had a few points that I would like to share with the devs here -

   - Admins should have the ability to make an Application available for
   production and take it down anytime when required.
   - Resource specific publication services should help in automation of
   modifications to Compute Resources. Admins should only have to
   approve/reject these modifications. These would help in lessening work on
   the Admin side.
   - Queues should have more controllable attributes like Max Memory limit
   and sucharge.
   - Queues should show dynamic variables specific to each queue to
   admins/users like -
      - Running Jobs
      - Waiting Jobs
   - In application interfaces, "ApplicationArgument" should be able to
   take multiple argument flags than just one

These topics are open for discussion and views. Feel free to make your
comments.

-- 
-Regards,
Nipurn Doshi

Mime
View raw message