Hi Dev, A week or so ago, Suresh, Dimuthu and I met to discuss what to do with GatewayResourceProfile [0] now that we have the new GroupResourceProfile (on the develop branch). We decided to basically deprecate GatewayResourceProfile and move anything in it that is still needed to a new “TenantProfile”. The reason for the name Tenant is to keep the terminology more general than “Gateway”.
Looking at the code, we already started down this path with the Profile Service. It has a TenantProfileService and there is actually a Tenant model [1], but actually the TenantProfileService uses the workspace’s Gateway model. The main fields on the GatewayResourceProfile that aren’t part of the GroupResourceProfile are the following: * default credentialStoreToken - I’m proposing adding a default credentialStoreToken field to GroupResourceProfile so we can fully migrate this field as well * identityServerTenant and identityServerPwdCredToken - this is already part of the Gateway/Tenant model that TenantProfileService is using so these fields already have a home Here’s a list of the proposed changes: Profile Service changes • Create TenantProfile model (see existing tenant_profile_model.thrift which is currently unused) • Rename GatewayEntity to TenantProfileEntity • Rename gateway->tenant in profile-tenant-cpi.thrift Experiment Catalog changes • Change GATEWAY table to just have GATEWAY_ID, only needed for referential integrity • Change the Gateway model to just have gatewayId App Catalog changes • Same as Experiment Catalog, just need a Gateway/Tenant model with the ID for referential integrity services-security changes • Get password credential for identity server from TenantProfileService GroupResourceProfile changes • Add a default credential store token to GroupResourceProfile [2] • Remove following from GroupComputeResourcePreference • overrideByAiravata • preferredJobSubmissionProtocol • preferredDataMovementProtocol • preferredBatchQueue • usageReportingGatewayId? • sshAccountProvisioner fields (move this somewhere else) GFac/Helix changes • Remove preferredJobSubmission/DataMovement protocols, preferred batch queue PGA Changes • Update names of fields and methods gateway->tenant. Functionality should be the same, just a name change. Gateway request process will need testing Related changes * Move sshAccountProvisioner fields to its own tables Questions • Where should usageReportingGatewayId go? Should this be set at the gateway level? Should this be overrideable by GroupResourceProfiles? Thanks, Marcus [0] https://issues.apache.org/jira/browse/AIRAVATA-2806 [1] https://github.com/apache/airavata/blob/3451a63dd21c96978226bc30754e94196a4519c3/thrift-interface-descriptions/data-models/user-tenant-group-models/tenant_profile_model.thrift#L52-L52 [2] https://issues.apache.org/jira/browse/AIRAVATA-2865
