Wednesday, 2021-02-24

*** e0ne has quit IRC00:01
*** tosky has quit IRC00:10
*** jmasud has joined #openstack-meeting00:55
*** mlavalle has quit IRC00:57
*** jmasud_ has quit IRC00:58
*** jmasud has quit IRC01:04
*** jmasud has joined #openstack-meeting01:06
*** ricolin_ has joined #openstack-meeting01:21
*** timburke_ has quit IRC01:45
*** macz_ has quit IRC02:04
*** jmasud has quit IRC02:08
*** ricolin_ has quit IRC02:11
*** ricolin_ has joined #openstack-meeting02:11
*** jmasud has joined #openstack-meeting02:15
*** rcernin has quit IRC02:37
*** jmasud has quit IRC02:58
*** rh-jelabarre has quit IRC03:01
*** jmasud has joined #openstack-meeting03:05
*** macz_ has joined #openstack-meeting03:05
*** macz_ has quit IRC03:10
*** macz_ has joined #openstack-meeting03:26
*** yamamoto has quit IRC03:27
*** macz_ has quit IRC03:31
*** macz_ has joined #openstack-meeting04:06
*** jmasud has quit IRC04:10
*** macz_ has quit IRC04:10
*** jmasud has joined #openstack-meeting04:20
*** macz_ has joined #openstack-meeting04:27
*** macz_ has quit IRC04:32
*** rcernin has joined #openstack-meeting04:44
*** macz_ has joined #openstack-meeting04:48
*** macz_ has quit IRC04:52
*** rcernin has quit IRC04:54
*** rcernin has joined #openstack-meeting04:55
*** jmasud has quit IRC04:57
*** jmasud has joined #openstack-meeting05:00
*** macz_ has joined #openstack-meeting05:09
*** macz_ has quit IRC05:13
*** rcernin has quit IRC05:14
*** udesale has joined #openstack-meeting05:21
*** rcernin has joined #openstack-meeting05:21
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-meeting05:33
*** gyee has quit IRC05:34
*** ricolin has quit IRC06:00
*** ricolin_ has quit IRC06:27
*** ricolin has joined #openstack-meeting06:28
*** timburke_ has joined #openstack-meeting06:45
*** timburke_ is now known as timburke06:45
*** macz_ has joined #openstack-meeting06:47
*** macz_ has quit IRC06:52
*** dklyle has quit IRC07:16
*** slaweq has joined #openstack-meeting07:27
*** e0ne has joined #openstack-meeting07:38
*** jmasud has quit IRC07:38
*** rcernin has quit IRC07:39
*** e0ne has quit IRC07:39
*** ralonsoh has joined #openstack-meeting07:48
*** belmoreira has joined #openstack-meeting07:55
*** edagawa_kc has joined #openstack-meeting08:00
*** edagawa_kc has joined #openstack-meeting08:02
*** edagawa_kc has quit IRC08:02
*** rpittau|afk is now known as rpittau08:11
*** rcernin has joined #openstack-meeting08:15
*** ociuhandu has joined #openstack-meeting08:20
*** ociuhandu has quit IRC08:31
*** rcernin has quit IRC08:31
*** rcernin has joined #openstack-meeting08:33
*** ociuhandu has joined #openstack-meeting08:36
*** macz_ has joined #openstack-meeting08:44
*** macz_ has quit IRC08:49
*** rcernin has quit IRC09:08
*** ociuhandu has quit IRC09:09
*** tosky has joined #openstack-meeting09:18
*** e0ne has joined #openstack-meeting09:21
*** ociuhandu has joined #openstack-meeting09:40
*** ociuhandu has quit IRC09:49
*** ociuhandu has joined #openstack-meeting09:52
*** ociuhandu has quit IRC09:53
*** ociuhandu has joined #openstack-meeting09:53
*** ociuhandu has quit IRC09:58
*** ociuhandu has joined #openstack-meeting10:00
*** ociuhandu has joined #openstack-meeting10:01
*** ociuhandu has quit IRC10:03
*** ociuhandu has joined #openstack-meeting10:03
*** macz_ has joined #openstack-meeting10:07
*** macz_ has quit IRC10:12
*** rcernin has joined #openstack-meeting10:27
*** rcernin has quit IRC10:42
*** rcernin has joined #openstack-meeting10:52
*** oneswig has joined #openstack-meeting11:01
oneswig#startmeeting scientific-sig11:01
openstackMeeting started Wed Feb 24 11:01:17 2021 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:01
*** openstack changes topic to " (Meeting topic: scientific-sig)"11:01
openstackThe meeting name has been set to 'scientific_sig'11:01
*** eliaswimmer has joined #openstack-meeting11:01
oneswig#link agenda for today
oneswigeliaswimmer: hi!11:02
eliaswimmerhi Stig!11:02
oneswigThanks for coming along11:03
oneswig(Just concluding another meeting)11:04
oneswigHow's things?11:07
oneswig#topic use of glance image metadata for inter-cloud portability11:08
*** openstack changes topic to "use of glance image metadata for inter-cloud portability (Meeting topic: scientific-sig)"11:08
oneswigIn the topic of inter-cloud portability, image naming is probably square one11:09
oneswig#link Listed properties in Glance docs
oneswigSetting lots of these is helpful to people trying to port their deployment to your cloud11:11
*** rcernin has quit IRC11:12
*** macz_ has joined #openstack-meeting11:13
eliaswimmeris there some naming convention for images yet?11:13
oneswigIn practice we could probably set more, for example here's table stakes11:14
oneswig    os_type: "linux"11:14
oneswig    os_distro: "centos"11:14
oneswig    os_version: "7.5"11:14
oneswig    hw_rng_model: "virtio"11:14
oneswigAh, naming, I think there are only informal conventions there.11:14
*** udesale_ has joined #openstack-meeting11:14
oneswigThis is where the discovery process comes in - how do I ask Glance, "What is the latest best CentOS 8 image" for example11:15
oneswiga metadata-driven lookup11:15
oneswigAlas we didn't get details ahead on Chris Layton's thoughts on this.11:16
eliaswimmerok, now I get it! For me a patch level tag would be an important label.11:16
eliaswimmercause centos 8 can be a lot off different versions11:17
oneswigso true11:17
*** udesale has quit IRC11:18
*** macz_ has quit IRC11:18
oneswigeliaswimmer: are you providing infrastructure-as-a-service on your system?11:19
*** ociuhandu has quit IRC11:19
oneswig(or planning to?)11:19
*** e0ne has quit IRC11:20
eliaswimmerthat's the plan! Currently only in an early stage11:20
*** ociuhandu has joined #openstack-meeting11:20
eliaswimmerThere is still a lot to do, like CD of images to OpenStack, image scanning etc11:20
eliaswimmerAnother question is how to lock images with vulnerabilities11:22
*** e0ne has joined #openstack-meeting11:22
oneswigTo prevent further deployments with it?11:22
oneswigSounds like a good idea11:22
eliaswimmerone can't remove them as long as the used, at least not when using ceph11:23
oneswigJust delete the image perhaps?  Deployed instances would only lose the name of the image they used11:23
oneswigeliaswimmer: are you sure?  could that be a copy-on-write detail11:24
eliaswimmeroneswig: Not 100%, maybe it was a permission issue11:24
*** ociuhandu has quit IRC11:25
eliaswimmerBut when deleting, users miss the metadata from the images11:26
*** ociuhandu has joined #openstack-meeting11:26
*** ociuhandu has quit IRC11:30
oneswigThat's true, but perhaps they don't need it after the VM is deployed.11:32
eliaswimmerAbout image scanning. Even if it is a bit off topic now, but we should also do so with Kolla images.11:34
*** ociuhandu has joined #openstack-meeting11:34
oneswigThe container images?11:37
oneswigWe've done some interesting exploration with using Clair11:37
eliaswimmerah, yes. that is what I was thinking11:38
oneswigIt was enough to convince us that it is a very useful function - we'll definitely use it11:38
eliaswimmerI do so with my images for jupyterhub, it's quite easy and the recent sudo bug shows how important that is11:40
eliaswimmersame can be done for all types of images, even live systems11:40
*** ociuhandu has quit IRC11:41
oneswigOn the image tags, there was an effort to set some standards as part of the IRIS federation in the UK, but I don't know if anything has been adopted by that group11:48
oneswigAnyway, I don't think we'll progress much further today, between us :-)11:52
*** ociuhandu has joined #openstack-meeting11:58
verdurinI've also looked at Anchore for image scanning.11:58
oneswigHi verdurin, just in time...11:59
oneswigCan you compare and contrast?11:59
oneswigAh, we should wrap up.  Thanks eliaswimmer verdurin12:03
*** openstack changes topic to "OpenStack Meetings ||"12:03
openstackMeeting ended Wed Feb 24 12:03:30 2021 UTC.  Information about MeetBot at . (v 0.1.4)12:03
openstackMinutes (text):
*** e0ne has quit IRC12:19
*** ociuhandu has quit IRC12:24
*** ociuhandu has joined #openstack-meeting12:24
*** ociuhandu has quit IRC12:29
*** vishalmanchanda has joined #openstack-meeting12:46
*** oneswig has quit IRC12:54
*** macz_ has joined #openstack-meeting13:01
*** macz_ has quit IRC13:06
*** rh-jelabarre has joined #openstack-meeting13:20
*** liuyulong has joined #openstack-meeting13:39
*** ociuhandu has joined #openstack-meeting13:42
*** Luzi has joined #openstack-meeting13:47
*** e0ne has joined #openstack-meeting13:50
*** belmoreira has quit IRC13:56
*** belmoreira has joined #openstack-meeting13:56
*** macz_ has joined #openstack-meeting13:58
slaweqhi liuyulong14:00
slaweqI'm in the other meeting in same time but I will be lurking here14:00
liuyulong#startmeeting neutron_l314:02
openstackMeeting started Wed Feb 24 14:02:14 2021 UTC and is due to finish in 60 minutes.  The chair is liuyulong. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:02
openstackThe meeting name has been set to 'neutron_l3'14:02
liuyulongLong time no see. :)14:02
*** macz_ has quit IRC14:02
liuyulongOK, let's start.14:03
liuyulong#topic Bugs14:04
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:04
openstackLaunchpad bug 1913646 in neutron "duplicate for #1913621 DVR router ARP traffic broken for networks containing multiple subnets" [Medium,Confirmed] - Assigned to LIU Yulong (dragon889)14:04
openstackLaunchpad bug 1913646 in neutron "DVR router ARP traffic broken for networks containing multiple subnets" [Medium,Confirmed] - Assigned to LIU Yulong (dragon889)14:04
*** rpittau is now known as rpittau|afk14:04
liuyulongThis was fixed in a way that we change the ARP reply dest mac to the router gateway.14:04
liuyulongBut the bug reporter said that 1913646 is a bit different.14:05
liuyulongSorry, it's 191362114:05
liuyulongThe main issue of bug/1913621 is why the Permant ARP was not added.14:06
*** lajoskatona has joined #openstack-meeting14:06
liuyulongHi, lajoskatona14:07
liuyulongSo I just removed the duplicated mark.14:07
liuyulongI agree that point, the main problem of 1913621  may exist in dvr related code.14:07
liuyulongI will revisit this bug  1913621 and try to reproduce that.14:10
openstackLaunchpad bug 1916022 in neutron "L3HA Race condition during startup of the agent may cause inconsistent router's states" [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)14:10
liuyulongThe patch is here.14:11
liuyulongI've read the code, but not test it yet.14:11
liuyulongA "Race condition" bug sometimes is not so much easy to test, IMO.14:12
slaweqyes we found it with tobiko tests14:13
slaweqthose tobiko tests can be very useful for us in some cases :)14:14
liuyulongmaybe run some times job in that tobiko to verify the fix14:15
slaweqliuyulong: I did14:16
slaweqthis is "test patch" which runs tobiko jobs14:16
slaweqand it passed many times already14:16
slaweqso for me it's clearly solving the issue14:16
liuyulongYep, Great work!14:17
liuyulongJust post my +214:18
liuyulongOK, next one14:18
openstackLaunchpad bug 1916024 in neutron "HA router master instance in error state because qg-xx interface is down" [High,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:18
liuyulongThe fix ^14:19
liuyulongThe fix is simple, just use the normal workaround method "retry".14:20
liuyulongI have left some comment here.14:20
liuyulongThere are some actions " DelPortCommand(port=qg-3e872c7f-68" and "AddPortCommand(bridge=br-int, port=qg-3e872c7f-68"14:21
liuyulongI don't know if these method can be the root cause, but it is really close to the behavior we found.14:22
liuyulongWhile ovsdbapp is doing the "delete and add" work, the privsep deamon is trying to run the "ip link" related command.14:23
liuyulongSo, maybe we can refactor that replace_port method to a more grace way: not delete it, but clear attributes and reset.14:28
*** Luzi has quit IRC14:28
liuyulongJust some thoughts, do not be sure if it really works.14:28
liuyulongOK, no more bugs from me then.14:29
liuyulongAny updates?14:29
*** ociuhandu has quit IRC14:29
*** ociuhandu has joined #openstack-meeting14:30
liuyulongOK, let's move on14:31
liuyulong#topic distributed_dhcp14:31
*** openstack changes topic to "distributed_dhcp (Meeting topic: neutron_l3)"14:31
liuyulongI have uploaded all code.14:31
liuyulongThe fullstack test case is passed locally in my devstack environment.14:32
liuyulongI'm not quite sure why the upstream is failing.14:32
liuyulongOne issue may be the DHCP client version.14:33
*** ociuhandu has quit IRC14:34
liuyulongSince we use namespace as the fake VM, the dhcp client should be from "Linux ubuntu-focal-ovh-gra1-0023152345 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux"14:35
liuyulongMaybe I should run a devstack deployment in ubuntu to verify this case.14:35
liuyulongSome other concerns are that maybe protocol coverage of the DHCPv4/v6 responder.14:37
liuyulongAll these options and replies are based on the dnsmasq example of dhcp-instance from DHCP-agent.14:38
liuyulongWe use Wireshark to verify and compare all related options from distribtued_dhcp and dnsmasq14:39
liuyulongMaybe it's not enough.14:39
liuyulongSo, any comments/problem/testing/issues you have about these DHCPv4/v6 responder are welcomed.14:40
haleybi wonder if looking at things in an OVN environment would help?  at least the flows?14:40
liuyulongThis is the main part of the distributed DHCP.14:40
liuyulonghaleyb, I did that, seems negtive.14:41
liuyulongThe flows from OVN and OVS are totally different.14:41
liuyulongActually for the implementation here for ovs agent, we only add one flow for DHCP request.14:42
liuyulong"submit to controller, aka ovs-agent"14:42
liuyulongOVN's flow has some user data, then upload to ovn-controller.14:42
haleyback, just thinking out loud14:43
liuyulongovn-controller can read those userdata, but ovs-agent with ryu app does not.14:43
*** Luzi has joined #openstack-meeting14:43
*** ociuhandu has joined #openstack-meeting14:44
liuyulongLast thing about this bp is that config option...14:45
liuyulong"disable_traditional_dhcp" or "enable_traditional_dhcp"14:45
liuyulongI'm still thinking that we should not add config option to "enable neutron's default behavior by default".14:46
lajoskatonaI would say to make anyway default the "legacy" dhcp, otherwise I am fine with any14:46
liuyulongThe original purpose and main aim is to "disable" something.14:47
liuyulonglajoskatona, yes, we will make sure that.14:49
haleybliuyulong: yes, it seems a little backwards, but to me it looks similar to other config options we've added where the default is True14:49
haleybfor example, we've done that when we wanted to add a new thing then backport the config option, not that this is the same case14:50
haleybi.e. set the option to what the current default is - enabling dhcp-agent14:51
haleybi don't think the "votes" agreed on either direction in the review14:51
*** munimeha1 has joined #openstack-meeting14:51
liuyulongThis option should not be backported to stable branch. : )14:53
*** macz_ has joined #openstack-meeting14:53
liuyulongMaybe someday this "disable_traditional_dhcp = True" will be default value.14:53
liuyulongOK, time is running out.14:55
haleybor the enable default is False :)  maybe i should ask someone that works on tripleo what they think, since they're maybe more in-tune with exposing config options to customers14:55
liuyulonghaleyb, great, thank you.14:56
liuyulongWe can continue the discussion on the gerrit.14:56
liuyulong#topic On demand agenda14:56
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:56
liuyulongI have one update here:14:56
liuyulongThe spec for "elastic snat"
*** macz_ has quit IRC14:57
liuyulongReviews are welcomed.14:57
liuyulongOK, thank you guys14:59
liuyulongLet's end here.14:59
*** openstack changes topic to "OpenStack Meetings ||"15:00
openstackMeeting ended Wed Feb 24 15:00:05 2021 UTC.  Information about MeetBot at . (v 0.1.4)15:00
openstackMinutes (text):
*** liuyulong has quit IRC15:00
*** lajoskatona has left #openstack-meeting15:00
*** lpetrut has joined #openstack-meeting15:13
*** abhishekk is now known as abhishekk|afk15:20
*** soniya29 is now known as soniya29|ruck15:22
*** lpetrut has quit IRC15:24
*** dklyle has joined #openstack-meeting15:46
*** abhishekk|afk is now known as abhishekk15:47
*** munimeha1 has quit IRC15:52
*** ociuhandu has quit IRC16:09
*** ociuhandu has joined #openstack-meeting16:10
*** ociuhandu has quit IRC16:14
*** macz_ has joined #openstack-meeting16:15
*** jmasud has joined #openstack-meeting16:22
*** vishalmanchanda has quit IRC16:36
*** gyee has joined #openstack-meeting16:41
*** jmasud has quit IRC16:41
*** jmasud has joined #openstack-meeting16:44
*** ociuhandu has joined #openstack-meeting16:47
*** belmoreira has quit IRC16:48
*** udesale_ has quit IRC16:54
*** ociuhandu_ has joined #openstack-meeting17:04
*** ociuhandu has quit IRC17:07
*** ociuhandu_ has quit IRC17:08
*** ociuhandu has joined #openstack-meeting17:18
*** ociuhandu has quit IRC17:22
*** dklyle has quit IRC17:53
*** Luzi has quit IRC17:56
*** ralonsoh has quit IRC18:00
*** dklyle has joined #openstack-meeting18:13
*** rcernin has joined #openstack-meeting19:10
*** rcernin has quit IRC19:15
*** eliaswimmer has quit IRC19:18
*** rh-jelabarre has quit IRC19:27
*** rh-jelabarre has joined #openstack-meeting19:30
*** jmasud has quit IRC19:51
*** eliaswimmer has joined #openstack-meeting19:51
*** rcernin has joined #openstack-meeting20:33
*** rcernin has quit IRC20:47
*** eliaswimmer has quit IRC20:57
*** acoles has joined #openstack-meeting21:00
timburke#startmeeting swift21:00
openstackMeeting started Wed Feb 24 21:00:19 2021 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
timburkewho's here for the swift meeting?21:00
acoleskota sent his apologies earlier in #openstack-swift21:01
rledisezhi o/21:03
timburkeagenda's at
timburkefirst up21:03
timburke#topic sharding backports21:03
*** openstack changes topic to "sharding backports (Meeting topic: swift)"21:03
timburkezaitcev isn't in here right now, but i wanted to at least give a short status update21:03
timburkelooks like he's been busy making sure that all the patches proposed for train made it onto ussuri and victoria21:04
claygtimburke: do you have any idea why he's doing that?21:05
timburkevictoria's just about all caught up, but i haven't looked at any of the ussuri patches yet. expect a bunch more merges21:05
mattoliverauhopeuflly he has clients who just want some shardy goodness21:05
timburkeor do you mean why he's backporting to u and v? so if someone takes the new train release with all those fixes, we want to make sure they could upgrade to u/v21:06
timburkesome of the patches include things like new states in the sharder's state machine -- at the end of all this, it'd likely be pretty bad to go from tip of stable/train to the master -> stable/ussuri branch point, for example21:07
*** eliaswimmer has joined #openstack-meeting21:08
timburkea bunch of the train patches are in need of rebasing; i'll likely get to it if zaitcev doesn't, but likely after making progres on ussuri and victoria21:08
timburkethat's about it21:09
timburke#topic CORS tests21:09
*** openstack changes topic to "CORS tests (Meeting topic: swift)"21:09
claygsounds weird, we just don't normally backport stuff like this (fixes to "experimental" features) - so i wasn't sure what was going on21:09
timburkeit's getting less and less experimental on master, so it seems reasonable to me to get a bunch of those fixes on whatever version people want to use sharding on, too21:10
claygspeaking of "less experimental" that CORS is pretty hawt21:11
timburkei figure there can be a lot of reasons to hold off on upgrading (even if master swift should Just Work with old OpenStack)21:11
timburkeso yeah21:11
timburkea long while back, i started poking at writing some in-browser CORS func tests21:11
timburkethis was originally to feel out a patch torgomatic was working on to pull CORS handling out to middleware, but that kinda stalled, so my tests did, too21:12
clayg"func" tests - browser integration tests - point is javascript in a browser is the only reasonable way to exercise CORS (since half of it is "the browser won't let the request XYZ")21:13
timburkebut for more than a year now i've had users wanting to be able to use s3api and CORS, and it's sure been a useful way to ensure that works21:13
clayg... *if* the origin says this or that ... which is what our "CORS support" is going about configuring21:13
*** rcernin has joined #openstack-meeting21:14
timburkethere have been a few iterations of how the test runs, but the core of it now seems fairly reasonable/useful to people21:14
claygright; we need to ship some CORS support for s3api - aws s3 has some/enough support for some CORS things we already do in the swift side - so it's mostly just making s3api let things through21:14
claygI'm getting a strong feel for the makeup of the test suite - the various stages and how things get put together21:15
timburkei think acoles, clayg, and mattoliverau have all managed to run the tests locally, and there's even a gate job21:15
claygI have some experience debugging the setup and webserver, and the javascript tests21:15
acolesyes, I have played with the tests quite a bit21:16
acolesI tried out selenium today with safari automation, all worked fine21:16
claygi'm less familiar with how the gate job works - I've run and broken and fixed them locally21:16
claygacoles: NICE!!!21:16
acolesI also put up a deliberate regression today to check the gate job
timburkeso i guess this is the point at which we try to sell everyone else in the community on the idea of merging it21:16
claygacoles: awww but we're still waiting on results21:17
timburke...which makes it a little unfortunate that the only non-nvidian this week is rledisez ;-)21:17
claygrledisez: is all about that CORS tho - and testing rledisez loves testing21:17
*** rcernin has quit IRC21:19
timburkeso rledisez, if you've got any thoughts now, i'd love to hear them; if not, we'll probably bring it up again next week (assuming we've got more people here)21:19
timburkenext week it is ;-)21:21
timburke#topic shrinking21:21
*** openstack changes topic to "shrinking (Meeting topic: swift)"21:21
timburkehow are things going there?21:21
acolesIIRC main progress over last week has been mattoliverau  getting shrinking candidate into recon cache21:22
acolesI've been working on estimating tombstone rows in dbs to better inform shrinking decision - hope to have a WIP patch soon21:23
timburkewhat are the next major pieces of work? what all's already proposed that needs review?21:24
claygi'm loving shrinking_candidates in recon - all about that compactible_ranges 💪21:24
acolesI'm looking forward to reviews on swift-manage-shard-ranges repair
claygI think we're still trying to figure out if we can update state and keep in_progress around a little bit after the finish:
clayg*update state *timestamp*21:25
mattoliverauwhat clay said :)21:26
timburkesounds good21:26
timburke#topic relinker21:26
*** openstack changes topic to "relinker (Meeting topic: swift)"21:26
acoleshmmmm ]21:26
* acoles is nervous about timestamps21:26
timburkeacoles, and mattoliverau were busy while i was out last week -- my chain's down to just one unmerged patch!21:27
timburke(relinker: Parallelize per disk)21:27
mattoliveraurelink all the things!21:27
timburkethanks for all the reviews and fix-ups!21:28
timburkei'll try to get that last one cleaned up some more, shift from parallelize=yes/no to workers=<N>21:28
timburke#topic debug_logger21:29
*** openstack changes topic to "debug_logger (Meeting topic: swift)"21:29
timburkeclayg, i think this is your topic?21:29
claygoh gross21:29
claygI guess I just wanted folks to tell me what to name the module if not `from test.unit.logging import debug_logger` or whatever the change is doing currently21:30
acoleswhat was it before?21:31
clayg`from test.logging import debug_logger` seemed reasonable to me, but because python2 imports are weird I had to `from __future__ import absolute_import` in `test/` because otherwise `import logging` might do some nonsense21:31
acolesoh debug_loggger21:32
*** rcernin has joined #openstack-meeting21:32
claygacoles: I suppose on master today we have test.debug_logger - I could live with `from test.debug_logger import debug_logger` I think21:32
timburkeyeah, that seems fairly reasonable to me21:33
acolesIDK I sometimes find it confusing when we have modules with same names, but it's no big deal21:33
timburkewhat *is* the difference between DebugLogger and debug_logger, anyway?21:33
acolesI mean, same names, different qualified names21:33
*** zaitcev has joined #openstack-meeting21:34
* zaitcev flies in21:34
claygthe function is like a factory21:34
acolesdebug_logger gets you an adapter wrapped DebugLogger21:34
claygtimburke: `return DebugLogAdapter(DebugLogger(), name)`21:35
claygi'm ok with dropping the module rename - so I think we're done21:35
acolesclayg: thanks21:36
timburke#topic tempauth system-level read-only role21:36
*** openstack changes topic to "tempauth system-level read-only role (Meeting topic: swift)"21:36
*** rcernin has quit IRC21:37
timburkezaitcev already has a +2 on it -- do we have any concerns about merging it?21:37
timburkei guess the main question is, is this a concept that we view as being generally good and useful in an auth middleware? having tempauth support it seems like a precursor to us writing func tests for it, which seems like a good idea21:39
*** rcernin has joined #openstack-meeting21:40
zaitcevI agree with functests. Although in general functests are supposed to be possible to run against any test cluster, not just SAIO. They would work with Keystone too.21:41
zaitcevBut it's helpful to have the support in tempauth as well.21:41
zaitcevOne thing that I stopped to consider is that it clearly adds baggage. We have so many various knobs and configurations already.21:42
zaitcevBut it's a good feature, right? The upside is significant... right?21:42
timburkeabsolutely. i'd expect it to get another user entry in /etc/swift/test.conf and we could update the DSVM job to ensure that the tests get run against both auth systems21:42
timburkeanother way of looking at it: if someone were writing a new auth system today, (1) would we push them to include such a role and (2) would we point to tempauth as a starting point for writing their own thing?21:43
timburke(i think my answer on both of those is probably "yes", but that might just be me)21:44
zaitcevThey could have roles with attributes, I suppose. In keystone you get a role called "compliance", and it has no intrinsic features. Is it a reader? Is it an admin? You don't know. But in a new auth system you could.21:45
*** rcernin has quit IRC21:45
zaitcevTempauth has no RBAC. It has no roles, only identities which can have attributes such as "reseller reader".21:45
zaitcevSo, I think the answer is yes, we'd ask the authors to support it21:46
*** rcernin has joined #openstack-meeting21:46
zaitcevIs this about the auth that Nvidia inherited from Swiftstack?21:46
*** slaweq has quit IRC21:48
claygafaik this has nothing to do with nvidia or swiftstack - if we want a feature like this in our legacy of beta auth systems - we'd add that w/o any disruption of upsttream21:49
timburkenot really, i don't think. i remember talking to clayg and him having a concern like "idk -- when i'm in a dev env (which is kinda the point of tempauth) auth is never really in the way of me reading data"21:49
claygthat's just a round about way of arguing zaitcev 's point about "baggage"21:49
claygbut it seemed like between the two of you - there's interest; so it's minor baggage for people that want to ignore it o/21:50
zaitcevFundamentally, all the new role adds is safety against buggy scripts run by the audit team.21:50
*** rcernin has quit IRC21:51
timburkei could see it growing beyond that -- we could move toward a container-sync that doesn't need an internal-client, say21:51
zaitcevI didn't think about it.21:51
zaitcevWell, as far as tempauth goes we might as well land it now, I think.21:52
timburkesounds like a plan21:52
timburke#topic open discussion21:52
zaitcevI started in keystone because of internal interests wanted Keystone.21:52
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:52
timburkelast few minutes: anything else we ought to bring up this week?21:52
zaitcevWell, I'm glad to see Clay.21:53
zaitcevOnline, that is.21:53
acolesI'll flag up this change because it downgrades a warning to info
acolesmaybe I should wait for more people being here next week, just in case anyone feels it should remain a warning21:54
zaitcevTwo +2 is sufficient21:54
acolesbut I'm excited that it fixes a probe test intermittent failure :)21:54
mattoliverauI added a crazy graphviz tool so people could checkout graph views of shard ranges from container-info and s-m-s-r info. Helps to see what's going on in a sharded container esp when there are a lot of shards.
mattoliverauNo rush on that though, just wanted to put it somewhere and somewhere where it's upstream :)21:56
timburkeoh, and i need to get a release together! i keep getting side tracked :-(21:56
timburkeanyone opposed to dropping lower-constraints testing from swiftclient?
*** eliaswimmer has quit IRC21:58
mattoliverauoh yeah. if it's getting in our way, kill it!! If they ever fix it we can add it back21:58
claygmattoliverau: ❤️21:59
timburkei think it's more a matter of our lower-constraints needing to nix most/all of the keystone/osc requirements and our tests needing to skip a bunch of things if those aren't available. i just felt like i wasted enough time on trying to make it work22:00
timburkeall right, we're at time22:00
timburkethank you all for coming, and thank you for working on swift!22:00
*** openstack changes topic to "OpenStack Meetings ||"22:00
openstackMeeting ended Wed Feb 24 22:00:33 2021 UTC.  Information about MeetBot at . (v 0.1.4)22:00
openstackMinutes (text):
*** zaitcev has left #openstack-meeting22:00
*** acoles has left #openstack-meeting22:00
*** rh-jelabarre has quit IRC22:08
*** rcernin has joined #openstack-meeting22:15
*** mlavalle has joined #openstack-meeting22:36
*** e0ne has quit IRC23:17

Generated by 2.17.2 by Marius Gedminas - find it at!