Wednesday, 2018-10-31

*** gyee has quit IRC00:36
*** markvoelker has quit IRC00:49
*** markvoelker has joined #openstack-meeting00:50
*** longkb has joined #openstack-meeting00:52
*** ssbarnea has quit IRC00:52
*** markvoelker has quit IRC00:55
*** ykatabam has quit IRC00:55
*** ykatabam has joined #openstack-meeting01:04
*** yamahata has quit IRC01:36
*** iyamahat has quit IRC01:36
*** iyamahat has joined #openstack-meeting01:52
*** hongbin has joined #openstack-meeting02:02
*** diablo_rojo has quit IRC02:02
*** yamahata has joined #openstack-meeting02:10
*** mhen has quit IRC02:13
*** mhen has joined #openstack-meeting02:16
*** erlon has quit IRC02:33
*** tetsuro has joined #openstack-meeting02:45
*** markvoelker has joined #openstack-meeting02:51
*** psachin has joined #openstack-meeting02:52
*** cloudrancher has quit IRC03:11
*** cloudrancher has joined #openstack-meeting03:11
*** tetsuro has quit IRC03:12
*** tetsuro has joined #openstack-meeting03:16
*** Nel1x has joined #openstack-meeting03:23
*** markvoelker has quit IRC03:24
*** martial__ has quit IRC03:31
*** janki has joined #openstack-meeting03:47
*** tetsuro has quit IRC03:51
*** Nel1x has quit IRC03:52
*** hongbin has quit IRC04:01
*** markvoelker has joined #openstack-meeting04:21
*** yamahata has quit IRC04:35
*** yamahata has joined #openstack-meeting04:35
*** ykatabam has quit IRC04:51
*** ykatabam has joined #openstack-meeting04:53
*** markvoelker has quit IRC04:54
*** armax has joined #openstack-meeting05:28
*** ykatabam has quit IRC05:29
*** pcaruana|elisa| has joined #openstack-meeting05:29
*** pcaruana|elisa| has quit IRC05:37
*** janki has quit IRC05:46
*** janki has joined #openstack-meeting05:49
*** markvoelker has joined #openstack-meeting05:51
*** ykatabam has joined #openstack-meeting05:56
*** e0ne has joined #openstack-meeting06:16
*** e0ne has quit IRC06:18
*** janki has quit IRC06:18
*** markvoelker has quit IRC06:26
*** ykatabam has quit IRC06:33
*** janki has joined #openstack-meeting06:37
*** armax_ has joined #openstack-meeting06:42
*** armax has quit IRC06:42
*** armax_ is now known as armax06:42
*** markvoelker has joined #openstack-meeting07:24
*** pcaruana|elisa| has joined #openstack-meeting07:45
*** tssurya has joined #openstack-meeting07:45
*** markvoelker has quit IRC07:57
*** hle2 has quit IRC08:00
*** LiangFang has quit IRC08:01
*** Liang__ has joined #openstack-meeting08:04
*** e0ne has joined #openstack-meeting08:12
*** liuyulong has quit IRC08:12
*** larainema has quit IRC08:30
*** ralonsoh has joined #openstack-meeting08:31
*** ssbarnea has joined #openstack-meeting08:40
*** a-pugachev has joined #openstack-meeting08:50
*** markvoelker has joined #openstack-meeting08:54
*** pcaruana|elisa| has quit IRC09:13
*** Liang__ has quit IRC09:14
*** pcaruana|elisa| has joined #openstack-meeting09:15
*** Qiming has quit IRC09:16
*** NikitaKonovalov has quit IRC09:16
*** e0ne has quit IRC09:16
*** Liang__ has joined #openstack-meeting09:18
*** NikitaKonovalov has joined #openstack-meeting09:18
*** Qiming has joined #openstack-meeting09:19
*** e0ne has joined #openstack-meeting09:25
*** markvoelker has quit IRC09:27
*** ttsiouts has joined #openstack-meeting09:28
*** ttsiouts has quit IRC09:29
*** ttsiouts has joined #openstack-meeting09:45
*** ianychoi has quit IRC09:51
*** ianychoi has joined #openstack-meeting09:52
*** kopecmartin|off is now known as kopecmartin10:05
*** electrofelix has joined #openstack-meeting10:07
*** apetrich has quit IRC10:12
*** markvoelker has joined #openstack-meeting10:24
*** apetrich has joined #openstack-meeting10:27
*** rossella_s has joined #openstack-meeting10:31
*** yamamoto has quit IRC10:34
*** yamamoto has joined #openstack-meeting10:34
*** Liang__ has quit IRC10:37
*** yamamoto has quit IRC10:39
*** yamamoto has joined #openstack-meeting10:40
*** yamamoto has quit IRC10:41
*** shrasool has joined #openstack-meeting10:42
*** markvoelker has quit IRC10:58
*** e0ne has quit IRC11:15
*** e0ne has joined #openstack-meeting11:15
*** ykatabam has joined #openstack-meeting11:23
*** e0ne has quit IRC11:27
*** yamamoto has joined #openstack-meeting11:28
*** yamamoto has quit IRC11:35
*** yamamoto has joined #openstack-meeting11:35
*** rossella_s has quit IRC11:40
*** longkb has quit IRC11:41
*** raildo has joined #openstack-meeting11:51
*** markvoelker has joined #openstack-meeting11:54
*** rossella_s has joined #openstack-meeting11:55
*** shintaro has joined #openstack-meeting12:00
*** markvoelker has quit IRC12:13
*** jchhatbar has joined #openstack-meeting12:28
*** jchhatbar has quit IRC12:28
*** janki has quit IRC12:29
*** janki has joined #openstack-meeting12:29
*** ttsiouts has quit IRC12:30
*** tpsilva has joined #openstack-meeting12:38
*** yamamoto has quit IRC12:44
*** yamamoto has joined #openstack-meeting13:04
*** e0ne has joined #openstack-meeting13:06
*** erlon has joined #openstack-meeting13:08
*** raildo has quit IRC13:09
*** raildo_ has joined #openstack-meeting13:09
*** rbudden has joined #openstack-meeting13:09
*** eharney has joined #openstack-meeting13:13
*** mriedem has joined #openstack-meeting13:14
*** mriedem is now known as ash_williams13:15
*** ttsiouts has joined #openstack-meeting13:16
*** liuyulong has joined #openstack-meeting13:19
*** dustins has joined #openstack-meeting13:20
*** janki has quit IRC13:22
*** janki has joined #openstack-meeting13:23
*** sambetts|afk is now known as sambetts13:28
*** daikk115 has joined #openstack-meeting13:28
*** slaweq has quit IRC13:29
*** eharney_ has joined #openstack-meeting13:30
*** jamesmcarthur has joined #openstack-meeting13:31
*** eharney_ has quit IRC13:35
*** yamamoto has quit IRC13:37
*** yamamoto has joined #openstack-meeting13:38
*** yamamoto has quit IRC13:38
*** cloudrancher has quit IRC13:53
*** jamesmcarthur has quit IRC13:54
*** cloudrancher has joined #openstack-meeting13:54
*** jamesmcarthur has joined #openstack-meeting13:55
*** awaugama has joined #openstack-meeting13:59
*** yamamoto has joined #openstack-meeting14:00
*** raildo_ has quit IRC14:00
*** jamesmcarthur has quit IRC14:01
*** shintaro has quit IRC14:09
*** shrasool has quit IRC14:13
*** hongbin has joined #openstack-meeting14:14
*** e0ne has quit IRC14:19
*** e0ne has joined #openstack-meeting14:26
*** raildo has joined #openstack-meeting14:30
*** cloudrancher has quit IRC14:38
*** cloudrancher has joined #openstack-meeting14:39
*** e0ne has quit IRC14:41
*** slaweq has joined #openstack-meeting14:41
*** e0ne has joined #openstack-meeting14:44
*** Leo_m has joined #openstack-meeting14:52
*** mpiwowarczy has joined #openstack-meeting14:58
*** ianychoi has quit IRC15:00
*** gyee has joined #openstack-meeting15:01
*** slaweq has quit IRC15:01
*** rossella_s has quit IRC15:04
*** rossella_s has joined #openstack-meeting15:07
*** dkrol has joined #openstack-meeting15:09
*** rossella_s has quit IRC15:12
*** ash_williams has left #openstack-meeting15:21
*** ash_williams has joined #openstack-meeting15:21
*** ykatabam has quit IRC15:27
*** rossella_s has joined #openstack-meeting15:27
*** slaweq has joined #openstack-meeting15:29
*** ganso has joined #openstack-meeting15:48
*** kopecmartin is now known as kopecmartin|off15:49
*** woojay has joined #openstack-meeting15:54
*** rosmaita has joined #openstack-meeting15:57
*** eharney has quit IRC15:59
*** fanzhang has quit IRC16:00
*** fanzhang has joined #openstack-meeting16:00
* smcginnis whistles16:01
jungleboyj#startmeeting Cinder16:01
openstackMeeting started Wed Oct 31 16:01:02 2018 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
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
daikk115o/16:01
smcginniso/16:01
_alastor_o/16:01
yikuno/16:01
e0nehi16:01
rosmaitao/16:01
whoami-rajatHi16:01
xyanghi16:01
erlonhey16: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 rosmaita16:01
jungleboyj@!16:01
_pewp_jungleboyj (。・∀・)ノ16:01
geguileohi! o/16:01
gansohello16:02
*** jbernard has joined #openstack-meeting16:03
jungleboyjOk.  Looks like we have a lot of people already so we can get started16:03
jungleboyj#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:03
jungleboyjJust a reminder that I have created Forum Etherpads for Berlin:16:04
jungleboyj#link https://wiki.openstack.org/wiki/Forum/Berlin201816:04
jungleboyjPlease take a look and add your thoughts there.  Hopefully we will have good discussion there.16:04
jungleboyjI think that is all I have for announcements.16:05
jungleboyjAnything to add smcginnis  ?16:05
smcginnisHmm, not that I can think of, but I'll probably think of something later.16:05
jungleboyjOk.  Sounds good.16:06
*** jamesmcarthur has joined #openstack-meeting16:06
jungleboyj#topic Cinder get together in Berlin?16:06
*** openstack changes topic to "Cinder get together in Berlin? (Meeting topic: Cinder)"16:06
rosmaitais the etherpad really slow or is it just me?16:06
jungleboyjrosmaita:  It is slow.  I was having issues with it earlier.16:06
daikk115rosmaita, same with me.16:06
jungleboyjSo, a number of groups are having get togethers at Berlin.16:07
jungleboyjare people interested in trying to do something in Berlin?16:07
* jungleboyj hears crickets16:08
rosmaita"if you plan it, they will come"16:08
erlonI am16:08
jungleboyjrosmaita:  True enough.  :-)16:09
erlonit always good the get together16:09
smcginnisWould be fun. Have to collected an informal show of hands who will be in Berlin?16:09
e0neerlon: +116:09
jungleboyjI did in the last meeting.  There are a few of us.16:09
jungleboyjI will be there, smcginnis, geguileo , e0ne16:10
jungleboyj#link https://etherpad.openstack.org/p/BER-cinder-outing-planning16:10
jungleboyjThere is an etherpad that we can use to plan the event.16:10
jungleboyjThough etherpad is not happy at the moment so it is hard to start filling that in now.16:11
*** dustins has quit IRC16:12
jungleboyjsmcginnis:  You seemed to have an idea of what nights are already busy?16:12
jungleboyjSounded like Thursday might be the best night?16:13
smcginnisI have something Monday. Other nights should be OK.16:13
e0ne+116:13
*** janki has quit IRC16:13
smcginnisFolks are probably leaving Thursday night.16:13
smcginnisSo Wednesday might be best?16:13
jungleboyjOk.  I don't have anything planned yet so Wednesday should be fine for me.16:14
geguileoI don't have anything planned either16:14
jungleboyjWednesday night is the Meet and Geek Pub Crawl but people could join that later and would rather get time with the team.16:16
smcginnisOh right, forgot about that.16:16
smcginnisWe could combine to two as well.16:16
jungleboyjOtherwise we could do it after the Market Place Mixer on Tuesday.16:17
jungleboyjI don't have a strong preference.16:18
jungleboyjSo, I will put together the etherpad linked on the meeting agenda when etherpad is working again.16:19
jungleboyjWill send an e-mail to the mailing list to get people involved.16:19
jungleboyjPeople can then indicate their interest in joining and we can touch on it again next week.16:19
jungleboyjSound like a plan?16:20
jungleboyjI will take that as a yes.16:20
jungleboyj#topic New Cinder Incremental backup flow16:20
*** openstack changes topic to "New Cinder Incremental backup flow (Meeting topic: Cinder)"16:20
jungleboyjdaikk115:  Your floor.16:21
daikk115thank jungleboyj16:21
daikk115I'm using Ceph as a backend for Cinder, so the backup flow is so weird16:21
jungleboyjOk.16:22
smcginnisOh, you mean differential backup according to the description on the etherpad.16:22
daikk115the first one must be full backup and others always incremental16:22
smcginnisIn backup parlance, that is not incremental.16:22
daikk115smcginnis, yep.16:22
jungleboyjI feel like we talked about this at the PTG.16:23
geguileoI don't follow16:23
geguileoRBD backups are incremental, right?16:23
smcginnisSo differential has been discussed before. We can't support that since we don't do change block tracking to know what parts to backup.16:23
jungleboyjAh, that is right.16:23
daikk115what I want to have is "multiple full backups and every new incremental backup should be based on latest full backup"16:24
smcginnisPlease stop saying incremental.16:24
geguileodaikk115: there is a BZ to allow full backups after a full backup16:24
geguileoand there is a patch to allow that16:24
whoami-rajathttps://bugs.launchpad.net/cinder/+bug/1790713 i think there was a discussion regarding this in a meeting and this bug was filed.16:24
openstackLaunchpad bug 1790713 in Cinder "Ceph RBD backup driver cannot create full backups after the first full backup" [Undecided,In progress] - Assigned to Sofia Enriquez (lsofia-enriquez)16:24
smcginnisThat's another issue with ceph.16:24
geguileothat way it will follow the incremental flag16:24
jungleboyjgeguileo: Ah, that was what we talked about at the PTG.16:24
daikk115geguileo, I have tested that.16:24
geguileodaikk115: and is it OK?16:25
daikk115but new "differential backup" always base on the first full16:25
smcginnisBUt this is different. We have full and incremental backups already, just a bug in the ceph driver. Differential is different.16:25
smcginnisAnd something we've discussed a few times already and determined we can't/won't do.16:25
e0nesmcginnis: +116:26
geguileowe could do differential just like we do it now16:26
daikk115smcginnis, the usecase is create full backup for the first day of week.16:26
geguileoboth for RBD and for chuncked16:26
smcginnisI know the use case.16:26
daikk115and every day in that week we create diff backup.16:26
daikk115for the new week, we do the samething16:26
geguileodaikk115: it can be done, are you willing to work on it?16:26
jungleboyjgeguileo:  How can it be done?16:26
smcginnisgeguileo: I don't think it can be done. At least in the past, there were some backends that claimed it would not work for them.16:26
geguileojungleboyj: in which driver RBD or chunked one?16:27
smcginnisI've fine if someone can figure it out, but they can't just look at ceph and assume everything works the same way.16:27
jungleboyjRBD16:27
smcginnis*I'm16:27
geguileosmcginnis: we are not talking about "perfect differential", but a differential similar to our incremental16:27
jungleboyjsmcginnis:  ++16:27
*** kencjohnston has quit IRC16:27
smcginnisMy statement still stands. :)16:27
geguileoyeah, I think it could be done in RBD as well, though we would need to do tests to figure it out16:28
geguileosmcginnis: +116:28
geguileoI believe it can be done, but like smcginnis said, someone would have to confirm it and work on it16:28
*** aagate has joined #openstack-meeting16:28
whoami-rajatis this patch serving the similar purpose or otherwise ? https://review.openstack.org/#/c/612503/ geguileo16:28
daikk115But as my WIP patchset, the idea from my side is having new column to store "base" for each "differential backups"16:28
jungleboyjOk.16:28
*** kencjohnston has joined #openstack-meeting16:29
daikk115this my propose https://review.openstack.org/#/c/614469/16:29
smcginnisYou shouldn't need to store that. That can be determined when needed.16:29
daikk115whoami-rajat, that patch only help to create more full backups, that's16:29
jungleboyjwhoami-rajat:  No, that was just fixing a bug where once you did an incremental backup, that was all you could do.16:29
e0nedaikk115: how will it work for nfs and swift?16:29
geguileodaikk115: I have just read the commit message and it doesn't sound right16:30
daikk115e0ne, that's question. I'm don't know about that backend, but just think new column will not affect other backend16:30
e0nedaikk115: it's a bad idea to add a new column just for a one backend16:31
daikk115geguileo, sure, my commit message did not clear enough16:31
jungleboyjgeguileo:  ++16:31
geguileodaikk115: what are you trying to fix?16:31
whoami-rajatdaikk115:  jungleboyj  ok, seems like that should be supported first to have multiple full backups16:31
daikk115e0ne, I know but the idea is parent_id and base_id should be present together for any backend16:32
jungleboyjwhoami-rajat:  Correct.  That is a known issue that needs to get resolved.16:32
smcginnisGet rid of the new column and all the unnecessary shifting of code and it might be easier to see.16:32
daikk115in case we want create multile full backup and multiple incremental/diff from them16:32
geguileodaikk115: I believe we can do that now, since we have the link to the parent16:32
e0negeguileo: +1\16:33
smcginnisdaikk115: Oh, so you want to have the option to create a differential backup from a full backup other than the most recent?16:33
daikk115one incremental can be parent of other incremental16:33
daikk115right? geguileo16:33
geguileoso we can have N backups to 1 parent backup relationship16:33
geguileodaikk115: yes, it can be16:33
daikk115so we don't know which full backup is base full backup for new incremental/diff?16:33
geguileodaikk115: actually that's how it works right now, the parent is the latest backup16:34
geguileothat's why it's incremental and not differential at the moment16:34
geguileoif we want to allow user to specify the parent, we would just have to modify the API, and a couple of places16:34
smcginnisWIth incremental, it's always the last backup. Seems odd to want to do an incremental or differntial from something other than the last full backup.16:34
geguileoincremental is always from the last backup (incremental or full)16:35
daikk115smcginnis, for Ceph backup, it always create new snap in first full16:35
geguileodifferential is from the last full16:35
daikk115did not create snap in latest full backup16:35
smcginnisSo I think 1) this needs a spec actually spelling out what you're trying to accomplish here clearly, 2) prototype code for more than just ceph.16:35
geguileodaikk115: the snapshot is to set a marker16:35
geguileodaikk115: so we can then request the diff between that point and current point16:35
geguileoI think we are going into implementation details16:35
jungleboyjsmcginnis:  ++16:36
geguileosmcginnis: +116:36
jungleboyjToo complicated to just pound out in code.16:36
smcginnise0ne: Are you still working on this: https://specs.openstack.org/openstack/cinder-specs/specs/stein/generic-backup-implementation.html16:36
daikk115geguileo, but cinder did not allow to delete the first full(last week full backup)?16:36
e0neit's a day when I always agree with smcginnis16:36
smcginnis:)16:36
jungleboyje0ne:  Good place to be.16:36
geguileoI think it's not too complicated if you are very familiar with the code, but complex otherwise, too many variables/options16:37
*** pcaruana|elisa| has quit IRC16:37
e0nesmcginnis: yep. I'll publish patches early next week to statr discussion16:37
jungleboyj:-)16:37
geguileodaikk115: you cannot delete it because you have dependent backups (the incremental ones)16:37
smcginnise0ne: Awesome!16:37
jungleboyje0ne:  ++16:37
e0neI rebased my old patch and split it into the chain16:37
smcginnisOh nice.16:38
daikk115geguileo, we should let new incremental backup know that it should be depend on last full backup not the first full is not16:38
geguileodaikk115: once we fix the RBD problem and you can create full backups whenever you want, then you will be able to delete all incremental and the old full16:38
e0neneed to test it more and clean up before publishing16:38
daikk115first full backup16:38
geguileodaikk115: that's how it works right now!16:38
geguileodaikk115: it's not based on the last full, but the last incremental16:38
geguileodaikk115: in ALL backup drivers16:38
daikk115that is not real use case we have which smcginnis also know16:39
*** ttsiouts has quit IRC16:39
geguileodaikk115: I'm saying what we HAVE, not want you would like to have (aka your use case)16:39
*** ttsiouts has joined #openstack-meeting16:39
geguileodaikk115: if that's not the case, then it would be a bug in the RBD driver (because it would be doing differential instead of incremental)16:39
geguileoand that's not what it used to do from the start, so it would have been changed at some point16:40
geguileounnitentionally16:40
smcginnisdaikk115: Let's get a spec written up that we can all read and make sure we're talking about the same solution.16:40
smcginnisdaikk115: And just to reiterate, it needs to be something that doesn't only apply to how ceph works.16:40
jungleboyjI think that sounds like a good plan since this is not clear right now.16:40
jungleboyjsmcginnis: ++16:40
geguileodaikk115: sounds good16:40
geguileosmcginnis: +116:41
daikk115smcginnis, the above link is not the same problem.16:41
smcginnisWhat above link?16:41
jungleboyj#action daikk115  To create a Spec for discussion.16:42
daikk115smcginnis, Oops, sorry, never mind16:42
daikk115jungleboyj, Ok, I will to that16:42
daikk115s/to/do16:42
enriquetaso#info enriquetaso16:43
smcginnisenriquetaso: You have been informed. :)16:43
jungleboyj?16:43
e0ne:)16:43
smcginnisjungleboyj: I think we can move on.16:43
jungleboyjenriquetaso:  Info16:43
daikk115ok :D thanks16:43
jungleboyjWith pleasure.16:43
enriquetasosorry, i'm late16:43
jungleboyjenriquetaso:  Ah.  No problem.  Welcome to the party.16:44
daikk115enriquetaso, hi16:44
*** ttsiouts has quit IRC16:44
jungleboyj@!16:44
_pewp_jungleboyj (◍˃̶ᗜ˂̶◍)ノ”16:44
jungleboyjSo, moving on.16:44
jungleboyj#topic User Feedback Etherpad.16:45
*** openstack changes topic to "User Feedback Etherpad. (Meeting topic: Cinder)"16:45
jungleboyjCan anyone get to the etherpad right now>16:45
smcginnisThey just upgraded the instance I think.16:45
e0ne#link https://etherpad.openstack.org/p/BER-Cinder_User_Survey_Responses16:46
jungleboyjSo, I have a cached copy here.  So let me at least share what I did.16:46
daikk115jungleboyj, I can but quite slow16:46
jungleboyjOk.16:47
enriquetasohi daikk115 , geguileo thanks for discuss the incremental option for backups16:47
jungleboyjSo, I got the translated feedback for the user feedback survey from the Foundation.16:47
smcginnisjungleboyj: Thanks for categorizing into common themes. That helps.16:47
geguileojungleboyj: I can't get to it, and the outing planning seems to have no content... r:-??16:47
jungleboyjgeguileo:  Correct at the moment.16:48
jungleboyjsmcginnis:  You are welcome.16:48
geguileojungleboyj: OK, I can access now  :-)16:48
geguileojungleboyj: thanks16:48
smcginnisInfra is aware of the issue.16:48
jungleboyjAs smcginnis has idicated I looked through the feedback and documented the common themes for the comments.16:48
jungleboyjFell into 12 categories.16:48
jungleboyjI have put some initial thoughts in there but given that all of you have expertise in different areas here I would appreciate all of you adding responses here.16:49
jungleboyjWhat I am hoping is that we will get a good number of people in the forum summit session that maybe can help us understand the feedback given that it is so vague.16:50
*** gyee has quit IRC16:50
jungleboyjThey want backup/disaster recovery improvements but they don't say what.16:50
jungleboyjI think we have already addressed the question of automated backup processes.16:51
jungleboyjI think all of the requests for multi-attach support is likely to be Ceph users.16:51
jungleboyjThat short-coming is being addressed.  Correct?16:51
e0nejungleboy: we did. everybody can use mistral for such automation16:51
*** jgriffit1 is now known as jgriffith16:53
jungleboyjSo, I think, looking at the list that we have a number of things in flight that address the comments.16:53
smcginnis#link https://review.openstack.org/#/c/595827/ Ceph multiattach spec16:54
jungleboyjIf you know of details/patches/specs that apply to the comments please add them here so that we can be prepared to address comments/questions from anyone that makes it to the Forum Session.16:54
jungleboyjsmcginnis: Case in point.  Thank you!16:54
jungleboyjWow.  Now weird things happening in etherpad.16:55
jungleboyjAnyone have anything else there they can update now?16:55
*** diablo_rojo has joined #openstack-meeting16:56
smcginnisDid we do read only multiattach?16:56
smcginnisI remember that being something we were going to follow on the initial work to do, but I didn't think anything had been done yet.16:57
jungleboyjsmcginnis: Hmmm, you know.  I think that is another things that we just talked about.16:57
jungleboyjSo, that one may be one that need to be given some priority.16:58
*** ash_williams is now known as ash_sawing16:59
jungleboyjOk.  Well.  We have run out of time.16:59
smcginnisSomeone tell jgriffith he needs to work on multiattach some more.16:59
jungleboyjHope everyone has a safe and happy Halloween.16:59
jungleboyjsmcginnis:  ++16:59
jungleboyjThanks for joining the meeting and hope to talk to you all again next week!16:59
smcginnis🎃🎃🎃16:59
jungleboyj:-)17:00
daikk115see you :D17:00
jungleboyjThanks!17:00
jungleboyj#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Wed Oct 31 17:00:23 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2018/cinder.2018-10-31-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2018/cinder.2018-10-31-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2018/cinder.2018-10-31-16.01.log.html17:00
*** jbernard has left #openstack-meeting17:01
*** woojay has left #openstack-meeting17:01
*** e0ne has quit IRC17:08
*** walshh__ has joined #openstack-meeting17:08
*** ganso has left #openstack-meeting17:09
*** eharney has joined #openstack-meeting17:10
*** Swami has joined #openstack-meeting17:12
*** shrasool has joined #openstack-meeting17:22
*** dustins has joined #openstack-meeting17:26
*** Leo_m has quit IRC17:29
*** shrasool has quit IRC17:33
*** electrofelix has quit IRC17:38
*** aojea has quit IRC17:40
*** iyamahat has quit IRC17:42
*** Leo_m has joined #openstack-meeting17:43
*** gyee has joined #openstack-meeting17:44
*** yamahata has quit IRC17:44
*** sambetts is now known as sambetts|afk17:46
*** a-pugachev has quit IRC17:53
*** iyamahat has joined #openstack-meeting17:59
*** walshh__ has quit IRC18:04
*** ash_sawing has quit IRC18:07
*** mriedem has joined #openstack-meeting18:11
*** rosmaita has left #openstack-meeting18:11
*** mriedem is now known as ash_williams18:11
*** ralonsoh has quit IRC18:17
*** yamahata has joined #openstack-meeting18:20
*** cloudrancher has quit IRC18:23
*** cloudrancher has joined #openstack-meeting18:23
*** e0ne has joined #openstack-meeting18:31
*** e0ne has quit IRC18:32
*** psachin has quit IRC18:36
*** tssurya has quit IRC18:39
*** daikk115 has quit IRC18:42
*** jamesmcarthur has quit IRC18:52
*** jamesmcarthur has joined #openstack-meeting18:52
*** jamesmcarthur has quit IRC18:57
SotK#startmeeting storyboard19:00
openstackMeeting started Wed Oct 31 19:00:57 2018 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
fungihey howdy!19:00
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
diablo_rojoHello!19:01
*** jamesmcarthur has joined #openstack-meeting19:01
SotK#link https://wiki.openstack.org/wiki/Meetings/StoryBoard#Agenda_for_next_meeting Agenda19:02
*** iyamahat has quit IRC19:02
SotK#topic Migration Updates19:02
*** openstack changes topic to "Migration Updates (Meeting topic: storyboard)"19:02
SotKany updates this week diablo_rojo?19:02
*** iyamahat has joined #openstack-meeting19:03
* fungi hopes we're not keeping SotK from evening hallowe'en festivities19:03
*** zaneb has quit IRC19:03
diablo_rojoSadly not, just that I still haven't had time to dig into the LP API to figure why things are being cut short of the full migration19:04
diablo_rojoYeah we can make this quick19:04
fungifull neutron migration, right19:04
diablo_rojoRight19:04
clarkbOn the attachment spec I think it would be helpful for storyboard to describe the requirements it feels it has for this feature. Then we can build around that rather than going with whatever infra could do today. THis helps inform both directions of the needs and limitations I think.19:04
* fungi thinks clarkb is jumping ahead on the agenda ;)19:05
* diablo_rojo thinks so too19:05
clarkbsorry19:05
diablo_rojoAttachments are just so exciting :019:05
clarkb(that was my update)19:05
clarkbthey are!19:06
SotKdiablo_rojo: no worries, I've also not had much time this week19:06
SotK#topic Berlin19:07
*** openstack changes topic to "Berlin (Meeting topic: storyboard)"19:07
clarkb(I now see the topic was specifically migration updates)19:07
diablo_rojoWRT the neutron migration, I am kind of prioritizing the attachment spec and moving that forward higher. Hence the lack of progress.19:07
diablo_rojoclarkb, lol19:07
SotKyeah that makes sense to me19:07
*** iyamahat_ has joined #openstack-meeting19:07
diablo_rojoNothing new on the Berlin topic, just wanted to make sure those watching knew about it.19:08
*** iyamahat has quit IRC19:08
*** jamesmcarthur has quit IRC19:08
*** jamesmcarthur has joined #openstack-meeting19:09
SotK#topic Story Attachments19:09
*** openstack changes topic to "Story Attachments (Meeting topic: storyboard)"19:09
diablo_rojoI could send something to the ML telling people to bring last concerns to the Berlin forum session?19:09
diablo_rojoJust a thought19:10
clarkbdiablo_rojo: ++ and remind them that storyboard will be there is probably worthwhile19:10
SotKdiablo_rojo: yep that sounds worthwhile19:10
* diablo_rojo adds that as a todo for today19:10
diablo_rojoAnywho, attachment things now :)19:11
fungiso on the attachments spec, i feel like the actual requirements are fairly nominal/flexible, but a lot of that has to do with how we design the feature19:11
fungistorage requirements i mean19:11
clarkbya I'm sure we can make something work. But I think it would be valuable to undersatnd how storyboard would like to see it work19:11
clarkbThen see if the hosting can accomodate that (rather than the other way around)19:11
fungii'm also curious as to whether the comments i posted make sense, with regards to a simpler way to go about this security-wise19:12
diablo_rojofungi, it mostly made sense, I think I was failing to see how it was different than the undiscoverable URIs?19:12
fungiif an attachment is only reachable by knowing its url which includes a uuid someone would have to guess or otherwise be provided, is that sufficiently secure?19:12
*** erlon has quit IRC19:13
diablo_rojoI would guess so? but I certainly am no security expert19:13
fungiother parts of the spec described temporary urls and/or proxying all the content requests through storyboard19:13
SotKI think the part I was misunderstanding from your idea was that the URL is determined at upload time and recorded in storyboard, rather than being generated on demand19:13
SotKI think this way sounds much easier to implement19:13
SotKbut I don't really feel entirely qualified to comment on its security19:14
SotKI don't see anything immediately wrong19:14
persiaOne of the differences is that if there is a magic open URI, that can be pasted to e.g. IRC.  Conversely, if control is managed by storyboard directly, pasting the URI doesn't disclose anything.  Personally, I think having a separate storage system (with guessable UUIDs) is probably sufficiently secure for task tracking, but others may be more concerned.19:14
clarkbThe two big things seem to be controllable URIs and indexable content19:15
fungiyeah, my take is that if someone can leak the persistent url to the attachment, then they can just as easily leak the contents of the attachment or other aspects of the private story anyway19:15
persiaWhat is the benefit of indexable content?19:15
clarkbpersia: you can store adsvertisements or similar that show up in google seraches19:15
persiafungi: Absolutely.19:15
persiaclarkb: I consider that a detriment, but I can see the potential for abuse.19:16
clarkbthis is the sort of spamming we've seen on our wiki19:16
fungiyeah, i think what clarkb means is we don't want them indexable. i mentioned some possible solutions to that as well19:16
persiaHas anyone asked #launchpad how they deal with the potential for spam?19:16
diablo_rojopersia, I have not19:17
fungidoesn't prevent someone from posting the url to an attachment somewhere else where it can then be indexed by a search engine i guess, but these days that's a less attractive prospect19:17
diablo_rojobut that would be useful information19:17
fungibasically if they already have somewhere unpoliced to post the url, then they'd just post the raw content there instead19:17
persiaMy vague memory is that they have a policy and a means to delete things that seems to work.  Dunno about volume of LP-hosted projects vs. OSF-hosted projects.19:17
fungithat's what we saw happening with our wiki, fwiw19:18
*** iyamahat_ has quit IRC19:18
diablo_rojofungi, posting advertisemnets or logs of things?19:19
fungii do agree with clarkb that it's something we should keep an eye out for, and don't think it should really factor too much into the design19:19
fungidiablo_rojo: these days it's mostly people posting urls to scams or phone numbers for the same19:19
diablo_rojoGot it.19:19
fungiso that when you google "miscrosoft office support" you get friendly results for a phone number to call where they'll take your credit card info19:20
clarkbfungi: from the design side if say swift publicly served content doesn't allow you to not index (or alternatively index at all) that is something that should factor in? I agree ti shouldn't be the main consideration, just another thing to check when considering options19:20
fungiyes, if the object store conveniently provides a public index to all content you serve from it, that would be something to discount it19:21
fungii don't think swift forces a public index of your objects, for precisely this reason19:21
diablo_rojoSomething we don't want.19:21
fungibasically, under my suggested design, we would want storyboard to privately maintain its index of (persistent public) object urls, and would not want the object store to serve an index of those19:22
clarkbfungi: makes sense to me19:23
fungiwe also would want to be sure said urls couldn't be enumerated in any achievable amount of time19:23
*** diablo_rojo_phon has joined #openstack-meeting19:23
fungiby someone who lacks access to that index19:23
* SotK thinks that this sounds like the best solution of the ones that have been suggested19:24
persiaIndeed19:24
fungianyway, i didn't want to monopolize the discussion, just want to be sure we don't go off overengineering complex solutions where simpler ones are possible19:24
clarkb++19:25
*** ash_williams is now known as mriedem_away19:25
diablo_rojo_phonLost connection on laptop. But I'll go back through meeting logs and get the spec updated with this approach.19:25
fungithanks diablo_rojo_phon! and i hope your laptop didn't have too much candu19:25
fungicandy19:25
SotKmakes sense, I don't really see any worthwhile benefit to the more complicated suggestions I noted now19:25
diablo_rojo_phonI had most comments addressed aside from this section so I should have it up today ish.19:26
SotKnice, thanks :)19:26
*** diablo_rojo has quit IRC19:26
fungimy old life as a security wonk mostly involved reminding people that complex security solutions are really just increased opportunities for vulnerabilities19:26
diablo_rojo_phonMaintenance is in my apartment and flipped the breakers so I haz no internets.19:27
*** erlon has joined #openstack-meeting19:27
SotKI think that basically covers attachments then19:27
SotK#topic In Progress Work19:27
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:27
diablo_rojo_phonCool :)19:28
fungiand you're sure these aren't neighborhood hooligans disguised as maintenance workers?19:28
diablo_rojo_phonfungi: pretty sure since he's fixed a bunch of other things in the apartment previously19:28
diablo_rojo_phonI have two patches that could use reviews.19:28
persiaIt's a long con then?19:28
fungioffer candy anyway19:28
clarkbcould be a really good costume19:29
diablo_rojo_phonHigh level of dedication just to flip my breakers.19:29
* SotK failed to get anywhere with his backlog of reviews to do, I'll attempt to get to them this week19:29
* diablo_rojo_phon doesn't have any candy in the apartment19:29
fungii only managed to review the attachments spec, fwiw19:30
fungidiablo_rojo_phon: shots then?19:30
diablo_rojo_phonThanks SotK :) We are all juggling a lot of stuff so we understand19:30
diablo_rojo_phonfungi: could do that, there's no shortage of alcohol here lol19:30
fungiwhen i lived in raleigh, there was a townhouse of russians across the street who always set up a bar in their driveway and served vodka shots to the parents taking their kids around19:30
fungiit was pretty awesome19:31
diablo_rojo_phonThat is excellent.19:31
diablo_rojo_phonSotK: I don't think I got around to reviewing your patch either so I guess it's only fair lol19:31
SotKha, that's a great idea19:31
SotKI don't think I have enough alcohol around to do it though19:32
SotKdiablo_rojo_phon: no worries :)19:32
SotKI think folk have mostly learnt the workaround for the bug that patch fixes at this point19:32
* diablo_rojo_phon thought about sharing a photo and decided that proof doesn't need to exist on the internet.19:32
SotKor at least, I've not noticed anyone complain recently19:32
diablo_rojo_phonStill nice to get it fixed SotK :)19:33
SotKindeed19:33
*** erlon has quit IRC19:35
diablo_rojo_phonWas someone investigating what happened with fatema's patch?19:35
SotKI was going to but also didn't get around to that19:35
diablo_rojo_phonWhat say we end early to do some of these things?19:36
diablo_rojo_phonUnless someone else has something to talk about?19:36
SotKsounds good to me19:37
SotKI don't have anything else19:37
fungii'll review some storyboard changes19:37
diablo_rojo_phonOh! clarkb is there gonna be an infra dinner at the summit?19:37
diablo_rojo_phonfungi: much appreciated!19:37
clarkbdiablo_rojo_phon: I haven't put together one19:39
clarkbI guess I can take a look. Mostly its a huge pain to figure out reservations for a large group and half the time they want a deposit19:40
clarkbDenver is easy because beer garden and nice weather. Berlin probably has the beer gardens but not the nice weather19:40
fungiberlin doesn't seem to have actively staffed biergartens in november19:41
fungiyou need a bierstube instead, and seating will be more complicated19:41
clarkbWe can probably do an informal thing? I expect a smaller but also differentish group (frickler and ajaeger but no paul or david or robyn etc)19:41
clarkbI'll send out an email trying to schedule an informal thing with the expectation that different tables/locations may happen19:42
clarkbI think that is easiest19:42
fungiwe can say "everybody meet at $venue and we can try to get tables nearish to each other"19:42
clarkb++19:42
fungibut not actually organize anything19:42
diablo_rojo_phonThat works.19:43
*** jamesmcarthur has quit IRC19:44
*** e0ne has joined #openstack-meeting19:44
*** jamesmcarthur has joined #openstack-meeting19:45
*** e0ne has quit IRC19:45
*** diablo_rojo has joined #openstack-meeting19:45
*** awaugama has quit IRC19:46
SotKok, lets end the meeting19:47
SotKthanks for coming folks :)19:47
SotK#endmeeting19:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:47
openstackMeeting ended Wed Oct 31 19:47:21 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2018/storyboard.2018-10-31-19.00.html19:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2018/storyboard.2018-10-31-19.00.txt19:47
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2018/storyboard.2018-10-31-19.00.log.html19:47
diablo_rojoThanks SotK!19:47
fungithanks for chairing, SotK!19:47
clarkbI found a 100% vegan brew pub19:48
clarkbhttps://vaust.berlin/ if that helps anyone with food while in berlin19:48
diablo_rojoclarkb, should probably tell hogepodge19:50
*** apetrich has quit IRC19:50
*** erlon has joined #openstack-meeting19:51
*** raildo has quit IRC19:53
*** iyamahat_ has joined #openstack-meeting20:02
*** apetrich has joined #openstack-meeting20:04
hogepodge?20:09
clarkbhogepodge: https://vaust.berlin/ vegan brewpub thing in berlin20:09
*** apetrich has quit IRC20:14
*** liuyulong has quit IRC20:18
*** raildo has joined #openstack-meeting20:22
*** raildo has quit IRC20:22
*** jamesmcarthur has quit IRC20:24
*** e0ne has joined #openstack-meeting20:30
*** imacdonn has quit IRC20:34
*** imacdonn has joined #openstack-meeting20:34
*** jamesmcarthur has joined #openstack-meeting20:38
*** jamesmcarthur has quit IRC20:43
*** e0ne has quit IRC20:50
*** timburke has joined #openstack-meeting20:50
*** shrasool has joined #openstack-meeting20:58
*** patchbot has joined #openstack-meeting20:59
notmynameswift team meeting time20:59
notmyname#startmeeting swift20:59
openstackMeeting started Wed Oct 31 20:59:56 2018 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.20:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:59
*** openstack changes topic to " (Meeting topic: swift)"20:59
openstackThe meeting name has been set to 'swift'21:00
notmynamewho's here for the swift team meeting?21:00
mattoliverauo/21:00
timburkeo/21:00
kota_hi21:00
*** zaneb has joined #openstack-meeting21:00
rledisezo/21:00
notmynamewelcome zaneb21:00
zanebo/21:00
notmynameclayg: tdasilva: ping21:00
claygohai!21:01
tdasilvahello!21:01
notmynamezaneb: glad you could make it. do you have any particular schedule restrictions? (leaving early, etc)21:01
notmynameagenda this week is at...21:01
notmyname#link https://wiki.openstack.org/wiki/Meetings/Swift21:01
zanebnotmyname: nope, I can be here for the duration21:01
notmyname"normal" stuff, but the main topic is the tc vision proposal that zane is championing21:02
notmynamezaneb: great!21:02
notmyname#topic tc vision document21:02
*** openstack changes topic to "tc vision document (Meeting topic: swift)"21:02
notmyname#link http://lists.openstack.org/pipermail/openstack-dev/2018-October/136031.html21:02
notmyname#link https://review.openstack.org/#/c/592205/21:03
patchbotpatch 592205 - governance - [DRAFT] Add a Technical Vision statement - 4 patch sets21:03
notmynameok, so the first question is "who actually read it?" :-)21:03
zaneb:D21:03
claygI skimmed it - but then I wanted to start making comments - so I stopped21:03
timburkei read... some of it, anyway21:03
kota_:P21:03
claygthe patch seemed fine, but then people start talking - it makes me want to drink21:04
notmynameheh21:04
notmynameI think the frustrating part of this kind of thing is that it is very meta. it's not about solving problems; it's for solving problems about how we solve problems.21:04
claygsome people are better at that sort of thing21:04
timburkei remember thinking "event notifications where appropriate" could use some fleshing out -- that's definitely something that swift's been interested in, but it's hard21:04
notmynamerledisez: tdasilva: kota_: did you get a chance to read it?21:05
timburkeBidirectional Compatibility seemed to be stepping outside of the service-only purview21:05
timburkeit's on the client to figure out how to maintain compatibility with older services, just as it's on the services to figure out how to maintain compat with older clients21:05
kota_briefly, not get in detail.21:05
rlediseznotmyname: not really, I'm going through it right now briefly21:05
notmynameok21:05
zanebtimburke: it does apply to some stuff like Heat and Mistral on the service side21:05
notmynamehere's my summary ( zaneb, please correct me if I get things grossly wrong)21:06
notmynametc want's to write down some guidelines used for defining the "in" and "out" for openstack. it's doing this by describing and defining basic things about cloud infrastructure and then declaring them to be in scope for openstack. so that if project x shows how they match one or more of these basic principles, they are then in scope for being in openstack21:06
timburkefelt like fault-tolerance/high-availability might be another good pillar (and just so happens to be something we're good at ;-)21:06
zanebtimburke: and arguably to e.g. microversions and stuff in APIs21:06
notmynameswift often has a different perspective on openstack because we pioneered "independently deployable" and also have a data-centric API (instead of provisioning). this document describes several cloud principles that swift does, so zane says this should finally put that debate to bed21:06
*** shrasool has quit IRC21:07
notmynamezaneb: is that about right? maybe my understanding of the overall purpose is more limited than you have in mind21:07
zanebnotmyname: that's a fair summary, although there are other reasons for doing it also21:07
notmynameyes. please share :-)21:07
zanebone is, as you said, that the TC currently has no standard for judging which projects should be allowed to join, and it's a pain point for us21:08
zanebbut another is that we want to give projects something they can refer to when making design decisions21:08
mattoliverauI've skimmed it, seems notmyname you've had some interesting discussions in gerrit about some definitions21:08
notmynamemattoliverau: I tried to avoid the biggest traps, I think :-)21:09
zaneband a lot of that stuff have previously only been at the level of folklore that people picked up by osmosis, if at all21:09
notmynamezaneb: meaning that if eg we have a new feature we are designing, we could compare it against this list to see if it's good or bad?21:09
notmynamewell, appropriate or not21:09
zaneband it'd be nice to have a kind of framework within which the services sit so that the people independently designing them eventually produce something coherent21:10
notmynamethat last thing sounds terrific. design a system so that independent parties converge on a cohesive whole. (also sounds really hard)21:10
zanebyes, really hard to get it happen on purpose, but absolutely not going to happen by accident :)21:11
clayg^ that's rich21:11
timburkedesigning converging systems in general is hard -- see our troubles with replication, dark data, and ghost listings :P21:11
notmynamezaneb: so are you thinking this document will guide (or advise) feature development?21:12
timburkeit's even worse when the system's made up of people instead of programs21:12
zanebnotmyname: to some extent, yes, but to different degrees for different projects21:12
zaneband a lot of it is stuff that we old-timers already know, but hadn't written down in one place21:13
notmynameTBH I'm struggling with ... well, I'm struggling with how to express my thoughts via text chat :-)21:13
mattoliveraumeme? interpritive dance?21:14
notmynamelol21:14
clayglol21:14
zanebone thing I personally would love to get is events out of every service. imagine if we'd had Storlets but for everything 5 years ago - we'd have invented Lambda before AWS did21:15
notmynameI'm very concerned when someone starts defining boundries in the openstack ecosystem, because swift has oftentimes been put in the "other" group. that's why I pay attention to these sorts for discussions. but on the other hand, it's hard to see how it matters on an ongoing day-to-day basis21:16
claygI think that might be baggage - I feel more in-crowd cool kids these days21:16
notmynameclayg: it totally could be21:17
zanebfwiw I think everyone else has a lot to learn from Swift, and allowing it to be defined as 'other' has prevented the rest of OpenStack from doing that as much as we should21:17
zanebso as I said in the email, I hope drawing the boundary where it is in this doc will help people to *stop* seeing Swift as 'other'21:18
clayg:hugs:21:18
notmynameclayg: that's the emoji thing I'm looking for! :-)21:19
claygzaneb: what would be most helpful from "us" (and by us I mostly mean other people besides me)21:19
clayg... but especially from notmyname :P21:19
clayg:hugs:21:19
notmynameheh21:19
zaneblol21:19
claygmattoliverau!  mattoliverau is helpful21:20
mattoliveraulol21:20
kota_lol21:20
* notmyname waits for zaneb before asking more questions21:20
zanebthe most helpful thing for me is people engaging with the review, because in the end this will be successful if people feel like we all came up with it together, and it's not something handed down from the TC21:21
notmynamezaneb: the outreach you're doing to specific projects in great. thank you21:22
zanebif I start typing gibberish, it's because a miniature human is attacking the keyboard21:22
zanebI mean, more gibberish than usual21:22
notmynameclayg: timburke: you both said you had some comments but help back from posting them21:22
notmynamewere they about the doc in general, any specifics in it, or just the commentary about the doc?21:23
mattoliveraulol21:23
claygnotmyname: honestly 9/10 of my "comments" were "hell, yeah!" the others were like "no YOU'RE WRONG, this is good."21:23
claygI'm paraphrasing21:24
zaneblol21:24
timburkei think mostly just the comments i made here. seemed like actually posting would mostly add more noise (to what will definitely be a noisy review) rather than help, but i could be wrong21:25
zanebtimburke: you mentioned fleshing out the 'event notifications where appropriate' - would be very interested in what sort of stuff you'd like to see there21:25
timburkemostly just what "where appropriate" means21:26
timburkebecause i honestly don't know where the appropriate line would be in swift21:26
notmynametimburke: in my experience with openstack, it's very good to have noisy reviews early in order to get a right version of the doc from the start (but like clayg, that may be my own historic baggage)21:26
zanebthat section is kind of toned down because that is TOTALLY MY HOBBY HORSE and I would write the whole thing about just that if I could ;)21:26
timburke"on every swift operation" feels *incredibly* noisy, like we'd almost certainly cause whatever message queue we're putting those notifications in to fall over21:27
*** dkrol has quit IRC21:27
claygTIL https://en.wikipedia.org/wiki/Hobby_horse#Other_meanings21:27
zanebclayg: it's fortunate that didn't take a much darker turn :D21:28
*** mhen has quit IRC21:28
zanebtimburke: maybe we should let users filter at the source?21:29
notmynamezaneb: do you think this document will take a turn towards more "provisioning-only" language? one commenter seemed to want to move it in that direction21:29
timburkenotmyname: i was noticing that too...21:29
zanebnotmyname: by that you mean just-Nova-providing-a-VPS?21:30
zanebaka the "free VMWare" model?21:30
notmynamemore generally, like "you ask openstack to give you resources that you can then use directly"21:30
zaneboh, ok21:31
notmynameI have two general concerns with things that try to define openstack. the first is provisioning vs "data-plane" api disctinctions. the second is a focus on compute-only or compute-first language21:31
*** mhen has joined #openstack-meeting21:33
clayg... so many half typed sentences ...21:33
zanebimo there's such a mixture of different things that it's never going to make sense to say openstack is control-plane-only21:33
notmynamelol21:33
claygI actually need to cut out (happy halloween everybody!)21:33
kota_lol21:33
timburkenotmyname: yeah, i kinda want to point kevin at https://governance.openstack.org/tc/reference/principles.html#openstack-primarily-produces-software and say that while others may reimplement the swift protocol (we have no control over that, they can make their own decisions), that's not Swift21:33
clayg+1 to everything zaneb says21:33
notmynameclayg: thanks for joining while you could. I definitely appreciate your comments and perspective21:34
claygnotmyname: was there anything else on the agenda?21:34
claygrledisez: ohai!?21:34
claygI'll read the logs21:34
zanebthat comment from Kevin was interesting food for thought, but I don't think it's going to change the direction of the document in any major way21:34
notmynameclayg: nah, jsut "normal" stuff like "go land the s3api patches" and review losf :-)21:34
claygk21:34
claygl8r21:35
zanebclayg: thanks o/21:35
rledisezclayg: ohai???21:35
notmynamekota_: rledisez: what do you think about this doc (or this discussion)? we haven't heard from you yet21:35
timburkerledisez: don't worry, i speak clayg. "oh, hi there!" and in this particular context, "sorry we couldn't chat"21:36
rledisezso, i just read it. it is interesting, i'm not sure i see how it could drive everydays decissions about feature/implementation. if we need something, will we really restict ourself to what this document allow?21:37
rlediseztimburke: thx for the translation :D21:37
kota_notmyname: i have (probably) same concerns with you on the definition of the openstack because swift provides data-centric apis.21:37
notmynamerledisez: yeah, I completely agree about the feature development influence21:37
kota_and also, Storlets does...21:37
notmynamekota_: yeah. did you notice anything that gives you concern?21:38
rlediseznotmyname: but I like the turn it takes about the place of Swift inside Openstack21:38
kota_just a guideline could be fine but if it'll be restriction, I could not sure I could follow it, maybe?21:38
notmynamekota_: from what I understand of it, and from what zaneb has said, I do not expect there to be any definitions that turn in to "data-centric is bad"21:39
kota_notmyname: ok,21:39
zanebas far as features in Swift go, I'd be most interested in hearing if the things documented are consistent with the decisions about features you've made in the *past*, so we can hand the knowledge on to some of the newer teams21:40
kota_thanks for clarification.21:40
notmynamezaneb: ah, yes, that cuts to the chase21:40
kota_zaneb: that sounds nice21:41
notmynamezaneb: I question some of the "hardware virtualization" section. it mentions storage, but what we do with object storage is sortof hard to fit into a "storage virtualization" world. at least much harder than cinder21:41
zanebnotmyname: that reminds me, we should discuss you comment about regions, but not sure if this is the time21:41
notmynamezaneb: sure. we can discuss the regions in the review, I think. it doesn't seem like a major issue to me21:41
zanebok21:41
zanebnotmyname: IMHO hardware virtualisation is necessary for a cloud, but it also tends to scale in coarse-grained ways (from the application perspective)21:42
zanebso we need both that and things like Swift that provide more fine-grained scaling21:43
mattoliverauyeah, just the term regions means different things in Swift and keystone, they can fit together depending on your deployment topology but doesn't have to. We need a venn diagram :P Just like Swift containers and containers (though they don't overlap at all) :P21:44
notmynameyeah. the HW virtualization works well in the "free vmware" mindset. but swift (object storage) is really more about not thinking about hardware at all (from the app perspective). and that normally means the service is runnign on bare metal21:44
kota_i think it depends on the definition. IMO Swift API virtualized actual hardware and data placement.21:44
kota_we could assume.21:44
notmynamekota_: yeah :-). I think the definition is vague enough that we could make what swift does fit in to it. swift abstracts hard drives. you can swap them out and everything just keeps working.21:45
timburkenotmyname: i think that whole section doesn't really apply, because we don't21:45
timburkehave a service "provided by a specialised piece of hardware"21:45
zanebkota_: you could say that about almost anything ;)21:45
notmyname"a hard drive"21:45
claygLol @ tburke is my opposite of Obama’s “Luther”21:46
zanebmy 2c: they're separate things; we need both in OpenStack21:46
notmynamezaneb: I'm not really sure what to do next. my summary of what we've said in here is that most people are mostly ok with it (or at least not too concerned about the current version). we have some smaller wording questions, but nothing that's very troubling21:47
notmynamezaneb: so to repeat what clayg said earlier, what do you need from us now? have we given you anything that will help you? do we need to do something else?21:47
notmynamebased on the comments from the rest of the team, I'm ok with putting my own +1 on it as a swift representative.21:48
zanebcomments on the review if you have changes to be addressed would be great21:48
zanebthere will be another patchset coming soon, but +1s on that would be great21:49
notmynameok. I'll wait until the next patchset21:49
zanebwe have a Forum session at the summit, so hoping to get folks along to that to discuss where we're at and what we need to do to finalise it21:49
* kota_ will be there.21:50
notmynameok. I'll look for that on the schedule21:50
notmyname(my time in berlin is a bit limited)21:50
*** rbudden has quit IRC21:50
zaneb#link https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22818/vision-for-openstack-clouds-discussion21:50
notmynameok, last few minutes (thanks for being patient with a longer meeting this week)21:51
zanebreally appreciate everyone's input, thank you!21:51
notmynamezaneb: thank you for taking the time to specifically ask us about this doc21:51
notmyname#topic other topics21:51
*** openstack changes topic to "other topics (Meeting topic: swift)"21:51
notmyname#link https://wiki.openstack.org/wiki/Swift/PriorityReviews21:52
notmynamepriority reviews page is looking pretty similar to where it's been21:52
mattoliverauthanks zaneb for coming, listening and taking the time, great work on the vision work21:52
notmynametimburke: I'm wondering about the s3api patches. I'd really like to land them soon. maybe if we threaten to jsut land them then maybe mattoliverau and kota_ will look at them? ;-)21:53
zanebmattoliverau: my pleasure, thanks!21:53
notmynamerledisez: I saw new patches (or patch sets) from alex about losf?21:53
*** erlon has quit IRC21:53
zaitcevtimburke was doing such a good job adapting proxy that at one point got my manager to write down a working py3 proxy as a checkpoint on 10/10. But now he's away doing god knows what that Swiftstack needs more... Like completely random things.21:53
kota_it looks 3 patches are remaining21:54
kota_for s3api in prioriry21:54
notmynamekota_: yeah21:54
mattoliverauYeah, sorry, I've joined a new virtual team (happens every 6 months or so) so been busy ramping up. So haven't been reviewing as much as I should. I'll make sure I find work time to devote to more reivews :)21:54
timburkenotmyname: merge 'em all!21:54
notmyname:-)21:54
rlediseznotmyname: maybe, tbh i was not focused on that. but as tim said, "merge 'em all!"21:54
timburkezaitcev: i think we *are* really close to a working py3 proxy (at least for some requests?)21:55
*** eharney has quit IRC21:55
timburkehaving tests that verify that will be interesting, though :-/21:55
kota_i think I could look at 2 patches w/o patch 592231 but only 592231 is still not sure it goes fine way...21:56
patchbothttps://review.openstack.org/#/c/592231/ - swift - s3api: Include '-' in S3 ETags of normal SLOs - 3 patch sets21:56
kota_i'd like to get another person's opinion for that21:56
notmynamekota_: ok. could you leave a comment with your concerns or questions in gerrit? right now only tdasilva is on it21:57
notmynameso between the two of you, maybe we can get it landed quickly21:57
kota_and sorry of my slow pace for the reviews, various things goes in work and private...21:58
kota_notmyname: ok21:58
notmynamekota_: do not worry. I completely understand21:58
*** apetrich has joined #openstack-meeting21:58
notmynamezaitcev: I also wanted to say thanks for your py3 work. it's often tedious and thankless and hard to see progress, but as you know it's important. so thanks for working on it21:59
notmynamezaitcev: also, good luck with IBM :-)21:59
mattoliverau^ +100 to both these things22:00
zaitcevnotmyname: I'm quite interested in IBM's public cloud, they have some storage running in there. Not sure if it's Swift or not.22:00
notmynamezaitcev: the softlayer stuff is still, I think. eveything else is cleversafe (spectrum scale is the name now, i think)22:00
notmynameok, we're at full time22:00
mattoliverauand I guess thats time.22:00
notmynamethanks for coming today22:01
notmynamethanks for working through the tc doc22:01
notmynameand thanks for your work on swift!22:01
notmyname#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"22:01
openstackMeeting ended Wed Oct 31 22:01:22 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-10-31-20.59.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-10-31-20.59.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-10-31-20.59.log.html22:01
*** zaitcev has left #openstack-meeting22:01
*** patchbot has left #openstack-meeting22:01
*** timburke has left #openstack-meeting22:01
*** jamesmcarthur has joined #openstack-meeting22:16
*** dustins has quit IRC22:17
*** diablo_rojo has quit IRC22:18
*** gyee has quit IRC22:19
*** jamesmcarthur has quit IRC22:21
*** ykatabam has joined #openstack-meeting22:26
*** mriedem_away has quit IRC22:44
*** diablo_rojo has joined #openstack-meeting22:50
*** erlon has joined #openstack-meeting22:59
*** erlon has quit IRC23:04
*** hongbin has quit IRC23:06
*** _alastor_ has quit IRC23:06
*** erlon has joined #openstack-meeting23:19
*** tpsilva has quit IRC23:22
*** ianychoi has joined #openstack-meeting23:35
*** diablo_rojo has quit IRC23:45
*** Swami has quit IRC23:48

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