Support for specific python-novaclient version

[ctria]

Hello,

Is there a reason why the dependencies are limited to python-novaclient==2.27.0?

I'm one of the maintainers of this package for Fedora and that dependency prevents me from being able to update it to the latest release given that fedora uses python-novaclient 3.3.1 currently.

Is there any (extended?) test suite I can run if I want to remove that strict dependency to a "python-novaclient>=2.27.0"?

I'm tagging @sivel to this as it looks like he enforced this on 1.9.7.

Cheers,
Christos

[briancurtin]

We're not actively developing Pyrax and don't intend to move with novaclient changes.

[EmanNo1]

If Pyrax is not being developed, what should I use in it's place?

[briancurtin]

@EmanNo1 rackspacesdk (which is built on openstacksdk). I don't have docs up for anything Rackspace specific at the moment, but the rackspacesdk PyPI page will get you started with connecting to your Rackspace account, and the general OpenStack SDK docs are relatively complete.

Right now you can use Cloud Servers, Cloud Files, Cloud Networks, Cloud Backup, Cloud Monitoring, some of Cloud Databases and Cloud Block Storage, and I think that's it for right now. It's not at feature parity with Pyrax as it stands, but that's what I'm working towards. We're pretty close to a 1.0 release of the upstream openstacksdk project, after which I'm going to work towards rounding on the Rackspace specifics in the rackspacesdk extension.

[chrismeyersfsu]

Please reconsider. The version pinned does not allow for shade to be installed along side pyrax https://github.com/openstack-infra/shade/blob/1.13.1/requirements.txt

[EdLeafe]

I have a fix posted to my fork - all you really need to update is pyrax/__init__.py.

https://github.com/EdLeafe/pyrax

I've only briefly tested it, but it seems to work for me. And apologies for the poor way the transition to the OpenStack SDK has been handled. I had no idea that pyrax users would ever be left hanging like this.

[erikmack]

Openstack SDK is unusable.

conn.object_store.upload_object(data="huge in-memory blob")

... is an unacceptable API. Please fix pyrax or fix openstacksdk. I'm trying to publish changes to a static website in cloud files, and there seems to be no python way to do it anymore.

[briancurtin]

File a bug at https://bugs.launchpad.net/python-openstacksdk if you have specific comments about how that library works, or https://github.com/rackerlabs/rackspace-sdk-plugin if it's Rackspace specific (as I'm not familiar with static websites in cloud files).

[ssbarnea]

It seems that current "policy" of not updating pyrax dependencies make it a time-bomb. As of today this package cannot be installed without breaking almost anything possible related to openstack.

Yes we know that virtualenv is supposed to isolate but this does not work if consumers do already need to use other openstack libraries.

If there is no desired to update dependencies the least you can do is to embed these dependencies into pyrax distributions and avoid to install them (using them as submodules), this would avoid creating conflicts.

[EdLeafe]

I still follow the issues with pyrax, even though I haven't worked for Rackspace in 3 years. It really saddens me to see people left hanging. So:

https://blog.leafe.com/fanatical-support/

That blog post documents the history behind these problems, and my desire to help. Since Rackspace has made it clear that they do not care enough to make even this minor change, you should probably not waste your breath here, and instead work from my fork:

https://github.com/EdLeafe/pyrax

I've already posted the change to that fork that unpins novaclient. If you have any other pull requests or bug issues, I will do my best to help out. Please keep in mind that this is no longer the job I am paid to do by my employer, so turnaround will be variable at best.

[ssbarnea]

@EdLeafe Maybe moving the package under https://github.com/pycontribs/pyrax umbrella would be safer way to assure it may receive some hotfixes (like this one) if needed.

We need to get at least two people with rights to release new versions on pypi. My PYPI username is sorin in case someone can add me as a maintainer.

It seems that at this moment the only PYPI account that can release are brian.curtin and sivel.

[briancurtin]

@ssbarnea I added sorin as a maintainer on PyPI. @sivel is currently out on sabbatical and won't be checking work or github emails until later this month, so I'm leaving him in for right now. When he comes back, if he isn't working on pyrax either, then we'll find someone to take over the package with owner status.

Transferring this to https://github.com/pycontribs/pyrax is fine, but you can't transfer a repo to an account with the same name, so if you want this there then email me at brian@python.org and we can orchestrate that.

[EdLeafe]

@ssbarnea Sure, that's fine. As long as users are not hung out to dry as before.

[ssbarnea]

I will rename pycontribs/pyrax to pyrax_old so owner can perform repo move. I think I can do it today or during the weekend. I will update when I finish my lunch :)

[cardoe]

So the change @EdLeafe was talking about appears to be EdLeafe@0f2dba6