Friday, 2021-07-16

*** diablo_rojo is now known as Guest96102:54
*** ykarel|away is now known as ykarel04:31
*** iurygregory_ is now known as iurygregory06:38
*** amoralej|away is now known as amoralej07:02
*** rpittau|afk is now known as rpittau07:31
*** ykarel is now known as ykarel|lunch09:06
opendevreviewHervĂ© Beraud proposed openstack/releases master: fix placeholder  https://review.opendev.org/c/openstack/releases/+/80104110:00
hberaudelodilles: o/ I think that this one could be merged => https://review.opendev.org/c/openstack/releases/+/79684110:33
hberauddtantsur, iurygregory, rpittau: o/ Please can you have a look to those patches => https://review.opendev.org/c/openstack/releases/+/800251 https://review.opendev.org/c/openstack/releases/+/800234 thanks by advance10:36
opendevreviewMerged openstack/releases master: Create queens-eol tag for horizon project  https://review.opendev.org/c/openstack/releases/+/79954310:38
elodilleshberaud: hi, actually I'm not quite sure10:55
hberaudok10:55
hberaudso I drop my +210:56
elodilleshberaud: i was checking some newton branches that are still open10:56
elodillesand I see that there are newton-eol tags10:56
elodillesjust they are placed on weird commits10:56
elodilles:S10:56
hberaudah10:56
gibiprometheanfire: ack, thanks. 10:57
dtantsurhberaud: lgtm, sorry for the delay10:57
hberauddtantsur: np10:57
elodilleshberaud: there is already a newton-eol for dragonflow as well it seems: https://opendev.org/openstack/dragonflow/src/tag/newton-eol10:58
elodilleshberaud: it just does not match the tip of the stable/newton: https://opendev.org/openstack/dragonflow/commits/branch/stable/newton10:58
elodillesso I guess all the stale newton/mitaka/etc branches have the same issue: the *-eol tag does not match with the last commit's hash11:00
hberaudi see11:00
elodillesi am still thinking what should be the best fix for these situations... maybe we should use some *-eol-fix tags or I don't know...11:01
elodillesand then we can delete the branches11:01
iurygregoryhberaud, looking now11:03
hberaudelodilles: I don't know if it will be allowed by our tools, we can give a try11:06
hberaudiurygregory: thanks11:06
*** ykarel|lunch is now known as ykarel11:11
opendevreviewElod Illes proposed openstack/releases master: [dragonflow] Set eol to Dragonflow Ocata  https://review.opendev.org/c/openstack/releases/+/79684111:12
elodilleshberaud: yes, I have that fear that we cannot add such... I'll try that... :-/ meanwhile I've updated the patch to handle at least the ocata branch of dragonflow ^^^11:17
elodilleshberaud: I don't see ocata-eol there yet, at least...11:17
pabelangerMorning! sorry to ask again, but I'm curious how https://review.opendev.org/c/openstack/releases/+/772357 was generated. It is the release schedule for openstack, I'm curious is it was generted by hand, or more likely via a tool12:02
pabelangersmcginnis: ^ hopefully you'll be able to shed some light, given it was your change12:04
*** amoralej is now known as amoralej|lunch12:05
*** marios_ is now known as marios12:40
hberaudpabelanger: Hello12:56
pabelangero/12:56
hberaudI planned to reply you this morning but you was disconnected12:57
hberaudpabelanger: So these planning are generated by following this doc of our process => https://releases.openstack.org/reference/process.html#week-after-milestone-212:58
pabelangeryah, sorry about that. I haven't setup znc yet for new irc servers, so just on web12:58
hberaudpabelanger: We own a script to generate a base template that will be fulfilled manually with key dates12:59
hberaudYou can find an example of how to launch it in our process doc ^12:59
pabelangerperfect! thanks13:00
pabelangerlet me test it out13:00
hberaudpabelanger: you are welcome13:00
hberaudok np13:00
pabelangerI'm looking to reuse some of the logic for ansible project, given how awesome openstack releases are13:00
hberaudCool13:00
hberaudDo not hesitate to ask more questions, we will be happy to help you13:00
hberaudpabelanger: if you are interested in here is our next series' proposed schedule https://review.opendev.org/c/openstack/releases/+/80066313:03
hberaudpabelanger: and here is an example of our related ML announcement => http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023681.html13:05
pabelangerhberaud: how are the sphinx docs generated? I'm guessing you pipe the output of list_weeks.py into the schedule.yaml file. But still not seeing the sphinx part13:06
hberaudYes we pipe the output of the list_weeks.py into the schedule.yaml13:08
hberaudpabelanger: and the table is generated using the sphinx extension datatemplates => https://sphinxcontribdatatemplates.readthedocs.io/en/latest/nodata.html13:10
*** marios is now known as marios|call13:10
hberaudpabelanger: data are passed by using params to the extensions, see the line 13 in this file => https://review.opendev.org/c/openstack/releases/+/800663/1/doc/source/yoga/schedule.rst13:11
hberaudpabelanger: and here is our rendering template https://opendev.org/openstack/releases/src/branch/master/doc/source/_themes/releases/schedule_table.tmpl13:13
hberaud(passed to datatemplates)13:13
pabelangerack, so is the schedule.rst file handcrafted initially? with some static data for dates, then rest is loaded dynamically13:13
hberaud(that correspond to our series schedule)13:13
hberaudyes13:13
*** amoralej|lunch is now known as amoralej13:13
pabelangergot it13:14
hberaudschedule.* are hand crafted13:14
pabelangerthat was the step I was missing13:14
hberaudAnd this kind of patch is mostly for fulfilling with data https://review.opendev.org/c/openstack/releases/+/80066313:17
pabelangerhberaud: is tox -edocs enough to generate the sphinx files from the schedule.* bits or is there another entry poing?13:17
hberaudpabelanger: nope it's the one13:17
hberaud(yes tox-e docs is enough)13:18
pabelanger++13:18
hberaudpabelanger: One main advantage of that is that it allow every team to fulfil their own team planning (teams specific their dates) e.g: https://opendev.org/openstack/releases/commit/9f652aee73a2061b06a66933bcb4d02b94d8198013:21
hberaudpabelanger: `x-project` dates are cross key dates and `project-specific` dates are specific to teams13:23
hberaudpabelanger: This kind of feature can help the ansible project to reflect your SIG topics per example13:24
hberaudI know that the ansible project split the maintenance into modules/topics (files, auth), so, each ansible maintenance group could define its own specific schedule driven by through the cross goals.13:30
*** marios|call is now known as marios13:34
hberaud#startmeeting releaseteam14:00
opendevmeetMeeting started Fri Jul 16 14:00:09 2021 UTC and is due to finish in 60 minutes.  The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'releaseteam'14:00
hberaudPing list: elod armstrong14:00
hberaudWe're way down on line 206 now14:00
ttxo/14:00
hberaud#link https://etherpad.opendev.org/p/xena-relmgt-tracking14:00
hberaudWill just wait a couple minutes for folks.14:00
ttxadded a couple of topics14:01
hberaudack14:01
elodilleso/14:01
hberaudOk let's go!14:03
hberaud#topic Review task completion14:03
hberaudMilestone-2 => https://review.opendev.org/q/topic:%2522xena--milestone-2%2522+status:open14:03
opendevreviewMerged openstack/releases master: Create queens-eol tag for manila-ui project  https://review.opendev.org/c/openstack/releases/+/80096314:03
hberaudA couple of patch just need a final +214:03
hberaudDeadline is today so feel free to approve them14:04
hberaudWe just have 3 exceptions 14:04
ttxI'm on it14:04
hberaudWhere people asked to wait for patches14:05
hberaudttx: thanks14:05
ttxall pretty straightforward14:05
hberaudExcellent14:06
hberaudThe next topic is "Ask Cinder team if we should include rbd-iscsi-client for Xena release."14:06
hberaudSo, they replied "it's on an independent release model, we have a CI issue to work out, but we intend to release sometime during xena"14:06
hberaudSo, no rush for this one14:06
hberaudConcerning the barbican-ui topic, the team replied the same that during Wallaby. They have a patch that's been languishing that has all the basic functionality for barbican-ui. They would rather not abandon it, given that it is in their roadmap downstream, just kind of low priority right now.14:07
hberaudSo, I would suggest to give them on more chance14:08
ttxoh, it's independent?14:08
*** rpittau is now known as rpittau|afk14:08
hberaudApparently yes14:08
ttxthen I agree we need no decision14:08
ttxhmm14:09
ttxit would be independent if it existed14:09
ttxWe only need to finalize xena content, so as long as it's not xena material we are good14:09
hberaudAnd the last one was the monasca part, I proposed a patch to retire the project, and the team agreed with that https://review.opendev.org/c/openstack/releases/+/800628 So I think that we can +2 this one14:09
ttx+214:10
hberaudttx: I think that they plan to host this project under the independent umbrella14:10
hberaudbut it doesn't yet exist on our side, right?14:10
ttxok then we are good, they can release when they want14:10
hberaudok14:11
hberaudAnd that's all for the discussion part14:12
hberaudThe last topic was to catch the ACL issues and apparently no issues have been detected, thanks ttx14:12
ttxyep, empty output means no issues14:12
hberaudExcellent, no news, good news14:13
hberaudThen we go to task assignment14:13
hberaud#topic Assign R-11 tasks14:13
hberaudSo14:13
hberaudWe only have to handle the remaining exceptions for Milestone-214:14
hberaudAs you know I'll be mostly offline during the 2 next weeks14:14
hberaudSo, ttx, elodilles, I'll let you handle the 3 remaining patches14:15
ttxSo it's just about keeping an eye on those for new submissions?14:15
elodillesthere are the 3 exception you linked earlier,  am I right?14:15
elodilleshberaud: ack14:15
hberaudyes14:15
ttxok we can keep the watch. Did you give an extra deadline?14:15
opendevreviewMerged openstack/releases master: Xena-2 Release for openstacksdk  https://review.opendev.org/c/openstack/releases/+/80023714:16
opendevreviewMerged openstack/releases master: Xena-2 Release for metalsmith  https://review.opendev.org/c/openstack/releases/+/80023414:16
hberaudFor now, I didn't gave extra deadline, I'll leave a comment to notify our extra deadline and my PTO to PTL14:17
hberaudPTLs14:17
hberaudUsually Done14:19
hberauds/Usually//14:19
hberaudAnd that's all for next weeks assignments14:20
opendevreviewMerged openstack/releases master: Xena-2 Release for python-ironic-inspector-client  https://review.opendev.org/c/openstack/releases/+/80025114:20
hberaudI already proposed the Yoga schedule but we will discuss about this later during the meeting14:21
hberaud#topic Review countdown email contents14:21
hberaudhttps://etherpad.opendev.org/p/relmgmt-weekly-emails14:21
ttxI US-ified the dates14:23
ttxAll good otherwuse14:23
ttx+i14:24
hberaudOk14:24
opendevreviewMerged openstack/releases master: fix placeholder  https://review.opendev.org/c/openstack/releases/+/80104114:24
armstrongLGTM!14:24
opendevreviewMerged openstack/releases master: Propose to retire monasca-analytics from deliverables  https://review.opendev.org/c/openstack/releases/+/80062814:24
hberaudSent!14:25
hberaud#topic SBOMs for OpenStack?14:25
ttxyeah so14:25
hberaudttx: the floor is yours14:25
ttxThere is this thing the Biden administration has been pushing14:25
ttxcalled software bill of materials14:26
ttxin an effort to better track supply chain issues14:26
hberaudhttps://en.wikipedia.org/wiki/Software_bill_of_materials14:26
ttxI noticed that Kubernetes started to work on publishing a formal SBOM doc with each release14:26
ttxWe might want to follow suit, before someone else asks14:26
ttxAt this stage the idea would be to do our homework and learn about it14:27
ttxand of te various tools being created to help handle them14:27
armstrongI think the Linux foundation is also doing similar 14:27
hberaudI really love the idea14:27
ttxLF maintains SPDX which is a standard format14:27
ttxWe have pretty good dependency tracking in openstack already14:28
ttxbut that may just be one piece of the puzzle14:28
hberaudMaybe we could inspire from the LF14:28
ttxIt might not be a Xena thing, but definitely a hot topic for the yeti PTG14:28
hberaudYes14:28
hberaudyeti? isn't yoga?14:28
ttxSo this was more of a flag I wanted to raise so that we all learn more about those14:28
ttxArh Yoga14:28
ttxYggdrasil14:28
hberaudlol14:29
ttxToda whatever14:29
hberaudGood suggestion14:29
ttxIt will always be yeti in my mind14:29
hberaudBoys don't cry14:29
ttxhttp://scd.rfi.fr/sites/filesrfi/imagecache/rfi_16x9_1024_578/sites/images.rfi.fr/files/aef_image/yeti-tintin_0.jpg14:30
armstrongttx are you too attached to yeti :)14:30
hberaud:)14:30
ttxalright that is all I had on this topic14:31
ttxoh, maybe a link14:31
hberaudOk I added SBOM to our "things to change"14:31
ttxhttps://github.com/kubernetes/release/blob/master/docs/bom/create-a-bill-of-materials.md14:31
ttxThat's the K8s proposed process around SBOM, pretty new14:32
ttxand very go-centric14:32
hberaudok14:32
ttxbut still interesting to see as a data point14:32
hberaudI'll have a deeper look14:32
hberaudSure14:32
hberaud+114:32
hberaudSo, next topic14:33
hberaud#topic Yoga proposed schedule14:33
ttxyour email worked for me btw14:33
ttxI think you had a stale PGP sig block14:33
hberaud#link  https://review.opendev.org/c/openstack/releases/+/80066314:33
hberaudttx: yes14:33
hberaudDo we want to propose more alternative schedules?14:34
hberaudI prefer to start with this one and spend time on alternative if really needed14:34
ttxAt first glance i was thinking... this is short, like it does not account for lost time around new year14:34
ttxBut event-wise that may lead to better alignment, so I think we can work with it14:35
ttxlike if we do 25w every time we'll skew14:35
hberaudI fear that we miss the ubuntu train if we propose longer schedule14:35
ttxbut for now skew is probably a good diea14:36
ttxyeah I know they will appreciate the timing here14:36
ttxso +1 for me, after careful consideration14:36
ttxBut I don;t want to influence the feedback14:36
hberaudNo problem, we have the time to leave the time to think more about this14:37
hberaudAnything else about this topic?14:37
ttxno14:38
hberaudOk move on14:38
hberaud#topic Open Floor14:38
hberaudAnything else to discuss today?14:38
elodillesone thing from me14:39
hberaudelodilles: the floor is yours14:39
elodillesI know that the timing is not the best (vacations), but I'm planning to generate release patches for Ussuri to prepare for the EM transition in November14:39
elodillesEOM14:39
elodillesI mean that's it :X14:40
hberaudCan't we wait at least the end of R-11?14:40
elodillesof course we can :)14:40
hberaudOk, so LGTM14:41
elodillesthough i don't know how fast the teams will react14:41
hberaudYou'll start by releasing the latest deltas?14:41
elodilles(usually a ~half or so of the patches are abandoned due to missing approval from teams)14:41
elodilleshberaud: yes14:41
hberaudOk that will limit the back and forth14:42
hberaudAt first glance November seems a bit far from us but as you said people take time to react, so... why not14:43
elodilleshberaud: this is not the final release :)14:43
elodillesmore like a final-but-one :)14:44
hberaudok14:44
hberaud:)14:44
elodillesthis process was done by smcginnis some time ago,14:44
hberaudOk14:44
elodillesto avoid breakages with the final releases14:44
hberaudI see14:44
hberaudSold14:45
elodilles(teams in hurry, releases after deadline, things break, etc)14:45
hberaudOk no problem you convinced me :)14:45
elodillesok, thanks :) then I'll generate the patches then around next Friday, is that OK?14:46
hberaudThat make sense14:46
hberaudOk for me14:46
elodillesack14:46
*** ykarel is now known as ykarel|away14:46
hberaudAnything else that you want to discuss today?14:47
elodillesnothing else from me :X14:47
ttxnope nothing14:48
hberaudOK, thanks everyone. Let's wrap up.14:50
hberaud#endmeeting14:50
opendevmeetMeeting ended Fri Jul 16 14:50:02 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:50
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2021/releaseteam.2021-07-16-14.00.html14:50
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2021/releaseteam.2021-07-16-14.00.txt14:50
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2021/releaseteam.2021-07-16-14.00.log.html14:50
elodillesthanks o/14:50
armstrongthanks hberaud 14:51
gmannhberaud: elodilles as Train is EM, I am going to cut train-last for tempest and its plugins today15:47
hberaudgmann: ack15:47
elodillesgmann: thanks for the heads up!16:17
*** marios is now known as marios|out16:35
*** amoralej is now known as amoralej|off16:45
clarkbas a heads up we're going to try and do a zuul restart later today to ensure it restarts cleanly on Sunday/Monday as part of the Gerrit server move16:56
clarkbwill try to remember to let you know as we get closer to that. Hoping to let more of these jobs finish up and do it once we reach quieter friday time16:56
opendevreviewElod Illes proposed openstack/releases master: WIP: [packaging-deb] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/80112218:05
opendevreviewElod Illes proposed openstack/releases master: [powervm] Transition Ocata to End of Life  https://review.opendev.org/c/openstack/releases/+/80112318:16
clarkband now it is looking like we are getting close to doing that restart20:31
clarkbqueues are largely empty now20:31
opendevreviewGhanshyam proposed openstack/releases master: [Tempest] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80113320:57
opendevreviewGhanshyam proposed openstack/releases master: [oswin-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80113421:06
opendevreviewGhanshyam proposed openstack/releases master: [vitrage-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80113521:14
opendevreviewGhanshyam proposed openstack/releases master: [ec2api-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80113621:18
opendevreviewGhanshyam proposed openstack/releases master: [trove-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80113721:22
opendevreviewGhanshyam proposed openstack/releases master: [cloudkitty-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80113821:27
opendevreviewGoutham Pacha Ravi proposed openstack/releases master: [manila] Transition stable/queens and stable/rocky to eol  https://review.opendev.org/c/openstack/releases/+/80114121:51
opendevreviewGoutham Pacha Ravi proposed openstack/releases master: [python-manilaclient] Transition stable/queens and stable/rocky to eol  https://review.opendev.org/c/openstack/releases/+/80114221:53
opendevreviewGoutham Pacha Ravi proposed openstack/releases master: [manila-ui] Transition stable/rocky to eol  https://review.opendev.org/c/openstack/releases/+/80114321:57
opendevreviewGoutham Pacha Ravi proposed openstack/releases master: [manila-ui] Transition stable/rocky to eol  https://review.opendev.org/c/openstack/releases/+/80114322:09
opendevreviewGoutham Pacha Ravi proposed openstack/releases master: [python-manilaclient] Transition stable/queens and stable/rocky to eol  https://review.opendev.org/c/openstack/releases/+/80114222:09
opendevreviewGoutham Pacha Ravi proposed openstack/releases master: [manila] Transition stable/queens and stable/rocky to eol  https://review.opendev.org/c/openstack/releases/+/80114122:09
opendevreviewGhanshyam proposed openstack/releases master: [neutron-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80114622:19
opendevreviewGhanshyam proposed openstack/releases master: [senlin-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80114722:24
opendevreviewGhanshyam proposed openstack/releases master: [zaqar-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80114822:29
opendevreviewGhanshyam proposed openstack/releases master: [magnum-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80114922:34
opendevreviewGhanshyam proposed openstack/releases master: [manila-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80115022:37
opendevreviewGhanshyam proposed openstack/releases master: [kuryr-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80115122:40
opendevreviewGhanshyam proposed openstack/releases master: [telemetry-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80115222:45
opendevreviewGhanshyam proposed openstack/releases master: [watcher-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80115322:49
opendevreviewGhanshyam proposed openstack/releases master: [zun-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80115422:52
opendevreviewGhanshyam proposed openstack/releases master: [sahara-tests] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80115522:56
opendevreviewGhanshyam proposed openstack/releases master: [freezer-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80115823:40
opendevreviewGhanshyam proposed openstack/releases master: [blazar-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80116123:46
opendevreviewGhanshyam proposed openstack/releases master: [mistral-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80116323:49
opendevreviewGhanshyam proposed openstack/releases master: [monasca-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80116423:52
opendevreviewGhanshyam proposed openstack/releases master: [octavia-tempest-plugin] Tag train-last  https://review.opendev.org/c/openstack/releases/+/80116523:57

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