Wednesday, 2017-10-18

rm_workjohnsom: so looks like 1-2weeks before they can release new tempest00:03
rm_workso I guess maybe we're stuck until then? :/00:04
rm_workbecause it only runs if we pull down gitmaster tempest00:04
rm_workbut, the one we're using IS the stable interface00:04
*** jniesz has quit IRC00:06
johnsomHe said not yet, but will be00:06
rm_worksemantics :P00:06
rm_workat the time the release happens (ie, 1-2 weeks) that is the stable interface00:06
johnsomHahaha, so...  Not sure how to move forward with that master issue.00:07
rm_workwait. i think00:12
*** dayou has joined #openstack-lbaas00:26
-openstackstatus- NOTICE: due to unscheduled restart of zuulv3.o.o you will need to 'recheck' your jobs that were last running. Sorry for the inconvenience.00:32
rm_workjohnsom: whoops T_T guessing you'll have to recheck?00:45
rm_workyep it's not listed :/00:45
rm_workguess this'll take a little longer00:46
*** aojea has joined #openstack-lbaas00:47
*** aojea has quit IRC00:51
*** tongl has joined #openstack-lbaas00:55
*** tongl has quit IRC01:11
johnsomYeah, darn it01:23
*** AlexeyAbashkin has joined #openstack-lbaas01:23
johnsomAh, you got it.  Thanks!01:23
*** AlexeyAbashkin has quit IRC01:27
openstackgerritAdam Harwell proposed openstack/octavia-tempest-plugin master: WIP: Failover test
*** tongl has joined #openstack-lbaas01:47
*** aojea has joined #openstack-lbaas01:48
*** aojea has quit IRC01:52
*** yamamoto has joined #openstack-lbaas01:56
kongrm_work: hi, after looking at, i still have question regarding to the vip_address02:04
kongpls see my comment02:05
*** AlexeyAbashkin has joined #openstack-lbaas02:23
*** AlexeyAbashkin has quit IRC02:27
*** chlong has quit IRC02:47
*** openstackgerrit has quit IRC03:22
*** AlexeyAbashkin has joined #openstack-lbaas03:23
*** AlexeyAbashkin has quit IRC03:27
*** sanfern has joined #openstack-lbaas03:31
*** sri_ has quit IRC03:31
*** yamamoto_ has joined #openstack-lbaas03:39
*** yamamoto has quit IRC03:42
*** links has joined #openstack-lbaas03:46
*** aojea has joined #openstack-lbaas03:49
*** aojea has quit IRC03:54
*** aojea has joined #openstack-lbaas04:50
*** aojea has quit IRC04:54
*** sanfern has quit IRC05:13
*** sanfern has joined #openstack-lbaas05:15
Tenguhello! I've enabled neutron-lbaasv2 in tripleO, but apparently I'm missing something, because I don't see any entry in horizon interface. but lbaasv2 is active, as I can see its agents in `openstack network agent list' output.05:22
TenguI don't really know if the question has to be asked on #tripleo or here…05:22
*** aojea has joined #openstack-lbaas05:51
*** aojea has quit IRC05:55
*** tongl has quit IRC06:44
*** pcaruana has joined #openstack-lbaas06:45
*** armax has quit IRC06:45
*** tesseract has joined #openstack-lbaas07:17
*** bzhao has joined #openstack-lbaas07:25
bzhaoreedip, ping07:26
*** ipsecguy_ has joined #openstack-lbaas07:28
*** Alex_Staf_ has joined #openstack-lbaas07:30
*** ipsecguy has quit IRC07:31
*** wasmum has joined #openstack-lbaas07:34
*** aojea has joined #openstack-lbaas07:38
nmagnezirm_work, o/07:41
*** aojea has quit IRC07:48
*** AlexeyAbashkin has joined #openstack-lbaas07:57
*** jidar has quit IRC08:03
*** bzhao has quit IRC08:04
*** bzhao has joined #openstack-lbaas08:04
nmagneziTengu, i suspect you should ask in TripleO, but just FYI in LBaaSv2 you need the neutron-lbaas-dashboard-plugin for Horizon to be deployed (and if you run Octavia it's named octavia-dashboard-plugin)08:05
Tengunmagnezi: hello! thanks for your answer - I think the answers is indeed on #tripleo. I found out why it's not set, and it's fully tripleo related. apparently missing an "enable_lb: True" in the horizon config.08:07
Tengunmagnezi: would openstack-neutron-lbaas-ui be the same?08:12
*** belharar has joined #openstack-lbaas08:16
*** slaweq has joined #openstack-lbaas08:23
*** ipsecguy has joined #openstack-lbaas08:24
*** ipsecguy_ has quit IRC08:28
*** mnaser has quit IRC08:30
*** belharar has quit IRC08:36
*** belharar has joined #openstack-lbaas08:36
nmagneziTengu, yeah, i think so :)08:37
*** yamamoto_ has quit IRC08:37
*** leyal has quit IRC08:38
Tengunmagnezi: seems it's ok. so I have a couple of issues to solve on my own, but basically I have the necessary information in order to install/activate it, and provide a patch against tripleo in order to get a correct support. Thanks for your time :)08:38
nmagneziTengu, np!08:38
*** yamamoto has joined #openstack-lbaas08:40
*** yamamoto has quit IRC08:40
*** mnaser has joined #openstack-lbaas08:41
*** aojea has joined #openstack-lbaas08:44
*** leyal has joined #openstack-lbaas08:45
*** aojea has quit IRC08:48
*** dayou has quit IRC09:00
*** dayou has joined #openstack-lbaas09:02
*** yamamoto has joined #openstack-lbaas09:07
*** dayou has quit IRC09:10
*** yamamoto has quit IRC09:11
*** yamamoto has joined #openstack-lbaas09:17
*** yamamoto has quit IRC09:21
*** dayou has joined #openstack-lbaas09:24
*** yamamoto has joined #openstack-lbaas09:28
*** yamamoto_ has joined #openstack-lbaas09:34
*** salmankhan has joined #openstack-lbaas09:35
*** yamamoto has quit IRC09:37
*** aojea has joined #openstack-lbaas09:45
*** sapd__ has quit IRC09:45
*** sapd_ has joined #openstack-lbaas09:45
*** sapd_ has quit IRC09:47
*** sapd_ has joined #openstack-lbaas09:48
*** aojea has quit IRC09:49
*** AlexeyAbashkin has quit IRC09:49
*** yamamoto_ has quit IRC09:56
*** yamamoto has joined #openstack-lbaas10:26
*** aojea has joined #openstack-lbaas10:45
*** aojea has quit IRC10:50
*** sanfern has quit IRC10:54
*** AlexeyAbashkin has joined #openstack-lbaas10:55
*** chlong has joined #openstack-lbaas11:01
*** atoth has joined #openstack-lbaas11:12
*** ramishra has quit IRC11:31
*** ramishra has joined #openstack-lbaas11:39
*** aojea has joined #openstack-lbaas11:46
*** aojea has quit IRC11:50
*** sanfern has joined #openstack-lbaas11:58
*** openstackgerrit has joined #openstack-lbaas11:59
openstackgerritMerged openstack/octavia master: Change 14.04 to 16.04 in devstack setup guide
*** yamamoto has quit IRC11:59
TenguI guess nobody in here has anything to do with tripleo-related project voring on gerrit? :)12:00
nmagneziTengu, we're happy to help with Octavia & LBaaS questions, but we don't have +2 votes on TripleO if that's what you're asking :)12:02
Tengunmagnezi: :'(12:02
Tenguanyway, it will be pushed. eventually.12:02
TenguI know what to do on my own in order to get the lbaas UI at least :)12:03
*** sanfern has quit IRC12:29
*** sanfern has joined #openstack-lbaas12:29
*** belharar has joined #openstack-lbaas12:33
*** links has quit IRC12:44
*** aojea has joined #openstack-lbaas12:47
*** aojea has quit IRC12:51
*** yamamoto has joined #openstack-lbaas12:59
*** belharar has quit IRC13:03
*** yamamoto has quit IRC13:07
openstackgerritSlawek Kaplonski proposed openstack/neutron-lbaas master: Allow to extend sub_resource attributes
openstackgerritSlawek Kaplonski proposed openstack/neutron-lbaas master: Allow to extend sub_resource attributes
*** leitan has joined #openstack-lbaas13:23
*** belharar has joined #openstack-lbaas13:29
*** armax has joined #openstack-lbaas13:50
*** yamamoto has joined #openstack-lbaas13:54
*** yamamoto has quit IRC13:55
*** tongl has joined #openstack-lbaas14:04
*** tongl has quit IRC14:23
*** fnaval has joined #openstack-lbaas14:41
*** tonygunk has joined #openstack-lbaas14:43
*** aojea has joined #openstack-lbaas14:48
*** chlong has quit IRC14:52
*** aojea has quit IRC14:53
*** yamamoto has joined #openstack-lbaas14:55
*** yamamoto has quit IRC15:05
*** ramishra has quit IRC15:07
*** catintheroof has joined #openstack-lbaas15:13
*** pcaruana has quit IRC15:19
*** tesseract has quit IRC15:20
*** fnaval_ has joined #openstack-lbaas15:20
*** fnaval has quit IRC15:21
*** slaweq_ has joined #openstack-lbaas15:28
*** belharar has quit IRC15:35
*** aojea has joined #openstack-lbaas15:49
openstackgerritMichael Johnson proposed openstack/neutron-lbaas master: Update release notes doc theme
*** aojea has quit IRC15:54
*** links has joined #openstack-lbaas15:55
openstackgerritMurali Annamneni proposed openstack/neutron-lbaas master: Enable MySQL Cluster Support for neutron-lbaas
*** slaweq_ has quit IRC16:00
*** tongl has joined #openstack-lbaas16:07
openstackgerritMichael Johnson proposed openstack/octavia-dashboard master: Add release notes support to octavia-dashboard
openstackgerritMichael Johnson proposed openstack/neutron-lbaas master: Update release notes doc theme
*** links has quit IRC16:28
*** AlexeyAbashkin has quit IRC16:47
*** aojea has joined #openstack-lbaas16:50
*** aojea has quit IRC16:54
*** leyal has quit IRC17:04
*** leyal has joined #openstack-lbaas17:05
*** Swami has joined #openstack-lbaas17:12
*** Swami has quit IRC17:15
*** Swami has joined #openstack-lbaas17:16
*** sshank has joined #openstack-lbaas17:22
*** aojea has joined #openstack-lbaas17:22
*** sshank has quit IRC17:40
*** sshank has joined #openstack-lbaas17:44
*** catinthe_ has joined #openstack-lbaas17:53
*** catintheroof has quit IRC17:53
openstackgerritboden proposed openstack/neutron-lbaas master: use FAULT_MAP from neutron-lib
johnsomThese zuul restarts are painful17:58
*** catintheroof has joined #openstack-lbaas17:59
*** catinthe_ has quit IRC18:01
*** catinthe_ has joined #openstack-lbaas18:05
*** catintheroof has quit IRC18:07
*** catintheroof has joined #openstack-lbaas18:14
*** catinthe_ has quit IRC18:15
*** AlexeyAbashkin has joined #openstack-lbaas18:19
*** AlexeyAbashkin has quit IRC18:24
*** tonygunk has quit IRC18:24
*** aojea has quit IRC18:30
*** slaweq_ has joined #openstack-lbaas18:33
*** slaweq_ has quit IRC18:37
*** jidar has joined #openstack-lbaas18:45
*** jidar has quit IRC18:59
*** jidar has joined #openstack-lbaas19:00
*** jidar has left #openstack-lbaas19:02
*** slaweq_ has joined #openstack-lbaas19:08
*** salmankhan has quit IRC19:09
*** sanfern has quit IRC19:10
openstackgerritMerged openstack/neutron-lbaas master: Move neutron-lbaas zuulv3 configuration in repo
*** aojea has joined #openstack-lbaas19:16
johnsomYay, we are on our way19:19
*** AlexeyAbashkin has joined #openstack-lbaas19:19
openstackgerritMichael Johnson proposed openstack/octavia master: Move Octavia zuulv3 configuration in repo
*** aojea has quit IRC19:21
*** AlexeyAbashkin has quit IRC19:24
*** jdavis has joined #openstack-lbaas19:28
*** atoth has quit IRC19:28
johnsomFYI, if you submit a patch and it doesn't show up in the new zuul dashboard, check the "queue length" at the top.  Those are commits that haven't been brought into the pipelines yet.19:33
johnsomIt's at 374 now...  sigh19:33
*** jniesz has joined #openstack-lbaas19:34
johnsomOnce in the pipeline, then you start waiting for a instance to start your gates19:34
nmagnezijohnsom, i'm still not convinced that this was an actual upgrade..19:37
nmagnezimore of a downgrade.. :|19:37
johnsomI think once the rough edges are buffed out we will be happier with it19:38
nmagneziyeah that's what they said about Vista :P19:40
nmagnezijokes aside, I really hope we'll get to that point..19:40
johnsomOh, Vista, ouch19:41
*** sshank has quit IRC19:46
nmagnezijohnsom, a question about
nmagnezijohnsom, i looked at the Octavia patch we merged some time ago ( )19:47
nmagnezijohnsom, do we need to also modify doc/source/ ?19:48
nmagneziin neutron-lbaas19:48
johnsomnmagnezi Short answer, yes.  Long answer, there is a bunch of re-work-around stuff that needs to happen to neutron-lbaas docs, but I have put them at a lower priority.19:49
nmagnezijohnsom, fair enough19:49
johnsomOctavia meeting starting soon on #openstack-lbaas19:50
johnsomMostly because most folks still go to the neutron docs for lbaas, so, it's all about priorities...19:52
nmagnezijohnsom, voted :)19:52
Alex_Staf_nmagnezi, the TC vote ?19:53
Alex_Staf_hi guys19:54
johnsomAlex_Staf_ Hi.  BTW, I moved your topic down to after the Bug/progress reports on the agenda19:55
johnsomMade it it's own topic item19:55
*** longstaf_ has joined #openstack-lbaas19:55
*** longstaff has joined #openstack-lbaas19:55
Alex_Staf_johnsom, cool19:56
*** slaweq_ has quit IRC19:57
johnsomI hope rm_work and kong can make this meeting, he has been active on the tempest stuff.19:58
Alex_Staf_johnsom, if they will not I promise I will bug them all other time :)19:59
johnsomHahaha, fair enough19:59
*** armax has quit IRC19:59
johnsomThey both tend to be on later in the day US19:59
johnsom#startmeeting Octavia20:00
openstackMeeting started Wed Oct 18 20:00:08 2017 UTC and is due to finish in 60 minutes.  The chair is johnsom. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: Octavia)"20:00
openstackThe meeting name has been set to 'octavia'20:00
Alex_Staf_johnsom, yep I already told my manager that my hours will be partly US oriented20:00
johnsomHi all20:00
johnsom#topic Announcements20:00
*** openstack changes topic to "Announcements (Meeting topic: Octavia)"20:00
*** sshank has joined #openstack-lbaas20:01
johnsomStarting off, Queens MS1 release is posted.  I'm not sure when they will approve and release that due to the zuul issues, but it's posted.20:01
johnsomAlso, Newton EOL coming - delayed by gate issues / zuul v320:01
johnsomNewton EOL should have been today, but I suspect it will get delayed a bit as well.20:02
xgerman_TC votes20:02
johnsomTC elections are open for voting.  If you are a foundation member and have contributed to OpenStack you should have received a ballot email.20:02
johnsom<It's on the agenda...>20:02
johnsomI also wanted to mention that I have started work on moving the Octavia projects over to using in-repo zuul v3 configs.20:03
johnsomSide note, if you use gmail the ballots are going into the spam folder....20:03
Alex_Staf_help with the email topic pls20:04
xgerman_PTG dates have been announced: week of 2/26 in Dublin20:04
Alex_Staf_it's going to a cold PTG20:04
*** ipsecguy_ has joined #openstack-lbaas20:04
xgerman_whiskey will keep you warm20:04
johnsomThe subject is "Poll: Queens TC Election"20:04
Alex_Staf_xgerman_, u , sir, r a wise man :)20:05
*** sshank has quit IRC20:05
johnsomImpact from the Zuul V3 work is for a short (as short as I can) we will be running duplicates of some of the gates.  One is the legacy- and one not.  legacy- is the old auto-generated job that will go away.20:06
johnsomI have started with neutron-lbaas as Octavia has nlbaas gates.20:06
johnsomSo far, it's going ok, but slower than I would like due to the zuul issues20:06
johnsomYep, PTG in Dublin.  Makes me nervous as I know some OpenStack locals that might try to break me.20:07
johnsomAny other announcements today?20:07
xgerman_birthdays, weddings ?20:08
*** ipsecguy has quit IRC20:08
johnsomNeither here...20:08
johnsom#topic Brief progress reports / bugs needing review20:08
*** openstack changes topic to "Brief progress reports / bugs needing review (Meeting topic: Octavia)"20:08
johnsomYou have probably seen the patches go by, I am working on getting our zuul v3 house in order.20:09
johnsomI also did some investigation into the OVH host gate failures, but ran out of creative ideas other than turning off KVM if the hostname has "-ovh-" in it.  Something about some of their hosts makes kvm die.20:10
rm_workAh while I remember, Alex_Staf_ can you stay on after the meeting for a bit if you can? wanted to talk to you about tempest stuff20:10
johnsomThe google implies an AMD issue, but I don't know20:10
johnsomAlso I wanted to highlight the provider driver spec is up for review:20:10
Alex_Staf_rm_work, sure it is part of the topics20:10
johnsomPlease give it a browse and comment so we can take a second pass addressing comments, having discussions, etc.20:11
johnsomAny other progress updates folks would like to share?20:11
Alex_Staf_johnsom, added to task list to view the doc20:12
johnsomCool, thanks20:12
johnsom#topic Automated tests - Structure guidelines Doc is needed20:12
*** openstack changes topic to "Automated tests - Structure guidelines Doc is needed (Meeting topic: Octavia)"20:12
johnsomAlex_Staf_ you have the floor...  grin20:12
Alex_Staf_Ok that's one mine20:12
*** sshank has joined #openstack-lbaas20:12
Alex_Staf_after submitting inital patch to the octavia git , and not the plugin ( my bad )20:13
Alex_Staf_I saw that I have many gaps that prevent me from going forward20:13
Alex_Staf_the fact that I am junior python writer is not helping so your help and guidance will be needed20:14
*** sshank has quit IRC20:14
*** sshank has joined #openstack-lbaas20:14
johnsomNot a problem, we are happy to help20:14
Alex_Staf_additionally we need those guidelines to be written20:14
rm_workYeah, so we have been working on a patch for almost three months now for the new tempest testing framework for octavia20:14
rm_workIt's here:
rm_workAny testing you write should be based on that patch20:14
rm_workIt provides all of the framework that should be required20:15
Alex_Staf_rm_work, cool20:15
rm_workMostly that is a collaboration between JudeC, kong and myself20:15
Alex_Staf_rm_work, I will look into that20:15
Alex_Staf_rm_work, add me to that list :)20:15
johnsomWell, there is a chain of patches:
rm_workI recommend you pull that down and try it out, and give us your comments ;)20:15
rm_workyes, so, there are a full range of tests based on this commit too20:15
Alex_Staf_I saw those and commented on several20:15
rm_workas johnsom points out20:15
rm_workwe need to rebase them20:15
rm_workwe have been stabilizing the first one20:16
rm_workbut now that it looks right, we can move on to rebasing and tweaking those other ones20:16
johnsomYeah, start with the LB patch, the others may need updates based on changes made to it20:16
nmagnezirm_work, will that framework use the octavia python client? (i know some tempest stuff is using tempest made clients)20:16
rm_workthat was our plan for the rest of this week20:16
rm_worknmagnezi: no20:16
rm_worknmagnezi: in fact, tempest guidelines specifically expect you to not use any client but the tempest ones20:17
nmagnezirm_work, i never understood the motivation for this20:17
rm_workbecause the clients are specifically made to interact correctly with the API20:17
nmagnezibut okay, good to know20:17
rm_workand tempest wants to be able to send custom stuff for negative tests20:17
*** openstackgerrit has quit IRC20:17
rm_workand trying to break the API / hit edge cases20:17
rm_workwhich using the clients would explicitly prevent20:17
johnsomnmagnezi I was thinking the same thing, but in reading more on the tempest docs, they want to use a built in REST client so you can do more negative testing than the SDK or client would allow.20:18
Alex_Staf_rm_work, tempest has functions for the Octavia API ?20:18
rm_workAlex_Staf_: it does as of :)20:18
johnsomYeah, what he said... grin20:18
rm_workthe goal of tempest is not "for everything to work correctly", it's "to break everything if possible" :P20:19
rm_workwhich means don't use known-good clients20:19
johnsomThese patches should be creating a tempest "service client" for octavia per:
rm_workyep, they do that20:19
Alex_Staf_rm_work, CRUD is not scenario testing we should move it to "API"20:19
nmagnezirm_work, in my mind, it would have made more sense to somehow have a way to switch off the checks in the official client and use it also for testing (but that's not for this discussion i guess)20:19
rm_workAlex_Staf_: API testing is for testing the API interactions, which our CRUD actually isn't20:20
nmagneziyeah, a scenario test is more of a "user story" i think\20:20
rm_workit's testing the backend processes20:20
Alex_Staf_rm_work, hmmm20:20
rm_workCRUD *is* a user story20:20
johnsomnmagnezi There might be some interesting philosophical questions with SDKs and clients to be had over beverages with the QA team20:20
rm_workwe *do have* API tests, that test the API explicitly, in the Octavia functional test suite20:20
Alex_Staf_rm_work,  a tricky one cus scenario should test not only creation but LB process for configuration scenario20:21
rm_workthe CRUD tests in Tempest are not actually testing the API20:21
rm_workwe know the API works from the other tests20:21
rm_workthese tests make sure the worker and queue and other-system integrations like nova and neutron work in reality20:21
Alex_Staf_rm_work, ok I got u , so we need to add some LB verification to the creation process20:21
rm_workwe also have tests for traffic20:22
johnsomrm_work I really like our existing API functional tests, but wonder if the release independent nature of the tempest plugin means we need "traditional" tempest API tests too.20:22
rm_workbut just being able to actually create, update and delete a LB is quite a lot more complex than just what the API does20:22
rm_workjohnsom: yeah, we discussed this before -- if we did API tests in tempest, it's probably a good idea, but we need to do them separately with a noop config20:23
rm_worki'd be in favor of adding a set of those20:23
Alex_Staf_rm_work,  ok I can live with that even though the terminology is different from what I am familiar with.20:23
johnsomOk, I am cool with that being a future item too.  We have coverage with functional API20:23
rm_workdefinitely future20:23
Alex_Staf_where can I look at the tests for traffic ?20:24
Alex_Staf_same link ?20:24
rm_workAlex_Staf_: when you get more deeply familiar with how octavia works on the backend, you'll understand better why I call CRUD a scenario :P20:24
johnsomAlex_Staf_ If you have not seen them, Octavia is a bit different than other projects in that our functional gates spin up an API server and run against that with no backend controller worker.20:24
rm_workthose are the traffic tests20:24
rm_workright now there's one, I have a second one WIP on top of it in a different CR20:24
Alex_Staf_rm_work, I know actually but u added a new logic to my understanding20:25
rm_workbut I still need to figure out some logistics around that one (it's for testing failover, and right now it is designed specifically for ACTIVE_STANDBY, which we don't run in our gates at all (though we should!)20:25
johnsomRight, Active/Standby tests have been long needed20:26
johnsomZuulv3 could make that actually possible20:26
nmagneziindeed. would be really great to have such  tests20:26
Alex_Staf_whats zuul (v3)20:26
rm_workyes, though also at the moment it only actually works with the FLIP driver, since the FLIP driver updates the DB on failover, but the default upstream driver does not20:26
rm_workI wanted to discuss a thought about how to make that happen, actually20:27
Alex_Staf_tnx, added to the task list20:27
johnsomIt's a new gate testing system for OpenStack.  It went live Sunday20:27
johnsomSo back to the tempest plugin, Alex_Staf_ you were asking about guidelines, I pointed you to the tempest plugin docs, were there more guidelines you think we as Octavia need to create?20:28
Alex_Staf_Where are the CRED function should be written for each object for example20:29
Alex_Staf_johnsom, after u told me that there will be object_client files it is clear to me . So stuff like those20:30
Alex_Staf_I think a brief explanation with example could be good .20:30
nmagnezijohnsom, what are our goals for the tempest plugin as far as queens goes anyway?20:31
johnsomI think once we have the LB patch landed it will be easier to follow the tempest plugin docs.20:31
Alex_Staf_johnsom, agree20:32
johnsomnmagnezi Good question, give me a second20:32
*** sshank has quit IRC20:32
johnsomFor the 'official" queens goal on the tempest plugin the completion criteria is here:20:32
nmagnezii see "Switch gating jobs to use the new plugin project instead of the bundled one"20:33
johnsomFor us, I would really like to see at least basic CRUD coverage for the main objects, LB, listener, L7, etc. running and gating20:33
nmagnezii guess we'll need to dedicate some resources to make it happen20:34
* nmagnezi glares at Alex_Staf_ 20:34
Alex_Staf_l7 has zillion of possible scenarios20:34
johnsomSo far, rm_work, JudeC, and kong have been working on that, more is always helpful!20:34
Alex_Staf_o/   \o/   \o20:35
*** armax has joined #openstack-lbaas20:35
rm_workyeah we haven't gotten to L7 yet lol20:35
*** sshank has joined #openstack-lbaas20:35
johnsomYeah, I'm not expecting we will have the mythical "full coverage" in queens, but at least a basic CRUD set would be good.20:35
Alex_Staf_rm_work, I have a matrix for that I will share20:35
xgerman_tests are a good way of getting people started on the project20:35
nmagnezixgerman_, +120:36
rm_workprobably we can have you work on that one :P just use that first LB testing patch as a base20:36
rm_workand look at how we were adding the other tests to it20:36
rm_worklike pool / listener20:36
Alex_Staf_cool I will study the testing patch and follow that20:37
Alex_Staf_prepare yourselves for a questions rain :)20:37
johnsomReally, the only other must-do item (IMO) is get a provider driver interface in place for queens20:37
johnsomAct/Act is high-want20:37
johnsomAgain, IMO20:38
johnsomAlex_Staf_ Don't be shy, we will all probably learn something20:38
*** openstackgerrit has joined #openstack-lbaas20:38
openstackgerritAdam Harwell proposed openstack/octavia-tempest-plugin master: Create scenario tests for loadbalancers
rm_work^^ addressed the latest round of concerns from you and kong20:39
johnsomOk, any other items on the tempest plugin work?20:39
rm_workerr, johnsom and kong20:39
*** PagliaccisCloud has quit IRC20:39
rm_workAlex_Staf_: yeah we may actually want to do some sort of dynamic testing with that20:39
rm_workbasically, provide that matrix in actual programatic matrix form, and have tempest do every permutation20:40
rm_work(for an API test, at least)20:40
rm_workthough it'd be nice to do it with traffic as well, but that'd require more individual tests i think20:40
Alex_Staf_rm_work, sounds smarter :) interesting how this happens20:40
johnsomWhat ever happened to that DDT stuff that was started in neutron-lbaas?  I know it never made it far enough to actually be a gate.20:40
Alex_Staf_rm_work, my plan is to test it with traffic20:40
xgerman_nah, it was in the gate bu tetsing took too long20:41
Alex_Staf_it did not play nice =\20:41
rm_workjohnsom: basically it died i think, fnaval_ was the driver for it IIRC and he got pulled off20:41
Alex_Staf_not on my setups at least20:41
fnaval_hi Alex_Staf_ - were you able to find what you were looking for earlier?20:41
xgerman_well, it was tesring a ton of combinations and that took long — so let’s focus on the ahppy case20:41
*** fnaval_ is now known as fnaval20:41
rm_workif we reuse a LB for that, it should be OK20:42
nmagnezirm_work, looks like he's back :)20:42
kongrm_work: ack20:42
Alex_Staf_fnaval, I am getting there . Have a big patch to read :)20:42
kongrm_work: will review and test today20:42
fnavalcool! =)20:42
xgerman_rm_work — reusing stuff is always questionable in tests20:42
rm_workxgerman_: yeah but in this case, we can have one that tries to test all permutations20:43
Alex_Staf_xgerman_, it is better to recreate for testing20:43
rm_worksince the issue will really be "does the traffic pass correctly", not "does the LB error"20:43
rm_workwe have other tests that we can run individually to make sure the LB correctly accepts the config20:44
fnavalI really liked that it did/does permutations so that it can find the edge cases.   I think tagging happy test cases and running them would be better(but leaving in the ddt stuff).20:44
xgerman_ok, I am just wary since if we find something odd it might be tough to reproduce.fix20:44
johnsomYes and no, I think we should look at optimizing the tests around a single LB where it makes sense.  We may be able to spin up more compute hosts with zuulv3 which would help with the test time by paralleling more.20:45
*** PagliaccisCloud has joined #openstack-lbaas20:45
johnsomLB create is high overhead and has a time penalty.20:46
johnsomAre we ready to move on to Open Discussion or is there more to discuss here?20:47
johnsom#topic Open Discussion20:47
*** openstack changes topic to "Open Discussion (Meeting topic: Octavia)"20:47
johnsomOk, other topics today?20:48
rm_workMaintenance API / Amphora-AZ20:48
rm_workI've had a spec stewing for an API around doing maintenance on AZ/HV ...20:48
rm_workbut I think I've been convinced we don't really need it20:48
rm_workso long as I can get agreement to merge one of the two patches I've got up for returning Amphora AZ data20:49
johnsomI lean towards the query nova approach, but I need to circle back on those. I have been distracted with all of these gate issues.20:50
rm_workThe first one stores the data locally in our DB at create time, so it can be very quickly searched/filtered on:20:50
rm_workThe second approach queries nova along with every request, and returns responses from that data:20:50
johnsomEvery request to this admin API for amphora details....20:50
rm_workyes, good distinction20:51
johnsomNot every API request20:51
rm_worknot like, EVERY call :P20:51
rm_workIt will be guaranteed accurate, while technically the first approach *could* drift, if people are doing live-migrates and such, though I don't think that's especially likely20:51
rm_workI'm generally more in favor of the first approach (we store it in the DB) because I think the risk/reward tradeoff is clear for me, but possibly with some deployers it might skew the other way20:52
rm_workI feel like the second one (query nova) is less contentious... less efficient in the 95% case, but more accurate in the 5% case20:52
rm_workand since we get to always go with the LCD here...20:53
rm_workMy guess is that's the one people will generally vote for ;)20:53
jnieszfor the first approach is there an option to re-sync?20:53
rm_workI didn't have one, though we could do that20:53
jnieszif it happens to get out of sync since create20:53
*** catintheroof has quit IRC20:53
rm_workjust adds complexity20:53
rm_workI'm sure housekeeping could do it as a periodic20:53
*** leitan has quit IRC20:53
*** catintheroof has joined #openstack-lbaas20:54
johnsomI lean more towards the query nova approach for two reasons. 1. Single point of truth in nova. 2. Platform folks may have maintenance procedures for the hosts/hypervisors that just live-migrates whatever instances are running for maintenance, so we would have inaccurate info in the DB.20:54
xgerman_let’s not overthink this — let’s go with nova and if we see issues we can add on20:54
johnsomTrue, it's probably easier to change to storing than to change the other way (no DB contraction for example)20:56
rm_workso ok, please review ?20:56
jnieszyea that makes sense20:56
johnsomOk, so  please everyone, review the specs rm_work listed and give your input.20:56
rm_workAs I said, I think the maintenance API spec is dead -- planning to abandon it assuming the Amp-az patch merges, and no one else expresses interest20:57
johnsomWe have a few more minutes, any other topics?20:57
rm_workI might put up another spec for an AZ-evacuate call to do pre-failure though20:57
*** catintheroof has quit IRC20:58
johnsomOk folks, thanks for the strong turn out today!20:58
nmagnezibye :)20:58
Alex_Staf_Good night/day/afternoon guys20:58
*** openstack changes topic to "Welcome to LBaaS / Octavia - Queens development is now open."20:59
openstackMeeting ended Wed Oct 18 20:58:59 2017 UTC.  Information about MeetBot at . (v 0.1.4)20:59
openstackMinutes (text):
Alex_Staf_rm_work, we covered everything u wanted ?20:59
rm_workI think so20:59
Alex_Staf_rm_work, me too20:59
*** longstaf_ has left #openstack-lbaas20:59
*** longstaff has quit IRC20:59
Alex_Staf_I will bug u from time to time20:59
nmagnezijohnsom, I have a question related to neutron-lbaas and security groups (not sure it is relevant for the Octavia implementation), do you have a minute?21:00
johnsomYeah, just ping folks here in the channel.  There are usually folks around that might be able to answer/help21:00
johnsomnmagnezi Sure21:00
nmagnezijohnsom, i was asked about a use-case that very much reminds what is listed here: (search for "Update the security group")21:01
nmagnezijohnsom, now, the person who asked me this told me he tested and tried to allow the loadbalancer to accept traffic only from a specific source21:02
nmagnezibut it does not seem to get enforced at all21:02
nmagnezi(the port details show that the sec group is indeed attached to the port)21:02
johnsomYep.  That doc is wrong21:02
nmagnezinow, we have a suspicion that this is not suppose to work21:03
johnsomIs this a port the user passed in or lbaas created?21:03
nmagneziso that port is kinda the same as a route port, no?21:03
nmagnezithe lbaas-vip port21:03
johnsomRight, but users can pass in a port or they can have neutron lbaas create the port.21:04
johnsomEither way, a security group gets applied to the port by lbaas/octavia that restricts it down to the TCP ports defined as listeners.21:05
johnsomThe issue comes around due to the port ownership and firewalling the amphora21:05
johnsomWe talked about this some at the PTG:21:05
johnsomLine 46921:05
* nmagnezi looks21:05
johnsomIn the past we proposed adding an ACL API for the listeners/load balancers to work around this issue21:06
johnsomThe container folks want to be able to add security groups to the ports to allow transitive trust, which is yet another issue.21:06
nmagneziso what do we expect to happen if a user creates a loadbalancer an existing port21:07
nmagneziwill that behave differently?21:07
nmagneziwill sec groups be enforced because that port was created by the user?21:08
johnsomI'm not 100% sure in neutron-lbaas with other drivers.  With Octavia we will apply our own SG to the port21:08
johnsomThis is "A hard one" grin21:08
johnsomWhat we really want is to be able to layer SGs with the base owned by the octavia service account and the later SGs owned by the tenant21:09
nmagneziack. i guess what i'm trying to understand is why technically it does not work in n-lbaas. I understand that the doc is wrong but not sure I understand how that vip port gets away from the sec group21:09
johnsomTechnically it's possible at a low level, but OpenStack doesn't really enable that today as far as I konw21:10
nmagneziyeah that sounds good actually..21:10
*** tongl has quit IRC21:11
johnsomnmagnezi My guess is if you come in with an admin account and look at the port it has a different SG applied to it.21:11
*** jdavis has quit IRC21:11
nmagnezijohnsom, i'll try to deploy and node and look, but from the log i got it seems like the sec group is indeed attached to the port, just not enforced at all21:12
nmagnezijohnsom, and by "port" i mean that port n-lbaas create from the VIP21:12
johnsomI know there was an old bug in neutron-lbaas v1 that SGs just didn't work, but I don't think that was an issue with v221:13
nmagnezimmm.. so what exactly makes the doc wrong? we don't expect this to work by design?21:15
johnsomWell, in most cases I don't think the user can see the VIP port as it's owned by neutron-lbaas/octavia. (unless the user is ADMIN)21:16
johnsomSecond I would expect the security group to just get overwriten21:17
nmagnezioverwritten when the user adds listeners for example?21:17
nmagnezii guess we have a doc to enhance.. :D21:18
johnsomWell, that is the newton version of the networking guide...21:19
*** AlexeyAbashkin has joined #openstack-lbaas21:19
johnsomA whole bunch of that documentation for neutron-lbaas has strange stuff in it.  It was outside of the repos so the neutron-lbaas folks didn't know it was getting changed wrong.21:20
*** AlexeyAbashkin has quit IRC21:24
nmagnezijohnsom, yeah. that doc is very misleading.. now I need to make sense of it to others :)
johnsomlol yes21:27
nmagneziafk for ~30 min21:27
johnsomnmagnezi We are certainly open to ideas around the SG issue21:27
nmagnezijohnsom, yeah. i'm not going to waste time on this from n-lbaas. would be cool to have it in Octavia. just wanted to help out the person who asked me :)21:28
*** sshank has quit IRC21:33
*** openstackgerrit has quit IRC21:48
mugsieThe problem with a Octavia owned security group is that normal users can't see it21:49
johnsomHa, yes, that is one issue I listed above.21:50
johnsomUp late?21:50
mugsieYeah, just on the way home21:50
mugsieHad a beer with kiall21:50
xgerman_(from a pub)21:50
johnsomHa, nice. speaking terms21:50
mugsieHey, you got to get in training for the PTG21:51
johnsomHahaha, I know....21:51
mugsiexgerman_: seems ready21:53
rm_workI get absolutely wrecked by pretty much any European, so I don't even try to keep up anymore :P21:55
rm_workwent head-to-head with a German when I was 21 ... Thankfully he got me home somehow. :P21:56
mugsieGermans can be dangerous. They have hollow legs21:56
*** slaweq_ has joined #openstack-lbaas21:58
*** slaweq_ has quit IRC22:02
*** leitan has joined #openstack-lbaas22:04
*** ipsecguy_ has quit IRC22:06
*** openstackgerrit has joined #openstack-lbaas22:07
openstackgerritMichael Johnson proposed openstack/octavia-dashboard master: Add release notes support to octavia-dashboard
*** leitan has quit IRC22:08
*** sshank has joined #openstack-lbaas22:11
*** med_ has quit IRC22:23
*** Guest99060 has joined #openstack-lbaas22:23
*** ipsecguy has joined #openstack-lbaas22:29
johnsomSo, the sphinx template tool builds broken sphinx configs...  Ah well, that fixes the release notes for dashboard.22:34
*** jniesz has quit IRC22:42
*** fnaval has quit IRC22:47
*** jdavis has joined #openstack-lbaas23:12
*** jdavis has quit IRC23:17
*** AlexeyAbashkin has joined #openstack-lbaas23:19
*** AlexeyAbashkin has quit IRC23:23
openstackgerritMichael Johnson proposed openstack/octavia master: Move Octavia zuulv3 configuration in repo
rm_workjohnsom: so we're good for Octavia now that n-lbaas merged?23:53
johnsomThe octavia patch is next, yes.  I noticed I had the wrong nlbaas job voting so just fixed that.23:54
johnsomHopefully we can merge the octavia one tomorrow then I can put in the jobs to remove the legacy-23:55
johnsomJust a bummer it's taking 4+ hours for a run to finish today.23:55
rm_workeverything is running TWICE23:57
rm_workfor everyone23:57
rm_workuntil they all get this stuff merged23:57
rm_workso the gates are understandably slammed during transition23:57
johnsomIt seems like this is the issue they are fighting at the moment:23:58

Generated by 2.15.3 by Marius Gedminas - find it at!