Wednesday, 2018-01-17

« Tuesday, 2018-01-16 Index Thursday, 2018-01-18 »
*** yamamoto has joined #openstack-lbaas00:08
*** nmagnezi has quit IRC01:13
*** nmagnezi has joined #openstack-lbaas01:13
*** nmagnezi has quit IRC01:26
*** nmagnezi has joined #openstack-lbaas01:28
openstackgerritHengqing Hu proposed openstack/octavia-dashboard master: Remove oslosphinx from docs  https://review.openstack.org/53423801:31
*** dayou has quit IRC01:51
*** dayou has joined #openstack-lbaas02:20
*** dayou has quit IRC02:26
*** dayou has joined #openstack-lbaas02:43
*** fnaval_ has quit IRC02:46
*** fnaval has joined #openstack-lbaas02:48
openstackgerritwanghui proposed openstack/octavia master: fix the wrong path of LoadBalancer  https://review.openstack.org/53459302:57
openstackgerritwanghui proposed openstack/octavia master: Fix a typo of "octavia" in comment  https://review.openstack.org/53459303:46
openstackgerritMichael Johnson proposed openstack/octavia-dashboard master: Update the installation and contributors documents  https://review.openstack.org/53376003:55
*** fnaval has quit IRC03:59
openstackgerritMichael Johnson proposed openstack/octavia master: Don't run fucntional jobs for docs changes  https://review.openstack.org/52654804:43
openstackgerritMichael Johnson proposed openstack/octavia master: Don't run fucntional jobs for docs changes  https://review.openstack.org/52654804:45
*** links has joined #openstack-lbaas04:49
openstackgerritMichael Johnson proposed openstack/neutron-lbaas master: Don't run scenario jobs for docs changes  https://review.openstack.org/53461904:54
*** annp has joined #openstack-lbaas06:00
*** armax has quit IRC06:01
*** armax has joined #openstack-lbaas06:01
*** armax has quit IRC06:02
*** armax has joined #openstack-lbaas06:02
*** armax has quit IRC06:02
*** gcheresh has joined #openstack-lbaas06:27
*** fnaval has joined #openstack-lbaas06:35
*** sapd__ has quit IRC06:38
*** sapd__ has joined #openstack-lbaas06:39
openstackgerritOpenStack Proposal Bot proposed openstack/neutron-lbaas master: Imported Translations from Zanata  https://review.openstack.org/52760006:41
*** Alex_Staf has joined #openstack-lbaas06:43
openstackgerritSanthosh Fernandes proposed openstack/octavia master: L3 ACTIVE-ACTIVE Data model impact  https://review.openstack.org/52472206:44
*** Alex_Staf has quit IRC07:13
*** threestrands_ has quit IRC07:20
openstackgerritchenxiangui proposed openstack/octavia master: Change import order  https://review.openstack.org/53465607:42
*** pcaruana has joined #openstack-lbaas07:48
*** pcaruana has quit IRC07:55
*** pcaruana has joined #openstack-lbaas07:55
*** AlexeyAbashkin has joined #openstack-lbaas07:57
*** cristicalin has joined #openstack-lbaas08:04
*** Alex_Staf has joined #openstack-lbaas08:13
*** cristicalin has quit IRC08:14
*** cristicalin has joined #openstack-lbaas08:14
*** b_bezak has joined #openstack-lbaas08:17
*** cristicalin has quit IRC08:22
*** cristicalin has joined #openstack-lbaas08:22
*** tesseract has joined #openstack-lbaas08:29
*** cristicalin has quit IRC08:41
*** rcernin has quit IRC08:45
openstackgerritchenxiangui proposed openstack/octavia master: Fix the wrong word  https://review.openstack.org/53468608:54
*** annp has quit IRC09:01
*** annp has joined #openstack-lbaas09:01
*** gans has joined #openstack-lbaas09:22
*** rcernin has joined #openstack-lbaas09:40
ganshttps://github.com/openstack/requirements/commit/34d56244a87ac2a61170ab8fa81dc86dba70fc1f#diff-0bdd949ed8a7fdd4f95240bd951779c809:41
ganshttps://github.com/openstack/requirements/commit/34d56244a87ac2a61170ab8fa81dc86dba70fc1f#diff-0bdd949ed8a7fdd4f95240bd951779c8L36809:42
gansSphinx version has been upgraded to 1.6.6  .   Getting this error on zuul : http://logs.openstack.org/22/524722/32/check/build-openstack-sphinx-docs/345e926/job-output.txt.gz#_2018-01-17_06_56_12_47647509:43
ganshttp://logs.openstack.org/22/524722/32/check/build-openstack-sphinx-docs/345e926/job-output.txt.gz#_2018-01-17_06_56_12_47647509:43
*** yamamoto has quit IRC09:49
*** yamamoto has joined #openstack-lbaas09:57
*** annp has quit IRC10:09
*** salmankhan has joined #openstack-lbaas10:15
openstackgerritGanpat Agarwal proposed openstack/octavia master: [WIP] ACTIVE-ACTIVE with exabgp-speaker - Octavia agent  https://review.openstack.org/49101610:17
*** salmankhan has quit IRC10:19
*** yamamoto has quit IRC10:31
*** yamamoto has joined #openstack-lbaas10:31
*** yamamoto has quit IRC10:31
*** gans has quit IRC10:33
*** gans has joined #openstack-lbaas10:35
*** sri_ has joined #openstack-lbaas10:39
*** salmankhan has joined #openstack-lbaas10:51
*** dims has quit IRC10:57
*** dims has joined #openstack-lbaas10:58
*** gans has quit IRC11:11
openstackgerritMerged openstack/octavia-dashboard master: Remove oslosphinx from docs  https://review.openstack.org/53423811:15
*** yamamoto has joined #openstack-lbaas11:32
*** yamamoto has quit IRC11:32
*** yamamoto has joined #openstack-lbaas11:32
*** AlexeyAbashkin has quit IRC11:36
openstackgerritMerged openstack/python-octaviaclient master: Updated from global requirements  https://review.openstack.org/53305111:57
openstackgerritMerged openstack/python-octaviaclient master: Remove direct dependency on testtools  https://review.openstack.org/53332011:58
*** AlexeyAbashkin has joined #openstack-lbaas12:02
*** AlexeyAbashkin has quit IRC12:06
*** AlexeyAbashkin has joined #openstack-lbaas12:12
*** salmankhan has quit IRC12:12
*** salmankhan has joined #openstack-lbaas12:14
*** rcernin has quit IRC12:14
*** fnaval has quit IRC13:37
dayougans, https://github.com/sphinx-doc/sphinx/pull/4335/files, while sphinx was upgraded to 1.6.6, it included a fix that has negative side effect.13:54
*** gans has joined #openstack-lbaas13:58
*** gans has quit IRC14:01
*** aojea_ has joined #openstack-lbaas14:02
openstackgerritHengqing Hu proposed openstack/octavia master: Add license for empty __init__.py  https://review.openstack.org/53476514:10
dayouI tried to fix that here: https://review.openstack.org/#/c/534765/14:14
*** gans has joined #openstack-lbaas14:28
gansdayou, i tried your patch, worked perfect14:29
dayougans, thanks for the testing, man!14:29
*** ianychoi has quit IRC14:48
*** ianychoi has joined #openstack-lbaas14:52
*** fnaval has joined #openstack-lbaas14:57
*** links has quit IRC15:11
*** armax has joined #openstack-lbaas15:14
*** gans has quit IRC15:27
*** yamamoto has quit IRC15:31
*** yamamoto has joined #openstack-lbaas15:46
*** gcheresh has quit IRC15:51
*** yamamoto has quit IRC15:51
*** Alex_Staf has quit IRC15:57
*** gans has joined #openstack-lbaas15:58
*** yamamoto has joined #openstack-lbaas16:04
*** b_bezak has quit IRC16:05
*** yamamoto has quit IRC16:08
*** atoth has joined #openstack-lbaas16:08
*** aojea_ has quit IRC16:17
*** aojea_ has joined #openstack-lbaas16:17
*** aojea_ has quit IRC16:22
*** b_bezak has joined #openstack-lbaas16:30
*** AlexeyAbashkin has quit IRC16:41
*** sanfern has joined #openstack-lbaas16:45
*** pcaruana has quit IRC16:46
*** jniesz has joined #openstack-lbaas16:55
johnsomdayou Do you have any ideas on this failure on the Ocata branch? https://review.openstack.org/#/c/515768/17:02
*** salmankhan has quit IRC17:04
*** salmankhan has joined #openstack-lbaas17:05
*** gans has quit IRC17:08
*** yamamoto has joined #openstack-lbaas17:08
*** b_bezak has quit IRC17:14
*** yamamoto has quit IRC17:17
*** tesseract has quit IRC17:21
openstackgerritSanthosh Fernandes proposed openstack/octavia master: L3 ACTIVE-ACTIVE Data model impact  https://review.openstack.org/52472217:28
*** beagles is now known as beagles_afk17:35
*** aojea has joined #openstack-lbaas17:50
*** aojea_ has joined #openstack-lbaas17:55
*** aojea has quit IRC17:58
*** aojea has joined #openstack-lbaas18:01
*** aojea_ has quit IRC18:03
*** aojea_ has joined #openstack-lbaas18:05
*** Alex_Staf has joined #openstack-lbaas18:07
*** aojea has quit IRC18:08
*** aojea has joined #openstack-lbaas18:11
*** aojea_ has quit IRC18:13
*** ianychoi has quit IRC18:14
*** ianychoi has joined #openstack-lbaas18:15
*** aojea_ has joined #openstack-lbaas18:15
*** aojea has quit IRC18:19
*** AlexeyAbashkin has joined #openstack-lbaas18:20
*** aojea has joined #openstack-lbaas18:21
*** aojea_ has quit IRC18:23
*** AlexeyAbashkin has quit IRC18:25
*** aojea_ has joined #openstack-lbaas18:25
*** sanfern has quit IRC18:27
*** aojea has quit IRC18:28
*** aojea has joined #openstack-lbaas18:31
*** aojea_ has quit IRC18:34
*** aojea has quit IRC18:39
*** openstackstatus has quit IRC18:40
*** openstackstatus has joined #openstack-lbaas18:42
*** ChanServ sets mode: +v openstackstatus18:42
*** sanfern has joined #openstack-lbaas18:43
*** AlexeyAbashkin has joined #openstack-lbaas18:47
*** AlexeyAbashkin has quit IRC18:52
*** ivve has quit IRC19:05
*** atoth has quit IRC19:12
*** ivve has joined #openstack-lbaas19:19
*** longstaff has joined #openstack-lbaas19:45
Alex_StafI am ready :)19:54
johnsomNice19:55
rm_workI am awake!19:56
johnsomWow, double bonus19:56
Alex_Stafrm_work, what time is now there ? ( BTW where is there?)19:57
rm_work.... noon19:57
rm_workSeattle area <_<19:58
xgerman_not in RAX time19:58
Alex_Staf10 h difference19:58
nmagneziAlex_Staf, it does not matter. rm_work never actually sleeps19:59
rm_workyeah if this meeting was at like 2am i'd probably make it much easier :P19:59
Alex_Stafnmagnezi, agreed so the effort does not count it is standard  now19:59
Alex_Stafhaha19:59
cgoncalvesowl kind of guy :)19:59
Alex_Stafrm_work, for us specially19:59
johnsom#startmeeting Octavia20:00
openstackMeeting started Wed Jan 17 20:00:02 2018 UTC and is due to finish in 60 minutes.  The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
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
johnsomHi folks20:00
nmagnezio/20:00
longstaffhi20:00
Alex_Stafo/20:00
johnsomSounds like we have a good crowd today20:00
xgerman_o/20:00
johnsom#topic Announcements20:00
*** openstack changes topic to "Announcements (Meeting topic: Octavia)"20:00
johnsomFinal reminder: feature freeze - Queens MS3 is coming January 22nd20:00
johnsom#link https://releases.openstack.org/queens/schedule.html20:01
johnsomThis is next week folks!20:01
jnieszhi20:01
johnsomAlso, please note that all requirements changes need to be in next week as well as global requirements will freeze20:01
rm_workok, I will check today to see if there's anything of mine that's waiting on me20:02
johnsomI am closely monitoring the openstacksdk GR change to make sure it makes it for our dashboard.20:02
johnsomRocky release schedule has been published20:02
nmagnezijohnsom, do we have a review priority list?20:02
johnsom#link https://releases.openstack.org/rocky/schedule.html20:02
johnsomPriority bug/patch list for Queens20:03
johnsom#link https://etherpad.openstack.org/p/Octavia-Queens-Priority-Review20:03
johnsomnmagnezi It was next on the agenda....20:03
nmagnezisorry :)20:03
johnsomNP20:03
johnsomPriority now is getting feature patches merged. Then we will have a bit of time to focus on bugs.20:03
johnsomPTL nominations for Rocky open January 29th20:04
Alex_Staf:( I am QA this will always be sad for me20:04
johnsom#link https://governance.openstack.org/election/20:04
rm_workI nominate johnsom as PTL!20:04
rm_workFour more years!20:04
nmagnezi+220:04
nmagnezi:)20:05
johnsomSo now is the time to get you company buy-in if you are interested in running for PTL20:05
johnsomYou guys have to wait until the 29th20:05
johnsomgrin20:05
johnsomIf anyone has questions about the PTL role, feel free to ping me20:05
johnsomAlso of note, the provider specification has merged!20:05
jnieszjohnsom are you able to run again?20:06
johnsomjniesz I don't know yet20:06
johnsomIt's too early for the pointy hair types to have considered it...  grin20:06
cgoncalvesable and willing to :)20:07
johnsomAny other announcements today?20:07
johnsom#topic Brief progress reports / bugs needing review20:08
*** openstack changes topic to "Brief progress reports / bugs needing review (Meeting topic: Octavia)"20:08
johnsomI am busy on act/act and making sure we have a plan for MS3.20:08
johnsomI posted a patch for the amphora driver that merges the OVS and L3 needs.20:09
johnsomI am currently working on the OVS element for the amphora image. This is a bit complicated as the distros do not seem to have a version that has the features we need.20:09
Alex_Stafjohnsom, BTW are there plans for octvia to work with OVN ?20:10
jnieszjohnsom, usually the cloud archive repos have newer ovs20:10
jnieszdistros ovs version is usually way behind20:10
Alex_StafI am wokring on moving neutron lbaas tests to octavia plugin to have very basic coverage20:10
johnsomjniesz, yes, but those also bring other baggage...20:11
*** Kowsalya_ has joined #openstack-lbaas20:11
jnieszyea, I've also compiled from source for new ovs20:11
rm_workAlex_Staf: so, I would push the brakes a bit on your work there actually20:11
Alex_Stafrm_work, do tell :)20:12
johnsomAlex_Staf Currently, I don't think octavia needs to be aware of OVN itself.  There is a proposed driver for it however on the neutron-lbaas side.20:12
rm_workAlex_Staf: A) we're explicitly not directly porting tests, because our old tests were bad20:12
rm_workAlex_Staf: B) I've noticed a lot of your patches are duplicates of stuff we already have in progress (other patches)20:12
rm_workand that are almost complete20:12
rm_workI would recommend taking a day or two to look at what already is in progress20:12
rm_workand maybe review / test / contribute to those patches20:12
Alex_Stafrm_work, pls share the patches . I know there is a listener patch but it has no traffic in it20:13
johnsom+1 Yes, this tempest-plugin should be legacy free and aligned to the current tempest plugin requirements.  The old tests are horrible and we have explicitly not copied them over.20:13
*** salmankhan has quit IRC20:13
rm_workAlex_Staf: just look at https://review.openstack.org/#/q/project:openstack/octavia-tempest-plugin20:13
Alex_Stafjohnsom, rm_work ok , Could u pls expand why do u think they were bad ? ( I did not write them so it is ok  :))20:13
Alex_StafI am asking bcus I think they provide us with very basic nice covarage20:14
Alex_Stafcoverage20:14
rm_workso for example, your listener test20:14
rm_workhttps://review.openstack.org/528727 (Loadbalancer test_listener_basic test added.)20:14
rm_workis literally right next to this one in the list:20:14
johnsomOne other progress update on my part (probably should have been an announcement): Ubuntu has posted an early version of bionic (18.x) that will be the new LTS.  It has the old 1.7.9 haproxy in it from artful. I have opened a bug to get 1.8-stable in bionic: https://bugs.launchpad.net/bugs/174346520:14
openstackLaunchpad bug 1743465 in haproxy (Ubuntu) "Bionic should have haproxy 1.8-stable" [Undecided,Confirmed]20:14
rm_workhttps://review.openstack.org/#/c/492311/ (20:14
rm_workAdd basic tests for listeners)20:14
johnsomPlease upvote that bug if you care about getting 1.8 into the next LTS that OpenStack will adopt.20:15
*** b_bezak has joined #openstack-lbaas20:15
rm_workwhich has been in development since August20:15
johnsom#link https://review.openstack.org/#/q/project:openstack/octavia-tempest-plugin+status:open20:15
Alex_Stafrm_work, agree- but this test does not send traffic to be load balanced . it is CRED api test basically20:15
johnsomThat may help, it is a list of the open patches for the tempest-plugin20:15
*** Kowsalya_ has quit IRC20:16
rm_workwe have a test already merged that sends traffic20:16
rm_workhttps://github.com/openstack/octavia-tempest-plugin/blob/master/octavia_tempest_plugin/tests/v2/scenario/test_basic_ops.py#L62-L9220:16
Alex_Stafthe basic test ?20:16
rm_workyes20:16
*** slaweq has joined #openstack-lbaas20:17
nmagnezimight be worth having a storyboard for newly suggested test so we can have a discussion about new tests before one invest time in coding them..20:17
rm_workwe will need more complex ones eventually for like, L7 Session Persistence and the like20:17
johnsomAlex_Staf The issues with the old tempest tests are: 1. They do not adhere to the tempest-plugin stable APIs, they use legacy code from tempest. 2. They are laid out poorly, loading too many things into single calls, so things can't be reused. Etc.20:17
rm_workbut yeah20:17
rm_workwhat i'm saying is, we need to step back and discuss what tests we need, which ones are in flight, etc20:17
rm_workbefore people end up doing a ton of duplicate or unnecessary work20:18
Alex_Stafok guys I will not proceed with those20:18
Alex_StafI will start proposing tests from my test plan though20:18
rm_workas an action item, people who are interested in testing (hopefully a lot of us) should schedule a time to actually go through this20:18
Alex_StafI have bunch of test I need to automate20:18
rm_workand make an etherpad we can use as a development guide20:18
rm_work1) Agree what tests we need to have20:19
rm_work2) Lay them out logically20:19
johnsom#link https://storyboard.openstack.org/#!/project/91020:19
rm_work3) Add links to ones that are in progress20:19
johnsomStories can go there.20:19
xgerman_is our google doc with test cases still floating around?20:19
rm_workLOL20:19
rm_workthat was from20:19
rm_workoh man20:19
rm_worklike 2016?20:19
johnsomyears ago20:19
rm_work2015?20:19
*** b_bezak has quit IRC20:19
rm_workI might have access somewhere...20:19
xgerman_LBs didn’t change that much…20:19
rm_workanyway, again, what i am saying is we need to meet about this20:20
johnsomTrue, it is still probably valid to some degree.  Let me look if I have a link20:20
rm_workbecause it will eat our whole meeting if we let it20:20
rm_workso let's agree to meet soon, and then move on with this meeting :P20:20
rm_workI am also very interested in getting testing sorted out20:20
Alex_Stafcool I already cant wait20:21
johnsomYeah, also interested in helping out with testing.20:23
xgerman_+120:23
nmagnezi+120:23
Alex_Stafmy main effort is testing so let make it count :)20:23
rm_workwould be good to at least have all objects covered with CRUD20:23
johnsomAny other progress updates today?20:23
rm_workAlex_Staf: yeah i was not saying STOP WORKING, just ... focus on review/test/contribution to the existing patches first20:23
rm_workso we can get those merged20:23
rm_workand then move on to the harder stuff20:23
johnsomYeah, we need the basic CRUD to close our community goal...20:23
Alex_Stafrm_work, np  this is how I understood it20:23
cgoncalvesI have made some progress on the health manager dynamic vif instatiation thingy PoC20:24
johnsomAh, for the lb-mgmt-net20:24
cgoncalvesthe thing I mentioned a few weeks ago (last year!) that was considering os-vif20:24
johnsomCool, feel free to put that on the agenda when you are ready to present it.20:24
cgoncalvesI have uploaded a super early patch set to os-vif20:25
cgoncalvesI will :)20:25
cgoncalves#link https://review.openstack.org/#/c/533713/20:25
johnsom#topic CLI for amphora actions (failover, etc.) (xgerman)20:25
*** openstack changes topic to "CLI for amphora actions (failover, etc.) (xgerman) (Meeting topic: Octavia)"20:25
johnsom#link https://review.openstack.org/#/c/532424/20:25
johnsomUgh, the agenda got a little out of order, sorry Alex, you are next!20:26
xgerman_ok, my turn?20:26
Alex_Stafxgerman_, shoot20:26
xgerman_yeah, ao my main worry is that if we keep adding Octavia provider speicifc functionality to the client without marking it as such things will get confusing for users20:27
xgerman_imagine another provider adds special functionality to the CLI…20:27
xgerman_how does a user know which commands are for wich provider20:27
xgerman_?20:27
rm_workyes, i actually agree20:28
rm_worki kinda DO want a namespace "octavia" for these things20:28
rm_workbecause if you think about it20:28
* cgoncalves wonders if 'octavia' provider is the best name for calling the reference implementation20:28
rm_workwe have `loadbalancer` for /lbaas/20:28
rm_workwe should have `octavia` for /octavia/20:28
rm_workcgoncalves: that's ... a fair point :/20:28
xgerman_cgoncalves: +120:28
rm_workwhere we are now is where i kept trying to get people to go originally, like 3 years ago, but at the time politically we had to play things a little differently20:29
johnsomWell, it is the bundled reference (default) driver20:29
cgoncalvesputting that naming aside, wouldn't most/all providers provide a failover api anyway?20:29
xgerman_we have that with laod balancer20:29
rm_workmaybe? but we can't guarantee it's consistent20:29
johnsomI agree that the currently proposed: openstack loadbalancer amphora failover is a bit confusing.20:29
rm_workin how it works, or what it requires as input20:29
xgerman_but this talks about amphora failover20:29
rm_worki would recommend we do `openstack octavia amphora failover` and `openstack octavia amphora list`20:30
rm_workfor example20:30
rm_worki am pretty sure the namespace is clear >_>20:30
johnsomI think we will have a hard time getting "openstack octavia" approved, as they call out *not* including project names/code names in the OSC docs.20:30
rm_workeugh20:30
jnieszwouldn't failover be relevant to all providers that used amps?20:30
jnieszsome providers don't use amps20:30
cgoncalves-1 for 'openstack octavia' because openstack cli is supposed to be service implementation agnostic20:31
rm_workjniesz: well, we have no idea what the API for that would look like20:31
cgoncalveson the other side, there's 'openstack congress' for example20:31
Alex_StafI think openstack loadbalancer is very good20:31
rm_workwell, this is not something that's agnostic to service implementation20:31
rm_workit's specifically octavia20:31
rm_workthis won't work now or probably ever for F5 / A10 / etc20:31
rm_workbecause it's not part of the loadbalancer API yet20:32
cgoncalvesrm_work: true. I also don't like much 'openstack loadbalancer' either but I can't think of a better name for it20:32
nmagnezifor what it's worth, there are precedents for implementation specific API calls even in neutron-lbaas API (something with which agent is hosting which loadbalancer)20:32
rm_workwhen/if we make a version of the call that's architected to be exposed inside /lbaas/ (the namespace for the generic calls) then we would want those CLI options to be available20:32
johnsomI hate to make it so long, but maybe "openstack loadbalancer driver octavia amphora failover" LOL20:32
xgerman_well, we are ok with openstack loadbalancer for the functionality every provider *should* support20:32
Alex_Stafthe cli should be comfortable for the userm and the API path should be matched to that and not the opposite20:32
nmagnezijohnsom, LOL +120:32
Alex_Stafjohnsom, +120:32
rm_workxgerman_: +120:33
rm_workthat's what i'm saying20:33
xgerman_the question is where do we put provider specific stuff20:33
Alex_StafI, as  a user would like to see what I am doing in the command I execute , ieven if it is long20:33
rm_workso, we DO have an `openstack loadbalancer failover` which is different from what `openstack octavia amphora failover` would do20:34
rm_worknot to mention there's LIST/GET commands for amphora too20:34
johnsomOne other consideration "openstack extension" exists...  Maybe we can build on that20:34
xgerman_yes, failing over a load balancer has meaning for ote rproviders20:34
rm_workI vote we at least try to get `openstack octavia` approved20:34
cgoncalvesI suggest we check how other projects are doing, e.g. neutron (obviously), with regard to provider-specific commands and generic ones20:34
xgerman_+!20:34
johnsomYeah, this is a good conversation for the PTG too, though that is a while out.  In Denver I just camped in the OSC room for an hour and hashed out our issues....20:35
rm_workyeah, I'm still looking at whether i can get to that or not20:36
rm_workit's looking a lot like "if i can crash on someone's floor for the week"20:36
rm_workthen I can buy my own airfare...20:36
xgerman_:-(20:36
rm_worksimilar to you in AUS I guess20:36
xgerman_yep20:36
johnsomSo, let's take an action item to go research how other projects have handled the driver specific commands, and come back next week with some ideas.20:37
johnsom#link https://etherpad.openstack.org/p/octavia-drivers-osc20:37
johnsomHere is an etherpad we can put down references and ideas.20:37
rm_workOr I might just suck it up and get a cheap airbnb if such a thing exists20:37
xgerman_hostel?20:37
rm_workin europe those tend to be OK, yeah20:38
xgerman_rm_work also try tavel assistance20:38
cgoncalvesjohnsom: thanks!20:38
rm_worki think it's too late20:38
xgerman_nope: #link http://superuser.openstack.org/articles/tips-for-getting-a-travel-grant-to-the-next-openstack-summit/20:38
rm_workas usual, corporate is unclear on whether they'll do travel, until after the travel assist program finishes20:38
rm_workkkk20:39
rm_worki'll file20:39
-openstackstatus- NOTICE: Zuul will be offline for a few minutes; existing changes will be re-enqueued; approvals during the downtime will need to be re-added.20:39
johnsomJoy, more zuul fun20:39
johnsomOk, moving on20:40
johnsom#topic Testing automation - L7 content switching coverage plan- what is planned for that? (Alex_Staf)20:40
rm_workthough i can't find the dublin page :/20:40
*** openstack changes topic to "Testing automation - L7 content switching coverage plan- what is planned for that? (Alex_Staf) (Meeting topic: Octavia)"20:40
johnsomrm_work https://www.openstack.org/ptg#tab_travel20:40
Alex_StafOל דם ןא ןד רקךשאקג אם אקדאןמע שמג 'ק שרק מםא איקרק נוא20:41
Alex_Stafohhhhh20:41
johnsomrm_work or specifically: https://openstackfoundation.formstack.com/forms/travelsupportptg_dublin20:41
rm_workanyone here doing single occupancy that would just upgrade to a double and i can give you the difference :P20:41
rm_workit's small20:41
johnsomHa, ummm, do I need google translate for this? grin20:41
Alex_Stafok this is related to test of l720:41
Alex_Stafwe should have a robot for wrong language20:41
johnsomOuch, google translate fails me20:41
Alex_StafI made a matrix with the feature coverage for planning but I think rm_work once told me there will be some tool that will run automatically on all options ?20:42
johnsomDDT? I'm not sure what the status of that is....20:43
*** KeithMnemonic has joined #openstack-lbaas20:43
xgerman_yep20:43
xgerman_but wroth looking into20:43
Alex_Stafoh this is what are those DDT test in lbaas ?20:43
xgerman_yep20:44
Alex_StafI could not figure that out20:44
johnsomYeah, that got started, but never finished.  They currently don't run in the gate if I remember correctly20:44
johnsomIf I remember it was based on this module:20:45
johnsom#link https://pypi.python.org/pypi/testscenarios20:45
xgerman_they understandibly take a very long time… so ran afoul the gate limit20:45
johnsomWhich hasn't been updated since 201520:45
johnsomSo, that might not be a good idea20:46
Alex_StafI will start automating tests even if it is for Redhat - we need and want that ASAP. I would love to write them in a way that fit upstream so it can be contributed so I think we should have a plan next week20:46
johnsomYes, we had gate time limit issues with the way the tests were designed.  For things like this we should really work to design tests to re-use the LB as much as possible to limit the number of VM boots.20:47
johnsomAlex_Staf +120:47
johnsomMy #1 concern is making sure we adhere to only using the stable interface:20:47
johnsom#link https://docs.openstack.org/tempest/latest/plugin.html#stable-tempest-apis-plugins-may-use20:47
johnsomThis is where the old tests go off the rails due to legacy20:48
Alex_StafOk I will consult face to face with nmagnezi in the office20:49
johnsom#2 is making it nicely moduler so we can add new tests easily.20:49
Alex_Stafnot to miss anything20:49
johnsomAlex_Staf was there a specific topic about L7 tests?20:49
Alex_Stafjohnsom, yes to ask regarding the automatic matrix20:49
Alex_Stafas I did and got an answer20:49
Alex_Staf:)20:50
johnsomOk20:50
nmagneziAlex_Staf, might be worth to have a dedicated community meeting about tests :-)20:50
Alex_Stafnmagnezi, indeed20:50
johnsomI think we need to align our API testing too.  Currently this is done with the functional tests that are in-tree.  I think we should talk about moving those out of tree into the plugin or ...  I don't think we need duplicate tests in the tempest-plugin20:51
johnsomYeah, good idea.20:52
*** KeithMnemonic has quit IRC20:52
xgerman_+120:52
johnsom#link https://etherpad.openstack.org/p/octavia-testing-planning20:52
Alex_Stafis there anybody else planning to write tests ?20:53
cgoncalvesFYI, added these 2 new etherpads to https://etherpad.openstack.org/p/octavia-ptg-rocky20:54
johnsom<PTL hat> Testing is everyone's responsiblity</PTL hat>20:54
johnsomI would like to help with tests, eventually20:54
nmagnezijohnsom, let's see how the meeting minutes keeps the formatting with this ^^ :)20:55
johnsomHa20:55
Alex_Stafjohnsom, I know but everybody has ton of other staff so it eventually could be unprioritized20:55
Alex_Stafnmagnezi, LOL20:55
johnsomSo let's update that etherpad with thoughts/issues then we can schedule a testing meeting either via IRC or hangouts.20:55
johnsomAlex_Staf Once we have a good framework set out, it will become a gating factor to get features merged.20:56
johnsomIMO20:56
Alex_Stafjohnsom, amen to that20:56
nmagnezi+120:56
johnsomI think we have just been missing the basic framework for folks to build off of.20:57
rm_workyep20:57
johnsom#topic Open Discussion20:58
*** openstack changes topic to "Open Discussion (Meeting topic: Octavia)"20:58
johnsomAnything else in the few minutes left?20:58
jniesz#link https://review.openstack.org/#/c/528850/20:58
jnieszposted some comments20:58
jnieszregarding support for multiple service_types for amps20:58
johnsomjniesz Ok.  It's good to vote so they don't get overlooked... I see it already has a +2.20:59
johnsomI will take a loot20:59
xgerman_yeah, I like to get some things into Q-3 so we have them20:59
johnsomlook20:59
*** aojea has joined #openstack-lbaas21:00
rm_workyeah i will review my patches today21:00
johnsom#endmeeting21:00
*** openstack changes topic to "Welcome to LBaaS / Octavia - Queens priority review etherpad https://etherpad.openstack.org/p/Octavia-Queens-Priority-Review"21:00
openstackMeeting ended Wed Jan 17 21:00:08 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
jnieszthanks21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/octavia/2018/octavia.2018-01-17-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/octavia/2018/octavia.2018-01-17-20.00.txt21:00
johnsomSorry, out of time folks.21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/octavia/2018/octavia.2018-01-17-20.00.log.html21:00
johnsomThanks for joining21:00
rm_worki need to address johnsom's concern on the PKCS12 patch21:00
rm_workhadn't had time to deal with it this week21:00
rm_workerr, last week. but maybe today/tomorrow21:00
rm_workapplied for travel, we'll see.21:01
rm_workback after lunch21:01
*** longstaff has quit IRC21:01
johnsomOk, added those two issues to the agenda for next week.  Hopefully we will get some content on the etherpads21:03
*** aojea_ has joined #openstack-lbaas21:05
*** Alex_Staf has quit IRC21:06
*** aojea has quit IRC21:08
*** aojea has joined #openstack-lbaas21:09
*** aojea_ has quit IRC21:13
*** aojea_ has joined #openstack-lbaas21:15
*** aojea has quit IRC21:18
*** aojea has joined #openstack-lbaas21:21
*** aojea_ has quit IRC21:23
*** aojea_ has joined #openstack-lbaas21:25
*** aojea has quit IRC21:28
*** salmankhan has joined #openstack-lbaas21:28
*** aojea has joined #openstack-lbaas21:30
*** aojea_ has quit IRC21:33
*** salmankhan has quit IRC21:33
*** aojea_ has joined #openstack-lbaas21:35
*** aojea has quit IRC21:38
*** aojea has joined #openstack-lbaas21:41
*** threestrands_ has joined #openstack-lbaas21:44
*** aojea_ has quit IRC21:44
*** threestrands_ has quit IRC21:45
*** threestrands_ has joined #openstack-lbaas21:45
*** threestrands_ has quit IRC21:45
*** threestrands_ has joined #openstack-lbaas21:45
*** aojea_ has joined #openstack-lbaas21:45
*** aojea_ has quit IRC21:45
*** aojea has quit IRC21:48
*** fnaval has quit IRC21:50
rm_worksooo does anyone understand tempest's account credentials stuff?21:58
rm_workif I provide two credentials (one admin, one not) and tell it to use those, it OKs them for the first test, locks them, and then no other test can run using them >_<21:59
rm_workso the rest fail because they have no credentials to run21:59
*** rcernin has joined #openstack-lbaas22:02
openstackgerritMichael Johnson proposed openstack/octavia master: ACTIVE-ACTIVE: OVS diskimage-builder element  https://review.openstack.org/53384922:08
johnsomrm_work I am not, about the best I can help you with is this link: https://docs.openstack.org/tempest/latest/configuration.html#dynamic-credentials22:11
rm_worki think the issue is i specifically DON'T want that22:12
rm_workso i do see I can set that to false...22:12
rm_workbut i think i did already22:12
*** slaweq has quit IRC22:23
rm_workk figured it out22:54
rm_worki can either run serially, or i can write a bash loop that constantly clears out the tempest account locks :)22:54
johnsomThat doesn't seem to make sense.22:55
rm_workor mount a FS in the lock folder that always returns success on writes but returns nothing on reads :)22:55
rm_workapparently it's "core to tempest's design" that everything has to be run isolated22:55
rm_workbecause "tests aren't written assuming they are running alongside other things"22:55
rm_worknevermind that in the real world, people might be creating more than one server at a time22:56
rm_workIMO that's catering to people who are writing tests in a way that's a little naive22:56
rm_workbut whatever22:56
rm_workhard to go and say "ok, everyone rewrite ALL THE TESTS to not assume you'll be isolated"22:56
rm_worki'm sure there's some where the isolation really is important22:56
rm_workit's just that there's no way (or plans for a way) to tell tempest to ignore that feature22:57
« Tuesday, 2018-01-16 Index Thursday, 2018-01-18 »

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