[requirements][kuryr][flame] openshift dificulties
Openshift upstream is giving us difficulty as they are capping the version of urllib3 and kubernetes we are using.
-urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1
I've opened an issue with them but not had much luck there (and their prefered solution just pushes the can down the road).
https://github.com/openshift/openshift-restclient-python/issues/289
What I'd us to do is move off of openshift as our usage doesn't seem too much.
openstack/kuryr-tempest-plugin uses it for one import (and just one function with that import). I'm not sure exactly what you are doing with it but would it be too much to ask to move to something else?
x/flame has it in it's constraints but I don't see any actual usage, so perhaps it's a false flag.
Please let me know what you think
On Wed, May 29, 2019, at 1:54 PM, Matthew Thode wrote:
Openshift upstream is giving us difficulty as they are capping the version of urllib3 and kubernetes we are using.
-urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1
I've opened an issue with them but not had much luck there (and their prefered solution just pushes the can down the road).
https://github.com/openshift/openshift-restclient-python/issues/289
What I'd us to do is move off of openshift as our usage doesn't seem too much.
openstack/kuryr-tempest-plugin uses it for one import (and just one function with that import). I'm not sure exactly what you are doing with it but would it be too much to ask to move to something else?
x/flame has it in it's constraints but I don't see any actual usage, so perhaps it's a false flag.
Please let me know what you think
I think part of the issue here is that the kubernetes lib is generated code and not "curated" with backward compatibility in mind. That said it is worth noting that the infra team found that openshift lib + kubernetes lib < 9.0 does not work with the ansible k8s modules (there is a bug in the blocking calls which causes them to go out to lunch and never return). Depending on where we pull these libraries in we may need to override anyway for things to function at all.
Clark
On Wed, 2019-05-29 at 15:53 -0500, Matthew Thode wrote:
Openshift upstream is giving us difficulty as they are capping the version of urllib3 and kubernetes we are using.
-urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1
I've opened an issue with them but not had much luck there (and their prefered solution just pushes the can down the road).
https://github.com/openshift/openshift-restclient-python/issues/289
What I'd us to do is move off of openshift as our usage doesn't seem too much.
openstack/kuryr-tempest-plugin uses it for one import (and just one function with that import). I'm not sure exactly what you are doing with it but would it be too much to ask to move to something else?
From Kuryr side it's not really much effort, we can switch to bare REST
calls, but obviously we prefer the client. If there's much support for getting rid of it, we can do the switch.
x/flame has it in it's constraints but I don't see any actual usage, so perhaps it's a false flag.
Please let me know what you think
On 19-05-30 17:07:54, Michał Dulko wrote:
On Wed, 2019-05-29 at 15:53 -0500, Matthew Thode wrote:
Openshift upstream is giving us difficulty as they are capping the version of urllib3 and kubernetes we are using.
-urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1
I've opened an issue with them but not had much luck there (and their prefered solution just pushes the can down the road).
https://github.com/openshift/openshift-restclient-python/issues/289
What I'd us to do is move off of openshift as our usage doesn't seem too much.
openstack/kuryr-tempest-plugin uses it for one import (and just one function with that import). I'm not sure exactly what you are doing with it but would it be too much to ask to move to something else?
From Kuryr side it's not really much effort, we can switch to bare REST calls, but obviously we prefer the client. If there's much support for getting rid of it, we can do the switch.
Right now Kyryr is only using it in that one place and it's blocking the update of urllib3 and kubernetes for the rest of openstack. So if it's not too much trouble it'd be nice to have happen.
x/flame has it in it's constraints but I don't see any actual usage, so perhaps it's a false flag.
Please let me know what you think
On 19-05-30 10:17:39, Matthew Thode wrote:
On 19-05-30 17:07:54, Michał Dulko wrote:
On Wed, 2019-05-29 at 15:53 -0500, Matthew Thode wrote:
Openshift upstream is giving us difficulty as they are capping the version of urllib3 and kubernetes we are using.
-urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1
I've opened an issue with them but not had much luck there (and their prefered solution just pushes the can down the road).
https://github.com/openshift/openshift-restclient-python/issues/289
What I'd us to do is move off of openshift as our usage doesn't seem too much.
openstack/kuryr-tempest-plugin uses it for one import (and just one function with that import). I'm not sure exactly what you are doing with it but would it be too much to ask to move to something else?
From Kuryr side it's not really much effort, we can switch to bare REST calls, but obviously we prefer the client. If there's much support for getting rid of it, we can do the switch.
Right now Kyryr is only using it in that one place and it's blocking the update of urllib3 and kubernetes for the rest of openstack. So if it's not too much trouble it'd be nice to have happen.
x/flame has it in it's constraints but I don't see any actual usage, so perhaps it's a false flag.
Please let me know what you think
Any updates on this? I'd like to move forward on removing the dependency if possible.
On Wed, 2019-06-05 at 11:58 -0500, Matthew Thode wrote:
On 19-05-30 10:17:39, Matthew Thode wrote:
On 19-05-30 17:07:54, Michał Dulko wrote:
On Wed, 2019-05-29 at 15:53 -0500, Matthew Thode wrote:
Openshift upstream is giving us difficulty as they are capping the version of urllib3 and kubernetes we are using.
-urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1
I've opened an issue with them but not had much luck there (and their prefered solution just pushes the can down the road).
https://github.com/openshift/openshift-restclient-python/issues/289
What I'd us to do is move off of openshift as our usage doesn't seem too much.
openstack/kuryr-tempest-plugin uses it for one import (and just one function with that import). I'm not sure exactly what you are doing with it but would it be too much to ask to move to something else?
From Kuryr side it's not really much effort, we can switch to bare REST calls, but obviously we prefer the client. If there's much support for getting rid of it, we can do the switch.
Right now Kyryr is only using it in that one place and it's blocking the update of urllib3 and kubernetes for the rest of openstack. So if it's not too much trouble it'd be nice to have happen.
x/flame has it in it's constraints but I don't see any actual usage, so perhaps it's a false flag.
Please let me know what you think
Any updates on this? I'd like to move forward on removing the dependency if possible.
Sure, I'm waiting for some spare time to do this. Fastest it may happen will probably be next week.
On 19-06-06 09:13:46, Michał Dulko wrote:
On Wed, 2019-06-05 at 11:58 -0500, Matthew Thode wrote:
On 19-05-30 10:17:39, Matthew Thode wrote:
On 19-05-30 17:07:54, Michał Dulko wrote:
On Wed, 2019-05-29 at 15:53 -0500, Matthew Thode wrote:
Openshift upstream is giving us difficulty as they are capping the version of urllib3 and kubernetes we are using.
-urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1
I've opened an issue with them but not had much luck there (and their prefered solution just pushes the can down the road).
https://github.com/openshift/openshift-restclient-python/issues/289
What I'd us to do is move off of openshift as our usage doesn't seem too much.
openstack/kuryr-tempest-plugin uses it for one import (and just one function with that import). I'm not sure exactly what you are doing with it but would it be too much to ask to move to something else?
From Kuryr side it's not really much effort, we can switch to bare REST calls, but obviously we prefer the client. If there's much support for getting rid of it, we can do the switch.
Right now Kyryr is only using it in that one place and it's blocking the update of urllib3 and kubernetes for the rest of openstack. So if it's not too much trouble it'd be nice to have happen.
x/flame has it in it's constraints but I don't see any actual usage, so perhaps it's a false flag.
Please let me know what you think
Any updates on this? I'd like to move forward on removing the dependency if possible.
Sure, I'm waiting for some spare time to do this. Fastest it may happen will probably be next week.
Sounds good, thanks for working on it.
On Thu, 2019-06-06 at 09:17 -0500, Matthew Thode wrote:
On 19-06-06 09:13:46, Michał Dulko wrote:
On Wed, 2019-06-05 at 11:58 -0500, Matthew Thode wrote:
On 19-05-30 10:17:39, Matthew Thode wrote:
On 19-05-30 17:07:54, Michał Dulko wrote:
On Wed, 2019-05-29 at 15:53 -0500, Matthew Thode wrote:
Openshift upstream is giving us difficulty as they are capping the version of urllib3 and kubernetes we are using.
-urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1
I've opened an issue with them but not had much luck there (and their prefered solution just pushes the can down the road).
https://github.com/openshift/openshift-restclient-python/issues/289
What I'd us to do is move off of openshift as our usage doesn't seem too much.
openstack/kuryr-tempest-plugin uses it for one import (and just one function with that import). I'm not sure exactly what you are doing with it but would it be too much to ask to move to something else?
From Kuryr side it's not really much effort, we can switch to bare REST calls, but obviously we prefer the client. If there's much support for getting rid of it, we can do the switch.
Right now Kyryr is only using it in that one place and it's blocking the update of urllib3 and kubernetes for the rest of openstack. So if it's not too much trouble it'd be nice to have happen.
x/flame has it in it's constraints but I don't see any actual usage, so perhaps it's a false flag.
Please let me know what you think
Any updates on this? I'd like to move forward on removing the dependency if possible.
Sure, I'm waiting for some spare time to do this. Fastest it may happen will probably be next week.
Sounds good, thanks for working on it.
The patch [1] is up, let's see if my alternative approach haven't broke our gates. I'll ping you once it's merged so you can propose a patch removing openshift library from global-requirements.
participants (3)
-
Clark Boylan
-
Matthew Thode
-
Michał Dulko