meeting: bundle deployment to non-platforms

Ian Springer ian.springer at redhat.com
Fri May 27 15:46:18 UTC 2011


On 05/27/2011 11:15 AM, John Mazzitelli wrote:
>> * Originally bundles were designed to lay down complete servers (app
>> server with apps already in place, etc).   The latest proposal moves
>> toward smaller, one-off  deployments.  We may need to work out the
>> semantics around when one bundle's deployment dir is a subdir of another
>> bundle's deployment dir.  For example, bundle-1 is an app-server and
>> bundle-2 is a web-app.  And then bundle-1 gets reverted...
> yet another good question - we need to think about this. deploying a
> bundle inside a bundle will be problematic.


I think the solution here would be for the user to make sure the outer 
bundle includes the deploy directory in the list of directories to ignore.

We could help alleviate this by checking if the selected destination dir 
is a subdir of any other deployed bundle's destination dir before 
deploying the bundle. The warning could look something like this:

"Warning: The selected destination directory 
'/opt/jboss-eap-5.1.1.GA/jboss-as/default/server/deploy' is a 
subdirectory of the deployed bundle 'JBoss EAP' v2.0. Future updates of 
the 'JBoss EAP' bundle could blow away the 'MyEnterpriseApp.ear' bundle 
unless the 'JBoss EAP' bundle is configured to ignore the 
'/opt/jboss-eap-5.1.1.GA/jboss-as/default/server/deploy' directory. Are 
you sure you want to proceed?"

>> * Question - where is the deployment meta-data kept?  It can't be stored
>> under the deploy directory, right?
> and yet another good question. We do support the ability to deploy
> bundles in the deploy/ directory (if you enable that new feature where
> the recipe tells us to not fully manage the root dest dir). HOWEVER, you
> can only deploy ONE bundle to it. You can't deploy more than one because
> the metadata will overlap/overwrite each other. So this is something
> else to think about.


In the case of deploying an exploded ear or war, the bundle metadata 
could potentially be stored in the ear or war directory. However, this 
wouldn't work out if the ear or was deployed as a file, or for a bundle 
that included multiple deployments (e.g. an ear, a sar, and a ds.xml 
file), so I think we're going to have to add support for multiple 
bundles deployed to the same destination directory.



More information about the rhq-devel mailing list