airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Saminda Wijeratne <>
Subject Re: Application Catalog CPI design
Date Thu, 22 May 2014 04:55:16 GMT
Looking what generally GFac requires I'd say something along the lines of
following would be useful.

   - Functions required to retrieve all the access data of a given
   application id (eg: inputs/outputs/security data/validation data/host
   properties/application properties/job properties etc.)
   - Functions to help gfac scheduling (eg: get all SSH supported
   deployments, get all trestles deployments)
   - Functions validating permissions to use the resources (eg: disabled
   resources, inactive job managers etc)

On Wed, May 21, 2014 at 1:15 AM, Sachith Withana <>wrote:

> Hi folks,
> Here's[1] the initial Application Catalog Design with the basic functions
> regarding the application, deployment, host and gatewayProfile Objects.
> In terms of the users of the App Catalog like the GFac, what kind of
> fine-grained CPI methods are required ?
> ex: should we pass the whole Application Object and expect the GFac to
> deal with it or allow more fine-grained methods to get the inputs, hosts
> ...etc?
> Please note that I haven't included the search functionality in this phase
> of the CPI design.
> [1]
> --
> Thanks,
> Sachith Withana

View raw message