[
https://issues.apache.org/jira/browse/AIRAVATA-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Marru reassigned AIRAVATA-383:
-------------------------------------
Assignee: Suresh Marru
> Unify Airavata Configuration Properties
> ----------------------------------------
>
> Key: AIRAVATA-383
> URL: https://issues.apache.org/jira/browse/AIRAVATA-383
> Project: Airavata
> Issue Type: Improvement
> Components: GFac, Workflow Interpreter, XBaya
> Affects Versions: 0.4-INCUBATING
> Environment: All
> Reporter: Suresh Marru
> Assignee: Suresh Marru
>
> Currently there are too many configuration properties for individual
> services. As the deployment is converging into single service, I propose to
> bundle up configurations into following two categories
> airavata-server-config.properties and airavata-client-config.properties. The
> server configuration should contain all information related to executions,
> security and deployment specific information. The client configuration should
> have default configurations to connect to airavata server and other related
> configs. XBaya when running in monitoring and composition mode will only need
> client cofigs. But Xbaya is used as a orchestrator, then the server config
> locations should also be specified.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
