Tuesday, 2014-08-12

*** vivek-ebay has quit IRC00:01
*** ptoohill-oo has joined #openstack-lbaas00:03
*** sbfox has quit IRC00:08
*** xgerman has quit IRC00:22
sbalukoffrm_work: That sucks.00:37
*** fnaval has quit IRC00:39
*** fnaval has joined #openstack-lbaas00:39
*** fnaval has quit IRC00:44
*** VijayB_ has quit IRC01:00
rm_yousbalukoff: yep :(01:08
*** mlavalle has quit IRC01:11
*** woodster_ has quit IRC01:25
*** sbfox has joined #openstack-lbaas01:34
bloganyikes zuul is backed up like crazy01:46
bloganim sure that is normal for this stage in the release cycle01:46
bloganah man robin williams died01:49
*** vjay has joined #openstack-lbaas01:52
*** fnaval has joined #openstack-lbaas01:54
*** fnaval has quit IRC02:03
*** sbfox has quit IRC02:05
dougwigi think you just killed zuul.02:10
*** fnaval has joined #openstack-lbaas02:22
*** sbalukoff has quit IRC02:23
*** VijayB_ has joined #openstack-lbaas02:25
*** ptoohill-oo has quit IRC02:28
*** vivek-ebay has joined #openstack-lbaas02:28
*** vivek-eb_ has joined #openstack-lbaas02:35
*** vivek-ebay has quit IRC02:35
*** ptoohill-oo has joined #openstack-lbaas02:52
*** VijayB_ has quit IRC03:06
bloganand a failure in a tempest test unrelated03:10
*** crc32 has quit IRC03:41
*** sbfox has joined #openstack-lbaas03:41
*** woodster_ has joined #openstack-lbaas03:44
dougwigat least you'll get the notice like 9 times.03:50
yfriedblogan: I mean that I'd like to be able to do "lb-version" and get "1" or "2" in return03:51
*** HenryG is now known as HenryG_afk04:14
*** yfried has quit IRC04:29
*** sbalukoff has joined #openstack-lbaas04:30
*** fnaval has quit IRC04:31
*** enikanorov has quit IRC05:10
*** enikanorov has joined #openstack-lbaas05:11
*** vivek-ebay has joined #openstack-lbaas05:31
*** vivek-eb_ has quit IRC05:34
*** vivek-ebay has quit IRC05:35
*** yfried has joined #openstack-lbaas05:44
*** woodster_ has quit IRC05:45
*** evgenyf has joined #openstack-lbaas06:07
*** sballe has joined #openstack-lbaas07:27
*** ptoohill-oo has quit IRC07:29
*** jschwarz has joined #openstack-lbaas07:32
jschwarzmorning guys07:32
jschwarzI encountered this bug https://bugs.launchpad.net/python-neutronclient/+bug/1353536 a while back, which effects my ability to create a healthmonitor whatsoever07:35
jschwarzCan anyone offer a solution? seems like the launchpad bug isn't getting any attention :(07:35
openstackgerritStephen Balukoff proposed a change to stackforge/octavia: Octavia v0.5 component design  https://review.openstack.org/11345807:52
sbalukoffDang... can't seem to log into launchpad to add comments to my own gerrit review above. :P07:56
sbalukoffAah well.. I guess I should get some sleep anyway.07:56
*** sbfox has quit IRC08:03
*** Krast has joined #openstack-lbaas08:06
*** yfried is now known as yfried_afk08:27
*** Krast has quit IRC08:40
*** Krast has joined #openstack-lbaas08:40
*** vjay has quit IRC08:40
jschwarzanybody? nobody? :<09:21
*** evgenyf has quit IRC09:27
*** evgenyf has joined #openstack-lbaas09:32
Krast:)09:33
*** ctracey has quit IRC09:49
*** ctracey has joined #openstack-lbaas09:53
*** yfried_afk is now known as yfried10:35
*** sballe has quit IRC10:46
*** Krast has quit IRC10:50
*** jschwarz is now known as jschwarz|away11:07
*** jschwarz|away is now known as jschwarz11:48
*** HenryG_afk is now known as HenryG13:02
*** blogan has quit IRC13:27
*** ptoohill has quit IRC13:28
*** TrevorV has quit IRC13:28
*** vjay has joined #openstack-lbaas13:28
*** evgenyf has quit IRC13:29
*** ptoohill has joined #openstack-lbaas13:33
*** blogan has joined #openstack-lbaas13:33
*** TrevorV has joined #openstack-lbaas13:34
*** TrevorV has quit IRC13:39
*** ptoohill has quit IRC13:39
*** blogan has quit IRC13:40
*** ptoohill has joined #openstack-lbaas13:45
*** blogan has joined #openstack-lbaas13:46
*** TrevorV has joined #openstack-lbaas13:46
*** evgenyf has joined #openstack-lbaas13:53
*** ptoohill-oo has joined #openstack-lbaas13:59
*** ptoohill-oo has quit IRC14:08
*** ptoohill-oo has joined #openstack-lbaas14:20
*** ptoohill-oo has quit IRC14:29
*** ptoohill-oo has joined #openstack-lbaas14:30
*** sbfox has joined #openstack-lbaas14:44
*** markmcclain has joined #openstack-lbaas14:44
*** vivek-ebay has joined #openstack-lbaas14:46
*** sbfox has quit IRC14:59
*** markmcclain1 has joined #openstack-lbaas15:00
*** markmcclain has quit IRC15:01
dougwigjschwarz: on that bug, yikes.   the optional args are not being treated positionally.15:11
dougwigI'll add something to launch pad shortly.15:12
jschwarzdougwig, you mean like this one: https://bugs.launchpad.net/python-neutronclient/+bug/1353536 ?15:15
jschwarzdougwig, It is caused by a patch Kevin Benton added a couple of weeks back which adds a nuetron --timeout argument15:16
*** xgerman has joined #openstack-lbaas15:16
jschwarzDiscussed this with Ilya Shakhat and decided I should talk with Kevin and see what he thinks (because technically its his bug)15:17
*** jorgem has joined #openstack-lbaas15:20
*** mlavalle has joined #openstack-lbaas15:20
*** vivek-eb_ has joined #openstack-lbaas15:24
*** vivek-ebay has quit IRC15:26
*** jschwarz has quit IRC15:32
*** mlavalle has joined #openstack-lbaas15:35
*** ptoohill-oo has quit IRC15:35
*** orion__ has joined #openstack-lbaas15:42
*** woodster_ has joined #openstack-lbaas15:44
dougwigok.  i put my $0.02 in the bug report as well.15:52
dougwigblogan: i think you got rebased.15:58
TrevorVdougwig, blogan is off today, not sure he'll be around to respond for you16:06
TrevorV2ยข16:06
TrevorVHa, sorry, had to look up the cent symbol and see if it worked in chats :D16:07
dougwigok.  if anyone needs our code today, be sure to pull it from the last patchset that blogan pushed, NOT the latest.  it got stomped.  ping me if you need help.16:07
TrevorVAlright will do16:07
*** vivek-ebay has joined #openstack-lbaas16:10
*** yfried_ has joined #openstack-lbaas16:13
*** sbfox has joined #openstack-lbaas16:13
*** vivek-eb_ has quit IRC16:14
*** yfried has quit IRC16:14
*** vivek-ebay has quit IRC16:14
*** evgenyf has quit IRC16:15
*** yfried__ has joined #openstack-lbaas16:16
*** yfried_ has quit IRC16:20
*** yfried__ has quit IRC16:22
xgermanTrevorV, rmwork: not sure if you alreday saw sbalukoff's new proposal: https://review.openstack.org/#/c/113458/1/doc/source/design/version0.5/component-design.rst16:22
xgermanI got it from Susanne so I am not sure how well it's advertised16:22
TrevorVxgerman, I did not, but I'll look at it right now, thanks :)16:23
*** sbalukoff has quit IRC16:25
TrevorVAnyone around that can help me with this?  I'm trying to "./stack.sh" on ubuntu 14.04 and I'm getting this16:34
TrevorV2014-08-12 16:23:47.883 | +++ nova flavor-list16:34
TrevorV2014-08-12 16:23:48.254 | ERROR (AttributeError): 'module' object has no attribute 'add_arg'16:34
TrevorVAside from that, I don't have a stack trace16:34
*** vivek-ebay has joined #openstack-lbaas16:40
*** markmcclain1 has quit IRC16:42
*** sbfox has quit IRC16:45
orion__TrevorV: maybe try increasing log level to get more output?17:01
*** mestery has quit IRC17:02
*** magesh_ has joined #openstack-lbaas17:02
*** mestery has joined #openstack-lbaas17:03
*** jschwarz has joined #openstack-lbaas17:12
*** ptoohill-oo has joined #openstack-lbaas17:12
vjayHey all!17:15
vjayAnyone knows/remembers why stats were moved from pool in V1 to loadbalancer in V2?17:15
dougwighi vjay.  because LB's are analogous to what pool's were in v1.  we have plans to add stats to all the objects, but not in juno.17:20
vjayhi dougwig. LB == pool, didnt understand :-(. only thing common between them is the provider attribute i guess.17:21
xgermanthe idea is that stats sort of get rolled up in LB17:22
dougwigwell, they're both the logical root node of a single load balancer, is what i meant.  the end result being that you get stats for a single vip/virtual server in both versions.17:22
xgermanalso the stats stuff (for ceilometer) is going from a pull to a push system in Kilo17:23
vjaydougwig: vip of v1 == listener of v2. in V1 stats were rolling up max to this entity not difinely to the actual virtual IP level across listeners.17:26
dougwigvjay: but vips and pools are 1:1 in v1, so it's the same difference.17:26
vjayvip != virtual ip in V117:27
vjayterminology problem17:27
xgermanyeah, I am glad 2.0 improves on that17:28
dougwigok, i sense a disconnect.  how are the numbers between v2 and v1 functionally different?  i know we want to enhance them, but that is post-refactor.17:28
vjaythe stats itself dont make much sense for me17:29
xgermanso the numbers in 1.0 are broken - so I wouldn't get too hung up if there is a disconnect17:29
vjayi would expect a different kind of stats for VIP/loadbalancer17:29
vjayand different one for listeners17:29
vjayi would like to see connection stats in listener17:30
vjaynot in LB.17:30
vjayLB==loadbalancer17:30
xgermanyeah, that sounds useful17:31
xgermanbut we also need the roll up to see what the IP generates17:31
xgerman(or box for that matter)17:31
vjayit is really usecase based17:31
vjayi dont see the use for rolling up now17:32
xgermanwe like to bill per load balancer17:32
vjaycant that be done by bytes transmitted?17:32
vjayand received?17:32
vjayok i see it17:33
vjayso all loadbalancer's stats are summed to bill right?17:34
xgermanyes, that's the plan17:34
vjayWill there be a problem to sum all listener stats and bill?17:35
*** yfried__ has joined #openstack-lbaas17:36
xgermanlet's say our preference is to collate in LBaaS and not ceilometer17:36
vjayok17:37
xgermanbut we can take it to the mailing list and see what others think17:37
vjaysure17:37
dougwigthe plan for kilo is to add stats() calls to every object.  you can pick at what level you pull them.17:39
xgermandon17:39
xgerman't forget the push proposal for ceilometer17:39
xgermanso you can pick but some (like lbs) might push17:40
dougwigi haven't, but that relies on an agent or octavia.17:40
xgermanyep17:40
*** sbalukoff has joined #openstack-lbaas17:47
sbalukoffOh yes-- the v0.5 component design document is out. (openstackgerrit bot announced it in channel here last night.)17:51
rm_worksbalukoff: nice, i'll get to reading that17:54
sbalukoffIt's pretty similar to the v1.0 design, except everything that touches the Intermediate Message Bus has been collapsed down to just a 'controller'17:55
rm_workwe weren't going to have *any* HA really until 1.0 right?17:56
rm_workand even then, minimal?17:56
rm_workor was HA/scale not till 2.0?17:57
*** mestery has quit IRC18:00
*** VijayB has joined #openstack-lbaas18:01
*** jschwarz has quit IRC18:03
*** jschwarz has joined #openstack-lbaas18:04
*** jschwarz has quit IRC18:07
*** sbfox has joined #openstack-lbaas18:12
dougwigdefine HA?  HA with VMs is kind of like building a castle with a permanently open gate.18:13
*** sbfox1 has joined #openstack-lbaas18:15
*** sbfox has quit IRC18:17
rm_worksbalukoff: reviewed...18:18
rm_workI had some questions18:18
sbalukoffrm_work: 0.5 will have no HA at the controller level built into the design. This should still be achievable through external means (eg. set up two machines and run your own scripts to start/stop controller services on fail-over)18:19
sbalukoffv0.5 does have HA at the service delivery level.18:19
sbalukoffv1.0 has HA features built into the design.18:19
rm_workah ok i was thinking at the LB level18:19
rm_workso yes, it does still18:19
sbalukoffYep.18:19
sbalukoffWe can't use it at all without HA. :)18:20
rm_workStandby pool // Active/Standy18:20
sbalukoffYep!18:20
rm_workanywho, see my comments on review18:20
sbalukoffSounds good.18:20
sbalukoffI also just responded to Susanne's comments.18:20
sbalukoffI'll take a look at yours. :)18:21
*** markmcclain has joined #openstack-lbaas18:21
*** ptoohill-oo has quit IRC18:23
*** vjay has quit IRC18:31
sbalukoffrm_work: Ok, I responded to your comments. :)18:31
*** crc32 has joined #openstack-lbaas18:32
*** vjay has joined #openstack-lbaas18:33
*** crc32 has quit IRC18:33
*** crc32 has joined #openstack-lbaas18:34
*** vivek-eb_ has joined #openstack-lbaas18:34
*** vivek-eb_ has quit IRC18:35
rm_workk18:36
*** vivek-eb_ has joined #openstack-lbaas18:36
*** vivek-ebay has quit IRC18:37
*** vivek-eb_ has quit IRC18:58
*** vjay has quit IRC19:07
openstackgerritStephen Balukoff proposed a change to stackforge/octavia: Octavia v0.5 component design  https://review.openstack.org/11345819:25
*** magesh_ has quit IRC19:26
sbalukoffrm_work and sballe: There are a couple significant changes in the above new revision of that patch, specifically around the operator API. :)19:26
*** mestery has joined #openstack-lbaas19:27
*** whytewolf has joined #openstack-lbaas19:45
*** VijayB has quit IRC19:56
*** jorgem has quit IRC20:03
*** sbfox1 has quit IRC20:05
*** sbfox has joined #openstack-lbaas20:17
*** mlavalle has quit IRC20:18
rm_workkk20:20
rm_worksbalukoff / dougwig / xgerman: could you remind me why we were allowing for colocation / apolocation hints? what is the point of apolocation exactly? (this may be setup for a followup question)20:21
*** ptoohill-oo has joined #openstack-lbaas20:22
*** magesh_ has joined #openstack-lbaas20:27
*** mlavalle has joined #openstack-lbaas20:36
*** crc32 has quit IRC20:38
*** VijayB has joined #openstack-lbaas21:02
*** fnaval has joined #openstack-lbaas21:06
*** VijayB has quit IRC21:06
*** VijayB has joined #openstack-lbaas21:07
*** mlavalle has quit IRC21:17
*** sbfox has quit IRC21:22
*** yfried__ has quit IRC21:25
*** crc32 has joined #openstack-lbaas21:36
xgermanrm_work the colocation/apolocation thing is not that relevant for us since we can't control the rack things end up -- the only use would be to schedule things in different availability zones22:14
rm_workok yeah22:14
rm_workso if we only have one AZ per DC, then... for instance, Rackspace wouldn't even bother to expose those features22:14
rm_workthat is what I was thinking22:14
rm_workbecause we don't really have control of nova's scheduler22:15
xgermanyep - I think Bluebox can control the Rack they end up in22:15
rm_workand with the setup we're thinking of using, it won't even matter where they are22:15
rm_worklike... if that CAB goes down, it's probably because the DC went down <_<22:15
xgermanwell, in any network if you could schedule your backend nodes and the lb on the same CPU then you would have more spped22:16
rm_workyeah but our users have no visibility to that :P22:16
xgermanneither to ours22:17
*** sbfox has joined #openstack-lbaas22:35
rm_worksbalukoff: see PM22:40
xgermanrm_work: Did you figure out what the USER APIU HANDLER is in the .5 spec. Wouldn't the user talk through Neutron LBaaS with Octavia?22:59
rm_workwell23:03
rm_workunless Octavia does have its own API eventually (which it should)23:03
rm_workthe section is probably there for future specs23:03
*** ptoohill-oo has quit IRC23:03
rm_workxgerman: ^^23:04
xgermanyep, future specs23:04
xgermanor as a life insurance if lbaas v2.0 never makes it23:04
rm_workheh yeah23:04
rm_workthat's actually a good call23:04
rm_workwith the current clusterf&$%23:04
rm_workwe may need to accelerate our spinoff plans23:05
rm_worklol23:05
xgermanlikely --23:05
xgermanrm_work, sbalukoff: Also johnsonm and I think that simplifying by just putting everything in one daemon will make it difficult to split tasks23:23
xgermanbetween people (I am not very fond of watching the rebasing hell brandon lives in)23:24
sbalukoffxgerman: There's no reason we couldn't make the controller multiple daemons, really...  but doing so at this point is less important than getting its external interfaces correct.23:24
sbalukoff(Interfaces to Neutron, Neutron LBaaS and Octavia VMs)23:24
xgermanunderstood. I just don't want to close the door on that before we have a better idea how to split work23:25
sbalukoffYep!23:25
*** sbfox has quit IRC23:25
sbalukoffI'm actually in favor of making the controller several daemons, but it does add extra complexity to the project up front...  0.5 is sort of a proof of concept of "does this model using Octavia VMs work?"23:26
sbalukoffIt's not the scalable version we all need.23:26
sbalukoffxgerman: In any case, please add those comments in gerrit, too-- so they're perserved (sort of) for posterity?23:27
xgermanof course :-)23:27
xgermanyeah, I also like the proof of concept idea but I found it easier to split work when everybody gets their own component23:28
sbalukoffAgreed.23:29
sbalukoffThere are a several ways to skin this cat.23:29
sbalukoffThe design is meant to be "simple enough" but if enough of y'all agree that we should just plan on having several daemons that work in tandem on the same box (later to become separate controllers on separate boxes), I'm happy to alter the design, eh.23:29
sbalukoffoh, on the apolocation / colocation stuff:  This is usually stuff driven by business requirements, sometimes having to do with security.23:31
sbalukoffFor example, a customer may need to guarantee that loadbalancer 1 and loadbalancer 2 are never served from the same physical hardware.23:31
sbalukoffShoudln't matter in a cloud... but then, these kinds of requirements usually come from people who aren't used to the cloud paradigm.23:32
sbalukoffThere's also performance reasons a customer might want this.23:32
sbalukoffThe cloud is supposed to be immune to bad neighbor problems. But as operators, we know this often isn't the case.23:32
sbalukoffAnd customers figure that out, too.23:32
sbalukoffSo...  there's a need for colocation / apolocation logic.23:33
sbalukoffAnd the ability to colocate several loadbalancers on the same Octavia VM is an operator optimization that some might want to use to consume fewer resources in large public clouds.23:34
sbalukoff(And also on private clouds)23:34
sbalukoffWe occasionally get customers who want all their dev environments to be functionally equivalent to production, but not necessarily performance-equivalent.23:34
sbalukoffAnd depending on how they're billed, there might be an incentive for them to colocate all their dev loadbalancers on the same VM.23:35
sbalukoffAgain, these are requirements that come down the pipe from customers... and since they can be implemented without too much trouble on our part, I don't see a major reason not to allow it.23:36
sbalukoff(Well, partially from customers, partly from our management and product people.)23:36
dougwigpresumably we'll use a framework that abstracts the controllers enough that splitting it later or sooner is trivial?  (I haven't used pecan, but if split or not split is a gate, that sounds like duplicated glue/bugs.)23:36
sbalukoffdougwig: That's what I'd recommend.23:37
dougwigsbalukoff: hey, some people like reinventing wheels.  they're never round, but hey.23:38
sbalukoffMmm.... delicious repetition.23:39
rm_workhmm ok, the design we're considering doesn't really make any sense at all for apo/co-location, for ANY of the reasons you listed (including incentive to co-locate to save costs), but I guess we'll talk about it tomorrow at the meeting23:42
*** whytewolf has left #openstack-lbaas23:45
*** fnaval has quit IRC23:51
*** fnaval has joined #openstack-lbaas23:51
*** fnaval has quit IRC23:56
xgermansame here -- no colocation requirement23:57
*** fnaval has joined #openstack-lbaas23:59

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