GitHub user gouravshenoy opened a pull request:
https://github.com/apache/airavata/pull/70
Move aurora-client properties to airavata-server.properties, and detect
leading aurora scheduler
This PR contains the following changes related to the aurora-client cloud
module:
1. Added all aurora client related properties from
"aurora-scheduler.properties" to the "airavata-server.properties".
2. Updated the ServerSettings.java to retrieve respt. property values
3. Removed dependency to aurora-scheduler property file in
AuroraThriftClient.java, and instead reading from ServerSettings.java.
4. Removed dependency to "commons-io" from aurora-client cloud module.
5. Updated "aurora.scheduler.hosts" property to take multiple "host:port"
value pairs, and then detect leading aurora scheduler before performing RPC
call.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gouravshenoy/airavata aurora-mesos-integration
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/airavata/pull/70.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 #70
----
commit bf5d8c79645adf161d9121bb84ffcb4acd86f382
Author: Shameera Rathnayaka <[email protected]>
Date: 2016-11-02T03:30:00Z
Deletege cloud environment creation task to common env setup task
commit c6e96ca2d3d4e0c329fd83f745589eff5c7ceac9
Author: Gourav Shenoy <[email protected]>
Date: 2016-11-02T18:57:19Z
Merge pull request #3 from apache/auroraMesosIntegration
Merge aurora-mesos-integration branch
commit 01f804433e0745aca8c5e9f8fd48fb3efd33b25e
Author: Gourav Shenoy <[email protected]>
Date: 2016-11-02T21:50:48Z
Move aurora-scheduler properties to airavata-server.properties, AND detect
leading aurora scheduler
----
---
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.
---
