Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
Date: Wed, 31 May 2017 16:23:04 +0000 (UTC)
From: "Valentin Aitken (JIRA)" <jira@apache.org>
To: dev@brooklyn.apache.org
Message-ID: <JIRA.13076208.1496242053000.333005.1496247784372@Atlassian.JIRA>
In-Reply-To: <JIRA.13076208.1496242053000@Atlassian.JIRA>
References: <JIRA.13076208.1496242053000@Atlassian.JIRA> <JIRA.13076208.1496242053507@jira-lw-us.apache.org>
Subject: [jira] [Commented] (BROOKLYN-512) osVersionRegex not choosing
 latest version for centos on AWS-EC2, AzureARM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 31 May 2017 16:23:13 -0000


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

Valentin Aitken commented on BROOKLYN-512:
------------------------------------------

In that regard, deploying
{noformat}
name: aws centos 7.3
location:
  'jclouds:aws-ec2:eu-central-1':
    osFamily: centos
    osVersionRegex: 7\.3.*
services:
  - type: org.apache.brooklyn.entity.software.base.EmptySoftwareProcess
{noformat}

does not find a location. Deploying that blueprint shows "cannot find image error":
{noformat}
Predicates.and(nullEqualToIsParentOrIsGrandparentOfCurrentLocation(),Predicates.and(osFamily(centos),osVersion(7\.3.*)))): Unable to match required VM template constraints PortableTemplateBuilder[ports=[22], os=centos, locationId=eu-central-1, osVersionRegex=7\.3.*, 
{noformat}

> osVersionRegex not choosing latest version for centos on AWS-EC2, AzureARM
> --------------------------------------------------------------------------
>
>                 Key: BROOKLYN-512
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-512
>             Project: Brooklyn
>          Issue Type: Improvement
>            Reporter: Valentin Aitken
>
> Scenario 1:
> Deploy a sample app in Azure ARM using the following blueprint:
> {noformat}
> name: app on AzureARM osVersionRegex
> location:
>   'jclouds:azurecompute-arm':
>     region: northeurope
>     jclouds.azurecompute.arm.publishers: OpenLogic
>     osVersionRegex: 7
>     identity: xxxxxxxxxxxidentity
>     credential: xxxxxcreds
>     endpoint: "https://management.azure.com/subscriptions/sub-idxxxx
>     oauth.endpoint: "https://login.microsoftonline.com/oathxxxxxxxx"
> services:
>   - type: org.apache.brooklyn.entity.software.base.EmptySoftwareProcess
> {noformat}
> This chooses {{CentOS Linux release 7.1.1503}} and I expect to choose latest available for OpenLogic which is CentOS 7.3.x
> as a workaround I can use {{imageId: northeurope/OpenLogic/CentOS/7.3}}
> -----
> Scenario 2, AWS EC2:
> {noformat}
> name: aws centos 7
> location:
>   'jclouds:aws-ec2:eu-central-1':
>     osFamily: centos
>     osVersionRegex: 7\..*
>     loginUser: root
> services:
>   - type: org.apache.brooklyn.entity.software.base.EmptySoftwareProcess
> {noformat}
> Chooses {{CentOS Linux release 7.0.1406}}.
> Again as a workaround I should specify imageId.
> ----
> It is most likely to be a jclouds issue. Not sure whether the two have same cause though.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)