Monday, 2013-11-18

*** ashaikh has quit IRC00:06
*** flwang has joined #openstack-meeting-alt00:14
*** sarob has joined #openstack-meeting-alt00:32
*** jmaron has joined #openstack-meeting-alt00:34
*** jmaron has quit IRC00:39
*** dolphm has quit IRC00:39
*** boris-42 has joined #openstack-meeting-alt01:03
*** markwash has joined #openstack-meeting-alt01:05
*** markwash has quit IRC01:06
*** boris-42 has quit IRC01:17
*** nati_ueno has joined #openstack-meeting-alt01:20
*** sarob has quit IRC01:23
*** sarob has joined #openstack-meeting-alt01:23
*** nosnos has joined #openstack-meeting-alt01:24
*** radix_ has joined #openstack-meeting-alt01:25
*** sarob has quit IRC01:29
*** jmaron has joined #openstack-meeting-alt01:34
*** jmaron has quit IRC01:39
*** brents has quit IRC01:53
*** dolphm has joined #openstack-meeting-alt01:55
*** nati_ueno has quit IRC01:59
*** brents has joined #openstack-meeting-alt02:05
*** alazarev has joined #openstack-meeting-alt02:17
*** dolphm has quit IRC02:17
*** yamahata has joined #openstack-meeting-alt02:21
*** radix__ has joined #openstack-meeting-alt02:21
*** radix_ has quit IRC02:23
*** dolphm has joined #openstack-meeting-alt02:24
*** kraman has joined #openstack-meeting-alt02:25
*** alazarev has quit IRC02:28
*** cody-somerville has joined #openstack-meeting-alt02:28
*** alazarev has joined #openstack-meeting-alt02:30
*** sarob has joined #openstack-meeting-alt02:34
*** flwang has quit IRC02:35
*** sarob has quit IRC02:39
*** radix_ has joined #openstack-meeting-alt02:40
*** flwang has joined #openstack-meeting-alt02:40
*** radix__ has quit IRC02:40
*** jmaron has joined #openstack-meeting-alt02:43
*** flwang has quit IRC02:43
*** cody-somerville has quit IRC02:44
*** brents has quit IRC02:46
*** jmaron has quit IRC02:47
*** aignatov has joined #openstack-meeting-alt03:05
*** kraman1 has joined #openstack-meeting-alt03:06
*** kraman has quit IRC03:09
*** nati_ueno has joined #openstack-meeting-alt03:09
*** nati_ueno has quit IRC03:14
*** eankutse has joined #openstack-meeting-alt03:22
*** alazarev has quit IRC03:22
*** markwash has joined #openstack-meeting-alt03:23
*** alazarev has joined #openstack-meeting-alt03:23
*** dolphm has quit IRC03:25
*** markwash has quit IRC03:28
*** alazarev has quit IRC03:29
*** coolsvap has joined #openstack-meeting-alt03:42
*** jmaron has joined #openstack-meeting-alt03:43
*** ben_duyujie has joined #openstack-meeting-alt03:48
*** jmaron has quit IRC03:48
*** boris-42 has joined #openstack-meeting-alt03:49
*** dolphm has joined #openstack-meeting-alt03:52
*** flwang has joined #openstack-meeting-alt03:52
*** boris-42 has quit IRC03:54
*** eankutse has joined #openstack-meeting-alt03:56
*** nati_ueno has joined #openstack-meeting-alt04:09
*** markwash has joined #openstack-meeting-alt04:16
*** markwash has quit IRC04:24
*** eankutse has quit IRC04:31
*** dolphm has quit IRC04:31
*** jmaron has joined #openstack-meeting-alt04:44
*** sergmelikyan has joined #openstack-meeting-alt04:47
*** aignatov has quit IRC04:48
*** jmaron has quit IRC04:49
*** IlyaE has joined #openstack-meeting-alt04:49
*** IlyaE has quit IRC04:59
*** IlyaE has joined #openstack-meeting-alt05:03
*** IlyaE has quit IRC05:08
*** IlyaE has joined #openstack-meeting-alt05:10
*** sarob has joined #openstack-meeting-alt05:11
*** yamahata has quit IRC05:12
*** kraman1 has quit IRC05:18
*** kraman has joined #openstack-meeting-alt05:24
*** kraman1 has joined #openstack-meeting-alt05:24
*** kraman has quit IRC05:28
*** alazarev has joined #openstack-meeting-alt05:32
*** nosnos_ has joined #openstack-meeting-alt05:36
*** nosnos has quit IRC05:36
*** DennyZhang has joined #openstack-meeting-alt05:40
*** nati_ueno has quit IRC05:41
*** boris-42 has joined #openstack-meeting-alt05:44
*** jmaron has joined #openstack-meeting-alt05:45
*** jmaron has quit IRC05:50
*** IlyaE has quit IRC05:52
*** SergeyLukjanov has joined #openstack-meeting-alt05:54
*** IlyaE has joined #openstack-meeting-alt05:55
*** sarob has quit IRC05:57
*** sarob has joined #openstack-meeting-alt05:57
*** kraman has joined #openstack-meeting-alt05:59
*** sergmelikyan has quit IRC06:00
*** flwang has quit IRC06:02
*** sarob has quit IRC06:02
*** kraman1 has quit IRC06:03
*** boris-42 has quit IRC06:03
*** flwang has joined #openstack-meeting-alt06:03
*** DennyZhang has quit IRC06:04
*** boris-42 has joined #openstack-meeting-alt06:06
*** alazarev has quit IRC06:07
*** alazarev has joined #openstack-meeting-alt06:08
*** IlyaE has quit IRC06:11
*** sergmelikyan has joined #openstack-meeting-alt06:12
*** IlyaE has joined #openstack-meeting-alt06:13
*** markwash has joined #openstack-meeting-alt06:20
*** alazarev has quit IRC06:26
*** sarob has joined #openstack-meeting-alt06:36
*** alazarev has joined #openstack-meeting-alt06:40
*** SergeyLukjanov has quit IRC06:41
*** jmaron has joined #openstack-meeting-alt06:46
*** yamahata has joined #openstack-meeting-alt06:46
*** jmaron has quit IRC06:46
*** flwang has quit IRC06:53
*** flwang has joined #openstack-meeting-alt06:56
*** nosnos_ has quit IRC06:56
*** nosnos has joined #openstack-meeting-alt06:56
*** IlyaE has quit IRC07:01
*** nati_ueno has joined #openstack-meeting-alt07:06
*** nati_ueno has quit IRC07:08
*** kraman has quit IRC07:16
*** sarob has quit IRC07:19
*** sarob has joined #openstack-meeting-alt07:19
*** akuznetsov has quit IRC07:23
*** sarob has quit IRC07:24
*** jcoufal has joined #openstack-meeting-alt07:27
*** boris-42 has quit IRC07:37
*** IlyaE has joined #openstack-meeting-alt07:39
*** yogesh has joined #openstack-meeting-alt07:43
*** flaper87 has quit IRC07:48
*** flaper87 has joined #openstack-meeting-alt07:48
*** flwang has quit IRC07:55
*** SergeyLukjanov has joined #openstack-meeting-alt08:02
*** alazarev has quit IRC08:12
*** IlyaE has quit IRC08:12
*** jtomasek has joined #openstack-meeting-alt08:14
*** kraman has joined #openstack-meeting-alt08:16
*** akuznetsov has joined #openstack-meeting-alt08:17
*** aignatov has joined #openstack-meeting-alt08:45
*** flwang has joined #openstack-meeting-alt08:46
*** kraman has quit IRC08:51
*** ilyashakhat has joined #openstack-meeting-alt08:52
*** nosnos has quit IRC08:59
*** nosnos has joined #openstack-meeting-alt08:59
*** nosnos has quit IRC09:03
*** lsmola_ has joined #openstack-meeting-alt09:10
*** ashaikh has joined #openstack-meeting-alt09:28
*** derekh has joined #openstack-meeting-alt09:45
*** kraman has joined #openstack-meeting-alt09:46
*** yogesh has quit IRC09:48
*** boris-42 has joined #openstack-meeting-alt09:49
*** kraman has quit IRC09:51
*** SergeyLukjanov has quit IRC09:51
*** SergeyLukjanov has joined #openstack-meeting-alt09:54
*** sergmelikyan has quit IRC10:02
*** ikhudoshyn has quit IRC10:05
*** ikhudoshyn has joined #openstack-meeting-alt10:07
*** flwang has quit IRC10:08
*** ashaikh has quit IRC10:11
*** aignatov has quit IRC10:14
*** akuznetsov has quit IRC10:22
*** rsblendido has joined #openstack-meeting-alt10:38
*** rossella_s has joined #openstack-meeting-alt10:38
*** noslzzp has joined #openstack-meeting-alt10:40
*** kraman has joined #openstack-meeting-alt10:47
*** kraman has quit IRC10:52
*** akuznetsov has joined #openstack-meeting-alt10:56
*** sergmelikyan has joined #openstack-meeting-alt10:57
*** SaD has joined #openstack-meeting-alt10:58
*** aignatov has joined #openstack-meeting-alt11:02
*** aignatov_ has joined #openstack-meeting-alt11:06
*** aignatov has quit IRC11:07
*** aignatov_ is now known as aignatov11:07
*** jcoufal has quit IRC11:14
*** sergmelikyan has quit IRC11:14
*** ilyashakhat has quit IRC11:17
*** ilyashakhat has joined #openstack-meeting-alt11:18
*** pcm_ has joined #openstack-meeting-alt11:20
*** pcm_ has quit IRC11:20
*** pcm_ has joined #openstack-meeting-alt11:20
*** SergeyLukjanov has quit IRC11:24
*** yamahata_ has joined #openstack-meeting-alt11:26
*** SergeyLukjanov has joined #openstack-meeting-alt11:27
*** akuznetsov has quit IRC11:37
*** ben_duyujie has quit IRC11:39
*** kraman has joined #openstack-meeting-alt11:48
*** akuznetsov has joined #openstack-meeting-alt11:52
*** jcoufal has joined #openstack-meeting-alt12:01
*** coolsvap has quit IRC12:09
*** yamahata_ has quit IRC12:19
*** kraman has quit IRC12:21
*** IlyaE has joined #openstack-meeting-alt12:30
*** noslzzp has quit IRC12:31
*** IlyaE has quit IRC12:34
*** IlyaE has joined #openstack-meeting-alt12:43
*** IlyaE has quit IRC12:47
*** SergeyLukjanov is now known as _SergeyLukjanov12:53
*** _SergeyLukjanov has quit IRC12:53
*** coolsvap has joined #openstack-meeting-alt12:55
*** yamahata_ has joined #openstack-meeting-alt13:05
*** pdmars has joined #openstack-meeting-alt13:14
*** kraman has joined #openstack-meeting-alt13:16
*** kraman has quit IRC13:21
*** sergmelikyan has joined #openstack-meeting-alt13:29
*** nati_ueno has joined #openstack-meeting-alt13:35
*** nati_ueno has quit IRC13:37
*** nati_ueno has joined #openstack-meeting-alt13:38
*** enikanorov has quit IRC13:38
*** enikanorov has joined #openstack-meeting-alt13:38
*** SergeyLukjanov has joined #openstack-meeting-alt13:44
*** yamahata_ has quit IRC13:47
*** IlyaE has joined #openstack-meeting-alt13:48
*** yogesh has joined #openstack-meeting-alt13:48
*** yamahata_ has joined #openstack-meeting-alt13:49
*** yogesh has quit IRC13:53
*** dprince has joined #openstack-meeting-alt13:54
*** noslzzp has joined #openstack-meeting-alt13:57
*** sballe has quit IRC13:57
*** kevinconway has joined #openstack-meeting-alt14:10
*** julim has joined #openstack-meeting-alt14:12
*** cody-somerville has joined #openstack-meeting-alt14:16
*** aignatov has quit IRC14:17
*** kraman has joined #openstack-meeting-alt14:17
*** eankutse has joined #openstack-meeting-alt14:19
*** eankutse has quit IRC14:20
*** eankutse has joined #openstack-meeting-alt14:20
*** kraman has quit IRC14:21
*** julim has quit IRC14:23
*** julim has joined #openstack-meeting-alt14:26
*** zhaoqin has joined #openstack-meeting-alt14:27
*** jmaron has joined #openstack-meeting-alt14:27
*** lblanchard has joined #openstack-meeting-alt14:30
*** SergeyLukjanov is now known as _SergeyLukjanov14:32
*** _SergeyLukjanov has quit IRC14:32
*** Barker has joined #openstack-meeting-alt14:33
*** jprovazn has joined #openstack-meeting-alt14:38
*** amytron has joined #openstack-meeting-alt14:38
*** kraman has joined #openstack-meeting-alt14:53
*** kraman has quit IRC14:57
*** kraman has joined #openstack-meeting-alt14:57
*** kraman has quit IRC15:02
*** SergeyLukjanov has joined #openstack-meeting-alt15:02
*** SergeyLukjanov has quit IRC15:04
*** devkulkarni has quit IRC15:06
*** SergeyLukjanov has joined #openstack-meeting-alt15:10
*** aignatov has joined #openstack-meeting-alt15:16
*** eankutse has quit IRC15:18
*** eankutse has joined #openstack-meeting-alt15:19
*** alazarev has joined #openstack-meeting-alt15:22
*** tanisdl has joined #openstack-meeting-alt15:25
*** eankutse has quit IRC15:27
*** jmaron has quit IRC15:29
*** kraman has joined #openstack-meeting-alt15:36
*** devkulkarni has joined #openstack-meeting-alt15:38
*** markwash has quit IRC15:40
*** betsy has quit IRC15:41
*** d0ugal has quit IRC15:51
*** d0ugal has joined #openstack-meeting-alt15:52
*** d0ugal has joined #openstack-meeting-alt15:52
*** kraman has quit IRC15:53
*** kraman has joined #openstack-meeting-alt15:58
*** stanlagun has joined #openstack-meeting-alt16:00
*** kgriffs_afk is now known as kgriffs16:00
*** kraman has quit IRC16:02
*** tsufiev has joined #openstack-meeting-alt16:04
*** julim has quit IRC16:04
*** julim has joined #openstack-meeting-alt16:05
*** jergerber has joined #openstack-meeting-alt16:05
*** alcabrera has joined #openstack-meeting-alt16:06
*** ametts has joined #openstack-meeting-alt16:06
kgriffswho's here for the marconi mtg?16:06
alcabrerao/16:06
*** IgorYozhikov has joined #openstack-meeting-alt16:07
kgriffsflaper87: you around?16:08
flaper87o/16:08
flaper87Yes sir16:08
kgriffsexcellente16:08
kgriffsWell, we have 3 of us16:08
alcabrerayup16:08
kgriffswhere's malini?16:09
* ametts is lurking16:09
kgriffsametts: welcome!16:09
ametts(and multitasking)16:09
*** aignatov has quit IRC16:09
alcabreramalini is at the doctor, last I heard. She'll be around in about 30m.16:09
flaper87ametts: d00000000d16:09
flaper87alcabrera: welcoime :D16:09
alcabreraflaper87: :D16:09
kgriffsalcabrera: kk16:09
kgriffsLet's get this party started.16:09
alcabrera /begin marconi-fiesta16:09
kgriffs#startmeeting marconi16:09
openstackMeeting started Mon Nov 18 16:09:50 2013 UTC and is due to finish in 60 minutes.  The chair is kgriffs. Information about MeetBot at http://wiki.debian.org/MeetBot.16:09
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:09
*** openstack changes topic to " (Meeting topic: marconi)"16:09
openstackThe meeting name has been set to 'marconi'16:09
kgriffs#link https://wiki.openstack.org/wiki/Meetings/Marconi#Agenda16:09
kgriffs#topic Hong Kong summit retrospective16:10
*** openstack changes topic to "Hong Kong summit retrospective (Meeting topic: marconi)"16:10
kgriffsametts, flaper87: how did you think things went?16:10
alcabreraI'm going to drop a few relevant links here.16:10
flaper87I'm very happy with how things went16:10
alcabrera#link https://etherpad.openstack.org/p/IcehouseMarconiFeaturesAPIChanges16:10
alcabrera#link https://etherpad.openstack.org/p/IcehouseMarconiNotificationService16:11
alcabrera#link https://etherpad.openstack.org/p/IcehouseMarconiAMQPSupport16:11
flaper87People attended to our sessions16:11
alcabrera#link https://etherpad.openstack.org/p/IcehouseMarconiInOut16:11
flaper87we've got feedback from the community overall16:11
amettsDecent attendance:  30-50 people at the design sessions, and I counted about 65 at the afternoon session.16:11
flaper87After our talk people gave feedback as well16:11
*** brents has joined #openstack-meeting-alt16:11
amettsWe probably would have had more folks there, except it was Friday afternoon and people were starting to head out already.16:12
flaper87I'm also happy with how kgriffs session went16:12
*** eankutse has joined #openstack-meeting-alt16:12
*** eankutse has quit IRC16:12
kgriffsI also thought it went well16:12
kgriffsIn spite of the jet lag. :p16:12
*** eankutse has joined #openstack-meeting-alt16:12
alcabreraWas there any particular feature16:12
alcabrerathat people were asking for?16:13
*** SergeyLukjanov has quit IRC16:13
kgriffsLots of people interested in notifications16:13
kgriffsone person was asking about security16:13
*** jmontemayor has joined #openstack-meeting-alt16:13
kgriffsas in, how do I ensure that one client can't get messages meant for a different one16:13
kgriffsAnother theme was "queue provisioning as a service"16:14
alcabrerahmmm16:14
*** zane has joined #openstack-meeting-alt16:14
flaper87yeah16:14
kgriffsI think at some point it may make sense to spin up a project to provision single-tenant AMQP instances or somthing, ala Trove16:14
alcabreraso notifications is definitely a hot-topic - cool.16:14
flaper87I'm not 100% sure about it but I haven't put many thoughts on that16:14
kgriffsright16:15
kgriffssomething to keep in the back of our minds - not a high priority right now16:15
kgriffsHP suggested several things16:15
kgriffslike, binary payloads combined with storing the content type in the metadata16:16
kgriffs(ala Swift)16:16
*** jmaron has joined #openstack-meeting-alt16:16
kgriffsSounds like they don't have bandwidth to contribute code at the moment, but maybe that will change if they hire more people16:16
kgriffsflaper87, ametts: other things you would call out?16:16
alcabreraI'm looking forward to that! +1 for contributor bandwidth16:16
flaper87that's cool. I found Hung suggestions very valuable, unfortunatelly many of them didn't fit into current MArconi's goals16:17
flaper87but we should definitely keep an eye on those16:17
kgriffs+116:17
kgriffshe had some good "lessons learned" to share based on customer feedback16:17
kgriffssounded like most customers are internal ones, fwiw16:17
amettsSounds like there was good support for an early 1.1 version in the fourth session.16:18
kgriffs(internal == HP)16:18
kgriffsyep16:18
kgriffsI was happy that Everett attended16:18
kgriffsflaper87: He maintains the Rackspace Java SDK16:18
kgriffs- Jclouds guy16:19
kgriffshttps://github.com/everett-toews16:19
kgriffsflaper87: you should talk about client design with him some time16:20
flaper87ow, didn't know that! Awesome!16:20
kgriffswhich also reminds me, a couple people asked about JMS support16:20
flaper87I'll definitely do that16:20
kgriffsflaper87: maybe you can ask him about JMS as well16:20
flaper87+116:20
kgriffsrock on16:20
flaper87I've already some ideas re JMS / AMQP / STOMP / MQTT16:20
flaper87but we need to dig more into that16:21
kgriffskk16:21
flaper87and sounds like Jth summit thing16:21
flaper87anyway, I'll ping him offline16:21
kgriffsotherwise, I still need to finish digesting my notes from the summit and updating the wiki/blueprints accordingly. TBH, I've been busy just catching up with email and preparing for the Solum mini-design-summit happening in SFO tomorrow and wed.16:22
kgriffs#action flaper87 to get in touch with Everett Toews and talk shop16:22
*** katyafervent has joined #openstack-meeting-alt16:22
kgriffsspeaking of which, we should start thinking about how Marconi could tie into a PaaS16:23
*** dprince has quit IRC16:23
*** boris-42 has quit IRC16:23
flaper87+116:23
alcabrera+116:23
kgriffsok, anything else on the topic of the summit?16:23
*** alazarev has quit IRC16:23
flaper87I have to take a deeper look at Solum, I whish I had more bandwidth to contirbute to it16:23
kgriffsflaper87: bandwidth is hard to come by. I hear ya!16:24
kgriffsI need to upgrade to 10g16:24
flaper87lol16:24
alcabrera:P16:24
kgriffsfwiw I am planning to starting contributing on a regular basis to Oslo16:24
kgriffsI also may be doing some webob work16:25
kgriffswe'll see16:25
kgriffsso much to do, so little time. :p16:25
kgriffsaaanyway16:25
kgriffsI would like to see more Marconi folks contributing to other OS projects16:25
kgriffshelps us stay in sync with the community, and we may end up getting people to reciprocate and contribute to Marconi16:26
kgriffsI know flaper87 already does that.16:26
kgriffs(kudos)16:26
flaper87:D16:26
alcabreraI see the value of it. Just got to make the time. :)16:26
kgriffsok, let's move on16:27
kgriffs#topic review actions from last mtg16:27
*** openstack changes topic to "review actions from last mtg (Meeting topic: marconi)"16:27
kgriffshttp://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-28-16.04.html16:27
kgriffs#link http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-10-28-16.04.html16:27
kgriffsI'll go first16:27
kgriffsT-shirts: mission accomplished!16:27
flaper87kgriffs: +116:28
alcabreraw00t16:28
kgriffswe handed out all but about 4 of the 75 I brought with me16:28
* ametts is glad kgriffs didn't get arrested by Hong Kong Customs agents16:28
kgriffslol16:28
flaper87lol16:28
kgriffsthey were like, "dude, do you have any drugs in there?".16:28
kgriffs"no"16:28
kgriffs"carry on"16:28
ametts(I'm not sure how to encode bail on an expense report)16:28
kgriffsLOL16:29
alcabreralol16:29
kgriffsametts: you have the contact info for the screen printing shop if you'd like to order more16:29
amettsYes I do.  Thanks.16:29
kgriffsThey are great for meetups and recruiting fairs16:30
*** alazarev has joined #openstack-meeting-alt16:30
kgriffsflaper87: I will forward the graphics on to you16:30
*** alazarev has quit IRC16:30
kgriffsmoving on16:30
flaper87kgriffs: awesome, thanks!16:30
kgriffs" flaper87 to firm up cross-transport-api-spec"16:30
flaper87kgriffs: done, I've been also chatting with Cindy about that16:31
flaper87we've been writing mores stuff there16:31
flaper87and We'll start coding on it ASAP16:31
kgriffsok, cool16:31
*** rnirmal has joined #openstack-meeting-alt16:31
*** alazarev has joined #openstack-meeting-alt16:31
*** alazarev has quit IRC16:31
flaper87once the whole idea is well defined, we'll also move the info to the wiki16:32
flaper87Architecture related info16:32
kgriffsflaper87: you may also want to chat with the Nova guys about this16:32
kgriffssince they will be using JSON schema as well, sounds like16:32
flaper87yeah16:32
alcabrerajsonschema - picking up steam across the board. gtk.16:32
flaper87we are also using it in Glance, FWIW. But I'll definitely keep an eye on Nova work16:32
kgriffsI envision a sort of RESTful WSME module growing out of this that multiple projects can share.16:32
*** ben_duyujie has joined #openstack-meeting-alt16:33
kgriffsalcabrera: oh yeah, you should have been at the Pecan/WSME nova session16:33
alcabreraoh?16:33
*** betsy has joined #openstack-meeting-alt16:33
kgriffslet me summarize16:33
kgriffs"you guys should be using Pecan/WSME for your next API"16:34
kgriffs"OK. Who else is using it?"16:34
kgriffs"Just ceilometer, but we have commitments from a bunch of other projects"16:34
kgriffs"Blah blah blah..."16:34
kgriffs"So how do extensions work with WSME"16:34
kgriffs"They don't really. WSME definitions are static. But that is OK because you can just define a generic string table and use that. And OS projects should stop supporting arbitrary extensions anyway."16:35
*** ben_duyujie has quit IRC16:35
*** yidclare has joined #openstack-meeting-alt16:35
kgriffs"That's not going to happen any time soon"16:35
kgriffs"But we need to enforce portability of OS apps and scripts"16:36
kgriffs[Back-and-forth, no consensus reached on that point]16:36
alcabreradoesn't sound like that went well.16:36
kgriffs"So, going back to WSME and extensions, did I hear right that the definitions are static."16:37
kgriffs"That's correct."16:37
kgriffs"OK, then that isn't going to work."16:37
kgriffs[blah blah blah...]16:37
kgriffs"OK, let's go with Pecan and JSON schema"16:37
kgriffsI forgot to mention this little gem earlier...16:38
alcabreraheh. :)16:38
kgriffs"Marconi gets a pass on using Falcon since they are a data plane api"16:38
alcabreraoh yeah!16:38
alcabreraI heard that one from flaper8716:38
alcabreravery cool16:38
alcabreraLemme just note that down...16:39
alcabrera#info Marconi gets a pass on using Falcon since they are a data plane api16:39
kgriffsbut, I still promised to do a POC pecan driver and try to help improve Pecan performance, which is starting to look like improving webob16:39
alcabreraisn't a spin off of webob used in Swift?16:39
alcabreraswiftob?16:39
kgriffsp.s. - flaper87 and I only spoke a couple sentences the entire time16:39
kgriffsswob16:40
flaper87:D16:40
kgriffsnot sure how related it is16:40
kgriffswe may be able to "steal" some code or at least ideas from there16:40
kgriffsok, so other action item16:41
kgriffsalcabrera to research ways we can use heat to deploy marconi itself, as well as provision queues, whatever16:41
alcabrerastarted16:41
alcabreraI did some reading on Heat this morning to familiarize myself with what it is, what it can be used for.16:41
alcabreraThe whole orchestration idea.16:41
notmynamealcabrera: swob = a swift replacement to webob that doesn't break on every minro version bump16:41
kgriffsalcabrera: have you already reached out to keith bray?16:41
alcabrerakgriffs: I have not.16:41
kgriffsnotmyname: does it have the same interface16:42
kgriffsalcabrera: ok, I will introduce you16:42
alcabrerathanks!16:42
*** sacharya has joined #openstack-meeting-alt16:42
notmynamekgriffs: it's intended to be a drop-in replacement (ie that's what it first did). I assume it still is, but we don't test that path. https://github.com/openstack/swift/blob/master/swift/common/swob.py#L1716:43
kgriffsnotmyname: ah, interesting. I wonder how much in Pecan would break if you just swapped it in place for webob16:44
notmynametransit time to the office. if there are other questions, just ping me in one of those dozen or so of channels I'm in16:45
kgriffsnotmyname: will do, thanks!16:45
alcabreraI'll keep researching heat-side and I'll speak with Keith Bray for next time.16:46
kgriffssounds like a plan16:46
kgriffs#action alcabrera to keep researching heat, and engage with the team16:46
kgriffs#action kgriffs to play with swob16:47
kgriffs#topic Sharding Updates (cpp-cabrera)16:47
*** openstack changes topic to "Sharding Updates (cpp-cabrera) (Meeting topic: marconi)"16:47
alcabreraalright16:47
alcabreralots of great news here16:48
alcabreraso - we have sharding being tested extensively over at Rackspace.16:48
alcabreraHere's a report from a test run last week using 3 mongodb shards:16:48
alcabrera#link http://198.61.239.147:8000/log/20131112-1806/report.html16:48
alcabreraWhile the report tells us little about the scaling behavior, it *is* scaling, as we were maxing out a single storage instance at about 2000 rps previously. :)16:49
alcabreraSo - sharding works!16:49
kgriffsso we peak at just under 4000 shards16:49
alcabrerawell, not 4000 shards... 4000 rps. :)16:50
alcabrerabut yes.16:50
kgriffsone other data point - I noticed that the standard deviation (so to speak) is a lot smaller under heavy load for shards vs. no shards16:50
kgriffsso, it gives more consistent performance to users16:50
kgriffswhich is always a good thing16:50
kgriffs(just ask anyone using AWS)16:50
alcabrerayup16:50
flaper87hahaha16:50
alcabrerawe're better able to hide GC latency this way. :D16:51
kgriffsI believe the reason is that having more shards adds more "jitter"16:51
kgriffsas in, more chances for requests to get through in a timely manner without stalling16:51
kgriffsyou know, chaos theory. ;)16:52
alcabreraThis'll be true, as long as long as few heavy hitters end up colocated - the "busy queues are colocated" problem16:52
alcabreracoined as of this moment. :P16:52
*** alazarev has joined #openstack-meeting-alt16:52
alcabreraSo other sharding news -16:53
alcabreraThe patches!16:53
alcabreraWe have patches awaiting review, and I've been updating as I go.16:53
alcabreraThanks for the review, flaper87!16:53
flaper87alcabrera: +116:53
alcabreraThe entry patch to sharding is:16:53
alcabrera#link https://review.openstack.org/#/c/54605/16:54
flaper87BTW, we've been lacking of reviews lately. We should get back to do a number of reviews per day16:54
alcabreraThe rest follows from there.16:54
alcabreraflaper87: +116:54
alcabreraI think the summit threw us all off our routine.16:54
alcabrera:D16:54
alcabreraHopefully, we can get sharding merged soon. I'm requesting some help with reviews on that.16:55
alcabreraso that's that for sharding. Any thoughts or questions on this?16:55
kgriffs+1 wrt reviews16:56
kgriffsflaper87, alcabrera: I would love it if you guys could also peak at solum once in a while and do some +1/-1's there16:56
kgriffsI want to make sure it is aligned with other projects16:56
kgriffs#link https://review.openstack.org/#/q/status:open+project:stackforge/solum,n,z16:56
flaper87sure thing!16:56
alcabrerawow, solum is busy.16:57
alcabreraA page of reviews pending!16:57
kgriffsI will be doing lots of reviews for Marconi this week16:57
kgriffsalcabrera: looks like you have -1 here to address16:57
kgriffshttps://review.openstack.org/#/c/54605/16:57
kgriffsflaper87: I was kind of waiting for you to get to a point where you are ready to +2 alcabrera's patches before I did my final review16:58
alcabrerakgriffs: yup. I'm trying to DRY up the sharding implementation. It's proving to be a little tricky.16:58
alcabreraI've addressed all feedback on that one save for the DRYness.16:58
kgriffsI went over the patches quite a bit, esp. when I filled in a week or so ago for alcabrera while he was out of the office16:58
kgriffsok16:59
kgriffsmaybe we leave the DRYness for a follow-up patch?16:59
flaper87kgriffs: sounds good! I'll take another look at that patch16:59
alcabrerait wouldn't hurt to save it for later, IMO.16:59
kgriffsflaper87: thanks. I just feel like I am too close to the code and need to let it "cool off" before I look again16:59
kgriffsflaper87: thoughts on saving DRY refactoring?17:00
kgriffs(for the near future)17:00
flaper87If DRY changes are not big, I'd prefer seeing them in this patch, otherwise we can let them land in a separate patch17:00
* kgriffs has his eye on the time17:01
alcabreraoops - I actually didn't upload the patch where I addressed the feedbaclk. Let me do that now... >.>17:01
kgriffsflaper87: agreed17:01
alcabrera*feedback17:01
kgriffsalcabrera: how much churn would the DRY work create?17:01
alcabrerakgriffs: It would change the implementation for every forwarded method.17:01
*** SergeyLukjanov has joined #openstack-meeting-alt17:01
*** jmontemayor has quit IRC17:01
kgriffsah, *that*17:01
*** Barker has quit IRC17:01
kgriffsI remember thinking it could be made more DRY17:02
kgriffsI may have even commented on it at one point17:02
kgriffsbut that's beside the point17:02
kgriffshmmm17:02
alcabreraThe pattern currently is: 1) lookup a target, 2) if it exists, call a method on a particular controller, 3) if it doesn't return a value or raise an exception.17:02
alcabrera1) ... 2a) ... 2b)17:02
* flaper87 just read alcabrera answer to his comment about that17:02
*** akuznetsov has quit IRC17:04
*** aignatov has joined #openstack-meeting-alt17:04
kgriffsok, we are out of time17:05
alcabrerashould we move on to the next topic and address sharding further in #openstack-marconi?17:05
alcabrerayep, that would do it. :P17:05
flaper87hahaha17:05
kgriffs#action alcabrera to work on sharding feedback and get it approved17:05
kgriffs#endmeeting17:05
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:05
openstackMeeting ended Mon Nov 18 17:05:53 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-11-18-16.09.html17:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-11-18-16.09.txt17:05
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-11-18-16.09.log.html17:05
kgriffsthanks guys!17:06
kgriffsalcabrera: Can you add the minutes to the wiki?17:06
kgriffsI will update the agenda17:06
alcabrerakgriffs: will do17:06
kgriffsthanks!17:06
*** enikanorov_ has joined #openstack-meeting-alt17:06
*** amitgandhi has joined #openstack-meeting-alt17:07
*** jmontemayor has joined #openstack-meeting-alt17:08
*** alcabrera has left #openstack-meeting-alt17:08
*** ametts has quit IRC17:09
*** amitgandhi has left #openstack-meeting-alt17:09
*** cpallares has joined #openstack-meeting-alt17:12
*** cpallares has left #openstack-meeting-alt17:13
*** Barker has joined #openstack-meeting-alt17:14
*** julim has quit IRC17:15
*** ashaikh has joined #openstack-meeting-alt17:18
*** julim has joined #openstack-meeting-alt17:19
*** jtomasek has quit IRC17:21
*** enikanorov_ has quit IRC17:25
*** enikanorov_ has joined #openstack-meeting-alt17:25
*** jmaron has left #openstack-meeting-alt17:28
*** jcoufal has quit IRC17:31
*** dprince has joined #openstack-meeting-alt17:33
*** flaper87 is now known as flaper87|afk17:37
*** twoputt_ has joined #openstack-meeting-alt17:43
*** twoputt has joined #openstack-meeting-alt17:43
*** yjiang5 has joined #openstack-meeting-alt17:44
*** aignatov has quit IRC17:48
*** markwash has joined #openstack-meeting-alt17:51
*** aignatov has joined #openstack-meeting-alt17:57
*** harlowja has joined #openstack-meeting-alt17:59
*** derekh has quit IRC18:00
*** AlanClark has joined #openstack-meeting-alt18:07
*** sarob has joined #openstack-meeting-alt18:07
*** yogesh has joined #openstack-meeting-alt18:20
*** amcrn has joined #openstack-meeting-alt18:24
*** rossella_s has quit IRC18:25
*** rsblendido has quit IRC18:25
*** coolsvap has quit IRC18:28
*** akuznetsov has joined #openstack-meeting-alt18:30
*** ashaikh has quit IRC18:37
*** eankutse has quit IRC18:38
*** ashaikh has joined #openstack-meeting-alt18:39
*** lsmola_ has quit IRC18:42
*** jprovazn has quit IRC18:43
*** rook has joined #openstack-meeting-alt18:49
*** Brian___ has joined #openstack-meeting-alt18:50
*** baoli has joined #openstack-meeting-alt18:55
*** irenab has joined #openstack-meeting-alt18:57
*** rnirmal has quit IRC18:58
*** AlanClark has quit IRC18:59
*** aclark_ has joined #openstack-meeting-alt18:59
*** itzikb has joined #openstack-meeting-alt19:00
*** sadasu has joined #openstack-meeting-alt19:00
*** yidclare has quit IRC19:00
*** vipul is now known as vipul-away19:01
*** sarob has quit IRC19:01
*** sarob has joined #openstack-meeting-alt19:01
baoliHello everyone19:03
yjiang5hi19:03
sadasuHello! Welcome to our 1st lci passthrough meeting19:03
sadasupci*19:03
itzikbhi19:04
irenabhi19:04
*** ijw has joined #openstack-meeting-alt19:04
yjiang5sadasu, baoli ,who will chair this meeting?19:05
sadasuI put baoli as the chair19:06
*** sarob has quit IRC19:06
yjiang5sadasu: cool19:06
baoli@yjiang5, I was thinking to start our first meeting with discussion on pci whitelist and pci alias19:06
baoliI had a discussion with yongli during the summit19:06
*** IlyaE has quit IRC19:07
yjiang5baoli: sure. I know Yongli is working on this and finish part of the coding.19:07
irenab@baoli: any specific networking requirements with regards to this?19:07
irenabor we just go with white list approach first?19:08
baoli@irenab yes. that's how we group the PCI devices19:08
ijwSo we'd whitelist into groups and then attach data to each group, I presume?19:08
yjiang5baoli: what do you mean exactly of the white list? I think white list is mostly to select the devices that can be assigned to guest, right?19:08
*** aclark_ has quit IRC19:08
baoliOk, first Let me recap what we have discussed f19:08
*** eankutse has joined #openstack-meeting-alt19:09
baoliA white list is define by each and every compute node19:09
yjiang5baoli: great.19:09
baoliAs of now, you can define a white list as something like pci_passthrough_whitelist='[{"vendor_id":"1137","product_id":"0071"}]19:10
*** vipul-away is now known as vipul19:10
irenabalias defined by controller and has a meeting of provider network in case of NIC device type for PCI passthrough. Am I right?19:10
irenabI mean meaning not meeting, sorry19:11
baoli@irenab, sorry, let me finish the recap. I will indicate the end of the recap19:11
baoliSo basically, it's a list of (<vendor_id, product_id>) now. But it's not sufficient to group the devices based on their common charactoristics (either by networking requirements, or others)19:13
*** sgordon has joined #openstack-meeting-alt19:13
baoliSo Yongli thinks to enhance it as a list of tuples <filter, group_name>, with <filter> as <vendor_id, product_id, physical_function_id>, and <group_name> as a string19:15
*** akuznetsov has quit IRC19:15
baoliOn top of that, on the controller node, one can define PCI alias for grouping19:16
ijwPCI alias being what, just a name?19:17
*** eankutse has quit IRC19:17
baoli@ijw, essentially, yes. But it represents a group of PCI devices that share the same charactoristics as designated by the cloud admin19:18
yjiang5ijw: IIUC, alias is an alias to PCI requests.19:18
ijwThat's fine for some use cases but not ideal for all of them, I think.  But did you want to finish the recap before I get into the details?19:18
*** derekh has joined #openstack-meeting-alt19:19
baoli@ijw, sure. Essentially, the compute node reports all the PCI devices by the means of PCI whitelist. PCI requests can be made by the means of PCI alias. end of recap19:20
ijwOK, so the compute host is reporting a list of devices (or possibly a count, I know we've discussed both before) and the control node contains the additional data.  That is generally the wrong way around, though.19:21
baoliCan you elaborate why it's wrong?19:21
baoliit's basically how it's working now.19:22
ijwFor network cards needing additional data - be that the switch port they're attached to, if you're dealing with them individually, or the provider network they're attached to if you're dealing with them in groups - it's usually the compute node that needs that information at port update time.19:22
yjiang5ijw: here the compute node means nova, or neurtron agent?19:22
ijwAlso, for NIC ports plugged into a switch where you expect to reprogram the switch when you put the port into a VM, the allocation pool can't contain the data.19:23
ijwnova, in practice.  Nova would call neutron's update-port, neutron would program the switch port accordingly and, presumably, inform nova of the encap to put on the port.19:23
ijw(if one is required)19:23
ijwAlso, I'll raise the point I was making several months ago, that in fact you don't really need to report every device back to the control node, only the number of devices of a particular type, which would be the number of devices per alias.  The scheduler never needs to know what the PCI address is, it just needs to know if sufficient resource is free.19:25
*** jtomasek has joined #openstack-meeting-alt19:25
yjiang5ijw:  For your scheduler information, that's been done as is now. The so called pci_stats. +1 for your discussion and I will give my input after you finished it.19:25
ijwDone now.19:25
*** garyduan has quit IRC19:26
*** garyduan has joined #openstack-meeting-alt19:26
yjiang5I think white list is the mechanism to select the device to be assigned. I'm not sure if it's best to specify the pci white list on it. I'd elaborate my idea.19:26
ijwyjiang5: I'm fine with the grouping concept of the whitelist, that sounds eminently sensible, I just take issue with where auxiliary data should be attached.19:27
*** demorris has joined #openstack-meeting-alt19:28
ijwyjiang5: I don't think you can attach it to the alias because it can differ per device within the alias.19:28
yjiang5IMO, PCi device in fact two type of property, one is generic property like vendor_id, device_id, BDF. , another is usage specific property like switch port, the group name, anything that is defined.19:28
*** sarob has joined #openstack-meeting-alt19:28
ijwYea19:28
baoliijw: additional networking info is defined by means of port profile, which is entered in the nova boot or nova interface-attach commands19:29
yjiang5currently the generic property is saved in the table as a separated column, while the usage specific one is defined in the extra_info.19:29
baoliijw, I agree with your comments about scheduling19:29
ijwbaoli: how can the tenant calling 'nova boot' know anything about the physical connection of the network interface?19:30
irenab@ijw: tetant should not know19:30
yjiang5I'd keep the white list to be based on generic property, like BDF, vendor_id etc (we need add the BDF to white list). Then we need another mechanism to specify the extra attributes to the devices, and that extra attributes will be saved in DB as extra_info.19:30
ijwyjiang5: that extra information can remain in memory on the compute host.19:31
ijwProviding it's not required for scheduling, at least.19:31
ijwIt doesn't need to be persistently stored.19:31
ijw(and that's true *even* if it's needed for scheduling, but talk to boris42 about that bit, he's messing about with the scheduler)19:31
yjiang5ijw: No, I think it is required in DB, for example, the group name can be one of them, and should be used by scheduler to select device.19:32
baoliijw: good question. But someone needs to know when trying to instantiate a VM that requires pci-passthrough and special networking requirement19:32
yjiang5irenab: a curios question, how will neutron get such information, like network switch ?19:32
baoliOne way to do that is to associate that with the network a VM will be attaching to.19:33
ijwyjiang5: what at present needs to go into the DB is what's required for scheduling and nothing more - which, at present, is the alias.19:33
ijwbaoli: you need to specify when you want a PCI device, but in my opinion you should simply specify 'this should be a PCI device' to the —nic command rather than anything else, and the net-id should be respected as normal.19:34
yjiang5ijw: no, alias is just an alias to pci request, like group_name is xxx, vendor_id is xxx etc. And the scheduler will match the pci request with pci_stats in DB.19:34
ijwyjiang5: the switch port was intended to be additional information that was stored in the compute node's config file.19:34
ijwyjiang5: I could, quite reasonably, have two different NIC types with different vendor_id and want to use them the same.19:35
irenabijw: by switch port you mean the physical switch attached to Server?19:35
ijwirenab: yup19:35
baoliijw, did you get a chance to go through an email thread we had before the summit?19:35
yjiang5ijw: alias can be ORed , so it's ok. It's just a rule.19:35
ijwBut why would you specify alias on the control node rather than the compute node?19:36
*** brents has quit IRC19:36
*** ashaikh has quit IRC19:37
baoliActually, with the enhanced whitelist defintion, no alias needs to be specified on the controller node. In a matter of fact, the <group_name> is the PCI alias name19:37
yjiang5ijw: to seperate the request with the property.19:37
*** yidclare has joined #openstack-meeting-alt19:37
irenaband group name is a provider network name?19:38
irenabor switch port?19:38
ijwSeems to me that if you're using a provider network name, or a switch port, that should be specifiable per-device or per-group on the compute node.  So lines on the compute node should look something like:19:38
yjiang5baoli: I think that's in fact a quite simplified solution, not sure if it will meet all requirement. If yes, that's ok for me.19:38
sadasuire nab: IIUC: a switch port19:38
ijwpci_passthrough_whitelist='{ "my_group_name": {"vendor_id":"1137","product_id":"0071", extra_data: { "provider_network": "fred"}]19:39
baoli@irenab, if need be, yes you can use a pci alias to represent a provider network19:39
ijwThen I could specify multiple lines with my_group_name, and the selection criteria could be very general or completely specific to slot and function.19:40
irenabjust need to make sure scheduler take in to account the network connectivity19:40
baoliijw, I don't think that you want to put network specific info in the whitelist19:40
*** jcooley_ has joined #openstack-meeting-alt19:41
ijwI want to put it somewhere where (a) it resides on the compute node, since the compute node should carry all its own information and (b) you can bind it to a specific port on a network card, specifically19:41
baoliThe association of networking info with VM is made during boot or interface operations19:41
ijwNo, it really isn't19:41
ijwI associate it with a network at that point, yes, absolutely.  But if I have to reprogram devices in the network to make that association I need to have the information around telling me what it is I have to reprogram19:42
*** ashaikh has joined #openstack-meeting-alt19:43
baoliThat info will be maintained in the neutron port database19:43
sadasu@baoli: the network information in the whitelist serves a diff purpose from the networking info given when we bring up a VM19:43
ijwWhere will it get that from?19:43
baoliIt can get it from the port-create api, for one example19:44
irenab@baoli: can you please make a step abck and explain how the scheduling part is solved?19:45
baoliThe point is, when someone wants to create a port with special pci requirement, it should be able to indicate that and the special requirement he intends to assigen to that port19:45
ijwThat's an interesting idea, though not specifically what I was getting at.19:46
baoli@irenab, can we discuss scheduling in more detail in the next meeting?19:46
irenab@baoli: sure19:46
baoliWe should come to consensus about what exactly PCI whitelist and PCI alias are19:47
*** eankutse has joined #openstack-meeting-alt19:47
ijwSo we agree that there's a filter on which PCI devices are included for passthrough, and we're grouping PCI devices into groups that we're calling 'aliases', I think19:48
sadasufrom the current discussion it appears that we need only one and not both.19:48
*** IlyaE has joined #openstack-meeting-alt19:48
ijwWe seem to disagree on how the whitelist and aliases actually interact with each other.19:48
*** aignatov has quit IRC19:48
yjiang5I'm not fully agree with the alias.19:48
irenabAs far as I understand alias is used for VM request19:49
yjiang5at least in current implementation, alias is just an alias to pci request, which is rules of pci property.19:49
ijwMeaning it just turns a friendly name into a vendor/product set?19:49
irenabwhite list is used to group devices available for VMs on certain compute node, right?19:49
*** sarob has quit IRC19:50
ijwI think at the moment whitelist just determines what's made available, rather than grouping them, doesn't it?19:50
*** sarob has joined #openstack-meeting-alt19:50
baoli@yjang5, PCI alias is part of the pci request, that indicate the requested PCI device should be alloacated from PCI devices that are defined by the alias. Is this right?19:50
*** kraman has joined #openstack-meeting-alt19:51
yjiang5ijw: yes, at least now, whitelist is just determine what's available, not groupiing. I'm not against to use it as grouping, but that's in fact an extension to white list. After all, white list is white list, right?19:51
yjiang5baoli: alias is not part of request, it will be translated to pci request.19:51
yjiang5you can think alias as 'name' for pci request, which can be long and boring :)19:51
ijwI would argue that you sometimes want to alias different device types together (for instance perhaps I don't care who my NIC vendor is just so long as I get a nic)19:52
*** SergeyLukjanov has quit IRC19:52
*** sarob_ has joined #openstack-meeting-alt19:52
*** sarob has quit IRC19:52
yjiang5ijw: that's how you define the pci request. You want a pci request to cover the devices you want to group.19:52
*** IlyaE has quit IRC19:53
ijwOK19:53
ijwI was thinking in terms of passing the friendly alias name between control and compute nodes, really, but I guess it works either way19:53
*** twoputt_ has quit IRC19:53
*** twoputt has quit IRC19:53
yjiang5baoli: I'm not against use whitelist for groupname, but just want to make sure every one is on the same page.19:54
yjiang5baoli: one ways step back, have you discussed with yongli of the exact format of the extended white list that covers the group?19:55
*** IlyaE has joined #openstack-meeting-alt19:56
baoliyjiang5, use of whitelist for groupname is actually a side effect of putting a "name" as part of the whitelist. Originally, I thought we could still have both whitelist and alias: with whitelist indicating all the PCI devices available on the compute node, and the alias to group pci devices19:56
baoliyjang5, I had a long discussion with Yongli during the summit on this.19:57
irenab@baoli: so how the VM boot request will look like?19:57
baoliUnfortunately, it's 2am his time now, and he can't attend to this discusstion19:57
yjiang5irenab: your question is important , the vm boot request format :)19:58
baoli@irenab, it should be similar to what we have discussed in the email thread19:58
yjiang5baoli: IMHO, group just mean device with similar property, right? Why you emphasis it ?19:59
irenab@baoli: so there is still a flavor containing extra_spec with PCI device request, right?19:59
*** aclark_ has joined #openstack-meeting-alt19:59
yjiang5baoli: Possibly I missed important information.19:59
*** rook has quit IRC20:00
sadasuLets keep the vm boot request format as the topic for next week's discussion.20:00
baoliso folks, time is up for this meeting. Let's continue with email. I am also planning to write up something based on our discussion so far, for everyoen to comment. We really need to come to consensus on what white list and alias are20:00
yjiang5baoli: sadasu , are you in US timezone?20:01
irenab@baoli: +120:01
*** mestery_ has joined #openstack-meeting-alt20:01
yjiang5if yes, we can discuss in IRC.20:01
sadasuyjiang5 : yes20:01
yjiang5which channel you usually stays at? in #openstack-dev?20:02
*** sarob_ has quit IRC20:02
*** devkulkarni1 has joined #openstack-meeting-alt20:02
*** sarob has joined #openstack-meeting-alt20:02
irenabplease keep us posted with details of your further discussion to comment20:02
*** mestery has quit IRC20:02
yjiang5irenab: sure20:02
baoliyjang5, I have a different meeting to attend now.20:03
yjiang5irenab: If we have any conclusion, will post to the list20:03
sadasuyjiang5: lets meet in openstack-dev20:03
yjiang5ok20:03
irenabThank you for the meeting20:03
itzikbthanks20:03
sadasuthanks everyone20:03
yjiang5thanks.20:04
*** irenab has left #openstack-meeting-alt20:04
*** devkulkarni has quit IRC20:05
*** jcooley_ has quit IRC20:05
*** devkulkarni1 has quit IRC20:06
*** sarob has quit IRC20:07
*** sadasu has quit IRC20:08
*** mestery_ is now known as mestery20:08
*** devkulkarni has joined #openstack-meeting-alt20:13
*** rnirmal has joined #openstack-meeting-alt20:18
*** alazarev has quit IRC20:22
*** yogesh has quit IRC20:24
*** IlyaE has quit IRC20:27
*** yogesh_ has joined #openstack-meeting-alt20:28
*** dprince has quit IRC20:30
*** alazarev has joined #openstack-meeting-alt20:32
*** itzikb has quit IRC20:35
*** alazarev has quit IRC20:36
*** derekh has quit IRC20:36
*** IlyaE has joined #openstack-meeting-alt20:42
*** IlyaE has quit IRC20:42
*** IlyaE has joined #openstack-meeting-alt20:44
*** sarob has joined #openstack-meeting-alt20:44
*** Barker has quit IRC20:45
*** jcooley_ has joined #openstack-meeting-alt20:45
*** jcooley_ has quit IRC20:46
*** rook has joined #openstack-meeting-alt20:54
*** kgriffs is now known as kgriffs_afk20:55
*** jtomasek has quit IRC20:55
*** jtomasek has joined #openstack-meeting-alt20:56
*** kgriffs_afk is now known as kgriffs20:58
*** alazarev has joined #openstack-meeting-alt20:58
*** ashaikh_ has joined #openstack-meeting-alt20:58
*** denis_makogon_ has joined #openstack-meeting-alt20:59
*** ashaikh has quit IRC21:00
*** ashaikh_ is now known as ashaikh21:00
*** jtomasek has quit IRC21:01
*** geoffarnold has joined #openstack-meeting-alt21:01
*** amotoki has joined #openstack-meeting-alt21:02
*** yogesh_ has quit IRC21:02
*** denis_makogon has quit IRC21:03
*** denis_makogon_ is now known as denis_makogon21:03
*** dmakogon_ has joined #openstack-meeting-alt21:03
*** jtomasek has joined #openstack-meeting-alt21:04
*** yogesh has joined #openstack-meeting-alt21:05
*** noslzzp has quit IRC21:06
*** aclark_ has quit IRC21:07
*** IlyaE has quit IRC21:07
*** lblanchard has quit IRC21:09
*** IlyaE has joined #openstack-meeting-alt21:10
*** IlyaE has quit IRC21:14
*** julim has quit IRC21:19
*** aignatov has joined #openstack-meeting-alt21:24
*** aignatov has quit IRC21:25
*** enikanorov_ has quit IRC21:26
*** ilyashakhat has quit IRC21:26
*** Brian___ has quit IRC21:26
*** yogesh has quit IRC21:26
*** ilyashakhat has joined #openstack-meeting-alt21:26
*** enikanorov_ has joined #openstack-meeting-alt21:27
*** yogesh has joined #openstack-meeting-alt21:27
*** yogesh has quit IRC21:31
*** jcooley_ has joined #openstack-meeting-alt21:43
*** devkulkarni has quit IRC21:52
*** devkulkarni1 has joined #openstack-meeting-alt21:52
*** yogesh has joined #openstack-meeting-alt21:54
*** baoli has quit IRC21:54
*** vipul is now known as vipul-away21:59
*** nati_uen_ has joined #openstack-meeting-alt22:00
*** geoffarnold has quit IRC22:02
*** matrohon has joined #openstack-meeting-alt22:03
*** nati_ueno has quit IRC22:04
*** pdmars has quit IRC22:08
*** devkulkarni1 has quit IRC22:12
*** vipul-away is now known as vipul22:13
*** sgordon has quit IRC22:21
*** sarob_ has joined #openstack-meeting-alt22:22
*** sarob has quit IRC22:25
*** sarob_ has quit IRC22:27
*** RajeshMohan has quit IRC22:27
*** RajeshMohan has joined #openstack-meeting-alt22:28
*** kraman has quit IRC22:30
*** yogesh has quit IRC22:34
*** jtomasek has quit IRC22:35
*** jcooley_ has quit IRC22:38
*** lblanchard has joined #openstack-meeting-alt22:39
*** yogesh has joined #openstack-meeting-alt22:40
*** yogesh has quit IRC22:44
*** yogesh has joined #openstack-meeting-alt22:45
*** betsy has quit IRC22:48
*** yogesh has quit IRC22:49
*** julim has joined #openstack-meeting-alt22:49
*** yogesh has joined #openstack-meeting-alt22:49
*** eankutse has quit IRC22:53
*** yogesh has quit IRC22:53
*** sacharya has quit IRC22:55
*** kraman has joined #openstack-meeting-alt22:57
*** yogesh has joined #openstack-meeting-alt22:58
*** pcm_ has quit IRC23:00
*** julim has quit IRC23:01
*** yogesh has quit IRC23:02
*** devkulkarni has joined #openstack-meeting-alt23:02
*** yogesh has joined #openstack-meeting-alt23:03
*** RajeshMohan has quit IRC23:03
*** RajeshMohan has joined #openstack-meeting-alt23:04
*** amotoki has quit IRC23:04
*** demorris has quit IRC23:06
*** ashaikh has quit IRC23:08
*** yogesh has quit IRC23:08
*** ashaikh has joined #openstack-meeting-alt23:11
*** stanlagun has quit IRC23:11
*** beekneemech is now known as bnemec23:14
*** matrohon has quit IRC23:16
*** bdpayne has joined #openstack-meeting-alt23:16
*** julim has joined #openstack-meeting-alt23:17
*** amytron has quit IRC23:20
*** yamahata_ has quit IRC23:21
*** kgriffs is now known as kgriffs_afk23:24
*** denis_makogon has quit IRC23:26
*** vipul is now known as vipul-away23:28
*** vipul-away is now known as vipul23:32
*** alazarev has quit IRC23:40
*** boris-42 has joined #openstack-meeting-alt23:41
*** alazarev has joined #openstack-meeting-alt23:43
*** vipul is now known as vipul-away23:44
*** vipul-away is now known as vipul23:44
*** boris-42 has quit IRC23:47
*** RajeshMohan has quit IRC23:48
*** RajeshMohan has joined #openstack-meeting-alt23:48
*** RajeshMohan has quit IRC23:50
*** RajeshMohan has joined #openstack-meeting-alt23:51
*** vipul is now known as vipul-away23:54
*** vipul-away is now known as vipul23:54
*** vipul is now known as vipul-away23:55
*** vipul-away is now known as vipul23:55
*** sacharya has joined #openstack-meeting-alt23:57

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