Monday, 2015-09-28

*** denghui has quit IRC00:01
*** denghui has joined #openstack-lbaas00:01
*** bharathm has joined #openstack-lbaas00:12
*** rm_you has quit IRC00:15
*** vivek-ebay has joined #openstack-lbaas00:26
*** vivek-ebay has quit IRC01:09
*** Brian_shang has joined #openstack-lbaas01:18
*** Brian_shang has quit IRC01:26
*** Brian_shang has joined #openstack-lbaas01:27
*** diogogmt has quit IRC01:28
*** diogogmt has joined #openstack-lbaas01:29
*** Brian_shang has quit IRC01:31
*** Brian_shang has joined #openstack-lbaas01:32
*** bana_k has joined #openstack-lbaas01:35
*** bank_ has joined #openstack-lbaas01:36
*** telmich_ has joined #openstack-lbaas01:36
*** telmich has quit IRC01:38
*** bank_ has quit IRC01:40
*** bana_k has quit IRC01:40
*** bank_ has joined #openstack-lbaas01:45
*** bharathm has quit IRC01:49
*** bank__ has joined #openstack-lbaas01:49
*** bank_ has quit IRC01:51
*** vivek-ebay has joined #openstack-lbaas02:27
*** ajmiller has joined #openstack-lbaas02:30
*** ajmiller has quit IRC02:31
*** vivek-ebay has quit IRC03:06
*** Brian_shang has quit IRC03:07
*** Brian_shang has joined #openstack-lbaas03:08
*** bank__ has quit IRC03:13
*** diogogmt has quit IRC03:24
*** denghui has quit IRC03:40
*** denghui has joined #openstack-lbaas03:41
*** bank_ has joined #openstack-lbaas03:53
*** amotoki has joined #openstack-lbaas04:27
*** vjay10 has joined #openstack-lbaas04:37
*** bana_k has joined #openstack-lbaas04:37
*** vjay10 has quit IRC04:44
*** vjay10 has joined #openstack-lbaas04:47
*** vjay10 has quit IRC04:51
*** bana_k has quit IRC04:51
*** bana_k has joined #openstack-lbaas04:51
*** numans has joined #openstack-lbaas04:52
*** bank_ has quit IRC04:53
*** bank_ has joined #openstack-lbaas04:53
*** bana_k has quit IRC04:57
*** bank_ has quit IRC04:58
*** bank_ has joined #openstack-lbaas05:26
*** bana_k has joined #openstack-lbaas05:28
*** Brian_shang has quit IRC05:39
*** Brian_shang has joined #openstack-lbaas05:40
*** vjay10 has joined #openstack-lbaas05:44
*** bank_ has quit IRC05:45
*** bank_ has joined #openstack-lbaas05:49
*** sbalukoff has quit IRC05:55
*** bana_k has quit IRC05:58
*** bana_k has joined #openstack-lbaas05:58
*** sbalukoff has joined #openstack-lbaas06:08
*** bank_ has quit IRC06:33
*** vjay10 has quit IRC06:35
*** bana_k has quit IRC06:38
*** kiran-r has joined #openstack-lbaas06:55
*** itsuugo has joined #openstack-lbaas06:56
*** vjay10 has joined #openstack-lbaas06:58
itsuugohi, I'm lost in LbaaS documentation, if I want to have LBaaS with L7 extensions what do I need? octavia, lbaasv2?07:11
*** itsuugo has quit IRC07:16
*** itsuugo has joined #openstack-lbaas07:17
*** chlong has quit IRC07:17
*** vjay11 has joined #openstack-lbaas07:39
*** vjay10 has quit IRC07:39
*** vjay11 has quit IRC07:47
*** vjay11 has joined #openstack-lbaas07:57
*** kiran-r has quit IRC08:26
*** eezhova has quit IRC08:31
*** eezhova has joined #openstack-lbaas08:34
openstackgerritElena Ezhova proposed openstack/neutron-lbaas: [WIP][LBaaS v2] Improve API tests performance  https://review.openstack.org/22637008:53
*** kiran-r has joined #openstack-lbaas08:57
*** apuimedo has joined #openstack-lbaas09:14
Brian_shangitsuugo: No need octavia, just use lbaasv2 with HaproxyNSDriver.09:26
itsuugothxs09:27
*** sc68cal has quit IRC09:52
itsuugoBrian_shang: is lbaasv2 available in kilo? I can't find any doc to enable it :(09:54
*** amotoki has quit IRC09:55
*** sc68cal has joined #openstack-lbaas09:56
*** sc68cal has quit IRC09:56
*** sc68cal has joined #openstack-lbaas09:56
Brian_shangitsuugo: yes, you can read neutron-lbaas/devstack/plugin.sh to enable it.09:57
itsuugoI'm using ubuntu repos for openstack kilo, and seems that lbaas v2 is not working there10:20
itsuugoI have enabled service_provider=LOADBALANCERV2:Haproxy:neutron_lbaas.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default10:20
itsuugoand tried with neutron.conf:service_plugins = lbaasv2 neutron.conf:service_plugins = lbaas without success10:21
*** kiran-r has quit IRC10:22
*** sballe has joined #openstack-lbaas10:45
*** nmagnezi__ has joined #openstack-lbaas11:03
*** nmagnezi__ has quit IRC11:07
*** Brian_shang has quit IRC11:12
*** Brian_shang has joined #openstack-lbaas11:12
*** vjay11 has quit IRC11:16
*** chlong has joined #openstack-lbaas11:43
*** itsuugo has quit IRC11:47
*** itsuugo has joined #openstack-lbaas12:03
*** itsuugo has quit IRC12:51
*** numans has quit IRC13:25
*** vjay11 has joined #openstack-lbaas13:42
*** itsuugo has joined #openstack-lbaas13:59
*** itsuugo has quit IRC14:01
*** denghui has quit IRC14:34
*** vjay11 has quit IRC14:43
xgermanrm_work: https://review.openstack.org/#/c/228074/15:07
*** sbalukoff has quit IRC15:15
rm_workxgerman: looking15:17
xgermanthanks — it’s a spec Barbican/DNSaaS15:17
*** TrevorV has joined #openstack-lbaas15:19
rm_workyeah15:21
rm_workit looks fine other than the set of IFs on line 50-67 being super confusing to me15:21
rm_worki am not sure what most of those are really saying15:21
rm_workdo you understand?15:21
xgermanI think they sort of make sense — since it seems DNSaS handles domains and subdomains15:23
rm_workso the first one:15:24
xgermanso of if you get a cert for *.rackspace.com it should be the same for r_work.rackspace.com15:24
rm_workIf a subdomain is created and a wild card certificate is associated15:24
rm_workwith the parent, the subdomain will have no wild card cert set.15:24
rm_workI have mydomain.com15:24
rm_workI set a wildcard for it15:24
rm_workI create yours.mydomain.com15:24
xgermanok, I think they allow domains be managed for more than one tenant15:25
johnsomI'm trying to think about the relationship with anchor here.15:25
rm_workyours.mydomain.com will NOT have a wildcard configured (meaning, the wildcard for the top-level is explicitly not shared) ?15:25
xgermanyep, they are multi tenant. So the admin might own *.ebay.com and each tenant can have a sundomain15:25
rm_workand the wildcard for the tld is explicitly not shared lower15:26
xgermanyep15:26
rm_workso someone.yours.mydomain.com would not work15:26
rm_workor, it would, but it wouldn't have a cert15:26
xgermanyeah, which seems limiting15:26
rm_workthough err15:26
johnsomrm_work while you are around, this is a simple one to get our coverage stuff going again: https://review.openstack.org/#/c/225548/15:27
rm_workif I have a wildcard cert for mydomain.com15:27
xgermanjohnsom you got a -115:27
rm_workit DOES cover *.mydomain.com15:27
rm_workwhich includes yours.mydomain.com15:27
rm_workbecause that's the point of having a wildcard cert15:27
johnsomrm_work ah, crumb15:27
rm_workbut this is saying that it specifically wouldn't share it15:27
rm_workright?15:27
xgermanyep, that’s their multi-tenant thing15:28
rm_workwhich ... what is the point of having a wildcard cert at all if it isn't shared with subdomains15:28
rm_workjohnsom: yeah i THINK we need to get that !=4.0 in global15:29
rm_workbecause otherwise our reqs could cause problems in a shared env15:29
xgerman+115:29
johnsomYeah, probably.15:29
rm_workor, figure out why 4.0 breaks us15:29
johnsomI will work on that.  The 4.0 release is clearly broken15:29
rm_workif it's a buggy release, then yeah we need !=4.0 in global and they need to release an update15:30
johnsomNed the developer doesn't seem to have an idea of what is going on.15:30
rm_work>_>15:30
johnsomIt seems to me this cert via dns spec is a bit dangerous.  Usually you don't want people to wildly create signed subdomains, etc.  There should be some diligence with issuing signed certs.15:38
rm_workwell, there is a lot of info required for this to work15:39
rm_workA) it's not at all a synchronous process with Barbican15:39
johnsomI'm just looking at the section about multiple tenants15:39
rm_workB) in order to get a cert, you need to provide quite a bit of specific info15:40
xgermanyeah, I think they didn’t understand how Barbican works/or want to use their own CA15:41
* redrobot pokes head in15:41
redrobotxgerman what questions do you have?15:42
rm_workredrobot: we're looking at https://review.openstack.org/#/c/228074/115:42
xgermanyeah, my mugs over there brought it to my attention15:42
johnsomLine 60 down is making me scratch my head15:42
xgermanmugsy15:42
rm_workerr, accidentally +1d instead of -1d lol15:42
rm_workjohnsom: i think 60+ is the only part that makes SENSE to me15:43
rm_worksince the "CA" is just a thing global to all of barbican15:43
rm_workso if you are using CA ID 315:43
rm_workand the domain transfers to another tenant15:43
rm_workCA ID 3 is the same CA15:44
rm_workwhy that matters, I don't quite know15:44
*** Kiall has joined #openstack-lbaas15:44
rm_workbut it'd still have the same CA available in Barbican to create a new cert15:44
xgermanor renew the cert15:44
*** mugsie has joined #openstack-lbaas15:44
rm_workyes15:44
openstackgerritMerged openstack/neutron-lbaas: Kill HEADS file  https://review.openstack.org/22746615:47
*** mlavalle has joined #openstack-lbaas16:01
*** vjay11 has joined #openstack-lbaas16:33
openstackgerritPhillip Toohill proposed openstack/neutron-lbaas: Allow updating TLS refs  https://review.openstack.org/22065416:33
*** alejandrito has joined #openstack-lbaas16:39
*** vivek-ebay has joined #openstack-lbaas16:43
*** Brian_shang has quit IRC16:47
*** Brian_shang has joined #openstack-lbaas16:48
openstackgerritPhillip Toohill proposed openstack/octavia: Updates for containers functionality  https://review.openstack.org/19995416:48
*** vivek-ebay has quit IRC16:51
openstackgerritMerged openstack/octavia: Remove quotes from subshell call in bash script  https://review.openstack.org/22671616:52
*** vivek-ebay has joined #openstack-lbaas17:01
*** TrevorV has quit IRC17:05
*** TrevorV has joined #openstack-lbaas17:06
*** minwang2 has joined #openstack-lbaas17:11
*** bana_k has joined #openstack-lbaas17:13
*** bank_ has joined #openstack-lbaas17:14
*** apuimedo has quit IRC17:21
openstackgerritPhillip Toohill proposed openstack/octavia: Updates for containers functionality  https://review.openstack.org/19995417:22
*** apuimedo has joined #openstack-lbaas17:23
*** vjay11 has quit IRC17:23
*** vivek-ebay has quit IRC17:31
*** vivek-ebay has joined #openstack-lbaas17:32
*** sbalukoff has joined #openstack-lbaas17:34
*** pckizer has joined #openstack-lbaas17:37
*** Aish has joined #openstack-lbaas17:46
*** madhu_ak has joined #openstack-lbaas18:13
bana_khow do i specify the session persistence while creating the pool ?18:20
*** mestery_afk is now known as mestery18:22
pc-potholebana_k: Is it not allowing you to specifiy session persistence in the request body?18:25
bana_knope its letting me allow18:39
bana_kbut I am not able to figure it out, but I think I got it now18:39
johnsomFYI, the global requirements change to exclude coverage 4.0: https://review.openstack.org/#/c/228581/118:49
pc-potholejohnsom: Question: In the controller worker around line 50, the ComputeBuildException is caught and rethrown. I think I understand why this is done, but since this is also done in my review and others have questions regarding it im asking here in hopes you could clarify for us.18:53
*** fnaval has quit IRC18:55
*** minwang2 has quit IRC18:56
*** barclaac|2 has joined #openstack-lbaas19:02
bana_kIn octavia.conf I see we have a flavor as 10, is it nova flavor?19:02
*** bank_ has quit IRC19:03
pc-potholebana_k: the default that's commented out in the conf is empty for me.19:04
pc-potholeThe retries have 1019:04
*** barclaac has quit IRC19:05
bana_koh I think I might have the old code. It shows me as 1019:05
pc-potholeoh in the devstack settings19:05
pc-potholeI dont have devstack running atm, but you could query to see the flavor id's and see if they match.19:06
bana_kyes I see that in octaiva conf we have flavor as 10 n nova flavor-list does not have that19:07
pc-potholeit should be the nova flavor. the devstack plugin is setting this. You can see the default in the settings file.19:09
*** barclaac|2 has quit IRC19:09
bana_kok, ll see19:09
bana_kthanks19:09
pc-potholeill stack see what i get19:10
*** barclaac|2 has joined #openstack-lbaas19:10
bana_kthat will be great :). thanks19:10
*** itsuugo has joined #openstack-lbaas19:11
*** Aish has quit IRC19:20
*** fnaval has joined #openstack-lbaas19:23
bloganbana_k: do a flavor-list --all19:25
bloganbana_k: its created as not public19:26
pc-potholeyea, bana_k I have m1.amphora as the flavor with ID of 10.19:36
rm_workit's created as part of the devstack spinup19:38
rm_workhttps://github.com/openstack/octavia/blob/master/devstack/plugin.sh#L14619:38
rm_workhttps://github.com/openstack/octavia/blob/master/devstack/settings#L3219:39
rm_workbana_k: ^^19:39
*** woodster_ has joined #openstack-lbaas19:42
johnsombana_k I added flavor 10 to the devstack plugin.sh to be able to cut the amount of memory down to 1GB of RAM and 2GB of disk19:48
johnsompc-pothole Can you give me a file:line#?  In controller_worker.py:50 is the init class with member_repo19:50
pc-potholejohnsom: i was looking at the wrong things. No longer an issue, sorry for that.19:50
bana_koh ok. will check out johnsom, thanks19:51
johnsomOk19:51
bana_kthis is the wip https://review.openstack.org/#/c/228598/19:51
bana_kfor heat hooks19:51
bana_kplease review19:52
bana_kIt still needs a lot of work n input19:52
johnsomCool19:52
openstackgerritPhillip Toohill proposed openstack/octavia: Updates for containers functionality  https://review.openstack.org/19995419:52
*** minwang2 has joined #openstack-lbaas19:52
*** Aish has joined #openstack-lbaas19:56
*** vivek-ebay has quit IRC20:05
openstackgerritPhillip Toohill proposed openstack/octavia: Adding new network driver for containers  https://review.openstack.org/19785820:05
openstackgerritPhillip Toohill proposed openstack/octavia: Updates for containers functionality  https://review.openstack.org/19995420:07
openstackgerritGerman Eichberger proposed openstack/octavia: Explicitly kills a process listening on the amphora port  https://review.openstack.org/22791220:22
*** mlavalle has quit IRC20:27
*** barclaac|2 has quit IRC20:38
*** barclaac|2 has joined #openstack-lbaas20:41
openstackgerritMichael Johnson proposed openstack/octavia: Fix a typo in the .coveragerc file  https://review.openstack.org/22554820:41
*** vivek-ebay has joined #openstack-lbaas20:49
*** mlavalle has joined #openstack-lbaas20:54
openstackgerritmin wang proposed openstack/octavia: Add cert tracking and rotating in Housekeeping  https://review.openstack.org/21535920:55
*** Aish has quit IRC21:15
*** Aish has joined #openstack-lbaas21:17
*** itsuugo has quit IRC21:29
*** TrevorV has quit IRC21:36
*** vivek-ebay has quit IRC21:51
bloganxgerman, johnsom, rm_work, dougwig: we are probably going to have to skip some tests in the api-lb job22:01
blogantemporarily22:01
xgermank22:01
johnsomWhy is that?22:01
dougwigi would say let's upgrade that probably to definitely.  or split the jobs further.22:01
openstackgerritmin wang proposed openstack/octavia: Add cert tracking and rotating in Housekeeping  https://review.openstack.org/21535922:02
xgermanwell. let’s see if we can get the container stuff going22:02
* johnsom looks puzzled... We are running faster than 3-4 other jobs, what changed?22:02
dougwigthe lb job is going >120 minutes.22:03
dougwigno clue22:03
rm_workerr22:04
rm_workyes22:04
johnsomI saw one over the weekend, but that was before our tests even ran22:04
rm_workerr22:04
rm_workhmm22:04
rm_work120 is the timeout?22:04
johnsom125 actually.22:04
rm_workthe MINIMAL is still fine at <60m right?22:04
johnsomWhich one are you looking at?22:04
rm_workload_balancers was the long one since the beginning22:04
rm_workbut i thought it was going <12022:04
*** vivek-ebay has joined #openstack-lbaas22:05
johnsomYeah, that was the long one22:05
xgermanso, why can’t we run our tests as long as we want?22:05
bloganhttp://logs.openstack.org/87/226587/2/check/gate-neutron-lbaasv2-dsvm-loadbalancer/bb56340/console.html22:07
bloganxgerman: because if they allow all the integration tests to run as long as wanted, and then they have to retrigger when something ahead of them fails, it'll get backed up to no end22:07
bloganbc the gate jobs will have to restart again if there's a failure ahead of them22:07
johnsomYeah, those are really slow hosts22:08
*** alejandrito has quit IRC22:09
johnsomThat is really strange, they are failing before the timeout.22:11
bloganjohnsom: new mechansim got merged on friday that causes that22:11
johnsomThis one ran until 2:01:25 https://review.openstack.org/#/c/227363/22:11
xgermanah, so mechanism need to fix their act...22:12
xgermanour work is done — kick them out...22:12
xgermankidding...22:12
bloganjohnsom: so the timeout is recalculated a bit now, the timeout doesn't include the devstack build so there is definitely some time changes22:12
johnsomThe variability in the hosts is what worries me, this one finished in 1:30:49 https://review.openstack.org/#/c/227466/22:12
johnsomblogan patch link?22:13
johnsomI'm lost on that one too, as without the devstack setup time you patch test ran 1:21 ish22:14
bloganhttps://review.openstack.org/#/c/227476/22:14
*** vivek-ebay has quit IRC22:17
johnsomI like that there is a chance we could get a full log set on timeout, but it is not clear how much time they took away from the test itself.22:18
johnsomtimeout -s 9 81m bash22:21
johnsomSo, tests now have to run inside 81 minutes22:22
johnsomdepending on how long the host takes for devstack setup22:22
johnsomUgh, ugly22:22
bloganyeah i know22:22
johnsomI would have blocked this for nested virt if it was clear the impact.22:23
johnsom(not that my vote counts)22:23
bloganwell do any of us pay attention to all reviews in all of these projects?22:24
xgermanwell, don’t they have to pass jenkins before?22:25
xgermanso if we time out and therefore vote no how do they get in?22:25
rm_workgate changes don't test against projects22:25
xgermanah, ok22:26
rm_workwhich is why normally you make gate stuff experimental first, then test, then flip to normal/voting22:26
xgermanyeah, that’s how we do it22:26
johnsomSo, on a good host we take 1:08:17 and on a bad host we took 1:15:0322:28
johnsomI guess we should aim to take about 15 minutes out, which is roughly three tests.22:29
xgermanwell, then the next change comes… I think we have a systemic problem22:30
johnsomYep22:31
johnsomEasy solution is to split the load balancer tests in half22:32
xgermanok, we should do that22:33
xgermanbut then something happened and we need to split in 4ths22:33
xgermandougwig we need some process change so others can’t break our tests that easy22:33
bloganwhat if we changed all the api tests to use the noop drivers, but then we also ran the minimal tests job we have for neutron using the VM drivers?22:35
johnsomWorst part hear is a change in devstack will cut our test time22:36
johnsomhear->here22:38
johnsomugh.  This all makes my head hurt.22:38
bloganwell do you think the noop drivers for the api tests and only use the real drivers for a minimal test suite would be fine?22:38
johnsomnoop to me seems like we are asking for trouble.22:38
*** vivek-ebay has joined #openstack-lbaas22:38
xgerman+122:39
xgermansome of those api tests look for real stuff22:39
xgermanso we would need to fix that22:39
johnsomBut this comes back to my comment last week about re-evaluating what we are testing and where22:39
bloganwell we are in trouble right now, adn if we have to keep skipping tests we'll be getting in more trouble22:39
johnsomAgreed.22:39
bloganthe way i see it is, most of these tests are testing api validation, which is just updates to the db22:40
johnsomBTW, noop is not going to be a quick fix as I'm pretty sure it will require a bunch of fixes22:40
bloganactually22:40
xgermanwell, they also test the driver22:40
johnsomShould the?22:40
bloganjohnsom: im sure too but i think if i focus on it for a night i can get it working but that might be all sunshine and rainbows thinking22:40
johnsomthey?22:40
bloganjohnsom: actually this brings up another improvement we can make, we'eve talkeda bout it ebfore22:41
bloganupdates to name and descriptions houldn't go do the drivers22:41
bloganbut that wouldn't help these test runs out much22:41
johnsomSo, that is the question right?  Should API tests only test the API layer, in which case they should not be going to the drivers22:41
bloganbc its the creation that is causing the problem22:41
xgermanso we feel that most stuff does;t go the driver and we can easily separate that22:41
xgermanand api tests are mostly not exposing driver problems...22:42
bloganwell if those tests only cared about the API then they woudln't care if something went ACTIVe22:42
bloganjust that it got accepted22:42
johnsomI would then argue that API tests are not appropriate for the minimal gate, as nothing would test the plugging22:42
bloganand returned correctly22:42
xgermanjohnsom +!22:43
xgerman+122:43
blogani guess at this point its choosing the lesser of 5 evils22:43
johnsomSo, we have the following test categories today: minimal (neutron gate), API, scenario, driver ???22:44
xgermanwell, if we need to choose between evils something is fundamentally wrong --22:44
johnsomdriver CI?22:44
bloganintegrated22:44
blogani guess22:44
blogandriver-integrated22:44
xgermanbut I gotta run an errand so...22:44
bloganwhatever i knwo what you mean :)22:44
bloganxgerman: way to leave us in a dire situation!22:45
xgermansorry22:45
bloganxgerman: im just kidding with ya22:45
bloganxgerman: go do your more important stuff22:45
johnsomWe just assign the work to him, that's all22:45
bloganeasy!22:45
johnsomI would propose:22:46
johnsomminimal - does an end-to-end happy path scenario test22:46
johnsomAPI - checks for API completeness and functionality.  I would argue this could be a dummy driver.22:47
johnsomScenario - Extensive end-to-end tests.  How do we pull this off without nested virt or containers?  If those would even get us down in time.  Maybe many gates.22:47
bloganwell, we could do the first 2 right? fix the logging noop22:48
bloganthen in the last one we just enable what we can for now and improve as time goes on, especially if we get containers or nested virt in22:49
johnsomDoes that give us enough coverage?22:49
bloganthough clarkb said they did a very unscientific test with nested virt and they didnt see any improvements, but i didnt argue with him bc i dont see how it owuldn't boot faster22:49
johnsomWe have minimal now, I assume it still functions22:49
bloganjohnsom: i think it gives us better coverage than right now where we're skipping a lot of tests22:49
johnsomI just worry about the dummy driver if we don't have good scenario tests.22:51
bloganwell it'll at least be testing api, now obviously it won't test if a particular configuration breaks a VM or container build or haproxy update22:52
johnsomSo, flip the coin for a minute.  What is the harm in creating more gate jobs?  Neutron has a ton22:52
bloganbut if haproxy fails now, the tests still won't catch that22:52
johnsomYeah, I noticed that22:53
bloganthe tests now catch if neutron or nova fail really, the scenario tests will test haproxy updates happen correctly22:53
bloganmore gate jobs? it feels dirty too22:53
bloganthe way we're splitting tests seems a bit hacky, and doesn't seem like something anyone else is doing22:54
bloganwe're splitting to get true parallelism basically22:55
johnsomBTW, if you have vmware workstation available, you can test the difference with and without nested virtualization enabled really easily.  It's a check box for the VM.22:55
bloganbut if we actually tried to do parallel execution of these tests at once i'm pretty sure 1) the tests are written for that and 2) memory issues22:55
blogani dont have that available22:55
*** mlavalle has quit IRC22:56
johnsomYeah, the only parallel option we have is multiple gates.  We can't push the current instances much farther22:57
johnsomI'm just saying, neutron has 19 test gates22:57
blogani can work on the noop drivers tongiht just to see how much work it'd be to get those working22:57
bloganor we can go for the immediate fix right now and skip tests22:58
bloganand then try to re-structure the jobs22:58
johnsomIt's up to you since you're doing the work.  I don't think we have anything so critical it has to be merged in the next couple of days.22:59
bloganto me, i think doing the minimal, API with noop drivers, and then real tests that we slowly get more coverage on is the best path forward22:59
johnsomby real tests, meaning setup more gates?22:59
bloganif thats what we have to do to get decent coverage with VM drivers23:00
bloganbut if we do that just to run all the tests i dont see the point in having an API job run that runs those same tests with just noop drivers23:01
bloganto me, scenario tests that just test CUD oeprations (READ will happen organically in thsoe tests), will be fine23:02
bloganso 1 create update and delete method each for each resource (lb, listener, etc)23:02
blogansorry test not method23:02
bloganas of now creating an lb with session persistence or a certain lb algorithm isn't going to fail the test even if sess pers or the algorithm doesn't get updated in haproxy23:03
johnsomYeah, I am warming to this.  With scenario tests, I would hope we can pack a lot more in without so many create/delete lbs23:03
bloganthe current scenario tests that do 4 tests run in under an hour23:04
blogansorry 3 tests23:05
johnsomHa23:05
bloganbut they are doing much more than the api tests23:05
bloganactually spinning up VMs to be web servers23:05
bloganto be load balanced23:06
*** fnaval has quit IRC23:06
johnsomOk.  Give it a go.  I can probably help switching the gate around for driver/no-driver if you would like after the noop is working23:06
blogansure, ill get it working and let ya know23:06
bloganif we go with the noop driver on these tests we can tell thsoe jobs not to even spin up nova or neutron correct?23:07
bloganwell we'll need neutron23:07
bloganbut not nova23:08
blogani can test that out too23:08
bloganlol23:08
bloganalright im headed hom23:08
blogani will work on this tonight23:08
johnsomYeah, API doesn't need nova/neutron23:08
johnsomJust minimal23:08
bloganwell we'll need neutron to load neutron-lbaas23:08
bloganoctavia won't need it23:09
johnsomYeah, sorry, just don't need to plug/unplug, etc.23:09
johnsomThat is what I meant23:09
johnsomdougwig must just be hiding...23:11
johnsomHe dropped out of the conversation early23:11
bloganhe just likes to get the conversation started and then watch his puppets dance23:11
johnsomPulls the pin and runs eh?23:11
bloganso eh doesn't have to do anything truly technical23:11
bloganlol thats a better analogy23:12
bloganalright bbl23:13
johnsomGood luck!23:13
*** fnaval has joined #openstack-lbaas23:15
*** vivek-ebay has quit IRC23:26
*** vivek-eb_ has joined #openstack-lbaas23:26
*** bharathm has joined #openstack-lbaas23:26
*** Aish has quit IRC23:39
openstackgerritMichael Johnson proposed openstack/neutron-lbaas: Update the devstack readme.md for Octavia as ref  https://review.openstack.org/22866823:56
xgerman^^ johnsom can you tag that to geo into RC223:58
xgermandougwig wonder if you could help23:58
johnsomYeah, I wondered about that23:58
xgerman:-)23:58

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