[GitHub] libcloud pull request #867: StorageVolumeSnapshot now has a .name

[allardhoeve]

GitHub user allardhoeve opened a pull request:

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

StorageVolumeSnapshot now has a .name

## StorageVolumeSnapshot now has an attribute .name

### Description

StorageVolumeSnapshot is the last object that normally has a name, that 
does not actually have an attribute `.name`. This PR adds that attribute. It 
leaves the `.extra['name']` though, for backwards-compatibility.

### Status

- done, ready for review

### Checklist (tick everything that applies)

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



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

$ git pull https://github.com/ByteInternet/libcloud snapshot-has-name

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

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

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

This closes #867


commit 785ec4e2e7122871471a1112acb8eeb47cadcd88
Author: Allard Hoeve 
Date:   2016-09-23T14:30:57Z

StorageVolumeSnapshot now has a .name




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (LIBCLOUD-853) Openstack: allow a user to list availability zones

[Michel Samia (JIRA)]

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

Michel Samia updated LIBCLOUD-853:
--
Priority: Minor  (was: Major)

> Openstack: allow a user to list availability zones
> --
>
> Key: LIBCLOUD-853
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-853
> Project: Libcloud
>  Issue Type: Improvement
>  Components: Compute
>Reporter: Michel Samia
>Priority: Minor
>




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

[jira] [Created] (LIBCLOUD-853) Openstack: allow a user to list availability zones

[Michel Samia (JIRA)]

Michel Samia created LIBCLOUD-853:
-

 Summary: Openstack: allow a user to list availability zones
 Key: LIBCLOUD-853
 URL: https://issues.apache.org/jira/browse/LIBCLOUD-853
 Project: Libcloud
  Issue Type: Improvement
  Components: Compute
Reporter: Michel Samia






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

[GitHub] libcloud pull request #866: OS create_snapshot posts optional keywords only ...

[allardhoeve]

GitHub user allardhoeve opened a pull request:

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

OS create_snapshot posts optional keywords only when needed

## OS create_snapshot_volume does not post optional keywords if they are 
None

### Description

On never OpenStacks, posting None for `name` or `description` will return a 
400 Bad Request.

### Status

- done, ready for review

### Checklist (tick everything that applies)

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



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

$ git pull https://github.com/ByteInternet/libcloud fix-os-create-snapshot

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

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

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

This closes #866


commit e6e33b72604e337bf5317dbea573703cbdc3b983
Author: Allard Hoeve 
Date:   2016-09-23T10:23:52Z

OS create_snapshot posts optional keywords only when needed




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] libcloud pull request #865: Add ex_stop_node to OS driver

[allardhoeve]

GitHub user allardhoeve opened a pull request:

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

Add ex_stop_node to OS driver

## Add ex_stop_node to OS driver

### Description

Current OpenStack driver can suspend, but not stop a node. This PR adds 
that.

### Status

- done, ready for review

### Checklist (tick everything that applies)

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



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

$ git pull https://github.com/ByteInternet/libcloud fix-os-not-found

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

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

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

This closes #865


commit a93391fad40117a9e880c8e63d36816cb9e67646
Author: Allard Hoeve 
Date:   2016-09-23T09:07:26Z

Add ex_stop_node to OS driver




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---