[
https://issues.apache.org/jira/browse/WHIRR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085471#comment-13085471
]
Adrian Cole commented on WHIRR-361:
-----------------------------------
testing zookeeper via mvn -Pintegration clean install
-DargLine="-Dwhirr.test.provider=cloudservers-us ... works fine
testing with -Dwhirr.test.provider=aws-ec2 and patch for WHIRR-341 which uses
ami-63be790a has the following behavior:
- Both nodes start and install zookeeper. However, it appears only one node
seems to have scripts run on ConfigureClusterAction.doAction, so only one
starts zookeeper in this case. This is visible in
target/test-data/jclouds-compute.log and whirr.log
This is completely repeatable, but I haven't isolated why this is occurring
> refactor jclouds dependencies
> -----------------------------
>
> Key: WHIRR-361
> URL: https://issues.apache.org/jira/browse/WHIRR-361
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.6.0
> Reporter: Adrian Cole
> Assignee: Adrian Cole
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: WHIRR-361-fixguava.patch, WHIRR-361.patch,
> org.apache.whirr.service.hbase.integration.HBase089ServiceTest.txt
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> There are a few problems in our maven configuration, and a couple places
> where we aren't using the best jclouds configuration.
> * in our pom files, we needlessly declare transitive dependencies modules.
> this is unnecessary maintenance, as jclouds version/dependency configuration
> is scoped to whirr core
> * we've switched to SLF4J, yet haven't configured jclouds to use it
> * especially considering we are uploading large blobs, we should be using
> the jclouds EnterpriseConfigurationModule which handles file slicing much
> more effectively.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
