You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Sneha Tilak <sn...@gmail.com> on 2017/07/24 16:53:47 UTC
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*
Re: Exposing Sharing Service through PGA
Posted by Supun Nakandala <su...@gmail.com>.
Yes. Also, I think we don't need to duplicate group information anywhere
else. We can use the groups in the sharing service as the primary and only
location where we store groups.
On Tue, Jul 25, 2017 at 11:03 AM, Sneha Tilak <sn...@gmail.com>
wrote:
> Yes, Gourav. To portray the sharing service as an independent service, I
> think this was Suresh's intention as well.
>
> - Sneha Tilak
>
>
> On Jul 25, 2017 11:00 AM, "Shenoy, Gourav Ganesh" <go...@indiana.edu>
> wrote:
>
> I think what Supun meant is to make Sharing an independent service, i.e.
> not include it as part of the profile-service. But instead of maintaining a
> different database at the service level (like how we have a profile-service
> db), and then replicating that info at the registry via events, directly
> manipulate the sharing registry db. Am I right Supun?
>
>
>
> Thanks and Regards,
>
> Gourav Shenoy
>
>
>
> *From: *"Christie, Marcus Aaron" <ma...@iu.edu>
> *Date: *Tuesday, July 25, 2017 at 9:49 AM
> *To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
> *Cc: *"Shenoy, Gourav Ganesh" <go...@indiana.edu>
>
> *Subject: *Re: Exposing Sharing Service through PGA
>
>
>
> Supun,
>
>
>
> You mean have PGA call the sharing API directly?
>
>
>
>
>
> On Jul 24, 2017, at 4:55 PM, Supun Nakandala <su...@gmail.com>
> 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 <ma...@iu.edu>
> 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 <go...@indiana.edu>
> 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 <sn...@gmail.com>
> *Reply-To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
> *Date: *Monday, July 24, 2017 at 1:23 PM
> *To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
> *Cc: *"Christie, Marcus Aaron" <ma...@iu.edu>
> *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 <
> goshenoy@indiana.edu> 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 <sn...@gmail.com>
> *Reply-To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
> *Date: *Monday, July 24, 2017 at 12:53 PM
> *To: *"dev@airavata.apache.org" <de...@airavata.apache.org>, "Christie,
> Marcus Aaron" <ma...@iu.edu>
> *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*
>
>
>
>
>
>
>
>
>
>
>
Re: Exposing Sharing Service through PGA
Posted by Sneha Tilak <sn...@gmail.com>.
Yes, Gourav. To portray the sharing service as an independent service, I
think this was Suresh's intention as well.
- Sneha Tilak
On Jul 25, 2017 11:00 AM, "Shenoy, Gourav Ganesh" <go...@indiana.edu>
wrote:
I think what Supun meant is to make Sharing an independent service, i.e.
not include it as part of the profile-service. But instead of maintaining a
different database at the service level (like how we have a profile-service
db), and then replicating that info at the registry via events, directly
manipulate the sharing registry db. Am I right Supun?
Thanks and Regards,
Gourav Shenoy
*From: *"Christie, Marcus Aaron" <ma...@iu.edu>
*Date: *Tuesday, July 25, 2017 at 9:49 AM
*To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
*Cc: *"Shenoy, Gourav Ganesh" <go...@indiana.edu>
*Subject: *Re: Exposing Sharing Service through PGA
Supun,
You mean have PGA call the sharing API directly?
On Jul 24, 2017, at 4:55 PM, Supun Nakandala <su...@gmail.com>
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 <ma...@iu.edu>
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 <go...@indiana.edu>
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 <sn...@gmail.com>
*Reply-To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
*Date: *Monday, July 24, 2017 at 1:23 PM
*To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
*Cc: *"Christie, Marcus Aaron" <ma...@iu.edu>
*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 <go...@indiana.edu>
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 <sn...@gmail.com>
*Reply-To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
*Date: *Monday, July 24, 2017 at 12:53 PM
*To: *"dev@airavata.apache.org" <de...@airavata.apache.org>, "Christie,
Marcus Aaron" <ma...@iu.edu>
*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*
Re: Exposing Sharing Service through PGA
Posted by "Shenoy, Gourav Ganesh" <go...@indiana.edu>.
I think what Supun meant is to make Sharing an independent service, i.e. not include it as part of the profile-service. But instead of maintaining a different database at the service level (like how we have a profile-service db), and then replicating that info at the registry via events, directly manipulate the sharing registry db. Am I right Supun?
Thanks and Regards,
Gourav Shenoy
From: "Christie, Marcus Aaron" <ma...@iu.edu>
Date: Tuesday, July 25, 2017 at 9:49 AM
To: "dev@airavata.apache.org" <de...@airavata.apache.org>
Cc: "Shenoy, Gourav Ganesh" <go...@indiana.edu>
Subject: Re: Exposing Sharing Service through PGA
Supun,
You mean have PGA call the sharing API directly?
On Jul 24, 2017, at 4:55 PM, Supun Nakandala <su...@gmail.com>> 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 <ma...@iu.edu>> 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 <go...@indiana.edu>> 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 <sn...@gmail.com>>
Reply-To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>
Date: Monday, July 24, 2017 at 1:23 PM
To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>
Cc: "Christie, Marcus Aaron" <ma...@iu.edu>>
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 <go...@indiana.edu>> 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 <sn...@gmail.com>>
Reply-To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>
Date: Monday, July 24, 2017 at 12:53 PM
To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>, "Christie, Marcus Aaron" <ma...@iu.edu>>
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
Re: Exposing Sharing Service through PGA
Posted by "Christie, Marcus Aaron" <ma...@iu.edu>.
Supun,
You mean have PGA call the sharing API directly?
On Jul 24, 2017, at 4:55 PM, Supun Nakandala <su...@gmail.com>> 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 <ma...@iu.edu>> 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 <go...@indiana.edu>> 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 <sn...@gmail.com>>
Reply-To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>
Date: Monday, July 24, 2017 at 1:23 PM
To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>
Cc: "Christie, Marcus Aaron" <ma...@iu.edu>>
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 <go...@indiana.edu>> 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 <sn...@gmail.com>>
Reply-To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>
Date: Monday, July 24, 2017 at 12:53 PM
To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>, "Christie, Marcus Aaron" <ma...@iu.edu>>
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
Re: Exposing Sharing Service through PGA
Posted by Supun Nakandala <su...@gmail.com>.
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 <ma...@iu.edu>
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 <go...@indiana.edu>
> 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 <sn...@gmail.com>
> *Reply-To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
> *Date: *Monday, July 24, 2017 at 1:23 PM
> *To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
> *Cc: *"Christie, Marcus Aaron" <ma...@iu.edu>
> *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 <
> goshenoy@indiana.edu> 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 <sn...@gmail.com>
> *Reply-To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
> *Date: *Monday, July 24, 2017 at 12:53 PM
> *To: *"dev@airavata.apache.org" <de...@airavata.apache.org>, "Christie,
> Marcus Aaron" <ma...@iu.edu>
> *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*
>
>
>
>
>
Re: Exposing Sharing Service through PGA
Posted by "Christie, Marcus Aaron" <ma...@iu.edu>.
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 <go...@indiana.edu>> 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 <sn...@gmail.com>>
Reply-To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>
Date: Monday, July 24, 2017 at 1:23 PM
To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>
Cc: "Christie, Marcus Aaron" <ma...@iu.edu>>
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 <go...@indiana.edu>> 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 <sn...@gmail.com>>
Reply-To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>
Date: Monday, July 24, 2017 at 12:53 PM
To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>, "Christie, Marcus Aaron" <ma...@iu.edu>>
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
Re: Exposing Sharing Service through PGA
Posted by "Shenoy, Gourav Ganesh" <go...@indiana.edu>.
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 <sn...@gmail.com>
Reply-To: "dev@airavata.apache.org" <de...@airavata.apache.org>
Date: Monday, July 24, 2017 at 1:23 PM
To: "dev@airavata.apache.org" <de...@airavata.apache.org>
Cc: "Christie, Marcus Aaron" <ma...@iu.edu>
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 <go...@indiana.edu>> 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 <sn...@gmail.com>>
Reply-To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>
Date: Monday, July 24, 2017 at 12:53 PM
To: "dev@airavata.apache.org<ma...@airavata.apache.org>" <de...@airavata.apache.org>>, "Christie, Marcus Aaron" <ma...@iu.edu>>
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
Re: Exposing Sharing Service through PGA
Posted by Sneha Tilak <sn...@gmail.com>.
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 <goshenoy@indiana.edu
> 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 <sn...@gmail.com>
> *Reply-To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
> *Date: *Monday, July 24, 2017 at 12:53 PM
> *To: *"dev@airavata.apache.org" <de...@airavata.apache.org>, "Christie,
> Marcus Aaron" <ma...@iu.edu>
> *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*
>
Re: Exposing Sharing Service through PGA
Posted by "Shenoy, Gourav Ganesh" <go...@indiana.edu>.
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 <sn...@gmail.com>
Reply-To: "dev@airavata.apache.org" <de...@airavata.apache.org>
Date: Monday, July 24, 2017 at 12:53 PM
To: "dev@airavata.apache.org" <de...@airavata.apache.org>, "Christie, Marcus Aaron" <ma...@iu.edu>
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