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] [Commented] (JCLOUDS-1379) incompatible instance types selected in new AWS regions
Date Mon, 05 Feb 2018 13:34:00 GMT

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

Ignasi Barrera commented on JCLOUDS-1379:

I'd say there are two ways to fix this:
 * Let the hardware supplier return every instance type with the {{location}} field properly
populated. This means that we need to return one copy of the type for each location where
it is supported, and potentially change the identifiers to be unique by region. Something
like {{us-east-1/t2.micro}}.
 * Implement the logic in [supportsImage|http://jclouds.apache.org/reference/javadoc/2.0.x/org/jclouds/compute/domain/Hardware.html#supportsImage()] predicate.
This way we avoid duplicating the hardware profiles and changing the IDs (backward incompatible)
and can make instance types available or not depending on the configured image and its location.

AFAIK there is no API call in AWS that returns the list of instance types available in a region,
so that code that maps all existing ones to a location would need to be hard-coded and maintained
the same way we maintain the list of existing types.

> incompatible instance types selected in new AWS regions
> -------------------------------------------------------
>                 Key: JCLOUDS-1379
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1379
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 2.0.3
>            Reporter: Alex Heneveld
>            Priority: Major
>              Labels: aws-ec2
> Using AWS EC2, if I specify minRam 4096M and minCores 4, I get a VM fine in some regions
(eu-west-1) but errors in others (eu-west-2)
> AWSResponseException: request POST https://ec2.eu-west-2.amazonaws.com/ HTTP/1.1 failed
with code 400, error: AWSError\{requestId='...', requestToken='null', code='Unsupported',
message='The requested configuration is currently not supported. Please check the documentation
for supported configurations.' ...}
> I assume this is because some instance types are not available in some regions.
> Can we do further filtering on instance type selection so that minRam/minCores work as

This message was sent by Atlassian JIRA

View raw message