[ 
https://issues.apache.org/jira/browse/WHIRR-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ioannis Canellos updated WHIRR-548:
-----------------------------------

    Attachment: whirr-548-update-3.patch

I am attaching a rewrite of the initial patch that does the following:

i) Introduces DynamicComputeCache, which is a ComputeCache that can be 
externally added compute services.
ii) In OSGi the DynamicComputeCache is used by default.
iii) Fixed minor issues in the activator of whirr-core.
iv) Fixed an IllegalStateException when uninstalling whirr-hbase from OSGi.
v) Brought back karaf commands blueprint descriptor.
vi) Improved loading of default-xxxx.properties files to be more OSGi friendly.
vii) Added TCCL trick to make velocity play nicely inside OSGI (hbase + hadoop).

                
> Allow whirr to reuse existing compute services
> ----------------------------------------------
>
>                 Key: WHIRR-548
>                 URL: https://issues.apache.org/jira/browse/WHIRR-548
>             Project: Whirr
>          Issue Type: Improvement
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>             Fix For: 0.8.0
>
>         Attachments: WHIRR-548.patch, WHIRR-548.patch, 
> whirr-548-update-3.patch
>
>
> When using whirr as a library or inside a managed environment it's possible 
> that the compute service is managed separately from whirr.
> For these cases it would be useful to allow whirr to reuse an existing 
> compute service.
> I am thinking that we could have the a compute service property as part of 
> ClusterSpec. In these cases whirr could reuse the compute service if 
> available.

--
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

Reply via email to