Thursday, 2018-11-08

*** tetsuro has joined #openstack-meeting-alt00:01
*** dustins has quit IRC00:02
*** dhellmann has joined #openstack-meeting-alt00:07
*** gyee has quit IRC00:55
*** markstur has joined #openstack-meeting-alt00:56
*** dtrainor has quit IRC01:03
*** dtrainor has joined #openstack-meeting-alt01:04
*** dangtrinhnt_x has joined #openstack-meeting-alt01:12
*** Swami has quit IRC01:24
*** ayoung has quit IRC01:29
*** yamamoto has joined #openstack-meeting-alt01:45
*** dangtrinhnt_x has quit IRC01:46
*** diablo_rojo has quit IRC01:53
*** erlon_ has quit IRC02:10
*** markstur has quit IRC02:11
*** hongbin has joined #openstack-meeting-alt02:13
*** markstur has joined #openstack-meeting-alt02:39
*** markvoelker has joined #openstack-meeting-alt02:45
*** markvoelker has quit IRC02:45
*** cloudrancher has quit IRC02:45
*** markvoelker has joined #openstack-meeting-alt02:45
*** cloudrancher has joined #openstack-meeting-alt02:45
*** yamamoto has quit IRC02:49
*** markvoelker has quit IRC02:50
*** markvoelker has joined #openstack-meeting-alt02:55
*** fungi has quit IRC03:06
*** fungi has joined #openstack-meeting-alt03:09
*** markstur has quit IRC03:09
*** fungi has quit IRC03:10
*** iyamahat has quit IRC03:15
*** yamahata has quit IRC03:16
*** mrhillsman has joined #openstack-meeting-alt03:20
*** fungi has joined #openstack-meeting-alt03:40
*** fungi has quit IRC03:41
*** fungi has joined #openstack-meeting-alt03:45
*** sambetts|afk has quit IRC04:11
*** sambetts_ has joined #openstack-meeting-alt04:18
*** janki has joined #openstack-meeting-alt04:36
*** radeks_ has joined #openstack-meeting-alt04:39
*** apetrich has quit IRC04:45
*** apetrich has joined #openstack-meeting-alt04:46
*** iyamahat has joined #openstack-meeting-alt04:48
*** yamahata has joined #openstack-meeting-alt05:27
*** munimeha1 has quit IRC05:28
*** tetsuro has quit IRC05:33
*** yamamoto has joined #openstack-meeting-alt05:45
*** hongbin has quit IRC06:02
*** diablo_rojo has joined #openstack-meeting-alt06:20
*** bswartz has quit IRC06:35
*** dpawlik has joined #openstack-meeting-alt07:04
*** tssurya has joined #openstack-meeting-alt07:23
*** rdopiera has joined #openstack-meeting-alt07:24
*** slaweq has joined #openstack-meeting-alt07:39
*** alexchadin has joined #openstack-meeting-alt07:39
*** yamamoto has quit IRC07:46
*** yamamoto has joined #openstack-meeting-alt07:46
*** yamamoto has quit IRC07:47
*** bnemec has quit IRC08:00
*** diablo_rojo has quit IRC08:08
*** iyamahat has quit IRC08:13
*** jtomasek has joined #openstack-meeting-alt08:18
*** bnemec has joined #openstack-meeting-alt08:26
*** yamamoto has joined #openstack-meeting-alt08:34
*** yamamoto has quit IRC08:40
*** yamamoto has joined #openstack-meeting-alt08:46
*** yamamoto has quit IRC08:47
*** yamamoto has joined #openstack-meeting-alt08:49
*** radeks has joined #openstack-meeting-alt09:11
*** radeks_ has quit IRC09:12
*** yamamoto has quit IRC09:13
*** derekh has joined #openstack-meeting-alt09:32
*** iyamahat has joined #openstack-meeting-alt09:45
*** dtrainor has quit IRC09:45
*** dtrainor has joined #openstack-meeting-alt09:46
*** e0ne has joined #openstack-meeting-alt09:50
*** ttsiouts has joined #openstack-meeting-alt09:54
*** yamamoto has joined #openstack-meeting-alt09:54
*** ttsiouts has quit IRC09:56
*** ttsiouts has joined #openstack-meeting-alt09:57
*** ttsiouts_ has joined #openstack-meeting-alt09:59
*** ttsiouts has quit IRC09:59
*** yamamoto has quit IRC10:00
*** yamamoto has joined #openstack-meeting-alt10:04
*** ttsiouts_ has quit IRC10:19
*** ttsiouts has joined #openstack-meeting-alt10:20
*** iyamahat has quit IRC10:23
*** ttsiouts has quit IRC10:24
*** tetsuro has joined #openstack-meeting-alt10:27
*** panda|off is now known as panda10:31
*** ttsiouts has joined #openstack-meeting-alt10:34
*** efried has quit IRC10:38
*** efried has joined #openstack-meeting-alt10:38
*** yamahata has quit IRC10:42
*** erlon_ has joined #openstack-meeting-alt11:08
*** yamamoto has quit IRC11:10
*** yamamoto has joined #openstack-meeting-alt11:14
*** ttsiouts has quit IRC11:35
*** ttsiouts has joined #openstack-meeting-alt11:35
*** ttsiouts has quit IRC11:38
*** ttsiouts_ has joined #openstack-meeting-alt11:38
*** tetsuro has quit IRC12:06
*** pbourke has quit IRC12:11
*** pbourke has joined #openstack-meeting-alt12:11
*** jcoufal has joined #openstack-meeting-alt12:13
*** ttsiouts_ has quit IRC12:14
*** ttsiouts has joined #openstack-meeting-alt12:14
*** raildo has joined #openstack-meeting-alt12:17
*** ttsiouts has quit IRC12:19
*** janki has quit IRC12:20
*** jcoufal has quit IRC12:35
*** ttsiouts has joined #openstack-meeting-alt12:52
*** ccamacho has quit IRC12:53
*** jcoufal has joined #openstack-meeting-alt12:55
*** ttsiouts has quit IRC12:56
*** ttsiouts has joined #openstack-meeting-alt12:57
*** panda is now known as panda|off12:59
*** e0ne has quit IRC13:03
*** yamamoto has quit IRC13:07
*** yamamoto has joined #openstack-meeting-alt13:09
*** dpawlik has quit IRC13:11
*** yamamoto has quit IRC13:14
*** ccamacho has joined #openstack-meeting-alt13:18
*** dpawlik has joined #openstack-meeting-alt13:26
*** janki has joined #openstack-meeting-alt13:29
*** dpawlik has quit IRC13:31
*** dustins has joined #openstack-meeting-alt13:35
*** e0ne has joined #openstack-meeting-alt13:37
*** ccamacho has quit IRC13:52
*** ccamacho has joined #openstack-meeting-alt13:53
*** jcoufal has quit IRC13:55
*** dpawlik has joined #openstack-meeting-alt13:58
*** yamamoto has joined #openstack-meeting-alt13:58
*** dpawlik has quit IRC13:59
*** ccamacho has quit IRC14:02
*** pbourke has quit IRC14:02
*** derekh has quit IRC14:02
*** bnemec has quit IRC14:02
*** jtomasek has quit IRC14:02
*** sambetts_ has quit IRC14:02
*** lhinds has quit IRC14:02
*** fanzhang has quit IRC14:02
*** ircuser-1 has quit IRC14:02
*** tonyb has quit IRC14:02
*** gibi has quit IRC14:02
*** pbourke has joined #openstack-meeting-alt14:02
*** fanzhang has joined #openstack-meeting-alt14:03
*** yamamoto has quit IRC14:03
*** dpawlik has joined #openstack-meeting-alt14:04
*** dpawlik has quit IRC14:04
*** sambetts_ has joined #openstack-meeting-alt14:04
*** jtomasek has joined #openstack-meeting-alt14:04
*** lhinds has joined #openstack-meeting-alt14:04
*** dpawlik has joined #openstack-meeting-alt14:04
*** tonyb has joined #openstack-meeting-alt14:07
*** gibi has joined #openstack-meeting-alt14:07
*** bnemec has joined #openstack-meeting-alt14:07
*** ttsiouts has quit IRC14:16
*** dtrainor has quit IRC14:17
*** ttsiouts has joined #openstack-meeting-alt14:17
*** dtrainor has joined #openstack-meeting-alt14:17
*** ttsiouts has quit IRC14:19
*** ttsiouts has joined #openstack-meeting-alt14:20
*** janki has quit IRC14:30
*** bswartz has joined #openstack-meeting-alt14:30
*** alexchadin has quit IRC14:39
*** ganso has joined #openstack-meeting-alt14:51
*** hongbin has joined #openstack-meeting-alt14:55
tbarron#startmeeting manila15:00
* bswartz looks around for manila ppl15:00
openstackMeeting started Thu Nov  8 15:00:52 2018 UTC and is due to finish in 60 minutes.  The chair is tbarron. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: manila)"15:00
openstackThe meeting name has been set to 'manila'15:00
bswartz.o/15:01
tbarronhey ben15:01
gouthamro/15:01
tbarronlet's wait a min ...15:01
tbarronping ganso15:01
gansohello15:01
tbarronping vkmc15:01
tbarronping dustins15:01
vkmco/15:01
tbarronping zhongjun15:02
dustinsAhoy15:02
tbarronping xyang15:02
tbarronping markstur15:02
tbarronping toabctl15:02
xyanghi15:02
tbarronping erlon15:02
tbarronpiing tpsilva15:02
xyangso early15:02
tbarronping amito15:02
tbarronxyang: so late :)15:03
tbarronI'm in Rome and it's time for an apertiv.15:03
tbarronHi all, let's get going.15:03
amitoHey15:03
tbarron#chair bswartz15:04
openstackCurrent chairs: bswartz tbarron15:04
amitotbarron: Oh in Rome already15:04
tbarronjust in case, and also15:04
tbarronbswartz will be picking up chair part way through15:04
tbarronI's even later for amito :)15:04
tbarronHello all!15:04
tbarron#topic announcements15:04
*** openstack changes topic to "announcements (Meeting topic: manila)"15:04
tbarronSummit is next week.15:05
*** dtrainor_ has joined #openstack-meeting-alt15:05
tbarronI think ganso, erlon, tpsilva, amito, vkmc, and myself will be there.15:05
tbarronanyone else?15:05
tbarronWe have a pretty good set of sessions involving manila topics:15:05
tbarron#link https://www.openstack.org/summit/berlin-2018/summit-schedule/global-search?t=manila15:06
tbarronalso one on Ceph day (monday)15:06
tbarron#link https://ceph.com/cephdays/ceph-day-berlin/15:06
tbarronamito may be arranging a  get together Tuesday night15:07
tbarronamito: I note that cinder is thinking the same way if we want to see if we can piggy-back15:07
tbarronAnything else on summit?15:07
amitoIt seems like there's a RH party on Tuesday15:07
tbarronamito: Monday15:07
*** dtrainor has quit IRC15:07
vkmcboth15:07
amitoRH+Trilio15:07
tbarronamito: ah, that's a difft thing.  We don't do manila bakup atm.15:08
amitoMaybe Wednesday and move Cinder as well?15:08
amitolol15:08
tbarronamito: Wednesday is pub crawl15:08
amitoOh15:08
tbarronamito: let's take it to #openstack-manila15:08
amitoWhere do I sign up? (for the pub crawl, lol)15:09
tbarronsounds like trilio and RH want inifinidat for cinder ...15:09
tbarronamito: there's a link I think off the main summit page15:09
*** ccamacho has joined #openstack-meeting-alt15:09
tbarronamito: ping me if you don't find it15:09
amitoI'll check that, thanks tbarron15:09
tbarronOK, next question.15:09
amitoSo we'll have the dinner on Tue.15:09
tbarronDo we meet next week?15:09
bswartzI can meet15:10
tbarronamito: just get Trilio to invite us all and we can grab a corner table :) not many of us.15:10
tbarronI can too.15:10
bswartzI'm pretty sure 2 weeks from now most of us cannot15:10
bswartzSo if we cancel next week we'll be going 3 weeks between meetings15:10
tbarronAnd as I think we'll see ^^ and that we have unfinished spec review business.15:11
tbarronOK, let's meet.15:11
tbarronAnyone who can not attend next week?15:11
gouthamri can, virtual-beer'o'clock same time next week15:12
tbarron#agreed we will meet next week as usual even though it's summit week15:12
tbarron#topic spec reviews15:12
*** openstack changes topic to "spec reviews (Meeting topic: manila)"15:12
bswartzgouthamr: beer-o-clock is 7am for you?15:12
tbarronSo it's spec deadline but we're really just now in the middle of all these reviews!15:12
gouthamrbswartz: it can be if we want it to be :D15:12
tbarronAnd I think the reviews are making progress.15:12
tbarronBut we started reviewing late -- again.15:13
tbarronI honestly think there is too much work associated with these reveiws to complete it all this cycle but --15:13
tbarronwhether I'm right about that or not -- it seems a shame15:13
tbarronto lose momentum and not get the design work that is ongoing completed.15:14
tbarronThere, that's what I have to say abou this.15:14
tbarronThoughts from others?15:14
gansotbarron: I agree that reviews should have started earlier15:14
bswartzMerging a spec isn't a guarantee that we'll merge a feature in the same release15:14
*** leni1 has joined #openstack-meeting-alt15:15
*** ttsiouts has quit IRC15:15
tbarronAnd some of them (not pointing at you ganso) should have been posted earlier, but they were posted by notable slackers :)15:15
bswartzBut not merging a spec is a guarantee we won't merge a feature15:15
* tbarron is messing around obviously15:15
tbarronbswartz: ++15:15
*** ttsiouts has joined #openstack-meeting-alt15:15
tbarronSo I want to propose that we extend the deadline until 29 November.15:16
bswartzBlanket extension?15:16
tbarronSome of us will be at summit next week and will have limited bandwidth.15:16
tbarronbswartz: not for any new submissions, but for the four submitted.15:16
bswartzRight, okay15:16
gouthamr~erm, notable slacker would like to add one more~15:17
tbarronBecause I think they are worth thinking about collectively and seeing if we can get agreement on them.15:17
tbarrongouthamr: you already have two if you refresh the agenda15:17
tbarrongouthamr: do you have three in mind?15:17
gouthamroh, nope, just two15:17
tbarrongouthamr: it's only becasuse I honestly think that both of those you proposed are things that we15:18
tbarronshould think about collectively now, while we're doing it, that I'm not being a meanie about them.15:18
tbarronNo guarantee that I'll agree with them.  I haven't had time to study much more than the problem statement.15:19
gouthamrsure, thank you for including the link, i will keep my elevator pitch ready :)15:19
tbarronBut I agree with the problem staements and think that if in the month of Novmember we could as a tem15:19
tbarronas a team15:19
*** ttsiouts has quit IRC15:19
tbarronget good design in place for the big residual DHSS=True issues and15:19
tbarronfor the manila AZ usage and storage-protocol/capability discovery15:20
tbarronwe'd actually have accomplished some good work in this spec cycle.15:20
tbarronContrary views?15:21
bswartzYou're arguing for getting all 4 specs in shape in the next 3 weeks?15:21
tbarronThe 29 November date is a bit out but we have summit and US Thanksgiving (big football holidy) in that window.15:21
tbarronbswartz: Yes.15:21
bswartzIs there any priority order we could put on them15:22
bswartz?15:22
tbarrongood question.15:22
bswartzIf push comes to shove and we can't get them all done?15:22
*** ttsiouts has joined #openstack-meeting-alt15:22
tbarronganso's forst priority was manage/unmanage for share servers, enabling that capability for DHSS=True15:22
tbarronfirst15:23
gansotbarron: yes15:23
tbarronI think that ones very close (even though it's not my personal first priotiry)15:23
tbarronbswartz already +2ed it, then ganso had to tweak because I -1ed but15:23
tbarronI'm pretty much OK with it now.15:24
bswartzI'm inclined to follow the priorities of the spec authors, because they'll also be implementing in their own priority orders (presumably)15:24
tbarrongouthamr: vkmc: can you look at this one this week?15:24
tbarronbswartz: +115:24
gouthamrtbarron: ack15:24
vkmctbarron, sure thing15:24
tbarronok then his next prio was the tough one, share networks spanning subnets.15:25
tbarronmy next prio would be gouthamr's AZ spec15:25
tbarronbut it came in late15:25
bswartz#link https://review.openstack.org/#/c/61612315:25
tbarronbswartz: I'm going to turn over chair to you since you met with ganso and gouthmr on that one15:26
tbarronAnd I have to drop the meeting soon.15:26
tbarronI will read the log (bouncer and recorded) but15:26
bswartzokay should we go over all the specs in teh agenda?15:26
bswartzOr start with ^15:26
tbarronbswartz: probably set priorities first as you suggested, then15:26
tbarronmaybe dig into the tough one given your meeting?15:26
* bswartz sees 5 links15:26
bswartzIs it 4 or 5 specs?15:27
tbarrontwo are for the extend share networks work15:27
gouthamrbswartz: i'm writing another one which makes it 515:27
bswartzWait that makes 615:27
tbarronone is gouthamr's orignal from newton moved over15:27
bswartzOkay15:27
bswartzLet's just go in order, and try to go fast15:27
bswartzEnjoy your vacation tbarron!15:27
* bswartz salutes15:27
bswartz#topic Manage/Unmanage Share Servers15:28
*** openstack changes topic to "Manage/Unmanage Share Servers (Meeting topic: manila)"15:28
bswartz#link  https://review.openstack.org/#/c/60734215:28
tbarronbswartz: thank you!15:28
vkmcbabai tbarron :)15:28
bswartzOkay as mentioned before, I'm okay with this as of PS1115:28
gouthamrtbarron: ++ enjoy the wine/food + more wine15:28
vkmcenjoy15:29
gansotbarron: and don't forget italian pasta15:29
bswartzThere's been a lot of discussion since my +215:29
amitoenjoy tbarron!15:29
bswartzAnything left to discuss on this or do we just need final reviews?15:29
gansobswartz: I think we only need the final reviews, no major concerns raised since the first revision15:29
bswartzgoing once...15:29
gouthamrnope, will take a look15:30
bswartztwice...15:30
bswartz#topic Share Networks Span Subnets15:30
*** openstack changes topic to "Share Networks Span Subnets (Meeting topic: manila)"15:30
bswartz#link https://review.openstack.org/#/c/391805/15:30
bswartz#link https://review.openstack.org/#/c/615947/115:30
bswartzSo this is a topic that goes back years15:30
bswartzIt's a thorny topic that we've spend a lot of time discussion in front of whiteboards at various venues15:31
bswartzGouthamr proposed a spec long ago that we agreed to, but it was never implemented15:31
bswartzGanso wants to do that work, plus more, to complete the picture15:31
bswartzI like the idea of having a comprehensive design, even if the implementation has to be phased over longer than 1 release15:32
bswartzBecause if we leave parts of the design undecided, it creates risk that the implementation might go in the wrong direction15:32
gansobswartz: correction, for now my commitment it to do just that work. I can propose the "plus more", but I will not commit15:33
gansobswartz: I will not commit *at this titme15:33
gansos/titme/time15:33
bswartzganso: I just meant you were volunteering to complete the design portion15:33
gansobswartz: oh ok15:33
bswartzI really like where this design seems to have ended up, even though it probably a ton of work to make it reality15:33
bswartzganso: can you outline the relationship between the 2 specs so everyone understand why it's split?15:34
gansobswartz: sure15:34
gansoso in summary15:34
gansoWhen we introduced IPv6, we noticed that we weren't able to have share servers serving export locations in IPv4 and IPv6 at the same time15:34
gansoit is not a very good user experience to not be able to serve your shares in IPv4+IPv6, if the hosts that could consume those shares can have IPv4+IPv615:35
gansoto accomplish that, we would need to allow a share network to be assigned to at least 2 subnets15:36
gansoand if we can do 2, we could even do more, but that's another bonus use case15:36
gansoin the first design of the Replication in DHSS=True spec, we don't change that share network subnet limitation, so the IPv4+IPv6 problem remains15:37
gansobut we make changes to the share network APIs that could conflict with the work to improve the IPv4+IPv6 and we desire to do in the future15:38
bswartzYeah we're trying to address multiple problems with these specs15:38
bswartzCleaning up all the loose ends from the original share-networks design15:38
gansoso our current plan of attack is to design what we plan to work on in the future to solve the IPv4+IPv6 share servers situation, so we can safely implement Replication in DHSS=True knowing we won't have problems in the future15:39
gansowe've agreed to a phased implementation, but we need to design these phases first, before start implementing them15:40
ganso<end of summary>15:41
bswartzSo IMO this spec should answer all the questions regarding how share networks will eventually work15:41
bswartzIncluding how we'll get dual IPv4/IPv6 support for share servers15:41
bswartzHow share servers will support replication15:42
bswartzAnd how share servers will support multiple subnets15:42
bswartzIn particular, changes to the driver interface are needed15:42
bswartzAnd there will need to be a capability/versioning exercise similar to what happened with access rules15:43
bswartzganso has suggested that for this release the only thing we might get is the replication (multi-AZ) support which could be done without changing the driver interface yet15:43
*** cloudrancher has quit IRC15:43
bswartzBut I'd still like to have written down where we eventually plan to go with share networks so we can make sure that the stein phase of this work doesn't conflict with that15:44
bswartzSeem reasonable?15:44
*** cloudrancher has joined #openstack-meeting-alt15:44
* bswartz looks at clock15:45
gansobswartz: yep15:45
bswartzBetter keep moving15:45
bswartz#topic Create share from snapshots in another pool or back end15:45
*** openstack changes topic to "Create share from snapshots in another pool or back end (Meeting topic: manila)"15:45
bswartz#link https://review.openstack.org/#/c/609537/15:45
gansook that is a good one15:45
*** yamahata has joined #openstack-meeting-alt15:45
gansomost of the feedback have been incorporated into the spec15:46
gansoexcept one15:46
ganso"I would like to see a mechanism to tell Manila, on a per-share-create basis, that it should ignore the location of the snapshot when scheduling the new share. This would be a scheduler hint, which the scheduler could safely ignore, but would result in dramatically better load balancing in the situation where a large number of shares were created from the same snapshot, and the end user had some knowledge of the15:46
gansolayout of the storage backends."15:46
bswartzThis is a solution to the practical issue we have where if you always create shares from snapshots, your shares all get crowded on the same pool15:46
*** ttsiouts has quit IRC15:46
bswartzganso: what is the likelihood this gets implemented in Stein?15:46
gansobswartz: if only this and manage/unmanage merges, it is very likely15:47
*** ttsiouts has joined #openstack-meeting-alt15:47
bswartzokay but which is higher priority in your mind?15:47
ganso1) manage/unmanage, 2) replication, 3) this one15:48
gansoif only 1) and 3) merge15:48
gansothen they will be implemented15:48
gansoif all 3 merge15:48
bswartzOkay15:48
ganso#3 will most likely not be implemented in Stein15:48
bswartzThis one seems like less of a bear to implement for sure15:48
bswartzBut there are some complex issues to consider15:48
gansoyea it doesn't seem to be a lot of code15:48
*** ttsiouts has quit IRC15:49
bswartzgouthamr: have you read this one?15:49
*** ttsiouts has joined #openstack-meeting-alt15:49
gansoso in summary, the user will be able to choose the AZ to create a share from snapshot in15:49
bswartzIt might be only tbarron and I have any opinions so far15:49
gouthamrbswartz: not yet, but familiar with the idea/motivation - so will do15:49
*** cloudrancher has quit IRC15:49
amitoMight be a stupid question but... how is create share in another pool different than manage share when we're talking about two different backends?15:49
gansoand there will be capabilities that allow manila to determine a compatible destination host15:49
bswartzgouthamr: the issue that we need to sort out is how the cross-pool scheduling gets triggered15:50
amito(I read through the spec)15:50
*** cloudrancher has joined #openstack-meeting-alt15:50
bswartzganso and I were debating the extent to which end-users should be empowered to make that happen15:50
bswartzbecause you can make the argument that only the administrator should know or care about this particular problem15:50
gansoand, even if the same AZ is chosen, there is a balancing rule (suggested by tbarron) to allow the admin to have some control on whether a share is created in the same pool with COW efficiency, or in another backend, for the purpose of capacity balancing15:50
gouthamrbswartz: ah, and the current direction is "AZ"?15:50
bswartzThe problem from my perspective is that, to make an ideal decision, you need to know if a particular snapshot will only be cloned a small number of times, or whether it will be cloned a large number of times15:51
bswartzOnly an end user can understand the usage patterns of the snapshots15:51
*** derekh has joined #openstack-meeting-alt15:52
bswartzIf you err on the side of keeping things on the same pool, you have the same problem we have today15:52
gansobswartz suggests that a parameter in the "create share API" should be added to force load balancing. I don't like this idea because this parameter doesn't make sense for users that aren't supposed to know of backends (unless they are also admins, which is not generally the case).15:52
gouthamrhow many times are you cloning this snapshot - can we infer that without asking the question?15:52
bswartzBut if you're too aggressive about scheduling new shares to other pools you could end up needlessly lowering storage efficiency and wasting time copying data15:52
bswartzMy intuition is that the the end user should be empowered to give hints to the scheduler, to cover the cases when the end user and the admin are actually the same person or at least people who talk to eachother15:53
bswartzBut such hints would not make sense in a more traditional public cloud deployment15:54
*** dtrainor has joined #openstack-meeting-alt15:54
gansogouthamr: if the user intends to send 100 requests, and send them individually, it is harder for us to decide whether to spread it or not. Although, if the user could mark the snapshot with a flag, we could know it. But why should a user mark it if it is not supposed to know or care about backends and balancing?15:54
bswartzMy solution there is to call them hints so it's clear that the system it welcome to ignore them15:54
*** dtrainor_ has quit IRC15:55
gouthamrganso: +115:55
gansobswartz: regarding efficiency, it could go both ways15:55
gansobswartz: if you have COW, then creating a 100 new shares from a snapshot is going to consume 0 bytes (in theory)15:56
bswartzAnyways I'd like to answer that question before this spec merges15:56
bswartzThat's the crux of the issue15:56
bswartzLet's move on though, I have a hard stop in 4 minutes15:56
bswartz#topic Storage Availability Zone Improvements15:56
*** openstack changes topic to "Storage Availability Zone Improvements (Meeting topic: manila)"15:56
gansobswartz: if we spread them, we would consume ~50x the size of the original share15:56
bswartz#link https://review.openstack.org/#/c/616123/15:56
bswartzThis is new as of yesterday15:57
bswartzI started to take a look this morning15:57
gouthamrbswartz: you're thought is to allow users to say `create --snapshot mysnap --okay-with-slow-creation` or `create --snapshot mysnap --quickly-if-possible`15:57
gouthamrbswartz: don't yet15:57
bswartzgouthamr: yes15:57
* gouthamr reddit-shames himself with you're/your15:58
gouthamrokay, sorry - i can quickly cover these two specs15:58
bswartzAnything to say about this? I'm not done reviewing15:58
gansogouthamr: still, how about the COW concerns? slow and fast isn't the only concern15:58
bswartzgouthamr and your other spec has a workflow -115:58
gouthamrganso: hmm, lemme read previous comments and your spec15:58
gouthamrbswartz: yes, it is not complete15:58
bswartzstill aiming for stein though?15:59
gouthamryep15:59
* bswartz waves the shame stick at gouthamr15:59
gouthamr:)15:59
bswartztoday was supposed to be the deadline!15:59
bswartzPlease get it in shape and ping people for reviews15:59
gouthamrsure thing15:59
bswartzthat's all the time we have I'm afraid15:59
bswartzWe will meet next week, despite people being at summit16:00
bswartzhopefully to make more progress on these specs16:00
bswartzenjoy berlin16:00
bswartzI'll miss you guys16:00
bswartz#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Thu Nov  8 16:00:42 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2018/manila.2018-11-08-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2018/manila.2018-11-08-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2018/manila.2018-11-08-15.00.log.html16:00
gansoTschüss16:00
*** ganso has left #openstack-meeting-alt16:01
*** ttsiouts has quit IRC16:07
*** ttsiouts has joined #openstack-meeting-alt16:08
*** leni1 has quit IRC16:12
*** dklyle has quit IRC16:17
*** gyee has joined #openstack-meeting-alt16:18
*** tssurya has quit IRC16:19
*** panda|off is now known as panda|rover16:19
*** jcoufal has joined #openstack-meeting-alt16:20
*** jcoufal has quit IRC16:20
*** jcoufal has joined #openstack-meeting-alt16:21
*** dklyle has joined #openstack-meeting-alt16:23
*** yamamoto has joined #openstack-meeting-alt16:40
*** slaweq has quit IRC16:40
*** cloudrancher has quit IRC16:43
*** cloudrancher has joined #openstack-meeting-alt16:44
*** yamamoto has quit IRC16:44
*** fanzhang has quit IRC16:46
*** e0ne has quit IRC16:48
*** fanzhang has joined #openstack-meeting-alt16:49
*** iyamahat has joined #openstack-meeting-alt16:55
*** slaweq has joined #openstack-meeting-alt16:58
*** panda|rover is now known as panda|rover|off17:02
*** rdopiera has quit IRC17:05
*** cloudrancher has quit IRC17:07
*** cloudrancher has joined #openstack-meeting-alt17:08
*** derekh has quit IRC17:14
*** derekh has joined #openstack-meeting-alt17:15
*** ttsiouts has quit IRC17:16
*** cloudrancher has quit IRC17:19
*** Leo_m has joined #openstack-meeting-alt17:27
*** irclogbot_1 has quit IRC17:31
*** ccamacho has quit IRC17:32
*** iyamahat has quit IRC17:39
*** yamahata has quit IRC17:40
*** diablo_rojo has joined #openstack-meeting-alt17:48
*** liuyulong has quit IRC17:50
*** iyamahat has joined #openstack-meeting-alt17:55
*** ircuser-1 has joined #openstack-meeting-alt18:01
*** derekh has quit IRC18:01
*** irclogbot_1 has joined #openstack-meeting-alt18:01
*** irclogbot_1 has quit IRC18:05
*** yamahata has joined #openstack-meeting-alt18:16
*** irclogbot_1 has joined #openstack-meeting-alt18:26
*** irclogbot_1 has quit IRC18:32
*** irclogbot_1 has joined #openstack-meeting-alt18:36
*** cloudrancher has joined #openstack-meeting-alt18:40
*** dpawlik has quit IRC19:00
*** dpawlik has joined #openstack-meeting-alt19:00
*** diablo_rojo has quit IRC19:12
*** diablo_rojo has joined #openstack-meeting-alt19:15
*** dustins has quit IRC19:26
*** smyers_ has joined #openstack-meeting-alt19:26
*** smyers has quit IRC19:26
*** smyers_ is now known as smyers19:26
*** dustins has joined #openstack-meeting-alt19:26
*** erlon_ has quit IRC19:31
*** dave-mccowan has joined #openstack-meeting-alt19:56
*** cloudrancher has quit IRC19:57
*** jtomasek has quit IRC20:05
*** dpawlik has quit IRC20:10
*** markstur has joined #openstack-meeting-alt20:17
*** e0ne has joined #openstack-meeting-alt20:19
*** e0ne has quit IRC20:22
*** dpawlik has joined #openstack-meeting-alt20:26
*** dpawlik has quit IRC20:30
*** radeks_ has joined #openstack-meeting-alt20:31
*** dave-mccowan has quit IRC20:33
*** radeks has quit IRC20:34
*** radeks__ has joined #openstack-meeting-alt20:36
*** raildo has quit IRC20:37
*** radeks_ has quit IRC20:39
*** dklyle has quit IRC20:45
*** dklyle has joined #openstack-meeting-alt20:45
*** dklyle has quit IRC20:46
*** markstur_ has joined #openstack-meeting-alt20:48
*** markstur has quit IRC20:51
*** radeks__ has quit IRC21:06
*** diablo_rojo has quit IRC21:50
*** iyamahat_ has joined #openstack-meeting-alt21:58
*** yamahata__ has joined #openstack-meeting-alt21:59
*** isq_ has quit IRC22:00
*** iyamahat has quit IRC22:00
*** diablo_rojo has joined #openstack-meeting-alt22:03
*** dustins has quit IRC22:36
*** Leo_m has quit IRC23:14
*** slaweq has quit IRC23:15
*** jcoufal has quit IRC23:28
*** dklyle has joined #openstack-meeting-alt23:44
*** erlon_ has joined #openstack-meeting-alt23:46
*** cloudrancher has joined #openstack-meeting-alt23:47

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