Thursday, 2021-11-11

opendevreviewGhanshyam proposed openstack/governance-sigs master: Rename ‘Extended Maintenance’ SIG to the ‘Stable Maintenance’  https://review.opendev.org/c/openstack/governance-sigs/+/81749901:01
*** diablo_rojo_phone is now known as Guest556101:14
*** Guest5561 is now known as diablo_rojo_phone01:16
opendevreviewGhanshyam proposed openstack/governance master: Remove retired training-labs repo  https://review.opendev.org/c/openstack/governance/+/81751102:27
opendevreviewGhanshyam proposed openstack/governance master: Retire training-labs repo  https://review.opendev.org/c/openstack/governance/+/81751102:29
*** ykarel__ is now known as ykarel05:32
*** pojadhav is now known as pojadhav|afk07:52
*** pojadhav|afk is now known as pojadhav08:30
*** ykarel is now known as ykarel|lunch10:05
*** ykarel|lunch is now known as ykarel11:19
*** gagehugo_ is now known as gagehugo13:43
*** jungleboyj_ is now known as jungleboyj13:43
*** diablo_rojo_phone_ is now known as diablo_rojo_phone13:45
*** gmann_ is now known as gmann13:45
*** diablo_rojo_phone is now known as Guest561413:45
*** gouthamr_ is now known as gouthamr13:45
*** bbezak_ is now known as bbezak13:45
*** johnsom_ is now known as johnsom13:46
*** knikolla_ is now known as knikolla13:46
*** pojadhav is now known as pojadhav|sick13:46
*** ykarel is now known as ykarel|away14:46
mnaserhi guys, I'm using oftc's web client today14:56
mnaserirc cloud seems to be down :(14:56
mnaser_or maybe now they're back right as i said something?14:57
gmannmnaser: yeah, I think it is unstable since yesterday night 14:57
*** mnaser_ is now known as mnaser14:58
jungleboyjIt is back up at the moment, but it was down for a while.15:00
gmann#startmeeting tc15:00
opendevmeetMeeting started Thu Nov 11 15:00:26 2021 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'tc'15:00
gmanntc-members: meeting time15:00
gmann#topic Roll call15:00
gmanno/15:00
mnasero/15:00
ade_leeo/15:01
jungleboyjo/15:01
gmannhope everyone adjusted meeting time change with daylight saving things15:01
jungleboyj:-)  I was smart enough to put it on my calendar in UTC.15:02
gmannyeah, I did same after i missed lot of meeting last time :)15:02
gmannless member today, may be holiday in USA, Poland and other place15:03
gmannlet's start15:03
gmann#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions15:03
dansmitho/15:03
gmanntoday agenda ^^15:03
belmoreirao/15:03
*** diablo_rojo__ is now known as diablo_rojo15:03
gmann#topic Follow up on past action items15:03
jungleboyj++15:03
diablo_rojoo/15:03
gmannnone from last meeting #link https://meetings.opendev.org/meetings/tc/2021/tc.2021-11-04-15.02.html15:04
gmann#topic Gate health check15:04
dansmithI've only had a few patches in the gate in the last week, but I haven't noticed any big problems15:04
gmannyeah15:04
dansmithI think nova reported some legit failure at some point though, but I didn't look deep15:04
jungleboyjI have seen things merging pretty efficiently.15:04
gmannonly one was devstack removed the keystone admin client creation and it broke few projects like tacker, blazer etc15:05
dansmithalso I think clarkb noted that nova has something n-v in the gate queue15:05
gmannyeah15:05
jungleboyjCinder was hit with a queueing problem earlier but it sounds like that is fixed.15:05
gmannon job cleanup, I am removing the opensuse job, please review where ever you can +2 #link https://review.opendev.org/q/topic:%22remove-tempest-full-py3-opensuse15%22+(status:open%20OR%20status:merged)15:06
gmannlet's move next15:07
gmann#topic Updates on community-wide goal15:07
gmannDecoupling goal from release cycle15:07
gmannwe need more review on this #link https://review.opendev.org/c/openstack/governance/+/81638715:07
gmannso that we can get this in first to avoid merge conflict/rebase need on proposed/rework on  goals15:07
jungleboyjOk.  I will look.15:08
gmannthanks 15:08
gmannRBAC goal rework 15:08
dansmithI'm behind on looking at the recent changes to that15:09
dansmithwill try to do that today15:09
gmannwe had second call after PTG to continue the discussion and things are much clear now on what to target in Yoga15:09
gmann#link #link https://review.opendev.org/c/openstack/governance/+/81515815:09
gmanndansmith: thanks15:09
gmann#link https://review.opendev.org/c/openstack/governance/+/81515815:09
gmannother also please review.15:10
jungleboyj++15:10
gmannand we will continue the discussion on various open things for future cycle in policy popup biweekly meeting. 15:10
gmannI will send the meeting detail on ML soon. 15:10
rosmaitagmann: that meeting is scheduled for today according to eavesdrop invite15:11
gmannrosmaita: yeah, as we meet yesterday i think  we can skip today and do from next week with biweekly odd 18th Nov, 2nd Dec..15:11
gmannrosmaita: I updated here #link https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popup_Team#Meeting15:12
rosmaitagmann: ty15:12
gmannand proposed the ical update also #link https://review.opendev.org/c/opendev/irc-meetings/+/81749615:12
gmannonce that is merged I will update on ML too15:12
rosmaitaok, great15:13
gmannanything else on RBAC ?15:13
gmannnext is new proposed goal - "Proposed community goal for FIPS compatibility and compliance"15:14
gmann#link https://review.opendev.org/c/openstack/governance/+/81658715:14
gmannade_lee: hand over to you15:14
ade_leethanks15:14
ade_leeI'm not if folks have had a chance to review, but there has been a lt of work around fips15:15
ade_leeI split this up into two goals here -- fips compatibility and fips compliance15:15
ade_leefips compatibility means - I turn ffips on and everything still works15:16
ade_leefips compliance means compatibility + I only use crypto libraries that have been fips certified15:16
ade_leeI think that we've made a lot of progress in fips compatibility to the point that we might be able to achieve it in Y15:17
ade_leeie. most of the projects now have ci gate jobs in progress to run with fips enabled.15:18
jungleboyjThat is good.15:18
ade_leeand we've identified and fixed a bunch of places where things would trip up -- ie. md5 , bad ciphers etc.15:18
ade_leewhat making this a community goal would do would be to get all the remaining projects on board, as well as 3rd party vendors15:19
ade_leemaybe even, we could replace all the regular ci jobs with fips enabled versions15:19
gmannI saw the tempest changes plan on that but not read the goal completely. 15:19
ade_leeie. if it works under fips, it could work otherwise too.15:19
ade_leeas a longer term goal, we could do fips compliance - maybe for Z, because that will require changes like - for example, replacing paramiko and other non-certified crypto15:21
fungithere are probably some blindspots worth noting when testing with fips mode on15:21
gmannI think proposal is to replace paramiko with libssh ?15:21
ade_leeand we'd like to do that consistently across openstack ideally15:21
mnaserquestion that might be silly15:21
fungifor example support of any cyrptographic algorithms not approved by the usa nist can't be exercised15:21
ade_leegmann, that could be the approach - there may be others15:21
mnaseris there a benefit in running FIPS only for our gates15:21
ade_leelibssh uses certified cryto in the backend15:21
gmannk15:22
mnaserlike is there a downside to making everything FIPS only by standard?15:22
fungifor example, you can't ssh with keys using ed2551915:22
fungimnaser: it's an americentric standard pushed by the united states government, so people in other countries, and particularly governments of countries besides the usa, are understandably wary15:23
fungiit's great when you want to supply resources under usa government/defense department contracts15:24
fungibut maybe not in other cases15:24
mnaserok i see15:25
gmannis fips compliance means 'everything FIPS only ' ?15:25
mnaserso its not necessary a 'good to have by default'15:25
gmannyeah15:25
ade_leeits also not just govts though - many financial and regulated industries want fips too - as a requiremwnt for other compliance regimes 15:26
fungithe global technical community is split on opinion, some expect nist has cryptographic strength as the primary goal, others suspect the nsa has convinced nist not to approve algorithms they don't know how to compromise... i personally expect it's a mix of those two priorities as well as other influences15:27
* jungleboyj feels like he is being watched15:27
fungithough supposedly fips 186-5 will add curve25519 as an allowed primitive, so ssh with ed25519 keys will probably eventually work in fips mode15:28
mnaserokay that's fair, so it's not overall a 'good thing' for us to aim for fips only to 'increase security'15:29
fungiright, it's possible to be "more secure than fips" in ways that are not fips compliant (depending on your definition of "secure" of course), but those are mostly corner cases15:30
dansmitheven if it doesn't get us better security,15:30
dansmithis it bad to run with that as a default just because a lot of people _do_ want it?15:30
dansmithlike, are we losing coverage if we enable?15:30
fungimaking sure openstack can be used in fips-compliant environments is 100% a good thing, i think15:30
fungionly testing in fips mode may reduce coverage, mainly around any support we might have for cryptographic primitives not (yet) approved by nist15:31
mnaseryeah, i am thinking more of 'do we do it by default' or not15:31
fungibut for the most part openstack doesn't really roll its own crypto, and tries to leave that to external dependencies15:31
gmannI am also not sure about default but definitely  make openstack fips compatible and test with few jobs15:31
fungiwell, also currently only know how to do fips mode testing on rhel/fedora-derived distros, so debian/ubuntu would probably take a fair amount of work to use for fips mode testing15:32
fungiand obviously the majority of our testing happens on whatever the latest ubuntu lts was at the time we started a given cycle15:33
ade_leefungi, thats true - although by the time that is done, most of the fips bugs will have been shaken out.15:34
dansmiththat seems like both a good reason not to enable by default, but also probably a bad thing if we don't know how to make our own primary test platform compliant :D15:34
gmannyeah. if we think on making it default then enabling in ubutnu is required15:34
ade_leemuch of the work in setting up the fips jobs has been getting them working on rhel/centos instead of ubuntu.15:34
gmannwe can start with the centos job adding in tempest and other tempest plugins and see15:35
fungiworth noting, logistically, fips mode is explicitly a non-default configuration for most linux distros (even the rhel/fedora-derived ones), so to test in fips mode on opendev's standard distro images you need to reboot the test nodes into fips mode15:35
fungiyou can't effectively enter/exit fips mode without a complete reboot15:36
gmannbut defining a goal to make it default seems difficult in Yoga15:36
dansmithdefault is different than complete right?15:36
fungiso that does extend job runtime a bit to swizzle the kernel parameters and reboot15:36
dansmithcomplete can mean "everyone runs at least one job to ensure compliance"15:37
gmannwe can go with three steps here 1. run few jobs on few projects 2. complete- have all project at least on job 3. discuss on making it default or not15:37
dansmithyeah15:38
ade_leegmann, we're already doing 1 -- I'm hoping for at least 215:38
gmannade_lee: as you mentioned, you have already divided it into multiple steps/goal. and with our new structure on goal, we can do it in these three steps and see how fast we do it. new structure I mean this #link https://review.opendev.org/c/openstack/governance/+/81638715:39
jungleboyjgmann:  That sounds like a reasonable plan.15:39
gmannade_lee: and with new structure which is not merged yet, it can be done at any different time within a cycle or in multiple cycle.15:39
ade_leegmann, ack - I can add in the new miestones etc.15:40
ade_leeas described in the template you described15:40
gmannade_lee: cool, and we will continue the discussion on gerrit. 15:41
ade_leecool15:41
gmannade_lee: you can add depends on the 816387in case to avoid merge conflict or so15:41
ade_leewill do15:41
gmannade_lee: thanks for the proposal and explaining here 15:41
ade_leethanks all15:41
gmannmoving next15:42
gmann#topic Adjutant need PTLs and maintainers15:42
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025555.html15:42
gmannI saw fungi reply on email to someone asking on Adjutant plan and reaching out to adrian15:43
gmannnut did not find the original email they asked on, may be i missed15:43
gmannbut I think there is no volunteer to help on this project or may be they are discussion internally ?15:43
gmann* help on this project yet15:44
mnaserisn't catalyst using this internally?15:44
gmannnot sure, adrian mentioned they might take this up but not sure15:45
gmannbut at least they are aware as I see Andrew  from catalyst reply on this ML thread15:46
fungii was replying to this:15:46
gmannI will send another reminder on ML and not sure how long adrian will be there to help/lead so they might need to take this soon15:46
fungi#link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025713.html 15:46
gmannyeah15:47
gmannso let's wait for more time on this15:47
gmannmoving next15:47
gmann#topic Pain Point targeting15:47
gmann#link https://etherpad.opendev.org/p/pain-point-elimination15:48
gmannwe decided to continue iterating the list and keep discussion on this.15:48
gmannwe did not much time in last week meeting also and this too15:49
gmannI think we can have a voice call to iterate it in adhoc meeting?15:49
gmannbelmoreira: ricolin_ what you think?15:49
gmannlike RBAC discussion we are doing15:50
belmoreiralooks good to me15:50
gmanncool, belmoreira or ricolin_ any one of you to schedule it otherwise I can do, sometime for next week or so?15:51
jungleboyjI think that makes sense as a next step.15:51
gmannyeah, we do not get much time in weekly meeting so doing it in adhoc meeting will be more productive 15:51
belmoreirait would be better to confirm with ricolin_ first since he started this effort15:52
jungleboyjbelmoreira:  ++15:52
gmannsure, he is not here today but I will ping him in case he miss to see our ping here. 15:52
gmann#action gmann, ricolin_ to schedule adhoc meeting for pain point discussions 15:53
gmann#topic Open Reviews15:53
gmann#link https://review.opendev.org/q/projects:openstack/governance+is:open15:53
gmannlot of open reviews, let check what all are ready to vote15:53
gmannthis one is needed for goal things #link https://review.opendev.org/c/openstack/governance/+/81638715:54
gmannmnaser: jungleboyj rosmaita diablo_rojo spotz ^^ please check15:54
jungleboyjmnaser:  Got it.15:55
gmannthis will be quick one as we discussed in last meeting to remvoe the office hours #link https://review.opendev.org/c/openstack/governance/+/81749315:55
gmannand this one is important for Yoga testing runtime so that we can start working on new testing part soon #link https://review.opendev.org/c/openstack/governance/+/81585115:55
gmannfrickler: fungi ^^ you too in case you have not checked the latest version15:56
gmannwith adding centos9-stream, I have removed the py36 and making py3.8 and py3.9 as voting15:56
gmannthere are othr open reviews also which are ready to vote, please check and review in this week as much as possible15:57
fungii think we're getting close on stream 9 testing, right now we're trying to work through getting package mirroring in place15:58
gmann+1, thanks15:58
diablo_rojoI will check that out toda15:59
gmannthanks 15:59
gmannone last thing- 15:59
gmannis openinfra tv keynotes 1 hr long or 2? on 18th15:59
gmann#link https://openinfra.dev/live/15:59
gmannah but it is at same time out tc meeting16:00
gmannwe can cancel it for next week on 18th if ok for everyone ?16:00
fungiyes, i was just watching this week's episode during the tc meeting16:00
gmanncancel TC meeting16:00
diablo_rojoyes please16:00
jungleboyjThat would be good.16:01
gmannok, let's cancel meeting on 18th and we will meet on 25th Nov. I will update on ML too16:01
gmannthanks everyone for joining, let's close it for today16:01
gmann#endmeeting16:02
opendevmeetMeeting ended Thu Nov 11 16:02:04 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2021/tc.2021-11-11-15.00.html16:02
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2021/tc.2021-11-11-15.00.txt16:02
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2021/tc.2021-11-11-15.00.log.html16:02
diablo_rojoThanks gmann!16:02
jungleboyjThank you!16:02
opendevreviewLance Bragstad proposed openstack/governance master: Rework the yoga secure RBAC community goal  https://review.opendev.org/c/openstack/governance/+/81515817:46
opendevreviewLance Bragstad proposed openstack/governance master: Rework the yoga secure RBAC community goal  https://review.opendev.org/c/openstack/governance/+/81515818:16
opendevreviewMerged openstack/governance master: Decouple the community-wide goals from cycle release  https://review.opendev.org/c/openstack/governance/+/81638718:37
opendevreviewMerged openstack/governance master: Unselect RBAC goal to rework the implementation  https://review.opendev.org/c/openstack/governance/+/81625318:38
gmannlbragstad: ^^ these are merged now which end up merge conflict to 815158. as RBAC goal is moved to goal/proposed dir we need to rebase it and add different milestone. and once we agree on the proposed goal then we can move to goal/selected. this is new process18:42
lbragstadgmann ok - cool18:42
gmannlbragstad: I can rebase it with new structure if you want? sorry for merge conflict 18:42
lbragstadgmann no worries - i figured that was going to happen anyway and i was anticipating it18:43
gmannfungi: mnaser can you help on these two project-config changes to proceed on few repo retirement https://review.opendev.org/c/openstack/project-config/+/817324/1  https://review.opendev.org/c/openstack/project-config/+/81750219:00
opendevreviewMerged openstack/governance master: Merge 'Technical Writing' SIG into TC  https://review.opendev.org/c/openstack/governance/+/81586919:02

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