[openstack-dev] [horizon][packaging] django-openstack-auth retirement
Hi, packaging teams and operators This mail is the announcement of retirement of django-openstack-auth python package in the Queens release. Horizon team merged the code of django-openstack-auth into the horizon repo mainly from the maintenance reason. For more detail, see the blueprint https://blueprints.launchpad.net/horizon/+spec/merge-openstack-auth. [To packaging teams] Ensure not to install django-openstack-auth in Queens horizon package. "openstack_auth" python module is now provided by horizon instead of django_openstack_auth. [To operators] If you install horizon and django-openstack-auth by using pip (instead of distribution packages), please uninstall django-openstack-auth python package before upgrading horizon. Otherwise, "openstack_auth" module is maintained by both horizon and django-openstack-auth after upgrading horizon and it confuses the pip file management, while horizon works. If you have questions, feel to reach the horizon team. Thanks, Akihiro __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement
On 2018-01-22 14:40:49 +0900 (+0900), Akihiro Motoki wrote: [...] > If you install horizon and django-openstack-auth by using pip (instead > of distribution packages), please uninstall django-openstack-auth > python package before upgrading horizon. > Otherwise, "openstack_auth" module is maintained by both horizon and > django-openstack-auth after upgrading horizon and it confuses the pip > file management, while horizon works. [...] If we were already publishing Horizon to PyPI, we could have a new (and final) major version of DOA as a transitional package to stop providing any module itself and depend on the new version of Horizon which provides that module instead. I suppose without Horizon on PyPI, documentation of the issue is the most we can do for this situation. -- Jeremy Stanley signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement
2018-01-22 20:30 GMT+09:00 Jeremy Stanley : > On 2018-01-22 14:40:49 +0900 (+0900), Akihiro Motoki wrote: > [...] >> If you install horizon and django-openstack-auth by using pip (instead >> of distribution packages), please uninstall django-openstack-auth >> python package before upgrading horizon. >> Otherwise, "openstack_auth" module is maintained by both horizon and >> django-openstack-auth after upgrading horizon and it confuses the pip >> file management, while horizon works. > [...] > > If we were already publishing Horizon to PyPI, we could have a new > (and final) major version of DOA as a transitional package to stop > providing any module itself and depend on the new version of Horizon > which provides that module instead. I suppose without Horizon on > PyPI, documentation of the issue is the most we can do for this > situation. Horizon usually does not publish its releases to PyPI, so I think what we can do is to document it. P.S. The only exceptions on PyPI horizon are 12.0.2 and 2012.2 releases. 12.0.2 was released last week but I don't know why it is available at PyPI. In deliverables/pike/horizon.yaml in the openstack/releases repo, we don't have "include-pypi-link: yes". Thanks, Akihiro __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement
On 2018-01-23 23:19:59 +0900 (+0900), Akihiro Motoki wrote: [...] > Horizon usually does not publish its releases to PyPI, so I think what > we can do is to document it. > > P.S. > The only exceptions on PyPI horizon are 12.0.2 and 2012.2 releases. > 12.0.2 was released last week but I don't know why it is available at > PyPI. In deliverables/pike/horizon.yaml in the openstack/releases > repo, we don't have "include-pypi-link: yes". [...] Right, my "if we were already" was a reference to the work under discussion to eventually get all OpenStack services publishing wheels and sdists on PyPI. There are still some logistical issues to be ironed out (e.g., the fact that we don't control the "keystone" entry there) so I doubt it'll happen before Queens releases but we might have it going sometime in the Rocky cycle. I was mostly just lamenting that it's not something we can take advantage of for the current DOA/Horizon transition. -- Jeremy Stanley signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement
On 01/24/2018 08:25 AM, Jeremy Stanley wrote: On 2018-01-23 23:19:59 +0900 (+0900), Akihiro Motoki wrote: [...] Horizon usually does not publish its releases to PyPI, so I think what we can do is to document it. P.S. The only exceptions on PyPI horizon are 12.0.2 and 2012.2 releases. 12.0.2 was released last week but I don't know why it is available at PyPI. In deliverables/pike/horizon.yaml in the openstack/releases repo, we don't have "include-pypi-link: yes". [...] Right, my "if we were already" was a reference to the work under discussion to eventually get all OpenStack services publishing wheels and sdists on PyPI. There are still some logistical issues to be ironed out (e.g., the fact that we don't control the "keystone" entry there) so I doubt it'll happen before Queens releases but we might have it going sometime in the Rocky cycle. I was mostly just lamenting that it's not something we can take advantage of for the current DOA/Horizon transition. Horizon and neutron were updated to start publishing to PyPI already. https://review.openstack.org/#/c/531822/ This is so that we can start working on unwinding the neutron and horizon specific versions of jobs for neutron and horizon plugins. Monty __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement
On 2018-01-24 08:47:30 -0600 (-0600), Monty Taylor wrote: [...] > Horizon and neutron were updated to start publishing to PyPI > already. > > https://review.openstack.org/#/c/531822/ > > This is so that we can start working on unwinding the neutron and > horizon specific versions of jobs for neutron and horizon plugins. Nice! I somehow missed that merging a couple of weeks back. In that case, I suppose we could in theory do one final transitional package upload of DOA depending on the conflicting Horizon release if others think that's a good idea. -- Jeremy Stanley signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement
2018-01-27 2:45 GMT+09:00 Jeremy Stanley : > On 2018-01-24 08:47:30 -0600 (-0600), Monty Taylor wrote: > [...] >> Horizon and neutron were updated to start publishing to PyPI >> already. >> >> https://review.openstack.org/#/c/531822/ >> >> This is so that we can start working on unwinding the neutron and >> horizon specific versions of jobs for neutron and horizon plugins. > > Nice! I somehow missed that merging a couple of weeks back. In that > case, I suppose we could in theory do one final transitional package > upload of DOA depending on the conflicting Horizon release if others > think that's a good idea. Thanks for clarification. Then, does it make sense to release django-openstack-auth 4.0.0 and require it in horizon queens? Note that the current latest version is 3.5.0 and older horizon dependency is django-openstack-auth>=3.5.0. Luckily enough, the requirement freeze is extended one week. -- Akihiro Motoki __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
