Wednesday, 2019-06-19

*** mattw4 has joined #openstack-meeting00:02
*** bdx has quit IRC00:02
*** bdx has joined #openstack-meeting00:03
*** slaweq has joined #openstack-meeting00:11
*** slaweq has quit IRC00:16
*** diablo_rojo has joined #openstack-meeting00:21
*** dviroel has quit IRC00:25
*** mattw4 has quit IRC00:32
*** gyee has quit IRC00:32
*** yamahata has quit IRC00:37
*** iyamahat has quit IRC00:37
*** diablo_rojo has quit IRC00:51
*** mriedem_away has quit IRC01:01
*** zhangchi has joined #openstack-meeting01:02
zhangchi#startmeeting tricircle01:03
openstackMeeting started Wed Jun 19 01:03:46 2019 UTC and is due to finish in 60 minutes.  The chair is zhangchi. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:03
*** openstack changes topic to " (Meeting topic: tricircle)"01:03
openstackThe meeting name has been set to 'tricircle'01:03
zhangchiMorning welcome back to tricircle meeting01:05
*** diablo_rojo has joined #openstack-meeting01:06
*** lbragstad has quit IRC01:08
*** tetsuro has joined #openstack-meeting01:10
*** cyg has joined #openstack-meeting01:13
zhangchiNeutron master updated and some unit test can not pass. I am trying to resolve securitygrouprule db can not load problem01:14
*** igordc has quit IRC01:16
*** XSM_HUST has joined #openstack-meeting01:19
zhangchihi XSM_HUST, I saw your suggestion add region_name by Zuul have been accepted by community01:21
zhangchiThis may take some time for community zuul team to fix the problem01:23
zhangchiGood. How things else going on01:25
XSM_HUSThow about the spec of container I have submitted last time?01:25
zhangchiOh I have a read it and I think this is a good spec01:26
zhangchiI will finished review it today01:27
XSM_HUSTif zun team fix that bug, I will write a installation doc about zun management.01:28
zhangchigood and may be some more detail user guide can be added01:33
*** baojg has joined #openstack-meeting01:35
zhangchiNeutron master recently have been reconstructed a lot from db api interface. This may result tricirlce ci not passed frequently. We will try to keep up with it01:38
*** ykatabam has quit IRC01:47
*** tetsuro has quit IRC01:48
zhangchiHi cyg , so have you found somethings more can be updated  to adjust to zuul v301:51
*** tetsuro has joined #openstack-meeting01:52
zhangchiCi system names Job names and ansible playbooks  definition may be changed01:53
cygI have nothing to update01:54
zhangchiok if all is updated to zuul v3 and have been checked we will colse the agenda01:57
*** apetrich has quit IRC01:57
*** hongbin has joined #openstack-meeting01:58
zhangchiwelcome hongbin02:00
zhangchiwe have meet some more tempest problems from neutron db api.02:03
zhangchiMaybe we can exchange next time02:05
zhangchiAny more topics and problems?02:05
zhangchiok. If not will end meeting right now02:06
zhangchiThanks for all your attending02:07
zhangchibye XSM_HUST Thank your time02:07
*** XSM_HUST has quit IRC02:08
*** whoami-rajat has joined #openstack-meeting02:08
*** tinwood has quit IRC02:08
zhangchiNext meeting is July 3th Welcome all to join :)02:08
*** openstack changes topic to "OpenStack Meetings ||"02:09
openstackMeeting ended Wed Jun 19 02:09:14 2019 UTC.  Information about MeetBot at . (v 0.1.4)02:09
openstackMinutes (text):
*** tinwood has joined #openstack-meeting02:10
*** cyg has quit IRC02:11
*** slaweq has joined #openstack-meeting02:11
*** slaweq has quit IRC02:16
*** ykatabam has joined #openstack-meeting02:45
*** tetsuro has quit IRC02:47
*** diablo_rojo has quit IRC02:49
*** _alastor_ has quit IRC02:50
*** ricolin has joined #openstack-meeting02:55
*** markvoelker has joined #openstack-meeting03:00
*** mattw4 has joined #openstack-meeting03:00
*** markvoelker has quit IRC03:06
*** slaweq has joined #openstack-meeting03:11
*** slaweq has quit IRC03:15
*** tetsuro has joined #openstack-meeting03:29
*** psachin has joined #openstack-meeting03:32
*** tetsuro has quit IRC03:34
*** zhangchi has quit IRC03:41
*** _alastor_ has joined #openstack-meeting03:50
*** _alastor_ has quit IRC03:54
*** psachin has quit IRC04:01
*** markvoelker has joined #openstack-meeting04:01
*** psachin has joined #openstack-meeting04:03
*** markvoelker has quit IRC04:06
*** imsurit has joined #openstack-meeting04:23
*** hongbin has quit IRC04:25
*** ykatabam has quit IRC04:44
*** ykatabam has joined #openstack-meeting04:51
*** vishalmanchanda has joined #openstack-meeting04:55
*** tetsuro has joined #openstack-meeting05:07
*** slaweq has joined #openstack-meeting05:11
*** e0ne has joined #openstack-meeting05:15
*** slaweq has quit IRC05:16
*** e0ne has quit IRC05:20
*** dmacpher_ has joined #openstack-meeting05:24
*** dklyle_ has joined #openstack-meeting05:24
*** yamamoto_ has joined #openstack-meeting05:24
*** david-lyle has quit IRC05:27
*** yamamoto has quit IRC05:27
*** freerunner has quit IRC05:27
*** dmacpher has quit IRC05:27
*** freerunner has joined #openstack-meeting05:28
*** irclogbot_3 has quit IRC05:30
*** sridharg has joined #openstack-meeting05:31
*** irclogbot_1 has joined #openstack-meeting05:31
*** Luzi has joined #openstack-meeting05:50
*** iyamahat has joined #openstack-meeting05:59
*** ykatabam has quit IRC06:04
*** ykatabam has joined #openstack-meeting06:06
*** tetsuro has quit IRC06:10
*** slaweq has joined #openstack-meeting06:11
*** ricolin has quit IRC06:18
*** ricolin has joined #openstack-meeting06:19
*** rajinir has quit IRC06:22
*** apetrich has joined #openstack-meeting06:30
*** kopecmartin|off is now known as kopecmartin06:32
*** belmoreira has joined #openstack-meeting06:40
*** rubasov has joined #openstack-meeting06:43
*** ykatabam has quit IRC06:51
*** rcernin has quit IRC06:51
*** cheng1 has quit IRC06:53
*** cheng1 has joined #openstack-meeting06:55
*** igordc has joined #openstack-meeting07:05
*** igordc has quit IRC07:10
*** ralonsoh has joined #openstack-meeting07:16
*** tesseract has joined #openstack-meeting07:20
*** yamahata has joined #openstack-meeting07:23
*** tetsuro has joined #openstack-meeting07:33
*** tssurya has joined #openstack-meeting07:38
*** belmoreira has quit IRC07:38
*** tetsuro has quit IRC07:38
*** ttsiouts has joined #openstack-meeting07:42
*** belmoreira has joined #openstack-meeting07:44
*** yamamoto_ has quit IRC07:54
*** trident has quit IRC07:57
*** trident has joined #openstack-meeting08:01
*** Adri2000 has quit IRC08:01
*** Adri2000 has joined #openstack-meeting08:03
*** ttsiouts has quit IRC08:06
*** ttsiouts has joined #openstack-meeting08:07
*** joxyuki has quit IRC08:08
*** ttsiouts has quit IRC08:11
*** ociuhandu has joined #openstack-meeting08:15
*** ttsiouts has joined #openstack-meeting08:16
*** yamamoto has joined #openstack-meeting08:18
*** pcaruana has quit IRC08:27
*** yamamoto has quit IRC08:29
*** yamamoto has joined #openstack-meeting08:32
*** yamamoto has quit IRC08:32
*** e0ne has joined #openstack-meeting08:34
*** _alastor_ has joined #openstack-meeting08:35
*** _alastor_ has quit IRC08:39
*** pcaruana has joined #openstack-meeting08:45
*** markvoelker has joined #openstack-meeting08:53
*** tetsuro has joined #openstack-meeting08:55
*** markvoelker has quit IRC08:58
*** mattw4 has quit IRC08:59
*** imsurit has quit IRC09:05
*** tetsuro has quit IRC09:11
*** kaisers1 has quit IRC09:13
*** kaisers has joined #openstack-meeting09:16
*** brinzh has joined #openstack-meeting09:17
*** brinzh has quit IRC09:18
*** brinzhang has joined #openstack-meeting09:20
*** belmoreira has quit IRC09:25
*** Lucas_Gray has joined #openstack-meeting09:26
*** ykatabam has joined #openstack-meeting09:32
*** igordc has joined #openstack-meeting09:37
*** janki has joined #openstack-meeting09:43
*** yamamoto has joined #openstack-meeting09:48
*** lpetrut has joined #openstack-meeting09:49
*** markvoelker has joined #openstack-meeting09:53
*** brinzhang has quit IRC09:55
*** yamamoto has quit IRC09:57
*** markvoelker has quit IRC09:58
*** electrofelix has joined #openstack-meeting10:03
*** electrofelix has quit IRC10:03
*** electrofelix has joined #openstack-meeting10:09
*** lpetrut has quit IRC10:13
*** rcernin has joined #openstack-meeting10:19
*** yamamoto has joined #openstack-meeting10:29
*** dviroel has joined #openstack-meeting10:29
*** _alastor_ has joined #openstack-meeting10:35
*** HPCJohn has joined #openstack-meeting10:37
*** _alastor_ has quit IRC10:40
*** Lucas_Gray has quit IRC10:45
*** priteau has joined #openstack-meeting10:46
*** ttsiouts has quit IRC10:47
*** ttsiouts has joined #openstack-meeting10:48
*** lpetrut has joined #openstack-meeting10:51
*** ttsiouts has quit IRC10:52
*** markvoelker has joined #openstack-meeting10:54
*** oneswig has joined #openstack-meeting10:57
*** janders has joined #openstack-meeting10:59
*** markvoelker has quit IRC10:59
oneswig#startmeeting scientific-sig11:00
openstackMeeting started Wed Jun 19 11:00:47 2019 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:00
*** openstack changes topic to " (Meeting topic: scientific-sig)"11:00
openstackThe meeting name has been set to 'scientific_sig'11:00
oneswig#link Agenda for today
jandersg'day all!11:01
*** ykatabam has quit IRC11:01
oneswighi verdurin janders, glad you could make it11:01
oneswigjanders: have you seen martial at ISC?11:02
oneswig#topic ISC roundup11:02
*** openstack changes topic to "ISC roundup (Meeting topic: scientific-sig)"11:02
*** martial has joined #openstack-meeting11:02
jandersoneswig: I haven't attended this year unfortunately11:02
oneswigmartial: guten tag :-)11:02
oneswig#chair martial11:02
openstackCurrent chairs: martial oneswig11:02
oneswigjanders: ah, for some reason I thought you were going11:02
oneswigmy mistake11:02
jandersfew of my colleagues were there though11:03
janderswe scored a decent IO500 score :)11:03
oneswigas did we :-)11:03
*** Shrews has left #openstack-meeting11:03
martialjanders: coming to Shanghai btw?11:03
oneswigjanders: bracewell?11:04
martialActually talked to the organizers by chance last night11:04
martialMentioned the BoF11:04
martialWas told it is comitee driven11:04
jandersthat's right! :)11:04
oneswigThe Bof from ISC?11:04
jandersstill thinking whether I should aim for Shanghai or not. The political climate right now is so so. Good destination though!11:05
martialThe Chinese teams here are interesting, they have a demo of sugon too11:06
martialReally nice11:06
oneswigmartial: what are they demonstrating?11:07
martialMostly their different data centers11:07
martialAnd a sale team explain how you can use it in your setup11:07
janderslooking at IO500 - you have the fastest Lustre, while we have the fastest BeeGFS :)11:08
oneswigCalling that evens janders?11:08
martialVery interesting hardware11:08
martialVery popular beegfs here11:08
jandersthe 10 node challenge was close to even :)11:09
janderson the main list, a different story though. Very well done!11:09
oneswigI think a lot of the tuning at Cambridge was done on striping for large server configurations.11:09
oneswigThanks janders, although I don't think we were involved in the performance tuning at all, just the dynamic orchestration11:10
jandersNearly double the score of the second place. That's something! :)11:10
oneswigIt was about half the score of the (then) top place in the last list, which goes to show what tuning can do for Lustre!11:11
jandersyour good advice helped us out with making some early architectural decisions - so thank you! :)11:11
janderspretty amazing IOPS numbers too - I didn't know Lustre can do that11:11
*** njohnston has left #openstack-meeting11:12
jandersaggregate bandwidth - hell yeah but IOPS? That's something quite new.11:12
martialAm going to walk around and read ;)11:12
oneswigmartial: what's the news on hpc cloud at ISC?11:13
jandersstorage aside, what were the ISC highlights?11:13
jandersexactly :)11:13
martialTrend is toward arm (very present), AMD new processors and beegfs11:14
martialNvidia is not present which is surprising11:14
oneswignot at all?11:15
martialCouple nvidia people for talks but that is it11:16
oneswigThat's surprising to me11:16
martialSame here11:16
jandersesp given the mlnx acquisition..11:16
martialMellanox is here11:17
martialBut no Nvidia "themselves"11:17
martialOracle, IBM, hp, Microsoft,...11:19
oneswigHow much public cloud presence is there?11:20
martialGoogle cloud11:20
oneswighave Google come up with an HPC offering yet?  Its well overdue11:20
martialActually they had a booth talk about this yesterday11:21
martialAm looking for the name11:22
HPCJohnJohnH here. Interested in what Google are doing11:22
oneswigWhile you're digging that up, let's shift over to HPCW11:22
martialIt provision hpc workloads11:22
oneswigHi HPCJohn :-)11:22
oneswigmartial: was there anything like the Bof we proposed?11:23
martialNothing comparable11:23
jandersgoogle HPC offering = k8s DCaaS? :)11:24
martialIn the videos11:25
oneswigjanders: would love to see your BeeGFS tuning make its way into
martialBasically deploys slurm and other tools and you can use it11:26
oneswigmartial: it's bobbins unless they've done something to improve the networking11:26
martialAs a regular cloud with hpc tools pre installed11:26
jandersoneswig: nice! :) we're far behind with ansible-isation of BeeGFS but hoping to catch up :)11:27
martialSeems more of a use case at the demo I saw but seems interesting11:28
martialAs for hpcw it is happening tomorrow11:28
martialQuite an interesting program11:28
oneswigmartial: ah, so my round-up agenda item was premature!11:28
martialWith 5 minutes slot for most presenters11:28
jandersyeah Thursdays at ISC can be quite interesting :)11:29
martialIt's okay, I should have access to all the slide decks11:29
martialAnd should be able to share11:29
oneswigmartial: how many 5-minute presentations?11:29
martialThat's the program so far11:30
janderssounds like a lightning-talk-storm over Frankfurt.. :)11:30
martialMaybe I could had a slide on Kayobe11:30
oneswigThat would be cool martial, let me know if you need resources for that11:31
oneswigSo what's Christian up to - apart from hosting HPCW?11:31
HPCJohnI know Christian. Good guy11:31
*** ttsiouts has joined #openstack-meeting11:32
HPCJohnIf it is relevant, the latest version of Singularity is out yesterday. Lots of OCI features.11:32
HPCJohnAlso you can check a Singularity container directly out of a Docker harbour, as I understand11:32
HPCJohnThe direct quoto so I get ti right    an oras:// URI allowing you to push and pull SIF files to supported OCI registries!11:33
oneswigI was talking to someone about the latest on containers, MPI, kubernetes, etc.11:33
martialChristian is starting at Amazon in July I think11:34
oneswig#link Latest on MPI configuration with Singularity and K8S
martialStig I will follow up on slack11:35
martialA one page for Kayobe would be cool indeed11:35
oneswigmartial: I'll see what I can find for you11:35
oneswigOK, so we can't cover HPCW just yet but I was definitely at the Sanger Centre OpenStack day yesterday...11:36
oneswig#topic Sanger OpenStack day round-up11:36
*** openstack changes topic to "Sanger OpenStack day round-up (Meeting topic: scientific-sig)"11:36
oneswigHad a good session there, some interesting talks11:36
verdurinMissed it again... Eheu.11:36
oneswigGerry Reilly from Health Data Research UK gave a good high-level presentation on secure computing environments11:37
oneswigHad very similar thoughts in the abstract to the kind of projects going on across the research computing / Openstack space11:37
oneswigThere was some interesting update from the Sanger team themselves on their giant Ceph deployment, and plans for more science and more data on OpenStack11:38
oneswigI mentioned you verdurin - in reference to your description of "sidegrades" a couple of years ago when you had your Crick hat on11:38
verdurinWas at the HDRUK meeting last week when those environments were being discussed.11:39
oneswigverdurin: interesting.  Is there any scope for alignment on these matters?11:39
martialStig sent you a pm on slack11:39
oneswigJani from Basel presented on something similar in Switzerland - SPHN - but with federation involved11:40
verdurinThere is, my impression is that there's still a diversity of viewpoints.11:41
oneswigBruno from the Crick presented on eMedlab - as an early pioneer it has plenty of hindsight to offer11:42
oneswigverdurin: it would be interesting to hear how those discussions develop.11:43
HPCJohnMe too please - hindsight is a wonderful thing.11:43
HPCJohnI have followed eMEdlab from early days11:43
oneswigI hadn't realised there was 512G RAM in each hypervisor - that's quite something, particularly in a machine that's >3 years old11:45
oneswigjohnthetubaguy presented on upstream developments for research computing use cases and I presented on some recent Rocky upgrade experiences11:46
oneswigIt was good to hear an update on the scale of the JASMIN system and their new Mirantis OpenStack deployment too.11:47
oneswig#topic AOB11:49
*** openstack changes topic to "AOB (Meeting topic: scientific-sig)"11:49
oneswigSo what else is new?11:49
HPCJohnJASMIN interesting. Scientists not using public cloud.   But gathering research grants into a central facility11:49
oneswigHPCJohn: It does appear to be a success story.11:50
HPCJohnI can see that model being applied more widely - I guess in climate research there is no patient ideitifiable data!11:50
oneswigThat niche field intersecting climate science and genomics - seasonally-affected disorder perhaps?11:51
jandersfrom my side - a little follow up from Denver11:52
openstackLaunchpad bug 1829449 in neutron "Implement consistency check and self-healing for SDN-managed fabrics" [Wishlist,New]11:52
janderssome progress on the SDN front11:52
janders tags:added: rfe-approved11:52
jandersthanks to those involved! :)11:53
oneswigThe glacier of development grinds ever onwards11:53
oneswigGood work janders, keep it up!11:54
oneswigWe had an interesting problem using Docker and the overlay storage driver11:54
*** raildo has joined #openstack-meeting11:54
*** rfolco has joined #openstack-meeting11:54
oneswigIt turns out that you can exceed 64K hard links to a single inode!11:54
*** markvoelker has joined #openstack-meeting11:55
HPCJohnSome filsystems hide small files inside the inode11:55
HPCJohnYou are turning this on its head - hiding a filesystem in the inode11:55
oneswigIn yum, there is a file called checksum_type in the metadata of each package which is hard-linked to one source.  ie,the hard link count is a function of the number of packages installed11:55
oneswigThe layers of Docker overlays, and multiple containers using the same base layers will compound this.11:56
oneswigHence we hit 65536 links - the limit for ext411:56
oneswigSolution: XFS allows more links :-)11:56
jandersI will have that with triple-nested VMs, thanks :)11:57
oneswigThe unexpected consequences of creating many virtual systems from one physical one.11:57
*** yamamoto has quit IRC11:57
oneswigWe are nearly at the hour, any more to add?11:58
janderssome time back I was trying to convince mlnx to implemented SRIOV in nested-virt, but they didn't share my enthusiasm :)11:58
oneswigjanders: we may start work soon on HA support for Mellanox-NEO-UFM SDN11:58
janderscool! I'm heading in that direction, too11:58
oneswigsee you at the first hurdle then :-)11:59
jandersjust hitting some roadblocks lower down the stack with new hardware11:59
jandersthat's right! :)11:59
jandersno rest for the wicked11:59
martialCool talk soon team11:59
oneswigAnd on that note, back to it.11:59
jandersthank you all11:59
oneswigThanks all11:59
*** openstack changes topic to "OpenStack Meetings ||"11:59
openstackMeeting ended Wed Jun 19 11:59:48 2019 UTC.  Information about MeetBot at . (v 0.1.4)11:59
openstackMinutes (text):
*** markvoelker has quit IRC12:00
*** HPCJohn has quit IRC12:00
*** oneswig has quit IRC12:00
*** janders has quit IRC12:01
*** rcernin has quit IRC12:15
*** carloss has joined #openstack-meeting12:17
*** Lucas_Gray has joined #openstack-meeting12:17
*** priteau has quit IRC12:27
*** liuyulong has joined #openstack-meeting12:28
*** _alastor_ has joined #openstack-meeting12:30
*** eharney has quit IRC12:40
*** yamamoto has joined #openstack-meeting12:41
*** markvoelker has joined #openstack-meeting12:56
*** ttsiouts has quit IRC13:00
*** markvoelker has quit IRC13:00
*** ttsiouts has joined #openstack-meeting13:01
*** ttsiouts has quit IRC13:05
*** baojg has quit IRC13:07
*** mriedem has joined #openstack-meeting13:11
*** ttsiouts has joined #openstack-meeting13:18
*** lbragstad has joined #openstack-meeting13:20
*** bbowen has joined #openstack-meeting13:24
*** bbowen_ has quit IRC13:24
*** _alastor_ has quit IRC13:33
*** rajinir has joined #openstack-meeting13:40
*** lseki has joined #openstack-meeting13:40
*** eharney has joined #openstack-meeting13:50
*** mlavalle has joined #openstack-meeting13:53
*** janki has quit IRC13:57
*** markvoelker has joined #openstack-meeting13:57
liuyulong#startmeeting neutron_l314:00
openstackMeeting started Wed Jun 19 14:00:07 2019 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:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:00
openstackThe meeting name has been set to 'neutron_l3'14:00
*** liuyulong has quit IRC14:01
*** markvoelker has quit IRC14:01
mlavalledang our chair person you fell off14:02
*** liuyulong has joined #openstack-meeting14:02
mlavallehe came back14:02
liuyulongI lost the connection14:02
liuyulongThe meeting is started or not?14:02
liuyulong#chair mlavalle14:02
openstackCurrent chairs: liuyulong mlavalle14:02
liuyulong#chair haleyb14:02
openstackCurrent chairs: haleyb liuyulong mlavalle14:02
liuyulongHello everyone, it is my first time to host L3 meeting. : )14:03
slaweqliuyulong: good luck :)14:03
liuyulong#action liuyulong lost the connection at the very beginning.14:03
liuyulong#topic Announcements14:04
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:04
*** liuyulong has quit IRC14:05
*** jamesmcarthur has joined #openstack-meeting14:05
*** liuyulong has joined #openstack-meeting14:05
*** tssurya has quit IRC14:06
liuyulongTerribly sorry...14:07
mlavalledon't worry about it14:07
liuyulongWe are in T-2 dev cycle now.14:07
liuyulongNo bugs are targeted to this milestone.14:08
liuyulongOnly 4 BPs14:08
mlavallethere are a few more to come14:08
mlavallethey will be in the dashboard soon14:08
*** brinzhang has joined #openstack-meeting14:09
liuyulongmlavalle, OK14:09
liuyulongWelcome to China and welcome to Shanghai.14:09
liuyulongYes, call for speakers, please submit your presentation for Open Infrastructure Summit Shanghai, and hope to see all you guys there.14:10
mlavallelooking forward to it14:10
mlavalleone thing to mention is that we all need business Chinese visa14:11
liuyulongmlavalle and I will submit a port forwarding topic.14:11
*** martial has quit IRC14:11
mlavalleYou need an invitation letter from the OpenStack Foundation14:12
*** Lucas_Gray has quit IRC14:12
mlavallethe Foundation will make it available over the next 2 or 3 weeks14:12
*** Lucas_Gray has joined #openstack-meeting14:13
liuyulongYes, our community supports us.14:13
mlavalleand with that you have to go to the nearest Chinese consulate14:13
mlavallein the USA, there are companies that help you get the visa. In my case, I used in the past cibt.com14:13
*** lpetrut has quit IRC14:14
* mlavalle will go quiet now14:14
liuyulongI don't need this, haha14:15
liuyulongmlavalle, thanks for the tips14:15
brinzhangThe application for the visa card is very simple. As long as the conditions are met, it is ok to wait for the application to pass.14:15
liuyulongbrinzhang, great news, thanks.14:16
liuyulongany other announcements?14:16
liuyulongOK, let's move on.14:16
liuyulong#topic Bugs14:16
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:16
liuyulongmlavalle is our bug deputy this week14:16
mlavalleno, I was last week14:17
liuyulongs/last week14:17
openstackLaunchpad bug 1832307 in neutron "Functional test neutron.tests.functional.agent.linux.test_ip_lib.IpMonitorTestCase. test_add_remove_ip_address_and_interface is failing" [Critical,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:17
brinzhangliuyulong: this is the Zhao Shang Bank14:17
liuyulongThe fix is here:
liuyulongit is almost done14:17
liuyulongI run the test 100 times locally, all passed.14:18
liuyulongIt's in the gate now (another recheck is needed.)14:19
openstackLaunchpad bug 1821912 in neutron "intermittent ssh failures in various scenario tests" [High,In progress] - Assigned to LIU Yulong (dragon889)14:20
liuyulongI did not make much more progress on this issue recently, but I've noticed that seems we have a smaller chance to encounter it now.14:20
mlavalleI am investigating failures with the connectivity test with 2 routers14:21
mlavalleand some of those ssh failures must come from it14:21
mlavalleso I think we are slowly nibbling at it14:22
mlavalleis there a test case that produces the most failures?14:22
liuyulongThis link is pointing to all the patch sets we have:, most of them do not have much activities.14:22
liuyulongmlavalle, yes, I read the neutron_ci meeting log.14:23
liuyulongmlavalle, no,  I have no data about the most failure case14:24
liuyulongtotally random, IMOP14:24
mlavalleare we still using the kibana search query at the top of the bug?14:24
liuyulongI have a SPEC, the idea is coming out from this bug. Also, no much activities.14:24
mlavalleI see you added a query in note #1614:25
mlavalleI'll give it a try nd see if I can identify a pattern14:25
liuyulong^ this was a newer log query I left before.14:26
mlavalleand I'll go back to the probe RFE14:26
mlavallegood to know it is connected to this bug14:27
liuyulongI will continue pay attention on this bug.14:28
openstackLaunchpad bug 1831534 in neutron "[l3][dvr] with openflow security group east-west traffic between different vlan networks is broken" [High,In progress] - Assigned to yangjianfeng (yangjianfeng)14:28
liuyulongmlavalle, cool14:30
liuyulongThe first version fix is here:, after some tests locally, IMO, the potential impact of this change is too wide. Almost every L3 scenario traffic is affected.14:30
*** zaneb has quit IRC14:30
liuyulongFor instance, dvr router floating IP, dvr_no_external centrilized floating IP, vlan networks east-west traffic, vlan network to tunnel network east-west traffic, L3 dvr east-west traffic between dvr and dvr_no_external, and various combinations based on the state of ovs-agent security group: enable_security_group = False/True.14:30
*** zaneb has joined #openstack-meeting14:30
liuyulongAnd neutron upstream CI does not cover all these cases, IMO, at least vlan networks east-west traffic is not covered. So we may need to test these cases manually. It is not achievable, IMO, people always forget some details.14:30
liuyulongSo, I have an alternative fix for this now: Comparing with Jianfeng's fix, this now has the minimum influence. It only touches one scenario: the VLAN networks with enabled security group.14:31
liuyulongAm I still here?14:32
mlavalleso your point is trying to be the least disruptive, right?14:32
*** liuyulong_ has joined #openstack-meeting14:34
liuyulong_#action I'm the backup.14:35
liuyulongBut I have a question about how the ovs-agent take care of those flows based on the physical VLAN id when update the network segmentation_id.14:35
liuyulongAnd after some test, if restart the ovs-agent, the new vlan id will be used for these related flows.14:36
ralonsohthere is no need to restart the agent14:36
*** Luzi has quit IRC14:36
liuyulongSo it's OK. Still the small fix for this bug.14:36
ralonsohthat's the point of this feature14:36
ralonsohyes, slaweq has two patches upstream to fix it14:36
tidwellrthis issue is a strange one, I'm surprised to see people attempting to use DVR with VLAN networks. I was always under the impression it was known that DVR only works with vxlan networks, but there's no reason we shouldn't make this work14:38
liuyulongLet me quickly go through the bugs.14:38
liuyulongConnection is so unstable...14:38
mlavalletidwellr: +++14:38
liuyulongralonsoh, if ovs-agent restart is not needed, then those flows will not be updated.14:39
slaweqliuyulong: they should be I think14:39
ralonsohliuyulong, which flows? in which bridge?14:39
openstackLaunchpad bug 1831706 in neutron "[DVR] Modify `in_port` field of packets which from remote qr-* port" [Undecided,In progress] - Assigned to yangjianfeng (yangjianfeng)14:39
liuyulongBased on the former bug, Jianfeng wants to start a new approach which is trying to simplify the security group openflow flows.14:40
liuyulongAnd the gerrit link is
liuyulongThis may be significant for large scale deployment with countless user security group rules.14:40
openstackLaunchpad bug 1832745 in neutron "_update_network_segmentation_id KeyError: 'provider:network_type'" [Medium,New]14:40
liuyulongDuring the recent local testing, I noticed everytime I restart the OVS-agent, I will get such KeyError: 'provider:network_type' log. And seems, as haleyb mentioned in LP, in neutron we have many place which is in such style network['provider:network_type']. Each one may need to take care.14:41
liuyulongralonsoh, physical bridges (e.g. br-vlan)14:41
*** dklyle_ has quit IRC14:42
liuyulongThat's all from me.14:42
liuyulongSo, are there any other bugs that need the team to pay attention?14:42
ralonsohliuyulong, please take a look at the function: I change the connection between br-int and br-phys14:42
*** dklyle has joined #openstack-meeting14:42
haleybliuyulong: regarding that bug ^^^, is it only provider networks that are affected?14:43
haleybi.e. others don't have this segment list14:43
liuyulonghaleyb, for my test env, it is router HA networks.14:43
ralonsohliuyulong, I'll take care of this bug14:44
ralonsohthis is the problem of not having a common API (or object) for agents14:44
liuyulongralonsoh, cool, thanks14:44
ralonsoheverything passed from the server is an undefined dict14:45
liuyulongNo? Let's move on.14:45
liuyulong#topic Routed Networks14:45
*** openstack changes topic to "Routed Networks (Meeting topic: neutron_l3)"14:45
liuyulongmlavalle, tidwellr, wwriverrat: if you guys need to continue your discussion, please go ahead.14:45
mlavalleas mentioned yesterday during the neutron meeting14:45
mlavalle1) ralonsoh looking at sriov implications. There doesn't seem to be many14:46
mlavalle2) I'm deploying the patch in my ovs system, to gauge implications.14:46
mlavallewith this^^^ I think we can help wwriverrat to complete the spec14:47
mlavallethe patch is here:
*** brinzhang0 has joined #openstack-meeting14:47
*** brinzhang has quit IRC14:47
mlavalleand that's all I have for today14:48
tidwellron the floating IP's front, I was thinking of pushing a WIP patch illustrating my idea around
mlavallethat woyuld be great14:50
*** liuyulong_ has quit IRC14:51
*** liuyulong has quit IRC14:51
tidwellrI don't this approach is terribly invasive, I think we just need to agree on an approach14:51
*** liuyulong has joined #openstack-meeting14:52
*** liuyulong has quit IRC14:53
*** liuyulong has joined #openstack-meeting14:53
*** belmoreira has joined #openstack-meeting14:53
*** brinzhang0 has quit IRC14:53
liuyulongagain...sorry for that14:53
liuyulong#topic On demand agenda14:54
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"14:54
liuyulongI wasted some time in the re-connection.14:54
liuyulongAnd we are running out of time.14:55
mlavalleno additional topics from me14:55
liuyulongAnything else to discuss here today?14:56
liuyulongOK, a happy ending14:56
*** openstack changes topic to "OpenStack Meetings ||"14:56
openstackMeeting ended Wed Jun 19 14:56:49 2019 UTC.  Information about MeetBot at . (v 0.1.4)14:56
openstackMinutes (text):
*** markvoelker has joined #openstack-meeting14:58
*** lpetrut has joined #openstack-meeting14:58
*** lpetrut has quit IRC14:59
*** lpetrut has joined #openstack-meeting14:59
*** markvoelker has quit IRC15:02
*** sridharg has quit IRC15:06
*** mattw4 has joined #openstack-meeting15:11
*** _alastor_ has joined #openstack-meeting15:13
*** yamamoto has quit IRC15:15
*** enriquetaso has joined #openstack-meeting15:24
*** lpetrut has quit IRC15:30
*** gyee has joined #openstack-meeting15:32
*** enriquetaso has quit IRC15:44
*** enriquetaso has joined #openstack-meeting15:45
*** mattw4 has quit IRC15:47
*** mattw4 has joined #openstack-meeting15:47
*** mattw4 has quit IRC15:55
*** belmoreira has quit IRC15:57
*** markvoelker has joined #openstack-meeting15:58
*** mattw4 has joined #openstack-meeting15:59
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Jun 19 16:00:23 2019 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at
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
jungleboyjcourtesy ping:  jungleboyj whoami-rajat rajinir lseki carloss pots woojay erlon geguileo eharney rosmaita enriquetaso e0ne smcginnis davidsha walshh_ xyang hemna _hemna16:00
*** diablo_rojo has joined #openstack-meeting16:00
_pewp_jungleboyj (◍˃̶ᗜ˂̶◍)ノ”16:00
geguileohi! o/16:00
*** woojay has joined #openstack-meeting16:01
jungleboyjHello everyone.16:01
*** ttsiouts has quit IRC16:02
jungleboyjGive people one more moment to show up.16:02
*** ttsiouts has joined #openstack-meeting16:03
*** markvoelker has quit IRC16:03
jungleboyjOk, now e0ne is here.  We can start.  :-)16:03
* e0ne feels useful today :)16:04
*** davidsha has joined #openstack-meeting16:04
jungleboyj#topic announcements16:04
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:04
jungleboyjAs you can see not a lot today.16:04
jungleboyjJust the reminder that the requirement to have 3rd Party CI running on Py3 is coming up in about a month.16:04
jungleboyjWill start doing an audit of systems soon.16:04
e0nejungleboyj, smcginnis: do you know how many 3rd party CI use python3?16:05
jungleboyje0ne:  I haven't actually looked yet.16:05
smcginnise0ne: I've seen a couple at least, but I've been afraid to really go look at them all.16:05
jungleboyjsmcginnis:  Same here.16:06
smcginnisThere are several driver maintainers here. Anyone have any progress or updates to report on this?16:06
*** ttsiouts has quit IRC16:07
smcginnisPy37 is an officially supported runtime for train, so if driver maintainers don't make sure they work right with it, there could be a lot of pain in a few months when customers want to try out the new release.16:08
walshh_dell_emc have moved from py36 to py3716:08
smcginniswalshh_: Awesome - thanks!16:08
jungleboyjThat is good.16:09
jungleboyjrajinir: Anything from your team?16:09
*** lpetrut has joined #openstack-meeting16:10
jungleboyjAnyone else?16:10
woojayLINSTOR is 3.716:10
jungleboyjwoojay:  Woot woot!16:10
smcginniswoojay: Nice! :)16:11
*** _erlon_ has joined #openstack-meeting16:12
* _erlon_ sneaks ...16:12
dviroele0ne: We (NetApp) are using python3 on our CI.16:12
jungleboyjGood.  So, we aren't asking for something that doesn't work.16:13
jungleboyjSo, hopefully others have it working too and just aren't in the meeting.16:14
_erlon_jungleboyj: no, it works, we just needed to set USE_PYTHON3=True in our jobs16:14
walshh_I believe legacy Dell drivers are in the process of changing to py37 also.  It may even be complete16:14
smcginnisdviroel: 3.7?16:15
_erlon_3.6 or 3.7 not sure16:15
dviroelsmcginnis: need to check that16:16
smcginnisOK, it needs to be 3.7, but if it's already using 3.6 then that shouldn't be as big of a hurdle.16:16
jungleboyjOk.  Any further discussion needed on that then?16:16
_erlon_smcginnis: 3.5 actually16:16
smcginnisOK, so a little work to do there yet.16:17
_erlon_I think DEVSTACK should allow you to set the version. We are just using the default16:17
smcginnisIt just depends on what version is available on your platform.16:17
smcginnisNothing controlled by devstack other that USE_PYTHON3=true16:17
_erlon_smcginnis: hmm, jobs still running on xenial16:17
_erlon_smcginnis: if 3.7 is not available there and we need to move to ubuntu 18 it will be a big lap16:18
smcginnisYou probably should move though. Xenial isn't a supported version anymore.16:19
whoami-rajati thought CI's moved to Bionic?16:19
smcginnisjungleboyj: Guess this should have been a full topic and not just an announcement. :D16:19
_erlon_smcginnis: jungleboyj: I know 3.7 is the recommended, but is that a requirement for Train?16:19
jungleboyj:-)  Well, it is good we are having the discussion.16:19
_erlon_move to ubuntu 18 will take us some time16:20
smcginnis_erlon_: Yes, that's what we've stated several times over the last few months.16:20
rajinirwalshh_, jungleboyj: sorry I'm late. All dell emc ci has moved to 3.716:20
smcginnisrajinir: Thanks!16:20
jungleboyjrajinir:  No problem.  Thank you!16:20
_erlon_whoami-rajat: if you move them its moved :P16:20
e0neubuntu 18.04, python 3.5 and 3.7 should be supported16:21
smcginnis3.6 and 3.7, not 3.516:21
_erlon_smcginnis: damn, I just picked the python 3 part16:21
e0nesmcginnis: sure, just a typo :(16:21
smcginnisAnd can run on whatever you can install py3.7 on, but if you want to actually run what customers are being told is supported, that's Bionic, CentOs/RHEL7, or openSUSE Leap 15.16:22
*** liuyulong has quit IRC16:22
smcginnise0ne: ;)16:22
rajinirThere are two flags in devstack USE_PYTHON3 and PYTHON3_VERSION16:22
smcginnisOh, great.16:23
_erlon_rajinir: great! Good to know thanks16:24
_erlon_I'll give a shot on that16:24
jungleboyjAnything more on Py3?16:25
*** rfolco has quit IRC16:25
jungleboyjI take that as a no.16:26
*** rfolco has joined #openstack-meeting16:26
jungleboyjThank you all vendors for your input and for participating here.16:26
jungleboyjAppreciate all of you that stay active.16:26
*** yamahata has quit IRC16:27
jungleboyjOk.  So ...16:27
jungleboyj#topic Open Discussion16:27
*** openstack changes topic to "Open Discussion (Meeting topic: Cinder)"16:28
*** iyamahat has quit IRC16:28
jungleboyjAnything else that people want to discuss?16:28
_erlon_I do16:28
jungleboyj_erlon_: Sure.16:28
_erlon_I would like to get some input on the replication interaction beteewn Nova and Cinder16:29
_erlon_may be there's someone here with some backgrond and experience on that16:29
_erlon_Im trying to understand if is possible to do a dynamic re-discover of volumes after a failover/failback16:29
jungleboyjWhat kind of information are you looking for?16:30
jungleboyjHmmm ...16:30
jungleboyjgeguileo: You know that code path to some extent ...16:31
_erlon_I know, that currently its said that you need to detach and re-attach the volumes, but this seems to be a very manual process and I *think* its not possible for volume backed VMs16:31
geguileothere is no interaction afaik16:31
*** kopecmartin is now known as kopecmartin|off16:31
geguileo_erlon_: if you mean for boot volume VMs, yes, you are correct16:31
jungleboyjRight.  Limited functionality there.16:32
geguileoI think I wrote somewhere current limitations...16:32
_erlon_geguileo: because its not implemented or because is not possible?16:32
_erlon_I was trying to imagine how it would be possible, but I think it might not16:32
jungleboyjFor Volume Backed VMs I think it is highly unlikely that it could work.16:34
_erlon_jungleboyj: yep, so, one would have to re-create those kind of VMs16:34
jungleboyj_erlon_:  Correct.16:34
smcginnisIt's all very manual right now, kind of on purpose.16:35
geguileo_erlon_: I believe this falls in the same category of changing the root volume contents16:35
jungleboyjsmcginnis: ++16:35
smcginnisPast attempts had tried to bite off too much, so we wanted a minimally viable feature.16:35
geguileo_erlon_: so it could be implemented in the same way that we are working now to reimage the root volume16:35
smcginnisI know folks want something like VMware SRM, but that's not at all what we provide and it would take a LOT of work to get there.16:35
geguileo_erlon_: but in this case it would need to reattach it16:35
_erlon_smcginnis: it can contiue to be manual, but only triggered manualy, not the whole process, that sometims might require manual intervention to DB16:36
_erlon_how its peoples experience with what we have so far16:37
*** mattw4 has quit IRC16:37
*** mattw4 has joined #openstack-meeting16:37
_erlon_I hope nobudy ever needed to use it lol16:37
jungleboyj_erlon_:  That is a good question.  Not sure how many people are actually using it.16:37
jungleboyjAfter all the work to get it there ... if no one is using it.  *Sigh*16:38
_erlon_jungleboyj: we found out this lat days that our SF driver has some flaws that would make hardly possible to someone to use it, so, we believe nobody has ever really even tried16:38
jungleboyjProbably true.16:39
*** iyamahat has joined #openstack-meeting16:39
geguileo_erlon_: replication at this point is mainly to ensure you don't lose data16:39
geguileobut to recover, that would require a lot of knowledge and manual steps16:40
_erlon_jungleboyj: Im putting 2 meaning to the 'using' word, I would expect people to use, in the sense of having it ready for a disaster, but not really having to do a failover16:40
jungleboyjAh, true enough.16:40
geguileoit was discussed at some point to have a feature to "try the failover/failback"16:41
jungleboyjYes.  Wasn't some of that implemented?16:41
_erlon_geguileo: yes, that was the first point in replication v1. To be able to continually test the process16:41
geguileoto ensure that it was actually working16:41
_erlon_but with the backend based replication on v2 this was left behind16:42
*** mattw4 has quit IRC16:42
jungleboyjAh, that is right.16:43
_erlon_it is possible to do it, you would need to setup a backend using the same arrays and them keep failing over it back and forth periodically16:44
jungleboyjSo, I think what we are getting at here is that if this hasn't been tested by vendors, it probably hasn't been tested.16:44
jungleboyjThat is not good.16:45
geguileojungleboyj: you mean that the failover and failback hasn't been tested?16:45
jungleboyjgeguileo: Not sure.16:45
geguileoor that the whole process of failing over + making the VMs work?16:45
jungleboyjWho has tested it?16:45
geguileoI tested it16:45
jungleboyjOk, that is good.16:46
geguileowhen I was helping jobernar on the RBD failover16:46
jungleboyjDid you do anything with VMs?16:46
geguileoand I discovered a bunch of issues in our core code and fixed most of them16:46
_erlon_geguileo: we mean that there's few testing on Cinder and there not a good way for users that have it in production to test the failover16:46
geguileojungleboyj: this was a long time ago, when Nova couldn't even force-detach16:47
_erlon_jungleboyj: we are probably putting together some replication tests this release we could try to run them on the gate with ceph16:47
geguileoso it was not possible to cleanly re-attach a volume, the old one would still be there16:47
geguileo_erlon_: agreed, there is not enough testing16:47
jungleboyjOk.  That isn't surprising.16:48
geguileo_erlon_: and recovering VMs is not easy (it is HARD)16:48
jungleboyjThat is why there needs to be a detach and reattach?16:48
*** ricolin has quit IRC16:48
_erlon_geguileo: if you re-attach the device will came back in another path in the VMs right?16:48
geguileojungleboyj: in a perfect world we should just tell Nova which volumes have been failed over16:48
_erlon_yeap, I assume so16:49
geguileoand nova would do whatever needs to do16:49
geguileo_erlon_: yup16:49
jungleboyjYeah, that would be nice.16:49
*** lpetrut has quit IRC16:49
_erlon_geguileo: couldn't Cinder let nova know it? so, that would be a more straightforward process for the admin?16:50
geguileo_erlon_: but maybe Nova can hack around this16:50
geguileo_erlon_: yes, Cinder could let Nova know16:50
geguileowhich volumes and the instances they are connected to16:50
geguileoiirc the failover method returned volumes that have been failed over16:50
_erlon_geguileo: Nova can, but not the OS, which will  be trying  to  write to the dead device16:51
geguileoso then Cinder would just need to check the instances they are attached to and tell Nova about those16:51
_erlon_geguileo: yes they do16:51
geguileo(ok, my memory is not that bad)16:51
geguileo_erlon_: we would have to talk with Nova and see if it would be helpful for them to know the change16:52
geguileo(aka can they do something about it?)16:52
_erlon_geguileo: mhm, Ill try to bring that to next Nova meeting16:53
geguileo_erlon_: thanks16:53
_erlon_not sure if Ill make it tomorrow, but asap16:53
jungleboyj_erlon_:  Cool.  Thank you for following up on that.16:54
_erlon_jungleboyj: sure, np16:54
jungleboyj#action Erlon to follow up with Nova team to find out if there is anything they can do to handle failures better if they know the volumes failed over and the associated instances.16:54
jungleboyjWe have 6 minutes left.  Anything else that people would like to discuss.16:55
jungleboyjgeguileo:  Thanks for the expertise there by the way.16:55
*** diablo_rojo has quit IRC16:56
jungleboyjOk.  Looks like everyone has gone quiet so I will wrap up the meeting.16:56
jungleboyjThank you all for attending.  Good discussions today.16:56
smcginnisThanks jungleboyj16:56
*** openstack changes topic to "OpenStack Meetings ||"16:56
openstackMeeting ended Wed Jun 19 16:56:48 2019 UTC.  Information about MeetBot at . (v 0.1.4)16:56
_pewp_jungleboyj (♦亝д 亝)ノ16:56
openstackMinutes (text):
*** davidsha has quit IRC16:57
*** woojay has left #openstack-meeting16:57
*** Lucas_Gray has quit IRC16:58
*** yamahata has joined #openstack-meeting16:59
geguileojungleboyj: np16:59
*** markvoelker has joined #openstack-meeting16:59
*** trident has quit IRC17:02
*** markvoelker has quit IRC17:04
*** trident has joined #openstack-meeting17:04
*** e0ne has quit IRC17:20
*** tesseract has quit IRC17:21
*** eharney has quit IRC17:25
*** diablo_rojo has joined #openstack-meeting17:26
*** ayoung has joined #openstack-meeting17:32
*** tesseract has joined #openstack-meeting17:36
*** mattw4 has joined #openstack-meeting17:36
*** eharney has joined #openstack-meeting17:38
*** raildo has quit IRC17:44
*** psachin has quit IRC17:48
*** melwitt is now known as jgwentworth17:55
*** markvoelker has joined #openstack-meeting18:00
*** ociuhandu has quit IRC18:02
*** markvoelker has quit IRC18:05
*** diablo_rojo has quit IRC18:05
*** electrofelix has quit IRC18:08
*** pcaruana has quit IRC18:11
*** diablo_rojo has joined #openstack-meeting18:31
*** e0ne has joined #openstack-meeting18:35
*** dtrainor has quit IRC18:36
*** dtrainor has joined #openstack-meeting18:36
*** e0ne has quit IRC18:36
*** jamesmcarthur has quit IRC18:40
*** jamesmcarthur has joined #openstack-meeting18:41
*** dtrainor has quit IRC18:42
*** dtrainor has joined #openstack-meeting18:43
*** jamesmcarthur has quit IRC18:46
*** diablo_rojo has quit IRC18:46
*** tesseract has quit IRC18:49
*** diablo_rojo has joined #openstack-meeting18:57
SotK#startmeeting storyboard19:00
openstackMeeting started Wed Jun 19 19:00:22 2019 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: storyboard)"19:00
openstackThe meeting name has been set to 'storyboard'19:00
SotK#link Agenda19:00
SotK#topic Announcements19:00
*** openstack changes topic to "Announcements (Meeting topic: storyboard)"19:00
*** markvoelker has joined #openstack-meeting19:01
SotKfungi migrated Karbor's bugs from Launchpad19:01
SotK and we released the API (twice because there was a bug)!19:01
SotKanyone have anything further to announce?19:02
diablo_rojoNope, thats all I had :)19:02
SotK#topic Migration Updates19:03
*** openstack changes topic to "Migration Updates (Meeting topic: storyboard)"19:03
SotKas noted above, Karbor's bugs were migrated19:03
SotKany other updates I've missed?19:03
fungiyup, a good time was had by al19:03
fungi(al always has a good time)19:03
*** jamesmcarthur has joined #openstack-meeting19:04
fungino other migration updates for which i'm aware, no19:05
diablo_rojoI suppose I have some updating of the board/story to do19:05
*** e0ne has joined #openstack-meeting19:05
diablo_rojoI think I've fallen behind a bit on keeping ht up to date19:05
*** ayoung has quit IRC19:06
SotK#link!/board/45 Migration Status board19:07
diablo_rojoYeah that one :)19:07
SotK#topic Story Triaging19:08
*** openstack changes topic to "Story Triaging (Meeting topic: storyboard)"19:08
SotKso we had a pretty successful time the other week tagging a bunch of stuff and creating some stories19:08
SotKwe should finish that off with more tagging and updating the priorities board19:08
diablo_rojo+2 we should do it again19:09
diablo_rojoand then I can document all the tags19:09
SotKwhen is a good time?19:09
diablo_rojoan hour earlier than this works or Friday anytime19:10
*** jamesmcarthur has quit IRC19:10
SotKshall we do 17:00 UTC on Friday like last time then?19:12
diablo_rojoWorks for me.19:12
diablo_rojofungi, did you wanna join the party?19:12
diablo_rojoI can add you to the invite.19:13
fungii've added it to my calendar for 1700z on the 21st19:13
fungii should be around19:13
fungiif nothing's on fire i'll try to pitch in19:14
diablo_rojofungi, cool :) I'll share my zoom link/number for you to join too.19:14
*** ayoung has joined #openstack-meeting19:14
SotK#agreed More story triaging/tagging at 17:00 UTC on Friday 21st June19:15
SotK#topic In Progress Work19:15
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:15
SotKthe attachments is waiting on me updating the patches to use openstack-sdk and form posts rather than the current method19:16
diablo_rojofungi, let me know if you want me to send it to a different email I just did it to your @yuggoth19:16
SotKs/attachments/attachments work/19:16
fungidiablo_rojo: that'll be perfect19:16
fungii owed an update on production server backups... confirmed it's working and did a remote restore from the backup server to make sure it contains a current nightly db dump19:17
diablo_rojoSotK, noted, I will keep an eye out for those updates19:17
SotKopenstack-sdk doesn't seem to work with the swift-all-in-one docker image I've been using (since it uses legacy auth), so its also blocked on me finding an image it does work with and/or deploying devstack or something to test against19:18
SotKthe security teams stuff is pretty much finished now19:18
SotKit might be worth adding API support for auto-assigning teams as well as doing that in the UI, to make sure its enforced no matter how folk create the story19:18
SotKand there is still outstanding work to subscribe the team members to the story19:19
fungiyep, it's on my to do list to set up some security team integration on sb.o.o19:19
diablo_rojoSotK, do we have a story for the remaining work?19:19
fungias in configure a couple of existing security teams as associated with projects19:19
diablo_rojoOr is that all in the original story?19:19
*** markvoelker has quit IRC19:20
SotKits in the original story19:20
diablo_rojoOkay cool19:20
diablo_rojonevermind then :)19:20
SotK#link!/story/2000568 Private stories story19:20
SotKdid we get a new set of slow query logs btw?19:21
fungiwe're still loggging it19:21
fungii don't think any new analyses have been run on it yet19:21
fungicorvus: mordred: is that something either of you have time for in the near-ish future?19:22
fungiif not, i can follow earlier notes and work it out19:22
*** jamesmcarthur has joined #openstack-meeting19:23
diablo_rojoSince we no longer have an intern... to work on storyboard search optimizations :(19:24
fungidoesn't mean they won't be worked on, but yes that's sad for us (and exciting for our would-be intern!)19:25
*** phughk has joined #openstack-meeting19:25
SotKindeed, someone else will have to find time :)19:26
SotKanything else in progress that folks want to raise?19:28
diablo_rojomkarray's patches?19:28
diablo_rojoI still have more to fix up again don't I?19:28
diablo_rojoTwo of the three anyway it looks like19:29
diablo_rojoI will try to get those up today19:29
SotKthanks, I'll get them reviewed and merged when you do19:30
diablo_rojoOh haha for one of them there was a comment about doing a search with a regex and I had a brain lapse. Havent had to write a regex in like.. 5 years.19:32
* SotK recommends this wonderful thing:
diablo_rojoHeh, was just playing with something similar, but this one looks better19:34
diablo_rojoWill get that done asap.19:35
SotKthanks :)19:36
fungimy only real recommendation is to not try to write a regular expression parser19:36
diablo_rojoNot on my todo list today19:36
fungialso, keep in mind that operating on user-supplied regular expressions can be dangerous19:37
fungiso choose an expression parser specifically designed for handling user-supplied expressions19:37
diablo_rojoWe can chat about all that post meeting in the channel19:39
SotKanything else in progress?19:39
fungiyeah, there's one i'm aware of for python but having trouble remembering the name19:39
fungianyway, don't use the re module from python's stdlib19:40
fungiit's great for handling statically-defined expressions, dangerous for untrusted user-supplied ones19:40
diablo_rojoThat makes sense19:41
SotKiirc the comment was about matching user input with a regex rather than naively trying to treat everything with a colon in differently, so we shouldn't have to worry too much about that I think19:42
fungiahh, so not accepting regular expressions as a search syntax19:42
fungithat should be safe enough with the re module then19:43
fungiallowing searches based on regular expressions would also be nice, but that's a in-the-future-when-we-have-a-new-search-language sort of thing19:43
diablo_rojoIts in javascript in the webclient though so a python module wont work?19:43
fungiright, if this is matching within javascript you'll need to use one of the many regex parsers on npm i suppose19:44
*** mlavalle has left #openstack-meeting19:44
fungi(unless there's native support for them within the javascript language itself?)19:44
fungi((seems doubtful, but i have no idea))19:45
SotKit does:
*** eharney has quit IRC19:47
diablo_rojoOkay well I got nothing else for the meeting.19:48
diablo_rojoWe can continue regexing in channel :)19:48
SotKlets end it here then, thanks for coming folks :)19:49
*** openstack changes topic to "OpenStack Meetings ||"19:49
openstackMeeting ended Wed Jun 19 19:49:16 2019 UTC.  Information about MeetBot at . (v 0.1.4)19:49
openstackMinutes (text):
*** ayoung has quit IRC19:49
fungithanks SotK!19:51
*** jgwentworth is now known as melwitt19:52
*** ralonsoh has quit IRC19:53
*** artom has quit IRC20:02
*** e0ne has quit IRC20:11
*** jamesmcarthur has quit IRC20:13
*** jamesmcarthur has joined #openstack-meeting20:15
*** markvoelker has joined #openstack-meeting20:17
*** belmoreira has joined #openstack-meeting20:20
*** jamesmcarthur has quit IRC20:23
*** eharney has joined #openstack-meeting20:36
*** markvoelker has quit IRC20:36
*** whoami-rajat has quit IRC20:47
*** e0ne has joined #openstack-meeting20:55
*** e0ne has quit IRC20:59
*** alecuyer has joined #openstack-meeting21:00
*** e0ne has joined #openstack-meeting21:00
timburke#startmeeting swift21:00
openstackMeeting started Wed Jun 19 21:00:46 2019 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:01
timburkesounded like kota_ wouldn't be able to join, and rledisez is still moving21:02
timburkelet's get started!21:02
timburkeagenda's pretty short21:03
timburkeso, let's do some updates21:03
timburke#topic py321:03
*** openstack changes topic to "py3 (Meeting topic: swift)"21:03
timburkeall the unit tests have been approved!21:03
timburkejust waiting on locale and tempurl to make their way through the gate21:04
timburkelast blocker for a release is being able to run func tests under py2 against services running py321:04
timburkethat requires a couple small fixups21:06
timburke to make func tests not break prefixes part-way through a codepoint21:06
timburke to get some things in s3api to be native strings21:06
mattoliverauwow, cool nice work. Sorry I'm been away most the last week (since before the last meeting) and still playing catchup here and at work.21:06
mattoliverauIs the priority reviews page up to date?21:07
timburke to make ECAppIter happy, but i might be willing to known-issues it for now21:07
timburkemattoliverau, mostly. i'll make sure it is shortly after the meeting21:08
mattoliverauoh looks like it is. nice21:08
timburkea bunch of stuff landed just this morning :-)21:08
timburke is more meaty, required to work around so we can send and receive non-ascii header names21:09
timburkei think once we get those in, i'll tag 2.2221:10
claygTAG IT21:10
timburkenext steps are things like getting a py3 dsvm job ( and porting func tests (there's a list on
timburkeclayg, REVIEW IT21:11
claygseems reasonable21:11
timburkeafter those, we try to suss out what kind of a test plan we'd like to see to declare full support21:12
timburkewell, that and probe tests21:12
timburkeanybody have questions on py3 or what needs doing there?21:12
timburke#topic lots of small files21:13
*** openstack changes topic to "lots of small files (Meeting topic: swift)"21:13
timburkealecuyer, how's it going?21:13
alecuyerI have written more tests for, the classes this time. That was slow and I restarted once, but I hope to have something "reviewable" soon21:14
alecuyerI pushed it here but I don't think it's worth looking at yet :)21:14
timburkewhat can we do to help? more reviews, more patches, more manual testing?21:15
alecuyerWell if someone wants to take a quick look , just to check if it's very wrong, but otherwise I think I just have to write these tests :)21:16
timburkei really need to try out sometime ...21:17
timburkesounds good21:17
timburke#topic open discussion21:17
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:17
timburkeanything else to bring up?21:18
timburkei know clayg's been looking at symlinks and versioning and s3api lately21:18
claygit's gettin there21:18
claygthe hardlink to symlink thing is getting so annoying21:19
timburkeshould we give a little background on it to help mattoliverau and alecuyer catch up?21:20
mattoliverauyes please :)21:21
alecuyerhardlink is "symlink with md5 of target" or is that very wrong21:21
claygthat's it21:21
claygthe neat thing this does is allow us to keep some information uptodate in the container listing21:21
claygso normally when you put a symlink your container listings just show these zero byte objects with the symlink_target key21:22
mattoliveraumd5 of target, sounds like a bitch to keep up to date in the symlink21:22
claygbut when you KNOW this symlink doesn't work unless the target doesn't change you can keep the hash (and the content-length) in the listing and you know it's valid (at least for the lifetime of the hardlink)21:22
claygyeah so the use-case was actually versioned writes21:23
claygso versioned writes today does a lot of moving data around to keep the "active" objects actually "in" the container... but with symlinks we can solve for data protection requirements in place21:23
claygand with using hardlinks we can even make listings of the version'd container looking reasonable (as far as etags & bytes)21:24
claygso that's all great21:24
timburkeit also resolves some race conditions when you have concurrent overwrites to the same (biggish) object21:25
claygsomewhere along the way the idea of "use hardlinks to point to the versions" got sideways when the the "version" was actually a symlink... just cause when we fleshed out hardlinks we didn't really define the behavior for hardlink to symlink...21:25
claygright as "a bunch of data movement" wasn't bad enough - there's also the fact that it takes awhile and leaves wide race windows21:26
mattoliveraulol, wow.21:26
alecuyerthat's a case we need to support then ?21:26
claygsymlink based versions is awesome, and with hardlinks there's very little downside21:26
*** rfolco is now known as rfolco_off21:26
claygthe hardlink to symlink use-case?  currently I have versioned writes just doing symlinks when the target in the version'd container is itself a symlink... and that may be the way to go if we can't come up with a definition for the behavior of hardlink to a symlink that we WANT21:27
timburkealecuyer, i like your thought process :-)21:27
timburkei think part of it was that we have existing functional tests with versioning and symlinks, and we want to make sure they still pass21:28
alecuyerbut now I think I see the case for it with clay's explanation ;)21:28
claygthe usecase for *hardlinks* or specifically for hardlinks *to symlinks*21:28
alecuyerah, hardlinks I had no doubts, hardlinks to symlinks I meant21:29
*** enriquetaso has quit IRC21:29
claygI think the use-case for hadnlinks is pretty solid - the etag validation is nice, but the benifit is mostly the container listings - by making more concret the relationship with the link and the target it because reasonable to maintain state about what that hardlink points to...21:29
claygso that's great21:29
claygyeah hardlinks to symlinks 🤮21:29
mattoliverauoh yeah, ok so for versioned writes hardlinks sound great.. once the edge cases are thought through. Tho a random symlink with a pointer to an object elsewhere, with an md5 of the target seems hard to keep up to date. Unless you know the target never changes.21:30
claygit just ends up akward in versioned writes having to track if it's versioning an object (write a hardlink) or a symlink (write a symlink)21:30
*** _erlon_ has quit IRC21:31
mattoliveraubut hey maybe people actually want that. You'll then know if somethings changed. maybe there are usecases you'd actaully want to use that. Like a tamper seal21:32
*** markvoelker has joined #openstack-meeting21:33
claygI think there's definately use-cases for symlinks and hardlinks21:33
mattoliverauBut I haven't looked at the code, so only making assumptions on the discussion here. I should go take a look :)21:33
claygversioned writes definately prefers hardlinks because it makes the redirection more transparent21:33
claygeverything I have posted is rusty - i'll try to push up some current revisions soon21:34
alecuyerI'm lost now, I thought you woulnd't update the md5 (if the target changes the link is broken ?) but I should try it and read the code :)21:34
alecuyerit's that one right ?
claygno, i need to push21:34
claygidk why tim brought it up21:34
claygby next week i'll have some patches21:34
mattoliveraubecause it's interesting? ;)21:35
timburkemainly 'cause you mentioned it in channel this morning ;-)21:35
claygthe end game is s3api compatible object versioning support21:35
timburkeand i know that we want to be reviewing it soonish21:35
timburkesooner we can get other people thinking about it, too, the better21:35
timburkeanything else we want to discuss?21:36
timburkeall right, then we oughta let mattoliverau get breakfast and alecuyer get to bed :D21:38
mattoliverauthanks :)21:38
timburkethank you all for coming, and thank you for working on swift!21:38
*** openstack changes topic to "OpenStack Meetings ||"21:38
alecuyergood night then ;)21:38
openstackMeeting ended Wed Jun 19 21:38:35 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:38
openstackMinutes (text):
*** alecuyer has left #openstack-meeting21:38
*** e0ne has quit IRC21:39
*** jamesmcarthur has joined #openstack-meeting21:40
*** jamesmcarthur has quit IRC21:51
*** dviroel has quit IRC21:51
*** yamamoto has joined #openstack-meeting21:51
*** markvoelker has quit IRC21:53
*** yamamoto has quit IRC21:56
*** mriedem has quit IRC21:59
*** vishalmanchanda has quit IRC22:03
*** diablo_rojo has quit IRC22:05
*** belmoreira has quit IRC22:13
*** belmoreira has joined #openstack-meeting22:17
*** zbr|ruck has quit IRC22:17
*** carloss has quit IRC22:27
*** diablo_rojo has joined #openstack-meeting22:35
*** belmoreira has quit IRC22:45
*** markvoelker has joined #openstack-meeting22:50
*** rfolco_off has quit IRC22:56
*** markvoelker has quit IRC23:05
*** ykatabam has joined #openstack-meeting23:07
*** dmsimard0 has joined #openstack-meeting23:08
*** dmsimard has quit IRC23:08
*** rcernin has joined #openstack-meeting23:16
*** lseki has quit IRC23:29
*** slaweq has quit IRC23:47
*** yamamoto has joined #openstack-meeting23:53

Generated by 2.15.3 by Marius Gedminas - find it at!