Thursday, 2017-09-28

*** iyamahat has quit IRC00:01
*** nikhil has joined #openstack-meeting-cp00:46
*** edmondsw has joined #openstack-meeting-cp01:28
*** edmondsw has quit IRC01:32
*** sdague has quit IRC02:05
*** Rockyg has joined #openstack-meeting-cp02:50
*** nikhil has quit IRC02:55
*** edmondsw has joined #openstack-meeting-cp03:16
*** edmondsw has quit IRC03:21
*** Rockyg has quit IRC04:42
*** edmondsw has joined #openstack-meeting-cp05:04
*** edmondsw has quit IRC05:09
*** dfflanders has joined #openstack-meeting-cp05:22
*** iyamahat has joined #openstack-meeting-cp06:02
*** zhipeng has joined #openstack-meeting-cp06:08
*** iyamahat has quit IRC06:16
*** coolsvap has joined #openstack-meeting-cp06:20
*** markvoelker has quit IRC06:30
*** edmondsw has joined #openstack-meeting-cp06:52
*** edmondsw has quit IRC06:57
*** iyamahat has joined #openstack-meeting-cp07:14
*** dfflanders has quit IRC07:44
*** MarkBaker has joined #openstack-meeting-cp07:50
*** zhipeng has quit IRC08:10
*** iyamahat has quit IRC08:10
*** eglute has quit IRC08:14
*** eglute has joined #openstack-meeting-cp08:14
*** markvoelker has joined #openstack-meeting-cp08:31
*** yamahata has joined #openstack-meeting-cp08:36
*** edmondsw has joined #openstack-meeting-cp08:41
*** edmondsw has quit IRC08:45
*** yamahata has quit IRC08:46
*** yamahata has joined #openstack-meeting-cp08:47
*** markvoelker has quit IRC09:05
*** yamahata has quit IRC09:40
*** sdague has joined #openstack-meeting-cp09:44
*** markvoelker has joined #openstack-meeting-cp10:02
*** edmondsw has joined #openstack-meeting-cp10:29
*** edmondsw has quit IRC10:33
*** markvoelker has quit IRC10:35
*** iyamahat has joined #openstack-meeting-cp10:35
*** iyamahat has quit IRC10:36
*** iyamahat_ has joined #openstack-meeting-cp10:36
*** markvoelker has joined #openstack-meeting-cp11:32
*** markvoelker has quit IRC12:06
*** iyamahat_ has quit IRC12:06
*** markvoelker has joined #openstack-meeting-cp12:18
*** edmondsw has joined #openstack-meeting-cp12:31
*** iyamahat has joined #openstack-meeting-cp13:04
*** iyamahat has quit IRC13:05
*** iyamahat has joined #openstack-meeting-cp13:05
*** yamahata has joined #openstack-meeting-cp13:33
*** gouthamr has joined #openstack-meeting-cp13:35
*** iyamahat has quit IRC13:35
*** nikhil has joined #openstack-meeting-cp13:58
*** yamahata has quit IRC14:01
*** sdague has quit IRC15:07
*** xyang1 has joined #openstack-meeting-cp15:11
*** lamt has joined #openstack-meeting-cp15:16
*** edmondsw has quit IRC15:46
*** mriedem has joined #openstack-meeting-cp15:49
mriedemstvnoyes: when did you say your vacation starts?15:52
*** iyamahat has joined #openstack-meeting-cp15:52
stvnoyestomorrow15:52
mriedemok15:53
mriedemgoing through https://review.openstack.org/#/c/463987/ now15:53
stvnoyesok15:54
ildikov#startmeeting cinder-nova-api-changes16:00
openstackMeeting started Thu Sep 28 16:00:09 2017 UTC and is due to finish in 60 minutes.  The chair is ildikov. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: cinder-nova-api-changes)"16:00
openstackThe meeting name has been set to 'cinder_nova_api_changes'16:00
ildikovjohnthetubaguy jaypipes e0ne jgriffith hemna mriedem patrickeast smcginnis diablo_rojo xyang1 raj_singh lyarwood jungleboyj stvnoyes16:00
jgriffithoh... ildikov is here :)16:00
jungleboyj@!16:00
_pewp_jungleboyj (ه’́⌣’̀ه )/16:00
ildikovcouldn't start the meeting earlier :)16:00
mriedemo/16:00
ildikovmy availability is a bit hectic today16:01
ildikovwho would like to co-chair?16:01
stvnoyeso/16:01
jgriffithildikov: happy to help out if needed16:01
ildikovtopics are: uses_shared_connection flag, live_migrate patch if there's anything on it, figuring out how R/W and R/O works in Cinder and then agree on policies and our strategy on them16:02
ildikov#chair jgriffith16:02
openstackCurrent chairs: ildikov jgriffith16:02
smcginniso/16:02
ildikovjgriffith: floor is yours on the flag :)16:02
jgriffithI'll start perhaps this will be short16:02
jgriffithI have a Spec and a patch started for the flag....16:02
jgriffithhttps://review.openstack.org/#/c/507670/16:03
jgriffithI'm going to rework that a bit but the general idea remains the same16:03
jungleboyjjgriffith:  Cool.  I will review.  Hadn't looked as I wasn't sure the status.16:03
jgriffithI've since proposed:  https://review.openstack.org/#/c/508209/16:03
jgriffithwhich I'll use as the foundation for updating the shared-targets flag patch16:03
jgriffithThe gist of this is that we'll have a column that indicates shared_targets are used by a backend (defaults to true)16:04
jgriffithand we'll have a column that indicates a backend unique identifier (that's where the UUID column in services comes in)16:04
jgriffithDue to the fact that it is possible to have a single backend serving up multiple c-vol services I'll also add a config option for an admin to set that identifier if needed16:05
jgriffithI need to update the spec for that16:05
jgriffithI believe this addresses the concerns we had around the attach/detach races with shared targets16:06
jungleboyjOh ... That is why we need that.16:06
jungleboyjI get it now.16:06
jgriffithwell, at least it provides mechanisms to deal with it16:06
jgriffithjungleboyj: yeah, so refresher;  The proposal was to use the backend-identifier to create a lock if needed16:06
jungleboyjRight.16:06
jgriffithkk16:06
jgriffithDoes anybody have any questions about that?16:07
mriedem"indicates shared_targets are used by a backend (defaults to true)"16:07
mriedemwhy not default to None?16:07
mriedemdefaulting to saying all backends are shared targets seems bad16:07
jgriffithmriedem: so default to True seemed "safest" because it won't *hurt* if a backend isn't actually using them16:07
jgriffithThe converse however is not the case16:08
mriedemwhat sets the flag?16:08
jgriffiththe migration sets it intially16:08
mriedemsure but at runtime16:08
jgriffithand then service startup verifies it's correct... and additionally volume-create sets it16:08
jgriffithit utilizes capabilitly reporting from the driver16:08
mriedemok, so existing volumes might have it wrong based on their type/backend,16:08
mriedembut worst case is we're unnecessarily locking, yes?16:09
jgriffithmriedem: that's correct, but they'll have it wrong in such a way that it won't cause problems16:09
jgriffithjust slight ineffeciencies16:09
jgriffithmriedem: correct16:09
mriedemok, maybe point that out in the spec to note we've thought about it :)16:09
mriedemwhen we ask in a year16:09
jgriffithmriedem: will do, thought I did but that may have just been a comment in the code :)16:09
jgriffithI'll make sure it's noted in the spec and also written up in dev docs16:10
mriedemi haven't read any of it, so idk16:10
jgriffithmriedem: so you're saying there's a chance :)16:10
jungleboyjThat all makes sense to me.16:10
*** kbyrne has quit IRC16:10
jgriffithie that I didn't skip something16:10
mriedemsure16:10
jungleboyjAnd we are giving the users a way to set what they use to lock if necessary.16:10
jgriffithOne suggestion was to use a single column, if None don't use locks, if not None use what's there16:11
jgriffithI didn't like that16:11
jgriffithseemed to obtuse16:11
jungleboyj++16:11
jgriffithbesides, I think the UUID in the services column is something we should've had already anyway16:11
jgriffithuseful for other things16:12
jgriffithSo that's about all I have on that front for now16:12
*** kbyrne has joined #openstack-meeting-cp16:12
jgriffithanybody have a burning topic they want to discuss here?16:13
jgriffithOr questions about anything?16:13
jgriffithoh... ildikov has an agenda  :)16:13
jgriffith#topic live_migrate patch16:13
*** openstack changes topic to "live_migrate patch (Meeting topic: cinder-nova-api-changes)"16:13
jgriffithstvnoyes: ?16:13
stvnoyesfyi - I'll be away starting tomorrow and all next week.16:13
jgriffithstvnoyes: Unacceptable!!16:14
jgriffith:)16:14
stvnoyesi have a rv up that mriedem is rv'ing now. hopefully I can update it (if needed) before I leave16:14
stvnoyesboy, when they make you chair, it really goes to your head ;-)16:14
jgriffithstvnoyes: you have no idea!16:15
jgriffith:)16:15
jungleboyjstvnoyes:  jgriffith  Doesn't believe in vacation16:15
jgriffithstvnoyes: mriedem anything else to talk about on live-migrate?16:15
*** aselius has joined #openstack-meeting-cp16:15
mriedemjust posted some comments,16:15
mriedemi need to run through the test changes in this patch,16:16
stvnoyesok great. i'll take a look16:16
mriedemand re-run the live migration patch that hits this code16:16
stvnoyes...after lunch (if that's ok with john)16:16
jgriffithstvnoyes: I suppose :)16:16
johnthetubaguyI do still hope to review that soon... just sadly hasn't happened yet16:16
jgriffithOk, sounds like we're moving forward still, just need review time16:17
jgriffithanything else on live-migrate?16:17
jgriffithGoing once...16:17
stvnoyesgood here16:17
jgriffithGoing twice...16:17
jgriffithCool16:17
jgriffith#topic handling R/O, R/W on Cinder side16:18
*** openstack changes topic to "handling R/O, R/W on Cinder side (Meeting topic: cinder-nova-api-changes)"16:18
jgriffithyeah... umm, that16:18
jungleboyjYeah ...16:18
jungleboyjSo, I have talked to smcginnis  and tommylikehu  a little on this.16:18
jgriffithjungleboyj: share your findings with us brave ambassador16:19
jungleboyjIt seems like the default policy we were leaning towards there is that, if possible, the first attachment is R/W and subsequent ones are only allowed to be R-O .16:19
jungleboyjNot sure if it is possible to do that, but that, I think, is the direction we want to go.16:19
johnthetubaguythat sounds bad for the folks with the cluster management tools16:19
jungleboyjIf the admin is smarter than us then he can enable multiple R/W attaches .16:20
jungleboyjjohnthetubaguy:  How so?16:20
johnthetubaguythey don't have any hooks to call into cinder to do the enable, they just expect two r/w volumes, as I understand it16:20
jgriffithjohnthetubaguy: +116:20
johnthetubaguyjust like moving an IP between two hosts using vrrp16:20
johnthetubaguyor some such16:20
jgriffithFWIW I don't like config as the controller for that either16:20
jungleboyjWell, wouldn't they just set the policy for their cloud to allow multiple R/W attaches .16:20
jgriffithSeems like we could bake it into the attachment request?16:21
jgriffithand as far as backends that don't support it, fall back to our types model like we've done in the past16:21
johnthetubaguyso the attachment request means we change the Nova API so you say read only vs read/write?16:21
jgriffithie  If user wants a multi-attach volume they need to specify that16:21
*** iyamahat has quit IRC16:21
jungleboyjjgriffith:  So an option with the attach?16:21
jgriffithjohnthetubaguy: yeah, I'm thinking something like an additional option to attach that let's one request what they want (RW or RO)16:22
johnthetubaguymy worry is the concept of "first" seems very racey16:22
jungleboyjIf it is a second attach and the backend doesn't support it we fail?16:22
smcginnisAdd additional attachment r/o, add additional attachment r/w, etc?16:22
jgriffithjohnthetubaguy: +116:22
jungleboyjDuh, that seems so much more sensible.  :-)16:22
jungleboyjGood thing we have smart people to think of such things.  :-)16:22
johnthetubaguyright now, all attachments are r/w basically16:23
smcginnisjgriffith: That means another update to the attach api. And another MV bump, right?16:23
jungleboyjRight.16:23
jgriffithjungleboyj: well, it seems simple until we start implementing and find all the things we're not thinking of :)16:23
* jungleboyj laughs16:23
jgriffithsmcginnis: yes it does16:23
johnthetubaguyso we could just explicitly request that for everything from Nova when it creates an attachment16:23
jgriffithsmcginnis: or I could wrap it up in the existing bump that's in flight16:23
smcginnisjgriffith: ++16:23
johnthetubaguyso... can't we ignore this fight for the first version?16:24
jgriffithjohnthetubaguy: typically yes, but MV's make everybody think "oh... how do I do this without having to bump again"16:24
johnthetubaguylike v1 everything is r/w like we have today16:24
johnthetubaguyjgriffith: they were invented with the exact opposite intent16:24
mriedemheh yeah was going to say that16:25
jgriffithjohnthetubaguy: I know.. but psychology and dev laziness are amazing forces16:25
* johnthetubaguy nods16:25
johnthetubaguypeople forgot how bad creating extensions was16:25
johnthetubaguy...anyways16:25
jgriffithjohnthetubaguy: so I'm certainly not opposed to just treating R/O volumes as an additional feature later, independent of multi-attach16:25
jgriffithbut I think smcginnis and others had some concerns about people corrupting all of their data16:26
johnthetubaguyright, it feels like we just leave the R/O stuff for next cycle, focus on multi-attach for v116:26
johnthetubaguyso some users will not want to use multi-attach till we do the whole R/O attachment thingy16:26
jungleboyjjgriffith:  Yeah, how big a gun do we want to give people?16:26
johnthetubaguybut I am saying we just punt that, for now?16:26
mriedemdidn't we say at the ptg that people can already corrupt their data today? or was that just specific to boot from volume with the wrong volume?16:26
jgriffithI'm EZ/PZ on this and will let others decide what's best.  I can see strong arguments for either approach16:26
jgriffithmriedem: yeah, we may have16:27
jungleboyjI kind of remember that.16:27
johnthetubaguyso people should be able to turn off multi-attach, I think we all agree that right?16:27
jgriffithmriedem: BFV did come up as a special case here16:27
mriedemjohnthetubaguy: yes16:27
jungleboyjjohnthetubaguy:  Yes16:27
jgriffithjohnthetubaguy: def16:27
mriedemby policy, that could go into cinder today16:27
johnthetubaguyso this is really about how many folks will turn on the crazy shotgun?16:27
johnthetubaguymriedem++16:27
johnthetubaguyI think we add the crazy but simple thing now16:28
jgriffithsmcginnis: jungleboyj sound ok to you?16:28
johnthetubaguyand we come back, with user feedback, and work out the read only thing in SYD?16:28
smcginnisYep16:28
jgriffithhonestly I'm almost 100% certain we'll revisit this before it's all said and done anyway :)16:28
* johnthetubaguy notes he is not in SYD, and giggles a little16:28
stvnoyesfyi - oracle's RAC (a clustered FS) needs multiattach R/W, but not bfv16:28
jungleboyjOk, I think that sounds like a reasonable approach.16:29
mriedemwe also said we could put a policy in nova for bfv with multiattach16:29
johnthetubaguyso bfv really only makes sense with RO, thats a good point16:29
smcginnisjgriffith: We revisit everything before it's all said and done most of the time.16:29
johnthetubaguymriedem: +1 as long as we don't check it 2k times16:29
jgriffithstvnoyes: FYI back at you; RAC is one of the number one use cases I've been asked about for this over the years16:29
jgriffithjust FWIW16:29
mriedemjohnthetubaguy: this isn't listing instances so we should be fine :)16:29
johnthetubaguymriedem :)16:29
jgriffithstvnoyes: which means I'm kinda counting on you for insight on this :)16:30
smcginnisYep, same for me with RAC.16:30
johnthetubaguy++ on RAC (and whatever the MS thing is called)16:30
* jungleboyj sighs about MS .16:30
smcginnisASM, Veritas Storage Manager, MS clustering...16:30
jgriffithOk, so seems like we have a concencus on strategy16:31
johnthetubaguyso.. policy in Nova for BFV, policy in Cinder to turn it off16:31
stvnoyesi'm no RAC expert (I was on oracle virt product prior to this) but I can certainly find things out about it from other people at the company16:31
jgriffithjohnthetubaguy: not sure if we'd need that in Nova FWIW16:31
jgriffithjohnthetubaguy: Cinder has the bootable flag and knows if it's bootable or not16:31
jgriffithmight be cleaner to leave all of those concerns to the Cinder side16:31
jgriffithmaybe?16:31
johnthetubaguyoh... even better16:31
mriedemcheck the recap notes from the ptg, we waffled on this a bit there16:32
johnthetubaguyalthough I wonder if nova sets that flag16:32
smcginnisWait, we want a policy for mutliattach too, right? Not just bfv.16:32
johnthetubaguywe said it was needed, overlay tempfs16:32
johnthetubaguysmcginnis: I was meaning bfv with multi-attach16:32
johnthetubaguymy bad16:32
jgriffithok... so for right now here's my proposal (which I kinda hate that I'm saying it)16:32
smcginnisjohnthetubaguy: OK, just making sure it's clear.16:32
johnthetubaguysmcginnis++16:32
jgriffith1.  Multiattach for data volumes only16:33
jgriffith2.  No consideration of R/O (that's a new and separate thing)16:33
johnthetubaguy(data = bootable=false?)16:33
jgriffithThat means no multi-attach BFV for V116:33
* johnthetubaguy nods16:33
mriedemthis is the recap email btw http://lists.openstack.org/pipermail/openstack-dev/2017-September/122238.html16:33
jgriffithunless as we go it falls nicely into place16:33
jungleboyjjgriffith:  ++16:34
jgriffithNothings written in stone, except OV's and MV's :)16:34
smcginnisjgriffith: +116:34
stvnoyesjgriffith:  +116:34
jgriffithmriedem: johnthetubaguy sound like a sane plan?16:34
johnthetubaguyI think so... should check some things16:34
johnthetubaguy(2) means all attachments assumed to be r/w attachments?16:35
mriedemmight want to also float whatever policy change you're going to make by the operators and dev MLs16:35
jgriffithmriedem: good idea16:35
jgriffithjohnthetubaguy: correct on (2)16:35
johnthetubaguyI can take this to the scientific WG meeting, or get oneswig too16:35
johnthetubaguyjgriffith: cool, I think I am happy then16:35
jgriffithjohnthetubaguy: that would be great16:35
jungleboyjjohnthetubaguy:  Yeah, the more feedback we get the better.16:36
jgriffithand of course if folks have more feedback or thoughts we can discuss again in next weeks (or the next weeks....) meeting16:36
johnthetubaguyso I know people want the BFV thing, and want the read_only thing, but the idea here is to keep moving16:36
smcginnisDefinitely a good phase II goal to add those.16:36
ildikovthe good thing is that we can evolve on those easily16:37
jgriffithjohnthetubaguy: yeah, I want it too; and although I'm willing to say it's out of scope here I'm not counting it out16:37
smcginnisBut functionality that covers 80% of the needs is better than 0%.16:37
johnthetubaguyI think it should be phase II, like next cycle16:37
jgriffithWhat I mean is I'd like to set a goal and if we exceed it then nothing wrong with that right?16:37
ildikovwell, easier than some other things anyway16:37
smcginnisjohnthetubaguy: ++16:37
johnthetubaguyI think this is more like 40% coverage, but I could be wrong16:37
smcginnisjgriffith: Agree16:37
johnthetubaguybut thats way better than 0%16:37
jungleboyjRight.  Styick with the simpler cases to start with and then iterate.16:37
jgriffithalso attach has taught me that trying to get 100% in one shot is painful :)16:38
johnthetubaguyso.. I am tempted to see if we can get a spec up for phase II, if someone is willing?16:38
jgriffithnot that there was a choice there16:38
ildikovjgriffith: +1 :)16:38
jgriffithjohnthetubaguy: I'm willing to draft something for the Cinder side, but honestly knowing how I am with specs and the fact that there are 2 or 3 in front of it I'm not going to promise anything in terms of timelines16:39
johnthetubaguythat fair enough16:39
ildikovjgriffith: johnthetubaguy: I can look into it too, I need to clean up mine in Nova based on the above anyway16:39
johnthetubaguyI guess all we need for feedback is16:39
johnthetubaguyphase II enables BFV multi-attach and RO multi-attach16:39
johnthetubaguyphase I is all R/W attachments, and no BFV16:40
johnthetubaguy... so we should dig into the BFV thing16:40
johnthetubaguymriedem I think nova doesn't check the bootable flag right now?16:40
jungleboyjjohnthetubaguy:  That sounds right.16:41
mriedemwould have to look16:41
ildikovjohnthetubaguy: in my old multi-attach patch I check whether BFV tries to boot from the multiattach volume and fail if it does16:41
johnthetubaguyildikov: I think we probably want that version of the policy for now16:41
jungleboyjildikov: ++16:42
johnthetubaguyI would love this to be all on the cinder side, but I don't think we respect enough today to make that possible16:42
ildikovjohnthetubaguy: I guess it only means code cosmetics by putting the logic elsewhere16:42
jgriffithjohnthetubaguy: mriedem it does but I don't know if it's the context your'e looking for...16:42
johnthetubaguyjgriffith: it does?16:42
jgriffithhttps://review.openstack.org/#/c/508209/16:42
jgriffithoops16:42
jgriffithhttps://github.com/openstack/nova/blob/master/nova/compute/api.py#L103416:43
ildikovjohnthetubaguy: well, the BFV case it's not necessarily on the Cinder side16:43
jgriffithobviously there's needed modifications but the basic flow is there at least16:44
jgriffithand there is the concept of using and checking said flags16:44
johnthetubaguythat's all promising16:44
mriedemoh interesting,16:44
mriedemhowever,16:44
mriedemNOTE16:44
mriedemthat's only when bfv from an image-defined bdm16:45
mriedemwhich is,16:45
mriedema volume-backed instance snapshot image16:45
mriedemthat has bdm info in it16:45
johnthetubaguyoh, rather than a bdm passed on the boot command line16:45
mriedemoh hold the phone16:46
mriedemi think it's just a really poorly named method16:46
johnthetubaguyactually, that looks badly named16:46
jgriffithmriedem: that's what I thought16:46
jgriffithand a confusing comment16:46
jgriffithre "poorly named method"16:46
johnthetubaguyI assume the volumes nova creates form an image correctly are marked as bootable?16:46
jgriffithbecause if you trace back to who calls it16:46
johnthetubaguy(not that it matters in that case)16:47
mriedemjohnthetubaguy: doesn't say here https://github.com/openstack/nova/blob/master/nova/virt/block_device.py#L51316:47
johnthetubaguyso seems like cinder policy on bootable=True could work16:47
jgriffithanyway... might need some tweaking of things but there's a foundation at least16:47
mriedemcinder must default bootable to true for a new volume16:48
johnthetubaguymriedem: yeah, doesn't seem promising there, but it would also never be multi-attach, thankfully)16:48
jgriffithmriedem: ?16:48
jgriffithmriedem: negatory, unless I'm misunderstanding you.  Cinder defaults volumes to bootable=False until it actually lays down an image on them16:49
mriedemoh, well we pass an image_id here https://github.com/openstack/nova/blob/master/nova/virt/block_device.py#L51416:49
johnthetubaguyah, so passing an image would be the difference16:49
johnthetubaguyphew16:49
mriedemhow does this work then? https://github.com/openstack/nova/blob/master/nova/virt/block_device.py#L53516:50
* johnthetubaguy thinks this was all very educational16:50
mriedemcreates a blank volume16:50
mriedemmaybe that's not the root bdm16:50
johnthetubaguythats ephemerals16:50
mriedemok16:50
johnthetubaguyno I have no clue on the API syntax for that16:50
johnthetubaguyanyways, sounds like phase I plan A is intact16:51
jgriffithNot sure if this is what you guys are looking for:  https://github.com/openstack/nova/blob/master/nova/compute/api.py#L107916:51
jgriffithsorry, not completely following the dialogue16:51
jgriffithbut anyway16:51
johnthetubaguythat's what I found early tracing back, its all good16:52
jgriffithIIRC that's the default BFV path there16:52
jgriffithOk16:52
jgriffithOkie Dokie... anything else?16:53
jgriffith#topic open-discussion16:53
*** openstack changes topic to "open-discussion (Meeting topic: cinder-nova-api-changes)"16:53
jgriffithildikov: still with us?  Did we miss anything?16:53
ildikovI think we're good16:53
jgriffithsmcginnis: jungleboyj ?16:53
johnthetubaguyspoke to a scientific working group in london16:53
jungleboyjI think we are good16:53
johnthetubaguythey seemed happy we are making progress16:54
jungleboyjThat is good.16:54
ildikovjohnthetubaguy:  +116:54
jgriffithjohnthetubaguy: cool!  Our mission is to make the world happy :)16:54
johnthetubaguyI think I convinced them its complicated, hence the delay16:54
jgriffithOr at least the OpenStack world16:54
jungleboyj:-)16:54
johnthetubaguycool, next steps is review the code and specs?16:55
jgriffithhttp://www.allmusic.com/album/give-the-people-what-they-want-mw000019635716:55
jungleboyjjohnthetubaguy:  I think so and then start thinking about what we do for Phase II.16:55
ildikovAnd get the flag into Cinder to get the microversion bump16:55
* jgriffith realizes his presentation slides are sooo old he can start recycling them16:55
ildikovAnd merge stuff :)16:56
jungleboyjAnd make people happy16:56
johnthetubaguyjgriffith: s/kilo/queens/16:56
jgriffithjohnthetubaguy: hehe... close enough :)16:56
jgriffithjohnthetubaguy: most people haven't upgraded from Kilo yet anyway :)16:57
jgriffithOk... let's wrap this up then?16:58
* johnthetubaguy is happy he working with folks running pike clouds16:58
smcginnis:)16:58
jgriffithjohnthetubaguy: +116:58
jgriffithYou're a lucky lucky man!16:58
jungleboyjSounds good.16:59
jgriffithalrighty then, until next week.  Thanks all!!!16:59
jgriffith#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Thu Sep 28 16:59:19 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder_nova_api_changes/2017/cinder_nova_api_changes.2017-09-28-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder_nova_api_changes/2017/cinder_nova_api_changes.2017-09-28-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder_nova_api_changes/2017/cinder_nova_api_changes.2017-09-28-16.00.log.html16:59
ildikovThanks All!!!16:59
jungleboyjThank you!16:59
*** mriedem has left #openstack-meeting-cp17:10
*** nikhil has quit IRC17:18
*** coolsvap has quit IRC17:29
*** diablo_rojo has joined #openstack-meeting-cp17:38
*** edmondsw has joined #openstack-meeting-cp18:01
*** edmondsw has quit IRC18:04
*** edmondsw has joined #openstack-meeting-cp18:04
*** nikhil has joined #openstack-meeting-cp19:27
*** nhelgeson has joined #openstack-meeting-cp19:49
*** yamahata has joined #openstack-meeting-cp20:57
*** MarkBaker has quit IRC21:20
*** nikhil has quit IRC21:36
*** iyamahat has joined #openstack-meeting-cp21:53
*** gouthamr has quit IRC21:56
*** gouthamr has joined #openstack-meeting-cp22:03
*** iyamahat_ has joined #openstack-meeting-cp22:07
*** iyamahat has quit IRC22:07
*** iyamahat_ has quit IRC22:08
*** gouthamr has quit IRC22:18
*** gouthamr has joined #openstack-meeting-cp22:20
*** gouthamr has quit IRC22:23
*** iyamahat has joined #openstack-meeting-cp22:25
*** lbragstad has quit IRC22:37
*** xyang1 has quit IRC22:50
*** reed has quit IRC23:05
*** reed has joined #openstack-meeting-cp23:08
*** markvoelker has quit IRC23:37
*** iyamahat has quit IRC23:56
*** yamahata has quit IRC23:56

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