Trunk is already using 1.5.0-beta.9. WHIRR-593 is still open waiting for jclouds 1.5.0 final.
-- Andrei Savu / axemblr.com On Wed, Aug 15, 2012 at 12:03 AM, Paul Baclace <[email protected]>wrote: > I need to get Whirr + jclouds running on HPCloud this week. It looks like > WHIRR-593 is in good shape if jclouds 1.5.0-beta.9 is used. > > What do I need to do in order to get a version of Whirr that will use > jclouds 1.5.0-beta.9? Are the WHIRR-593 patches committed? If so, what > revision in the whirr svn? > > > Paul > > > > On 20120813 22:27 , Adrian Cole (JIRA) wrote: > >> [ https://issues.apache.org/**jira/browse/WHIRR-593?page=** >> com.atlassian.jira.plugin.**system.issuetabpanels:all-**tabpanel<https://issues.apache.org/jira/browse/WHIRR-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel>] >> >> Adrian Cole updated WHIRR-593: >> ------------------------------ >> >> Attachment: WHIRR-593_beta10.patch >> >> For use with the following test repo. Please report back to >> http://code.google.com/p/**jclouds/issues/detail?id=1068<http://code.google.com/p/jclouds/issues/detail?id=1068>when >> done! >> >> <repository> >> <id>jclouds-staging</id> >> <url>https://oss.sonatype.org/**content/repositories/** >> orgjclouds-039<https://oss.sonatype.org/content/repositories/orgjclouds-039> >> </url> >> <releases> >> <enabled>true</enabled> >> </releases> >> <snapshots> >> <enabled>false</enabled> >> </snapshots> >> </repository> >> >> >> >>> Upgrade to jclouds 1.5.0 >>> ------------------------ >>> >>> Key: WHIRR-593 >>> URL: >>> https://issues.apache.org/**jira/browse/WHIRR-593<https://issues.apache.org/jira/browse/WHIRR-593> >>> Project: Whirr >>> Issue Type: Improvement >>> Reporter: Andrei Savu >>> Assignee: Adrian Cole >>> Fix For: 0.8.0 >>> >>> Attachments: WHIRR-593_beta10.patch, >>> WHIRR-593+fix-zookeeper-test.**patch, WHIRR-593-mk4.patch, >>> WHIRR-593-mk5.patch, WHIRR-593.patch, WHIRR-593-sec-groups.patch >>> >>> >>> Jclouds 1.5.0 brings a lot of improvements and a set of new providers we >>> can use. >>> Adrian added on the discussion list: >>> "Jclouds 1.5 has a concept called TemplateBuilderSpec which allows you to >>> declare a String representation of TemplateBuilder mechanics. >>> This allows you to set a property to override the default templates used >>> in >>> jclouds. >>> For ex. >>> aws-ec2.template=imageId=ami-**foo,hardwareId=m1.large,** >>> locationId=eu-west-1 >>> Importantly, these are just strings, so you can publish a series per >>> operating system family, and choose at runtime with >>> templateBuilder.from(spec) >>> Ex. You can make your own Map<String, TemplateBuilderSpec> with your >>> favorite choices, perhaps locking in templates by id so you don't have to >>> maintain the brittle java install scripts. >>> Ex. >>> templates.get("oneiric-java-**ec2"); >>> Regardless of how this is used, the important part is that the constant >>> complaints of automatic selection can now be over, as we can provide a >>> properties syntax to afford users a means to supply their preferences >>> declaratively." >>> >> -- >> 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<https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa> >> For more information on JIRA, see: http://www.atlassian.com/** >> software/jira <http://www.atlassian.com/software/jira> >> >> >> > >
