You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by kuytje <gi...@git.apache.org> on 2016/03/22 15:29:15 UTC
[GitHub] airavata pull request: Commit all changes for the folowing files
GitHub user kuytje opened a pull request:
https://github.com/apache/airavata/pull/29
Commit all changes for the folowing files
1. Configure your SGE resource type in gfac yaml config file
(airavata/modules/configuration/server/src/main/resources/gfac-config.yaml.config).
As you can see you need to provide an output parser and email parser for
your SGE, Unless you can't use existing implementations you need to come
up with your own implementations of these interfaces.
2. Don't modify thrift generated file, instead add your new
ResourceJobManagerType to
airavata/thrift-interface-descriptions/data-models/resource-catalog-models/compute_resource_model.thrift
file and generate thrift classes.
3. Come up with SGE JobConfiguration class, and modify
org.apache.airavata.gfac.impl.Factory#getJobManagerConfiguration method
to provide it. You should have xslt template for your SGE script file.
4. add your XSLT file in
airavata/distribution/src/main/assembly/bin-assembly.xml. Otherwise it
will not be added to bin directory.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kuytje/airavata add_sge
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/airavata/pull/29.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 #29
----
commit 3ee4cc1a4f60c964169268e13562f01712702557
Author: eric <er...@wur.nl>
Date: 2016-03-22T12:24:43Z
Commit all changes for the folowing files
1. Configure your SGE resource type in gfac yaml config file
(airavata/modules/configuration/server/src/main/resources/gfac-config.yaml.config).
As you can see you need to provide an output parser and email parser for
your SGE, Unless you can't use existing implementations you need to come
up with your own implementations of these interfaces.
2. Don't modify thrift generated file, instead add your new
ResourceJobManagerType to
airavata/thrift-interface-descriptions/data-models/resource-catalog-models/compute_resource_model.thrift
file and generate thrift classes.
3. Come up with SGE JobConfiguration class, and modify
org.apache.airavata.gfac.impl.Factory#getJobManagerConfiguration method
to provide it. You should have xslt template for your SGE script file.
4. add your XSLT file in
airavata/distribution/src/main/assembly/bin-assembly.xml. Otherwise it
will not be added to bin directory.
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] airavata issue #29: Adding SGE
Posted by smarru <gi...@git.apache.org>.
Github user smarru commented on the issue:
https://github.com/apache/airavata/pull/29
Eric, apologies for not following on this PR for long. Can we revisit this? Are you using this SGE interface?
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] airavata pull request: Commit all changes for the folowing files
Posted by kuytje <gi...@git.apache.org>.
Github user kuytje commented on the pull request:
https://github.com/apache/airavata/pull/29#issuecomment-199841878
Added sge,
I ignored the maximum number of nodes value because I couldn't find the option in SGE and used serial as parallel environment as used on ROCKS clusters. Other users should create a parallel environment named serial using <qconf -ap serial>.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---