GitHub user anujbhan reopened a pull request:
https://github.com/apache/airavata/pull/50
Feature request : User compute resource preference
**Note: This pull request is not ready for merging**
This feature adds the capability for user to define a user specific compute
preference (Ex: An IU Big Red II account) for job scheduling.
1. Created new Data model for User resource profile (Similar to
GatewayResourceProfile but omitting unnecessary fields).
2. Changes to Airavata Api thrift model, defined end points to consume the
created Data model
3. Changes to registry module to add new DB tables and handlers
- Some changes need to be discussed with the team, like handling
the user-profile data model from registry
- Primary keys in User_Resource_Profile table and their respective
handlers
- Some changes are pending, like validating the USER_ID field in
User_Resource_Profile, since this change involves creating user table in
registry, it needs to be discussed with the team.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/anujbhan/airavata userComputeResource
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/airavata/pull/50.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #50
----
commit 81c6ea841e265dc8f7f159e4bbe0d1457db2b213
Author: Anuj Bhandar <[email protected]>
Date: 2016-10-03T00:57:28Z
Feature request: User Compute Preference
commit 8469effce22ffe3a54255d3920ee33b9d9035c06
Author: Anuj Bhandar <[email protected]>
Date: 2016-10-07T15:48:58Z
correcting the registry code, testing not yet complete
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
