Wednesday, 2019-09-11

*** jamesmcarthur has joined #openstack-meeting00:02
*** jbadiapa has quit IRC00:04
*** jamesmcarthur has quit IRC00:06
*** jamesmcarthur has joined #openstack-meeting00:10
*** slaweq has joined #openstack-meeting00:11
*** slaweq has quit IRC00:16
*** tetsuro has joined #openstack-meeting00:26
*** jamesmcarthur has quit IRC00:27
*** armax has quit IRC00:32
*** ekcs has quit IRC00:34
*** mahatic has quit IRC00:39
*** jamesmcarthur has joined #openstack-meeting00:39
*** eharney has quit IRC00:42
*** gyee has quit IRC00:42
*** jamesmcarthur has quit IRC00:44
*** tetsuro has quit IRC00:54
*** armax has joined #openstack-meeting00:56
*** jamesmcarthur has joined #openstack-meeting01:02
*** tetsuro has joined #openstack-meeting01:02
*** ykatabam has joined #openstack-meeting01:05
*** mriedem has joined #openstack-meeting01:06
*** XSM_HUST has joined #openstack-meeting01:11
*** tetsuro has quit IRC01:15
*** liuyulong has joined #openstack-meeting01:25
*** lbragstad has quit IRC01:26
*** lbragstad has joined #openstack-meeting01:26
*** tetsuro has joined #openstack-meeting01:28
*** hyunsikyang has quit IRC01:34
*** tetsuro has quit IRC01:40
*** tetsuro has joined #openstack-meeting01:40
*** liuyulong has quit IRC01:55
*** jamesmcarthur has quit IRC01:59
*** jamesmcarthur has joined #openstack-meeting02:04
*** slaweq has joined #openstack-meeting02:11
*** slaweq has quit IRC02:15
*** lseki has quit IRC02:18
*** carloss has quit IRC02:21
*** njohnston|lunch has quit IRC02:22
*** tetsuro has quit IRC02:47
*** mriedem has quit IRC02:48
*** yamamoto has joined #openstack-meeting02:56
*** tetsuro has joined #openstack-meeting03:00
*** jamesmcarthur has quit IRC03:00
*** tetsuro has quit IRC03:05
*** jamesmcarthur has joined #openstack-meeting03:06
*** jamesmcarthur has quit IRC03:13
*** jamesmcarthur has joined #openstack-meeting03:25
*** rfolco has quit IRC03:32
*** patrickeast has quit IRC03:39
*** PrinzElvis has quit IRC03:39
*** larainema has joined #openstack-meeting03:39
*** datasundae has quit IRC03:41
*** knikolla has quit IRC03:42
*** ildikov has quit IRC03:42
*** csatari has quit IRC03:42
*** patrickeast has joined #openstack-meeting03:43
*** datasundae has joined #openstack-meeting03:44
*** knikolla has joined #openstack-meeting03:45
*** ildikov has joined #openstack-meeting03:45
*** csatari has joined #openstack-meeting03:45
*** PrinzElvis has joined #openstack-meeting03:45
*** jamesmcarthur has quit IRC03:57
*** rbudden has quit IRC04:09
*** rbudden has joined #openstack-meeting04:10
*** rbudden has joined #openstack-meeting04:10
*** joxyuki has left #openstack-meeting04:24
*** ianychoi_ has joined #openstack-meeting04:25
*** ianychoi has quit IRC04:27
*** pcaruana has joined #openstack-meeting04:42
*** links has joined #openstack-meeting04:51
*** brault has joined #openstack-meeting05:00
*** links has quit IRC05:04
*** brault has quit IRC05:05
*** Luzi has joined #openstack-meeting05:07
*** slaweq has joined #openstack-meeting05:11
*** links has joined #openstack-meeting05:12
*** pcaruana has quit IRC05:12
*** slaweq has quit IRC05:16
*** rubasov has quit IRC05:21
*** rcernin has quit IRC05:22
*** redrobot has quit IRC05:25
*** rcernin has joined #openstack-meeting05:38
*** kopecmartin|off is now known as kopecmartin05:46
*** brinzhang_ has joined #openstack-meeting05:50
*** rcernin has quit IRC05:51
*** jraju__ has joined #openstack-meeting05:53
*** links has quit IRC05:53
*** brinzhang has quit IRC05:54
*** yamamoto has quit IRC06:06
*** rcernin has joined #openstack-meeting06:09
*** slaweq has joined #openstack-meeting06:10
*** slaweq has quit IRC06:15
*** slaweq has joined #openstack-meeting06:21
*** pcaruana has joined #openstack-meeting06:21
*** tetsuro has joined #openstack-meeting06:26
*** radeks has joined #openstack-meeting06:35
*** ricolin has joined #openstack-meeting06:38
*** ricolin has quit IRC06:39
*** ociuhandu has joined #openstack-meeting06:42
*** tetsuro_ has joined #openstack-meeting06:46
*** ociuhandu has quit IRC06:46
*** tetsuro has quit IRC06:48
*** lpetrut has joined #openstack-meeting06:52
*** XSM_HUST has quit IRC06:52
*** brault has joined #openstack-meeting06:57
*** ociuhandu has joined #openstack-meeting07:04
*** rubasov has joined #openstack-meeting07:04
*** ociuhandu has quit IRC07:04
*** ociuhandu has joined #openstack-meeting07:07
*** ociuhandu has quit IRC07:08
*** trident has quit IRC07:08
*** tetsuro_ has quit IRC07:09
*** tesseract has joined #openstack-meeting07:11
*** trident has joined #openstack-meeting07:17
*** ralonsoh has joined #openstack-meeting07:19
*** tetsuro has joined #openstack-meeting07:21
*** trident has quit IRC07:22
*** ociuhandu has joined #openstack-meeting07:24
*** trident has joined #openstack-meeting07:31
*** radeks has quit IRC07:34
*** rcernin has quit IRC07:38
*** ykatabam has quit IRC07:43
*** tetsuro has quit IRC07:45
*** e0ne has joined #openstack-meeting07:56
*** jbadiapa has joined #openstack-meeting08:01
*** tssurya has joined #openstack-meeting08:02
*** rubasov has quit IRC08:05
*** rubasov has joined #openstack-meeting08:06
*** e0ne has quit IRC08:12
*** ociuhandu has quit IRC08:12
*** ociuhandu has joined #openstack-meeting08:15
*** links has joined #openstack-meeting08:17
*** jraju__ has quit IRC08:19
*** tssurya has quit IRC08:22
*** radeks has joined #openstack-meeting08:24
*** jawad_axd has joined #openstack-meeting08:29
*** rubasov has quit IRC08:29
*** tssurya has joined #openstack-meeting08:36
*** rubasov has joined #openstack-meeting08:40
*** e0ne has joined #openstack-meeting08:40
*** ykatabam has joined #openstack-meeting08:51
*** priteau has joined #openstack-meeting08:53
*** ttsiouts has joined #openstack-meeting09:00
*** lpetrut has quit IRC09:04
*** ianychoi_ has quit IRC09:09
*** rcernin has joined #openstack-meeting09:11
*** zhubx has joined #openstack-meeting09:26
*** boxiang has quit IRC09:29
*** links has quit IRC09:34
*** links has joined #openstack-meeting09:34
*** jraju__ has joined #openstack-meeting09:38
*** links has quit IRC09:39
*** rcernin has quit IRC09:41
*** ociuhandu has quit IRC09:43
*** brinzhang_ has quit IRC09:45
*** brinzhang_ has joined #openstack-meeting09:46
*** brinzhang_ has quit IRC09:46
*** ociuhandu has joined #openstack-meeting09:49
*** ociuhandu has quit IRC09:54
*** dkushwaha has quit IRC10:07
*** tssurya has quit IRC10:10
*** brinzhang has joined #openstack-meeting10:19
*** ykatabam has quit IRC10:20
*** ykatabam has joined #openstack-meeting10:22
*** ttsiouts has quit IRC10:23
*** ttsiouts has joined #openstack-meeting10:23
*** ttsiouts has quit IRC10:28
*** ianychoi has joined #openstack-meeting10:30
*** ianychoi has quit IRC10:45
*** belmoreira has joined #openstack-meeting10:45
*** ianychoi has joined #openstack-meeting10:45
*** janders has joined #openstack-meeting11:00
jandersg'day11:01
*** ttsiouts has joined #openstack-meeting11:03
*** ttsiouts has quit IRC11:07
*** b1airo has joined #openstack-meeting11:11
*** ttsiouts has joined #openstack-meeting11:12
b1airoo/11:12
*** janders has quit IRC11:14
*** carloss has joined #openstack-meeting11:16
*** janders has joined #openstack-meeting11:19
jandersg'day again11:19
ildikovb1airo: I'm around if you wanna chat :)11:19
janderssorry my Poisoned Apple crapped out again11:19
b1airooh hai11:19
jandersactually, I do have some potentially interesting AOB bits to share11:19
b1airowas briefly distracted in Slack-land11:19
janders1) I did get HDR200 to work eventually11:19
ildikovSlack-land is very distracting11:19
jandersyeah I need to rejoin that group again.. for some reason my slack config lost it11:20
b1airowant a fresh invite?11:20
jandersyes please11:21
jandersjacob.anders.au@gmail.com11:21
jandersthanks!11:21
janders---------------------------------------------------------------------------------------                    RDMA_Write BW Test Dual-port       : OFF          Device         : mlx5_3 Number of qps   : 1            Transport type : IB Connection type : RC           Using SRQ      : OFF TX depth        : 128 CQ Moderation   : 100 Mtu             :11:21
janders4096[B] Link type       : IB Max inline data : 0[B] rdma_cm QPs     : OFF Data ex. method : Ethernet--------------------------------------------------------------------------------------- local address: LID 0x01 QPN 0x08a7 PSN 0xef254c RKey 0x0a28af VAddr11:21
janders0x007fcb0b3d0000---------------------------------------------------------------------------------------                    RDMA_Write BW Test Dual-port       : OFF          Device         : mlx5_1 Number of qps   : 1            Transport type : IB Connection type : RC           Using SRQ      : OFF TX depth        : 128 CQ Moderation   : 100 Mtu11:21
janders: 4096[B] Link type       : IB Max inline data : 0[B] rdma_cm QPs     : OFF Data ex. method : Ethernet--------------------------------------------------------------------------------------- local address: LID 0x09 QPN 0x0ca1 PSN 0xc0192b RKey 0x0dc5cf VAddr 0x007f2058230000  remote address: LID 0x02 QPN 0x08aa PSN 0x17ff6e RKey 0x0a299e VAddr11:21
janders0x007f3dcb190000  remote address: LID 0x07 QPN 0x0c9f PSN 0x90ffb4 RKey 0x0dbcc3 VAddr 0x007f2cb58f0000--------------------------------------------------------------------------------------- #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]11:21
jandersMsgRate[Mpps]--------------------------------------------------------------------------------------- #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]   MsgRate[Mpps]65536 5000 11805.88 11498.61 0.183978---------------------------------------------------------------------------------------65536 5000 11537.78 11504.8811:21
janders0.184078---------------------------------------------------------------------------------------[root@hdr200-2 ~]#11:21
jandersoops, what a mess11:21
janders--------------------------------------------------------------------------------------- #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]   MsgRate[Mpps]--------------------------------------------------------------------------------------- #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]   MsgRate[Mpps]65536 500011:21
janders11805.88 11498.61 0.183978---------------------------------------------------------------------------------------65536 5000 11537.78 11504.88 0.184078---------------------------------------------------------------------------------------[root@hdr200-2 ~]#11:21
jandersstill a mess11:21
jandersokay I will give up pasting ib_write_bw outputs here11:21
janders:)11:21
janderslong story short I can get 2x10GB/s11:21
janders(after a long series of battles)11:22
*** gibi is now known as gibi_fly11:22
jandersHDR200 is essentially 2xHDR100 sharing a cable11:22
jandershence 2x10GB/s as opposed to 1x20GB/s11:22
jandersbut in any case it should make a nice interconnect for those NVMe boxes I was talking about in the past weeks11:22
jandersall of this is applicable to PCIe3 HDR200s - the non-Intel cards probably go 1x20GB/s :)11:23
jandersdue to PCIe4 goodness11:23
jandersVPI still isn't GA but hopefully soon. The above results are from the all-IB mode11:24
b1airoyeah i figured there would be some interesting caveats like that around squeezing full-bandwidth out of it11:25
*** ykatabam has quit IRC11:25
jandersib_write_bw can't do it11:26
jandersneeds wrappers11:26
b1airohmm, couldn't reinvite you. tried deactivating and reactivating your account, see if that gives you any notification11:26
jandersI think that might be pretty telling in regards to other apps being able to use it11:26
jandersthanks! I will keep an eye on the notification11:27
b1airoyeah, i wonder/guess that means a single QP can't do it...?11:27
jandersif not will fire up another laptop, that browser hopefull still has it11:27
jandersindeed11:27
jandersI think you need at least two threads to be able to get 20GB/s11:27
jandershowever - I'm mostly thinking of HDR200 as a badass storage interconnect, so not too worried (yet)11:28
janderswith HDR200 you essentially get ib0 and ib1, each with separate IP11:28
b1airoyeah fair enough. i guess latency-wise it isn't any different from 100G11:28
jandersso I think software that used to run cool on dual-port older cards (or just dual cards) will probably work okay11:28
jandershmm good question11:29
jandersI dont have any latency numbers from the CX5 nodes handy but can get fresh ones from CX611:29
janderswas around 1.0 usec if I remember correctly11:29
jandersand that rings a bell11:29
janders1.09-1.10 usec avt11:30
b1airofor 0 bit datagrams?11:30
jandersthat was just from a default run11:31
jandersthat's 2 bytes I think11:31
janderswould you like me to test any specific settings?11:31
b1aironah, don't have any specific applications in mind at this point11:33
b1airobut thanks!11:33
jandersno worries!11:33
jandersI hope to get GPFS going on those in the coming couple weeks, so should have better idea how the NVMe fitout and HDR200 works together11:33
jandersmy gut feel is the servers will probably be cool given enough parallelism11:34
jandersclients will probably suck unless there's enough parallelism11:34
janderswhich probably won't be the case for11:34
b1airolol, usual case for storage then11:34
janders"organic" workloads (it's a small system for now)11:34
jandersthe other funky thing I'm playing with is ansibleising onboarding OpenStack users/projects11:35
jandersand that includes assigning roles, quotas, creating default networking so that the users don't need to know/care, etc11:35
jandersI came across an interesting challenge11:35
jandershow to auto-generate reasonably strong passwords and store them in a reasonably secure way?11:36
jandersideally from ansible11:36
janders(obviously everything can be wrapped in shell module in the worst case...)11:36
jandersI was hoping that ansible can nicely write into ansible-vaults but doesn't seem to be the case11:36
jandersI'm using lookup/password with a flat file with locked down perms as a fallback11:37
b1airothat's a bit sad11:37
jandersdo you have any suggestions how to do this better?11:37
b1airoi wonder if `pass` could help11:40
jandersis that a third party app, or an ansible module?11:40
b1airoyep, looks like: https://docs.ansible.com/ansible/2.5/plugins/lookup/passwordstore.html11:41
b1airohttps://www.passwordstore.org/11:42
jandersnice!11:42
jandersit's a very similar mechanism to my flat file, except more secure11:42
jandersI was hoping to use ansible-vault like this, but given lack of support, this might do what I need11:42
jandersthanks Blair! :)11:42
b1airo:-)11:42
jandersin general what I'm trying to achieve is being able to define projects like this:11:43
jandersprojects:  sample-one:    name: sample-one    enabled: true    description: comment-1    quota:      instances: 2      cores: 2      ram: 2048      volumes: 2      gigabytes: 2      snapshots: 2      floatingips: 2      networks: 1      subnets: 1      routers: 1      ports: 50    members:      - user1      - user2    networking:11:43
janderscreate_default: true      create_router: true    credentials:      create_cli_creds: true      create_api_creds: true  sample-two:    name: sample-two    ...11:43
jandersoops11:43
jandersit's pretty yaml, trust me :)11:43
jandersessentially this defines quota, members, what "automagic" features are supposed to be in, etc11:44
janderswhen finished I will set defaults such that it will work reasonably well with almost no information except project name and memberships11:44
*** raildo has joined #openstack-meeting11:44
jandersinstead of gettins support guys to waste time helping new users create networks, etc, I figured I'll template *everything* and if the users know enough to go beyond that, they can go ahead11:45
jandersotherwise this is enough to start spinning up VMs using another template I will give em11:45
b1airoyeah, sounds like a plan. i always wanted us to do something like this with secgroups etc for Nectar11:46
jandersdid you guys have a similar cleanup mechanism for decom projects?11:46
b1airoyeah, let me dig it up...11:47
jandersI'm thinking how do approach that without onboarding too much risk of someone accidentally deleting everything on the Cloud11:47
b1airohttps://github.com/NeCTAR-RC/nectar-tools/tree/master/nectar_tools/expiry11:48
b1airoyeah gotta automate that for sure11:49
jandersnice, great work!11:49
jandersI just got my ansible to parse that yaml defining all project memberships - and create credsfile for each user for each project they are a part of11:50
jandersnow need to do the same for the API stuff11:50
jandersdo you know if it's possible to have the CLI tools use .config/openstack/clouds.yml?11:50
janderstraditionally CLIs tend to prefer some sort of a creds file with environment variables and APIs take clouds.yml11:51
jandersone could script populating creds from clouds.yml11:51
jandersbut I wonder if it's possible to just have the CLIs read it "natively"11:51
jandersdo you know?11:51
b1airolooks like it is11:53
b1airohave never used it personally, but... https://docs.openstack.org/python-openstackclient/stein/cli/authentication.html11:54
*** brault has quit IRC11:54
jandersthanks! I will keep digging11:54
b1airo"The command line arguments are processed and a configuration is loaded from clouds.yaml if --os-cloud is provided"11:55
jandersI think general consensus is it should work, but I haven't had much success just yet11:55
jandersah11:55
jandersit was just a stupid default keystone version11:55
*** brault has joined #openstack-meeting11:55
*** brault has quit IRC11:55
*** brault has joined #openstack-meeting11:56
jandersokay... last one of my "interesting" questions11:56
janders:)11:56
jandersit seems that11:56
jandersdepending on the kind of a loop used in ansible11:56
jandersit is or it is not possible to reference the "key" variable11:56
b1airoon this week's episode of The Chaser (OpenStack edition)11:56
jandersprojects:  sample-one:    name: sample-one11:56
*** lseki has joined #openstack-meeting11:57
b1airooh yeah? that doesn't surprise me tbh11:57
jandersif I use with_dict I can reference the name either via item.key or item.0.name11:58
janderswhich would allow me to kill the name field entirely11:58
jandersthis, however, does not seem to work with with_subelements11:58
janderswhich I need for those bits where I have to traverse a two-dimensional array (sort, of)11:58
jandersI might be messing up the syntax slightly, but I think I got the challenge right11:59
jandershave you come across this limitation?11:59
jandersgoogled a ton of ppl running into this but no solution - hence the redundant "name" field is still there12:00
jandersnot a big deal, just puzzling me12:00
jandersokay - we're out of time12:00
jandersthanks for all the hints Blair! :)12:00
b1aironah 'fraid not, only messed with simple loops in ansible thus far12:00
jandersright! no worries12:01
b1airosuspect oneswig et al might have some hints though given kayobe is mainly ansible12:01
jandersindeed!12:01
jandersmight try again next week then! :)12:01
b1airoright, i'm off to make my eyes bleed in peoplesoft again.. :-/12:02
*** rfolco has joined #openstack-meeting12:06
*** lpetrut has joined #openstack-meeting12:13
*** ociuhandu has joined #openstack-meeting12:13
*** ociuhandu has quit IRC12:14
*** ociuhandu has joined #openstack-meeting12:16
*** ociuhandu has quit IRC12:16
*** jamesmcarthur has joined #openstack-meeting12:25
*** jraju__ is now known as links12:29
*** jamesmcarthur has quit IRC12:30
*** ociuhandu has joined #openstack-meeting12:38
*** njohnston has joined #openstack-meeting12:46
*** e0ne has quit IRC12:46
*** mriedem has joined #openstack-meeting12:49
*** eharney has joined #openstack-meeting12:51
*** e0ne has joined #openstack-meeting12:52
*** rbudden has joined #openstack-meeting13:03
*** dhellmann has quit IRC13:06
*** ociuhandu has quit IRC13:12
*** ociuhandu has joined #openstack-meeting13:13
*** ociuhandu has quit IRC13:18
*** ociuhandu has joined #openstack-meeting13:26
*** ociuhandu has quit IRC13:31
*** eharney has quit IRC13:32
*** eharney has joined #openstack-meeting13:32
*** enriquetaso has joined #openstack-meeting13:36
*** panda is now known as panda|ruck13:40
*** ociuhandu has joined #openstack-meeting13:41
*** panda|ruck is now known as panda|rover13:45
*** redrobot has joined #openstack-meeting13:50
*** jawad_axd has quit IRC13:55
*** liuyulong has joined #openstack-meeting13:59
*** Luzi has quit IRC13:59
*** liuyulong_ has joined #openstack-meeting14:00
liuyulongtest14:00
liuyulong_test14:00
slaweqhi liuyulong_ :)14:00
liuyulong_hi14:00
liuyulong#startmeeting neutron_l314:00
openstackMeeting started Wed Sep 11 14:00:40 2019 UTC and is due to finish in 60 minutes.  The chair is liuyulong. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:00
openstackThe meeting name has been set to 'neutron_l3'14:00
liuyulong#chair liuyulong_14:01
openstackCurrent chairs: liuyulong liuyulong_14:01
*** liuyulong has left #openstack-meeting14:01
*** liuyulong has joined #openstack-meeting14:01
liuyulong#chair haleyb14:02
openstackCurrent chairs: haleyb liuyulong liuyulong_14:02
liuyulong#chair slaweq14:02
openstackCurrent chairs: haleyb liuyulong liuyulong_ slaweq14:02
haleybhi14:02
liuyulongJust in case, :)14:02
liuyulong#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:02
liuyulongI have no announcement this week.14:03
liuyulongIf you guys have, please tap the keyboard directly. : )14:04
ralonsohhi14:05
slaweqI have one short thing14:05
slaweq(or 2)14:05
slaweqjust a reminders:14:05
slaweqShanghai PTG planning etherpad14:05
slaweq    https://etherpad.openstack.org/p/Shanghai-Neutron-Planning14:05
slaweqShanghai Forum brainstorming etherpad14:05
slaweq    https://etherpad.openstack.org/p/neutron-shanghai-forum-brainstorming14:05
slaweqplease put there Your proposals for topics14:05
slaweqthat's all from me :)14:06
liuyulongI have a lot of ideas.14:07
liuyulongAny other announcements?14:09
liuyulongOK, let's move on.14:09
liuyulong#topic Bugs14:10
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:10
liuyulong#link http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009261.html14:11
liuyulongNate Johnston was our bug deputy last week, thanks.14:11
njohnstonmy pleasure14:11
liuyulongMost of those bugs are related to CI. IMO14:11
njohnstonI agree, I think the one most aligned with L3 is: https://bugs.launchpad.net/bugs/184293714:12
openstackLaunchpad bug 1842937 in neutron "Some ports assigned to routers don't have the correspondent routerport register" [Undecided,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:12
liuyulongYes, it is14:14
ralonsohsorry, I was in other chat14:15
ralonsohI have a patch in gerrit for this14:15
ralonsohone sec14:15
*** diablo_rojo has joined #openstack-meeting14:15
ralonsoh#link https://review.opendev.org/#/c/680413/14:15
ralonsohthe point is this patch is not solving the problem14:15
liuyulongI'm looking at that. :  )14:15
ralonsohbut mitigating it: when the port, during the sync, does not have all the ips (and subnets)14:16
ralonsohalthough in the Neutron DB the information is correctly populated14:16
ralonsohthis patch is forcing the DHCP agent to retrieve, at this point, the correct information from the server14:16
liuyulongOne small concern is that we may take care of such DB query, do not make it slow like others once we had.14:16
ralonsohthat's the point14:17
ralonsohif the port does not have this information, we'll force a full resync14:18
ralonsohthis is going to be slower, for sure14:18
*** ricolin has joined #openstack-meeting14:18
ralonsohthis is happening ONLY when the port information is not correct/not totally populated14:18
ralonsoheventually, if the port does not have those IPs, the server will generate other IPs and the agent will resync the whole subnet14:19
liuyulongThis new query is related to remove router interface only?14:20
ralonsohremove? no, we are not removing it14:21
ralonsohthe DHCP port is present in the system14:21
liuyulongOK, I may have to take a deep look of that patch.14:22
liuyulongOne more interesting thing is that I noticed our local queens performance, the attach interface API will takes more than 60s+.14:22
liuyulongThat's will be another story.14:23
*** electrofelix has joined #openstack-meeting14:26
liuyulongNext14:26
liuyulong#link https://bugs.launchpad.net/neutron/+bug/184328514:27
openstackLaunchpad bug 1838760 in neutron "duplicate for #1843285 Security groups don't work for trunk ports with iptables_hybrid fw driver" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)14:27
liuyulong#undo14:27
openstackRemoving item from minutes: #link https://bugs.launchpad.net/neutron/+bug/184328514:27
liuyulongWrong link.14:28
liuyulong#link https://bugs.launchpad.net/neutron/+bug/184232714:29
openstackLaunchpad bug 1842327 in neutron "Report in logs when FIP associate and disassociate" [Medium,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:29
liuyulongThis patch looks good to me now.14:29
liuyulongFor the log one.14:29
liuyulong#link https://review.opendev.org/#/c/679667/14:30
*** rubasov has quit IRC14:30
liuyulongAnd it has a l3_db change here: https://review.opendev.org/#/c/680976/14:30
ralonsohyes, the second one requested by Terry14:31
ralonsohRyan14:31
ralonsohand makes sense to implement this patch https://review.opendev.org/#/c/680976/14:31
*** b1airo has quit IRC14:31
ralonsohwe should have only one place to decide if FIP is associated, disassociated or nothing14:31
liuyulongMake sense, I've changed these code a long time ago.14:33
liuyulongAnd once we have a potential consensus which is updating the floating IP by empty "{}" API input, l3 plugin which change nothing, and no errors.14:34
*** priteau has quit IRC14:34
liuyulongSo please consider such scenario. And maybe make sure that association_event will not be added for such scenario.14:35
ralonsohok14:36
*** ttsiouts has quit IRC14:37
*** zhubx has quit IRC14:37
*** zhubx has joined #openstack-meeting14:37
*** ttsiouts has joined #openstack-meeting14:37
liuyulong#link https://bugs.launchpad.net/neutron/+bug/184302514:37
openstackLaunchpad bug 1843025 in neutron "FWaaS v2 fails to add ICMPv6 rules via horizon" [High,In progress] - Assigned to Brian Haley (brian-haley)14:38
liuyulongIt is fixed IMO, just need a backport.14:38
haleybi just did a cherry-pick on that one14:38
haleybso maybe it's just a duplicate?14:39
liuyulongNo, I noticed the bug assignee change, so I have no actions. : )14:40
liuyulongOK, that's all bugs from me.14:40
liuyulongAny other bugs?14:41
*** zhubx has quit IRC14:41
*** zhubx has joined #openstack-meeting14:41
*** ttsiouts has quit IRC14:42
liuyulongOK, let's move on.14:42
liuyulong#topic On demand agenda14:42
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:42
*** belmoreira has quit IRC14:43
*** zhubx has quit IRC14:43
liuyulongLast week I started the topic of "IPv6", and I read lots of neutron specs about floating IPv6.14:43
*** zhubx has joined #openstack-meeting14:44
liuyulong#link https://review.opendev.org/#/q/status:abandoned+project:openstack/neutron+branch:master+topic:bp/ipv6-router-and-dvr14:44
liuyulong#link https://review.opendev.org/#/q/ndp14:44
liuyulongWe have this merged and implemented:https://review.opendev.org/#/c/139731/14:45
liuyulongBad link, it should be this: https://review.opendev.org/#/c/101306/ "14:46
liuyulongSupport Router Advertisement Daemon (radvd) for IPv6"14:46
liuyulong#link https://review.opendev.org/#/c/139731/14:46
haleybthat and floating IPv6 are different things14:46
liuyulongthis is the spec for floating IPv6.14:46
*** links has quit IRC14:46
liuyulonghaleyb, yes, just a gerrit query. : )14:47
haleybi think only one plugin supports floating IPv6, we had decided years ago not to do it in the core code14:47
haleybis there a use case for doing it?  it's not like there's a shortage of IPv6 addresses :)14:49
liuyulongYes, IIRC, midonet may support floating IPv6.14:49
liuyulongAfter the L3 meeting last week, Donny Davis gave me their IPv6 deployment details.14:50
haleybi know swami has been working on "fast exit" IPv6 w/DVR, which would be useful14:50
liuyulongThey uses the BGP.14:51
*** panda|rover is now known as panda|ruck14:52
liuyulongBut it may also need some extra works.14:52
haleybright, it's a good use of BGP, assuming your infrastructure supports it14:52
liuyulong1. Access the public network until the user apply or pay for it.14:53
liuyulong2. Qos for IPv6 traffic to external world.14:53
*** jbadiapa has quit IRC14:54
liuyulongOure IPv4 floating IP has both abilities now.14:54
haleybso floating IP allocation costs $$ ?14:56
*** janders has quit IRC14:56
liuyulongTo achive these, neutron may need some new resource "IPv6 address" or "Floating IPv6 Address" and the QoS binding for it.14:57
liuyulonghaleyb, no, bandwidth costs money.14:57
haleybliuyulong: i was wondering how the user "paid" for external access in 1) above14:58
haleybone way is to charge for a floating IP address14:58
liuyulongIt can be one way.14:59
haleybi hope not to have floating IPv614:59
liuyulongIn my experience, pay for some bandwidth is more popular in China.15:00
haleybwe are at time15:00
liuyulongOK, then let's end here.15:01
liuyulong#endmeeting15:01
slaweqo/15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:01
openstackMeeting ended Wed Sep 11 15:01:05 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-09-11-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-09-11-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2019/neutron_l3.2019-09-11-14.00.log.html15:01
ralonsohbye15:01
haleybbye15:01
*** liuyulong_ has quit IRC15:02
*** ayoung has quit IRC15:07
*** jamesmcarthur has joined #openstack-meeting15:08
*** ayoung has joined #openstack-meeting15:10
*** zhengMa has joined #openstack-meeting15:20
*** rubasov has joined #openstack-meeting15:21
*** gyee has joined #openstack-meeting15:23
*** macz has joined #openstack-meeting15:29
*** rosmaita has joined #openstack-meeting15:29
*** igordc has joined #openstack-meeting15:31
*** mattw4 has joined #openstack-meeting15:34
*** eharney has quit IRC15:37
*** e0ne has quit IRC15:42
*** e0ne has joined #openstack-meeting15:42
*** ayoung has quit IRC15:43
*** ayoung has joined #openstack-meeting15:45
*** eharney has joined #openstack-meeting15:50
*** Garyx has quit IRC15:53
*** Garyx has joined #openstack-meeting15:54
*** diablo_rojo has quit IRC15:59
*** diablo_rojo has joined #openstack-meeting15:59
jungleboyj#startmeeting Cinder16:00
whoami-rajatHi16:00
openstackMeeting started Wed Sep 11 16:00:29 2019 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
smcginniso/16:00
jungleboyjcourtesy ping:  jungleboyj whoami-rajat rajinir lseki carloss pots woojay erlon geguileo eharney rosmaita enriquetaso e0ne smcginnis davidsha walshh_ xyang hemna _hemna tosky sfernand16:00
eharneyhi16:00
rosmaitao/16:00
walshh_hi16:01
jungleboyj@!16:01
_pewp_jungleboyj |ʘ‿ʘ)╯16:01
*** deiter has joined #openstack-meeting16:01
*** geguileo has joined #openstack-meeting16:01
jungleboyjLooks like we have the usual suspects here and I need to try to wrap up the meeting early this week if possible.16:02
jungleboyjSo ... #announcements16:03
jungleboyj#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:03
jungleboyjAll the announcements are actually rosmaita 's .  So, I will hand the mic to him.16:03
e0nehi16:03
rosmaitathanks16:03
rosmaitaok, release update16:03
rosmaitaos-brick for train (0.11.0) was released last week16:04
rosmaitaand we  have a stable/train branch for os-brick16:04
jungleboyj\o/16:04
*** mattw4 has quit IRC16:04
rosmaitaso just a reminder that bugfixes need to go into master and then be proposed to stable/train16:04
smcginnisWe should probably do a 1.0 release for os-brick. I think it's "production ready" now.16:04
*** mattw4 has joined #openstack-meeting16:04
smcginnisFor ussuri ^16:04
eharneyos-brick is past 2.0 already :)16:04
rosmaitaok, we can schedule a major release for brick in U16:05
jungleboyjYeah. 2.10.016:05
rosmaitawe could do like java and release 6.016:05
smcginnisOK, that's what I thought.16:05
enriquetasoo/16:05
rosmaitasorry, i had the wrong version number there16:06
jungleboyj:-)16:06
rosmaitathe brick cincerclient ext is 0.11.0, was released earlier this week16:06
rosmaitaand it has a stable branch too, so same deal with any bugfixes -- master then stable/train16:07
rosmaitafinally, the cinderclient new major release 5.0.0 is almost ready16:07
rosmaitaone patch remains:16:07
rosmaita#link https://review.opendev.org/#/c/653831/16:07
rosmaitait's still in check, will need some reviews later today please16:08
rosmaitathen we can release as soon as the change merges16:08
jungleboyjrosmaita:  ++16:08
smcginnisAt least the gate seems a little better today.16:08
rajiniro/16:08
rosmaitaand when we release cinderclient, we'll have a stable/train branch, etc16:09
jungleboyjSo, other than the one patch we are good to have all the libraries out on time?16:09
rosmaitayes, i think we are in good shape16:09
rosmaitacinderlib is a cycle-trailing release model16:09
rosmaitaso that one comes after cinder train release16:10
jungleboyjOk.  rosmaita  Did anyone make sure that the client changes that are being released match up with what looks to go into the server for Train?16:10
rosmaitaummm ... not sure16:10
rosmaitai forgot to check16:10
*** mattw4 has quit IRC16:10
jungleboyj:-)  We should probably do that before we cut the client.16:10
rosmaitayes, i will take that action item16:11
jungleboyjrosmaita:  Awesome.  Thank you.16:11
rosmaita#action rosmaita verify MAX_VERSION for client16:11
rosmaitai think that's all for releases unless anyone has a question16:11
*** deiter has quit IRC16:11
jungleboyjThank you again for shepherding all that.16:12
enriquetasorosmaita++16:12
smcginnisHmm, according to https://opendev.org/openstack/cinder/src/branch/master/cinder/api/openstack/rest_api_version_history.rst, we haven't added any MV's in train?16:12
rosmaitathat should make things easy16:13
jungleboyjThat is possible.16:13
jungleboyj:-)16:13
smcginnisHuh, I guess so - https://opendev.org/openstack/cinder/src/branch/master/cinder/api/microversions.py#L16016:13
rosmaitaand https://opendev.org/openstack/python-cinderclient/src/branch/master/cinderclient/api_versions.py#L3216:14
rosmaitaso looks like we are ok16:15
jungleboyjGood news.  :-)16:15
jungleboyjOk.  So I think we can move along then.16:16
rosmaitaok, Shanghai Forum Topics16:16
jungleboyj++16:16
rosmaita#link https://etherpad.openstack.org/p/cinder-shanghai-forum-proposals16:16
rosmaitaso, the forum is supposed to give us a chance to discuss long term strategy with users/operators/packagers16:17
rosmaitageguileo suggested a general feedback topic, so that's on the etherpad16:17
jungleboyjrosmaita: I have a  couple to put in there that came up at the mid-cycle.  Will do that today.16:17
rosmaitabut if anyone has a particular topic, that would be good16:18
geguileojungleboyj: thanks16:18
jungleboyjrosmaita: ++ Would be great if we got people to show up for that and give feedback.16:18
rosmaitai sent a note to the ML [ops] to see if any operators want us to address anything16:18
rosmaitaanyway, we have to formally submit topics at the end of next week, so if you could get topics on the etherpad before the next cinder meeting, that would be awesome16:19
rosmaitathe idea is we are supposed to be "brainstorming" and then vote for what the team wants to submit16:19
jungleboyjSounds like a good plan.16:20
rosmaitaone other thing, even if you won't be there, please add a topic if you have one16:20
rosmaitaok, that's all for that16:20
rosmaitaone more etherpad for you:16:20
rosmaita#link https://etherpad.openstack.org/p/cinder-ussuri-ptg-planning16:20
* jungleboyj sits back and relaxes16:21
jungleboyj:-)16:21
rosmaitai don't think our sessions have been confirmed yet, but we can start collecting discussion points16:21
rosmaitaalso, i don't know if we'll be able to do remote joining for this16:21
jungleboyjI had requested a 2 day session with 2 to 4 hours separate for on-boarding.16:21
rosmaitai haven't heard much about the facilities16:21
*** ricolin has quit IRC16:22
rosmaitaok, so we should expect at least 1.5 days16:22
jungleboyjTheoretically BlueJeans should work again.  My co-workers can join from China.16:22
smcginnisNo projectors. Zoom blocked by the great firewall. Shared large rooms.16:22
* jungleboyj gags16:22
rosmaitayeah ... so this should be fun16:23
smcginnisParis all over again, with the fun parties and good pastries.16:23
smcginnis*without16:23
jungleboyjYou mean without?16:23
jungleboyjYeah.16:23
e0ne:(16:23
eharneyi'd settle for an IRC live stream of the discussions16:23
*** thgcorrea has joined #openstack-meeting16:23
rosmaitawell, we'll always have paris16:23
eharney:P16:23
rosmaitai guess we could do IRC16:23
rosmaitaif we use our channel, we get an automatic transcript16:23
jungleboyjYeah,  Well, isn't that kind of what the ehterpad is?16:23
smcginnisHopefully we can get to freenode.16:24
whoami-rajatIRC live stream?16:24
jungleboyjOMG, so we will all be in the same room typing to each other.16:24
rosmaitasmcginnis: you are Mr. Cheerful today16:24
jungleboyjDo I have to go to China?16:24
smcginnisrosmaita: :)16:24
jungleboyjsmcginnis:  Dude you were cheerful on Monday.16:24
geguileowe could always VPN out of the country and use whatever we want16:24
smcginnisSorry, trying not to be too pessimistic, but there are a lot of little concerns with how things are shaping up.16:24
smcginnisgeguileo: That's what I've had to do while there.16:25
jungleboyjgeguileo:  Yeah, I think I have some freedom with Lenovo VPN.  I am working on setting up a backup but no idea what the latency will be jumping through my house.16:25
smcginnisWorks well, as long as you have a VPN that doesn't get blocked.16:25
geguileojungleboyj: I doubt my house would be any better  XD16:25
rosmaitayeah, i thought there was some kind of vpn-detection-and-blocking ability16:25
smcginnisrosmaita: Many are blocked, but a few still work.16:25
rosmaitaok, so for now, let's pretend we'll all be able to have a great discussion, and please add ideas to the etherpad16:26
jungleboyjAnyway, no point grumbling about what we can't control.16:26
jungleboyjrosmaita:  That a boy.16:26
smcginnisYep, let's focus on what we want to accomplish.16:26
rosmaitahttps://etherpad.openstack.org/p/cinder-ussuri-ptg-planning16:26
rosmaitaok, that's all from me16:26
jungleboyjWell, this is good to see names going into the etherpad as attendees.16:27
jungleboyjOk.  So, it looks like the next topic is ...16:27
jungleboyj#topic Please review my Train feature ...16:27
*** openstack changes topic to "Please review my Train feature ... (Meeting topic: Cinder)"16:27
smcginnisHah16:27
jungleboyjWe need to add a louder horn, better fuel efficiency,16:28
jungleboyjOther ideas?16:28
jungleboyjSo, it looks like we have a few features that need review.16:29
eharneyyes16:29
eharneyvolume rekey is one: https://review.opendev.org/#/c/664976/16:30
* jungleboyj is clicking through them.16:30
rosmaitai need to re-review that and the image compression patch16:30
*** ociuhandu has quit IRC16:30
zhengMathanks!16:30
rosmaitae0ne's patch looks pretty straightforward, assuming everyone is good with removing BackupDriverWithVerify16:31
e0ne:)16:31
jungleboyjYeah.16:31
eharneylooks sensible to me16:31
jungleboyjsmcginnis:  Loves removing code.16:31
jungleboyj:-)16:31
e0newe discussed in during the last PTG...16:31
rosmaitai thought i remembered something like that16:32
rosmaitai don't mean to leave out whoami-rajat's patch, we definitely want to get that into Train16:33
jungleboyjDon't we need a release note on that?16:33
jungleboyjrosmaita: ++16:33
eharneyrelease note for which?16:33
rosmaitajungleboyj: i don't think there's really anything to say, it's an unused interface16:33
jungleboyje0ne's patch.16:33
eharneyrosmaita: i agree16:33
rosmaitai assumed you meant e0ne's patch16:33
e0nejungleboyj: I can add it but I don't think somebody uses it16:33
rosmaitai think the less said the better16:34
jungleboyjAh, ok.  I guess you are right if it isn't being used.16:34
e0ne5 years and nothing in cinder repo16:34
jungleboyjOk.  I am good as is and will look at the other patches.  It looks like they all are pretty close.16:35
smcginnisYeah, release note might just be confusing on that one.16:35
*** ekcs has joined #openstack-meeting16:35
jungleboyjgotcha.16:35
jungleboyjOk, anything else to cover on reviews?16:35
eharneyi added a question to the default vol type patch16:35
rosmaitai have a question about a feature freeze exception16:36
jungleboyjrosmaita: Go ahead16:36
rosmaitathe change to glance that introduces 'cinder_encryption_key_deletion_policy' merged last week16:36
*** ralonsoh has quit IRC16:37
rosmaitado i need a FFE for a patch for us to start using it?16:37
rosmaitait's not really a feature, but it's not really a bug either16:37
* jungleboyj defers to the release guy in the room16:37
jungleboyjsmcginnis:  ...16:37
eharneythat mostly just consists of adding a field to the glance metadata from cinder, right?16:37
rosmaitaexactly16:37
jungleboyjThat doesn't sound like it requires an FFE.16:38
rosmaitai don't think we want any configuration on our end?16:38
jungleboyjTo enable a feature that has merged in Glance.16:38
e0nejungleboyj: +116:38
eharneyIMO we need to land it either way, an FFE is probably overhead w/o a lot of benefit for a small change like that16:38
jungleboyjeharney:  ++16:38
smcginnisFFE is up to the PTL, but if we need that, we should get the change in.16:38
rosmaitayeah, i'll get a patch up today or early tomorrow16:39
jungleboyjIt was something we agreed to at the PTG.  I think we are good to get that in without complicating things.16:39
rosmaitaok, cool16:39
jungleboyjIt is unlikely to break Cinder.16:39
jungleboyjI assume?16:39
rosmaitapretty unlikely16:39
rosmaitafairly unlikely16:39
jungleboyjOk.  And we still have a bit of runtime.16:39
jungleboyjLets get the patch up and take a look.16:40
rosmaitaok16:40
*** lpetrut has quit IRC16:40
jungleboyj#topic open discussion16:40
*** openstack changes topic to "open discussion (Meeting topic: Cinder)"16:40
jungleboyjAnyone have other topics for today?16:40
jungleboyjThat sounds like a no.16:41
jungleboyjSo, going to give people 19 minutes of their day back.16:41
rosmaita\o/16:42
jungleboyjThank you all for coming.16:42
jungleboyjrosmaita: Thanks for helping get this release out properly!16:42
whoami-rajatThanks !16:42
jungleboyj#endmeeting16:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:42
openstackMeeting ended Wed Sep 11 16:42:23 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-09-11-16.00.html16:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-09-11-16.00.txt16:42
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-09-11-16.00.log.html16:42
rosmaitaoh yeah, core reviewers please keep an eye on https://review.opendev.org/#/c/653831/16:42
jungleboyjWill do.16:42
*** ociuhandu has joined #openstack-meeting16:46
*** geguileo has quit IRC16:46
*** ayoung has quit IRC16:51
*** ayoung has joined #openstack-meeting16:53
*** e0ne has quit IRC16:54
*** tesseract has quit IRC16:57
*** gibi_fly is now known as gibi_bus16:58
*** mriedem is now known as gibi_zeppelin16:58
*** gibi_zeppelin is now known as gibi_submarine16:58
*** gibi_submarine is now known as mriedem16:58
*** zhengMa has left #openstack-meeting17:02
*** ociuhandu has quit IRC17:08
*** ayoung has quit IRC17:14
*** ayoung has joined #openstack-meeting17:17
*** ociuhandu has joined #openstack-meeting17:27
*** ociuhandu has quit IRC17:31
*** brault has quit IRC17:33
*** brault has joined #openstack-meeting17:35
*** brault has quit IRC17:35
*** brault has joined #openstack-meeting17:35
*** kopecmartin is now known as kopecmartin|off17:38
*** ayoung has quit IRC17:39
*** ayoung has joined #openstack-meeting17:42
*** liuyulong has quit IRC17:45
*** e0ne has joined #openstack-meeting17:55
*** electrofelix has quit IRC17:56
*** e0ne has quit IRC17:59
*** jamesmcarthur has quit IRC18:06
*** jamesmcarthur has joined #openstack-meeting18:07
*** jamesmcarthur has quit IRC18:11
*** Garyx has quit IRC18:12
*** Garyx has joined #openstack-meeting18:16
*** e0ne has joined #openstack-meeting18:17
*** panda|ruck is now known as panda|ruck|off18:21
*** jbadiapa has joined #openstack-meeting18:27
*** radeks has quit IRC18:40
*** eharney has quit IRC18:55
*** enriquetaso has quit IRC19:00
*** senrique_ has joined #openstack-meeting19:01
*** brault has quit IRC19:02
SotK#startmeeting storyboard19:02
openstackMeeting started Wed Sep 11 19:02:41 2019 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: storyboard)"19:02
openstackThe meeting name has been set to 'storyboard'19:02
*** senrique_ has quit IRC19:02
*** thgcorrea has quit IRC19:03
SotK#link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda19:03
SotKI don't think there's anything to announce this week, and assume nothing new on the migrations front too19:03
SotK#topic PTG + Forum19:04
*** openstack changes topic to "PTG + Forum (Meeting topic: storyboard)"19:04
fungidiablo_rojo: you're up!19:05
diablo_rojoOh jeez that was fast.19:05
diablo_rojoI wrote a thing a while back19:05
diablo_rojoif it looks alright. I will submit it.19:06
fungi#link https://etherpad.openstack.org/p/storyboard-shanghai-ptg-planning19:06
fungithat thing?19:06
*** enriquetaso has joined #openstack-meeting19:08
*** eharney has joined #openstack-meeting19:08
diablo_rojoThats the one19:08
SotKlooks good to me19:09
fungiseems great. thanks!19:09
fungiship it19:09
diablo_rojoCool.19:11
diablo_rojoAt some point we should discuss an outline for both of the different onboardings19:12
diablo_rojoBut that can wait to see if the Forum session gets selected.19:12
diablo_rojoThats all I had on this topic for now.19:12
SotKthanks :)19:13
SotK#topic In Progress Work19:13
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:13
SotKI've not done a huge amount other than a quick look over the slow query digest19:15
fungiany first impressions?19:16
fungii'm happy to refresh it again too if need be19:16
diablo_rojomordred, around by chance?19:17
fungi#link http://files.openstack.org/user/fungi/storyboard/ slow query analysis19:17
fungii think mordred is still out of pocket until next week19:18
fungii think that digest-output.txt.gz is telling us that 50.5% of the total query time was spent on "SELECT stories tasks stories"19:19
*** rubasov has quit IRC19:19
funginot quite sure what that abbreviation means19:22
fungi(it doesn't seem to be actual sql)19:22
SotKI think its just the tables being queried, the full query is further down in the file19:22
fungiyeah, i'm guessing that's the one marked "Query 1"19:23
SotKyep19:23
fungiaverage exec time is 91s19:23
SotKI think that query is the generic story getting query, but I'm not certain19:23
SotKits certainly ugly and slow19:23
fungithe query itself wraps 22 lines on my 80-column terminal, yes19:25
diablo_rojoOuch19:25
fungiwell, that's the explain expansion of it19:25
SotKI've not done enough database optimising to immediately know which the worst parts are, but I'll try to experiment with ways to simplify it19:25
fungiso basically as verbose an interpretation of the query as possible, but that's indeed still big19:26
fungii wonder whether there's some way to decorate queries in the application so that we get useful backtracking breadcrumbs in the query logs19:26
fungicorvus: if you're around, maybe you know whether that's a thing?19:27
corvusack; catching up19:28
*** artom has quit IRC19:28
corvusthat is an excellent idea; i don't know of a way to do that, but i don't consider my knowledge there exhaustive.  i'd probably look into not using the slow query log and instead doing something in python19:30
fungihrm, like wrap all orm calls in some timer code?19:31
corvusyeah, something like that19:31
fungithat would indeed give us the ability to, say, raise non-terminating exceptions in the application logs which include tracebacks19:31
fungiwhenever a query runs over a certain threshold19:32
fungithough maybe harder to identify frequently-run queries which in aggregate add up to a lot of waiting19:32
corvus#link https://docs.sqlalchemy.org/en/13/faq/performance.html19:32
corvusthat may not be too hard19:32
fungiyeah, i guess they could be bucketed19:33
fungithat's a very helpful-looking document. thanks!!!19:33
SotKindeed, I can try some of the things described there this weekend sometime hopefully19:34
fungithat would be awesome19:35
fungii'll try to digest the recommendations there too19:35
fungiwe can probably couple it with slow query logging to correlate the views from the db end and teh app end19:35
fungione other thing i noticed when turning the slow log back on... it took a while to start registering any queries slower than 1s, and days to start hitting any over 20s, but eventually started regularly logging some which took minutes19:36
*** artom has joined #openstack-meeting19:37
fungiit may just be coincidence, but i wonder whether we're seeing some sort of degradation over time19:37
fungias i did restart mysqld in the process of troubleshooting whether i had properly reenabled the slow log19:37
diablo_rojoHuh19:38
SotKinteresting, sounds like maybe yes19:38
diablo_rojothat does sound likely19:39
fungichecking our cacti graphs, that production server is fairly under-utilized, but it does use the majority of available memory for cache19:41
fungi#link http://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=66356&rra_id=all19:41
funginot really sure if giving it more memory would help or not19:42
fungiaccording to top, apache is using more resident memory than mysqld, but mysqld is using more virtual memory19:42
fungialso rabbit is using rather a lot of virtual memory19:43
fungii wonder if cache memory for mysqld is getting starved out over time by one of its competitors there19:43
fungii suppose i could do some experiments tracking query times before and after restarts of apache and rabbit19:44
fungiand ultimately, also restarts of mysql19:44
SotKseems worth trying19:45
*** eharney has quit IRC19:45
fungii've put those experiments on my to do list19:46
SotKthanks :)19:46
SotK#topic Open Discussion19:47
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"19:47
diablo_rojothanks fungi :)19:47
diablo_rojoI got nothing for open discussion.19:47
SotKfungi: you also mentioned external group management in the channel earlier19:47
fungiso one thing i'm finding is increasing in urgency is group management19:47
fungiyeah19:47
diablo_rojoMakes sense.19:47
fungithere are an increasing number of openstack projects which are under vmt oversight and migrating to storyboard19:48
fungiwe have several at my last count19:48
*** vishalmanchanda has quit IRC19:48
diablo_rojoThats good news I suppose. Though I suppose we should write some script or something to import the groups.19:49
diablo_rojoMaybe an addition onto the current migration script?19:49
fungiwell, before that even, i want to start publishing recommended practices for manitaining core security reviewer groups and for lp we already have a self-managed solution for that. for sb i think what we've discussed in the past is either synchronizing groups from gerrit or creating them from structured data files in git19:49
SotKthat matches my memory19:49
fungithe challenge i've run up aganist in trying to plan that mechanism (either of them) is that we don't necessarily have preexisting accounts in sb19:50
fungiso i'm trying to figure out how best to deal with that19:50
SotKwill a similar method to the one used by the migration scripts work19:51
fungibut also, we need a good discoverable unique handle for each user which we can use to perform lookups19:51
SotK?19:51
SotKyeah19:51
diablo_rojoI guess we skip the ones that don't have accounts19:51
diablo_rojoand add them later?19:51
SotKI guess the closest we have to that is openid19:52
fungiyeah, i think i can say that users need to create an account in sb before they'll be added to the group by whatever automated process we settle on19:52
diablo_rojoThat works for me19:52
SotKthen as long as they use the same openid for gerrit and storyboard it should be reasonably easy to match them right?19:53
fungibut right we'd for example need to map an openid which the person creating the list of users (think... a ptl) can find and add to the list19:53
SotKunless gerrit makes it hard to find users' openids19:53
SotKoh I was only considering the "mirror gerrit groups" approach19:54
fungiwell, yeah, gerrit doesn't expose openids last i checked so that would need a direct db query (and recreatnig from scratch when users move into notedb in later gerrit versions)19:54
SotKfar less than ideal then19:54
SotKhmm19:54
fungialso using gerrit as a proxy for group management means creating groups in gerrit which are unused by acls, and we don't (currently) have any self-service automation for that either19:54
*** panda|ruck|off has quit IRC19:55
SotKmaybe we need to revisit the "unique nicknames" thing we've talked about in the past19:55
*** gibi_bus is now known as gibi19:55
fungiright, or make it possible to look up openids in sb19:55
fungifor the structured data file in git approach anyway19:55
fungialternatively, we can do the same thing gerrit does and assume e-mail addresses are unique to a single user19:56
fungiand then work out a way to add users to a group via e-mail address lookup19:56
SotKyou mean make it possible for PTLs to find the openids of their team members' storyboard accounts?19:57
fungieven just exposing a unique account id number somewhwere could do the trick though, as long as we added api support to convert that to an account or to be able to use it directly in group member addition calls19:57
*** panda has joined #openstack-meeting19:57
SotKI think that's already possible with the API, we just need to add some sensible UI for viewing information about users19:58
fungibut yeah, whatever unique identifier we settle on, we need some means for a non-admin sb user to figure out another sb user's unique id19:58
SotKpeople have requested a "user profile" type page in the past, probably we should bump that idea up the priority list since it also implies a way to find users19:59
fungiif we had that, i think i have enough to put together some simple automation driven from structured data in git and a workflow around it19:59
fungianyway, i mainly wanted to explain the current challenges, and get folks thinking if there are any elegant solutions19:59
* SotK will apply some thought to it20:00
fungior at least to help identify which solution would be most preferable20:00
fungithanks!20:00
fungiand looks like we're out of time20:00
SotKyep20:00
SotKthanks for coming folks!20:00
SotK#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
openstackMeeting ended Wed Sep 11 20:00:28 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-09-11-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-09-11-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-09-11-19.02.log.html20:00
fungithanks for chairing, SotK!20:00
diablo_rojothanks SotK!20:04
*** jamesmcarthur has joined #openstack-meeting20:06
*** e0ne has quit IRC20:06
*** rosmaita has left #openstack-meeting20:14
*** e0ne has joined #openstack-meeting20:15
*** e0ne has quit IRC20:16
*** e0ne has joined #openstack-meeting20:16
*** ayoung has quit IRC20:24
*** ayoung has joined #openstack-meeting20:24
*** markvoelker has quit IRC20:27
*** e0ne has quit IRC20:29
*** e0ne_ has joined #openstack-meeting20:29
*** ayoung has quit IRC20:35
*** markvoelker has joined #openstack-meeting20:36
*** ayoung has joined #openstack-meeting20:38
*** markvoelker has quit IRC20:41
*** ociuhandu has joined #openstack-meeting20:50
*** enriquetaso has quit IRC20:54
*** ociuhandu has quit IRC20:57
*** alecuyer has joined #openstack-meeting20:59
timburke#startmeeting swift21:00
openstackMeeting started Wed Sep 11 21:00:04 2019 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
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
alecuyero/21:00
mattoliverauo/21:01
tdasilvao/21:01
timburkeagenda's at https://wiki.openstack.org/wiki/Meetings/Swift21:02
timburke#topic Shanghai21:02
*** openstack changes topic to "Shanghai (Meeting topic: swift)"21:02
timburkejust a quick reminder that we ought to put things we want to talk about on the etherpad so we won't forget21:03
timburke#link https://etherpad.openstack.org/p/swift-ptg-shanghai21:03
timburkenot that i'm concerned about us finding something to talk about ;-)21:03
timburkejust want to make sure we remember to cover what we wanted to21:03
timburkeon to updates!21:04
timburke#topic py321:04
*** openstack changes topic to "py3 (Meeting topic: swift)"21:04
timburkei'm inclined to approve the probe tests (https://review.opendev.org/#/c/671333/) based on zaitcev's +2 and mattoliverau's prior generally-approving review, barring objections21:05
timburkeafter that i need to start looking at making a py3 probe tests job21:06
mattoliveraudid you remove the print?21:06
timburkeyup :-)21:06
mattoliverauok, give me a sec ;)21:06
timburkehehe21:06
mattoliveraudone21:07
tdasilvafwiw, I haven't been able to run probetests on my fedora-saio, i still need to find time to debug it21:07
tdasilvai'm assuming zaitcev is able thou, so i'm not super concerned, it's most likely my env.21:08
*** ykatabam has joined #openstack-meeting21:08
timburkethe main other thing i'd like people to think about is which func test jobs we can drop. at the moment we've got 5 in-process func test jobs running for each of py2 and py321:09
timburkei've got this feeling like a lot of that's repeating testing of things where we already have good coverage21:09
*** slaweq has quit IRC21:10
timburkeit gets particularly annoying when we have spurious failures because of a resource-constrained gate21:10
mattoliverauthat is alot. though we do test different configurations which is good.21:10
mattoliverauDropping some from say py2 and py3 might be good. _OR_ do we want to move some as periodic jobs21:10
timburkebut, that situation also seems like it might be improving? idk. i'm not in a *big* hurry... just wanted to put it out there21:11
*** slaweq has joined #openstack-meeting21:11
mattoliverauso they get tested say weekly, to make sure py2 encryption doesn't die, for example21:11
mattoliverauyeah, just brain storming :)21:11
tdasilvaI always forget why we have a separate s3api? why can't that be enabled by default such that tests are run in the regular func tests21:12
alecuyerIs there a way to trigger them all, for example after a patch has been reviewed, updated etc.. before merging ?21:12
timburkemattoliverau, yeah, i was thinking about something like run ec on py3 and encryption on py2 or similar, relying on unit test coverage to catch ec-py2 and encryption-py3 bugs21:12
timburkemaybe move some to experimental?21:12
timburkethat sounds a lot like alecuyer's suggestion :-)21:13
mattoliverauor trigger some func tests based on patch contents. Ie only run py3 encryption if something happens in the encryption middleware21:14
mattoliverauotherwise run py2 encryption each time21:14
mattoliveraua dunno, we may need a matrix :)21:14
timburke^^^ not a bad idea... we tend to compartmentalize functionality pretty well...21:15
*** rcernin has joined #openstack-meeting21:15
timburkeanyway, maybe something to talk about more in the coming weeks (or even shanghai)21:15
timburke#topic versioning21:15
*** openstack changes topic to "versioning (Meeting topic: swift)"21:15
tdasilvabut we also know that swift tests do not put a big load on the gate, so i'm not sure we would see better results, would we?21:16
timburketdasilva, true... mainly i don't want to type "recheck" so much :P21:16
tdasilva+121:17
timburkeassuming a more-or-less constant rate of spurious failures, fewer jobs mean fewer rechecks21:18
timburke(our removing jobs would almost certainly be rounding-error in terms of gate-resource-constraints)21:18
*** slaweq has quit IRC21:18
timburkelooks like clayg's not around ATM; i can give an update on versioning (unless tdasilva would like to)21:19
*** boxiang has joined #openstack-meeting21:19
tdasilvatimburke: go ahead21:20
*** jamesmcarthur has quit IRC21:20
timburkeso clayg, tdasilva, and i have been talking about what design would get us to S3-style versioning a lot lately21:20
*** zhubx has quit IRC21:20
timburkei think what we're landing on is two separate filters so we only have to have a single "mode" loaded in our heads at a time while coding and reviewing21:21
timburkebut with a single entrypoint, similar to what we did with encryption wrapping up encrypter and decrypter21:21
mattoliverau2 filters? for different modes?21:23
mattoliverauDo we have an ethernet page or something where the rough idea/plan lives?21:23
mattoliveraucan we make one, so I can live vicariously though you guys.. or ask silly questions :P21:24
timburkemattoliverau, yep. keep versioned_writes more or less as it is to deal with x-versions/history-location, add another one that wraps it (or is wrapped by it) for the new data layout21:24
timburkeno etherpad yet -- can try to get that going21:25
mattoliveraucool, I know clayg asked if I was free to talk about some of this. Which is cool, but we should try and keep the discussion open. Having said that, thanks guys for all the hard work :)21:26
timburkethis still gives us something of an opportunity for a clean break, which means we can have the new mode only use symlinks when writing new versions or restoring versions, rather than having this extra bifurcation21:27
mattoliverauI like that21:27
*** slaweq has joined #openstack-meeting21:27
tdasilvamattoliverau: it's definitely not set in stone, it's just the latest idea we had and liked it, but please do share your ideas too21:27
mattoliverauif we can get symlinks + new layout + backwards compat. That'll be amazing21:27
timburketdasilva or i will work on getting https://review.opendev.org/#/c/678962/ and https://review.opendev.org/#/c/681054/ consolidated21:28
timburkemattoliverau, it's that last one that's always tricky ;-)21:28
tdasilvamattoliverau: what do you mean by backwards compat?21:28
mattoliverauyeah, I was OK with loosing the last, so long as we're careful21:28
timburkeso... what's your opinion on what "backwards compat" means? yeah, tdasilva get's it ;-)21:28
timburkedoes it mean "this old mode continues working, but you can do this new thing for new stuff", or do we need a migration path to get people from the old to the new?21:29
mattoliverausorry, I mean that we can use the same API and things auto migrate over. Not introducing a new versioning API, or middleware what makes old versions incompatable21:30
mattoliverauby auto migrate, I mean from when you start adding new items21:30
mattoliveraunot something in the back ground21:30
mattoliverauso old continues working, but new stuff uses the new thing.. but it is all accessible via the same API21:31
mattoliverauwith some enhancements to the API if we want to add some s3api-isms21:31
*** slaweq has quit IRC21:32
mattoliverauThe biggest thing I want to see is that any awesome new feature is accessible via the swift API not just s3api. I just want our swift api to always be a first class citizen in swift (obviously).  even if we have to talk about a new seperate versioning API. But if you can make them work together.. I'm all for that.21:33
timburkeso, if i had a container using x-history-location (since that was the best we had available) and it's accumulated some versions of objects... what are your expectations if/when you try to switch it to the new mode?21:33
timburkeyes, definitely want this to be a swift api first, with s3api shimming into it. the smaller we can make that shim, the better21:34
*** zaitcev has joined #openstack-meeting21:34
mattoliverauI dunno, either there is a new API, so you have to keep the old versioned writes middleware if you still want to access them. And start using the new API for 2.0.. or ideally, any new versioning uses symlinks. but if you delete it'll reach back into the old naming and bring them back21:35
*** rbudden has quit IRC21:35
*** rbudden has joined #openstack-meeting21:36
mattoliverauthough, I obviously haven't really thought it through too deeply21:36
timburkeyeah, and that last part is where it gets messy fast :-(21:36
*** rbudden has quit IRC21:36
*** rbudden has joined #openstack-meeting21:37
*** rbudden has quit IRC21:37
mattoliverauI bet. Which is why I was thinking it might be out of scope.. but if we can.. sweet :)21:37
*** rbudden has joined #openstack-meeting21:37
timburkei'll make sure we get an etherpad up so we can continue to think & talk this through. maybe we could even find a time to get a video chat going ahead of shanghai ;-)21:38
*** rbudden has quit IRC21:38
*** rbudden has joined #openstack-meeting21:38
mattoliverauI'll try and look into the patches so I can better grok the probs :)21:38
timburkei'd appreciate it 👍21:39
*** rbudden has quit IRC21:39
*** rbudden has joined #openstack-meeting21:39
timburkekeeping moving...21:39
timburke#topic lots of small files21:39
*** openstack changes topic to "lots of small files (Meeting topic: swift)"21:39
*** rbudden has quit IRC21:39
timburkeso we haven't had review bandwidth to spare for poor alecuyer :-(21:39
*** rbudden has joined #openstack-meeting21:40
alecuyerno worries I know everyone is busy :)21:40
timburkebut meanwhile he's looking to push to prod -- i kinda feel like that's sufficiently good for merging to a feature branch ;-)21:40
*** rbudden has quit IRC21:40
timburkeanyone have objections there?21:40
*** e0ne_ has quit IRC21:41
timburkeit seems like this represents the current state-of-the-art, and i definitely don't want to slow down alecuyer on any of this, or otherwise make life more difficult21:41
mattoliverausorry, I'm slow, you mean patches are sitting open and we should get them landed to the feature branch?21:42
mattoliverauquicker.21:42
mattoliverauif so, feature branches should be quick to merge.21:43
timburkehttps://review.opendev.org/#/c/679022/ is the patch on feature/losf to drop grpc for http21:43
alecuyerOne thing I can say about it is that it only changes the way the index-server communicates with the python. But nothing on disk changes. So if changes are required it shouldn't be a problem (no backward compatibility issue)21:43
mattoliveraupush a patch. leave it open for x time and land it even if people haven't reviewed it too hard.. the idea of a feature branch is to move fast.. leave it open long enough to give people a chance to know its there and see it.21:44
mattoliveraubut don't feel bad about landing code. It will have to be reviewed again anyway.21:44
mattoliverauWell that's how Al and I worked on the sharding stuff.21:44
timburkemattoliverau, that's basically the conclusion i reached this morning when i saw kota_ apologizing for not reviewing it ;-)21:45
timburkemerging. just wanted to confirm that we're on the same page about it21:45
mattoliverauif the patch breaks something we can fix it. or revert it, so no stress :)21:45
mattoliverauthat's why feature branches are awesome. So if it's holding you up, merge it ;)21:46
timburkealecuyer, what are the next steps we need for losf?21:47
alecuyerfirst thing after that patch, I think, would be to rebase https://review.opendev.org/#/c/666378/21:47
alecuyer(and adress your latest comments!)21:47
alecuyerthen I need to push a few patches for issues we found (sorry I haven't pushed these earlier)21:48
*** ykatabam is now known as yuko21:48
*** yuko is now known as ykatabam21:48
alecuyerand one last thing to mention, wrt to the CPU usage (that I think you also noticed at swiftstack while testing),21:49
timburkesounds great! i'll try harder to make time to review them, and get them merged even if i can't spare time for a thorough review ;-)21:49
mattoliveraualecuyer: how dare you find issues and fix them.. and then want to share them.. shame on you :P21:49
alecuyermattoliverau: yeah I know ;) still I should share them quicker :)21:50
alecuyerforgot half of my last sentence, sorry - CPU usage : we are considering using the hashes.pkl21:50
alecuyerJust discussing this, happy to discuss it here or later (i think we're short on time, leave time for other topics)21:51
timburkeoh... does it skip that entirely at the moment, and recompute every time? interesting...21:51
alecuyerit does21:51
timburkei think we also tend to tune our replicators/reconstructors aggressively, which would compound the issue21:52
timburkeer, maybe "to be aggressive" would be more clear21:53
alecuyeryes, so that was probably a bad call. the good news is is should be easy to reuse (just change the path so we don't have to create on dir per hashes.pkl file, prefix the filename with the partition, for example)21:53
*** mriedem is now known as mriedem_afk21:53
alecuyer(the bad call -> doing away the hashes.pkl I mean - not being aggressive while reconstrucing)21:53
timburkelove it21:53
timburkethanks for keeping us updated21:53
mattoliverau+121:53
timburke#topic sharding21:53
*** openstack changes topic to "sharding (Meeting topic: swift)"21:53
timburkesorry mattoliverau -- still haven't gotten to reviewing :-(21:54
mattoliveraunps21:54
mattoliverauAs I mentioned last week21:54
mattoliverauI've reworked the empty broker patch21:55
timburkealso, we got a new bug! and mattoliverau already has the beginnings of a patch :-)21:55
mattoliverauyeah21:55
mattoliverauwas about to mention that. I went and worked on a patch to clean up cleave contexts21:55
mattoliverauit's currently attached to the bug. But will add some tests and push it up as an actual patch21:56
mattoliverauI'll try and get that done in the next few days21:56
timburkehttps://bugs.launchpad.net/swift/+bug/184331321:56
openstackLaunchpad bug 1843313 in OpenStack Object Storage (swift) "Sharding handoffs creates a *ton* of container-server headers" [Undecided,New]21:56
mattoliverauthanks timburke I was looking for that :)21:56
mattoliverauand thanks timburkefor the bug report with a good solution idea. Makes life easier.21:57
timburkethanks mattoliverau!21:57
mattoliverauthat's all I've got21:58
timburke#topic open discussion21:58
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:58
*** hemna has joined #openstack-meeting21:58
timburkeanything else to bring up real quick?21:58
mattoliverauI've been looking into the PDF train goal21:58
timburkeoh, right!21:58
timburkethanks for that21:58
mattoliveraumaking progress, I've pulled Nick, a suse guy who did the designate PDF stuff21:59
mattoliverauto help point me in the right direction re latex and sphinx debugging21:59
*** markvoelker has joined #openstack-meeting21:59
timburkeanything you need the rest of us to help with? proofreading, i suppose21:59
mattoliverauI think tables get messed up when we use ``tag`` s in the columns22:00
mattoliverauSo I might need to remove them to get it to build properly22:00
mattoliverauor hard code table column lengths.. which I'd rather not do.22:00
mattoliverauanyway. I'll kjeep playing :)22:00
timburke...probably fine to give them normal formatting. *shrug*22:00
*** panda has quit IRC22:00
timburkeall right, time to wrap up22:01
mattoliverauyeah, especailly if it means they'll work and in a table I assume they'll still stand out.22:01
mattoliveraukk22:01
timburkethank you all for coming, and thank you for working on swift!22:01
timburke#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"22:01
openstackMeeting ended Wed Sep 11 22:01:30 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
zaitcevyay22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-09-11-21.00.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-09-11-21.00.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-09-11-21.00.log.html22:01
timburkelol sorry zaitcev22:01
zaitcevtoo slow22:01
*** zaitcev has left #openstack-meeting22:02
*** panda has joined #openstack-meeting22:03
*** slaweq has joined #openstack-meeting22:11
*** whoami-rajat has quit IRC22:11
*** slaweq has quit IRC22:16
*** ykatabam has quit IRC22:19
*** ykatabam has joined #openstack-meeting22:28
*** raildo has quit IRC22:49
*** mtreinish has quit IRC22:54
*** mtreinish has joined #openstack-meeting22:55
*** macz has quit IRC23:01
*** hemna has quit IRC23:04
*** slaweq has joined #openstack-meeting23:10
*** slaweq has quit IRC23:15
*** igordc has quit IRC23:18
*** jamesmcarthur has joined #openstack-meeting23:32
*** igordc has joined #openstack-meeting23:33
*** igordc has quit IRC23:40
*** igordc has joined #openstack-meeting23:42
*** hemna has joined #openstack-meeting23:42
*** jamesmcarthur has quit IRC23:46
*** jamesmcarthur has joined #openstack-meeting23:46
*** mriedem_afk has quit IRC23:49
*** jamesmcarthur has quit IRC23:51
*** carloss has quit IRC23:55

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!