Tuesday, 2014-09-02

*** sbfox has quit IRC00:12
*** sbfox has joined #openstack-lbaas00:43
*** mestery has quit IRC01:48
*** amotoki has joined #openstack-lbaas02:00
*** mlavalle_ has quit IRC02:07
*** mlavalle_ has joined #openstack-lbaas02:21
*** mlavalle_ has quit IRC02:32
*** mlavalle_ has joined #openstack-lbaas02:32
*** mlavalle_ has quit IRC02:33
*** mestery has joined #openstack-lbaas03:41
*** mestery has quit IRC04:08
*** rm_work|away is now known as rm_work06:32
*** sbfox has quit IRC06:57
*** openstackgerrit has quit IRC07:02
*** woodster has quit IRC07:15
*** jschwarz has joined #openstack-lbaas07:37
*** mestery has joined #openstack-lbaas08:03
*** mestery has quit IRC08:22
*** mestery has joined #openstack-lbaas08:23
*** mestery has quit IRC08:52
*** mestery has joined #openstack-lbaas08:52
*** cipcosma has joined #openstack-lbaas09:24
*** cipcosma has quit IRC09:26
*** rm_work is now known as rm_work|away09:37
*** rm_work|away is now known as rm_work09:59
*** rm_work is now known as rm_work|away10:13
*** mestery has quit IRC10:15
*** mestery has joined #openstack-lbaas10:15
*** mestery has quit IRC10:21
*** mestery has joined #openstack-lbaas10:22
*** amotoki has quit IRC11:22
*** mestery has quit IRC11:46
*** mestery has joined #openstack-lbaas12:06
*** mestery_ has joined #openstack-lbaas12:12
*** mestery has quit IRC12:13
*** woodster has joined #openstack-lbaas12:21
*** mestery has joined #openstack-lbaas12:35
*** mestery_ has quit IRC12:35
*** sbfox has joined #openstack-lbaas13:54
*** ptoohill has quit IRC14:01
*** openstackgerrit has joined #openstack-lbaas14:06
*** mestery_ has joined #openstack-lbaas14:31
*** mestery has quit IRC14:33
*** mestery_ is now known as mestery14:35
*** jschwarz has quit IRC15:04
*** markmcclain has joined #openstack-lbaas15:15
*** markmcclain has quit IRC15:16
*** markmcclain has joined #openstack-lbaas15:18
*** jorgem has joined #openstack-lbaas15:19
bloganhello everyone15:34
dougwigmorning15:45
dougwigi grabbed those bp's you mentioned last night.15:45
*** barclaac has joined #openstack-lbaas16:06
dougwigjorgem: hmm, mechanism is tasty.16:07
*** barclaac has quit IRC16:13
*** mestery_ has joined #openstack-lbaas16:16
*** sbalukoff1 has quit IRC16:18
*** mestery has quit IRC16:19
*** sbalukoff has joined #openstack-lbaas16:24
jorgemdougwig: you don't like gizmo?!?!?! ol16:25
jorgemlol16:25
jorgemman I was secretly going for that16:25
*** mestery has joined #openstack-lbaas16:26
*** mestery_ has quit IRC16:30
*** jschwarz has joined #openstack-lbaas16:44
*** jschwarz has quit IRC16:45
blogandougwig: awesome, thanks!17:56
blogananyone have any comments about the blueprint process in general?18:02
*** rm_work|away is now known as rm_work18:04
sbalukoffblogan: I'm looking into what you wrote earlier. I'll poke you if / when I have specific comments. :)18:10
blogansbalukoff: okay18:12
blogandougwig are you saying you like the term mechanism?18:13
*** rm_work is now known as rm_work|away18:14
openstackgerritBrandon Logan proposed a change to stackforge/octavia: Initial migration for database structure  https://review.openstack.org/11467118:41
*** mlavalle has joined #openstack-lbaas20:33
*** crc32 has joined #openstack-lbaas20:44
*** mestery has quit IRC20:53
*** mestery has joined #openstack-lbaas20:55
*** mlavalle has quit IRC20:56
*** mlavalle has joined #openstack-lbaas20:56
*** jorgem has quit IRC21:00
*** mlavalle has quit IRC21:02
*** mlavalle has joined #openstack-lbaas21:02
*** mlavalle has quit IRC21:04
*** mlavalle has joined #openstack-lbaas21:04
*** mlavalle has quit IRC21:17
*** mlavalle has joined #openstack-lbaas21:18
*** vivek-ebay has joined #openstack-lbaas21:41
*** vivek-ebay has quit IRC22:05
*** vivek-ebay has joined #openstack-lbaas22:07
dougwigblogan: yes, i like mechanism or appliance or backend about 1000x more than device.22:22
openstackgerritTrevor Vardeman proposed a change to stackforge/octavia: Initial creation of db models, modules, and tests  https://review.openstack.org/11671822:24
dougwigof course, i like vm and container the most, and i seem to be in a minority there.22:25
blogani think appliance or backend is the best22:26
*** sballe_ has joined #openstack-lbaas22:27
dougwigmy only problem with appliance is that if octavia eventually becomes the front-end of openstack lbaas, then we'll be shunting to hardware appliances at the same layer, or software appliances one layer deeper.22:27
sbalukoffdougwig: I don't quite follow why that's a problem.22:28
sbalukoffdougwig: Also, I actually don't want Octavia to be the front-end for OpenStack LBaaS. Even if the two projects are run by essentially the same people, I think they should probably remain separate long-term.22:29
sballe_was listening on the old lbass channel. I am usign an old laptop and I guess I hadn't updated all the channels :-( I am back :-)22:29
dougwigthere's a lot that hardware appliances don't need: scheduler, nova magic, HA monitoring, etc.  so if we eventually plumb those in, we will have two depths of backends, so to speak.  and one is already well known as "appliance".22:30
dougwigsballe_: welcome back22:30
sballe_dougwig, :-)22:30
sbalukoffAs someone pointed out, among other things, Octavia is a framework for managing a whole bunch of load balancer virtual appliances.  A hardware solution is fundamentally incompatible in many ways with that model. But both can certainly do load balancing.22:30
dougwigsbalukoff: not that i'm advocating merging.  just a possible naming collision that seems pointless to bake in, when there are like 20 possibilities.22:30
sbalukoffdougwig: I hear you.22:31
sballe_sbalukoff, I understand that YOU might not want the two projects merged but other might22:31
sbalukoffsballe_: I've yet to hear a good technical reason why they ought to be merged.  *shrug*22:32
sbalukoffBut I think I just threw out one that is a good reason not to merge. :P22:33
sbalukoffI suspect there are others.22:33
sballe_sbalukoff, I think we just have different goals with these projects and that is naturla given that we are in different businesses22:33
dougwiggauntlet thrown.  if octavia eventually has its own rest api, keystone plumbing, cli, etc, then it might be expedient to simply make it the basis of openstack lbaas, especially as the ref driver is already baked in.  the objects the user interacts with having nothing to do with virtual appliances on the backend.22:33
sballe_The problem I have with not merging Octavia into the incubator LBaaS project is that we could end up with the existing reference implementation being deemed good enough and at that point Octavia will be a Stackforge project with no hope of becoming part of OpenStack.22:34
dougwigsbalukoff: again, i'm not advocating that.  but there are reasons both ways.22:34
sballe_but you all know my opinion on this now22:34
sbalukoffsballe_: This harkens back to your mandate to only use openstack-branded products.22:34
blogansballe_: if the goal is for spinning out of neutron then gettign Octavia into the LBaaS tree will be fairly easy22:35
dougwigblogan: +122:35
sballe_blogan, yes but sbalukoff just said he is not interested in that22:35
sbalukoffsballe_: Er... no I didn't?22:35
* sballe_ looking back in the IRC to find where I thought sbalukoff said that22:36
blogansballe_: then the only real question is should it be in the same tree or not, and if its not in the same tree then will become an openstack project22:36
sbalukoffsballe_: I have no interest in getting burnt again on this project mostly be introducing leadership here who don't have its best interests in mind (or are too distracted with other things to prioritize it.)22:36
sbalukoffI really, *really* don't want to get burnt again, and especially be Neutron core leadership. :/22:37
blogansbalukoff: are you saying you'd be fine with octavia in the same tree as LBaaS if LBaaS got spun out and governed itself?22:38
sbalukoffblogan: Yep.22:38
sballe_blogan, +122:38
bloganexcellent22:38
blogannow do we all agree we want to spin out?22:38
sbalukoffYep.22:38
sballe_sbalukoff, blogan Wow we are in agreement :-)22:38
sbalukoffI think we've been violently agreeing most of the time.22:39
sballe_Spin out of the Neutron: YES Spin out of Networking Program: No I believe LBaaS belogn there22:39
sballe_sbalukoff, I agree :)22:39
sbalukoffI just am really, really not game for putting this project in a position where it can either become a political pawn, or red-headed stepchild of Neutron leadership.22:39
sbalukoffWe gave them the benefit of the doubt once.22:39
dougwigi do want to see the incubator in action for a few months.22:39
sbalukoffThey need to earn that trust back again if they want to have a say in this project. :/22:40
sballe_dougwig, +122:40
blogani think we're all fine with reamining in the Networking program as long as we can govern ourselves.  Though being under the networking program will probably have some other governing body but I'd be fine with dealing with that22:40
sbalukoffIt all has to do with what degree of autonomy we enjoy.22:41
sbalukoffI like the technical advice and experience the Neutron folks bring.22:41
bloganyep22:41
sbalukoffI don't like the politics.22:41
dougwiglet's not devolve into another incubator rant.  there are reviews to be done.22:42
sbalukoffdougwig: +122:42
sbalukoffBut, I'd like to see this talk of a merge put to rest until we actually have something that's a lot closer to being something that could be merged.22:43
sbalukoff(I think it's pretty distracting from actually making the product / making the product better.)22:43
sballe_sbalukoff, +1 on  the technical advice and experience the Neutron folks brin22:43
bloganwell i think the end goals should be known to everyone so if those goals are not in line with some then why would they want to contribute to something they can't use?22:44
sballe_blogan, +122:44
bloganso i see that as a reason this discussion should happen, but I think we just needed to state our goals clearer22:45
sbalukoffblogan: Is anyone here advocating a load balancer that isn't merged into OpenStack in some fashion in the long run?22:45
dougwigsbalukoff: some company's involved here might need more of the process laid out, for their management or whatnot.  it's not code, sure, but let's get the question answered for them and move on.22:45
sballe_blogan, I totally agree with that22:45
sballe_dougwig, +122:45
blogansbalukoff: no but I can see how the confusion could happen before this conversation that Octavia should just remain in stackforge22:45
sballe_Also while we are working on Octavia in Stackforge what would prevent somebody from coming in an redoing the refrence implementaiton so it is good enought and bar the way for Octavia to make it in22:46
blogansballe_: good enough for whom?22:46
sbalukoffPoint number 1 in our constitution:22:46
sbalukoffOctavia is an OpenStack project22:46
sbalukoff-------------------------------22:46
sbalukoffThis means we try to run things the same way other "canonized" OpenStack22:46
sbalukoffprojects operate from a procedural perspective. This is because we hope that22:46
sbalukoffOctavia will eventually become a standard part of any OpenStack deployment.22:46
sballe_blogan, we ran into that situation when we tried to get libra accepted into openstack and we were told by the TC that the Neutron lBaaS was good enough22:47
bloganhahaha, thats funny22:47
sbalukoffsballe_: If someone wants to make an open source operator-grade load balancer faster than us to spite us all, I have no problem with that! We get to enjoy the fruits of that labor in any case.22:47
blogannot funny good, funny sad22:48
sballe_sbalukoff, is that even legal: Octavia is an OpenStack project?22:48
sbalukoffsballe_: What do you mean?22:48
sballe_I believe they are rules for what can be called OpenStack22:49
sbalukoffIt's a philosophical point. We're not making a legal statement there.22:49
sbalukoffIf they come to us and tell us to change that, that's fine.22:49
bloganunless you consider the constitution an advertisement22:49
sballe_https://wiki.openstack.org/wiki/Programs22:49
sbalukoffblogan: It'd be a pretty shitty advertisement. ;22:49
sbalukoff;)22:49
bloganyou'd need the micromachines guy to put that into a 30 second radio or tv spot22:50
sballe_sbalukoff, I understand what you are saying22:50
sbalukoffsballe_: If you have a problem with that wording, feel free to submit a gerrit change request.22:50
sbalukoff:P22:51
sballe_but that would probably have been ok a couple of releases ago but now the whole openstack thingy is pretty rigid22:51
sbalukoffsballe_: What is the point in bickering about this?22:51
sballe_sbalukoff, Let me just run it by our TC member22:51
sbalukoffSeriously?22:51
blogansballe_: do you know any more details on the Programs? that wiki is lacking any details22:51
sballe_sbalukoff, I understand you feel this is bickering... Sorry about that..22:53
sbalukoffsballe_: It's actually worse than that. I feel like these are supremely unimportant details that delay us from getting real work done.22:54
sbalukoffAgain, if someone has a problem with the wording in the constitution, I'll happily take a look at a gerrit review to change it, eh.22:54
sballe_sbalukoff, Will do22:55
sballe_sbalukoff, I will look into it since we need to make sure we comply with OpenStack policies. That is my last comment on this.22:56
sbalukoffsballe_: Thank you.22:57
bloganalright im out for now, ill be on later, probably start working on another blueprint23:00
sbalukoffblogan: Thanks!23:00
*** vivek-ebay has quit IRC23:01
dougwigsballe_: is there something specific, process-wise, that HP needs to see?  i don't think we're going to have any new answers any time soon.23:03
*** vivek-ebay has joined #openstack-lbaas23:12
*** rm_work|away is now known as rm_work23:16
sballe_dougwig I just chatted with sbalukoff about this.23:18
a2hillHe referenced 'micromachines' heh :) So, 'device' is out the window i assume? :D23:20
dougwigi hate 'device' with the passion of a thousand burning suns.  alas, i have but one vote to cast against it's mediocrity.23:21
sbalukofftoaster23:21
sbalukoffI'm now throwing my weight behind calling it the toaster.23:21
dougwigbattlestar-loadtaillica23:22
a2hillAll hail toaster!23:22
a2hilllol23:22
a2hillthat works too!23:22
a2hillI'm ok with whatever! The naming arguments always gets me, I see why theyre important to some degree, I'm just horrible at it and think its silly to spend too much time on things like that. JS23:23
a2hillbut battlestart-loadtallica sounds pretty slick ;)23:23
sbalukoffOnly two difficult problems in computer science:  Cache invalidation, naming things, and off-by-one errors.23:24
a2hill^^^23:24
a2hilllol23:24
*** vivek-ebay has quit IRC23:31
*** vivek-ebay has joined #openstack-lbaas23:32
*** markmcclain has quit IRC23:37
* rm_work just finished dealing with cache invalidation in python-barbicanclient, naming is a nice reprieve 23:37
*** mlavalle has quit IRC23:50

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