Thursday, 2015-07-09

*** galstrom_zzz is now known as galstrom00:03
*** puranamr has joined #openstack-meeting-400:07
*** galstrom is now known as galstrom_zzz00:13
*** Swami has quit IRC00:14
*** delatte has joined #openstack-meeting-400:15
*** galstrom_zzz is now known as galstrom00:15
*** irenab has joined #openstack-meeting-400:17
*** delattec has quit IRC00:17
*** yamahata has joined #openstack-meeting-400:18
*** galstrom is now known as galstrom_zzz00:19
*** irenab has quit IRC00:21
*** dims has quit IRC00:21
*** sballe has quit IRC00:22
*** puranamr has quit IRC00:25
*** puranamr has joined #openstack-meeting-400:28
*** auld has quit IRC00:33
*** auld has joined #openstack-meeting-400:35
*** banix has joined #openstack-meeting-400:45
*** hurricanerix has joined #openstack-meeting-400:46
*** catherineD has joined #openstack-meeting-400:50
*** xingchao has joined #openstack-meeting-400:53
*** rockyg has joined #openstack-meeting-400:57
*** cdelatte has joined #openstack-meeting-400:57
*** sdake has joined #openstack-meeting-400:57
*** delatte has quit IRC00:59
*** xingchao has quit IRC00:59
*** xingchao has joined #openstack-meeting-401:00
markvoelker#startmeeting defcore01:00
openstackMeeting started Thu Jul  9 01:00:27 2015 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at http://wiki.debian.org/MeetBot.01:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:00
*** openstack changes topic to " (Meeting topic: defcore)"01:00
openstackThe meeting name has been set to 'defcore'01:00
markvoelker#chair hogepodge01:00
openstackCurrent chairs: hogepodge markvoelker01:00
markvoelkero/01:00
catherineDo/01:00
markvoelker#link https://etherpad.openstack.org/p/DefCoreFlag.7 Agenda for today01:01
markvoelkerhogepodge: around?01:01
hogepodgeo/01:01
*** sdake_ has quit IRC01:01
markvoelkeranyone else today?  Rob and Egle are out.01:01
hurricanerixo/01:01
rockygo/01:01
markvoelkerOk then, off we go....01:02
hogepodgePlease drop your timezone also.01:02
hogepodgePDT01:02
hurricanerixCST01:02
catherineDPDT01:02
markvoelkerEDT01:02
markvoelker#topic Alternating meeting schedule review01:02
*** openstack changes topic to "Alternating meeting schedule review (Meeting topic: defcore)"01:02
*** DericHorn-HP has joined #openstack-meeting-401:03
markvoelkerSo earlier in the flag cycle we adopted an alternating meeting schedule and set an AI for today to talk about whether it's working out or not.01:03
markvoelkerThe idea was to make DefCore meetings more accessible to global participation.01:03
markvoelkerLooking back over past meeting logs, we have gotten some AsiaPac participation...though not a lot.01:03
markvoelkerPersonally I'm fine with the current alternating times, but it's worth discussing.  Any strong opinions?01:04
rockygpdt01:04
hogepodgeI've noticed smaller participation for the later time, and some europeans stating the later time is not possible for them.01:05
hogepodgeI'd prefer the early morning (PDT) time, but it's not an overly strong preference.01:05
*** xingchao has quit IRC01:06
*** vinceb has joined #openstack-meeting-401:06
markvoelkerhogepodge: we are getting some participation from AsiaPac at the later time though...do you know of European folks interested in attending that aren't because of the time?01:06
markvoelkerPersonally today's meeting time isn't super great for me, but it's not horrible either and I'm happy to keep it if it means we're letting AsiaPac participate.01:07
hogepodgeone person from the tailgate group was adamant that the meeting time for tonight isn't possible to attend.01:07
catherineDdo we get European folks at the earlier time?01:07
rockygtailgate?01:08
markvoelkerhogepodge: what about the other alternating week timeslot (15:00 UTC).  That should be much more doable for Europe, no?01:08
hogepodgerockyg: it's an interoperability and testing group formed in Vancouver01:08
hogepodgemarkvoelker: I can check01:08
markvoelkerOk.  I'm happy to take this up on the ML again if folks think it's worth a broader discussion.01:08
markvoelker(feel free to say "yes, do that Mark!" or "No, don't do that Mark!" now folks =p)01:09
hogepodgeYes, take it to the mailing list Mark! :-D01:10
rockygI know someHuawei folks have attended the later meetings.  I don't know if they spoke up, though ;-)01:10
*** amotoki has joined #openstack-meeting-401:10
markvoelkerhogepodge, rockyg: duly noted.01:10
markvoelkerOk, the other meeting thing we had to talk about was separating out capabilities meetings again since we've spent approximately zero time on that so far in Flag cycle meetings.01:10
markvoelkerI think there's no real opposition to doing this (speak up if there is), so I'll put something out on the ML.01:11
markvoelkerWE're going to talk about capabilities scoring a bit more later in today's meeting, so I suggest we move on.01:11
markvoelker#action: markvoelker to start ML discussion meeting times and capabilities meeting breakout01:12
markvoelker#topic midcycle agenda01:12
*** openstack changes topic to "midcycle agenda (Meeting topic: defcore)"01:12
markvoelker#link https://etherpad.openstack.org/p/DefCoreFlag.MidCycle Midcycle agenda (tentative)01:12
markvoelkerThose of you who expressed interest in helping plan the midcycle got together last week to frame up a tentative agenda, which is in the etherpad above01:13
markvoelkerOne note:01:13
markvoelkersince then we've spoken to the Neutron and Nova PTL's and they've agreed to attend01:13
markvoelkerBut the timeslot we had doesn't work for them (one is in the UK, one is in Minnesota for what it's worth)01:13
rockygwaht about glance?01:13
markvoelkerThey're available on the morning of the first day, so we'll be moving the networking discussion to then01:14
rockygOK by me.01:14
markvoelkerrockyg: good question.  hogepodge, you were going to reach out to Nikhil?01:14
hogepodgemarkvoelker: yes, I haven't yet. I'll add it to my todo for tomorrow.01:14
markvoelkerFWIW, the Nova PTL said he'd be interested in doing that right after the networking discussion.01:15
markvoelkerhogepodge: ok, thanks01:15
rockygHe'll be in Virginia, so if we need him with the nova ptl, it's a bit easier, maybe.01:15
markvoelker#action: hogepodge to reach out to Glance PTL about remoting in to midcycle on the morning of the 29th01:15
markvoelkerWe also need to settle on a remote attendance mechanism and get that set up (Google Hangout/Join.me/whatever)01:16
markvoelkerBut that's not particularly urgent.01:16
markvoelkerI'll give myself an AI to work out the mechanics with our esteemed chairs and get the final schedule published so folks can plan.01:17
markvoelker#action markvoelker to work with zehicle, eglute, hogepodge to finalize remote attendance details and agenda once we hear from Glance PTL01:17
markvoelkerAny other midcycle stuff we need to talk about?01:17
hogepodgeIBM may have a sophisticated system in place. Do you know catherineD?01:17
rockygMaybe.  Hotels nearby?01:18
hogepodgeJust a reminder that the board meeting is the day before01:18
catherineDhogepodge: you will be connected to IBMVisitor wireless network ..01:18
rockygLike within walking distance?01:18
markvoelkerrockyg: I'm staying at Aloft which is basically across the street.01:18
rockygcool.  How's that mesh with the board meeting location?01:18
hogepodgeI'll be looking for an AirBnB, and maybe the Aloft since I'll be there for the entire week.01:19
*** sdake_ has joined #openstack-meeting-401:19
rockygAnd, IBM might need pre-registration or picture ID.  Only an issue for non-flyers01:19
markvoelkerrockyg: not great but not horrible I think?  I won't be in town in time for the Board meeting so I didn't take that into account.01:19
rockygThanks01:20
markvoelkerrockyg: yeah, I think vince was going to send out a note with whatever was needed.01:20
markvoelkerOk, anything else on midcycle?01:20
catherineDrockyg: markvoelker:  hogepodge:  do you all leave on Thursday?01:20
vincebWe will need a list of people that are in attendance so that I can enter them in to the system01:20
hogepodgeI leave early Friday morning01:20
markvoelkercatherineD: I'm flying out early Friday too.01:20
vincebYou all will need picture IDs to show to security for temporary badges.01:21
catherineDoh if that is the case I should leave Friday also .... Thanks ..01:21
*** sdake has quit IRC01:21
*** armax has quit IRC01:21
markvoelkervinceb: Just names?  We could use the etherpad for that perhaps?01:21
*** galstrom_zzz is now known as galstrom01:21
rockygI think I'm Friday, am, too.01:21
markvoelkeror whatever is easiest for you...01:21
vincebmarkvoelker: Just names and you can email me a list or we can put them in etherpad.  Either way works for me01:22
markvoelkervinceb: ok, thanks.  And so:01:22
markvoelker#action everyone If you're coming to the midcycle, please add your name to https://etherpad.openstack.org/p/DefCoreFlag.MidCycle01:23
vincebAs for accomodations for those that are travelling.  The IBM address is 11501 Burnet Rd.  Austin, TX01:23
vincebYou should be able to find plenty of accomodations near by.01:24
markvoelkerAnd in case anyone forgets, that address is also in the etherpad. =)01:24
markvoelkerOk, anything else on midcycle?01:25
markvoelker#topic Review backlog01:25
*** openstack changes topic to "Review backlog (Meeting topic: defcore)"01:25
markvoelkerWe have a bunch of reviews in the queue that have been sitting around for a while.01:26
*** fitoduarte has joined #openstack-meeting-401:26
markvoelkerWe can spend some time on these at the midcycle if necessary, but many of them seem like they're low-hanging fruit that we could easily clear off the plate before then.01:26
markvoelker(and thus free up more time for other stuff)01:27
markvoelkerI've taken a stab at bucketizing them in the etherpad for today's meeting: https://etherpad.openstack.org/p/DefCoreFlag.701:27
rockygYeah, I did two in the time I connected to the meeting and its start01:27
markvoelkerI figured I'd bargain a little tonight. =)  If we move on to the last item on the agenda for tonight, we'll probably finish early.01:29
markvoelkerSo if we do that, would folks be willing to hang around and use the extra time to review the first 10 or so on the list?  Those should all be pretty low-hanging fruitish I think.01:29
markvoelkerSo probably an easy way to slice the backlog in half before the hour is out.01:29
markvoelkerSound good?01:30
rockygWorks for me.01:30
* markvoelker sits quietly hoping for more positive acknowledgements01:31
markvoelkerPretty please? =)01:31
vincebI have to drop.  You all have a good day/evening.01:31
markvoelkervinceb: thanks, you too01:31
catherineDmarkvoelker: works for me too01:31
hurricanerixworks for me as well01:32
* markvoelker looks in hogepodge's direction although he's probably the submitter on some of these and has reviewed others already01:32
*** vinceb has quit IRC01:32
markvoelkerExcellent!  I'll count that as a win.  Ok, moving on then....01:32
markvoelker#topic Capabilities review01:32
*** openstack changes topic to "Capabilities review (Meeting topic: defcore)"01:32
rockygI'd like to discuss two that are related.  The glance ones, https://review.openstack.org/#/c/189867/ and https://review.openstack.org/#/c/196154/01:33
rockygOops.  Sorry.  Jumped the gun...01:33
markvoelkerrockyg: want to leave your comments in gerrit and we'll discuss at the end of the meeting if there's time?01:33
*** DericHorn-HP_ has joined #openstack-meeting-401:33
rockygYup.  Just wondering if they might really be the same thing and should be merged or something01:34
markvoelkerWe've very briefly discussed capabilities scoring a little bit on the tail end of previous meetings, and it'll be on the agenda at the midcycle too01:34
*** DericHorn-HP_ has quit IRC01:34
markvoelkerBut I think there's a little pre-work we need to do before then01:34
*** DericHorn-HP has quit IRC01:34
*** jasondotstar has joined #openstack-meeting-401:35
markvoelkerIn a nutshell, I think we need to split up the work of identifying candidates to addition to the next Guideline.  There's just no way we have enough bandwidth to do it all in meetings.01:35
markvoelkerSo, I'd like to see if there are folks interested in working on particular projects.  I'm already working on networking, so I'm happy to tackle Neutron/Nova.01:36
markvoelkerBasically you just need to identify candidate capabilities that you think are strong enough canddiates to include in a future spec to have a discussion about.01:36
markvoelkerPreferably you consult with the PTL and/or technical contributors.01:37
markvoelkerThen once we decide on a fomrat, you can post them to gerrit for folks to review.  We'll use meeting time for ones that there's not consensus on.01:37
markvoelkerGenerally make sense?01:38
markvoelkerIf we can at least decide on owners before Austin, we'll have a nice head start.01:38
rockygso we have nova, neutron, cinder, keystone.. what else?01:38
markvoelker(or co-owners....nothing says you have to do it alone)01:38
rockygOh, swift01:38
markvoelkerrockyg: I put a list in the etherpad.01:38
rockygThanks!01:38
markvoelkerIt's not all of the components in the last integrated release, but it's most of the ones that are widely deployed in the last user survey.01:39
hurricanerixIf there is Swift stuff, I can help with that if needed since I already contribute to it.01:39
hogepodgeI'd like to note that we had an error crop up in the keystond capabilities and components01:39
rockygI think we can count glance out until they come to some agreement with nova and themselves01:39
hogepodgeIt's not a required component in 2015.05, but has a required capability.01:40
markvoelkerAnd to be clear: you're not signing up for work that has to be done immediately.  We're obliged to complete the scoring by September 27th according to the 2015A process doc.01:40
markvoelkerhurricanerix: excellent!01:40
hogepodge#link http://lists.openstack.org/pipermail/defcore-committee/2015-July/000891.html01:40
*** ivar-laz_ has joined #openstack-meeting-401:40
markvoelkerhogepodge: duly noted, can I sign you up to work on keystone again this time around?  You did that last time and are well familiar with it I believe. =)01:41
* markvoelker isn't buttering hogepodge up....nope, not at all01:41
hogepodgeyes, although there isn't much there in terms of non-admin api01:41
rockygI would go for cinder, but I've got booth duty at OSCon :P01:41
hogepodgeptl might have some minor changes01:41
markvoelkerrockyg: OSCON shouldn't be a problem.  You have months before it all needs to be done (but the sooner the better)01:42
rockygOh.  then count me in.  I've got a sorta working relationship with Mike Perez01:42
markvoelkerrockyg: thanks!01:42
markvoelkerI can take Nova as well I suppose, since I'm talking with them about networking stuff anyway....01:43
markvoelkerAnyone for Glance, Heat, Ceilometer, other?01:43
catherineDI can take Heat01:44
hogepodgeI'll do glance01:44
*** ivar-lazzaro has quit IRC01:44
markvoelkerthank you catherineD, hogepodge01:44
rockygmaybe some morning person will sign up for ceilometer :_)01:44
*** ivar-laz_ has quit IRC01:44
*** bitblt has quit IRC01:45
markvoelkerCeilometer anyone?  I know some of the ceilometer devs, but nova and neutron seem like they're going to be mighty time consuming already....01:45
markvoelkerOk, we'll table that one for now and ask for volunteers again later....we're missing some folks tonight so still able baodies at hand.01:46
rockygPut it in the meeting summary and ask for volunteers in it.  A morning cycle person might volunteer.01:46
catherineDSo we will use the Capability names from https://docs.google.com/spreadsheets/d/15Fkt2n95WPPe7CYH-0WIKz3dhMeW3FW2gl5aSlamEeY/edit?pli=1#gid=561264013?01:47
markvoelkercatherineD: that's a fine starting point, yes.01:48
markvoelkerOne other note on capabilities: VanL and I were supposed to try to meet last week before he went on PTO to discuss scoring mechanisms, but couldn't work out a time before the holiday.01:48
*** Sukhdev has quit IRC01:48
markvoelkerI'll be circling back with him next when when he's back01:48
markvoelkerSo look for a note from one or both of us on the ML with a proposed mechanism after then.01:48
*** sigmavirus24_awa is now known as sigmavirus2401:49
markvoelker#link https://docs.google.com/spreadsheets/d/15Fkt2n95WPPe7CYH-0WIKz3dhMeW3FW2gl5aSlamEeY/edit?pli=1#gid=561264013? capability names01:49
markvoelkerAnything else on this?01:49
markvoelker#topic open floor01:50
*** openstack changes topic to "open floor (Meeting topic: defcore)"01:50
markvoelkerAnything else anyone wants to bring up tonight before we adjourn to go review patches?01:50
markvoelkerGoing once...01:51
catherineDLet's review patches ..01:51
markvoelkercatherineD: sold!01:51
markvoelker#endmeeting01:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:51
openstackMeeting ended Thu Jul  9 01:51:39 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-07-09-01.00.html01:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-07-09-01.00.txt01:51
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-07-09-01.00.log.html01:51
*** rockyg has quit IRC01:53
*** carl_baldwin has quit IRC01:58
*** sdake_ has quit IRC02:07
*** crinkle has quit IRC02:08
*** Hunner has quit IRC02:08
*** puranamr has quit IRC02:09
*** galstrom is now known as galstrom_zzz02:10
*** yamahata has quit IRC02:10
*** Sukhdev has joined #openstack-meeting-402:11
*** sdake has joined #openstack-meeting-402:15
*** crinkle has joined #openstack-meeting-402:16
*** sigmavirus24 is now known as sigmavirus24_awa02:17
*** harshs has quit IRC02:18
*** Sukhdev has quit IRC02:20
*** Hunner has joined #openstack-meeting-402:23
*** sbalukoff has quit IRC02:26
*** banix has quit IRC02:32
*** yamamoto has joined #openstack-meeting-402:32
*** banix has joined #openstack-meeting-402:38
*** galstrom_zzz is now known as galstrom02:48
*** asselin_ has joined #openstack-meeting-402:48
*** smccully has quit IRC02:51
*** smccully has joined #openstack-meeting-402:52
*** VW_ has joined #openstack-meeting-402:57
*** VW_ has quit IRC03:04
*** VW_ has joined #openstack-meeting-403:05
*** puranamr has joined #openstack-meeting-403:08
*** puranamr has quit IRC03:08
*** VW_ has quit IRC03:10
*** Hunner has quit IRC03:14
*** armax has joined #openstack-meeting-403:16
*** banix has quit IRC03:17
*** jwagner is now known as jwagner_away03:23
*** banix has joined #openstack-meeting-403:29
*** amotoki has quit IRC03:37
*** jasondotstar has quit IRC03:37
*** asselin__ has joined #openstack-meeting-403:39
*** asselin_ has quit IRC03:43
*** yamamoto has quit IRC03:45
*** dims_ has joined #openstack-meeting-403:46
*** dims_ has quit IRC03:46
*** dims_ has joined #openstack-meeting-403:46
*** yamamoto has joined #openstack-meeting-403:51
*** amotoki has joined #openstack-meeting-403:51
*** vishwanathj has quit IRC04:02
*** sbalukoff has joined #openstack-meeting-404:03
*** vishwanathj has joined #openstack-meeting-404:03
*** vishwana_ has joined #openstack-meeting-404:07
*** galstrom is now known as galstrom_zzz04:08
*** markvoelker has quit IRC04:08
*** vishwanathj has quit IRC04:09
*** yamamoto has quit IRC04:12
*** dims_ has quit IRC04:14
*** dims has joined #openstack-meeting-404:15
*** amotoki has quit IRC04:17
*** dims has quit IRC04:20
*** banix has quit IRC04:22
*** amotoki has joined #openstack-meeting-404:23
*** Hunner has joined #openstack-meeting-404:28
*** banix has joined #openstack-meeting-404:30
*** banix has quit IRC04:32
*** amotoki has quit IRC04:33
*** banix has joined #openstack-meeting-404:33
*** watanabe_isao has joined #openstack-meeting-404:39
*** amotoki has joined #openstack-meeting-404:43
*** sdake has quit IRC04:45
*** banix has quit IRC04:48
*** lazy_prince has joined #openstack-meeting-404:54
*** dims has joined #openstack-meeting-405:01
*** dims_ has joined #openstack-meeting-405:02
*** harshs has joined #openstack-meeting-405:03
*** dims has quit IRC05:06
*** yamamoto has joined #openstack-meeting-405:10
*** dims_ has quit IRC05:14
*** nkrinner has joined #openstack-meeting-405:16
*** numan has joined #openstack-meeting-405:19
*** Sukhdev has joined #openstack-meeting-405:25
*** irenab has joined #openstack-meeting-405:29
*** spredzy|afk is now known as spredzy05:31
*** harshs has quit IRC05:44
*** xingchao has joined #openstack-meeting-405:45
*** ig0r_ has joined #openstack-meeting-405:51
*** ig0r__ has quit IRC05:55
*** fitoduarte has quit IRC05:57
*** markvoelker has joined #openstack-meeting-406:00
*** sdake has joined #openstack-meeting-406:03
*** markvoelker has quit IRC06:04
*** davidlenwell has quit IRC06:06
*** jpekkari has joined #openstack-meeting-406:07
*** Naohiro has joined #openstack-meeting-406:07
*** davidlenwell has joined #openstack-meeting-406:08
*** ajayaa has joined #openstack-meeting-406:12
*** fitoduarte has joined #openstack-meeting-406:15
*** dims has joined #openstack-meeting-406:15
*** xingchao has quit IRC06:20
*** fitoduarte has quit IRC06:20
*** fitoduarte has joined #openstack-meeting-406:20
*** dims has quit IRC06:20
*** Naohiro has quit IRC06:24
*** adduarte has joined #openstack-meeting-406:25
*** fitoduarte has quit IRC06:26
*** fitoduarte has joined #openstack-meeting-406:29
*** adduarte has quit IRC06:31
*** radek__ has joined #openstack-meeting-406:31
*** xingchao has joined #openstack-meeting-406:37
*** yamahata has joined #openstack-meeting-406:57
*** armax has quit IRC07:00
*** jpekkari has quit IRC07:01
*** sdake has quit IRC07:03
*** belmoreira has joined #openstack-meeting-407:15
*** tobe has joined #openstack-meeting-407:18
*** belmoreira has quit IRC07:21
*** Sukhdev has quit IRC07:25
*** belmoreira has joined #openstack-meeting-407:28
*** kumar has joined #openstack-meeting-407:37
*** smccully has quit IRC07:39
*** Sukhdev has joined #openstack-meeting-407:46
*** amotoki_ has joined #openstack-meeting-407:47
*** amotoki has quit IRC07:49
*** kumar has quit IRC07:51
*** jmccarthy has left #openstack-meeting-407:51
*** yamahata has quit IRC07:51
*** yamamoto has quit IRC07:52
*** markvoelker has joined #openstack-meeting-408:01
*** Sukhdev has quit IRC08:02
*** xingchao has quit IRC08:02
*** jasondotstar has joined #openstack-meeting-408:04
*** heha has joined #openstack-meeting-408:05
*** heha has quit IRC08:06
*** kobis has joined #openstack-meeting-408:06
*** markvoelker has quit IRC08:06
*** yamamoto has joined #openstack-meeting-408:07
*** qwebirc55410 has joined #openstack-meeting-408:12
*** qwebirc55410 has left #openstack-meeting-408:13
*** dims has joined #openstack-meeting-408:16
*** coldiso_ has quit IRC08:19
*** dims has quit IRC08:21
*** jasondotstar has quit IRC08:29
*** xingchao has joined #openstack-meeting-408:37
*** watanabe_isao has quit IRC08:43
*** ctlaugh_ has quit IRC08:47
*** jasondotstar has joined #openstack-meeting-408:53
*** ctlaugh_ has joined #openstack-meeting-409:01
*** amotoki_ has quit IRC09:02
*** xingchao has quit IRC09:28
*** yamamoto has quit IRC09:32
*** coldiso has joined #openstack-meeting-409:34
*** jpekkari has joined #openstack-meeting-409:53
*** markvoelker has joined #openstack-meeting-410:02
*** radek__ has quit IRC10:05
*** markvoelker has quit IRC10:06
*** radek__ has joined #openstack-meeting-410:07
*** dims has joined #openstack-meeting-410:17
*** dims has quit IRC10:21
*** kevsi_ has quit IRC10:27
*** sdake has joined #openstack-meeting-410:45
*** sdake_ has joined #openstack-meeting-410:46
*** sdake has quit IRC10:50
*** cdelatte has quit IRC11:16
*** jpekkari has quit IRC11:17
*** jpekkari has joined #openstack-meeting-411:32
*** markvoelker has joined #openstack-meeting-411:33
*** sdake_ has quit IRC11:33
*** 32NACCGVG has joined #openstack-meeting-411:36
*** spredzy is now known as spredzy|afk11:36
*** krykowski has joined #openstack-meeting-411:37
*** markvoelker has quit IRC11:37
*** sdake has joined #openstack-meeting-411:42
*** jpekkari has quit IRC11:46
*** igordcard_ has quit IRC11:46
*** tobe has quit IRC11:48
*** sdake_ has joined #openstack-meeting-411:56
*** sdake has quit IRC12:00
*** delatte has joined #openstack-meeting-412:00
*** 32NACCGVG has quit IRC12:00
*** zehicle has quit IRC12:04
*** markvoelker has joined #openstack-meeting-412:12
*** dims has joined #openstack-meeting-412:17
*** dims has quit IRC12:22
*** bknudson has quit IRC12:26
*** sdake has joined #openstack-meeting-412:28
*** sdake_ has quit IRC12:31
*** jasondotstar has quit IRC12:38
*** ajayaa has quit IRC12:38
*** dims has joined #openstack-meeting-412:40
*** bknudson has joined #openstack-meeting-412:42
*** klamath has joined #openstack-meeting-412:48
*** klamath has quit IRC12:49
*** pserebryakov has joined #openstack-meeting-412:49
*** klamath has joined #openstack-meeting-412:49
*** VW_ has joined #openstack-meeting-412:50
*** numan has quit IRC12:55
*** amotoki has joined #openstack-meeting-412:56
*** jasondotstar has joined #openstack-meeting-412:58
*** VW_ has quit IRC13:02
*** VW_ has joined #openstack-meeting-413:02
*** VW_ has quit IRC13:07
*** radez_g0n3 is now known as radez13:08
*** amotoki has quit IRC13:09
*** jckasper has quit IRC13:12
*** puranamr has joined #openstack-meeting-413:16
*** amotoki has joined #openstack-meeting-413:16
*** singlethink has joined #openstack-meeting-413:21
*** amotoki has quit IRC13:28
*** amotoki_ has joined #openstack-meeting-413:28
*** VW_ has joined #openstack-meeting-413:28
*** singleth_ has joined #openstack-meeting-413:29
*** singlethink has quit IRC13:33
*** ajayaa has joined #openstack-meeting-413:33
*** TheIntern has joined #openstack-meeting-413:42
*** irenab has quit IRC13:42
*** puranamr has quit IRC13:45
*** sigmavirus24_awa is now known as sigmavirus2413:47
*** stevelle has joined #openstack-meeting-413:51
*** bpoulos has joined #openstack-meeting-413:51
*** lakshmiS has joined #openstack-meeting-413:51
*** TravT_away has joined #openstack-meeting-413:52
*** banix has joined #openstack-meeting-413:52
*** jckasper has joined #openstack-meeting-413:55
*** dshakhray has joined #openstack-meeting-413:55
sigmavirus24o/ nikhil_k13:56
nikhil_kCourtesy meeting reminder: ativelkov, cpallares, esheffield, flaper87, flwang1, hemanthm, ivasilevskaya, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, zhiyan, pkoniszewski, krykowski, ajayaa, GB21, bpoulos, harshs, abhishekk13:56
* sigmavirus24 dances13:57
* kragniz prances13:57
*** abhishekk has joined #openstack-meeting-413:57
* SamYaple feels left out13:58
*** amotoki has joined #openstack-meeting-413:58
sigmavirus24I'm just in a good mood13:59
sigmavirus24sorry13:59
nikhil_k#startmeeting Glance14:00
openstackMeeting started Thu Jul  9 14:00:02 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: Glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
nikhil_k#topic agenda and roll call14:00
*** openstack changes topic to "agenda and roll call (Meeting topic: Glance)"14:00
nikhil_k#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
*** pserebryakov has quit IRC14:00
rosmaitao/14:00
abhishekko/14:00
bpouloso/14:00
nikhil_kLet's see who is around14:00
mfedosino/14:00
krykowskio/14:00
lakshmiSo/14:01
TravT_awayo/14:01
sigmavirus24o/14:01
*** TravT_away is now known as TravT14:01
sigmavirus24kragniz: you around?14:01
dshakhrayo/14:01
kragnizo/14:01
*** amotoki_ has quit IRC14:01
kragnizsigmavirus24: aye aye14:01
sigmavirus24:D14:01
nikhil_kGreat turnout!14:01
nikhil_kLet's get started14:01
nikhil_k#topic Updates14:02
*** openstack changes topic to "Updates (Meeting topic: Glance)"14:02
*** aventerav has joined #openstack-meeting-414:02
nikhil_k#info Artifacts sub-team meeting update14:02
*** aventerav has quit IRC14:02
nikhil_kWe had a decent discussion. ativelkov was working on some oslo-vo changes.14:02
*** aventerav has joined #openstack-meeting-414:03
mfedosinhi, Alex is not here, but I suppose he is still working on oslo.vo :)14:03
nikhil_kAPI evolution is in progress and needs to be discussed further with the WG.14:03
*** amotoki has quit IRC14:03
krykowskidoesn't he need any help on oslo.vo? :)14:03
nikhil_kI guess Alex is working on the summary14:03
mfedosinwe started to work on stable api yesterday14:03
nikhil_kcool14:03
mfedosinkrykowski, he said that his changes break nova14:04
mfedosinand it's not easy to fix because it requires a lot of work on the nova side14:04
nikhil_kalso, mfedosin is working on the client.14:05
mfedosinso Alex finds ways how to workaround that14:05
jokke_o/14:05
sabario/14:05
nikhil_kThe question raised was whether to move ahead with client before the API stabilizes or after14:05
krykowskimfedosin, cool, if any help needed I'm in here ;)14:05
mfedosinkrykowski, thanks14:06
*** s3wong has joined #openstack-meeting-414:06
jokke_nikhil_k: I'd say this is brilliant opportunity to utilize feature branch on client and go parallel for a while14:06
jokke_releasing from master and having the artifact stuff following on feature branch14:07
mfedosinI think we can merge the existing code and if api changes we will change the client code too14:07
nikhil_kumm, what other need exist for feature branch jokke_ ?14:07
jokke_nikhil_k: the branch needs to be created14:07
mfedosinjokke_, hmm, good idea, btw14:07
jokke_nikhil_k: then obviously if we want CIs running tests they need to be configured14:07
nikhil_kmfedosin: there are some other factors like the semver versioning of the client API14:07
nikhil_kmfedosin: if it's gunna change we shouldn't add it to master14:08
nikhil_kjokke_: makes sense14:08
nikhil_kI doubt it we should start the CI before API is fixed14:08
jokke_#link http://docs.openstack.org/infra/manual/drivers.html#feature-branches14:08
nikhil_kthe client question also applies to tempest changes14:09
nikhil_kWe are running behind14:09
mfedosinI strongly agree with jokke_'s suggestion14:09
*** yamahata has joined #openstack-meeting-414:10
nikhil_kLet's move on for now. We can continue next week on this14:10
jokke_that would make the testing bit easier while yest it will have bit of maintenance overhead with rebases to master14:10
nikhil_k#info Drivers' team meeting update14:10
sigmavirus24+1 jokke_14:10
nikhil_kjokke_: yeah14:10
nikhil_kFor the drivers' meeting, we chatted a bit more on the drivers' team evolution and the specs process14:11
nikhil_kI guess people voted on Stuart to be added to the team, given he wants to and has time14:11
nikhil_kOne more thing was we don't have specs merged. This process needs some change and documentation.14:12
nikhil_kAlso, Liberty is unlikely to have many specs merged as our focus is stability, support of v2 in Nova as possible given we match their constraints14:13
nikhil_kAnd we need to have Artifacts in a state that's acceptable to the community - that may mean moving the API out of the EXPERIMENTAL mode14:13
nikhil_kI guess the first thing to cover would be finding the specs that are likely to be merged in Liberty and are not in priority.14:15
nikhil_kFox example: I mentioned to the person who was interested in impl quotas that the feature seems rather difficult even for L314:15
sigmavirus24nikhil_k: agreed on that14:16
sigmavirus24personally I hope to have some time soon to review bpoulos's work on image signing and encryption. we said at the summit we wanted to pull that in14:17
nikhil_kyeah, I would like to see that one through. bpoulos , sigmavirus2414:17
*** smccully has joined #openstack-meeting-414:17
bpoulossigmavirus24: I would appreciate that14:17
sigmavirus24bpoulos: I hope to rope in reaperhulk too14:18
sigmavirus24(who was at your session standing over to your right against the wall)14:18
bpoulossigmavirus24: great, yeah, I've met him before14:18
* flaper87 kinda late14:19
nikhil_kLet's move on for now. We can chat more if needed in open discussion14:19
nikhil_k#topic M-Release name14:19
*** openstack changes topic to "M-Release name (Meeting topic: Glance)"14:19
nikhil_kI see kragniz updated the etherpad?14:20
*** pbourke has quit IRC14:20
nikhil_kwhat's more likely than Meiji (明治) ?14:20
kragnizfrom the ML thread, it looks like another name will be picked14:20
*** pbourke has joined #openstack-meeting-414:20
nikhil_kthanks14:21
nikhil_k#topic Return request ID to caller14:21
*** openstack changes topic to "Return request ID to caller (Meeting topic: Glance)"14:21
jokke_Meiji had apparently some minority target issues ... normal open OpenStack communication principles followed and none of the reasoning was told14:21
nikhil_k:)14:21
flaper87That name changed14:21
sigmavirus24jokke_: the reasoning was explained in the thread that asked we not use it14:22
flaper87sorry, lag14:22
flaper87I think it's fine now14:22
sigmavirus24flaper87: you should be sorry =P14:22
flaper87sigmavirus24: :D14:22
*** s3wong has quit IRC14:22
*** s3wong has joined #openstack-meeting-414:23
nikhil_kWe had some discussion on the Return request ID proposal in the CPL meeting.14:23
nikhil_kThe proposal is being reworked to impl return of obj (it's WIP)14:23
abhishekknikhil_k: yes, I am working on POC for solution provided by lifeless14:23
nikhil_k#link http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-07-07-21.01.log.html#l-5814:24
abhishekk#link https://review.openstack.org/15650814:24
nikhil_kThat one seems interesting and was hoping to get more feedback based on the use case lifeless described (from folks here)14:24
nikhil_kmay be there are more return val expected than req IDs14:25
nikhil_kinput at this point would be nice14:25
abhishekknikhil_k: most probably in next week CPL meeting i will come up with code14:25
nikhil_kabhishekk: thanks14:25
nikhil_k#topic Travel Support program14:25
*** openstack changes topic to "Travel Support program (Meeting topic: Glance)"14:25
sigmavirus24I'd like to see the POC before weighing in. Lifeless' suggestion makes sense14:25
nikhil_k#info for awareness https://wiki.openstack.org/wiki/Travel_Support_Program14:25
nikhil_kThose who want to travel to Tokyo, this is a nice opportunity to get funding outside of the regular corporate channels14:26
*** s3wong has quit IRC14:26
*** jwagner_away is now known as jwagner14:26
nikhil_ksigmavirus24: thanks14:27
*** s3wong has joined #openstack-meeting-414:27
nikhil_k#topic Rolling upgrade  (krykowski)14:27
*** openstack changes topic to "Rolling upgrade (krykowski) (Meeting topic: Glance)"14:27
*** svg has left #openstack-meeting-414:27
krykowskithe first question is if we are aware of any incoming issues related to upgrading Glance with no downtime between releases, e.g. Kilo -> Liberty?14:27
krykowskias we are api-oriented (which is stateless), we do not provide backwards incompatible changes and as I know we do not use internal rpc communication between services we should be free of issues when upgrading Glance to newer version. is that correct, or have missed something?14:28
*** jwagner is now known as jwagner_away14:28
nikhil_kkrykowski: I guess the questions here is does oslo.vo support the CRUD style dynamic prop protections?14:28
jokke_have anyone paid any attention lately to make that happen? :P14:29
jokke_I think we need to do API version bump on this cycle again14:29
nikhil_kjokke_: oops, any link?14:29
flaper87jokke_: what changes require it ?14:29
*** amotoki has joined #openstack-meeting-414:29
*** wko has joined #openstack-meeting-414:30
krykowskinikhil_k: what do you mean by CRUD style dynamic prop protections?14:30
* jokke_ tries to find ... just reviewed it like 2 days ago14:30
*** xingchao has joined #openstack-meeting-414:30
nikhil_kkrykowski: we have a possible rpc channel from g-api to g-reg14:30
flaper87jokke_: fwiw, I did mention in a change that approving it would require a version bump, I just don't recall which one14:30
*** jwagner_away is now known as jwagner14:31
*** xingchao has quit IRC14:31
nikhil_kkrykowski: Data consistency when you are allowed to read a subset of metadata and write another subset of the metadata units14:31
flaper87I wonder if we need v.o at all for rolling upgrades in glance14:31
flaper87v.o, afaiu, were originally created to communicate with services like nova-conductor14:31
flaper87which would act as the *only* interface on the database14:32
krykowskinikhil_k: will need to get familiar with the g-reg14:32
flaper87in glance's case, it could either be glance-api and/or glance-registry14:32
nikhil_kwell for offline migrations and static stlye data passing between services14:32
jokke_flaper87: I think we're talking about the same change14:32
flaper87but I don't think we've had backwards incompatible changes in the schema lately14:32
flaper87but I might be wrong there14:33
jokke_there has been also quite a few proposals with APIImacts flying lately, not sure how many of them merged14:33
flaper87mentioning the schema since that's what v.o would help with14:33
*** spredzy|afk is now known as spredzy14:33
nikhil_kIt's not just DB schema that matters afaict14:33
flaper87what I'm trying to say is that, I'd love to see identified what problems we have for rolling upgrades first14:33
jokke_++14:33
flaper87nikhil_k: I know, but that's what v.o would help with14:33
nikhil_kit's the image locations migration as first example14:34
* flaper87 was talking about v.o14:34
flaper87sorry for any confusion14:34
nikhil_koffline migration14:34
*** irenab has joined #openstack-meeting-414:35
nikhil_kas an example: image loc that has creds14:35
nikhil_kand we want to move it to using configs (swift store)14:35
flaper87Can we, as we normally do, identify the issues we have? it'd be really useful to work on a better plan to solve those issues14:35
nikhil_kyep14:35
jokke_so yeah sorry if I was too aggressive on that, but IMO we don't have rolling upgrade per default before someone points out that there is no issues, due to the fact that it's not priority (unfortunately) in our dev process14:36
flaper87nikhil_k: the locations one is a good (and perhaps tough) one14:36
nikhil_kthe spec should ideally have that in the problem it tries to solve14:36
*** xingchao has joined #openstack-meeting-414:36
krykowskisure is, will dig a bit and update the spec with specific issue14:36
flaper87krykowski: thank you. FWIW, I think this is an important effort14:36
nikhil_k++14:37
flaper87I'm happy you are willing to spend time on it14:37
jokke_++14:37
krykowskiflaper87: i'm here to serve you ;)14:37
nikhil_kthanks krykowski . I guess we can revisit this in the later week.14:38
krykowskinikhil_k: yup, thanks for the direction!14:38
nikhil_k#topic Reviews, Bugs and Releases14:38
*** openstack changes topic to "Reviews, Bugs and Releases (Meeting topic: Glance)"14:38
kragnizwe need a new glance_store release for the py34 work14:39
flaper87kragniz: wooooohhhhoooooooooo14:39
nikhil_kkrykowski: lifeless is the POC for that14:39
nikhil_koops, I meant kragniz14:39
kragniznikhil_k: yeah, just bringing it up here14:39
nikhil_kjokke_: was that you on python-glanceclient stable/kilo14:39
jokke_also queued up bunch of stable stuff ... glance_store gotta wait until Cinder gets their client requirements fixed, but glanceclient backports would need some love14:39
nikhil_k?14:40
nikhil_kcool14:40
*** yamahata has quit IRC14:40
jokke_if we merge the few in review atm. I think it would be good cut off to kick a release out of door as well14:41
sigmavirus24kragniz: thanks for bringing that up14:41
*** yamahata has joined #openstack-meeting-414:41
wkoI could really use some core reviews on https://review.openstack.org/#/c/195820/14:42
flaper87wko: hey thanks for raising that but please, wait until the open discussion14:42
*** harshs has joined #openstack-meeting-414:42
*** nkrinner has quit IRC14:42
wkook, sorry14:43
nikhil_kjokke_: any more updates for us?14:43
jokke_nikhil_k: not really ... seems that tests are bringing up .eggs/ so proposed gitignore for them now for all the repos, that's all from me now14:43
nikhil_kcool, thanks14:44
nikhil_k#topic Open Discussion14:44
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"14:44
nikhil_kwko: flaper87 ^14:44
jokke_and obviously, please people when fixing bugs that does not change APIs remeber to mark them backport potential and/or propose backports so we get the stables fixed ;)14:44
*** dims has quit IRC14:45
wkoI could really use some core reviews on https://review.openstack.org/#/c/195820/ :)14:45
jokke_wko: sorry I was eyeing that but it was too databasey for me ;)14:45
flaper87I'll be out starting tomorrow until the 20th. If folks need something from me, this is the right moment14:45
flaper87:D14:45
wkoand a +workflow on https://review.openstack.org/#/c/138612/14:45
jokke_flaper87: the stable reviews ;)14:46
flaper87jokke_: I was doing them on gertty14:46
mfedosinbtw, 200k was today14:46
nikhil_kwko: flaper87 wait, thanks waiting on thespec14:46
flaper87I guess it hasn't synced14:46
mfedosinhttps://review.openstack.org/#/c/200000/14:46
jokke_flaper87: <3 after than you can enjoy your holidays ;)14:47
flaper87jokke_: w0000h0000 :D14:47
jokke_mfedosin: gratz!!!14:47
mfedosindanke :) Darja will finish it today14:48
flaper87nikhil_k: https://review.openstack.org/#/c/154695/ that one could use your +2A (or other vote) when you get a chance14:48
jokke_mfedosin: I'll just -2 that so we can freeze it forever, feel free to repropose ;)14:48
nikhil_kthanks flaper87 . will take a look14:48
mfedosinjokke_, ;) then we will have unhandled exceptions from store forever14:49
jokke_mfedosin: that's a small prize to pay :P14:50
*** dims has joined #openstack-meeting-414:50
nikhil_kIf nothing more, we can conclude the meeting a few mins early.14:51
flaper87that's what I call success14:51
jokke_sounds good ... thanks everyone!14:51
nikhil_k;)14:51
flaper87cheers14:51
nikhil_kThanks all!14:51
nikhil_khave a nice vacay flaper8714:51
kragnizflaper87: have a good holiday!14:51
nikhil_k#endmeeting14:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:52
openstackMeeting ended Thu Jul  9 14:52:03 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-09-14.00.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-09-14.00.txt14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-09-14.00.log.html14:52
flaper87nikhil_k: kragniz grazie14:52
*** armax has joined #openstack-meeting-414:53
*** bpoulos has left #openstack-meeting-414:54
*** kobis has quit IRC14:56
*** carl_baldwin has joined #openstack-meeting-414:56
*** lakshmiS has quit IRC14:56
*** galstrom_zzz is now known as galstrom14:58
*** lakshmiS has joined #openstack-meeting-414:58
*** MarkAtwood has joined #openstack-meeting-414:59
*** dshakhray has quit IRC15:00
*** sjmc7 has joined #openstack-meeting-415:01
nikhil_kTravT: meeting?15:01
*** sdake_ has joined #openstack-meeting-415:01
*** TravT has quit IRC15:03
*** TravT has joined #openstack-meeting-415:04
TravT#startmeeting openstack search15:04
openstackMeeting started Thu Jul  9 15:04:18 2015 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot.15:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: openstack search)"15:04
openstackThe meeting name has been set to 'openstack_search'15:04
nikhil_ko/15:04
lakshmiSo/15:04
TravTAlways fun when your internet drops right at the wrong time15:04
TravTCourtesy meeting reminder: lakshmiS, mclaren, nikhil, rosmaita, sigmavirus24, TravT, krykowski, david-lyle, wko, kragniz, sjmc7, ekarlso15:04
lakshmiSyeah thats what i thought..15:04
sigmavirus24o/15:05
sjmc7o/15:05
*** sdake has quit IRC15:05
kragnizo/15:05
TravThey all15:05
*** markd_ has quit IRC15:05
TravT#topic status updates15:05
*** openstack changes topic to "status updates (Meeting topic: openstack search)"15:05
TravTJust wanted to say Happy one month anniversary to us15:06
rosmaitao/15:06
sjmc7:)15:06
sigmavirus24in which TravT becomes overly attached ptl15:06
TravTJust saw today that exactly a month ago we were voted in as a project.15:06
TravTlol15:06
sigmavirus24uhuh, "Just saw" righttttt ;)15:06
nikhil_k:P15:06
TravTwell, I had to help somebody submit a new governance proposal yesterday15:07
TravTand looked back on mine to help them.15:07
TravT:)15:07
nikhil_ksigmavirus24: I wonder how many moments in a day you are not in a funny mood :)15:07
TravTbut seriously, it did cause me to realize that we've actually come a long ways in a month15:07
nikhil_kin a good way :)15:07
TravTso thanks everybody for your help so far15:07
TravTok, now that tears have been s15:08
TravThed15:08
TravTlet's move on15:08
TravTagenda is here: https://etherpad.openstack.org/p/search-team-meeting-agenda15:08
TravTplease add anything you want to talk about15:08
TravT#topic Midcycle update (TravT)15:08
*** openstack changes topic to "Midcycle update (TravT) (Meeting topic: openstack search)"15:08
TravTSo, we aren't going to have an official one.15:09
sjmc7boo15:09
*** sdake_ has quit IRC15:09
TravTyeah, if we could have worked a shared one with glance and horizon, i think it could have worked.15:09
TravTbut that proved difficult.15:09
TravTsjmc7 and I will be at the horizon one July 21 - 23rd15:10
*** sdake has joined #openstack-meeting-415:10
TravTso, if anybody has any possibility of showing up at that one, we can spend some time on searchlight15:10
TravTi intend on discussing integration with the horizon team there.15:10
nikhil_kI tried to figure out my travel possibility for July 21st week and it's seems very tricky at this point.15:10
nikhil_kit*15:11
TravTbut we still can do some virtual meetup if needed.15:11
sigmavirus24Yeah, my travel freedom isn't exactly great =/15:11
TravTi'd like to keep our traction going.15:11
TravTwe have made good progress.15:11
TravTeven if lots of people are split focus15:11
TravT#topic Cross Project Updates15:12
*** openstack changes topic to "Cross Project Updates (Meeting topic: openstack search)"15:12
TravTI was only able to attend part of it15:12
TravTbut there is some discussion on new API guidelines15:12
TravTif you have time take a look15:12
TravThttp://lists.openstack.org/pipermail/openstack-dev/2015-July/068682.html15:12
*** s3wong has quit IRC15:12
TravTnikhil_k or david-lyle, was there anything else we should share?15:13
nikhil_kumm, we are not going to impl passthrough for any service at this point right?15:14
nikhil_kanyone planning on any idea like htat?15:14
sjmc7passthrough?15:14
nikhil_kuser -> SL -> my_openstack_service ?15:14
TravTi haven't had any thoughts around doing that.15:15
sjmc7ah. no, don't think so. like heat does?15:15
nikhil_kyeah :)15:15
nikhil_kthen nothing from me :)15:15
TravTexcept for keystone authentication (transparent)15:15
*** sambetts has quit IRC15:15
TravTok then on to bug reviews15:15
TravT#topic bugs15:15
*** openstack changes topic to "bugs (Meeting topic: openstack search)"15:15
lakshmiSBug 1470627: Made progress in avoiding conflict with ceilometer notification listner. Will require some changes to ceilometer code too. will be talking with them15:16
openstackbug 1470627 in OpenStack Search (Searchlight) "Searchlight does not receive notification when deployed in same env as Ceilometer" [High,In progress] https://launchpad.net/bugs/1470627 - Assigned to Lakshmi N Sampath (lakshmi-sampath)15:16
TravTlakshmiS: please fill us in15:16
*** sambetts has joined #openstack-meeting-415:17
lakshmiSWas able to read the notification twice from ceilometer and searchlight with some code changes in ceilometer too15:17
sjmc7without creating additional topics?15:17
lakshmiSwill be talking to their team on suggestions to changing their code for listner15:17
lakshmiSyeah on same topics15:17
sjmc7and you're pretty sure that's the right way to go about it?15:18
lakshmiSyeah it feels correct to me. will know more if ceilometer team has any reservations around it15:19
TravTdoes this use pools?15:19
lakshmiSyes15:19
sjmc7ok. i know a bunch of the ceilometer guys in fort collins if you want me (or travis) to talk to them. i'm there in two weeks15:19
lakshmiSsound good. thx15:19
TravTi also have found a workaround that we could suggest to them. i have found it to be pretty effective.15:19
TravTjust kill ceilometer-anotification15:19
sjmc7is it "disable ceilometer" ?:)15:20
TravT:-)15:20
lakshmiSyeah why didnt i think about that ;)15:20
TravTi dunno seems obvious to me15:20
TravTwell, lakshmiS, i think you should take it directly to them.15:20
TravThave they had their weekly meeting yet this week15:20
sjmc7yeah. be great to get this fixed15:20
TravTprobably you should submit a bug or something first to them15:21
lakshmiSyeah that was my plan. will do15:21
TravTand then bring it up.15:21
sjmc7we should parameterize the topic in searchlight, also15:21
sjmc7currently it's hardcoded in each plugin. probably ties in with endre's blueprint about plugin config15:21
david-lyleceilometer is having a virtual sprint today and tomorrow, I believe15:22
david-lyleso no weekly meeting15:22
TravTinteresting.  do you have info on that david-lyle?15:22
TravTmaybe lakshmi could just jump in there15:22
david-lylewill find15:22
*** vishwana_ has quit IRC15:23
lakshmiSthx david-lyle:15:23
*** vishwanathj has joined #openstack-meeting-415:23
TravTlakshmiS, if you have even the beginning of some code that you could submit as work in progress to searchlight and ceilometer15:23
TravTthat would be helpful as well.15:23
lakshmiSyeah will do15:23
david-lylehttp://lists.openstack.org/pipermail/openstack-dev/2015-July/068911.html15:23
TravTmakes it easier to discuss15:23
TravTsjmc7, should we talk more about the topic parameterization now, later, or next meeting?15:24
sjmc7it's not on the agenda, but i think we could agree something pretty quick15:24
TravTlet's circle back then during ekarlo's topic  if he arrives15:25
sjmc7k15:25
lakshmiSTravT: sjmc7: sound like topic parameterization could be included under making plugin configurable file15:25
TravTBug 1469813:15:26
openstackbug 1469813 in OpenStack Search (Searchlight) "Glance images 'Public images do not have members'" [High,In progress] https://launchpad.net/bugs/1469813 - Assigned to Steve McLellan (sjmc7)15:26
sjmc7yeah lakshmiS, endre has a BP for it already15:26
*** puranamr has joined #openstack-meeting-415:26
sjmc7i have a review up for 146981315:26
TravTthis is pretty important15:26
TravTotherwise, no images show up in the index on fresh devstack15:26
sjmc7sigmavirus15:26
sjmc7gah. sigmavirus24 had one comment i addressed15:27
sjmc7needs reviews15:27
sigmavirus24oh I didn't notice that you addressed it15:27
sigmavirus24let me look again15:27
*** puranamr has quit IRC15:27
TravTsjmc7 I just tested it about 30 minutes ago15:27
TravTand it does seem to solve the issue15:27
TravT#link https://review.openstack.org/#/c/196754/15:27
nikhil_kthanks TravT15:27
*** puranamr has joined #openstack-meeting-415:28
TravTok, thanks15:29
TravTBug 1469336:15:29
openstackbug 1469336 in OpenStack Search (Searchlight) "Errors are returned as html" [Undecided,New] https://launchpad.net/bugs/146933615:29
*** harshs has quit IRC15:29
TravTsjmc7 you filed this one and nobody has picked it up15:29
sjmc7i filed this. it's not hugely urgent15:29
sjmc7just looks messy15:29
TravTyeah, i was just looking at it, thinking that we'll want a json response when using it from horizon15:30
sjmc7right15:30
*** dims has quit IRC15:30
sjmc7well, always. we'll never want html responses. it's not a big deal, needs some middleware15:30
TravTso, if anybody can pick it up, please do15:30
TravTany other bugs anybody wants to discuss?15:31
sjmc7yes..15:31
sjmc7oh wait, the notifications one we already did15:31
sjmc7sorry. then no15:31
TravTwe'll wait for sjmc7 to make sure he's sure15:32
TravT:P15:32
*** dims has joined #openstack-meeting-415:32
*** dims has quit IRC15:32
TravT#topic blueprint review15:32
*** openstack changes topic to "blueprint review (Meeting topic: openstack search)"15:32
*** fitoduarte has quit IRC15:32
TravTekarlso, are you here?15:32
*** dims has joined #openstack-meeting-415:33
TravTi think he's usually on his way home at this time of day15:33
TravTso, maybe he'll be on shortly.15:33
TravTsince he added those15:33
*** igordcard_ has joined #openstack-meeting-415:33
TravTsjmc7, looks like you added a few15:33
sjmc7i did15:33
sjmc7nova support15:34
sjmc7https://blueprints.launchpad.net/searchlight/+spec/nova-instances-plugin15:34
sjmc7i have a WIP patch up  (https://review.openstack.org/#/c/198852/)15:35
sjmc7which is a pretty close copy of what we had for the summit demo15:35
sjmc7feedback etc welcome15:35
sjmc7stunned silence NOT welcome15:35
nikhil_k++15:35
TravTrosmaita: nikhil_k:15:36
* sigmavirus24 is stunned into silence15:36
sjmc7nikhil_k, i know you have concerns about versioned objects15:36
* sigmavirus24 leaves as he's no longer welcome15:36
sjmc7i don't know what they are :)15:36
nikhil_kI am to follow up a bit with John and TravT and I discussed to move on it further.15:36
sjmc7come back!!15:36
sjmc7ok15:36
*** harshs has joined #openstack-meeting-415:36
sjmc7i'll get a unit test up for it, but otherwise there's not much more i'm doing on it now15:36
TravTsigmavirus24: you better not leave!15:36
sigmavirus24=P15:36
nikhil_ksigmatroll, there?15:36
nikhil_k:P15:37
sjmc7if there's no more on that one, the other one was https://blueprints.launchpad.net/searchlight/+spec/openstack-client-usage15:37
sjmc7which i filed about 30 minutes ago15:37
nikhil_k:)15:37
TravTwait a sec15:37
nikhil_kthere's push for it15:37
nikhil_kbut I doubt if things are there yet15:37
sjmc7ok. i shall wait15:37
TravTon nova instances, should we look to get work in progress of it in sooner and enhance it?15:37
TravTor wait?15:37
TravTdefinitely needs to be looked at first, of course15:38
sjmc7i'd like to get it in if we can15:38
nikhil_kI don;t mind merging a smaller set of impl15:38
TravTjust wondering what we'll use to decide it is enough to have first merge15:38
nikhil_kCan we list all that we need as a part of that BP?15:39
nikhil_kis this just instances plugin?15:39
sjmc7yeah15:40
nikhil_kI see the notes on summit prototype and was wondering if enhancements expected were along those lines?15:40
sjmc7i want to get the base in first15:40
TravTi think getting a series of patches in is easier to review15:41
sjmc7i can't remember exactly what enhancements we listed but i'd like ot get something that works in, then make it better15:41
TravTi don't want to fall in the trap of massive patches that never merge.15:41
TravTespecially at this stage of the project15:41
sigmavirus24Agreed with TravT15:41
nikhil_kI am curious more about the BP, I like smaller patches15:41
sigmavirus24TravT: it's a good thing david-lyle witnessed our interaction at the summit otherwise people might expect that we'd be the same human being15:42
sjmc7ok. well, give whatever feedback. i'm keen to get this in so i'll make sure i put time aside15:42
TravTlol15:42
sjmc7:D15:42
nikhil_kwhat should be plan for the BP? Entire nova DB or just a couple of tables?15:42
sjmc7just instances15:42
nikhil_kok15:42
sjmc7don't think in terms of tables :)15:42
nikhil_kyeah, then I was on the wrong page15:42
TravTso, then we need another bp for more than instances15:42
nikhil_kall we need is some check on whether this works for cells (which may need some work for initial index or may be notif too)15:43
TravTnikhil_k, uou and rosmaita are more knowledgable about nova, so we need your help on figuring out what all we should do for nova15:43
sjmc7yeah - my nova knowledge is pretty limited15:43
nikhil_kbasically, instances can be great but we need meta and sys meta for the UX team to benefit15:44
nikhil_kespecially if ironic and magnum are to be differentiated15:44
sjmc7i don't know what those are, but i can benefit from instances on their own :)15:44
nikhil_k(that's the first req I know)15:44
sjmc7ok. let's not go too far down this now, but agree that we need more BPs around this15:45
TravTso, i think on current patch we can keep pretty simple, but still get a test up on it and quick look from nikhil_k, others.15:45
nikhil_kcool15:45
TravTok...15:46
TravTrunning out of time15:46
sjmc7i had one more BP15:46
TravTwhat was your other BP in agenda?15:46
sjmc7 https://blueprints.launchpad.net/searchlight/+spec/openstack-client-usage15:46
sjmc7very briefly (again) - the way the listener uses the openstack clients needs some TLC15:47
*** harshs has quit IRC15:47
sjmc7to avoid reauthenticating on every event it caches authorized clients, but i'm sure someone can come up with a neater way to do it15:47
*** daneyon has joined #openstack-meeting-415:48
sigmavirus24sjmc7: I'm sure the keystone team has ideas15:48
sjmc7and i also think that what's there right now will not deal with expired tokens properly. there's a quick fix for it, but there's also probably a nicer approach15:48
nikhil_kuse keystone middleware15:48
TravThow does this relate to the bug15:48
TravTBug 1471878:15:48
openstackbug 1471878 in OpenStack Search (Searchlight) "Service client auth in listener" [Undecided,New] https://launchpad.net/bugs/147187815:48
*** belmoreira has quit IRC15:48
sigmavirus24sjmc7: you should check out mfedosin's work in glance_store right now15:49
sjmc7ah, yes. i thought i'd already filed it15:49
sigmavirus24it looks to be a good lightweight solution15:49
TravTso they are the same?15:49
sigmavirus24goto pypa15:49
TravTsigmarvirus24, do you have a link?15:49
sjmc7not really TravT - the bug is to fix the current code15:49
sjmc7the BP is to reimplement15:49
nikhil_kyeah, that glance_store work seems a bit icky to me15:50
nikhil_khttps://github.com/openstack/keystonemiddleware is usually the best place to use cached tokens15:50
sjmc7remember this isn't re-authing on behalf of a user, but essentially maintaining a long-running admin auth token. the summit demo code caught Unauthorized exceptions and cleared its cached clients15:50
sjmc7the clients don't use keystonemiddle, do they?15:51
nikhil_knot that I know of15:51
sjmc7anyway, this can be discussed in the SL channel, don'tneed to do it here15:51
nikhil_kbut can we wrap?15:51
sjmc7possibly. let's discuss separately after folks have a chance to digest15:52
TravTok, maybe we should come back on this.15:52
sjmc7i'll fix 147878 in the meantime15:52
TravTnot sure ekarlso is back15:52
TravTbut i would like to point out that he got a designate plugin up15:53
sigmavirus24TravT: sorry, let me get that link15:53
sigmavirus24#link https://review.openstack.org/#/c/199049/515:53
TravTthanks sigmavirus2415:54
sjmc7will take a look, thanks15:54
TravTokay, let's get back to the talk on topics15:54
TravTi mean topic parameterization15:54
TravTactually...15:54
TravT#topic open discussion15:55
*** openstack changes topic to "open discussion (Meeting topic: openstack search)"15:55
TravTist before going to that (we can jump to room if needed)15:55
TravTanything else anybody needs to bring up?15:55
TravTI need to mention I'll be out of office next Wednesday, Thursday, Friday.15:55
nikhil_kVacation season15:56
TravTnikhil_k, will you be around to chair the meeting?15:56
nikhil_kTravT: will be and can do :)15:56
TravTthanks.15:56
TravTanything else from anybody?15:56
nikhil_ksjmc7: let's chat on the channel about client reauth possibilites if you've time15:57
sjmc7sure15:57
sjmc7let me fix the currently filed bug first15:57
TravTFYI that nikhil_k and I recorded a PTL webinar on searchlight for the foundation yesterday15:57
sjmc7so you can see what i want to replace15:57
*** banix has quit IRC15:57
TravTthey are supposed to publish those out soon15:57
nikhil_ksjmc7: awesome thanks!15:57
*** b3rnard0 has joined #openstack-meeting-415:57
nikhil_kTravT: yay!15:57
*** Vikram_ has joined #openstack-meeting-415:57
TravThow about we take the parameterization topic over to #openstack-searchlight15:58
nikhil_khopefully they will be out today/tomorrow ish15:58
TravTThanks everybody.  See you in the room15:58
TravT#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Thu Jul  9 15:58:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-09-15.04.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-09-15.04.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-09-15.04.log.html15:58
*** sjmc7 has left #openstack-meeting-415:59
*** lakshmiS has left #openstack-meeting-415:59
*** cloudnull has joined #openstack-meeting-415:59
*** odyssey4me has joined #openstack-meeting-416:01
*** ronr84 has joined #openstack-meeting-416:01
cloudnull#startmeeting OpenStack Ansible Meeting16:01
openstackMeeting started Thu Jul  9 16:01:26 2015 UTC and is due to finish in 60 minutes.  The chair is cloudnull. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:01
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:01
cloudnull#topic Agenda & rollcall16:01
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:01
*** qwebirc82056 has joined #openstack-meeting-416:02
b3rnard0hello16:02
andymccro/16:02
odyssey4meo/16:02
palendaeo/16:02
qwebirc82056good day folks16:02
*** ronr84 has quit IRC16:02
cloudnullhi everybody16:02
*** adityavajjha has joined #openstack-meeting-416:02
*** banix has joined #openstack-meeting-416:02
*** carl_baldwin has quit IRC16:02
serverascodeo/16:03
hughsaundershey16:03
*** bitblt has joined #openstack-meeting-416:03
*** git-harry has joined #openstack-meeting-416:04
qwebirc82056first time tacker joinee here - good to see you all16:04
d34dh0r53o/16:04
cloudnullwelcome qwebirc8205616:04
*** TravT has left #openstack-meeting-416:05
odyssey4mewelcome qwebirc82056 and serverascode :)16:05
cloudnull#topic Review action items from last week16:05
*** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)"16:05
cloudnullodyssey4me to update the specs for federation.16:05
*** dims_ has joined #openstack-meeting-416:05
cloudnulllooks like that was all done16:05
cloudnull#link https://blueprints.launchpad.net/openstack-ansible/+spec/keystone-federation16:06
cloudnullcloudnull we will no longer backport things from master until its been +w / merged into master.16:06
odyssey4meyep, those are done and should be considered final - can we get some final reviews on https://review.openstack.org/194147 ?16:06
cloudnullalso it seems that everyone is following that change16:06
cloudnullyes ^ that should be priority item https://review.openstack.org/#/c/194147/16:07
cloudnull#link https://review.openstack.org/#/c/194147/16:07
odyssey4meand https://review.openstack.org/19425516:07
cloudnull#topic Blueprints16:07
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:07
cloudnullso jumping into the specs / bps16:07
*** wko has quit IRC16:08
cloudnullodyssey4me:  whats your feeling on https://review.openstack.org/#/c/194255/ ?16:08
cloudnulldo we think that we'll have working bits by 11.1.x ?16:08
odyssey4mecloudnull yeah, we have some patches up for review which cover SSL-related stuff which we depend on16:09
odyssey4melet me pick them out for review attention:16:09
cloudnull++16:09
*** dims has quit IRC16:09
*** s3wong has joined #openstack-meeting-416:09
odyssey4me#link: https://review.openstack.org/194474 (keystone SSL support)16:10
odyssey4me#link: https://review.openstack.org/196943 (keystone v3 api usage in the Ansible library)16:10
odyssey4me#link: https://review.openstack.org/199307 (allow 'insecure' use of keystone by everything)16:11
odyssey4me#link: https://review.openstack.org/198957 (ssl offloading to haproxy)16:11
odyssey4meif we can get some attention on those reviews and try to get them merged this week that'd really help16:12
cloudnull+116:12
cloudnullpalendae hughsaunders sigmavirus24 mattt andymccr16:12
sigmavirus24sorry, I'm here16:13
hughsaundersok :)16:13
odyssey4meI think that the haproxy review still needs some attention.16:14
cloudnullabout that one .16:14
cloudnullwhen i looked at it last it was forwarding ssl to the endpoing using tcp16:14
odyssey4megit-harry has raised a good point in https://review.openstack.org/199307 - perhaps the decision of whether to set 'insecure' should be manual? thoughts on that?16:14
cloudnullhave we looked at haproxy 15 with ssl terminiation ?16:15
*** TheIntern has quit IRC16:15
odyssey4mecloudnull https://review.openstack.org/198957 is to use haproxy for ssl offloading, but https://review.openstack.org/194474 still implements ssl at the keystone endpoint as there are use-cases where people want to do both16:15
* cloudnull was looking at that review16:17
odyssey4methe haproxy patch will conflict with the keystone one at the moment, but we'll fix that - so I think that patch needs more work but the keystone one is good to go16:17
cloudnullmy one nit there would be the use of "http://ppa.launchpad.net/vbernat/haproxy-1.5/ubuntu"16:17
cloudnullin the past we've had deployment issues when using ppa's16:17
cloudnullbut i can cover that in the PR16:17
odyssey4mecloudnull yeah, perhaps the decision of using the ppa should be made based on whether there are any ssl endpoints... not use it if it's not needed16:18
cloudnull+1, I'd also not be against simply adding the ability for us to compile / build the package for haproxy.16:19
cloudnullif we deem 1.5 is the way to go16:19
stevelleafter reading the osad manifesto through once or twice that strikes me as not crazy16:19
cloudnull#link https://etherpad.openstack.org/p/openstack-ansible-manifesto16:20
cloudnullwiki:16:20
cloudnull#link https://wiki.openstack.org/wiki/OpenStackAnsible16:20
odyssey4meI have to admit, I haven't been able to read through it properly. :/16:21
cloudnulli figured id wait a couple weeks before i pr to master.16:22
cloudnullfor that reason, theres been a lot going on16:22
cloudnullbut if anyone has a minute to review it please tear it apart.16:22
odyssey4mecloudnull perhaps it should just be pr'd to master and we can edit/discuss in review?16:22
cloudnullmaybe, ill wait a few more days for people to collaborate on the etherpad.16:23
*** fitoduarte has joined #openstack-meeting-416:23
hughsaunderswill have a read16:23
stevelleI'm still doing tiny edits to fix typos and what not16:23
cloudnullthanks stevelle hughsaunders16:23
cloudnullnext on the BP reviews16:24
cloudnull#link https://review.openstack.org/#/c/17306716:24
cloudnullthis is for ceilometer cores please do the needfuls16:24
odyssey4meyep, I've just built it and it's build complete16:24
sigmavirus24odyssey4me: mind if I piggy back my testing off your build?16:24
odyssey4mesigmavirus24 sure, I'll add your keys16:25
sigmavirus24gracias16:25
odyssey4memsg sigmavirus 104.239.228.11816:26
odyssey4mehahaha16:26
odyssey4mewhoops16:26
*** svg has joined #openstack-meeting-416:26
d34dh0r53lulz16:26
*** carl_baldwin has joined #openstack-meeting-416:26
hughsaundersodyssey4me: its ok we didn't see hunter216:27
odyssey4meit's built - I'm not all that familiar with ceilometer so perhaps someone can do some things to make pretty graphs and stuff?16:27
cloudnull#topic Open discussion16:27
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:27
cloudnullshould we move the docs out into their own repo and elect a new core team for docs? - cloudnull16:28
cloudnullwhat do we think ?16:28
odyssey4mecloudnull if we can get a docs repo created in openstack/ then yeah, I think that's a good plan16:28
palendaeIMO no; at least not all docs16:28
andymccrdont think they need their own repo. The docs should pertain only to the os-ad stuff the rest of "how to openstack" is/should already be doc'd.16:28
d34dh0r53I nominate sigmavirus24 for core of docs16:29
palendaeI don't want to see it become more of a "docs is THEIR job" thing16:29
palendaeDocs should be on developers implementing a feature16:29
palendaeAt least part of them16:29
sigmavirus24d34dh0r53: of course16:29
stevelle == palendae16:29
palendaewe're already bad about keeping the docs we have up to date. I think this would just make it worse16:30
odyssey4meyeah, I am inclined to agree - we need to pay more attention to keeping docs up to date with code - and this makes it easier16:30
cloudnullok. so for now, do we say no moving the docs ?16:32
*** Swami has joined #openstack-meeting-416:33
andymccrthat would be my vote!16:33
palendaeFor now, no16:33
palendaeMaybe if it morphs and gets bigger16:33
andymccr(if it really gets that big we are probably doing it wrong)16:33
*** xingchao has quit IRC16:33
palendaeI think we'll still need some stuff documenting the structure and so on for other devs16:33
cloudnulllets try this16:33
palendaebut like andymccr says, that should be small16:33
cloudnull#startvote to move the docs into its own repo16:34
openstackUnable to parse vote topic and options.16:34
odyssey4meI agree with andymccr16:34
palendaeOo, using bot features16:34
sigmavirus24cloudnull: #startvote Should we move the docs into its own repo? Yes, no16:34
cloudnull#startvote to move the docs into its own repo? yes, no16:34
openstackBegin voting on: to move the docs into its own repo? Valid vote options are yes, no.16:34
openstackVote using '#vote OPTION'. Only your last vote counts.16:34
andymccr#vote no16:34
sigmavirus24#vote no16:34
odyssey4me#vote no16:35
*** numan has joined #openstack-meeting-416:35
stevelle#vote no16:35
palendae#vote no16:35
d34dh0r53#vote abstain16:35
openstackd34dh0r53: abstain is not a valid option. Valid options are yes, no.16:35
Apsu#vote pedro16:35
openstackApsu: pedro is not a valid option. Valid options are yes, no.16:35
*** rackertom has joined #openstack-meeting-416:35
odyssey4melol16:35
d34dh0r53damn, no Switzerland for me16:35
cloudnullgood enough for me16:36
sigmavirus24HAW HAW16:36
cloudnull#endvote16:36
d34dh0r53#vote no16:36
openstackVoted on "to move the docs into its own repo?" Results are16:36
openstackno (5): sigmavirus24, palendae, stevelle, odyssey4me, andymccr16:36
Apsud34dh0r53: You abstained anyway in the end.16:36
d34dh0r53FRAUD, I clearly got my vote in before the bell16:36
ApsuTime to recount the hanging chads16:36
cloudnullnext How should we handle the change in OpenStack package version numbers? odyssey4me16:36
cloudnullidk if this is a problem for us16:37
odyssey4meso the two links outline the changes and what they mean16:37
cloudnullpbr should kick out the right version numbers,16:37
odyssey4methis will affect upgrades16:37
cloudnulland we've been seeing this change in the recent master builds. IE http://rpc-repo.rackspace.com/os-releases/master/neutron-7.0.0.0b2.dev158-py2.py3-none-any.whl16:37
odyssey4meif that's the case, then great16:38
odyssey4mebut perhaps an upgrade test can be done to confirm?16:38
cloudnull+116:38
cloudnull#action test upgrading from kilo to liberty (master)16:38
sigmavirus24+116:39
sigmavirus24Would it be a good idea to add greande jobs like upstream uses?16:39
sigmavirus24(or to have jobs that test those upgrade paths)16:39
odyssey4mesigmavirus24 that'd be great16:39
cloudnulli looked at that. those jobs seem to be reserved for os namespaced projects.16:39
* sigmavirus24 wasn't volunteering16:39
stevellesoon cloudnull16:39
sigmavirus24cloudnull: so soon that won't be a problem?16:39
cloudnullas well as the periotic jobs.16:40
sigmavirus24== stevelle16:40
sigmavirus24what about patriotic jobs?16:40
cloudnull++ sigmavirus24 stevelle16:40
sigmavirus24=P16:40
cloudnullpatriotic jobs are once a year and the 4th has passed.16:40
stevellesigmavirus24: that's on your own time, son.16:40
cloudnullso is there anything pressing on the bug side.16:41
cloudnullany wish list items we want to raise ?16:41
cloudnullwe've been smashing the open bugs so great works guys !16:41
cloudnulllittering and ?16:42
andymccrswift multi region reviews are starting to go in as a headsup!16:43
stevelleany mid-cycle events we expect to have folks showing up at?16:43
stevellemight be worth a mention16:43
stevellesuppose that was early, not in open discussion yet16:44
cloudnullwe are stevelle16:44
cloudnullthe ops midcycle is in planning (kinda)16:45
cloudnull#link http://lists.openstack.org/pipermail/openstack-operators/2015-July/007592.html16:45
*** bitblt has quit IRC16:45
cloudnullit'd be great to get some more OSAD people in on that thread16:45
cloudnullfor anyone interested.16:46
cloudnull+1 andymccr16:46
cloudnullalso the kolla guys are looking into some of our modules to use within their, IE SamYaple, we might want to see if we can help out. it'd be a good collaborative effort . http://lists.openstack.org/pipermail/openstack-dev/2015-July/069014.html16:49
cloudnull*their project16:49
cloudnulland or participating in the thread, if anyone is interested.16:49
cloudnullthats all we have on the agenda today . im inclinded to end early if theres nothing else.16:50
palendaeI don't have anything16:51
* sigmavirus24 objects to ending early for no particular reason16:51
*** lazy_prince has quit IRC16:51
d34dh0r53#vote yes16:51
* d34dh0r53 is disenfranchised16:51
cloudnull#noted sigmavirus24 objects16:51
cloudnull#endmeeting16:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:52
openstackMeeting ended Thu Jul  9 16:52:06 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-09-16.01.html16:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-09-16.01.txt16:52
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-09-16.01.log.html16:52
cloudnullthanks everyone16:52
*** odyssey4me has left #openstack-meeting-416:53
*** sballe has joined #openstack-meeting-416:55
*** bouthors has joined #openstack-meeting-416:56
*** rackertom has left #openstack-meeting-416:57
*** Mohankumar_ has joined #openstack-meeting-416:57
*** sbalukoff has quit IRC16:58
*** Brian__ has joined #openstack-meeting-416:58
*** asselin_ has joined #openstack-meeting-416:58
*** LouisF has joined #openstack-meeting-416:58
*** cathy_ has joined #openstack-meeting-416:59
cathy_#startmeeting service_chaining17:00
openstackMeeting started Thu Jul  9 17:00:01 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service_chaining)"17:00
openstackThe meeting name has been set to 'service_chaining'17:00
*** stevelle has left #openstack-meeting-417:00
cathy_hi everyone17:00
*** asselin__ has quit IRC17:00
Vikram_cathy_:hi17:00
Swamicathy_: hi17:00
Mohankumar_Hi !17:00
bouthorscathy_:hi17:00
*** jwarendt has joined #openstack-meeting-417:00
LouisFhi17:00
Brian__hi17:01
pcarverhi17:01
cathy_#topic SFC spec, https://review.openstack.org/#/c/192933/8/doc/source/api.rst17:01
*** openstack changes topic to "SFC spec, https://review.openstack.org/#/c/192933/8/doc/source/api.rst (Meeting topic: service_chaining)"17:01
amotokihi17:01
cathy_any questions you would like to discuss?17:02
cathy_on the spec?17:02
*** b3rnard0 has left #openstack-meeting-417:02
cathy_amotoki: hi, glad that you join the meeting17:02
*** banix has quit IRC17:02
s3wonghello17:02
numanhi17:03
cathy_let's discuss the parameter which is now changed to ChainParameter object17:04
*** TheIntern has joined #openstack-meeting-417:04
bouthorscathy_: can we discuss how to make the classifier parameters more general, as per the email I sent to the list ?17:04
s3wongcathy_: we are still in patch set 817:04
*** TheIntern has left #openstack-meeting-417:04
s3wongcathy_: so there hasn't been update based on the various comments from armax17:04
*** Sukhdev has joined #openstack-meeting-417:05
cathy_s3wong: I am going to upload a new one soon17:05
s3wongcathy_: OK17:05
cathy_I have posted replies but will post a new version soon17:05
armaxs3wong, cathy_: yes I am looking forward to it17:05
cathy_bouthors: Yes, we can discuss that17:05
armaxI’ll review it to make sure we captured all the main points of our latest discussions17:05
cathy_armax: OK17:05
bouthorscathy_: ok17:06
cathy_For the Chain parameter object, Louis thinks there should be a link from the service chain object to this separate chainparam object.17:06
*** xingchao has joined #openstack-meeting-417:07
cathy_OK with everyone?17:07
s3wongcathy_: extension?17:07
LouisFs3wong: what do you mean by extension?17:07
cathy_s3wong: yes, the parameter will be modeled as an extension of the SFC object and there will be a separate API to create that chainparam object17:08
*** xingchao has quit IRC17:08
s3wongLouisF: the parameter blob would not really be part of the API, but rather an extension17:08
cathy_This is based on suggestion from Armando to create a separate chainparam object to specify the encap mechanism and failurepolicy17:09
LouisFarmando you proposed a separate chain parameter extension - seems a good idea17:09
bouthorscathy_: so in the cli we will have to provide a name or a uuid for the chainparm object17:09
LouisFbouthors: yes17:09
cathy_For this phase, the encap mechansim in the chainparam will be "none"17:09
s3wongcathy_: +117:10
*** sbalukoff has joined #openstack-meeting-417:10
cathy_which means we will not support the NSH for now which is suggested by Armando and Paul since OVS has not officially support NSH yet17:10
bouthorscathy_: why do we call it "encap mechanism" instead of "chaining mechanism"?17:10
Swamicathy_: this is to get rid of the dependency in the OVS.17:11
cathy_bouthors: I am open to the naming.17:11
cathy_Swami: yes, kindof17:12
Swamicathy_: thanks17:12
LouisFwe will add the chainparam it the next version of the doc so please review17:12
*** xingchao has joined #openstack-meeting-417:12
LouisFit -> to17:12
s3wongSwami: this is more to simplify stuff to ensure we have everything we need in OVS such that we can make progress in Liberty17:12
cathy_for naming, which one we should use?  everyone?17:12
Swamis3wong: understood17:12
cathy_encap or chaining mechanism?17:13
pcarverchaining mechanism sounds more general. I think that could be good.17:13
*** harshs has joined #openstack-meeting-417:13
s3wongcathy_: do we expect it to do more than specifying encap mechanism?17:13
bouthorscathy_, there could be multiple ways to encapsulate in NSH for example.17:14
LouisFencap-mech seems fine to me17:14
amotokiis it about packet format? or is it more than it?17:14
cathy_amotoki: it is about packet format17:14
pcarverwe've done some service chaining research based on MAC re-writing that doesn't use any encapsulation17:14
cathy_pcarver: that means the mechanism is none17:14
amotokiif it is about packet format, "encap" sounds better to me. we will think more than the format by "chaining mechanism"17:14
LouisFdolson have a well defined way using vlan-id to steer17:15
cathy_it is about packet format and how to correlate a packet with a chain17:15
LouisFhow about correlation-mech17:16
*** sdake has quit IRC17:16
LouisFi'm open to any reasonable as long as its meaning is well undestood17:17
cathy_The mechanism could be NSH-type1, NSH-type2, VLAN, Virtual EthernetPort, etc. For this phase, it will be none. We can discuss in later phase which one to support17:17
bouthorsbut then you could has NHS for data center, and NSH for Gi-LAN17:18
cathy_bouthors: that is counted as one mechanism17:18
cathy_it does not matter which scenario it is used.17:18
cathy_SO how about we call it "correlation mechanism"? Any "no" to this naming?17:19
LouisF+117:19
bouthors+117:19
Vikram_+117:19
pcarver+117:19
cathy_#agreed We will use "correlation mechanism"17:20
Mohankumar_+117:20
Swami+117:20
*** salv-orl_ has quit IRC17:20
*** sdake has joined #openstack-meeting-417:20
cathy_In the chain object, we will have ref to the chainparam object and have a separate API to create the chainparm. Any objection on this?17:21
cathy_Let's vote:-)17:21
LouisF+117:21
bouthors+117:21
Vikram_+117:21
pcarver+117:22
*** salv-orlando has joined #openstack-meeting-417:22
Brian__+117:22
Mohankumar_+117:22
cathy_#agree In the chain object, we will have ref to the chainparam object and have a separate API to create the chainparm17:22
Swamino objection17:22
cathy_Swami: :-)17:22
*** yamahata has quit IRC17:22
cathy_now let's discuss format of the ChainParam?17:23
*** geoffarnold has quit IRC17:24
cathy_Sorry what I mean is the parameter attribute format of the flow classifier17:24
cathy_ 1. A single parameter attribute (dict of name-value pairs for the classifier fields) as shown here.  2. Individual attributes for the classifier fields.17:24
cathy_Which option we should go for? everyone?17:24
LouisFbouthors: you have proposed a general way of encoding the classifier parameters including L7 parameters17:25
cathy_1. as shown in the spec? or 2?17:25
cathy_bouthors: what's your input?17:25
bouthorswe should push for a mechanism allowing for some extensions.17:25
cathy_bouthors: agree17:25
bouthorsmy proposal is a have a dictionnary of fields17:26
*** sdake_ has joined #openstack-meeting-417:26
LouisFbouthors: do you have link to your  doc?17:26
cathy_bouthors: OK, how about others' opinion?17:26
bouthorsand then the chainparm can contain a list of pairs fieldname, fieldvalue17:26
LouisF#link https://docs.google.com/document/d/1NkDwbAkPEfe-JuO37P5ZJ3wMH3LFpKCZBoB82hsb-t8/edit17:26
bouthorsI gave an example in the mailing list.17:26
bouthorsLouisF, thx17:27
LouisFwhat we have today is dict of name-value pairs17:27
LouisFarmax: you mentioned that dict result in a lot of complexity in the coding and db17:28
armaxLouisF: ues17:28
s3wongLouisF: wow... that is complicated...17:28
LouisFs3wong: is there a better way to handle extensibility?17:29
bouthorsFor example, ODL wants a way to do chaining between GBP groups of different tenants. We will not be able to define such a chain.17:29
armaxLouisF: let’s take this offlne, I don’t think we’ll be able to wrap this up here17:29
*** sdake has quit IRC17:29
s3wongso how many APIs we have to go through before we can specify something like "all traffic with destination port 80"17:29
s3wongLouisF: I do think we need to strike a balance between extensibility and usability --- particularly during phase one17:30
LouisFs3wong: we need to have an api that is reasonably straight-foward and yet allows for extensibility17:30
*** sdake has joined #openstack-meeting-417:30
bouthorsThe idea is that the dictionary are preconfigured. so in practise we don't change the number of APIs17:30
bouthorsThe idea is that the dictionary are preconfigured. so in practise we don't change the number of APIs used17:31
cathy_armax: I think we need to reach consensus so that we can update the spec based on consensus. Louis has listed two options. ANy other option? Let's discuss the cons and pros of each one and pick one.17:31
cathy_s3wong: what is your suggestion? 1 or 2 or another way?17:32
LouisFhaving individual attributes for the more common classifiers fields eg protocol, src/dest port, ip-prefixies make sense17:32
*** harshs_ has joined #openstack-meeting-417:32
s3wongcathy_: even with dictionary of fields, the fields need to be specified, right?17:33
cathy_Individual attributes means we do not group the flow descriptors.17:33
cathy_s3wong: yes17:34
LouisFthen additional fields can be handled by a more extensible format17:34
LouisFs3wong: yes17:34
*** sdake_ has quit IRC17:34
armaxcathy_: let me go over LouisF’s comments on the spec17:34
cathy_dictionary means we group the flow descriptors into a "parameter" field.17:35
*** dims_ has quit IRC17:35
LouisFarmax: my comment: The parameter attribute was introduced to allow for extensibility. Two options here:  1. A single parameter attribute (dict of name-value pairs for the classifier fields) as shown here.  2. Individual attributes for the classifier fields.  Defer to experts on REST API design for best approach for extensibility, readability, and simplest design.17:36
cathy_armax: OK. let us know your pick when you are done.17:36
bouthorsI woud rather choose option 217:36
Vikram_I vote for 2.17:37
*** dims has joined #openstack-meeting-417:37
LouisF+1 for 217:37
cathy_s3wong: ?17:37
armaxcathy_: at first glance it looks like 2 would be the way to go17:37
cathy_AFAIK, Armando likes 2 too17:38
cathy_armax: cool. So looks most people likes 217:38
armaxcathy_: well I dislkike the dict approach17:38
s3wongcathy_: sure, option 2 would be better than parsing a dictionary either at API level or driver17:38
*** FallenPegasus has joined #openstack-meeting-417:39
cathy_#agree the flow descriptors in Flow Classifier will go for Individual attributes for the classifier fields.17:39
Swami:q!17:39
cathy_Cool!17:39
* s3wong thinks Swami is using vi commands on his IRC client17:40
cathy_Any more questions on the spec that anyone would like to discuss?17:40
LouisFwill update next version with option 217:40
Swamis3wong: sorry wrong context17:40
s3wongSwami:   :-)17:40
LouisFSwami: understood17:40
-amotoki- Swami seems to quit from IRC forcely :-)17:40
cathy_pcarver: do you have more comments? we can discuss here. otherwise we will update based on all the comments and consensus. We need to get the spec merged as soon as possible which is the team's desire.17:41
*** auld has quit IRC17:41
LouisFwill update with the CLI commands17:42
LouisFper your suggestion armando17:42
cathy_Do we need to post REST API (JSON) examples in the spec?17:43
Vikram_+q17:43
Vikram_+117:43
Vikram_It will be good..17:44
LouisFi think the tables are sufficient17:44
pcarvercathy_: no I don't have a strong opinion on this point17:44
Mohankumar_Vikram agree17:44
amotokiJSON example would help us understand. I think we can skip CLI example.17:44
cathy_pcarver: OK, thanks.17:44
Vikram_cathy_:atleast resource name becomes clear and CLI will not have last time surprises17:44
Swamiyou can just add a wiki to show how the rest api works or looks.17:45
cathy_So we will post a few JSON examples for illustrative purpose.17:45
Vikram_+117:45
cathy_#agree the next version will post a few JSON examples for illustrative purpose17:46
bouthorsWhy do we need to have exclusivity between neutron_port and using other individual ones in ChainingParms?17:46
LouisFbouthors: is a neutron port is specified that woul include MAC address, IP address, etc17:48
cathy_Each chain can have multiple classifiers. If the user wants multiple flows to go through a chain, he cna specify multiple classifiers with one using neutron port and others using IP address etc. params.17:48
cathy_It is more clean to not mix them in one classifier.17:49
bouthorsBut we cannot say "trafic from this port, aimed at this dest"17:49
cathy_Neutron port itself already includes IP address etc.17:49
cathy_I think I added a reply int the spec that we will add source neutorn port and destination neutron port.17:50
LouisFbouthors: yes, good point17:51
cathy_bouthors: could you be more specific about your point?17:51
cathy_we have 8 minutes left17:52
LouisFso you mean from, say, neutron-port=X, tcp-port=8017:52
*** IlyaG has joined #openstack-meeting-417:52
bouthorswe can take it on the mailing list,  I was thinkg neutron-port-src=W, des=x.y.x.z.t/2417:53
cathy_your case is covered already17:53
cathy_sorry not covered17:53
bouthorsok17:54
cathy_Ok, I think we probably should lift the restriction to allow more flexible specificaiton of the flow descriptors17:54
*** salv-orlando has quit IRC17:55
LouisFbouthors: agree we need to support that, but what if it both src-neutorn-port=X (which has an IP address) and src-ip=10.1.1.1 are specified?17:55
cathy_I think we should remove the restriction. Any different opinions on this?17:55
*** geoffarnold has joined #openstack-meeting-417:55
LouisFneed to set precedence rules for the validation17:55
s3wongcathy_: what is the restriction?17:56
Vikram_LouisF: what do you mean precedence?17:56
LouisFs3wong: see line 22117:56
bouthorsThe parameters given must not contract themselves. For ex port-max < port -min , but also Louis example17:57
Vikram_you mean follow some order for classification?17:57
*** banix has joined #openstack-meeting-417:57
LouisFVikram_:  no, see my comment above:  at if it both src-neutorn-port=X (which has an IP address) and src-ip=10.1.1.1 are specified?17:57
cathy_Vikram_: Louis means the code internally needs to do some validation as bouthors mentioned.17:58
Vikram_cathy_, LouisF: understood17:58
LouisFwill update spec on this17:58
cathy_#agreed remove the restriction about Neutron port and other flow descriptors.17:59
*** SumitNaiksatam has joined #openstack-meeting-417:59
s3wongone minute17:59
cathy_#agreed remove the restriction about combination of Neutron port and other flow descriptors.17:59
Vikram_left :-)17:59
*** bknudson has quit IRC17:59
amotokido we have any meeting agenda wiki page?17:59
cathy_great discussion.time is up. thanks everyone. bye now17:59
bouthorsbye17:59
*** ivar-lazzaro has joined #openstack-meeting-417:59
amotokii would like to see pointers before meeitngs.17:59
Vikram_bye18:00
s3wongbye18:00
*** yamahata has joined #openstack-meeting-418:00
Swamibye18:00
cathy_amotoki: we will set it up18:00
cathy_But we have meeting logs18:00
pcarverbye18:00
cathy_#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
Mohankumar_bye18:00
openstackMeeting ended Thu Jul  9 18:00:21 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-09-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-09-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-09-17.00.log.html18:00
Brian__bye18:00
s3wongcathy_, amotoki: yeah, we need a wiki page to specify meeting agenda prior to meeting18:00
amotokicathy_: ok. thanks.18:00
*** Mohankumar_ has quit IRC18:00
s3wongand allowing people to add agenda items18:00
*** Brian__ has quit IRC18:00
fitoduartehello all18:00
*** Vikram_ has left #openstack-meeting-418:01
*** markmcclain has quit IRC18:03
*** davidlenwell has quit IRC18:03
*** xingchao has quit IRC18:04
*** davidlenwell has joined #openstack-meeting-418:05
*** zehicle has joined #openstack-meeting-418:05
*** markmcclain has joined #openstack-meeting-418:06
*** jwarendt has quit IRC18:11
*** cathy_ has quit IRC18:13
*** aventera_ has joined #openstack-meeting-418:14
*** aventerav has quit IRC18:14
*** auld has joined #openstack-meeting-418:15
*** zehicle has quit IRC18:16
*** zehicle has joined #openstack-meeting-418:17
*** puranamr has quit IRC18:17
*** puranamr has joined #openstack-meeting-418:19
*** Sukhdev has quit IRC18:19
*** sdake is now known as sdae18:19
*** sdae is now known as sdake18:19
*** dims has quit IRC18:21
*** abhishekk has quit IRC18:21
*** mwang2_ has joined #openstack-meeting-418:23
*** markvoelker has quit IRC18:24
*** markvoelker has joined #openstack-meeting-418:24
*** auld has quit IRC18:30
*** irenab has quit IRC18:31
*** auld has joined #openstack-meeting-418:33
*** sdake_ has joined #openstack-meeting-418:33
*** sdake has quit IRC18:36
*** sdake has joined #openstack-meeting-418:37
*** padkrish has joined #openstack-meeting-418:37
*** sdake_ has quit IRC18:40
*** geoffarnold has quit IRC18:43
*** svg has left #openstack-meeting-418:46
*** Sukhdev has joined #openstack-meeting-418:50
*** ajayaa has quit IRC18:51
*** puranamr has quit IRC18:52
*** zehicle has quit IRC18:54
*** geoffarnold has joined #openstack-meeting-418:54
*** auld has quit IRC18:54
*** IlyaG has quit IRC19:03
*** IlyaG has joined #openstack-meeting-419:03
*** dims has joined #openstack-meeting-419:10
*** puranamr has joined #openstack-meeting-419:11
*** ajayaa has joined #openstack-meeting-419:12
*** auld has joined #openstack-meeting-419:14
*** markvoelker has quit IRC19:15
*** markvoelker has joined #openstack-meeting-419:15
*** IlyaG has quit IRC19:21
*** numan has quit IRC19:23
*** auld has quit IRC19:23
*** qwebirc82056 has quit IRC19:24
*** sdake has quit IRC19:25
*** radek__ has quit IRC19:28
*** sdake has joined #openstack-meeting-419:29
*** zehicle has joined #openstack-meeting-419:33
*** radek__ has joined #openstack-meeting-419:33
*** sambetts has quit IRC19:35
*** sambetts has joined #openstack-meeting-419:38
*** asselin_ has quit IRC19:40
*** asselin_ has joined #openstack-meeting-419:40
*** auld has joined #openstack-meeting-419:41
*** singlethink has joined #openstack-meeting-419:44
*** mwang2_ has quit IRC19:47
*** singleth_ has quit IRC19:47
*** VW_ has quit IRC19:51
*** VW_ has joined #openstack-meeting-419:52
*** puranamr has quit IRC19:53
*** xingchao has joined #openstack-meeting-419:53
*** singleth_ has joined #openstack-meeting-419:54
*** VW__ has joined #openstack-meeting-419:55
*** puranamr has joined #openstack-meeting-419:55
*** VW_ has quit IRC19:56
*** singlethink has quit IRC19:57
*** palendae has quit IRC19:58
*** palendae has joined #openstack-meeting-419:59
*** xingchao has quit IRC19:59
*** irenab has joined #openstack-meeting-420:01
*** irenab has quit IRC20:01
*** LouisF has quit IRC20:04
*** puranamr has quit IRC20:05
*** puranamr has joined #openstack-meeting-420:06
*** padkrish has quit IRC20:07
*** padkrish has joined #openstack-meeting-420:10
*** mwang2 has joined #openstack-meeting-420:12
*** daneyon has quit IRC20:14
*** sdake_ has joined #openstack-meeting-420:15
*** sdake has quit IRC20:19
*** salv-orlando has joined #openstack-meeting-420:19
*** puranamr has quit IRC20:20
*** sdake_ is now known as sdake20:29
*** puranamr has joined #openstack-meeting-420:33
*** banix has quit IRC20:35
*** adityavajjha has quit IRC20:45
*** delatte has quit IRC20:46
*** Sukhdev has quit IRC20:50
*** xingchao has joined #openstack-meeting-420:57
*** padkrish has quit IRC21:00
*** padkrish has joined #openstack-meeting-421:00
*** padkrish has quit IRC21:01
*** padkrish_ has joined #openstack-meeting-421:01
*** jwagner is now known as jwagner_away21:01
*** ajayaa has quit IRC21:05
*** dims has quit IRC21:05
*** dims has joined #openstack-meeting-421:07
*** jckasper_ has joined #openstack-meeting-421:07
*** xingchao has quit IRC21:09
*** sigmavirus24 is now known as emacsraptor21:10
*** emacsraptor is now known as sigmavirus2421:10
*** fitoduarte has quit IRC21:12
*** zehicle has quit IRC21:12
*** jckasper_ has quit IRC21:13
*** jckasper_ has joined #openstack-meeting-421:14
*** jckasper_ has quit IRC21:20
*** auld has quit IRC21:22
*** jckasper_ has joined #openstack-meeting-421:30
*** TheIntern has joined #openstack-meeting-421:30
*** jckasper_ has quit IRC21:31
*** VW_ has joined #openstack-meeting-421:35
*** VW_ has quit IRC21:35
*** VW_ has joined #openstack-meeting-421:35
*** VW__ has quit IRC21:37
*** mwang2 has quit IRC21:37
*** sdake_ has joined #openstack-meeting-421:39
*** TheIntern has left #openstack-meeting-421:40
*** radek__ has quit IRC21:40
*** sdake has quit IRC21:42
*** IlyaG has joined #openstack-meeting-421:44
*** auld has joined #openstack-meeting-421:45
*** daneyon has joined #openstack-meeting-421:46
*** jpeeler has quit IRC21:48
*** daneyon_ has joined #openstack-meeting-421:49
*** Sukhdev has joined #openstack-meeting-421:51
*** daneyon has quit IRC21:52
*** daneyon has joined #openstack-meeting-421:56
*** jckasper has quit IRC21:56
*** padkrish_ has quit IRC21:56
*** padkrish has joined #openstack-meeting-421:57
*** fitoduarte has joined #openstack-meeting-421:57
*** VW_ has quit IRC21:58
*** padkrish_ has joined #openstack-meeting-421:58
*** VW_ has joined #openstack-meeting-421:58
*** VW__ has joined #openstack-meeting-421:59
*** sigmavirus24 is now known as sigmavirus24_awa21:59
*** padkrish has quit IRC21:59
*** daneyon_ has quit IRC22:00
*** daneyon_ has joined #openstack-meeting-422:01
*** amotoki has quit IRC22:02
*** dims has quit IRC22:03
*** VW_ has quit IRC22:03
*** dims has joined #openstack-meeting-422:03
*** padkrish_ has quit IRC22:03
*** bknudson has joined #openstack-meeting-422:04
*** padkrish has joined #openstack-meeting-422:04
*** daneyon has quit IRC22:04
*** padkrish has quit IRC22:06
*** padkrish has joined #openstack-meeting-422:06
*** daneyon_ has quit IRC22:11
*** jpeeler has joined #openstack-meeting-422:16
*** bouthors has quit IRC22:23
*** galstrom is now known as galstrom_zzz22:24
*** jasondotstar has quit IRC22:25
*** bknudson has quit IRC22:27
*** ivar-lazzaro has quit IRC22:29
*** ivar-lazzaro has joined #openstack-meeting-422:30
*** ivar-lazzaro has quit IRC22:30
*** ivar-lazzaro has joined #openstack-meeting-422:31
*** IlyaG has quit IRC22:34
*** xingchao has joined #openstack-meeting-422:38
*** singleth_ has quit IRC22:39
*** MarkAtwood has quit IRC22:40
*** jasondotstar has joined #openstack-meeting-422:43
*** xingchao has quit IRC22:55
*** padkrish has quit IRC22:58
*** FallenPegasus has quit IRC22:58
*** padkrish has joined #openstack-meeting-422:58
*** amotoki has joined #openstack-meeting-423:02
*** padkrish_ has joined #openstack-meeting-423:02
*** padkrish has quit IRC23:03
*** amotoki has quit IRC23:07
*** banix has joined #openstack-meeting-423:09
*** aventera_ has quit IRC23:09
*** padkrish_ has quit IRC23:13
*** padkrish has joined #openstack-meeting-423:14
*** salv-orlando has quit IRC23:18
*** padkrish has quit IRC23:18
*** sdake has joined #openstack-meeting-423:24
*** sdake__ has joined #openstack-meeting-423:26
*** sdake_ has quit IRC23:27
*** geoffarnold has quit IRC23:28
*** padkrish has joined #openstack-meeting-423:29
*** sdake has quit IRC23:29
*** sdake__ is now known as sdake23:30
*** Swami has quit IRC23:32
*** openstack has joined #openstack-meeting-423:38
*** ChanServ sets mode: +o openstack23:38
*** VW_ has joined #openstack-meeting-423:38
*** VW__ has quit IRC23:41
*** VW_ has quit IRC23:43
*** yamamoto has joined #openstack-meeting-423:49
*** yamamoto_ has joined #openstack-meeting-423:49
*** Sukhdev has quit IRC23:51
*** yamamoto_ has quit IRC23:52
*** Sukhdev has joined #openstack-meeting-423:52
*** jpekkari has joined #openstack-meeting-423:53
*** yamamoto has quit IRC23:53
*** ivar-laz_ has joined #openstack-meeting-423:56
*** banix has quit IRC23:59
*** ivar-lazzaro has quit IRC23:59

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