[jira] [Commented] (LIBCLOUD-1031) Edited .rst file and changed to api endpoint name

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726847#comment-16726847
 ] 

ASF GitHub Bot commented on LIBCLOUD-1031:
--

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1270


> Edited .rst file and changed to api endpoint name
> -
>
> Key: LIBCLOUD-1031
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1031
> Project: Libcloud
>  Issue Type: Improvement
> Environment: NTTC-CIS
>Reporter: Mitchell Raful
>Priority: Minor
>




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

[jira] [Commented] (LIBCLOUD-1031) Edited .rst file and changed to api endpoint name

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725017#comment-16725017
 ] 

ASF GitHub Bot commented on LIBCLOUD-1031:
--

GitHub user snmpboy opened a pull request:

https://github.com/apache/libcloud/pull/1270

[LIBCLOUD-1031] Fix lb docs by editing nttcis.rst in docs/loadbalancer and 
in changing endpoint canada to ca

Fix loadbalancer  docs by editing nttcis.rst in docs/loadbalancer and in 
changing endpoint 'canada' to 'ca' in libcloud/common/nttcis.py

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [ x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [x] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/NTTC-CIS/libcloud fix_lb_docs

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1270.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1270


commit 515b71b34f8889f69e117c1292b2a8d24dc55e36
Author: mitch 
Date:   2018-10-23T21:59:28Z

Merge branch 'trunk' of https://git-wip-us.apache.org/repos/asf/libcloud 
into trunk
to keep all changes in sync.

commit 0c62e374af91ecb6ebd6f6fbfdaa57bdba9aa7b8
Author: mitch 
Date:   2018-12-11T14:22:49Z

Merge branch 'trunk' of https://git-wip-us.apache.org/repos/asf/libcloud 
into trunk

commit 869040e7e03bf8a35e8111060d809a56715fed78
Author: mitch 
Date:   2018-12-13T17:20:28Z

Merge branch 'trunk' of https://git-wip-us.apache.org/repos/asf/libcloud 
into trunk

commit fb0ba6733d19c55ef1aa3d6ed69f973d0ebc0caa
Author: mitch 
Date:   2018-12-19T09:35:34Z

Merge branch 'trunk' of https://git-wip-us.apache.org/repos/asf/libcloud
into trunk

commit 47f980d19a5d9aff4ec024ce2eddd48f092f086b
Author: mitch 
Date:   2018-12-19T13:28:01Z

removed dimension data from nttcis.rst in docs/loadbalancers




> Edited .rst file and changed to api endpoint name
> -
>
> Key: LIBCLOUD-1031
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1031
> Project: Libcloud
>  Issue Type: Improvement
> Environment: NTTC-CIS
>Reporter: Mitchell Raful
>Priority: Minor
>




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

[jira] [Commented] (LIBCLOUD-1030) Disaster Recovery Service (DRS) for NTTC-CIS

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724701#comment-16724701
 ] 

ASF GitHub Bot commented on LIBCLOUD-1030:
--

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1268


> Disaster Recovery Service (DRS) for NTTC-CIS
> 
>
> Key: LIBCLOUD-1030
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1030
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Compute
>Reporter: Mitchell Raful
>Priority: Major
>
> Added code in the compute/drivers/nttcis module to support NTTC-CIS disaster 
> recovery service.



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

[jira] [Commented] (LIBCLOUD-874) Does Libcloud have plans to support new versions of OpenStack?

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708414#comment-16708414
 ] 

ASF GitHub Bot commented on LIBCLOUD-874:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1242


> Does Libcloud have plans to support new versions of OpenStack?
> --
>
> Key: LIBCLOUD-874
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-874
> Project: Libcloud
>  Issue Type: Improvement
>Reporter: Jim
>Priority: Blocker
>
> In the latest version 1.3.0, Libcloud still use Nova API to provide the 
> image, network and volume functions, which are deprecated in current 
> OpenStack verison. Does Libcloud have plans to support Glance v2, Neutron 
> v2.0 and Cinder v2 API for OpenStack?



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

[jira] [Commented] (LIBCLOUD-1026) Updated documentation for UpCloud driver

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700543#comment-16700543
 ] 

ASF GitHub Bot commented on LIBCLOUD-1026:
--

GitHub user iler opened a pull request:

https://github.com/apache/libcloud/pull/1259

[LIBCLOUD-1026] Update documentation for UpCloud driver

## Update UpCloud driver documentation

### Description

- Dropped www from the URL
- Added missing datacenters
- Updated API credentials instructions
- Updated logo

[https://issues.apache.org/jira/projects/LIBCLOUD/issues/LIBCLOUD-1026](
https://issues.apache.org/jira/projects/LIBCLOUD/issues/LIBCLOUD-1026)

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [x] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/UpCloudLtd/libcloud 
1026-upcloud-driver-documentation-update

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1259.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1259


commit 7f1c7a798bf30c3b2223077b60b3305cf8956689
Author: Ilari Mäkelä 
Date:   2018-11-27T14:56:20Z

[LIBCLOUD-1026] Update documentation for UpCloud driver




> Updated documentation for UpCloud driver
> 
>
> Key: LIBCLOUD-1026
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1026
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Ilari Mäkelä
>Priority: Trivial
>
> Update the documentation for UpCloud driver with at least the following:
>  * Update the logo
>  * Add missing data center(s)
>  * Update API credentials instructions



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

[jira] [Commented] (LIBCLOUD-1026) Updated documentation for UpCloud driver

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700553#comment-16700553
 ] 

ASF GitHub Bot commented on LIBCLOUD-1026:
--

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1259


> Updated documentation for UpCloud driver
> 
>
> Key: LIBCLOUD-1026
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1026
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Ilari Mäkelä
>Priority: Trivial
>
> Update the documentation for UpCloud driver with at least the following:
>  * Update the logo
>  * Add missing data center(s)
>  * Update API credentials instructions



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

[jira] [Commented] (LIBCLOUD-1025) add a driver for RcodeZero DNS

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695916#comment-16695916
 ] 

ASF GitHub Bot commented on LIBCLOUD-1025:
--

GitHub user MikeAT opened a pull request:

https://github.com/apache/libcloud/pull/1256

[LIBCLOUD-1025] Add a new DNS driver for RcodeZero DNS.

## Add a new DNS driver for RcodeZero DNS.

### Description

This PR adds a new DNS  driver for RcodeZero DNS (API-Doc at 
https//my.rcodezero.at/api-doc).
RcodeZero is a European DNS provider with 35+ node around the world.

This driver support all methods offered by the libcloud dns api.

The JIRA ticket can be found here:
https://issues.apache.org/jira/browse/LIBCLOUD-1025


### Status
- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [x] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MikeAT/libcloud 
Libcloud-1025_add_RcodeZero_DNS_Driver

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1256.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1256


commit 78dafcbf314723028c9cc7c3268646971957d3ef
Author: Michael Braunoeder 
Date:   2018-11-22T13:40:59Z

[LIBCLOUD-1025] Add a new DNS driver for RcodeZero DNS.




> add a driver for RcodeZero DNS
> --
>
> Key: LIBCLOUD-1025
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1025
> Project: Libcloud
>  Issue Type: Improvement
>  Components: DNS
>Reporter: Michael Braunoeder
>Priority: Major
>
> add a driver for RcodeZero DNS : https://my.rcodezero.at/api-doc/



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

[jira] [Commented] (LIBCLOUD-1022) enhance digitalocean dns driver with ttl parameter

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682399#comment-16682399
 ] 

ASF GitHub Bot commented on LIBCLOUD-1022:
--

GitHub user kiniou opened a pull request:

https://github.com/apache/libcloud/pull/1252

[LIBCLOUD-1022] Enhance digitalocean dns driver with `ttl` parameter

## Enhance digitalocean dns driver with `ttl` parameter

### Description

DigitalOcean provides a parameter to update dns records with `ttl` but the 
current driver's code actually doesn't support it.

For reference:

- 
https://developers.digitalocean.com/documentation/v2/#update-a-domain-record
- 
https://developers.digitalocean.com/documentation/v2/#create-a-new-domain-record

### Status

ready for review


### Checklist (tick everything that applies)

- [X] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [X] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kiniou/libcloud 
LIBCLOUD-1022_digitalocean-dns-record-ttl-parameter

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1252.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1252


commit 57a80f94922eaa1fd8fa813414fac0e45613f80d
Author: Kevin Roy 
Date:   2018-11-10T10:34:17Z

add `ttl` parameters to digitalocean record operations




> enhance digitalocean dns driver with ttl parameter
> --
>
> Key: LIBCLOUD-1022
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1022
> Project: Libcloud
>  Issue Type: Bug
>  Components: DNS
>Reporter: Kevin Roy
>Priority: Minor
>
> DigitalOcean provides a parameters to update dns records with {{ttl}} 
> parameter but the current driver's code actually doesn't support it.
> For reference:
>  * 
> [https://developers.digitalocean.com/documentation/v2/#update-a-domain-record]
>  * 
> [https://developers.digitalocean.com/documentation/v2/#create-a-new-domain-record]
>  



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

[jira] [Commented] (LIBCLOUD-1021) No drivers exist for NTTCommunications Cloud Infrastructure Services

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669544#comment-16669544
 ] 

ASF GitHub Bot commented on LIBCLOUD-1021:
--

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1250


> No drivers exist for NTTCommunications Cloud Infrastructure Services
> 
>
> Key: LIBCLOUD-1021
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1021
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute, LoadBalancer
>Affects Versions: 2.3.0
>Reporter: Mitchell Raful
>Priority: Major
>
> NTT has taken the Dimension Data Cloud and folded it into NTT Communications. 
>  The compute and loadbalancer drivers have been created.  Most the components 
> are the same with some added features that were not updated for DD.  Test, 
> fixture, and docs have been created as well.



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

[jira] [Commented] (LIBCLOUD-1014) Add tags when create a snapshot

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665408#comment-16665408
 ] 

ASF GitHub Bot commented on LIBCLOUD-1014:
--

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1240


> Add tags when create a snapshot
> ---
>
> Key: LIBCLOUD-1014
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1014
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Rafael dos Santos Goncalves
>Priority: Minor
>  Labels: features
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> Hello, 
>     In my aws account have a lot of snapshots of many different projects. To 
> organize that, i need to create tags in my snapshots. Looking the method 
> [create_volume_snapshot|https://libcloud.readthedocs.io/en/latest/compute/drivers/ec2.html#libcloud.compute.drivers.ec2.BaseEC2NodeDriver.create_volume_snapshot]
>  i can't create tags. We can improve that method to accept metadata, what you 
> think ?
>  
> Thanks :D



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

[jira] [Commented] (LIBCLOUD-1021) No drivers exist for NTTCommunications Cloud Infrastructure Services

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662349#comment-16662349
 ] 

ASF GitHub Bot commented on LIBCLOUD-1021:
--

GitHub user snmpboy opened a pull request:

https://github.com/apache/libcloud/pull/1250

[LIBCLOUD-1021] Add loadbalancer and compute drivers for NTTC-CIS.

## Changes Title [LIBCLOUD-1021] Add loadbalancer and compute drivers for 
NTTC-CIS. Tests updated. Tox passes.s)

### Description

NTT Communications has taken over the Dimension Data Cloud and renamed it 
to NTT Communications Cloud Infrastructure Services (NTTC-CIS).  Comnpute and 
loadbalancer drivers have been added along with test, fixtures, and docs.  
### Status

- done, ready for review

### Checklist (tick everything that applies)
Does this require ICLA? Linting was done with pre-confugred Tox tests.
- [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/snmpboy/libcloud DDtoNTT

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1250.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1250


commit c67c2ba3c7cb745a6429efee77616fb8881a888d
Author: srinivasashok 
Date:   2018-05-14T12:59:07Z

changes made to get the VMware tools status.

commit 4089aafe57d1451aa8a9d4af8fb2fbbbfa8acab7
Author: srinivasashok 
Date:   2018-05-15T05:34:59Z

Merge pull request #1 from DimensionDataDevOps/vmware_tool_fix

changes made to get the VMware tools status.

commit 644f1168565af935428b70ea762e58f8e2d83f34
Author: mitch 
Date:   2018-07-06T15:12:13Z

added a test

commit b80bf325878da701d8bc4ebd55e305c2ed4565b5
Author: mitch 
Date:   2018-07-06T19:23:42Z

added nttcis modules to libcloud/common and libcloud/drivers and passed 
connection test

commit cdc27a6687ced8bae58c4fd801924c1e897a68bc
Author: mitch 
Date:   2018-07-13T13:52:49Z

Added nttcis modules to backup and loadbalancer packages and edited 
providers and types modules in packages at needed

commit e49ef2bdd8c8f461fd3f80be6a95b7f48a706556
Author: mitch 
Date:   2018-08-03T15:51:25Z

adding snapshot class to common/nttcis.py

commit 3ebd1dbcd20dc9c2349992875ce8d58af2472bf7
Author: mitch 
Date:   2018-08-06T16:34:00Z

Can now find and list snapshots when enabled on a server

commit b3fa472e5ab7d952e9034eb29c4a8c5acc21599b
Author: mitch 
Date:   2018-08-15T15:34:01Z

renamed test file to lib_edit_test.py

commit db96211311acdc65c10d8104f737c253fa374214
Author: mitch 
Date:   2018-08-15T18:04:21Z

added a lib_misc_test.py for anything that was not a create, edit, or list 
of some type of CC elelemnt

commit b4a7e98d2056d9b4f0f3d9b4535e9aaf10215dc7
Author: mitch 
Date:   2018-08-16T20:12:42Z

fixed drivers/nttcis.py which could not find disks as the CC API had 
changed.

commit 141d235b51da29b3cc414fb7d8a4147ae5b50774
Author: mitch 
Date:   2018-08-27T19:41:33Z

added or updated multiple methods for disk or scsi controller handling.

commit 273486d090ec5604e5a805da845fa7f2d95c814b
Author: mitch 
Date:   2018-08-31T17:55:29Z

added tests for deploy and detete servers

commit fd68cc6d91531ca44f353e34d0c6938d12e7ba42
Author: mitch 
Date:   2018-09-06T17:22:53Z

fixed ex_edit_firewall_rule as position is not required unless changing 
firewall rule placement

commit 1bffad07ac73d0e99f70612a50a77944a3ff848e
Author: mitch 
Date:   2018-09-09T17:28:20Z

added 'xsi:nil': 'true' to compute/drivers/nttcis module in 
edit_ip_address_list

commit b19a16539c34d22c3d7582c2a32f6a613b78bb16
Author: mitch 
Date:   2018-09-17T13:45:13Z

added tests for all aspects of Vlans and NAT Rules

commit 2e6156f9e675926fb03c03c03c7edac63e028ad0
Author: mitch 
Date:   2018-09-18T14:32:11Z

Added the ability to specify a load balancing algorithm without having to 
use the Aglortimh class in base.py.  Changed load balancing algorithm choices 
to LEAST_CONNECTIONS_MEMBER, LEAST_CONNECTIONS_NODE, OBSERVED_MEMBER, 
OBSERVED_NODE, PREDICTIVE_MEMBER, PREDICTIVE_NODE

commit f63a13dcd953cf29348d358578f8e89552771185
Author: mitch 
Date:   2018-09-20T19:01:10Z

update tests in all test modules

commit d4ae1ababf549bf88b4971fad4eff733d2d711f0
Author: mitch 
Date:   2018-09-26T17:21:26Z

Added support for expanding a VM's disk.  Added a get snapshot using 
snapshot id. Removed 

[jira] [Commented] (LIBCLOUD-1017) Improvements to Azure ARM compute driver

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16632632#comment-16632632
 ] 

ASF GitHub Bot commented on LIBCLOUD-1017:
--

GitHub user palashgandhi opened a pull request:

https://github.com/apache/libcloud/pull/1244

[LIBCLOUD-1017] Improvements to Azure ARM compute driver

## [LIBCLOUD-1017] Improvements to Azure ARM compute driver

### Description

The following are the proposed changes in brief:

1. Add functionality to resize a volume in Azure
2. Add functionality to update the network profile of a node
3. Add functionality to update a network interface's properties
4. Add functionality to check IP address availability
5. Create and Update some fixtures
6. Some minor fixes to docstrings

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/palashgandhi/libcloud trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1244.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1244


commit 3c63780e9de65cd0939cd685825e6eff82c3bea7
Author: Palash Gandhi 
Date:   2018-09-12T01:14:46Z

[LIBCLOUD-1017] Improvements to Azure ARM compute driver




> Improvements to Azure ARM compute driver
> 
>
> Key: LIBCLOUD-1017
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1017
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Palash Gandhi
>Priority: Minor
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> The following are the proposed changes in brief:
>  # Add ability to set API version to be used
>  # Add functionality to resize a volume in Azure
>  # Add functionality to update the network profile of a node
>  # Add functionality to update a network interface's properties
>  # Add functionality to check IP address availability
>  # Create and Update some fixtures



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

[jira] [Commented] (LIBCLOUD-1017) Improvements to Azure ARM compute driver

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16632621#comment-16632621
 ] 

ASF GitHub Bot commented on LIBCLOUD-1017:
--

Github user palashgandhi closed the pull request at:

https://github.com/apache/libcloud/pull/1243


> Improvements to Azure ARM compute driver
> 
>
> Key: LIBCLOUD-1017
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1017
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Palash Gandhi
>Priority: Minor
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> The following are the proposed changes in brief:
>  # Add ability to set API version to be used
>  # Add functionality to resize a volume in Azure
>  # Add functionality to update the network profile of a node
>  # Add functionality to update a network interface's properties
>  # Add functionality to check IP address availability
>  # Create and Update some fixtures



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

[jira] [Commented] (LIBCLOUD-1017) Improvements to Azure ARM compute driver

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630862#comment-16630862
 ] 

ASF GitHub Bot commented on LIBCLOUD-1017:
--

GitHub user palashgandhi opened a pull request:

https://github.com/apache/libcloud/pull/1243

[LIBCLOUD-1017] Improvements to Azure ARM compute driver

## [LIBCLOUD-1017] Improvements to Azure ARM compute driver

### Description

The following are the proposed changes in brief:

1. Add ability to set API version to be used
2. Add functionality to resize a volume in Azure
3. Add functionality to update the network profile of a node
4. Add functionality to update a network interface's properties
5. Add functionality to check IP address availability
6. Create and Update some fixtures
7. Some minor fixes to docstrings

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)

### Notes to reviewers
- I am still in doubt about the fixtures I generated


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/palashgandhi/libcloud trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1243.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1243


commit 5333c1339a4bd707a104be55d1c17b8354326a9d
Author: Palash Gandhi 
Date:   2018-09-12T01:14:46Z

[LIBCLOUD-1017] Improvements to Azure ARM compute driver




> Improvements to Azure ARM compute driver
> 
>
> Key: LIBCLOUD-1017
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1017
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Palash Gandhi
>Priority: Minor
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> The following are the proposed changes in brief:
>  # Add ability to set API version to be used
>  # Add functionality to resize a volume in Azure
>  # Add functionality to update the network profile of a node
>  # Add functionality to update a network interface's properties
>  # Add functionality to check IP address availability
>  # Create and Update some fixtures



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

[jira] [Commented] (LIBCLOUD-874) Does Libcloud have plans to support new versions of OpenStack?

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16628316#comment-16628316
 ] 

ASF GitHub Bot commented on LIBCLOUD-874:
-

GitHub user micafer opened a pull request:

https://github.com/apache/libcloud/pull/1242

Implement new versions of OpenStack API calls [LIBCLOUD-874]

## Implement new versions of OpenStack API calls [LIBCLOUD-874]

### Description

This PR overwrite the usage of the deprecated nova API methods:
- /os-volumes
- /os-snapshots
- /os-security-groups
- /os-security-group-rules
- /os-floating-ips
- /os-floating-ip-pools

Replacing them with corresponding calls to neutron and cinder.

Also other minor fixes has been made as fixing the function parse_error to 
avoid error if "code" is not in the response message or fixing _to_port 
function to make it work with old OpenStack versions where some fields as: 
port_security_enabled or project_id are not returned by the API.

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/micafer/libcloud sec_groups

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1242.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1242


commit b3d8b15b81a934d9364df168ae5433549a5a880e
Author: micafer 
Date:   2018-09-24T10:54:47Z

Add cinder support LIBCLOUD-874

commit 1761c77c836faa0af53f390bc9ae012ab56e653b
Author: micafer 
Date:   2018-09-24T11:03:38Z

Add cinder support LIBCLOUD-874

commit 78e96a51eaca71c0156553de599fbf6b9e1179f6
Author: micafer 
Date:   2018-09-24T13:19:43Z

Add cinder support LIBCLOUD-874

commit 82b3dd034eb23e2ce7df01f11305a08b52c4773c
Author: micafer 
Date:   2018-09-24T14:10:39Z

Add cinder support LIBCLOUD-874

commit 557e1e5fa661eb2dedc914913606ea5cdb7fcb90
Author: micafer 
Date:   2018-09-24T14:20:20Z

Add cinder support LIBCLOUD-874

commit a65f4a6cc4439355ae3d39dec6f606e0470a992e
Author: micafer 
Date:   2018-09-24T14:32:58Z

Add cinder support LIBCLOUD-874

commit b6103c7be4f22960b45cb5d24ee50a18fe16cc28
Author: micafer 
Date:   2018-09-24T15:13:29Z

Move sec groups to neutron api LIBCLOUD-874

commit bd8318b53676f84e91ed775dc174545f00ac834b
Author: micafer 
Date:   2018-09-24T15:16:19Z

Add cinder support LIBCLOUD-874

commit 860bfad85d108d77923acb8422bf561e58b68d16
Author: micafer 
Date:   2018-09-24T15:21:20Z

Merge branch 'trunk' into sec_groups

commit c5add2fc8436088e07f20e9da3a6c7a491257101
Author: micafer 
Date:   2018-09-25T06:57:05Z

Move sec groups to neutron api LIBCLOUD-874

commit 9cc717f2643e3375d729f04816e8df65ed5a52db
Author: micafer 
Date:   2018-09-25T13:35:28Z

Move floatingips to neutron api LIBCLOUD-874

commit ef30fe7f9ec8f6fbe09e384485f933a1ec7904c9
Author: micafer 
Date:   2018-09-25T14:24:14Z

Fix _to_port to make it work with old versions

commit bcbd0ca33c4ce4649e12d8289091a850bdc38ffd
Author: micafer 
Date:   2018-09-25T14:38:45Z

Remove print

commit fbe0e2613b1f8e6a40164d7513b357602b73de8e
Author: micafer 
Date:   2018-09-25T14:54:01Z

Update comment




> Does Libcloud have plans to support new versions of OpenStack?
> --
>
> Key: LIBCLOUD-874
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-874
> Project: Libcloud
>  Issue Type: Improvement
>Reporter: Jim
>Priority: Blocker
>
> In the latest version 1.3.0, Libcloud still use Nova API to provide the 
> image, network and volume functions, which are deprecated in current 
> OpenStack verison. Does Libcloud have plans to support Glance v2, Neutron 
> v2.0 and Cinder v2 API for OpenStack?



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

[jira] [Commented] (LIBCLOUD-1014) Add tags when create a snapshot

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626097#comment-16626097
 ] 

ASF GitHub Bot commented on LIBCLOUD-1014:
--

GitHub user elesbom opened a pull request:

https://github.com/apache/libcloud/pull/1240

[LIBCLOUD-1014] Accept tags when create a snapshot

## Accept tags when create snapshot

### Description
 In my aws account have a lot of snapshots of many different projects. To 
organize that, i need to create tags in my snapshots. Looking the method 
[create_volume_snapshot](https://libcloud.readthedocs.io/en/latest/compute/drivers/ec2.html#libcloud.compute.drivers.ec2.BaseEC2NodeDriver.create_volume_snapshot)
 i can't create tags. This pull request allow you pass tags to snapshot. Link 
for [jira](https://issues.apache.org/jira/browse/LIBCLOUD-1014)

### Status
- done, ready for review

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/elesbom/libcloud 
LIBCLOUD-1014_tags_for_snapshot

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1240.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1240


commit 53d2b2c2044f910cde13e6660590545559d5870a
Author: elesbom 
Date:   2018-09-24T16:18:42Z

[LIBCLOUD-1014] Accept metadata when create a snapshot




> Add tags when create a snapshot
> ---
>
> Key: LIBCLOUD-1014
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1014
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Rafael dos Santos Goncalves
>Priority: Minor
>  Labels: features
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> Hello, 
>     In my aws account have a lot of snapshots of many different projects. To 
> organize that, i need to create tags in my snapshots. Looking the method 
> [create_volume_snapshot|https://libcloud.readthedocs.io/en/latest/compute/drivers/ec2.html#libcloud.compute.drivers.ec2.BaseEC2NodeDriver.create_volume_snapshot]
>  i can't create tags. We can improve that method to accept metadata, what you 
> think ?
>  
> Thanks :D



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

[jira] [Commented] (LIBCLOUD-997) OpenStack_2_ImageConnection does not work if ex_force_base_url is used

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620272#comment-16620272
 ] 

ASF GitHub Bot commented on LIBCLOUD-997:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1215


> OpenStack_2_ImageConnection does not work if ex_force_base_url is used
> --
>
> Key: LIBCLOUD-997
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-997
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Miguel Caballer
>Priority: Major
>
> The OpenStack_2_NodeDriver uses two connections
> the base class connection attribute and a new one: image_connection.
> In this case if the user has specified the ex_force_base_url one of them will 
> fail, as both uses the same base url, but there are different services with 
> different urls.  If the user set the compute base url (the standard case) the 
> image one will not work a viceversa
>  



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

[jira] [Commented] (LIBCLOUD-1005) Update gandi compute driver to permit ansible dynamic inventory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588656#comment-16588656
 ] 

ASF GitHub Bot commented on LIBCLOUD-1005:
--

GitHub user gdchamal opened a pull request:

https://github.com/apache/libcloud/pull/1234

[LIBCLOUD-1005] Update gandi driver

## Update gandi compute driver to permit a complete integration with ansible

### Description

Refresh the gandi compute driver and add some functionalities to permit to 
have an ansible dynamic inventory.

Add private vlan management methods
Add a farm parameter for node creation to group them for dynamic inventory
Better management of additionnal IP addresses (public and privates)
Full test suite and refresh of existing ones

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Gandi/libcloud trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1234.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1234


commit a449951f6cf59c0c89b906dee43e87d84b9211f2
Author: Pablo 
Date:   2018-05-11T09:03:43Z

[LIBCLOUD-1005] Update gandi driver




> Update gandi compute driver to permit ansible dynamic inventory
> ---
>
> Key: LIBCLOUD-1005
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1005
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Aymeric Barantal
>Priority: Minor
>
> I want to make a small update of gandi compute driver to permit to set a 
> `farm` parameter upon node creation. This parameter then will be used to 
> group nodes for a dynamic ansible inventory



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

[jira] [Commented] (LIBCLOUD-1007) RFC3339 date parsing in GCE driver fails

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16585814#comment-16585814
 ] 

ASF GitHub Bot commented on LIBCLOUD-1007:
--

GitHub user fatmcgav opened a pull request:

https://github.com/apache/libcloud/pull/1232

[LIBCLOUD-1007] Resolve RFC3339 date parsing issues with GCE Compute driver.

Resolves issue with RFC3339 date parsing in the GCE Compute driver. 
Timestamp strings are now parsed upto and including the microsecond value. 
The call to deprecate the Google Compute image now also correctly formats 
the date as RFC3339 format. 

Fixes https://issues.apache.org/jira/browse/LIBCLOUD-1007


- done, ready for review


- [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/fatmcgav/libcloud gce_fix_rfc3339_parsing

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1232.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1232


commit d3ae06dcb95725db7d6474f193e182e3e4aa46fc
Author: Gavin Williams 
Date:   2018-08-20T11:20:22Z

[gce] Fix parsing of timestamp string.
Now parses microseconds as part of strptime function, stopping at the '+' 
character to denote a timezone offset.

commit 37a6d9adccbe0f6b1373708a4f7fcc14a38642b7
Author: Gavin Williams 
Date:   2018-08-20T11:21:31Z

[gce] Use return value from `timestamp_to_datetime` and correctly format
the request datetime to RFC3339 format.




> RFC3339 date parsing in GCE driver fails
> 
>
> Key: LIBCLOUD-1007
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1007
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Gavin Williams
>Priority: Major
>
> When attempting to use the `deprecated` param on `GCENodeImage.deprecate()` 
> [1], the call was failing with:
> {noformat}
> 2018-08-20 11:52:08 - DEBUG: Delete at = 2018-08-23T10:52:08.061384+00:00
> Traceback (most recent call last):
> File 
> "/Users/fatmcgav/.virtualenvs/packer_builder/lib/python3.6/site-packages/libcloud/compute/drivers/gce.py",
>  line 6371, in ex_deprecate_image
> timestamp_to_datetime(value)
> File 
> "/Users/fatmcgav/.virtualenvs/packer_builder/lib/python3.6/site-packages/libcloud/compute/drivers/gce.py",
>  line 57, in timestamp_to_datetime
> ts = datetime.datetime.strptime(timestamp[:-10], '%Y-%m-%dT%H:%M:%S')
> File 
> "/usr/local/Cellar/python/3.6.5_1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/_strptime.py",
>  line 565, in _strptime_datetime
> tt, fraction = _strptime(data_string, format)
> File 
> "/usr/local/Cellar/python/3.6.5_1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/_strptime.py",
>  line 365, in _strptime
> data_string[found.end():])
> ValueError: unconverted data remains: .06
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File "scripts/packer-image-manager.py", line 135, in 
> main()
> File "scripts/packer-image-manager.py", line 126, in main
> deprecate_images()
> File "scripts/packer-image-manager.py", line 56, in deprecate_images
> dry_run=args.dry_run)
> File "/Users/fatmcgav/Work/infra/infra/packer2.0/lib/utils.py", line 82, in 
> deprecate_image
> if image.deprecate(replacement_image, 'DEPRECATED', deleted=delete_at):
> File 
> "/Users/fatmcgav/.virtualenvs/packer_builder/lib/python3.6/site-packages/libcloud/compute/drivers/gce.py",
>  line 699, in deprecate
> deprecated, obsolete, deleted)
> File 
> "/Users/fatmcgav/.virtualenvs/packer_builder/lib/python3.6/site-packages/libcloud/compute/drivers/gce.py",
>  line 6375, in ex_deprecate_image
> attribute)
> ValueError: deleted must be an RFC3339 timestamp
> {noformat}
> It would appear that the date parsing logic in `timestamp_to_datetime` [2] is 
> flawed, assuming that the length of `microseconds + tz offset` will always be 
> 10 characters, whereas the above example has 12 characters.
> Patch applied as follows:
> {code:java}
> diff --git a/libcloud/compute/drivers/gce.py b/libcloud/compute/drivers/gce.py
> index 3dfc87d3..efcdcb87 100644
> --- a/libcloud/compute/drivers/gce.py
> +++ b/libcloud/compute/drivers/gce.py
> @@ -52,9 +52,9 @@ def timestamp_to_datetime(timestamp):
> :return: Datetime object 

[jira] [Commented] (LIBCLOUD-1005) Update gandi compute driver to permit ansible dynamic inventory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563870#comment-16563870
 ] 

ASF GitHub Bot commented on LIBCLOUD-1005:
--

Github user gdchamal closed the pull request at:

https://github.com/apache/libcloud/pull/1229


> Update gandi compute driver to permit ansible dynamic inventory
> ---
>
> Key: LIBCLOUD-1005
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1005
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Aymeric Barantal
>Priority: Minor
>
> I want to make a small update of gandi compute driver to permit to set a 
> `farm` parameter upon node creation. This parameter then will be used to 
> group nodes for a dynamic ansible inventory



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

[jira] [Commented] (LIBCLOUD-1005) Update gandi compute driver to permit ansible dynamic inventory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563609#comment-16563609
 ] 

ASF GitHub Bot commented on LIBCLOUD-1005:
--

GitHub user gdchamal opened a pull request:

https://github.com/apache/libcloud/pull/1229

[LIBCLOUD-1005] Update gandi driver

## Changes Title (replace this with a logical title for your changes)

Update gandi compute driver to permit a complete integration with ansible

### Description

Refresh the gandi compute driver and add some functionalities to permit to 
have an ansible dynamic inventory.

- Add private vlan management methods
- Add a farm parameter for node creation to group them for dynamic inventory
- Better management of additionnal IP addresses (public and privates)
- Full test suite and refresh of existing ones

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x ] Documentation
- [x ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Gandi/libcloud trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1229.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1229


commit 4f345a691cd814cf66713924da948dd37239f9c9
Author: Pablo 
Date:   2018-05-11T09:03:43Z

[LIBCLOUD-1005] Update gandi driver




> Update gandi compute driver to permit ansible dynamic inventory
> ---
>
> Key: LIBCLOUD-1005
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1005
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Aymeric Barantal
>Priority: Minor
>
> I want to make a small update of gandi compute driver to permit to set a 
> `farm` parameter upon node creation. This parameter then will be used to 
> group nodes for a dynamic ansible inventory



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

[jira] [Commented] (LIBCLOUD-1004) Allow EC2 driver to create_node from LaunchTemplate

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531955#comment-16531955
 ] 

ASF GitHub Bot commented on LIBCLOUD-1004:
--

GitHub user rojopolis opened a pull request:

https://github.com/apache/libcloud/pull/1224

[LIBCLOUD-1004] Add launch template support to EC2 create_node

## Launch template support for EC2 create_node

### Allows Nodes to be created from EC2 Launch Templates

This change allows Nodes to be created from predefined Launch Templates in 
EC2.  
This is useful in a number of scenarios:
* Organizational standards are implemented with Templates.
* etc.

The attributes specified in the call to create_node will take precedence 
over those defined in the template (per provider documentation).

 Provider docs: 
- 
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RunInstances.html
- 
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_LaunchTemplateSpecification.html

### Status
- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rojopolis/libcloud 
LIBCLOUD-1004_ec2_instance_template

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1224.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1224


commit 42a3053ff4bf50ee58ea96504b6036bfeb2d9747
Author: Robert Jordan 
Date:   2018-07-03T21:01:37Z

[LIBCLOUD-1004] Add launch template support to EC2 create_node




> Allow EC2 driver to create_node from LaunchTemplate
> ---
>
> Key: LIBCLOUD-1004
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1004
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Robert Jordan
>Priority: Trivial
>
> As a user of libcloud EC2 driver I would like to be able to create nodes 
> based off of a predefined EC2 launch template.
> https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_LaunchTemplateSpecification.html



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

[jira] [Commented] (LIBCLOUD-1002) Allow GCE driver to create_node from InstanceTemplate

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530772#comment-16530772
 ] 

ASF GitHub Bot commented on LIBCLOUD-1002:
--

GitHub user rojopolis opened a pull request:

https://github.com/apache/libcloud/pull/1223

[LIBCLOUD-1002] Add instance template support to GCE create_node

## Instance template support for GCE create_node

### Allows Nodes to be created from GCE Instance Templates

This change allows Nodes to be created from predefined Instance Templates 
in GCE.  
This is useful in a number of scenarios:
* Organizational standards are implemented with Templates.
* etc.

The attributes specified in the call to create_node will take precedence 
over those defined in the template (per provider documentation).

 Provider docs: 
- https://cloud.google.com/compute/docs/reference/rest/v1/instances/insert
- 
https://cloud.google.com/compute/docs/instances/create-vm-from-instance-template

### Status
- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rojopolis/libcloud 
LIBCLOUD-1002_gce_instance_template

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1223.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1223


commit 271aff59636f7f1dd9764ba39753fd5c1c4b3f27
Author: Robert Jordan 
Date:   2018-07-03T03:21:22Z

[LIBCLOUD-1002] Add instance template support to GCE create_node




> Allow GCE driver to create_node from InstanceTemplate
> -
>
> Key: LIBCLOUD-1002
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1002
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Robert Jordan
>Priority: Trivial
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> As a user of libcloud GCE driver I would like to be able to create nodes 
> based off of a predefined GCE instance template.
> https://cloud.google.com/compute/docs/instances/create-vm-from-instance-template



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

[jira] [Commented] (LIBCLOUD-1002) Allow GCE driver to create_node from InstanceTemplate

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530615#comment-16530615
 ] 

ASF GitHub Bot commented on LIBCLOUD-1002:
--

Github user rojopolis closed the pull request at:

https://github.com/apache/libcloud/pull/1222


> Allow GCE driver to create_node from InstanceTemplate
> -
>
> Key: LIBCLOUD-1002
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1002
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Robert Jordan
>Priority: Trivial
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> As a user of libcloud GCE driver I would like to be able to create nodes 
> based off of a predefined GCE instance template.
> https://cloud.google.com/compute/docs/instances/create-vm-from-instance-template



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

[jira] [Commented] (LIBCLOUD-1002) Allow GCE driver to create_node from InstanceTemplate

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530576#comment-16530576
 ] 

ASF GitHub Bot commented on LIBCLOUD-1002:
--

GitHub user rojopolis opened a pull request:

https://github.com/apache/libcloud/pull/1222

[LIBCLOUD-1002] Instance template support for GCE create_node

## Instance template support for GCE create_node

### Allows Nodes to be created from GCE Instance Templates

This change allows Nodes to be created from predefined Instance Templates 
in GCE.  
This is useful in a number of scenarios:
* Organizational standards are implemented with Templates.
* etc.

The attributes specified in the call to create_node will take precedence 
over those defined in the template (per provider documentation).

 Provider docs: 
- https://cloud.google.com/compute/docs/reference/rest/v1/instances/insert
- 
https://cloud.google.com/compute/docs/instances/create-vm-from-instance-template

### Status
- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rojopolis/libcloud 
LIBCLOUD-1002_gce_source_instance_template

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1222.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1222


commit ba1ce31771b8691af864d7e3585e0778ab685843
Author: Robert Jordan 
Date:   2018-07-02T23:08:39Z

[LIBCLOUD-1002] Add support for creating GCE instances from template

commit 8f64453561e9b3b8e7306223304f165b15595c7f
Author: Robert Jordan 
Date:   2018-07-02T23:27:48Z

[LIBCLOUD-1002] Add support for creating GCE instances from template




> Allow GCE driver to create_node from InstanceTemplate
> -
>
> Key: LIBCLOUD-1002
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1002
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Robert Jordan
>Priority: Trivial
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> As a user of libcloud GCE driver I would like to be able to create nodes 
> based off of a predefined GCE instance template.
> https://cloud.google.com/compute/docs/instances/create-vm-from-instance-template



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

[jira] [Commented] (LIBCLOUD-956) Add Scaleway Compute driver

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508553#comment-16508553
 ] 

ASF GitHub Bot commented on LIBCLOUD-956:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1121


> Add Scaleway Compute driver
> ---
>
> Key: LIBCLOUD-956
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-956
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Compute
>Reporter: Dan Hunsaker
>Priority: Major
>
> Adds support for Scaleway as a compute provider. Functionality is fairly 
> basic, but does work properly. Tests are in place to verify, with fixtures 
> pulled from the Scaleway docs, or actual responses to the associated requests 
> where the docs aren't clear.



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

[jira] [Commented] (LIBCLOUD-997) OpenStack_2_ImageConnection does not work if ex_force_base_url is used

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490332#comment-16490332
 ] 

ASF GitHub Bot commented on LIBCLOUD-997:
-

GitHub user micafer opened a pull request:

https://github.com/apache/libcloud/pull/1215

Fix LIBCLOUD-997, implements LIBCLOUD-998 and LIBCLOUD-604

## Fix LIBCLOUD-997, implements LIBCLOUD-998 and LIBCLOUD-604

### Description
 LIBCLOUD-604:

Add equivalent function for returning listed subnets in OpenStack driver. 
Similar to `ex_list_subnet` for EC2 endpoint providers.

 LIBCLOUD-997:

The OpenStack_2_NodeDriver uses two connections

the base class connection attribute and a new one: image_connection.

In this case if the user has specified the ex_force_base_url one of them 
will fail, as both uses the same base url, but there are different services 
with different urls.  If the user set the compute base url (the standard case) 
the image one will not work a viceversa

 LIBCLOUD-998:
OpenStack_2_NodeDriver class uses the deprecated path "/os-networks" of the 
compute API instead of using the "/v2.0/networks" of the neutron API that i the 
current one.


### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/micafer/libcloud trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1215.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1215


commit 814bc3e366bdce7f2b935eeb3c7ed21d562cf3e8
Author: micafer 
Date:   2017-06-20T06:21:37Z

Fix #LIBCLOUD-925

commit 7deee735c43b38e021153579d41193b49cbba1dd
Author: micafer 
Date:   2017-11-29T12:37:11Z

Merge remote-tracking branch 'upstream/trunk' into trunk

commit 00efcf2be242acfa8821dec7c2ec14537a5f9584
Author: micafer 
Date:   2017-11-29T12:51:18Z

Improve error message

commit e23be01804d4d435382fb2dc2b1bf68ad0f5e401
Author: micafer 
Date:   2017-11-30T08:56:02Z

Fix LIBCLOUD-965

commit 3dd6f4d5aec21f8d11e415fe4d95d2e316bb3dac
Author: micafer 
Date:   2017-11-30T09:59:31Z

Fix test

commit 15ae45805dcef1d91498af33598ee5c2059c411a
Author: micafer 
Date:   2017-12-18T09:21:24Z

Merge remote-tracking branch 'upstream/trunk' into trunk

commit ca38440afb003c30b884cd6e1afb15cfb163d0d6
Author: micafer 
Date:   2018-01-30T11:46:23Z

Imrpove test

commit 5deb1595eb110e1ae92db01f2579f6c68e062fd0
Author: Miguel Caballer 
Date:   2018-05-11T11:42:22Z

Merge pull request #1 from apache/trunk

Merge upstream

commit a6c19b6ce97a6c7d151ede99627bcdc8f6590f12
Author: micafer 
Date:   2018-05-11T11:47:20Z

return extra_specs in OpenStackNodeSize

commit 271813f59cd9f0b5b67f829b4d5427fe62a352b7
Author: micafer 
Date:   2018-05-11T11:49:49Z

return extra_specs in OpenStackNodeSize

commit c7464b57dcc7e09fdfa01348de85f85046dac3a1
Author: micafer 
Date:   2018-05-25T07:05:49Z

Fix LIBCLOUD-997, implements LIBCLOUD-998 and LIBCLOUD-604




> OpenStack_2_ImageConnection does not work if ex_force_base_url is used
> --
>
> Key: LIBCLOUD-997
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-997
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Miguel Caballer
>Priority: Major
>
> The OpenStack_2_NodeDriver uses two connections
> the base class connection attribute and a new one: image_connection.
> In this case if the user has specified the ex_force_base_url one of them will 
> fail, as both uses the same base url, but there are different services with 
> different urls.  If the user set the compute base url (the standard case) the 
> image one will not work a viceversa
>  



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

[jira] [Commented] (LIBCLOUD-996) Support GCP service_account authentication from JSON obj/str

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487953#comment-16487953
 ] 

ASF GitHub Bot commented on LIBCLOUD-996:
-

GitHub user bverschueren opened a pull request:

https://github.com/apache/libcloud/pull/1214

[LIBCLOUD-996] Support GCP service_account authentication from JSON obj/str

## Support GCP service_account authentication from JSON obj/str

### Description


Currently GCP service_account authentication credentials can be provided 
using the JSON/PEM file acquired from GCP console or gcloud utility. It would 
be convenient if the JSON content could be directly provided as an object or 
serialized JSON string to eliminate the need of having the file locally on the 
calling host.

In this PR:
- add logic to support JSON dict and str handling
- rearrange PEM/JSON related GCE_PARAMS_* constant names in test_google.py 
for better clarity
- add tests for JSON content as a dict and as a str


### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bverschueren/libcloud 
LIBCLOUD-996_gcp_svc_acct_credentials_from_json

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1214.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1214


commit 409d428eed31b017c74c9b34378a3817b55398df
Author: Bram Verschueren 
Date:   2018-05-09T13:56:29Z

add support for retrieving private key from JSON object/string/file




> Support GCP service_account authentication from JSON obj/str
> 
>
> Key: LIBCLOUD-996
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-996
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Core
>Reporter: Bram
>Priority: Minor
>
> Currently GCP service_account authentication credentials can be provided 
> using the JSON/PEM file acquired from GCP console or gcloud utility. It would 
> be convenient if the JSON content could be directly provided as an object or 
> serialized JSON string to eliminate the need of having the file locally on 
> the calling host.



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

[jira] [Commented] (LIBCLOUD-963) Add option to attach GPU when creating instances in GCE

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458379#comment-16458379
 ] 

ASF GitHub Bot commented on LIBCLOUD-963:
-

GitHub user byronyi reopened a pull request:

https://github.com/apache/libcloud/pull/1204

Fixes LIBCLOUD-963

See https://github.com/apache/libcloud/pull/1163#issuecomment-385246605 for 
the rationale.

@mjjohnson1 @pquentin @tonybaloney @crunk1 Any comments?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/byronyi/libcloud trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1204.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1204


commit db5a41102f68ab7933c8fee2ab7245ec72abe441
Author: Bairen Yi 
Date:   2018-04-29T16:24:44Z

Fixes LIBCLOUD-963




> Add option to attach GPU when creating instances in GCE
> ---
>
> Key: LIBCLOUD-963
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-963
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Gareth McFarlane
>Priority: Major
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Currently, GCP provides the ability to attach a GPU to in instance when it's 
> created:
> https://cloud.google.com/compute/docs/gpus/add-gpus
> This option should be added to the GCE Compute module.  



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

[jira] [Commented] (LIBCLOUD-963) Add option to attach GPU when creating instances in GCE

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458369#comment-16458369
 ] 

ASF GitHub Bot commented on LIBCLOUD-963:
-

Github user byronyi closed the pull request at:

https://github.com/apache/libcloud/pull/1204


> Add option to attach GPU when creating instances in GCE
> ---
>
> Key: LIBCLOUD-963
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-963
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Gareth McFarlane
>Priority: Major
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Currently, GCP provides the ability to attach a GPU to in instance when it's 
> created:
> https://cloud.google.com/compute/docs/gpus/add-gpus
> This option should be added to the GCE Compute module.  



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

[jira] [Commented] (LIBCLOUD-963) Add option to attach GPU when creating instances in GCE

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458067#comment-16458067
 ] 

ASF GitHub Bot commented on LIBCLOUD-963:
-

GitHub user byronyi opened a pull request:

https://github.com/apache/libcloud/pull/1204

Fixes LIBCLOUD-963

See https://github.com/apache/libcloud/pull/1163#issuecomment-385246605 for 
the rationale.

@mjjohnson1 @pquentin @tonybaloney @crunk1 Any comments?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/byronyi/libcloud trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1204.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1204






> Add option to attach GPU when creating instances in GCE
> ---
>
> Key: LIBCLOUD-963
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-963
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Gareth McFarlane
>Priority: Major
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Currently, GCP provides the ability to attach a GPU to in instance when it's 
> created:
> https://cloud.google.com/compute/docs/gpus/add-gpus
> This option should be added to the GCE Compute module.  



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

[jira] [Commented] (LIBCLOUD-851) Azure blob storage - Unable to list blobs of a container

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440126#comment-16440126
 ] 

ASF GitHub Bot commented on LIBCLOUD-851:
-

GitHub user daviskirk opened a pull request:

https://github.com/apache/libcloud/pull/1202

Fix hash value in azure blob store


## Upgrade azure blob storage api

### Description

* Upgrade to minimum api version allowed by azure (see )

* Return actual file (md5) hash instead of etag ('"0xFFF"')

The current trunk version of libcloud throws a Libcloud error also 
described in (https://issues.apache.org/jira/browse/LIBCLOUD-851)

```
Traceback (most recent call last):
  File "...", line 12, in 
c = d.list_containers()[1]
  File "libcloud/libcloud/storage/base.py", line 209, in list_containers
return list(self.iterate_containers())
  File "libcloud/libcloud/storage/drivers/azure_blobs.py", line 371, in 
iterate_containers
(response.status), driver=self)
libcloud.common.types.LibcloudError:  'Unexpected status code: 400'>
```
and the corresponing response body of the failing request is:
```
response.body
'InvalidHeaderValueThe value for 
one of the HTTP headers is not in the correct 
format.\nRequestId:dd262993-501e-0030-6cd1-d5868200\nTime:2018-04-16T22:24:39.6566784Zx-ms-version2012-02-12'
```

From looking at:

https://docs.microsoft.com/en-us/rest/api/storageservices/versioning-for-the-azure-storage-services#for-blob-storage-accounts

the easiest fix is to upgrade the api version to the minumum supported 
version (2014-02-12).

In addition, the other cloud drivers all provide the actual md5 hash when 
uploading or getting an object.  This allows the user to check if a file has 
changed online compared to locally.  The current master version provides the 
etag value as the "hash" attribute (interestingly with literal quotes around 
the tag: `'"0xFFF"'`) which is not compatible with the other 
drivers.

Replace this with the PR description (mention the changes you have made, why
you have made them, provide some background and any references to the 
provider
documentation if needed, etc.).

I am assuming that these are both bugs and not design decisions (if so feel 
free to close this request).

### Status

- work in progress

### Checklist (tick everything that applies)

- [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/daviskirk/libcloud 
851_fix-azure-blob-storage-api-version

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1202.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1202


commit c73beb6879353ff9689f23580a5ee3499782de05
Author: Davis Kirkendall 
Date:   2018-04-16T22:05:02Z

Fix hash value in azure blob store

- Upgrade to minimum api version allowed by azure (see 
https://docs.microsoft.com/en-us/rest/api/storageservices/versioning-for-the-azure-storage-services#for-blob-storage-accounts)
- Return actual file (md5) hash instead of etag ('"0xFFF"')




> Azure blob storage - Unable to list blobs of a container
> 
>
> Key: LIBCLOUD-851
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-851
> Project: Libcloud
>  Issue Type: Bug
>  Components: Storage
> Environment: Debian GNU/Linux
>Reporter: Antoine R. Dumont
>Priority: Major
>  Labels: blobstore, storage_drivers
>
> Hello,
> Trying to list the blobs of a container in an azure blob storage, the 
> instanciation step of a container systematically breaks with a 400 bad 
> request.
> I have not much details in the error message:
> {code:title=output|borderStyle=solid}
> Traceback (most recent call last):
>   File "./bin/basic-scenario", line 20, in 
> container = driver.get_container(container_name=container_name)
>   File 
> "/usr/lib/python3/dist-packages/libcloud/storage/drivers/azure_blobs.py", 
> line 441, in get_container
> (response.status), driver=self)
> libcloud.common.types.LibcloudError:   0x7f674c6b67f0> 'Unexpected status code: 400'
> {code}

[jira] [Commented] (LIBCLOUD-982) Packet _to_size() KeyError data['pricing']['hourly']

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430402#comment-16430402
 ] 

ASF GitHub Bot commented on LIBCLOUD-982:
-

Github user sjain-rvbd closed the pull request at:

https://github.com/apache/libcloud/pull/1199


> Packet _to_size() KeyError data['pricing']['hourly']
> 
>
> Key: LIBCLOUD-982
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-982
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Nick Allen
>Priority: Major
>
> Looks like a typo in the PacketNodeDriver._to_size() method. 
> It's looking for data['pricing']['hourly'], when it's actually stored as 
> data['pricing']['hour']. 
> {code:java}
> File 
> "/Users/nick/.pyenv/versions/2.7.10/envs/bundles-2.7.10/lib/python2.7/site-packages/libcloud/compute/drivers/packet.py",
>  line 96, in list_nodes return list(map(self._to_node, data)) File 
> "/Users/nick/.pyenv/versions/2.7.10/envs/bundles-2.7.10/lib/python2.7/site-packages/libcloud/compute/drivers/packet.py",
>  line 198, in _to_node size = self._to_size(data['plan']) File 
> "/Users/nick/.pyenv/versions/2.7.10/envs/bundles-2.7.10/lib/python2.7/site-packages/libcloud/compute/drivers/packet.py",
>  line 233, in _to_size price = data['pricing']['hourly'] KeyError: 'hourly'
> {code}



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

[jira] [Commented] (LIBCLOUD-982) Packet _to_size() KeyError data['pricing']['hourly']

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430238#comment-16430238
 ] 

ASF GitHub Bot commented on LIBCLOUD-982:
-

GitHub user sjain-rvbd opened a pull request:

https://github.com/apache/libcloud/pull/1199

[LIBCLOUD-982] Data stored in wrong format for Packet providers

https://issues.apache.org/jira/browse/LIBCLOUD-982

A typo in the PacketNodeDriver._to_size() method. 
It's looking for data['pricing']['hourly'], when it's actually stored as 
data['pricing']['hour']. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sjain-rvbd/libcloud 
LIBCLOUD-982_Packet_Driver_to_size

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1199.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1199


commit f6c19f28dcfd209cb36068277e554e4cb134b91a
Author: Saurabh Jain 
Date:   2018-04-09T07:51:29Z

[LIBCLOUD-982] Data stored in data['pricing']['hour'] format for Packet.net 
based providers.




> Packet _to_size() KeyError data['pricing']['hourly']
> 
>
> Key: LIBCLOUD-982
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-982
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Nick Allen
>Priority: Major
>
> Looks like a typo in the PacketNodeDriver._to_size() method. 
> It's looking for data['pricing']['hourly'], when it's actually stored as 
> data['pricing']['hour']. 
> {code:java}
> File 
> "/Users/nick/.pyenv/versions/2.7.10/envs/bundles-2.7.10/lib/python2.7/site-packages/libcloud/compute/drivers/packet.py",
>  line 96, in list_nodes return list(map(self._to_node, data)) File 
> "/Users/nick/.pyenv/versions/2.7.10/envs/bundles-2.7.10/lib/python2.7/site-packages/libcloud/compute/drivers/packet.py",
>  line 198, in _to_node size = self._to_size(data['plan']) File 
> "/Users/nick/.pyenv/versions/2.7.10/envs/bundles-2.7.10/lib/python2.7/site-packages/libcloud/compute/drivers/packet.py",
>  line 233, in _to_size price = data['pricing']['hourly'] KeyError: 'hourly'
> {code}



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

[jira] [Commented] (LIBCLOUD-985) GCE - Support network routingmode and subnet secondary/internal access options

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420184#comment-16420184
 ] 

ASF GitHub Bot commented on LIBCLOUD-985:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1181


> GCE - Support network routingmode and subnet secondary/internal access options
> --
>
> Key: LIBCLOUD-985
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-985
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
> Environment: N/A
>Reporter: Max L
>Priority: Minor
>
> As of 3/2018, Google Cloud APIs support a few more creation flags for 
> networks and subnetworks.
> Networks: BGP Routing mode regional/global
> Subnetworks: Secondary IP Ranges, Private IP access to GCP APIs.
> It would be good to add coverage for these.



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

[jira] [Commented] (LIBCLOUD-958) S3 always upload as application/octet-stream

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420157#comment-16420157
 ] 

ASF GitHub Bot commented on LIBCLOUD-958:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1195


> S3 always upload as application/octet-stream
> 
>
> Key: LIBCLOUD-958
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-958
> Project: Libcloud
>  Issue Type: Bug
>  Components: Storage
>Reporter: Iuri de Silvio
>Priority: Major
>
> S3 multipart upload 
> (https://github.com/apache/libcloud/blob/6e4c2e15e8dcbc7b7c5c9a895f7b78f11fd3ba6b/libcloud/storage/drivers/s3.py#L868)
>  does not try to guess content mimetype, like normal upload does 
> (https://github.com/apache/libcloud/blob/6e4c2e15e8dcbc7b7c5c9a895f7b78f11fd3ba6b/libcloud/storage/base.py#L597).
> All multipart upload is done as `application/octet-stream`.



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

[jira] [Commented] (LIBCLOUD-986) List / Iterate container with prefix for Azure Blob service (This support exists in the other drivers already)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16410830#comment-16410830
 ] 

ASF GitHub Bot commented on LIBCLOUD-986:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1193


> List / Iterate container with prefix for Azure Blob service (This support 
> exists in the other drivers already)
> --
>
> Key: LIBCLOUD-986
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-986
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Storage
>Reporter: Joshua Hawkinson
>Priority: Major
>
> While testing out the libcloud storage abstraction I've come across a curious 
> omission in driver support. It seems that for many drivers there is 
> additional support for the {{list_container_objects()}} and 
> {{iterate_container_objects()}} to support a prefix (or {{ex_prefix)}}. 
> This functionality is not present in the Azure driver for some reason.   I've 
> gone and checked the list_blobs API and it also supports this functionality 
> as seen here:
> [https://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs]
>  
> I've attempted a quick and dirty patch that seems to work as well.
> {code}
> azure_blobs.py Line 384
> -def iterate_container_objects(self, container):
> +def iterate_container_objects(self, container, ex_prefix=None):
> """
> @inherits: :class:`StorageDriver.iterate_container_objects`
> """
> params = {'restype': 'container',
>   'comp': 'list',
> +  'prefix': ex_prefix,
>   'maxresults': RESPONSES_PER_REQUEST,
>   'include': 'metadata'}
> Line 419 (Add new function)
> def list_container_objects(self, container, ex_prefix=None):
> """
> Return a list of objects for the given container.
> 
> :param container: Container instance.
> :type container: :class:`Container`
> 
> :param ex_prefix: Only return objects starting with ex_prefix
> :type ex_prefix: ``str``
> 
> :return: A list of Object instances.
> :rtype: ``list`` of :class:`Object`
> """
> return list(self.iterate_container_objects(container,
>ex_prefix=ex_prefix))
> 
>  {code}
>  
> I've just worked around this at a higher level for now. There isn't any 
> urgency on my end,  but it would be nice if the abstraction was more 
> consistent so I could remove the workaround code.



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

[jira] [Commented] (LIBCLOUD-986) List / Iterate container with prefix for Azure Blob service (This support exists in the other drivers already)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408465#comment-16408465
 ] 

ASF GitHub Bot commented on LIBCLOUD-986:
-

GitHub user jhawkinson opened a pull request:

https://github.com/apache/libcloud/pull/1193

LIBCLOUD-986: Add prefix option to azure blob list and iterate containers

## LIBCLOUD-986: Add prefix filter for list and iterate containers to Azure 
Blob Storage Driver

### Description
While testing out the libcloud storage abstraction I've come across a 
curious omission in driver support. It seems that for many drivers there is 
additional support for the list_container_objects() and 
iterate_container_objects() to support a prefix (or ex_prefix). 

This functionality is not present in the Azure driver for some reason.   
I've gone and checked the list_blobs API and it also supports this 
functionality as seen here:

https://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs

I've added the support to the AzureBlobsStorageDriver with these changes.

### Status
- done, ready for review

### Checklist
- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jhawkinson/libcloud LIBCLOUD-986

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1193.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1193


commit 735c9e645a067da48192f4846502fd50e1feef0b
Author: jhawk 
Date:   2018-03-21T19:08:02Z

LIBCLOUD-986: Add prefix option to azure blob list and iterate container 
methods




> List / Iterate container with prefix for Azure Blob service (This support 
> exists in the other drivers already)
> --
>
> Key: LIBCLOUD-986
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-986
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Storage
>Reporter: Joshua Hawkinson
>Priority: Major
>
> While testing out the libcloud storage abstraction I've come across a curious 
> omission in driver support. It seems that for many drivers there is 
> additional support for the {{list_container_objects()}} and 
> {{iterate_container_objects()}} to support a prefix (or {{ex_prefix)}}. 
> This functionality is not present in the Azure driver for some reason.   I've 
> gone and checked the list_blobs API and it also supports this functionality 
> as seen here:
> [https://docs.microsoft.com/en-us/rest/api/storageservices/list-blobs]
>  
> I've attempted a quick and dirty patch that seems to work as well.
> {code}
> azure_blobs.py Line 384
> -def iterate_container_objects(self, container):
> +def iterate_container_objects(self, container, ex_prefix=None):
> """
> @inherits: :class:`StorageDriver.iterate_container_objects`
> """
> params = {'restype': 'container',
>   'comp': 'list',
> +  'prefix': ex_prefix,
>   'maxresults': RESPONSES_PER_REQUEST,
>   'include': 'metadata'}
> Line 419 (Add new function)
> def list_container_objects(self, container, ex_prefix=None):
> """
> Return a list of objects for the given container.
> 
> :param container: Container instance.
> :type container: :class:`Container`
> 
> :param ex_prefix: Only return objects starting with ex_prefix
> :type ex_prefix: ``str``
> 
> :return: A list of Object instances.
> :rtype: ``list`` of :class:`Object`
> """
> return list(self.iterate_container_objects(container,
>ex_prefix=ex_prefix))
> 
>  {code}
>  
> I've just worked around this at a higher level for now. There isn't any 
> urgency on my end,  but it would be nice if the abstraction was more 
> consistent so I could remove the workaround code.



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

[jira] [Commented] (LIBCLOUD-961) GCE public projects list out of date

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408285#comment-16408285
 ] 

ASF GitHub Bot commented on LIBCLOUD-961:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1143


> GCE public projects list out of date
> 
>
> Key: LIBCLOUD-961
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-961
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Sean Marlow
>Priority: Minor
>
> https://github.com/apache/libcloud/blob/trunk/libcloud/compute/drivers/gce.py#L1734
> Not available anymore according to GCE projects list: gce-nvme, 
> google-containers
> Missing cos-cloud, suse-sap-cloud, suse-byos-cloud and windows-sql-cloud.
> List found at https://cloud.google.com/compute/docs/images#os-compute-support



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

[jira] [Commented] (LIBCLOUD-973) ex_create_multiple_nodes API in gce.py compute driver does not handle boot disk size.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402036#comment-16402036
 ] 

ASF GitHub Bot commented on LIBCLOUD-973:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1162


> ex_create_multiple_nodes API in gce.py compute driver does not handle boot 
> disk size.
> -
>
> Key: LIBCLOUD-973
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-973
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Rahul Paigavan
>Priority: Major
>  Labels: compute, disk
>
> When we want to create multiple nodes with some specified boot disk size, 
> ex_create_multiple_nodes does not handle this case.
> By default it create a boot disk of 10 GB size.
> We would like to specify  (in GB) to ex_create_multiple_nodes API 
> call
> and it should create  boot disk for node.
> Issue is observed in latest Libcloud 2.2.1 version.



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

[jira] [Commented] (LIBCLOUD-985) GCE - Support network routingmode and subnet secondary/internal access options

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397520#comment-16397520
 ] 

ASF GitHub Bot commented on LIBCLOUD-985:
-

GitHub user maxlip opened a pull request:

https://github.com/apache/libcloud/pull/1181

[LIBCLOUD-985] Add coverage for newer GCE network and subnet options.

## [LIBCLOUD-985] Add coverage for newer GCE network and subnet options.

### Description

Addressing 
[LIBCLOUD-985](https://issues.apache.org/jira/browse/LIBCLOUD-985), PR adds the 
ability to handle a few newer GCE network and subnet options upon creation.
For networks, supports BGP routing mode
For subnetworks, supports secondary IP Ranges, Private IP access to GCP APIs

See 
[](https://cloud.google.com/compute/docs/reference/rest/v1/networks/insert) and 
[https://cloud.google.com/compute/docs/reference/rest/v1/subnetworks/insert](url)

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/maxlip/libcloud 
LIBCLOUD-985_More_Net_SubNet_Options

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1181.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1181


commit 497820988e1ee5e9abaac4aa5a8655698fa9330b
Author: Max 
Date:   2018-03-13T19:12:56Z

[LIBCLOUD-985] Add coverage for newer GCE network and subnet creation 
options.




> GCE - Support network routingmode and subnet secondary/internal access options
> --
>
> Key: LIBCLOUD-985
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-985
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
> Environment: N/A
>Reporter: Max L
>Priority: Minor
>
> As of 3/2018, Google Cloud APIs support a few more creation flags for 
> networks and subnetworks.
> Networks: BGP Routing mode regional/global
> Subnetworks: Secondary IP Ranges, Private IP access to GCP APIs.
> It would be good to add coverage for these.



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

[jira] [Commented] (LIBCLOUD-960) GCE update firewall rule coverage for egress/deny and service accounts

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376179#comment-16376179
 ] 

ASF GitHub Bot commented on LIBCLOUD-960:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1144


> GCE update firewall rule coverage for egress/deny and service accounts
> --
>
> Key: LIBCLOUD-960
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-960
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Max L
>Priority: Minor
>
> GCE support 4-way firewall rules (ingress/egress, allow/deny) and filtering 
> by service accounts, now. Let's update libcloud's coverage.



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

[jira] [Commented] (LIBCLOUD-965) /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16345502#comment-16345502
 ] 

ASF GitHub Bot commented on LIBCLOUD-965:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1145


> /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth
> 
>
> Key: LIBCLOUD-965
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-965
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Miguel Caballer
>Priority: Minor
>
> As stated here:
> https://developer.openstack.org/api-ref/identity/v3-ext/#list-projects-a-federated-user-can-access
> The path: /v3/OS-FEDERATION/projects has been deprecated in v1.1. Use core 
> GET /auth/projects. This call has the same response format.



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

[jira] [Commented] (LIBCLOUD-977) Implement DigitalOcean's rebuild and resize commands

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16342269#comment-16342269
 ] 

ASF GitHub Bot commented on LIBCLOUD-977:
-

Github user adamwight closed the pull request at:

https://github.com/apache/libcloud/pull/1169


> Implement DigitalOcean's rebuild and resize commands
> 
>
> Key: LIBCLOUD-977
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-977
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Compute
>Reporter: Adam Wight
>Priority: Minor
>  Labels: pull-request-available
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> I'd like to add "ex_" driver functions for DigitalOcean's rebuild and resize 
> APIs, because I've switched to using libcloud and these are part of my 
> workflow.



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

[jira] [Commented] (LIBCLOUD-977) Implement DigitalOcean's rebuild and resize commands

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341372#comment-16341372
 ] 

ASF GitHub Bot commented on LIBCLOUD-977:
-

GitHub user adamwight opened a pull request:

https://github.com/apache/libcloud/pull/1169

[LIBCLOUD-977] Adds rebuild and resize commands for DigitalOcean

Implement the following DigitalOcean APIs as driver-specific extensions,
* https://developers.digitalocean.com/documentation/v2/#rebuild-a-droplet
* https://developers.digitalocean.com/documentation/v2/#resize-a-droplet

Smoke tests locally.

## Changes Title (replace this with a logical title for your changes)

### Description

Replace this with the PR description (mention the changes you have made, why
you have made them, provide some background and any references to the 
provider
documentation if needed, etc.).

For more information on contributing, please see 
[Contributing](http://libcloud.readthedocs.org/en/latest/development.html#contributing)
section of our documentation.

### Status

Replace this: describe the PR status. Examples:

- work in progress
- done, ready for review

### Checklist (tick everything that applies)

- [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/adamwight/libcloud do_rebuild_resize

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1169.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1169


commit 64c485b20cc73d32cfcd19296734f521ce6b78d5
Author: Adam Wight 
Date:   2018-01-26T18:02:41Z

Adds rebuild and resize commands for DigitalOcean

Implement the following DigitalOcean APIs as driver-specific extensions,
* https://developers.digitalocean.com/documentation/v2/#rebuild-a-droplet
* https://developers.digitalocean.com/documentation/v2/#resize-a-droplet

Smoke tests locally.




> Implement DigitalOcean's rebuild and resize commands
> 
>
> Key: LIBCLOUD-977
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-977
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Compute
>Affects Versions: 0.15.1
>Reporter: Adam Wight
>Priority: Minor
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> I'd like to add "ex_" driver functions for DigitalOcean's rebuild and resize 
> APIs, because I've switched to using libcloud and these are part of my 
> workflow.



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

[jira] [Commented] (LIBCLOUD-879) GCE Load balancer suppose that all VM have public ip

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339140#comment-16339140
 ] 

ASF GitHub Bot commented on LIBCLOUD-879:
-

Github user charly37 closed the pull request at:

https://github.com/apache/libcloud/pull/952


> GCE Load balancer suppose that all VM have public ip
> 
>
> Key: LIBCLOUD-879
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-879
> Project: Libcloud
>  Issue Type: Bug
>  Components: LoadBalancer
> Environment: GCE MASTER
>Reporter: charles walker
>Priority: Minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When calling "list_members()" on a GCe load balancer libcloud object I end up 
> with the following stack :
> {noformat}
> Retrieve 2 Lbs. Here is the list : [ name=europe-lb-forwarding-rule, state=None, ip=10.77, 
> port=30012-30012>,  name=load-balancer-prd-comp-forwarding-rule-2, state=None, ip=1093, 
> port=30001-30001>]
> --Printing the node obj for DBG :  uuid=9001a5d9d425dc0e5dd1db5352296b08920bde21, name=tec--infra-2ktm, 
> state=RUNNING, public_ips=[], private_ips=['10.'], provider=Google 
> Compute Engine ...>
> Traceback (most recent call last):
>   File "LbTestPy.py", line 43, in 
> print ("Members: " +str(aLbs[0].list_members()))
>   File 
> "/home/cloud-user/LbTest/src/apache-libcloud/libcloud/loadbalancer/base.py", 
> line 110, in list_members
> return self.driver.balancer_list_members(balancer=self)
>   File 
> "/home/cloud-user/LbTest/src/apache-libcloud/libcloud/loadbalancer/drivers/gce.py",
>  line 274, in balancer_list_members
> balancer.extra['targetpool'].nodes]
>   File 
> "/home/cloud-user/LbTest/src/apache-libcloud/libcloud/loadbalancer/drivers/gce.py",
>  line 342, in _node_to_member
> member_ip = node.public_ips[0]
> IndexError: list index out of range
> {noformat}
> After some investigations it appears to comes from the method "def 
> _node_to_member(self, node, balancer):" in loadbalancer/drivers/gce.py. Mode 
> precisely this piece of the code :
> {code:title=code1.py|borderStyle=solid}
> if hasattr(node, 'name'):
>   member_id = node.name
>   member_ip = node.public_ips[0]
> else:
>   member_id = node
>   member_ip = None
> {code}
> which imply that all VM in the load balancer will have public IP. This is not 
> necessarly the case and thus when it happen the process crash (as you can see 
> in the previous stack where i added some debug log in my libcloud version to 
> print the node where the error occurs).
> I would had suggest to use private ip instead of public but I do not want to 
> impact the existing user of libcloud so I was thinking of a simple fix :
> {code:title=code1.py|borderStyle=solid}
> if hasattr(node, 'name'):
> member_id = node.name
> else:
> member_id = node
> if (len(node.public_ips) > 0):
> member_ip = node.public_ips[0]
> else:
> member_ip = None
> {code}



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

[jira] [Commented] (LIBCLOUD-975) Compute Cloudstack - Add change size and restore

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16338827#comment-16338827
 ] 

ASF GitHub Bot commented on LIBCLOUD-975:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1166


> Compute Cloudstack - Add change size and restore
> 
>
> Key: LIBCLOUD-975
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-975
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Affects Versions: 0.15.0
>Reporter: Mauro Murari
>Priority: Minor
>
> Add change size and restore to compute driver Cloudstack.
>  
> Change Size: 
> [https://cloudstack.apache.org/api/apidocs-4.10/apis/scaleVirtualMachine.html]
> Restore: 
> [https://cloudstack.apache.org/api/apidocs-4.10/apis/restoreVirtualMachine.html]
>  
>  



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

[jira] [Commented] (LIBCLOUD-975) Compute Cloudstack - Add change size and restore

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16336337#comment-16336337
 ] 

ASF GitHub Bot commented on LIBCLOUD-975:
-

GitHub user otherpirate opened a pull request:

https://github.com/apache/libcloud/pull/1166

LIBCLOUD-975 - Compute Cloudstack - Add change size and restore

## Compute Cloudstack - Add change size and restore

### Description

Add change size and restore method to Cloudstack compute driver.
Change Size: 
https://cloudstack.apache.org/api/apidocs-4.10/apis/scaleVirtualMachine.html
Restore: 
https://cloudstack.apache.org/api/apidocs-4.10/apis/restoreVirtualMachine.html

I added a logic in common.cloudstack.CloudStackConnection._sync_request to 
handle with old versions of cloudstack restore method.

### Status
- done, ready for review

### Checklist (tick everything that applies)

- [x] Flake8
- [x] Documentation
- [x] Tests
- [x] Real provider scenario tests


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/otherpirate/libcloud 
LIBCLOUD-975_change_size_and_restore

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1166.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1166


commit 7429490f05cf0f275ee385882b3e61bea4788a5f
Author: otherpirate 
Date:   2018-01-23T19:17:50Z

Add restore and resize/scale to Cloudstack compute driver




> Compute Cloudstack - Add change size and restore
> 
>
> Key: LIBCLOUD-975
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-975
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Affects Versions: 0.15.0
>Reporter: Mauro Murari
>Priority: Minor
>
> Add change size and restore to compute driver Cloudstack.
>  
> Change Size: 
> [https://cloudstack.apache.org/api/apidocs-4.10/apis/scaleVirtualMachine.html]
> Restore: 
> [https://cloudstack.apache.org/api/apidocs-4.10/apis/restoreVirtualMachine.html]
>  
>  



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

[jira] [Commented] (LIBCLOUD-973) ex_create_multiple_nodes API in gce.py compute driver does not handle boot disk size.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318323#comment-16318323
 ] 

ASF GitHub Bot commented on LIBCLOUD-973:
-

GitHub user Rahul-CSI opened a pull request:

https://github.com/apache/libcloud/pull/1162

[LIBCLOUD-973] Support disk_size parameter for boot disk when creating 
instance.

## Support specifying the disk size for boot disk when we create (one/more) 
google compute cloud instances.

### Description

This is fix for LIBCLOUD-973 bug.
Link to bug: https://issues.apache.org/jira/browse/LIBCLOUD-973
The ex_create_multiple_nodes API call in gce.py compute driver
does not handle boot disk size. Hence it creates a boot disk of size 10GB 
every time.
Added disk_size keyword parameter to ex_create_multiple_nodes API call,
It passes the parameter through internal method calls and adds the disk 
size to the POST request.

- API call sequence:
1. ex_create_multiple_nodes
2. _multi_create_node
3. _create_node_req
4. _create_instance_properties
5. _build_disk_gce_struct

### Status
- done, ready for review

### Checklist (tick everything that applies)

- [X] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [X] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cambridge-semantics/libcloud 
LIBCLOUD-973_Support_disk_size

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1162.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1162


commit 81b58ae68bafde1156e445e3985e729871cb2666
Author: Rahul Paigavan 
Date:   2018-01-09T11:49:49Z

[LIBCLOUD-973] Support disk_size parameter for boot disk while creating 
instances in ex_create_multiple_nodes API call.




> ex_create_multiple_nodes API in gce.py compute driver does not handle boot 
> disk size.
> -
>
> Key: LIBCLOUD-973
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-973
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Rahul Paigavan
>  Labels: compute, disk
>
> When we want to create multiple nodes with some specified boot disk size, 
> ex_create_multiple_nodes does not handle this case.
> By default it create a boot disk of 10 GB size.
> We would like to specify  (in GB) to ex_create_multiple_nodes API 
> call
> and it should create  boot disk for node.
> Issue is observed in latest Libcloud 2.2.1 version.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-809) GCE deploy_node function should accept all the same parameters as create_node

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315081#comment-16315081
 ] 

ASF GitHub Bot commented on LIBCLOUD-809:
-

GitHub user spyrdzy reopened a pull request:

https://github.com/apache/libcloud/pull/1155

Fixes Apache LIBCLOUD-809

## Changes 
Fixes Apache LIBCLOUD-809

### Description
Merged variables and docstrings for deploy_node to meet features added to 
create_node.

Reference link: https://issues.apache.org/jira/browse/LIBCLOUD-809

### Status
- done, ready for review

### Checklist (tick everything that applies)

- [X] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [X] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/spyrdzy/libcloud 809

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1155.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1155


commit ce3d727fd7661546e4cc49a9481f0f9cde432b16
Author: Alexander Spyrdz 
Date:   2017-12-15T05:35:24Z

deploy_node has variable parity with create_node.

commit 0e6bd6c61754bda04906e92b1c9b4bd26b2e5fa9
Author: Alexander Spyrdz 
Date:   2018-01-05T02:42:09Z

Merge branch 'trunk' into 809




> GCE deploy_node function should accept all the same parameters as create_node
> -
>
> Key: LIBCLOUD-809
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-809
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Joshua Buss
>
> I can't figure out if deploy_node has been built the way it has for some 
> reason, but in my use case I'd like to use deploy_node because I have a 
> script to run but I also want to set the preemptive flag and external IP, 
> which are available in create_node but not deploy_node for some reason.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-809) GCE deploy_node function should accept all the same parameters as create_node

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315080#comment-16315080
 ] 

ASF GitHub Bot commented on LIBCLOUD-809:
-

Github user spyrdzy closed the pull request at:

https://github.com/apache/libcloud/pull/1155


> GCE deploy_node function should accept all the same parameters as create_node
> -
>
> Key: LIBCLOUD-809
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-809
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Joshua Buss
>
> I can't figure out if deploy_node has been built the way it has for some 
> reason, but in my use case I'd like to use deploy_node because I have a 
> script to run but I also want to set the preemptive flag and external IP, 
> which are available in create_node but not deploy_node for some reason.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-809) GCE deploy_node function should accept all the same parameters as create_node

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312468#comment-16312468
 ] 

ASF GitHub Bot commented on LIBCLOUD-809:
-

GitHub user spyrdzy reopened a pull request:

https://github.com/apache/libcloud/pull/1155

Fixes Apache LIBCLOUD-809

## Changes 
Fixes Apache LIBCLOUD-809

### Description
Merged variables and docstrings for deploy_node to meet features added to 
create_node.

Reference link: https://issues.apache.org/jira/browse/LIBCLOUD-809

### Status
- done, ready for review

### Checklist (tick everything that applies)

- [X] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [X] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/spyrdzy/libcloud 809

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1155.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1155


commit ce3d727fd7661546e4cc49a9481f0f9cde432b16
Author: Alexander Spyrdz 
Date:   2017-12-15T05:35:24Z

deploy_node has variable parity with create_node.

commit 0e6bd6c61754bda04906e92b1c9b4bd26b2e5fa9
Author: Alexander Spyrdz 
Date:   2018-01-05T02:42:09Z

Merge branch 'trunk' into 809




> GCE deploy_node function should accept all the same parameters as create_node
> -
>
> Key: LIBCLOUD-809
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-809
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Joshua Buss
>
> I can't figure out if deploy_node has been built the way it has for some 
> reason, but in my use case I'd like to use deploy_node because I have a 
> script to run but I also want to set the preemptive flag and external IP, 
> which are available in create_node but not deploy_node for some reason.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-809) GCE deploy_node function should accept all the same parameters as create_node

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312467#comment-16312467
 ] 

ASF GitHub Bot commented on LIBCLOUD-809:
-

Github user spyrdzy closed the pull request at:

https://github.com/apache/libcloud/pull/1155


> GCE deploy_node function should accept all the same parameters as create_node
> -
>
> Key: LIBCLOUD-809
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-809
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Joshua Buss
>
> I can't figure out if deploy_node has been built the way it has for some 
> reason, but in my use case I'd like to use deploy_node because I have a 
> script to run but I also want to set the preemptive flag and external IP, 
> which are available in create_node but not deploy_node for some reason.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-971) wait_until_running error when empty ip addresses

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306282#comment-16306282
 ] 

ASF GitHub Bot commented on LIBCLOUD-971:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1156


> wait_until_running error when empty ip addresses
> 
>
> Key: LIBCLOUD-971
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-971
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Affects Versions: 0.13.3
>Reporter: Tobias Paepke
>Priority: Minor
>
> wait_until_running leads to an libcloud error if no valid ip address was 
> provided by list_nodes. This happens in our setup especially if the node is 
> running, but has no valid ip address assigned via dhcp.
> The function should retry to get a valid ip address until the timeout is 
> reached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-971) wait_until_running error when empty ip addresses

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16298462#comment-16298462
 ] 

ASF GitHub Bot commented on LIBCLOUD-971:
-

GitHub user paepke opened a pull request:

https://github.com/apache/libcloud/pull/1156

LIBCLOUD-971 - wait_until_running should only append addresses if the

## LIBCLOUD-971 

### Description

 LIBCLOUD-971 - wait_until_running should only append ip addresses if the 
list is not empty.

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [X] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [X] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paepke/libcloud LIBCLOUD-971

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1156.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1156


commit 933e3272a0db910bd97a55ce3d31c7cfbaa11347
Author: Tobias Paepke 
Date:   2017-12-20T13:04:19Z

LIBCLOUD-971 - wait_until_running should only append addresses if the
list is not empty.




> wait_until_running error when empty ip addresses
> 
>
> Key: LIBCLOUD-971
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-971
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Affects Versions: 0.13.3
>Reporter: Tobias Paepke
>Priority: Minor
>
> wait_until_running leads to an libcloud error if no valid ip address was 
> provided by list_nodes. This happens in our setup especially if the node is 
> running, but has no valid ip address assigned via dhcp.
> The function should retry to get a valid ip address until the timeout is 
> reached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-809) GCE deploy_node function should accept all the same parameters as create_node

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292066#comment-16292066
 ] 

ASF GitHub Bot commented on LIBCLOUD-809:
-

GitHub user spyrdzy opened a pull request:

https://github.com/apache/libcloud/pull/1155

Fixes Apache LIBCLOUD-809

## Changes 
Fixes Apache LIBCLOUD-809

### Description
Merged variables and docstrings for deploy_node to meet features added to 
create_node.

Reference link: https://issues.apache.org/jira/browse/LIBCLOUD-809

### Status
- done, ready for review

### Checklist (tick everything that applies)

- [X] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [X] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/spyrdzy/libcloud 809

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1155.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1155


commit 69d76ec9ea5da2abdf973f2540cea4c3a3688a53
Author: Alexander Spyrdz 
Date:   2017-12-15T05:35:24Z

deploy_node has variable parity with create_node.

commit addd61e56afdd8e7edb505813d6e353c2da49715
Author: Alexander Spyrdz 
Date:   2017-12-15T05:48:40Z

Docstring update

commit d00f90dee920517dfe84e975832e3002e696a6eb
Author: Alexander Spyrdz 
Date:   2017-12-15T05:50:55Z

Refix docstring




> GCE deploy_node function should accept all the same parameters as create_node
> -
>
> Key: LIBCLOUD-809
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-809
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Joshua Buss
>
> I can't figure out if deploy_node has been built the way it has for some 
> reason, but in my use case I'd like to use deploy_node because I have a 
> script to run but I also want to set the preemptive flag and external IP, 
> which are available in create_node but not deploy_node for some reason.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-969) Add pricing information to Upcloud driver list_sizes method

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291247#comment-16291247
 ] 

ASF GitHub Bot commented on LIBCLOUD-969:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1152


> Add pricing information to Upcloud driver list_sizes method
> ---
>
> Key: LIBCLOUD-969
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-969
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Mika Lackman
>
> Currently no pricing information is included in driver.list_sizes. Idea is to 
> add pricing information to NodeSize.extra field, because the price is 
> dependant on the hosting zone. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-969) Add pricing information to Upcloud driver list_sizes method

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285713#comment-16285713
 ] 

ASF GitHub Bot commented on LIBCLOUD-969:
-

GitHub user mlackman opened a pull request:

https://github.com/apache/libcloud/pull/1152

[LIBCLOUD-969] Add pricing information to UpCloud's driver list_sizes

## Changes Title (replace this with a logical title for your changes)

### Description

UpCloud's driver were missing the pricing information from list_sizes 
return values. Added the information to NodeSize.extra data, because pricing 
zone specific. 

### Status

Replace this: describe the PR status. Examples:

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [x] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/UpCloudLtd/libcloud 
LIBCLOUD-969_Add_pricing_information_to_Upcloud_driver_list_sizes_method

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1152.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1152


commit 39c2721ef04e1a9eab0161e744df263d4d09770a
Author: Mika Lackman 
Date:   2017-12-11T09:04:16Z

[LIBCLOUD-969] Add pricing information to UpCloud's driver list_sizes




> Add pricing information to Upcloud driver list_sizes method
> ---
>
> Key: LIBCLOUD-969
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-969
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Mika Lackman
>
> Currently no pricing information is included in driver.list_sizes. Idea is to 
> add pricing information to NodeSize.extra field, because the price is 
> dependant on the hosting zone. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-967) list_nodes() should include tags from DigitalOcean droplets

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279176#comment-16279176
 ] 

ASF GitHub Bot commented on LIBCLOUD-967:
-

GitHub user greendog99 opened a pull request:

https://github.com/apache/libcloud/pull/1149

[LIBCLOUD-967] Add support for DigitalOcean tags in list_nodes()

## Add support for DigitalOcean tags in list_nodes()

See: https://issues.apache.org/jira/browse/LIBCLOUD-967

### Description

Digital Ocean droplets can be tagged with multiple tags, such as 
"production" or "database", but these tags are not currently returned by 
{{list_nodes()}}.


https://www.digitalocean.com/community/tutorials/how-to-tag-digitalocean-droplets

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)

### Tests

Added tags to Digital Ocean fixtures and added test to confirm tags are 
captured by `list_nodes()`.

```
$ PYTHONPATH=. python3 libcloud/test/compute/test_digitalocean_v2.py
..libcloud/test/compute/test_digitalocean_v2.py:114: 
DeprecationWarning: Please use assertRaisesRegex instead.
  location=location)

--
Ran 34 tests in 0.217s

OK
```

DeprecationWarning in above test was pre-existing and unrelated to this 
change.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/greendog99/libcloud digitalocean_tags

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1149.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1149


commit 46ed6b19ac7f91dd9387f0c1600f75335a707f6d
Author: Mike Fischer 
Date:   2017-12-05T20:18:42Z

Add support for DigitalOcean tags in list_nodes()




> list_nodes() should include tags from DigitalOcean droplets
> ---
>
> Key: LIBCLOUD-967
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-967
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Michael Fischer
>Priority: Minor
>  Labels: compute, digitalocean
>
> Digital Ocean droplets can be tagged with multiple tags, such as "production" 
> or "database", but these tags are not currently returned by {{list_nodes()}}.
> I am about to submit a PR to implement this improvement. This ticket is being 
> opened to track any discussion around that PR.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-965) /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16278125#comment-16278125
 ] 

ASF GitHub Bot commented on LIBCLOUD-965:
-

GitHub user micafer reopened a pull request:

https://github.com/apache/libcloud/pull/1145

[LIBCLOUD-965] /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth

## [LIBCLOUD-965] /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC 
auth

### Description

As stated here:

https://developer.openstack.org/api-ref/identity/v3-ext/#list-projects-a-federated-user-can-access

The path: /v3/OS-FEDERATION/projects has been deprecated in v1.1. Use core 
GET /auth/projects. This call has the same response format.

Also added response.body as body of the MalformedResponseError to improve 
error messages in case of non expected response code.

### Status

- done, ready for review
Tests are failing due to extenal issues.

### Checklist (tick everything that applies)

- [X] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/micafer/libcloud trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1145.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1145


commit 814bc3e366bdce7f2b935eeb3c7ed21d562cf3e8
Author: micafer 
Date:   2017-06-20T06:21:37Z

Fix #LIBCLOUD-925

commit 7deee735c43b38e021153579d41193b49cbba1dd
Author: micafer 
Date:   2017-11-29T12:37:11Z

Merge remote-tracking branch 'upstream/trunk' into trunk

commit 00efcf2be242acfa8821dec7c2ec14537a5f9584
Author: micafer 
Date:   2017-11-29T12:51:18Z

Improve error message

commit e23be01804d4d435382fb2dc2b1bf68ad0f5e401
Author: micafer 
Date:   2017-11-30T08:56:02Z

Fix LIBCLOUD-965

commit 3dd6f4d5aec21f8d11e415fe4d95d2e316bb3dac
Author: micafer 
Date:   2017-11-30T09:59:31Z

Fix test




> /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth
> 
>
> Key: LIBCLOUD-965
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-965
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Miguel Caballer
>Priority: Minor
>
> As stated here:
> https://developer.openstack.org/api-ref/identity/v3-ext/#list-projects-a-federated-user-can-access
> The path: /v3/OS-FEDERATION/projects has been deprecated in v1.1. Use core 
> GET /auth/projects. This call has the same response format.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-965) /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16278124#comment-16278124
 ] 

ASF GitHub Bot commented on LIBCLOUD-965:
-

Github user micafer closed the pull request at:

https://github.com/apache/libcloud/pull/1145


> /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth
> 
>
> Key: LIBCLOUD-965
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-965
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Miguel Caballer
>Priority: Minor
>
> As stated here:
> https://developer.openstack.org/api-ref/identity/v3-ext/#list-projects-a-federated-user-can-access
> The path: /v3/OS-FEDERATION/projects has been deprecated in v1.1. Use core 
> GET /auth/projects. This call has the same response format.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-965) /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272568#comment-16272568
 ] 

ASF GitHub Bot commented on LIBCLOUD-965:
-

Github user micafer closed the pull request at:

https://github.com/apache/libcloud/pull/1145


> /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth
> 
>
> Key: LIBCLOUD-965
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-965
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Miguel Caballer
>Priority: Minor
>
> As stated here:
> https://developer.openstack.org/api-ref/identity/v3-ext/#list-projects-a-federated-user-can-access
> The path: /v3/OS-FEDERATION/projects has been deprecated in v1.1. Use core 
> GET /auth/projects. This call has the same response format.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-965) /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272569#comment-16272569
 ] 

ASF GitHub Bot commented on LIBCLOUD-965:
-

GitHub user micafer reopened a pull request:

https://github.com/apache/libcloud/pull/1145

[LIBCLOUD-965] /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth

## [LIBCLOUD-965] /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC 
auth

### Description

As stated here:

https://developer.openstack.org/api-ref/identity/v3-ext/#list-projects-a-federated-user-can-access

The path: /v3/OS-FEDERATION/projects has been deprecated in v1.1. Use core 
GET /auth/projects. This call has the same response format.

Also added response.body as body of the MalformedResponseError to improve 
error messages in case of non expected response code.

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [X] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/micafer/libcloud trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1145.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1145


commit 814bc3e366bdce7f2b935eeb3c7ed21d562cf3e8
Author: micafer 
Date:   2017-06-20T06:21:37Z

Fix #LIBCLOUD-925

commit 7deee735c43b38e021153579d41193b49cbba1dd
Author: micafer 
Date:   2017-11-29T12:37:11Z

Merge remote-tracking branch 'upstream/trunk' into trunk

commit 00efcf2be242acfa8821dec7c2ec14537a5f9584
Author: micafer 
Date:   2017-11-29T12:51:18Z

Improve error message

commit e23be01804d4d435382fb2dc2b1bf68ad0f5e401
Author: micafer 
Date:   2017-11-30T08:56:02Z

Fix LIBCLOUD-965

commit 3dd6f4d5aec21f8d11e415fe4d95d2e316bb3dac
Author: micafer 
Date:   2017-11-30T09:59:31Z

Fix test




> /v3/OS-FEDERATION/projects deprecated in OpenStack OIDC auth
> 
>
> Key: LIBCLOUD-965
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-965
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Miguel Caballer
>Priority: Minor
>
> As stated here:
> https://developer.openstack.org/api-ref/identity/v3-ext/#list-projects-a-federated-user-can-access
> The path: /v3/OS-FEDERATION/projects has been deprecated in v1.1. Use core 
> GET /auth/projects. This call has the same response format.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-960) GCE update firewall rule coverage for egress/deny and service accounts

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250011#comment-16250011
 ] 

ASF GitHub Bot commented on LIBCLOUD-960:
-

GitHub user maxlip opened a pull request:

https://github.com/apache/libcloud/pull/1144

LIBCLOUD-960: Expand GCE Firewall options coverage

## Expand GCE Firewall options coverage

### Description

Expanding coverage for full range of GCP firewall rule options currently in 
GA:
- Ingress or Egress direction
- Allow or Deny action
- Set Description and Priority values
- Define source and/or targets by service account

I've preserved the existing defaults.

Issue Link: https://issues.apache.org/jira/browse/LIBCLOUD-960

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/maxlip/libcloud 
LIBCLOUD-960_GCEFW-4Way-SvcAcct

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1144.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1144


commit cdf4a73045c0226757930a134d44afa024fba757
Author: Max 
Date:   2017-11-13T18:54:34Z

LIBCLOUD-960: Expand GCE Firewall options coverage




> GCE update firewall rule coverage for egress/deny and service accounts
> --
>
> Key: LIBCLOUD-960
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-960
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Max L
>Priority: Minor
>
> GCE support 4-way firewall rules (ingress/egress, allow/deny) and filtering 
> by service accounts, now. Let's update libcloud's coverage.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-961) GCE public projects list out of date

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250002#comment-16250002
 ] 

ASF GitHub Bot commented on LIBCLOUD-961:
-

GitHub user smarlowucf opened a pull request:

https://github.com/apache/libcloud/pull/1143

[LIBCLOUD-961] Update GCE public image projects list.

## Update GCE public image projects list

### Description

Add missing projects to list:
- cos-cloud
- suse-byos-cloud
- suse-sap-cloud
- windows-sql-cloud

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/smarlowucf/libcloud 
LIBCLOUD-961_image_projects

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1143.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1143


commit b0e87489d4280fca2afc827b8f53949047a7af7b
Author: Sean Marlow 
Date:   2017-11-13T18:54:21Z

[LIBCLOUD-961] Update GCE public image projects list.




> GCE public projects list out of date
> 
>
> Key: LIBCLOUD-961
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-961
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Sean Marlow
>Priority: Minor
>
> https://github.com/apache/libcloud/blob/trunk/libcloud/compute/drivers/gce.py#L1734
> Not available anymore according to GCE projects list: gce-nvme, 
> google-containers
> Missing cos-cloud, suse-sap-cloud, suse-byos-cloud and windows-sql-cloud.
> List found at https://cloud.google.com/compute/docs/images#os-compute-support



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-944) Add support for private IP addresses in GCE instance creation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226230#comment-16226230
 ] 

ASF GitHub Bot commented on LIBCLOUD-944:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1107


> Add support for private IP addresses in GCE instance creation
> -
>
> Key: LIBCLOUD-944
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-944
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Gareth McFarlane
>Priority: Minor
>
> GCE supports specifying a private IP address when deploying instances.  
> Currently only specifying the external IP of an instance is supported in 
> libcloud.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-955) Add support for DigitalOcean Spaces

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205474#comment-16205474
 ] 

ASF GitHub Bot commented on LIBCLOUD-955:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1129


> Add support for DigitalOcean Spaces
> ---
>
> Key: LIBCLOUD-955
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-955
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Storage
>Reporter: Andrew Starr-Bochicchio
>Priority: Minor
>
> DigitalOcean Spaces is an S3 compatible object storage service.
> https://developers.digitalocean.com/documentation/spaces/
> PR incoming.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-955) Add support for DigitalOcean Spaces

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204350#comment-16204350
 ] 

ASF GitHub Bot commented on LIBCLOUD-955:
-

GitHub user andrewsomething opened a pull request:

https://github.com/apache/libcloud/pull/1129

[LIBCLOUD-955] Add DigitalOcean Spaces support.

### Description

DigitalOcean Spaces is an S3 compatible object storage service. This adds 
support for it.

https://developers.digitalocean.com/documentation/spaces/

https://issues.apache.org/jira/browse/LIBCLOUD-955

### Status

- Docs still needed

### Checklist (tick everything that applies)

- [x ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/andrewsomething/libcloud 
LIBCLOUD-955_digitalocean-spaces

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1129.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1129


commit fb2f3addea3eb2078994687f6c3f3973592c3ba4
Author: Andrew Starr-Bochicchio 
Date:   2017-10-06T19:59:48Z

[LIBCLOUD-955] Add DigitalOcean Spaces support.




> Add support for DigitalOcean Spaces
> ---
>
> Key: LIBCLOUD-955
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-955
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Storage
>Reporter: Andrew Starr-Bochicchio
>Priority: Minor
>
> DigitalOcean Spaces is an S3 compatible object storage service.
> https://developers.digitalocean.com/documentation/spaces/
> PR incoming.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-954) EC2 driver don't support cn-north-1

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203058#comment-16203058
 ] 

ASF GitHub Bot commented on LIBCLOUD-954:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1127


> EC2 driver don't support cn-north-1
> ---
>
> Key: LIBCLOUD-954
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-954
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Duan Shiqiang
>
> From 2.1.0, the support of AWS EC2 for region cn-north-1. See this commit: 
> [Remove cn-north-1 from VALID_EC2_REGIONS list in EC2 compute 
> driver|https://github.com/apache/libcloud/commit/1e1d77f320a2314e96c79011ab62ee028a835503].
> I don't know why this is happening, please add the support back as we 
> actually have work load on AWS china region and has been using apache 
> libcloud for a while. Thx



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-954) EC2 driver don't support cn-north-1

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199898#comment-16199898
 ] 

ASF GitHub Bot commented on LIBCLOUD-954:
-

GitHub user pquentin opened a pull request:

https://github.com/apache/libcloud/pull/1127

[LIBCLOUD-954] ec2: Allow cn-north-1 even without pricing

## ec2: Allow cn-north-1 even without pricing

### Description

See https://issues.apache.org/jira/browse/LIBCLOUD-954 and 
https://github.com/apache/libcloud/commit/1e1d77f320a2314e96c79011ab62ee028a835503

@fjros and @duanshiqiang, what do you think?

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [x] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pquentin/libcloud allow-ec-cn-north-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1127.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1127


commit bd28b40cb960cd6cfc10595d018115265e1ee5a9
Author: Quentin Pradet 
Date:   2017-10-11T07:07:45Z

[LIBCLOUD-954] ec2: Allow cn-north-1 even without pricing




> EC2 driver don't support cn-north-1
> ---
>
> Key: LIBCLOUD-954
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-954
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Duan Shiqiang
>
> From 2.1.0, the support of AWS EC2 for region cn-north-1. See this commit: 
> [Remove cn-north-1 from VALID_EC2_REGIONS list in EC2 compute 
> driver|https://github.com/apache/libcloud/commit/1e1d77f320a2314e96c79011ab62ee028a835503].
> I don't know why this is happening, please add the support back as we 
> actually have work load on AWS china region and has been using apache 
> libcloud for a while. Thx



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-952) UpCloud driver does not set the storage size and storage tier

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16195025#comment-16195025
 ] 

ASF GitHub Bot commented on LIBCLOUD-952:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1124


> UpCloud driver does not set the storage size and storage tier
> -
>
> Key: LIBCLOUD-952
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-952
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Mika Lackman
>
> UpCloud's driver does not set the disk size nor the storage tier when node is 
> created from UpCloud's template



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-952) UpCloud driver does not set the storage size and storage tier

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16194938#comment-16194938
 ] 

ASF GitHub Bot commented on LIBCLOUD-952:
-

GitHub user mlackman opened a pull request:

https://github.com/apache/libcloud/pull/1124

[LIBCLOUD-952] Use disk size and storage tier also when creating node from 
template

## Add disk size and storage tier

### Description

Added missing storage_tier and disk size to the request body for creating 
node. Storage_tier has meaningful default value when not provided.  

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [x] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/UpCloudLtd/libcloud 
LIBCLOUD-952_UpCloud_driver_does_not_set_the_storage_size_and_storage_tier

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1124.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1124


commit e7e0869e7fbc174605f8d99172dd218685163d2a
Author: Mika Lackman 
Date:   2017-10-06T14:58:47Z

Use disk size and storage tier also when creating node from template




> UpCloud driver does not set the storage size and storage tier
> -
>
> Key: LIBCLOUD-952
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-952
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Mika Lackman
>
> UpCloud's driver does not set the disk size nor the storage tier when node is 
> created from UpCloud's template



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-951) Add possibility to define hostname to UpCloud driver

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16194154#comment-16194154
 ] 

ASF GitHub Bot commented on LIBCLOUD-951:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1123


> Add possibility to define hostname to UpCloud driver
> 
>
> Key: LIBCLOUD-951
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-951
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Mika Lackman
>
> Add way to define hostname



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-951) Add possibility to define hostname to UpCloud driver

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16194145#comment-16194145
 ] 

ASF GitHub Bot commented on LIBCLOUD-951:
-

GitHub user mlackman reopened a pull request:

https://github.com/apache/libcloud/pull/1123

[LIBCLOUD-951] Add possibility to define hostname to UpCloud driver

## UpCloud driver to support defining hostname

### Description

Added ex_hostname to UpcloudDriver create_node method to define the 
hostname.

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [x] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/UpCloudLtd/libcloud 
LIBCLOUD-951_Add_possibility_to_define_hostname_to_UpCloud_driver

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1123.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1123


commit ba34061871224ac210a1fcaa2d2d63b7ab74965e
Author: Mika Lackman 
Date:   2017-10-05T16:34:30Z

upcloud driver to take ex_hostname parameter for defining hostname




> Add possibility to define hostname to UpCloud driver
> 
>
> Key: LIBCLOUD-951
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-951
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Mika Lackman
>
> Add way to define hostname



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-951) Add possibility to define hostname to UpCloud driver

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16194144#comment-16194144
 ] 

ASF GitHub Bot commented on LIBCLOUD-951:
-

Github user mlackman closed the pull request at:

https://github.com/apache/libcloud/pull/1123


> Add possibility to define hostname to UpCloud driver
> 
>
> Key: LIBCLOUD-951
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-951
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Mika Lackman
>
> Add way to define hostname



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-951) Add possibility to define hostname to UpCloud driver

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16193203#comment-16193203
 ] 

ASF GitHub Bot commented on LIBCLOUD-951:
-

GitHub user mlackman opened a pull request:

https://github.com/apache/libcloud/pull/1123

[LIBCLOUD-951] Add possibility to define hostname to UpCloud driver

## UpCloud driver to support defining hostname

### Description

Added ex_hostname to UpcloudDriver create_node method to define the 
hostname.

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [x] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/UpCloudLtd/libcloud 
LIBCLOUD-951_Add_possibility_to_define_hostname_to_UpCloud_driver

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1123.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1123


commit ba34061871224ac210a1fcaa2d2d63b7ab74965e
Author: Mika Lackman 
Date:   2017-10-05T16:34:30Z

upcloud driver to take ex_hostname parameter for defining hostname




> Add possibility to define hostname to UpCloud driver
> 
>
> Key: LIBCLOUD-951
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-951
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Mika Lackman
>
> Add way to define hostname



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-926) [BUG Azure_ARM] in ex_create_public_ip function among other

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181966#comment-16181966
 ] 

ASF GitHub Bot commented on LIBCLOUD-926:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1098


> [BUG Azure_ARM] in ex_create_public_ip function among other
> ---
>
> Key: LIBCLOUD-926
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-926
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Cristina Guerra
>  Labels: azurecompute-arm, compute
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the file libcloud/compute/drivers/azure_arm.py.
> There are some functions as ex_create_public_ip function that it needs a 
> location parameter, when this parameter is send, a error happen:  "Location 
> is required".
> Looking at the code I found with the following:
> {code:python}
>if location is None and self.default_location:
> location = self.default_location
> else:
> raise ValueError("location is required.")
> {code}
> This does not evaluate a possible parameter, only if the value is None.
> I propose:
> {code:python}
> if location is None and self.default_location:
> location = self.default_location
> elif location is not None:
> location = location
> else:
> raise ValueError("location is required.")
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-938) Upcloud compute driver

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181920#comment-16181920
 ] 

ASF GitHub Bot commented on LIBCLOUD-938:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1102


> Upcloud compute driver
> --
>
> Key: LIBCLOUD-938
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-938
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Compute
>Reporter: Mika Lackman
>Priority: Minor
>
> Upcloud compute driver. Will be done against Upcloud's 1.2.4 api version 
> Upcloud's api documentation can be found from:
> https://www.upcloud.com/api/1.2.4/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-934) Add support for GCE instance labels

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178506#comment-16178506
 ] 

ASF GitHub Bot commented on LIBCLOUD-934:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1115


> Add support for GCE instance labels
> ---
>
> Key: LIBCLOUD-934
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-934
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Affects Versions: 0.2.0
> Environment: Ubuntu 17.04
>Reporter: Hrish
>
> Output of pip freeze | grep libcloud
> apache-libcloud==2.0.0
> The version is actually 2.0.0 but I cannot see it in the dropdown.
> There is no support for fetching the labels for GCE instances - 
> [https://cloud.google.com/compute/docs/labeling-resources]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-934) Add support for GCE instance labels

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173838#comment-16173838
 ] 

ASF GitHub Bot commented on LIBCLOUD-934:
-

GitHub user maxlip opened a pull request:

https://github.com/apache/libcloud/pull/1115

[LIBCLOUD-934] Adding support for GCE node labels.

## Changes Title [LIBCLOUD-934] Adding support for GCE node labels.

### Description

Added the ability to set [resource 
labels](https://cloud.google.com/compute/docs/reference/latest/instances/setLabels
) for GCE VMs. This can be done on node/multinode creation or via new 
ex_set_node_labels method.

There a few relevant JIRAs, such as 
https://issues.apache.org/jira/browse/LIBCLOUD-934

For more information on contributing, please see 
[Contributing](http://libcloud.readthedocs.org/en/latest/development.html#contributing)
section of our documentation.

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [ x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [x ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/maxlip/libcloud LIBCLOUD-934_gce-node-labels

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1115.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1115


commit 76848e98927d3261b03d8dcba3d1dfd8a2cab9d0
Author: maxlip 
Date:   2017-09-20T21:09:18Z

[LIBCLOUD-934] Adding support for GCE node labels.




> Add support for GCE instance labels
> ---
>
> Key: LIBCLOUD-934
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-934
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Affects Versions: 0.2.0
> Environment: Ubuntu 17.04
>Reporter: Hrish
>
> Output of pip freeze | grep libcloud
> apache-libcloud==2.0.0
> The version is actually 2.0.0 but I cannot see it in the dropdown.
> There is no support for fetching the labels for GCE instances - 
> [https://cloud.google.com/compute/docs/labeling-resources]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-946) Can't install apache-libcloud (file name too long)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172290#comment-16172290
 ] 

ASF GitHub Bot commented on LIBCLOUD-946:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1112


> Can't install apache-libcloud (file name too long)
> --
>
> Key: LIBCLOUD-946
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-946
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Cyrille Verrier
>Assignee: Tomaz Muraus
>
> h2. Environment
> OS: Ubuntu
> Python version: 3
> h2. Steps to reproduce
> {code}
> ➜  ~ $ mkdir test-apache-libcloud
> ➜  ~ $ cd test-apache-libcloud 
> ➜  test-apache-libcloud $ virtualenv .venvs
> ➜  test-apache-libcloud $ source .venvs/bin/activate 
> (.venvs) ➜  test-apache-libcloud $ pip install apache-libcloud==2.2.0
> {code}
> h2. Expected result
> libcloud is installed correctly
> h2. Actual result
> {code}
> Collecting apache-libcloud
>   Using cached apache_libcloud-2.2.0-py2.py3-none-any.whl
> Collecting requests (from apache-libcloud)
>   Using cached requests-2.18.4-py2.py3-none-any.whl
> Collecting urllib3<1.23,>=1.21.1 (from requests->apache-libcloud)
>   Using cached urllib3-1.22-py2.py3-none-any.whl
> Collecting idna<2.7,>=2.5 (from requests->apache-libcloud)
>   Using cached idna-2.6-py2.py3-none-any.whl
> Collecting chardet<3.1.0,>=3.0.2 (from requests->apache-libcloud)
>   Using cached chardet-3.0.4-py2.py3-none-any.whl
> Collecting certifi>=2017.4.17 (from requests->apache-libcloud)
>   Using cached certifi-2017.7.27.1-py2.py3-none-any.whl
> Installing collected packages: urllib3, idna, chardet, certifi, requests, 
> apache-libcloud
> Exception:
> Traceback (most recent call last):
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/basecommand.py",
>  line 215, in main
> status = self.run(options, args)
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/commands/install.py",
>  line 342, in run
> prefix=options.prefix_path,
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/req/req_set.py",
>  line 784, in install
> **kwargs
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/req/req_install.py",
>  line 851, in install
> self.move_wheel_files(self.source_dir, root=root, prefix=prefix)
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/req/req_install.py",
>  line 1064, in move_wheel_files
> isolated=self.isolated,
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/wheel.py",
>  line 345, in move_wheel_files
> clobber(source, lib_dir, True)
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/wheel.py",
>  line 323, in clobber
> shutil.copyfile(srcfile, destfile)
>   File "/usr/lib/python2.7/shutil.py", line 83, in copyfile
> with open(dst, 'wb') as fdst:
> IOError: [Errno 36] File name too long: 
> '/home/cyrille/test-apache-libcloud/.venvs/lib/python2.7/site-packages/libcloud/test/compute/fixtures/azure_arm/_subscriptions______resourceGroups_00_providers_Microsoft_Compute_virtualMachines_test_node_1_InstanceView.json'
> {code}
> Test files with long names added by commit:
> https://git-wip-us.apache.org/repos/asf?p=libcloud.git;a=commit;h=4bd4af926e42f255296b0611dd7215a607633b91
> h2. Remark
> Version *2.1.0* works fine
> {code}
> (.venvs) ➜  test-apache-libcloud pip install apache-libcloud==2.1.0
> Collecting apache-libcloud==2.1.0
>   Using cached apache_libcloud-2.1.0-py2.py3-none-any.whl
> Requirement already satisfied: requests in 
> ./.venvs/lib/python2.7/site-packages (from apache-libcloud==2.1.0)
> Requirement already satisfied: urllib3<1.23,>=1.21.1 in 
> ./.venvs/lib/python2.7/site-packages (from requests->apache-libcloud==2.1.0)
> Requirement already satisfied: idna<2.7,>=2.5 in 
> ./.venvs/lib/python2.7/site-packages (from requests->apache-libcloud==2.1.0)
> Requirement already satisfied: chardet<3.1.0,>=3.0.2 in 
> ./.venvs/lib/python2.7/site-packages (from requests->apache-libcloud==2.1.0)
> Requirement already satisfied: certifi>=2017.4.17 in 
> ./.venvs/lib/python2.7/site-packages (from requests->apache-libcloud==2.1.0)
> Installing collected packages: apache-libcloud
> Successfully installed apache-libcloud-2.1.0
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-945) testsuite fails on i686

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172182#comment-16172182
 ] 

ASF GitHub Bot commented on LIBCLOUD-945:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/


> testsuite fails on i686
> ---
>
> Key: LIBCLOUD-945
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-945
> Project: Libcloud
>  Issue Type: Bug
> Environment: build of python-apache-libcloud 2.2.0 on archlinux with 
> python3 on intel 32 bit
>Reporter: Erich Eckner
>Assignee: Tomaz Muraus
>  Labels: build
>
> There are several failures during test, because of type mismatches
> === FAILURES 
> ===
>  AzureBlobsTests.test_upload_object_invalid_md5 
> 
> self =  testMethod=test_upload_object_invalid_md5>
> def test_upload_object_invalid_md5(self):
> # Invalid md5 is returned by azure
> self.mock_response_klass.type = 'INVALID_HASH'
> 
> container = Container(name='foo_bar_container', extra={},
>   driver=self.driver)
> object_name = 'foo_test_upload'
> file_path = os.path.abspath(__file__)
> try:
> self.driver.upload_object(file_path=file_path, 
> container=container,
>   object_name=object_name,
> > verify_hash=True)
> libcloud/test/storage/test_azure_blobs.py:640: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> libcloud/storage/drivers/azure_blobs.py:771: in upload_object
> use_lease=ex_use_lease)
> libcloud/storage/drivers/azure_blobs.py:895: in _put_object
> stream=stream)
> libcloud/storage/base.py:627: in _upload_object
> headers=headers, raw=True)
> libcloud/common/base.py:590: in request
> stream=stream)
> libcloud/test/__init__.py:163: in prepared_request
> raw=raw, stream=stream)
> libcloud/http.py:227: in prepared_request
> prepped = self.session.prepare_request(req)
> /usr/lib/python2.7/site-packages/requests/sessions.py:437: in prepare_request
> hooks=merge_hooks(request.hooks, self.hooks),
> /usr/lib/python2.7/site-packages/requests/models.py:306: in prepare
> self.prepare_headers(headers)
> /usr/lib/python2.7/site-packages/requests/models.py:440: in prepare_headers
> check_header_validity(header)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> header = ('Content-Length', 37589L)
> def check_header_validity(header):
> """Verifies that header value is a string which doesn't contain
> leading whitespace or return characters. This prevents unintended
> header injection.
> 
> :param header: tuple, in the format (name, value).
> """
> name, value = header
> 
> if isinstance(value, bytes):
> pat = _CLEAN_HEADER_REGEX_BYTE
> else:
> pat = _CLEAN_HEADER_REGEX_STR
> try:
> if not pat.match(value):
> raise InvalidHeader("Invalid return character or leading 
> space in header: %s" % name)
> except TypeError:
> raise InvalidHeader("Value for header {%s: %s} must be of type 
> str or "
> >   "bytes, not %s" % (name, value, type(value)))
> E   InvalidHeader: Value for header {Content-Length: 37589} must be 
> of type str or bytes, not 
> /usr/lib/python2.7/site-packages/requests/utils.py:872: InvalidHeader
> ___ AzureBlobsTests.test_upload_page_object_success 
> 
> self =  testMethod=test_upload_page_object_success>
> def test_upload_page_object_success(self):
> self.mock_response_klass.use_param = None
> file_path = tempfile.mktemp(suffix='.jpg')
> file_size = AZURE_PAGE_CHUNK_SIZE * 4
> 
> with open(file_path, 'w') as file_hdl:
> file_hdl.write('0' * file_size)
> 
> container = Container(name='foo_bar_container', extra={},
>   driver=self.driver)
> object_name = 'foo_test_upload'
> extra = {'meta_data': {'some-value': 'foobar'}}
> obj = self.driver.upload_object(file_path=file_path,
> container=container,
> object_name=object_name,
> extra=extra,
> verify_hash=False,
> >   ex_blob_type='PageBlob')
> libcloud/test/storage/test_azure_blobs.py:707: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 

[jira] [Commented] (LIBCLOUD-946) Can't install apache-libcloud (file name too long)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171972#comment-16171972
 ] 

ASF GitHub Bot commented on LIBCLOUD-946:
-

GitHub user Kami opened a pull request:

https://github.com/apache/libcloud/pull/1112

[WIP] Make sure we don't have any files with names longer than 143 
characters

It looks like 2.2.0 broke installation on some systems, because we now ship 
files with names longer than 143 characters.

Most modern operating systems and file systems support file names with 
lengths up to 255 characters, but it looks like using an encrypted file system 
(layering ecryptfs on top of ext3/4) drops this limit to 143 characters.

This pull request fixes that and add a CI check which will catch issues 
like that in the future.

Resolves https://issues.apache.org/jira/browse/LIBCLOUD-946.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Kami/libcloud use_shorter_fixture_file_names

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1112.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1112


commit 60701af4e610b9eeb4e3c60034300148933d69ba
Author: Tomaz Muraus 
Date:   2017-09-19T16:00:09Z

Add a tox check which verifies we don't have any file which name is
longer than 143 characters.

143 characters seems to be the limit for ecryptfs file system layered on
top of ext4.

Source: 
https://askubuntu.com/questions/361976/find-files-with-a-minimum-filename-length

Part of LIBCLOUD-946.

commit 942255a6998c37d73cffba8ad90516b34f520c19
Author: Tomaz Muraus 
Date:   2017-09-19T16:14:44Z

Run checks step on Travis CI.




> Can't install apache-libcloud (file name too long)
> --
>
> Key: LIBCLOUD-946
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-946
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Cyrille Verrier
>Assignee: Tomaz Muraus
>
> h2. Environment
> OS: Ubuntu
> Python version: 3
> h2. Steps to reproduce
> {code}
> ➜  ~ $ mkdir test-apache-libcloud
> ➜  ~ $ cd test-apache-libcloud 
> ➜  test-apache-libcloud $ virtualenv .venvs
> ➜  test-apache-libcloud $ source .venvs/bin/activate 
> (.venvs) ➜  test-apache-libcloud $ pip install apache-libcloud==2.2.0
> {code}
> h2. Expected result
> libcloud is installed correctly
> h2. Actual result
> {code}
> Collecting apache-libcloud
>   Using cached apache_libcloud-2.2.0-py2.py3-none-any.whl
> Collecting requests (from apache-libcloud)
>   Using cached requests-2.18.4-py2.py3-none-any.whl
> Collecting urllib3<1.23,>=1.21.1 (from requests->apache-libcloud)
>   Using cached urllib3-1.22-py2.py3-none-any.whl
> Collecting idna<2.7,>=2.5 (from requests->apache-libcloud)
>   Using cached idna-2.6-py2.py3-none-any.whl
> Collecting chardet<3.1.0,>=3.0.2 (from requests->apache-libcloud)
>   Using cached chardet-3.0.4-py2.py3-none-any.whl
> Collecting certifi>=2017.4.17 (from requests->apache-libcloud)
>   Using cached certifi-2017.7.27.1-py2.py3-none-any.whl
> Installing collected packages: urllib3, idna, chardet, certifi, requests, 
> apache-libcloud
> Exception:
> Traceback (most recent call last):
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/basecommand.py",
>  line 215, in main
> status = self.run(options, args)
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/commands/install.py",
>  line 342, in run
> prefix=options.prefix_path,
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/req/req_set.py",
>  line 784, in install
> **kwargs
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/req/req_install.py",
>  line 851, in install
> self.move_wheel_files(self.source_dir, root=root, prefix=prefix)
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/req/req_install.py",
>  line 1064, in move_wheel_files
> isolated=self.isolated,
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/wheel.py",
>  line 345, in move_wheel_files
> clobber(source, lib_dir, True)
>   File 
> "/home/cyrille/test-apache-libcloud/.venvs/local/lib/python2.7/site-packages/pip/wheel.py",
>  line 323, in clobber
> shutil.copyfile(srcfile, destfile)
>   File "/usr/lib/python2.7/shutil.py", line 83, in copyfile
> with open(dst, 'wb') as fdst:
> IOError: [Errno 36] File name too long: 
> 

[jira] [Commented] (LIBCLOUD-945) testsuite fails on i686

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171931#comment-16171931
 ] 

ASF GitHub Bot commented on LIBCLOUD-945:
-

GitHub user Kami opened a pull request:

https://github.com/apache/libcloud/pull/

[Common] Make sure we normalize header types for test mock connection class

This pull request fixes the issue reported in 
https://issues.apache.org/jira/browse/LIBCLOUD-945.

We normalized header types inside the actual Connection class, but not 
inside the Connection class used by the tests. That's why some of the tests 
failed with newer version of `requests` which doesn't automatically cast header 
values to strings anymore.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Kami/libcloud make_sure_hader_value_is_string

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #


commit 7953b24e5126a193b1a5925ee7fa52c7cf0a3a3d
Author: Tomaz Muraus 
Date:   2017-09-19T15:27:27Z

Fix Azure blobs driver, make sure Content-Length header value is a
string and not a number.

Part of LIBCLOUD-945

commit 6e19a63847a6a554aef9078c7efce60c175ad32e
Author: Tomaz Muraus 
Date:   2017-09-19T15:28:08Z

Add test cases for it.

Part of LIBCLOUD-745.




> testsuite fails on i686
> ---
>
> Key: LIBCLOUD-945
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-945
> Project: Libcloud
>  Issue Type: Bug
> Environment: build of python-apache-libcloud 2.2.0 on archlinux with 
> python3 on intel 32 bit
>Reporter: Erich Eckner
>Assignee: Tomaz Muraus
>  Labels: build
>
> There are several failures during test, because of type mismatches
> === FAILURES 
> ===
>  AzureBlobsTests.test_upload_object_invalid_md5 
> 
> self =  testMethod=test_upload_object_invalid_md5>
> def test_upload_object_invalid_md5(self):
> # Invalid md5 is returned by azure
> self.mock_response_klass.type = 'INVALID_HASH'
> 
> container = Container(name='foo_bar_container', extra={},
>   driver=self.driver)
> object_name = 'foo_test_upload'
> file_path = os.path.abspath(__file__)
> try:
> self.driver.upload_object(file_path=file_path, 
> container=container,
>   object_name=object_name,
> > verify_hash=True)
> libcloud/test/storage/test_azure_blobs.py:640: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> libcloud/storage/drivers/azure_blobs.py:771: in upload_object
> use_lease=ex_use_lease)
> libcloud/storage/drivers/azure_blobs.py:895: in _put_object
> stream=stream)
> libcloud/storage/base.py:627: in _upload_object
> headers=headers, raw=True)
> libcloud/common/base.py:590: in request
> stream=stream)
> libcloud/test/__init__.py:163: in prepared_request
> raw=raw, stream=stream)
> libcloud/http.py:227: in prepared_request
> prepped = self.session.prepare_request(req)
> /usr/lib/python2.7/site-packages/requests/sessions.py:437: in prepare_request
> hooks=merge_hooks(request.hooks, self.hooks),
> /usr/lib/python2.7/site-packages/requests/models.py:306: in prepare
> self.prepare_headers(headers)
> /usr/lib/python2.7/site-packages/requests/models.py:440: in prepare_headers
> check_header_validity(header)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> header = ('Content-Length', 37589L)
> def check_header_validity(header):
> """Verifies that header value is a string which doesn't contain
> leading whitespace or return characters. This prevents unintended
> header injection.
> 
> :param header: tuple, in the format (name, value).
> """
> name, value = header
> 
> if isinstance(value, bytes):
> pat = _CLEAN_HEADER_REGEX_BYTE
> else:
> pat = _CLEAN_HEADER_REGEX_STR
> try:
> if not pat.match(value):
> raise InvalidHeader("Invalid return character or leading 
> space in header: %s" % name)
> except TypeError:
> raise InvalidHeader("Value for header {%s: %s} must be of type 
> str or "
> >   "bytes, not %s" % (name, value, type(value)))
> E   InvalidHeader: Value for header {Content-Length: 37589} must be 
> 

[jira] [Commented] (LIBCLOUD-944) Add support for private IP addresses in GCE instance creation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157877#comment-16157877
 ] 

ASF GitHub Bot commented on LIBCLOUD-944:
-

GitHub user vongazman opened a pull request:

https://github.com/apache/libcloud/pull/1107

[LIBCLOUD-944] Add support for private IP addresses in GCE instance creation

## Add support for private IP addresses in GCE instance creatio

### Description

GCE driver doesn't currently allow private IPs to be specified when 
creating instances. Updated gce.py driver to allow the optional parameter 
internal_ip which can be used when creating GCE instances.  

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vongazman/libcloud LIBCLOUD-944_private_ip

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1107.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1107


commit 27d79ea671b1d502930719d00cacbd8337be3a8b
Author: Gareth Mcfarlane 
Date:   2017-09-07T10:53:08Z

Add private IP functionality to GCE




> Add support for private IP addresses in GCE instance creation
> -
>
> Key: LIBCLOUD-944
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-944
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Gareth McFarlane
>Priority: Minor
>
> GCE supports specifying a private IP address when deploying instances.  
> Currently only specifying the external IP of an instance is supported in 
> libcloud.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-943) Azure ARM driver's ex_create_network_interface method is missing the option to create a static IP address

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155277#comment-16155277
 ] 

ASF GitHub Bot commented on LIBCLOUD-943:
-

GitHub user aki-k opened a pull request:

https://github.com/apache/libcloud/pull/1104

[LIBCLOUD-943] Add the option to Azure ARM ex_create_network_interfac…

### [LIBCLOUD-943] Add the option to Azure ARM ex_create_network_interface 
to create a static IP address

### Description

https://issues.apache.org/jira/browse/LIBCLOUD-943

Azure ARM driver's ex_create_network_interface is missing the option to 
create
a static IP address. "privateIPAllocationMethod" is set to "Dynamic" in the 
"data" 
dictionary. This change adds the option to create the network interface 
with a 
static IP address.

The value for the static IP address is defined with 
private_ip_address="n.n.n.n" in the 
ex_create_network_interface call.

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [x] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [x] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/aki-k/libcloud 
LIBCLOUD-943-ex_create_network_interface-private_ip_allocation_method-static

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1104.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1104


commit 2f22dbea6f36eef4e2608a731446d7854a4ca197
Author: Aki Ketolainen 
Date:   2017-09-06T12:04:05Z

[LIBCLOUD-943] Add the option to Azure ARM ex_create_network_interface to 
create a static IP address




> Azure ARM driver's ex_create_network_interface method is missing the option 
> to create a static IP address
> -
>
> Key: LIBCLOUD-943
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-943
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
> Environment: Python 3.5.2
>Reporter: Aki Ketolainen
>Priority: Trivial
>
> "privateIPAllocationMethod" is set to "Dynamic" in the "data" dictionary. 
> This associates a dynamic IP address from the Azure virtual network subnet 
> for the created network interface.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-926) [BUG Azure_ARM] in ex_create_public_ip function among other

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153769#comment-16153769
 ] 

ASF GitHub Bot commented on LIBCLOUD-926:
-

Github user SElsharkawy closed the pull request at:

https://github.com/apache/libcloud/pull/1051


> [BUG Azure_ARM] in ex_create_public_ip function among other
> ---
>
> Key: LIBCLOUD-926
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-926
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Cristina Guerra
>  Labels: azurecompute-arm, compute
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the file libcloud/compute/drivers/azure_arm.py.
> There are some functions as ex_create_public_ip function that it needs a 
> location parameter, when this parameter is send, a error happen:  "Location 
> is required".
> Looking at the code I found with the following:
> {code:python}
>if location is None and self.default_location:
> location = self.default_location
> else:
> raise ValueError("location is required.")
> {code}
> This does not evaluate a possible parameter, only if the value is None.
> I propose:
> {code:python}
> if location is None and self.default_location:
> location = self.default_location
> elif location is not None:
> location = location
> else:
> raise ValueError("location is required.")
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-926) [BUG Azure_ARM] in ex_create_public_ip function among other

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153770#comment-16153770
 ] 

ASF GitHub Bot commented on LIBCLOUD-926:
-

GitHub user SElsharkawy reopened a pull request:

https://github.com/apache/libcloud/pull/1098

LIBCLOUD-926 - Propagated changes to azure_arm.py from pull 1051

## Changes Title (Update: LIBCLOUD-926 - [BUG Azure_ARM] in 
ex_create_public_ip function among other)

### Description

This suggested update fixes the condition that checks for parameter 
"location" being None. If the parameter is not None, the original code would 
still exit and raise ValueError exception.

In the file libcloud/compute/drivers/azure_arm.py.
There are some functions as ex_create_public_ip function that it needs a 
location parameter, when this parameter is send, a error happen: "Location is 
required".
Looking at the code I found with the following:

   if location is None and self.default_location:
location = self.default_location
else:
raise ValueError("location is required.")
This does not evaluate a possible parameter, only if the value is None.

I suggested the following change:

if location is None:
if self.default_location:
location = self.default_location
else:
raise ValueError("location is required.")
The affected methods are:

   ex_create_network_security_group
   ex_delete_network_security_group
   ex_create_public_ip
The same code has been used in several other places.

### Status

done, ready for review

### Checklist (tick everything that applies)

- [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/SElsharkawy/libcloud LIBCLOUD-926_pull-1051

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1098.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1098


commit adadaf53882d6e15500079debc7344e5e2d28049
Author: Elsharkawy, Sameh 
Date:   2017-08-29T18:18:19Z

Propagated changes to azure_arm.py from pull 1051




> [BUG Azure_ARM] in ex_create_public_ip function among other
> ---
>
> Key: LIBCLOUD-926
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-926
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Cristina Guerra
>  Labels: azurecompute-arm, compute
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the file libcloud/compute/drivers/azure_arm.py.
> There are some functions as ex_create_public_ip function that it needs a 
> location parameter, when this parameter is send, a error happen:  "Location 
> is required".
> Looking at the code I found with the following:
> {code:python}
>if location is None and self.default_location:
> location = self.default_location
> else:
> raise ValueError("location is required.")
> {code}
> This does not evaluate a possible parameter, only if the value is None.
> I propose:
> {code:python}
> if location is None and self.default_location:
> location = self.default_location
> elif location is not None:
> location = location
> else:
> raise ValueError("location is required.")
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-926) [BUG Azure_ARM] in ex_create_public_ip function among other

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153752#comment-16153752
 ] 

ASF GitHub Bot commented on LIBCLOUD-926:
-

Github user SElsharkawy closed the pull request at:

https://github.com/apache/libcloud/pull/1098


> [BUG Azure_ARM] in ex_create_public_ip function among other
> ---
>
> Key: LIBCLOUD-926
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-926
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Cristina Guerra
>  Labels: azurecompute-arm, compute
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the file libcloud/compute/drivers/azure_arm.py.
> There are some functions as ex_create_public_ip function that it needs a 
> location parameter, when this parameter is send, a error happen:  "Location 
> is required".
> Looking at the code I found with the following:
> {code:python}
>if location is None and self.default_location:
> location = self.default_location
> else:
> raise ValueError("location is required.")
> {code}
> This does not evaluate a possible parameter, only if the value is None.
> I propose:
> {code:python}
> if location is None and self.default_location:
> location = self.default_location
> elif location is not None:
> location = location
> else:
> raise ValueError("location is required.")
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-940) Add 'end' to ec2 Reserved Instance data

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152000#comment-16152000
 ] 

ASF GitHub Bot commented on LIBCLOUD-940:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1099


> Add 'end' to ec2 Reserved Instance data
> ---
>
> Key: LIBCLOUD-940
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-940
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Chris Clarke
>
> The [DescribeReservedInstances 
> API|http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeReservedInstances.html]
>  returns 3 fields related to the timeframe of the reservation:
>   * start
>   * end
>   * duration
> When a reservation is modified, start changes to the effective date of the 
> modification, but duration remains the same (number of seconds in 1 or 3 
> years). The only way to determine when a modified reservation expires is to 
> use the end date.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-930) EC2 create_node should supply tag data to RunInstances rather than tagging separately

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150415#comment-16150415
 ] 

ASF GitHub Bot commented on LIBCLOUD-930:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1100


> EC2 create_node should supply tag data to RunInstances rather than tagging 
> separately
> -
>
> Key: LIBCLOUD-930
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-930
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Tom Morris
>
> While LIBCLOUD-690 is a real bug, it'd be moot if things were done correctly 
> with the tagging metadata being provided to the AWS RunInstances call where 
> it could be applied atomically with the creation of the node. The current 
> style of doing it in two separate calls allows for a window where nodes can 
> get created without their associated tags, making accounting for them much 
> more difficult.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-930) EC2 create_node should supply tag data to RunInstances rather than tagging separately

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148028#comment-16148028
 ] 

ASF GitHub Bot commented on LIBCLOUD-930:
-

GitHub user ldipenti opened a pull request:

https://github.com/apache/libcloud/pull/1100

Use TagSpecification parameter on EC2 create_node

## Take advantage of AWS EC2 tag-on-create feature

### Description

This small patch changes the way EC2 compute nodes are tagged when created, 
by adding the tags on the creation call instead of doing it immediately after. 
This avoids eventual consistency issues that sometimes happen when an instance 
isn't created yet so it can't be tagged.

For reference, the AWS docs are here: 
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RunInstances.html

This PR would tackle a colleague of mine has reported some weeks ago:
https://issues.apache.org/jira/browse/LIBCLOUD-930

### Status

- done, ready for review

### Checklist (tick everything that applies)

- [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [X] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes) (I've just submitted it.)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/curoverse/libcloud apache-libcloud-2.2.0.dev1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1100.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1100






> EC2 create_node should supply tag data to RunInstances rather than tagging 
> separately
> -
>
> Key: LIBCLOUD-930
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-930
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Tom Morris
>
> While LIBCLOUD-690 is a real bug, it'd be moot if things were done correctly 
> with the tagging metadata being provided to the AWS RunInstances call where 
> it could be applied atomically with the creation of the node. The current 
> style of doing it in two separate calls allows for a window where nodes can 
> get created without their associated tags, making accounting for them much 
> more difficult.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-940) Add 'end' to ec2 Reserved Instance data

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148005#comment-16148005
 ] 

ASF GitHub Bot commented on LIBCLOUD-940:
-

GitHub user xofer opened a pull request:

https://github.com/apache/libcloud/pull/1099

[LIBCLOUD-940]  Add 'end' to ec2 Reserved Instance data

## Add 'end' to ec2 Reserved Instance data

### Description

The [DescribeReservedInstances 
API](http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeReservedInstances.html)
 returns 3 fields related to the timeframe of the reservation:

  * start
  * end
  * duration

When a reservation is modified, start changes to the effective date of the 
modification, but duration remains the same (number of seconds in 1 or 3 
years). The only way to determine when a modified reservation expires is to use 
the end date.

### Status

done, ready for review

### Checklist (tick everything that applies)

- [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/xofer/libcloud ec2-ri-end

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1099.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1099






> Add 'end' to ec2 Reserved Instance data
> ---
>
> Key: LIBCLOUD-940
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-940
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Chris Clarke
>
> The [DescribeReservedInstances 
> API|http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeReservedInstances.html]
>  returns 3 fields related to the timeframe of the reservation:
>   * start
>   * end
>   * duration
> When a reservation is modified, start changes to the effective date of the 
> modification, but duration remains the same (number of seconds in 1 or 3 
> years). The only way to determine when a modified reservation expires is to 
> use the end date.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-926) [BUG Azure_ARM] in ex_create_public_ip function among other

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145852#comment-16145852
 ] 

ASF GitHub Bot commented on LIBCLOUD-926:
-

GitHub user SElsharkawy opened a pull request:

https://github.com/apache/libcloud/pull/1098

LIBCLOUD-926 - Propagated changes to azure_arm.py from pull 1051

## Changes Title (Update: LIBCLOUD-926 - [BUG Azure_ARM] in 
ex_create_public_ip function among other)

### Description

This suggested update fixes the condition that checks for parameter 
"location" being None. If the parameter is not None, the original code would 
still exit and raise ValueError exception.

In the file libcloud/compute/drivers/azure_arm.py.
There are some functions as ex_create_public_ip function that it needs a 
location parameter, when this parameter is send, a error happen: "Location is 
required".
Looking at the code I found with the following:

   if location is None and self.default_location:
location = self.default_location
else:
raise ValueError("location is required.")
This does not evaluate a possible parameter, only if the value is None.

I suggested the following change:

if location is None:
if self.default_location:
location = self.default_location
else:
raise ValueError("location is required.")
The affected methods are:

   ex_create_network_security_group
   ex_delete_network_security_group
   ex_create_public_ip
The same code has been used in several other places.

### Status

done, ready for review

### Checklist (tick everything that applies)

- [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/SElsharkawy/libcloud LIBCLOUD-926_pull-1051

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1098.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1098


commit adadaf53882d6e15500079debc7344e5e2d28049
Author: Elsharkawy, Sameh 
Date:   2017-08-29T18:18:19Z

Propagated changes to azure_arm.py from pull 1051




> [BUG Azure_ARM] in ex_create_public_ip function among other
> ---
>
> Key: LIBCLOUD-926
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-926
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Cristina Guerra
>  Labels: azurecompute-arm, compute
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the file libcloud/compute/drivers/azure_arm.py.
> There are some functions as ex_create_public_ip function that it needs a 
> location parameter, when this parameter is send, a error happen:  "Location 
> is required".
> Looking at the code I found with the following:
> {code:python}
>if location is None and self.default_location:
> location = self.default_location
> else:
> raise ValueError("location is required.")
> {code}
> This does not evaluate a possible parameter, only if the value is None.
> I propose:
> {code:python}
> if location is None and self.default_location:
> location = self.default_location
> elif location is not None:
> location = location
> else:
> raise ValueError("location is required.")
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-918) AzureNodeDriver's ex_create_public_ip method is missing the option to create a static public IP address

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134922#comment-16134922
 ] 

ASF GitHub Bot commented on LIBCLOUD-918:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1091


> AzureNodeDriver's ex_create_public_ip method is missing the option to create 
> a static public IP address
> ---
>
> Key: LIBCLOUD-918
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-918
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Affects Versions: 0.15.0
> Environment: CentOS 6.8 (x86_64)
>Reporter: Aki Ketolainen
>Priority: Minor
>
> In AzureNodeDriver class, ex_create_public_ip method does not allow for 
> creation of a static public IP address. "publicIPAllocationMethod" is 
> statically set to  "Dynamic" in the "data" dictionary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-936) AWS ELB/ALB Driver connection object initialization is broken

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134822#comment-16134822
 ] 

ASF GitHub Bot commented on LIBCLOUD-936:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1089


> AWS ELB/ALB Driver connection object initialization is broken
> -
>
> Key: LIBCLOUD-936
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-936
> Project: Libcloud
>  Issue Type: Bug
>  Components: LoadBalancer
>Reporter: Anton Kozyrev
>
> Code to reproduce:
> {code}
> from libcloud.loadbalancer.types import Provider
> from libcloud.loadbalancer.providers import get_driver
> key = ''
> secret = ''
> token = ''
> cls = get_driver(Provider.ELB)
> #cls = get_driver(Provider.ALB)
> driver = cls(key, secret, 'us-east-1', token=token)
> data = driver.list_balancers()
> {code}
> Error:
> {code}
> /Users/irvan/py27venv/bin/python test_token.py
> Traceback (most recent call last):
>   File "test_token.py", line 33, in 
> data = driver.list_balancers()
>   File 
> "/Users/irvan/Repos/GIT/github/libcloud/libcloud/loadbalancer/drivers/elb.py",
>  line 68, in list_balancers
> data = self.connection.request(ROOT, params=params).object
>   File "/Users/irvan/Repos/GIT/github/libcloud/libcloud/common/base.py", line 
> 603, in request
> headers=headers, stream=stream)
>   File "/Users/irvan/Repos/GIT/github/libcloud/libcloud/http.py", line 215, 
> in request
> verify=self.verification
>   File 
> "/Users/irvan/py27venv/lib/python2.7/site-packages/requests/sessions.py", 
> line 518, in request
> resp = self.send(prep, **send_kwargs)
>   File 
> "/Users/irvan/py27venv/lib/python2.7/site-packages/requests/sessions.py", 
> line 639, in send
> r = adapter.send(request, **kwargs)
>   File 
> "/Users/irvan/py27venv/lib/python2.7/site-packages/requests/adapters.py", 
> line 502, in send
> raise ConnectionError(e, request=request)
> requests.exceptions.ConnectionError: 
> HTTPSConnectionPool(host='elasticloadbalancing.%s.amazonaws.com', port=443): 
> Max retries exceeded with url: 
> /2012-06-01/?Action=DescribeLoadBalancers=2012-06-01 (Caused by 
> NewConnectionError('  object at 0x10760f4d0>: Failed to establish a new connection: [Errno 8] 
> nodename nor servname provided, or not known',))
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-875) Route 53 driver formats TXT records incorrectly

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134597#comment-16134597
 ] 

ASF GitHub Bot commented on LIBCLOUD-875:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1093


> Route 53 driver formats TXT records incorrectly
> ---
>
> Key: LIBCLOUD-875
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-875
> Project: Libcloud
>  Issue Type: Bug
>  Components: DNS
>Reporter: Tristan Seligmann
>
> Route 53 expects the values of TXT records to be wrapped in quotation marks 
> ("value"), but the driver does not add these for you.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-875) Route 53 driver formats TXT records incorrectly

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134587#comment-16134587
 ] 

ASF GitHub Bot commented on LIBCLOUD-875:
-

GitHub user tonybaloney opened a pull request:

https://github.com/apache/libcloud/pull/1093

LIBCLOUD-875 fix route 53 DNS quote encapsulation

## fix route 53 DNS quote encapsulation

Amazon's API stipulates that SPF and TXT records have quotes 
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#TXTFormat
The driver does not have any special casing for these records. I assume 
that existing users either:
- Get an error - see https://github.com/twisted/txacme/issues/120
- Add quotes before calling the methods, in which case this behaviour 
should be supported

For more information on contributing, please see 
[Contributing](http://libcloud.readthedocs.org/en/latest/development.html#contributing)
section of our documentation.

### Status

- work in progress

### Checklist (tick everything that applies)

- [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [ ] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tonybaloney/libcloud route53_formatting

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1093.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1093


commit b3b5086d19baa585af4987b0e32e7fdbe595ea5a
Author: Anthony Shaw 
Date:   2017-08-20T22:55:16Z

create tests to validate LIBCLOUD-875




> Route 53 driver formats TXT records incorrectly
> ---
>
> Key: LIBCLOUD-875
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-875
> Project: Libcloud
>  Issue Type: Bug
>  Components: DNS
>Reporter: Tristan Seligmann
>
> Route 53 expects the values of TXT records to be wrapped in quotation marks 
> ("value"), but the driver does not add these for you.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-918) AzureNodeDriver's ex_create_public_ip method is missing the option to create a static public IP address

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130952#comment-16130952
 ] 

ASF GitHub Bot commented on LIBCLOUD-918:
-

GitHub user aki-k opened a pull request:

https://github.com/apache/libcloud/pull/1091

[LIBCLOUD-918] Add an option to create a static public IP address.

### Title

Add an option to create a static public IP address.

### Description

Azure ARM driver's ex_create_public_ip only has the option to create a 
dynamic 
public IP address. This change adds the option to create a static public IP 
address.


https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-ip-addresses-overview-arm

### Status

done, ready for review

### Checklist (tick everything that applies)

- [X] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
- [X] Documentation
- [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
- [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/aki-k/libcloud 
LIBCLOUD-918_ex_create_public_ip

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/libcloud/pull/1091.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1091


commit c1ee7b14b1956744392eeb576c540e8c638af030
Author: Aki Ketolainen 
Date:   2017-08-17T18:06:32Z

[LIBCLOUD-918] Add an option to create a static public IP address.




> AzureNodeDriver's ex_create_public_ip method is missing the option to create 
> a static public IP address
> ---
>
> Key: LIBCLOUD-918
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-918
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Affects Versions: 0.15.0
> Environment: CentOS 6.8 (x86_64)
>Reporter: Aki Ketolainen
>Priority: Minor
>
> In AzureNodeDriver class, ex_create_public_ip method does not allow for 
> creation of a static public IP address. "publicIPAllocationMethod" is 
> statically set to  "Dynamic" in the "data" dictionary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LIBCLOUD-840) libcloud crashs when accessing Swift based object store using Keystone auth API v3

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122844#comment-16122844
 ] 

ASF GitHub Bot commented on LIBCLOUD-840:
-

Github user asfgit closed the pull request at:

https://github.com/apache/libcloud/pull/1068


> libcloud crashs when accessing Swift based object store using Keystone auth 
> API v3
> --
>
> Key: LIBCLOUD-840
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-840
> Project: Libcloud
>  Issue Type: Bug
>  Components: Storage
> Environment: ANY
>Reporter: Mario Oschwald
>Priority: Critical
> Attachments: LIBCLOUD-840-fix.patch
>
>
> libcloud crashs when accessing Swift based object store using Keystone auth 
> API v3
> Code to reproduce:
> {code}
> from libcloud.storage.types import Provider
> from libcloud.storage.providers import get_driver
> cls = get_driver(Provider.OPENSTACK_SWIFT)
> driver = cls('USER', 'PASSWORD', ex_force_auth_version='3.x_password',  
> ex_force_auth_url='https://keystone.cst.de:5001',
> ex_tenant_name='signing_service', ex_domain_name='AD', 
> ex_force_service_name='ceph')
> container = driver.create_container(container_name='fnord')
> {code}
> This produces the following stack trace:
> {code}
> Traceback (most recent call last):
>   File "D:/DEV/MAIN/Release Management/bin/cstutil/cloudtools.py", line 18, 
> in 
> main()
>   File "D:/DEV/MAIN/Release Management/bin/cstutil/cloudtools.py", line 14, 
> in main
> container = driver.create_container(container_name='fnord')
>   File 
> "C:\Python27\lib\site-packages\libcloud\storage\drivers\cloudfiles.py", line 
> 358, in create_container
> '/%s' % (container_name_encoded), method='PUT')
>   File 
> "C:\Python27\lib\site-packages\libcloud\storage\drivers\cloudfiles.py", line 
> 163, in request
> raw=raw)
>   File "C:\Python27\lib\site-packages\libcloud\common\openstack.py", line 
> 227, in request
> raw=raw)
>   File "C:\Python27\lib\site-packages\libcloud\common\base.py", line 753, in 
> request
> action = self.morph_action_hook(action)
>   File "C:\Python27\lib\site-packages\libcloud\common\openstack.py", line 
> 294, in morph_action_hook
> self._populate_hosts_and_request_paths()
>   File "C:\Python27\lib\site-packages\libcloud\common\openstack.py", line 
> 338, in _populate_hosts_and_request_paths
> url = self._ex_force_base_url or self.get_endpoint()
>   File 
> "C:\Python27\lib\site-packages\libcloud\storage\drivers\cloudfiles.py", line 
> 141, in get_endpoint
> if endpoint:
> UnboundLocalError: local variable 'endpoint' referenced before assignment
> {code}
> Please see attached patch for a trivial fix. Using the 2.0 endpoint locator
> mechanism works fine with 3.x



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)