Wednesday, 2017-04-19

openstackgerritAdam Harwell proposed openstack/octavia master: Remove singleton pattern from API controllers  https://review.openstack.org/45781300:00
openstackgerritAdam Harwell proposed openstack/octavia master: Introduce Octavia v2 API for Health Monitor  https://review.openstack.org/40625600:01
*** reedip has joined #openstack-lbaas00:08
johnsomOk, I am going to start preping dinner.  Ping me if there are things I should take a look at.00:12
*** JudeC has quit IRC00:20
*** JudeC has joined #openstack-lbaas00:22
rm_workk00:23
*** amotoki has quit IRC00:45
*** amotoki has joined #openstack-lbaas00:50
*** johnsom has quit IRC00:53
*** johnsom has joined #openstack-lbaas00:53
*** ajo has quit IRC00:54
*** amotoki has quit IRC00:59
*** ajo has joined #openstack-lbaas01:00
rm_workalmooooost....01:05
*** JudeC has quit IRC01:10
*** amotoki has joined #openstack-lbaas01:14
openstackgerritMerged openstack/neutron-lbaas master: Use OS_AUTH_URL instead of baked in defaults  https://review.openstack.org/45778101:14
openstackgerritAdam Harwell proposed openstack/neutron-lbaas master: Trying a different strategy for fixing py3 errors in testing  https://review.openstack.org/45739401:21
rm_workok rebased and +A01:23
*** aojea has joined #openstack-lbaas01:30
*** fnaval has quit IRC01:32
*** aojea has quit IRC01:36
*** gongysh has joined #openstack-lbaas01:54
*** amotoki has quit IRC02:35
*** amotoki has joined #openstack-lbaas02:50
*** fnaval has joined #openstack-lbaas02:54
rm_workjohnsom: i see you got most of the rechecks02:58
rm_workI was just going looking and noticed they all floated to the top :P02:58
johnsomYeah, had a minute after dinner02:58
*** csomerville has quit IRC02:59
*** csomerville has joined #openstack-lbaas03:00
rm_worktesting the py3 docs fix now03:01
rm_worksince we have no gate for it...03:01
*** sanfern has joined #openstack-lbaas03:02
*** JudeC has joined #openstack-lbaas03:06
*** ducnc has quit IRC03:06
*** ducnc1 has joined #openstack-lbaas03:07
rm_workok, i hit merge on a few n-lbaas patches that look good to go03:08
rm_worklooks like what I'd call "bugs" and testing-only, so whatever03:09
*** ducnc1 is now known as ducnc03:09
*** JudeC has quit IRC03:10
*** amotoki has quit IRC03:15
*** JudeC has joined #openstack-lbaas03:17
*** links has joined #openstack-lbaas03:19
*** jerrygb has joined #openstack-lbaas03:21
*** aojea has joined #openstack-lbaas03:32
*** amotoki has joined #openstack-lbaas03:35
*** aojea has quit IRC03:37
*** reedip has quit IRC03:50
openstackgerritMerged openstack/neutron-lbaas master: Trying a different strategy for fixing py3 errors in testing  https://review.openstack.org/45739403:53
*** ducnc1 has joined #openstack-lbaas03:56
*** gongysh has quit IRC03:56
*** ducnc has quit IRC03:56
*** ducnc1 is now known as ducnc03:56
*** chlong has quit IRC03:58
*** amotoki_ has joined #openstack-lbaas03:58
*** amotoki has quit IRC04:00
openstackgerritMerged openstack/neutron-lbaas master: Fix doc generation for Python3  https://review.openstack.org/45722504:01
openstackgerritMerged openstack/neutron-lbaas master: api test: Centralize listener/pool protocol  https://review.openstack.org/41507304:01
openstackgerritMerged openstack/neutron-lbaas master: api test: Add config options for listener/pool protocol  https://review.openstack.org/41507604:01
openstackgerritMerged openstack/neutron-lbaas master: api test: centralize health monitor protocol  https://review.openstack.org/41932404:01
*** amotoki_ has quit IRC04:06
openstackgerritMerged openstack/octavia master: Fix dumb error message typo  https://review.openstack.org/45695004:13
*** amotoki has joined #openstack-lbaas04:19
*** aojea has joined #openstack-lbaas04:33
*** links has quit IRC04:36
*** aojea has quit IRC04:38
*** links has joined #openstack-lbaas04:53
*** fnaval has quit IRC04:55
*** gongysh has joined #openstack-lbaas05:01
*** gcheresh_ has joined #openstack-lbaas05:18
*** amotoki_ has joined #openstack-lbaas05:23
*** links has quit IRC05:25
*** jerrygb has quit IRC05:25
*** amotoki has quit IRC05:26
johnsomYeah, I manually tested the py3 docs patch05:27
johnsomI just want to pull out the tox restrictions where they are implemented05:28
*** aojea has joined #openstack-lbaas05:32
*** links has joined #openstack-lbaas05:37
*** reedip_afk is now known as reedip05:40
*** armax has quit IRC05:48
*** JudeC has quit IRC05:53
*** aojea has quit IRC06:07
*** aojea has joined #openstack-lbaas06:07
*** rcernin has joined #openstack-lbaas06:08
*** aojea has quit IRC06:12
*** reedip has quit IRC06:23
*** reedip has joined #openstack-lbaas06:24
*** kobis has joined #openstack-lbaas06:25
*** voelzmo has joined #openstack-lbaas06:25
*** pcaruana has joined #openstack-lbaas06:33
*** JudeC has joined #openstack-lbaas06:56
*** tesseract has joined #openstack-lbaas07:01
openstackgerritM V P Nitesh proposed openstack/octavia master: Fix doc generation for Python3  https://review.openstack.org/45722407:20
openstackgerritYAMAMOTO Takashi proposed openstack/neutron-lbaas master: scenario test: configure scenario test protocols  https://review.openstack.org/41820107:20
*** aojea has joined #openstack-lbaas07:24
rm_worknmagnezi: err, did you run functional on that test locally? :P looks like a few fails07:25
rm_workhttp://logs.openstack.org/98/429398/34/check/gate-octavia-tox-functional-ubuntu-xenial/d1a4391/testr_results.html.gz07:25
rm_workjust need to change the tests actually :)07:26
rm_workcommented, just a one character change in one place lol07:27
*** JudeC has quit IRC07:35
*** jerrygb has joined #openstack-lbaas07:55
*** jerrygb has quit IRC08:00
*** ducnc has quit IRC08:06
*** cody-somerville has joined #openstack-lbaas08:09
*** cody-somerville has quit IRC08:09
*** cody-somerville has joined #openstack-lbaas08:09
*** csomerville has quit IRC08:11
*** amotoki_ has quit IRC08:22
openstackgerritMerged openstack/neutron-lbaas master: scenario test: configure scenario test protocols  https://review.openstack.org/41820109:10
*** dlundquist has quit IRC09:23
*** dlundquist has joined #openstack-lbaas09:23
*** amotoki has joined #openstack-lbaas09:29
*** amotoki has quit IRC09:45
*** amotoki has joined #openstack-lbaas09:58
*** belharar has joined #openstack-lbaas10:39
*** sanfern has quit IRC10:55
*** dmk0202 has joined #openstack-lbaas11:02
*** dmk0202 has quit IRC11:21
*** dmk0202 has joined #openstack-lbaas11:21
*** gongysh has quit IRC11:35
*** amotoki has quit IRC11:50
*** amotoki has joined #openstack-lbaas11:57
*** amotoki has quit IRC12:02
*** voelzmo has quit IRC12:23
*** kobis has quit IRC12:23
*** voelzmo has joined #openstack-lbaas12:23
*** kobis has joined #openstack-lbaas12:23
*** kobis has quit IRC12:23
*** voelzmo has quit IRC12:24
*** voelzmo has joined #openstack-lbaas12:24
*** sanfern has joined #openstack-lbaas12:30
*** krypto has joined #openstack-lbaas12:36
*** gongysh has joined #openstack-lbaas12:41
*** catintheroof has joined #openstack-lbaas12:48
*** kobis has joined #openstack-lbaas12:52
*** jerrygb has joined #openstack-lbaas12:53
*** vlaza has joined #openstack-lbaas12:59
vlazaHi everyone, can someone please point me to a functional guide to install Octavia on Ocata/RHEL_7 ? seems I cannot find the right way to do it..13:00
*** reedip_ has joined #openstack-lbaas13:06
*** reedip_ has quit IRC13:10
*** leitan has joined #openstack-lbaas13:17
leitanHi guys, is there any clear instructions on how to install / run octavia not in devstack? or its just build the image, upload+tag, and launch it ?13:18
*** leitan has quit IRC13:31
*** voelzmo has quit IRC13:38
*** voelzmo has joined #openstack-lbaas13:39
*** reedip_ has joined #openstack-lbaas13:42
*** voelzmo has quit IRC13:43
*** krypto has quit IRC13:43
*** voelzmo has joined #openstack-lbaas13:46
*** kobis has quit IRC13:58
*** links has quit IRC14:02
*** chlong has joined #openstack-lbaas14:03
*** kobis has joined #openstack-lbaas14:04
*** amotoki has joined #openstack-lbaas14:14
*** amotoki has quit IRC14:15
*** kobis has quit IRC14:16
openstackgerritNir Magnezi proposed openstack/octavia master: Auto detect haproxy user_group  https://review.openstack.org/42939814:23
*** belharar_ has joined #openstack-lbaas14:28
*** krypto has joined #openstack-lbaas14:30
*** belharar has quit IRC14:30
*** vlaza has quit IRC14:31
*** krypto has quit IRC14:36
*** fnaval has joined #openstack-lbaas14:37
*** krypto has joined #openstack-lbaas14:37
*** amotoki has joined #openstack-lbaas14:40
*** sanfern has quit IRC14:43
*** gcheresh_ has quit IRC14:51
johnsomvlaza leitan All we have right now is the quick start guide here: https://docs.openstack.org/developer/octavia/guides/dev-quick-start.html14:55
johnsomThis lays out the steps required to setup octavia.  You can also reference our devstack plugin script here: https://github.com/openstack/octavia/blob/master/devstack/plugin.sh14:55
johnsomWe hope to have a more step-by-step guide sometime during Pike14:56
*** kobis has joined #openstack-lbaas15:01
*** rcernin has quit IRC15:03
*** belharar_ has quit IRC15:03
*** voelzmo has quit IRC15:04
*** amotoki has quit IRC15:19
*** kobis has quit IRC15:24
*** kobis has joined #openstack-lbaas15:24
*** armax has joined #openstack-lbaas15:24
*** pcaruana has quit IRC15:28
*** gcheresh_ has joined #openstack-lbaas15:36
*** vlaza has joined #openstack-lbaas15:47
*** aojea has quit IRC15:51
*** sanfern has joined #openstack-lbaas15:53
*** tesseract has quit IRC15:59
rm_worknmagnezi: ugh, missed another one T_T16:03
rm_workjohnsom: I wish I knew where diltram was on the lxd gate :/16:04
rm_workthat would have been really nice to have, but it will be a ton of work to continue that and we had NO time for knowledge transfer :(16:05
johnsomYeah, I think he was waiting on an ubuntu backport to come through16:06
johnsomI may look into it at some point16:06
rm_workI wonder if he's still reachable16:08
rm_workjust to tell us what is going on16:08
rm_workso we can pick up his work16:09
rm_workdiltram: T_T16:09
*** dmk0202 has quit IRC16:09
rm_workxgerman: https://review.openstack.org/#/c/406256/16:11
rm_worknmagnezi: also https://review.openstack.org/#/c/454177/16:13
rm_workjohnsom: if you agree with me, you should remove your +2 as it is masking my -1 ^^16:13
rm_workif not, we should discuss16:14
rm_workwait, now I am confused because I thought when I commented it was on some other changes...16:14
johnsomIt needs to handle that input though right?16:15
johnsomYeah, that is just the imports16:15
rm_workwhere is the thing i was commenting on, wtf16:15
rm_workah, should that be a minimal response, or full response? for l7policy and pool16:16
rm_workmaybe that is what I meant16:16
rm_workoh, no16:16
johnsomIt's minimal, I'm pretty sure I opened a bug for that16:17
rm_workthey ARE used in the POST16:17
rm_worksee line 122/12316:17
rm_workIMO if we have a patch to fix this, it should *fix this* not just do the imports, when in reality, we don't even NEED the imports16:17
rm_workbecause I don't think we can take those things as part of the POST16:18
rm_workand we don't need them for the MinimalResponses16:18
rm_workI think in the end, those imports will actually *go away*]16:18
johnsomWhy can't you take them as part of the POST for single call create?16:18
rm_workfor single call create sure?16:19
rm_workbut this model is also for just Listener16:19
rm_workI mean... are we going to do it that way?16:19
rm_workcan you do a partial Single-Create?16:19
rm_workif you start from the Listener endpoint16:19
rm_workcan you do Listener+Pool+l7?16:19
johnsomI think so, yes16:20
rm_workok16:20
rm_workin that case, we need to HANDLE them16:20
rm_workbut you want to do that in a different patch?16:20
rm_workthis just seems like a sad patch, only does 2 characters change16:20
rm_workwhen there is a lot more work here16:20
johnsomYeah, I think the single call stuff is going to be a few patches16:20
rm_workbut, sure, I guess this is fine16:21
johnsomI agree, this is super small16:21
rm_workwhatever, I can just merge this16:21
rm_workand then start on fixing the rest16:21
rm_workthat is my next thing I think16:21
rm_workis the single-call16:21
rm_workwell, and trying to get the paging/sorting merged finally16:21
rm_workbasically I don't think that patch will DO anything16:22
*** gongysh has quit IRC16:22
rm_worksince we are changing the v1 to v2 for something that isn't actually looked at16:22
openstackgerritAdam Harwell proposed openstack/octavia master: Implement sorting and pagination for octavia  https://review.openstack.org/38214716:23
rm_work^^ just a rebase16:23
rm_workis xgerman back today?16:24
xgermanrm_work last day16:34
rm_workxgerman: err... ??16:36
rm_worklast day of vacation? or... *last day*?16:36
*** leitan has joined #openstack-lbaas16:37
rm_workleitan: from your earlier question, for us, we deploy by just making an image, pushing it to glance, and packaging up a venv with octavia installed16:39
rm_workleitan: it's very simple. because, we already have the rest of the cloud running, so we just point Octavia at it in config and it works16:39
leitanrm_work: ok, but if i want to do it outside a virtual env, living with the rest of the components16:40
leitanis there any place so i can read a step by step install16:40
leitan?16:40
rm_workI mean16:40
leitancause everything i can find16:40
leitanis for devstack16:40
rm_workyou would just install it16:40
rm_workyeah, you can look at what devstack does16:41
leitanif i do pip install octavia on the controller nodes16:41
rm_workbasically, you just need to "pip install octavia"16:41
rm_workand create a network for it to use for mgmt16:41
rm_workand have an admin account for it to auth with neutron and nova16:41
leitanrm_work: about the network, can it be a floating ip network ?16:42
leitanthat its a flat net16:42
rm_workno16:42
rm_workit needs to be a network that can create/bind ports16:42
rm_worknot associate flips16:42
leitanok, so if the external net is a flat one16:42
leitanit doest work either16:43
rm_workerr16:43
leitani needs to be a flat external_router=false16:43
rm_workI am not sure...16:43
rm_workso, I have a driver that I wrote, that does FLIP binding for the VIP instead of a port16:43
rm_workbut16:43
rm_workit is not in the main tree yet16:43
rm_workmaybe it is like what you need?16:43
rm_workalso it allows doing management over a default net16:44
rm_workinstead of a specific management network16:44
leitanno, im talking about the management network16:44
leitanfor the vip16:44
rm_workhttps://review.openstack.org/#/c/435612/16:44
leitani can later asociate a floating ip to it16:44
rm_workok16:44
leitanso is not an issue16:44
rm_workthe management network needs to be a normal neutron network16:44
leitanrm_work: normal means a flat ? accesible from the physical nodes ?16:45
leitanBRB16:45
rm_workI don't know what a flat network means16:45
rm_workit needs to be the kind of network you create with 'neutron net-create'16:45
rm_workjohnsom: maybe you can help me with terminology? I'm bad at neutron16:46
johnsomIt doesn't have to be flat, it can be routable, but the simplest configuration is flat16:46
openstackgerritMerged openstack/octavia master: Fix doc generation for Python3  https://review.openstack.org/45722416:52
*** amotoki has joined #openstack-lbaas16:54
openstackgerritMerged openstack/octavia master: Fix imports in v2 listener types  https://review.openstack.org/45417717:01
*** gcheresh_ has quit IRC17:07
*** chlong has quit IRC17:09
*** harlowja_ has quit IRC17:13
*** harlowja has joined #openstack-lbaas17:15
*** harlowja has quit IRC17:17
*** harlowja has joined #openstack-lbaas17:17
*** krypto has quit IRC17:25
*** chlong has joined #openstack-lbaas17:25
*** aojea has joined #openstack-lbaas17:38
xgermanLast day of vacation17:39
*** eandersson has joined #openstack-lbaas17:40
*** catintheroof has quit IRC17:47
leitanjohnsom: ok, so the external network that i already have configured on neutron will do as the management, but if i need to assign a floating ip to the vip will this break up the routing inside the amphora vm17:48
leitan?17:48
johnsomleitan Let me give an overview of networking for octavia just to make sure we are both talking about the same thing.17:48
leitanrm_work: when i pip install octavia, the i have to configure all the endpoints and that stuff like the ansible playbook does, or its not necesary ? and can work using just the neutron APi and shoot amphorae vms using the driver ?17:49
leitanim not clear about the if the "rest mode" its an option, or its mandatory17:49
johnsomOctavia currently uses service VMs we call amphora.  The amphora have an agent running inside them that provides monitoring and management.17:49
rm_workyeah so you will just configure octavia.conf with an admin account and your keystone endpoint17:50
rm_workand it will pick up nova/neutron endpoints from keystone17:50
johnsomThe controller processes talk to the amphora agent over the lb-mgmt-network and the amphora send health and stats back to the controllers over this network.  That is all it is used for, it is a private network simply for the controllers to talk with the amphora agent.  This network is configured at amphora boot time.17:50
johnsomThen, once the amphora is assigned to a load balancer, we hot plug the VIP network into the amphora and add another interface to the amphora.  This interface is isolated in a network namespace inside the amphora for security.  This is the VIP that customer traffic arrives on.17:52
johnsomWhen the user adds a member to the load balancer we will hot-plug those required networks into the amphroa inside the network namespace.17:52
johnsomTypically the lb-mgmt-network is not reachable from other networks and it has no need to be routable publicly.  It is a private management network.17:53
johnsomleitan Under ocata (I think that was the release you are using) the API is through neutron.   API requests go to neutron, then neutron-lbaas, then octavia driver for neutron-lbaas, and then to the octavia API.  In this case, you do not need to register the octavia API endpoint with keystone.  In fact, we don't recommend it.17:55
johnsomWith Pike  this will change.17:55
johnsomOptionally17:55
leitanjohnsom: great so it will be doing nova interface-add to the amphorae basically17:55
leitanjohnsom: im using Mitaka17:56
leitanjohnsom: so i need to also bring up the octavia api, i configure the octavia.conf with the database keystone and credentials, sync the db, bring up the api17:56
leitanif i not register the API into a keystone endpoint how neutron knows were the octavia api is ?17:57
leitanor it will capture messages from the queue ?17:57
johnsomleitan Under /etc/neutron/...  There is a configuration file for neutron lbaas the has an "[octavia]" section where you specify the octavia API endpoint18:00
johnsomIt's called "base_url" I think18:00
leitanjohnsom: ooook because i dindt find that in any guide, can you pin point me to an actual "complete" docs, because the lbaasv2 part on the neutron doc is not very octavia friendly18:07
leitanand the etherpads i found it just to build the amphorae image18:07
johnsomhttps://docs.openstack.org/developer/octavia/18:07
leitannothin related to the octaviaAPI/service configuration18:07
johnsomSpecifically the Operator quick start guide: https://docs.openstack.org/developer/octavia/guides/dev-quick-start.html18:08
johnsomI'm not sure what etherpads you are speaking of.18:08
leitanjohnsom: some i got from the IRC time ago18:09
leitanjohnsom: the operator guide will do18:09
leitanill start from there18:09
leitanand ping you guys if i cant understand something or if its not working18:09
leitanill probably build a docker image18:09
leitanwith the octavia api18:09
leitanso if you guys are interested i can share it later18:10
rm_workyeah, that is what we do18:10
leitanrm_work: is this image public ?18:10
rm_workthere is also support for octavia in kolla18:10
rm_workhmm, I don't think so :/18:10
leitanrm_work: ill take a look at kolla then, maybe it can save me some time18:10
rm_workkolla is for k8s18:10
rm_workbut it has some templates for things18:11
rm_workthat may be useful18:11
rm_workalso openstack-ansible has octavia support I believe18:11
reedip_rm_work, johnsom : do we need to verify if IP provided to a pool-member should be valid on the subnet its connected to ? Or would that be done automatically by raising an error if it isnt18:11
johnsomleitan OpenStack Ansible also puts all of the octavia processes in containers18:11
reedip_rm_work, johnsom :  reference: https://bugs.launchpad.net/octavia/+bug/168382418:11
openstackLaunchpad bug 1683824 in octavia "[neutron lbaasv2] ip and subnet is dismatched when creating pool-member" [Undecided,In progress] - Assigned to QingchuanHao (haoqingchuan-28)18:11
rm_workso similarly, there should be some useful templates there18:11
rm_workreedip_: we don't verify, it's up to the user to specify a correct subnet18:11
johnsomleitran Also, you can review the devstack plugin.sh as it has all of the steps we use to configure octavia for devstack: https://github.com/openstack/octavia/blob/master/devstack/plugin.sh18:12
rm_workor to not specify any subnet and we assume it is routable publically18:12
leitanrm_work: yes, i was looking at ansible-octavia at first18:12
rm_work(via the VIP network)18:12
leitanrm_work: this will do https://github.com/openstack/kolla/tree/master/docker/octavia18:12
reedip_rm_work: thats the bug , the developer/user may want the check to exist in the API (??)18:12
rm_workleitan: cool, yeah18:12
johnsomreedip_ We do not restrict member IPs to the subnet specified as there are use cases where that IP is routable from the subnet specified.18:13
leitanjohnsom rm_work thanks for the support guys, ill start from there18:13
rm_workleitan: FYI there is no difference between any of the dockerfiles, other than some weird thing in the api one to kick the db?18:13
rm_workleitan: but IMO just use the same one for every service18:13
*** aojea has quit IRC18:13
rm_workthere is no reason to differentiate, they all use exactly the same config and data and such18:13
leitanrm_work: ill build an AIO from that ones18:13
rm_workwe use the base18:13
reedip_johnsom : I gues maybe someone , like you , can explain it a bit more on the bug directly  ?? :)18:13
*** aojea has joined #openstack-lbaas18:14
johnsomreedip_ Yeah, I have to close these like every six months because people don't think of the routable case (though some folks use it)18:14
reedip_johnsom : probably means this sort of use case needs to be documented in the docs, right ?18:14
reedip_just my thought18:15
*** voelzmo has joined #openstack-lbaas18:15
johnsomreedip_ Sigh, yes.  I am working on docs!  You can help with reviews....  https://review.openstack.org/45575518:16
johnsomI'm not down to the members yet.  Starting pools now18:16
reedip_ok .. let me read them :)18:16
johnsomYou can click on the API-REF gate to read them rendered18:17
rm_workI am planning to review Listeners doc today18:17
rm_workI actually opened it and started, but I had to stop to talk to someone18:17
*** aojea has quit IRC18:18
*** chlong has quit IRC18:20
reedip_rm_work : lol , this actually happens everytime a  big doc review comes to me :D18:22
*** gcheresh_ has joined #openstack-lbaas18:25
johnsomI'm breaking it down by sections.....  Sorry they are a bit big18:26
*** catinthe_ has joined #openstack-lbaas18:30
*** amotoki has quit IRC18:30
leitanrm_work: i know its fun to document, hope i didnt break up your doc mojo :P18:34
*** aojea has joined #openstack-lbaas18:34
*** aojea_ has joined #openstack-lbaas18:35
*** aojea has quit IRC18:38
*** catinthe_ has quit IRC18:39
*** aojea_ has quit IRC18:41
*** JudeC has joined #openstack-lbaas18:41
*** aojea_ has joined #openstack-lbaas18:44
*** chlong has joined #openstack-lbaas18:45
*** aojea has joined #openstack-lbaas18:47
*** aojea_ has quit IRC18:48
*** aojea_ has joined #openstack-lbaas18:50
*** aojea has quit IRC18:53
rm_workhah i was not referring to you actually, your issue was relatively quick18:54
rm_workI was on hold with American Airlines, who couldn't understand how to process my credit card and thought because I booked in JPY not USD I must have booked via a travel agent, even though it was their website forcing me to use JPY...18:55
*** JudeC has quit IRC19:00
*** kobis has quit IRC19:07
*** kobis has joined #openstack-lbaas19:09
leitanrm_work: missing form validation engineer on the staff :P19:16
leitanjohnsom: i should probably go with octavia 3.0.3-beta.1  since im using mitaka ? or if i use the master tag should go fine ?19:18
johnsomleitan We have not released a 3.0.3 version of octavia yet....  We are currently working on the 1.0.0 release19:19
leitanim talking about the kolla tag19:19
leitanthought that maybe was synched with the actuall version19:20
johnsomleitan We create stable branches for the releases, so stable/mitaka (which is being EOL'd as we speak)19:20
johnsomhttps://docs.openstack.org/releasenotes/octavia/19:20
johnsomMitaka was 0.8.0 for us19:21
johnsomI'm not very familiar with kolla, but each project has it's own version number chain.19:21
johnsomAlso not, for the most part you can use newer versions of Octavia than the rest of your stack should you want new features.  You just need to test it to make sure.19:22
leitanill will take a look at that19:22
johnsomOnce mitaka is fully EOL, they will create a tag for mitaka-eol that is the last release of the project.19:23
johnsomFor that cycle19:23
*** reedip_ has quit IRC19:26
rm_workwhoops, HM bug19:26
rm_worksec19:26
*** JudeC has joined #openstack-lbaas19:28
rm_workgoing to push up the fix as part of paging/sorting, then backport it to HM19:32
rm_workbecause it's a big enough issue...19:32
rm_workrunning tests now19:33
leitanjohnsom: ill test the master tag on dockerhub, and downgrade if i find some phantom behaviour19:34
leitanthanks19:34
rm_workyeah, we are planning to run Octavia from master, even on our liberty cloud19:36
rm_workleitan: ^^19:36
rm_workit is working fine19:36
leitanrm_work: good to hear, ill take that path then, fearless :P19:37
openstackgerritAdam Harwell proposed openstack/octavia master: Implement sorting and pagination for octavia  https://review.openstack.org/38214719:38
*** voelzmo has quit IRC19:44
*** dmk0202 has joined #openstack-lbaas19:47
openstackgerritAdam Harwell proposed openstack/octavia master: Remove singleton pattern from API controllers  https://review.openstack.org/45781319:48
openstackgerritAdam Harwell proposed openstack/octavia master: Introduce Octavia v2 API for Health Monitor  https://review.openstack.org/40625619:48
openstackgerritAdam Harwell proposed openstack/octavia master: Implement sorting and pagination for octavia  https://review.openstack.org/38214719:49
rm_workok19:49
rm_workeverything is nice and fixed and rebased19:49
rm_workjohnsom: need to re-vote on HM19:49
johnsomOk19:50
johnsomI think I need to make a change to the quota patch too for the singleton issue19:50
rm_workyeah19:52
rm_workupdate it per my template19:52
rm_workand rebase on top of that change19:52
rm_workI wasted like 20 hours of my life on that stupid singleton thing19:54
rm_workonce i realized, it took like 5 minutes to fix >_<19:56
openstackgerritNir Magnezi proposed openstack/octavia master: Auto detect haproxy user_group  https://review.openstack.org/42939819:57
*** voelzmo has joined #openstack-lbaas19:57
johnsomOctavia meeting starting soon on #openstack-meeting-alt19:59
*** catintheroof has joined #openstack-lbaas19:59
*** bread_ has quit IRC20:00
*** voelzmo has quit IRC20:02
rm_workJudeC: join #openstack-meeting-alt :)20:03
*** cody-somerville has quit IRC20:08
*** cody-somerville has joined #openstack-lbaas20:09
*** cody-somerville has quit IRC20:09
*** cody-somerville has joined #openstack-lbaas20:09
*** aojea has joined #openstack-lbaas20:18
*** aojea_ has quit IRC20:21
leitanim trying something funny i dont know if if should be considered as a bug but, if you bring up the api, without synching the DB i get a fully output of the failed sql query and debug is set to false in the API, is this the epected response or should be a more "hide/friendly error"20:22
*** aojea_ has joined #openstack-lbaas20:25
*** aojea has quit IRC20:28
*** gcheresh_ has quit IRC20:43
*** catintheroof has quit IRC20:55
*** catintheroof has joined #openstack-lbaas20:55
*** leitan has quit IRC20:59
*** catintheroof has quit IRC21:00
*** catintheroof has joined #openstack-lbaas21:01
johnsomIt should be a better error21:02
*** kobis has quit IRC21:03
*** aojea_ has quit IRC21:06
*** catintheroof has quit IRC21:24
rm_workhmm, interesting that we exposed that directly21:31
rm_workI guess we just didn't consider21:31
rm_workwe should really fix those21:31
rm_workI tried to do a little around kinda genericising the exceptions21:31
*** catintheroof has joined #openstack-lbaas21:34
rm_worknmagnezi: one last set of changes21:45
rm_workfor py321:45
* nmagnezi listens21:45
rm_workline 11921:46
nmagnezirm_work, listener.py?21:46
rm_workone sec21:46
rm_workposted21:47
*** jerrygb has quit IRC21:47
nmagnezirm_work, I'm not sure i'm following those comments..21:53
nmagnezirm_work, i'm not saying there is anything wrong with them21:53
nmagnezirm_work, i just don't understand :\21:53
nmagnezirm_work, will look more closely..21:53
rm_workwe got rid of the binary mode stuff22:04
rm_workso it shouldn't be looking for a bytes write anymore22:05
rm_workright?22:05
rm_workhttp://logs.openstack.org/98/429398/36/check/gate-octavia-tox-functional-py35-ubuntu-xenial/b42566a/testr_results.html.gz22:05
rm_workJudeC: http://logs.openstack.org/20/456420/9/check/gate-neutron-lbaasv2-dsvm-py3x-scenario-ubuntu-xenial-nv/8a69425/console.html#_2017-04-19_03_27_07_73980322:07
*** chlong has quit IRC22:07
rm_workJudeC: I THINK that is because of something that I fixed already...22:07
rm_workI wonder if you need to rebase that22:07
rm_workhmm22:07
*** dmk0202 has quit IRC22:17
JudeCrm_work I can try a rebase right now if you would like22:19
*** gongysh has joined #openstack-lbaas22:38
*** gongysh has quit IRC22:40
*** fnaval has quit IRC22:46
*** jerrygb has joined #openstack-lbaas22:49
*** reedip_ has joined #openstack-lbaas22:52
*** jerrygb has quit IRC22:53
rm_workeh, it had a problem anyway JudeC22:57
rm_workmight need to test it in devstack yourself and see what's going on22:57
JudeCrm_work ok I will test it right now22:58
rm_worktry removing the join timeout23:07
rm_workit never joins23:07
*** vlaza has quit IRC23:29

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