You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kalumet-dev@incubator.apache.org by "Jean-Baptiste Onofré (Created JIRA)" <ji...@apache.org> on 2011/12/13 20:51:30 UTC
[jira] [Created] (KALUMET-4) Use global kscript (aka update plan)
Use global kscript (aka update plan)
------------------------------------
Key: KALUMET-4
URL: https://issues.apache.org/jira/browse/KALUMET-4
Project: Apache Kalumet
Issue Type: New Feature
Components: common-model, console
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: 0.6-incubating
Currently, Kalumet uses the following "hardcoded" update plan:
- update the "pre J2EE" softwares
- update the J2EE application server resources (data sources, JMS connection factories, etc)
- update J2EE application (archives, configuration files, etc)
- update the "post J2EE" softwares
In the softwares, we use a fully custom "update plan", allowing the users to orchestrate location, configuration files, etc.
It makes sense to use the software approach globally.
It means that we will provide a palette of "script units" (J2EE application server, middlewares, locations, configuration files, etc) and allow the users to describe the update plan named a kscript.
--
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
[jira] [Updated] (KALUMET-4) Use global kscript (aka update plan)
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KALUMET-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KALUMET-4:
---------------------------------------
Fix Version/s: (was: 0.6-incubating)
0.7-incubating
> Use global kscript (aka update plan)
> ------------------------------------
>
> Key: KALUMET-4
> URL: https://issues.apache.org/jira/browse/KALUMET-4
> Project: Kalumet
> Issue Type: New Feature
> Components: common-model, console
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 0.7-incubating
>
>
> Currently, Kalumet uses the following "hardcoded" update plan:
> - update the "pre J2EE" softwares
> - update the J2EE application server resources (data sources, JMS connection factories, etc)
> - update J2EE application (archives, configuration files, etc)
> - update the "post J2EE" softwares
> In the softwares, we use a fully custom "update plan", allowing the users to orchestrate location, configuration files, etc.
> It makes sense to use the software approach globally.
> It means that we will provide a palette of "script units" (J2EE application server, middlewares, locations, configuration files, etc) and allow the users to describe the update plan named a kscript.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira