1 Reply Latest reply: Sep 16, 2011 9:18 AM by Emanuel Muckenhuber RSS

Deployment features

karin k Newbie

Hi all,

Is RedHat/JBoss intending to offer more sophisticated features to alleviate the deployment on app servers for JBoss AS 7.x or higher like e.g:

 

  1. Possibility to define easily deployment plans to define deployment dependencies of different app servers in a domain (and deployment actions applied on a app server)  ; I have read something about a Rollout plan (here http://community.jboss.org/wiki/FormatOfADetypedOperationRequest) but I have not understood how to create such a plan. Is it just an idea or really at the moment available (JBoss AS 7.0)?
  2. Do you plan to have persistent deployment plans in future (I've found this Jira task Persist named rollout plans for reuse by clients but it seems to be opened to community, so is it really not part of JBoss AS 7.1 or JBoss EAP 6?
  3. Scripting language to implement logic into CLI batch scripts (similar to the way weblogic is doing it with Phyton)
  4. Recording of actions taken on the admin console and dumping that actions into a script (in order to alleviate the writing of domain management scripts)?
  5. Statistic/Logs about the status of the deployment (successful action, failed actions)
  6. Apache Maven integration: For making it easy to create deployment packages from a Maven environment and deploy that automatically into a JBoss development environment

 

Can it be that such sophisticated features are only offered for domain mode and not for standalone mode? Or will it be offered (when it makes sense) for both modes (e.g persistent deployment plans).

 

 

Thanks for your help

 

Regards
Karin

 



 


  • 1. Re: Deployment features
    Emanuel Muckenhuber Master

    Karin Krause wrote:

     

    Possibility to define easily deployment plans to define deployment dependencies of different app servers in a domain (and deployment actions applied on a app server)  ; I have read something about a Rollout plan (here http://community.jboss.org/wiki/FormatOfADetypedOperationRequest) but I have not understood how to create such a plan. Is it just an idea or really at the moment available (JBoss AS 7.0)?

    We already have some builder tools which help you in creating deployments plans as part of our native management client:

    https://github.com/jbossas/jboss-as/tree/master/controller-client/src/main/java/org/jboss/as/controller/client/helpers

     

    A deployment / rollout plan defines in which way/order deployments are pushed to server-groups as part of the managed domain mode. For standalone it's more a tool to deploy multiple deployments, since it just a single target.

    Karin Krause wrote:

     

    Do you plan to have persistent deployment plans in future (I've found this Jira task Persist named rollout plans for reuse by clients but it seems to be opened to community, so is it really not part of JBoss AS 7.1 or JBoss EAP 6? 

    In the end a deployment plan is just a set of operations, so a persistent deployment plan can be just a script. I think we have some example how to do a deployment using perl for standalone.

     

    Karin Krause wrote:

     

    Scripting language to implement logic into CLI batch scripts (similar to the way weblogic is doing it with Phyton)

    You can use JSON with the http management interface we provide. So you should be able to use your favorite scripting language.

     

    Karin Krause wrote:

     

    Recording of actions taken on the admin console and dumping that actions into a script (in order to alleviate the writing of domain management scripts)?

    Hmm, i don't think we do that, but that should hopefully not be too hard  - once you are a bit more familiar with the management api you should be able to find the corresponding operations using the CLI and metadata we provide.

     

    Karin Krause wrote:

     

    Statistic/Logs about the status of the deployment (successful action, failed actions)

    The deployment status should already be part of the information we expose through the mgmt API and we are going to continue to add more runtime metrics.

     

    Karin Krause wrote:

     

    Apache Maven integration: For making it easy to create deployment packages from a Maven environment and deploy that automatically into a JBoss development environment

    Hmm, not as part of AS - you might rather look at of those 2 projects: http://www.jboss.org/arquillian and http://www.jboss.org/shrinkwrap

    Karin Krause wrote:

     

    Can it be that such sophisticated features are only offered for domain mode and not for standalone mode? Or will it be offered (when it makes sense) for both modes (e.g persistent deployment plans).

    Well the domain mode is for managing multi-server environments, where standalone is the single VM approach we used to do with previous releases. So obviously there are some more complex domain operations available which are not in standalone.