Tuesday, 2021-02-23

*** suzhengwei has joined #openstack-masakari05:43
*** vishalmanchanda has joined #openstack-masakari06:24
*** suzhengwei_ has joined #openstack-masakari06:56
*** suzhengwei has quit IRC06:57
jopdorp_good morning07:01
yoctozepto#startmeeting masakari07:01
openstackMeeting started Tue Feb 23 07:01:56 2021 UTC and is due to finish in 60 minutes.  The chair is yoctozepto. Information about MeetBot at http://wiki.debian.org/MeetBot.07:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:01
*** openstack changes topic to " (Meeting topic: masakari)"07:02
openstackThe meeting name has been set to 'masakari'07:02
yoctozepto#topic Roll-call07:02
*** openstack changes topic to "Roll-call (Meeting topic: masakari)"07:02
yoctozepto\o/07:02
yoctozeptomorning jopdorp_07:02
jopdorp_o/07:02
yoctozeptomorning suzhengwei_07:02
suzhengwei_oo/07:02
yoctozepto#topic Agenda07:03
*** openstack changes topic to "Agenda (Meeting topic: masakari)"07:03
yoctozepto* Roll-call07:03
yoctozepto* Agenda07:03
yoctozepto* Announcements07:03
yoctozepto* Review action items from the last meeting07:03
yoctozepto* CI status07:03
yoctozepto* Backports pending reviews07:03
yoctozepto* Masakari CLI was deprecated in Stein already. https://docs.openstack.org/releasenotes/python-masakariclient/stein.html07:03
yoctozepto  ** We should confirm OSC has feature parity at the moment, e.g., no changes were merged that did not touch OSC side as well (if necessary).07:03
yoctozepto* Release planning https://etherpad.opendev.org/p/masakari-wallaby-vptg07:03
yoctozepto* Open discussion07:03
yoctozepto#topic Announcements07:03
*** openstack changes topic to "Announcements (Meeting topic: masakari)"07:03
yoctozeptoI have none; anyone?07:03
jopdorp_no07:04
yoctozepto#topic Review action items from the last meeting07:04
*** openstack changes topic to "Review action items from the last meeting (Meeting topic: masakari)"07:04
suzhengwei_It is difficulty to pull code from openstack gerrit recently. Do you?07:04
yoctozeptothere were none07:05
jopdorp_i didn't07:05
yoctozeptosuzhengwei_: not difficulties I guess07:05
jopdorp_didn't notice anything wrong07:05
yoctozeptobut it is slow07:05
yoctozeptotry to always fetch from opendev.org before going to review.opendev.org07:05
suzhengwei_ok.07:06
yoctozeptoif you have serious issues with it, you should talk to the infra folks on #openstack-infra07:06
yoctozepto#topic CI status07:06
*** openstack changes topic to "CI status (Meeting topic: masakari)"07:07
yoctozeptoCI looks green07:07
yoctozepto#topic Backports pending reviews07:07
*** openstack changes topic to "Backports pending reviews (Meeting topic: masakari)"07:07
yoctozeptothere are none07:07
yoctozepto#topic Masakari CLI was deprecated in Stein already. https://docs.openstack.org/releasenotes/python-masakariclient/stein.html07:08
*** openstack changes topic to "Masakari CLI was deprecated in Stein already. https://docs.openstack.org/releasenotes/python-masakariclient/stein.html (Meeting topic: masakari)"07:08
yoctozepto  ** We should confirm OSC has feature parity at the moment, e.g., no changes were merged that did not touch OSC side as well (if necessary).07:08
yoctozeptothis is something suzhengwei_ brought to my attention07:08
yoctozeptoare you willing to work on this aspect? I would love to see us drop the legacy command in this cycle to avoid further confusion07:09
yoctozeptothe plan would be to check whether the OSC client is able to perform all possible actions (that the legacy client can)07:10
yoctozeptoI guess it could boil down to comparing whether there were any changes to the legacy client from train till now07:10
yoctozeptoas that would mean the osc did not get them by mistake07:10
yoctozeptomore thorough analysis would be welcome07:11
yoctozeptobut this is a sane minimum I guess07:11
yoctozepto(I pause now, please read the above messages and let me know)07:11
jopdorp_I'm not sure how much work it would be07:12
jopdorp_i guess I could have a look07:12
yoctozeptojopdorp_: comparing since stein should be quick as I have not seen many changes07:12
yoctozeptothe thorough analysis would be a bit harder as it boils down to actually reading current code07:13
yoctozeptostill, our client is nothing compare to nova/neutron/whatever :D07:13
yoctozeptocompared*07:13
jopdorp_hehe07:13
suzhengwei_It just have 1.1 microverson since train.  for bp progress-details-recovery-workflows07:13
yoctozeptoyeah, but it is in OSC, no?07:14
jopdorp_should i compare stein masakari cli to stein osc train to train etc?07:14
yoctozeptook, let me do a bit of an introduction07:14
yoctozeptopython-masakariclient is the repo07:14
jopdorp_yes07:14
yoctozeptoin there the common code for interacting with masakari as a client lives07:15
yoctozeptoand it has both the legacy (standalone) client07:15
yoctozeptoand the OSC hooks07:15
jopdorp_right07:15
yoctozepto(I think it's called hooks, anyway, the other wording is that it implements an OSC plugin)07:16
yoctozeptoso the minimum goal is to inspect changes07:16
yoctozeptohappening after stein was released07:16
yoctozepto(so for train, ussuri, victoria, wallaby [now])07:16
yoctozeptoand if they touched only common code - great, only OSC code - great, both frontends - great, only legacy - bad (unless it was just fixing the legacy for some purpose)07:17
suzhengwei_It is 1.1 miscroversion in OSC.07:17
yoctozeptosuzhengwei_: yeah, that makes sense07:17
jopdorp_ok07:17
yoctozeptoafter either coverage analysis07:17
yoctozeptowe should finally enact the deprecation-cycle drop07:18
yoctozeptoand no longer provide the legacy client07:18
jopdorp_what do you mean by coverage analysis?07:18
jopdorp_compare to the api?07:18
jopdorp_or compare legacy to osc?07:18
jopdorp_or test coverage07:19
yoctozeptojopdorp_: the thing I was talking about: either minimum via "what new has happened" or "really compare the two codes"07:19
jopdorp_ok07:19
jopdorp_i think i can d that07:19
yoctozeptook, I think it's possible that we 3 can do that by the next meeting07:20
yoctozepto#action everybuddy to check whether we can drop the legacy client07:21
yoctozepto#topic Release planning https://etherpad.opendev.org/p/masakari-wallaby-vptg07:21
*** openstack changes topic to "Release planning https://etherpad.opendev.org/p/masakari-wallaby-vptg (Meeting topic: masakari)"07:21
yoctozepto#link https://releases.openstack.org/wallaby/schedule.html07:22
yoctozeptoit's R-7 !07:22
yoctozeptoR-5 is feature freeze and final release of clients07:22
jopdorp_ok07:23
yoctozeptoR-3 is RC107:23
yoctozeptohow are we faring with the new changes?07:23
jopdorp_i just went through my incoming reviews07:23
jopdorp_added a couple of nits07:24
jopdorp_and there was one line in https://review.opendev.org/c/openstack/masakari-monitors/+/76170407:24
yoctozeptogood07:24
jopdorp_that i think wasn't in line with the spec07:24
yoctozeptoack, I will check07:24
yoctozeptoI am now moving most of my extra time slots towards masakari07:25
yoctozepto(I love the last minute stress lol)07:25
jopdorp_haha07:25
yoctozeptoanyhow, let me check the queues07:26
yoctozeptoI think there is something we should merged07:26
yoctozeptohave*07:26
yoctozeptoasap07:26
yoctozeptoah, yes07:26
yoctozepto#link https://review.opendev.org/c/openstack/masakari/+/76802207:26
jopdorp_i checked this one https://review.opendev.org/c/openstack/masakari/+/45879307:26
yoctozeptojopdorp_, suzhengwei_: ^^07:26
jopdorp_oooh, scary one07:27
yoctozeptobut we need to merge it07:27
jopdorp_I didn't see it yet07:28
*** openstackgerrit has joined #openstack-masakari07:29
openstackgerritRadosÅ‚aw Piliszek proposed openstack/masakari master: Segment description allows multiline characters  https://review.opendev.org/c/openstack/masakari/+/57461407:29
suzhengwei_I'm having bad network condiction in my workgroud.07:30
yoctozeptosuzhengwei_: ack, you can read the logs later then and let me know if you need me for something07:30
suzhengwei_ok07:31
yoctozeptook, that's everything from me in here07:33
yoctozepto#topic Open discussion07:33
*** openstack changes topic to "Open discussion (Meeting topic: masakari)"07:33
jopdorp_well\07:38
jopdorp_i don't have anything to discuss07:43
yoctozeptoall right, let's close this session07:46
yoctozeptothank you07:46
yoctozeptoand remember to review that one asap07:46
yoctozepto#endmeeting07:46
*** openstack changes topic to "This channel is *LOGGED* | IRC meetings on Tuesdays @ 07:00 UTC | Whiteboard: https://etherpad.opendev.org/p/masakari-whiteboard"07:46
openstackMeeting ended Tue Feb 23 07:46:34 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-02-23-07.01.html07:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-02-23-07.01.txt07:46
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-02-23-07.01.log.html07:46
*** suzhengwei_ has quit IRC08:33
*** noonedeadpunk has quit IRC09:26
*** noonedeadpunk has joined #openstack-masakari09:29
*** vishalmanchanda has quit IRC14:33
*** gmann is now known as gmann_lunch19:47
*** gmann_lunch is now known as gmann20:07
openstackgerritPavlo Shchelokovskyy proposed openstack/masakari-dashboard master: Disable dashboard when Masakari is not available  https://review.opendev.org/c/openstack/masakari-dashboard/+/77721420:21

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!