search

alien4cloud / alien4cloud-cloudify2-provider

Contains the PaaS provider plugin to allow deployments using Cloudify v2
http://alien4cloud.github.io/documentation/cloudify2_driver/index.html
Apache License 2.0
0 stars 3 forks source link

Handle "usmlib" folder #2

Closed grozeille closed 9 years ago

grozeille commented 9 years ago

When we have "usmlib" folder in the "scripts" folder, it should be included in the "usmlib" folder in the root of the recipe.

WARNING: if we deploy multiple service, we can have version conflicts of JAR with different versions.

In general, to avoid that, all services should be executed in a seperate ClassLoader (they could have the same parent ClassLoader to share Cloudify libs)

lucboutier commented 9 years ago

Hi Mathias,

Our goal is to use TOSCA compatible recipe and to get closer and closer to TOSCA. Using usmlib stuff in your recipe is really too specific to Cloudify 2 and won't be portable in the future (either on cloudify 3 or any other possible implementation). Based on the this we also encourage people to leverage shell scripts and/or chef/puppet recipes rather than relying too much on Cloudify 2 specific groovy.

That said if you see a real use case that would push us to try to support this we would like know about it.

Regarding the class loaders support for the driver it is already different class loaders for every groovy scripts. Basically every parallel execution in the workflow we generate uses a new class loader that has the previous one as a parent.

Luc

lucboutier commented 9 years ago

I set the issue as wont fix for now so please let me know if you see any good reasons or important requirement for us to support it.