You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Marcus Christie (JIRA)" <ji...@apache.org> on 2018/03/06 14:08:00 UTC
[jira] [Created] (AIRAVATA-2708) GroupResourceProfile: model
resource policies as children of GroupComputeResourcePreferences instead
Marcus Christie created AIRAVATA-2708:
-----------------------------------------
Summary: GroupResourceProfile: model resource policies as children of GroupComputeResourcePreferences instead
Key: AIRAVATA-2708
URL: https://issues.apache.org/jira/browse/AIRAVATA-2708
Project: Airavata
Issue Type: Bug
Reporter: Marcus Christie
Assignee: Marcus Christie
Current GroupResourceProfile model is:
{code}
struct GroupResourceProfile {
1: required string gatewayId,
2: required string groupResourceProfileId,
3: optional string groupResourceProfileName,
4: optional list<GroupComputeResourcePreference> computePreferences,
5: optional list<ComputeResourcePolicy> computeResourcePolicies,
6: optional list<BatchQueueResourcePolicy> batchQueueResourcePolicies
7: optional i64 creationTime,
8: optional i64 updatedTime
}
{code}
Instead it would be more intuitive to model ComputeResourcePolicy and BatchQueueResourcePolicy as children of GroupComputeResourcePreference. Something like
{code}
struct GroupResourceProfile {
1: required string gatewayId,
2: required string groupResourceProfileId,
3: optional string groupResourceProfileName,
4: optional list<GroupComputeResourcePreference> computePreferences,
5: optional i64 creationTime,
6: optional i64 updatedTime
}
struct GroupComputeResourcePreference {
1: required string computeResourceId,
2: required string groupResourceProfileId,
...
19: optional ComputeResourcePolicy computeResourcePolicy,
20: optional list<BatchQueueResourcePolicy> batchQueueResourcePolicies
}
{code}
Could be a little tricky since we map the Thrift data models directly to the database models, so it will take some thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)