Hi All,
Sorry for less updates on Custos project progress for past couple of weeks, I was busy with Airavata Django portal testing due to PEARC 2019 conference. Now I am dedicating all my time to Custos project and you will be seeing more frequent updates on this mailing list. Here are the updates and questions that I have. Current Status: I am migrating the profile service into Custos. I have completed code changes for migration of the following parts: 1. user-profile-service: This manages the new user creation, user details updation, deleting user profile etc. 2. tenant-profile-service: This manages the creation, updation, deletion of the gateway. 3. iam-admin-service: This service interacts with keycloak service to update or query, user and gateway details. I am currently testing the changes, but you can have a look at the code here<https://github.com/apache/airavata-custos/pull/2> (https://github.com/apache/airavata-custos/pull/2/files). ? To Discuss: ??I have 2 things in mind that I wanted to discuss: 1. ??Group Service Migration:??? This service is tightly coupled with the airavata sharing registry service. Since sharing service will also be migrated to custos, I could defer the migration of group service until the migration of sharing service while keeping the dependency between these 2, or, I could decouple this dependency and make group service an independent service. We might need independent group service if we are allowing other Gateways to use only Custos authentication and profile service while implementing their own sharing service. What are our plans regarding this? 2. Integration of Custos with Airavata: There are couple of discussions that I wanted to bring up: * ? Authentication between Gateways and Custos : As of now, I have not implemented any authentication/authorization between these 2 services. Do we need this or would we rely on network and firewall based limited access to custos servers? If we do need it, I would appreciate suggestions on type of authentication to use. * ??Airavata proxying Custos services: Since the portals using Airavata should not be impacted with the migration of some of Airavata services, the Airavata APIs will essentially be proxying Custos services in some cases. For example the Airavata APIs for user creation,deletion, updation will remain the same but most of the business logic and database will be in Custos. Airavata will only keep user/tenant information specific to itself. So essentially, Airavata is just proxying Custos. This is true for most of the APIs which rely on Custos. To illustrate, this will be the architecture with the current Django portal : Portal web page ---> Django server ---> Airavata server ---> Custos server Where Django server and Airavata server are just acting as proxies for some of the APIs. Let me know if this is not as expected. Thanks & Regards, Aarushi Bisht
