Tuesday, 2014-11-18

*** chuckC_ has quit IRC00:10
*** david-lyle is now known as david-lyle_afk00:13
*** ChuckC has joined #openstack-meeting-400:13
*** ChuckC has quit IRC00:25
*** SridharRamaswam1 has quit IRC00:29
*** SridharRamaswamy has joined #openstack-meeting-400:37
*** SridharRamaswamy has quit IRC00:42
*** ChuckC has joined #openstack-meeting-400:43
*** chuckC_ has joined #openstack-meeting-400:45
*** ChuckC has quit IRC00:48
*** ChuckC has joined #openstack-meeting-400:49
*** dboik_ has joined #openstack-meeting-400:58
*** SridharRamaswamy has joined #openstack-meeting-401:02
*** yamahata has joined #openstack-meeting-401:06
*** yamahata has quit IRC01:07
*** yamahata has joined #openstack-meeting-401:07
*** SridharRamaswamy has quit IRC01:29
*** mwang2 has quit IRC02:03
*** SridharRamaswamy has joined #openstack-meeting-402:24
*** SridharRamaswamy has quit IRC02:37
*** s3wong has quit IRC02:51
*** chuckC_ has quit IRC02:59
*** chuckC_ has joined #openstack-meeting-403:00
*** sbalukoff has quit IRC03:04
*** SumitNaiksatam has quit IRC03:14
*** SumitNaiksatam has joined #openstack-meeting-403:14
*** naohirot has quit IRC03:27
*** chuckC_ has quit IRC03:39
*** naohirot has joined #openstack-meeting-404:02
*** dboik_ has quit IRC04:29
*** sbalukoff has joined #openstack-meeting-405:03
*** s3wong has joined #openstack-meeting-405:16
*** s3wong has quit IRC05:21
*** SridharRamaswamy has joined #openstack-meeting-405:21
*** SumitNaiksatam has quit IRC05:24
*** SumitNaiksatam has joined #openstack-meeting-405:26
*** SridharRamaswamy has quit IRC06:06
*** igordcard has joined #openstack-meeting-409:45
*** naohirot has quit IRC10:27
*** pc_m has joined #openstack-meeting-411:25
*** pc_m has left #openstack-meeting-411:43
*** igordcard has quit IRC11:52
*** naohirot has joined #openstack-meeting-412:51
*** igordcard has joined #openstack-meeting-412:59
*** dboik has joined #openstack-meeting-413:13
*** dboik has quit IRC13:35
*** evgenyf has joined #openstack-meeting-413:51
*** mestery has joined #openstack-meeting-413:55
*** dboik has joined #openstack-meeting-414:02
*** s3wong has joined #openstack-meeting-414:05
*** vishwanathj has joined #openstack-meeting-414:26
*** david-lyle_afk is now known as david-lyle14:43
*** s3wong has quit IRC15:01
*** SumitNaiksatam has quit IRC15:05
*** naohirot has quit IRC15:06
*** vishwanathj has quit IRC15:08
*** ChuckC_ has joined #openstack-meeting-415:11
*** ChuckC has quit IRC15:11
*** ChuckC_ has quit IRC15:21
*** ajmiller has joined #openstack-meeting-415:39
*** blogan_mobile has joined #openstack-meeting-415:43
*** blogan__mobile has joined #openstack-meeting-415:48
*** blogan_mobile has quit IRC15:50
*** TrevorV_ has joined #openstack-meeting-415:51
*** kobis has joined #openstack-meeting-415:57
*** a2hill has joined #openstack-meeting-415:57
*** johnsom_ has joined #openstack-meeting-415:58
*** SumitNaiksatam has joined #openstack-meeting-415:58
*** jamiem has joined #openstack-meeting-415:59
sbalukoffIs the LBaaS meeting happening in here right now?16:00
johnsom_Should be16:00
evgenyfHi, should be16:00
jamiemgood morning16:00
dougwighiya16:00
dougwig#startmeeting neutron lbaas16:00
openstackMeeting started Tue Nov 18 16:00:54 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
*** pc_m has joined #openstack-meeting-416:01
*** dboik_ has joined #openstack-meeting-416:01
dougwig#topic Roll call and Agenda16:01
*** openstack changes topic to "Roll call and Agenda (Meeting topic: neutron lbaas)"16:01
johnsom_o/16:01
ajmillero/16:01
dougwig#link https://wiki.openstack.org/wiki/Network/LBaaS#Meeting_18.11.201416:01
a2hillo/16:01
sballeo/16:01
*** jorgem has joined #openstack-meeting-416:01
*** xgerman has joined #openstack-meeting-416:01
dougwigsbalukoff: yes, i was just spacing out in my chair.16:01
jorgemo/16:01
xgermano/16:01
SumitNaiksatamhi16:01
sbalukoffHowdy, folks!16:01
* pc_m lurking16:01
sbalukoffOnce again, thanks for changing the meeting time.16:01
TrevorV_o/16:02
dougwigit's 4pm here.  i'll be grateful next week.  :)16:02
dougwig#topic Announcements16:02
*** openstack changes topic to "Announcements (Meeting topic: neutron lbaas)"16:02
dougwiglatest v2 review to focus on:16:02
dougwig#link https://review.openstack.org/#/c/123485/16:02
xgermansbalukoff I take it you didn't go to the neutron meeting :-)16:02
jamiemo/16:02
dougwiganyone have anything else to announce?16:03
sbalukoffxgerman: Nope!16:03
dougwig#topic Advanced services split16:03
*** openstack changes topic to "Advanced services split (Meeting topic: neutron lbaas)"16:03
dougwigi'm going to defer to the recent neutron meeting here:16:03
*** rm_work has joined #openstack-meeting-416:03
dougwig#link http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-11-18-14.02.html16:03
dougwig#link http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-11-18-14.02.log.html16:03
rm_worko/16:04
dougwigthe short answer was, not much of an update yet.16:04
*** blogan_mobile has joined #openstack-meeting-416:04
*** dboik has quit IRC16:04
*** blogan_mobile has quit IRC16:05
*** blogan_mobile has joined #openstack-meeting-416:05
dougwigi want to say, IMO, we should *not* be stalling lbaas v2 or octavia while we wait on this split.16:05
xgermanI think we have time for the long answer16:05
*** yamahata has quit IRC16:05
sbalukoffdougwig: +116:05
xgermandougwig +1 -- but I am not sure how our chances us to make progress to get it merged without the split16:05
rm_workmy understanding (and the direction I was leaning) was continuing full steam on octavia but slightly stalling neutron-lbaas work >_>16:05
rm_workxgerman ++16:06
*** blogan has joined #openstack-meeting-416:06
bloganim here!16:06
dougwigwe still have our feature branch, so i don't see why we'd need to stall.16:06
xgermanyeah, we need to get everything merged into the feature branch.16:06
*** blogan_mobile has quit IRC16:07
rm_workwell, I'd much rather get 100% returns on Octavia work in the meantime, get that up and working, then focus on neutron-lbaas when we're in a better position to get things done quickly and effectively (when we know what's going on)16:07
rm_workbut16:07
rm_workwe do still need to keep an eye on it so we don't lose whatever momentum we gained with regard to making the split actually happen16:07
dougwigi don't think we need a lot of focus on lbaas; just enough to deal with -1's.16:07
blogangetting the reviews merged into the feature branch that have not will help16:07
xgermanblogan +116:08
*** blogan__mobile has quit IRC16:08
bloganand it won't take much time from our standpoint to push for that and to pester to people16:08
xgermanand I will see if I can get some of our QA look at v216:08
xgermanwe also want to try it in a bigger installation than devstack16:09
dougwigis ctracey around?  is he going to update the client/cli, or should we find someone else to pick that up?16:09
rm_workwell, the TLS stuff in neutron-lbaas is very much broken/old/WIP16:09
bloganwell that depends on how the client will get split as well16:09
sbalukoffdougwig: I'm guessing we should find someone else to pick that up.16:09
rm_workso I'll need to look at that again16:09
bloganrm_work: good point16:10
sbalukoffHe's been very distracted by other BBG priorities, and I don't realistically expect him to spend time on LBaaS in the near future.16:10
dougwigsbalukoff: ok16:10
dougwig#action dougwig coordinate someone to take over client/cli lbaas stuff, maybe16:10
blogani nominate sbalukoff16:10
xgerman(who can't program)16:11
dougwigrm_work: did evgenyf update the tis stuff?  or are you?  or someone else?16:11
evgenyfrm_work: Do you mean the Barbican Util?16:11
bloganlol he can program in perl16:11
rm_workhe said he CAN, just slowly and badly :P16:11
rm_workevgenyf: yes, because for one, it is no longer a Barbican Util16:11
sbalukoff:)16:11
sbalukoffrm_work: +116:11
rm_workthat whole thing is going to be replaced with CertManager (the interface that merged to Octavia for talking to SecretStore backends)16:12
bloganso we're saying that many of the reveiws that are currently ready for review in the feature branch are no longer valid?16:12
bloganas in they should be WIPs?16:12
rm_workpossibly16:12
xgermancan we mark them accordingly?16:12
a2hillfor the TLS ref impl the certmanager stuff is only real blocker16:12
a2hillif were still using that16:13
rm_workyeah dougwig took over ownership of all of them so only he can WIP :/16:13
dougwigdo we have a volunteer to fold that into the current review for the feature branch?16:13
* blogan shakes fist at dougwig16:13
dougwigrm_work: which do you want WIP'ed?16:13
rm_workhttps://review.openstack.org/#/c/123492/ needs it16:13
dougwig#action rm_work msg dougwig for WIP reviews16:13
rm_work /msg dougwig https://review.openstack.org/#/c/123492/16:14
rm_work#done16:14
dougwigwe need to fold the cert manager stuff into that one, right?16:14
rm_workyes16:14
dougwigany takers for that?16:14
rm_workA large amount of that code is going to be straight up replaced16:14
bloganthat would also kind of make the needed by review a WIP as well16:14
rm_workI had assumed I would do it16:14
evgenyfdougwig: I will WIP TLS too16:15
bloganevgenyf: thanks16:15
dougwigi had hoped; wasn't sure if you had cycles.16:15
rm_workwell, it all depends on priority :)16:15
rm_workif we say this is a priority, I can get on it ASAP16:15
dougwigi'm going to wager that octavia 0.5 is higher priority, due to the uncertainty.  but if you get some cycles.16:15
dougwiganyone else have an opinion on that?16:16
blogani think making it a priority bc i dont want the split happening if these reviews do not get merged in16:16
xgermanblogan +116:17
blogani mean i dont watn the split dependent on these reviews16:17
sballeI agree16:17
evgenyfCan you please point me to the Octavia CertManager code?16:17
bloganof course the bigger bottleneck will be getting core review time, per usual16:17
rm_workevgenyf: https://review.openstack.org/#/c/131889/16:17
rm_workevgenyf: ignore anything about CertGenerator16:17
rm_workwe only need CertManager16:18
dougwigrm_work: have you talked to the oslo folks at all about a common cert client library?16:18
dougwig(maybe that could be you!)16:18
rm_workdougwig: yes, it's going to be a new project, probably named "Castellan"16:18
rm_workevgenyf: https://review.openstack.org/#/c/131889/9/octavia/certificates/manager/cert_mgr.py16:18
evgenyfrm_work: thanks16:18
rm_workvery simple interface16:18
sbalukoffHuh.16:18
rm_workdougwig / sbalukoff: Castellan (manager of a castle) :P16:19
rm_workstarting from Cinder's KeyMgr interface, rolling Cert support into it16:19
rm_workis "the plan" right now16:19
xgermanCastellan :-)16:19
dougwignice.16:19
dougwigrm_work: please update that review when you get some time.  i'd like to see things tied in a bow, like blogan, but i don't know what rax wants to see done first.  let us know if it's going to get starved for time.16:19
rm_workand when I say "the plan" I mean "my plan" because that is not yet "their plan" but i'm working on it :)16:19
rm_workyeah, I think I'm going to bump my current sprint topic a bit and work on that, it shouldn't take me too long16:20
blogandougwig: since rax will be using the v2 api and octavia, they're all kind of the same level of priority16:20
bloganat least that's what my advice would be16:20
dougwigblogan is always right.  except for the many times that he is not.  but he's right this time.16:21
* blogan chokes dougwig16:21
dougwigon that note...16:21
dougwig#topic Drivers, splitting status into operational and provisioning, and getting rid of DEFERRED16:21
*** openstack changes topic to "Drivers, splitting status into operational and provisioning, and getting rid of DEFERRED (Meeting topic: neutron lbaas)"16:21
dougwigwe talked about this at the summit.   was anyone against it?16:21
rm_workI never really got the rundown...16:22
xgermandidn't we decide to work with the ML2 folks and use task flow?16:22
rm_workbut I was sort of out of the loop of those internals, so don't mind me I guess16:22
bloganDEFERRED is the devil16:22
bloganxgerman this is a separate topic really16:22
xgermanI like to mix topics16:22
bloganyou like mix ins eh?16:22
rm_workI like to mix drinks, but 10am isn't the time for it :P16:22
dougwigwe are overloading the status field for operational and provisioning status, which results in ambiguity when something is provisioned but not yet useful.  thus, the DEFERRED state was born, and it is complex, and that complexity is owned by the drivers.  splitting that field makes the complexity disappear.16:23
rm_workdougwig: sounds good to me, as long as that description isn't leaving anything out :)16:23
bloganwell using taskflow would make the complexity owned by the plugin and not the drivers, but it still needs to go16:23
dougwigxgerman: yes, this is subtly inter-related to the other meeting topics.16:23
xgerman:-)16:23
dougwigok, let's go there16:23
dougwig#topic Drivers, potential taskflow model, all async16:24
*** openstack changes topic to "Drivers, potential taskflow model, all async (Meeting topic: neutron lbaas)"16:24
dougwigblogan, want to summarize this one?16:24
evgenyfdougwig: do we have some proposal paper for splitting status?16:24
bloganwell we would like to get all the db logic out of the drivers, and go to the exception model where the drivers throw an exception if something went wrong and the plugin catches tehse and updates the statuses accordingly16:24
*** kobis has quit IRC16:25
bloganlooks like using taskflow will be the best way to do this, it will make the lbaas API async no matter what driver is being used16:25
*** kobis has joined #openstack-meeting-416:25
a2hilltaskflow is still a wip?16:25
bloganthe problem is that neutron will be using taskflow as well and possibly in a different manner such that if we start using it now we may have to change how the drivers work as well when neutron's usage of taskflow happens16:25
dougwighttps://github.com/openstack/taskflow16:25
*** SumitNaiksatam has quit IRC16:26
dougwiga2hill: yes, that's really the only issue with using that model for drivers.  we can't just wait for it and neutron's use of it to be "done", so we need something in the interim.16:26
dougwighence, getting rid of deferred and then basically sticking with a driver model similar to v1 in the interim.16:27
a2hillAgreed, just wanted that fact stated. ;)16:27
blogandougwig: do you expect neutron to change how taskflow works or we will have to import a neutron.taskflow library to use it?16:27
xgermanI thought the ML2 plugin will use it16:28
bloganit will/is16:28
xgermanand we can use their model16:28
xgermanso we can just be like them?16:28
bloganyeah we need to talk to them some more16:28
dougwigi would expect we'd import or derive from some neutron base class, but it's really up in the air right now.16:28
xgermanwell, deriving from ML2 might be ok16:28
bloganto xgerman's point, if its good enough for ML2 to use right now, why wouldn't it be good enough for us to use?16:28
xgermanblogan +116:28
johnsom_blogan +116:29
dougwigit probably is; i don't much like re-implementing the glue twice in parallel, though.16:29
a2hilldougwig +116:29
blogani think more conversations with ML2 is warranted16:29
dougwig+116:29
*** kobis has quit IRC16:30
bloganand also markmcclain, just to gauge the stability of it16:30
bloganor volatility16:30
dougwigthis topic was meant as an intro for everyone, today.16:30
*** kobis has joined #openstack-meeting-416:30
dougwigok, while we're beating drivers to death...16:30
dougwig#topic v2 Object Model - Potentially simplifying the object relations or making the objects purely logical constructs16:30
*** openstack changes topic to "v2 Object Model - Potentially simplifying the object relations or making the objects purely logical constructs (Meeting topic: neutron lbaas)"16:30
xgermanwell, once you switch to exceptions the driver can throw operational and provisioning things and we can slot them into the right place16:30
dougwigduring the summit, we asked if we should further simplify the object model to not have as many root objects, which led to sam restating his desire to see the models with many-to-many, and have us basically pass full trees around.16:31
bloganevgenyf: do you think you could ask sam to send an email out with his proposal?16:32
dougwigIMO - in the interests of not rehashing decisions we've made, i'm fine sticking with the delicate balance that we ended up with for v2.16:32
bloganor if you know it well enough to send it yourself?16:32
evgenyfblogan: I will ask him16:32
dougwigother opinions/comments?16:32
dougwigevgenyf: ty16:32
xgermandougwig +116:32
sbalukoffdougwig: I'm all for not re-hashing decisions if there's not a compelling reason to.16:33
bloganthe compelling reason to me is that it is confusing16:33
xgermanalso we should wait until we have v2 ne in some trunk before we rock the boat16:33
bloganto an end-user16:33
sbalukoffxgerman: +116:33
bloganalso solving this could potentially solve the DEFERRED status issue as well16:33
bloganbut yeah none of these chanegs would go in until after the split happens16:34
*** banix has joined #openstack-meeting-416:34
bloganat least that is my interpretation of all of this16:34
dougwigvivek's ui concept could make any of these schemes palatable.16:34
dougwigunless i hear an objection, we'll wait for sam's email, and otherwise continue with the status quo.16:35
sbalukoffUltimately, I think it's a good idea to not have so many root objects. But again, does pushing for that now get us anything?16:35
blogansbalukoff: not right now, but after the split16:36
sbalukoffRight.16:36
dougwigagreed16:36
dougwig#topic Open discussion16:36
*** openstack changes topic to "Open discussion (Meeting topic: neutron lbaas)"16:36
dougwigdiscuss away...16:36
bloganit gets us something after the split in that we aren't drastically changing the v2 api from one release to the next16:36
blogandougwig: manish was the guy who was giving us a run down of taskflow and ML2 right?16:37
dougwigyes.16:38
dougwig#action blogan discuss taskflow drivers with ML216:38
xgermanplease include me -- I like taskflow :-)16:38
a2hillIm still a bit unclear, but are we going to get the .5 driver in as a ref impl 'before' the split so it gets merged in? Or do we want to go forward with the ref impl that is there (wip atm)?16:38
xgermanI think we will wait for the split and then decide what makes the most sense at that point16:39
dougwigno, we are not going to tie the octavia and neutron schedules together.  ref impl as is.16:39
a2hillFair enough16:39
a2hillThank you16:39
bloganyeah we shouldn't add any additional reviews to teh feature branch16:39
dougwiggoal 1: split.  goal 2: take over the world.16:39
xgerman+116:39
blogangoal 3: profit?16:39
a2hill:)16:40
dougwigany other items to discuss?16:40
a2hilladv services meeting next?16:40
dougwigyes16:41
sbalukoffa2hill: Yep16:41
dougwigalright folks, thanks, and bye.16:41
a2hillkk ;)16:41
sbalukoffSee y'all in 19 minutes!16:41
dougwig#endmeeting16:41
a2hill\016:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:41
openstackMeeting ended Tue Nov 18 16:41:24 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-11-18-16.00.html16:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-11-18-16.00.txt16:41
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-11-18-16.00.log.html16:41
jorgem\o/16:42
xgermano/16:42
*** jorgem has left #openstack-meeting-416:42
*** pc_m has left #openstack-meeting-416:43
*** TrevorV_ has left #openstack-meeting-416:43
*** ChuckC_ has joined #openstack-meeting-416:44
*** ChuckC_ is now known as ChuckC16:44
*** SumitNaiksatam has joined #openstack-meeting-416:50
*** pc_m has joined #openstack-meeting-416:54
*** pc_m has left #openstack-meeting-416:58
*** jackmccann has joined #openstack-meeting-416:59
SumitNaiksatamhi there17:00
xgermanhi17:00
dougwigo17:00
dougwigo/17:00
sballemorning17:00
SumitNaiksatamxgerman: dougwig blogan sballe: hi!17:00
sballe3rd meeting this morning :-)17:00
SumitNaiksatamsballe: :-)17:00
sbalukoffMorning again!17:00
SumitNaiksatamsbalukoff: hi17:00
*** vishwanathj has joined #openstack-meeting-417:00
SumitNaiksatamwe can decide how long we want this to be17:01
*** pc_m has joined #openstack-meeting-417:01
SumitNaiksatamvishwanathj: pc_m: hi17:01
SumitNaiksatamlets get started17:01
SumitNaiksatam#startmeeting Networking Advanced Services17:01
openstackMeeting started Tue Nov 18 17:01:20 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:01
johnsom_o/17:01
*** bobmel has joined #openstack-meeting-417:01
pc_mSumitNaiksatam: hi17:01
a2hillo/17:02
vishwanathjhello17:02
dougwigwhat is our agenda today?17:02
SumitNaiksatamthis discussion is a follow up to some of what happened in the neutron meeting earlier today17:02
bloganhello!17:02
SumitNaiksatam#info https://wiki.openstack.org/wiki/Meetings/AdvancedServices#Agenda17:02
rm_workp/17:02
rm_worko/17:02
SumitNaiksatamdougwig: the agenda is something that is up for discussion as well17:02
SumitNaiksatamfor those who missed the Neutron meeting in the morning, the short summary is that - there is no immediate update on the spin out/split17:03
*** kobis has quit IRC17:03
SumitNaiksatamthe plan is that an email will be sent to the ML with the proposal, and directed to the TC17:03
SumitNaiksatami believe we will proceed from there17:03
dougwig #link http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-11-18-14.02.log.html17:03
SumitNaiksatamdid i miss anything in that summary?17:03
dougwigthe log from that meeting17:03
SumitNaiksatamdougwig: thanks17:04
dougwigno, good summary17:04
* banix listening in from the last row17:04
*** s3wong has joined #openstack-meeting-417:04
SumitNaiksatambanix: :-)17:04
vishwanathjwhat is the impact to this team?17:04
s3wonghello, sorry, a little late17:04
SumitNaiksatamthe other thing that was dicussed is the charter/agenda for sub-team/groups17:04
SumitNaiksatams3wong: hi17:04
SumitNaiksatamvishwanathj: the spin ou/split is in the context of this team17:04
SumitNaiksatamvishwanathj: i.e. advanced services spin out17:04
SumitNaiksatamvishwanathj: so the impact is entirely on this team :-)17:05
SumitNaiksatamokay so regarding the sub-team/group -17:05
SumitNaiksatam#topic Team/Meeting logistics - should we be having this meeting17:05
*** openstack changes topic to "Team/Meeting logistics - should we be having this meeting (Meeting topic: Networking Advanced Services)"17:05
SumitNaiksatamso one things, i believe is firmly on the table now is that that services are being spun out in some form17:06
*** SridarK has joined #openstack-meeting-417:06
SumitNaiksatamand currently we udnerstand this to be a repo split, with a common repo for all the existing advanced services17:06
SumitNaiksatam*thing17:06
SumitNaiksatamsome of us came up with the following mission statement/charter for this new repo/project:17:07
SumitNaiksatamTo implement services and associated libraries that provide abstractions for advanced network functions beyond basic L2/L3 connectivity and forwarding.17:07
SumitNaiksatamthe above complements the current charter for neutron17:08
*** glebo has joined #openstack-meeting-417:08
bobmelSumitNaiksatam: Sounds pretty good to me,17:08
pc_m+117:08
SumitNaiksatambobmel: pc_m: okay17:08
blogan+117:08
SridarKSumitNaiksatam: i think that this is a good first stab it17:08
dougwig+`17:08
glebo'lo m8s17:08
dougwig+117:08
s3wong+117:08
SumitNaiksatamwe also have a critical mass of people working in each of the services and collectively as a services’ team17:09
sbalukoffYup!17:09
SumitNaiksatamso i would imagine that we have enough of a charter and team to form a sub-team/group?17:09
* glebo realises he just missed the "good first stab" and wonders if someone will repost via cut-n-paste, pls?17:09
SumitNaiksatamglebo: To implement services and associated libraries that provide abstractions for advanced network functions beyond basic L2/L3 connectivity and forwarding.17:09
pc_mI think so17:09
glebo+117:09
glebolooks great17:10
SumitNaiksatamso we agree that going forward we can represent this as a advanced services’ sub-team/group? (this might be obvious to most, but just making it clear)17:11
gleboanother way to say "advanced network functions" that is a bit more 'standard' jargon is: "service layer networking functions"17:11
sbalukoffSumit: Agreed!17:11
xgerman+117:11
SumitNaiksatamglebo: sure, we can discuss tuning the charter offline17:11
bobmel+117:11
pc_mSumitNaiksatam: yes17:11
SridarKSumitNaiksatam: +117:11
s3wong+117:11
glebo+117:11
sbalukoffglebo: Would 'service layer networking functions' include FWaaS?17:11
*** damon__ has joined #openstack-meeting-417:12
SumitNaiksatamsbalukoff: sure17:12
johnsom_+117:12
SumitNaiksatamokay, so the next part of the team logistics is the meeting17:12
SumitNaiksatam*this meeting17:12
SumitNaiksatamdo we need this meeting?17:12
sbalukoffOk, verbage is important because it's what people unfamiliar with the purpose of the team / project will use as a first introduction of what it's about. :)17:12
glebosbalukoff: yeah, but I take it back. Because if we use Service Layer Networking, then we'd have to change the name from Advanced Services to match, and I think we already have too much marketing familiarity with "advanced services". So let's stick with it17:12
SumitNaiksatamsbalukoff: true17:12
sbalukoffglebo: Right.17:13
SridarKglebo: +1 yes pls lets keep what we have now17:13
SumitNaiksatamreiterating my question - do we need this meeting?17:13
dougwigSumitNaiksatam: whether we needs this meeting, or can function inside the on-demand section of the neutron meeting, is a question that i don't think we can answer today.  i'd say keep it.17:13
sbalukoffAnyway: I think the meeting is important as a way for us to coordinate and make sure we're making progress in the direction we want to go.17:13
SumitNaiksatamdougwig: sbalukoff: okay17:13
sballedougwig: +117:13
sbalukoffIt could be a short meeting if we aren't making much progress / are blocked on stuff.17:13
s3wongSumitNaiksatam: from last experience, this meeting is absolutely needed if we are going to talk about flavor again :-)17:13
vishwanathj+117:13
s3wongs/last/past17:13
SumitNaiksatams3wong: :-)17:13
bobmel+117:13
SridarKSumitNaiksatam: yes i think this is good as we may not have enough bandwidth to discuss everything in the neutron mtg17:14
damon__I think we need, for we have so many advanced services17:14
xgermans3wong +117:14
gleboSumitNaiksatam:  we need this mtg at present to work on the split issues17:14
sbalukoffs3wong: +117:14
SridarKs3wong: :-)17:14
sballes3wong: +117:14
glebosplit issues first and foremost.17:14
SumitNaiksatamokay so i think there is fair agreement that on the team logisitics and this meeeting17:14
sbalukoffYep.17:14
damon__And maybe there are more and more advanced services since service chain release17:14
pc_ms3wong: +1 :)17:14
SridarKs3wong: lets go to Baskin Robbins :-)17:14
sbalukoffHaha!17:15
sballeSridarK: lol +117:15
glebowe need to get the "right" set of people into this meeting in order to really make progress on the split issue,17:15
SumitNaiksatamso i believe we can put this charter and reasoning on the adv services’ meeting and team wiki17:15
glebowhere "right people" includes17:15
SumitNaiksatamglebo: agree17:15
glebosome of the other cores and PTL and TC folks that are stake holders17:16
blogancharlie sheen?17:16
SumitNaiksatamblogan: :-)17:16
SumitNaiksatamglebo: that said17:16
glebomaybe what we need to do is craft a roster of who are the stake holders and then ensure we get buy in for participation17:16
sbalukoffblogan: Charlie Sheen? That's John F. Kennedy!17:16
SumitNaiksatamglebo: l believe the suggestion was that we have the discussion regarding the split in the main neutron meeting17:16
SumitNaiksatamwe use this meeting as a follow up17:16
gleboblogan:  charlie sheen:: role: marketing rep17:17
SumitNaiksatamto discuss between ourselves as to how to approach the work items17:17
SumitNaiksatamsince the split involves decisions that impact neutron and openstack as a whole17:17
sbalukoffsumit: +117:17
gleboSumitNaiksatam:  airtime and focus will be an issue in main neutron mtg. Just look at what happened today17:17
SumitNaiksatamso the discussion in best served in the neutron meeting17:17
SumitNaiksatamglebo: i hear you17:17
SumitNaiksatamglebo: but still i dont think this is left to us to decide :-)17:18
SumitNaiksatamokay moving to the split logistics17:18
glebohow do we mitigate that? failure to do so will, I'm afraid, push the split out of kilo17:18
SumitNaiksatamglebo: we will mitigate that by making sure we raise this topic during the neutron meeting17:18
*** SridarK_ has joined #openstack-meeting-417:18
SumitNaiksatamglebo: and also following up offline with the concerned folks17:19
s3wongglebo: you can certainly keep putting adv. services split as an agenda item on Neutron meeting until a point where the cores would have to give it some airtime :-)17:19
gleboSumitNaiksatam:  may be insufficient, but lets take it offline17:19
SumitNaiksatamthe first action item in that context will be to make sure that the email regarding the split gets sent to the ML asap17:19
SumitNaiksatamdoes everyone agree?17:19
glebos3wong:  true, and i think that is the plan so far17:19
xgerman+117:19
sbalukoff+117:19
damon__+117:19
glebo+117:20
vishwanathj+117:20
sballe+117:20
gleboitem owner?17:20
xgermanso how can we help mestery to get that done faster (ghostwrite the e-mail?)17:20
johnsom_+117:20
SumitNaiksatamonce the email gets sent, we can make enough noise to keep the thread alive and kicking, until everybody is sick and tired of us :-P17:20
SumitNaiksatamxgerman: that is certainly an option, if mestery is willing to take it :-)17:20
* glebo is pretty sure everyone is already sick and tired of us17:20
s3wongSumitNaiksatam: so based on this morning's meeting, mestery or markmcclain will send it out, according to russelb's request (of having one week ML time before being TC agenda item)17:20
SumitNaiksatams3wong: true17:20
gleboxgerman:  we can always provide some text and just say, "this may be of use"17:21
*** SridarK has quit IRC17:21
SumitNaiksatamxgerman: you want to take the AI to follow up with mestery on that?17:21
xgermansure, I can do that :-)17:21
SumitNaiksatamgreat17:21
SumitNaiksatam#action xgerman (among others) to follow up with mestery on sending the email regarding the adv services’ split to the ML17:21
SumitNaiksatamso lets say, as a team, we expect the email to be sent by the end of this week, fair?17:22
gleboI expect it to be sent tomorrow, latest17:22
vishwanathj+117:22
gleboTC needs to get it asap in order to get onto next week's TC calendar17:23
SumitNaiksatamglebo: yeah the earlier the better17:23
SumitNaiksatamglebo: agree17:23
glebo(per comments in Neutron this AM)17:23
SumitNaiksatamso latest by the end of this week17:23
blogani expect it later rather than sooner17:23
SumitNaiksatamblogan: :-)17:23
SumitNaiksatamso anything more to discuss in this specific context (next topic on agenda is about split logisitcs)17:24
SumitNaiksatam#topic Project spin out logistics17:24
*** openstack changes topic to "Project spin out logistics (Meeting topic: Networking Advanced Services)"17:24
bloganthere's a lot of unknowns on this one17:25
SumitNaiksatamso we are not taking any decisions here in this meeting (i dont believe we are empowered to either)17:25
SumitNaiksatamthis is just to get everyone up to speed in terms of what we have set in motion17:25
dougwigon the technical side, i've been working with infra and mark on this, and was planning to post a bp/spec with the gory details on friday (i'm traveling back stateside tomorrow/thursday)17:25
SumitNaiksatamdougwig: do you want to update the team on the two things you are doing?17:25
s3wongany updates from dougwig?17:25
s3wong(OK, there it is :-) )17:26
blogandougwig will you give us some updates?17:26
dougwigwe have an infra patch for the split itself; it is WIP pending knowing the real project name.17:26
SumitNaiksatamdougwig: has posted this patch for the split: https://review.openstack.org/#/c/132998/17:26
SumitNaiksatamthats the infra patch ^^^17:26
SumitNaiksatamhe is also working on a script to split the repo (and preserve the git history while doing so)17:27
xgermandougwig is a hero!17:27
*** hareeshp has joined #openstack-meeting-417:27
SumitNaiksatami believe this has been done before, and is on advice from the infra team17:27
SumitNaiksatamdougwig: yay, you rock!17:27
dougwigyep, it started from the oslo graduation script.17:27
bloganis the split going to be just cloning the neutron repo, or will it actually pull out the advanced services code?17:27
xgermancloning and then delete what we don't need17:28
dougwigtechnically, it's two repos, identifying the files you want from each, and then selectively pruning the history to remove what is no longer relevant.  you end up with two repos with the files you want, each with their own history, and then they diverge from there.17:28
bloganokay17:29
damon__Good17:29
SumitNaiksatamdougwig: so you would end up pruning in both the repos, right?17:29
dougwigcorrect17:29
SumitNaiksatamdougwig: okay, so from day one we will support adv services only from the spun out repo?17:29
dougwigcan you clarify that question?17:30
dougwigi think the answer to your question is 'yes', but i can interpret it a few different ways.17:31
SumitNaiksatamdougwig: so after you split (assuming it happens in the kilo time frame), we would no longer have the adv services code in the neutron repo, implying that, to deploy any adv services, you would have to use the adv servcies’ repo?17:31
dougwigthat's correct.17:31
xgerman+117:31
SumitNaiksatamokay17:31
xgermanbut we would still have to backport fixes to the old repo17:31
SumitNaiksatamthat would save us the trouble of maintaining in two places17:31
SumitNaiksatamxgerman: you mean stable branch?17:32
dougwigxgerman: for stable/juno, stable/icehouse, yes.17:32
xgermanwhat dougwig says17:32
SumitNaiksatamyeah, those branches would still have the adv services code artifacts17:32
SumitNaiksatamokay, i think so far the technical plan is clear to most people17:33
dougwigthere's other stuff, separate db, separate migration, tweak neutron to load out-of-tree plugins, but gerrit is likely a better place to discuss those.17:33
SumitNaiksatamnon-technical issue - what about naming?17:33
xgermanPositron?17:33
bloganpositron prob won't work17:33
xgerman:-(17:33
SumitNaiksatamblogan: really??17:33
bloganhttp://www.positronsoftwares.com/17:33
s3wongblogan: really, it is already taken?17:33
a2hillI couldnt find a class 9 trademark for positron17:34
SumitNaiksatambut isnt that different from just “positron”?17:34
a2hillsome were dead, but none active17:34
s3wongI guess that's the reason why only dougwig and I show up on #openstack-positron...17:34
SumitNaiksatama2hill: yey to that!17:34
SumitNaiksatam*yay17:34
xgermanyay17:35
blogandunno, but from talking to mark he didn't think it was plausible either17:35
bloganbc of that website17:35
*** dboik_ has quit IRC17:35
bloganthat doesn't mean its final though17:35
xgermanwell, we need somebody who owns a physics book for more particle names17:35
SumitNaiksatami would imagine there are legal folks employed by the openstack foundation to do this check, right?17:35
*** dboik has joined #openstack-meeting-417:35
bloganmuon17:35
bloganboson17:35
damon__ :-)17:35
bloganquark17:36
s3wongor we can go back to name after space/cosmic related stuff17:36
bloganSumitNaiksatam: yeah and mark will go through them17:36
xgermanhttp://en.wikipedia.org/wiki/List_of_particles17:36
SumitNaiksatamblogan: okay17:36
xgermanneutralino :-)17:37
bloganhe learned some lessons from the quantum name and renaming it17:37
bloganit was a cosmic chance that neutron was available17:37
*** dboik has quit IRC17:37
bloganneutrino17:37
SridarK_I think rackspace offered quark if i am not mistaken17:37
s3wongBackspace has trademark right on 'quark'?17:38
bloganyeah thats our internal neutron plugin and i'd hate to take it17:38
s3wongs/Backspace/Rackspace17:38
sbalukoffIt's not that hard to do a trademark search, eh.17:38
SridarK_s3wong: yes and they offered it17:38
bloganthat woudl be confusing to us internally!17:38
a2hillThey said quark was not trademarked yet17:38
bloganim easily confused17:38
xgermanso am I17:38
SumitNaiksatamokay so we can do some more homework on this17:39
sbalukoffIt's also not that hard to submit a trademark application. ;)17:39
SumitNaiksatambe ready with the options so that we can propose them at the right time17:39
SumitNaiksatamsbalukoff: want to try positron ;-)17:39
sbalukoff(Though it is time consuming)17:39
a2hillUsing TESS there are live ™ on positron but none for class 917:39
a2hillBut, i may be looking at things wrong17:39
SumitNaiksatamok moving on17:40
SumitNaiksatam#topic Mid cycle meet up proposal17:40
*** openstack changes topic to "Mid cycle meet up proposal (Meeting topic: Networking Advanced Services)"17:40
SridarK_#link https://etherpad.openstack.org/p/advanced-services-kilo-midcycle17:40
SumitNaiksatami guess this follows from the discussion with TC etc17:41
SumitNaiksatambut we can have a plan ready17:41
SumitNaiksatamSridarK_: thanks for the link17:41
glebowhat did folks think of my suggestion about Dec 11, to ensure we have the right cores and TC and PTL and such?17:41
bloganmestery mentioned an email today?17:41
glebo(back on name) orgasmatron?17:41
xgermanglebo you like skiing?17:42
SumitNaiksatamglebo: lol!17:42
SumitNaiksatamblogan: email to the ML?17:42
s3wongglebo: yeah... that's a REAL name :-)17:42
dougwigglebo: i think de-focusing that meetup is not a good idea, nor will it breed goodwill.  we should work to have those cores/ptl in attendance at whatever other meetup we do.17:42
SumitNaiksatamblogan: i meant to ask, is the email already sent to the ML?17:42
glebohttp://en.wikipedia.org/wiki/Orgasmatron_(disambiguation)17:43
glebopretty sure it's not trademarked17:43
bloganSumitNaiksatam: no i dont think it has yet, i just understood that is what he menat17:43
SumitNaiksatamblogan: ah okay17:43
glebo(from a woody allen move, sleeper, 1971)17:43
glebomovie17:43
* pc_m can we have one discussion?17:43
s3wongglebo: in addition to what dougwig said - after the split, we are independent projects with probably non-100%-overlapping contributors. And there is a great chance that some Neutron cores are just NOT too interested in adv. services17:44
blogans3wong: similar to how it is now :)17:44
glebodougwig:  ack. just thinking that so much travel may not be realistic for normal humans, esp those w/ families17:44
s3wongblogan: :-)17:44
SumitNaiksatami would hope that we can collectively decide the logistics of the meetup so as to give everyone’s opinion a fair chance17:44
xgermanthen we do it in MSP17:44
SumitNaiksatamglebo: completely understandable17:45
glebos3wong:  ack. Was hoping the meetup on 11th would be really tightly focused on split execution17:45
SumitNaiksatamxgerman: MSP?17:45
xgermanMinneapolis -- that's where Kyle lives17:45
SumitNaiksatamxgerman: ha :-)17:45
gleboxgerman:  ha ha17:45
dougwigglebo: i'm really interested in the vendor split, so a split meetup will be, umm, hard.  ;)17:45
SumitNaiksatamin -3017:45
xgermanI know the US by airport codes17:46
SridarK_xgerman: Minneapolis in Dec ?17:46
SridarK_:-)17:46
glebodougwig:  ha17:46
SumitNaiksatamanyway, we can leverage the above etherpad for some of these discussions as well17:46
johnsom_SridarK_ +117:47
SumitNaiksatamso in terms of agenda, i proposed some time for each of the adv services, just to cross-sync17:47
SumitNaiksatami am not sure we have enough time today17:47
dougwigfor lbaas, just scroll up one hour.  :)17:47
SumitNaiksatammay be we can do a quick 2 min rapid fire?17:47
s3wongSumitNaiksatam: is VPNaS going to be having their meeting during this hour :-)17:47
SumitNaiksatamdougwig: :-)17:47
SumitNaiksatams3wong: no :-)17:48
SumitNaiksatamso lets start in reverse order17:48
dougwigfor flavors, i spoke to eugene and mark, and will be re-proposing mark's spec for kilo/neutron, tweaking it for the feedback he got at the end.17:48
SumitNaiksatam#topic VPNaaS update17:48
*** openstack changes topic to "VPNaaS update (Meeting topic: Networking Advanced Services)"17:48
SumitNaiksatam#undo17:48
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x1dfca50>17:48
SumitNaiksatam#topic Flavors17:48
*** openstack changes topic to "Flavors (Meeting topic: Networking Advanced Services)"17:48
SumitNaiksatamdougwig: thanks for that update17:48
s3wongdougwig: who is going to pick up flavor in Kilo cycle?17:48
dougwigs3wong: me17:48
dougwigit's my turn to be full of holes.17:49
SumitNaiksatami also believe there is resistance to using the term “flavors” (sorry for bringing up a naming issue again)17:49
s3wongdougwig: because as we talked about during the summit, flavor is going to be part of Neutron instead of Positron17:49
xgermanlet's call it ice cream then17:49
SumitNaiksatams3wong: “flavor is going to be part of Neutron instead of Positron” which session was this discussed in?17:49
xgermanyeah, I also thought we own flavors17:50
sbalukoffs3wong: What was the reasoning there? So that people could use multiple types of SDN for layer 2/3 stuff in a single OpenStack installation or something?17:50
dougwigi'm going to propose it in neutron-specs, because no other specs repo exists yet.  i was punting on the question of where.17:50
s3wongSumitNaiksatam: the Friday one --- it was a 5 minutes discussion, due to the fact that flavor framework will affect L3 services17:50
xgermanFriday was very confusing...17:50
sbalukoffs3wong: Do you recall how they affect L3 services?17:50
SumitNaiksatams3wong: okay, i would have hoped “flavors” was inside positron, that made more sense to me17:51
sbalukoffYeah, Friday was pretty much useless for me.17:51
s3wongsbalukoff: yes, the main reason for that is flavor can affect whether we select a vendor driver that can both be a router and FW, for example17:51
sbalukoffI think most if not all of us wanted flavors to be in positron.17:51
sballeSumitNaiksatam: +117:51
sbalukoffs3wong. Aah.17:51
s3wongsbalukoff, SumitNaiksatam, dougwig: guys, it wasn't my idea :-) it was just being talked about during the meetup on Friday, I just reflected back on this17:52
xgermanmmh, but once we spin out that shouldn't be an issue any longer17:52
sbalukoffWell, there's always the possibility of making Neutron dependent on a shared flavors library which lives in positron once Neutron is in a position to actually offer that feature. :)17:52
s3wongI too would like this in Positron :-)17:52
SumitNaiksatams3wong: to that i would say, we should probably not be ttying “multi-service” appliances to flavors17:52
SumitNaiksatams3wong: understood17:52
sbalukoffSumit: Agreed!17:53
xgermanok, so we assume Friday never happened -- nobody remembers that day anyway :-)17:53
sbalukoffHaha!17:53
SumitNaiksatamsbalukoff: i like that idea17:53
sballelol17:53
bobmelSumitNaiksatam: What do you mean by the multi-service statement?17:53
SumitNaiksatambobmel: router + fw17:53
s3wongxgerman: well, when we get to FWaaS segment, the Friday meeting did have some important implication on what the FWaaS team needs to do prior to the split17:53
SumitNaiksatamthe simpler thing to do would be to have “flavors” per service-type17:53
sbalukoffAlso not a terrible idea.17:54
s3wongso there is still important things coming out of that Friday meetup :-)17:54
xgermanI have a selective memory17:54
sbalukoffThe flavor framework *ought* to be pretty light-weight.17:54
s3wongdougwig: is flavor per service-type the design now?17:54
sbalukoffBut then, I could be horribly underestimating that17:54
dougwigSumitNaiksatam: can you explain what you mean by that?  isn't the current proposal a per-service thing already?17:54
sballeDo we want to discuss  to have “flavors” per service-type?17:54
SumitNaiksatamsbalukoff: there could be a path for evolution :-)17:54
dougwigs3wong: yes, flavors specify a service, and a number of attached service profiles (meta-data configs)17:55
SumitNaiksatamdougwig: if its per-service, then it does not address “router + FW” , right?17:55
s3wongsballe: flavor discussion is always the safest bet to occupy the ENTIRE meeting time :-)17:55
dougwigthe service field is a string, and can be anything.17:55
sbalukoffHaha17:55
sballes3wong: :-)17:55
SumitNaiksatams3wong: from experience :-)17:56
bobmelSumitNaiksatam: Why not? There could be flaovrs for router and flavors for FW17:56
xgermanwell, let's wait for the proposal to surface so we can discuss it in gerrit17:56
xgermanalso we are T-417:56
s3wongxgerman: +117:56
SumitNaiksatambobmel: true, but s3wong was relaying the discussion specifying the need for a flavor which captures, both, a router and a firewall, as a one flavor17:56
SumitNaiksatamxgerman: +117:57
SumitNaiksatam#topic open discussion17:57
*** openstack changes topic to "open discussion (Meeting topic: Networking Advanced Services)"17:57
SumitNaiksatamwe have 3 mins17:57
s3wongSumitNaiksatam: that said, if we use flavor to select L3 service also, the argument remains17:57
bobmelI think it is preferable to keep flavors per service and not flavors that combines multiple services17:57
SumitNaiksatamso skipped the per service update (thanks to flavors!)17:57
SumitNaiksatambobmel: okay17:57
SumitNaiksatams3wong: yeah, something to consider17:57
s3wonganyway, let's get some quick updates on FWaaS --- the per-router work as well as the service group work, how are these going?17:57
SumitNaiksatams3wong: sure17:58
igordcardWhat about more general flavors that combine service flavors?17:58
SumitNaiksatamthe team has met on a couple of occasions to discuss this17:58
SumitNaiksatamSridarK_: will is in the process of translating this into a spec (i am referring to the FWaaS insertion)17:58
SridarK_SumitNaiksatam: and all yes working thru that17:59
SumitNaiksatamwe will also follow up on this topic on tomorrow’s FWaaS meeting, more details there17:59
SridarK_would prefer a more generic model (perhaps ports) rather than just a router_id17:59
xgerman+117:59
SumitNaiksatamservice groups spec is in review17:59
SumitNaiksatamSridarK_: +117:59
s3wongSridarK_: I (along with Kanzhe) vowed to NOT submit a service insertion spec unless and until Positron is spun off18:00
SridarK_s3wong: :-)18:00
SumitNaiksatamservice groups: #link https://review.openstack.org/#/c/131596/18:01
xgermanbye18:01
*** xgerman has left #openstack-meeting-418:01
SumitNaiksatamalright thanks everyone18:01
SumitNaiksatambye!18:01
SumitNaiksatam#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
SridarK_bye18:01
openstackMeeting ended Tue Nov 18 18:01:12 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-11-18-17.01.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-11-18-17.01.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-11-18-17.01.log.html18:01
*** pc_m has left #openstack-meeting-418:01
*** vishwanathj has left #openstack-meeting-418:01
SumitNaiksatammay be we did not need to end so abruptly18:03
SumitNaiksatamdid not realize that this channel is free most of the time :-)18:03
sballebye18:03
dougwiglol18:03
s3wongSumitNaiksatam: #openstack-meeting-4 is quite unoccupied :-)18:03
dougwigit is the wild west right now.18:03
sballelol18:04
SumitNaiksatamyeah, so used to watching over the shoulder on the other channels :-)18:06
*** evgenyf has quit IRC18:06
*** SridharRamaswamy has joined #openstack-meeting-418:15
dougwigbecause they're coming for you?18:16
*** ivar-lazzaro has joined #openstack-meeting-418:17
*** johnsom_ has left #openstack-meeting-418:27
*** SridharRamaswamy has quit IRC18:33
*** dboik has joined #openstack-meeting-418:34
*** SridharRamaswamy has joined #openstack-meeting-418:53
*** glebo has quit IRC18:55
*** ajmiller has quit IRC18:56
*** ajmiller has joined #openstack-meeting-418:56
*** dboik_ has joined #openstack-meeting-418:58
*** mwang2 has joined #openstack-meeting-418:58
*** glebo has joined #openstack-meeting-419:01
*** dboik has quit IRC19:01
*** SridarK_ has quit IRC19:02
*** glebo has quit IRC19:07
*** igordcard has quit IRC19:16
*** SridharRamaswamy has quit IRC19:31
*** SridharRamaswamy has joined #openstack-meeting-419:34
*** damon__ has quit IRC20:01
*** jamiem has quit IRC20:18
*** hareeshp has quit IRC20:21
*** dboik_ has quit IRC20:44
*** dboik has joined #openstack-meeting-420:44
*** jamiem has joined #openstack-meeting-420:49
*** hareeshp has joined #openstack-meeting-420:49
*** glebo has joined #openstack-meeting-420:57
*** glebo has quit IRC20:59
*** hareeshp has quit IRC20:59
*** glebo has joined #openstack-meeting-421:00
*** SridharRamaswamy has quit IRC21:05
*** SridharRamaswamy has joined #openstack-meeting-421:10
*** SumitNaiksatam has quit IRC21:11
*** glebo has left #openstack-meeting-421:19
*** SumitNaiksatam has joined #openstack-meeting-421:50
*** banix has quit IRC21:56
*** SridharRamaswamy has quit IRC22:00
*** dboik has quit IRC22:00
*** dboik has joined #openstack-meeting-422:02
*** banix has joined #openstack-meeting-422:33
*** SridharRamaswamy has joined #openstack-meeting-422:35
*** banix has quit IRC22:41
*** jamiem has quit IRC22:46
*** SridharRamaswamy has quit IRC23:07
*** ChuckC has quit IRC23:11
*** banix has joined #openstack-meeting-423:16
*** bobmel has quit IRC23:17
*** mwang2 has quit IRC23:29
*** banix has quit IRC23:32
*** dboik_ has joined #openstack-meeting-423:36
*** ChuckC has joined #openstack-meeting-423:37
*** dboik_ has quit IRC23:37
*** SridharRamaswamy has joined #openstack-meeting-423:37
*** dboik has quit IRC23:39
*** SridharRamaswamy has quit IRC23:42
*** SridharRamaswamy has joined #openstack-meeting-423:57
*** banix has joined #openstack-meeting-423:57

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