Wednesday, 2019-01-09

*** jamesmcarthur has joined #openstack-meeting00:02
*** jamesmcarthur has quit IRC00:06
*** rcernin has quit IRC00:07
*** martial__ has quit IRC00:07
*** rcernin has joined #openstack-meeting00:09
*** yamamoto has joined #openstack-meeting00:09
*** armax has joined #openstack-meeting00:15
*** M0nk3Ee has quit IRC00:16
*** slaweq has quit IRC00:18
*** yamamoto has quit IRC00:19
*** artom has joined #openstack-meeting00:23
*** artom has quit IRC00:23
*** macza has quit IRC00:28
*** slaweq has joined #openstack-meeting00:35
*** liuyulong has quit IRC00:39
*** yamamoto has joined #openstack-meeting00:41
*** yamamoto has quit IRC00:45
*** Swami has quit IRC00:46
*** armax has quit IRC00:46
*** slaweq has quit IRC00:47
*** tetsuro has joined #openstack-meeting00:53
*** Liang__ has joined #openstack-meeting00:55
*** armax has joined #openstack-meeting00:56
*** Liang__ has quit IRC00:56
*** Liang__ has joined #openstack-meeting00:56
*** iyamahat_ has quit IRC01:09
*** armax has quit IRC01:09
*** jesusaur has joined #openstack-meeting01:12
*** erlon has joined #openstack-meeting01:15
*** slaweq has joined #openstack-meeting01:18
*** erlon has quit IRC01:22
*** slaweq has quit IRC01:23
*** baojg has quit IRC01:24
*** tetsuro has quit IRC01:41
*** hongbin_ has joined #openstack-meeting01:48
*** macza has joined #openstack-meeting01:53
*** macza has quit IRC01:57
*** bobh has joined #openstack-meeting02:41
*** bobh has quit IRC02:47
*** psachin has joined #openstack-meeting02:48
*** whoami-rajat has joined #openstack-meeting02:52
*** mhen has quit IRC02:58
*** mhen has joined #openstack-meeting02:59
*** factor has quit IRC03:04
*** gyee has quit IRC03:10
*** markvoelker has joined #openstack-meeting03:11
*** markvoelker has quit IRC03:12
*** apetrich has quit IRC03:16
*** anteaya has quit IRC03:24
*** janki has joined #openstack-meeting03:45
*** yamamoto has joined #openstack-meeting03:52
*** yamamoto has quit IRC03:54
*** yamamoto has joined #openstack-meeting03:55
*** diablo_rojo has quit IRC04:00
*** imsurit has joined #openstack-meeting04:02
*** yamamoto has quit IRC04:04
*** yamamoto has joined #openstack-meeting04:05
*** vishalmanchanda has joined #openstack-meeting04:11
*** yamamoto has quit IRC04:12
*** macza has joined #openstack-meeting04:16
*** hongbin_ has quit IRC04:24
*** sridharg has joined #openstack-meeting04:27
*** markvoelker has joined #openstack-meeting04:37
*** markvoelker has quit IRC04:42
*** wwriverrat has joined #openstack-meeting04:52
*** phuoc__ has joined #openstack-meeting04:52
*** arne_wiebalck_ has joined #openstack-meeting04:53
*** dtrainor_ has joined #openstack-meeting04:53
*** rf0lc0 has joined #openstack-meeting04:53
*** lifeless_ has joined #openstack-meeting04:57
*** jbadiapa has joined #openstack-meeting04:57
*** sridharg has quit IRC05:02
*** psachin has quit IRC05:02
*** jesusaur has quit IRC05:02
*** rfolco has quit IRC05:02
*** dtrainor has quit IRC05:02
*** irclogbot_1 has quit IRC05:02
*** phuoc_ has quit IRC05:02
*** arne_wiebalck has quit IRC05:02
*** chason has quit IRC05:02
*** lifeless has quit IRC05:02
*** arne_wiebalck_ is now known as arne_wiebalck05:02
*** irclogbot_1 has joined #openstack-meeting05:06
*** sridharg has joined #openstack-meeting05:08
*** jesusaur has joined #openstack-meeting05:09
*** armax has joined #openstack-meeting05:27
*** imsurit has quit IRC05:31
*** imsurit has joined #openstack-meeting05:39
*** markvoelker has joined #openstack-meeting06:04
*** radeks has joined #openstack-meeting06:05
*** e0ne has joined #openstack-meeting06:22
*** e0ne has quit IRC06:23
*** macza has quit IRC06:28
*** Luzi has joined #openstack-meeting06:56
*** jrbalderrama has joined #openstack-meeting07:04
*** pcaruana has joined #openstack-meeting07:06
*** e0ne has joined #openstack-meeting07:18
*** e0ne has quit IRC07:22
*** rcernin has quit IRC07:26
*** factor has joined #openstack-meeting07:27
*** imsurit has quit IRC07:31
*** bobh has joined #openstack-meeting07:39
*** bobh has quit IRC07:43
*** e0ne has joined #openstack-meeting07:47
*** armax has quit IRC07:49
*** lpetrut has joined #openstack-meeting07:55
*** yikun has quit IRC07:55
*** slaweq has joined #openstack-meeting08:12
*** jrbalderrama has quit IRC08:21
*** hongbin has quit IRC08:23
*** ralonsoh has joined #openstack-meeting08:25
*** imsurit has joined #openstack-meeting08:26
*** apetrich has joined #openstack-meeting08:38
*** Yingxin has joined #openstack-meeting08:38
*** e0ne has quit IRC08:47
*** yamamoto has joined #openstack-meeting08:56
*** yamamoto has quit IRC08:57
*** imsurit has quit IRC09:20
*** bobh has joined #openstack-meeting09:25
*** Liang__ has quit IRC09:25
*** yamamoto has joined #openstack-meeting09:27
*** yamamoto_ has joined #openstack-meeting09:27
*** yamamoto has quit IRC09:31
*** M0nk3Ee has joined #openstack-meeting09:32
*** markvoelker has quit IRC09:33
*** yamamoto_ has quit IRC09:33
*** carlos_silva has joined #openstack-meeting09:46
*** kopecmartin|off is now known as kopecmartin09:56
*** bobh has quit IRC10:19
*** e0ne has joined #openstack-meeting10:21
*** electrofelix has joined #openstack-meeting10:58
*** jamesmcarthur has joined #openstack-meeting11:17
*** jamesmcarthur has quit IRC11:21
*** yamamoto has joined #openstack-meeting11:22
*** yamamoto has quit IRC11:23
*** yamamoto has joined #openstack-meeting11:23
*** erlon has joined #openstack-meeting11:34
*** rtjure has quit IRC11:40
*** erlon has quit IRC11:40
*** davidsha has joined #openstack-meeting11:57
*** rtjure has joined #openstack-meeting12:00
*** erlon has joined #openstack-meeting12:10
*** bobh has joined #openstack-meeting12:18
*** bobh has quit IRC12:24
*** yamamoto_ has joined #openstack-meeting12:29
*** e0ne has quit IRC12:30
*** yamamoto has quit IRC12:33
*** erlon has quit IRC12:37
*** raildo has joined #openstack-meeting12:48
*** rf0lc0 is now known as rfolco12:49
*** erlon has joined #openstack-meeting12:52
*** yamamoto_ has quit IRC12:54
*** yamamoto has joined #openstack-meeting12:55
*** yamamoto has quit IRC12:57
*** erlon has quit IRC13:09
*** sridharg has quit IRC13:20
*** e0ne has joined #openstack-meeting13:24
*** erlon has joined #openstack-meeting13:25
*** yamamoto has joined #openstack-meeting13:28
*** jamesmcarthur has joined #openstack-meeting13:50
*** vishalmanchanda has quit IRC13:51
*** whoami-rajat has quit IRC13:52
*** yamamoto has quit IRC13:54
*** qwebirc35204 has joined #openstack-meeting14:02
*** qwebirc35204 has quit IRC14:02
*** munimeha1 has joined #openstack-meeting14:13
*** vishalmanchanda has joined #openstack-meeting14:15
*** mpwiwoarczy has joined #openstack-meeting14:15
*** jamesmcarthur has quit IRC14:26
*** janki has quit IRC14:26
*** janki has joined #openstack-meeting14:27
*** jamesmcarthur has joined #openstack-meeting14:27
*** yamamoto has joined #openstack-meeting14:27
*** whoami-rajat has joined #openstack-meeting14:31
*** yamamoto has quit IRC14:33
*** janki has quit IRC14:47
*** janki has joined #openstack-meeting14:47
*** janki has quit IRC14:51
*** martinkennelly has joined #openstack-meeting14:52
*** janki has joined #openstack-meeting14:52
*** janki has quit IRC14:53
*** factor has quit IRC14:57
*** mpwiwoarczy has quit IRC14:59
*** luizbag has joined #openstack-meeting15:02
*** awaugama has joined #openstack-meeting15:03
*** yamamoto has joined #openstack-meeting15:03
*** yamamoto has quit IRC15:08
*** chason_ has joined #openstack-meeting15:09
*** ssbarnea has quit IRC15:10
*** mjturek has joined #openstack-meeting15:10
*** ssbarnea|rover has joined #openstack-meeting15:10
*** Luzi has quit IRC15:19
*** hongbin has joined #openstack-meeting15:22
*** yamamoto has joined #openstack-meeting15:36
*** lpetrut has quit IRC15:37
*** wwriverrat has quit IRC15:38
*** yikun has joined #openstack-meeting15:39
*** armax has joined #openstack-meeting15:41
*** yamamoto has quit IRC15:42
*** woojay has joined #openstack-meeting15:44
*** walshh_ has joined #openstack-meeting15:56
*** Liang__ has joined #openstack-meeting15:58
*** Liang__ is now known as LiangFang15:58
*** enriquetaso has joined #openstack-meeting15:59
*** lixiaoy1 has joined #openstack-meeting16:00
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Jan  9 16:00:42 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
enriquetasohello o/16:01
jungleboyjcourtesy ping jungleboyj diablo_rojo, diablo_rojo_phon, rajinir tbarron xyang xyang1 e0ne gouthamr thingee erlon tpsilva ganso patrickeast tommylikehu eharney geguileo smcginnis lhx_ lhx__ aspiers jgriffith moshele hwalsh felipemonteiro lpetrut lseki _alastor_ whoami-rajat yikun rosmaita enriquetaso16:01
*** jmlowe has left #openstack-meeting16:01
jungleboyjHello everyone.16:01
jungleboyjHappy New Year!16:02
LiangFanghappy new year~16:02
*** asbishop has joined #openstack-meeting16:02
enriquetasoHappy New year!16:02
whoami-rajatHappy new year everyone :)16:02
*** lseki has joined #openstack-meeting16:02
*** ganso has joined #openstack-meeting16:03
*** hongbin has quit IRC16:03
jungleboyjLooks like we have a good crowd, so lets get started.16:03
*** pcaruana has quit IRC16:03
jungleboyj#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:03
smcginnisAnyone else having trouble loading the etherpad?16:04
*** mszwed_ has joined #openstack-meeting16:04
jungleboyjsmcginnis:  It is working ok for me.16:04
e0nesmcginnis: it works good for me16:04
smcginnisOK, must be a local issue then.16:04
yikunit works ok for me16:04
mszwed_Hello everybody16:04
martinkennellyFine for me16:04
enriquetasofine for me16:04
jungleboyjsmcginnis:  You aren't trying to use the old one are you?16:04
smcginnisNope. Looks like my browser needed a kick in the head. Working now.16:05
jungleboyjOk.  Good.16:06
*** tkauthar has joined #openstack-meeting16:06
jungleboyjSo, Milestone 2 is this week.  smcginnis  and I have been working on getting drivers merged that are ready and on getting specs approved.16:06
jungleboyjAny help that others can give to get reviews though is appreciated.16:07
jungleboyjI don't think the backlog is too bad, but we definitely have a number to get through.16:07
mszwed_jungleboyj: regarding your question on gerrit about CI for SPDK: it is up and running. It should leave a result any time now.16:07
jungleboyjmszwed_:  Great.  Will watch for that.16:08
*** thgcorrea has joined #openstack-meeting16:08
erlonjungleboyj, do you have that review priority etherpad?16:08
jungleboyjI don't think I have more to say there.  Have a couple of specs to mention later in the agenda.16:09
e0neerlon: hi is it.
erlonjungleboyj, e0ne, thanks16:09
jungleboyjAlso, for those of you working on developing code that goes along with items in that etherpad, please add links as I go through it on occasion.16:10
*** yamamoto has joined #openstack-meeting16:10
jungleboyjI have also been using the new Priorities dashboard a lot.16:10
jungleboyjPlease remember to set priorities where appropriate.16:11
erlonyeap, lot of the topics does not have the links16:11
jungleboyjerlon:  Yeah, and I haven't had a chance to find all those.  So, crowd sourcing would be appreciated there.16:11
jungleboyjIt will help get your code reviewed.16:11
jungleboyjAlso wanted to share that I have proposed the 2.7.0 release of os-brick16:12
jungleboyjThis includes the new RSD connector.16:12
Yingxinjungleboyj: there's another fix in the os-brick now..16:13
davidshajungleboyj, there is a follow patch for that:
Yingxinjungleboyj: switched to a newer release of RSD backend and find a issue there16:13
jungleboyjOk.  I will take a look at that and then try to get a bug-fix release out.16:13
Yingxinjungleboyj: thanks!16:14
jungleboyjFinally, I have proposed two new core members on the mailing list.16:14
*** yamamoto has quit IRC16:14
jungleboyjWaiting to see if anyone has objections to Yingxin and whoami-rajat joining the core team.16:15
whoami-rajatyikun ?  ^16:15
jungleboyjThank you for the work you guys have done in the last couple of months to support Cinder16:15
jungleboyjOoops, autocomplete fail yikun16:15
yikunha, :)16:15
jungleboyjwhoami-rajat:  You are correct.16:15
jungleboyjyikun: Sorry about that.16:16
yikunjungleboyj: don't mind, haha :)16:16
jungleboyjThat was almost as bad as forgetting to invite my directory to our scrums.16:16
jungleboyjOk, I give up.16:17
jungleboyjSo, other core team members, please see that e-mail.  If I don't hear any dissent I will add whoami-rajat and yikun in a week.16:17
whoami-rajatjungleboyj:  Thanks Jay for proposing. :)16:17
jungleboyjwhoami-rajat: My pleasure and thanks to smcginnis for his input.16:18
*** gyee has joined #openstack-meeting16:18
jungleboyjOk.  Moving on to the agenda.16:18
yikunthanks, :)16:19
jungleboyj#topic mid-cycle planning update16:19
*** openstack changes topic to "mid-cycle planning update (Meeting topic: Cinder)"16:19
jungleboyjyikun:  You are welcome!  Thanks for joining us!16:19
jungleboyjSo, Lenovo is confirmed as the host.16:19
* e0ne will join mid-cycle via hangout this time :(16:20
jungleboyjI have rooms reserved on site and am working on getting snacks and drinks set up.16:20
jungleboyje0ne:  Glad if you can do it remotely at least.16:20
jungleboyjsmcginnis:  And I worked on getting the agenda set up in the etherpad.16:21
e0nejungleboyj: I'll do my best to not sleep during the mid-cycle :). different timezones could affect a bit my participation16:21
jungleboyjPlease continue to add topics in there.16:21
smcginnise0ne: :)16:21
jungleboyje0ne:  Understood.  For topics that need your participation or geguileo 's we should try to schedule them earlier in the day.16:21
e0nejungleboyj: thanks!16:22
jungleboyjFor people who are able to attend in RTP please make sure to update the etherpad so I know how many people to plan for.16:23
jungleboyjAlso, if you want to stay at the same hotel as smcginnis and I ... I sent the details in this e-mail:
jungleboyjsmcginnis:  You are planning to stay there as well.  Right?16:23
smcginnisYep, haven't booked yet, but that's my plan.16:24
fungiit's tempting to stop in (only 4 hours from home) but i'm travelling two weeks solid leading up to that :(16:24
*** artom has joined #openstack-meeting16:24
smcginnisWould be great to see you if circumstances caused you to be in the area fungi!16:24
jungleboyjfungi:  If you can make it, we would love to have you.  Might be dinner in it for you.  :-)16:25
*** armax has quit IRC16:25
jungleboyjUnderstand if it is too much traveling though.16:25
fungiyep, still trying to work out how to mention it to christine without her threatening me with bodily harm ;)16:25
jungleboyj:-)  I know that feeling.16:26
*** diablo_rojo has joined #openstack-meeting16:26
jungleboyjSo, that is all I have there.  The week is approaching quickly so get your topics in and please join us if you can!16:26
jungleboyj#topic Denver PTG Planning update16:26
*** openstack changes topic to "Denver PTG Planning update (Meeting topic: Cinder)"16:26
jungleboyjThe Foundation sent out a request for how many teams wanted to do the PTG.16:27
jungleboyjI responded that Cinder wanted a room.  Said we were ok with 2 to 3 days of time.16:27
jungleboyjWe always have enough people there to have some sort of meeting so didn't feel we needed to wait to poll everyone.16:28
jungleboyjSo, please plan to attend if you are able to do so.16:28
jungleboyjAny questions/concerns there?16:29
e0neI didn't get an approval yet, but I'm going to be there16:29
smcginnisIn case anyone hasn't seen, Summit is Mon-Wed, PTG is Thurs-Sat.16:29
jungleboyje0ne:  Good!16:29
jungleboyjsmcginnis:  Thanks.  :-)16:29
jungleboyjAfter the mid-cycle we can start building the PTG topic list.16:30
e0neI hope, there be a good weather in May in Denver. I did great hiking last PTG16:30
mszwed_smcginnis: remind me please exact dates16:30
jungleboyj4/29 to 5/116:31
jungleboyjFor the summit.16:31
jungleboyjPTG is 5/2 to 5/416:32
e0neMay 2-4 for PTG16:32
smcginnisThere will still be a Forum during the Summit. I'm not sure how things will sort out between that and the PTG, but there is still some value for developers to be there for the first half of the week.16:32
smcginnisBut going to be a long week.16:32
jungleboyjsmcginnis:  Yes it is.16:32
*** jamesmcarthur has quit IRC16:33
jungleboyjSo, Cinder is planning to be there.  Hope that many of you can join us.16:33
*** rosmaita has joined #openstack-meeting16:34
mszwed_I'm wondering if it is a good idea to present there spdk and Cinder integration - technology, benefits, etc... what do you think?16:34
jungleboyjmszwed_:  That is something you could propose as a topic for the summit.16:35
jungleboyjsmcginnis:  Is the call for papers already open>?16:35
e0nejungleboyj: yes16:35
smcginnisYes, but the CFP closes soon.16:35
mszwed_when is the cutoff date for proposing this?16:36
davidshaJanuary 20th I think16:36
e0neSummit  CFP is  open until Wednesday, January 23 at 11:59pm PT.16:36
*** wwriverrat has joined #openstack-meeting16:36
*** abishop_ has joined #openstack-meeting16:36
jungleboyjOk.  Lets move along.16:37
jungleboyj#topic quick review of specs16:37
*** openstack changes topic to "quick review of specs (Meeting topic: Cinder)"16:37
*** lhinds has quit IRC16:37
jungleboyjSo, we have two outstanding specs that we need to decide if we are going to include in Stein.16:37
jungleboyjFlatten volume from glance rbd image16:38
*** macza has joined #openstack-meeting16:38
*** radez has quit IRC16:38
jungleboyjThis makes sense to me but if we have any Ceph experts that can chime in, it would be appreciated.16:38
jungleboyjWhich is the Image encryption spec.16:39
*** bdperkin has quit IRC16:39
jungleboyjrosmaita:  Was going to look through this one.  Unfortunately eharney is out this week and he was the one that had the most questions there.16:39
*** kopecmartin has quit IRC16:39
*** haleyb|away has quit IRC16:39
jungleboyjDo we have anyone else who knows encryption well that can help review?16:39
*** awaugama has quit IRC16:40
*** asbishop has quit IRC16:40
lixiaoy1I ever worked on encrytion, and I can help to review encryption16:40
smcginnislixiaoy1: Thanks!16:40
jungleboyjlixiaoy1:  That would be great if you can look.16:40
*** lhinds has joined #openstack-meeting16:40
lixiaoy1my pleasure16:41
LiangFangI may take a look too16:41
jungleboyjCool.  I think it is a good feature but want to make sure we are thinking through it properly.16:41
jungleboyjOk.  Moving along.16:42
jungleboyj#topic Cinder RSD Driver Status update16:42
*** openstack changes topic to "Cinder RSD Driver Status update (Meeting topic: Cinder)"16:42
jungleboyjNow I do mean to ping you.  :-)16:42
YingxinThe RSD driver code is good16:42
Yingxinand CI is reporting16:42
jungleboyjYingxin: Agreed.  It looks pretty good.16:42
Yingxinbut CI will cause more overhead and the attach does not respond16:42
Yingxinand there is another snapshot deletion issue from backend16:43
jungleboyjWhat do you mean the attach does not respond?16:43
Yingxinthe fix from backend could be in 1~2 weeks I heard16:43
jungleboyjDoes it require the os-brick fix?16:43
mszwed_Yingxin: is this related to inflate call?16:44
YingxinRSD attach volume will not be effective right after the volume created16:44
lixiaoy1jungleboyj, no, the fix is in the storage backend16:44
jungleboyjlixiaoy1:  Ok.16:44
YingxinThat's why I added retry in Driver code16:44
davidshaJust to clarify, the CI is working. Myself and martinkennelly are working on it atm.16:44
Yingxinbut RSD still doesn't respond with CI16:45
smcginnisSo it works, a fix is needed in the storage backend itself, but in the meantime the retries in os-brick will help avoid the issue - is that right?16:45
Yingxinwhich will be fixes from RSD16:45
*** jamesmcarthur has joined #openstack-meeting16:45
YingxinYes but seems it doesn't help much16:45
smcginnisYingxin: So the CI is running but not reporting yet?16:46
smcginnisStill not clear if it is passing or not.16:46
jungleboyjsmcginnis:  It is reporting but not passing yet.16:46
Yingxinsome tests failed because of the two issues I mentioned.16:46
Yingxinjungleboyj: smcginnis yes16:47
smcginnisAre they specific tests, or is it kind of random?16:47
davidshasmcginnis: It's running atm, it uncovered a bug in the backend.16:47
jungleboyjdavidsha: It is working.  :-)16:47
jungleboyjWhy are you thinking this will take weeks to fix?16:48
Yingxinit's from another team to fix RSD issues16:48
smcginnisLooks like CI isn't running all tests yet though  - Status: Pass 92 Failure 16 Skip 416:48
davidshaThe team that works on RSD need some time to make the changes and rebuild the env16:48
smcginnisThis is why CI is almost as important as writing the driver code. If it was running earlier it hopefully would have caught this.16:49
smcginnisIt doesn't sound like things will be ready for the deadline.16:49
YingxinIs it possible to have some exceptions of the deadline there?16:50
*** iyamahat has joined #openstack-meeting16:51
*** imacdonn has quit IRC16:51
smcginnisIf it was just a test that needed to be temporarily skipped, maybe. But it's failing a lot of tests and not even running all of them yet, so it doesn't seem so.16:51
mszwed_If the issue with deleting snapshot is the same that I hear of 2 days ago than this is very simple fix that should be done fast :)16:51
*** imacdonn has joined #openstack-meeting16:51
*** abishop_ is now known as abishop16:51
mszwed_Yingxin: the issue with attach functionality is already root caused? If not I can work with backend team to solve this (we work at the same site).16:53
Yingxinmszwed_: yes, there'are some discussions about it and I can forward.16:53
Yingxinmszwed_: thank you!16:53
mszwed_ok, I'll see what I can do and I will go to them tomorrow.16:54
*** bdperkin has joined #openstack-meeting16:54
smcginnisSounds like there's hope. Can we check on status tomorrow?16:54
Yingxinmszwed_: appreciated16:55
Yingxinsmcginnis: sure16:55
jungleboyjIf there is hope ...16:55
martinkennellysmcginnis: When you say not all tests are running, do you mean the skipped tests?16:55
jungleboyjmartinkennelly:  The full set of Cinder tempest tests should be run.  About 220 tests.16:55
jungleboyjOk, if there is more discussion lets take it to the channel.16:56
jungleboyjWe only have 4 minutes left.16:56
jungleboyjPlease keep smcginnis and I updated in the channel on your progress.16:56
jungleboyjWe will have to re-address tomorrow.16:56
mszwed_please keep in mind that RSD is also using NVMf so not all tests will pass (some assume scsi interface)16:57
jungleboyj#topic Should we consider abandoned?16:57
*** openstack changes topic to "Should we consider abandoned? (Meeting topic: Cinder)"16:57
abishopre: this patch, the author hasn't responded since last November16:57
abishopI can take over the work, but would prefer to submit something completely different16:57
abishopdifferent code and commit message (i.e. nothing from this review would be left intact)16:57
smcginnisabishop: That would be great if you could take that over.16:57
jungleboyjsmcginnis:  ++16:58
smcginnisabishop: No updates in a very long time from them.16:58
jungleboyjI can abandon if you can take over.16:58
smcginnisI would assume it's abandoned at this point.16:58
abishopok, will do, thx16:58
smcginnisabishop: Thanks for taking that!16:58
jungleboyjYes, thank you!16:58
abishopnp! glad someone reported the issue!16:58
jungleboyjLiangFang:  We are almost out of time.  Can you move your topic forward to next week's meeting?16:59
jungleboyjLiangFang:  Sorry about that.16:59
LiangFangcurrently cpu is doing the image conversion, I think we can leverage some hardware accelerator to do this if the platform have such hardware, I may have spec about this16:59
jungleboyjI will pull it forward when I create the next agenda.16:59
jungleboyjSo, need to wrap up.17:00
smcginnismszwed_: Doesn't look like you are in #openstack-cinder. Can you join that channel?17:00
jungleboyjThank you team for showing up.17:00
mszwed_smcginnis: sure17:00
e0nesee you next week17:00
jungleboyjPlease remember to comment on the mid-cycle etherpad.17:00
jungleboyjThanks all!17:00
*** openstack changes topic to "OpenStack Meetings ||"17:00
openstackMeeting ended Wed Jan  9 17:00:49 2019 UTC.  Information about MeetBot at . (v 0.1.4)17:00
openstackMinutes (text):
*** ganso has left #openstack-meeting17:00
*** abishop has left #openstack-meeting17:03
*** e0ne has quit IRC17:03
*** LiangFang has quit IRC17:03
*** _alastor1 is now known as _alastor_17:07
*** lseki has left #openstack-meeting17:07
*** woojay has left #openstack-meeting17:07
*** armax has joined #openstack-meeting17:17
*** mszwed_ has left #openstack-meeting17:18
*** yamamoto has joined #openstack-meeting17:24
*** yamamoto has quit IRC17:29
*** aojea has quit IRC17:48
*** yamamoto has joined #openstack-meeting17:56
*** yamamoto has quit IRC18:01
*** davidsha has quit IRC18:07
*** awaugama has joined #openstack-meeting18:15
*** armax has quit IRC18:16
*** armax has joined #openstack-meeting18:16
*** tkauthar has quit IRC18:25
*** martinkennelly has quit IRC18:25
*** yamahata has quit IRC18:31
*** lpetrut has joined #openstack-meeting18:33
*** e0ne has joined #openstack-meeting18:35
*** jamesmcarthur has quit IRC18:36
*** lpetrut has quit IRC18:37
*** macza has quit IRC18:44
*** martinkennelly has joined #openstack-meeting18:44
*** macza has joined #openstack-meeting18:45
*** electrofelix has quit IRC18:55
*** awaugama_ has joined #openstack-meeting18:58
*** awaugama has quit IRC19:00
SotK#startmeeting storyboard19:00
openstackMeeting started Wed Jan  9 19:00:58 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:01
*** openstack changes topic to " (Meeting topic: storyboard)"19:01
openstackThe meeting name has been set to 'storyboard'19:01
SotK#link Agenda19:02
*** e0ne has quit IRC19:02
SotK(ish, I meant to update it but ran out of time)19:02
*** carlos_silva has quit IRC19:02
fungiagenda-ish is plenty19:03
SotKdiablo_rojo: have there been any migration updates the last few weeks?19:03
*** jamesmcarthur has joined #openstack-meeting19:04
diablo_rojoEhhh nope nothing lately19:05
*** e0ne has joined #openstack-meeting19:05
diablo_rojoThings have been slow with the holidays19:05
SotK#topic In-Progress Work19:05
*** openstack changes topic to "In-Progress Work (Meeting topic: storyboard)"19:05
openstackRemoving item from minutes: #topic In-Progress Work19:05
SotK#topic Story Attachments19:06
*** openstack changes topic to "Story Attachments (Meeting topic: storyboard)"19:06
SotKthe spec got merged, we should implement it!19:06
diablo_rojoHa ha yes we should19:07
*** phuoc__ has quit IRC19:08
SotKany volunteers? :D19:08
diablo_rojoI can help if you wanna work on it together SotK19:08
SotKin all seriousness I was planning to make it the next thing on my to do list if nobody else is super excited to do so19:08
diablo_rojoGo for it :)19:08
fungii'm happy to help with the storage provisioning, at the very least19:08
diablo_rojoAnd let me know how I can help.19:09
SotKsounds good, I'll try to make some time in the near future to get started :)19:09
SotK#topic Moving database closer to the site19:09
*** openstack changes topic to "Moving database closer to the site (Meeting topic: storyboard)"19:09
diablo_rojoSotK, if you want to meet to set up a bunch of tasks and divy some of them up I would totally be down for that.19:10
diablo_rojoOr I can focus on other bugs and stuff19:10
SotKthat sounds like a good idea but I want to get ideas straight in my head first19:11
fungion the db move, as noted i'm coupling it with a server "upgrade" (rebuild) on ubuntu xenial since the sortyboard servers were still on trusty19:12
fungibut wanted to build the instances as servers now that we have the domani settled (and then keep the vhost at least for the time being)19:12
fungiwhenever i mistype domain as domani i get flashbacks from latin class19:13
diablo_rojoSotK, yeah I am fine with that.19:13
diablo_rojofungi, lol19:13
SotKthanks for working on this :)19:14
fungithe intent being to have less to clean up later when we inevitably rename the service19:14
fungianyway, there was still a fair amount of plumbing missing in the infra to support using the new domain name for servers, so i needed to get in some fairly large patches to expand all our host regexes and globs19:14
fungithat's all in now, and i'm trying to boot as i type this19:15
fungionce it's hopefully reachable and puppeted, i'm going to test switching over from the old dev server to it, and then once that's confirmed working i'll try the db dump and import19:15
*** yamamoto has joined #openstack-meeting19:16
fungiwe've at least already got the puppet updated to deploy a local mysqld on these servers, so really just the export/import is all we should need19:16
fungi#link database move plan19:16
diablo_rojoThat's awesome progress :)19:16
diablo_rojoI hope it all goes well.19:16
fungithat's the basic steps i'm going to follow for the actual db maintenance19:16
SotKindeed, sounds good19:16
diablo_rojoThanks for all your hard work on this over the holidays fungi :)19:17
fungiand with that, it just spat back some ip addresses at me, so i'll be trying it out as soon as we're done with the meeting19:17
fungidiablo_rojo: i'm going to make up for it by disappearing for a couple of weeks at the end of this month ;)19:17
*** armax has quit IRC19:17
SotKsemi-related, am I imagining it or was there a plan at some point to redeploy storyboard-dev in containers sometime too?19:18
fungiwe'll need that to upgrade to bionic, yes19:18
fungimordred had mentioned sb as a possible early containering19:19
mordredyeah. I've got a patch up to start down the building containers road19:19
fungisince it uses pbr, we can likely make pbrx images of it fairly easily?19:19
SotKthat's what the patch does aiui19:19
fungiand we already have jobs to automate it19:19
fungiso, yes i think so19:20
mordredyeah. although ... I've been having some thoughts about some ways to change that process19:20
mordredso - yeah - but let me take another pass at that patch before we get too far19:20
fungiwell, we'll at least be off trusty rsn and can think about containers on bionic more easily19:20
SotKok then19:20
*** yamamoto has quit IRC19:21
* SotK is looking forward to experimenting with the result19:21
SotK#topic In-Progress Work19:22
*** openstack changes topic to "In-Progress Work (Meeting topic: storyboard)"19:22
SotKI have a couple of tag and worklist related patches that need either +1s or +A, but haven't actually done much recently because of holidays and lack of time19:23
SotKso I still have a big backlog of reviews to do myself, sorry19:23
diablo_rojoI think I only have a patch or two that need attention.19:23
diablo_rojoI will go through and see if there are any I need to review still19:24
* diablo_rojo writes 'SB reviews' post it and sticks it next to others 19:24
SotKiirc you've reviewed them but a couple are ready for approving when you get time19:24
diablo_rojoMaybe fungi should take a look too?19:25
diablo_rojoUnless we are single core approving?19:25
SotKwe have done in the past, but I don't mind waiting for fungi too if he has time19:25
fungihappy to take a peek, but single-core approvals in sb have been a thing for a while19:25
fungigiven the limited size of its core review team19:26
diablo_rojoI can give them till next week and then approve if you don't get the time fungi19:27
SotKsounds good to me19:27
SotKanything else to mention here?19:28
*** awaugama_ has quit IRC19:29
diablo_rojoDon't think so atm19:30
*** luizbag has left #openstack-meeting19:30
*** awaugama has joined #openstack-meeting19:30
SotK#topic Open Discussion19:30
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"19:30
diablo_rojoSotK, registered for Denver yet? ;)19:31
SotKnot yet, have I managed to miss the discount-for-past-PTG-attendees email I was waiting for?19:32
SotKit is still in my calendar though :)19:33
diablo_rojofungi, those should have gone out right?19:33
fungii didn't think they'd gone out yet, but also it sounds like it won't cover dublin-only attendees since they already got discount passes to two subsequent summits, but also we can almost certainly get yours comped through travel support19:34
*** rosmaita has left #openstack-meeting19:34
fungiwe probably even know someone on the tsp committee as well as a ptl or several to vouch for you as an essential attendee19:35
SotKI'll look into that soon then19:35
* diablo_rojo grins 19:36
diablo_rojoYeah you might know someone like that19:37
SotKanything else to discuss?19:39
diablo_rojoDon't think so atm19:39
SotKin that case, thanks all for attending :)19:40
*** openstack changes topic to "OpenStack Meetings ||"19:40
openstackMeeting ended Wed Jan  9 19:40:21 2019 UTC.  Information about MeetBot at . (v 0.1.4)19:40
openstackMinutes (text):
*** ralonsoh has quit IRC19:40
fungithanks SotK!19:40
diablo_rojoThanks SotK!19:43
*** martinkennelly has quit IRC19:45
*** efried has joined #openstack-meeting20:06
*** e0ne has quit IRC20:08
*** thgcorrea has quit IRC20:13
*** radeks_ has joined #openstack-meeting20:22
*** radeks has quit IRC20:25
*** munimeha1 has quit IRC20:34
*** slaweq has quit IRC20:37
*** awaugama has quit IRC20:39
*** efried has quit IRC20:40
*** hongbin has joined #openstack-meeting20:42
*** martinkennelly has joined #openstack-meeting20:44
*** markvoelker has joined #openstack-meeting20:45
*** slaweq has joined #openstack-meeting20:52
*** patchbot has joined #openstack-meeting20:56
*** timburke has joined #openstack-meeting20:59
notmynameswift team meeting time21:00
notmyname#startmeeting swift21:00
openstackMeeting started Wed Jan  9 21:00:13 2019 UTC and is due to finish in 60 minutes.  The chair is notmyname. 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
notmynamewho's here for the swift team meeting?21:00
rledisezhi o/21:00
mattoliveraurledisez couldn't decide on a greating so used both :P21:01
notmynameclayg: timburke: tdasilva: ?21:01
notmynamegood to see everyone here21:02
rledisezmattoliverau: as I always say, why choosing? ;)21:02
notmynamewelcome back and happy new year21:02
*** m_kazuhiro has joined #openstack-meeting21:02
mattoliveraunotmyname: thanks, you too!21:02
clayg2019!!! 🎉21:02
notmynameit's here, whether you're ready or not :-)21:03
notmynameall right. first meeting of the new year. let's recap to see where we are21:03
* mattoliverau notes that he's been up all night with a sick baby, so might be a little sleep deprived and therefore extra sarcastic this morn ;P21:03
notmynameswift 2.20.0 has been released. best release ever21:03
claygpoor baby21:03
mattoliverauyeah :(21:03
notmynamemattoliverau: sorry to hear that. good luck21:04
clayg2.20.0 was solid 👍21:04
*** yamamoto has joined #openstack-meeting21:04
rledisez"swift 2.20 is here, whether you're ready or not :-)" \o/21:04
timburke2.21 will be *even better* ;-)21:04
notmynamewe're in the middle of the openstack stein cycle. the openstack schedule is ...21:04
notmynamekey points are the end-of-february client release (ie python-swiftclient)21:05
notmynameand the final swift release needed the first week of april (at the latest)21:05
notmynamenote that there is *not* an openstack event before then. the ptg and summit have combined and will be in denver in may21:06
notmynamealso, looking far-future, towards the end of the year there will be a summit in china (no details published that I've seen)21:06
mattoliverauthey must've had a 3 for 1 deal for denver :P21:06
mattoliverauthough this next one will be at a different venue21:07
notmynamemore immediately, along with the 2.20.0 release, we landed a lot of backports. timburke tells me that he's got more; I'd like to have a tag on the stable branches by the end of next week21:07
timburkeApril 29 - May 121:07
mattoliverauoh china, interesting21:07
mattoliveraugood idea. If we have backports lets release em21:08
claygChina might be cool21:08
notmynameI need to check that the priority review page is up to date21:08
* mattoliverau might keep talking to stay awake :P21:08
claygDeven... when is Denver?  Is it a design summit?  are we going?21:08
notmynameclayg: yes. we should all go. there will be developer sessions/rooms21:09
*** yamamoto has quit IRC21:09
notmynameapril 29 -> may 121:09
kota_in the latter half of the week?21:10
notmynameall the details are there21:10
notmynamethat's everythign I can think of about current schedules for stuff.21:11
kota_ok, ptg is May 2 - 4, 201921:11
claygbah, Saturday21:11
notmynameah, ok. I see21:11
timburkeidk... my kid's first birthday is 4/30...21:11
claygyay 1st birthday!21:12
claygcake cake cake!21:12
notmynameyeah, you don't want to miss that :-)21:12
notmynamethe Big Things we've been talking about are still around and still in progress21:12
*** ociuhandu has joined #openstack-meeting21:13
mattoliverauif the PTG part is 2 -4 that's all we really need to be at right?21:13
*** radeks_ has quit IRC21:13
claygmattoliverau: 👍21:13
notmynamewe've got LOSF and task queue and py3 port are the most definite things21:13
tdasilvanotice CFG for summit closes in two weeks from today21:14
notmynamemattoliverau: clayg: definitely those days. one of the summit days may be interesting. hard to say right now. probably is different for each person21:14
timburkeoh yeah, i should go look over ...21:14
patchbotpatch 629610 - swift - WIP py3: object server - 1 patch set21:14
mattoliverausure, it'll come down to my employer anyway21:14
claygcool cool!21:14
notmynamerledisez: how's LOSF? what are your next plans for it?21:15
m_kazuhiroWho will go to the PTG or summit?21:15
notmynamem_kazuhiro: I suspect most or all of us will be at the ptg part. and some will be at the summit too21:15
notmynamem_kazuhiro: also, welcome! :-)21:16
mattoliverauI plan too.. but again employer.. and I have to remind them as I missed the last few :(21:16
rlediseznotmyname: right now alecuyer is taking a step back, working on some other projects. it's good enough for our production. I think at that point we need a plan for LOSF in Swift. what will happen, how, when, …21:16
rledisezof course, we still want it upstream21:16
notmynamerledisez: ah, ok. that's interesting21:16
notmynameI think the rest of us want it upstream too :-)21:16
rledisezthe current code run on 2.18, we will work soon to adapt it to 2.20 (or 2.21, depends how fast it's released :))21:17
notmynamerledisez: so are you saying that there are not any more obvious design changes. you are fairly happy with how it's working in prod now?21:17
rlediseznotmyname: yes, as far as we know, we've found no more bugs, and it matches all our needs/expectation on performance21:18
rledisezthere could be some perf improvment on some part, but nothing major21:18
notmynamedo you have any plans on how to propose it upstream?21:18
notmynameor rather, plans on how to get it landed upstream?21:19
rledisezI think we are waiting for a plan. alex cannot do that alone, because there will be of course reviews that will make changes to the design21:19
notmynameso we (all of us) need to work together on finding that plan21:20
rledisezso, first would be reviews of the design, then working on code/helping us making the code matching quality expectation of reviewers, etc...21:20
rledisezand tests...21:20
rlediseznotmyname: +121:20
notmynamewhat is your opinion of the code now? is it sufficiently tested and documented to land upstream? do you think the code quality matches what's in swift?21:21
notmynameI'm not sure how to phrase that question. mostly wondering if you expect it to change much once proposed21:21
notmyname...or what work is needed before it's proposed21:21
notmynameor differences between what needs to be proposed vs what's been proposed previously21:21
rlediseznotmyname: I don't think so. it's not much documented, and the tests are pretty limited (the golang RPC is fully tested I think, not the diskfile). but at least, func tests are passing :)21:22
notmynamethere is not a wrong answer. I'm only trying to manage expectations for myself and everyone. so we understand if this is something nearly done or will need a few months of work from the whole team21:22
notmynamerledisez: anything else to share about LOSF right now?21:23
rlediseznotmyname: no, as I said alex took a step back, so it didn't change much in the last few weeks21:24
notmynamewe'll come back to LOSF, of course, but for this meeting I want to move on21:24
notmynamenext up is the same questions for the task queue work21:24
notmynamem_kazuhiro: and kota_: how is this project going?21:24
notmynameand what are your next plans for it?21:25
kota_i saw m_kazuhiro has updated the patches, but that's all I know so far.21:25
m_kazuhiroFirst I want to merge Patch 601950. This is for general task queue patch.21:26
patchbot - swift - Enable to configure object-expirer in object-serve... - 11 patch sets21:26
m_kazuhiroI updated and fixed this patch at December. So I think the patch is ready for review now.21:27
*** jamesmcarthur has quit IRC21:27
notmynameok, that's good to hear21:27
notmynameis there anythign else to add at this point, or should the conversation happen in gerrit about that patch?21:28
m_kazuhiroI want to know who can review the patch.21:29
*** jamesmcarthur has joined #openstack-meeting21:29
notmynameI don't think I can answer that right now. I want to get a sense of all the stuff going on first, so that we all know21:30
notmynamethe final Big Thing that's going on is the py3 port21:30
notmynamedoesn't look like zaitcev made it today. but I know timburke has been helping with this some21:30
notmyname(is there anything timburke doesn't do?)21:31
notmynameand py3 is something that matters a lot to you mattoliverau, right? that is, it matters a lot to suse21:31
*** vishalmanchanda has quit IRC21:31
notmynamelike it does for redhat and canonical21:31
notmynameit looks like there is a proposal today to port the object server to py321:32
mattoliverauyeah, it's one of the goals that SUSE is interested in OpenStack wide, for obvious reasons.21:32
notmynamemattoliverau: is it something they're asking you to work on specifically?21:32
mattoliverauSo something I'll try and get back into, but probably not really until I'm back from Germany and Christ Church. But will try and review whats there in the mean time.21:33
notmynameonce it's done, I think both canonical and suse need to send redhat a box of cupcakes to thank redhat for porting swift ;-)21:34
claygmmmmm cupcakes21:34
timburkei want cupcakes! ;-)21:34
mattoliverau+1 :)21:34
notmynamethe py3 todo list is essentially tracked in the tox.ini file21:34
notmynamethat's ported stuff21:35
timburkethat makes it seem like we havne't done much! really, it's
timburkeand two of those are directories21:36
timburkewait, three!21:36
notmynamein fact, we *want* that list to be very short because it means that we've eg ported everythign under common21:36
notmynameso the list will keep getting longer until it shrinks by a lot (when a whole directory is ported). then it will grow again. then it will shrink to zero when everything is ported and we require py3 compat for 100% of the code21:37
timburkeone of the real interesting things will be to compare coverage reports between py2 and py3 unit test runs21:37
timburkefwiw, i currently see 33143 total statements on py2, and 25384 on py321:38
timburke(with 92% and 74% coverage, respectively)21:38
notmynamethe py3 work will be constant (with people getting more anxious about it as time goes by) until it's done21:39
timburkeso we still have some 7k lines that never even get imported21:39
notmynameanything else on the py3 work?21:39
*** ociuhandu has quit IRC21:39
notmynameI think we've probably covered that topic enough21:39
notmynamewhich leads us to... what? what else is there to bring up this week in the meeting?21:40
notmynamehave we missed any big existing ongoing work? anything else to bring up today?21:40
timburke would be good to have21:41
patchbotpatch 629301 - swift - Verify client input for v4 signatures - 1 patch set21:41
kota_wooo s3api21:41
notmynameyes, that one would be good. it's been tracked as a private security issue until recently. we opened it to treat it as a security-hardening opportunity instead of a critical open vulnerability21:41
claygwoo s3api!21:42
notmynamebut it needs to be closed asap21:42
openstackLaunchpad bug 1765834 in OpenStack Security Advisory "Need to verify content of v4-signed PUTs" [Undecided,Incomplete]21:42
notmynameif there is one, single important patch right now, it's likely that one21:42
mattoliverauI raised yesterday, cause I was pinged about it from 2 different people on 2 different openstack deployement tools internally yesterday. Nothing major, but something to think about. So will put some words on the bug report about it.21:42
openstackLaunchpad bug 1811044 in OpenStack Object Storage (swift) "Allow_versions config option in Container-server is deprecated but removing can lead to some version containers failing to version objects" [Undecided,New] - Assigned to Matthew Oliver (matt-0)21:42
timburkei really like the "In the future, Swift will hopefully grow a way to perform SHA256 verification on the object-server." idea21:43
mattoliverauie as I actually thnk about it. And not spitballing ideas21:43
notmynamemattoliverau: ah, ok. is this something you're working on a patch for, or do you need somethign from the rest of us first?21:43
mattoliveraunah, I can do it. Just letting y'all know.21:44
timburkemattoliverau: did they "Configure the versioned_writes middleware in the proxy-server instead" per the deprecation warning? or did they just forget that step?21:45
claygmattoliverau: awesome, thanks for chasing that down!21:45
mattoliverauno you can do it. but if you don't "reset" the versioning on a container that was set pre 2.4.0 the middleware wont check the old metadata anaymore21:45
timburkeor am i misunderstanding the bug? i must admit, i only skimmed it...21:46
timburkeoh... yeah, that's no good21:46
mattoliverauI mean, they added the middleware properly.21:46
timburkeoh yeah, speaking of audit watchers... lives!21:46
patchbotpatch 212824 - swift - Let developers/operators add watchers to object audit - 12 patch sets21:47
mattoliverauI noticed, which is why I added at as an idea ;P21:47
notmynameok, anything else from anyone? otherwise, let's go ahead and end the meeting21:48
rledisezto share what are my plans on Swift, I'll continue to work on SSYNC this year. my goal is to make it as fast as possible in 4 major steps:21:48
rledisez1. concurrency per partitions ( => need more tests)21:48
rledisez2. delete reverted object ASAP (patch half written)21:48
rledisez3. fsync() batch (need more thinking)21:48
rledisez4. better coordination between servers (need a lot of thinking)21:48
patchbotpatch 613987 - swift - SSYNC: enable multiple SSYNC connections per job - 4 patch sets21:48
rledisezbtw, thx mattoliverau for the review on ^21:48
mattoliveraurledisez: nice!21:49
mattoliveraunps, I'll try and loop back round on it21:49
timburkerledisez: clayg and i should post some of the ideas we've had around 4...21:49
timburkewe drew out some diagrams a while back... i know i took a picture21:49
rlediseztimburke: that would be very interesting. we've got some, but it was just talking around a coffee, nothing much21:50
mattoliverauyeah please, share diagrams!21:51
claygI'm really mad about SSYNC not really being un-interruptable - the whole protocol falls over if it hits a 4/5XX responses when it's streaming data :'(21:51
claygeverything will be better with gRPC - which we get with LOSF right!?21:51
rledisezclayg: that point is addressed in 221:52
rledisezif i understand you well21:52
claygprobably not :P21:52
rledisezhaha, you're so mysterious :D21:53
rledisezin point 2, because the receiver maintain a list of success/failure and send it back to the sender, we can ignore and continue, then the sender clean what was a success21:53
claygwell maybe... depending on how drastically you restructure the interface when you let ssync remove data files as it reverts (which agreed, would be great)21:53
rledisez(that's the patch i'm working on)21:53
notmynameprobably a good idea to move that conversation into -swift21:54
notmynamei'll end this meeting now21:54
notmynamethank you everyone for coming21:54
claygnotmyname: thanks!21:54
notmynameI'm excited about what the swift team will be able to do in 2019 :-)21:54
clayghere here!21:54
notmynamethanks for your work on the project21:54
*** openstack changes topic to "OpenStack Meetings ||"21:55
openstackMeeting ended Wed Jan  9 21:55:02 2019 UTC.  Information about MeetBot at . (v 0.1.4)21:55
openstackMinutes (text):
*** timburke has left #openstack-meeting21:55
*** patchbot has left #openstack-meeting21:55
*** m_kazuhiro has quit IRC21:59
*** hongbin has quit IRC22:40
*** rcernin has joined #openstack-meeting22:52
*** hongbin has joined #openstack-meeting22:52
*** yamamoto has joined #openstack-meeting22:52
*** hongbin has quit IRC22:52
*** diablo_rojo has quit IRC22:53
*** hongbin has joined #openstack-meeting22:54
*** yamamoto has quit IRC22:56
*** markvoelker has quit IRC22:57
*** markvoelker has joined #openstack-meeting22:57
*** macza has quit IRC22:59
*** macza has joined #openstack-meeting22:59
*** markvoelker has quit IRC23:02
*** whoami-rajat has quit IRC23:04
*** erlon has quit IRC23:06
*** jamesmcarthur has quit IRC23:07
*** jamesmcarthur has joined #openstack-meeting23:10
*** jamesmcarthur has quit IRC23:11
*** diablo_rojo has joined #openstack-meeting23:12
*** jamesmcarthur has joined #openstack-meeting23:18
*** jamesmcarthur has quit IRC23:30
*** yamamoto has joined #openstack-meeting23:30
*** jamesmcarthur has joined #openstack-meeting23:32
*** jamesmcarthur has quit IRC23:35
*** jamesmcarthur has joined #openstack-meeting23:36
*** jamesmcarthur has quit IRC23:37
*** enriquetaso has quit IRC23:39
*** hongbin has quit IRC23:52
*** _alastor_ has quit IRC23:59

Generated by 2.15.3 by Marius Gedminas - find it at!