Wednesday, 2014-09-03

*** vivek-ebay has quit IRC00:15
*** vivek-ebay has joined #openstack-lbaas00:17
*** vivek-ebay has quit IRC00:17
*** crc32 has quit IRC00:19
*** sballe_ has quit IRC00:22
*** sballe has joined #openstack-lbaas00:31
*** mestery has quit IRC01:31
*** mestery has joined #openstack-lbaas01:31
*** sballe has quit IRC01:32
*** mestery_ has joined #openstack-lbaas01:35
*** mestery has quit IRC01:37
*** vivek-ebay has joined #openstack-lbaas01:47
*** sbalukoff has quit IRC02:09
*** mestery_ is now known as mestery02:09
*** sbalukoff has joined #openstack-lbaas02:09
*** vivek-ebay has quit IRC02:19
*** sbfox has quit IRC02:39
*** woodster has quit IRC02:45
*** sbfox has joined #openstack-lbaas03:42
sbalukoffHey y'all! Finally got around to putting this together:  https://wiki.openstack.org/wiki/Octavia/Non-arbitrary_Decisions03:58
sbalukoffI imagine we'll make another entry there when we decide on what we're going to call the vm / container / appliance / device / whatever.03:58
bloganlol i was thinking the same thing03:59
bloganand also API look03:59
sbalukoffAPI look?04:02
bloganone root entity versus all being root04:02
sbalukoffOh, yes!04:02
sbalukoffIndeed we'll want to document that decision04:02
bloganbtw i'm starting on that as we speak, ill bring up what I believe we had consensus on in a thread on the ML once I get it set up04:03
sbalukoffSounds good!04:03
bloganit'll just be an operator API that only talks to the db for now, but it'd be nice to actually have something running04:05
sbalukoffGotta start somewhere.04:06
sbalukoffMaybe a no-op driver for Octavia?04:07
sbalukoff(er.. for the Octavia VM / device / thingy)04:07
blogannot a bad idea once the interfaces get created04:07
sbalukoffNo-op logging driver.04:07
sbalukoffWe've already done one of those, eh!04:07
blogandoug did!04:07
sbalukoffYep.04:07
blogani think the interface blueprints are low hanging fruit blueprints04:08
bloganso its something someone can do for first time coding04:09
bloganand i didn't want to take that04:09
bloganactually implementing a driver based on that will be the hard part (though the creating a good interface is not without its own obstacles)04:10
sbalukoffHaha! Yeah, I may end up volunteering for that since I could use some python practice.04:11
sbalukoffUnless I would be a bottleneck to others getting shit done.04:11
sbalukoff(It's always my first priority to make sure I can keep others busy. ;) )04:11
bloganI don't think it will be much of a bottleneck, nothing really depending on it just yet04:13
bloganplus you probably have a good idea on what these drivers should be doing, not exactly how they will do it04:14
sbalukoffCool beans.04:14
sbalukoffYes.04:14
*** vivek-ebay has joined #openstack-lbaas04:14
blogani just keep thinking of more and more blueprints!04:15
sbalukoffHaha!04:16
sbalukoffPlenty for people to pick through if they're looking for something to do, eh!04:17
bloganyou could say there is a plethora04:17
bloganhttps://www.youtube.com/watch?v=-mTUmczVdik04:18
sbalukoffOh, man, I haven't seen that movie in forever!04:18
blogani love that movie04:18
sbalukoffHehe!04:20
sbalukoffOk, I'mma head offline for a while, eh! Catch y'all later.04:21
bloganlater04:21
*** sbfox has quit IRC04:31
*** sbfox has joined #openstack-lbaas04:38
*** xgerman has joined #openstack-lbaas04:40
*** amotoki has joined #openstack-lbaas04:56
*** enikanorov__ has quit IRC05:23
*** sbfox has quit IRC05:37
*** vivek-ebay has quit IRC05:48
*** xgerman has quit IRC06:26
*** jschwarz has joined #openstack-lbaas07:49
*** amotoki has quit IRC08:52
*** markmcclain has joined #openstack-lbaas12:02
*** markmcclain has quit IRC12:02
*** HenryG is now known as HenryG_afk12:04
*** markmcclain has joined #openstack-lbaas12:04
*** enikanorov has joined #openstack-lbaas13:01
*** woodster_ has joined #openstack-lbaas13:12
*** enikanorov__ has joined #openstack-lbaas13:17
*** enikanorov has quit IRC13:19
*** vivek-ebay has joined #openstack-lbaas13:43
*** rm_work is now known as rm_work|away14:03
*** vivek-ebay has quit IRC14:18
*** HenryG_afk is now known as HenryG14:36
*** xgerman_ has joined #openstack-lbaas14:49
*** vivek-ebay has joined #openstack-lbaas14:54
*** sbfox has joined #openstack-lbaas14:57
*** jorgem has joined #openstack-lbaas15:02
*** Youcef has joined #openstack-lbaas15:07
*** jorgem has quit IRC15:09
*** ptoohill has joined #openstack-lbaas15:11
*** jorgem has joined #openstack-lbaas15:13
*** jorgem has quit IRC15:13
*** vivek-ebay has quit IRC15:21
*** vivek-ebay has joined #openstack-lbaas15:21
*** ptoohill has quit IRC15:32
*** jschwarz has quit IRC15:38
*** vivek-eb_ has joined #openstack-lbaas15:42
*** vivek-ebay has quit IRC15:44
*** vivek-eb_ has quit IRC15:46
*** mlavalle has joined #openstack-lbaas15:53
*** mlavalle has quit IRC15:54
*** mlavalle has joined #openstack-lbaas15:55
*** jorgem has joined #openstack-lbaas15:58
*** enikanorov has joined #openstack-lbaas16:00
*** pckizer_ has joined #openstack-lbaas16:08
*** ctracey_ has joined #openstack-lbaas16:08
*** ctracey has quit IRC16:08
*** dougwig has quit IRC16:08
*** enikanorov_ has quit IRC16:08
*** jkoelker has quit IRC16:08
*** pckizer has quit IRC16:08
*** ctracey_ is now known as ctracey16:08
*** jkoelker has joined #openstack-lbaas16:09
*** dougwig_ has joined #openstack-lbaas16:10
*** rm_work|away is now known as rm_work16:22
bloganhello16:35
rm_workhi16:39
*** vivek-ebay has joined #openstack-lbaas16:46
*** Youcef has quit IRC16:50
sbalukoff'allo!16:51
xgerman_blogan, morning!!16:56
dougwig_morning all.16:59
dougwig_xgerman_: the 0.5 review awaits your +A16:59
xgerman_coming...16:59
dougwig_everyone: please add your backend/vm/container/toaster naming input, as i want to drive that review to a close today: https://etherpad.openstack.org/p/octavia-backend-name16:59
sbalukoffWait...17:00
* dougwig_ waits17:00
*** dougwig_ is now known as dougwig17:00
sbalukoffHold off on the +A for a moment--  I noticed one other file that needs to be updated (waiting on the local tox run to complete before I push it up.)17:01
sbalukoffdougwig_: On that naming input thing, are we allowed to -1 ideas we particularly don't like, too?17:02
sbalukoffOr just +1 the ideas we like.17:02
sbalukoffOh, I see you already -1'ed one. XD17:03
xgerman_too late +A17:07
rm_workheh I will put my vote in once I arrive in the office17:08
rm_workkeep getting stuck responding to things and fixing/reviewing CRs in the morning17:08
dougwigsbalukoff: heck yes.17:08
dougwigi +1'ed everything i liked, and -1'ed the one that i don't.17:08
openstackgerritStephen Balukoff proposed a change to stackforge/octavia: Octavia v0.5 component design  https://review.openstack.org/11345817:08
sbalukoffInteresting. I wonder what the system will do if a new patchset is uploaded after a +A, but prior to a merge.17:10
sbalukoffI guess we're going to find out.17:10
rm_worknew patchset should kill +W17:12
rm_work+A?17:12
rm_workwhat is +A17:12
rm_workah17:13
rm_workyou meant the same thing17:13
rm_workI guess I call it +W because … +W(orkflow)17:13
xgerman_so how do I assign blueprints?17:13
xgerman_blogan? Am I alcking some powers?17:13
rm_workxgerman_: on the launchpad blueprint page it should have an edit pencil icon thing next to assignee17:14
rm_workif you don't have that, then yes17:14
rm_workusually only BP owners can do it?17:14
xgerman_no, I don't have the edit pencil17:14
rm_workhmm17:15
rm_workgah, i hate that they broke the CR->BP linkage17:15
xgerman_and neither does johnsonm_ -- so unless sballe has it you guys are cutting us :-(17:15
sbalukoffrw_work: I think you're right. The Zuul status is showing octavia in the 'check' column, not the 'merge' column.17:15
sbalukoffxgerman_: Can you go ahead and +A again?17:16
rm_worksbalukoff: yes, I've had +W cancelled on me before T_T17:16
rm_workxgerman_: don't listen to sbalukoff, wait for the check to pass before you +W >_<17:16
sbalukoffNaaah!17:16
rm_workalso, am I missing something, why is it +A? >_>17:16
sbalukoffIt's probably going to fail the python 3.3 check, since it seems most things are failing that at the moment. :P17:16
sbalukoffrm_work: No idea.17:16
sbalukoffI'm happy to call it +W, just others started calling it +A first.17:17
rm_workhmm17:17
rm_workweird17:17
rm_workwell if +A is correct I want to be using that term17:17
sbalukoffI'm not sure what's correct.17:17
rm_workbut I also don't want to blindly use a term I don't understand17:17
rm_workso I'm stuck fo rnow :P17:17
sbalukoffI'm just playing the card game 'Mao' here.17:17
rm_workhaha yes17:17
rm_workI feel that way too sometimes <_<17:17
sbalukoffxgerman_: Let me see what's going on there, why you can't edit stuff on the BP.17:19
dougwigsomeone +2/+A that review again quick, so we nuke the other merge17:19
xgerman_dougwig, don't you have the power, too17:20
xgerman_I am trying to assign blueprints to my HP teammmates and me :-)17:20
dougwigyep, but then our review lives in history with only one +2.  bad form, though i'll do it if someone else doesn't update it soon.17:20
xgerman_ok, I will +217:20
xgerman_done17:21
xgerman_dougwig +A17:21
xgerman_or, you can +A -- the alst time got me into trouble and I am not falling for that again ;-)17:21
rm_workdougwig: do YOU know why it's +A?17:21
dougwig+Approved17:22
dougwigthe rest are just votes.17:22
dougwigalright, zuul looks better now.  cross your fingers that the file add doesn't break jenkins.17:23
sbalukoffGerman: I added you to the octavia-core team on launchpad. Do you have access to do stuff there now?17:24
xgerman_Yes. Things look much better!!17:25
rm_workdougwig: ah, ok. in Barbican everyone talks about "Workflow" -- "Can you workflow my change?"17:25
dougwigfrom the gerrit UI:17:26
dougwigWorkflow:17:26
dougwig+1 Approved17:26
dougwig 0 Ready for reviews17:26
dougwig-1 Work in progress17:26
dougwigyou can actually trigger +A with 0 +2's.  it's the flag that matters.17:26
rm_workwell, you can if it's set up that way for your repo17:30
rm_workyou CAN set it up to *require* a number of +2s, right?17:31
rm_workdougwig: see, reading that UI, I would still assume the action is "workflow" so you'd +Workflow or -Workflow17:31
sbalukoffrm_work: Probably, but I generally prefer rules like that to be override-able and enforced by practice, not necessarily automated policy.17:32
rm_workotherwise by that logic it'd be +A and -W17:32
xgerman_ok, Al Miller is part of HP. He started today with the LBaaS team in case you are wondering ;-)17:32
sbalukoffAwesome!17:32
dougwigis he in channel?17:34
rm_workbbl17:34
dougwignaming vote: https://etherpad.openstack.org/p/octavia-backend-name17:50
dougwigi'm not going to let the review sit forever, so if you care at all, please speak up.17:50
*** jorgem has quit IRC17:57
*** jorgem has joined #openstack-lbaas18:01
openstackgerritA change was merged to stackforge/octavia: Octavia v0.5 component design  https://review.openstack.org/11345818:20
*** ajmiller has joined #openstack-lbaas18:34
bloganNO TO VM!!!!!18:41
blogani must come up with a campaign slogan18:41
bloganxgerman_: are you able to assign now?18:41
bloganxgerman_: nvm i see your response18:41
*** jorgem has quit IRC18:42
dougwigha, i love how node had a mini-consensus a few days ago, and is now all -1.  :)18:42
xgerman_yeah, sbalukoff hooked me up18:42
xgerman_and I asked our naming speicalist Julian to throw in some names ;-)18:42
dougwigright now it's either backend or container, folks.  vote early, vote often!  err, wait.18:43
*** jorgem has joined #openstack-lbaas18:44
bloganthere's really not going to be a name that just sticks out as being right18:51
blogani think this list should be wittled down to the most popular, and then people are only allowed to vote for one18:51
dougwighttps://www.irccloud.com/pastebin/sST8G9dT18:55
dougwigpod is actually growing on me.18:56
bloganme too, though the first thought was no way18:57
dougwigyeah, i threw it in as a lark.18:58
dougwigbut it's not overloaded, it is a thing which contains something(s), and we can define our own vocabulary.18:58
bloganim trying to get carlos and jorge to vote, don't worry i'm not telling them to vote for what i want18:58
dougwiggoing to grab some food before the meeting19:04
*** ptoohill has joined #openstack-lbaas19:13
*** crc32 has joined #openstack-lbaas19:20
blogancrc32, ptoohill: https://etherpad.openstack.org/p/octavia-backend-name19:21
*** crc32 has quit IRC19:21
*** ajmiller_ has joined #openstack-lbaas19:29
*** crc32 has joined #openstack-lbaas19:30
*** ajmiller has quit IRC19:32
sbalukoffI just threw a few more suggestions up there. Please go -1 them.19:43
*** sballe has joined #openstack-lbaas19:47
bloganlol19:49
bloganhmm19:49
*** vivek-ebay has quit IRC19:52
dougwighttps://www.irccloud.com/pastebin/53hWEacA19:54
dougwigthere is currently only one with a positive number.19:54
sbalukoffIsn't a pod a grouping of desks?19:55
sbalukoff(Among other things, obviously)19:56
dougwigit's also that thing they drop in your driveway, or a bean.19:56
dougwigand the pod people.19:56
sbalukoff6 more suggestions for people to -119:57
sbalukoffAlso, your math is off: pod only has a +219:58
sbalukoffSo what's a grouping of pods?  A plant?19:59
bloganwhats a grouping of groups?19:59
sbalukoff(Thinking of what we call the thing holding the loadbalancer in the active-active topology which is a grouping of nova vms)19:59
sbalukoffOr a vine?19:59
sbalukoffOk, meeting time, eh!20:00
sbalukoff#startmeeting Octavia20:00
openstackMeeting started Wed Sep  3 20:00:09 2014 UTC and is due to finish in 60 minutes.  The chair is sbalukoff. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
openstackThe meeting name has been set to 'octavia'20:00
dougwigsbalukoff: a stalk?20:00
sballeo/20:00
sbalukoffOk, folks!20:00
bloganhi20:00
blogan\o/20:00
sbalukoffHere's the agenda for today:20:00
sbalukoff#link https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda#Meeting_2014-09-0320:00
sbalukoffLet's get going20:01
sbalukoff#topic Briefly discuss Octavia/Non-arbitrary Decisions wiki page20:01
sbalukoffI just wanted to briefly bring people's attention to this.20:01
sbalukoff#link https://wiki.openstack.org/wiki/Octavia/Non-arbitrary_Decisions20:01
sbalukoffWe'll be using that for documenting decisions that took longer than a couple minutes to resolve (like the damn name thing).20:01
sbalukoffPlease let me know if you've got any questions about that.20:02
sbalukoffIf y'all have concerns about that, we can discuss at the next meeting.20:02
bloganlgtm20:02
sbalukoff(I am not expecting y'all to have concerns, as we discussed this in the last couple meetings.)20:02
sballesounds good to me. i am in a meeting and it is runnign late20:02
sbalukoffOk!20:03
sbalukoff#topic Briefly discuss v0.5 component design under review, Brandon's initial database migrations, push for consensus on that.20:03
jorgemhello!20:03
TrevorVo/20:03
sbalukoffSo, basically, this is about just making sure we're processing reviews in a timely manner.20:03
rm_worko/20:03
sbalukoffLooks like the v0.5 component design was merged earlier today.20:03
dougwigsbalukoff: the mentioned review is blocked on mine, which i will be trying to merge today.20:03
bloganmigrations need one more PS bc of the name thing, and need to add attributes to the health monitor20:04
sbalukoffOther than the naming thing that we're discussing, which is clearly a blocker for a couple of these, any major concerns to discuss at this time?20:04
TrevorVI have a topic if we have time.  Not pressing, just wondering what people's thoughts are20:04
sbalukoffTrevorV: Er... does it have to do with the current topic?20:05
sbalukoff(current topic is essentially discussing outstanding concerns with outstanding gerrit review stuff.)20:05
sbalukoff#link https://review.openstack.org/#/q/stackforge/octavia+status:open,n,z20:05
TrevorVNo it does not sballe20:05
rm_workguessing not because he said he as a Topic :P20:05
TrevorVsbalukoff, ** mah bad20:06
sbalukoffOh, haha!20:06
sbalukoffOk, we'll try to get through the remaining topics quickly if we can so we can discuss your topic, eh.20:06
sbalukoffOk!20:06
sbalukoffSo, moving on!20:06
sbalukoff#topic Get consensus on name of "thingy" doing the load balancing (VM / appliance / device / strategy / toaster / whatever)20:06
dougwig#link https://etherpad.openstack.org/p/octavia-backend-name20:06
dougwiggo vote.20:06
sbalukoffYes, please go vote20:07
sbalukoffWe need a decision on this today, because it's holding up other work.20:07
dougwigin about 1 hour and 23 minutes, i'm going to update the patchset with the winner, and then push for reviews.  we've had literally no other comments since the weekend except on naming.20:07
dougwigthe review in question:20:08
dougwig#link https://review.openstack.org/#/c/117701/20:08
blogandougwig: i think it'd be smart to get the top 3 adn then everyone vote on that, but only one vote20:08
sbalukoffdougwig: That seems fair.20:08
sbalukoffblogan: There's only one with a positive score right now, I think.20:08
rm_workblogan +1, though that delays things again20:08
TrevorV+1 blogan20:08
rm_workbut I think it is the fairest20:08
dougwigblogan: eh, runoff's are good when you only have on vote amongst many.  there is no limit here.20:08
dougwig /on/one/20:08
blogani think if there are 3 things and someone doesn't like any, but they had to choose one, the vote will be much clearer20:09
*** vivek-ebay has joined #openstack-lbaas20:09
sbalukoffOne thing to consider with this name:20:09
rm_workblogan +1 again20:09
dougwigok, at 3:30 we'll have a runoff.  voting will end at 5pm (this is all mountain time.)20:09
sbalukoffThis describes a nova instance dedicated to running the octavia code + haproxy which actually does the load balancing in this solution.20:10
sbalukoffIn an active-active topology, there will be groupings of these which perform the load balancing.20:10
rm_workplease set your name if you are voting so we can see who everyone is :P20:10
dougwigand at present, we literally have no names with >0 points.20:10
sbalukoffSo, it would be good if the name we choose has a logical grouping of some kind.20:10
sbalukoff(eg. sheep / flock ) or something.20:10
sbalukoffNot that I'm suggesting sheep at this point.20:11
bloganmay as well call it cats20:11
rm_workcats / herd?20:11
dougwigi'm definitely upload sheep.  you don't want to know what i'm naming the driver/interface.20:11
bloganindeed20:11
sbalukoffHaha!20:11
rm_workalthough RMS might get on us because of GNU/Herd20:11
*** tmc3inphilly has joined #openstack-lbaas20:11
rm_workor is that Hurd20:11
sbalukoffThat would be a good reflection of trying to get this group to agree on something. ;)20:11
rm_workheh yes20:11
bloganthis will be the hardest problem we come across20:12
ptoohillBattlestar-loadtallica is a logical grouping and should totally win20:12
sbalukoffAbsolutely.20:12
dougwigok, go vote, i think we can move on?20:12
sballeMy meeting is running even later. I'll have to read the minutes later20:12
rm_workvelociraptor / pack <-- just sayin'20:12
rm_workkk20:12
rm_workah though WD uses velociraptor for a line of drives :/20:13
sbalukoffserial killer / bloodbath20:13
dougwigone last note: there are a TON of -1's in there.  try to find some +1's, or suggest something new.  i don't want a vote among the least hated here.20:14
rm_worktruth20:14
TrevorVI wish we had enough logical space to explain why people are placing -1 or +1.  It always helps me make a decision when I know what people's thoughts are20:14
TrevorV(logical space?)20:15
rm_workdoug has been adding briefly why he's -1'ing i think20:15
rm_workor20:15
rm_workI guess he and Jorge did20:15
TrevorVhonestly, "overloaded term" is a bad argument for a -1 since its already overloaded it seems to make sense to use it... IMO20:15
sbalukoffTrevorV -120:16
sbalukoff:)20:16
TrevorVAt most I'd say -0.520:16
dougwigheh, note that i put that on "instance".  :)20:16
sbalukoffNo, I disagree: Having an overloaded term used for something with a specific purpose just irritates me.20:16
sbalukoffI know! Let's go with "server"20:17
sbalukoffYeah. No.20:17
dougwigno, no.  "object"20:17
bloganbut this is supposed to bea generic term20:17
sbalukoffdougwig: That's making me physically ill.20:17
crc32yea I withdraw instance. Cause we'll need a term in front of it now.20:17
sbalukoffblogan: "generic enough"20:17
TrevorVblogan, +1, hence me saying overloaded-term doesn't make sense.20:17
sbalukoffThe octavia load balancing thingy actually has a specific purpose.20:17
bloganwell a container has a specific purpose, and its to hold things, but it has a genric name20:18
bloganor does20:18
bloganit20:18
bloganoye20:18
*** KunalGandhiEbay has joined #openstack-lbaas20:18
sbalukoffIt runs the software which actually delivers the load balancing service to the end user.20:18
sbalukoffRight.20:18
TrevorVSo its a host, sbalukoff ?20:19
sbalukoffTrevorV: You're lucky you're not within throwing distance.20:19
TrevorVI'm actually serious here, since that seems appropriate to me with that description :D20:19
rm_workpeon / grunt? :P20:19
sbalukoffrm_work: +120:19
crc32Sounds like a "<InsertTermHere>Manager"20:19
sbalukoffThese things shouldn't be that intelligent.20:19
vivek-ebayI am confused. What are we suggesting name for? octavia-backend ?20:20
rm_worktotally adding both of those20:20
ptoohillOh dear, executive decision time on naming issues? Let's just default to toaster or something? Isn't there other pressing issues?20:20
TrevorVRight, so what keeps us from using an overloaded-term?  :)20:20
sbalukoffvivek-ebay: Yes.20:20
sbalukoffThe Octavia VM in previous diagrams and component designs.20:20
dougwigTrevorV: imagine if you're new to the project, clone it, and have nothing as a roadmap except the directory listing.  there are a few generic terms that have enough meaning to help.  host isn't one of them.20:20
rm_workptoohill: well unfortunately this is blocking a major CR20:20
xgerman_sorry for being late20:20
TrevorVdougwig, that's fair.20:20
sbalukoffptoohill: Yes there are.20:20
sbalukoffSo!20:20
rm_workI'm thinking about something that is a good metaphor20:21
rm_workpeon / grunt are that20:21
rm_workthey're the actual "workers"20:21
rm_workoh20:21
sbalukoffAdd any suggestions you want before the end of this meeting...  directly after the meeting, everyone please register your +1 / -1 / abstain on this.20:21
rm_workis "workers" super overloaded? >_>20:21
dougwigworker/colony/ant20:21
rm_worki like worker/colony20:21
bloganso as dougwig said, this vote will be until 330pm Mountain Time, and then the top 3 will have another vote which will close at 5pm Mountain Time20:21
dougwighive20:21
sbalukoffAnyone have anything else to add to this discussion right now?20:21
sbalukoffdougwig: bee20:22
dougwigi think we're past time to move on.  take your ideas to the etherpad, please20:22
vivek-ebaybeehive20:22
sbalukoffYep.20:22
ptoohillGoooses20:22
sbalukoffOk!20:22
ptoohillOh were past that srry20:22
sbalukoff#topic Discuss where haproxy config should be rendered (controller, driver, or Octavia VM / appliance)(Driver, of course.)20:22
sbalukoffMy thought echoes Dougwig's here:  In the driver.20:22
jorgemi added approach20:23
sbalukoff(And then configs get pushed out to the octavia load balancer thingy)20:23
dougwig(sorry for editorializing the agenda, i couldn't resist.)20:23
sbalukoffAnyone have different ideas here?20:23
bloganisn't the driver basiaclly in the controller?20:23
sbalukoffblogan: Yes, ish.20:23
sbalukoff;)20:23
dougwigblogan: yes, imported by controller.20:23
sbalukoffIt gets loaded by the controller.20:23
bloganthe controller will just instantiate whatever driver it needs to use20:23
xgerman_no, we like it to be in the VM20:23
sbalukoffxgerman_: Please explain your reasoning.20:24
jorgem+1 blogan20:24
xgerman_I though we discussed that last time20:24
dougwigi actually don't care beyond it not being in the controller core.  it's really a driver issue, but as long as the interface isn't hard-coded to haproxy, it matters not whether that occurs in the driver or VM.20:24
jorgemIt makes it easier to test as well20:24
jorgembecause we can mock stuff out20:24
rm_worksbalukoff: +1, in the driver IMO20:24
bloganxgerman_: any strong reasons why it should be on the VM side?20:25
xgerman_then I can switch haproxy, etc. without changing the controller20:25
dougwigxgerman_: especially considering that if you roll a custom VM, you could make your driver a pass-through.20:25
johnsom_dougwig +120:25
sbalukoffxgerman_: So a couple reasons I don't want this in the VM:   1.  It puts more intelligence into the VM than is necessary (again, centralize intelligence, distribute workload)20:25
sbalukoff2. It makes the back-end API (ie. what the driver/controller speaks to the VM) more complicated20:25
TrevorV+1 driver20:26
sbalukoffAlso: 3. It makes it more difficult to add new minor features... because you'll have to go out and update 10,000+ VMs instead of updating a few controllers.20:26
xgerman_well, you have to do that anyway in case of security updates20:26
sbalukoffxgerman_: So, if you want to replace haproxy with nginx, that seems to call for a new driver in any case.20:27
sbalukoffxgerman_: Yep, so let's not exacerbate the problem by having to do it for minor feature additions, too.  Also, not all security updates will necessarily require that.  If it's a problem that can be fixed with an update to a config (eg. "disable this kind of SSL") then that doesn't require updating all VMs.20:28
*** sballe has quit IRC20:28
dougwigi think this becomes a difference of, do we have an nginx and an haproxy driver, or do we have a nova VM driver, which different VM's?  one of these schemes will fit inside the other.20:28
dougwig /which/with/20:28
sbalukoffxgerman_: If you want to have an Octavia VM be able to run either haproxy or nginx, that's doable too-- and accomplishing this is still easier by writing a driver which can do both, and making a minor change to the back-end API.20:28
xgerman_well, my vision was that the controller talk to the VMs in some octavia protocol and the the vm renders it as needed20:28
sbalukoff(Speaking from experience, as our BLBv1 product can do either haproxy or nginx)20:29
dougwig(an aside, i will note that from minute zero in this conversation, we have used the term VM to describe what we're voting on naming.)20:29
xgerman_so now we need to bookkeerp which vm is compatible with which driver, versions need to fit, etc.20:29
sbalukoffxgerman_: I think that's good in theory, but in practice will be more of a pain once you have a large deployment.20:29
rm_workxgerman_: yeah that makes sense and I was thinking that too -- although then we have to define another whole interface level, which i think we can avoid by just doing it in the driver layer20:29
sbalukoffxgerman_: All of that is solved if you have an API command to gather that info. Think of it like API versioning.20:30
rm_workthough yeah, i am concerned about the bookkeeping20:30
sbalukoffOctavia VMs will also have a version, eh.20:30
xgerman_yep, so we might have to replace VMs + the driver20:30
xgerman_to solve the special case of "minor changes"20:31
sbalukoffxgerman_: For major changes, yes.20:31
sbalukoffBut that's no different from the model you've proposed.20:31
sbalukoffNo, actually, you don't have to replace the VMs for minor changes.20:31
xgerman_yeah, but for major changes I do20:31
sbalukoffxgerman_: Again, which is no different than the solution you've proposed.20:32
sbalukoffThe difference here is that you have to replace the VMs for minor changes as well.20:32
sbalukoffI don't.20:32
xgerman_yep, so I don't create a special case20:32
sbalukoff...20:32
rm_work(dougwig yeah we kind of anchored the discussion in a way by saying "vote on what to call VMs" :P)20:32
sbalukoffxgerman_: The solution that allows for the least amount of overall pain is the best one, IMO.20:33
TrevorVsbalukoff, +120:33
sbalukoffRather than making everything equally painful20:33
sbalukoffAnyway, do we want to vote on this here, or do y'all think that mailing list discussion is warranted?20:34
dougwigi think that if xgerman_ isn't convinced, this needs to be punted to ML or voice.20:34
xgerman_well, so far the advantage of your proposal id for minor upgrades; downside is more bookeeping20:34
dougwigjinx20:34
sbalukoffxgerman_: There's more than just that.20:35
bloganif the config rendering gets done on the VM side, will the controller even need an haproxy/nginx driver? would that just be pushed to the VM?20:35
TrevorV+1 to mailing list20:35
sbalukoffThe backend API is also far less complicated.20:35
TrevorVblogan, I think the argument is having that all pushed to VM20:35
xgerman_ok, mailing list20:35
sbalukoffAnd again, your solution goes against the whole "centralize intelligence / decentralize workload" design philosophy.20:35
dougwigblogan: yes, because not all appliance backends will have the luxury of implementing it all inside the VM.20:35
blogandougwig: ++ for your use of appliance20:35
TrevorVdougwig, (I see what you did there)20:36
sbalukoffhaha20:36
tmc3inphillyUnit of Compute (UoC)20:36
sbalukoffOk, we'll punt to mailing list.20:36
xgerman_ok20:36
sbalukoffxgerman_: Do you want to start that thread, or shall I?20:36
xgerman_you can start it20:37
sbalukoffOk, will do.20:37
sbalukoffOk, next topic20:37
sbalukoff#topic Discuss DB model around loadbalancer VIPs in relation to different front-end topologies and how be to represent these abstractly20:37
sbalukoffSo, in looking at how to make the network stuff work, I think blogan and I realized that we've not yet come up with a good way to represent the types of connections the VMs / appliances will need to the rest of the network.20:38
rm_workthat's... quite a wordy topic :P20:39
sbalukoffWe could default to Neutron terms here, which I think is actually not good because it assumes a lot about layer-2 topology.20:39
dougwigsbalukoff: can you give an example or two?20:39
TrevorV+1 dougwig20:39
xgerman_+120:40
sbalukoffdougwig: So, right now if we're working with just Neutron as a networking layer, if we want to represent the front-end connectivity to a VIP address (ie. part of the loadbalancer object), we need to record both the vip_address and vip_port_id20:40
sbalukoffOr something like that..20:40
sbalukoffWhat the user is actually probably interested in is vip_address and subnet_id20:40
bloganif octavia is responsible for creating the vip_port, then we need a subnet_id20:40
sbalukoffBut that's assuming layer-2 connectivity on the front-end.20:40
bloganand if floating ips are being used, thats different20:41
sbalukoffThings get more complicated with layer-3 (routed) connectivity20:41
dougwigand overlapping subnets.20:41
sbalukoffBecause a layer-3 address isn't going to be associated with a port, it's going to be associated with a route.20:41
sbalukoffdougwig: Well, ignoring the overlapping subnets problem for a bit, we still have trouble reliably representing things even if there isn't overlap.20:42
dougwigwe'll have to have some generic id fields, which the network_driver is going to have to map to neutron specifics.  the question is how many id fields, and what to name them?20:42
dougwigor a text blob where we can put whatever json the network_driver needs?20:42
blogandougwig: i believe that is the extent of the problem, making sure we have the necessary fields and good names (naming things!@#@##)20:42
sbalukoffdougwig: I'd love it if we had a way to refer to these things in "Octavia language" or something, which the driver then translates to do whatever is necessary for that type of connectivity on the network side.20:42
TrevorVdougwig, don't forget what is required versus optional20:42
sbalukoffSo, that we're using more industry standard terms and concepts, and aren't doing what I think to be "hackish" ways of handling this with Neutron specifically (eg. associating an address with a port and the not putting that port on any subnet, because that's how you handle a layer-3 route? really?)20:43
bloganxgerman_: from HP's perspective, what information would you need to store for front end connectivity?20:43
sbalukoffI don't want to bake that kind of hack-ish-ness into Octavia's design, if we can avoid it.20:44
blogansbalukoff: you can have a port without a subnet in neutron?20:44
xgerman_we are still discussing on our end how things will shape up20:44
dougwigmaybe we inch our way there?  0.25 is vip and members on same subnet, 0.5 is vips all on one subnet, members on others, etc...  there's no reason these db models have to be perfect in the first rev; we're going to learn a lot in the first prototype.20:44
sbalukoffblogan: I think so, but I could possibly be wrong. You might have to create the subnet, and then not attach it to a router. I forget-- it's been a few months since I looked into how to do this.20:45
blogandougwig: +1, I think that may end up being what we need to do because there is a lot of unknowns right now20:45
sbalukoffdougwig: I guess I'm asking: Is anyone out there an expert who has an opinion on the right way to do this that can talk to us?20:45
blogansbalukoff: i'm not totally 100% sure, but I didn't think it was possible to have a port not on a subnet20:45
sbalukoffUnfortunately, my neutron networking expert is on vacation this week. :P20:46
sbalukoffblogan: Then I'm probably wrong, but I don't think I'm wrong about making floating IPs work a non-hackish kind of thing. ;)20:46
dougwigsbalukoff: i think i'd still advocate getting some code on the books with a simpler topology first.20:46
blogancould just store these things as generic for now, network_resource_id20:47
sbalukoffdougwig: I'd really rather have this model figured out before we paint ourselves into a corner with an inadequate design baked into other components. :P20:47
*** sballe has joined #openstack-lbaas20:47
TrevorVdougwig, if I understood you correctly, you mean to just leave naming/fields tied to Neutron for now, and modify as needed later?20:47
sbalukoffIn any case, we don't need a final decision on that now, or even this or next week, IMO.20:48
dougwigno, i mean as we find fields we need to add to support neutron, we think of generic names/concepts and add them to the migrations at that time, instead of waiting to have perfect models.20:48
blogansbalukoff: I don't think a major refactor before 0.5 will be a huge deal (famous last words I know)20:48
sbalukoffdougwig: You're right that we can get some work done without having this figured out.20:48
TrevorVdougwig, ah, gotcha, thanks20:48
sbalukoffMosty, I wanted to make the rest of y'all aware of the problem, so if you can pull in resources, or if you have a good idea on how to solve this in the long run that you'd like to share, I'd love to hear it.20:48
sbalukoff(Over the next coming weeks, eh.)20:49
sbalukoffAnyway, we've only got 10 minutes left, so I wanted to move on to the next topic.20:49
blogansbalukoff: in the meantime is using generic names acceptable?20:49
sbalukoffblogan: I don't think we've got another choice. :)20:50
xgerman_blogan +120:50
blogandone20:50
sbalukoffblogan: Nobody is suggesting anything else at this time, eh.20:50
sbalukoffOk!20:50
dougwigi'd put their neutron counterpart names in the models (as comments), where we differ.20:50
blogandougwig: good idea20:50
sbalukoffdougwig: +120:50
sbalukoff#topic Discuss blueprints here, look for volunteers: https://blueprints.launchpad.net/octavia/20:50
sbalukoffOk, folks!20:50
sbalukoffWe have blueprints! Please start claiming them!20:50
sbalukoff(And fleshing them out, doing work on them, etc.)20:51
xgerman_+120:51
bloganeveryoen agree on the process?20:51
sbalukoffAlso, please make sure to start updating the stand-up etherpad I created (modeled on the one Jorge did for Neutron LBaaS)20:51
blogangiving more details in the blueprint work items/whiteboard?20:51
sbalukoff#link https://etherpad.openstack.org/p/octavia-weekly-standup20:51
blogansome things like interface designs are probably just easiest showing the code honestly20:52
xgerman_ok, good to know'20:52
johnsom_Can we capture the networking concerns on the ML so we can pass it around to people for comment?20:53
*** markmcclain1 has joined #openstack-lbaas20:53
bloganjohnsom_: i think that is a good idea20:53
sbalukoffjohnsom_: Sure.20:53
sbalukoff#action sbalukoff to start ML thread on front-end topology representation concerns20:54
*** markmcclain has quit IRC20:54
sbalukoffOk, Trevor! What's your topic?20:54
dougwigsbalukoff: switch the topic to open discussion...20:54
sbalukoff#topic Open Discussion20:54
bloganTrevorV: you had something20:55
TrevorVSo in some of my work with the db-repository blueprint, a question came up.  Where do we do validation of request/ownership?20:55
TrevorVFor example:20:55
TrevorVIf a customer makes a request to retrieve a load balancer by an ID that doesn't belong to their tenant, where does the exception get thrown from?20:56
TrevorV(Implementation detail, I know, but it helps)20:56
sbalukoffTrevorV: So I see that as being a function of the API.20:56
*** jorgem has quit IRC20:56
TrevorVSo the API layer would retrieve the object and then check its tenant_id?20:56
TrevorVSort of situation?20:56
blogani think the more generic question is how much validation do we want the database layer to be responsible for versus an actaul validation alyer?20:56
TrevorV+1 blogan, much more concise20:57
xgerman_can you circumvent the validation layer?20:57
*** tmc3inphilly has quit IRC20:57
sbalukoffblogan: Syntax, santity checks at the DB layer, authorization at the validation layer?20:57
TrevorVxgerman_, you shouldn't be able to unless you're accessing the operator api20:57
sbalukoffEr...20:57
sbalukoffWell, I suppose we could do all of that at the validation layer.20:57
rm_workare we using RBAC using keystone middleware?20:57
bloganxgerman_: i don't think the validation should be able to be circumvented at all, but that could be argued20:58
dougwigi like permissions in controller, validation in ORM.  but that's me.20:58
rm_workif so, they we do it like barbican does it -- assign rbac roles and on the function we say to enforce a specific role requirement, and the middleware handles it20:58
a2hillrm_work +1 RBAC can handle a lot of that for us20:58
xgerman_blogan_, I just want to make sure we don't open a security hole by designing it wrong20:58
xgerman_a2hill, rmwork +120:58
xgerman_I love roles20:58
sbalukoffa2hill, rm_work: +120:59
sbalukoffWhy not go with a precedent, eh?20:59
bloganthats fine, but for things that are not handled by rbac20:59
xgerman_example?20:59
dougwigthe counter-argument is to keep this stuff simple for now, since if we're a driver of lbaas, that crap will all be done for us.20:59
blogansuch as maximum values20:59
dougwig(i.e. a trusted entity)20:59
dougwig((except by sbalukoff))20:59
sbalukoffHaha21:00
sbalukoffOk, well, we're out of time for this meeting.21:00
sbalukoffI didn't get a chance to do the vote on whether to keep things here or move back to webex.21:00
sbalukoffI'll add that as an agenda item for next time.21:00
xgerman_let's vote next time :-)21:00
sbalukoffThanks y'all!21:00
sbalukoff#endmeeting21:00
openstackMeeting ended Wed Sep  3 21:00:45 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
dougwigyay, another IRC meeting!21:00
bloganreal quick, if the database can provide an automatic vlaidation (foreign key constraint) should we just rely on that?21:00
TrevorVSounds good, thanks!21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-09-03-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-09-03-20.00.txt21:00
TrevorV\021:00
openstackLog:            http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-09-03-20.00.log.html21:00
bloganinstead of making two calls?21:00
TrevorV\o21:00
rm_worki know the meeting is over, but21:01
*** markmcclain1 has quit IRC21:01
dougwigblogan: i hate getting SQL involved, because it makes swapping databases harder.21:01
rm_workin response to xgerman_'s concerns, yeah, we shouldn't JUST count on the RBAC/keystone layer21:01
sbalukoffrm_work: NO! YOU ARE ABSOLUTELY NOT ALLOWED TO KEEP TALKING21:01
*** markmcclain has joined #openstack-lbaas21:01
sbalukoffXD21:01
a2hillThe validation errors will bubble up as a proper error response then that would be fine imo21:01
dougwigbut i wouldn't object in that case.21:01
blogandougwig: so you're syaing make two calls to the database for that validation?21:01
rm_worktenant_id should also be passed through with the object_id to the repository layer and included as part of the filter/lookup21:01
rm_workwhich isn't strictly "validation" so much as "preventing really random bad things from happening"21:02
dougwigblogan: i'll cop out, and say that i'd mostly go with the norm for other openstack projects.21:02
rm_worksbalukoff: :P21:02
sbalukoffdougwig: +121:02
xgerman_yeah, putting the tenant_id in the query sounds smart21:02
rm_workyeah take a look at the SQLAlchemy layer in Barbican21:02
rm_workthey do what I am referring to21:02
blogandougwig: okay, going off of neutron, they do a lot of validation in the db module, which i'm not a fan off21:02
bloganof21:02
bloganhowever, if it prevents multiple database calls, i can see that point21:03
xgerman_I think Brabican is to right way to go21:03
rm_workhttps://github.com/openstack/barbican/blob/master/barbican/model/repositories.py#L56621:03
dougwigsbalukoff: IRC doesn't seem to be cramping your ability to talk:21:03
dougwighttps://www.irccloud.com/pastebin/KurFnaFd21:03
dougwig:)21:03
a2hillbut your db is a source of truth, so having that validation there isnt a bad thing is it?21:03
xgerman_yeah, our security people love it when it's almost impossible to get to anotehr tenant21:04
sbalukoffdougwig: I could talk two or three times as fast via voice.21:04
sbalukoffAnd so can everyone else.21:04
dougwigcorrect me if i'm wrong, but we don't yet need a solution hardened to billions of hostile users.  just one trusted entity.21:04
sbalukoff;)21:04
blogansbalukoff: but we met everythign on the agenda, and it was pretty packed21:04
sbalukoffblogan: I felt like I had to cut off some conversations prematurely.21:05
dougwigsbalukoff: you out-typed the next chattiest person by 3x !!.  :)21:05
sbalukoffLike the one we're still having.21:05
rm_worksbalukoff: maybe YOU can, but on voice, no one else can talk while you are21:05
rm_worksbalukoff: so TOTAL talking will be less21:05
a2hillchirpchirp back to the delorean21:05
sbalukoffrm_work: Yeah, but focus will be better. As will understanding.21:05
rm_workeh21:05
rm_workI liked being able to re-read some of the more complicated things people said21:05
rm_workin voice it's gone and i have to try to remember and figure out WTF and just get confused :P21:06
sbalukoffReally, text is a vastly inferior form of communication for most types of group conversations.21:06
sbalukofftext is great if you have specific details to share.21:06
dougwigsbalukoff: IMO, most of the conversations that have to end prematurely belong on the ML, so there's some contemplation time.21:06
rm_worki'd say text is inferior for SMALL groups, but MUCH better for large groups21:06
sbalukoffBut it sucks when the point is to try to get consensus on things and understand differing points of view.21:06
bloganthere a pros and cons to both, but I think for what we are doing IRC is the best fit21:07
bloganand you must comply sbalukoff21:07
sbalukoffWell, we'll vote on it next week. But I remain unconvinced. :P21:07
rm_workbecause again, while you maybe be able to talk faster than type, talking is limited to exactly 1h of "airtime", whereas if everyone were to talk out loud all the things they said in IRC, i think we'd have 3h+ of talking total :P21:07
sbalukoffHaha21:07
bloganhave you ever been convinced that you were wrong?21:07
sbalukoffrm_work: Actually no. If you read the transcript aloud you'll get through it in like 20 minutes.21:07
rm_workfor example I have said maybe three sentences per meeting in every webex we've had, because i have to compete for airtime21:08
sbalukoffblogan: I have, actually. ;)21:08
rm_workbut i was able to say a lot here :P21:08
rm_worksbalukoff: deciding now whether i want to actually make that audio recording just to see what happens21:08
rm_worksbalukoff: i might do it21:08
bloganlol sbalukoff, there we have precedence. once wrong, always wrong21:08
sbalukoffblogan: I argue fiercely for the stuff I'm convinced of, and I guess I expect others to do the same. If I don't have a strong opinion I'll usually say that or refrain from adding much to a discussion, opting instead to listen to others' points of view.21:09
sbalukoffBut I have been wrong, many times.21:09
rm_worki feel that sbalukoff and I are very similar in that regard21:09
bloganrm_work: that wouldn't be an accurate measure because people still have to think before speaking so there would be some down time, unless you're sbalukoff21:09
sbalukoffHeck, the design we're working off of here is not what I would have recommended last January.21:09
rm_workexcept that i have not been wrong as often :P21:09
sbalukoffI think the desing we've got here is vastly superior to what I came up with alone back then.21:09
* rm_work jabs sbalukoff 21:09
sbalukoffblogan: Haha!21:10
rm_workI would do it assuming appropriate pauses21:10
sbalukoffcrc32 did have a good point about IRC though: There is often lack of focus.21:10
rm_workand by "appropriate" i mean probably a few seconds at least inbetween switching people21:10
blogansbalukoff: I'm just a terrible speaker when it comes to getting my point across and I do it best through text I believe.  I feel that is also soemthing common in a lot of other people as well.21:10
sbalukoff3-4 different conversations happening at once in a single medium.21:10
rm_workwell, that is just up to the moderator21:10
dougwigif anyone wants to channel their inner holy war: https://review.openstack.org/#/c/118479/21:11
sbalukoffIt's confusing, especailly if you want to participate in all of these discussions.21:11
rm_workbut i don't think it's necessarily a bad thing21:11
dougwigblogan: +121:11
rm_worki think of it as parallelizing21:11
blogani'm not sure why having a currently broken env is a problem. can you explain?21:11
rm_workbut a moderator can easily say "please stick to the topic"21:11
sbalukoffblogan: I have not had trouble understanding your points when you've expressed them via voice in the past.21:11
bloganthat one is kind of ironic21:11
rm_workand "please take this out-of-channel or save it till after" and people will generally comply21:11
sbalukoffrm_work: Yeah, except they don't.21:12
rm_workwell21:12
rm_workyou were the moderator21:12
sbalukoffAnd people who are having trouble following along get left behind in the "text orgy"21:12
rm_workfeel free to do so :P21:12
sbalukoffrm_work: Part of the reason I ended up typing 3x as much as the next person.21:12
blogansbalukoff: well i would argue that is because I've talked about them to you before the webex meeting21:12
rm_workheh21:12
blogansbalukoff: on irc21:12
sbalukoffblogan: Is that different here?21:13
sbalukoffI mean-- we put the agenda out a day before the event. People have time to read through that and know what's going to be discussed and ask questions on IRC beforehand.21:13
bloganno, but it obviously works well through IRC (and reviews obviously)21:13
sbalukoffblogan: As long as we both agree on terminology and whatnot.21:13
sbalukoffblogan: I can't tell you how many times I've seen simple misunderstandings there that would have been easily picked up in voice.21:14
sbalukoff(From inflection, the way people actually say the words, etc.)21:14
rm_worksbalukoff: i won't argue that what you're talking about doesn't happen21:14
rm_workit definitely does21:14
sbalukoffAlso, sarcasm works really well in text.21:14
rm_workbut i don't think it's a good enough reason to move to a less accessible medium21:14
sbalukoffIn any case...21:14
dougwigcan't we all just agree that the best meeting medium would be emacs?21:14
dougwignone of this vim stuff21:15
bloganlike i said pros and cons to both, IRC pros outweigh the webex pros in my mind21:15
rm_workand i DARE you to argue that webex isn't "less accessible" than IRC <_<21:15
sbalukoffI don't see me convincing you or you convincing me on this matter--  so I'll defer to what the majority wants when we vote on it next week, eh.21:15
blogansbalukoff: agreed to disagree21:15
blogani think we can all agree IRC is better21:15
bloganno opposition, that statement is fact now21:16
sbalukoffrm_work: Heh! From using the technology, yes, IRC is easier for most of us. For getting one's point across, if you're a slow typist, or have trouble sorting through the text orgy, IRC is worse.21:16
sbalukoffblogan: I'm 1000% in agreement with you.21:16
rm_workheh, well, i really want to do a recording of dictating the entire IRC chat... but i have somewhat lost my voice since last weekend (either from yelling too much during gaming, or from some sort of plague)21:16
blogansbalukoff: at least you have something to sort through, with voice you can't sort through any of it21:16
sbalukoffblogan: If Trevor is still writing up meeting minutes from the recording, then I would argue that ends up being the best way to digest these meetings. His meeting minutes rock.21:17
rm_workyeah, and when i have to look away for a minute (which happens to me REGULARLY during these meetings), i am not completely lost when I come back, I just read the scrollback21:17
blogansbalukoff: he is not allowed to do them anymore21:17
sbalukoffblogan: But yes, if you're involved in a voice meeting you have to give your full attention to the meeting. Multi-tasking is less effective.21:17
sbalukoffOne might argue that's a good thing. ;)21:17
dougwigblogan: lol21:18
rm_worksbalukoff: it might be, but it doesn't keep me from NEEDING to shift attention >_>21:18
blogannot a good thing if there are many things going on with the actual businesses we work for21:18
rm_workyes21:18
dougwigit's also easy to attend IRC meetings in noisy environments, like airports.  which i have done many times.21:18
rm_workyeah21:18
sbalukoffblogan and rm_work: Again, opinions differ on this.21:18
blogani now21:19
blogani know, im just scratching my arguing itch21:19
rm_worksbalukoff: opinions differ on whether or not things come up that cause people to stop paying attention to meetings? :P21:19
rm_worki don't think that's an opinion thing21:19
rm_workI think that's a fact thing :)21:19
blogansbalukoff: i was just hoping i could be around to see one of those times you would concede defeat21:19
sbalukoffrm_work: No, on whether that makes for a more effective meeting.21:20
sbalukoffSpecifically...21:20
dougwigy'all are just debate masturbating at this point.  IRC is clearly superior for a variety of reasons, and none of the parties in this conversation are going to change their minds.21:20
bloganso....Incubator?21:20
rm_workif people have to step away for a minute, they should just be locked out of the discussion because "obviously it isn't important enough for them"? :P21:20
sbalukoffWe banned laptops and cell phones from a few key meetings in the past, and suddenly they got both a lot more focused, and we got through the material faster.21:20
sbalukoffhaha21:21
bloganwell you can't exactly force that on this community21:21
dougwigproject octavia, the iron fist of openstack.21:21
rm_workdougwig +121:21
sbalukoffHaha!21:21
bloganin soviet octavia, meetings run you21:21
sbalukoffrm_work: No, figure out how to handle those disruptions without losing focus on the meeting. :P21:22
bloganalright i gotta get off for a bit21:22
bloganill be on later21:22
sbalukoffI just really hate seeing things dragged out a lot longer than they need to be, which I think happens with IRC relatively frequently.21:22
blogani enjoyed this21:22
dougwigsbalukoff: pay attention to the chairing of the next neutron meeting.  things do not drag out.21:23
sbalukoffdougwig: How quickly is consensus achieved?21:24
sbalukoffJust because you got through an agenda doesn't mean it was an effective discussion. :P21:24
dougwigeither very quickly, or it's a damn fast punt to another medium.  the meeting is just a synchronization point.21:24
dougwigthere is discussion and decisions.21:25
sbalukoffYeah, and what you're saying is that meetings are not appropriate for discussions.21:25
sbalukoffThis is a pretty fundamental difference from what I think.21:25
dougwigFIVE MINUTES REMAIN TO VOTE.  this is your last chance to load it up in another browser with a new color and go chicago on the results.21:25
sbalukoffAnd I think that idea is imposed because having a good discussion on IRC in a short enough interval is next to impossible.21:26
dougwigno, not what i said at all.   some agenda items are flagged for discussions, and go on longer.21:26
rm_worklol dougwig21:26
sbalukoffHow do the "discussions" happen?21:26
sbalukoffMailing list thread?21:26
rm_workonly one I like in there is Worker, really (and peon/grunt, but i don't expect others to like it) so whatev21:26
sbalukoffAgain, that's often not the best place for them.21:26
dougwigdepends.  i've seen some in channel, a lot to ML, some to phone conferences.21:26
sbalukoffOh, so they do go to voice?21:26
dougwigyeah, some of the incubator stuff went to voice.21:27
sbalukoffAnyway, my point is that in the IRC meetings, no actual discussion of the topic takes place. As you were saying, it either gets decided quickly or gets punted to another medium. The IRC meetings are seen as a place to "synchronize" on what are presumably pretty much already-discussed points.21:29
sbalukoffMy point is that if you have a voice meeting, you actually can discuss things there because the bandwidth is so much higher, and the chances of being misunderstood are lower.21:30
sbalukoffPeople are also less rude to each other via voice.21:30
sbalukoffGenerally speaking.21:30
dougwigi saw quite a bit of discussion happening today.  it's true that you can't always get to consensus, but some of those topics i wanted more time to think about anyway.21:31
dougwigwait, how did i get sucked into arguing about this?  we won't resolve this, via either an IRC argument or voice.  :)21:32
sbalukoffSo, there's no reason you can't punt to another medium or later date when having a voice meeting.21:32
sbalukoffAnd yes, we discussed things, but the point is that discussion was truncated often without a good conclusion.21:32
sbalukoffHaha!21:32
sbalukoffWow, just looked at the line counts from the meeting.21:35
sbalukoffI think I may have come close to matching the total of everyone else. XD21:35
sbalukoff(I don't think that happens via voice, but I could be wrong--  I'm pretty sure I yield the floor more often than that when I'm not pushing insanely hard to actually get through the whole agenda like I felt pressured to do this week.)21:36
sbalukoff;)21:36
sbalukoffAnyway, I'll quit talking about that now.21:36
* rm_work starts narrating into a recorder21:48
sbalukoffHaha! Awesome.21:53
*** rm_work has quit IRC21:54
sbalukoffYay, google: http://www.mindwareconnections.com/blog/bid/79429/Can-I-Type-Faster-Than-I-Talk-A-Dragon-Comparison21:54
sbalukoffThat's mostly marketing, I think.21:55
sbalukoffThis is probably less biased:  http://en.wikipedia.org/wiki/Words_per_minute21:55
sbalukoffAlso, rm_work:  While you can have 3-4 different conversations going on at once, the extra time it takes to try to follow those conversations probably trumps any parallelism benefit.21:56
sbalukoffBut it is easier to get a word in edge-wise with IRC, mostly.21:56
sbalukoff(Unless you're up against me, and I miss what you typed...  :P )21:57
sbalukoffBecause I can keep droning on, and on, and on. ;)21:57
sbalukoffLike right now.21:57
sbalukoffWhy am I still typing?  Even I don't know.21:57
sbalukoffAnd like the rest of you, I kinda wish I'd shut up.21:57
*** TrevorV_ has joined #openstack-lbaas21:59
*** rm_work|away has joined #openstack-lbaas22:01
*** rm_work|away is now known as rm_work22:01
*** rm_work has joined #openstack-lbaas22:01
*** vivek-ebay has quit IRC22:02
*** vivek-ebay has joined #openstack-lbaas22:03
*** openstack has joined #openstack-lbaas22:10
a2hillbattlestar-loadtallica won right? I mean it wasnt even a challenge right?22:11
*** markmcclain has quit IRC22:20
dougwigrunoff voting is now open: https://etherpad.openstack.org/p/octavia-backend-name22:23
dougwigheh, another benefit to IRC.  if sbalukoff keeps talking, you can close the window.22:24
bloganlol22:25
blogansame with webex of course22:25
bloganactually you can mute him in webex and watch all his hand motions22:25
bloganwhich could be entertaining22:25
dougwigooh, that's a fun idea.22:26
a2hillhis video is usually disabled though :P22:26
bloganis ant/colony really a serious contendor?22:26
a2hilllmbo22:26
sbalukoffI expect to see my actions re-dubbed into something funny if y'all are going to do that. XD22:26
sbalukoffYeah, my laptop camera has... spotty reliability.22:26
bloganif Octavia was called AntFarm or AntHill or something, i could see that making sense22:26
dougwigit had a total of 0.  i already editorialized out one contender.  i didn't want to do two.22:27
bloganwhich one?22:27
dougwigmaybe we should take a page from the rotating times that neutron and nova use, and suggest rotating irc/voice every other week?22:27
dougwig(peon)22:27
bloganoh battlestar-loadtallica22:27
bloganoh nevermind22:27
dougwigoh, and that one.22:27
dougwigi used number of votes to kind of sway in some lower ones.22:28
bloganare you abstaining?22:28
dougwigthere are none that i *love* on that list, so i'm still thinking about it.22:29
*** vivek-ebay has quit IRC22:29
blogani thought you would like mechanism the most22:29
*** vivek-ebay has joined #openstack-lbaas22:30
*** TrevorV_ has quit IRC22:32
rm_workah22:33
rm_workhow long for runnoff?22:33
blogan30 more mins22:33
*** vivek-ebay has quit IRC22:33
rm_worklol dougwig voted against one of his own later ideas :P22:34
*** vivek-ebay has joined #openstack-lbaas22:35
sbalukoffI should have voted agianst most of my suggestions there because they were mostly terrible.22:36
rm_workheh22:37
rm_workI liked worker / colony better than ant/colony, but ant made it :(22:37
rm_workand I liked peon better than grunt :P but ah well22:37
dougwigi'll leave the runoff until 9pm mountain.22:38
dougwigblogan: my order is roughly: mechanism, pod, appliance, ... distant ..., ant/colony/grunt, ... far far away ..., device.22:38
sbalukoffI totally changed my vote.22:41
sbalukoffI'm so wishy-washy.22:41
sbalukoffAnd... back again.22:41
sbalukoffSo sneaky!22:42
sbalukoffOk, so... I need to go AFK for a while, I've got a massive gut-ache and I'm starting to get loopy. Catch y'all later.22:42
rm_workI thought you DIDN'T like Appliance?22:46
rm_workor that Octavia as a whole is supposed to be an "appliance"22:46
rm_workso having an Appliance with internal Appliances makes little sense22:46
dougwigi don't like appliance, since depending on the lbaas spinout ,we could have appliance meaning two different things.22:46
rm_workyes22:47
rm_workit's on my list of "bad"22:47
dougwigthird on my list is not above the "like" line.  :)22:47
rm_workbut now I am worried that if I spread out my vote, Appliance could win :)22:47
dougwiglol22:47
rm_workI don't like mechanism because the implication just seems... wrong to me22:47
rm_workI'll vote for pod if you do :)22:47
rm_workjust please god not appliance22:48
dougwigi don't like ant because it's such a common build system, that having an ant subdir will have obvious implications.22:48
rm_workwhy did I forget to -1 appliance earlier T_T22:48
dougwigi don't like device because it's about as vague as "object".22:48
rm_workdougwig: right, agree22:48
rm_workI liked worker for that T_T22:48
rm_workworker/colony22:48
rm_workant is >_<22:48
rm_workworker describes the thing quite well, not sure why people so vehemently dislike it22:48
dougwigthat combo was -1.22:49
dougwigif i pull that in, the list gets way long.22:49
rm_workyeah >_>22:50
rm_worki think probably the only reason ant/colony wasn't -1 as well was because the person who -1'd the whole list including worker, was already offline when ant/colony was added :P22:50
rm_workor, not the whole list, but... >_>22:51
rm_worklol trevor did -1 to everything but toadlactica, "", and container22:51
rm_workrofl22:51
rm_workso wha'd'ya say? pod? i'm not a huge fan of mechanism, but I HATE appliance22:52
rm_workand if we both vote pod, it's not as scary]22:52
blogando mechanism over pod22:52
rm_workyou voted for appliance >_>22:53
bloganso22:53
bloganid rather have mechanism over pod22:53
bloganso you do as i say22:53
rm_worklol22:53
sbalukoffI'm back on the 'pod' bandwagon.22:53
rm_workwoot22:53
blogandamny you sbalukoff!22:53
bloganand damn22:53
rm_workpod makes sense as a thing that "contains" the haproxy/nginx/whatever22:53
rm_workmechanism... >_>22:54
rm_workand appliance is a conflict22:54
bloganthis is going ot be shuffling of votes because i will vote for mechanism if it looks like appliance will be the equivalent of ron paul22:54
rm_worklol22:54
bloganhonestly, i'd be fine with any of those 322:54
bloganpod i feel a bit dirty with, but ive felt dirtier before and quickly got over that22:55
dougwigtoo bad we didn't add some roman themed containers.  amphora, aqueduct, etc.22:55
rm_workI still like worker best but pod is my second choice from the list i think22:55
dougwiggiven our project name.22:55
rm_workyeah22:55
sbalukoffcistern22:55
rm_workdougwig: i was just thinking we are really bad shape here thematically22:55
bloganquick dougwig22:55
blogando it22:55
rm_workohshiiiii\22:55
bloganfind something22:55
rm_workcan we restart voting with better names plox >_>22:55
rm_workeven cistern is better22:55
rm_worklol22:55
bloganive gotta take care of a baby22:55
rm_workamphora is good actually22:56
dougwigfuck it, voting is postponed until tomorrow.  these names all suck.  let's explore the roman theme.22:56
sbalukoff...22:56
sbalukoffseriously?22:56
rm_workdude, amphora22:56
rm_workwe should really have stuck to theme22:56
dougwigsbalukoff: half?22:56
sbalukoffThat's true.22:56
sbalukoffI guess Octavia is a roman name.22:56
rm_workyes22:56
dougwigi only thought of the roman thing 5 minutes ago.22:56
sbalukoffSee, dougwig!22:57
rm_workthat and this "second round of voting" after everyone at rackspace has left except me and brandon, is ... >_<22:57
sbalukoffYou should totally have taken this thing seriously earlier. XD22:57
rm_workyeah I had been thinking about thematic names but i forgot it was roman22:57
sbalukoffrm_work ... awesome?22:57
dougwigdude, i have been trying to think of names since last week.  i can't control inspiration.22:57
rm_worksbalukoff: lol22:57
rm_workright? just needed a muse22:57
sbalukoffdougwig: There's an RFC for that.22:57
dougwighaha, you switched to pod again?22:58
rm_workso do all parties present agree to postpone? :P22:58
sbalukoff(see earlier statements about me being loopy.)22:58
dougwigwhat say ye, slip in some roman names and leave the final vote open until tomorrow?  roll with what we've got?  restart from scratch?22:58
sbalukoffWell, let's hear some roman name suggestions.22:58
rm_workAmphora22:58
rm_workwas his and mine22:58
dougwigamphora, aqueduct, cistern22:59
dougwigdolium22:59
rm_workamphora is thematic, very accurate, and doesn't conflict directly with "container"22:59
rm_workand a lot of people hopefully don't have to look it up, i think22:59
dougwigchariot?22:59
rm_workI knew the word already...22:59
rm_workhmm22:59
rm_workyeah anyway, I think we restart with this narrowed down list + roman stuff22:59
rm_workI think there are some clear winners in the roman group23:00
sbalukoffpithos23:00
dougwigcaltrop (i never knew that was roman)23:00
rm_workbut we have to be fair to the existing ones I guess23:00
sbalukoffThe amphora complements the large storage container, the pithos, which makes available capacities between one-half and two and one-half tons.23:00
rm_workwait caltrop is roman? and... related?23:00
rm_workisn't a caltrop a spike for injuring marching footmen/cavalry?23:00
sbalukoffI like chariot23:00
sbalukoffrm_work: It is.23:00
dougwigrm_work: it was a hit when googling "roman device"23:01
rm_worknot sure caltrop provides great imagery :P23:01
rm_workhah23:01
rm_workI googled "roman container"23:01
rm_workbecause other than the naming conflict, container is the idea we're trying to get across23:01
dougwigyeah, that was my first google.23:01
rm_workI see Dolium too23:01
rm_workthough I feel like that is less well known than Amphora23:02
rm_worksmall, agile, and very numerous23:02
*** vivek-ebay has quit IRC23:02
rm_workand Amphorae is a good plural :P23:02
*** vivek-ebay has joined #openstack-lbaas23:03
rm_workI think Amphora has my vote, i feel MUCH better about that than any of the shitty options we started with :P23:03
rm_workglad dougwig had some inspiration in the nick of time23:03
rm_workah so we're just adding them instead of voting to postpone? :P23:04
* dougwig feigns innocence23:04
*** TrevorV_ has joined #openstack-lbaas23:04
*** vivek-ebay has quit IRC23:04
sbalukoffChanging sides again.23:04
dougwigi'm joining you23:04
sbalukoffWe can call it 'amp' for short.23:05
sbalukoffBecause I like shortening things.23:05
rm_workyeah i like that23:05
rm_workeasy to shorten in conversation to "amps23:05
sbalukoffAnd we totally won't call it by a 3-syllable name in the long run. ;)23:05
rm_work"23:05
rm_workblogan: quick, change your vote23:05
rm_work:P23:05
sbalukoffHAHA23:05
*** vivek-ebay has joined #openstack-lbaas23:05
rm_workcistern makes me think of toilets >_>23:06
bloganso i do have some reservations about this now23:06
rm_workblogan: i have some reservations about your face23:07
rm_workbut i'll let them slide this once23:07
sbalukoffHAHA23:07
bloganone argument for going against one of those is that someone new coming into the project would not know what appliance/device or whatever means23:07
sbalukoffGood! Read some fscking docs. ;)23:07
rm_workheh23:07
blogani guarandamntee you that new people will not know what amphora will be23:07
rm_workright23:07
rm_workbut they won't MISTAKE IT for another concept23:07
sbalukoffNo really... that's probably because they don't understand what the actual meaning of the word 'amphora' is.23:07
rm_workit'll just be an unknown until they read up23:07
sbalukoffOnce they learn that, they'll understand.23:07
blogansbalukoff: thats what i mean23:07
sbalukoffrm_work:23:08
bloganits a container23:08
sbalukoffYes, avoiding conflict with another term is actually better here.23:08
rm_workright23:08
bloganso if container had a problem wouldnt this?23:08
sbalukoffYeah, but we chose another term because 'container' means different things in other contexts.23:08
sbalukoffIt could very well be a VM.23:08
* rm_work gets out his gladiator gear in preparation to agree VIOLENTLY with sbalukoff 23:08
sbalukoffDo you know of anything else named 'amphora' in IT?23:08
bloganim not saying im against it, just saying there could be issues23:08
sbalukoffor computer science?23:08
rm_workyes, and Amphora MEANS container, but doesn't have the same specific connotation as the english WORD container23:09
rm_workwhich is why it works23:09
sbalukoffOh man, I'm totally going to re-watch that movie tonight.23:09
rm_workexcellently23:09
bloganis a good point23:09
sbalukoffSpecifically amphora is a smallish jar.23:09
sbalukoffSo, I like that over other words for 'container' in roman, too.23:09
rm_workyeah. well, somewhat small. not small compared to a mason jar :P23:09
bloganwell, why are we sending commands to a smallish jar23:10
sbalukoffBecause these things are supposd to be smallish. We'll just have a ton of them in a large cloud.23:10
dougwigwe're not... we're sending them to AMPHORA!!!!23:10
rm_workbecause we use smallish-VMs/containers :P23:10
bloganlets just call it elysium23:10
rm_worksbalukoff: exactly :P23:10
rm_workand amphorae were small but used in large numbers :P23:10
rm_workso, perfect!23:10
sbalukoffrm_work is totally convincing me.23:10
rm_worksbalukoff: pfft, what, *you* are convincing *me*23:11
rm_workwhat's going on here23:11
bloganhe never quits until he has or one of you are dead23:11
rm_worki'm confused because we are in a feedback loop i think23:11
rm_workconvincing each other23:11
sbalukoffHaha23:11
rm_workof the same thing23:11
sbalukoffviolent agreement.23:12
dougwigcircle jerk detected!23:12
blogani like it better than pod23:12
rm_workhaha23:12
sbalukoffYou're right, dammit!23:12
sbalukoffblogan: +123:12
rm_work+1s all around23:12
bloganbut also should this be decided on with a minority?23:12
* rm_work is going to be super disappointed when he looks in the morning and amphora is losing somehow23:12
sbalukoffToo late. I'mma go update design docs and diagrams now.23:12
sbalukoff;)23:13
rm_workI mean, I think the plan is still to do the vote via the page23:13
rm_workbut23:13
bloganwhen does the vote close?23:13
rm_workamphora should be +4 now against 023:13
dougwigthe vote is staying open until tomorrow at lunchtime.23:13
* rm_work glares at blogan 23:13
sbalukoffHaha!23:13
rm_workoh wait, is that blogan voting for appliance, or some unnamed person23:13
sbalukoffSo, we'll document this decision on the non-arbitrary decisions page.23:13
rm_workthere's two of almost the same exact color23:13
sbalukoffThough it still is rather arbitrary.23:13
blogan so you're saying I have until lunch for you to pander to me for my vote?23:14
rm_worklol23:14
dougwigthat's blogan.  and you know what happened to traitors in rome.23:14
sbalukoffBut still. WE WASTED TIME ON THIS! So, we're definitely not not documenting it.23:14
blogangifted with gold and set free to go make their own country?23:14
rm_workwhelp. i'm happy with this "decision".23:14
rm_worktime to head home then :)23:14
dougwigi'll note that my original patchset had vm/driver, which NOT ONE PERSON actually misunderstood.23:14
sbalukoffblogan: Yes, of course. Let me just size up this cross for you...23:14
rm_workugh, early morning meeting tomorrow23:14
sbalukoffrm_work: Yeah. :P23:15
rm_workglad I'm no longer in PST... though I feel like I am >_>23:15
bloganno one misunderstood because we've been using that term for a while because we know the first iterations will be using VMs23:15
sbalukoffdougwig: Yep.23:15
*** mlavalle has quit IRC23:15
bloganmy kid is so fussy right now23:17
sbalukoffWhy are you paying attention to your kid when you could be paying attention to me?23:18
sbalukoffHas anyone thought of my feelings here?23:18
sbalukoffOk, seriously, heading offline now.23:19
bloganyou are like baby huey23:19
*** mlavalle_ has joined #openstack-lbaas23:21
TrevorV_HA I forgot to vote... damnit :D23:22
TrevorV_Sucks to be me23:22
sbalukoffhttp://33.media.tumblr.com/tumblr_lhhkdyZ4zm1qcrozeo1_500.gif23:23
sbalukoffMaybe like that.23:23
sbalukoffTrevorV_: VOTE! It's ongoing.23:24
sbalukoffBut you missed the discussion of amphora earlier23:24
sbalukoffYou're totally off the project if you don't vote for amphora.23:24
sbalukoffJust sayin'23:24
TrevorV_sbalukoff: You're supposed to be offline by now right?23:25
TrevorV_Link me real quick, I'll put in a vote23:25
sbalukoffArgh! Dammit!23:25
TrevorV_Lulz23:25
*** ptoohill has quit IRC23:25
sbalukoffhttps://etherpad.openstack.org/p/octavia-backend-name23:25
sbalukoffI am supposed to be offline.23:25
TrevorV_See you tomorrow morning sbalukoff (so GTFO bruh!)23:26
sbalukoffHeh! Will do!23:26
rm_workha, spirited away baby :P23:28
rm_workoh right and i was going home23:28
* rm_work homes23:28
*** TrevorV_ has quit IRC23:28
*** mlavalle_ has quit IRC23:54

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