Supun, You mean have PGA call the sharing API directly?
On Jul 24, 2017, at 4:55 PM, Supun Nakandala <[email protected]<mailto:[email protected]>> wrote: I think carving out the group management API methods to a separate service is better. In the current version user information is stored in profile service and replicated in sharing service. But I think for groups we can use the sharing group implementation directly. WDYT Marcus? On Mon, Jul 24, 2017 at 4:45 PM, Christie, Marcus Aaron <[email protected]<mailto:[email protected]>> wrote: I would assume that we can just take the group management API methods from airavata_api.thrift and move them into a new thrift file for this new group management service. Is the idea that groups would be stored in the profile_service database and replicated to the sharing registry? On Jul 24, 2017, at 1:29 PM, Shenoy, Gourav Ganesh <[email protected]<mailto:[email protected]>> wrote: You would need to add new Thrift interfaces/models under "thrift-interface-descriptions/service-cpis/profile-service". After writing the thrift models/interfaces, you’ll need to generate the Java/PHP/C++ stubs. As far as the handler, you would need to manually create a handler class and implement the appropriate "Iface" class within the generated service class. You can refer to any of the previous tenant/user service handler class. Thanks and Regards, Gourav Shenoy From: Sneha Tilak <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Monday, July 24, 2017 at 1:23 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Cc: "Christie, Marcus Aaron" <[email protected]<mailto:[email protected]>> Subject: Re: Exposing Sharing Service through PGA Thanks, Gaurav. Is there any automated way to generate the handler or should it be done manually so that we can generate the Thrift stubs. I am familiar with generating the stubs to be later included in the PGA libraries. Regards, Sneha Tilak Regards, Sneha Tilak On Mon, Jul 24, 2017 at 1:07 PM, Shenoy, Gourav Ganesh <[email protected]<mailto:[email protected]>> wrote: Hi Sneha, If I recollect correctly, the roadmap to introduce the “Airavata-Services” SDK included the Profile Service which consisted of 3 components – user, tenant and groups. Currently, we have implemented the user and tenant SDKs. I am assuming, if you want to allow management of the groups (via sharing) at the PGA or via service APIs, you will need to add a new implementation/service for groups in the "profile-service" – something like "profile-group-core", and add thrift server handler to "profile-service-server". Hope this helps! Thanks and Regards, Gourav Shenoy From: Sneha Tilak <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Monday, July 24, 2017 at 12:53 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "Christie, Marcus Aaron" <[email protected]<mailto:[email protected]>> Subject: Exposing Sharing Service through PGA Hi dev / Marcus, I have been working on implementing a UI to create and manage user groups in Airavata. For this, we have to expose the Sharing Registry services to the PGA. What would be the best way to do this? Marcus, would this be similar to what we did for the Keycloak and Tenant profile features? Regards, Sneha Tilak
