jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignasi Barrera (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (JCLOUDS-314) Allow TemplateBuilder user to supply Image preference logic
Date Wed, 02 Oct 2013 14:44:42 GMT

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

Ignasi Barrera closed JCLOUDS-314.

    Resolution: Duplicate

> Allow TemplateBuilder user to supply Image preference logic
> -----------------------------------------------------------
>                 Key: JCLOUDS-314
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-314
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-core
>    Affects Versions: 1.6.2
>         Environment: All
>            Reporter: Alex Heneveld
>            Priority: Minor
> I'd like to tie in to jclouds's TemplateBuilder so that I can use its filtering capabilities
(matching) but then use custom logic to determine which of the matching images is "best" (for
my custom value of best, i.e. my preferences).
> The driving use case is that I want a portable way to say "any recent ubuntu or centos".
 Normally this is the default of course but it doesn't always do the right thing when other
options are specified -- broken ubuntu "alpha" images in AWS being the worst offender (asking
for 16gb RAM in us-west-1 gives back an awful ubuntu 8.04 alpha, for instance!).  It would
also handle use cases where someone says "Ubuntu 11 or 12, or CentOS 6.x, is best. failing
that, Ubuntu 10 or CentOS 5.x. (and never any alpha images!)".
> I'm thinking allowing to set an `imageSorter(Ordering)`. This fits with how
> the Impl currently works (it already uses an Ordering, you just can't change
> it; and it stays in line with the naming convention of `Sorter` as in 
> `Ordering hardwareSorter()`.)

This message was sent by Atlassian JIRA

View raw message