[KALUMET-4] Use global kscript (aka update plan)

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 0.7-incubating
• Component/s: common-model, console
• Assignee: Jean-Baptiste Onofré
• Reporter: Jean-Baptiste Onofré
• Created: 13/Dec/11 20:51
• Updated: 04/Dec/12 17:52

Description

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.