Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update references to novaclient 1.1 #594

Merged
merged 1 commit into from Jan 14, 2016
Merged

Conversation

EdLeafe
Copy link
Contributor

@EdLeafe EdLeafe commented Dec 21, 2015

Recent releases of novaclient removed the references to the v1.1 client.
This patch updates the import statements to refer to the v2 client, and
also updates the check for the 1.1 extensions. The required version for
python-novaclient has also been increased to use 2.27.0 as the minimum.

Recent releases of novaclient removed the references to the v1.1 client.
This patch updates the import statements to refer to the v2 client, and
also updates the check for the 1.1 extensions. The required version for
python-novaclient has also been increased to use 2.27.0 as the minimum.
@briancurtin
Copy link
Contributor

Looks alright, going to wait for @sivel to take a look.

@sivel
Copy link
Contributor

sivel commented Dec 21, 2015

I'll go ahead and assign this to myself. I likely will not get to it immediately, but I'll work on testing these changes and trying this out with the ansible integration tests as well.

@ChrisHacker
Copy link

@sivel That's fine, but this has been sitting here for almost a month. When will it be merged?

@sivel
Copy link
Contributor

sivel commented Jan 14, 2016

pyrax has been deprecated, and in a freeze. With another recently reported issue, I believe we will perform a release soon, to maintain functionality in Ansible. I will plan on including this fix and the other.

@ChrisHacker
Copy link

@sivel Is the OpenSDK ready for production use as its replacement? Last I checked, it wasn't. If it is, let me know. If not, as many others have previously noted, it's not a great idea to deprecate the library that everyone is using before releasing the new one and allowing for time to change over.

@briancurtin
Copy link
Contributor

It's not a 1:1 replacement yet, but it is relatively complete and down to a few things to add before it hits 1.0 -- this is speaking for the upstream OpenStack SDK. With that, things like Cloud Servers, Cloud Files, Cloud Networks, are pretty complete as far as covering the API goes, and they work well. Things like Cloud Monitoring, which are not OpenStack but are proprietary Rackspace products, are going to be added to the Rackspace plugin to OpenStack SDK, but we don't have a timeline available for them at the moment.

@ChrisHacker
Copy link

@briancurtin As a fellow dev I get juggling legacy while building the future, but mixing 'pretty complete' with deprecating the prior library doesn't seem to be in the same ballpark as fanatical customer service. Disappointing.

sivel added a commit that referenced this pull request Jan 14, 2016
Update references to novaclient 1.1
@sivel sivel merged commit 6c75e5f into pycontribs:working Jan 14, 2016
@sivel
Copy link
Contributor

sivel commented Jan 14, 2016

Merged Thanks. I am going to make one change, in that I am going to pin python-novaclient explicitly to 2.27.0. Because we allow the release to be >= I feel that is at least a partial cause that we have to keep updating things related to novaclient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants