[jira] [Commented] (LIBCLOUD-1039) Cloudfiles storage download_object_as_stream results in HttpLibResponseProxy error.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1039:
---

Commit 49b2206729ff4bacfef6803a1424e2ea6fa9045b in libcloud's branch 
refs/heads/trunk from Tomaz Muraus
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=49b2206 ]

Merge branch 'fix/LIBCLOUD-1039-fix-download-object-as-stream-cloudfiles' of 
https://github.com/mattseymour/libcloud into 
mattseymour-fix/LIBCLOUD-1039-fix-download-object-as-stream-cloudfiles


> Cloudfiles storage download_object_as_stream results in HttpLibResponseProxy 
> error.
> ---
>
> Key: LIBCLOUD-1039
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1039
> Project: Libcloud
>  Issue Type: Bug
> Environment: All,
>  
> Specific instance: Linux (ubuntu), Python3.5 and Python3.6, libcloud version 
> 2.4.0
>Reporter: matt seymour
>Priority: Major
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> When calling the download_object_as_stream method in the CLoudfiles driver a 
> HttpLibResponseProxy error is raised as the resulting (returning) object is 
> not a generator.



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

[jira] [Commented] (LIBCLOUD-1039) Cloudfiles storage download_object_as_stream results in HttpLibResponseProxy error.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1039:
---

Commit 49b2206729ff4bacfef6803a1424e2ea6fa9045b in libcloud's branch 
refs/heads/trunk from Tomaz Muraus
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=49b2206 ]

Merge branch 'fix/LIBCLOUD-1039-fix-download-object-as-stream-cloudfiles' of 
https://github.com/mattseymour/libcloud into 
mattseymour-fix/LIBCLOUD-1039-fix-download-object-as-stream-cloudfiles


> Cloudfiles storage download_object_as_stream results in HttpLibResponseProxy 
> error.
> ---
>
> Key: LIBCLOUD-1039
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1039
> Project: Libcloud
>  Issue Type: Bug
> Environment: All,
>  
> Specific instance: Linux (ubuntu), Python3.5 and Python3.6, libcloud version 
> 2.4.0
>Reporter: matt seymour
>Priority: Major
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> When calling the download_object_as_stream method in the CLoudfiles driver a 
> HttpLibResponseProxy error is raised as the resulting (returning) object is 
> not a generator.



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

[jira] [Commented] (LIBCLOUD-1039) Cloudfiles storage download_object_as_stream results in HttpLibResponseProxy error.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1039:
---

Commit 494cac548d9f92338c403c2cb76458bdf79530da in libcloud's branch 
refs/heads/trunk from Matt Seymour
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=494cac5 ]

Fixes LIBCLOUD-1039 - cloudfiles download_object_as_stream

When downloading an object as a stream `download_object_as_stream`
in storage/drivers/cloudfiles.py a generator object should be
returned. Currently a rerquest/response object is returned
in resulting in a HttpLibResponseProxy error.

This commit alters the callback_kwargs to use a
requests/response.iter_content resulting in an iterator object
being returned.


> Cloudfiles storage download_object_as_stream results in HttpLibResponseProxy 
> error.
> ---
>
> Key: LIBCLOUD-1039
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1039
> Project: Libcloud
>  Issue Type: Bug
> Environment: All,
>  
> Specific instance: Linux (ubuntu), Python3.5 and Python3.6, libcloud version 
> 2.4.0
>Reporter: matt seymour
>Priority: Major
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> When calling the download_object_as_stream method in the CLoudfiles driver a 
> HttpLibResponseProxy error is raised as the resulting (returning) object is 
> not a generator.



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

[jira] [Commented] (LIBCLOUD-1043) Azure Storage driver crashes when passed a non file-like iterator

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1043:
---

Commit f086aa68dfa543bc6b0cc348cb6a0bc1f43d6621 in libcloud's branch 
refs/heads/trunk from Tomaz Muraus
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=f086aa6 ]

Merge pull request #1287 from 
CatalystCode/1043_fix_azure_upload_object_via_stream_with_iterator

[LIBCLOUD-1043] Fix Azure upload_object_via_stream used with iter

> Azure Storage driver crashes when passed a non file-like iterator
> -
>
> Key: LIBCLOUD-1043
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1043
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Clemens Wolff
>Priority: Major
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> The azure_blobs implementation of {{upload_object_via_stream(iterator, ...)}} 
> currently assumes that the passed-in iterator always is a file-like object 
> that implements {{seek(...)}} 
> ([source|https://github.com/apache/libcloud/blob/a1f9897ce107eb1b01674262ca1b9ff1f91d46f0/libcloud/storage/drivers/azure_blobs.py#L828-L830]).
> This means that function crashes when used with arbitrary iterators as 
> returned by {{iter(...)}}.
> Notably, the libcloud integration for django-storages exercises this 
> functionality 
> ([source|https://github.com/jschneier/django-storages/blob/b441b74a17a46eb87ee4b10f60774b9a080c0fe1/storages/backends/apache_libcloud.py#L158])
>  which makes django-storages + libcloud + Azure Blobs currently unusable. See 
> detailed stacktrace below:
> {code:python}
> Traceback (most recent call last):
>   File ".../app/manage.py", line 15, in 
> execute_from_command_line(sys.argv)
>   File "...\lib\site-packages\django\core\management\__init__.py", line 381, 
> in execute_from_command_line
> utility.execute()
>   File "...\lib\site-packages\django\core\management\__init__.py", line 375, 
> in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "...\lib\site-packages\django\core\management\base.py", line 316, in 
> run_from_argv
> self.execute(*args, **cmd_options)
>   File "...\lib\site-packages\django\core\management\base.py", line 353, in 
> execute
> output = self.handle(*args, **options)
>   File 
> "...\lib\site-packages\django\contrib\staticfiles\management\commands\collectstatic.py",
>  line 188, in handle
> collected = self.collect()
>   File 
> "...\lib\site-packages\django\contrib\staticfiles\management\commands\collectstatic.py",
>  line 114, in collect
> handler(path, prefixed_path, storage)
>   File 
> "...\lib\site-packages\django\contrib\staticfiles\management\commands\collectstatic.py",
>  line 353, in copy_file
> self.storage.save(prefixed_path, source_file)
>   File "...\lib\site-packages\django\core\files\storage.py", line 49, in save
> return self._save(name, content)
>   File "...\lib\site-packages\storages\backends\apache_libcloud.py", line 
> 157, in _save
> self.driver.upload_object_via_stream(iter(file), self._get_bucket(), name)
>   File "...\lib\site-packages\libcloud\storage\drivers\azure_blobs.py", line 
> 828, in upload_object_via_stream
> iterator.seek(0, os.SEEK_END)
> AttributeError: 'generator' object has no attribute 'seek'
> {code}



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

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

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1022:
---

Commit 18bb84a263a7ba821188717193d6326e5a07a283 in libcloud's branch 
refs/heads/trunk from Tomaz Muraus
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=18bb84a ]

Merge branch 'LIBCLOUD-1022_digitalocean-dns-record-ttl-parameter' of 
https://github.com/kiniou/libcloud into 
LIBCLOUD-1022_digitalocean-dns-record-ttl-parameter


> enhance digitalocean dns driver with ttl parameter
> --
>
> Key: LIBCLOUD-1022
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1022
> Project: Libcloud
>  Issue Type: Improvement
>  Components: DNS
>Reporter: Kevin Roy
>Priority: Minor
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> DigitalOcean provides a parameter 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-1022) enhance digitalocean dns driver with ttl parameter

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1022:
---

Commit 7078d07a83bf09eed8d776a49e5b919ab6b3bd70 in libcloud's branch 
refs/heads/trunk from Kevin Roy
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=7078d07 ]

[LIBCLOUD-1022] check 'ttl' presence instead of try-catching


> enhance digitalocean dns driver with ttl parameter
> --
>
> Key: LIBCLOUD-1022
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1022
> Project: Libcloud
>  Issue Type: Improvement
>  Components: DNS
>Reporter: Kevin Roy
>Priority: Minor
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> DigitalOcean provides a parameter 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-1022) enhance digitalocean dns driver with ttl parameter

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1022:
---

Commit 064ad6cd4cf145ddabd0fc15cb00d965ef7688e4 in libcloud's branch 
refs/heads/trunk from Tomaz Muraus
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=064ad6c ]

Merge pull request #1252 from 
kiniou/LIBCLOUD-1022_digitalocean-dns-record-ttl-parameter

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

> enhance digitalocean dns driver with ttl parameter
> --
>
> Key: LIBCLOUD-1022
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1022
> Project: Libcloud
>  Issue Type: Improvement
>  Components: DNS
>Reporter: Kevin Roy
>Priority: Minor
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> DigitalOcean provides a parameter 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-1022) enhance digitalocean dns driver with ttl parameter

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1022:
---

Commit 064ad6cd4cf145ddabd0fc15cb00d965ef7688e4 in libcloud's branch 
refs/heads/trunk from Tomaz Muraus
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=064ad6c ]

Merge pull request #1252 from 
kiniou/LIBCLOUD-1022_digitalocean-dns-record-ttl-parameter

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

> enhance digitalocean dns driver with ttl parameter
> --
>
> Key: LIBCLOUD-1022
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1022
> Project: Libcloud
>  Issue Type: Improvement
>  Components: DNS
>Reporter: Kevin Roy
>Priority: Minor
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> DigitalOcean provides a parameter 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-1022) enhance digitalocean dns driver with ttl parameter

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1022:
---

Commit 18bb84a263a7ba821188717193d6326e5a07a283 in libcloud's branch 
refs/heads/trunk from Tomaz Muraus
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=18bb84a ]

Merge branch 'LIBCLOUD-1022_digitalocean-dns-record-ttl-parameter' of 
https://github.com/kiniou/libcloud into 
LIBCLOUD-1022_digitalocean-dns-record-ttl-parameter


> enhance digitalocean dns driver with ttl parameter
> --
>
> Key: LIBCLOUD-1022
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1022
> Project: Libcloud
>  Issue Type: Improvement
>  Components: DNS
>Reporter: Kevin Roy
>Priority: Minor
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> DigitalOcean provides a parameter 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-1040) CloudSigma provider ex_list_subscriptions() fails if your subscription includes free tier resources

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1040:
---

Commit e8547848a80f96bfa483bac2d0ae1fe8da3634c0 in libcloud's branch 
refs/heads/trunk from Tomaz Muraus
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=e854784 ]

Merge pull request #1284 from 
aki-k/LIBCLOUD-1040_CloudSigma_provider_ex_list_subscriptions_fails_if_your_subscription_includes_free_tier_resources

LIBCLOUD-1040_CloudSigma_provider_ex_list_subscriptions_fails_if_your…

> CloudSigma provider ex_list_subscriptions() fails if your subscription 
> includes free tier resources
> ---
>
> Key: LIBCLOUD-1040
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1040
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Affects Versions: 2.4.0
> Environment: CentOS 6.10
> python 3.5.2
>  
>Reporter: Aki Ketolainen
>Priority: Minor
>  Labels: easyfix
>
> When using driver.ex_list_subscriptions(status='all', resources=None) to list 
> your resources, you'll receive the error:
>   File 
> "/sw/libcloud/2.4.0/lib/python3.5/site-packages/libcloud/utils/iso8601.py", 
> line 117, in parse_date
>     m = ISO8601_REGEX.match(datestring)
> TypeError: expected string or bytes-like object
> CloudSigma gave some free resources to their customers a few years ago.
>  period=None, object_uuid=None>
>  period=None, object_uuid=None>
> I suspect these are the problem resources with no end time.
> I've added to iso8601.py on lines 117 and 118:
>     if datestring is None:
>     datestring = "-01-01T12:00:00+00:00"
> Not sure if this is an appropriate fix but seems to fix it.
>  



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

[jira] [Commented] (LIBCLOUD-1040) CloudSigma provider ex_list_subscriptions() fails if your subscription includes free tier resources

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1040:
---

Commit 46b9efb09a56f873a902f26a521868e16d8a7738 in libcloud's branch 
refs/heads/trunk from Tomaz Muraus
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=46b9efb ]

Merge branch 
'LIBCLOUD-1040_CloudSigma_provider_ex_list_subscriptions_fails_if_your_subscription_includes_free_tier_resources'
 of https://github.com/aki-k/libcloud into 
LIBCLOUD-1040_CloudSigma_provider_ex_list_subscriptions_fails_if_your_subscription_includes_free_tier_resources


> CloudSigma provider ex_list_subscriptions() fails if your subscription 
> includes free tier resources
> ---
>
> Key: LIBCLOUD-1040
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1040
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Affects Versions: 2.4.0
> Environment: CentOS 6.10
> python 3.5.2
>  
>Reporter: Aki Ketolainen
>Priority: Minor
>  Labels: easyfix
>
> When using driver.ex_list_subscriptions(status='all', resources=None) to list 
> your resources, you'll receive the error:
>   File 
> "/sw/libcloud/2.4.0/lib/python3.5/site-packages/libcloud/utils/iso8601.py", 
> line 117, in parse_date
>     m = ISO8601_REGEX.match(datestring)
> TypeError: expected string or bytes-like object
> CloudSigma gave some free resources to their customers a few years ago.
>  period=None, object_uuid=None>
>  period=None, object_uuid=None>
> I suspect these are the problem resources with no end time.
> I've added to iso8601.py on lines 117 and 118:
>     if datestring is None:
>     datestring = "-01-01T12:00:00+00:00"
> Not sure if this is an appropriate fix but seems to fix it.
>  



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

[jira] [Commented] (LIBCLOUD-1040) CloudSigma provider ex_list_subscriptions() fails if your subscription includes free tier resources

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1040:
---

Commit 940d97dab28ce04bf7767cd1772b07ceb79a1714 in libcloud's branch 
refs/heads/trunk from Aki Ketolainen
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=940d97d ]

LIBCLOUD-1040_CloudSigma_provider_ex_list_subscriptions_fails_if_your_subscription_includes_free_tier_resources


> CloudSigma provider ex_list_subscriptions() fails if your subscription 
> includes free tier resources
> ---
>
> Key: LIBCLOUD-1040
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1040
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Affects Versions: 2.4.0
> Environment: CentOS 6.10
> python 3.5.2
>  
>Reporter: Aki Ketolainen
>Priority: Minor
>  Labels: easyfix
>
> When using driver.ex_list_subscriptions(status='all', resources=None) to list 
> your resources, you'll receive the error:
>   File 
> "/sw/libcloud/2.4.0/lib/python3.5/site-packages/libcloud/utils/iso8601.py", 
> line 117, in parse_date
>     m = ISO8601_REGEX.match(datestring)
> TypeError: expected string or bytes-like object
> CloudSigma gave some free resources to their customers a few years ago.
>  period=None, object_uuid=None>
>  period=None, object_uuid=None>
> I suspect these are the problem resources with no end time.
> I've added to iso8601.py on lines 117 and 118:
>     if datestring is None:
>     datestring = "-01-01T12:00:00+00:00"
> Not sure if this is an appropriate fix but seems to fix it.
>  



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

[jira] [Commented] (LIBCLOUD-1040) CloudSigma provider ex_list_subscriptions() fails if your subscription includes free tier resources

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1040:
---

Commit e8547848a80f96bfa483bac2d0ae1fe8da3634c0 in libcloud's branch 
refs/heads/trunk from Tomaz Muraus
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=e854784 ]

Merge pull request #1284 from 
aki-k/LIBCLOUD-1040_CloudSigma_provider_ex_list_subscriptions_fails_if_your_subscription_includes_free_tier_resources

LIBCLOUD-1040_CloudSigma_provider_ex_list_subscriptions_fails_if_your…

> CloudSigma provider ex_list_subscriptions() fails if your subscription 
> includes free tier resources
> ---
>
> Key: LIBCLOUD-1040
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1040
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Affects Versions: 2.4.0
> Environment: CentOS 6.10
> python 3.5.2
>  
>Reporter: Aki Ketolainen
>Priority: Minor
>  Labels: easyfix
>
> When using driver.ex_list_subscriptions(status='all', resources=None) to list 
> your resources, you'll receive the error:
>   File 
> "/sw/libcloud/2.4.0/lib/python3.5/site-packages/libcloud/utils/iso8601.py", 
> line 117, in parse_date
>     m = ISO8601_REGEX.match(datestring)
> TypeError: expected string or bytes-like object
> CloudSigma gave some free resources to their customers a few years ago.
>  period=None, object_uuid=None>
>  period=None, object_uuid=None>
> I suspect these are the problem resources with no end time.
> I've added to iso8601.py on lines 117 and 118:
>     if datestring is None:
>     datestring = "-01-01T12:00:00+00:00"
> Not sure if this is an appropriate fix but seems to fix it.
>  



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

[jira] [Commented] (LIBCLOUD-1040) CloudSigma provider ex_list_subscriptions() fails if your subscription includes free tier resources

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1040:
---

Commit 46b9efb09a56f873a902f26a521868e16d8a7738 in libcloud's branch 
refs/heads/trunk from Tomaz Muraus
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=46b9efb ]

Merge branch 
'LIBCLOUD-1040_CloudSigma_provider_ex_list_subscriptions_fails_if_your_subscription_includes_free_tier_resources'
 of https://github.com/aki-k/libcloud into 
LIBCLOUD-1040_CloudSigma_provider_ex_list_subscriptions_fails_if_your_subscription_includes_free_tier_resources


> CloudSigma provider ex_list_subscriptions() fails if your subscription 
> includes free tier resources
> ---
>
> Key: LIBCLOUD-1040
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1040
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Affects Versions: 2.4.0
> Environment: CentOS 6.10
> python 3.5.2
>  
>Reporter: Aki Ketolainen
>Priority: Minor
>  Labels: easyfix
>
> When using driver.ex_list_subscriptions(status='all', resources=None) to list 
> your resources, you'll receive the error:
>   File 
> "/sw/libcloud/2.4.0/lib/python3.5/site-packages/libcloud/utils/iso8601.py", 
> line 117, in parse_date
>     m = ISO8601_REGEX.match(datestring)
> TypeError: expected string or bytes-like object
> CloudSigma gave some free resources to their customers a few years ago.
>  period=None, object_uuid=None>
>  period=None, object_uuid=None>
> I suspect these are the problem resources with no end time.
> I've added to iso8601.py on lines 117 and 118:
>     if datestring is None:
>     datestring = "-01-01T12:00:00+00:00"
> Not sure if this is an appropriate fix but seems to fix it.
>  



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

[jira] [Commented] (LIBCLOUD-1015) libcloud must not use pycrypto

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1015:
---

Commit a68022d1dff4daebafccff15106ba6988c9464d8 in libcloud's branch 
refs/heads/trunk from Ryan Petrello
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=a68022d ]

Use cryptography (not PyCrypto) for GCE service account authentication

see: https://issues.apache.org/jira/browse/LIBCLOUD-1015


> libcloud must not use pycrypto
> --
>
> Key: LIBCLOUD-1015
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-1015
> Project: Libcloud
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.3.0
>Reporter: Björn Boschman
>Priority: Major
>
> while looking at the github page you can see that pycrytp is unmaintained
> rumor has it that even dangerous bugs might exist



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

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

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1025:
---

Commit 78dafcbf314723028c9cc7c3268646971957d3ef in libcloud's branch 
refs/heads/trunk from Michael Braunoeder
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=78dafcb ]

[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
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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-1025) add a driver for RcodeZero DNS

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1025:
---

Commit 771fa66da5aeaff8225669358420b676f7ae1b31 in libcloud's branch 
refs/heads/trunk from Michael Braunoeder
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=771fa66 ]

[LIBCLOUD-1025] fixed travis errors.


> 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
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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-1025) add a driver for RcodeZero DNS

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1025:
---

Commit 69b110bc46f9ba6371101ac079a86225bc75bd48 in libcloud's branch 
refs/heads/trunk from Anthony Shaw
[ https://gitbox.apache.org/repos/asf?p=libcloud.git;h=69b110b ]

Merge pull request #1256 from MikeAT/Libcloud-1025_add_RcodeZero_DNS_Driver

[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
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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-1026) Updated documentation for UpCloud driver

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1026:
---

Commit dd6aaba856d5f3ed6e8a05c4f92465a968af450d in libcloud's branch 
refs/heads/trunk from [~ilarimakela]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=dd6aaba ]

[LIBCLOUD-1026] Update documentation for UpCloud driver

Signed-off-by: Rick van de Loo 


> 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-1014) Add tags when create a snapshot

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1014:
---

Commit 51b6609f8d34d9fe73134fdc76aa968cd1210425 in libcloud's branch 
refs/heads/trunk from elesbom
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=51b6609 ]

[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-1014) Add tags when create a snapshot

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1014:
---

Commit 7dce67d17764bf47430c5e5207748fc25c8e73c1 in libcloud's branch 
refs/heads/trunk from elesbom
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=7dce67d ]

[LIBCLOUD-1014] Fix test for PR #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-1014) Add tags when create a snapshot

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-1014:
---

Commit 608598821758cab79ed5e61b370ee0407f03616a in libcloud's branch 
refs/heads/trunk from elesbom
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=6085988 ]

[LIBCLOUD-1014] PEP8

Signed-off-by: Rick van de Loo 


> 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-604) Add `ex_list_subnets` to OpenStack provider

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-604:
--

Commit c7464b57dcc7e09fdfa01348de85f85046dac3a1 in libcloud's branch 
refs/heads/trunk from micafer
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=c7464b5 ]

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


> Add `ex_list_subnets` to OpenStack provider
> ---
>
> Key: LIBCLOUD-604
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-604
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Compute
>Affects Versions: 0.13.3
> Environment: Generic OpenStack
>Reporter: Tim Fall
>Priority: Minor
>
> Add equivalent function for returning listed subnets in OpenStack driver. 
> Similar to `ex_list_subnet` for EC2 endpoint providers.



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

[jira] [Commented] (LIBCLOUD-998) Use "/v2.0/networks" path in case of the OpenStack_2_NodeDriver class

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-998:
--

Commit c7464b57dcc7e09fdfa01348de85f85046dac3a1 in libcloud's branch 
refs/heads/trunk from micafer
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=c7464b5 ]

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


> Use "/v2.0/networks" path in case of the OpenStack_2_NodeDriver class
> -
>
> Key: LIBCLOUD-998
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-998
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Miguel Caballer
>Priority: Major
>
> Currently 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.



--
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 subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-997:
--

Commit c7464b57dcc7e09fdfa01348de85f85046dac3a1 in libcloud's branch 
refs/heads/trunk from micafer
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=c7464b5 ]

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-985) GCE - Support network routingmode and subnet secondary/internal access options

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-985:
--

Commit 9702f72b57f9b1372c289146a20cf201a0d6ea5d in libcloud's branch 
refs/heads/trunk from [~maxlip]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=9702f72 ]

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

Signed-off-by: Quentin Pradet 


> 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-986) List / Iterate container with prefix for Azure Blob service (This support exists in the other drivers already)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-986:
--

Commit ed0406043e438e0eeeb7e94dbc7aa0d65c0b8720 in libcloud's branch 
refs/heads/trunk from jhawk
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=ed04060 ]

LIBCLOUD-986: Fix S3 iteration without prefix

Closes #1194

Signed-off-by: Quentin Pradet 


> 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 subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-986:
--

Commit 1af5caf92a97092f7f11221ca881127e90807cb5 in libcloud's branch 
refs/heads/trunk from jhawk
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=1af5caf ]

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

Signed-off-by: Quentin Pradet 


> 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 subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-961:
--

Commit 924f12c232e586c677a2380250a8e5c31605b8d3 in libcloud's branch 
refs/heads/trunk from [~smarlow]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=924f12c ]

[LIBCLOUD-961] Update GCE public image list.

Add missing projects and update the image families for each
project based on `gcloud compute images list` info.


> 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 subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-973:
--

Commit 94db5c45db6cdf136afe83508a184dcadf54f0a2 in libcloud's branch 
refs/heads/trunk from [~Rahul-CSI]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=94db5c4 ]

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

Signed-off-by: Quentin Pradet 


> 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-960) GCE update firewall rule coverage for egress/deny and service accounts

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-960:
--

Commit 2337ab3d7c2af45bf41ff546242547e8fea02de3 in libcloud's branch 
refs/heads/trunk from [~maxlip]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=2337ab3 ]

LIBCLOUD-960: Expand GCE Firewall options coverage

Signed-off-by: Quentin Pradet 


> 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 subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-965:
--

Commit 7ef969c03841dc2afd624ace7f607e50d6f400ab in libcloud's branch 
refs/heads/trunk from [~micafer]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=7ef969c ]

Fix LIBCLOUD-965

Signed-off-by: Quentin Pradet 


> /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-971) wait_until_running error when empty ip addresses

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-971:
--

Commit 5c35c9894a776052c60fca4a0f0263bf6be7daad in libcloud's branch 
refs/heads/trunk from [~paepke]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=5c35c98 ]

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

Closes #1156

Part of LIBCLOUD-971.

Signed-off-by: Tomaz Muraus 


> 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 subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-971:
--

Commit 5c35c9894a776052c60fca4a0f0263bf6be7daad in libcloud's branch 
refs/heads/trunk from [~paepke]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=5c35c98 ]

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

Closes #1156

Part of LIBCLOUD-971.

Signed-off-by: Tomaz Muraus 


> 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-969) Add pricing information to Upcloud driver list_sizes method

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-969:
--

Commit 721a83aec40894bd8e3be03cb5e4cea0fd278696 in libcloud's branch 
refs/heads/trunk from [~mlackman]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=721a83a ]

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

Signed-off-by: Quentin Pradet 


> 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-955) Add support for DigitalOcean Spaces

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-955:
--

Commit 79052a080f87a436f27701db7429fa7dcb11d433 in libcloud's branch 
refs/heads/trunk from [~andrewsomething]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=79052a0 ]

[LIBCLOUD-955] Add DigitalOcean Spaces support.

Signed-off-by: Quentin Pradet 


> 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 subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-954:
--

Commit bd7a397e1ff3e3f2fc7f4d6f6b643d3d6c764111 in libcloud's branch 
refs/heads/trunk from [~quentinp]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=bd7a397 ]

[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-946) Can't install apache-libcloud (file name too long)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-946:
--

Commit 60701af4e610b9eeb4e3c60034300148933d69ba in libcloud's branch 
refs/heads/trunk from [~kami]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=60701af ]

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.


> 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)
> 

[jira] [Commented] (LIBCLOUD-745) Add Vultr DNS provider implementation

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-745:
--

Commit cf884251d98f7a67a5b35055caa4108500dbc654 in libcloud's branch 
refs/heads/trunk from [~kami]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=cf88425 ]

Add test cases for it.

Part of LIBCLOUD-745.


> Add Vultr DNS provider implementation
> -
>
> Key: LIBCLOUD-745
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-745
> Project: Libcloud
>  Issue Type: New Feature
>  Components: DNS
>Reporter: Alejandro Pereira
>Priority: Minor
>
> Im currenty working on adding this provider.



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

[jira] [Commented] (LIBCLOUD-945) testsuite fails on i686

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-945:
--

Commit 28a5590425aefc2983d40b71b4372e3340ceeecf in libcloud's branch 
refs/heads/trunk from [~kami]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=28a5590 ]

Fix Azure blobs driver, make sure Content-Length header value is a
string and not a number.

Part of LIBCLOUD-945

Closes #


> 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,
> 

[jira] [Commented] (LIBCLOUD-875) Route 53 driver formats TXT records incorrectly

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-875:
--

Commit b3b5086d19baa585af4987b0e32e7fdbe595ea5a in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=b3b5086 ]

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-840) libcloud crashs when accessing Swift based object store using Keystone auth API v3

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-840:
--

Commit 0378495ab879fb33f493d6c67164d39202bf7849 in libcloud's branch 
refs/heads/trunk from [~hakanc]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=0378495 ]

Fix #LIBCLOUD-840

Update OpenStackSwiftConnection to work with auth version 3.0


> 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)

[jira] [Commented] (LIBCLOUD-458) Use HTTPS CDN URIs for Rackspace Cloud Files

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-458:
--

Commit b21787bd4f500bee9e61f700bb21b2e88bf21d1a in libcloud's branch 
refs/heads/trunk from [~ayleph]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=b21787b ]

Add SSL URI support for LIBCLOUD-458

Add an optional argument to retrieve the x-cdn-ssl-uri of a Cloud Files
container.


> Use HTTPS CDN URIs for Rackspace Cloud Files
> 
>
> Key: LIBCLOUD-458
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-458
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Storage
>Affects Versions: 0.14.0-beta3
>Reporter: Michael Farrell
>
> I found another patch in my collection, where I had patched the Rackspace 
> storage driver to use the HTTPS CDN URI.
> I'm unsure if it may be best to have this as an option for storage drivers, 
> but if this option is added, it will also need to be implemented for the 
> other storage drivers.  I would like some advice on this.
> The patch that hard codes it to use HTTPS URIs always for the CDN, as a 
> 1-line change (ie: without the settings proposed above):
> {code}
>  libcloud/storage/drivers/cloudfiles.py 
> 
> index 1502a33..6e7f931 100644
> @@ -273,7 +273,7 @@ class CloudFilesStorageDriver(StorageDriver, 
> OpenStackDriverMixin):
> cdn_request=True)
>  
>  if response.status == httplib.NO_CONTENT:
> -cdn_url = response.headers['x-cdn-uri']
> +cdn_url = response.headers['x-cdn-ssl-uri']
>  return cdn_url
>  elif response.status == httplib.NOT_FOUND:
>  raise ContainerDoesNotExistError(value='',
> {code}



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

[jira] [Commented] (LIBCLOUD-925) Error in GCE driver in function _get_error

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-925:
--

Commit fe092f0c2ac45f140786deb89de9fa6942ed738a in libcloud's branch 
refs/heads/trunk from [~micafer]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=fe092f0 ]

Fix #LIBCLOUD-925
Closes #1074


> Error in GCE driver in function _get_error
> --
>
> Key: LIBCLOUD-925
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-925
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Miguel Caballer
>Priority: Minor
>  Labels: gce
>
> _get_error function assumes that the body['error'] value is a dict, but in 
> some cases it contains an string (unicode).
> So it tries to do a err.get and it failts.
> I has to be something like that:
> {noformat}
> if 'code' in err:
> code = err.get('code')
> message = err.get('message')
> else:
> code = None
> if 'reason' in err:
> code = err.get('reason')
> message = body.get('error_description', err)
> {noformat}



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

[jira] [Commented] (LIBCLOUD-912) [python] Requests tries to connect to 127.0.0.1:443

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-912:
--

Commit b8ba6c10accdf6d9ce8a40787e2300a594437ebe in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=b8ba6c1 ]

issues with LIBCLOUD-912


> [python] Requests tries to connect to 127.0.0.1:443
> ---
>
> Key: LIBCLOUD-912
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-912
> Project: Libcloud
>  Issue Type: Bug
> Environment: python 2.7
> apache-libcloud==2.0.0rc2
>Reporter: Alexis Lesieur
>  Labels: newbie, python
>
> Hi!
> Sorry if this story is not created properly.
> I'm not that familiar with how you guys manage your Jira. Feel free to give 
> me directions or just modify the ticket :-)
> So we have been trying to upgrade the version of our libcloud python package, 
> but it breaks for our rackspace/openstack environment.
> I have been digging for a while and I couldn't find where the difference was 
> between 1.x.x and 2.0.0rc2.
> Observed behavior:
> 1.x.x:
> 3 connections are created:
> - to 127.0.0.1:443
> - to host:3000 (ex_force_auth_url)
> - to host:8774/v2/... (don't know where it comes from)
> 2.0.0rc2:
> 2 connections
> - to 127.0.0.1:443
> - to host:3000 (ex_force_auth_url)
> and the last connection is done using 127.0.0.1:443 again, using the same 
> connector created in the first one
> I don't understand the change in behavior between the two versions.
> I tried use the ex_force_base_url flag, and while it does look like the path 
> of that url is respected, the host is always replaced by 127.0.0.1.
> Any idea of what is happening?
> Thanks!



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

[jira] [Commented] (LIBCLOUD-910) Not a Gzipped file when using LIBCLOUD_DEBUG

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-910:
--

Commit 4e5ddfbf2ab6c3bbaf7b2092ce3094dff54d5b59 in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=4e5ddfb ]

add test to show LIBCLOUD-910 failure


> Not a Gzipped file when using LIBCLOUD_DEBUG
> 
>
> Key: LIBCLOUD-910
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-910
> Project: Libcloud
>  Issue Type: Bug
>  Components: Core
> Environment: python 2.6, debian jessie
>Reporter: Tom Melendez
>
> ## Summary
> When LIBCLOUD_DEBUG is set, receive a gzip error.  If the call to 
> decompress_data is commented out, things progress fine. 
> Offending line:
>   File "./libcloud/utils/loggingconnection.py", line 71, in _log_response
> body = decompress_data('gzip', body)
> ## Stacktrace
> (libcloud-testing) 
> supertom@supertom:~/virts/libcloud-testing/code/apache-libcloud-2.0.0rc2$ 
> demos/gce_demo.py --compute
> => Compute demo/test start time: 2017-04-05 16:22:58.309187
> DEBUG:requests.packages.urllib3.connectionpool:Starting new HTTPS connection 
> (1): www.googleapis.com
> DEBUG:requests.packages.urllib3.connectionpool:https://www.googleapis.com:443 
> "GET /compute/v1/projects/supertom-graphite/zones HTTP/1.1" 200 None
> /usr/lib/python2.7/gzip.py:196: UnicodeWarning: Unicode unequal comparison 
> failed to convert both arguments to Unicode - interpreting them as being 
> unequal
>   if magic != '\037\213':
> Traceback (most recent call last):
>   File "demos/gce_demo.py", line 957, in 
> main_compute()
>   File "demos/gce_demo.py", line 342, in main_compute
> gce = get_gce_driver()
>   File "demos/gce_demo.py", line 111, in get_gce_driver
> driver = get_driver(Provider.GCE)(*args, **kwargs)
>   File "./libcloud/compute/drivers/gce.py", line 1803, in __init__
> self.zone_list = self.ex_list_zones()
>   File "./libcloud/compute/drivers/gce.py", line 2757, in ex_list_zones
> response = self.connection.request(request, method='GET').object
>   File "./libcloud/compute/drivers/gce.py", line 121, in request
> response = super(GCEConnection, self).request(*args, **kwargs)
>   File "./libcloud/common/google.py", line 806, in request
> *args, **kwargs)
>   File "./libcloud/common/base.py", line 664, in request
> 'response': self.connection.getresponse()}
>   File "./libcloud/utils/loggingconnection.py", line 141, in getresponse
> rv = self._log_response(HttpLibResponseProxy(original_response))
>   File "./libcloud/utils/loggingconnection.py", line 71, in _log_response
> body = decompress_data('gzip', body)
>   File "./libcloud/utils/compression.py", line 39, in decompress_data
> return gzip.GzipFile(fileobj=cls(data)).read()
>   File "/usr/lib/python2.7/gzip.py", line 261, in read
> self._read(readsize)
>   File "/usr/lib/python2.7/gzip.py", line 303, in _read
> self._read_gzip_header()
>   File "/usr/lib/python2.7/gzip.py", line 197, in _read_gzip_header
> raise IOError, 'Not a gzipped file'
> IOError: Not a gzipped file
> ## Steps to reproduce
> export LIBCLOUD_DEBUG=/tmp/gce-libcloud.log
> (set values in demos/secrets.py)
> demos/gce_demo.py --compute



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

[jira] [Commented] (LIBCLOUD-893) Having certifi installed breaks libcloud.security.py for 2.0.0rc1

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-893:
--

Commit 516018d050a5470afe4a07d33d1fcb26d0e1df18 in libcloud's branch 
refs/heads/trunk from [~bennettaur]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=516018d ]

Fixed a NoneType error being thrown in libcloud.security when certify is 
installed (LIBCLOUD-893)
Closes #982


> Having certifi installed breaks libcloud.security.py for 2.0.0rc1
> -
>
> Key: LIBCLOUD-893
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-893
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Michael Bennett
>Priority: Minor
>
> This change: 
> https://github.com/apache/libcloud/commit/a4ad8d4a44dbf6069d924cdadabfff522ed703e6
> Causes libcloud.security to fail on import when the certifi package is 
> installed. CA_CERTS_PATH was initialized to None however with certifi 
> installed, line 58 attempts to insert the certifi_ca_bundle_path and throws a 
> NoneType error



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

[jira] [Commented] (LIBCLOUD-887) setting LIBCLOUD_DEBUG causes unexpected keyword 'stream' TypeError

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-887:
--

Commit ed6d012aab1c8bad83f66bf4ed4621b1d5fe0d27 in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=ed6d012 ]

create a test to prove LIBCLOUD-887 is a bug


> setting LIBCLOUD_DEBUG causes unexpected keyword 'stream' TypeError
> ---
>
> Key: LIBCLOUD-887
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-887
> Project: Libcloud
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 0.15.1
> Environment: Ubuntu, python 2.7
>Reporter: Tom Melendez
>
> If a user sets LIBCLOUD_DEBUG, they will receive an error and no requests 
> will be made.  This is happening on trunk.
> In ./libcloud/utils/loggingconnection.py
> LoggingConnection.request does not accept the stream keyword which causes an 
> error:
> TypeError: request() got an unexpected keyword argument 'stream'
> I can manually add the stream keyword to the parameter list and all is good 
> again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-826) GCE list nodes performance improvement

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-826:
--

Commit 03575ecfd9ac13a64c9469be87c96b1677de8493 in libcloud's branch 
refs/heads/trunk from [~supertom]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=03575ec ]

[google compute] Improve performance of list nodes by caching volume 
information.

We leverage the aggregated disk call and store the result.  For the list node 
operation, we've added an extra parameter to use the cached data, which results 
to true.

Tests and fixtures updated as well.

Closes #813
Closes LIBCLOUD-826

Signed-off-by: Eric Johnson 


> GCE list nodes performance improvement
> --
>
> Key: LIBCLOUD-826
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-826
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Tom Melendez
>  Labels: gce
>
> list_nodes currently makes at least one independent API call to the disks/get 
> API (to obtain disk information) for each node in the list.  This change will 
> use the disks/aggregatedList API for this instead, reducing NUM_INSTANCES API 
> calls to one.
> I ran some simple command-line tests to demonstrate the improvements in 
> response time and API calls.
> Below is an in-network comparison using 40 nodes in 4 different regions.
> ||Code||instances/zones/regions||Time (sec)||API Calls
> |Current 1.0|40/4/2|6.805|43|
> |with disks/aggregatedList|40/4/2|0.919|4|
> I have a PR forthcoming to implement this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-879:
--

Commit 1666a8da34068db0557cc9b186736f571e73df58 in libcloud's branch 
refs/heads/trunk from [~charly37]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=1666a8d ]

[LIBCLOUD-879] Add support of node without public IP in LB

closes #879

Signed-off-by: Allard Hoeve 


> 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
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-873) Updated ProfitBricks Compute Driver (REST api v3)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-873:
--

Commit 2569a5f2a953314483712667a964e5463990f617 in libcloud's branch 
refs/heads/trunk from [~matfin]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=2569a5f ]

[LIBCLOUD-873] Updated ProfitBricks Compute Driver (REST api v3)

Refactoring the compute  driver to remove support for the EOL SOAP api and 
modifying api calls to use the REST api (v3).

Removing XML test fixtures and replacing them with JSON fixtures.

Providing wrappers for all new functionality provided in v3 of the Cloud API.

Addressing an issue in libcloud/common/base.py where a http status code of 202 
would not be flagged as a successful request.


> Updated ProfitBricks Compute Driver (REST api v3)
> -
>
> Key: LIBCLOUD-873
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-873
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Affects Versions: 0.13.3
> Environment: Linux, Windows
>Reporter: Matt Finucane
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Updated the compute driver for the ProfitBricks platform.
> This update removes the SOAP api calls and replaces them with REST calls.
> All functions documented in v3 of the ProfitBricks Cloud API are included 
> with this driver.
> This is also related to the issue 
> https://issues.apache.org/jira/browse/LIBCLOUD-866?filter=-2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-862) Vultr driver does not implement SSH key create and delete methods

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-862:
--

Commit 5c6cc2f36f11ca78a50ee357c5b58acc2fdb0183 in libcloud's branch 
refs/heads/trunk from [~femnad]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=5c6cc2f ]

[LIBCLOUD-862] Implement SSH Key Create/Delete Methods for Vultr

* Add methods to the Vultr compute driver for creating and deleting SSH key
  pairs.
* Add the corresponding tests for the Vultr compute driver test suite.


> Vultr driver does not implement SSH key create and delete methods
> -
>
> Key: LIBCLOUD-862
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-862
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Compute
>Reporter: Fahri Cihan Demirci
>Priority: Minor
>
> The Vultr compute driver is not implementing SSH key create and delete 
> methods.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-861) Volume snapshot operations are not implemented for Digital Ocean driver

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-861:
--

Commit 8c5a4aff28c1f0eb7b7229558f2e88b83691df73 in libcloud's branch 
refs/heads/trunk from [~femnad]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=8c5a4af ]

LIBCLOUD-861: Implement Volume Snapshot Operations for Digital Ocean

* Add methods for creating, listing and deleting volume snapshots to the
  Digital Ocean driver.
* Add the corresponding tests and their fixtures.


> Volume snapshot operations are not implemented for Digital Ocean driver
> ---
>
> Key: LIBCLOUD-861
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-861
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Compute
>Reporter: Fahri Cihan Demirci
>Priority: Minor
>
> For the Digital Ocean driver, volume snapshot operations, like creating 
> snapshots for volumes, listing volume snapshots and deleting volume 
> snapshots, have not been implemented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-850) Docker Driver missing '/' prior to URI

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-850:
--

Commit 053d57469b502e5e548e2bbfa0322ec018387764 in libcloud's branch 
refs/heads/trunk from [~mloria]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=053d574 ]

fix LIBCLOUD-850


> Docker Driver missing '/' prior to URI
> --
>
> Key: LIBCLOUD-850
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-850
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Mario Loria
>Priority: Critical
>
> Just tried the docker driver and found that it's improperly sending requests 
> to the Docker API:
> {{http://127.0.0.1:4243v1.24/containers/json?all=1}}
> which yields:
> {code}
> >>> conn.list_containers()
> Traceback (most recent call last):
>   File "", line 1, in 
> conn.list_containers()
>   File 
> "/home/mloria/arrovenv/lib/python3.5/site-packages/libcloud/container/drivers/docker.py
> ", line 279, in list_containers
> "v%s/containers/json%s" % (self.version, ex)).object
>   File 
> "/home/mloria/arrovenv/lib/python3.5/site-packages/libcloud/common/base.py", 
> line 862, 
> in request
> response = responseCls(**kwargs)
>   File 
> "/home/mloria/arrovenv/lib/python3.5/site-packages/libcloud/common/base.py", 
> line 179, 
> in __init__
> headers=self.headers)
> libcloud.common.exceptions.BaseHTTPError: 400 Bad Request
> {code}
> I've verified this by making the same GET request with Postman, which worked 
> properly (with the missing '/'). Also, Wireshark: http://imgur.com/a/ogEge



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-858) Unable to list nodes with Libvirt provider on Python 3

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-858:
--

Commit f5ff0cfb080b767b542e9deec5ecc34dedcb4f0c in libcloud's branch 
refs/heads/trunk from [~femnad]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=f5ff0cf ]

LIBCLOUD-858: Fix Listing Libvirt Nodes with Python 3

Closes #894


> Unable to list nodes with Libvirt provider on Python 3
> --
>
> Key: LIBCLOUD-858
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-858
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
> Environment: Ubuntu 16.04.1 LTS
> Python 3.5.2
> Libcloud installed from 1a836148250ebf852a7f28e4d93007417ee7639d
>Reporter: Fahri Cihan Demirci
>
> Using the {{list_nodes}} methods of the Libvirt provider driver results in an 
> error when using Python 3. A simple script to trigger this is as follows:
> {code}
> from libcloud.compute.providers import get_driver
> from libcloud.compute.types import Provider
> cls = get_driver(Provider.LIBVIRT)
> driver = cls('qemu:///system')
> nodes = driver.list_nodes()
> {code}
> It results in the following error:
> {code}
> Traceback (most recent call last):
>   File "libcloud_list_nodes.py", line 6, in 
> nodes = driver.list_nodes()
>   File 
> "/home/femnad/v/libcloud3-pristine/lib/python3.5/site-packages/apache_libcloud-1.2.1-py3.5.egg/libcloud/compute/drivers/libvirt_driver.py",
>  line 120, in list_nodes
> nodes = self._to_nodes(domains=domains)
>   File 
> "/home/femnad/v/libcloud3-pristine/lib/python3.5/site-packages/apache_libcloud-1.2.1-py3.5.egg/libcloud/compute/drivers/libvirt_driver.py",
>  line 276, in _to_nodes
> nodes = [self._to_node(domain=domain) for domain in domains]
>   File 
> "/home/femnad/v/libcloud3-pristine/lib/python3.5/site-packages/apache_libcloud-1.2.1-py3.5.egg/libcloud/compute/drivers/libvirt_driver.py",
>  line 276, in 
> nodes = [self._to_node(domain=domain) for domain in domains]
>   File 
> "/home/femnad/v/libcloud3-pristine/lib/python3.5/site-packages/apache_libcloud-1.2.1-py3.5.egg/libcloud/compute/drivers/libvirt_driver.py",
>  line 285, in _to_node
> ip_addresses = self._get_ip_addresses_for_domain(domain)
>   File 
> "/home/femnad/v/libcloud3-pristine/lib/python3.5/site-packages/apache_libcloud-1.2.1-py3.5.egg/libcloud/compute/drivers/libvirt_driver.py",
>  line 333, in _get_ip_addresses_for_domain
> arp_table = self._parse_ip_table_arp(arp_output=stdout)
>   File 
> "/home/femnad/v/libcloud3-pristine/lib/python3.5/site-packages/apache_libcloud-1.2.1-py3.5.egg/libcloud/compute/drivers/libvirt_driver.py",
>  line 410, in _parse_ip_table_arp
> return self._parse_mac_addr_table(arp_output, arp_regex)
>   File 
> "/home/femnad/v/libcloud3-pristine/lib/python3.5/site-packages/apache_libcloud-1.2.1-py3.5.egg/libcloud/compute/drivers/libvirt_driver.py",
>  line 431, in _parse_mac_addr_table
> lines = cmd_output.split('\n')
> TypeError: a bytes-like object is required, not 'str'
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-835) Malformed auth token causes fatal exception in Google Storage driver

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-835:
--

Commit 78df34cf8db8706440ee594c571d80de8613433e in libcloud's branch 
refs/heads/trunk from [~paul.tiplady]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=78df34c ]

Fix caching of Google auth tokens

_write_token_to_file was not zeroing the file before writing
a new token, causing corruption.

FIXES: LIBCLOUD-835

Closes #844

Signed-off-by: Tomaz Muraus 


> Malformed auth token causes fatal exception in Google Storage driver
> 
>
> Key: LIBCLOUD-835
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-835
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Paul Tiplady
>Priority: Critical
>
> One of my Django instances has started hitting a libcloud error which is 
> causing a fatal exception, bringing down the instance.
> It looks like libcloud is writing invalid JSON into the auth token, which 
> then causes a JSON parse error when it is subsequently read back in.
> Here's the token that's written:
> {code}
> $ cat /root/.google_libcloud_auth.
> {"access_token": "", "token_type": "Bearer", "expire_time": 
> "2016-07-12T16:45:09Z", "expires_in": 3559}09Z", "expires_in": 3537}
> {code}
> Note the two "expires_in" keys, one with a nonsense value of `3559}09Z"`
> Environment:
> Python 3.4.4 
> apache-libcloud==1.0.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-830) Add S3 support for cn-north-1

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-830:
--

Commit 6d3e60163af15c324195863542fd763fd51f5302 in libcloud's branch 
refs/heads/trunk from [~jamiecressey]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=6d3e601 ]

LIBCLOUD-830 Adding S3 support for cn-north-1

Closes #827

Signed-off-by: Tomaz Muraus 


> Add S3 support for cn-north-1
> -
>
> Key: LIBCLOUD-830
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-830
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Storage
>Reporter: Jamie Cressey
>Priority: Minor
>
> Currently unable to access S3 China using LibCloud



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-820) libvirt module only doesn't check if nodes are remote

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-820:
--

Commit bff3f29321c38825f4be881bc344487aa3052369 in libcloud's branch 
refs/heads/trunk from [~Katana Steel]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=bff3f29 ]

LIBCLOUD-820 added arp cache check using iproute2

In case arp isn't accessable by the user (as is the case for me
on debian testing) the use ip neighbor

Closes #788

Signed-off-by: Tomaz Muraus 


> libvirt module only doesn't check if nodes are remote
> -
>
> Key: LIBCLOUD-820
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-820
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Rene Kjellerup
>  Labels: easyfix
>
> in _get_ip_addresses_for_domain function it states:
> {noformat}
> def _get_ip_addresses_for_domain(self, domain):
> """
> Retrieve IP addresses for the provided domain.
> Note: This functionality is currently only supported on Linux and
> only works if this code is run on the same machine as the VMs run
> on.
> :return: IP addresses for the provided domain.
> :rtype: ``list``
> """
> {noformat}
> however it only checks if the platform is Linux... not if the it's on the 
> same machine. this causes list_nodes() to fail when using 
> uri='qemu+ssh:///systems'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-820) libvirt module only doesn't check if nodes are remote

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-820:
--

Commit 13e3b6e2c0e134350f6a50ac0af7a8e4cd819d36 in libcloud's branch 
refs/heads/trunk from [~Katana Steel]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=13e3b6e ]

LIBCLOUD-820 fixed lint errors

Closes #788

Signed-off-by: Tomaz Muraus 


> libvirt module only doesn't check if nodes are remote
> -
>
> Key: LIBCLOUD-820
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-820
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Rene Kjellerup
>  Labels: easyfix
>
> in _get_ip_addresses_for_domain function it states:
> {noformat}
> def _get_ip_addresses_for_domain(self, domain):
> """
> Retrieve IP addresses for the provided domain.
> Note: This functionality is currently only supported on Linux and
> only works if this code is run on the same machine as the VMs run
> on.
> :return: IP addresses for the provided domain.
> :rtype: ``list``
> """
> {noformat}
> however it only checks if the platform is Linux... not if the it's on the 
> same machine. this causes list_nodes() to fail when using 
> uri='qemu+ssh:///systems'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-713) GCE driver list_sizes does not return the price

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-713:
--

Commit f5537811d97a7b58a1222a2f43dfccfa6add3bc6 in libcloud's branch 
refs/heads/trunk from [~erjohnso]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=f553781 ]

[google compute] fix missing pricing data

Closes LIBCLOUD-713
Closes #778

Signed-off-by: Eric Johnson 


> GCE driver list_sizes does not return the price
> ---
>
> Key: LIBCLOUD-713
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-713
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Affects Versions: 0.15.1
>Reporter: Webinav
>Assignee: Eric Johnson
>Priority: Minor
> Fix For: 0.15.1
>
>
> I am using libcloud 0.15.1 and trying to pullout the pricing details for GCE
> I noticed that there is a KeyError exception thrown which causes the price to 
> be set as None
> Driver: GCE
> File: gce.py
> API: _to_node_size()
> Snippet:
> try:
> price = self._get_size_price(size_id=machine_type['name'])
> except KeyError:
> price = None



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-802) Add drivers for Aliyun cloud

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-802:
--

Commit a8479e18b288460f64d8b82327d9e11db1abf23d in libcloud's branch 
refs/heads/trunk from [~samsong8610]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=a8479e1 ]

[LIBCLOUD-802] Add doc page and examples for Aliyun ecs

Signed-off-by: Tomaz Muraus 

Closes #712


> Add drivers for Aliyun cloud
> 
>
> Key: LIBCLOUD-802
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-802
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Compute, LoadBalancer, Storage
>Reporter: sam song
>  Labels: features
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Aliyun is the biggest cloud provider in China, it provides AWS-like cloud 
> services, such as ECS, SLB, OSS etc.
> This issue aims to implement drivers for Aliyun ECS(compute), SLB(load 
> balancer), OSS(storage) services.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-802) Add drivers for Aliyun cloud

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-802:
--

Commit e6002e0ad443b9762f7a5e6187aeb4617e2874e8 in libcloud's branch 
refs/heads/trunk from xg.song
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=e6002e0 ]

[LIBCLOUD-802] Add drivers for Aliyun cloud

Closes #712

Signed-off-by: Tomaz Muraus 


> Add drivers for Aliyun cloud
> 
>
> Key: LIBCLOUD-802
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-802
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Compute, LoadBalancer, Storage
>Reporter: sam song
>  Labels: features
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Aliyun is the biggest cloud provider in China, it provides AWS-like cloud 
> services, such as ECS, SLB, OSS etc.
> This issue aims to implement drivers for Aliyun ECS(compute), SLB(load 
> balancer), OSS(storage) services.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-802) Add drivers for Aliyun cloud

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-802:
--

Commit ae4c482b7d9c01f6593e842775bf74e7e81eac6d in libcloud's branch 
refs/heads/trunk from [~samsong8610]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=ae4c482 ]

[LIBCLOUD-802] Refactor codes according to the project convention

Use immutable value for argument default
Prefer explicit arguments to kwargs
Add ALIYUN_ prefix to providers constant

Closes #712

Signed-off-by: Tomaz Muraus 


> Add drivers for Aliyun cloud
> 
>
> Key: LIBCLOUD-802
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-802
> Project: Libcloud
>  Issue Type: New Feature
>  Components: Compute, LoadBalancer, Storage
>Reporter: sam song
>  Labels: features
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Aliyun is the biggest cloud provider in China, it provides AWS-like cloud 
> services, such as ECS, SLB, OSS etc.
> This issue aims to implement drivers for Aliyun ECS(compute), SLB(load 
> balancer), OSS(storage) services.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-785) GCE: Service Account User ID has been changed the postfix

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-785:
--

Commit 22093a6a55a73274be263567effbe1af577e22c7 in libcloud's branch 
refs/heads/0.20.1 from [~erjohnso]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=22093a6 ]

[google] Allow for old and new style service account client email address

Closes LIBCLOUD-785


> GCE: Service Account User ID has been changed the postfix
> -
>
> Key: LIBCLOUD-785
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-785
> Project: Libcloud
>  Issue Type: Bug
>  Components: Core
>Reporter: Hoang Phan
>Assignee: Eric Johnson
>  Labels: gce, google-compute-engine, oauth2
>
> The post-fix of Service Account has been change from 
> developer.gserviceaccount.com to ..iam.gserviceaccount.com. It 
> make user always need to use api service to authenticate.
> https://github.com/apache/libcloud/blob/trunk/libcloud/common/google.py#L609



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-769) Backup driver type

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-769:
--

Commit cb9b89c9f94f4f69ca9091757c22a72a089b29aa in libcloud's branch 
refs/heads/trunk from anthony-shaw
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=cb9b89c ]

Merge branch 'LIBCLOUD-769_Backup_Driver' into trunk


> Backup driver type
> --
>
> Key: LIBCLOUD-769
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-769
> Project: Libcloud
>  Issue Type: New Feature
>Reporter: Anthony Shaw
>
> Introduce a driver for 'cloud backup' for service providers that support a 
> standalone BaaS product or service. 
> Targeted specifically at backing up existing nodes. Design must support min 3 
> drivers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-786) GCENodeDriver.ex_get_image needs some love, see description.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-786:
--

Commit 81a8dbc324f870444e980aee523fea48fc37cbcc in libcloud's branch 
refs/heads/trunk from [~crunk1]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=81a8dbc ]

Implemented LazyObject class, which provides a .lazy class method. The lazy 
class method returns a Proxy object that subclasses the target object class. 
Upon accessing the proxy object in any way, the object is initialized.

Modified Google Compute Engine License objects, GCELicense, to be such a lazy
object. This addresses https://issues.apache.org/jira/browse/LIBCLOUD-786.

Tests/Verification:
  tox -e lint
  python setup.py test
  Added test/common/test_base.py which has LazyObjectTest

Signed-off-by: Eric Johnson 


> GCENodeDriver.ex_get_image needs some love, see description.
> 
>
> Key: LIBCLOUD-786
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-786
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
>Reporter: Scott Crunkleton
>
> Firstly, the parameter 'ex_project_list' is a misnomer. It is being treated 
> as a single project, not list of projects.
> Secondly, it's slow. When not providing a project parameter, ex_get_image 
> lists all images from all projects listed in GCENodeDriver.IMAGE_PROJECTS. 
> This is a separate API call for each project. After getting all the images, 
> any images that have licenses create another API call via ex_get_license. 
> Thirdly, if any of the license calls try to pull a license from an image 
> project that the user doesn't have access to, it raises a 
> ResourceNotFoundError.
> My opinion: fix the ex_project_list param, and see about not populating the 
> image license data when fetching images.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-785) GCE: Service Account User ID has been changed the postfix

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-785:
--

Commit 88170f6582dd6cc3bce87c0ab3a89118551fe508 in libcloud's branch 
refs/heads/trunk from [~erjohnso]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=88170f6 ]

[google] Allow for old and new style service account client email address

Closes LIBCLOUD-785


> GCE: Service Account User ID has been changed the postfix
> -
>
> Key: LIBCLOUD-785
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-785
> Project: Libcloud
>  Issue Type: Bug
>  Components: Core
>Reporter: Hoang Phan
>Assignee: Eric Johnson
>  Labels: gce, google-compute-engine, oauth2
>
> The post-fix of Service Account has been change from 
> developer.gserviceaccount.com to ..iam.gserviceaccount.com. It 
> make user always need to use api service to authenticate.
> https://github.com/apache/libcloud/blob/trunk/libcloud/common/google.py#L609



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-718) gce_libcloud_auth credentials file world-readable

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-718:
--

Commit 59fec8e7a203ce95bca7a8b6c5c1744f4f718527 in libcloud's branch 
refs/heads/trunk from [~erjohnso]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=59fec8e ]

[google] Minor security improvement for storing cached GCE credentials

Closes LIBCLOUD-718


> gce_libcloud_auth credentials file world-readable
> -
>
> Key: LIBCLOUD-718
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-718
> Project: Libcloud
>  Issue Type: Bug
>  Components: Core
>Reporter: Siim Põder
>
> I noticed a suspicious-looking world-readable file on a VM that talks to 
> Google Compute Engine API via libcloud: 
> {noformat}
> -rw-r--r--  1 root root  164 Jun 27 21:21 
> .gce_libcloud_auth.wargame-engine
> {noformat}
> It contains a "Bearer" access token so presumably should not be readable by 
> other users on a shared system. I suspect this (untested) patch might maybe 
> fix this in git head:
> {noformat}
> diff --git a/libcloud/common/google.py b/libcloud/common/google.py
> index 694cf93..7a658c8 100644
> --- a/libcloud/common/google.py
> +++ b/libcloud/common/google.py
> @@ -715,7 +715,7 @@ class GoogleBaseConnection(ConnectionUserAndKey, 
> PollingConnection):
>  """
>  filename = os.path.realpath(os.path.expanduser(self.credential_file))
>  data = json.dumps(self.token_info)
> -with open(filename, 'w') as f:
> +with os.open(filename, os.O_WRONLY, 0o600) as f:
>  f.write(data)
>  
>  def has_completed(self, response): 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-776) Google Storage tests take forever on a Mac

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-776:
--

Commit 7e087d6bcad8a4a6bcfac614efe73ff5fef57e18 in libcloud's branch 
refs/heads/trunk from [~crunk1]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=7e087d6 ]

Fix unittests on Python 2.6 and modified/cleaned up Google tests.

Closes #648
Closes LIBCLOUD-776

Signed-off-by: Eric Johnson 


> Google Storage tests take forever on a Mac
> --
>
> Key: LIBCLOUD-776
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-776
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Greg Hill
>
> If you run tox on a Mac, the google storage tests take forever.  I tracked it 
> down to the _is_gce() method making an HTTP GET request against 
> http://metadata - for some reason this is slow on a mac but fails fast on 
> linux.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-775) Add support for updating node specification in Dimension Data driver

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-775:
--

Commit e8e758d9c690916f2c33e8d0afdd2a7cc9a07552 in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=e8e758d ]

LIBCLOUD-775 Update node, update VMware tools, add storage, change storage size 
or speed, remove storage. With tests

Signed-off-by: Anthony Shaw 


> Add support for updating node specification in Dimension Data driver
> 
>
> Key: LIBCLOUD-775
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-775
> Project: Libcloud
>  Issue Type: Improvement
>Reporter: Anthony Shaw
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-761) Extend Dimension Data driver to support monitoring features and network management

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-761:
--

Commit 8abaf891c17c984a6bda5d7cd7d785dc4545826d in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=8abaf89 ]

Merge branch 'LIBCLOUD-761_Network_and_monitoring_support' into trunk

Conflicts:
libcloud/compute/drivers/dimensiondata.py
libcloud/test/compute/test_dimensiondata.py


> Extend Dimension Data driver to support monitoring features and network 
> management
> --
>
> Key: LIBCLOUD-761
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-761
> Project: Libcloud
>  Issue Type: New Feature
>Reporter: Anthony Shaw
>
> Add more functions to the DD driver to cover off monitoring (on, off, set 
> plan) and network management for MCP 1.0 data centers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-766) CloudStack node.public_ips has duplicate ip addresses

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-766:
--

Commit 455a279f25654c4fcca9a516d835b0c0e1a33907 in libcloud's branch 
refs/heads/trunk from [~atsaki]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=455a279 ]

[LIBCLOUD-766] Unique node.public_ips returned by CloudStack ex_get_node and
list_nodes.

Closes #626

Signed-off-by: Tomaz Muraus 


> CloudStack node.public_ips has duplicate ip addresses 
> --
>
> Key: LIBCLOUD-766
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-766
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Atsushi Sasaki
>
> CloudStack driver's ex_get_node and list_nodes return nodes which 
> node.public_ips have duplicate ip addresses.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-767) CloudStack ex_get_node returns wrong node ip address ids

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-767:
--

Commit b37548b92be75004db807170a3ee68aa023b720b in libcloud's branch 
refs/heads/trunk from [~atsaki]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=b37548b ]

[LIBCLOUD-767] Fixed CloudStackAddress parameters

Closes #627

Signed-off-by: Tomaz Muraus 


> CloudStack ex_get_node returns wrong node ip address ids
> 
>
> Key: LIBCLOUD-767
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-767
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Atsushi Sasaki
>
> CloudStack ex_get_node returns a CloudStackNode object.
> CloudStackAddress attributes of extra["ip_addresses"] of the node are not set 
> correctly .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-765) Root level python logger is being set to DEBUG and console

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-765:
--

Commit a64678aa875d0d1966ce7b0748782eb2d34b4f7c in libcloud's branch 
refs/heads/trunk from [~kami]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=a64678a ]

Fix a bug / regression with Libcloud accidentaly setting paramiko root logger
level to DEBUG (this should only happen if LIBCLOUD_DEBUG environment variable)
is provided.

Part of LIBCLOUD-765, reported by John Bresnahan.


> Root level python logger is being set to DEBUG and console
> --
>
> Key: LIBCLOUD-765
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-765
> Project: Libcloud
>  Issue Type: Bug
>Reporter: John Bresnahan
>
> When usuing libcloud the following lines appear to set the root level python 
> logger to the console and to DEBUG:
> https://github.com/apache/libcloud/blob/trunk/libcloud/__init__.py#L74-L75



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-759) Add Pricing Data for SoftLayer CSP

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-759:
--

Commit 728bd887336ec324c0697da5ba5349a1f7024585 in libcloud's branch 
refs/heads/trunk from [~henkslaaf]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=728bd88 ]

Add standardized snapshot states to VolumeSnapshot

LIBCLOUD-759
closes: #602

Signed-off-by: Allard Hoeve 


> Add Pricing Data for SoftLayer CSP
> --
>
> Key: LIBCLOUD-759
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-759
> Project: Libcloud
>  Issue Type: Improvement
>Reporter: David Wilson
>Priority: Minor
>
> SoftLayer currently has no pricing data in the pricing.json file. Add pricing 
> data for SoftLayer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-760) Malformed XML requests in Dimension Data driver.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-760:
--

Commit 4fadb5631ee05898452d622f7493fb30a999bee1 in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=4fadb56 ]

LIBCLOUD-760 Fixed XML element names for Dimension Data requests

Closes #610

Signed-off-by: Eric Johnson 


> Malformed XML requests in Dimension Data driver.
> 
>
> Key: LIBCLOUD-760
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-760
> Project: Libcloud
>  Issue Type: Bug
>Reporter: Anthony Shaw
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-759) Add Pricing Data for SoftLayer CSP

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-759:
--

Commit a73e7b2de881977e2c90c3598f2b60d0190450cd in libcloud's branch 
refs/heads/trunk from [~dwilson2038]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=a73e7b2 ]

LIBCLOUD-759 Updated pricing.json file to include data from SoftLayer

Closes #603

Signed-off-by: Tomaz Muraus 


> Add Pricing Data for SoftLayer CSP
> --
>
> Key: LIBCLOUD-759
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-759
> Project: Libcloud
>  Issue Type: Improvement
>Reporter: David Wilson
>Priority: Minor
>
> SoftLayer currently has no pricing data in the pricing.json file. Add pricing 
> data for SoftLayer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-759) Add Pricing Data for SoftLayer CSP

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-759:
--

Commit 70bd1aa94433020925402db44cdcad23d13bc0d9 in libcloud's branch 
refs/heads/trunk from [~dwilson2038]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=70bd1aa ]

LIBCLOUD-759 Changed SoftLayer Node driver to use pricing information

Closes #603

Signed-off-by: Tomaz Muraus 


> Add Pricing Data for SoftLayer CSP
> --
>
> Key: LIBCLOUD-759
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-759
> Project: Libcloud
>  Issue Type: Improvement
>Reporter: David Wilson
>Priority: Minor
>
> SoftLayer currently has no pricing data in the pricing.json file. Add pricing 
> data for SoftLayer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-749) CloudStack: bugs in the method ex_authorize_security_group_ingress

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-749:
--

Commit a35bc7e536edc2f2c7c54d8f001d557029170562 in libcloud's branch 
refs/heads/trunk from lionel
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=a35bc7e ]

[LIBCLOUD-749] Fixed a minor issue with the docstring of the method 
ex_authorize_security_group_ingress

Closes #580

Signed-off-by: Tomaz Muraus 


> CloudStack: bugs in the method ex_authorize_security_group_ingress
> --
>
> Key: LIBCLOUD-749
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-749
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
> Environment: CloudStack compute driver
>Reporter: L. Schaub
>  Labels: Bug, CloudStack, Improvement, SecurityGroups
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> The method ex_authorize_security_group_ingress contains some bugs:
> - The docstring doesn't match parameters of the method.
> - Only ICMP and TCP is allowed even if the doc of the parameter "protocol" 
> mention TCP and UDP.
> - Moreover ICMP cannot be used because there is no way to specify the two 
> required parameters "icmptype" and "icmpcode".
> - The parameter endport is not used if it's defined.
> - The return type is not a list but a dict.
> - The unit test doesn't use parameters in the correct order.
> So I created a patch which aims to fix these bugs and also try to do the 
> following:
> - Improve the docstring to be a bit more detailed (the previous one comes 
> from the official Apache CloudStack documentation).
> - Add a kwargs to allow to provide extra parameters defined in the API and in 
> the docstring.
> - Improve the unit test.
> - Add support for other protocols like AH, GRE, ESP which are available on 
> some Cloud like Exoscale.
> I will provide the patch as a Pull Request in GitHub.
> Regards



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-749) CloudStack: bugs in the method ex_authorize_security_group_ingress

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-749:
--

Commit 64876e9fc12d428fba99aafc4d3691db25d60598 in libcloud's branch 
refs/heads/trunk from lionel
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=64876e9 ]

[LIBCLOUD-749] CloudStack: minor fixes to comply with pep8.

Closes #580

Signed-off-by: Tomaz Muraus 


> CloudStack: bugs in the method ex_authorize_security_group_ingress
> --
>
> Key: LIBCLOUD-749
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-749
> Project: Libcloud
>  Issue Type: Bug
>  Components: Compute
> Environment: CloudStack compute driver
>Reporter: L. Schaub
>  Labels: Bug, CloudStack, Improvement, SecurityGroups
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> The method ex_authorize_security_group_ingress contains some bugs:
> - The docstring doesn't match parameters of the method.
> - Only ICMP and TCP is allowed even if the doc of the parameter "protocol" 
> mention TCP and UDP.
> - Moreover ICMP cannot be used because there is no way to specify the two 
> required parameters "icmptype" and "icmpcode".
> - The parameter endport is not used if it's defined.
> - The return type is not a list but a dict.
> - The unit test doesn't use parameters in the correct order.
> So I created a patch which aims to fix these bugs and also try to do the 
> following:
> - Improve the docstring to be a bit more detailed (the previous one comes 
> from the official Apache CloudStack documentation).
> - Add a kwargs to allow to provide extra parameters defined in the API and in 
> the docstring.
> - Improve the unit test.
> - Add support for other protocols like AH, GRE, ESP which are available on 
> some Cloud like Exoscale.
> I will provide the patch as a Pull Request in GitHub.
> Regards



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-746) Add LiquidWeb DNS provider implementation

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-746:
--

Commit b35575f83fa4052c1d450ff2febd313e5f55f978 in libcloud's branch 
refs/heads/trunk from oltjano
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=b35575f ]

[LIBCLOUD-746] Add LiquidWeb DNS provider implementation

Closes #581

Signed-off-by: Tomaz Muraus 


> Add LiquidWeb DNS provider implementation
> -
>
> Key: LIBCLOUD-746
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-746
> Project: Libcloud
>  Issue Type: New Feature
>  Components: DNS
>Reporter: Alejandro Pereira
>Priority: Minor
>
> I'm going to add code to provide this provider.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-739) Add provider for DNS simple

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-739:
--

Commit 7ecaebbf7495ab2cf94cabf9c0700b4323d67768 in libcloud's branch 
refs/heads/trunk from [~kami]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=7ecaebb ]

Merge branch 'trunk' into LIBCLOUD-739_simpledns

Conflicts:
libcloud/dns/providers.py
libcloud/dns/types.py
libcloud/test/secrets.py-dist


> Add provider for DNS simple
> ---
>
> Key: LIBCLOUD-739
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-739
> Project: Libcloud
>  Issue Type: Improvement
>  Components: DNS
>Reporter: Alejandro Pereira
>Priority: Minor
>  Labels: features
>
> We would like to add a provider for this dns provider: https://dnsimple.com/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-739) Add provider for DNS simple

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-739:
--

Commit cacc8a9c9b915b5ab10a4ad59db034bd45d53b22 in libcloud's branch 
refs/heads/trunk from [~aleGpereira]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=cacc8a9 ]

[LIBCLOUD-739] Add DNSimple provider implementation


> Add provider for DNS simple
> ---
>
> Key: LIBCLOUD-739
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-739
> Project: Libcloud
>  Issue Type: Improvement
>  Components: DNS
>Reporter: Alejandro Pereira
>Priority: Minor
>  Labels: features
>
> We would like to add a provider for this dns provider: https://dnsimple.com/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-732) Add support for worldwidedns.net

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-732:
--

Commit e136292a9c9a0bbd25cb4da0a614f5ff069633ab in libcloud's branch 
refs/heads/trunk from [~kami]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=e136292 ]

Merge branch 'trunk' into LIBCLOUD-732_worldwidedns

Closes #566

Signed-off-by: Tomaz Muraus 

Conflicts:
CHANGES.rst


> Add support for worldwidedns.net
> 
>
> Key: LIBCLOUD-732
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-732
> Project: Libcloud
>  Issue Type: Improvement
>  Components: DNS
>Reporter: Alejandro Pereira
>Priority: Minor
>  Labels: features
>   Original Estimate: 0.2h
>  Remaining Estimate: 0.2h
>
> We want to start hosting on WorldWideDNS.net and we'll like to do it using 
> this tool. I'll be working in this :).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-714) Traceback when simplejson < 2.1.0 is installed

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on LIBCLOUD-714:
--

Commit 1aaaef95745cebf66a26128f3e74c13fa7361a90 in libcloud's branch 
refs/heads/trunk from [~erikjohnzon]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=1aaaef9 ]

Fix traceback when simplejson < 2.1.0 is installed

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

Closes #577

Signed-off-by: Tomaz Muraus 


> Traceback when simplejson < 2.1.0 is installed
> --
>
> Key: LIBCLOUD-714
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-714
> Project: Libcloud
>  Issue Type: Bug
> Environment: Linux
>Reporter: Erik Johnson
>
> When simplejson 2.0.9 (the version available in RHEL 6) is installed, the 
> following traceback occurs when attempting to use libcloud:
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/salt/loader.py", line 951, in 
> _load_module
> ), fn_, fpath, desc)
>   File "/usr/lib/python2.6/site-packages/salt/cloud/clouds/rackspace.py", 
> line 46, in 
> from libcloud.compute.base import NodeState
>   File "/usr/lib/python2.6/site-packages/libcloud/compute/base.py", line 32, 
> in 
> from libcloud.pricing import get_size_price
>   File "/usr/lib/python2.6/site-packages/libcloud/pricing.py", line 26, in 
> 
> JSONDecodeError = json.JSONDecodeError
> AttributeError: 'module' object has no attribute 'JSONDecodeError'
> Upgrading to simplejson 2.1.0 or greater fixes this issue. Applying the 
> following fix to libcloud should resolve the issue: 
> http://www.fpaste.org/225608/49936143/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-737) Create Dimension Data Load Balancing driver

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14721506#comment-14721506
 ] 

ASF subversion and git services commented on LIBCLOUD-737:
--

Commit 06b11e8a30515faa50af163697ba5a39de133445 in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=06b11e8 ]

[LIBCLOUD-737] Pad it out.


 Create Dimension Data Load Balancing driver
 ---

 Key: LIBCLOUD-737
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-737
 Project: Libcloud
  Issue Type: Improvement
  Components: LoadBalancer
Reporter: Anthony Shaw
   Original Estimate: 48h
  Remaining Estimate: 48h

 Create a driver for the Dimension Data VIP functionality in MCP 2.0 data 
 centers that mirrors the LoadBalancer Driver in libcloud. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-735) AuroraDNS driver

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715385#comment-14715385
 ] 

ASF subversion and git services commented on LIBCLOUD-735:
--

Commit 810d3ad9cf9ec599602cb505d8adb240ccedc1ea in libcloud's branch 
refs/heads/trunk from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=810d3ad ]

LIBCLOUD-735: Implementation of AuroraDNS driver

AuroraDNS is the new DNS product of PCextreme under the cloud name 'Aurora'.

Closes #563

Signed-off-by: Tomaz Muraus to...@tomaz.me


 AuroraDNS driver
 

 Key: LIBCLOUD-735
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-735
 Project: Libcloud
  Issue Type: New Feature
  Components: DNS
Reporter: Wido den Hollander
  Labels: aurora, dns, driver, pcextreme

 AuroraDNS is a soon to be launched product from PCextreme B.V. which adds DNS 
 to their cloud portfolio which is named Aurora.
 The REST API has been stabilized and this issue is for the addition of 
 AuroraDNS to libcloud.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-730) add 'fault' to node.extra in openstack node driver

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14650236#comment-14650236
 ] 

ASF subversion and git services commented on LIBCLOUD-730:
--

Commit 97e5e8403c85db0374ce2cb2935382d09f9b1301 in libcloud's branch 
refs/heads/trunk from [~nfox]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=97e5e84 ]

Add instance fault to OpenStack_NodeDriver

`InstanceFault` is returned by the API but is not saved in the 
`OpenStack_1_1_NodeDriver.extra` field. Adding `fault` to the `extra` field.
(https://issues.apache.org/jira/browse/LIBCLOUD-730)

Signed-off-by: Tomaz Muraus to...@apache.org


 add 'fault' to node.extra in openstack node driver
 --

 Key: LIBCLOUD-730
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-730
 Project: Libcloud
  Issue Type: Bug
  Components: Compute
Reporter: Nick Fox
Priority: Minor
  Labels: easyfix

 The `OpenStack_1_1_NodeDriver` does not return `fault` in 
 `OpenStack_1_1_NodeDriver.extra` yet it is returned from the api. Fault gives 
 information on why a server is in error state if the server reached an error 
 state. It is an [instance 
 fault|https://github.com/openstack/nova/blob/4cf6ef68199183697a0209751575f88fe5b2a733/nova/objects/instance_fault.py].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-719) AuroraObjects storage driver

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612948#comment-14612948
 ] 

ASF subversion and git services commented on LIBCLOUD-719:
--

Commit 6edeeaff6514ee9d1e8e65ad0dba65a70da0a067 in libcloud's branch 
refs/heads/trunk from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=6edeeaf ]

LIBCLOUD-719: AuroraObjects storage driver

AuroraObjects is a object store compatible with Amazon S3.

The driver extends the Amazon S3 driver and overwrites the host pointing
it towards the AuroraObjects servers in the European Union.

Signed-off-by: Sebastien Goasguen run...@gmail.com

This closes #540


 AuroraObjects storage driver
 

 Key: LIBCLOUD-719
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-719
 Project: Libcloud
  Issue Type: New Feature
  Components: Storage
Reporter: Wido den Hollander

 PCextreme offers a Amazon S3 compatible object store under the name 
 AuroraObjects.
 It is based on Ceph and uses Varnish for caching frequently accessed objects.
 Libcloud storage driver support would be a extension of the Amazon S3 storage 
 driver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-681) Google DNS: Allow for multiple additions and/or deletions of Resource Record Sets in one call

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14556361#comment-14556361
 ] 

ASF subversion and git services commented on LIBCLOUD-681:
--

Commit c3fd03c658a37772f61ebc42c414f3e88d59f4e3 in libcloud's branch 
refs/heads/trunk from [~smstone]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=c3fd03c ]

[google dns] LIBCLOUD-681: Allow for multiple record changes in one call

Closes #526

Signed-off-by: Eric Johnson erjoh...@google.com


 Google DNS: Allow for multiple additions and/or deletions of Resource Record 
 Sets in one call
 -

 Key: LIBCLOUD-681
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-681
 Project: Libcloud
  Issue Type: New Feature
  Components: DNS
Reporter: Steven Stone
Assignee: Eric Johnson

 Currently the {{libcloud.dns.drivers.google}} module only supports creating 
 or deleting one DNS record at a time. It is very time consuming with the 
 current {{create_record}} and {{delete_record}} methods to migrate a 
 substantial amount of DNS records.
 The [Google Cloud DNS 
 API|https://cloud.google.com/dns/api/v1beta1/changes#resource] supports 
 sending multiple additions and/or deletions to resource record sets in one 
 call, so there should be a corresponding method that supports this 
 functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-712) EC2 driver modifies region details

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545501#comment-14545501
 ] 

ASF subversion and git services commented on LIBCLOUD-712:
--

Commit 59cfd4fda8bde20a6d9b9f8e18703115c0fe0105 in libcloud's branch 
refs/heads/trunk from [~henkslaaf]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=59cfd4f ]

Merge LIBCLOUD-712_fix-ec2-sigver into trunk

closes #712


 EC2 driver modifies region details
 --

 Key: LIBCLOUD-712
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-712
 Project: Libcloud
  Issue Type: Bug
  Components: Compute
Reporter: Maarten van Schaik

 When creating an EC2 connection, the signature version is taken from the 
 region details using a pop-operation. This modifies the configuration: 
 subsequent connections will not have the signature version available and will 
 fall back to version 2.
 Example:
 {code}
 from libcloud.compute.drivers.ec2 import EC2NodeDriver
 drv = EC2NodeDriver('abc', region='eu-central-1')
 print drv.signature_version
 drv2 = EC2NodeDriver('abc', region='eu-central-1')
 print drv2.signature_version
 {code}
 Prints:
 {code}
 4
 2
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-687) Unable to set GCE metadata if no metadata already exists

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542681#comment-14542681
 ] 

ASF subversion and git services commented on LIBCLOUD-687:
--

Commit aaa8e9e3a3a73d44aa6632089d60e8806f0f2de4 in libcloud's branch 
refs/heads/trunk from [~erjohnso]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=aaa8e9e ]

[google compute] Fixes LIBCLOUD-687: handle empty project metadata

Closes #521

Signed-off-by: Eric Johnson erjoh...@google.com


 Unable to set GCE metadata if no metadata already exists
 

 Key: LIBCLOUD-687
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-687
 Project: Libcloud
  Issue Type: Bug
  Components: Compute
Reporter: Eli Courtwright
Assignee: Eric Johnson

 The {{libcloud.compute.drivers.gce.GCENodeDriver}} class has a nonstandard 
 method {{ex_set_common_metadata}} which we can use to (among other things) 
 set SSH keys.
 When calling this method on the latest libcloud 0.17.0 (which is not 
 currently a listed version in Jira), I get the following error:
 {code}
  conn.ex_set_common_instance_metadata({})
 Traceback (most recent call last):
   File stdin, line 1, in module
   File 
 /opt/sideboard/lib/python2.7/site-packages/libcloud/compute/drivers/gce.py, 
 line 1129, in ex_set_common_instance_metadata
 for md in current_metadata['items']:
 KeyError: 'items'
 {code}
 I get this error regardless of what data I pass to the 
 {{ex_set_common_instance_metadata}} method.  From delving into the libcloud 
 code, I find the following block of code:
 {code}
 project = self.ex_get_project()
 current_metadata = project.extra['commonInstanceMetadata']
 fingerprint = current_metadata['fingerprint']
 # grab copy of current 'sshKeys' in case we want to retain them
 current_keys = 
 for md in current_metadata['items']:
 {code}
 So it looks as if the method assumes that {{self.ex_get_project()}} will 
 return:
 - an object with a {{.extra}} dictionary (which it does)
 - that dictionary will have a commonInstanceMetadata key which maps to 
 another dictionary (which is correct)
 - that sub-dictionary will have an items key whose value is iterable (which 
 is wrong)
 That last assumption is only wrong if there is no project metadata already 
 associated with the project, e.g. for a new project.
 I'm working around this problem currently by monkeypatching libcloud:
 {code}
 def patch_gce_ex_get_project():
 orig_get_project = GCENodeDriver.ex_get_project
 def ex_get_project(self):
 project = orig_get_project(self)
 project.extra['commonInstanceMetadata'].setdefault('items', [])
 return project
 GCENodeDriver.ex_get_project = ex_get_project
 {code}
 but having a real fix would be great for the next version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-697) GCE Compute driver create_node does not accept str for ex_boot_disk

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542590#comment-14542590
 ] 

ASF subversion and git services commented on LIBCLOUD-697:
--

Commit 8664118c877a43f1434a576bd46223707589b078 in libcloud's branch 
refs/heads/trunk from [~erjohnso]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=8664118 ]

[google compute] fixes LIBCLOUD-697: allow string for ex_boot_disk on 
create_node

Closes #520

Signed-off-by: Eric Johnson erjoh...@google.com


 GCE Compute driver create_node does not accept str for ex_boot_disk
 ---

 Key: LIBCLOUD-697
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-697
 Project: Libcloud
  Issue Type: Bug
  Components: Compute
Reporter: Jason DeTiberus
Assignee: Eric Johnson

 The documentation for the GCE compute driver states that the ex_boot_disk 
 param for create_node takes either a StorageVolume or str.  If you pass a 
 string, it results in the following traceback:
 {code:none}
 failed: [localhost] = {failed: true, parsed: false}
 Traceback (most recent call last):
   File 
 /home/jdetiber/.ansible/tmp/ansible-tmp-1429541392.81-113800638314850/gce, 
 line 2278, in module
 main()
   File 
 /home/jdetiber/.ansible/tmp/ansible-tmp-1429541392.81-113800638314850/gce, 
 line 577, in main
 module.exit_json(**(node_mgr.execute()))
   File 
 /home/jdetiber/.ansible/tmp/ansible-tmp-1429541392.81-113800638314850/gce, 
 line 352, in execute
 metadata)
   File 
 /home/jdetiber/.ansible/tmp/ansible-tmp-1429541392.81-113800638314850/gce, 
 line 461, in create_instances_by_names
 lc_network, lc_zone, metadata)
   File 
 /home/jdetiber/.ansible/tmp/ansible-tmp-1429541392.81-113800638314850/gce, 
 line 433, in create_instance_by_name
 ex_nic_gce_struct=nics
   File /usr/lib/python2.7/site-packages/libcloud/compute/drivers/gce.py, 
 line 2202, in create_node
 ex_automatic_restart)
   File /usr/lib/python2.7/site-packages/libcloud/compute/drivers/gce.py, 
 line 4507, in _create_node_req
 'deviceName': boot_disk.name,
 AttributeError: 'str' object has no attribute 'name'
 {code}
 The issue appears to be that create_node is passing the ex_boot_disk argument 
 directly to _create_node_req (where the boot_disk param expects a 
 StorageVolume or None).
 Either the docs need to be updated or create_node should instantiate a 
 StorageVolume from ex_boot_disk if it is a str.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-696) GCE Compute driver returns null for image.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542824#comment-14542824
 ] 

ASF subversion and git services commented on LIBCLOUD-696:
--

Commit 1e3d3cbc6fcc6f3cc862da31b9e17ca5450b95f6 in libcloud's branch 
refs/heads/trunk from [~erjohnso]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=1e3d3cb ]

[google compute] LIBCLOUD-696: improve node image detection

Closes #522

Signed-off-by: Eric Johnson erjoh...@google.com


 GCE Compute driver returns null for image.
 --

 Key: LIBCLOUD-696
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-696
 Project: Libcloud
  Issue Type: Bug
  Components: Compute
Reporter: Jason DeTiberus
Assignee: Eric Johnson

 The GCE Compute driver is currently returning null for image.  The issue 
 appears to be related to a change in the data returned from the api.
 In libcloud/compute/drivers/gce.py:
 {code:none|title=_to_node}
 extra['image'] = node.get('image')
 ...
 for disk in extra['disks']:
 if disk.get('boot') and disk.get('type') == 'PERSISTENT':
 bd = self._get_components_from_path(disk['source'])
 extra['boot_disk'] = self.ex_get_volume(bd['name'], bd['zone'])
 extra['image'] = bd['name']
 ...
 if extra['image']:
 image = self._get_components_from_path(extra['image'])['name']
 else:
 image = None
 {code}
 This looks like it should be:
 {code:none}
 for disk in extra['disks']:
 if disk.get('boot') and disk.get('type') == 'PERSISTENT':
 bd = self._get_components_from_path(disk['source'])
 extra['boot_disk'] = self.ex_get_volume(bd['name'], bd['zone'])
 extra['image'] = bd['name']
 ...
 if extra['image']:
 image = self._get_components_from_path(extra['image'])['name']
 else:
 image = None
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-698) Rename OpSource driver Dimension Data

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530510#comment-14530510
 ] 

ASF subversion and git services commented on LIBCLOUD-698:
--

Commit 119c1903e5309ac9efef6a1d1df7ac13789ad11c in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=119c190 ]

LIBCLOUD-698 rename OpSource Dimension Data. Added Dimension Data driver.

LIBCLOUD-698 Added provider type for dimension data

LIBCLOUD-698 Added missing text fixtures and test parameters

LIBCLOUD-698 Reformatted lines as DimensionData is quite a long string, PEP8 
compliance completed.

LIBCLOUD-698 worked through casing changes from original opsource driver, 
replaced kwargs with named parameters as per libcloud BP.

LIBCLOUD-698 Added some documentation of the driver

LIBCLOUD-698 Added indexes and support matrix for the driver

Closes #507

Signed-off-by: Tomaz Muraus to...@apache.org


 Rename OpSource driver Dimension Data
 -

 Key: LIBCLOUD-698
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-698
 Project: Libcloud
  Issue Type: New Feature
  Components: Compute
Reporter: Anthony Shaw
Priority: Minor
 Attachments: patch.diff


 The OpSource driver needs to be renamed to Dimension Data, since OpSource was 
 acquired in 2011. Dimension Data have renamed the platform and added 
 multi-geo support.
 This feature request is a placeholder for extensions to support 
 multi-geography and rename the driver.
 Dimension Data will work on the fork and present back the branch to the team 
 on completion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-698) Rename OpSource driver Dimension Data

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530509#comment-14530509
 ] 

ASF subversion and git services commented on LIBCLOUD-698:
--

Commit 119c1903e5309ac9efef6a1d1df7ac13789ad11c in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=119c190 ]

LIBCLOUD-698 rename OpSource Dimension Data. Added Dimension Data driver.

LIBCLOUD-698 Added provider type for dimension data

LIBCLOUD-698 Added missing text fixtures and test parameters

LIBCLOUD-698 Reformatted lines as DimensionData is quite a long string, PEP8 
compliance completed.

LIBCLOUD-698 worked through casing changes from original opsource driver, 
replaced kwargs with named parameters as per libcloud BP.

LIBCLOUD-698 Added some documentation of the driver

LIBCLOUD-698 Added indexes and support matrix for the driver

Closes #507

Signed-off-by: Tomaz Muraus to...@apache.org


 Rename OpSource driver Dimension Data
 -

 Key: LIBCLOUD-698
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-698
 Project: Libcloud
  Issue Type: New Feature
  Components: Compute
Reporter: Anthony Shaw
Priority: Minor
 Attachments: patch.diff


 The OpSource driver needs to be renamed to Dimension Data, since OpSource was 
 acquired in 2011. Dimension Data have renamed the platform and added 
 multi-geo support.
 This feature request is a placeholder for extensions to support 
 multi-geography and rename the driver.
 Dimension Data will work on the fork and present back the branch to the team 
 on completion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-698) Rename OpSource driver Dimension Data

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530511#comment-14530511
 ] 

ASF subversion and git services commented on LIBCLOUD-698:
--

Commit 119c1903e5309ac9efef6a1d1df7ac13789ad11c in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=119c190 ]

LIBCLOUD-698 rename OpSource Dimension Data. Added Dimension Data driver.

LIBCLOUD-698 Added provider type for dimension data

LIBCLOUD-698 Added missing text fixtures and test parameters

LIBCLOUD-698 Reformatted lines as DimensionData is quite a long string, PEP8 
compliance completed.

LIBCLOUD-698 worked through casing changes from original opsource driver, 
replaced kwargs with named parameters as per libcloud BP.

LIBCLOUD-698 Added some documentation of the driver

LIBCLOUD-698 Added indexes and support matrix for the driver

Closes #507

Signed-off-by: Tomaz Muraus to...@apache.org


 Rename OpSource driver Dimension Data
 -

 Key: LIBCLOUD-698
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-698
 Project: Libcloud
  Issue Type: New Feature
  Components: Compute
Reporter: Anthony Shaw
Priority: Minor
 Attachments: patch.diff


 The OpSource driver needs to be renamed to Dimension Data, since OpSource was 
 acquired in 2011. Dimension Data have renamed the platform and added 
 multi-geo support.
 This feature request is a placeholder for extensions to support 
 multi-geography and rename the driver.
 Dimension Data will work on the fork and present back the branch to the team 
 on completion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-698) Rename OpSource driver Dimension Data

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530512#comment-14530512
 ] 

ASF subversion and git services commented on LIBCLOUD-698:
--

Commit 119c1903e5309ac9efef6a1d1df7ac13789ad11c in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=119c190 ]

LIBCLOUD-698 rename OpSource Dimension Data. Added Dimension Data driver.

LIBCLOUD-698 Added provider type for dimension data

LIBCLOUD-698 Added missing text fixtures and test parameters

LIBCLOUD-698 Reformatted lines as DimensionData is quite a long string, PEP8 
compliance completed.

LIBCLOUD-698 worked through casing changes from original opsource driver, 
replaced kwargs with named parameters as per libcloud BP.

LIBCLOUD-698 Added some documentation of the driver

LIBCLOUD-698 Added indexes and support matrix for the driver

Closes #507

Signed-off-by: Tomaz Muraus to...@apache.org


 Rename OpSource driver Dimension Data
 -

 Key: LIBCLOUD-698
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-698
 Project: Libcloud
  Issue Type: New Feature
  Components: Compute
Reporter: Anthony Shaw
Priority: Minor
 Attachments: patch.diff


 The OpSource driver needs to be renamed to Dimension Data, since OpSource was 
 acquired in 2011. Dimension Data have renamed the platform and added 
 multi-geo support.
 This feature request is a placeholder for extensions to support 
 multi-geography and rename the driver.
 Dimension Data will work on the fork and present back the branch to the team 
 on completion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-698) Rename OpSource driver Dimension Data

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530507#comment-14530507
 ] 

ASF subversion and git services commented on LIBCLOUD-698:
--

Commit 119c1903e5309ac9efef6a1d1df7ac13789ad11c in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=119c190 ]

LIBCLOUD-698 rename OpSource Dimension Data. Added Dimension Data driver.

LIBCLOUD-698 Added provider type for dimension data

LIBCLOUD-698 Added missing text fixtures and test parameters

LIBCLOUD-698 Reformatted lines as DimensionData is quite a long string, PEP8 
compliance completed.

LIBCLOUD-698 worked through casing changes from original opsource driver, 
replaced kwargs with named parameters as per libcloud BP.

LIBCLOUD-698 Added some documentation of the driver

LIBCLOUD-698 Added indexes and support matrix for the driver

Closes #507

Signed-off-by: Tomaz Muraus to...@apache.org


 Rename OpSource driver Dimension Data
 -

 Key: LIBCLOUD-698
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-698
 Project: Libcloud
  Issue Type: New Feature
  Components: Compute
Reporter: Anthony Shaw
Priority: Minor
 Attachments: patch.diff


 The OpSource driver needs to be renamed to Dimension Data, since OpSource was 
 acquired in 2011. Dimension Data have renamed the platform and added 
 multi-geo support.
 This feature request is a placeholder for extensions to support 
 multi-geography and rename the driver.
 Dimension Data will work on the fork and present back the branch to the team 
 on completion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (LIBCLOUD-698) Rename OpSource driver Dimension Data

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LIBCLOUD-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530508#comment-14530508
 ] 

ASF subversion and git services commented on LIBCLOUD-698:
--

Commit 119c1903e5309ac9efef6a1d1df7ac13789ad11c in libcloud's branch 
refs/heads/trunk from [~anthonypjshaw]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=119c190 ]

LIBCLOUD-698 rename OpSource Dimension Data. Added Dimension Data driver.

LIBCLOUD-698 Added provider type for dimension data

LIBCLOUD-698 Added missing text fixtures and test parameters

LIBCLOUD-698 Reformatted lines as DimensionData is quite a long string, PEP8 
compliance completed.

LIBCLOUD-698 worked through casing changes from original opsource driver, 
replaced kwargs with named parameters as per libcloud BP.

LIBCLOUD-698 Added some documentation of the driver

LIBCLOUD-698 Added indexes and support matrix for the driver

Closes #507

Signed-off-by: Tomaz Muraus to...@apache.org


 Rename OpSource driver Dimension Data
 -

 Key: LIBCLOUD-698
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-698
 Project: Libcloud
  Issue Type: New Feature
  Components: Compute
Reporter: Anthony Shaw
Priority: Minor
 Attachments: patch.diff


 The OpSource driver needs to be renamed to Dimension Data, since OpSource was 
 acquired in 2011. Dimension Data have renamed the platform and added 
 multi-geo support.
 This feature request is a placeholder for extensions to support 
 multi-geography and rename the driver.
 Dimension Data will work on the fork and present back the branch to the team 
 on completion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)