Monday, 2014-08-11

*** rm_you has joined #openstack-lbaas00:59
*** rm_you has joined #openstack-lbaas01:00
*** VijayB has quit IRC01:12
*** sbfox has joined #openstack-lbaas01:34
*** vivek-ebay has joined #openstack-lbaas01:55
*** sbfox has quit IRC02:00
*** VijayB has joined #openstack-lbaas02:01
*** vivek-ebay has quit IRC02:38
*** vivek-ebay has joined #openstack-lbaas02:40
*** VijayB has quit IRC02:40
*** vivek-ebay has quit IRC02:44
*** sbfox has joined #openstack-lbaas02:53
*** sbfox has quit IRC02:55
*** vivek-ebay has joined #openstack-lbaas03:30
*** HenryG_ has joined #openstack-lbaas04:14
*** ptoohill-oo has quit IRC04:15
*** HenryG_ has quit IRC04:16
*** HenryG has quit IRC04:16
*** HenryG has joined #openstack-lbaas04:18
*** HenryG is now known as HenryG_afk04:18
*** sbfox has joined #openstack-lbaas04:55
*** vjay has joined #openstack-lbaas05:07
*** sbfox has quit IRC05:17
*** vivek-ebay has quit IRC05:18
*** blogan_ has quit IRC05:55
*** evgenyf has joined #openstack-lbaas06:41
*** sbalukoff has joined #openstack-lbaas06:51
*** sbfox has joined #openstack-lbaas06:57
*** sbfox has quit IRC07:05
*** Youcef has joined #openstack-lbaas07:35
*** sballe has joined #openstack-lbaas08:55
sballeMorning :-) Back from vacation but still in Denmark.08:56
*** evgenyf has quit IRC09:20
*** evgenyf has joined #openstack-lbaas09:31
*** sballe has quit IRC10:24
*** sballe has joined #openstack-lbaas11:37
*** vjay has quit IRC11:56
*** HenryG_afk is now known as HenryG12:01
*** vjay has joined #openstack-lbaas12:01
*** sballe has quit IRC12:18
*** vjay has quit IRC13:03
*** vjay has joined #openstack-lbaas13:07
*** vjay has quit IRC13:27
*** vjay has joined #openstack-lbaas13:30
*** vjay has quit IRC13:37
*** vjay has joined #openstack-lbaas13:45
*** vjay has quit IRC13:50
*** vjay has joined #openstack-lbaas13:56
*** markmcclain has joined #openstack-lbaas14:28
*** xgerman has joined #openstack-lbaas15:02
*** xgerman has quit IRC15:05
*** xgerman has joined #openstack-lbaas15:07
*** sbfox1 has joined #openstack-lbaas15:07
*** sbfox2 has joined #openstack-lbaas15:11
*** sbalukoff has quit IRC15:12
*** sbfox has joined #openstack-lbaas15:12
*** sbfox2 has quit IRC15:13
*** sbfox1 has quit IRC15:14
*** sbfox has quit IRC15:24
*** sbfox has joined #openstack-lbaas15:24
dougwigmorning.  rough life you've got.  :)15:32
bloganmorning15:41
rm_workmorning15:51
*** sbfox has quit IRC15:54
*** markmcclain has quit IRC15:56
*** evgenyf has quit IRC15:57
dougwigblogan: you wouldn't have to give a provider for every object. just the first that's created (which could also default, if there's a default.)15:59
dougwigafter that, it's optional, since it's an error if it's different.15:59
dougwigi guess if you wait to link them, you'd have to give it on each.  double and triple extra belch.16:01
dougwigblech.16:01
bloganso if I create a pool with provider A and then I want to create a listener with the same provider and provider A is not default, wouldn't I still need to say the listener is using provider A?16:01
*** sbfox has joined #openstack-lbaas16:03
*** Youcef has quit IRC16:04
dougwignot if the listener references said pool; you could infer.16:05
bloganso if the listener does not specify the provider, then either the user's intent is that they want the listener to be on provider A or the default provider16:09
bloganwhich we won't know the exact intent16:09
dougwigwell, if it's linking into an existing object tree, there is only one valid intent.  but i kind of talked myself out of the auto-magic above when i referenced making them all unlinked and then linking.16:11
bloganyeah you're right on the one valid intent16:12
blogani don't understand your auto-magic scenario above16:12
bloganah now i do16:13
bloganif you just create without linking, but then expect to update and link16:13
bloganwhat happens on the create16:13
dougwigexactly.  which, btw, is a HUGE GIANT WART we will have to deal with when converting to many-to-many and multiple providers.16:14
bloganyes indeed16:14
bloganif we ever do16:15
*** vivek-ebay has joined #openstack-lbaas16:16
*** VijayB has joined #openstack-lbaas16:29
*** HenryG has quit IRC16:30
*** openstack has joined #openstack-lbaas16:32
*** mlavalle has joined #openstack-lbaas16:34
bloganmlavalle: saw your email, thanks for the updates, looking good16:36
bloganmlavalle: I have some code updates coming soon16:37
mlavalleblogan: glad to help :-)16:37
mlavalleblogan: great. every time you deploy new code, let me know and we can pass it thorugh the api test16:37
bloganmlavalle: will do16:37
*** HenryG has joined #openstack-lbaas16:39
bloganmestery: where there be discussions on the experimental out-of-tree proposal in the neutron meeting today?16:43
bloganmestery: s/where/will16:43
*** sbfox1 has joined #openstack-lbaas17:10
*** sbfox has quit IRC17:12
*** Youcef has joined #openstack-lbaas17:13
dougwigblogan: there's a gbp "post mortem" at the neutron meeting today.  i expect that and the various proposals for how to address it will happen then.17:15
*** sballe has joined #openstack-lbaas17:20
*** markmcclain has joined #openstack-lbaas17:30
*** vjay has quit IRC17:30
*** sballe has quit IRC17:39
*** vjay has joined #openstack-lbaas17:57
*** sbalukoff has joined #openstack-lbaas17:59
sbalukoffGuten Morgen!18:03
bloganoh look who it is18:03
blogandougwig: oh good ill shall participate18:07
bloganor just lurk18:07
dougwigi was planning to lurk18:10
*** sballe has joined #openstack-lbaas18:19
*** sbfox1 has quit IRC18:34
*** sbfox has joined #openstack-lbaas18:34
*** sbfox has quit IRC18:34
*** yfried has joined #openstack-lbaas18:38
yfrieddougwig: ?18:38
dougwighiya.18:38
dougwigyou'll get more opinions here.  :)18:38
dougwigmost of us don't monitor the neutron channel.18:39
dougwigthe db relation model changed majorly between v1 and v2, so the same interface won't work.18:39
yfrieddougwig: could you give an example? why can't the interface remain the same?18:40
dougwigyour point of it being confusing to have two at the same time is valid; at least if a version something doesn't make it obvious.  this is a can of worms here, which is why i wanted you to hear the responses in this channel.18:40
*** sballe has quit IRC18:40
yfrieddougwig: it feels to me like you would have neutron and novanetwork at the same time18:42
dougwigsure.  lots of little stuff.  there are new objects: loadbalancer and listener.  health monitors are no longer 1-to-many, so the associate/disassociate commands are gone, the current pool requires a subnet, that got moved to members, the current api/cli assumes pool as a root object, all objects are now independent.18:42
yfrieddougwig: you can't have them. that's why all novanetwork api calls are proxied to neutron. can't you do something similar with lbv1 if v2 is enabled?18:43
dougwigerr, i can't have what?18:44
yfrieddougwig: a deployment with both novanetwork and neutron18:44
dougwigit's a good question, and a constraint that i'd personally support.18:45
*** sbfox has joined #openstack-lbaas18:47
yfrieddougwig: personally i'd be more comfortable if you moved the lbaas api to a different module (same way nova api has module for servers and hosts) and have v1 and v2 clients implementing the same api calls for common methods such as create_pool18:48
yfrieddougwig: at run time the correct client is loaded and if listeners are called from v1 clients you get an appropriate exception18:48
dougwighow do you reconcile that with such massively different object structures?  i mean, the entry point would be named the same, but the json payload would be fundamentally incompatible.18:49
dougwigahh, so same endpoints, different payloads, fail if you detect the wrong version?18:49
dougwigi think that blogan tried something like that when he first starting adding the new api calls, and it got super messy. i'll leave it to him to comment, but the separate extension change was made at the meetup, after a discussion with mark and kyle.18:50
yfrieddougwig: I'm more concerned with pythonclients and cli18:51
*** sballe has joined #openstack-lbaas18:51
dougwigthat hasn't merged yet: https://review.openstack.org/#/c/111475/18:52
yfrieddougwig: I don't really care if the client implements a different rest call, json payload and uri, as long as the user executes the same command and the payload/uri are decided at runtime according to the client and the lbaas version active18:53
yfrieddougwig: making sure you don't run the risk of creating v1 pools with v2 vip (even if the call seems different)18:53
dougwigi'd suggest bringing that up in that review, which is where that interface lives.18:54
dougwigi'm not a strong enough advocate of the separate clients/commands to give you a good counter-argument.  :)18:54
*** sballe_ has joined #openstack-lbaas18:58
*** sballe has quit IRC19:01
*** sballe_ has quit IRC19:01
*** HenryG_ has joined #openstack-lbaas19:04
*** HenryG has quit IRC19:05
yfrieddougwig: tnx. I've tried to express my concern on the patch19:07
*** VijayB has quit IRC19:13
*** vivek-ebay has quit IRC19:23
*** markmcclain has quit IRC19:25
*** sbfox has quit IRC19:30
*** sballe has joined #openstack-lbaas19:36
sbalukoffyfried: Sorry, I must me missing half this conversation. What is it you're proposing?19:38
yfriedsbalukoff: see my review https://review.openstack.org/#/c/111475/319:39
yfriedI'd like to make sure that if v1 and v2 can't be active at the same time, and that if you use try to use v1 when v2 is active you'll get an appropriate error. just like you can't use neutron when novanetwork is on and vice versa19:41
sbalukoffSo, I think most people who have been working on Neutron LBaaS in the last few months would really like to simply ditch the v1 API, object model, etc. But what we learned at the mid-cycle meetup was that that wasn't going to fly and get accepted.19:41
sbalukoffNot that with the discussion about the neutron-incubator project it looks like we're going to get v2 at all... but I digress.19:42
dougwigright, but he's proposing that it gets disabled if v2 is active.19:42
dougwigwhich does seem reasonable.19:42
sbalukoffWhat we've been trying to do is move to the new object model and create a shim so that v1 commands (both API and command-line) operate on the v2 models.19:43
sbalukoffYep, it seems reasonable to me, too.19:43
sbalukoffAnd it would simplify things for us considerably.19:43
yfriedI'm concerned about users creating v1 objects and trying to match them with v2 objects and unable to figure out what's wrong19:44
sbalukoffWell, v1 objects shouldn't actually exist anymore after the v2 object code gets merged. Rather, v1 API / command-line should operate on v2 objects.19:44
yfriednot to mention the automation hell that's going to be raised if instead of importing v2 client in place of v1 we will have to search and replace all existing api calls19:45
sbalukoffBut you're right, it is dangerous to mix.19:45
yfriedsbalukoff: if that's the case then the proposed prefix of lb/lbaas difference is redundant. simply use the same api calls but direct them to the new version19:46
sbalukoffWell, if the neutron-incubator project comes to light, there's a pretty good chance that we'll lose all enthusiasm to make it backward compatible with v1 at all (be that shim layer or what have you).19:46
yfriedsbalukoff: glad to finally be understood. I was beginning to think I'm crazy19:47
sbalukoffyfried: Before we were being told that we're unlikely to get the v2 stuff into Juno, we were being told we couldn't do that in order to get the code into Juno.19:47
sbalukoffSo... there's history here that lead to this (IMO sub-optimal) direction....19:48
dougwigyep.  x1019:48
sbalukoffI actually feel like the discussion around neutron-incubator and whether there's any realistic chance of seeing v2 in Juno needs to be resolved before we can decide these kinds of things.19:49
sbalukoffBefore we can decide to change direction like you're proposing.19:49
dougwigit's not a direction change to do the intermediate step of only allowing one set of commands to be active.19:49
sbalukoffI think we're all most interested in getting v2 into Juno by jumping through the hoops set before us if there's a chance (we've been jumping through a LOT of hoops).19:50
sbalukoffBut... if that's not possible, then I would be all for doing this the "right" way. :P19:50
sbalukoffdougwig: Practically speaking, if neutron-incubator happens, I don't see the shim layer actually being written. (ie. in favor of simply dumping the v1 API / model for v2 when it "graduates")19:51
sbalukoffAnd if that's the case, then we've inherently solved this problem.19:51
sbalukoffv1 cannot be active at the same time as v2.19:51
dougwiguhh, no.  because they are separate api extensions today, you can load both.19:52
dougwigwhich leads to this:19:52
dougwighttps://www.irccloud.com/pastebin/Gf5wy0Tm19:52
sbalukoffdougwig: Right. We've got a mixed API / CLI right now because we were told that's the only way to get this in Juno.19:53
*** vivek-ebay has joined #openstack-lbaas19:53
sbalukoffMy point is, if Juno is off the table, then I don't see a point in doing that.19:53
sbalukoffDoes that make sense?19:53
dougwigright.  has nothing to do with the shim. and as an incubator, with a separate extension, that wouldn't change.19:53
sbalukoffOk, I don't think i'm following you.19:54
*** sballe has quit IRC19:54
yfriedsbalukoff: I'm no project manager, but if that's the case, I'd rather it not go in Juno. that risk and the reaction of disappointed customers is greater than the gain19:54
dougwigno, because going incubator doesn't make lbaas v1 go away as a supported api19:54
dougwigyfried: openstack lbaas customers are already a disappointed bunch.19:55
dougwig:)19:55
sbalukoffdougwig: +119:55
yfrieddougwig: wait until they here they are going to get a non-working v2 ... )19:55
sbalukofflbaas v1 is basically crap. I don't know of any operator of any decent size that actually uses it.19:56
*** markmcclain has joined #openstack-lbaas19:56
*** VijayB_ has joined #openstack-lbaas19:56
yfriedsbalukoff: think about those willing to give v2 a second chance and then failing to understand the API19:57
*** vivek-ebay has quit IRC19:57
*** vivek-ebay has joined #openstack-lbaas19:57
sbalukoffyfried: You raise a good point.20:01
bloganim back, sorry meeting20:01
dougwigyep, he does.20:02
blogancatching up one sec20:02
yfriedsbalukoff: tnx. glad I was able to talk to you guys while you are still open for discussion20:02
bloganyfried: you're suggesting that v1 API not be available at teh same time as v2 API and they both use the same prefix correct?20:05
bloganand the reason I did not do the shim is because the logic, edge cases, adn what not were pretty insane20:07
bloganand we didn't have time to get that figured out20:07
yfriedblogan: you are correct. not only the same cli names but also the same signatures in the pythonclient20:16
yfriedblogan: I understand you guys are working under a crazy time table, but I am thinking of the user experience and automation points of view20:17
bloganso if v1 pool has attributes v2 pool does not and vice versa, wouldn't that make the signatures be different?20:17
yfriedblogan: I'm sorry. I didn't understand you last comment20:17
bloganwell what do you mean by signature? method signatures or command line signature? or something different?20:18
yfriedblogan: let me correct myself - not method signature, but at the very least - method names20:18
yfriedsame for cli commands20:19
bloganah okay20:19
bloganyeah that can be done20:19
bloganwell20:19
bloganyes it can be done, as long as it is expected the parameters can and will be different20:19
bloganyfried: out of curiousity, how would the client handle v2 neutron vs v3 neutron? the same way?20:20
yfriedblogan: only if you must :) thank you20:20
yfriedblogan: I believe it should20:21
yfriedblogan: from user pov, upgrade should demand the least amount of change to he's setup, scripts and MO20:21
bloganyfried: our main problem was that this is akin to versioning an API, except lbaas is an extension of neutron20:22
bloganyfried: so accessing a new version of a REST API is usually done by adding another resource at the version uri level20:22
bloganyfried: but for the client, the lb can be chosen if v1 is active, and lbaas can be chosen if v2 is active20:23
*** crc32 has joined #openstack-lbaas20:23
bloganthat makes me wonder, is there a resource in neutron that will list out the active extensions20:24
bloganand if there is i'm an idiot for not already knowing that20:24
dougwighttps://www.irccloud.com/pastebin/zmakiKkv20:33
yfrieddougwig: sbalukoff: blogan: I need to go to sleep now. it was a good conv all around. please include me on further LB discussions20:34
yfrieddougwig: hehe20:34
dougwigyfried: they always happen in our IRC meeting, the ML, or via reviews.20:34
dougwigwe will not ignore your -1's.20:35
*** Youcef has quit IRC20:42
yfriedblogan: one last thing - I would like to see API&CLI for getting the active LB version from the SERVER20:50
yfriedblogan: do you think you could add that?20:50
yfriedit would help users/ automation a great deal20:50
bloganyfried: what exactly do you mean?20:55
bloganyou mean an api resource to give the version currently running?20:55
* sbalukoff returns from a meeting as well.21:00
*** tmc3inphilly has joined #openstack-lbaas21:01
*** HenryG_ is now known as HenryG21:01
*** vivek-ebay has quit IRC21:13
*** vivek-ebay has joined #openstack-lbaas21:24
*** fnaval has joined #openstack-lbaas21:28
*** sbfox has joined #openstack-lbaas21:34
*** vivek-ebay has quit IRC21:37
*** vivek-ebay has joined #openstack-lbaas21:42
*** vjay has quit IRC21:43
dougwiganyone curious as to the incubator debate who was not at the neutron meeting just now: http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-08-11-21.00.log.html22:04
blogansooo any takers on when a consensus on incubator agreement will happen?22:04
bloganactually I think the incubator will be easy to agree on, its just whether GBP should go in there22:04
blogancan't say I disagree with lbaas v2 going in22:04
tmc3inphillyquite honestly, EVERYTHING except what is core Neutron should go through this process22:05
tmc3inphillyand there should be strict guidlines that determine whether it should be a plugin/addon/driver/etc... or merely a consume of neutron22:05
tmc3inphilly*consumer22:06
dougwigwell, the greater problem is that in the context of "the cloud", having a single group for "the network" seems to be... optimistic.  i mean, we have like three groups for storage, and one for networking?22:06
dougwigbut i also hate duplication/waste, and oslo hasn't caught up yet.22:06
dougwigi like the network umbrella, it's just not ready yet.22:06
tmc3inphillyquite honestly, there should be a group for Layers 0 through 2, a separate group for Layer 3, and sepearate group(s) for layer 4 - 722:07
tmc3inphillyswitching and network ports is a completely different world from routing22:08
dougwigi don't think all of layer7 should be lumped together.  that's a bit broad.  ;)22:08
tmc3inphillyno that is why i left it as group(s) :-)22:09
dougwigoh, i see.22:09
dougwigskimmed to fast.  :)22:09
tmc3inphillyVPN, FW, LB are all network services/applications but should not be lumped together22:09
*** vivek-ebay has quit IRC22:10
tmc3inphillyelse we will end up where Nova was and Neutron is22:10
tmc3inphillylike a turtle on its back22:10
bloganneutron needs some cleaning upf irst for that to happen22:10
dougwigat the same time, those are small enough that they could share infrastructure and reviewers and get some cross-gain.  at the cost of independence.  and i guess the end of that road is the problem we're in now, too.22:10
bloganlots of hooks in the service cross talk code that doesn't go through the API22:10
tmc3inphillyAgreed22:11
*** vivek-ebay has joined #openstack-lbaas22:12
tmc3inphillyIndependence to promote stability and velocity, yet same sets of core reviewers to maintain consistency and perspective22:12
tmc3inphillyi think it is achievable22:12
tmc3inphillythe hard part is selling it to the masses22:13
*** fnaval_ has joined #openstack-lbaas22:28
*** fnaval has quit IRC22:29
*** sbfox1 has joined #openstack-lbaas22:30
*** sbfox has quit IRC22:30
*** sbfox1 has quit IRC22:37
*** tmc3inphilly has quit IRC22:41
*** sbfox has joined #openstack-lbaas22:45
sbalukoffdougwig: Thanks for the link to that transcript. I'll try to start attending the Monday Neutron meetings as well. :/22:59
sbalukoffAfter all, there clearly wasn't enough contention in that meeting.22:59
sbalukoff:P22:59
blogansbalukoff: i wonder if openstack would have exploded had you maded it23:00
sbalukoffHaha!23:00
sbalukoffblogan: for what it's worth, you asked the same questions and raised the same concerns I would have.23:00
sbalukoffYou just did it a lot nicer than I would have. ;)23:00
bloganlol23:00
bloganwell nicer doesn't always get answers23:00
*** vivek-eb_ has joined #openstack-lbaas23:00
sbalukoffHaha!23:00
*** vivek-ebay has quit IRC23:00
sbalukoffWell, I think there's nobody happy with how things have gone with the GBP discussion (on either side of "the aisle" as it were).23:01
blogani still don't think the incubator would have solved the situation GBP is in23:01
sbalukoffAnd I really dislike that it's going to affect how things are going for LBaaS as well.23:01
bloganeven though I think it is the right solution for neutron23:01
sbalukoffblogan: I agree23:01
sbalukoffIf people can't talk openly about their concerns, then process isn't going to help.23:02
bloganwell honestly, even if GBP didn't happen, I'm not so certain v2 would have made it in Juno23:02
sbalukoffblogan: I know, but as it is, there's basically zero chance.23:02
sbalukoffWhich is frustrating...23:02
sbalukoffmy mind keeps going back to the meeting in Atlanta where I told the core devs we didn't trust them to be able to deliver.23:02
sbalukoff:/23:02
sbalukoffAnyway...23:02
bloganlol23:03
sbalukoffThis also potentially affects where we go with Octavia.23:03
bloganI think we just stay the course with Octavia23:03
sbalukoffblogan: Well, there isn't much of a course right now...  not in code anyway, since everyone who is competent at coding has been doing so on Neutron LBaaS.23:03
bloganim sure your opinion is different but lbaas will still be useable when Octavia gets in a state that its useable as well.  It may not be in neutron proper at first though23:04
sbalukoffVERY frustrating, because if we'd actually just started with Octavia, we might be somewhere with it now. :/23:04
blogansbalukoff: call me an optimist (which many do) but the work done isn't going in the trash can23:04
sbalukoffOh, sure, it's not completely wasted. But it's certainly not the best way we could have been spending our time.23:05
sbalukoffAnyway... this is something I'd like to discuss at the Wednesday Octavia meeting.23:05
sbalukoffAlong with the v0.5 spec. Which... yes, I still haven't sent out yet. (Sorry!)23:05
* blogan shakes fist at the sky23:06
bloganWHY?!?!!23:06
bloganj/k23:06
sbalukoffHeh!23:06
bloganwe got a good run down on how we will do what we need to do with our network at rax today23:07
sbalukoffWell, trying to keep up with the GBP discussion, and Friday ended up essentially being a sick day to me. (Massive migrane). But anyway... those aren't excuses and I'm truly sorry it's not in y'all's hands yet.23:07
sbalukoffOh, good!23:07
bloganbut it does boil down so far, i'm sure there will be some caveats we aren't thinking about, to the vip being a floating ip in neutron23:09
bloganbut we'll have more details on wednesday23:10
rm_workblogan: http://i.imgur.com/2iRD7fm.jpg :P23:11
blogancould you describe that feeling to me? what it feels like to get a merge in?23:11
rm_workhehehe23:11
sbalukoffLOL23:12
rm_workit's wonderful :P23:12
rm_workalso the lady at the bakery looked at me funny23:12
bloganand rightfully so23:12
blogani don't know if you realize this, but everyone looks at you weird23:13
rm_work^_^23:13
*** vivek-eb_ has quit IRC23:19
*** vivek-ebay has joined #openstack-lbaas23:19
*** vivek-ebay has quit IRC23:20
*** vivek-ebay has joined #openstack-lbaas23:21
*** vivek-ebay has quit IRC23:22
*** vivek-eb_ has joined #openstack-lbaas23:22
rm_workhttp://www.huffingtonpost.com/2014/08/11/robin-williams-dead-dies_n_5670050.html :(23:23
*** vivek-eb_ has quit IRC23:23
*** vivek-ebay has joined #openstack-lbaas23:25
*** vivek-ebay has quit IRC23:25
*** vivek-ebay has joined #openstack-lbaas23:26
*** markmcclain has quit IRC23:27
*** vivek-ebay has quit IRC23:35
*** vivek-ebay has joined #openstack-lbaas23:36
*** fnaval has joined #openstack-lbaas23:44
*** ptoohill-oo has joined #openstack-lbaas23:47
*** fnaval_ has quit IRC23:47
*** ptoohill-oo has quit IRC23:56

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