whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Cole (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-504) Upgrade to jclouds 1.4.0
Date Sun, 19 Feb 2012 01:25:59 GMT

    [ https://issues.apache.org/jira/browse/WHIRR-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211178#comment-13211178

Adrian Cole commented on WHIRR-504:

Updates in latest patch:

  * employs new jclouds features such as submitScriptOnNode and its EventBus mechanisms for
script notification.

  * refactored DryRunModule and showed an example test you can use to sanity check services
offline, based on David's work: CassandraServiceDryRunTest

  * shown an example of how to use jclouds InstallJDK function in ZooKeeperClusterActionHandler.


  * zookeeper passed on cloudservers-us, but when the zookeepers start on aws-ec2, the tests
that actually connect to the ports fail.

  * I tried cassandra, but there seems to be an issue, even on rackspace where the default
install_jdk script fails with "Package sun-java6-jdk has no installation candidate"  I'd suggest
to move to InstallJDK statement like I did in zookeeper.

  * The itests seem to rely on guava 10.0.1, which is a problem, maybe Ioannis can have a
look and see if this can be updated.

I know I've reorganized imports and I understand that this isn't nice, but I don't have any
more time, so I figured I'd kick the patch out for folks to help progress. 
> Upgrade to jclouds 1.4.0
> ------------------------
>                 Key: WHIRR-504
>                 URL: https://issues.apache.org/jira/browse/WHIRR-504
>             Project: Whirr
>          Issue Type: Improvement
>            Reporter: Andrei Savu
>            Assignee: Adrian Cole
>             Fix For: 0.8.0
>         Attachments: WHIRR-504.patch, WHIRR-504.patch, WHIRR-504.patch
> At this time 1.4.0 RC1 is out and if no major bugs are discovered we should be able to
have a final release pretty soon. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message