| amotoki | vishalmanchanda: I -1'ed your release patch as I think there is no need to bump the major version | 07:11 |
|---|---|---|
| amotoki | I am not sure we need the major version bump only due to the requirement change. This is a super gray zone. | 07:13 |
| vishalmanchanda | amotoki: hi, let's say if I cut a new release for stable/xena in future then what version I will use? | 07:15 |
| amotoki | vishalmanchanda: my general answer is we just need a patch version bump. | 07:16 |
| vishalmanchanda | amotoki: Is it 20.1.1? | 07:16 |
| amotoki | vishalmanchanda: generally speaking, stable branches do not have features so no minor version is required | 07:16 |
| amotoki | vishalmanchanda: if we bump the major version in master, it would be nice to drop deprecated features together. | 07:17 |
| amotoki | vishalmanchanda: did you have any discussion what features can be dropped in the PTG? | 07:17 |
| vishalmanchanda | amotoki: yeah we have some discussion about dropping code for launch instance django based implementation. | 07:18 |
| amotoki | when are such removal planned? It is better to drop something in the earlier stage of the cycle. | 07:20 |
| vishalmanchanda | I am planning to drop this once I complete this djang3.2 related work. | 07:21 |
| amotoki | vishalmanchanda: how many times do you plan to bump the major version in yoga? | 07:23 |
| vishalmanchanda | amotoki: ok I will update my release patch to bump minor version. | 07:24 |
| amotoki | vishalmanchanda: just wait for the release team feedback | 07:24 |
| amotoki | vishalmanchanda: I am not sure we should keep a room for minor version(s) in stable/xena. | 07:24 |
| vishalmanchanda | amotoki: sure. | 07:25 |
| amotoki | vishalmanchanda: in case of xena and wallaby, our first released were shipped with the major version bump along with the feature drops. | 07:27 |
| vishalmanchanda | amotoki: but I think you are right I just checked the older patches for horizon release. | 07:27 |
| vishalmanchanda | #startmeeting horizon | 15:00 |
| opendevmeet | Meeting started Wed Oct 27 15:00:07 2021 UTC and is due to finish in 60 minutes. The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| opendevmeet | The meeting name has been set to 'horizon' | 15:00 |
| vishalmanchanda | hi anyone around for horizon meeting? | 15:01 |
| amotoki | hi | 15:01 |
| vishalmanchanda | let's wait for few minutes if more people join us. | 15:02 |
| vishalmanchanda | tmazur: e0ne : rdopiera : around? | 15:03 |
| tmazur | o/ | 15:04 |
| vishalmanchanda | ok Let's start the meeting. | 15:04 |
| vishalmanchanda | First of all, thank you all for joining the PTG discussion. It's good to see you all. | 15:05 |
| vishalmanchanda | In case if you are not able to join or missed any topic discussion please take a look at ptg eherpad | 15:05 |
| vishalmanchanda | https://etherpad.opendev.org/p/horizon-yoga-ptg | 15:05 |
| vishalmanchanda | #topic Notices | 15:06 |
| vishalmanchanda | few notices from my side for this week. | 15:06 |
| vishalmanchanda | This week is R-22, Yoga-1 milestone is R-19(Nov 15 - Nov 19) | 15:06 |
| amotoki | do we have assignees for priority items? Or are they just listed? | 15:06 |
| vishalmanchanda | Yoga Schedule https://releases.openstack.org/yoga/schedule.html | 15:06 |
| vishalmanchanda | amotoki: I will come to that point. | 15:07 |
| vishalmanchanda | I have cut first release for Yoga cycle so that all horizon plugins can consume django upper bump change and patch is merged today https://review.opendev.org/c/openstack/releases/+/815334 | 15:08 |
| vishalmanchanda | I have updated our release priority etherpad and priority items for Yoga cycle. | 15:08 |
| vishalmanchanda | So please a look at etherpad and any other priority if I missed any. | 15:08 |
| amotoki | vishalmanchanda: okay. we are now in the "Notices" topic, if more discussion is needed, let's cover later. | 15:09 |
| vishalmanchanda | Also, If you are working on any task mentioned on the etherpad, please add your name so we ask the status throughout the cycle. | 15:09 |
| amotoki | vishalmanchanda: where in which etherpad do you mean? | 15:09 |
| amotoki | the PTG etherpad? the priority etherpad? or something other? | 15:10 |
| vishalmanchanda | https://etherpad.opendev.org/p/horizon-release-priorities | 15:10 |
| vishalmanchanda | amotoki: release priority etherpad | 15:10 |
| vishalmanchanda | I have also updated the Weekly meeting Section in the release priority etherpad, so if you have topic to discuss please add it there. | 15:12 |
| vishalmanchanda | that's all announcement from my side for this week, if anyone have any announcement to make go ahead. | 15:13 |
| vishalmanchanda | moving to next topic | 15:14 |
| vishalmanchanda | #topic Django 3.2 support | 15:14 |
| vishalmanchanda | patch to update upper constraints to use new horizon release is up https://review.opendev.org/c/openstack/requirements/+/815628 | 15:15 |
| rdopiera | sorry for being late | 15:15 |
| vishalmanchanda | once above patch is merged I will purpose a patch to bump minimum django version to 3.2 in horizon and then cut a new release for horizon. | 15:16 |
| vishalmanchanda | I was also thinking if I should drop code for Launch instance python based implementation and django 2 support together so we not have to cut two releases. | 15:17 |
| amotoki | do we want to give some time to horizon plugins to bump the lower bound or want a new horizon release to force them to update their l-c? | 15:17 |
| amotoki | the gray zone is whetherr we need a major version bump when we change the lower bound of Django. | 15:18 |
| vishalmanchanda | I am not sure if horizon plugins are much active and they are going bump there lower bound. | 15:20 |
| vishalmanchanda | You mean if we drop Django 2 support then we didn't need a major version bump. | 15:21 |
| amotoki | vishalmanchanda: regrading the major version, yes. it is really a grayzone. | 15:22 |
| amotoki | I cannot say which is better | 15:22 |
| vishalmanchanda | but if I look at prometheanfire comment on my patch https://review.opendev.org/c/openstack/requirements/+/815096 it say we need to do a major version bump. | 15:22 |
| amotoki | yeah, a major version bump should work. what I am not sure is that the semantic versioning requires the major version bump when our (major) dependency are changed | 15:24 |
| amotoki | if we can do other changes which requires a major version change, it would be really nice to do them together | 15:24 |
| amotoki | so it is nice to have the removal of django Launch instance form in a same release | 15:25 |
| vishalmanchanda | amotoki: ok I will try to push a patch by next week. | 15:26 |
| amotoki | it is not specific to Django 2 vs 3. it can happen every Django LTS change :-( | 15:26 |
| vishalmanchanda | moving to next topic | 15:26 |
| amotoki | IMO I don't want to see a major version bump more than once in a release :_ | 15:27 |
| amotoki | :) | 15:27 |
| vishalmanchanda | amotoki: sure. | 15:27 |
| vishalmanchanda | #topic Bug deputy report | 15:27 |
| vishalmanchanda | We have 3 new bugs reported from last 2 weeks. | 15:28 |
| vishalmanchanda | one of them is already triaged 2 needs to be verify https://bugs.launchpad.net/horizon/+bug/1947295 and https://bugs.launchpad.net/horizon/+bug/1946534 | 15:29 |
| vishalmanchanda | I will take a look at these bug tomorrow. | 15:29 |
| amotoki | regarding the first one https://bugs.launchpad.net/horizon/+bug/1947295, the bug author found a solution. | 15:29 |
| amotoki | it looks like that the package they use still uses wsgi/django.wsgi unfortunately | 15:30 |
| amotoki | I think it is a bug of the package. | 15:30 |
| amotoki | I am not sure such kind of thing should be covered by the upstream team. | 15:31 |
| vishalmanchanda | amotoki: yeah, thanks feel free to add your comment there. | 15:31 |
| amotoki | will do if I don't forget it :p | 15:32 |
| vishalmanchanda | amotoki: thanks or I will mark it as incomplete as it is not horizon bug. | 15:33 |
| amotoki | where is a good place to report a bug on such package? | 15:33 |
| vishalmanchanda | I don't know maybe zigo know more about that. | 15:34 |
| amotoki | I only have an experience on ubuntu cloud archive as an OpenStack operator, so I don't know where is a right place for RPM package | 15:34 |
| opendevreview | Vadym Markov proposed openstack/horizon master: Fix for "Resize instance" button https://review.opendev.org/c/openstack/horizon/+/808102 | 15:34 |
| vishalmanchanda | ok moving to next topic | 15:35 |
| opendevreview | Vadym Markov proposed openstack/horizon master: WIP Fix for "Resize instance" button https://review.opendev.org/c/openstack/horizon/+/808102 | 15:35 |
| vishalmanchanda | #topic On demand agenda | 15:35 |
| zigo | vishalmanchanda: What package? | 15:35 |
| amotoki | vishalmanchanda: I don't think zigo is the right contact as he is a Debian package maintainers | 15:35 |
| vishalmanchanda | Do we have any other topic to discuss. | 15:35 |
| zigo | o/ | 15:36 |
| amotoki | zigo: sorry for bugging you. we are just wonder where is the right place to file a bug on a wrong configuration of RPM package of horizon. | 15:36 |
| vishalmanchanda | zigo: we are just discussing a bug and I thought maybe you know where to report it. | 15:36 |
| zigo | I'm not the right person for RPM stuff ... :) | 15:36 |
| amotoki | zigo: perhaps you are not the right person as you are a debian guy and I know it well. | 15:37 |
| zigo | Indeed. | 15:37 |
| rdopiera | I suppose that would be me | 15:37 |
| vishalmanchanda | cool. | 15:37 |
| amotoki | rdopiera: where should we report a bug? RDO? | 15:39 |
| rdopiera | amotoki: yes | 15:39 |
| amotoki | rdopiera: thanks. | 15:39 |
| amotoki | as upstream, it is better to forward a bug on packaging rather than marking such as Incomplete/Invalid. | 15:40 |
| vishalmanchanda | oh I forgot to mention I will not be able to host the next weekly meeting as it's the holiday for me. | 15:40 |
| rdopiera | I actually think he's following the wrong guide | 15:41 |
| vishalmanchanda | Can someone else chair it or we can skip? | 15:41 |
| rdopiera | he didn't mention which one he followed, other than it is "official" | 15:41 |
| amotoki | I think we can skip. I believe you discussed a lot in the PTG already. | 15:41 |
| vishalmanchanda | rdopiera: We can ask him about the steps how to reproduce it and let' see. | 15:42 |
| amotoki | rdopiera: good point. let's clarify it | 15:42 |
| vishalmanchanda | ok I will send a mail on open-discuss about skipping next weekly meeting in case noone come forward to chair it. | 15:44 |
| vishalmanchanda | I think we can end this meeting if we have nothing else to discuss. | 15:45 |
| vishalmanchanda | Also, please add your name if you are going to work on any task mentioned in release etherpad for yoga cycle | 15:46 |
| vishalmanchanda | https://etherpad.opendev.org/p/horizon-release-priorities line 6 | 15:46 |
| vishalmanchanda | Thanks everyone for joining! | 15:48 |
| vishalmanchanda | #endmeeting | 15:48 |
| opendevmeet | Meeting ended Wed Oct 27 15:48:33 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:48 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/horizon/2021/horizon.2021-10-27-15.00.html | 15:48 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/horizon/2021/horizon.2021-10-27-15.00.txt | 15:48 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/horizon/2021/horizon.2021-10-27-15.00.log.html | 15:48 |
| -amotoki- was disconnected | 15:48 | |
| amotoki | perhaps "official" means the documention from the horizon team, but it is not well maintained as nobody verifies it :p | 15:48 |
| amotoki | it seems the meeting ended which I was disconnected. | 15:48 |
| amotoki | I have one question on horizon-selenium-headless | 15:48 |
| vishalmanchanda | amotoki: please ask. | 15:49 |
| amotoki | we have only 7 tests in horizon-selenium-headless | 15:49 |
| amotoki | what is the purpose of this job? | 15:49 |
| amotoki | can we migrate them to other tests. | 15:49 |
| amotoki | ? | 15:49 |
| amotoki | I am not sure. I am just asking it | 15:49 |
| rdopiera | I just checked we have /usr/share/openstack-dashboard/openstack_dashboard/wsgi.py | 15:50 |
| amotoki | rdopiera: yes. $APP/wsgi.py is what Django upstream recommends. | 15:51 |
| vishalmanchanda | amotoki: TBH I have no idea about this job as of now maybe tmazur rdopiera know more! | 15:51 |
| rdopiera | so I have no idea where he got /usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi | 15:51 |
| rdopiera | I suspect from some janky old tutorial | 15:52 |
| amotoki | we added in commit 0ca736e5da47413db6749053e6083b82cbb24825 and dropped wsgi/django.wsgi in some release(s) later. | 15:52 |
| amotoki | commit 7e682a2d528bcff992334d8792e33abbd57f5802 dropped wsgi/django.wsgi in wallaby | 15:53 |
| amotoki | rdopiera: as I commented above, it was a way to configure horizon with apache. I wonder the package has not updated their apache config. | 15:54 |
| amotoki | so I think he just installed the package and hit the issue | 15:55 |
| rdopiera | amotoki: I think he wrote his own apache config | 16:05 |
| rdopiera | amotoki: based on some tutorial he found | 16:05 |
| rdopiera | hmm, you might be right, though, nobody normally installs openstack just from the rpm, without puppet or tripleo | 16:07 |
| rdopiera | so we might have missed that | 16:08 |
| rdopiera | yup, you are right | 16:09 |
| opendevreview | Tatiana Ovchinnikova proposed openstack/horizon master: Mark "Source" tab in the launch instance form as required https://review.opendev.org/c/openstack/horizon/+/788813 | 16:12 |
| ganso | amotoki: hi! when you have some time could you please take a look at and provide some feedback so it can be further worked on for the yoga cycle? Thanks in advance. https://review.opendev.org/c/openstack/horizon/+/806454 | 17:47 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!