[ 
https://issues.apache.org/jira/browse/AIRAVATA-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364711#comment-16364711
 ] 

ASF GitHub Bot commented on AIRAVATA-2659:
------------------------------------------

machristie commented on issue #169: [AIRAVATA-2659] GroupResourceProfile for 
modeling resource sharing with specific groups of users
URL: https://github.com/apache/airavata/pull/169#issuecomment-365733445
 
 
   @eldhomathulla here's Sachin's pull request. See especially his changes to 
Thrift files.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> GroupResourceProfile for modeling resource sharing with specific groups of 
> users
> --------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2659
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2659
>             Project: Airavata
>          Issue Type: Improvement
>            Reporter: Sachin Kariyattin
>            Assignee: Sachin Kariyattin
>            Priority: Major
>
> The first step in implementing the Group Resource Profile backend is to 
> create the required models and add methods to store the details in the 
> registry. The GroupResourceProfile implementation will be added to the 
> app_catalog and the following changes have been made as part of it.
>  * Created the following thrift models for the GroupResourceProfile
> {{       struct GroupResourceProfile}}
>  {{       struct GroupComputeResourcePreference}}
>  {{       struct ComputeResourcePolicy}}
>  {{       struct BatchQueueResourcePolicy}}
>  * Created new tables in the app_catalog schema.
>  * Implemented GroupResourceProfileRepository.
>  * Added GroupResourceProfileRepositoryTest.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to