Tuesday, 2014-12-02

*** ChuckC_ has joined #openstack-meeting-400:12
*** ChuckC_ is now known as ChuckC00:20
*** ChuckC has quit IRC00:29
*** SumitNaiksatam has quit IRC00:46
*** igordcard has quit IRC00:47
*** david-lyle is now known as david-lyle_afk01:03
*** SumitNaiksatam has joined #openstack-meeting-401:23
*** shwetaap has joined #openstack-meeting-401:24
*** SumitNaiksatam has quit IRC01:29
*** s3wong has quit IRC01:35
*** shwetaap has quit IRC02:08
*** dboik has joined #openstack-meeting-402:13
*** dboik has quit IRC02:18
*** ChuckC has joined #openstack-meeting-402:34
*** shwetaap has joined #openstack-meeting-402:55
*** ivar-laz_ has joined #openstack-meeting-403:09
*** ivar-laz_ has quit IRC03:09
*** ivar-laz_ has joined #openstack-meeting-403:10
*** ivar-lazzaro has quit IRC03:12
*** ivar-laz_ has quit IRC03:14
*** shwetaap has quit IRC06:40
*** nfedotov has joined #openstack-meeting-407:16
*** nfedotov1 has joined #openstack-meeting-407:18
*** nfedotov1 has quit IRC07:19
*** nfedotov has quit IRC07:20
*** shwetaap has joined #openstack-meeting-407:21
*** SumitNaiksatam has joined #openstack-meeting-407:59
*** kobis has joined #openstack-meeting-408:04
*** igordcard has joined #openstack-meeting-409:31
*** evgenyf has joined #openstack-meeting-410:16
*** nfedotov has joined #openstack-meeting-412:05
*** nfedotov has quit IRC12:12
*** igordcard has quit IRC13:28
*** igordcard has joined #openstack-meeting-413:31
*** igordcard has quit IRC13:56
*** shwetaap has quit IRC13:58
*** shwetaap has joined #openstack-meeting-413:58
*** dboik has joined #openstack-meeting-414:01
*** shwetaap has quit IRC14:02
*** hareeshp has joined #openstack-meeting-414:24
*** yamahata has joined #openstack-meeting-415:02
*** nikhil_k|vacay is now known as nikhil_k15:18
*** johnsom has joined #openstack-meeting-415:54
dougwigmorning15:57
sballemorning15:57
johnsomHello15:58
kobishi15:58
*** xgerman has joined #openstack-meeting-415:58
ajmillerGood Morning15:59
xgermangm15:59
dougwig#startmeeting neutron lbaas16:00
openstackMeeting started Tue Dec  2 16:00:03 2014 UTC and is due to finish in 60 minutes.  The chair is dougwig. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron lbaas)"16:00
openstackThe meeting name has been set to 'neutron_lbaas'16:00
dougwig#topic Roll call and Agenda and general waking up...16:00
*** openstack changes topic to "Roll call and Agenda and general waking up... (Meeting topic: neutron lbaas)"16:00
johnsomo/16:00
ajmillerhere16:00
xgermano/16:00
dougwigagenda:16:00
dougwig#link https://wiki.openstack.org/wiki/Network/LBaaS#Meeting_02.12.201416:00
sbalukoffMorning!16:00
rm_worko/16:00
xgermananyhting form the Neutron meeting I tend to skip?16:00
blogan\o/16:00
dougwigyep, but that's later in the agenda.16:00
xgermansuspensew16:01
*** jamiem has joined #openstack-meeting-416:01
evgenyfHi16:01
jamiemo/16:01
dougwig#topic Announcements16:01
*** openstack changes topic to "Announcements (Meeting topic: neutron lbaas)"16:01
dougwigReview of the week:16:02
dougwig#link https://review.openstack.org/#/c/123487/16:02
dougwigthat's the first half of the agent-less ref driver.  needs eyes.16:02
dougwigany other announcements from anyone?16:02
bloganneeds to rerun the testst oo16:02
blogantoo16:02
dougwigjenkins was unhappy last night16:02
bloganis it recheck or recheck no bug?16:02
dougwigrecheck16:03
bloganused to be recheck no bug16:03
xgermanajmiller discovered that one of the Neutron changes broke our migrations16:03
dougwigthey changed it16:03
dougwigyou can check status.openstack.org/zuul to see if it re-queues.16:03
dougwig#topic Flavors16:03
*** openstack changes topic to "Flavors (Meeting topic: neutron lbaas)"16:03
dougwig#link https://review.openstack.org/#/c/10272316:03
dougwigthe spec has been resurrected.  whether it is undead or reanimated remains to be seen.16:03
sballelol16:04
dougwigspec approval deadline is 12/14, so please weigh in with feedback.16:04
*** ajmiller has quit IRC16:04
dougwigany flavors questions/comments/feedback now?16:04
bloganneed to refresh my memory16:04
*** ajmiller has joined #openstack-meeting-416:05
xgermansame here16:05
dougwigok, i'll ping again next week.16:05
dougwig#topic Advanced services split discussion16:05
*** openstack changes topic to "Advanced services split discussion (Meeting topic: neutron lbaas)"16:05
dougwig#link https://review.openstack.org/#/c/136835/16:05
dougwigSome discussion at the neutron meeting this morning, at timestamp 14:26:1316:05
dougwig#link http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-12-02-14.01.log.html16:05
dougwigcurrent spec creates four teams (neutron, lbaas, fwaas, vpnaas), and current decision is to share the neutron database with separate tables/migration chains.16:06
dougwigwe need that spec to solidify this week if we're going to get it in early in the cycle.16:06
blogansounds ambitious given all the comments16:06
sbalukoffDoug is doing a good job of addressing what he can in the comments.16:07
bloganyes he is16:07
xgerman+10016:07
sbalukoffBut yes, there are probably a few things that others in the group are simply not going to agree on.16:07
blogani think the extensions decision and the same db will speed up the acceptance though16:07
sbalukoffI guess we'll see how willing people are to compromise.16:07
sbalukoffYeah, there are a lot of trade-offs which are being made in the interest in speeding up acceptance.16:08
dougwigindeed.16:08
sbalukoffEven if we can't come to terms on the governance issue, having a technical plan to get split repositories is a step in the right direction, IMO.16:08
*** jorgem has joined #openstack-meeting-416:09
xgermandid governace get even discussed today?16:09
xgermanI think we are doing a good job dancing around that :-)16:09
dougwiggovernance is pretty simple, actually.  either we're in the networking program, and it's up to mestery, or we go to stackforge, with all that entails.  both are viable options.16:09
mestery++16:09
sbalukoffOh hey!16:09
sbalukoffI won't call you the devil this time. ;)16:10
sbalukoff(You know, speak of the devil...)16:10
sbalukoffSorry, it's early and my brain is trying hard to humor.16:10
dougwigif we're insulting kyle, we say kyle, not mestery, so his irc client doesn't light up.16:10
mesterylol16:11
dougwigi think there's a gerrit spec about that somewhere.16:11
xgermanlol16:11
sbalukoffHa!16:11
*** markmcclain has joined #openstack-meeting-416:11
dougwigalright, any split comments/feedback/questions?  meeting slots on this topic have been pretty quiet, which is either awesome or worrisome.16:11
xgermanwe just want it done -)16:11
sbalukoffActually, I feel like we're in a pretty good place with that spec...16:11
bloganim just interested in getting progress done, path of least resistance at this point16:11
johnsom+1 on done16:11
sbalukoffLet's push hard for consensus.16:11
xgermanI don't think there is much we can do except +116:12
blogani can +100016:13
dougwigok, then please leave some comments or whatnot on the gerrit spec, and let's get this rolling.  it'll get an update this morning for the decisions from today's neutron meeting.16:13
xgerman+100016:13
sballemestery: I would like to attend the neutron meetup remote. Anything around taht yet?16:13
dougwigi'll post in channel when it's ready for action again.16:13
dougwigsballe: he mentioned in the meeting this morning that he's working on it.  see the beginning of that chat log, in announcements.16:13
sbalukoffsballe: +116:13
mesterysballe: We will have remote participation, the plan for people coding is to have an etherpad where people can pick items, and we'll be in-channel on #openstack-neutron16:13
mesteryI'll see about Hangouts as well16:14
mesteryThough that depends on what Adobe can offer there too :)16:14
bloganthey can't photoshop everyone in?16:14
dougwigi can offer a webex if it helps.16:14
sballedougwig: I know I was there. I just wanted mestery to know that I am interested in attendign even thought I didn;t put my name onthe wiki16:14
rm_workblogan: +116:14
mesterysballe: Got it16:14
mesteryblogan: lol16:14
*** pc_m has joined #openstack-meeting-416:15
dougwig#topic Open discussion16:15
*** openstack changes topic to "Open discussion (Meeting topic: neutron lbaas)"16:15
kobisI wonder - if vendor code is pushed out of neutron, will the *aas repos include vendor code?16:15
blogankobis: it will icnlude the vendor drivers16:15
dougwigkobis: that is mentioned in the spec.  yes, because we're still trying to grow community16:15
sbalukoffkobis: Yes, according to the latest spec.16:15
sbalukoffHeh!16:15
kobisok 10x16:15
xgermanyep, we also said so at the summit16:15
dougwigi would expect the long-term to look similar to neutron, though.16:16
*** TrevorV has joined #openstack-meeting-416:16
xgermanme, too16:16
dougwigany other topics for today?16:16
bloganyes16:16
bloganneutron lbaas meetup16:16
dougwig#topic neutron lbaas meetup16:16
*** openstack changes topic to "neutron lbaas meetup (Meeting topic: neutron lbaas)"16:16
dougwiggo16:16
dougwigblogan?16:17
blogandoes everyone feel it is worth having it separate from an octavia meetup?  I'm sure we want octavia to focus on octavia, but just getting everyone's thoughts16:17
xgermanno, we should combine16:18
xgermandougwig - time for #vote16:18
bloganwell we need to get everyone's thoughts on it first16:18
sbalukoffWhat do we hope to accomplish at the neutron LBaaS meetup?16:18
sballeif we combine will we have another face 2 face in January? LBaaS/Octavia?16:18
bloganneutron lbaas this time aroudn will have a lot to do, especially with the split16:18
dougwigi think there's quite a bit of v2 work left, and having folks in the same room, with enough cores to make a difference, would help a lot.16:18
sbalukoffOk.16:19
dougwigplus, it needs to be later than december, to give the split time to settle16:19
sbalukoffI agree16:19
blogani agree with that16:19
dougwigIMO16:19
sbalukoffI'm in favor having it separate16:19
sbalukoffGiven those requirements.16:19
bloganhowever, i worry that having another meetup may cause a low attendance outcome16:19
sbalukoffOr objectives, rather.16:19
xgermanblogan +1016:19
sbalukoffWell, we likely won't get a second Octavia face to face this cycle then.16:20
dougwigi wouldn't object to an octavia/lbaas meetup in late january.  the holidays and the split is just making the december meetup tough.16:20
xgermanalso there is the advanced services meetup16:20
sballeand markmcclain will be at the Octavia one. We could use him to do some +2 on LBaaS stuff16:20
sbalukoffAs long as people are OK with some folks working on Octavia stuff at the Neutron LBaaS meetup, I'm OK with that.16:20
dougwigit'd need the full 5 days, and we'd want to schedule some of those days for lbaas only, and some for octavia only, IMO.16:20
bloganxgerman: im not sure there will be one now, though I am not sure16:21
dougwigsbalukoff: as long as octavia doesn't prevent v2 from making progress, they're the same teams.16:21
sbalukoffTrue16:21
sballedougwig: +116:21
xgermanok, with the family I am waty to be gone two weeks in January16:21
mesteryFolks: Any reason not to just have a single meetup for lbaas in december? Why are two needed?16:21
* mestery goes back to lurking16:21
sbalukoffLet's have our employers rent out a conference center for the whole month of January and meet there and work on both.16:21
sbalukoff;)16:21
sballesbalukoff: +116:21
bloganmestery: the main reason is there is a lot to do on both fronts16:22
sbalukoffYep.16:22
sballesbalukoff: thinks this is a good idea. not distractions or meetings16:22
dougwigmestery: because the current december date is holidays for many (me!), and the split won't be done yet.16:22
mesteryAh, got it dougwig and blogan. Just curious16:22
sbalukoffsballe: Unfortunately totally impractical. ;)16:22
*** bobmel has joined #openstack-meeting-416:22
sballesbalukoff I know16:22
bloganwell rackspace can host this meeting if it is determined we want it16:22
dougwigmestery: curiosity will be punished.16:22
markmcclainI'm on the road nearly all of January… so I won't be able to attend either in person/remote16:23
mesterylol16:23
sbalukoffblogan; I'm pretty sure we want it.16:23
sbalukoffAlso, Texas is nice in January.16:23
xgermanso is Seattle :-)16:23
xgermanor Boise :-)16:23
sbalukoffxgerman: In January?16:23
rm_workseattle is cold and possibly snowy in January :P16:23
bloganis it worth having without mestery and markmcclain there? if we can't get fast +2 eyes?16:23
sballehow about Boston ;-)16:23
xgermanyep, we can go to the slopes and ski16:23
mesteryblogan: By then LBaaS will be it's own repo with at least you and dougwig as +2 :)16:24
sbalukoffHaha!16:24
rm_workbut if I need to stay in WA longer let me know so I can cancel my return flight :)16:24
sbalukoffmestery: That's very optimistic of you. ;)16:24
xgermanrm_work just move there and start RAX west16:24
bloganmestery: good point, that totally escaped me16:24
mesterylol16:24
rm_workxgerman: RAX West is called the SFO office :)16:24
rm_work… which would be awesome to work out of, I think16:25
bloganokay so are we in agreement that we want one in January?16:25
dougwigalright, where's consensus at on this point?  merged or separate?16:25
dougwigha, jinx16:25
xgermanor shoudl we aim for later in case the plit gets dealyes...16:25
bloganlater would be nearing the end of kilo16:25
xgermanbut we could make the last big push16:26
* dougwig would prefer some soak time.16:26
bloganbut if we have specs approved and mestery and markmcclain are okay with some exceptions to a late spec, then I'd be fine with later16:26
dougwigi'd think the last push should be for making octavia 1.0 be the ref.  IMO.16:26
dougwigwhich implies we need v2 solid earlier.16:27
bloganyep16:27
rm_workoh god, 1.0 by Kilo *and* made the ref for n-lb?16:27
rm_work>_>16:27
dougwigthat might too ambitious.  :)16:27
dougwigbut you've gotta have goals.16:27
sbalukoffHeh!16:28
blogancouldn't 0.5 be the ref impl?16:28
rm_workhonestly not sure what I think of Octavia being the ref driver for n-lb still...16:28
bloganadn then it gets upgraded to 1.016:28
sbalukoffBig Hairy Audacious Goals?16:28
dougwigblogan: i thought 0.5 wasn't scalable?16:28
bloganits not16:28
xgermandepends on the hardware16:28
rm_workI like the idea of the "reference" driver being something SIMPLE so it can be easily updated when the API changes16:28
dougwigbetter or worse than the agent-ified haproxy namespace driver?16:28
sbalukoffAlso, Neutron LBaaS v1 reference is not scalable.16:28
rm_workOctavia seems a bit complex (and out of tree)16:28
blogansbalukoff: it is16:29
dougwigit's scalable with the agent on other machines.  just not pleasantly.16:29
xgermanlet's not get too far off topic16:29
*** jwarendt has joined #openstack-meeting-416:29
rm_workIMO leave the namespace driver as the ref <_<16:29
dougwigthank you, back to topic.16:29
bloganwell thats antoehr discussion at a later time16:29
bloganback to meetup16:29
dougwigwhat's the vote syntax?16:29
blogan#startvote16:29
openstackOnly the meeting chair may start a vote.16:30
xgermanwell, we should find out if the adv services meetup is happening16:30
rm_workI mean, what are we voting on?16:30
sbalukoff.#startvote question? Yes No Maybe16:30
rm_workJust "Yes/No" to "have two meetings"?16:30
bloganxgerman: im almost certain that was going to happen with adv svc was spinning out as one16:30
dougwigi was just going to take the temperature of the room.16:30
rm_workor something more specific16:30
dougwig#startvote Are you ok with two meetups? Yes No Maybe16:31
xgermanok, and that was split related also -- so we will have two split related meetups in jan16:31
openstackBegin voting on: Are you ok with two meetups? Valid vote options are Yes, No, Maybe.16:31
openstackVote using '#vote OPTION'. Only your last vote counts.16:31
*** SumitNaiksatam has quit IRC16:31
blogan#vote Yes16:31
sbalukoff#vote Yes16:31
rm_worki am a LITTLE worried about making everyone travel so often16:31
dougwigauto-correct changed meetups to metopes.  that is some high end dictionary action.16:31
xgerman#vote Maybe16:31
dougwig#vote yes16:31
johnsom#vote Maybe16:31
sballe#vote yes16:31
TrevorV#vote maybe16:31
rm_work#vote Maybe16:31
bloganswitzerland16:32
ptoohill#vote maybe16:32
dougwiggood heavens, commit people.  :)16:32
dougwig#endvote16:32
rm_work"If I don't make it, tell my wife I said -- Hello."16:32
openstackVoted on "Are you ok with two meetups?" Results are16:32
openstackMaybe (5): xgerman, rm_work, ptoohill, johnsom, TrevorV16:32
openstackYes (4): dougwig, sballe, sbalukoff, blogan16:32
dougwigblogan: this is your topic.  did you get what you needed?16:33
bloganwell if that vote is a binding contract16:33
sbalukoffrm_work: Those who don't want to / can't travel can always attend remotely.16:33
bloganwhich i dont think it is16:33
dougwigit is not16:33
rm_workhttps://www.youtube.com/watch?v=ussCHoQttyQ  https://www.youtube.com/watch?v=fpaQpyU_QiM16:33
ptoohilli guess if its here im fine with it. anywhere else we cant go. and on that note im interested how the remote aspect for the upcoming meetup is going to work16:33
bloganso if we had it in January16:33
blogandoes the week of the 19th work for people?16:33
sbalukoffI'm OK with having it in Texas.16:34
sbalukoffblogan: AFAIK, yes.16:34
sballesballe is checking her calendar16:34
sballeCan we have it in Austin if it is Texas?16:35
ptoohillI would love to have it in Austin16:35
rm_workheh, yeah, me too16:35
dougwigsballe: is HP volunteering space in Austin?16:35
johnsomI think I would only be able to make the first three days the week of the 19th16:35
rm_workthough we'd have to start later so we have time to take the shuttle in the morning from SA :P16:35
xgermanwe have space everywhere :-)16:35
ptoohillEVERYWHERE16:35
jorgemrm_work: or we could carpool together :)16:36
sballeI know RAX has space in Auston too. But HP we have space too16:36
blogancan it be a week long replay of the hp paris party?16:36
dougwigmonday the 19th is MLK day, fyi.16:36
TrevorVI'm not gonna lie, I'm probably not going to travel to Austin daily for that.16:36
rm_workjorgem: gah16:36
sbalukoffOh...16:36
sbalukoffYeah, let's avoid the week of the 19th then.16:36
dougwigmeetup proposal is 20-22, i think.16:36
*** yamahata has quit IRC16:36
bloganwell what about just start on Tuesday the 20th16:36
xgermanI think that week is anyway pretty close to the other meetup16:36
ptoohillI would do anything to get out of SA daily16:36
sbalukoffHave it be a 3-day thing?16:37
xgermanblogan then you only get 4 days16:37
sbalukoffThat works.16:37
sbalukoffI can't attend the 23rd either.16:37
xgermanso 36-39 would be better for sbalukoff16:37
bloganmost meetups are only 3 days anyway, so people dont ahve to travel on weekends16:37
xgerman23-2916:37
sbalukoffxgerman: Which other meetup?16:37
xgermanadv services16:38
sbalukoffAah.16:38
bloganxgerman: i dont think they're having one16:38
xgermanI thought you said they would16:38
bloganwhen we were going to split out as one yes, but now we're not16:38
sbalukoffIf the split entails 4 different repositories, the need for an advanced services meetup starts to make less sense.16:38
sballeI am not available 26-30 I will be in Sunnyvale and Seattle16:38
ptoohillthat message should be talked about a bit louder16:38
blogansbalukoff: indeed16:39
bloganif the toher advanced services want to have a meetup, then they may choose that16:39
dougwiglet's go for some closure here.   if we don't have consensus on good timing/location here, let's fire up an etherpad.16:39
xgermandougwig +116:40
sbalukoffdougwig +116:40
sballe=116:40
sballe+116:40
bloganill fire one up16:40
dougwig#action blogan setup lbaas meetup etherpad16:41
dougwigthank you16:41
dougwig#topic Open discussion16:41
*** openstack changes topic to "Open discussion (Meeting topic: neutron lbaas)"16:41
sbalukoffSweet.16:41
dougwigother topics?16:41
xgermansure16:41
xgermanjust a PSA we founbd that one of the lastest Neutron topics breaks our feature branch16:41
blogando we need to fix a merge conflict?16:41
bloganor is it a functional break?16:42
ajmillerThere is a problem when upgrading the neutron database.16:42
ajmillerI am working on suggesting a patch.16:42
dougwigdo we just need another merge from master?16:42
bloganwhat is the break?16:42
dougwigif so, mestery needs to submit it.16:42
ajmillerMerge from master would probably fix it.  There has been a database upgrade on master, and that breaks the neutron upgrade.16:43
*** bobmel has quit IRC16:43
bloganis it just bc another db migration came in?16:43
xgermanyep16:43
ajmillerblogan yes16:43
bloganoh okay well thats expected, if its just an alembic sequence issue16:44
ajmilleryes16:44
bloganim not sure if thats something we always want to merge master for16:44
dougwigok, i'll ask for another merge.  i found out the hard way last time that only someone in the neutron release group can submit the patch.16:44
*** banix has joined #openstack-meeting-416:44
sbalukoffEew.16:44
bloganif we merge master for every new migration, thats a lot of contacting neutron release group to merge16:44
xgermanwell, once the split happends16:45
sbalukoff...16:45
dougwigis the feature branch broken, or just swapping between feature and master on the same install?16:45
sbalukoffThere is that.16:45
dougwigbecause if it's the latter, i agree with blogan.  wipe and reset16:45
bloganyeah so why dont we wait until the split is ready, then do one merge16:45
rm_work+116:45
xgermanBut inquisitive minds want to try out LbaaS v216:46
xgerman...16:46
bloganthe feature branch should still work on its own16:46
bloganhopefully inquisitive minds can do a git checkout feature/lbaasv2 and restart?16:47
bloganunless they need some features that are in master as well16:47
dougwigxgerman: use neutron-db-manage to rollback to feature back alembic and then go forward.16:47
dougwig /back/branch16:47
*** jackmccann has joined #openstack-meeting-416:47
dougwigi can add instructions for that to the devstack wiki16:47
bloganoh yeah that too16:48
bloganlol16:48
xgermanwell, so we decided to not track master with our feature branch?16:48
xgermanJust making sure we are on the same page16:48
bloganxgerman: i think waiting until the split to do one final merge is the best option16:48
xgermanI am ok with that -- I just like it spelled out16:48
dougwigwhen the branch was created, folks wanted to minimize the number of master merges.  if there's something broken between them (which happened with jenkins jobs once), we merge.  if it's just diverging migrations, we'll reset the chain for the final merge.16:49
dougwigthat was our earlier plan, at least.16:49
dougwigany other issues there, or any other topics for today?16:50
xgermanI am good --16:50
dougwigalright, thanks folks, and goodbye16:51
xgermano/16:51
bloganadios16:51
ajmillerbye16:51
TrevorVo/16:51
dougwig#endmeeting16:51
sballeBYE16:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:51
*** TrevorV has left #openstack-meeting-416:51
openstackMeeting ended Tue Dec  2 16:51:34 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-12-02-16.00.html16:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-12-02-16.00.txt16:51
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-12-02-16.00.log.html16:51
rm_workwhew16:51
sbalukoffHeh!16:51
sbalukoffDang, not enough time for me to take a nap before the next meeting. :P16:52
sbalukoff(I'm totally getting one after, though.)16:52
*** david-lyle_afk is now known as david-lyle16:52
*** jwarendt has quit IRC16:55
*** pc_m has left #openstack-meeting-416:55
*** trinaths1 has joined #openstack-meeting-416:56
*** sunil_ has joined #openstack-meeting-416:57
*** SumitNaiksatam has joined #openstack-meeting-416:58
*** pc_m has joined #openstack-meeting-416:59
*** igordcard has joined #openstack-meeting-417:00
dougwighello advanced services.17:00
bloganhello17:00
SumitNaiksatamdougwig: blogan: hi there17:00
hareeshphello17:00
dougwigmorning SumitNaiksatam17:00
sbalukoffHowdy, folks!17:00
xgermano/17:00
banixhi17:01
SumitNaiksatamdougwig: morning (thanks to neutron IRC had an early start ;-) )17:01
*** SridarK has joined #openstack-meeting-417:01
SumitNaiksatamhareeshp: sbalukoff xgerman banix: hi17:01
SumitNaiksatamokay lets get started17:01
pc_mhi17:01
*** glebo has joined #openstack-meeting-417:01
SridarKHi17:01
SumitNaiksatam#startmeeting Networking Advanced Services17:01
gleboyo17:01
openstackMeeting started Tue Dec  2 17:01:56 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: Networking Advanced Services)"17:01
openstackThe meeting name has been set to 'networking_advanced_services'17:02
SumitNaiksatampc_m: SridarK glebo: hi17:02
johnsomo/17:02
SumitNaiksatam#info https://wiki.openstack.org/wiki/Meetings/AdvancedServices#Agenda17:02
SumitNaiksatamcopy pasting from the neutron IRC for the benefit who missed it -17:02
SumitNaiksatam#info SPD is 12-8-2014 and SAD is 12-15-201417:02
SumitNaiksatam#info Kilo-1 is 12-18-201417:02
*** jorgem has left #openstack-meeting-417:03
*** bobmel has joined #openstack-meeting-417:03
sbalukoffCould you expand those acronyms please?17:03
SumitNaiksatamany other info/announcements people would like to share? (apart from the services’ split discussion, of course)17:03
SumitNaiksatamSpec Proposal Deadline17:03
dougwigSpec approval deadline, and the first is the submission deadline (not sure on the P)17:03
SumitNaiksatamSpec Approval Deadline17:03
sbalukoffThanks!17:03
bloganit'll be a SAD day17:04
xgermanbecause you spec doesn't make it?17:04
sbalukoffbadum-tish!17:04
banixnot knowing what that is, probably no17:04
SumitNaiksatamblogan: exactly - seemed like SAD had become common neutron lingo17:04
banixsorry; wrong window17:04
sunil_hello everyone!17:05
*** mhanif has joined #openstack-meeting-417:05
SumitNaiksatamokay next topic - our raison d'être17:05
SumitNaiksatam#topic Advanced services’ spin out17:06
*** openstack changes topic to "Advanced services’ spin out (Meeting topic: Networking Advanced Services)"17:06
SridarKSumitNaiksatam: seems Paris has left its impression on u :-)17:06
SumitNaiksatamSridarK: oh good catch!17:06
SumitNaiksatamServices' split: #link https://review.openstack.org/#/c/13683517:06
SumitNaiksatamand there is a somewhat related spec which factors into the extensions’ discussions: #link https://review.openstack.org/#/c/13676017:07
SumitNaiksatamto summarize for those who missed the meeting in the morning17:07
dougwigplease note the imminent changes that are coming, based on today's neutron meeting:17:07
dougwighttps://www.irccloud.com/pastebin/5qRvFm1X17:07
* glebo yeah, thinks 06:00 is PAINFUL, but was commuting through inches of rain at the time.17:08
SumitNaiksatamdougwig: thanks, i was just about to summarize that, seems like you had it prepared ;-)17:08
SumitNaiksatamglebo: yeah, commute was pretty painful17:08
dougwigthat was my gerrit comment when I did -A just a few ago.  :)17:08
SumitNaiksatamdougwig: you mean workflow-a17:09
xgermanneat17:09
SumitNaiksatam*workflow-117:09
trinaths1Hi17:09
SumitNaiksatamdougwig: those read like executive decisions ;-P17:10
dougwigi realized after hitting submit that i should've put, "from the neutron meeting..."  :)17:10
mesterySumitNaiksatam: That's because they were discussed and agreed to in the neutron meeting today17:10
mesterydougwig: ++17:10
SumitNaiksatammestery: yes sure, just pulling dougwig’s leg here17:10
mesterylol17:10
dougwigwith both the split and flavors, it's a good thing that i'm secretly a spider.17:11
sbalukoffWait, are we now getting to accuse dougwig of being a merciless tyrant?17:11
*** carl_baldwin has joined #openstack-meeting-417:11
SumitNaiksatammestery: glad you could make it to this meeting as well17:11
* mestery is omniscient17:11
SumitNaiksatamsbalukoff: that we thought was already established, no? ;-)17:12
glebomestery:  lol17:12
sbalukoffAs long as I get to carry around a pitchfork and torch, I'm happy.17:12
SumitNaiksatamokay, so any thoughts feedback on those points, or anything else in the latest spec that we need discuss today/here?17:13
sbalukoffAaanyway.17:13
xgermansbalukoff likes to be the only merciless tyrant in town17:13
glebosbalukoff:  wait, we already passed halloween, no?17:13
sbalukoffxgerman: +117:13
sbalukoffI feel like the current spec is pretty close to what we need to get progress to happen.17:13
xgerman+117:14
SumitNaiksatamsbalukoff: okay17:14
sbalukoffAs such, if you've got objections, please make specific comments to that effect soon!17:14
xgermanand if not +117:14
dougwigthe work needs to start next week at the latest, so we need to get things solid.17:14
sbalukoffxgerman: +117:14
xgermanyep, originally split was aimed for k117:14
xgermanand we can still make it17:15
dougwigi don't mind some rework later, but if you've got something major, please don't wait.17:15
trinaths1I'm new here then, How to propose a spec here?17:15
sbalukoffAnd make time *now* to review if you haven't done so and feel like you have a horse in this race.17:15
SumitNaiksatamtrinaths1: hi, same as neutron spec17:15
dougwigtrinaths1: our specs are neutron specs17:15
*** nlahouti has joined #openstack-meeting-417:15
xgermanthere is a wiki somewhere explaining the process17:16
SumitNaiksatamis pc_m here?17:16
pc_myes sir17:16
trinaths1okay. How will they be pointed to Advanced services?17:16
SumitNaiksatamtrinaths1: thats not needed, its all one neutron track17:17
trinaths1okay.17:17
trinaths1SumitNaiksatam: understood.17:17
SumitNaiksatam#topic Services’ impact by L3 agent refactoring17:17
*** openstack changes topic to "Services’ impact by L3 agent refactoring (Meeting topic: Networking Advanced Services)"17:17
SumitNaiksatamthis would impact fwaas and vpnaas17:17
SumitNaiksatampc_m: you want to summarize where we are at with this?17:18
pc_msure17:18
pc_mCarl has a BP out for the effort (I think 131535)17:18
pc_mI did a commit for review to start the observer pattern to allow agents to register with L3 agent to get notifications for events.17:19
pc_m13654917:19
pc_mAssaf has refined it some, and will do a updated patch that merges his with mine. Will have it tomorrow or Thur I suspect.17:19
*** s3wong has joined #openstack-meeting-417:19
pc_mCurrently, we're trying to work out the notifications.17:20
SumitNaiksatam#link https://review.openstack.org/#/c/131535/ (for the spec)17:20
pc_mSeems like there may be some variation as to where notifications will occur.17:20
pc_mWill need help from FW folks to see about where hooks are needed for that agent.17:21
SumitNaiksatam#link https://review.openstack.org/#/c/136549/ (for pc_m’s patch)17:21
SridarKpc_m: i volunteer17:21
pc_mI think Assaf's is #link https://review.openstack.org/#/c/13766817:21
pc_mSridarK: thanks!17:21
pc_mWe can hook up offline. Looking at router add/delete/update and where agents need to be notified, for agent specific actions.17:22
glebopc_m: i can also have Gary Duan from our team take a look17:22
SridarKpc_m: there are few places that notifications are needed esp on router stuff17:22
SridarKpc_m: yes exactly17:22
pc_mglebo: super! The more the merrier.17:22
pc_mI think we want to get Assaf's and my commits merged, and then it is a matter of working out the notification points and refine the notification method.17:23
SumitNaiksatampc_m: so this does not propose to move away from the l3 agent inheriting from the fwaas agent?17:23
hareeshppc_m: Is is the plan to still go for multiple agents (per service) or service specfic classes somehow loaded by a single agent?17:23
pc_mSumitNaiksatam: I think it will split them up. We're trying to tackle it piecemeal.17:24
SumitNaiksatampc_m: ah ok17:24
SumitNaiksatamhareeshp: yeah, my earlier question17:24
hareeshpSumitNaiksatam: yes ;)17:24
*** dboik has quit IRC17:24
*** SridharRamaswamy has joined #openstack-meeting-417:24
pc_mI posted on ML (a few weeks back) some steps Carl and I discussed, and I think Carl has it in his BP.17:24
carl_baldwinSumitNaiksatam: It is proposed to move away from the inheritence for FW.  Very soon.17:24
SumitNaiksatamcarl_baldwin: okay17:25
SumitNaiksatampc_m: so your patch is the first one to be reviewed in this chain, right?17:25
pc_mSumitNaiksatam: Sort of... Assaf's is dependent on mine. There are a few others as well.17:25
pc_mCarl has one to split up the L3 agent into modules.17:26
SumitNaiksatamah there is a topic for this:17:26
SumitNaiksatam#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/restructure-l3-agent,n,z17:26
carl_baldwinAs soon as we identify how FW needs to be notified and what callbacks are needed on the l3_agent and router then we should be able to break the inheritence relationship.17:26
pc_mTake a look at the BP first of all, so that we can get closure on carl_baldwin's BP.17:26
dougwigat the end of this discussion, i just want to make sure that my naive assumption that this work exists in parallel to the split is actually true, and we don't have to block on each other.17:27
SumitNaiksatamcarl_baldwin: pc_m: sounds good17:27
SridarKcarl_baldwin: currently it is mostly on the router_interface_add17:27
pc_mdougwig: good question, and concern17:27
SridarKso we should be able to do this with some minimal restructure of the code17:28
SridarK(FW agent code)17:28
SumitNaiksatamdougwig: i would tend to think that this refactoring of the agent has to be accomplished prior to the fwaas and vpnaas split17:28
SumitNaiksatamso that the respective agents can move with the services when the split happens17:28
dougwigwhat is the timeline for that?  alternately, i'm ok with a temporary circular dependency with the l3 agent17:28
dougwigtemporary == never shipped.17:29
SumitNaiksatamdougwig: yeah i agree, if there is a workaround, we should consider that17:29
xgermanalso since we are now splitting into 3 repos do we eed to split all at once?17:29
pc_mdougwig: We're hot on it now... not sure how long to tease it all apart.17:29
carl_baldwindougwig: This is currently our highest priority.  The bp just merged yesterday and so we should working on it in earnest.17:29
dougwigwe have this, split, rest refactor, and vendor split, all aimed straight at each other.  anything we can do to sever dependencies will make the impending management nightmare easier.17:30
xgerman+117:30
SridharRamaswamydougwig: +117:30
sbalukoff+117:31
s3wong+117:31
johnsom+117:31
SumitNaiksatamagreed, so it might help to get some of these things in first, so that we dont have too many loose ends after the split17:31
trinaths1+117:31
pc_m+117:31
dougwigSumitNaiksatam: that is the opposite of severing dependencies.  :)17:31
trinaths1(confused) what does a split mean?17:31
* pc_m +1 to dougwig's comment17:32
SumitNaiksatamdougwig: not all dependencies are equal17:32
dougwigtrinaths1: https://review.openstack.org/#/c/136835/17:32
pc_mSo REST refactoring starts next week at the mid-cycle?17:32
dougwiganytime you say "before" or "after", it is a dependency, and adds risk, IMO.17:32
SumitNaiksatammestery: if you are still around, is there a timeline we are targeting for the services’ repo split?17:33
trinaths1dougwig:  thanks17:33
dougwigit's next week, unless the rest refactor makes it impossible.17:34
xgermanSumitNaiksatam at the summit we said K117:34
carl_baldwindougwig: Did you have a plan for moving FW out of tree without breaking the inheritence hierarchy?17:34
xgermanI would still aim for that17:34
* carl_baldwin has not completely read the bp. Sorry.17:34
SumitNaiksatamthat would help to evaluate if its feasible at all to address any percieved dependenices for the split17:34
dougwigcarl_baldwin: yes, but you'll need a bucket handy.17:34
pc_m:)17:34
dougwigcarl_baldwin: the short-form would be treating the classes/repos as if they're not separate for the very short-term.17:35
*** mhanif_ has joined #openstack-meeting-417:35
trinaths1dougwig: okay. thanks for the clarity.17:35
dougwigthen the fw team can refactor to independence on their own timeline.17:36
* carl_baldwin wonders where he left that bucket. ;)17:36
dougwigi did warn you.17:36
mesterySumitNaiksatam: The work will be done next week in SLC17:36
carl_baldwinSo, initially, the two repos are co-dependent?17:37
SumitNaiksatamso the idea would be that neutron would depend on adv services’ repo, and adv services’ repo would depend on neutron?17:37
SumitNaiksatamcarl_baldwin: yeah, you summarized it better :-)17:37
dougwigcarl_baldwin: until the l3 refactor is done, yes.  that's the only circular link that i know of.17:37
carl_baldwindougwig: I think that is fine for the (very) short term but I’ll be looking again for the bucket if Kilo ships like that.17:37
dougwigi don't think we can allow kilo to ship like that.17:37
SumitNaiksatami guess we would need the co-dependency would be needed regardless of the L3 agent dependency issue17:38
SumitNaiksatam* i guess the co-dependency would be needed regardless of the L3 agent dependency issue17:38
dougwigonly for the upgrade scenario.  the plan is to have a hacking rule to prevent any other circular usages.17:38
dougwigwith an exception for l3 for now17:38
SumitNaiksatamdougwig: okay17:39
*** mhanif__ has joined #openstack-meeting-417:39
SumitNaiksatamso if the spin out is planned for the next week, i am guessing that is probably too short a time frame to achieve the l3 agent refactoring17:40
*** ivar-lazzaro has joined #openstack-meeting-417:40
carl_baldwindougwig: okay.  Does it mean more complexity in the build / test environment to support this co-dependent thing?17:40
*** mhanif_ has quit IRC17:40
pc_mSumitNaiksatam: yup17:40
dougwigno.  the circular link is already there for the upgrade scenarios.  it just means abusing it slightly for fun and profit.17:40
dougwigthe only extra work is the exception to the new hacking rule17:40
*** markmcclain has quit IRC17:41
*** ivar-lazzaro has quit IRC17:41
*** mhanif has quit IRC17:41
*** ivar-lazzaro has joined #openstack-meeting-417:42
carl_baldwindougwig: okay.  I’m okay going forward with that.  We can rebase our work to react to it.17:42
SumitNaiksatamperhaps we can set the services’ agents (fwaas/vpnaas) as a target for K2, that way we are more or less guaranteed to get it done in Kilo17:42
SumitNaiksatamif it lands earlier, great, but we can proceed with the split regardless17:43
dougwigi'll include this refactor and breaking this link in the split timeline.  for K2 as SumitNaiksatam suggests?17:43
SumitNaiksatamdougwig: i think that will be good to call out17:43
xgerman+117:43
dougwigwill do.17:43
SumitNaiksatamdougwig: at least it identifies what we need to follow up on after the split as an immediate requirement17:44
dougwiglook for a spec with a detailed roadmap by lunchtime.17:44
carl_baldwinSumitNaiksatam: I’d like to target an initial break out of the inheritence hierarchy for a couple weeks from now.  I’m not sure how much work will be needed to get to where you would like the service agents to be.17:44
SumitNaiksatamdougwig: thanks17:44
*** shwetaap has joined #openstack-meeting-417:44
SumitNaiksatamcarl_baldwin: agreed, i think, like SridarK mentioned, on the fwaas side we dont anticipate it to be as much17:44
carl_baldwinI’m focused on detangling the L3 agent first.  Service agents second.17:44
SumitNaiksatamperhaps pc_m can talk to for the vpn side of things17:44
carl_baldwinSumitNaiksatam: dougwig: +117:44
SridarKSumitNaiksatam: carl_baldwin: yes should not be too bad on FW17:45
*** mhanif__ has quit IRC17:45
SridarKI have probab jinxed it by saying that. :-)17:45
SumitNaiksatamokay we have 15 mins left, and we haven’t ye reached “flavors” :-)17:45
SridharRamaswamySumitNaiksatam: pc_m: i can help out if any vpn work spills over17:45
pc_mI don't think there is too much on VPN. only a handful of notifications.17:45
sbalukoffHeh!17:45
SumitNaiksatamSridharRamaswamy: pc_m: okay thanks17:45
SumitNaiksatam#topic Flavors17:46
*** openstack changes topic to "Flavors (Meeting topic: Networking Advanced Services)"17:46
SumitNaiksatam#link https://review.openstack.org/#/c/10272317:46
SumitNaiksatamthe spec has been repurposed from Juno ^^^17:46
*** shwetaap1 has joined #openstack-meeting-417:46
sbalukoffIt's back from the grave!17:46
dougwigand it wants your brains17:46
* sbalukoff prepares his pitchfork and torch again17:46
dougwigerr, eyes.17:46
dougwigi meant eyes.17:46
sbalukoffYes, eyes.17:46
*** mwang2 has joined #openstack-meeting-417:46
SumitNaiksatamdougwig: thanks for resurrecting it in time for the SPD17:47
johnsomMmmm, the flavor...17:47
dougwigit's roughly similar to mark's spec from juno.  did anyone have major issues with that one?17:47
dougwigand by roughly, i mean almost entirely identical.17:47
xgermanI loved it@@17:47
SumitNaiksatamnot to rat hole into names, but i believe there were some suggestions to drop the use of “flavor” terminology in general in OpenStack17:47
dougwigdo we have a good alternative?17:48
SumitNaiksatamif those still persist, perhpas they will show up early in the review17:48
SumitNaiksatamdougwig: not sure, i was just trying to look up the threads that i recall reading a week or so back17:48
sbalukoffIf we want this approved before the SAD date, those reviews / objections better come quick!17:48
SumitNaiksatamsbalukoff: agree17:49
*** shwetaap has quit IRC17:49
dougwigsbalukoff: +10017:49
SumitNaiksatamdougwig: will look up and post if i can dig it out17:49
dougwigSumitNaiksatam: thanks17:49
SumitNaiksatamanything more of “flavors”?17:49
SumitNaiksatamnot sure if people had a chance to read it since it was resurrected17:50
sbalukoffWell, they should take the opportunity now. :)17:50
* pc_m unfortunately not yet17:50
SumitNaiksatamok moving on17:50
SumitNaiksatam#topic Open Discussion (and any FWaaS/LBaaS/VPNaaS updates)17:51
*** openstack changes topic to "Open Discussion (and any FWaaS/LBaaS/VPNaaS updates) (Meeting topic: Networking Advanced Services)"17:51
dougwigfor lbaas updates, scroll up one hour to the meeting minutes.  :)17:51
SumitNaiksatamdougwig: :-)17:51
sbalukoffHaha17:51
trinaths1:)17:51
sunil_quick admin question: do we have a separate mailing list for advanced services?17:51
SumitNaiksatamsunil_: not really17:51
trinaths1SumitNaiksatam: When can I propose the FW Spec for K?17:52
SumitNaiksatamsunil_: in fact there isnt one for neutron either17:52
SridarKSumitNaiksatam: FWaaS putting together spec for FW insertion on router - should have it out by tomorrow17:52
SumitNaiksatamtrinaths1: you can and should before SPD (dec 8th)17:52
SridharRamaswamy my understanding is the BPs on the flight need to be reproposed against advanced services spec repo ? Is this correct ?17:52
SumitNaiksatamSridharRamaswamy: there isnt a separate repo17:52
xgermanthere is only one spec repo17:52
SumitNaiksatamokay, just to clarify for everyone’s benefit -17:52
dougwigSridharRamaswamy: no, only neutron-specs, and only re-propose if it was from juno and needs to be for kilo17:53
SumitNaiksatamif you need propose a spec, please propose a spec in Neutron Specs, nothing has changed17:53
trinaths1SumitNaiksatam: Okay, Here is my spec https://review.openstack.org/#/c/126187/17:53
glebore: FW insertion…17:53
glebohow are we doing on the use cases?17:53
gleboI've lost track since I went on TG break17:53
trinaths1SumitNaiksatam: please consider it for K.17:53
SumitNaiksatamif you need to send an email regarding advanced services, you send the email to the -dev ML, and prefix with:17:53
SridharRamaswamySumitNaiksatam: okay, I've a vpn spec already in neutron-spec/kilo #link https://review.openstack.org/#/c/136693/17:54
SumitNaiksatam[Neutron][advanced-services] or [Neutron][LBaaS] or [Neutron][FWaaS] or [Neutron][VPNaaS]17:54
SumitNaiksatamtrinaths1: SridharRamaswamy: great17:54
gleboSridarK:  I'll keep my eyes open for the insertion on router spec17:54
trinaths1SumitNaiksatam: :) reviews bless the specs..17:54
SumitNaiksatamon the fwaas side, SridarK will be posting a new spec for the insertion17:54
SumitNaiksatamglebo: ^^^17:54
trinaths1* reviewers17:54
SridharRamaswamydougwig: this is a new spec for Kilo17:54
SumitNaiksatamglebo: we sill need the use cases :-)17:55
SridarKglebo: yes have sent a reminder to FW folks on that17:55
SumitNaiksatampc_m: SridharRamaswamy: anything you would like to add for VPNaaS that is relevant to the rest of the adv services’ team here?17:55
pc_mnothing from me.17:55
SridharRamaswamynothing from me, waiting for all the refactors to fly in :)17:56
* pc_m still trying to get unburied from vacation and 4 days of no internet17:56
SumitNaiksatamaltighty, if nothing else, we can call it a wrap and take back  4 mins!17:56
pc_mwho hoo17:56
SumitNaiksatamthanks all for joining!17:56
SumitNaiksatambye17:56
trinaths1bye all17:56
SridarKbye17:56
dougwigbye17:56
SridharRamaswamybye all17:56
pc_mbye17:56
SumitNaiksatam#endmeeting17:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:56
openstackMeeting ended Tue Dec  2 17:56:41 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-12-02-17.01.html17:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-12-02-17.01.txt17:56
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-12-02-17.01.log.html17:56
*** pc_m has left #openstack-meeting-417:56
gleboSridarK:  SumitNaiksatam: hmmm…. brian gil-torres and I defined them all a few weeks back17:56
*** trinaths1 has left #openstack-meeting-417:57
gleboI'll circle back w/ him re: write up logistics17:57
SridarKglebo: did u send it out ?17:57
SumitNaiksatamglebo: yes please17:57
SridarKglebo: catch up on email17:57
glebothought he was taking first crack at text, but maybe I misunderstood. I'll ping him now and reply on ML17:57
* glebo really17:57
SridarKglebo: ok cool17:57
* glebo really needs to catch up on email. ha ha17:57
glebottys17:58
SridarKglebo: i have a thread going u can check and respond on that pls17:58
*** SridarK has quit IRC17:58
*** xgerman has left #openstack-meeting-417:59
*** markmcclain has joined #openstack-meeting-417:59
*** johnsom has left #openstack-meeting-418:00
*** nlahouti has left #openstack-meeting-418:00
*** ivar-laz_ has joined #openstack-meeting-418:02
*** ivar-laz_ has quit IRC18:02
*** ivar-laz_ has joined #openstack-meeting-418:03
*** ivar-lazzaro has quit IRC18:06
*** dboik has joined #openstack-meeting-418:06
*** glebo has quit IRC18:07
*** kobis has quit IRC18:08
*** evgenyf has quit IRC18:13
*** sunil_ has quit IRC18:18
*** markmcclain has quit IRC18:31
*** kobis has joined #openstack-meeting-418:32
*** glebo has joined #openstack-meeting-418:33
*** banix has quit IRC18:34
*** kobis has quit IRC18:39
*** kobis has joined #openstack-meeting-418:39
*** markmcclain has joined #openstack-meeting-418:41
*** shwetaap1 has quit IRC18:44
*** kobis1 has joined #openstack-meeting-418:44
*** kobis has quit IRC18:46
*** ivar-laz_ has quit IRC18:58
*** ivar-lazzaro has joined #openstack-meeting-418:58
*** dboik_ has joined #openstack-meeting-418:59
*** ivar-lazzaro has quit IRC18:59
*** ivar-lazzaro has joined #openstack-meeting-419:00
*** ivar-lazzaro has quit IRC19:01
*** ivar-lazzaro has joined #openstack-meeting-419:01
*** dboik has quit IRC19:03
*** SridharRamaswam1 has joined #openstack-meeting-419:04
*** SridharRamaswamy has quit IRC19:04
*** carl_baldwin has quit IRC19:08
*** banix has joined #openstack-meeting-419:15
*** SridharRamaswam1 has quit IRC20:01
*** dboik_ has quit IRC20:05
*** dboik has joined #openstack-meeting-420:06
*** dboik has quit IRC20:07
*** dboik has joined #openstack-meeting-420:07
*** SridharRamaswamy has joined #openstack-meeting-420:07
*** carl_baldwin has joined #openstack-meeting-420:19
*** glebo has quit IRC20:31
*** SridharRamaswamy has quit IRC20:47
*** SumitNaiksatam has quit IRC20:51
*** igordcard has quit IRC20:52
*** igordcard has joined #openstack-meeting-420:56
*** kobis1 has quit IRC21:01
*** SridharRamaswamy has joined #openstack-meeting-421:02
*** glebo has joined #openstack-meeting-421:04
*** ajmiller_ has joined #openstack-meeting-421:07
*** ajmiller_ has quit IRC21:07
*** ajmiller has quit IRC21:10
*** glebo has quit IRC21:17
*** hareeshp has quit IRC21:22
*** glebo has joined #openstack-meeting-421:22
*** SumitNaiksatam has joined #openstack-meeting-421:22
*** SridharRamaswamy has quit IRC21:44
*** SridharRamaswamy has joined #openstack-meeting-421:45
*** SridharRamaswamy has quit IRC21:51
*** SumitNaiksatam has quit IRC21:51
*** hareeshp has joined #openstack-meeting-421:52
*** SumitNaiksatam has joined #openstack-meeting-421:55
*** hareeshp has quit IRC22:00
*** carl_baldwin has quit IRC22:01
*** glebo has quit IRC22:07
*** jamiem has quit IRC22:10
*** SridharRamaswamy has joined #openstack-meeting-422:10
*** igordcard has quit IRC22:12
*** banix has quit IRC22:21
*** dboik has quit IRC22:26
*** dboik has joined #openstack-meeting-422:26
*** dboik has quit IRC22:28
*** dboik has joined #openstack-meeting-422:28
*** banix has joined #openstack-meeting-422:35
*** dboik has quit IRC22:44
*** dboik has joined #openstack-meeting-422:48
*** dboik has quit IRC22:48
*** dboik has joined #openstack-meeting-422:48
*** glebo1 has joined #openstack-meeting-422:56
*** glebo1 has quit IRC22:56
*** ajmiller has joined #openstack-meeting-422:56
*** dboik has quit IRC22:59
*** dboik has joined #openstack-meeting-423:01
*** ajmiller has quit IRC23:02
*** ajmiller has joined #openstack-meeting-423:04
*** banix has quit IRC23:11
*** glebo has joined #openstack-meeting-423:28
*** dboik_ has joined #openstack-meeting-423:31
*** dboik has quit IRC23:35
*** dboik_ has quit IRC23:36
*** glebo has left #openstack-meeting-423:36

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