15:00:58 <e0ne> #startmeeting horizon
15:00:59 <openstack> Meeting started Wed Dec  5 15:00:58 2018 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:00 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:02 <openstack> The meeting name has been set to 'horizon'
15:01:18 <e0ne> hi. is anybody around here for horizon meeting?
15:01:37 <vishalmanchanda> e0ne: Hi
15:01:55 <amotoki> hi
15:02:54 <vishalmanchanda> amotoki: hi
15:02:59 <e0ne> here is our agenda: https://wiki.openstack.org/wiki/Meetings/Horizon
15:03:26 <e0ne> #topic Notices
15:04:01 <e0ne> I'm going to move all items from the agenda into the https://etherpad.openstack.org/p/horizon-reviews-priority etherpad and keep that updated
15:04:22 <e0ne> so we'll get our agenda more dynamic
15:04:48 <e0ne> I'm working on integration tests and removing mox
15:04:58 <amotoki> does this mean we change the agent to the etherpad?
15:05:08 <e0ne> amotoki: no
15:05:38 <e0ne> now, agenda contains our priorities list for the release
15:05:53 <amotoki> okay
15:06:03 <amotoki> I was confused with "move all items from the agenda"...
15:06:06 <e0ne> but it' doesn't work well with low participation in  meetings, IMO
15:06:25 <e0ne> I mean move release priorities list to the etherpad
15:06:40 <amotoki> okay
15:06:44 <e0ne> amotoki: does it sounds reasonable?
15:06:51 <amotoki> yes
15:06:56 <e0ne> great
15:07:28 <amotoki> just note: i have two on-demand topics. I would like to discuss them later
15:07:46 <e0ne> I'm expecting that patches with integration tests job end mox removing will be published by the end of week by me
15:08:01 <e0ne> that's all updates from my side
15:08:05 <e0ne> #chair  amotoki
15:08:06 <openstack> Current chairs: amotoki e0ne
15:08:19 <e0ne> amotoki: feel free to bring up your topics
15:08:35 <amotoki> e0ne: sure
15:08:58 <amotoki> e0ne: doesn't openstack_auth UT depend on mox?
15:09:22 <e0ne> amotoki: yes, I almost finished my patch to remove it
15:09:38 <rdopiera> o/
15:09:40 <amotoki> e0ne: great
15:09:58 <e0ne> rdopiera: hi
15:10:43 <e0ne> amotoki: what topics do you want to discuss?
15:11:04 <amotoki> e0ne: the one is ocata EM
15:11:31 <amotoki> and the other is about some broken panels caused by nova extension retire.
15:11:51 <amotoki> can we move on?
15:11:54 <e0ne> sure
15:12:01 <amotoki> #topic ocata EM
15:12:20 <amotoki> as you may know, the extended maintenance (EM) phase was introduced
15:12:57 <amotoki> https://releases.openstack.org/ says Ocata is in Extended Maintenance
15:13:20 <amotoki> each project can decide when they enter into the EM mode.
15:13:37 <e0ne> amotoki: do you propose to get some patched beckported?
15:14:09 <amotoki> e0ne: even if we enter into EM all backports will be accepted
15:14:15 <e0ne> +1
15:14:26 <amotoki> the detail explanation is found at https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases
15:14:35 <amotoki> see "Extended Maintenance" section
15:14:54 <amotoki> the point is "No Releases produced, reduced CI commitment"
15:15:25 <amotoki> so what we need to discuss is the horizon team can care ocata or not.
15:15:57 <e0ne> I'm OK to get backports to ocata for horizon
15:16:19 <rdopiera> I'm going to fix things for ocata anyways, because we support it downstream
15:16:21 <amotoki> e0ne: do you understand what EM means correctly?
15:16:41 <rdopiera> I might as well propose the patches upstream
15:17:06 <amotoki> in EM phase, stable/ocata still accepts backports
15:17:11 <e0ne> as I understand, only security fixes are accepted
15:17:17 <amotoki> but we don't cut any release
15:17:45 <amotoki> possibly we can find other folks who are interested in maintaining a specific stable branch
15:19:02 <amotoki> FYI nova ocata already entered into EM mode and neutron has not yet.
15:20:05 <e0ne> do we need to tag ocata-em for horizon now?
15:20:23 <amotoki> e0ne: it depends on our decision
15:20:41 <amotoki> if horizon-stable-maint continue to maintain stable/ocata, ocata-em tag is unnecessary
15:21:20 <amotoki> honestly I don't have ocata env now so I tend to hesitate to review stable/ocata backports, while I always tests pike/queens/rocky backports in my local envs.
15:22:03 <e0ne> we have a lot clouds with ocata at our customers
15:22:18 <amotoki> we don't need to rush the conclusion but it is a good chance to be aware of "extended maintenance"
15:22:36 <e0ne> amotoki: good point
15:22:44 <amotoki> e0ne: that's the reason we introduced "extended maintenace"
15:23:41 <amotoki> In the EM phase, the stable team from the upstream team no longer need to take care of such branches, but patches are accetped
15:24:24 <amotoki> the point is members of the community interested in a given project/branch can be stable maintainers.
15:25:12 <amotoki> I joined almost all PTG/Forum sessions on this topic and understand what it means.
15:25:27 <amotoki> I am leading the discussion on neutron EM
15:25:47 <amotoki> but in case of horizon, e0ne and rdopiera are involved in downstream package maintenance
15:25:59 <amotoki> so I think it is almost up to you two
15:26:02 <e0ne> as an OpenStack vendor, I'm interesting in ocata support
15:26:27 <e0ne> I'll take a look if we've got something in downstream and not in upstream
15:27:48 <amotoki> I think we need to enter into EM phase at some time. otherwise, horizon stable cores will be responsible for more and more stable branches :( I don't think it works.
15:28:10 <e0ne> amotoki: +1
15:29:29 <e0ne> I'm OK to support it at least until Stein will be released
15:30:07 <amotoki> I think it looks better to understand what "EM" means more and we can revisit this topic
15:30:33 <e0ne> +1
15:31:16 <amotoki> I sometimes check the number of commits in stable branches from last release
15:31:32 <amotoki> but I haven't covered ocata recently....
15:32:30 <amotoki> can we move on?
15:33:14 <e0ne> I don't have anything to add
15:33:50 <amotoki> #topic some broken panels by nova extension retirement
15:34:12 <amotoki> I noticed some admin panels are not shown like Aggregates in my recent devstack
15:34:23 <e0ne> which panels are broken now?
15:34:24 <amotoki> nova retired the extension mechanism
15:34:36 <amotoki> for example Aggregates panel is not shown
15:34:48 <amotoki> I haven't checked all
15:35:12 <amotoki> I think we need to check nova microversion now to check features
15:35:30 <amotoki> my question is whether we need to cover both microversion and nova extensions.
15:35:56 <cosss_> Hi, just joined. Traffic is bad :(
15:36:16 <amotoki> perhaps it is related to a topic that how old releases need to be supported by the latest horizon
15:36:19 <e0ne> AFAIR, horizon tried to work with n-1 release in the past
15:36:42 <amotoki> n-1 is supported
15:36:42 <e0ne> but I don't know if somebody uses new horizon with an old release
15:37:00 <amotoki> yeah, but we have no clear policy
15:38:15 <e0ne> I need to check how it's easy or not to maintain both extensions and microversions for nova
15:38:56 <amotoki> in my first impression, it is not difficult
15:39:03 <amotoki> relatively easy
15:39:06 <e0ne> ideally, it would be good to support both of them in S release and drop nova extensions in T
15:39:40 <amotoki> my question leads to another question "when we drop old mechanism?"
15:40:10 <e0ne> T release sound reasonable if we want to work with n-1 release
15:40:52 <e0ne> it sounds like a critical bug. I can find a time and put it on the top of my list for tomorrow
15:40:52 <amotoki> I am okay with it
15:41:26 <e0ne> amotoki: did you file a bug?
15:41:38 <amotoki> I just noticed this during I joined a conference so I had no time to file it so far.
15:41:42 <amotoki> e0ne: sure. I will file it
15:41:52 <e0ne> amotoki: thanks
15:42:44 <amotoki> okay, my topics are over.
15:43:02 <amotoki> does anyone have a topic to be discussed?
15:43:04 <e0ne> amotoki: thanks for bringing them
15:43:14 <e0ne> amotoki: nothing from me
15:43:47 <amotoki> cosss_: hi, do you have any topic? you joined a bit ago
15:44:31 <vishalmanchanda> none from my side.
15:44:57 <e0ne> sounds like we can wrap up the meeting
15:45:06 <e0ne> thanks everybody who joined us
15:45:08 <cosss_> Not really. Just chiming in to read along looking if my effort can be helpful somewhere
15:45:34 <e0ne> cosss_: any contribution are welcome:)
15:45:43 <amotoki> cosss_: thanks. welcome :)
15:46:00 <e0ne> cosss_: feel free to ping us in #openstack-horizon if any questions
15:47:19 <cosss_> I will thanks!. Currently working on the password_expires_at bug. Think prolly will finish it friday.
15:47:36 <e0ne> cosss_: great. thanks for the help!
15:49:01 <e0ne> see you next week
15:49:24 <cosss_> see you!
15:49:29 <amotoki> see you
15:49:47 <vishalmanchanda> bye all!
15:50:03 <e0ne> #endmeeting