Tuesday, 2019-11-05

*** ramishra has quit IRC00:14
*** ivve has quit IRC00:25
*** ccamposr__ has joined #openstack-lbaas00:51
*** ccamposr has quit IRC00:53
*** yamamoto has joined #openstack-lbaas01:07
*** tkajinam has joined #openstack-lbaas01:52
*** yamamoto has quit IRC01:56
*** yamamoto_ has joined #openstack-lbaas01:56
*** yamamoto_ has quit IRC01:58
*** yamamoto has joined #openstack-lbaas01:58
*** yamamoto has quit IRC01:58
*** yamamoto has joined #openstack-lbaas01:58
*** yamamoto has quit IRC02:12
*** yamamoto has joined #openstack-lbaas02:13
*** yamamoto has quit IRC02:25
*** yamamoto has joined #openstack-lbaas02:30
*** lxkong has quit IRC02:30
*** yamamoto has quit IRC02:31
*** yamamoto has joined #openstack-lbaas02:36
*** yamamoto has quit IRC02:38
*** tkajinam has quit IRC02:40
*** ricolin has joined #openstack-lbaas02:53
*** ricolin has quit IRC03:35
*** psachin has joined #openstack-lbaas03:38
*** ricolin has joined #openstack-lbaas03:41
*** ricolin has quit IRC03:57
*** ricolin has joined #openstack-lbaas03:57
*** nmagnezi has quit IRC04:04
*** ricolin has quit IRC04:13
*** ricolin has joined #openstack-lbaas05:23
*** pcaruana has joined #openstack-lbaas05:41
*** ricolin has quit IRC05:50
*** gcheresh_ has joined #openstack-lbaas06:22
*** AlexStaf has quit IRC06:48
*** yamamoto has joined #openstack-lbaas07:08
*** yamamoto has quit IRC07:09
*** yamamoto has joined #openstack-lbaas07:10
*** yamamoto has quit IRC07:10
*** yamamoto has joined #openstack-lbaas07:11
*** yamamoto_ has joined #openstack-lbaas07:14
*** yamamoto has quit IRC07:17
*** ricolin has joined #openstack-lbaas07:17
*** lxkong has joined #openstack-lbaas07:19
*** yamamoto_ has quit IRC07:19
*** gcheresh_ has quit IRC07:32
*** gcheresh_ has joined #openstack-lbaas07:38
*** luksky has joined #openstack-lbaas07:39
*** ricolin_ has joined #openstack-lbaas07:45
*** ricolin has quit IRC07:47
*** yamamoto has joined #openstack-lbaas07:47
*** yamamoto has quit IRC07:48
*** yamamoto has joined #openstack-lbaas07:48
*** yamamoto has quit IRC07:49
*** yamamoto has joined #openstack-lbaas07:51
*** yamamoto has quit IRC07:54
*** yamamoto has joined #openstack-lbaas07:55
*** yamamoto has quit IRC07:57
*** ricolin_ has quit IRC08:04
*** ricolin_ has joined #openstack-lbaas08:04
*** AlexStaf has joined #openstack-lbaas08:23
*** tesseract has joined #openstack-lbaas08:24
*** ccamposr has joined #openstack-lbaas08:34
*** ccamposr__ has quit IRC08:37
*** ricolin_ has quit IRC08:37
openstackgerritAnn Taraday proposed openstack/octavia master: Add option to set default ssl ciphers in haproxy  https://review.opendev.org/68533709:38
*** ccamposr has quit IRC10:01
*** ccamposr has joined #openstack-lbaas10:11
*** lemko has joined #openstack-lbaas10:18
*** gcheresh_ has quit IRC10:20
*** gcheresh has joined #openstack-lbaas10:20
*** CobHead has joined #openstack-lbaas10:38
*** ivve has joined #openstack-lbaas10:46
*** ataraday has joined #openstack-lbaas11:46
ataradayIn case someone is around, I've updated ptg etherpad with taskflow jobboard status - let me know if I need to highlight some other points about it.11:49
*** luksky has quit IRC12:13
*** henriqueof has quit IRC12:16
openstackgerritAnn Taraday proposed openstack/octavia master: Add option to set default ssl ciphers in haproxy  https://review.opendev.org/68533712:25
*** luksky has joined #openstack-lbaas13:37
*** yamamoto has joined #openstack-lbaas13:48
*** yamamoto has quit IRC13:52
*** yamamoto has joined #openstack-lbaas13:52
*** yamamoto has quit IRC13:54
lukskyhi, I have question about octavia-amphora-agent. Does this service is needed ?14:04
lukskyWhere can I read about it ?14:05
*** yamamoto has joined #openstack-lbaas14:06
*** ramishra has joined #openstack-lbaas14:07
*** goldyfruit_ has joined #openstack-lbaas14:19
johnsomluksky: the Amphora agent runs inside the Amphora service VMs. It is required when you are using the amphora driver. The image creating script will install it for you. No configuration is required inside the image, it is automatic.14:31
johnsomataraday: thank you, I will take a look.14:31
*** goldyfruit___ has joined #openstack-lbaas14:34
*** goldyfruit_ has quit IRC14:36
lukskyjohnsom: thank You - I'm asking becouse I see on octavia controller (turned off/disabled) octavia-amphora-agent.service in systemd (on system, which I get to administer) and was wondering WTF14:38
*** gcheresh has quit IRC14:48
*** yamamoto has quit IRC14:49
*** ramishra has quit IRC14:50
*** TrevorV has joined #openstack-lbaas14:56
*** yamamoto has joined #openstack-lbaas15:26
*** yamamoto has quit IRC15:31
*** yamamoto has joined #openstack-lbaas15:36
*** yamamoto has quit IRC15:41
*** yamamoto has joined #openstack-lbaas15:47
*** Trevor_V has joined #openstack-lbaas16:08
*** TrevorV has quit IRC16:11
openstackgerritMichael Johnson proposed openstack/octavia master: Stop allowing the deletion of an in-use flavor  https://review.opendev.org/69242716:21
*** luksky has quit IRC16:31
*** tesseract has quit IRC16:50
*** luksky has joined #openstack-lbaas16:57
*** AlexStaf has quit IRC16:59
generalfuzzHi - I'm having trouble setting up Octavia. My issue is that the octavia worker is unable to connect to the amphorae VM.17:07
generalfuzzI've written up details about my environment here: https://ask.openstack.org/en/question/124991/octavia-worker-not-able-to-connect-to-amphora/17:07
johnsomOk, are you able to ssh to the amphorae VM over the lb-mgmt-net?17:08
generalfuzzI can ssh into amphorae VM using network namespace17:08
johnsomGive me a minute to read through what you put on ask.17:09
generalfuzzie "ip netns exec qdhcp-79f55a3b-3bba-4aec-a2a8-5eefaca033d1 ssh cirros@10.16.100.14"17:09
johnsomYeah, that is not a good test.17:09
johnsomAh, ok, so a Kolla issue. Sadly I'm not very familiar with how Kolla is setup for Octavia. But I can try to walk through some things to debug.17:13
generalfuzzawesome, open to suggestions17:13
johnsomSo, the controller processes (worker, health manager, and house keeping) must have a network path to the amphora over the lb-mgmt-net.17:14
johnsomIt looks like kolla is calling that lb-net17:14
generalfuzzI created that network17:14
johnsomInside your controller worker container, do you have an interface for the lb-net?17:15
johnsomOh, hmmm, I would have expected kolla to create that for you.17:15
johnsomThe other deployment tools all create that network automatically.17:15
generalfuzzlet me double check kolla on that17:16
johnsomIf there is not an interface for that lb-net inside the containers, we will need to add that.17:17
generalfuzzcheck the interfaces with "ip a" ?17:19
johnsomyes17:20
*** psachin has quit IRC17:20
generalfuzzits a long list, not sure if lb-net is there -17:20
johnsomit is usually called something like o-hm0, but that is up to the deployment tool17:20
generalfuzzhttps://www.irccloud.com/pastebin/XnXEmmXj/17:20
johnsomThat is inside the worker container?17:21
generalfuzzyes17:21
johnsomCan you do a "openstack subnet show d17fa379-ad28-47cf-8479-8d5a7c46965e" ?17:22
johnsomWe can probably match up the subnet to the interface17:22
generalfuzzhttps://www.irccloud.com/pastebin/i20b1QPu/17:22
johnsomYep, ok, so there is no interface in the worker container to allow it to access that network.17:23
generalfuzzso, this behavior is expected17:24
johnsomI would recommend asking in the kolla IRC channels how that should be configured.17:24
johnsomYes, you must have the lb-mgmt-net connected to the controllers. That is a required deployment configuration.17:24
generalfuzzAt what point in non-kolla deployment does this association happen?17:24
johnsomInstallation/deployment.17:24
johnsomprior to attempting to start the controller processes17:25
generalfuzzIs there a history of this working in Kolla?17:25
generalfuzzoctavia deployment, I mean17:26
johnsomYeah, I know some folks are using it, but all of that Kolla work was done by the Kolla team. The core Octavia team typically doesn't work on the deployment tools as there are so many and they are pretty specialized. We mostly work with the tool we use most.17:28
johnsomOne person that has used Kolla is at the summit and the other is either at the summit or offline in this time window.17:28
generalfuzzok17:28
johnsomYour best bet for help with this is using the kolla channels.17:28
generalfuzzthanks much for your help17:28
johnsomI can show you how some of the other tools do it if you want to go it on your own, but I would expect there is a "kolla" way to do it.17:29
generalfuzzwhere does this network get assigned to worker - is it in /etc/octavia/octavia.conf ?17:35
generalfuzzbecause I do have the following configured - amp_boot_network_list = 79f55a3b-3bba-4aec-a2a8-5eefaca033d117:35
*** ccamposr__ has joined #openstack-lbaas17:36
johnsomRight, that config tells the amphora what network ID to use for the lb-mgmt-net at boot. For what I saw, that setting is correct.17:36
johnsomI think the issue is the controllers have no route/access to the lb-mgmt-net.17:36
johnsomThere is no octavia.conf setting for that. It is all deployment tool. The controllers just know the IP address assigned to the amphora and attempt to access that IP on the amphora agent port, 944317:37
*** ccamposr has quit IRC17:38
johnsom The deployment tool has a lot of options about how to give access. Devstack and tripleo both create an interface on the neutron network called o-hm0 for the controllers. OpenStack-ansible uses a provider network and VLANs. Others have created routers and routes.17:38
johnsomgeneralfuzz I found this blog article using kolla-ansible: https://shreddedbacon.com/post/openstack-kolla/17:40
johnsomIt looks like this person had to setup that network too. It is just not clear to me how he made that VLAN, 400, available to the controllers. Maybe the neutron configuration for the provider networks also adds a path to that VLAN17:42
johnsomOr they just created the ports on the vlan themselves17:43
johnsomAh there appears to be this too: https://bugs.launchpad.net/kolla-ansible/+bug/171968817:44
openstackLaunchpad bug 1719688 in kolla-ansible "kolla-ansible does not create provider network needed by octavia" [Wishlist,Triaged]17:44
generalfuzzok, so others have run into this in kolla land - good to know17:48
johnsomI think we are pushing twelve different deployment tools that support Octavia now. It's pretty hard to keep up with them all.17:51
*** goldyfruit___ has quit IRC17:53
*** goldyfruit___ has joined #openstack-lbaas17:58
*** gcheresh has joined #openstack-lbaas18:10
*** gcheresh has quit IRC18:20
*** goldyfruit_ has joined #openstack-lbaas18:46
*** goldyfruit___ has quit IRC18:49
*** gcheresh has joined #openstack-lbaas19:13
*** goldyfruit_ has quit IRC19:14
*** gcheresh_ has joined #openstack-lbaas19:22
*** gcheresh has quit IRC19:25
*** ccamposr has joined #openstack-lbaas19:28
*** ccamposr__ has quit IRC19:30
*** ccamposr__ has joined #openstack-lbaas19:52
*** ccamposr has quit IRC19:54
*** gcheresh_ has quit IRC20:27
*** goldyfruit_ has joined #openstack-lbaas20:33
*** gcheresh_ has joined #openstack-lbaas20:37
*** gcheresh_ has quit IRC21:10
*** mriedem has joined #openstack-lbaas21:19
mriedemfor anyone around, i've got a random user flaming me up because he's using the old deprecated neutron lbaasv2 stuff and can't find the api reference https://docs.openstack.org/api-ref/network/v2/index.html#load-balancer-as-a-service-2-0-deprecated - he's not using octavia so doesn't care about the octavia api reference, or is it the exact same?21:19
johnsomLol, was replying over there too. Grin21:20
mriedemyou shamed me into moving21:20
johnsomThe Octavia API also implements the lbaasv2 API. It is a superset.21:20
mriedemsure,21:21
mriedembut if you're using the old thing, how do you know what's new and only available with octavia?21:21
johnsomThe api ref that was in the neutron docs had been wrong for years21:21
johnsomSomeone merged the old lbaasv1 and lbaasv2 together making a mess21:21
johnsomSo we decided correct docs were the best plan.21:22
mriedemok, that doesn't surprise me21:22
mriedembut still, how does someone know what is unique to octavia?21:23
*** Trevor_V has quit IRC21:23
johnsomAnything that doesn’t have a version call out should work with the last neutron-lbaas release21:23
mriedemversion call out == "added in x release" ?21:23
johnsomOur api-ref is versioned, starting with lbaasv2 as the reference21:24
mriedemi don't know how you guys version your api21:24
johnsomCorrect21:24
mriedemx release isn't really a version though21:24
johnsomOh, sorry, I thought you typed version, not release21:25
mriedemi mean, the end user doesn't necessarily know what version of openstack the cloud is running21:25
johnsomIt is documented by api version21:25
mriedemmaybe it would be easier if you could just point me at some api that is unique to octavia?21:25
johnsomThere are commands to get the version discovery info21:25
johnsomAt least I think the neutron API had version discovery21:26
mriedemok so like this https://docs.openstack.org/api-ref/load-balancer/v2/index.html#filtering-by-tags21:26
mriedemNew in version 2.521:26
mriedem2.0 is backward compatible with neutron lbaasv2 yeah?21:27
mriedemanything > 2.0 is ocatavia only21:27
*** lemko has quit IRC21:27
mriedemis that correct?21:27
johnsomhttps://docs.openstack.org/api-ref/load-balancer/v2/index.html?expanded=list-flavors-detail#list-flavors21:27
mriedem"New in version 2.6"21:27
mriedemack21:27
johnsomCorrect21:27
mriedemhow do you request the version? in the route path or a header?21:28
johnsomThey will also get a “not implemented” message should they stray21:28
mriedem/v2.6/lbaas/flavors ?21:28
johnsomNo, our API is additive only. No need to request a version21:29
mriedemok, so if i'm talking to a cloud that has 2.6 and listing flavors, i'll get whatever goodies are in 2.6, else i won't21:29
mriedemas a user i can't opt in21:29
mriedemright?21:29
mriedemthat's like how glance's api works21:29
johnsomCorrect, /v2 gets you everything up to the api version the cloud is advertising21:30
johnsomSame as neutron and neutron-lbaas was21:30
mriedemwithout the extension mumbo jumbo in neutron i'm guessing21:30
johnsomCorrect21:31
mriedemwell that's a relief :)21:31
mriedemjohnsom: ok, i've passed this on. thanks, it's helpful. it might be nice to have something in the api-ref detailing some of ^ and i realize patches are welcome...21:32
johnsomNuetron21:32
johnsomOpps, it is called out in the neutron-lbaas deprecation FAQ21:33
mriedemsure, but assume i do'nt know anything about openstack21:33
mriedemand i'm coming to the octavia docs and i'm like, wtf is a neutron? i just want that sweet sweet lbaas action21:33
johnsomhttps://wiki.openstack.org/wiki/Neutron/LBaaS/Deprecation21:34
mriedemthat's not linked from https://docs.openstack.org/api-ref/load-balancer/v2/index.html but ok,21:34
mriedemit's linked from the neutron api-ref21:34
johnsomNuetron-lbaas went EOL, no train release, so ....21:34
mriedemhttps://docs.openstack.org/api-ref/network/v2/index.html?expanded=#load-balancer-as-a-service-2-0-deprecated21:34
mriedemi yield21:35
johnsomLol21:35
mriedembtw you're not in shanghai answering these questions right now are you?21:35
johnsomLet me know if you need more info. Now you know the place21:35
johnsomNo, I am the odd core out on this trip21:36
johnsomStill on mobile though, ran out for lunch21:36
mriedemsounds like a feature rather than a bug21:36
johnsomAgreed21:36
*** mriedem has left #openstack-lbaas21:48
*** pcaruana has quit IRC22:03
*** gthiemonge has quit IRC22:14
*** gthiemon1e has joined #openstack-lbaas22:14
*** armax has joined #openstack-lbaas22:27
*** rcernin has joined #openstack-lbaas22:29
*** luksky has quit IRC22:54
*** ramishra has joined #openstack-lbaas23:04
*** armax has quit IRC23:41
*** ccamposr__ has quit IRC23:46

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