Difference between revisions of "Meetings/Horizon"
< Meetings
(→Agenda for Next Meeting) |
(→Agenda for Next Meeting) |
||
Line 10: | Line 10: | ||
** http://lists.openstack.org/pipermail/openstack-dev/2017-October/124129.html | ** http://lists.openstack.org/pipermail/openstack-dev/2017-October/124129.html | ||
** https://blueprints.launchpad.net/horizon/+spec/fetch-resources-in-parallel | ** https://blueprints.launchpad.net/horizon/+spec/fetch-resources-in-parallel | ||
− | |||
− | |||
* Merge openstack-auth https://blueprints.launchpad.net/horizon/+spec/merge-openstack-auth (amotoki but he will not be able to join the meeting as usual) | * Merge openstack-auth https://blueprints.launchpad.net/horizon/+spec/merge-openstack-auth (amotoki but he will not be able to join the meeting as usual) |
Revision as of 13:28, 27 November 2017
The OpenStack Horizon Team holds public meetings in #openstack-meeting-3, weekly on Wednesdays at 2000 UTC.
See http://eavesdrop.openstack.org/#Horizon_Team_Meeting for recordings of previous meetings and the upcoming meeting schedule.
Everyone is encouraged to attend!
Agenda for Next Meeting
- Notices
- Fetch resources in parallel discussion (again) (e0ne)
- Merge openstack-auth https://blueprints.launchpad.net/horizon/+spec/merge-openstack-auth (amotoki but he will not be able to join the meeting as usual)
- Upgrade issue of openstack_auth in pip environment
- If an operator install horizon using pip directly rather than distribution package, there seems an upgrade notice is required. The following is what I see. Do you would like to have this in the release note?
- Install django_openstack_auth and horizon from Pike and then install horizon from Queens => openstack_auth from django_openstack_auth was kept. http://paste.openstack.org/show/626820/
- Install django_openstack_auth and horizon from Pike, remove django_openstack_auth and then install horizon from Queens => openstack_auth from horizon was installed. http://paste.openstack.org/show/626823/
- General progress is found at the whiteboard of the blueprint
- There are various ongoing things around horizon plugins and requirements. (amotoki will follow-up the on-going things)
- Some TODOs are remaining (Needs volunteers)
- Future of django-openstack-auth repo?
- Upgrade issue of openstack_auth in pip environment
- Publishing server projects to PyPI (added by amotoki)
- http://lists.openstack.org/pipermail/openstack-dev/2017-November/thread.html#124676
- horizon (and neutron) causes a tricky situation around unit testing. Someone needs to be aware of the direction. tox_install.sh is a really workaround. In the past, we explored horizon-lib but somehow it failed (thought I don't know the exact reason).
- Open Discussion
- Bump Django minimum version to >=1.11 in Queens?
- Pike requirement is Django>=1.8, so it is better to keep py27djXXX variants even if we bump the min version.
- Bump Django minimum version to >=1.11 in Queens?