Adding Isuru explicitly to the discussion Good question. This is something that we need to properly evaluate the margin of integration between Custos and general Airavata data models. I agree that resources are not directly integrated with Custos but at some point, Resource Service has to talk to Custos to check for the permissions for accessing a particular resource. Based on current standing, I would say resource backend will still talk to Airavata backend class and within Airavata backend, it will talk to Custos only to check for authorization.
Isuru has been doing a lot of exploration in this area and he might have a better explanation than mine. Thanks On Sat, Apr 4, 2020 at 9:16 PM Aravind Ramalingam <poke...@gmail.com> wrote: > Hello, > > As per my current understanding wouldn't the Custos project only act as a > production set up for secret service? To store our API keys or SSH keys. > > Wouldn't we require something additional for the resource service where we > would store our resource information? > > Thank you > Aravind Ramalingam > > On Apr 4, 2020, at 21:07, Suresh Marru <sma...@apache.org> wrote: > > Hi Akshay, > > For production deployments I suggest to integrate with Airavata Custos > services - https://github.com/apache/airavata-custos/tree/develop > > Please ask questions as you explore these. > > Suresh > > On Apr 4, 2020, at 7:29 PM, Rajvanshi, Akshay <aksra...@iu.edu> wrote: > > Hello, > > Currently we did the local setup for the airavata-mft and copied a file > within our VM, but currently we have an implementation for resource and > service backend with file based backend. How do we go about implementing at > the production level ? Are we expected to add the support for the service > we plan to integrate with separately? > > Thanks > > >
