[
https://issues.apache.org/jira/browse/BROOKLYN-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thach Mai updated BROOKLYN-582:
-------------------------------
Description:
When running a blueprint for AWS EC2, specifying "minRam" and "minCores"
combination will not work for some regions.
Example of a blueprint that works:
{{name: WORK}}
{{services:}}
{{- type: server}}
{{ name: WORK}}
{{location:}}
{{ jclouds:aws-ec2:}}
{{ identity: ----}}
{{ credential: ----}}
{{ }}
{{ region: eu-west-1}}
{{ }}
{{ osFamily: ubuntu}}
{{ minRam: 4096M}}
{{ minCores: 4}}
{{ }}
{{ user: sample}}
{{ password: s4mpl3}}
If we run the same blueprint, but changing the region to "eu-west-2", it
results in an error:
{\{Error invoking start at EmptySoftwareProcessImpl{id=nd40mzs7n0}: Failed to
get VM after 2 attempts. - First cause is org.jclouds.aws.AWSResponseException:
request POST [https://ec2.eu-west-2.amazonaws.com/] HTTP/1.1 failed with code
400, error: AWSError{requestId='11cc4fed-1a3a-483b-8661-7c1ff68e37ac',
requestToken='null', code='Unsupported', message='The requested configuration
is currently not supported. Please check the documentation for supported
configurations.', context='
{Response=, Errors=}'} (listed in primary trace); plus 1 more (e.g. the last is
org.jclouds.aws.AWSResponseException: request POST
[https://ec2.eu-west-2.amazonaws.com/] HTTP/1.1 failed with code 400, error:
AWSError\{requestId='ddf4f700-642c-401a-91b0-9e84f39d2208',
requestToken='null', code='Unsupported', message='The requested configuration
is currently not supported. Please check the documentation for supported
configurations.', context='{Response=, Errors=}'}): AWSResponseException:
request POST [https://ec2.eu-west-2.amazonaws.com/] HTTP/1.1 failed with code
400, error: AWSError\{requestId='11cc4fed-1a3a-483b-8661-7c1ff68e37ac',
requestToken='null', code='Unsupported', message='The requested configuration
is currently not supported. Please check the documentation for supported
configurations.', context='{Response=, Errors=}'}}}
The root cause is likely because jClouds algorithm proposes an instance type
that doesn't exist for some regions.
was:
When running a blueprint for AWS EC2, specifying "minRam" and "minCores"
combination will not work for some regions.
Example of a blueprint that works:
{{name: WORK}}
{{services:}}
{{- type: server}}
{{ name: WORK}}
{{location:}}
{{ jclouds:aws-ec2:}}
{{ identity: ----}}
{{ credential: ----}}
{{ }}
{{ region: eu-west-1}}
{{ }}
{{ osFamily: ubuntu}}
{{ minRam: 4096M}}
{{ minCores: 4}}
{{ }}
{{ user: sample}}
{{ password: s4mpl3}}
If we run the same blueprint, but changing the region to "eu-west-2", it
results in an error:
{{Error invoking start at EmptySoftwareProcessImpl\{id=nd40mzs7n0}: Failed to
get VM after 2 attempts. - First cause is org.jclouds.aws.AWSResponseException:
request POST https://ec2.eu-west-2.amazonaws.com/ HTTP/1.1 failed with code
400, error: AWSError\{requestId='11cc4fed-1a3a-483b-8661-7c1ff68e37ac',
requestToken='null', code='Unsupported', message='The requested configuration
is currently not supported. Please check the documentation for supported
configurations.', context='{Response=, Errors=}'} (listed in primary trace);
plus 1 more (e.g. the last is org.jclouds.aws.AWSResponseException: request
POST https://ec2.eu-west-2.amazonaws.com/ HTTP/1.1 failed with code 400, error:
AWSError\{requestId='ddf4f700-642c-401a-91b0-9e84f39d2208',
requestToken='null', code='Unsupported', message='The requested configuration
is currently not supported. Please check the documentation for supported
configurations.', context='{Response=, Errors=}'}): AWSResponseException:
request POST https://ec2.eu-west-2.amazonaws.com/ HTTP/1.1 failed with code
400, error: AWSError\{requestId='11cc4fed-1a3a-483b-8661-7c1ff68e37ac',
requestToken='null', code='Unsupported', message='The requested configuration
is currently not supported. Please check the documentation for supported
configurations.', context='{Response=, Errors=}'}}}
The root cause is like because jClouds algorithm proposes an instance type from
minCores and minRam that doesn't exist for some regions.
> AWS EC2 blueprint fails due to invalid instance type proposed
> -------------------------------------------------------------
>
> Key: BROOKLYN-582
> URL: https://issues.apache.org/jira/browse/BROOKLYN-582
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Thach Mai
> Priority: Major
>
> When running a blueprint for AWS EC2, specifying "minRam" and "minCores"
> combination will not work for some regions.
> Example of a blueprint that works:
> {{name: WORK}}
> {{services:}}
> {{- type: server}}
> {{ name: WORK}}
> {{location:}}
> {{ jclouds:aws-ec2:}}
> {{ identity: ----}}
> {{ credential: ----}}
> {{ }}
> {{ region: eu-west-1}}
> {{ }}
> {{ osFamily: ubuntu}}
> {{ minRam: 4096M}}
> {{ minCores: 4}}
> {{ }}
> {{ user: sample}}
> {{ password: s4mpl3}}
>
> If we run the same blueprint, but changing the region to "eu-west-2", it
> results in an error:
> {\{Error invoking start at EmptySoftwareProcessImpl{id=nd40mzs7n0}: Failed to
> get VM after 2 attempts. - First cause is
> org.jclouds.aws.AWSResponseException: request POST
> [https://ec2.eu-west-2.amazonaws.com/] HTTP/1.1 failed with code 400, error:
> AWSError{requestId='11cc4fed-1a3a-483b-8661-7c1ff68e37ac',
> requestToken='null', code='Unsupported', message='The requested configuration
> is currently not supported. Please check the documentation for supported
> configurations.', context='
> {Response=, Errors=}'} (listed in primary trace); plus 1 more (e.g. the last
> is org.jclouds.aws.AWSResponseException: request POST
> [https://ec2.eu-west-2.amazonaws.com/] HTTP/1.1 failed with code 400, error:
> AWSError\{requestId='ddf4f700-642c-401a-91b0-9e84f39d2208',
> requestToken='null', code='Unsupported', message='The requested configuration
> is currently not supported. Please check the documentation for supported
> configurations.', context='{Response=, Errors=}'}): AWSResponseException:
> request POST [https://ec2.eu-west-2.amazonaws.com/] HTTP/1.1 failed with code
> 400, error: AWSError\{requestId='11cc4fed-1a3a-483b-8661-7c1ff68e37ac',
> requestToken='null', code='Unsupported', message='The requested configuration
> is currently not supported. Please check the documentation for supported
> configurations.', context='{Response=, Errors=}'}}}
>
> The root cause is likely because jClouds algorithm proposes an instance type
> that doesn't exist for some regions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
