Thursday, 2014-05-01

*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"00:04
-openstackstatus- NOTICE: the gate is still fairly backed up, though nodepool is back on track and chipping away at remaining changes. some py3k/pypy node starvation is slowing recovery00:04
*** david-lyle has joined #openstack-meeting-300:09
*** david-lyle has quit IRC00:13
*** Swami has quit IRC00:14
*** beyounn has quit IRC00:22
*** TravT has quit IRC00:43
*** yamahata has quit IRC00:44
*** MaxV_ has joined #openstack-meeting-301:04
*** eguz has quit IRC01:10
*** nati_ueno has joined #openstack-meeting-301:16
*** otherwiseguy has joined #openstack-meeting-301:16
*** mwagner_lap has joined #openstack-meeting-301:17
*** MaxV_ has quit IRC01:26
*** jpomero has quit IRC01:30
*** devlaps has quit IRC01:41
*** yamahata has joined #openstack-meeting-301:44
*** nati_ueno has quit IRC01:47
*** devlaps has joined #openstack-meeting-302:13
*** sankarshan is now known as sankarshan_away02:17
*** devlaps has quit IRC02:17
*** jrist is now known as jrist-afk02:30
*** julim has quit IRC02:33
*** beyounn has joined #openstack-meeting-302:53
*** enykeev has joined #openstack-meeting-302:58
*** eghobo has joined #openstack-meeting-303:08
*** devlaps has joined #openstack-meeting-303:13
*** devlaps has quit IRC03:17
*** alexpilotti has quit IRC03:25
*** beyounn has quit IRC03:37
*** otherwiseguy has quit IRC03:50
*** banix has quit IRC04:01
*** devlaps has joined #openstack-meeting-304:13
*** devlaps has quit IRC04:17
*** otherwiseguy has joined #openstack-meeting-305:08
*** otherwiseguy has quit IRC05:13
*** devlaps has joined #openstack-meeting-305:13
*** chuckC has left #openstack-meeting-305:42
*** chuckC has joined #openstack-meeting-305:43
*** chuckC has left #openstack-meeting-305:43
*** Tufin has joined #openstack-meeting-305:55
*** coolsvap|afk is now known as coolsvap06:04
*** Tufin has quit IRC06:18
*** eghobo has quit IRC06:24
*** devlaps has quit IRC06:33
*** Tufin has joined #openstack-meeting-307:12
*** devlaps has joined #openstack-meeting-307:13
*** devlaps has quit IRC07:18
*** jamielennox is now known as jamielennox|away07:23
*** Tufin has quit IRC07:56
*** devlaps has joined #openstack-meeting-308:13
*** devlaps has quit IRC08:17
*** jcoufal has joined #openstack-meeting-308:40
*** MaxV_ has joined #openstack-meeting-308:44
*** overlayer has joined #openstack-meeting-308:51
*** MaxV_ has quit IRC08:55
*** jrist-afk has quit IRC09:08
*** jrist-afk has joined #openstack-meeting-309:11
*** devlaps has joined #openstack-meeting-309:13
*** devlaps has quit IRC09:17
*** jcoufal has quit IRC09:23
*** jcoufal has joined #openstack-meeting-309:23
*** MaxV_ has joined #openstack-meeting-310:03
*** devlaps has joined #openstack-meeting-310:13
*** devlaps has quit IRC10:18
*** overlayer_ has joined #openstack-meeting-310:46
*** overlayer has quit IRC10:47
*** MaxV_ has quit IRC10:52
*** MaxV_ has joined #openstack-meeting-310:55
*** alexpilotti has joined #openstack-meeting-311:04
*** devlaps has joined #openstack-meeting-311:13
*** overlayer_ has quit IRC11:15
*** devlaps has quit IRC11:17
*** overlayer has joined #openstack-meeting-311:28
*** overlayer has quit IRC11:33
*** overlayer has joined #openstack-meeting-311:34
*** jcoufal has quit IRC11:34
*** yamahata has quit IRC11:45
*** coolsvap is now known as coolsvap|afk11:50
*** rkukura_ has joined #openstack-meeting-312:00
*** overlayer_ has joined #openstack-meeting-312:00
*** overlayer has quit IRC12:01
*** devlaps has joined #openstack-meeting-312:13
*** devlaps has quit IRC12:17
*** alexpilotti has quit IRC12:29
*** MaxV_ has quit IRC12:31
*** alexpilotti has joined #openstack-meeting-312:41
*** yamahata has joined #openstack-meeting-312:42
*** MaxV_ has joined #openstack-meeting-312:45
*** ttrifonov_zZzz is now known as ttrifonov12:45
*** alexpilotti has quit IRC12:47
*** MaxV_ has quit IRC12:49
*** MaxV_ has joined #openstack-meeting-313:02
*** safchain has joined #openstack-meeting-313:05
*** MaxV_ has quit IRC13:08
*** jrist-afk is now known as jrist13:09
*** rkukura_ has quit IRC13:13
*** devlaps has joined #openstack-meeting-313:13
*** julim has joined #openstack-meeting-313:16
*** devlaps has quit IRC13:18
*** peristeri has joined #openstack-meeting-313:30
*** lblanchard has joined #openstack-meeting-313:30
*** MaxV_ has joined #openstack-meeting-313:32
*** yamahata has quit IRC13:52
*** yamahata has joined #openstack-meeting-313:52
*** sankarshan_away is now known as sankarshan13:54
*** banix has joined #openstack-meeting-313:59
*** shakamunyi has joined #openstack-meeting-313:59
*** mfer has joined #openstack-meeting-314:00
*** yamahata has quit IRC14:03
*** jpomero has joined #openstack-meeting-314:03
*** banix has quit IRC14:03
*** yamahata has joined #openstack-meeting-314:04
*** devlaps has joined #openstack-meeting-314:13
*** devlaps has quit IRC14:18
*** otherwiseguy has joined #openstack-meeting-314:22
*** alexpilotti has joined #openstack-meeting-314:24
*** david-lyle has joined #openstack-meeting-314:31
*** TravT has joined #openstack-meeting-314:41
*** tjones has left #openstack-meeting-314:47
*** yamahata has quit IRC14:54
*** markmcclain has joined #openstack-meeting-314:54
*** markmcclain1 has joined #openstack-meeting-314:58
*** markmcclain has quit IRC14:59
*** pcm_ has joined #openstack-meeting-315:00
*** pcm_ has left #openstack-meeting-315:03
*** BrianB_ has joined #openstack-meeting-315:03
*** overlayer has joined #openstack-meeting-315:04
*** cjellick has quit IRC15:05
*** nextone92 has joined #openstack-meeting-315:05
*** overlayer_ has quit IRC15:05
*** overlayer has quit IRC15:05
*** overlayer has joined #openstack-meeting-315:06
*** overlayer has quit IRC15:06
*** overlayer has joined #openstack-meeting-315:06
*** yamahata has joined #openstack-meeting-315:07
*** overlayer has quit IRC15:18
*** overlayer has joined #openstack-meeting-315:20
*** jaypipes has quit IRC15:23
*** mestery has quit IRC15:27
*** peristeri has quit IRC15:33
*** BrianB_ has quit IRC15:35
*** cjellick has joined #openstack-meeting-315:37
*** Swami has joined #openstack-meeting-315:39
*** devlaps has joined #openstack-meeting-315:43
*** safchain has quit IRC15:44
*** eghobo has joined #openstack-meeting-315:59
*** nextone92 has left #openstack-meeting-316:04
*** markmcclain1 has quit IRC16:05
*** MaxV_ has quit IRC16:06
*** beyounn has joined #openstack-meeting-316:08
*** nati_ueno has joined #openstack-meeting-316:31
*** alexpilotti has quit IRC16:34
*** sankarshan is now known as sankarshan_away16:34
*** zehicle_at_dell has joined #openstack-meeting-316:36
*** rockyg has joined #openstack-meeting-316:39
*** emagana has joined #openstack-meeting-316:44
*** catherineD has joined #openstack-meeting-316:51
*** markmcclain has joined #openstack-meeting-316:55
*** overlayer has quit IRC16:57
rockygo/16:59
catherineDHello17:00
*** overlayer has joined #openstack-meeting-317:00
zehicle_at_dello/17:00
zehicle_at_dell#startmeeting Refstack17:02
openstackMeeting started Thu May  1 17:02:40 2014 UTC and is due to finish in 60 minutes.  The chair is zehicle_at_dell. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: Refstack)"17:02
openstackThe meeting name has been set to 'refstack'17:02
zehicle_at_dellroll call!17:02
zehicle_at_dello/17:02
rockygthanks for starting.17:02
rockygo/17:03
zehicle_at_delldavidlenwell, you here?17:03
catherineDHere17:04
zehicle_at_dellI don't see David online17:05
rockygyeah.  looks like just a bot.17:06
zehicle_at_delllet me look at the backlog17:06
zehicle_at_delllooks like we have some docs and specs that need reivew (still)17:07
zehicle_at_dellI can give a tcup update17:07
zehicle_at_dell#topic TCUP17:08
*** openstack changes topic to "TCUP (Meeting topic: Refstack)"17:08
zehicle_at_dell#topic Agenda17:08
*** openstack changes topic to "Agenda (Meeting topic: Refstack)"17:08
zehicle_at_delllet's get an agenda together first17:08
zehicle_at_dellTCUP17:08
zehicle_at_dellDefCore status/update17:08
zehicle_at_dellSummit Prep17:08
*** shakamunyi has quit IRC17:09
rockygRefstack dev focus short term17:09
zehicle_at_dellControlling critical JSON asssets (must-pass test lists & driver test json)17:09
rockygsummit meetups (QA, others?)17:09
*** SumitNaiksatam has quit IRC17:10
*** praveen_dell has joined #openstack-meeting-317:10
*** Louis_ has joined #openstack-meeting-317:10
zehicle_at_dellok, let's get started then17:11
praveen_dellHello all17:11
zehicle_at_dell#topic Refstack dev focus short term17:11
*** openstack changes topic to "Refstack dev focus short term (Meeting topic: Refstack)"17:11
*** stack_ has joined #openstack-meeting-317:12
zehicle_at_dellrockyg, your topic...17:12
rockygyo17:12
zehicle_at_dellas far as I know, it's getting the upload API spec nailed and then posted17:12
rockygok.17:13
rockygI'm willing to meet for that.  Sounds like catherineD is in Fremont.  Is ther a coffeeshop with wifi that way?17:13
zehicle_at_dellf2f would help move things forward.17:14
rockygWe can skyp in others and get it nailed enough to prototype.17:14
*** alexpilotti has joined #openstack-meeting-317:14
zehicle_at_dellcan you coordinate w/ davidlenwell17:14
zehicle_at_dellwe don't have critical mass to go further on this one17:15
zehicle_at_dellagree?17:15
zehicle_at_dellfor this meeting (not in general )17:15
rockygYes.17:15
zehicle_at_dell#topic TCUP17:15
*** openstack changes topic to "TCUP (Meeting topic: Refstack)"17:15
catherineDrockyg: IBM site is in south bay (near Morgan Hill.  We can drive to Fremont17:15
*** SridarK has quit IRC17:15
rockygWe definitely need to brainstorm.17:15
catherineDrockyg: +117:16
zehicle_at_dellI follwed Praveen's instructions and got tempest to run from TCUP.  I'm pending an edit to his pull but it's looking good17:16
rockygWe can meet at the endo of a BART line, or in RWC by the Caltrain.17:16
rockygYes!17:16
rockygcatherineD: where do you live?17:17
rockygmy coffee cup is empty :(17:17
praveen_dellI am hoping to edit that document tommorrow as I was busy with my regular stuff17:17
catherineDI live in Cupertino but do not mind driving17:17
davidlenwellHi guys17:17
davidlenwellsorry .. train delay17:17
rockygTrain BART?17:18
zehicle_at_dell#topic Refstack dev focus short term17:18
*** openstack changes topic to "Refstack dev focus short term (Meeting topic: Refstack)"17:18
rockyg^or^17:18
davidlenwellyes bart17:18
zehicle_at_dellI pushed the topic back to Refstack Dev17:19
rockygso, f2f soonest.  We can mee at the southernmost end of a BART line.17:19
davidlenwelllets get back to that in a minute17:19
zehicle_at_dellpending topics are: TCUP, Summit, managed JSON artifacts, Defcore17:19
rockygGoes with the topic.  Nailing down the API spec17:19
rockygAPI upload spec.17:20
davidlenwellI'm working on a spec for that based on the one I already submitted and the notes given by raymond17:21
davidlenwellit will be updated today17:21
davidlenwellwe do not have to have a f2f about the api spec17:21
rockygk17:21
davidlenwellalso I had a chat with catherine earlier this week.. we agreed on several more phone calls leading up to them releaseing a spec that allows api->api communication of results17:21
davidlenwellmeaning local refstack can talk to remote refstack .. i would very much like to stay on track with that plan17:22
davidlenwellwith an agreed upon spec we can finish that code in a day or two17:22
davidlenwellwithout the spec it could eat weeks of rework17:22
davidlenwellplease please please please write the spec .. I am available for as many phone calls that are needed to get there17:22
rockygkool17:22
*** tedchang has joined #openstack-meeting-317:23
davidlenwellif we fly by the seat of our pants leading up to the summit we are going to be caught with our pants down17:23
rockygWho owns that spec?  Catherine or Raymond?17:23
davidlenwelleither one17:23
davidlenwellcatherineD: is who I spoke to about it17:23
rockygLet's get a date locked down for submitting to Gerrit.  catherineD?17:24
catherineDThis is the one with Sync and authorization .... We need to discuss with David about authorization protocol ..17:24
catherineDwhich method for authorization etc ...17:24
davidlenwellcatherineD: lets do a phone call this afternoon to discuss the details of that17:24
*** waiman has joined #openstack-meeting-317:24
*** SumitNaiksatam has joined #openstack-meeting-317:24
catherineDThat is one of the topic for f2f ..17:25
catherineDok17:25
davidlenwellwe'll circle back to face to face in a few17:25
zehicle_at_delladded to agenda :)17:26
davidlenwellthank you17:26
davidlenwellokay lets move on to goals for the sumit .. then we'll talk about the summit session17:26
zehicle_at_dell#topic summit17:26
*** openstack changes topic to "summit (Meeting topic: Refstack)"17:26
davidlenwellso among our goals for the summit..17:26
davidlenwell* distributable tcup17:26
davidlenwell* live results gathering17:27
*** waiman is now known as RaymondWong17:27
davidlenwell* finalized release version specifications17:27
*** markmcclain has quit IRC17:27
davidlenwell* remote api to central api sync17:28
davidlenwelllive results gathering is basically finished.. however there was a question about how to flag things as finished ..17:28
davidlenwellRaymondWong: to answer your questions about that..17:28
davidlenwellI believe we can simply use an error response code / time out to tell if a test fialed for soem reason .. and the act of submitting results back to the api should indicate its finished status17:29
*** otherwiseguy has quit IRC17:29
davidlenwellso we need distributable tcup and the remote api sync17:30
*** catherineD has quit IRC17:30
davidlenwellif catherine can finish the spec for that by monday I think we are in good shape ..17:30
davidlenwellif we need a f2f to make that happen .. we'll discuss it ..17:30
*** catherineD has joined #openstack-meeting-317:30
davidlenwelltoday I am going to work with joshua and zehicle_at_delluntil we have tcup working as it should17:30
RaymondWongI think we can do a phone call for that... we have some questions about what to sync and how to authenticate.17:31
zehicle_at_dell+117:31
davidlenwelljoshua is also going to help a lot with how we are hosting the website and displaying data17:31
*** chuckC has joined #openstack-meeting-317:31
davidlenwellSo I think we can meet the goals I've layed out above17:31
davidlenwellbefore the summit .. but we have to stay orginized and keep on it17:31
davidlenwellI say that for my self as much as anyone else ..17:31
davidlenwellokay .. so moving along to the summit session..17:32
davidlenwellI will be preparing slides and a 20 minute talk giving us a deep dive into the current state of refstack followed by 5 or so about where we are going from here..17:32
zehicle_at_dell#topic summit17:32
*** openstack changes topic to "summit (Meeting topic: Refstack)"17:32
zehicle_at_delljoshua and I also have a defcore preso about it17:33
davidlenwellthe primary goal of this session is to recruite a little more outside help17:33
davidlenwellgain a little more acceptance by the infra group .. they will be invited17:33
davidlenwellwhile at pycon I had a lot of talks with jim blair about how we can integrate with their framework.. and I believe we are in sync. ..17:34
davidlenwellso I want a few of them in the loop as much as possible ..17:34
davidlenwellzehicle_at_dell: can you talk about what it is you are presenting to defcore?17:34
zehicle_at_dellyy17:35
zehicle_at_dellthat's a lot more than Refstack17:35
zehicle_at_dellthe prmary focus is to show community the list of "core capabilities" that we've come up with from the process17:35
zehicle_at_dellthat list (really the must-pass test list) should be setup as a JSON file in refstack BTW17:36
rockygI would like a QA/Tempest liasson for Refstack, also.  Lots of new things there.17:36
zehicle_at_dellbut we need the community to look at that list and understand how we got there17:36
zehicle_at_dellwe have some graphics and examples that help people understand17:36
davidlenwellrockyg: lets come back to that17:36
rockygKewl.  Is the matrix available/will be available?17:36
zehicle_at_dellit's the one we were working on17:37
zehicle_at_dellwe need to get more review on it next week17:37
zehicle_at_dellfrom the tech committees17:37
rockygSo, dev's should be able to see the mapping by viewing the two, but maybe not others.17:37
zehicle_at_dellyy17:37
zehicle_at_dellI'm going to break it into sub specialities for review17:38
rockyggood17:38
zehicle_at_dellbut first I need more explanation of scoring capablities so they don't freak out about the work17:38
zehicle_at_dellwhich also has made great progress17:38
davidlenwellfor now we'll populate the json list in refstack with every single test17:38
zehicle_at_dellall of that leads back to TCUP because we want to collect data17:38
zehicle_at_delldavidlenwell, yes.  that's the plan17:39
zehicle_at_dellwe need to work on a JSON schema for it17:39
zehicle_at_dellthat's another topic I wanted for the agenda17:39
davidlenwellzehicle_at_dell: we've already basically done that17:39
zehicle_at_dell:)17:39
davidlenwellmonths ago catherineD RaymondWong and tedchang sat in a room and talked it out17:39
zehicle_at_dellthat enough about defcore at the summit?17:39
davidlenwellwe should have notes17:39
davidlenwellyeah .. im happy with that17:39
davidlenwellwhats the next topic ?17:39
zehicle_at_delllet's talk about the json then17:39
zehicle_at_dell#topic json17:40
*** openstack changes topic to "json (Meeting topic: Refstack)"17:40
zehicle_at_dellthe driver test team also needs a place to store json info17:40
*** MaxV_ has joined #openstack-meeting-317:40
zehicle_at_dellthat's high stakes (like required tests)17:40
zehicle_at_dellI'd suggested that github/refstack is a good place for that since it's managed17:40
davidlenwellindeed17:41
zehicle_at_dellbut we likely need an agreed directory for it17:41
*** MaxV_ has quit IRC17:41
davidlenwellzehicle_at_dell: thats easy enough17:41
zehicle_at_dellyy17:41
zehicle_at_delljust want to get naming right17:41
zehicle_at_delland it would make sense to put the place holders there17:41
rockygand a rst file with instructions17:41
zehicle_at_delldriver test team has the files (I believe)17:41
davidlenwellzehicle_at_dell: since we are sharing with another team .. lets write it up in a spec17:42
davidlenwellthat way its clear17:42
zehicle_at_dellwe also need to document the control process - since the review cycle needs to be a bit more transparent17:42
rockyg+117:42
davidlenwellzehicle_at_dell: can you elaborate on that please?17:42
zehicle_at_dellmeaning, a vendor rep would need to +1 on changes to their driver17:42
zehicle_at_delland a defcore committee member (Josh or I likely) wouldk have to +1 changes to the must-pass list17:43
zehicle_at_dellso, the review of those files is specialized17:43
davidlenwellwell adding you guys to the gate should be easy enough17:43
zehicle_at_dellwe don't have to be gate17:43
zehicle_at_dellin fact, I'd rather not17:43
davidlenwellyou want +approve17:43
zehicle_at_dellright17:43
davidlenwellnot +217:43
davidlenwellI'll have to figure out if we can do that17:44
zehicle_at_dellthanks17:44
davidlenwellwe might need to eventually move things to another repo17:44
*** otherwiseguy has joined #openstack-meeting-317:44
rockygLikely, once things get more formal.17:44
zehicle_at_dellperhaps - I think it's OK if we don't have all the bells17:44
zehicle_at_dellas long as we agree on the process we can use transparency to make sure it's legit17:44
rockyg+1  Lots of business stuff gets invloved later on.17:44
davidlenwellfor now I can agree to not +2 +a something unles syou or josh have +1'd it17:45
zehicle_at_dellthat's what I was looking for17:45
davidlenwellin that folder17:45
davidlenwellor file17:45
davidlenwellas far as the rest of the code goes .. things will proceed as normal17:45
rockyg+1;)17:45
zehicle_at_dell+117:45
zehicle_at_dellname of the folder?17:45
*** eghobo has quit IRC17:46
rockygthirdparty17:46
zehicle_at_dellsuggestions?  /reference /truth /requirements17:46
*** eghobo has joined #openstack-meeting-317:46
davidlenwell/defcore/requirements.json ?17:46
zehicle_at_dellnot quite17:46
zehicle_at_dellI'm OK w/ defcore17:46
davidlenwellzehicle_at_dell: can you write up the spec for the format of the json?17:47
RaymondWongit may need to be versioned, havana vs icehouse...17:47
zehicle_at_dellwas thiking /defcore/must-pass.json and /defcore/drivers.json17:47
davidlenwellRaymondWong: probably yes17:47
zehicle_at_dellRaymondWong, yes OR needs to be in the json format17:47
zehicle_at_dellprobably better to have a file per version17:48
davidlenwellzehicle_at_dell: "/defcore/havana/must-pass.json17:48
zehicle_at_dell+117:48
rockyg+117:48
davidlenwelloh .. use underscores in file names not - signs17:48
zehicle_at_delldavidlenwell, I'd rather defer to you or others on the json schema because it really drives the web page17:48
davidlenwellRaymondWong: I think you would be well suited to write this spec17:49
zehicle_at_delllet's keep it simpler.... /defcore/havana/coretests.json17:49
rockygyes!17:49
RaymondWongwho is going to do the scoring part of code? that will depend on the json, and may have requirements for that.17:50
zehicle_at_dellRaymondWong, that's Defcore's job17:50
zehicle_at_dellwe've got a list of tests that are required for core17:50
zehicle_at_dell...um... will have.  not done yet ;)17:51
davidlenwellRaymondWong: we just need to set up the format for the data17:51
RaymondWongi meaning implementing the code logic in refstack to compare the result with the requirement to give a pass/fail score on the web page.17:51
davidlenwellRaymondWong: you are getting ahead of your self17:51
zehicle_at_dellagree, we DO want that but first we need to collect the data17:52
davidlenwellokay .. so zehicle_at_dell.. can you give us a really rough idea of what the requirements coming from defcore will look like ?17:52
zehicle_at_dellyes17:52
rockygHow about if we can just display the results with fails highlighted?17:52
zehicle_at_dellbasically, it's just a list of tests17:52
davidlenwellif you can get that to raymond todayish17:52
zehicle_at_dellthe test names17:53
*** Swami_ has joined #openstack-meeting-317:53
zehicle_at_dellthere's also a concept of capabilities17:53
zehicle_at_dellso, we'd also have a mapping of tests into capability groups17:53
*** rand738 has quit IRC17:53
davidlenwellokay .. lets clear this up ..we do not need to display anything right now17:53
zehicle_at_delllikely that should be a JSON file too17:53
zehicle_at_delldavidlenwell, correct.  that's future function17:53
davidlenwellright now we need to collect data17:53
zehicle_at_dellI think we'll need a second JSON file for /defcore/havana/capabilities.json17:54
davidlenwellso having this thing in place that parses the data through this json file we are taling abotu is not currently required17:54
rockygOK.  So, where do these json files get stored?17:54
zehicle_at_dellbut, again, that's not to be linked into the UI yet17:54
*** marun has joined #openstack-meeting-317:54
davidlenwellin the repo rockyg17:54
rockygThe results, that is.17:54
*** rkukura has joined #openstack-meeting-317:54
zehicle_at_delldavidlenwell, correct.  not required yet17:54
davidlenwellthe results are stored RAW in the database17:54
*** markmcclain has joined #openstack-meeting-317:55
davidlenwellwe'll process them later .. catherineDhas done a good job writing tools that allow us to bulk process data17:55
*** rand738 has joined #openstack-meeting-317:55
zehicle_at_delldavid - do you want me to put those files in as placeholders?17:56
davidlenwellzehicle_at_dell: yes please17:56
zehicle_at_dellkk17:56
davidlenwellRaymondWong: we can talk offline about what I expect from a spec for this17:57
davidlenwellit is 11 .. so we do need to wrap up in here17:57
zehicle_at_dell#topic wrapup17:57
*** openstack changes topic to "wrapup (Meeting topic: Refstack)"17:57
*** hemanthravi has joined #openstack-meeting-317:57
*** thinrichs has joined #openstack-meeting-317:57
zehicle_at_dellI think we'll need to make specific plans for summit next meeting17:57
rockygwhat's left undiscussed on agenda?17:57
davidlenwellI'll be in #refstack all day .. joshua will be working with me .. please jump in and nag for things17:58
zehicle_at_dellyou got f2f covered?17:58
catherineDDavid and we will ahve a call to discuss authentication ...17:58
davidlenwellwe're delaying it for now17:58
*** terryw has joined #openstack-meeting-317:58
davidlenwellcatherineD: lets say at 4pm17:58
rockygworks for me.17:58
catherineDOK17:58
*** mestery has joined #openstack-meeting-317:58
rockygback over to #refstack for me for just a little bit.17:59
davidlenwellokay zehicle_at_dell don't forget to end the meeting here17:59
*** otherwiseguy has quit IRC17:59
zehicle_at_dellI'm online most of the time - got to drive in for a few meetings but then back.  I'll ping in and out of #refstack17:59
*** s3wong has joined #openstack-meeting-317:59
zehicle_at_dell#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Thu May  1 17:59:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-05-01-17.02.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-05-01-17.02.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-05-01-17.02.log.html17:59
*** jpomero_ has joined #openstack-meeting-318:00
*** banix has joined #openstack-meeting-318:00
SumitNaiksatamhi Neutrons!18:00
s3wongHello18:00
SumitNaiksatambanix: hi18:01
SumitNaiksatams3wong: hi18:01
banixSumitNaiksatam: hi18:01
*** kanzhe has joined #openstack-meeting-318:01
Swami_hi all18:01
banixhi everybody18:01
hemanthravihi18:01
*** rockyg has left #openstack-meeting-318:01
SumitNaiksatamhemanthravi: hi18:01
SumitNaiksatamSwami: hi18:02
SumitNaiksatamok lets get started18:02
SumitNaiksatam#startmeeting networking_policy18:02
openstackMeeting started Thu May  1 18:02:29 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** jpomero has quit IRC18:02
*** openstack changes topic to " (Meeting topic: networking_policy)"18:02
openstackThe meeting name has been set to 'networking_policy'18:02
marunhi18:02
*** praveen_dell has quit IRC18:02
*** terryw has quit IRC18:03
thinrichsHi all18:03
rkukurahi18:03
*** catherineD has left #openstack-meeting-318:03
*** otherwiseguy has joined #openstack-meeting-318:03
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy18:03
SumitNaiksatam#topic GP bp spec review18:04
*** openstack changes topic to "GP bp spec review (Meeting topic: networking_policy)"18:04
SumitNaiksatam#link https://review.openstack.org/#/c/89469/18:04
SumitNaiksatami think a lot of comments were addressed over the last week18:04
SumitNaiksatami think we are making good progress and close to converging18:04
SumitNaiksatamquestions/thoughts on that?18:05
SumitNaiksatamok we can move on the PoC update18:06
banixlooking good!18:06
SumitNaiksatambanix: ok18:06
SumitNaiksatam#topic PoC Status Update18:06
*** openstack changes topic to "PoC Status Update (Meeting topic: networking_policy)"18:06
SumitNaiksatamwe had some folks huddling together last tuesday and spending a few hours brainstorming on the PoC18:07
SumitNaiksatami think a lot of issues got sorted out during that discussion18:07
SumitNaiksatamthanks to all those who participated18:07
*** otherwiseguy has quit IRC18:08
*** john_cl has joined #openstack-meeting-318:08
SumitNaiksatam#info PoC branch is: https://github.com/noironetworks/neutron-group-policy/tree/group-policy-poc18:08
SumitNaiksatami made some changes to the model based on the feedback on the gerrit review18:09
s3wongSumitNaiksatam: such as?18:09
SumitNaiksatamnothing that we did not discuss on tuesday18:09
SumitNaiksatami am referring to whatever i did before tuesday18:10
SumitNaiksatamcurrently we still only have EPG, EP, BD and RD represented in the PoC branch as far as the model is concerned18:10
SumitNaiksatamhope to make progress on that18:10
*** s3wong has quit IRC18:10
SumitNaiksatami think rkukura has made good progress on the mapping driver18:10
SumitNaiksatamrkukura: over to you18:11
rkukuraSumitNaiksatam: Do those resources in the PoC code all match the current spec?18:11
SumitNaiksatamrkukura: i think so18:11
rkukuraI didn’t make much progress yesteday, but am today18:11
rkukuraI hope to push an update late today that create the neutron resources when GP resources are created.18:11
SumitNaiksatamrkukura: sweet18:11
Louis_i noticed that classifier and action are not in db_group_policy.py18:12
SumitNaiksatambtw, the group policy to classical neutron resources is being captured in this document (for the PoC): #link https://docs.google.com/a/noironetworks.com/document/d/134P7TJdiIfjPWbmstSTY4vp9E6oRYTFs64ON3thFxhI/edit#18:12
rkukuraI’ll push that to rkukura/mapping, and we can review and decide when to merge to group-policy-poc18:12
*** s3wong_ has joined #openstack-meeting-318:12
s3wong_sorry, disconnect for a moment18:12
SumitNaiksatamLouis_: not implemented yet18:12
SumitNaiksatamLouis_: we wanted to get an end-to-end flow going with the EP and the EPG18:13
SumitNaiksatamLouis_: also waiting for some of the discussion to settle down on gerrit18:13
SumitNaiksatambut we should be good to implement those now, its next on my list18:13
Louis_thx - is the intent to use ml2 driver mechanisms?18:13
rkukuraI don’t see any reason progress can’t be made on the other parts of the model in the PoC while the mapping of the EP, EPG, BD, and RD are being completed18:14
rkukuraLouis_: The GP plugin has a driver API similar to ML2’s driver API18:14
SumitNaiksatamrkukura: yes those things are going in parallel18:14
rkukuraLouis_: And the plan is for the GP plugin to work with the ML2 plugin’s neutron resources when its mapping driver is used18:15
Louis_thx18:15
SumitNaiksatamrkukura: my earlier comment was not that the progress is waiting for the mapping to happen, it was more like our focus is on getting on flow going first18:15
SumitNaiksatamon -> one18:15
rkukuraSumitNaiksatam: agreed18:16
SumitNaiksatamrkukura: anything else?18:16
rkukuraNot from me18:16
SumitNaiksatamrkukura: thanks, great progress18:16
*** mandeep has joined #openstack-meeting-318:16
SumitNaiksatams3wong_: over to you18:16
SumitNaiksatamfor the service redirect part18:16
Louis_can you add an example of consumer/provider and role/capab18:16
SumitNaiksatamLouis_: sure18:17
Louis_thx18:17
s3wong_I started looking at it. The idea is to have an UUID passed, and for the PoC, I will assume this is FW, and will then turn on FW on the router between two EPG18:17
SumitNaiksatams3wong_: ok, i know this is a tough one for you, since the discussion on the services’ side is very much evolving18:18
SumitNaiksatams3wong_:  i guess we will need to iterate through this18:18
*** s3wong_ is now known as s3wong18:18
s3wongin the future, of course, the service object would tell us where to put the object can be inserted and traffic could be steered18:18
s3wongbut for now, we have no way of "redirect" flow to "service" in Neutron18:19
Louis_will the redirect action value be a list of service instance uuids or a service chain uuid or either?18:19
s3wongso for the PoC, I will just turn on FWaaS on a router :-)18:19
SumitNaiksatams3wong: yes, we will rely on abstractions exposed by the adv services’ framework to do insertion, steering, etc18:19
SumitNaiksatams3wong:  ok18:19
banixLouis_: a service chain uuid18:20
s3wongLouis_: for now, we agreed on having redirect be the final action18:20
SumitNaiksatamLouis_: either one service or a service chain18:20
banixLouis_: not implemented yet18:20
s3wongand that object can certainly be service chain18:20
SumitNaiksatamLouis_: yeah, like banix and s3wong  said abouve, its one single uuid, either service or service chain18:20
Louis_what do u mean by "final" action?18:21
SumitNaiksatamLouis_: however service chain is currently not represented in neutron18:21
Louis_i see18:21
SumitNaiksatamany other questions for s3wong or on service redirect?18:22
SumitNaiksatamredirect action that is18:23
Louis_would order of the list of service uuids be siginifcant?18:23
SumitNaiksatamLouis_: the order is significant in the proposed chain resources18:23
SumitNaiksatam*resource18:23
SumitNaiksatamideally it would be a graph representation18:23
SumitNaiksatambut that is difficult to achieve18:24
s3wongSumitNaiksatam: Louis_: are we still talking about 'redirect' or service chaining in Neutron in general?18:24
SumitNaiksatamwe will be happy if we can get going with a linear ordered chain18:24
SumitNaiksatams3wong: yes, sorry, we are digressing to advanced services discussion in neutron18:24
Louis_redirect18:24
s3wongLouis_: 'redirect' to only one UUID, and you should only have one 'redirect' action18:25
s3wongat least for now18:25
Louis_ok18:25
SumitNaiksatamLouis_: fyi - we have a different meeting to discuss services chains and other services’ related aspects in neutron: #link https://wiki.openstack.org/wiki/Meetings/AdvancedServices18:25
*** MaxV has joined #openstack-meeting-318:25
Louis_am aware of that thx18:25
SumitNaiksatamhemanthravi: any progress on the Client, CLI?18:26
hemanthraviSumitNaiksatam: not much since the last commit, will work on this and should have it done by sun18:27
SumitNaiksatamhemanthravi: ok18:27
SumitNaiksatamhemanthravi: so what resources are currently implemented?18:27
hemanthraviand test it out with rkukura's mapping branch, any config that i need to have?18:27
hemanthraviendpoint, endpoint-group are currently impl18:28
SumitNaiksatamhemanthravi: we have a PoC branch18:28
SumitNaiksatamhemanthravi: are they updated with the latest model?18:28
hemanthraviSumitNaiksatam: i think ep, epg didn't change, but will check18:29
SumitNaiksatamhemanthravi: ok thanks18:29
hemanthravirkukura: any config that i need to run the gp plugin?18:29
SumitNaiksatamhemanthravi: any chance that you can have the EP/EPG by friday?18:29
rkukuraI haven’t tried it outside the UTs18:29
SumitNaiksatamhemanthravi: the service plugin needs to be set to the group policy plugin18:30
hemanthraviSumitNaiksatam: most likely sat18:30
rkukuraYou’ll need to configure a core_plugin and list of service_plugins, which should include group_policy plugin18:30
hemanthravirkukura, SumitNaiksatam: ok18:30
SumitNaiksatamhemanthravi: there is a noop plugin driver which is used for the UTs18:31
rkukuraYou may need to configure the GP plugin to use the dummy driver for now, or the mapping driver if you want neutron resources to be created (once I push)18:31
SumitNaiksatamhemanthravi: yeah rkukura and I are saying the same thing18:31
hemanthravirkukura: ok will try it out and ping you with any qs18:32
SumitNaiksatamhemanthravi: i would recommend that you just use the dummy driver to begin with18:32
hemanthraviSumitNaiksatam: will do18:32
rkukurayes, the noop driver’s name is ‘dummy’18:32
rkukurahemanthravi: sure18:32
SumitNaiksatamany questions for hemanthravi regarding client/CLI18:32
*** prasadv has joined #openstack-meeting-318:33
SumitNaiksatamok moving on18:33
SumitNaiksatamronak here?18:34
SumitNaiksatamso ronak bravely stood up to take on the Horizon piece!18:34
* SumitNaiksatam applauds Ronak :-)18:34
hemanthravi+118:34
SumitNaiksatambut he doesnt seem to be here to absorb the applause18:34
* mandeep agrees18:34
nati_uenohi I'm writing wireframes18:35
nati_uenofor horizon18:35
nati_uenohttps://docs.google.com/presentation/d/1SmbhY5GTBKFV0U6XmAlaWn2nm-biV5bFVZDURZslNrg/edit#slide=id.g333b16535_035118:35
SumitNaiksatamnati_ueno: oh wow!18:35
* s3wong applauds nati_ueno instead :-)18:35
SumitNaiksatamronak also had captured some of the discussions in his wire frames18:36
nati_uenoI'm still struggling to understand gp, but we can use this as basement for discussion18:36
nati_uenoso can I have feedback on here?18:36
mandeepnati_ueno: roank is also building wireframes for group based policy. Can you follow up with him?18:36
SumitNaiksatamnati_ueno: this is very nice and detailed18:36
nati_uenomandeep: yap, interstting18:36
nati_uenois here here?18:36
nati_uenomandeep: could you share his mail address?18:37
nati_uenoSumitNaiksatam: thanks18:37
Swami_nati_ueno: good work on the UI Prototype18:37
mandeepnati_ueno: I will send that tou you by email18:37
nati_uenomandeep: Thnaks18:37
nati_uenoSwami_: Thanks18:37
nati_uenoso quick question18:37
nati_uenowhat's filters?18:37
nati_uenoI can't figureout, so it is ? in the wireframe18:37
*** otherwiseguy has joined #openstack-meeting-318:38
banixnati_ueno: thanks for the work; had a quick look; one comment18:38
SumitNaiksatamnati_ueno: filters defines who can consume a part of a contract, and who can provide a part of a contract18:38
mandeepnati_ueno: filters limit the scope of a specific policy rule to a specific role/capability (if that us desired)18:38
SumitNaiksatamnati_ueno: but filters can be optional18:38
banixnati_ueno: ahhh i noticed teh answer to the question i was about to ask….18:39
nati_uenohmm filters18:39
nati_uenobanix: ok18:39
SumitNaiksatamnati_ueno: quickly skimming through the document, i think we can simplify some of the workflow18:39
nati_uenoSumitNaiksatam: ok18:39
nati_uenoSumitNaiksatam: also, could you update filters part?18:40
nati_uenoSumitNaiksatam: may be, I can understand it if I see the UI18:40
SumitNaiksatamnati_ueno: sure18:40
nati_uenoSumitNaiksatam: I added you as an editor18:40
SumitNaiksatamnati_ueno: thanks18:40
mandeepnati_ueno: Can you add me and ronal as editors as well18:41
nati_uenoSumitNaiksatam: now you should believe me as I'm app guy.. actually, I'm UI guy :P18:41
mandeepnati_ueno: Renaissance man ... ;-)18:41
nati_uenomandeep: sure! please share mail address of yours (gmail version)18:41
SumitNaiksatamnati_ueno: you are all rolled into one18:42
Louis_volunteering my services...18:42
SumitNaiksatamnati_ueno: you talented Mr. Rippley!18:42
mandeepnati_ueno: I will send you that in the email as well18:42
*** MaxV has quit IRC18:42
nati_uenoSumitNaiksatam: mandeep: Thanks18:42
banixnati_ueno: now that you mentioned you are an app guy, what do you think of terms “provider” and “consumer”?18:43
banixnati_ueno: do they sound right? Do people use other terms?18:43
nati_uenobanix: honestly, it takes time to figure out the meanings18:43
*** peristeri has joined #openstack-meeting-318:44
nati_uenowe need some analogies18:44
SumitNaiksatamany more questions for on Horizons18:44
SumitNaiksatamnati_ueno: good point18:44
Louis_need some examples18:44
*** otherwiseguy has quit IRC18:44
mandeepLouis_: There is a PoC use-case on the wiki. Did you have a chance to look at that?18:45
Louis_yes could be clearer18:45
*** SridharRamaswamy has joined #openstack-meeting-318:45
nati_uenoso my big concern is there is no resource which shows consumer - provider -contract reationship.18:46
nati_uenoit is devised in several resource18:46
nati_uenoIn UI, we can correlate it, but18:46
nati_uenoit sounds like hard in CLI18:46
SumitNaiksatamnati_ueno: actually there is are two resources to capture the relationship18:46
nati_uenoSumitNaiksatam: yes two18:46
nati_uenoSumitNaiksatam: so it is devided18:47
*** jpomero__ has joined #openstack-meeting-318:47
nati_uenoSumitNaiksatam: ConsumerScore, ProviderScope, right?18:47
SumitNaiksatamnati_ueno: no, one for provider, one for consumer18:47
SumitNaiksatamnati_ueno: yes18:47
nati_uenoSumitNaiksatam: and ConsumerScope and ProviderScope is linked by selector?18:47
SumitNaiksatamnati_ueno: we got a lot of feedback that it was easier to understand that way, then all rolled into one18:47
nati_uenoya,18:47
nati_uenoso if we have one single scope object18:48
SumitNaiksatamnati_ueno: they both have a selector as an attribute18:48
nati_uenoSumitNaiksatam: yes. so they are connected by attribute18:48
SumitNaiksatamnati_ueno: i originally had only one18:48
mandeepnati_ueno: One important requirement was that these actions be decoupled from each other in time and privilages. This separation enables that18:48
nati_uenomandeep: we can have multiple scopes18:49
*** jpomero_ has quit IRC18:49
SumitNaiksatamone thing i wanted to put out there is that the workflow and interface we see in the UI does not have to map the exact resources in the backend18:49
mandeepnati_ueno: I am sorry I did not follow that.18:49
SumitNaiksatamwe can devise the workflow in an easier to consume fashion18:50
mandeepnati_ueno: Scope is a property of the relationship (either provider or consumer),18:50
nati_uenoSumitNaiksatam: It is better to easy to map18:50
nati_uenoGood model is easy to map UI18:50
SumitNaiksatamnati_ueno: not necessarily18:51
SumitNaiksatamwe have 10 mins or less18:51
mandeepIs rudra here18:51
*** otherwiseguy has joined #openstack-meeting-318:51
SumitNaiksatamthanks nati_ueno for the update18:51
SumitNaiksatammoving on to heat18:51
nati_uenoSumitNaiksatam: Thanks!18:51
SumitNaiksatamprasadv: here?18:52
SumitNaiksatami believe prasadv claimed victory here :-P18:52
banixnati_ueno: thanks!18:52
prasadvyes18:52
prasadvI have the classifier template18:52
prasadvand rest of them are mostly copy and paste18:52
nati_uenobanix: :)18:52
prasadvI had a question as to testing these18:53
SumitNaiksatamprasadv: go ahead18:53
prasadvwhen do we want to test the first call18:53
SumitNaiksatamprasadv: whenever the client is ready18:53
prasadvi mean say classifier through the neutron api18:53
SumitNaiksatamprasadv: that will be sometime next week18:53
mandeepprasadv: Rudra is bringing up an AWS instance with devstack on the integration branch18:53
prasadvthis is not with the client but with neutron api18:53
mandeepprasadv: We will be doing ene-to-end PoC integration on that18:54
prasadvok. meanwhile I will check in the resources..18:54
SumitNaiksatamprasadv: please do18:54
s3wongprasadv: cool18:55
SumitNaiksatamprasadv: thanks, and great progress!18:55
prasadvalso the template I will be using is what is provided on the preso right?18:55
Louis_will there be a gp meeting at summit?18:55
SumitNaiksatamLouis_: good question18:55
SumitNaiksatamthat was the next topic18:55
banixthanks prasadv !18:56
s3wongLouis_: both conference presentation as well as design summit, yes18:56
mandeepYes, thanks prasadv18:56
Louis_date  time?18:56
SumitNaiksatam#topic Atlanta summit18:56
*** openstack changes topic to "Atlanta summit (Meeting topic: networking_policy)"18:56
SumitNaiksatamdesign summit session #link http://junodesignsummit.sched.org/event/e9dd467daf0cae0cdb29ee97d64bbf56#.U2KMDK1dX3A18:56
s3wongLouis_: presentation will be Thurs @13:30; design session keeps on changing :-)18:57
banixThursday at 1:30 for the general talk18:57
SumitNaiksatamconference session: #link http://openstacksummitmay2014atlanta.sched.org/event/456a216328d5ff2162e3cefa168eb648#.U2KZE61dX3B18:57
SumitNaiksatamwe need to prepare for both18:58
SumitNaiksatambanix: over to you for the preso18:58
banixhave a first draft for the conference talk18:58
SumitNaiksatambanix: nice18:59
SumitNaiksatami think its coming along very well18:59
banixTrying to keep the discussion as simple as possible and then build on it to avoid getting bugged down in details early on18:59
s3wongbanix: Thanks!18:59
SumitNaiksatambanix: thanks!18:59
SumitNaiksatam#topic Open Discussion18:59
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:59
SumitNaiksatamany parting thoughts?18:59
banixSure; Will be working on it in the next 2 weeks :)18:59
SumitNaiksatambanix: thanks19:00
s3wongbanix: up until the morning of the presentation!19:00
SumitNaiksatams3wong: :-)19:00
banixs3wong: indeed :)19:00
s3wongbanix: it is exactly two weeks!19:00
SumitNaiksatams3wong: thats scary!19:00
mandeepbanix: s3wong: Just wanted to mention that we should have a common devstack server to work on soon19:00
SumitNaiksatamanything else?19:00
SumitNaiksatammandeep: thanks for bringing that up19:01
SumitNaiksatamrudra, is not here19:01
banixmandeep: that would be great19:01
SumitNaiksatamhe has taken that up19:01
s3wongmandeep: great!19:01
* SumitNaiksatam applauds rudra!19:01
SumitNaiksatamok we over time19:01
SumitNaiksatamthanks everyone!19:01
SumitNaiksatamuntil next week19:01
SumitNaiksatambye!19:01
s3wongthanks!19:01
banixbye19:01
SumitNaiksatam#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
openstackMeeting ended Thu May  1 19:01:55 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
*** prasadv has quit IRC19:01
rkukurabye19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-01-18.02.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-01-18.02.txt19:02
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-01-18.02.log.html19:02
*** hemanthravi has quit IRC19:02
Swami_bye19:02
*** Swami_ has left #openstack-meeting-319:02
*** thinrichs has quit IRC19:02
*** rkukura has left #openstack-meeting-319:02
*** s3wong has quit IRC19:10
*** eguz has joined #openstack-meeting-319:19
*** eguz has quit IRC19:19
*** eghobo has quit IRC19:23
*** MaxV has joined #openstack-meeting-319:26
*** otherwiseguy has quit IRC19:30
*** otherwiseguy has joined #openstack-meeting-319:31
*** MaxV has quit IRC19:31
*** MaxV has joined #openstack-meeting-319:33
*** lenrow has joined #openstack-meeting-319:34
*** Louis_ has quit IRC19:35
*** zehicle_at_dell has quit IRC19:37
*** otherwiseguy has quit IRC19:41
*** devlaps has quit IRC19:43
*** otherwiseguy has joined #openstack-meeting-319:45
*** nati_ueno has quit IRC19:45
*** jpomero__ has quit IRC19:46
*** mandeep has quit IRC19:46
*** otherwiseguy has quit IRC19:48
*** terryw has joined #openstack-meeting-319:48
*** schofield has joined #openstack-meeting-319:55
*** lenrow has quit IRC19:55
*** schofield has quit IRC19:56
*** schofield has joined #openstack-meeting-319:57
*** nati_ueno has joined #openstack-meeting-319:58
*** peristeri has quit IRC20:01
*** schofield has left #openstack-meeting-320:03
*** MaxV has quit IRC20:07
*** lblanchard has quit IRC20:11
*** jpomero has joined #openstack-meeting-320:12
*** kanzhe has quit IRC20:12
*** jpomero has quit IRC20:18
*** jpomero has joined #openstack-meeting-320:28
*** devlaps has joined #openstack-meeting-320:34
*** SumitNaiksatam has quit IRC20:34
*** stack_ has quit IRC20:38
*** stack__ has joined #openstack-meeting-320:39
*** MaxV has joined #openstack-meeting-320:43
*** david-lyle has quit IRC21:03
*** eghobo has joined #openstack-meeting-321:10
*** eghobo has quit IRC21:11
*** eghobo has joined #openstack-meeting-321:11
*** rockyg has joined #openstack-meeting-321:16
*** jamielennox|away is now known as jamielennox21:18
*** terryw has quit IRC21:22
*** soconnor-miranti has joined #openstack-meeting-321:22
*** soconnor-miranti is now known as OAK227821:24
*** OAK2278 is now known as Oak227821:24
*** Oak2278 has quit IRC21:26
*** Oak2278 has joined #openstack-meeting-321:28
*** Oak2278 has left #openstack-meeting-321:28
*** emagana has quit IRC21:43
*** MaxV has quit IRC21:46
*** zehicle_at_dell has joined #openstack-meeting-321:51
*** marun has quit IRC21:55
*** marun has joined #openstack-meeting-321:55
*** marun has quit IRC21:58
*** banix has quit IRC22:11
*** markmcclain has quit IRC22:14
*** otherwiseguy has joined #openstack-meeting-322:26
*** rockyg has quit IRC22:44
*** overlayer has quit IRC22:45
*** chuckC has quit IRC23:01
*** chuckC has joined #openstack-meeting-323:04
*** beyounn has quit IRC23:07
*** chuckC has quit IRC23:11
*** SumitNaiksatam has joined #openstack-meeting-323:12
*** mikal is now known as stillbert23:18
*** waiman has joined #openstack-meeting-323:21
*** RaymondWong has quit IRC23:21
*** waiman is now known as RaymondWong23:24
*** mestery has quit IRC23:31
*** RaymondWong has quit IRC23:35
*** shakamunyi has joined #openstack-meeting-323:42

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