[jira] [Updated] (JCLOUDS-1430) Aliyun ECS support

2018-07-02 Thread Andrea Turli (JIRA)


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

Andrea Turli updated JCLOUDS-1430:
--
Issue Type: Wish  (was: Bug)

> Aliyun ECS support
> --
>
> Key: JCLOUDS-1430
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1430
> Project: jclouds
>  Issue Type: Wish
>  Components: jclouds-labs
>Reporter: Andrea Turli
>Assignee: Andrea Turli
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (JCLOUDS-1430) Aliyun ECS support

2018-07-02 Thread Andrea Turli (JIRA)
Andrea Turli created JCLOUDS-1430:
-

 Summary: Aliyun ECS support
 Key: JCLOUDS-1430
 URL: https://issues.apache.org/jira/browse/JCLOUDS-1430
 Project: jclouds
  Issue Type: Bug
  Components: jclouds-labs
Reporter: Andrea Turli
Assignee: Andrea Turli






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [jclouds/jclouds] Added Virtual Network Gateway API (#1221)

2018-07-02 Thread Ignasi Barrera
Live test output:

```
---
 T E S T S
---
Running org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest
Configuring TestNG with: TestNG652Configurator
Starting test 
createVirtualNetworkGateway(org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest)
[pool-1-thread-1] Test 
createVirtualNetworkGateway(org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest)
 succeeded: 726ms
Test suite progress: tests succeeded: 1, failed: 0, skipped: 0.
Starting test 
getVirtualNetworkGateway(org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest)
[pool-1-thread-2] Test 
getVirtualNetworkGateway(org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest)
 succeeded: 103ms
Test suite progress: tests succeeded: 2, failed: 0, skipped: 0.
Starting test 
listVirtualNetworkGateways(org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest)
[pool-1-thread-2] Test 
listVirtualNetworkGateways(org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest)
 succeeded: 122ms
Test suite progress: tests succeeded: 3, failed: 0, skipped: 0.
Starting test 
updateVirtualNetworkGateway(org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest)
[pool-1-thread-2] Test 
updateVirtualNetworkGateway(org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest)
 succeeded: 1114706ms
Test suite progress: tests succeeded: 4, failed: 0, skipped: 0.
Starting test 
deleteVirtualNetworkGateway(org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest)
[pool-1-thread-3] Test 
deleteVirtualNetworkGateway(org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest)
 succeeded: 1838313ms
Test suite progress: tests succeeded: 5, failed: 0, skipped: 0.
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3,069.522 sec - 
in org.jclouds.azurecompute.arm.features.VirtualNetworkGatewayApiLiveTest

Results :

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1221#issuecomment-401798446

Re: [jclouds/jclouds] Added Virtual Network Gateway API (#1221)

2018-07-02 Thread Ignasi Barrera
@nacx pushed 1 commit.

9388c50  Fix checkstyle violations


-- 
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/jclouds/jclouds/pull/1221/files/ca5cdb6dffac20b210d3c7c2caf83fee0279bcca..9388c501085fbbf93ae8abc7ea0b5d80c179a914


[jclouds/jclouds] Added Virtual Network Gateway API (#1221)

2018-07-02 Thread Ignasi Barrera

You can view, comment on, or merge this pull request online at:

  https://github.com/jclouds/jclouds/pull/1221

-- Commit Summary --

  * Added Virtual Network Gateway API

-- File Changes --

M 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/AzureComputeApi.java
 (11)
M 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/AzureComputeProviderMetadata.java
 (2)
M 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/config/AzurePredicatesModule.java
 (1146)
M 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/strategy/CreateResourcesThenCreateNodes.java
 (20)
M 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/config/AzureComputeProperties.java
 (2)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/AddressSpace.java
 (39)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/IpAllocationMethod.java
 (28)
M 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/Subnet.java
 (10)
M 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/VirtualNetwork.java
 (21)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/BGPSettings.java
 (37)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/DHGroup.java
 (28)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/IPSecEncryption.java
 (28)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/IPSecIntegrity.java
 (28)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/IPSecPolicy.java
 (77)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/IkeEncryption.java
 (28)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/IkeIntegrity.java
 (28)
R 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/LocalNetworkGateway.java
 (11)
R 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/LocalNetworkGatewayProperties.java
 (47)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/PFSGroup.java
 (28)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/SKU.java
 (55)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/VPNClientConfiguration.java
 (89)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/VPNClientRevokedCertificate.java
 (57)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/VPNClientRootCertificate.java
 (57)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/VPNType.java
 (27)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/VirtualNetworkGateway.java
 (72)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/VirtualNetworkGatewayProperties.java
 (144)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/domain/vpn/VirtualNetworkGatewayType.java
 (28)
M 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/features/LocalNetworkGatewayApi.java
 (4)
A 
providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/features/VirtualNetworkGatewayApi.java
 (80)
M 
providers/azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/LocalNetworkGatewayApiLiveTest.java
 (8)
M 
providers/azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/LocalNetworkGatewayApiMockTest.java
 (8)
M 
providers/azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/NetworkInterfaceCardApiLiveTest.java
 (1)
M 
providers/azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/VirtualNetworkApiLiveTest.java
 (3)
M 
providers/azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/VirtualNetworkApiMockTest.java
 (22)
A 
providers/azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/VirtualNetworkGatewayApiLiveTest.java
 (132)
A 
providers/azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/VirtualNetworkGatewayApiMockTest.java
 (161)
M 
providers/azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/internal/BaseAzureComputeApiLiveTest.java
 (47)
A 
providers/azurecompute-arm/src/test/resources/virtualnetworkgatewaycreate.json 
(45)
A 
providers/azurecompute-arm/src/test/resources/virtualnetworkgatewayget.json (37)
A 
providers/azurecompute-arm/src/test/resources/virtualnetworkgatewaylist.json 
(49)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/1221.patch
https://github.com/jclouds/jclouds/pull/1221.diff

-- 
You are receiving t

[jira] [Commented] (JCLOUDS-1379) incompatible instance types selected in new AWS regions

2018-07-02 Thread Andrea Turli (JIRA)


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

Andrea Turli commented on JCLOUDS-1379:
---

those AWS Pricing API are not very promising,

[https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_pricing_GetAttributeValues.html]

look fast but incomplete, no information about the region, while

[https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_pricing_GetProducts.html]

look chatty and hard to filter.

We are not alone with this problem 
[https://forums.aws.amazon.com/thread.jspa?threadID=87859] but not sure we 
should expect progresses with this issue any time soon

> 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 expected?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JCLOUDS-1379) incompatible instance types selected in new AWS regions

2018-07-02 Thread Ignasi Barrera (JIRA)


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

Ignasi Barrera commented on JCLOUDS-1379:
-

I also think it is worth trying, but we need to have a couple things in mind:
 * Verify that the resulting list is accurate and complete for all regions.
 * The resulting implementation must be backwards-compatible and we should try 
not to break any existing jclouds code.

> 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 expected?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (JCLOUDS-1379) incompatible instance types selected in new AWS regions

2018-07-02 Thread Andrea Turli (JIRA)


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

Andrea Turli edited comment on JCLOUDS-1379 at 7/2/18 8:38 AM:
---

I've recently stumbled upon AWS Pricing API which may be useful to discover the 
instanceType and to get rid of the hard-coded instanceType support jclouds 
offers so far. 

Using those API looks reasonably simple to getProducts filtering by AWS 
service, `location`, and additional things like `operatingSystem` et al.

https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/reading-an-offer.html#json

I think it is worth trying to add it, maybe implemented similarly to aws sts? 
wdyt?


was (Author: andreaturli):
I've recently stumbled upon AWS Pricing API which may be useful to discover the 
instanceType and to get rid of the hard-coded instanceType support jclouds 
offers so far. 

 

I think it is worth trying to add it, maybe implemented similarly to aws sts? 
wdyt?

> 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 expected?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JCLOUDS-1379) incompatible instance types selected in new AWS regions

2018-07-02 Thread Andrea Turli (JIRA)


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

Andrea Turli commented on JCLOUDS-1379:
---

I've recently stumbled upon AWS Pricing API which may be useful to discover the 
instanceType and to get rid of the hard-coded instanceType support jclouds 
offers so far. 

 

I think it is worth trying to add it, maybe implemented similarly to aws sts? 
wdyt?

> 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 expected?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)