Hi Anuj, This is great summary. Since this is a new capability for Airavata, it will be useful to have dedicated wiki space to record all information. We can start with a high-level problem description (you have some of that in the form of use cases), architecture and design thoughts and Implementation plan (pointers to JIRA’s).
May be you can put it under - https://cwiki.apache.org/confluence/display/AIRAVATA/Architecture+Documentation <https://cwiki.apache.org/confluence/display/AIRAVATA/Architecture+Documentation> Mark and Terri might have some input on this task since CIPRES enforces soft quotas for users (but I guess there is no formal allocation request process). Once you have the wiki we can gather the feedback also there. Thanks, Suresh > On Sep 23, 2016, at 2:39 PM, Anuj Bhandar <[email protected]> wrote: > > Hi Dev, > > I have undertaken this project of designing and developing an resource > allocation service for Airavata, to give you some context, this service takes > inspiration from XRAS (XSEDE Resource Allocation Service). > > Here is the preliminary design document, which was written as a part of > GSOC-2016, > https://cwiki.apache.org/confluence/display/AIRAVATA/%5BGsoc+Proposal%5D+Resource+Allocation+Manager+for+Apache+Airavata. > > I have derived some use cases by discussing with Sudhakar Pamidighantam ( PI > - GridChem), here is the link : > https://issues.apache.org/jira/browse/AIRAVATA-2108. > > Any comments and improvements are gladly welcome. > > Thanks and best regards, > > Anuj Bhandar >
