Thursday, 2013-06-06

*** tanisdl has quit IRC00:11
*** lastidiot has joined #openstack-meeting-alt00:17
*** vipul is now known as vipul|away00:38
*** amytron has joined #openstack-meeting-alt00:42
*** grapex has quit IRC00:45
*** amytron has quit IRC00:45
*** amytron has joined #openstack-meeting-alt00:47
*** lifeless_ has joined #openstack-meeting-alt00:48
*** amytron has quit IRC00:48
*** amytron has joined #openstack-meeting-alt00:49
*** lifeless has quit IRC00:50
*** lifeless_ is now known as lifeless00:52
*** amytron has quit IRC00:52
*** lifeless has quit IRC00:53
*** bdpayne has quit IRC00:54
*** lifeless has joined #openstack-meeting-alt00:54
*** amytron has joined #openstack-meeting-alt00:55
*** lifeless has quit IRC00:59
*** vipul|away is now known as vipul01:05
*** amytron has quit IRC01:06
*** amytron has joined #openstack-meeting-alt01:07
*** lifeless has joined #openstack-meeting-alt01:08
*** Riddhi has joined #openstack-meeting-alt01:24
*** amytron has quit IRC01:24
*** amytron has joined #openstack-meeting-alt01:25
*** amytron has quit IRC01:36
*** amytron has joined #openstack-meeting-alt01:37
*** grapex has joined #openstack-meeting-alt01:41
*** amytron has quit IRC01:41
*** grapex has quit IRC01:41
*** grapex has joined #openstack-meeting-alt01:41
*** amytron has joined #openstack-meeting-alt01:41
*** yamahata has quit IRC01:46
*** amytron has quit IRC01:56
*** amytron has joined #openstack-meeting-alt01:58
*** yamahata has joined #openstack-meeting-alt02:03
*** grapex has quit IRC02:14
*** amytron has quit IRC02:14
*** amytron has joined #openstack-meeting-alt02:14
*** demorris has joined #openstack-meeting-alt02:18
*** markwash has joined #openstack-meeting-alt02:21
*** Riddhi has quit IRC02:22
*** cp16net is now known as cp16net|away02:39
*** amytron has quit IRC02:39
*** cp16net|away is now known as cp16net02:39
*** amytron has joined #openstack-meeting-alt02:41
*** cp16net is now known as cp16net|away02:49
*** cp16net|away is now known as cp16net02:55
*** demorris has quit IRC03:16
*** amytron has quit IRC03:16
*** amytron has joined #openstack-meeting-alt03:17
*** sdake_ has quit IRC03:23
*** sdake_ has joined #openstack-meeting-alt03:24
*** sdake_ has quit IRC03:24
*** sdake_ has joined #openstack-meeting-alt03:24
*** pcm__ has quit IRC03:24
*** SergeyLukjanov has joined #openstack-meeting-alt03:36
*** amytron has quit IRC03:36
*** amytron has joined #openstack-meeting-alt03:37
*** cp16net is now known as cp16net|away03:42
*** amytron has quit IRC03:42
*** amytron has joined #openstack-meeting-alt03:43
*** amytron has quit IRC03:56
*** amytron has joined #openstack-meeting-alt03:57
*** akuznetsov has joined #openstack-meeting-alt04:40
*** amytron has quit IRC04:40
*** amytron has joined #openstack-meeting-alt04:41
*** amytron has joined #openstack-meeting-alt04:44
*** Bobball has quit IRC04:48
*** euanh has quit IRC04:48
*** amytron has quit IRC04:51
*** amytron has joined #openstack-meeting-alt04:52
*** euanh has joined #openstack-meeting-alt04:56
*** Bobball has joined #openstack-meeting-alt04:59
*** amytron has quit IRC04:59
*** Bobball is now known as Guest8854604:59
*** amytron has joined #openstack-meeting-alt05:00
*** lastidiot has quit IRC05:14
*** SergeyLukjanov has quit IRC05:28
*** amytron has quit IRC05:31
*** amytron has joined #openstack-meeting-alt05:32
*** akuznetsov has quit IRC05:57
*** dhellmann-away has quit IRC06:12
*** IlyaE has joined #openstack-meeting-alt06:16
*** amytron has quit IRC06:16
*** amytron has joined #openstack-meeting-alt06:16
*** amytron_ has joined #openstack-meeting-alt06:30
*** amytron has quit IRC06:30
*** amytron_ is now known as amytron06:30
*** akuznetsov has joined #openstack-meeting-alt06:34
*** amytron has quit IRC06:40
*** sungju_ has quit IRC06:46
*** IlyaE has quit IRC06:53
*** IlyaE has joined #openstack-meeting-alt06:56
*** sdake_ has quit IRC07:15
*** dhellmann has joined #openstack-meeting-alt07:15
*** dhellmann has quit IRC07:29
*** akuznetsov has quit IRC07:33
*** qwerty_nor has joined #openstack-meeting-alt07:45
*** johnthetubaguy has joined #openstack-meeting-alt07:56
*** IlyaE has quit IRC08:04
*** johnthetubaguy1 has joined #openstack-meeting-alt08:20
*** akuznetsov has joined #openstack-meeting-alt08:21
*** johnthetubaguy has quit IRC08:23
*** Guest88546 is now known as Bobba08:37
*** euan has joined #openstack-meeting-alt08:50
*** Bobba has quit IRC08:50
*** euan is now known as Guest2546008:51
*** BobBall has joined #openstack-meeting-alt08:51
*** euan_ has joined #openstack-meeting-alt08:51
*** BobBall is now known as Guest4552708:51
*** euanh_ has joined #openstack-meeting-alt08:52
*** Guest45527 has quit IRC08:52
*** BobBall_ has joined #openstack-meeting-alt08:52
*** euanh has quit IRC08:54
*** Guest25460 has quit IRC08:54
*** euan_ has quit IRC08:56
*** euan_ has joined #openstack-meeting-alt08:56
*** euanh_ has quit IRC08:56
*** johnthetubaguy1 is now known as johnthetubaguy09:26
*** akuznetsov has quit IRC09:26
*** johnthetubaguy has quit IRC09:31
*** johnthetubaguy has joined #openstack-meeting-alt09:34
*** akuznetsov has joined #openstack-meeting-alt09:36
*** BobBall_ is now known as Bobba09:41
*** SergeyLukjanov has joined #openstack-meeting-alt09:45
*** akuznetsov has quit IRC09:49
*** johnthetubaguy has quit IRC10:00
*** johnthetubaguy has joined #openstack-meeting-alt10:00
*** sungju has joined #openstack-meeting-alt10:18
*** akuznetsov has joined #openstack-meeting-alt10:20
*** akuznetsov has quit IRC10:27
*** akuznetsov has joined #openstack-meeting-alt10:34
*** johnthetubaguy1 has joined #openstack-meeting-alt10:36
*** johnthetubaguy has quit IRC10:38
*** SergeyLukjanov has quit IRC10:49
*** SergeyLukjanov has joined #openstack-meeting-alt10:59
*** johnthetubaguy1 is now known as johnthetubaguy11:22
*** grapex has joined #openstack-meeting-alt11:43
*** qwerty_nor has quit IRC11:45
*** pcm__ has joined #openstack-meeting-alt11:46
*** mestery_ has joined #openstack-meeting-alt11:46
*** mestery has quit IRC11:50
*** HenryG has joined #openstack-meeting-alt11:53
*** grapex has quit IRC12:01
*** SergeyLukjanov has quit IRC13:00
*** grapex has joined #openstack-meeting-alt13:00
*** markwash has quit IRC13:08
*** markwash has joined #openstack-meeting-alt13:08
*** npasqua has joined #openstack-meeting-alt13:16
*** demorris has joined #openstack-meeting-alt13:16
*** briancline has quit IRC13:18
*** jergerber has quit IRC13:20
*** briancline has joined #openstack-meeting-alt13:22
*** dosaboy has joined #openstack-meeting-alt13:27
*** mtreinish has joined #openstack-meeting-alt13:34
*** openstack has joined #openstack-meeting-alt13:41
*** ChanServ sets mode: +o openstack13:41
*** openstack has joined #openstack-meeting-alt13:52
*** ChanServ sets mode: +o openstack13:52
*** Bobba has quit IRC13:54
*** BobBall has joined #openstack-meeting-alt13:54
*** euan_ has quit IRC13:58
*** esheffield has joined #openstack-meeting-alt14:00
markwashHi Folks14:00
markwasho/14:00
zhiyan1hi14:00
rosmaitahi14:01
icchao/14:01
zhiyan1hi iccha14:01
esheffieldhey markwash!14:01
esheffield\o14:01
icchahey zhiyan114:01
markwashlets start loggin14:01
markwash#startmeeting glance14:01
openstackMeeting started Thu Jun  6 14:01:30 2013 UTC.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: glance)"14:01
openstackThe meeting name has been set to 'glance'14:01
ameadeyo14:01
*** jbresnah has joined #openstack-meeting-alt14:01
markwashso, time change seems to work okay for east coast14:01
jbresnahwave14:02
zhiyan1yes :) thanks14:02
markwashjbresnah: hi!14:02
zhiyan1hi jbresnah14:02
icchait must be really early for PST ppl14:02
markwashjbresnah: glad you could make it!14:02
rosmaitajbresnah gets the worst time for a meeting award14:02
markwashiccha: not really, worst for hawaii14:02
icchadedication and love for glance jbresnah14:02
markwashbut this way zhiyan1 can be here more easily, (though it is pretty late!)14:03
zhiyan1:)14:03
* jbresnah is taking coffee intravenously14:03
markwashso anybody got anything they want to add to the informal agenda for today?14:03
zhiyan1yes, yes, cinder-glance-store..14:03
markwashzhiyan1: check14:03
markwash#link https://wiki.openstack.org/wiki/Meetings/Glance#Agenda_for_Next_Meeting14:03
markwashhas the rough outlines, I'm most interested in ongoing blueprints today14:04
icchaesheffield: and me just have some updates on documentation, not much though14:04
markwashcool14:04
jbresnahI would like to talk about the multiple locations bp if possible14:04
markwashjbresnah: deal14:05
zhiyan1yes, cool14:05
*** grapex has left #openstack-meeting-alt14:05
*** flaper87 has joined #openstack-meeting-alt14:05
rosmaitaif there is time i would like to mention import/export/clone14:05
markwashfor zhiyan1's glance-cinder-driver work, there is this etherpad14:05
markwash#link https://etherpad.openstack.org/linked-template-image14:05
flaper87o/14:05
markwashfolks might want to take a look through that before we get to it later on in the meeting14:05
zhiyan1hi flaper87.14:05
flaper87zhiyan1: hey :)14:06
zhiyan1thanks mark, yes, thatis:)14:06
* nikhil is eavsdroppping14:06
markwash#topic New Blueprints (fast-style!)14:06
*** openstack changes topic to "New Blueprints (fast-style!) (Meeting topic: glance)"14:06
markwashIs anyone in interested in checking the sanity of a few blueprints this week?14:07
flaper87o/14:07
markwashspecifically to help out marking them as approved14:07
jbresnahsure, any in particular?14:07
icchai thought we already though cross id was sane14:07
flaper87jbresnah: dude, you're awake14:07
flaper87T_T14:07
*** mclaren has joined #openstack-meeting-alt14:07
flaper87go to sleep14:07
markwashfirst there is14:07
flaper87:P14:07
markwash#link https://blueprints.launchpad.net/glance/+spec/ability-to-separate-snapshots-and-images14:07
jbresnahflaper87: partially14:07
markwashsecond there is14:08
markwash#link https://blueprints.launchpad.net/glance/+spec/cross-service-request-id14:08
*** cp16net|away is now known as cp16net14:08
flaper87markwash: there's a thread in the mailing list about the cross-service-...14:08
markwashand as a third option there is14:08
markwash#link https://blueprints.launchpad.net/glance/+spec/use-oslo-common-db-code14:08
rosmaitafirst one: can this just be done with metadata and the back end sorts things out?14:09
* markwash looks14:09
flaper87I'll take the last one14:09
flaper87:D14:09
*** DuncanT has joined #openstack-meeting-alt14:09
markwashrosmaita: possibly14:09
jbresnahmarkwash: I put out comments on the first 214:09
ameadeare we talking about the 1st one yet?14:10
rosmaitabecause there are a lot more use cases than just RAID level14:10
ameadeor all of them at once :P14:10
jbresnahi think the second is a solid idea, and seems to be going on in other OS projects14:10
iccha+1 jbresnah14:10
flaper87jbresnah: it is14:10
markwash+1 jbresnah14:10
rosmaita+1 jbresnah14:10
markwashit looks like we have plenty of interest14:11
jbresnahso i would say we can call the second one approved14:11
flaper87hahaha14:11
flaper87:D14:11
markwashI think the task here for each one is either to get more feedback, or to just yell at me to approve it14:11
markwashyeah +1 I'm approving the request id one now14:11
ameade+1 on the 2nd, am I crazy markwash or didn't we implement that together a long time ago?14:11
markwashyeah I thought we did :-)14:11
markwashokay looks good for new bps14:13
zhiyan1seems use-oslo-common-db-code is good to approval also, marwash?14:13
zhiyan1sorry, markwash14:13
markwashno worries!14:13
markwashthe oslo-common-db-code one is still a little unclear to me14:13
flaper87zhiyan1: I'd like to have more info about that one14:13
flaper87how he's planning to do it14:13
flaper87the impact14:13
markwashI'm hesitant about "common db" code because glance is very coupled to its schema still14:13
icchayeah what implications it entails14:13
zhiyan1is those code ready in oslo?14:13
markwashand I don't want us to suddenly be very coupled with all the other projects schema as well14:13
zhiyan1i'm not sure for that14:13
flaper87zhiyan1: yup, most of it14:13
mclarenmarkwash: also if we want to look at zero downtime with glance it may complicate it?14:14
zhiyan1ok, just port code and landing down to glance, right? ..14:14
mclarenie with glance first14:14
markwashmclaren: o/ !14:14
flaper87TBH, that one sounds more like Ith release to me, but I'll get more feedback14:14
markwashzhiyan1: it just may not be the right idea yet14:14
zhiyan1flaper87: goot it14:14
markwash#topic Blueprints in progress14:15
*** openstack changes topic to "Blueprints in progress (Meeting topic: glance)"14:15
zhiyan1seems, we need feedback to make sure it work well then to landing :)14:15
markwashjbresnah, want to talk about multiple locations?14:15
jbresnahyeah14:15
ameadedid we ever decide on bp #1?14:15
markwashameade, no, I think some folks were going to look into it more closely?14:15
markwashshould I have actioned somebody?14:15
jbresnahmarkwash: i put a question on it14:16
flaper87markwash: me for #314:16
jbresnahi can chase it a bit more, but maybe i can talk it out with ameade first14:16
*** djohnstone has joined #openstack-meeting-alt14:16
jbresnahi may be missing the intention14:16
markwash#action flaper87 evaluate use-oslo-common-db-code14:16
markwash#action jbresnah continue evaluating ability-to-separate-snapshots-and-images once there is feedback14:17
markwashseems like we're good14:17
markwashothers feel free to participate in those14:17
jbresnahcool14:18
* markwash yields to jbresnah about multiple locations14:18
zhiyan1jbresnah, could you pls talk about multiple locations? i really need it14:18
zhiyan1:)14:18
jbresnahi have a patch out there that i added comments to14:18
jbresnahi have not had a chance yet to see if anyone replied14:19
jbresnahhas anyone had a chance to see it?14:19
zhiyan1https://review.openstack.org/#/c/30517/  ?14:19
jbresnahno, i abandoned that14:19
zhiyan1yes, which one? sorry14:19
jbresnahhttps://review.openstack.org/#/c/31591/14:19
jbresnahmarkwash had thoughts on how to do it with PATCH14:20
markwashjbresnah: ah, good point about the restriction of multiple slashes14:20
jbresnahwhich i agree with14:20
zhiyan1cool, i will check it later14:20
jbresnahjust need to finalize the API14:20
jbresnahi also have:14:20
markwashI originally put in that restriction because I thoguht json-pointer was a bit much to implement14:20
jbresnahhttps://review.openstack.org/#/c/31306/14:20
markwashI think we could remove the restriction now but it might take some more code14:20
jbresnahmarkwash: is it openstack policy tho?14:21
jbresnah| http://docs.openstack.org/api/openstack-image-service/2.0/content/restricted-json-pointers.html14:21
markwashjbresnah: no no, I just wrote that as a CYA kind of thing14:21
jbresnahi could hard code a special case for /locations/ somewhat easily14:21
jbresnahheh ok14:21
markwashthe new format would be backwards compatible14:21
markwashso I think this is all great progress14:22
markwashand I'll keep reviewing!14:22
*** lastidiot has joined #openstack-meeting-alt14:22
jbresnahmarkwash: so should i loosen the restriction?14:22
markwashjbresnah: yes I think so14:22
jbresnahin the general case?14:22
markwashjbresnah: that would be okay but we probably have to put in some code restrictions to make sure most properties can only be strings14:23
markwashI don't think we want to support requests that add user properties that are lists or json objects14:23
jbresnahactually i ran into something with that yesterday14:23
jbresnahi think there are restrictions there14:23
*** xwizard has quit IRC14:23
markwashokay cool14:23
jbresnahi was trying to implement the last way, where the list is changed all at once14:24
*** djohnstone has quit IRC14:24
zhiyan1one sample question jbresnah, is this 'remove: [{"remove": "add", "path": "/locations", "value": <url>}]' should be this 'remove: [{"op": "remove", "path": "/locations", "value": <url>}]' ?14:24
jbresnahand errors come back saying it can only be a string, i didn't get far into it14:24
markwashlets talk about it later today in #openstack-glance14:24
jbresnahcool14:24
mclarendumb question: do these locations contain credentials? if so do they pick up the metadata_encryption setting?14:24
jbresnahzhiyan1: yeah that seems right14:24
markwashmclaren: I think they should pick up the encryption setting14:24
mclarenthx14:25
jbresnahmclaren: yeah they should14:25
markwashsome of that should have already been done maybe? but I'll check again14:25
*** djohnstone has joined #openstack-meeting-alt14:25
markwashso folks should keep reviewing multiple locations code14:25
zhiyan1markwash: could you pls show me the url about metadata_encryption ?14:25
jbresnahmclaren: they could contain such info, that is up to the admin adding the location14:25
jbresnahmclaren: we sort of changed the approach and there is a bit of a buyer-beware attitude with this one14:26
mclarengotcha14:26
* flaper87 needs to dig more into multiple-locations14:26
markwashzhiyan1: can you remind me after the meeting? I'll dig around and find it14:26
jbresnahzhiyan1: at some point i would like to talk to you about your interest in this bp14:26
zhiyan1sure14:26
jbresnahzhiyan1: cool, i want to make sure i am addressing all needs14:26
markwashanything else on multiple locations? next is glance-cinder-driver14:27
zhiyan1yes, for glance-cinder-store, if you checked https://etherpad.openstack.org/linked-template-image , there are some dependencies for implementation, and all about cinder: attach volume to host / direct volume IO.14:27
jbresnahmarkwash: i think that is good for here, just some follow up convos14:27
*** npasqua has quit IRC14:27
zhiyan1so, i dont want to blocked from that, can can dev now...so, i have talked a lot of glance-cinder-store before with mark :) , and seems there a three choice for me..14:27
zhiyan1A simple approach:14:28
zhiyan11) upload image to glance non-cinder store14:28
zhiyan12) tell cinder to create a volume from that image14:28
zhiyan13) register the image to cinder store, use image id (from step 1) + volume id (from step 2) as the location14:28
zhiyan1(each step is a separate api call)14:28
zhiyan1B. multi-locations approach14:28
zhiyan1C. final solution14:28
zhiyan1after cinder have a pretty method to support attach volume to host / direct volume io (base on 'brick'/cinder-agent, in H3 or I1), i will change the cinder store driver to read/write image data from remote volume driectly but not separate handling..14:28
*** amytron has joined #openstack-meeting-alt14:29
markwashcool14:29
markwashin the multi locations approach14:29
zhiyan1:), so jbresnah: i'm just now sure about #B14:29
markwashthe idea is that you create the image with a non-cinder store14:30
markwashthen ask cinder to create a volume from it14:30
zhiyan1how to let glance-cinder-store match your plan? or any thoughts/comments?14:30
markwashand then register the cinder volume as a location on the image14:30
zhiyan1markwash: yes, that of #A plan14:30
markwashthe caveat is that the cinder store location would *not* support getting image data directly14:30
icchaso B is an improvement over approach A ? with addition pf multiple locations?14:30
markwashzhiyan1: I thought I was describing plan B14:31
zhiyan1iccha: i think, yes14:31
zhiyan1yes, pls14:31
*** amytron has quit IRC14:31
*** lastidiot has quit IRC14:31
jbresnahi do not quite have my head around this yet, sorry14:31
flaper87mmh, cinder-store changes how glance's stores work, IMHO. I'm not fully against it but we need to figure it out a bit better14:31
icchawho will ask cinder to create volume from glance? is it glance or user?14:32
*** amytron has joined #openstack-meeting-alt14:32
zhiyan1api user14:32
flaper87My first comment is that multiple-locations is a must for it to happen - assuming I got the idea right.14:32
jbresnahdoes cinder act as a glance client at that point or does it have special privledges?14:33
markwashflaper87: yeah, thats my concern as well. it seems strange to have a location that you can't really "get"14:33
flaper87can the cinder location be a property of the image?14:33
zhiyan1flaper87: yes, yes, i'd like address C# plan directly , but i check with cinder team from two weekly meeting, not sure there is a clear plan to address what i/cinder-store need14:33
markwashflaper87: but I think it could be fine if we figure out a clean way to do it14:33
flaper87instad of a separate store ?14:33
flaper87instead*14:33
jbresnahmarkwash: why can you not get it?14:33
markwashflaper87: yes, actually it can be a property of the image, in the form of a block device mapping property14:34
markwashjbresnah: because the only way to get it right now is to attach the volume as a device directly to the glance api host14:34
*** Riddhi has joined #openstack-meeting-alt14:34
flaper87markwash: that makes more sense to me than having a separate store14:34
markwashwhich may be okay too, but feels super squicky to me14:34
zhiyan1jbresnah:cinder volume as a image, so it's glance's client. but i don't think there's a special privledges for cinder..14:34
jbresnahis the end use case so nova can find a volume to boot via glance?14:35
flaper87jbresnah: think so14:35
markwashjbresnah: basically14:35
flaper87ok, I got it right then14:35
*** Riddhi has quit IRC14:35
jbresnahso someone can 'get' the volume?14:35
icchawould the cinder store know that this image exists in glance other stores? or does glance become central point of authoirty over images/volume images now?14:35
markwashI think there is a constraint that the image should be bootable the "normal" way too14:35
jbresnahit just depends on where they are and what they can do?14:35
markwashiccha: in proposal B, glance stores the info in the locations table, cinder just treats the volume as usual14:36
markwashjbresnah: well, they can't download it through the http api14:37
flaper87markwash: iccha wich I think makes more sense14:37
jbresnahmarkwash: oh i see, so if it is the only location then it changes glance's assumed functionality14:37
markwashjbresnah: right14:37
markwashso maybe we just make it explicit that stores that can't download can't be the only locations ?14:38
markwashwow I failed at explicit I think14:38
flaper87lol14:38
markwashimages must have at least one location that can be downloaded from to be active14:38
markwashthat is fewer negatives14:38
icchashould we have additional info along with location to indicate store type or downloadable or not kind of information?14:38
jbresnahi think this is a fallout from the marriage of registry/replica service and data transfer service14:38
flaper87I think this shouldn't be used as a store and that services consuming images should check if the image has a "volume" property14:39
jbresnahi dont see it as horrible to have a EWECANTSERVETHATDATA14:39
zhiyan1markwash: we need keep forward-compatible i think, need support download, so justa localtion is not ok14:39
jbresnah... i probably should have used spaces14:39
markwashhaha14:39
markwashzhiyan1: it seems so strange though for people to want to download a volume from glance14:40
icchait might be ok to image info which locations you cant download from as long as there is a way to indicate downloadable locations vs not volumes etc14:40
icchabecause glance is image registry service basically right14:40
jbresnahso far i like having it as just another location, and throwing an error if you try to download it with only that location available14:40
*** qwerty_nor has joined #openstack-meeting-alt14:40
jbresnahbut i think i need to understand hte nova use case better14:40
esheffield+1 jbresnah14:40
*** Riddhi has joined #openstack-meeting-alt14:41
jbresnahiccha: yeah there should be a way to check if something is available for download14:41
jbresnahhow does nova boot from a volume now?  a specific flag saying use thing volume ID instead of an image ID?14:42
markwashsomething like that, but I don't recall exactly14:42
flaper87I don't think that just throwing an error when trying the service tries to download the image is good enough14:42
jbresnahand is the idea to make it always an image ID and pick the volume from that image ID in certain cases?14:42
zhiyan1jbresnah: this change not cover boot-from-volume, client need give volume id14:42
flaper87the location should contain that info, somehow14:42
mclarenhave we considered a /volumes resource?14:43
jbresnahi am confused because a volume boot has such different semantics over an image14:43
jbresnahso nova couldnt just pick a volume from glance without the use specifically saying to14:43
markwashmclaren: not that I know of14:43
jbresnahso i think i dont get the use case14:44
markwashshould we maybe have a followup discussion?14:44
markwashgive folks more time to prepare?14:44
flaper87markwash: +114:44
markwashokay cool14:44
iccha+114:44
zhiyan1ok, thanks14:44
markwash#action markwash schedule a followup meeting about the cinder store (at a time that is convenient to zhiyan please!)14:44
markwashThere were several other ongoing blueprints14:45
zhiyan1thanks guys :)14:45
flaper87zhiyan1: thank you14:45
markwash#topic async processing14:45
*** openstack changes topic to "async processing (Meeting topic: glance)"14:45
markwashI added a random assortment of ideas in code https://review.openstack.org/#/c/31874/114:45
markwashlet me know if you want me to add you as a reviewer, it is a draft so its restricted14:45
flaper87markwash: I commented on that draft few minutes ago14:46
markwashand also its pretty unclear still how some important parts would work14:46
markwashcool!14:46
ameademarkwash: add meh14:46
esheffieldmarkwash: I'd like to see that too14:46
zhiyan1markwash, pls add me?14:47
markwashsure14:47
rosmaitaand me and nikhil14:47
nikhil+114:47
markwashnikhil is on it14:47
mclarenmarkwash: me too if you can, thanks14:47
markwashokay I'm going to resubmit it as not a draft :-)14:47
nikhilI see that it's giving read only error in gerrit markwash14:47
markwashand jenkins can just deal14:47
nikhilthanks14:47
flaper87markwash: or, you could charge $10 for adding folks14:47
markwashhaha14:48
flaper87:D14:48
nikhilor just link us to ur github branch ?14:48
markwash#topic documentation14:48
*** openstack changes topic to "documentation (Meeting topic: glance)"14:48
nikhilmarkwash: ^^14:48
markwashiccha, esheffield updates about docs14:48
markwash?14:48
icchahttps://etherpad.openstack.org/glance_v1_vs_v214:48
markwashlooks like new stuff at the top?14:48
icchathe top part of etherpad has list of places where glance / image services documentation resides and how out of date/ missing info/incorrect info is listed14:49
markwash#link https://etherpad.openstack.org/glance_v1_vs_v214:49
*** Ekaterina_F has joined #openstack-meeting-alt14:49
icchaand also what the new documentation may need14:49
markwashlooks pretty good!14:49
zhiyan1yes,yes, seems good14:50
icchathe basic skeletal work of v1 vs v2 exists below, would be great to have ppl add in any info missed, or any other quirks or differences they have noticed in v2 vs v1 for ppl who would like to switch to be aware of14:50
jbresnahiccha: for v2 update it would be nice to see something about how "Content-Type: application/openstack-images-v2.0-json-patch and "Content-Type: application/openstack-images-v2.1-json-patch differ14:50
markwashI'll review that some more and then maybe we can figure out which thing we want to do next14:50
zhiyan1shall we push some encoding hits to the doc?14:51
zhiyan1probable somebady use non-ascii code string as the properties or some fields :)14:51
icchayes sure feel free to add anything you think which should be there14:51
icchathis is a very rough repository of all our collective knowledge14:51
markwashjbresnah: yeah hmm.. we should really push people in the direction of v2.1 and just ask that they never think about v2.0 if possible14:51
markwashhmm14:52
flaper87lol14:52
markwashv2.0 was compatible with draft 03 of the json-patch spec14:52
markwashv2.1 is compatible with the approved rfc version14:52
markwash6902 I think?14:52
icchajbresnah: that ll be great to add , are u volunteering to add it to etherpad :p14:52
markwash:-D14:52
flaper87iccha: he is14:52
flaper87:D14:52
jbresnahiccha: heh, i would but i asked because i need to learn the differences!14:52
markwash#topic import export clone14:52
*** openstack changes topic to "import export clone (Meeting topic: glance)"14:52
markwashrosmaita: a little bit of time. . .14:53
rosmaitaok, thanks, i think we're mostly agreed that a new resource is ok14:53
rosmaitaso post to /images/actions and get back a location14:53
rosmaitalike /images/actions/UUID14:53
rosmaitathen you poll the UUID14:53
rosmaitawhat you get back ...14:53
*** Ekaterina_F has quit IRC14:54
rosmaitadepends on what was in your request, something like { "import" : "stuff" }14:54
rosmaitalikewise for export, clone14:54
rosmaitaand what you get when you  poll the UUID coudl be different too14:54
rosmaitathat's actually my quyestions14:54
zhiyan1rosmaia: actually, i really not get the benefits from upload/download to import/export :) sorry for that, i have checked your wiki, but ..14:55
nikhil+114:55
nikhilrosmaita: +114:55
rosmaitain nova actions, there are 9, 7 dont return bodies14:55
markwashrosmaita: I had some thoughts in code about what an action would look like14:55
rosmaitathe 2 that do return different bodies14:55
rosmaitamarkwash: cool14:55
markwashshould be able to see it here in https://review.openstack.org/#/c/31874/1 now14:55
*** tanisdl has joined #openstack-meeting-alt14:56
esheffieldrosmaita: is the UUID basically an action identifier or the UUID of the image on which the action was taken? I assume the former?14:56
rosmaitaaction identifier14:56
nikhilmarkwash: yeah14:57
nikhilthanks14:57
markwashzhiyan1: the main benefit is that upload directly sets the data with no modifications14:57
markwashzhiyan1: import and export allow the format to change or for other lengthy processing to take place14:57
rosmaitazhiyan1: have u seen the mailing list discussion?14:58
zhiyan1yes, but not catch them...14:58
zhiyan1week ago, right?14:58
markwash(2 minutes left)14:58
rosmaitaright14:58
flaper87:(14:58
zhiyan1sorry, rosmaita, seems i need pick it up :(14:58
rosmaitazhiyan1: we cna talk in openstack-glance after mtg if you like14:58
markwashflaper87: did I skip you?14:59
zhiyan1goood :) thanks rosmaita.14:59
flaper87markwash: yup, registry-driver :D14:59
markwash#topic registry driver14:59
*** openstack changes topic to "registry driver (Meeting topic: glance)"14:59
zhiyan1:) 30s14:59
markwashI don't *think* there is anyone after us14:59
flaper87very quick, I'd love some feedback about this: http://lists.openstack.org/pipermail/openstack-dev/2013-June/009839.html14:59
markwashand won't turn into a pumpkin for another hour14:59
* ameade secretly just watched said disney movie15:00
flaper87the driver is *almost* done, I need to finish some tests that are being blocked by the fact that we don't have a way to deserialize datetimes15:00
markwashrusselb seemed to be poo-poo-ing that for some reason15:00
jbresnahheh ameade15:01
zhiyan1yes, you means primitive call right?15:01
flaper87so, I was thinking we could do something like nova does (convert strtime into datetime in the db_api function)15:01
markwashin json, it seems like datetimes should be objects that self-identify somehow15:01
flaper87markwash: some reason that 1) I still don't get 2) I disagree with what I got15:01
markwashflaper87: nod15:02
flaper87I don't think we need to define new models just to serialize / deserialize datetimes (which is what he's suggesting15:02
flaper87the other thing, that implementation won't land 'til H-315:02
flaper87which is bad for us15:02
*** tanisdl has quit IRC15:02
flaper87so, my suggestions are: 1) Implement datetime deserialization 2) do it in the sqlalchemy driver when needed15:02
flaper87#2 is the easiest15:03
flaper87but not the best, IMHO15:03
flaper87that's just a workaround15:03
markwashso do you want feedback on the ML or here or some other way?15:03
ameadei can't figure why a strtime would be getting to the sqlalchemy layer15:03
ameadebut i haven't been paying much attention to this15:03
flaper87both work for me, but if we do it in the m-l we better make sure to find a consensus15:04
ameadeoh rpc stuff right?15:04
markwashflaper87: then I better just talk to you in #openstack-glance :-)15:04
*** lastidiot has joined #openstack-meeting-alt15:04
flaper87markwash: +115:04
flaper87ameade: yup rpc stuff15:04
flaper87:(15:05
markwash#topic quick open discussion15:05
*** openstack changes topic to "quick open discussion (Meeting topic: glance)"15:05
flaper87I mean, :)15:05
flaper87:D15:05
flaper87can I say, We rock ?15:05
flaper87ok, I said it15:05
markwashdoes this meeting time work out okay?15:05
ameadeflaper87: we should just have all the services on one node :P15:05
markwashwe had mclaren and zhiyan so that part was great15:05
ameademarkwash: +115:05
mclarenthis time is great for me15:05
icchayup i agree good to have eveyrone included15:05
nikhil+115:05
zhiyan1:)15:06
* flaper87 thinks that jbresnah felt asleep again15:06
markwashjbresnah: can you deal with this once every two weeks?15:06
flaper87works for me, though15:06
ameadei dunno about having everyone here but the time is good15:06
ameade:P15:06
markwashhaha15:06
flaper87ameade: lol15:06
rosmaita+115:06
markwashokay cool, Imma call it15:06
jbresnahmarkwash: yeah probably15:06
markwash:-)15:06
ameadepeace out15:06
markwash#endmeeting15:07
*** openstack changes topic to "OpenStack meetings (alternate)"15:07
openstackMeeting ended Thu Jun  6 15:07:02 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:07
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-06-06-14.01.html15:07
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-06-06-14.01.txt15:07
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-06-06-14.01.log.html15:07
flaper87w00000000t15:07
markwashnext week meeting will be at the other time15:07
flaper87kk15:08
zhiyan1ok15:08
*** flaper87 has left #openstack-meeting-alt15:08
*** tanisdl has joined #openstack-meeting-alt15:09
*** bdpayne has joined #openstack-meeting-alt15:32
*** mclaren has quit IRC15:41
*** djohnstone has quit IRC15:57
*** djohnstone has joined #openstack-meeting-alt15:59
*** Riddhi_ has joined #openstack-meeting-alt16:00
*** tanisdl has quit IRC16:01
*** Riddhi_ has quit IRC16:01
*** Riddhi has quit IRC16:03
*** Riddhi has joined #openstack-meeting-alt16:06
*** IlyaE has joined #openstack-meeting-alt16:06
*** tanisdl has joined #openstack-meeting-alt16:08
*** dnosovit1ky has quit IRC16:13
*** djohnstone has quit IRC16:30
*** djohnstone has joined #openstack-meeting-alt16:30
*** djohnstone has quit IRC16:33
*** cp16net is now known as cp16net|away16:33
*** djohnstone has joined #openstack-meeting-alt16:34
*** johnthetubaguy has quit IRC16:37
*** johnthetubaguy has joined #openstack-meeting-alt16:37
*** akuznetsov has quit IRC16:40
*** tanisdl_ has joined #openstack-meeting-alt16:45
*** saurabhs has joined #openstack-meeting-alt16:45
*** tanisdl has quit IRC16:47
*** tanisdl_ is now known as tanisdl16:47
*** IlyaE has quit IRC16:56
*** cp16net|away is now known as cp16net17:04
*** esp has joined #openstack-meeting-alt17:09
*** Nikita has joined #openstack-meeting-alt17:10
*** Nikita has quit IRC17:10
*** esp has left #openstack-meeting-alt17:11
*** nkonovalov has joined #openstack-meeting-alt17:12
*** zhiyan1 has quit IRC17:18
*** johnthetubaguy has quit IRC17:19
*** dmitryme has joined #openstack-meeting-alt17:20
*** HenryG has quit IRC17:27
*** susanne-balle has joined #openstack-meeting-alt17:27
*** johnthetubaguy has joined #openstack-meeting-alt17:28
*** Riddhi has quit IRC17:33
*** pcm__ has quit IRC17:34
*** mestery_ is now known as mestery17:36
*** pcm___ has joined #openstack-meeting-alt17:36
*** Riddhi has joined #openstack-meeting-alt17:38
*** BalleS_ has joined #openstack-meeting-alt17:41
*** Riddhi has quit IRC17:43
*** susanne-balle has quit IRC17:44
*** dhellmann has joined #openstack-meeting-alt17:45
*** kagan has joined #openstack-meeting-alt17:45
*** Nadya has joined #openstack-meeting-alt17:57
*** mattf has joined #openstack-meeting-alt17:58
*** IlyaE has joined #openstack-meeting-alt17:58
*** aignatov2 has joined #openstack-meeting-alt18:00
SergeyLukjanovHi everyone18:02
SergeyLukjanovSavanna meeting will start in 5 minutes18:02
*** jmaron has joined #openstack-meeting-alt18:04
SergeyLukjanovShould we wait for someone?18:04
NadyaI think we'll start in 1 min18:05
jmaronJohn and Erik will not be joining today, if that's who you are waiting for...18:05
Nadyaoh, ok18:05
SergeyLukjanovjmaron, yep, thank you18:05
SergeyLukjanovI think we can start18:05
Nadya#startmeeting18:06
openstackNadya: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'18:06
Nadya#startmeeting savanna18:06
openstackMeeting started Thu Jun  6 18:06:09 2013 UTC.  The chair is Nadya. Information about MeetBot at http://wiki.debian.org/MeetBot.18:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:06
*** openstack changes topic to " (Meeting topic: savanna)"18:06
openstackThe meeting name has been set to 'savanna'18:06
*** akuznetsov has joined #openstack-meeting-alt18:06
Nadyahere is our agenda for today:18:06
Nadya1. Action items from previous meeting18:07
Nadya2. Updates18:07
Nadya3. convert() method18:07
Nadya4. IP discovery18:07
Nadya#topic Action items18:08
*** openstack changes topic to "Action items (Meeting topic: savanna)"18:08
NadyaSo, we had the following:18:08
NadyaACTION: ruhe add more details to savanna-dashboard blueprint (nprivalova, 18:52:38)18:08
NadyaACTION: SergeyLukjanov to update pluggable provisioning mechanism CR with latest ctx vision (SergeyLukjanov, 18:53:00)18:08
NadyaACTION: EricB create bp for Ambari (nprivalova, 18:56:43)18:08
NadyaSergey L, please update18:08
SergeyLukjanovyep, thank you18:08
*** Riddhi has joined #openstack-meeting-alt18:08
*** highlycaffeinate has joined #openstack-meeting-alt18:09
SergeyLukjanovok, we are working on the core part and I think that the beta version will be available tomorrow18:09
SergeyLukjanovoh, actions update)18:09
SergeyLukjanovsorry18:09
SergeyLukjanovwe was added details to BPs (links to mockups)18:10
Nadyait is usefull info, anyway :)18:10
SergeyLukjanovand I think that info about beta version of core part is actual for this question18:10
jmaronctx updates?18:10
*** Riddhi has quit IRC18:11
*** ruhe has joined #openstack-meeting-alt18:11
SergeyLukjanovaignatov send the letter with some details about using helpers18:11
SergeyLukjanovctx is partially implemented currently18:11
jmaronah..ok18:11
aignatov2I'v just replied on your question, jon18:11
SergeyLukjanovif you have some specific question, you're welcome :)18:11
*** Riddhi has joined #openstack-meeting-alt18:11
SergeyLukjanovadditionally, I think that we can make a call between me and plugin writer to discuss some things18:12
NadyaWe saw that Eric publiched blueprint so let`s move on18:12
SergeyLukjanovI mean integration we the core part18:12
jmaronok18:13
Nadya#topic Updates18:13
*** openstack changes topic to "Updates (Meeting topic: savanna)"18:13
NadyaAlex I, please update18:14
aignatov2ok, I'm working on vanilla plugin implementation18:14
aignatov2it's draft version on gerrit18:14
aignatov2you can observe it18:15
aignatov2#link https://review.openstack.org/#/c/31532/18:15
SergeyLukjanovit could be used as an example of using tools18:15
aignatov2jon, regarding your question, in my implemntation i'm operating only with cluster object18:16
SergeyLukjanovgenerally, there is no need to directly operate with context write know18:16
jmaronremind me which question that was?  ;)18:16
jmaronoh…ok.  now I understand.18:16
aignatov2Plugin Context object thread in savanna-all18:17
NadyaFrom my side: I'm preparing HOWTO document about Hadoop-Swift integration. Will start to work on Savanna integration tomorrow18:17
aignatov2another my update: also we have updated CR about fedora elements18:18
aignatov2there are some issues with installing rpm packages18:18
SergeyLukjanovmattf, thank you for contributing there18:18
ruhemattf, did you have a chance to build image with Fedora?18:19
aignatov2packages is not installing properly18:19
mattfmy pleasure18:19
mattfi didn't see the update, i must have fumbled on following the repo18:19
aignatov2just working on it to resolve issues18:19
ruheit's not there yet, we faced some issues, which could be caused by image-builder itself18:19
aignatov2link to CR18:20
aignatov2#link https://review.openstack.org/#/c/31218/18:20
SergeyLukjanovare there any other updates?18:20
SergeyLukjanovjmaron, maybe from your side?18:20
mattfi didn't complete building a fedora image after i learned you were already working on it18:20
Nadyadoes anyone else have updates?18:21
mattfi'll take a look at 3121818:21
jmaronwe are progressing well with the ambari plugin.  we're at the point where we need to make sure the integration with savanna api is complete and working, hence my questions about setting up a virtual env18:21
jmaronand we'll need to migrate some of our functionality to the ctx helpers, though I imagine we could keep some of that as is for the first iteration18:22
jmaron(direct use of ssh etc)18:22
SergeyLukjanovjmaron, I think we can have a talk with you about it, let's discuss it after the meeting18:22
aignatov2mattf, please feel free to comment it, Ivan sent several questions to diskimage-builder guys, but there is no answeres yet (18:22
jmaronok18:23
mattfaignatov2, have a pointer to the dib questions?18:23
aignatov2one sec18:24
SergeyLukjanovhere it is18:24
SergeyLukjanov#link http://lists.openstack.org/pipermail/openstack-dev/2013-June/009938.html18:24
Nadya#topic convert() method18:25
*** openstack changes topic to "convert() method (Meeting topic: savanna)"18:25
NadyaSergey L, please18:25
SergeyLukjanovmm, I want to take a small story about how we see this functionality18:25
*** jbresnah has left #openstack-meeting-alt18:25
SergeyLukjanovin todays discussions we are extend templates to include all information from cluster18:25
aignatov2mattf, It will be great to have rhel and/or centos instructions for creating cloud images to work with Savanna18:26
SergeyLukjanovso, we want to make user able to create cluster from cluster template specifying only cluster name and user key18:26
aignatov2do you have any thoughts? As I know DIB doesn't support these distros(18:26
SergeyLukjanovdue to this update it'll be cool if plugins would convert plugin-specific config files to cluster template18:26
mattfaignatov2, #link https://github.com/mattf/savanna/blob/RDO-quickstart/doc/source/rdo_quickstart.rst <- first draft of single node setup, rdo has changed a bit recently that's slowed production of the multi-node instructions18:27
SergeyLukjanovit provide an absolutely wide flexibility of using them18:27
SergeyLukjanovbtw cluster template could contain node groups description w/o node groups templates18:27
mattfaignatov2, i have dib working on fedora 17 to produce ubuntu savanna images and vanilla fedora images. i had to submit a few patches to dib to get it working.18:28
Nadyaby the way, we are discussing convert() method for the flow when user wants to create cluster from some configuration file which cannot be parsed by Savana. So it is needed to convert it into Template or cluster object18:28
SergeyLukjanovI'll describe it with additional details tomorrow18:28
SergeyLukjanovjamaron, do you have any thoughts on adjusting convert to converting config file to cluster template?18:28
SergeyLukjanovsorry, jmaron18:28
jmaronjust so I understand:  you are proposing that the convert method be changed from populating the cluster object to actually creating a savanna cluster template?18:29
SergeyLukjanovyes, because we want to make cluster templates fully describe cluster18:29
aignatov2mattf, that's really cool instruction. can we add these instruction to the main savanna repo in future?18:30
mattfabsolutely18:30
SergeyLukjanovso, if this cluster template will provide some configs that could be overrided while cluster creation than it will be an additional flexibility18:30
aignatov2great!18:30
jmarononce the cluster object is populated, it would be a simple matter for the controller/UI to relate the information in the returned cluster object, the process it goes through to create a cluster object model anyhow18:30
SergeyLukjanovand it could provide an ability for users to make some configs changes18:30
SergeyLukjanovjmaron, do you have plans to extract some config params from config file to cluster object>18:32
SergeyLukjanov?18:32
jmaronwhether we are using standard or provider specific templates, remember that both are essentially tied to a specific provider18:32
SergeyLukjanovyep, cluster templates are provider-specific too18:32
SergeyLukjanovI mean that you can extract some parameter from the provier-specific config18:32
Nadyajmaron, have you already started to implement convert()?18:32
jmaronthat's what convert() does, per the email exchange from a few days ago...18:32
jmaronconfig properties in the provider template are populated into the cluster user_inputs18:33
SergeyLukjanovjmaron, I'm very sorry, there are tons of discussions on this topic...18:33
ruhejmaron, convert() reruns cluster object which is essentially the same as cluster template18:33
jmaronagreed18:34
SergeyLukjanovrune, yes, that's I mean :)18:34
jmaronwe'd still prefer to return a populated cluster object.  persisting the contents of that cluster object into a template is probably an option the UI could support18:34
ruheso, if we make convert() to return cluster template, we don't loose anything. we just get all the features which templates have - user will have a lot of options to view/edit them18:35
Nadyajmaron, have you already started to implement convert()?18:35
jmaronwe've completed it18:35
SergeyLukjanovjmaron, I think it'll be clearer to use only one flow for cluster creation - from templates and supporting cluster template creation from provider-specific config file18:36
SergeyLukjanovyou still can use extra in it18:36
dmitrymejmaron, it would be great if you can already share your code18:36
dmitrymein that case we could find differences between your and our code earlier18:36
jmaronperhaps early next week.  we still need to refine some and John, who wrote it, is out for the next couple of days18:37
SergeyLukjanovprovider-specific templates is in general equals to our cluster templates18:37
*** markwash_ has joined #openstack-meeting-alt18:38
jmaronI don't understand why we need to return a cluster template rather than a cluster.  a template is simply a representation of the cluster object.  call __repr__ if you like to get the template out of it.  why generate a file as part of the runtime functionality?18:39
SergeyLukjanovI think that codebase will not be changed if convert to cluster templates instead of cluster18:39
ruhejmaron, you don't need to generate a file. you only need to generate an object representing cluster template18:40
*** IlyaE has quit IRC18:40
jmaronwhich is basically the cluster object!18:40
SergeyLukjanovbut cluster is an instance of cluster template18:41
jmaronso?18:41
SergeyLukjanovand user can create cluster template from pconfig file18:41
*** markwash has quit IRC18:41
*** markwash_ is now known as markwash18:41
SergeyLukjanovand then just use it to creating clusters18:41
jmaronyou want the conversion to occur prior to the creation flow?18:41
SergeyLukjanovI think that we should discuss it when you share your code18:41
SergeyLukjanovjmaron, yes18:42
Nadyajmaron, I see your point. Let`s postpone this discussion, we need to look at code18:42
ruhelet's move this conversation to the mailing list or to #savanna18:42
jmaronI think we're just confusing the users more.  We should be aiming to streamline the flow into a simple "pick your template" whether it's a savanna or provider one, iterate thru the steps, and submit18:42
SergeyLukjanovto not create some different flows of cluster creation that could be not clear for end-users18:42
SergeyLukjanovI think that it's great that we share that vision with team18:43
SergeyLukjanovand let's continue discussions later18:43
jmaronI would say we've just added a separate flow (convert your template).  the UI can be structured in such a way that the steps are clear and unified18:44
jmaronok18:44
Nadyajmaron, will we have 2 different cluster-creatin UI-flow?18:44
Nadyajmaron, I understood, 1 flow :)18:45
SergeyLukjanovin fact we just want to make some small changes in UI :)18:45
SergeyLukjanovbut let's go on18:45
SergeyLukjanov:)18:45
Nadya#topic IP discovery18:45
*** openstack changes topic to "IP discovery (Meeting topic: savanna)"18:45
SergeyLukjanovI propose the BP for the simple implementation of it18:46
SergeyLukjanovhere it is18:46
SergeyLukjanov#link https://blueprints.launchpad.net/savanna/+spec/ips-discovery-mechanism18:46
SergeyLukjanovare there any thoughts on it?18:46
jmaronwe took a look at that implementation.  at the moment that looks acceptable18:47
rnirmalwhy define them again in savanna.. can't they be defined in nova and in savanna just refer to which network maps to management / private and public18:47
mattfi've some, but they're incomplete18:47
rnirmaland savanna can use the appropriate ips for the instances provided by nova18:48
jmaronthat's the problem - we've encountered deployments where that private/public distinction isn't clear18:48
SergeyLukjanovrnirmal, it's not clear to determine which addresses should be used for different purposes18:48
mattfthe mananagement ip makes sense if you think about it as = "internal" or "public", not necessarily by itself. i don't think savanna generates enough traffic to warrant its own network18:48
rnirmalSergeyLukjanov: well won't that be part of the provider or who ever is setting it up to sync that18:49
mattfi'm not bought into the idea of "discovering" via savanna config - it appears it's duplicate config with the authoritative existing in nova-network / quantum18:49
mattfi.e. if you change floating ips in nova-network you also have to inform savanna -> leads to complications for admins18:49
SergeyLukjanovnova-network/quantum are both doesn't provide an ability to understand which ip is available for user18:49
mattffyi, my current floating range isn't easily expressed as x.y.z/p18:50
SergeyLukjanovand which should be used for communication between Hadoop nodes18:50
mattfquite possible we should be requesting enhancement in nn/q then18:50
rnirmalnot sure don't all the ips provided by nova-network or quantum accessible by the user18:50
*** Riddhi has quit IRC18:50
jmaronthat's great and the ideal - but we're seeing deployments where the private, public, float ip distinction isn't made clear via nova and there is reluctance to change the networking18:51
mattfi was hoping to look into the ability to tag interfaces, i.e. pub=10.0.0.1,priv=192.168.0.0 on instances, then config savanna to have internal_ip=priv, public_id=pub -- but i haven't had a chance yet18:51
mattfrnirmal, that's probably true, it'd be scoped to the tenant, but savanna knows tenant -- that's another good reason to not use savanna config18:52
mattf...you'll end up needing [networks] for each potential tenant?18:52
SergeyLukjanovif fact we can demand on networks names or specify networks in savanna18:52
rnirmalmattf: agree18:52
*** markwash has quit IRC18:52
mattfi'm also not clear on why the internal_ip would be added to /etc/hosts18:52
rnirmalthat would be for name resolution for hadoop I suppose18:53
dmitrymernimal: exactly18:53
mattf(fyi, this is all half formed, i was hoping to think it through more before responding on savanna-all)18:53
jmaronbut don't all those os based solutions assume that the given OS provider is willing to modify their networking to accommodate the solution?18:53
rnirmaljmaron: but not sure how defining them within savanna is going to help either18:54
*** vipul is now known as vipul|away18:54
*** vipul|away is now known as vipul18:54
jmaronthey have to be defined somewhere18:54
jmaronand if you can't control the OS stack18:54
mattfjmaron, there's definitely an issue around best practices. if an OS deployment isn't naming interfaces in a consistent / discoverable way, it's hard to do discovery18:54
jmaronsavanna is your only choice18:54
rnirmalnova provides tagged ips as such public=10.127.1.15; private=192.168.0.1518:54
jmaronand that's exactly what we're finding18:54
rnirmalor whatever be their names18:54
SergeyLukjanovgenerally, I do not like this approach too, but I have no ideas to implement this functionality...18:54
jmaronrnirmal:  not in a deployment I saw this week18:55
rnirmaland in savanna just map them to what savanna understands as internal and public ips18:55
SergeyLukjanovrnirmal, our OS installed in dev lab doesn't provide such tags18:55
*** flaper87 has joined #openstack-meeting-alt18:55
jmaronneither does the deployment at a customer site18:55
mattfand the one in my site is different from jmaron's18:55
jmaronand the customer will not change the deployment18:55
SergeyLukjanovjmaron, +118:56
aignatov2guys, 5 minutes left18:56
rnirmalhmm ok so how would you see implementing that within savanna18:56
mattfthere's still the idea of being able to discover by querying the tenant18:56
jmaronwith a sub-optimal approach ;)18:56
jmaronmattf:  I'd need to understand that better18:56
mattfi tend to de-dup config, because config is so easy for people to get wrong18:57
*** Riddhi has joined #openstack-meeting-alt18:57
mattfjmaron, me too18:57
mattfit's definitely a complex topic and worthy of some focused time18:57
rnirmal:) but on instance create does savanna pass in network info ?18:57
mattf+1 SergeyLukjanov for generating a bp so we have a place to discuss, but i'm skeptical w/ the current proposal18:57
SergeyLukjanovmattf, can you point us to API that provides info about networks destination?18:57
*** Riddhi has quit IRC18:57
*** malini has joined #openstack-meeting-alt18:58
mattfSergeyLukjanov, not atm, that's what i haven't gotten to yet in forming my understanding18:58
*** ametts has joined #openstack-meeting-alt18:58
ruheif there is a way to to get that info about tenant from nova/quantum, it would be great18:58
rnirmalanother topic to add to this discussion would be private networks support for the hadoop internal ips18:58
jmaronthat would be the ideal18:58
mattfif there isn't, it's an opportunity for the savanna community to contribute to the openstack networking community18:59
SergeyLukjanovBP creation is ok18:59
SergeyLukjanovmattf, we want to support not only the trunk version of openstack18:59
*** Riddhi has joined #openstack-meeting-alt18:59
mattfSergeyLukjanov, well, short term there's no feature, long term we should aim for closer integration w/ os networking19:00
mattfin between, who knows19:00
*** kgriffs has joined #openstack-meeting-alt19:00
jmaronsavanna filtering approach could be viewed as "last resort" but workable in some deployments, I suppose19:00
mattfwe should continue on #savanna and savanna-all19:00
Nadyayes19:00
Nadyawe are out of time :(19:01
NadyaThank you all19:01
*** cppcabrera has joined #openstack-meeting-alt19:01
mattfthanks all19:01
jmaronthanks19:01
aignatov2thanks19:01
ruhethanks19:01
SergeyLukjanovthank you guys19:01
Nadya#endmeeting19:01
*** openstack changes topic to "OpenStack meetings (alternate)"19:01
openstackMeeting ended Thu Jun  6 19:01:43 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-06-06-18.06.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-06-06-18.06.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-06-06-18.06.log.html19:01
kgriffsmarconi team - we are testing out mumble for this meeting, with notes taken with meetbot.19:02
*** nkonovalov has quit IRC19:03
kgriffssome folks are having trouble connecting19:04
kgriffsshall we just do IRC only this time, or go to plan B (G+)?19:04
*** mattf has left #openstack-meeting-alt19:04
*** ruhe has left #openstack-meeting-alt19:04
flaper87plan B19:05
*** jmaron has left #openstack-meeting-alt19:05
*** megan_w has joined #openstack-meeting-alt19:05
cppcabreraplan B works for me.19:05
kgriffsOK19:05
kgriffsstand by19:05
*** Nadya has quit IRC19:06
amettsOh.  Plan B is G+.  I thought Plan B was IRC.  I'm so confused....19:06
*** jrodom has joined #openstack-meeting-alt19:06
* flaper87 will fix someday that stupid ,ic19:07
flaper87mic19:07
cppcabreraPlan A.1 is IRC.19:08
kgriffshttps://plus.google.com/hangouts/_/2b91b6fea2d02e4c67c6657e98afedafa19abb4e19:09
*** vipul is now known as vipul|away19:09
kgriffstrying to figure out how to do "on air" in the new interface19:09
*** kagan has quit IRC19:09
kgriffsgive me 2 minutes, otherwise plan C - plain-old-irc19:09
kgriffs:p19:09
flaper87isn't it hangout public ?19:10
flaper87I mean, public circles19:10
kgriffsyes, but I wanted to record for posterity19:10
flaper87oh, I see19:10
flaper87erm, mmh, erm!19:11
flaper87no idea19:11
kgriffscan everyone join this19:11
kgriffshttps://plus.google.com/hangouts/_/43e14b608e33ae127ec6ab4852f0128ae0d8a87819:11
kgriffsthis second one is "on air"19:11
*** akuznetsov has quit IRC19:11
kgriffsfirst topic: experimenting with new ways to collaborate. :p19:12
amettsDid you start the meetbot meeting?19:12
kgriffsflaper87: you coming?19:12
flaper87kgriffs: yup19:13
flaper87joining19:13
kgriffs#startmeeting marconi19:14
openstackMeeting started Thu Jun  6 19:14:20 2013 UTC.  The chair is kgriffs. Information about MeetBot at http://wiki.debian.org/MeetBot.19:14
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:14
*** openstack changes topic to " (Meeting topic: marconi)"19:14
openstackThe meeting name has been set to 'marconi'19:14
kgriffs#link http://youtu.be/sDUw1Je_JJE19:15
flaper87I'm in but I can't hear anything19:16
kgriffsit said you left19:16
kgriffshttps://plus.google.com/hangouts/_/43e14b608e33ae127ec6ab4852f0128ae0d8a87819:16
kgriffstry again?19:16
amettsFlavio Percoco Premoli joined group chat.19:16
amettsFlavio Percoco Premoli left group chat.19:16
amettsFlavio Percoco Premoli joined group chat.19:16
amettsFlavio Percoco Premoli left group chat.19:16
kgriffsyou were there for a sec19:17
flaper87it throws some error on the video call19:17
kgriffscan you do sound only?19:17
kgriffsok, give up?19:17
kgriffs#topic audio meetings19:18
*** openstack changes topic to "audio meetings (Meeting topic: marconi)"19:18
kgriffs#action flaper87 to fix his mic19:18
kgriffs:D19:18
flaper87sorry guys, this stupid update doesn't seem to work correctly19:18
flaper87LOOOL19:18
kgriffs#topic H1 milestone closure19:19
*** openstack changes topic to "H1 milestone closure (Meeting topic: marconi)"19:19
flaper87I think I'm in19:19
*** Nadya has joined #openstack-meeting-alt19:19
flaper87kgriffs: saw you19:19
kgriffsok, let's try again another time - i think it had something to do with the "on air"19:19
kgriffsso, re H119:20
flaper87kk19:20
kgriffsit is now behind us19:20
kgriffsso, we need to update the bp's and trello cards19:20
flaper87kk19:20
kgriffswe made good progress on all the stuff we planned, but just didn't bring them all to closure19:21
kgriffsso, I can just move back everything, but wanted to ask if there was anything we had scoped for H1 that turned out to be lower priority and should be moved maybe to H3 instead of H219:22
kgriffshttps://trello.com/board/openstack-marconi/511403287d138cd6200078e019:22
* flaper87 checking19:23
kgriffsfor example, "validate input" I think we need before launch, but not immediate19:23
kgriffs(look at the "next up")19:23
kgriffsI'm wondering if we need that "next up" list, or just merge with the milestone lists?19:23
flaper87kgriffs: +1 for merge19:24
kgriffsany objections?19:24
flaper87the more focus in 1 column we can be the better19:24
flaper87focused*19:24
*** sdake_ has joined #openstack-meeting-alt19:25
*** sdake_ has quit IRC19:25
*** sdake_ has joined #openstack-meeting-alt19:25
kgriffs#agreed Merge "next up" list with milestone list19:25
kgriffsalso, I'd like to add a Havana-3.a19:26
flaper87kgriffs: +119:26
kgriffsBasically, I would like something to target for "pretty much production ready"19:26
kgriffsH3 will be for stabilization and whatever19:27
flaper87makes sense19:27
flaper87there's a limit for introducing new features19:28
kgriffsOK, let me do this. I will take a first pass and moving the cards around, and you guys can complain loudly in #openstack-marconi if you don't like what you see.19:28
flaper87IIRC it is september19:28
flaper87ok19:28
flaper87LIKE THIS ?19:28
kgriffsthat's about right. :D19:28
amettsIs some of the Havana-2 stuff optional?  We really going to add WebScoket, qpid, Kombu, etc?19:29
kgriffs#action kgriffs to clean up trello board, get things prioritized better19:29
flaper87ametts: I read those as "Nice to Have"19:29
flaper87TBH19:29
amettsMe too.19:29
kgriffsso, re incubation, can we put all the alternate drivers in September-ish timeframe?19:30
flaper87but we should definitely target them and focus on the column as "Must Have"19:30
flaper87kgriffs: sure19:30
kgriffsOK19:30
kgriffs#topic bugs19:31
*** openstack changes topic to "bugs (Meeting topic: marconi)"19:31
kgriffsSo, just wanted to get updates on bug fixes that are in progress19:31
malinibefore that, can we also define a time line for the marconi client ?19:32
flaper87kgriffs: I was working on Autoreconnect19:32
kgriffsmalini: let's do that next topic19:32
flaper87that discussion is still pending19:32
kgriffs#link https://bugs.launchpad.net/marconi/+bug/116982119:32
kgriffsOK19:32
kgriffsso, let's talk about that for a couple mins19:33
flaper87so, It basically works but it could be improved before letting it land19:33
flaper87cool19:33
kgriffsok, so your wrapper is only for reads, correct?19:33
* kgriffs is looking19:34
flaper87nope19:34
flaper87it is for everything, basically19:34
flaper87the big problem are reads, though19:34
flaper87the reason for that is that reads happen in the Cursor19:34
kgriffsoh, is there any danger of getting part way through a bulk insert and getting a disconnect error?19:35
kgriffs(ConnectionFailure)19:35
flaper87Autoreconnect should be raised before sending the bulk19:35
flaper87so, it would just retry19:35
kgriffs#link https://review.openstack.org/#/c/30230/2/marconi/storage/mongodb/utils.py19:35
kgriffsif the socket connection simply get's dropped, what happens?19:36
flaper87pymongo tries to connect without raising any error19:36
flaper87it raises an error when that attempt of connection fails19:36
kgriffseven halfway through a write?19:37
flaper87ah, you mean in the middle of the operation19:37
flaper87erm, well...19:37
flaper87we could remove the retry stuff19:37
kgriffsbasically, I just want to be sure we aren't doing a generic retry halfway through an insert, since the caller needs to reset the generator19:37
flaper87I'm honestly not sure whether we should be handling it at all. I mean, Marconi doesn't know what to do when AutoReconnect happens19:39
flaper87right? It just knows there was an error19:39
flaper87should we just return an error in the API?19:39
flaper87that question is valid even if we handle the Autoreconnect19:39
flaper87since mongodb might be completely innaccesible19:39
flaper87(dunno if that word exists)19:39
flaper87The other thing is that Cursors are lazy19:40
kgriffswell, the trouble is, in the case of a bulk message post, there is no way to know how many messages succeeded if we drop the connection halfway through. I guess with Mongo there isn't much to do about it?19:40
flaper87and none of the read operations will raise any error until they are truly consumed19:40
flaper87and that happens in the transport side19:40
kgriffskk19:40
kgriffsso, iterating that cursor could raise an AutoReconnect?19:41
flaper87yup19:41
flaper87so, crazy idea19:41
kgriffsthe plot thickens...19:41
*** sdake_ has quit IRC19:42
flaper87what if we have some kind of "abstract decorator" implemented in every storage that "knows" how to handle "storage specific errors" that might happen in the transport side?19:42
*** sdake_ has joined #openstack-meeting-alt19:42
*** sdake_ has quit IRC19:42
*** sdake_ has joined #openstack-meeting-alt19:42
flaper87or just possible exceptions19:42
flaper87so that it is possible to do in the transport side something like19:42
kgriffsok, so the transport could ask the driver for that thing, maybe it could be a context manager?19:43
flaper87try ... except self.storage.CatchThatStuff: ...19:43
kgriffsyeah, ok19:43
flaper87yeah, something like that19:43
kgriffssomething like that could work19:43
flaper87oke-doke19:43
kgriffsok, so we have two things to solve here19:43
kgriffsfirst, reads19:43
kgriffssecond, writes19:43
malinimaybe we are getting too focussed on a single bug ? *brings out her irritating cow bell*19:43
amettsRock on, malini!19:44
kgriffsdo we need to experiment to see if AutoReconnect errors are possible halfway through a bulk insert?19:44
kgriffsheh19:44
flaper87I think they are19:44
kgriffsOK, let's move on, but sounds like there's some homework19:44
flaper87at least a ConnectionFailure could be raised19:44
amettsAnd hey, if everything works besides reads and writes, we're good... no?19:44
flaper87ok, I'll re-write that patch along these lines19:44
kgriffsOK, can u verify what happens with bulk inserts?19:45
flaper87kgriffs: will do19:45
kgriffs(simulate a primary failover, see what happens)19:45
kgriffsexcellent19:45
flaper87ametts: as far as deletes work, we're fine19:45
flaper87:P19:45
amettsSounds like an awesome queue. :)19:45
kgriffs#action flaper87 to experiment with bulk insert behavior on mongo connection errors19:45
* flaper87 STFU19:45
kgriffs#action flaper87 to update AutoReconnect patch to handle read cursor errors19:46
kgriffsok, I know this bug is also in progress, any quick thoughts before we move off the bugs topic?19:47
kgriffs#link https://bugs.launchpad.net/marconi/+bug/118728019:47
*** aignatov2 has left #openstack-meeting-alt19:47
flaper87patch waiting for review19:47
kgriffskk, I think we can land this one pretty quickly. Looks like Jenkins is happy again19:48
kgriffsCan everyone re-review?19:48
* flaper87 hates eventlet19:48
amettsFWIW, there's a fair amount of overlap between several of these bugs, input validation, and failing system tests.19:48
flaper87marconi/tests/common/__init__.py19:49
flaper87renamed from lib/marconi_paste.py19:49
flaper87WTF?19:49
flaper87Jenkins is crazy19:49
kgriffsyes, the remaining bugs are mostly due to holes in the implementation re the API spec19:49
kgriffsheh19:49
*** dmitryme has quit IRC19:49
kgriffs#topic blueprints19:49
*** openstack changes topic to "blueprints (Meeting topic: marconi)"19:49
flaper87ametts: they exist just to make us beleive we're going faster19:49
kgriffsQA cluster news?19:49
flaper87we can close 2 bugs with 1 patch19:49
* flaper87 STFU19:49
flaper87I know, I've said it before19:49
amettsflaper87: LOL19:49
* kgriffs didn't hear anything19:50
maliniWe havent made much progress on the QA cluster since last time19:50
* kgriffs sad panda19:50
kgriffsany blocking issues?19:50
maliniits just that oz_akan had other priorities this week19:51
kgriffskk, will he be back on this next week?19:51
maliniyes19:51
kgriffskk, keep us posted19:52
amettsQA cluster runs system tests with every commit?19:52
*** SergeyLukjanov has quit IRC19:52
maliniits not hooked into jenkins yet19:52
maliniBut we'll be there soon19:52
kgriffs+119:52
kgriffshow about performance tests?19:52
maliniI have the xmls (i.e defining scenarios/loads etc.) ready19:53
maliniSo we are ready to run them when we have the cluster19:53
kgriffsexcellent19:53
kgriffsnice work19:53
maliniAlso, can I move those xmls to the marconi repo ?19:53
maliniunder tests/performance ?19:53
kgriffsand that will be triggered by patch submissions as well?19:53
maliniyes19:53
kgriffsflaper87: thoughts on where those should live?19:54
* ametts Wants to make sure we save time for a quick marconiclient discussion19:54
*** Riddhi has quit IRC19:54
flaper87mmhh, not right now, not sure if those should go into the tree19:54
kgriffsok, let's discuss in #openstack-marconi19:55
maliniok19:55
flaper87kk19:55
kgriffs#topic python-marconiclient19:55
*** openstack changes topic to "python-marconiclient (Meeting topic: marconi)"19:55
kgriffsnext steps, timing?19:55
maliniwe are stalled on the client because of Alessio's patch.19:55
*** mtreinish has quit IRC19:55
amettsJust noticed that stackforge/python-marconiclient doesn't have jdprax's original stuff  in it, but it does have Alessio's patch pending.19:55
amettsWhat's the plan -- we start with the patch and fold in jdprax's original stuff?19:56
flaper87ametts: so, the plan was to give alessio's code a try, and help improving that code19:56
flaper87The code proposed there is meant to be a shared client library that will, eventually, land in oslo19:57
flaper87but, it needs a lot of work and cleaning19:57
kgriffscan malini help with that work and cleaning?19:57
*** mtreinish has joined #openstack-meeting-alt19:57
amettsOk -- so that forms the base and it gets called by other stuff for marconi-specific things?19:58
maliniI emailed Alessio & at this point he badly needs reviews to merge his stuff into oslo-incubator19:58
kgriffswait - I thought he was merging this into python-marconiclient first?19:58
amettsIs there anything of value that gets reused from the jdprax stuff?19:58
flaper87kgriffs: yup19:58
*** vipul|away is now known as vipul19:58
flaper87first into marconiclient19:58
flaper87kgriffs: malini can help for sure19:59
malinihmm..So we dont need the oslo incubator stuff ?19:59
flaper87we should start reviewing that patch 'til the last bit19:59
*** djohnstone1 has joined #openstack-meeting-alt19:59
*** Riddhi has joined #openstack-meeting-alt19:59
maliniSo if we can get https://review.openstack.org/#/c/29255 fixed, we shud be good to go ?20:00
kgriffs(note: we are out of time, let's wrap up)20:00
flaper87malini: sort of, yeah20:00
flaper87we can keep discussing this stuff right now on #os-marconi20:01
*** djohnstone has quit IRC20:01
kgriffs#action malini and flaper87 to continue api client discussion elsewhere20:01
kgriffstwo parting thoughts20:01
*** Riddhi_ has joined #openstack-meeting-alt20:02
kgriffsmalini, can you add a few very basic security tests, maybe just fuzzing?20:02
kgriffsone possibility: http://gauntlt.org/20:02
maliniyes, I'll start looking at what we can add20:02
kgriffssecond thought, please review this RFC on the project: https://etherpad.openstack.org/queuing-scratch20:02
kgriffsok, thanks folks20:02
kgriffswe will shift some agenda items to next week.20:03
kgriffs#endmeeting20:03
*** openstack changes topic to "OpenStack meetings (alternate)"20:03
openstackMeeting ended Thu Jun  6 20:03:31 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-06-19.14.html20:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-06-19.14.txt20:03
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-06-19.14.log.html20:03
*** Riddhi has quit IRC20:04
*** Riddhi_ is now known as Riddhi20:04
*** dosaboy has quit IRC20:07
kgriffsNotes copied to wiki: https://wiki.openstack.org/wiki/Meetings/Marconi#Previous_meetings20:08
*** flaper87 has left #openstack-meeting-alt20:08
*** Riddhi has quit IRC20:09
*** Riddhi has joined #openstack-meeting-alt20:09
*** qwerty_nor has quit IRC20:10
*** highlycaffeinate has left #openstack-meeting-alt20:10
*** ametts has left #openstack-meeting-alt20:10
*** dmitryme has joined #openstack-meeting-alt20:12
*** mtreinish has quit IRC20:13
*** malini is now known as malini_away20:14
*** mtreinish has joined #openstack-meeting-alt20:15
*** pcm___ has quit IRC20:15
*** cppcabrera has left #openstack-meeting-alt20:17
*** kagan has joined #openstack-meeting-alt20:18
*** tanisdl_ has joined #openstack-meeting-alt20:19
*** tanisdl has quit IRC20:21
*** tanisdl_ is now known as tanisdl20:21
*** SergeyLukjanov has joined #openstack-meeting-alt20:33
*** Nadya has quit IRC20:33
*** johnthetubaguy has quit IRC20:43
*** Nadya has joined #openstack-meeting-alt20:45
*** Nadya has quit IRC20:50
*** megan_w has quit IRC21:00
*** jrodom_ has joined #openstack-meeting-alt21:01
*** jrodom_ has quit IRC21:01
*** jrodom has quit IRC21:04
*** jrodom has joined #openstack-meeting-alt21:05
*** jrodom has quit IRC21:10
*** mtreinish has quit IRC21:13
*** jrodom has joined #openstack-meeting-alt21:14
*** jrodom has quit IRC21:20
*** bdpayne has quit IRC21:20
*** Riddhi has quit IRC21:21
*** demorris has quit IRC21:21
*** Riddhi has joined #openstack-meeting-alt21:26
*** dmitryme has quit IRC21:32
*** amytron has quit IRC21:34
*** malini_away is now known as malini21:37
*** malini has left #openstack-meeting-alt21:38
*** jrodom has joined #openstack-meeting-alt21:47
*** jrodom has quit IRC21:47
*** jrodom has joined #openstack-meeting-alt21:48
*** demorris has joined #openstack-meeting-alt21:58
*** kgriffs has left #openstack-meeting-alt21:59
*** dhellmann is now known as dhellmann-away22:02
*** markwash has joined #openstack-meeting-alt22:06
*** SergeyLukjanov has quit IRC22:15
*** esheffield has quit IRC22:17
*** djohnstone1 has quit IRC22:18
*** lastidiot has quit IRC22:27
*** sdake_ has quit IRC22:33
*** markwash has quit IRC22:35
*** markwash has joined #openstack-meeting-alt22:36
*** vipul has quit IRC22:36
*** vipul has joined #openstack-meeting-alt22:48
*** rnirmal has quit IRC22:48
*** pcm__ has joined #openstack-meeting-alt22:58
*** pcm__ has quit IRC22:58
*** pcm__ has joined #openstack-meeting-alt22:59
*** vipul has quit IRC23:01
*** jrodom has quit IRC23:04
*** vipul has joined #openstack-meeting-alt23:04
*** seanrob has joined #openstack-meeting-alt23:09
*** seanrob_ has joined #openstack-meeting-alt23:12
*** seanrob has quit IRC23:16
*** BalleS_ has quit IRC23:16
*** sdake_ has joined #openstack-meeting-alt23:19
*** sdake_ has quit IRC23:19
*** sdake_ has joined #openstack-meeting-alt23:19
*** jrodom has joined #openstack-meeting-alt23:22
*** seanrob_ has quit IRC23:24
*** seanrob has joined #openstack-meeting-alt23:24
*** seanrob has quit IRC23:28
*** lastidiot has joined #openstack-meeting-alt23:34
*** seanrob has joined #openstack-meeting-alt23:34
*** seanrob_ has joined #openstack-meeting-alt23:37
*** seanrob has quit IRC23:37
*** seanrob has joined #openstack-meeting-alt23:43
*** seanrob__ has joined #openstack-meeting-alt23:44
*** seanrob has quit IRC23:45
*** seanrob_ has quit IRC23:46
*** seanrob__ has quit IRC23:48
*** demorris has quit IRC23:48
*** seanrob has joined #openstack-meeting-alt23:48
*** Riddhi has quit IRC23:50
*** kagan has quit IRC23:50
*** Riddhi has joined #openstack-meeting-alt23:51
*** zzs has joined #openstack-meeting-alt23:51
*** Riddhi has quit IRC23:52
*** seanrob_ has joined #openstack-meeting-alt23:55
*** seanrob has quit IRC23:55

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