[jira] [Commented] (JCLOUDS-331) Allow Image preference logic to be supplied to TemplateBuilder

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCLOUDS-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786314#comment-13786314 ] 

ASF subversion and git services commented on JCLOUDS-331:
---------------------------------------------------------

Commit 8207c53cf23d04ace95d84bd50eb875dc0ab7438 in branch refs/heads/master from [~alex.heneveld]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;h=8207c53 ]

JCLOUDS-331 - support specifying an imageChooser function in TemplateBuilder


> Allow Image preference logic to be supplied to TemplateBuilder
> --------------------------------------------------------------
>
>                 Key: JCLOUDS-331
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-331
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-core
>            Reporter: Alex Heneveld
>            Assignee: Andrew Phillips
>            Priority: Minor
>             Fix For: 1.7.0
>
>         Attachments: JCLOUDS-331.patch
>
>
> I'd like to tie in to jclouds's TemplateBuilder so that I can use its filtering/matching capabilities but then use custom logic to determine which of the matching images is "best" (for my custom value of best, i.e. preferred). 
> 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 wants to say "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 TemplateBuilderImpl 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
(v6.1#6144)