Wednesday, 2019-08-28

*** ijw_ has joined #openstack-meeting00:13
*** ijw has quit IRC00:17
*** ijw_ has quit IRC00:18
*** bbowen has quit IRC00:29
*** gyee has quit IRC00:43
*** zhangchi has joined #openstack-meeting00:44
*** markvoelker has quit IRC00:57
zhangchi#startmeeting tricircle00:59
openstackMeeting started Wed Aug 28 00:59:51 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.00:59
*** openstack changes topic to " (Meeting topic: tricircle)"00:59
openstackThe meeting name has been set to 'tricircle'00:59
zhangchiGood Moring, everyone01:00
zhangchiTime's up for tircircle meeting01:00
*** larainema has joined #openstack-meeting01:00
*** tetsuro has joined #openstack-meeting01:12
*** tetsuro has quit IRC01:13
*** ekcs has quit IRC01:14
zhangchiI think there only these things to discuss today: add multi-region name in kuryr has been promoted  and patch has been submitted01:17
*** jamesmcarthur has joined #openstack-meeting01:22
*** enriquetaso has quit IRC01:22
zhangchiMmh , We'll start up the specs reunifying Tricircle and trio2o in test01:29
zhangchiI think I am alone today, That's ok, I will endmeeting rightnow and hope to see you at Sep 11th01:30
*** openstack changes topic to "OpenStack Meetings ||"01:31
openstackMeeting ended Wed Aug 28 01:31:04 2019 UTC.  Information about MeetBot at . (v 0.1.4)01:31
openstackMinutes (text):
*** zhangchi has quit IRC01:35
*** hyunsikyang has quit IRC01:46
*** markvoelker has joined #openstack-meeting01:52
*** jamesmcarthur has quit IRC01:54
*** markvoelker has quit IRC02:02
*** markvoelker has joined #openstack-meeting02:03
*** nicolasbock has quit IRC02:09
*** apetrich has quit IRC02:09
*** eharney has quit IRC02:10
*** joxyuki has quit IRC02:13
*** markvoelker has quit IRC02:13
*** markvoelker has joined #openstack-meeting02:14
*** markvoelker has quit IRC02:24
*** ricolin has joined #openstack-meeting02:25
*** kunlunwan_ has joined #openstack-meeting02:28
*** kunlunwan_ has quit IRC02:31
*** kunlunwan has joined #openstack-meeting02:32
*** kunlunwan has quit IRC02:41
*** bbowen has joined #openstack-meeting02:44
*** psachin has joined #openstack-meeting03:10
*** ianychoi has quit IRC03:29
*** ianychoi has joined #openstack-meeting03:30
*** rfolco has quit IRC03:32
*** brinzhang has quit IRC03:49
*** brinzhang has joined #openstack-meeting03:50
*** brinzhang has quit IRC03:51
*** brinzhang has joined #openstack-meeting03:51
*** markvoelker has joined #openstack-meeting04:05
*** markvoelker has quit IRC04:10
*** njohnston has quit IRC04:35
*** darvon has quit IRC04:40
*** darvon has joined #openstack-meeting04:41
*** brault has joined #openstack-meeting04:50
*** brault has quit IRC04:54
*** zhubx has joined #openstack-meeting05:09
*** boxiang has quit IRC05:10
*** markvoelker has joined #openstack-meeting05:20
*** markvoelker has quit IRC05:25
*** jhesketh has quit IRC05:34
*** yaawang has quit IRC05:39
*** yaawang has joined #openstack-meeting05:40
*** jhesketh has joined #openstack-meeting05:42
*** Luzi has joined #openstack-meeting05:46
*** links has joined #openstack-meeting05:46
*** lpetrut has joined #openstack-meeting06:00
*** zhubx has quit IRC06:18
*** zhubx has joined #openstack-meeting06:18
*** slaweq has joined #openstack-meeting06:27
*** zhubx has quit IRC06:28
*** zhubx has joined #openstack-meeting06:28
*** yaawang has quit IRC06:31
*** slaweq has quit IRC06:32
*** yaawang has joined #openstack-meeting06:33
*** slaweq has joined #openstack-meeting06:48
*** macz has joined #openstack-meeting06:52
*** macz has quit IRC06:56
*** zhubx has quit IRC07:01
*** zhubx has joined #openstack-meeting07:01
*** trident has quit IRC07:08
*** zhubx has quit IRC07:11
*** zhubx has joined #openstack-meeting07:11
*** rcernin has quit IRC07:12
*** ykatabam has quit IRC07:14
*** trident has joined #openstack-meeting07:17
*** ykatabam has joined #openstack-meeting07:19
*** zhubx has quit IRC07:20
*** zhubx has joined #openstack-meeting07:20
*** zhubx has quit IRC07:30
*** zhubx has joined #openstack-meeting07:30
*** baojg has quit IRC08:07
*** apetrich has joined #openstack-meeting08:11
*** ralonsoh has joined #openstack-meeting08:24
*** zhubx has quit IRC08:26
*** zhubx has joined #openstack-meeting08:27
*** zhubx has quit IRC08:27
*** boxiang has joined #openstack-meeting08:29
*** boxiang has quit IRC08:33
*** boxiang has joined #openstack-meeting08:34
*** jraju__ has joined #openstack-meeting08:56
*** links has quit IRC08:57
*** cschwede has joined #openstack-meeting08:59
*** mtreinish has quit IRC09:13
*** mtreinish has joined #openstack-meeting09:15
*** brault has joined #openstack-meeting09:17
*** links has joined #openstack-meeting09:51
*** jraju__ has quit IRC09:52
*** zhubx has joined #openstack-meeting10:00
*** zhubx has quit IRC10:03
*** zhubx has joined #openstack-meeting10:03
*** boxiang has quit IRC10:03
*** zhubx has quit IRC10:04
*** zhubx has joined #openstack-meeting10:04
*** macz has joined #openstack-meeting10:05
*** zhubx has quit IRC10:06
*** zhubx has joined #openstack-meeting10:07
*** heikkine has joined #openstack-meeting10:07
*** zhubx has quit IRC10:08
*** zhubx has joined #openstack-meeting10:09
*** macz has quit IRC10:09
*** zhubx has quit IRC10:09
*** zhubx has joined #openstack-meeting10:10
*** ykatabam has joined #openstack-meeting10:10
*** ricolin has quit IRC10:25
*** HPCJohn has joined #openstack-meeting10:40
*** oneswig has joined #openstack-meeting10:58
oneswig#startmeeting scientific-sig11:00
openstackMeeting started Wed Aug 28 11:00:14 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
*** janders has joined #openstack-meeting11:01
oneswigback to school...11:01
janderstoo cool for school!11:01
jandersg'day all11:01
oneswighey janders, how's things?11:02
jandersnot too bad... just got the boot media for our GPFS cluster11:02
janderswas overlooked in the bill of materials somehow11:02
jandersbuild starting next week11:02
oneswigsounds good - how big?11:03
oneswighi verdurin, trust you've had a good summer11:03
janderssmall but should be punching above it's weight11:03
janderssix nodes11:03
janders12x8TB NVMe each11:03
oneswig2x 100G IB as well?11:03
verdurinoneswig: I like to think it's not quite over yet, but we'll see...11:03
oneswigverdurin: indeed11:03
oneswigjanders: nice!  does the HDR work?11:04
jandersI'm quietly hoping to reach the 100GB/s mark11:04
janderswell.. it doesn't.. yet11:04
jandersbut hopefully soon11:04
jandersif we wanted pure IB we could probably make it work today, but we're waiting for the VPI stuff to work11:05
jandersit's still few weeks from GA11:05
oneswigdual port hdr?11:06
jandersthis is actually a nice intro to the HPC-ceph discussion11:06
oneswigWe only have one item for the agenda - let's move on to it...11:07
jandersthe idea behind this cluster is ceph-like self healing with the goodness of RDMA transport11:07
oneswig#topic Scientific Ceph SIG11:07
*** openstack changes topic to "Scientific Ceph SIG (Meeting topic: scientific-sig)"11:07
*** carloss has joined #openstack-meeting11:07
jandersso - speaking of Ceph & HPC - how's RDMA support in Ceph going?11:07
oneswig#link Ceph meeting later today
oneswigjanders: my experience of it wasn't compelling11:07
*** nicolasbock has joined #openstack-meeting11:08
oneswigbut it was ~9 months ago11:08
janderswhat were the issues?11:08
verdurinYes, saw someone ask you about that on the mailing list oneswig11:08
oneswigAnd I'd love to spend some quality time with it in the absence of distraction...11:08
oneswigthe issues were various.  It worked OK for RoCE but didn't work reliably in other fabrics11:09
verdurinI'm trying to squeeze an update on this from Mellanox11:09
oneswigat the time I had EDR IB and OPA to compare with11:09
oneswigOPA I think was a first11:09
jandersthis might be the first time I hear something works with RoCE but not IB11:09
jandersusually it's the other way round isn't it? :)11:09
oneswigOn the RoCE side, performance was inconclusive.  I had a 25GE network and the performance saturated that.  The devices I had were SATA SSDs and networking was not the bottleneck.11:10
oneswigSo it was hard to show substantial benefit on the hardware available.11:10
oneswigIt actually underperformed TCP for large messages11:10
oneswigThe IB, I forget what the issue was but I think there were stability problems.  Lost transactions in the msgr protocol, that kind of thing.11:12
jandersyeah sounds a bit rough around the edges every time I look at it11:12
*** tesseract has joined #openstack-meeting11:12
jandersit would be awesome to have it relatively stable11:12
oneswigOne neat thing was that Intel had contributed some work for iWARP that appeared to have nothing to do with iWARP per se, but did introduce rdmacm, which was needed for all these weird and wonderful fabric variants11:12
*** ykatabam has quit IRC11:13
oneswigjanders: +1 on that, would love to see it work (and be worth the trouble)11:13
jandersIntel... I have some harsh words to say there in the AOB11:13
janderskeyword: VROC11:13
oneswigooh, won't be long to wait, we only have a short agenda for today.11:14
oneswigverdurin: how is Ceph performing for your workloads?11:14
verdurinNo complaints so far, oneswig: though I know there is much heavier work to come11:15
oneswig#link Ceph day for Research and Scientific Computing at CERN
oneswigverdurin: sounds intriguing - new projects coming on board?11:15
verdurinYes, and we're also looking at Ceph now for a different storage requirement.11:16
oneswigWill you be at the CERN event?11:16
verdurinI will.11:16
oneswigsuper, see you there :-)11:17
verdurinCurious how it relates to the other Ceph Day that's scheduled for London in October.11:17
jandersI envy you guys... Geneva - sure, 2hrs flight if even that...11:17
verdurinSadly my CERN User Pass has expired, so I have to visit as a civilian, like everyone else.11:17
oneswigjanders: we don't get to go to LCA, in return11:18
jandersif I were to pick one I don't think it'd be LCA11:18
oneswigverdurin: I'm sure they'll remember you...11:18
janderswill be a while till we get the Summit again11:18
verdurinThis is the other Ceph Day I mentioned:
jandersyou guys heading to Shanghai?11:19
verdurinObviously you have to filter out the CloudStack parts.11:19
oneswigI'm planning to be there janders11:19
jandersnot sure what I'll do11:19
verdurinNo plans to go so far.11:20
jandersI wouldn't expect much support given rather tense AUS-CN relations these days11:20
oneswigverdurin: last time I went to Ceph London it was in a venue somewhere in Docklands.  Good to see they've relocated it.11:20
janderswould be fun though!11:20
jandersdo you guys know if it's possible to remote into the PTG?11:20
oneswigjanders: you're not the first to entangle openstack with geo politics.11:20
verdurinoneswig: Canada Water, yes.11:21
oneswigverdurin: ah I remember seeing you there.  Wasn't it around the time of your move out west?11:21
verdurinoneswig: A few months afterwards.11:22
HPCJohnCanada Water Printworks?  5 minute walk from where I live. But I Agree - not a great conference venue.11:22
verdurinoneswig: lots of good user talks at the CERN day. Do you know whether upstream people will be there?11:22
oneswigverdurin: don't know I'm afraid11:23
oneswigHi HPCJohn, good to see you11:23
oneswigIt was a small venue that doubled as a daycare centre.  Don't remember the name...11:23
oneswigIf I have the chance I'll join the Scientific Ceph meeting later11:24
oneswigMight be interesting to run the RDMA flag up the pole there.11:24
verdurinYes, I'm hoping to do the same.11:24
janderswhat time is it? is it back to back with our meeting, or much later?11:24
oneswigI think any serious effort on making it zing is deferred until the scylladb-derived messenger is introduced (forget the name)11:24
HPCJohnMay I ask what time British Summer time?   I think 16:30 as that is European time also11:25
oneswigTime was 10:30am us eastern/4:30pm eu central time and I think that means 3:30pm BST11:25
oneswigIn Canberra, it's the middle of the night :-(11:26
verdurinHPCJohn: Yes, in my calendar as 15:3011:26
jandersyeah... makes me realise how lucky I am with the timing of this meetup!11:26
jandersI should move to Perth11:26
verdurinjanders: they're going to be discussing the timings, so it's quite possible they'll alternate like this one11:27
jandersthat would be very cool11:27
oneswigOK shall we move on?11:27
oneswig#topic AOB11:27
*** openstack changes topic to "AOB (Meeting topic: scientific-sig)"11:27
oneswigjanders: ?11:27
jandersok... bit of Intel bashing as promised11:27
jandershave you guys played with VROC much?11:27
oneswigTo my shame I admit to never having heard of it11:28
jandersCPU-assisted hybrid RAID11:28
oneswigAh, I think I've heard of that.11:28
janderswe originally wanted to run our BeeGFS nodes in RAID611:28
jandersbut as RAID6 sucks on NVMes, we ended up with smaller RAID0s11:28
jandersbut because of these limitations we thought we'll try VROC on our Cyber kit11:29
jandersso we did11:29
jandersSupported on RHEL711:29
janders...unless you use Ironic11:29
jandersIronic is too cut down to understand it11:29
janderss/ironic/IPA image11:29
oneswigThat's not surprising11:30
jandersso we have dual NVMes but so far can only run off a single one, no RAID protection11:30
oneswigCan you boot from sw-assisted raid?11:30
jandersit's work in progress, we're thinking of retro-fitting RAID after the fact in an automated way11:30
HPCJohnLooking forward to CEPH later on. Lunch calls!11:30
*** HPCJohn has quit IRC11:30
jandersoneswig: yes, we can11:30
jandersjust can't mark the VROC array as root_hint11:30
jandersbit of a bummer really11:31
janderswe're working on the retrofit script in the meantime11:31
oneswigSounds like a DIB element for your IPA image might help with building in the support11:31
janderswe've got an RFE/BZ with RHAT11:31
jandersbut all in all I have a sneaking suspicion we'll just leverage newly added SW-RAID support11:31
jandersas with RAID0/1 VROC doesn't bring much benefit AFAIK11:32
oneswigWith root hints don't you get a broad range of options, even device size?11:32
jandersRAID5/6 - different story11:32
janderstrouble is - IPA just can't see the array11:32
jandersfull RHEL can but not IPA11:32
janderswe had RHAT support look at it, we tweaked IPA initrd but no luck11:32
janderssounds like unnecessary complexity if you ask me11:32
oneswigIt's a fiddly environment to debug, for sure.11:33
*** Lucas_Gray has joined #openstack-meeting11:33
jandersso I'd say if you're looking for VROC for RAID0/1 scenarios, probably steer away from it11:33
jandersfor sure!11:33
verdurinjanders: not "Cost-efftice and simple" then?11:33
jandersfor RAID5/6, especially if there's an alternative root drive, sure11:33
jandersnot at all11:33
jandersnot at all11:33
jandersit did cost us way too much time to troubleshoot this already11:33
jandersso I thought I will share11:34
jandersgood idea but so far pretty troublesome11:34
verdurinThanks for suffering on all our behalf11:34
oneswigI look forward to the sequel...11:35
jandershopefully SW-RAID support will fix this once and for all11:35
jandersVROC->disable; done!11:35
janderson a good news front I played around with NVMe based iSCSI cinter11:35
jandersjust for a small POC11:35
janders3/2GB per sec read/write11:36
janders70k IOPS on a single client11:36
janders200k IOPS across four11:36
jandersnot a bit fan of iSCSI so was quite impressed11:36
oneswighave you tried it with iSER?  That works well11:36
jandersit's just a placeholder for the GPFS when it's ready - so I did not11:36
jandersbut I was expecting maybe 10% of that11:37
jandersnice surprise11:37
janders( unlike VROC ;)11:37
verdurinjanders: do keep us informed about your GPFS work11:38
janderswill do!11:38
oneswigThanks janders!11:38
jandershappy to give a lightning talk about it in Shanghai if it's ready (and if I am there)11:39
janders(or remote in if that's an option)11:39
oneswigI'll pencil you in...11:39
jandersit's EC-GPFS so if it all works as designed it will be a very interesting little system11:39
jandersbit of ceph-like design11:40
janders12x drives a node and self healing11:40
jandersPLUS all the GPFS features and stable RDMA transport11:40
oneswigjanders: what's the condition of the OpenStack drivers for it?11:40
jandersnot ideal, not too bad11:41
oneswigI'm guessing this is bare metal so infrastructure storage requirement is limited11:41
jandersthey claim they discontinued support for it few months back11:41
jandersbut we tested it also few months back and it worked reasonably well11:41
oneswiggood to hear.11:41
janderswe'll probably use it across the board (glance & cinder for VMs, native for BM)11:42
oneswigDid IBM add Manila?11:42
jandersI don't think so but not 100% sure11:43
jandersthe promise is that they cut down development effort for OpenStack to ramp up development effort for k8s11:43
*** markvoelker has joined #openstack-meeting11:43
jandersso when we get to that part, there might be more interesting options11:43
jandersnot sure where that's at right now though11:44
verdurinjanders: no restricted-data concerns for this system?11:44
janderslong story11:44
jandersshort answer - not yet11:44
verdurinIt's always a long story...11:44
janderslong answer - we're still working out some of the cybersecurity research workflows11:44
jandersgiven we're in AOB and we've got 15 mins to go11:45
jandersdo you guys have any experience with malware research related workflows on OpenStack11:45
jandersas in:11:45
janders1) building up the environment in an airgapped system11:45
janders2) getting the malware into the airgapped perimiter11:46
janders3) storing it11:46
janders4) injecting it11:46
jandersthat sort of stuff11:46
janderswe're getting more and more interest in that and it feels a bit like we're trailblazing... but are we?11:46
verdurinjanders: we have an air-gapped system, though not for malware research.11:47
jandershow do you balance security with giving users reasonable flexibility to built up their environment?11:47
oneswigIt's a very interesting use case.  Hope your Ironic node cleaning steps are good.11:47
jandersright now we're in between the easy way (just importing CentOS/RHEL point releases) and the more flexible way (regularly updating repo mirrors inside the airgap, including EPEL)11:48
jandersand this is even before we think about the malware bits11:48
jandersright now (and this is only a few days old concept) I'm thinking:11:49
janders1) build the environment in a less restricted environment (repo access, ssh in via floating IP)11:49
verdurinjanders: we're more like the latter, though in fact our users have very little ability to customise beyond requesting changes for us to implement11:49
janders2) move the environment to a restricted area (isolated network, no floats, VNC access only)11:50
janders3) inject malware by attaching volumes (with encrypted malware inside)11:50
jandersyeah the longer we thing about it the more convinced we are we'll end up playing a significant role in setting up user environments... :(11:51
jandersit really feels like something that either hasn't been fully solved - or has been solved by people who tend not to talk about their work..11:51
verdurinjanders: we did take an approach similar to your 1) and 2) steps, in order to make it more bearable/efficient at the preparation stage11:52
jandersso do you run 1) in non-airgap, take snapshots and import into airgapped for 2)?11:52
verdurinexactly, yes11:53
jandersok! might be a way forward, too11:53
janderswhat worries me is maintaining relatively up-to-date CentOS/RHEL/Ubuntu/...11:53
jandersif we go with what we described, that's an non-issue11:53
jandersfun times!11:54
verdurinYou're always up to something interesting...11:54
oneswigindeed.  Great use case11:54
jandersmy life these days is figuring this out, while getting HDR/VROC to work - and writing paperwork to keep funding going! :)11:54
jandersfrustrating at times11:55
jandershopefully we're past the worst11:55
*** ykatabam has joined #openstack-meeting11:55
jandersI will see where we end up with all this - and if I am still allowed to talk about it at that stage I'm happy to share the story with you guys11:55
oneswigthanks janders, would be a great topic for discussion.11:56
jandersthanks guys!11:56
oneswigOK, shall we wrap up?11:56
jandersI think so11:57
*** brinzhang has quit IRC11:57
jandersthanks for a great chat11:57
jandersplease do wave the RDMA flag at the Ceph meeting!11:57
*** brinzhang has joined #openstack-meeting11:57
oneswigI'll try...11:57
*** openstack changes topic to "OpenStack Meetings ||"11:57
openstackMeeting ended Wed Aug 28 11:57:42 2019 UTC.  Information about MeetBot at . (v 0.1.4)11:57
openstackMinutes (text):
oneswigthanks all11:57
janderssee ya11:57
*** janders has quit IRC12:08
*** rfolco has joined #openstack-meeting12:15
*** jamesmcarthur has joined #openstack-meeting12:22
*** njohnston_ has joined #openstack-meeting12:23
*** ykatabam has quit IRC12:25
*** jamesmcarthur has quit IRC12:29
*** larainema has quit IRC12:30
*** enriquetaso has joined #openstack-meeting12:34
*** brinzhang has quit IRC12:39
*** ttsiouts has joined #openstack-meeting12:43
*** jamesmcarthur has joined #openstack-meeting12:48
*** ricolin has joined #openstack-meeting12:50
*** dkehn has quit IRC12:53
*** ykatabam has joined #openstack-meeting13:01
*** oneswig has quit IRC13:02
*** mriedem has joined #openstack-meeting13:09
*** _pewp_ has quit IRC13:10
*** _pewp_ has joined #openstack-meeting13:11
*** baojg has joined #openstack-meeting13:19
*** ttsiouts has quit IRC13:48
*** ttsiouts has joined #openstack-meeting13:48
*** eharney has joined #openstack-meeting13:50
*** ttsiouts has quit IRC13:53
*** priteau has joined #openstack-meeting13:55
*** liuyulong has joined #openstack-meeting14:00
*** eharney has quit IRC14:00
liuyulong#startmeeting neutron_l314:00
openstackMeeting started Wed Aug 28 14:00:35 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 joined #openstack-meeting14:01
liuyulong_#startmeeting neutron_l314:01
openstackliuyulong_: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.14:01
haleybnested meeting? :)14:01
liuyulong_bad connection....14:01
liuyulong#chair haleyb14:02
openstackCurrent chairs: haleyb liuyulong14:02
liuyulong#chair liuyulong_14:02
openstackCurrent chairs: haleyb liuyulong liuyulong_14:02
liuyulongOK, let's start14:02
liuyulong#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:02
liuyulongI added some topics last night, hope you guys are interested in that.14:03
haleybliuyulong: instead of centralized DNAT scale-out, why not DVR?  but maybe that's a discussion for the ptg14:06
liuyulongThe number of PTG participants seems to be very small.14:06
liuyulonghaleyb, for some deployment, they just do not want all nodes have the public network NICs.14:08
liuyulonghaleyb, a centralized NAT cluster looks easy to manage and maintain.14:09
liuyulongSo please add your name and topic there.14:10
liuyulongLet's move on.14:10
liuyulong#topic Bugs14:10
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:10
liuyulongWe have no bug deputy email this week.14:11
haleybthere was a google doc i believe14:12
liuyulongAugust-19-2019Swaminathan Vasudevan (Swami)14:12
liuyulongAugust-26-2019Akihiro Motoki (amotoki)replaced by lajoskatona for Aug 2614:12
liuyulongSo last week should be Swaminathan, and this week lajoskatona14:13
*** boxiang has joined #openstack-meeting14:14
slaweqliuyulong: can You maybe use some url shortener and give short url here? :)14:14
liuyulongLet's scan the list by "newest first".14:15
haleybthat is the bug report for last week14:15
liuyulongI can not open that link right now...14:15
openstackLaunchpad bug 1841753 in neutron "Pyroute2 netns.ns_pids() will fail if during the function loop, one namespace is deleted" [Undecided,New] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:16
liuyulongralonsoh is working on this14:16
ralonsohI have a patch uploaded14:16
*** zhubx has quit IRC14:17
ralonsohthere is an issue in pyroute214:17
ralonsohso this is a workaround14:17
liuyulongSo the fix is a workaround.14:17
ralonsohthat's why I set related-bug in the comment14:17
ralonsohthis patch is not a fix for neutron14:18
ralonsohthe fix should be in pyroute214:18
ralonsoh(I'll propose a patch this week)14:18
liuyulongMake sense, current approach can help solve the problem, we can merge it soon if it break CI too much.14:19
openstackLaunchpad bug 1841682 in neutron "rootwrap sudo process goes into defunct state" [Undecided,New]14:19
*** tosky has joined #openstack-meeting14:19
ralonsohthat was filled yesterday14:19
liuyulongzombie process right?14:20
ralonsohthis should not be related to the last three patches submitted to neutron-keepalived14:20
ralonsohyes zoombie processes14:20
*** boxiang has quit IRC14:20
ralonsohthis bug is reported for an environment using rocky14:20
*** boxiang has joined #openstack-meeting14:21
ralonsohso I would like to know if this is happening now (I'll check the logs in the functional and fullstack tests)14:21
liuyulongSo I wonder what's the real command after that "[sudo]" ?14:21
ralonsohthat's the point: we can't know14:21
ralonsohthis happens if you spawn a process using "Ip netns"14:22
ralonsohand you kill the process inside the namespace14:22
ralonsohthe kernel process will remain in this state14:22
ralonsohI'll take a look at the current logs in the CI14:23
liuyulongGreat, thank you, may I assign this bug to you?14:23
liuyulongRodolfo Alonso (rodolfo-alonso-hernandez) right?14:24
liuyulongOK, let's move on14:24
*** boxiang has quit IRC14:25
*** boxiang has joined #openstack-meeting14:26
openstackLaunchpad bug 1839004 in neutron "Rocky DVR-SNAT seems missing entries for conntrack marking" [Undecided,Incomplete]14:26
*** markvoelker has quit IRC14:26
liuyulongSomething related to BGP14:27
haleybright, looked like subnet pool issue at first14:28
liuyulongRyan said it is not reproducable.14:28
*** jamesmcarthur has quit IRC14:29
*** jamesmcarthur has joined #openstack-meeting14:29
*** eharney has joined #openstack-meeting14:29
*** markvoelker has joined #openstack-meeting14:29
liuyulongBad connection...14:31
haleybcan probably close then14:31
liuyulongLet's keep an eye on that bug.14:31
*** xubozhang has joined #openstack-meeting14:32
liuyulongMost of other bugs related to L3 are marked as fixed or invalid.14:32
liuyulongSo if you guys have others, go ahead~14:33
openstackLaunchpad bug 1812118 in neutron "Neutron doesn't allow to update router external subnets" [Medium,In progress] - Assigned to Brian Haley (brian-haley)14:34
*** amotoki_ has quit IRC14:34
*** tosky_ has joined #openstack-meeting14:34
*** tosky has quit IRC14:34
haleybwhile i can't seem to get the test to pass, let's discuss the one-line change14:34
*** tosky_ is now known as tosky14:35
*** amotoki has joined #openstack-meeting14:35
haleybbasically the bug is you can't change the external subnet/IP of a router, you have to remove then re-add14:35
haleybbut i think it should be allowed if the network is not changing14:36
*** markvoelker has quit IRC14:37
*** markvoelker has joined #openstack-meeting14:38
liuyulongChange external subnet may have some issues of the public network connection. Any why users need to change the external subnet?14:38
*** Luzi has quit IRC14:40
haleybi didn't see any issues in testing, and it's possible to do, just have to be admin14:40
haleybif i can delete and add to do the same thing, why not update?14:40
haleybit doesn't seem much different than having multiple external subnets, and your router is on one, but floating IPs are on another14:42
haleybit should still work14:42
liuyulongSo the original request is whay this command does not work for normal user? "openstack router set --external-gateway 30e25ece-439b-4d9f-a3f7-816d0167d2cd --fixed-ip subnet=72808793-445e-4fe5-b653-097d720304e8 test"14:42
*** jamesmcarthur has quit IRC14:42
haleybright, because of the missing admin context14:43
liuyulongOK, looks like I was overthinking of this.14:45
haleybit's the darn test that is killing me, if anyone has a thought on that i'd appreciate it, seems simple from a high level14:46
*** jamesmcarthur has joined #openstack-meeting14:49
liuyulongShould call update_router for the test?14:50
liuyulong, you call the "update_port" now.14:50
*** Lucas_Gray has quit IRC14:51
haleybhmm, maybe that's it, i was thinking that test was very similar, i'll take a look, thanks liuyulong14:52
*** lpetrut has quit IRC14:52
haleybor i just remove the test :)14:53
liuyulongTest cases are always needed. : )14:53
slaweqliuyulong: nah, tests are only slowing us down :P14:54
haleybit seemed like fullstack was the right way though14:54
liuyulongOK, let's stop here today.14:55
liuyulongThank you guys for attending.14:56
*** openstack changes topic to "OpenStack Meetings ||"14:56
openstackMeeting ended Wed Aug 28 14:56:30 2019 UTC.  Information about MeetBot at . (v 0.1.4)14:56
openstackMinutes (text):
*** liuyulong has quit IRC14:57
*** liuyulong_ has quit IRC14:57
*** igordc has joined #openstack-meeting14:57
*** links has quit IRC15:01
*** jamesmcarthur has quit IRC15:02
*** xubozhang has quit IRC15:02
*** tidwellr has joined #openstack-meeting15:06
*** jamesmcarthur has joined #openstack-meeting15:13
*** lpetrut has joined #openstack-meeting15:15
*** jungleboyj has joined #openstack-meeting15:17
*** jamesmcarthur has quit IRC15:18
*** markvoelker has quit IRC15:18
*** donnyd has quit IRC15:19
*** donnyd has joined #openstack-meeting15:20
*** donnyd has quit IRC15:20
*** markvoelker has joined #openstack-meeting15:21
*** donnyd has joined #openstack-meeting15:21
*** hemna has joined #openstack-meeting15:22
*** gyee has joined #openstack-meeting15:26
*** niceplace_ has joined #openstack-meeting15:39
*** hemna has quit IRC15:40
*** hemna has joined #openstack-meeting15:41
*** panda is now known as panda|rover15:47
*** zhengMa has joined #openstack-meeting15:49
*** rosmaita has joined #openstack-meeting15:50
*** woojay has joined #openstack-meeting15:51
*** davidsha has joined #openstack-meeting16:00
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Aug 28 16:00:58 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:01
*** openstack changes topic to " (Meeting topic: Cinder)"16:01
openstackThe meeting name has been set to 'cinder'16:01
jungleboyjcourtesy ping:  jungleboyj whoami-rajat rajinir lseki carloss pots woojay erlon geguileo eharney rosmaita enriquetaso e0ne smcginnis davidsha walshh_ xyang hemna _hemna tosky16:01
geguileohi! o/16:01
*** thgcorrea has joined #openstack-meeting16:01
_pewp_jungleboyj ヾ(-_-;)16:01
*** whoami-rajat has joined #openstack-meeting16:01
jungleboyjHappy Wednesday!16:02
jungleboyjHope everyone is well.  Will give people another minute to assemble.16:03
*** tidwellr has quit IRC16:03
jungleboyjOk.  Lets get started.16:03
jungleboyj#topic announcements16:04
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:04
*** ricolin has quit IRC16:04
jungleboyjI have gotten the summary of last week's mid-cycle posted.16:04
*** ricolin has joined #openstack-meeting16:04
jungleboyjIt includes links to videos of the sessions.16:04
eharneythanks for putting that together16:04
rosmaitayeah, nicely done16:05
jungleboyjHad some really good discussion together and appreciate all those that attended remotely.  Even timezones made it challenging.16:05
jungleboyjThank you all.  :-)16:05
jungleboyjPlease look at the Action Items and address those that are assigned to you.16:05
jungleboyjAlso check the list for the HELP NEEDED items.16:05
jungleboyjThose are things that are free to be taken on.16:05
jungleboyjAlso, I think that rosmaita is planning to send out a survey on what we want to do for future mid-cycles.  Please watch for that.16:06
rosmaitawill try to get that out before the weekend16:07
jungleboyjrosmaita:  Thank you.16:07
jungleboyjNot a huge hurry, but obviously the earlier we start, the better.16:07
jungleboyjThat was all I had for announcements.16:07
jungleboyj#topic releases update16:07
*** openstack changes topic to "releases update (Meeting topic: Cinder)"16:07
jungleboyjrosmaita:  All your's.16:08
*** tesseract has quit IRC16:08
rosmaitaok, the Train release of os-brick has to happen next week16:08
rosmaitabunch of recent stuff that looks ok, some older items with no reviews, and some older items with problems16:08
whoami-rajatjungleboyj: may i have the etherpad link ?16:08
rosmaitawould probably be a good idea to use the Review Priority to put +2RP on stuff we absolutely want to get in16:08
whoami-rajatjungleboyj: thanks16:09
jungleboyjrosmaita:  ++16:09
eharneyi set +RP on the cryptsetup deprecation, should really get that in for this cycle16:09
rosmaitaok, great16:09
rosmaitabtw, cinderlib is on a different release schedule, so Train release doesn't have to happen until after the cinder Train release16:09
jungleboyjGood.  Thank you for verifying that.16:09
rosmaitathe Train release of python-cinderclient has to happen the week after (week of Sept 9)16:10
rosmaitathis is going to include bumping the client from 4.3.0->5.0.016:10
rosmaitaso we certainly need to get all the version change stuff merged (for example, v1 support removal)16:10
whoami-rajatI think the pdf generator is also a goal for train, not much important but good to get in.16:10
rosmaitaright, i think hemna said he has that working for the client16:11
*** bobh has joined #openstack-meeting16:11
jungleboyjrosmaita:  He did.16:11
rosmaitaso basically, we need all cores to pay attention to brick and the client over the next 2 weeks16:11
jungleboyjrosmaita:  ++16:11
rosmaitathat's all from me16:11
*** ricolin has quit IRC16:12
jungleboyjrosmaita:  Cool.  Thank you!16:12
jungleboyjAppreciate you continuing to watch the releases.16:12
jungleboyj#topic Replication.16:13
*** openstack changes topic to "Replication. (Meeting topic: Cinder)"16:13
jungleboyjThis was an item of discussion from the mid-cycle.16:13
jungleboyjIs anyone really making use of this?16:13
jungleboyjHave customers used it?16:13
jungleboyjReaching out to the vendors here to see what you all know?16:13
* jungleboyj hopes everyone is typing busily but guessing that isn't the case.16:14
jungleboyjHas anyone even tested the functionality recently?16:15
eharneya good amount of work went into getting it working with Ceph not too long ago16:15
smcginnisMight be good to post this to -discuss and -ops too.16:15
*** bobh has quit IRC16:15
jungleboyjeharney:  ++ That is good.  So we have some confidence that it at lest works for one driver.  :-)16:15
jungleboyjsmcginnis:  Yeah, thinking that might be the next step.16:16
*** bobh has joined #openstack-meeting16:16
smcginnisI've seen some vendors interested in making sure it is working, but I have not actually heard of any end users using it.16:16
jungleboyjsmcginnis:  Yeah, that was what I was afraid of.16:17
jungleboyjOk.  So I am guessing there is no more discussion to have right now then.16:18
jungleboyjI can send an e-mail to -discuss and -ops to see if we get a response there.16:18
smcginnisMight get more of a response than you've gotten here. :D16:18
jungleboyjOne can hope.16:19
jungleboyjOk.  That was all that I had for topics today then.16:19
jungleboyj#topic Open Discussion16:20
*** openstack changes topic to "Open Discussion (Meeting topic: Cinder)"16:20
jungleboyjAnyone have anything else to discuss today?16:20
enriquetasohey, I'm still looking for reviews in the bACKUP Incremental patch16:20
*** bobh has quit IRC16:20
enriquetasoI've fixed all the comments16:21
whoami-rajatSo as per geguileo 's review, my patch is ready to merge in cinderlib [1] but hasn't received any functionality reviews on the main cinder patch[2]16:21
jungleboyjOk.  I can look at that again.16:21
eharneythe rbd incr patch seemed like it was about there last time i looked at it, can take another look16:21
enriquetasothanks eharney16:21
jungleboyjeharney:  Good.  Want to get that in but definitely want you and geguileo to weigh in.16:22
geguileojungleboyj: I'll try to get another grumpy look at the patch16:23
jungleboyjgeguileo:  Don't be grumpy, be happy.  :-)16:23
jungleboyjSo, can take a look at the requested reviews.  Any other topics?16:25
zhengMaHi team, we have solved the 'merge' problem, I think our patch is ready for reviewing.
jungleboyjOk.  Taking silence as a no.16:26
*** brault has quit IRC16:27
jungleboyjOn that note it appears we could all use 30 minutes to go do code reviews.16:27
jungleboyj:-)  Ok.  Go forth and review.16:28
jungleboyjThanks all for attending.16:28
*** openstack changes topic to "OpenStack Meetings ||"16:28
openstackMeeting ended Wed Aug 28 16:28:38 2019 UTC.  Information about MeetBot at . (v 0.1.4)16:28
openstackMinutes (text):
*** zhengMa has quit IRC16:29
*** tosky has left #openstack-meeting16:30
*** davidsha has quit IRC16:32
*** macz has joined #openstack-meeting16:33
*** woojay has left #openstack-meeting16:35
*** mriedem is now known as mriedem_away16:49
*** ekcs has joined #openstack-meeting16:54
*** artom has quit IRC16:56
*** jamesmcarthur has joined #openstack-meeting17:00
*** zhengMa has joined #openstack-meeting17:13
*** ijw has joined #openstack-meeting17:14
*** ijw has quit IRC17:16
*** ijw has joined #openstack-meeting17:16
*** ijw has quit IRC17:17
*** ijw has joined #openstack-meeting17:18
*** zhengMa has quit IRC17:18
*** mlavalle has joined #openstack-meeting17:19
*** panda|rover is now known as panda|rover|off17:23
*** brault has joined #openstack-meeting17:30
*** brault has quit IRC17:34
*** eharney_ has joined #openstack-meeting17:43
*** njohnston_ has left #openstack-meeting17:43
*** eharney has quit IRC17:44
*** brault has joined #openstack-meeting17:44
*** brault has quit IRC17:45
*** eharney_ is now known as eharney17:46
*** mlavalle has left #openstack-meeting17:52
*** mmethot has quit IRC17:58
*** zbitter has joined #openstack-meeting17:58
*** mmethot has joined #openstack-meeting17:58
*** zaneb has quit IRC17:58
*** priteau has quit IRC18:12
*** ociuhandu has joined #openstack-meeting18:12
*** psachin has quit IRC18:13
*** mriedem_away is now known as mriedem18:21
*** enriquetaso has quit IRC18:22
*** igordc has quit IRC18:23
*** enriquetaso has joined #openstack-meeting18:28
*** thgcorrea has quit IRC18:41
*** jamesmcarthur has quit IRC18:43
*** bbowen has quit IRC18:51
*** lpetrut has quit IRC19:02
*** ociuhandu has quit IRC19:14
*** nicolasbock has quit IRC19:34
*** eharney has quit IRC19:36
fungino storyboard meeting this week (obviously), find us in #storyboard if you have something you wanted to bring up19:37
*** rosmaita has left #openstack-meeting19:37
*** ralonsoh has quit IRC19:42
*** gyee has quit IRC20:05
*** slaweq has quit IRC20:09
*** zhubx has joined #openstack-meeting20:20
*** gyee has joined #openstack-meeting20:23
*** boxiang has quit IRC20:24
*** brault has joined #openstack-meeting20:32
*** brault has quit IRC20:37
*** jamesmcarthur has joined #openstack-meeting20:44
*** enriquetaso has quit IRC20:51
*** bbowen has joined #openstack-meeting20:53
*** eharney has joined #openstack-meeting20:55
*** markvoelker has quit IRC20:58
*** markvoelker has joined #openstack-meeting20:58
*** belmoreira has joined #openstack-meeting20:59
*** jamesmcarthur has quit IRC20:59
timburke#startmeeting swift21:00
openstackMeeting started Wed Aug 28 21:00:17 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
*** patchbot has joined #openstack-meeting21:00
timburkewho's here for the swift meeting?21:00
rledisezhi o/21:00
* notmyname lurks21:01
* timburke will have to avoid bad-mouthing the previous PTL now21:02
*** alecuyer has joined #openstack-meeting21:02
timburkeall right, let's get started. agenda's at21:03
*** zaitcev_ has joined #openstack-meeting21:03
timburkefirst, a couple house-keeping items21:03
timburke#topic elections21:03
*** openstack changes topic to "elections (Meeting topic: swift)"21:03
timburkeit's election season!21:03
timburkefwiw, it looks like 4 of the current TC members will not be seeking re-election21:03
timburke(that's out of 6 seats up for election this cycle)21:03 if you've ever wanted to be on the comittee, your odds might be improved this cycle ;-)21:03
timburkeas for swift, i'd be happy and honored to continue serving as PTL21:04
timburkei feel like there's still room for me to grow in this role :-)21:04
timburkethough if anyone would like to serve instead (or otherwise has misgivings), feel free to speak up. now or later; here, in -swift, or in private21:04
kota_that's great news!21:04
timburkei serve at y'all's pleasure ;-)21:04
timburkekota_, oh i'm glad :-) i remember you and mattoliverau talking about maybe wanting to run -- and i really would hate to get in the way of that21:05
kota_my point is if no one else wants to run. so I'm happy with you continue to run the PTL.21:06
timburkeany questions/comments/concerns? on either part of the elections21:06
mattoliverautimburke: thanks, your doing a great job. notmyname has large shoes to fill, but your doing good. Keep it up!21:07
tdasilvatimburke: you are doing a great job, thanks for your efforts in leading the project!21:07
timburkei'll work on writing up my candidacy email and plan on sending it out tonight or tomorrow21:07
notmynametimburke: you're doing a great job :-)21:07
timburkenotmyname, oh how would *you* know, lurker!? :P21:08
timburke#topic shrinking the TC21:08
*** openstack changes topic to "shrinking the TC (Meeting topic: swift)"21:08
timburkemostly just a heads-up, keeping people in the loop if you haven't been keeping up on the mailing list21:08
timburkeapparently the TC is going to shrink over the next year and a half or so from 13 members to 11 or 921:08
timburke(details still being ironed out)21:08
timburkei don't think it'll really have much direct impact on us, just an fyi21:08
timburkeon to updates!21:09
notmynamethat's interesting21:09
timburkegood news is, if we have to argue about golang for losf, we'll have fewer people we have to convince, right? ;-)21:10
timburke#topic py321:10
*** openstack changes topic to "py3 (Meeting topic: swift)"21:10
*** markvoelker has quit IRC21:10
timburkeall func tests have merged! probe tests are mostly ported and have one +2 already!21:10
*** markvoelker has joined #openstack-meeting21:10
patchbotpatch 671333 - swift - py3: (mostly) port probe tests - 3 patch sets21:10
alecuyerwow :)21:11
timburkei still need to work on getting a gate job going for it21:11
timburkeit's been a long journey, thank you all for helping21:11
timburkei was looking back at what we had under test when, and wanted to share a little21:11
*** slaweq has joined #openstack-meeting21:11
timburkeour first openstack release with at least one test module getting exercised was mitaka, just testing exceptions21:11
timburkeby ocata, we'd gotten up to 4 modules... but then we stalled out and were still there for queens21:11
timburkerocky, we were up to 3021:11
timburkethen 90 in stein21:11
timburkenow we're at all 128! that seems amazingly fast for the size and scope of the work21:11
timburkecongrats everybody, and again, thank you all21:12
timburke(particularly zaitcev_ and mattoliverau :-)21:12
mattoliverauEspecially timburke and zaitcev_, I rode on their coat tails :)21:13
timburkeheh. now we just need to test it enough to really feel comfortable with it21:13
timburke#topic versioning21:14
*** openstack changes topic to "versioning (Meeting topic: swift)"21:14
timburkeclayg, how's it going?21:14
timburkeok, so that may have been rhetorical so i didn't feel like i was talking too much21:15
*** zaitcev_ has quit IRC21:16
timburkewe've got concerns about symlink versioning actually doing all the things we want it to do21:16
patchbotpatch 633857 - swift - symlink-backed versioned_writes - 19 patch sets21:16
*** slaweq has quit IRC21:16
*** zaitcev has joined #openstack-meeting21:16
*** belmoreira has quit IRC21:16
timburkeremember, in particular we want to get to the point that we can pretty faithfully mimic S3's notion of versioning21:17
timburkeso i started playing around with adding *another* mode, like history mode but with a naming convention for the versions that would be more useful there21:17
patchbotpatch 678962 - swift - WIP: Add another versioning mode with a new naming... - 1 patch set21:17
timburkeit needs lots of tests and i ought to start actually trying to wire in the s3api changes to see how well it works21:18
timburke...but i think it might work? biggest downside is that there isn't a good way to transition from using x-versions-location *or* x-history-location to the new mode :-(21:19
*** artom has joined #openstack-meeting21:20
mattoliveraumoar symlinking!21:20
timburkeif anybody has thoughts on versioning and/or s3api, it might be worth taking a look21:20
claygtimburke: sorry, i'm back21:21
timburkemattoliverau, yeah, i was about to say "(or really, *any* way)" but then i remembered that i'd thought about symlinking the new-style to the existing old name :-)21:21
*** ircuser-1 has quit IRC21:22
claygtimburke: if we're going this route can we make the third mode always use symlinks?21:22
claygi'm excited about the new ?versions=v params21:22
*** zaitcev has quit IRC21:23
claygI'd love to see if we could get that work with a copy/restore21:23
timburkeclayg, probably? it'll still need to be able to splice the listings though -- in case you turned it off then back on21:23
notmynameclayg: what's the status of your investigation? learned enough to compare to timburke's 3rd mode?21:23
*** zaitcev_ has joined #openstack-meeting21:23
timburkei *think* it'll mostly Just Work with COPY?21:23
timburkeoh yeah, and to fill out the context some more...21:24
patchbotpatch 673682 - swift - s3api: Implement versioning status API - 2 patch sets21:24
*** zaitcev_ has quit IRC21:24
timburkeclayg, anything else i'd forgotten to mention?21:24
*** belmoreira has joined #openstack-meeting21:25
claygnotmyname: well, I think the symlink-versioned writes code is going to port over pretty well - there's some differences because s3request objects aren't exactly the same as plain swob requests but mostly I can fork lift just the bits I need21:25
*** zaitcev has joined #openstack-meeting21:25
claygthe diff is going to be much different - instead of versioned_writes accrete a bunch of new conditional branches based on which mode you're using there's just going to be some new code paths that do symlink writes and other version'd operations in s3api mode21:26
claygit'll be using it's own sysmeta so it's compleatly orthogonal to versioned_writes21:26
claygit'll be interesting to see what looks like the best path forward in the short term - or long term depending on the bits we do/don't like21:27
timburkecompletely orthogonal -- so it won't be respected for bimodal access, yeah?21:28
clayginstead of reviewing a change to versoined writes and a new s3api feature for translation - it'll just be a change to s3api21:28
claygtimburke: exactly - it's a s3api feature only available through the s3api - at least that's the experiment i'm running - i'm not advocating for anything other than we should take the time to understand what an implementation like that would look like21:29
timburkegood to go into these things with our eyes as open as we can have them :-)21:29
claygtimburke: but related to that I would like to pull back on the forced use_symlinks migration for existing versioned writes containers21:30
timburkei'm torn -- that race condition is the commit message is still very much a thing :-/21:31
claygand it has been for a long time21:31
timburke*in the commit message21:31
timburketrue enough21:31
timburkeanyone else have questions, comments, or other feedback?21:33
timburke#topic lots of small files21:35
*** openstack changes topic to "lots of small files (Meeting topic: swift)"21:35
timburkealecuyer, i saw the RPC-ove-HTTP patch go by21:35
patchbotpatch 679022 - swift (feature/losf) - WIP - Support RPC over plain HTTP (vs gRPC) - 1 patch set21:35
alecuyerit removes the grpc dependency,21:35
alecuyeror almost : python still wants to find grpc to compile the protobuf definitions, I have to figure that one out21:36
alecuyerand I need to fix tests related to that change.21:36
timburkei was just noticing the "ImportError: cannot import name rpc_grpc" in logs :-)21:37
alecuyerso I pushed that a little quick today so you could have a look, but its not finished :) It should not take too long though to clean it up and fix the tests21:37
timburkenice! anything else we should be looking at for losf?21:38
alecuyer(cherry picked it from our branch which is still a little different from master)21:38
alecuyerwell it's great to have your tests feedback21:38
alecuyerthat's it for me for this week21:39
*** markvoelker has quit IRC21:39
*** markvoelker has joined #openstack-meeting21:40
timburke#topic sharding21:40
*** openstack changes topic to "sharding (Meeting topic: swift)"21:40
timburkemattoliverau, how's it going?21:41
timburkei know there was a bit of back-and-forth on
patchbotpatch 675820 - swift - sharder: Keep cleaving on empty shard ranges - 2 patch sets21:41
mattoliverauI've marked it as WIP as I have a go at reworking the cleave code21:42
mattoliverauclayg and timburke made some good points about code flow and we should avoid using exception handling to do so. Esp in py3. It was a way to not touch too much of the cleaving code.21:44
mattoliverauBut will have a play and rework cleaving to better fit skipping empty shards ranges in.21:44
*** markvoelker has quit IRC21:45
timburkethanks -- and i didn't mean to be discouraging -- i know i prefer not to fiddle too much with working code, too ;-)21:45
mattoliverauyeah and cleaving is already a little.. interesting. But to do it properly is the right way forward :)21:46
timburke#topic open discussion21:47
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:47
timburkeanybody have anything else to bring up?21:47
zaitcevI was disconnecting too much and missed any replies if you testd py2-py3 migrations.21:49
timburkezaitcev, no, not yet :-(21:49
timburkefwiw, i re-organized the priority reviews page a bit to better capture some of the work in flight. sorry for hogging it for py3 stuff so much lately21:50
*** eharney has quit IRC21:50
timburkeas always, if there's anything else you'd like to see on there, feel free to add it21:51
*** jbadiapa has quit IRC21:52
timburkeall right, i'm calling it21:53
timburkethank you all for coming, and thank you for working on swift!21:53
*** openstack changes topic to "OpenStack Meetings ||"21:53
openstackMeeting ended Wed Aug 28 21:53:18 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:53
openstackMinutes (text):
*** alecuyer has left #openstack-meeting21:54
*** mriedem has quit IRC21:54
*** zaitcev has left #openstack-meeting21:55
*** eharney has joined #openstack-meeting21:55
*** markvoelker has joined #openstack-meeting22:05
*** dviroel has quit IRC22:10
*** markvoelker has quit IRC22:11
*** slaweq has joined #openstack-meeting22:11
*** belmoreira has quit IRC22:11
*** enriquetaso has joined #openstack-meeting22:14
*** ircuser-1 has joined #openstack-meeting22:15
*** slaweq has quit IRC22:17
*** carloss has quit IRC22:29
*** patchbot has quit IRC22:38
*** notmyname has quit IRC22:38
*** notmyname has joined #openstack-meeting22:48
*** macz has quit IRC22:57
*** slaweq has joined #openstack-meeting23:11
*** slaweq has quit IRC23:15
*** rcernin has joined #openstack-meeting23:21
*** ykatabam has joined #openstack-meeting23:21
*** ykatabam has quit IRC23:26
*** rfolco has quit IRC23:29
*** ykatabam has joined #openstack-meeting23:37
*** tetsuro has joined #openstack-meeting23:44
*** Swami has joined #openstack-meeting23:44
*** Swami has quit IRC23:45
*** lseki has quit IRC23:48

Generated by 2.15.3 by Marius Gedminas - find it at!