Thursday, 2013-12-12

*** pcm_ has quit IRC00:00
*** mlavalle has quit IRC00:01
anteayagood night00:02
*** carl_baldwin has joined #openstack-neutron00:06
*** carl_baldwin has quit IRC00:10
*** banix has quit IRC00:13
openstackgerritA change was merged to openstack/neutron: move rpc_setup to the last step of __init__  https://review.openstack.org/6080500:25
*** x86brandon has joined #openstack-neutron00:31
openstackgerritA change was merged to openstack/neutron: Add X-Tenant-ID to metadata request  https://review.openstack.org/6143900:33
*** dims has joined #openstack-neutron00:43
*** yamahata_ has joined #openstack-neutron00:45
*** yamahata_ has quit IRC00:59
*** yamahata_ has joined #openstack-neutron01:00
*** banix has joined #openstack-neutron01:03
*** SumitNaiksatam has quit IRC01:05
*** salv-orlando_ has joined #openstack-neutron01:24
*** salv-orlando has quit IRC01:27
*** salv-orlando has joined #openstack-neutron01:27
*** salv-orlando_ has quit IRC01:28
*** ljjjustin has joined #openstack-neutron01:30
*** salv-orlando_ has joined #openstack-neutron01:33
*** salv-orlando_ has quit IRC01:34
*** salv-orlando__ has joined #openstack-neutron01:34
*** salv-orlando has quit IRC01:36
*** salv-orlando__ is now known as salv-orlando01:36
*** SumitNaiksatam has joined #openstack-neutron01:38
*** Jianyong has joined #openstack-neutron01:46
anteayamtreinish: nati_ueno posted a reply to your comment on https://review.openstack.org/#/c/61234/01:48
*** csd has quit IRC01:48
*** csd has joined #openstack-neutron01:50
*** gongysh has joined #openstack-neutron01:55
anteayamtreinish: thanks01:56
anteayagoing offline now, see y'all later02:03
*** csd has quit IRC02:05
*** vkozhukalov has joined #openstack-neutron02:38
*** Gu_______ has joined #openstack-neutron02:42
*** Gu_______ has quit IRC02:47
*** hxgqh1987 has joined #openstack-neutron02:48
*** suresh12 has quit IRC02:52
*** suresh12 has joined #openstack-neutron02:53
*** julim has quit IRC02:57
*** hxgqh1987 has quit IRC02:59
gongyshsumitnaiksatam: ping03:01
SumitNaiksatamgongysh: hi03:02
gongyshsumitnaiksatam: https://review.openstack.org/#/c/61341/ can u help to review it, I got +2 already.03:02
*** hxgqh1987 has joined #openstack-neutron03:02
SumitNaiksatamyeah sure03:03
SumitNaiksatami did see it03:03
SumitNaiksatami was not completely sure what tun_br.defer_apply_on does :-)03:04
*** SushilKM has joined #openstack-neutron03:06
gongyshsumitnaiksatam: it defers the ovs-ofctl calls,  store add-flow into a list and defer_apply_off will call add-flows in one shot.03:06
SumitNaiksatamyeah03:07
*** suresh12 has quit IRC03:10
*** rpodolyaka has quit IRC03:12
SumitNaiksatamgongysh: thinking about the test03:13
*** suresh12 has joined #openstack-neutron03:13
*** rpodolyaka has joined #openstack-neutron03:13
SumitNaiksatamgongysh: does it really test that all the flows are added to the list?03:13
SumitNaiksatamgongysh: i guess in the test we are just checking if we get the calls in the order03:15
gongysh<SumitNaiksatam>: a good question, I will see if I can improve it03:23
SumitNaiksatamgongysh: thats fine, i responded to the review03:23
*** alagalah has joined #openstack-neutron03:24
*** suresh12 has quit IRC03:37
gongyshnati_ueno: ping03:43
*** marun has joined #openstack-neutron04:06
openstackgerritA change was merged to openstack/neutron: Updated from global requirements  https://review.openstack.org/6097404:14
*** SushilKM has quit IRC04:17
*** hxgqh1987 has quit IRC04:22
*** banix has quit IRC04:27
*** chandankumar has joined #openstack-neutron04:36
*** suresh12 has joined #openstack-neutron04:56
*** yfried has quit IRC04:58
*** nati_ueno has quit IRC05:03
*** suresh12 has quit IRC05:08
*** yongli_away is now known as yongli05:14
*** garyk has quit IRC05:14
*** yfried has joined #openstack-neutron05:25
*** angryjesters has joined #openstack-neutron05:33
*** enikanorov_ has quit IRC05:37
*** enikanorov has joined #openstack-neutron05:37
*** AndreyGrebenniko has quit IRC05:41
*** AndreyGrebenniko has joined #openstack-neutron05:41
*** otherwiseguy has quit IRC05:50
*** gdubreui has quit IRC05:51
*** hxgqh1987 has joined #openstack-neutron05:53
*** suresh12 has joined #openstack-neutron05:54
*** garyk has joined #openstack-neutron05:56
*** alagalah has left #openstack-neutron06:03
*** suresh12 has quit IRC06:15
openstackgerritRoman Podoliaka proposed a change to openstack/neutron: Fix the migration adding a UC to agents table  https://review.openstack.org/6166306:28
*** suresh12 has joined #openstack-neutron06:32
openstackgerritJenkins proposed a change to openstack/neutron: Imported Translations from Transifex  https://review.openstack.org/6132506:34
*** SushilKM has joined #openstack-neutron06:38
gongyshenikanorov: ping06:39
*** alex_klimov has joined #openstack-neutron06:44
*** lifeless has quit IRC06:48
*** vkozhukalov has quit IRC06:51
*** jlibosva has joined #openstack-neutron06:52
*** yongli has quit IRC07:06
gongyshrkukura: hi07:08
openstackgerritgongysh proposed a change to openstack/neutron: synchronize ovs agent's rpc handlers and main thread  https://review.openstack.org/6166707:12
*** gongysh_ has joined #openstack-neutron07:13
*** jianingy_afk is now known as jianingy07:13
*** lifeless has joined #openstack-neutron07:15
*** gongysh has quit IRC07:16
*** gongysh_ has quit IRC07:16
*** gongysh has joined #openstack-neutron07:16
gongyshrkukura: ping07:16
gongyshsalv-orlando: ping07:27
*** Mierdin has joined #openstack-neutron07:31
*** amritanshu_RnD has joined #openstack-neutron07:45
*** Mierdin has left #openstack-neutron07:51
*** nati_ueno has joined #openstack-neutron07:52
*** ljjjustin has quit IRC08:02
*** Jianyong has quit IRC08:02
*** gongysh has quit IRC08:03
*** gongysh has joined #openstack-neutron08:05
*** Jianyong has joined #openstack-neutron08:06
*** safchain has joined #openstack-neutron08:08
*** mengxd has joined #openstack-neutron08:10
openstackgerritMaru Newby proposed a change to openstack/neutron: Send DHCP notifications regardless of agent status  https://review.openstack.org/6116808:10
openstackgerritA change was merged to openstack/python-neutronclient: Pin Sphinx to <1.2 in test-requirements  https://review.openstack.org/6155308:13
*** enikanorov_ has joined #openstack-neutron08:18
*** suresh12 has quit IRC08:21
*** yongli has joined #openstack-neutron08:22
*** vkozhukalov has joined #openstack-neutron08:28
openstackgerritOleg Bondarev proposed a change to openstack/neutron: LBaaS: fix handling pending create/update members and health monitors  https://review.openstack.org/6167308:29
*** fandikurnia01 has joined #openstack-neutron08:45
fandikurnia01Hi all08:45
openstackgerritgongysh proposed a change to openstack/neutron: add ml2 plugin into agent model migration scripts  https://review.openstack.org/6167708:46
*** ygbo_ has joined #openstack-neutron08:46
*** ygbo has joined #openstack-neutron08:46
*** ygbo has quit IRC08:46
fandikurnia01does openstack can be using multiple vlan /trunks for floating ip with many subnet08:46
fandikurnia01?08:46
*** mengxd has quit IRC08:48
*** afazekas has joined #openstack-neutron08:51
*** fouxm has joined #openstack-neutron08:56
*** jistr has joined #openstack-neutron09:03
*** jpich has joined #openstack-neutron09:05
*** salv-orlando has quit IRC09:05
*** ekarlso has quit IRC09:17
*** ekarlso has joined #openstack-neutron09:17
enikanorov_gongysh: Hi. could you please take a look at jenkins build failure for neutronclient? https://review.openstack.org/#/c/61561/09:17
enikanorov_gate-python-neutronclient-docs fails for some reason, while locally it passes09:18
enikanorov_i can't find out what could be wrong with my patch09:18
gongyshenikanorov_ , how about just recheck or wait for some time, for example tomorrow :) the ci is getting wrong now and then.09:22
*** jorisroovers has joined #openstack-neutron09:23
gongyshenikanorov_: would you like to approve https://review.openstack.org/#/c/61341/ which has got 2 +2 already.09:23
enikanorov_gongysh: i'm not a core :)09:24
enikanorov_i can review and put +1 though09:24
gongyshenikanorov_ thanks09:24
gongyshnati_ueno: ping09:25
openstackgerritRoman Podoliaka proposed a change to openstack/neutron: Fix the migration adding a UC to agents table  https://review.openstack.org/6166309:26
rpodolyakagongysh: hey! Looks like the mistake in the migration script I made uncovered issues with migrations not applying for ML2 plugin. I rebased my patch on yours, should be fixed now...09:27
*** jorisroovers has quit IRC09:27
openstackgerritSylvain Afchain proposed a change to openstack/neutron: Fix Metering doesn't respect the l3 agent binding  https://review.openstack.org/6001609:28
fandikurnia01hi there,09:28
gongyshrpodolyaka:  '*' means all plugins09:29
gongyshrpodolyaka: so do u need https://review.openstack.org/61663 patch?09:29
rpodolyakagongysh: yes09:29
rpodolyakagongysh: otherwise bigswitch/plumgrid/etc are broken09:30
rpodolyakagongysh: they don't create agents table09:30
rpodolyakagongysh:  on * ... yeah, I know... should have been more attentive :(09:30
gongyshrpodolyaka: got it. thanks09:31
rpodolyakagongysh: but the question is... how neutron works in devstack/tripleo now with ML2 plugin? without your patch agents migrations shoudn't have been applied, right?09:31
*** suresh12 has joined #openstack-neutron09:31
gongyshrpodolyaka: can you reproduce that bug I filed? I am also wondering how CI passed with your constraint patch.09:34
rpodolyakagongysh:  on passing CI - I thought we were testing only OVS/ML2 pair for which agents migrations must have been enabled09:34
rpodolyakagongysh: so my migration should have applied to those just fine09:35
rpodolyakagongysh: but it's broken for the plugins which are not using agents09:35
* rpodolyaka running devstack09:35
*** marun has quit IRC09:36
*** suresh12 has quit IRC09:36
gongyshrpodolyaka: I got the bug for OVS/ML2 in devstack.09:36
*** SushilKM has quit IRC09:37
*** marun has joined #openstack-neutron09:37
rpodolyakagongysh:  then I'm totally confused :( if we are running migrations scripts in devstack in order to install neutron, we must have spotted the bug when running CI tests09:37
gongyshrpodolyaka: yes, that is the problem. So I am asking if you can reproduce it in by running devstack.09:39
rpodolyakagongysh: running stack.sh now09:40
*** SushilKM has joined #openstack-neutron09:43
rpodolyakagongysh: http://paste.openstack.org/show/54870/09:43
rpodolyakagongysh: so no errors09:43
rpodolyakagongysh: this is my patch NOT rebased on master09:44
rpodolyakagongysh: let me try master now09:44
gongyshrpodolyaka: yes, please run on master09:45
*** jp_at_hp has joined #openstack-neutron09:55
rpodolyakagongysh: looks like enikanorov found the problem. https://github.com/openstack/neutron/blob/master/neutron/db/migration/alembic_migrations/versions/511471cc46b_agent_ext_model_supp.py#L3809:57
rpodolyakagongysh: agents table is created for LBaaS service plugin09:58
rpodolyakagongysh: I have LBaaS enabled in localrc, and AFAIK it's true for jenkins nodes too09:58
gongyshrpodolyaka:  any way, the ml2 plugin is later introduced than agent model, for ml2, we need it fixed.10:02
gongyshrpodolyaka: yes, my localrc has no lbaas enabled.10:02
rpodolyakagongysh: sure10:03
*** chandankumar_ has joined #openstack-neutron10:05
*** zhhuabj has quit IRC10:05
*** chandankumar has quit IRC10:08
*** gongysh has quit IRC10:10
*** AlexF has joined #openstack-neutron10:14
openstackgerritIsaku Yamahata proposed a change to openstack/neutron: ml2: gre, vxlan type driver can leak segment_id  https://review.openstack.org/6169410:22
*** AlexF has quit IRC10:28
*** salv-orlando has joined #openstack-neutron10:34
*** zhhuabj has joined #openstack-neutron10:35
*** fandikurnia01 has quit IRC10:41
*** salv-orlando has quit IRC10:42
*** bashok has joined #openstack-neutron10:43
*** heyongli has joined #openstack-neutron10:46
*** Jianyong has left #openstack-neutron10:51
openstackgerritOleg Bondarev proposed a change to openstack/neutron: LBaaS: fix handling pending create/update members and health monitors  https://review.openstack.org/6167310:55
*** hxgqh1987 has quit IRC10:55
*** yamahata_ has quit IRC10:58
openstackgerritOleg Bondarev proposed a change to openstack/neutron: LBaaS: check for associations before deleting health monitor  https://review.openstack.org/5382111:01
*** djoreilly has joined #openstack-neutron11:09
*** pcm_ has joined #openstack-neutron11:31
*** fouxm has quit IRC11:33
*** rossella_s has joined #openstack-neutron11:34
*** pcm_ has quit IRC11:36
*** pcm_ has joined #openstack-neutron11:37
*** salv-orlando has joined #openstack-neutron11:43
*** salv-orlando has quit IRC11:43
*** rkukura has quit IRC11:56
*** hxgqh1987 has joined #openstack-neutron11:59
*** gdubreui has joined #openstack-neutron12:00
*** gdubreui has quit IRC12:07
*** enikanorov has quit IRC12:24
*** enikanorov has joined #openstack-neutron12:24
*** hxgqh1987 has quit IRC12:26
*** hxgqh1987 has joined #openstack-neutron12:29
*** dims has quit IRC12:41
*** dims has joined #openstack-neutron12:41
openstackgerritAvishay Balderman proposed a change to openstack/neutron: LBaaS L7 model (WIP)  https://review.openstack.org/6172112:45
*** yamahata_ has joined #openstack-neutron12:55
*** kruskakli has joined #openstack-neutron12:59
*** fouxm has joined #openstack-neutron13:02
*** yamahata_ has quit IRC13:02
*** yamahata_ has joined #openstack-neutron13:04
*** yamahata_ has quit IRC13:09
*** dims has quit IRC13:17
*** amuller has joined #openstack-neutron13:17
*** Abhishek_ has joined #openstack-neutron13:17
*** dims has joined #openstack-neutron13:19
*** yamahata_ has joined #openstack-neutron13:24
*** enikanorov__ has joined #openstack-neutron13:26
openstackgerritSushil Kumar proposed a change to openstack/neutron: Updates tox.ini to use new features  https://review.openstack.org/6082513:29
*** chandankumar_ has quit IRC13:29
*** chandankumar has joined #openstack-neutron13:30
*** yamahata_ has quit IRC13:35
*** enikanorov__ has quit IRC13:50
*** yamahata_ has joined #openstack-neutron13:54
openstackgerritJianing Yang proposed a change to openstack/neutron: Implement basic functionalities for port forwarding  https://review.openstack.org/6051213:56
*** yamahata_ has quit IRC13:57
*** yamahata_ has joined #openstack-neutron13:57
*** yamahata_ has quit IRC13:58
*** yamahata_ has joined #openstack-neutron13:59
*** hxgqh1987 has quit IRC14:00
*** enikanorov__ has joined #openstack-neutron14:00
*** enikanorov__ has joined #openstack-neutron14:01
*** julim has joined #openstack-neutron14:09
*** hxgqh1987 has joined #openstack-neutron14:10
*** jianingy is now known as jianingy_afk14:12
*** yamahata_ has quit IRC14:12
*** yamahata_ has joined #openstack-neutron14:13
*** bashok has quit IRC14:15
*** jprovazn has joined #openstack-neutron14:16
*** changbl has quit IRC14:19
*** rkukura has joined #openstack-neutron14:24
*** hxgqh1987 has quit IRC14:26
*** carl_baldwin has joined #openstack-neutron14:29
*** otherwiseguy has joined #openstack-neutron14:33
*** hxgqh1987 has joined #openstack-neutron14:33
*** SushilKM has quit IRC14:35
*** banix has joined #openstack-neutron14:37
*** heyongli has quit IRC14:40
anteayaI recommend you read this post: http://lists.openstack.org/pipermail/openstack-dev/2013-December/022065.html14:41
anteayaseems that https://bugs.launchpad.net/tempest/+bug/1253896 is indeed a neutron issue14:41
anteayahas anyone seen salvatore today?14:42
*** aveiga has joined #openstack-neutron14:42
anteayahe is the neutron person with the most experience with bug 125389614:42
*** hxgqh1987 has quit IRC14:42
*** alex_klimov has quit IRC14:46
*** hxgqh1987 has joined #openstack-neutron14:46
*** alagalah has joined #openstack-neutron14:51
*** enikanorov__ has quit IRC14:53
*** hxgqh1987 has quit IRC14:55
openstackgerritZang MingJie proposed a change to openstack/neutron: Modular L2 TypeDriver refact (ovs-agent)  https://review.openstack.org/6176114:56
openstackgerritZang MingJie proposed a change to openstack/neutron: Modular L2 TypeDriver refact (service)  https://review.openstack.org/3789314:56
*** jecarey has joined #openstack-neutron14:58
*** jistr has quit IRC14:58
*** jistr has joined #openstack-neutron15:02
anteayasdague jog0 e-r is stating this patch is hitting 1253896 https://review.openstack.org/#/c/60825/415:05
anteayacan you help me find the location of the Error reading SSH protocol banner error? so far, I can't find it15:06
anteayaI can find Create member 30fab5ef-fffd-4452-8be4-8145e1f78016 failed on device driver haproxy_ns15:07
anteaya2013-12-12 14:18:48.744 6250 TRACE neutron.services.loadbalancer.drivers.haproxy.agent_manager Traceback (most recent call last):15:07
anteaya in lbaas.txt15:07
*** clev has joined #openstack-neutron15:09
sdagueanteaya: more 1253896.yaml15:11
sdaguequery: >15:11
sdague  message:"SSHTimeout: Connection to the" AND message:"via SSH timed15:11
sdague  out."15:11
sdague  AND filename:"console.html"15:11
sdaguehttp://logs.openstack.org/25/60825/4/check/check-tempest-dsvm-neutron/fb72815/console.html#_2013-12-12_14_38_42_33715:11
sdagueis the triggering line15:11
openstackgerritMathieu Rohon proposed a change to openstack/neutron: Send fdb remove message when a port is migrated  https://review.openstack.org/6176715:11
roaetAny neutron cores willing to approve this patch? It has been waiting since september https://review.openstack.org/#/c/44942/15:11
anteayaroaet: no approvals right now15:12
roaetOh?15:12
anteayawe need to get two pip install -U patches in first15:13
jog0anteaya: http://logs.openstack.org/25/60825/4/check/check-tempest-dsvm-neutron/fb72815/testr_results.html.gz15:13
* roaet nods15:13
anteayasee mailing list post15:13
anteayahttp://lists.openstack.org/pipermail/openstack-dev/2013-December/022065.html15:13
* roaet can't keep up with the ML15:13
anteayaroaet: thanks, yes I know that is why I am trying to help15:13
anteayaif you want to review those patches, that would speed things along15:14
anteayasdague jog0 thanks, I guess I am used to finding the actual error output in the title of the bug report or somewhere near the top15:15
anteayajog0: so last week we were in agreement that this wasn't neutron and sdague believes neutron is playing a large role15:16
anteayawho wants to help me fill in the blanks so I can act effectively15:16
anteayalike with knowledge15:16
jog0anteaya: yeah so last week I don't think it was as neutron bug15:17
jog0if you look at the graph for that bug, there was a recent uptick in hits15:17
anteayaroaet: I screwed up my mailing list post: https://review.openstack.org/#/c/61508/ is the other one15:19
anteayajog0: okay thanks, I will look15:19
roaetanteaya: if our packages aren't version locked could the default action of upgrading cause issues?15:20
* roaet wishes all requirements were version locked15:20
*** alagalah has left #openstack-neutron15:21
*** carl_baldwin has quit IRC15:21
anteayaroaet: I don't know15:22
anteayado you have specific packages that you are concerned about?15:23
*** carl_baldwin has joined #openstack-neutron15:23
roaetanteaya: no specific ones. all of them that aren't pinned. I don't have a solution for 'getting new features' other than letting things upgrade magically, but I dislike the risk involved with that.15:24
*** carl_baldwin has quit IRC15:24
roaetMaybe a version review board or something. I prefer human intervention when it comes to bumping versions of dependencies.15:25
*** jgrimm has joined #openstack-neutron15:25
anteayajog0 sdague am I missing something? did the fingerprint for bug 1253896 change at any point?15:25
anteayaroaet: I can understand that15:26
*** AlexF has joined #openstack-neutron15:26
anteayathis patch is to help folks with their local env15:26
anteayayou can pull the patch down and work with it locally noting any packaging issues you encounter in a comment on the patch15:27
anteayathat would help actually15:27
jog0anteaya: the fingerprint is a relativly generic one15:28
jog0that can be triggered by multiple root causes15:28
jog0so we just cought a second bug in that one I think15:28
jog0that or somehow the tests or config changed to make this worse15:29
anteayacould we possibly separate them out identifying individual causes?15:31
anteayato me Error reading SSH protocol banner is different than the haproxy_ns failure15:32
anteayaunless they are the same and I just don't know it15:33
jog0haproxy_ns?15:41
anteayathat was the error I saw15:42
jog0anteaya: in short yes we could seperate them as long as we have two fingerprints15:42
jog0anteaya: link15:42
*** garyk has quit IRC15:42
anteayahttp://logs.openstack.org/25/60825/4/check/check-tempest-dsvm-neutron/fb72815/logs/screen-q-lbaas.txt.gz#_2013-12-12_14_18_45_70715:43
anteayaI never saw an error mentioning banner anywhere in the logs I looked at15:43
anteayathe e-r fingerprint for 1253896 doesn't mention banner, but the bug report states it in the title15:45
jog0so the q-lbaas error may be unrelated15:45
anteayahmmmm15:45
jog0anteaya: ahh so the ssh bug has changed a little bit over time  Ithink15:45
anteayaunrelated to 1253896?15:45
jog0which is to say its confusing15:45
anteayayes15:45
jog0anteaya: not 100% convinced its unrelated but I can't see how it is related15:46
anteayahard to for me to follow up with the person fixing it if I don't have a clear understanding at the very least, of the fingerprint15:46
anteayajog0: fair enough15:46
anteayaanything else I can do to dig deeper into this?15:46
anteayato clarify if we do have just one bug or if this is multiple bugs being attributed to the same bug number?15:47
jog0anteaya: so the fingerpint now is15:49
jog0message:"SSHTimeout: Connection to the" AND message:"via SSH timed out." AND filename:"console.html"15:49
jog0that means we are basing this bug on the output of the tempest run15:49
jog0if we can find a line in neutron logs that allign with this failure then we can get a better bug classification on this15:49
jog0anteaya: also this started happening a lot in the past few days so go back to the commit logs and see if anything is suspicious15:50
*** vkozhukalov has quit IRC15:51
*** carl_baldwin has joined #openstack-neutron15:53
anteayaI will do my best15:54
anteayaso this might be a tempest commit or a neutron commit, yes?15:55
jog0anteaya: my guess is: neutron, tempest, nova, devstack-gate15:55
jog0looking at neutron now15:55
jog0'git log --no-merges --since=3.days'15:55
anteayak15:58
anteayajust in terms of my groking the elastic-recheck goodness this error "Timed out waiting for thing 5de6f55a-7f53-4c4e-b69e-3c16d1988d2c                       to become ACTIVE15:58
anteaya"15:58
anteayatriggered https://bugs.launchpad.net/nova/+bug/125762615:59
*** SushilKM has joined #openstack-neutron15:59
anteayabut I can't see the mention of RPC15:59
jog0http://logs.openstack.org/45/61745/1/check/check-tempest-dsvm-neutron/3d82336/logs/screen-q-svc.txt.gz?level=TRACE15:59
anteayanot in here: http://logs.openstack.org/08/61508/1/check/gate-tempest-dsvm-large-ops/775535b/testr_results.html.gz15:59
jog0anteaya: I can only look at one bug at a  time16:00
jog0I am still on 125389616:00
jog0so the q-svc log above ^16:00
jog0anteaya: thats a lot of stacktraces16:00
jog0don't know which ones are normal or not16:00
*** otherwiseguy has quit IRC16:00
jog0but fixing those will make this bug a little clearer16:00
*** otherwiseguy has joined #openstack-neutron16:01
anteayajog0: yeah sorry16:01
anteayafixing the stacktraces for the testr_results for 6150816:02
anteayasorry 6174516:02
anteayajog0: 61745 is a heat patch: https://review.openstack.org/#/c/6174516:03
anteayasorry fixing it for q-svc16:03
jog0http://logstash.openstack.org/#eyJzZWFyY2giOiJcIiBTZXNzaW9uJ3MgdHJhbnNhY3Rpb24gaGFzIGJlZW4gcm9sbGVkIGJhY2sgZHVlIHRvIGEgcHJldmlvdXMgZXhjZXB0aW9uIGR1cmluZyBmbHVzaC4gXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzODY4NjQxOTE3NTV916:04
jog0message:" Session's transaction has been rolled back due to a previous exception during flush. "16:04
jog0that doesn't signify a failure but that is a new bug that be related16:04
jog0heh thats haproxy16:05
anteayaokay16:06
*** yamahata_ has quit IRC16:07
*** ywu has joined #openstack-neutron16:07
anteayajog0 sdague which test results in screen-q-svc.txt? http://git.openstack.org/cgit/openstack/tempest/tree/tempest/api/network16:08
jog0anything that talks to neutron16:09
*** mlavalle has joined #openstack-neutron16:09
jog0screen-q-svc is neutron server16:09
anteayaso if my mission is to fix the stacktraces for q-svc16:09
jog0those are all stacktraces in neutron16:10
anteayahow do I begin my locating the file or files generating those stacktraces16:10
*** dhellmann is now known as dhellmann_16:10
anteayaso I can id them for clean up?16:10
anteayaor are you saying file bugs for each of the errors that show up16:10
jog0you don't really need to know what test generated them (but you can find that via tracing request-ids)16:11
jog0yeah file a bug for each stacktrace16:11
jog0http://logs.openstack.org/45/61745/1/check/check-tempest-dsvm-neutron/3d82336/logs/screen-q-svc.txt.gz?level=TRACE#_2013-12-12_14_34_40_31016:11
anteayathus eliminating the reason for the stacktrace being generated16:11
jog0yeah, so this many stacktraces makes it very easy for a gate failing stacktrace to hide in the noise16:11
anteayak16:12
anteayaso fir the link you gave me this is the error: MemberNotFound: Member 21f6ce73-fff8-4a7e-b798-527a4bb64b92 could not be found16:12
anteayafor16:12
anteayayes?16:12
jog0anteaya: yes, but the full stacktrace is the important part16:13
*** amritanshu_RnD has quit IRC16:13
jog0the bug should say, loadbalancer is stacktracing during  passing jobs (you would have to confirm that part)16:14
jog0then include a logstash query16:14
anteayahow do I create a logstash query?16:15
anteayaI tried yesterday and failed miserably16:15
anteayaover a million hits for my query, very useless16:15
*** markmcclain has joined #openstack-neutron16:16
jog0that one is hard16:16
jog0for  PoolMonitorAssociationNotFound: Monitor 26a39bb9-5a68-4fdd-853f-123e0f04125d is not associated with Pool 2bfcdb7a-8e5d-4bbc-8510-185916c863b116:16
jog0you can do message:" PoolMonitorAssociationNotFound: Monitor 26a39bb9-5a68-4fdd-853f-123e0f04125d is not associated with Pool 2bfcdb7a-8e5d-4bbc-8510-185916c863b116:16
jog0you can do message:" PoolMonitorAssociationNotFound"16:17
anteayak16:17
anteayalet me try that16:17
jog0message:"PoolMonitorAssociationNotFound" AND filename:"logs/screen-q-svc.txt" AND loglevel:"ERROR"16:18
anteayaah even better16:18
jog0if you click on a result, you get a list of attributes16:18
jog0and if you click on the magnifying glass that gets added to the query16:19
jog0FYI that query is from this patch I9fd90a1321611d202ef838681273081fa6c1686a16:19
anteayahttp://bit.ly/18FVAnd16:19
jog0the haproxy stuff is bad16:20
jog0err stacktracey16:20
anteayaone thing at a time16:20
jog0anteaya: I would search for last 7 days at least16:20
anteayak16:20
openstackgerritAvishay Balderman proposed a change to openstack/neutron: LBaaS L7 model (WIP)  https://review.openstack.org/6172116:21
anteayahttp://bit.ly/1gsrsAx16:22
*** changbl has joined #openstack-neutron16:22
anteayathat one started two days ago16:22
jog0anteaya: yup16:22
anteayaokay now let's address "if you click on a result, you get a list of attributes"16:22
anteayabuild change looks like a good bit of info16:23
anteayahow does that help me16:23
jog0things like build_patchset, build_uuid,filename16:23
jog0etc16:23
jog0you can click the magnifying glass in the action column to narrow your search16:23
*** yfried has quit IRC16:24
anteayaclicking16:24
*** SushilKM has quit IRC16:25
markmcclainanteaya: hi16:25
anteayamarkmcclain: hello16:25
anteayatrying to sort where we are on bug https://bugs.launchpad.net/tempest/+bug/125389616:25
anteayajog0 is helping16:25
anteayacan't reach salvatore yet16:26
*** SushilKM has joined #openstack-neutron16:26
anteaya1253896 is openstack's worst bug right now16:26
anteayawould be great if we could make some progress on it today16:26
anteayajog0: I'm still uncertain about what the magnifying glass does16:27
anteayabut we can move on16:27
markmcclainanteaya: when I spoke with salv-orlando he was still working on it16:28
anteayagreat16:28
anteayadid he by change submit any kind of patch yet?16:28
anteayaor do you know when he will be online?16:28
jog0anteaya: my brain is fried (its pat 5:30 here)16:29
jog0look up a kibana tutorial16:29
jog0that should help with logstash.openstack.org16:29
jog0kibana is the UI on logstash.openstack.org16:29
anteayajog0: thanks for all your help16:30
anteayahope Barcelona is going well16:30
anteayag'night16:30
*** srao has joined #openstack-neutron16:32
*** markmcclain has quit IRC16:33
anteayaobondarev: can you take a look at https://review.openstack.org/#/c/40381/ please?16:36
sraoNoob using devstack.  My bare metal server has eth0 connected to internet. eth2 connected to another blade. I want to run openstack as multi-node. How? Pls point to worksheets. I could only find single nic procedures for install.16:36
anteayaparticularly looking at jog0's comment16:37
anteayahi srao16:37
anteayaare you using devstack as a development environment?16:37
*** amuller has quit IRC16:37
srao@anteaya: Yes.16:37
*** garyk has joined #openstack-neutron16:38
*** Abhishek_ has quit IRC16:38
anteayagreat16:38
mlavallenati_ueno: sorry for last nigh…. as I said, I suspected I was missing something ;-(16:39
anteayaso what instructions are you following for your devstack installation?16:39
anteayamlavalle: hey there16:39
mlavalleanteaya; hey16:39
anteayamlavalle: have you had a chance to assess the results of nati_ueno's patch yet?16:39
sraoI tried the devstack multinode procedure on the devstack.org homepage.16:40
*** otherwiseguy has quit IRC16:40
mlavallenot yet16:40
anteayasrao: can you post the link for that please16:40
*** otherwiseguy has joined #openstack-neutron16:40
anteayamlavalle: okay let me know what you find once you have16:40
mlavallegive me a little bit16:40
sraohttp://devstack.org/guides/multinode-lab.html16:41
anteayamlavalle: sure16:42
anteayasrao: what image are you using?16:43
sraoubuntu 12.04 on the server16:43
anteayahave you successfully installed devstack at any point in the past?16:43
sraoyes. The default procedure works.16:45
anteayagreat16:45
*** Abhishek_ has joined #openstack-neutron16:45
anteayasrao: have you been able to implement the instructions for the multi-node lab as outlined?16:47
sraoYes. But I loose internet connectivity16:48
sraowhen I specify eth2 instead of eth016:48
*** SumitNaiksatam has quit IRC16:48
openstackgerritdekehn proposed a change to openstack/neutron: extra_dhcp_opt add checks for empty strings  https://review.openstack.org/5985816:49
anteayasrao: can you paste any output you have? paste.openstack.org unless you like something else16:49
*** ekarlso has quit IRC16:50
*** jistr has quit IRC16:50
*** ekarlso has joined #openstack-neutron16:51
srao@anateaya: What output do you need? There are so many screen windows spewing logs16:54
*** tnadeau has joined #openstack-neutron16:57
mlavalleanteaya: nati_ueno's batch fixed https://bugs.launchpad.net/tempest/+bug/125928216:58
*** emagana has joined #openstack-neutron16:58
*** srao has left #openstack-neutron16:59
mlavalleanteaya: so that sends us back to analyze what's triggering the next incarnation of https://bugs.launchpad.net/neutron/+bug/125144817:01
anteayamlavalle: yay17:01
anteayamlavalle: okay, any inital thoughts17:02
mlavalleanteaya; looking….17:02
anteayak17:02
mesteryFYI: Neutron third-party testing meeting in #openstack-meeting-alt now (Agenda on the etherpad here: https://etherpad.openstack.org/p/multi-node-neutron-tempest)17:03
mesteryFor those interested.17:03
*** safchain has quit IRC17:03
emaganamestery: I do not see antone there!17:04
emaganaanyone*17:04
mestery???17:04
mesteryWe're all talking now emagana :)17:04
emaganamine IRC client is making me a joke!17:04
*** SumitNaiksatam has joined #openstack-neutron17:05
anteayaI need a core to +A this patch: https://review.openstack.org/#/c/60825/17:06
anteayanati_ueno: are you about?17:06
*** srao has joined #openstack-neutron17:08
*** afazekas has quit IRC17:10
*** amotoki has joined #openstack-neutron17:13
*** JunPark has joined #openstack-neutron17:13
*** rudrarugge has joined #openstack-neutron17:13
mesteryanteaya: I can +A that patch if you want17:15
anteayayes please17:16
mesteryanteaya: Done.17:16
anteayathanks17:16
*** yfried has joined #openstack-neutron17:16
*** jpark has joined #openstack-neutron17:17
mlavalleanteaya: we now hit a problem with XML client….. that trips tempest.api.network.test_networks.BulkNetworkOpsXML.test_bulk_create_delete_network17:17
mlavallewhich leaves networks alive and that, in turn, triggers other tests trying to attach instances to a default network when several networks are possible…. I'll triage it in more detail this afternoon17:17
roaetAre there currently ml2 issues that are breaking devstack that we know about? https://bugs.launchpad.net/devstack/+bug/126041117:18
mesteryroaet: I saw a few reviews for DB migration issues with devstack, yes.17:18
mesteryI reviewed them this morning.17:18
mesteryCan't recall what htey are, in an IRC meeting ATM as well.17:18
anteayamlavalle: awesome thanks17:18
*** JunPark_ has joined #openstack-neutron17:19
anteayaif you don't beat me too it, I will add your above comments to that bug report17:19
*** JunPark has quit IRC17:21
*** garyk has quit IRC17:21
srao@anteaya: How can I get neutron to create an external bridge EACH for physical interface present using dashboard?17:21
sraoI should've sent that question to all audience :-)17:22
*** jpark has quit IRC17:22
anteayausing the dashboard? I am not sure horizon has the functionality17:22
anteayawe all read all the stuff17:23
*** decede has quit IRC17:23
sraook. In that case, how do I get it done in neutron? Is there a write up that you can point me to?17:23
anteayaI am mostly just the greeter and clarifier of questions, other folks jump in once they have a better sense of what you are looking for17:23
anteayanot that I know of17:23
anteayadtroyer is the devstack guy and is in #openstack-qa17:24
anteayayou might try talking directly to him to get your devstack up17:24
anteayaif this is for developement purposes17:24
sraoThanks. I'll try talking to him.17:25
anteayasure17:25
*** garyk has joined #openstack-neutron17:28
*** jaypipes has joined #openstack-neutron17:28
*** jaypipes has quit IRC17:28
*** AlexF has quit IRC17:29
*** nati_ueno has quit IRC17:34
*** djbkd has joined #openstack-neutron17:36
*** amotoki has quit IRC17:42
SumitNaiksatamrudrarugge: for your 3rd part testing, did you need to put the test box on the public network?17:45
rudraruggeYes we have a public server(s)17:45
SumitNaiksatamrudrarugge: ok thanks, so it seems like that would be the requirement?17:46
rudraruggeSumitNaiksatam: We launch VMs on these and then run the tests17:46
rudraruggeSumitNaiksatam: yes it seems like that17:46
*** emagana has quit IRC17:46
rudraruggeSumitNaiksatam: now we are trying to plug in a Jenkins and patch filter framework17:46
SumitNaiksatamrudrarugge: great, hope we can also catch up soon :-P17:47
rudraruggeSumitNaiksatam: surely - need to work on the fwaas also from my side :)17:47
openstackgerritEvgeny Fedoruk proposed a change to openstack/neutron: Extending quota support for neutron LBaaS entities  https://review.openstack.org/5872017:47
SumitNaiksatamrudrarugge: yes, looking forward to it17:47
*** decede has joined #openstack-neutron17:51
*** yfried has quit IRC17:51
*** rossella_s has quit IRC17:52
*** JunPark_ has quit IRC17:53
*** jpich has quit IRC17:54
*** nati_ueno has joined #openstack-neutron18:00
*** ygbo_ has quit IRC18:02
*** decede has quit IRC18:11
*** vkozhukalov has joined #openstack-neutron18:12
anteayanati_ueno: thanks for https://review.openstack.org/#/c/61234/18:13
anteayamlavalle: is working on the next bug now18:14
nati_uenoyour welcome. Thank you for finding this bug18:14
mlavallenati_ueno: sorry for last night18:14
nati_uenomlavalle: ? last night?18:14
mlavallenati_ueno: yeah, my comments in the review… I knew I was missing something18:15
nati_uenomlavalle: Totally no problem :)18:15
mlavallenati_ueno: :-)18:15
*** fouxm has quit IRC18:18
anteayaI'm stepping out, time for some sunshine. I should be back in an hour and a half or so18:24
anteayaif savatore comes online if someone could ask him for an update on https://bugs.launchpad.net/tempest/+bug/1253896 that would be much appreciated18:25
*** decede has joined #openstack-neutron18:25
anteayahttp://lists.openstack.org/pipermail/openstack-dev/2013-December/022052.html for context18:26
*** suresh12 has joined #openstack-neutron18:27
*** salv-orlando has joined #openstack-neutron18:27
*** jhurlbert has joined #openstack-neutron18:29
*** decede has quit IRC18:32
*** jhurlbert has quit IRC18:41
*** jhurlbert has joined #openstack-neutron18:42
*** jhurlbert has quit IRC18:44
openstackgerritZang MingJie proposed a change to openstack/neutron: Modular L2 TypeDriver refact (service)  https://review.openstack.org/3789318:44
openstackgerritZang MingJie proposed a change to openstack/neutron: Modular L2 TypeDriver refact (ovs-agent)  https://review.openstack.org/6176118:44
*** nati_uen_ has joined #openstack-neutron18:46
*** decede has joined #openstack-neutron18:46
*** nati_ueno has quit IRC18:49
*** decede has quit IRC18:51
*** nati_uen_ has quit IRC18:54
*** nati_ueno has joined #openstack-neutron18:55
*** djbkd has quit IRC19:02
*** jgrimm has quit IRC19:03
*** Abhishek_ has quit IRC19:08
*** decede has joined #openstack-neutron19:09
*** mlavalle has quit IRC19:15
*** dims has quit IRC19:33
SumitNaiksatamanteaya: is the embargo still on for approving (+A) patches?19:34
*** dims has joined #openstack-neutron19:34
roaetis +A the new +2?19:34
*** alex_klimov has joined #openstack-neutron19:34
roaetor are they not the same?19:35
SumitNaiksatamanteaya: looking at the gate queue it seems, it will be better to spare it for some time19:35
SumitNaiksatamroaet: second +2 is not automatic approval19:35
roaetot it19:35
roaet+g19:35
SumitNaiksatamroaet: the approve button still has to be hit -> +A :-)19:35
*** salv-orlando has quit IRC19:36
*** salv-orlando has joined #openstack-neutron19:36
*** SushilKM__ has joined #openstack-neutron19:43
*** SushilKM has quit IRC19:46
anteayaSumitNaiksatam: let me check if the pip install -U patches have merged yet19:46
anteayathat is what we are waiting on19:46
SumitNaiksatamanteaya: i think that has gone through19:46
SumitNaiksatamanteaya: but the queue is pretty long19:46
anteayahttps://review.openstack.org/#/c/60825/4 is still in the gate19:47
anteayaso is https://review.openstack.org/#/c/61508/19:47
SumitNaiksatamok19:47
anteayaonce those two have merged we are good for approvals again19:47
SumitNaiksatamanteaya: so we wait19:47
anteayathanks for checking SumitNaiksatam19:47
anteayawe do19:47
SumitNaiksatamanteaya: sure19:47
*** jprovazn has quit IRC19:58
*** mlavalle has joined #openstack-neutron19:59
*** jlibosva has quit IRC19:59
*** markmcclain has joined #openstack-neutron20:07
jog0anteaya: any progress on https://bugs.launchpad.net/tempest/+bug/1253896 ?20:08
anteayajog0: not so far20:11
anteayasalvatore seems to know the most about this bug and so far I have not be able to find him20:11
anteayastill working on getting a status update20:12
anteayajog0: is the sun up where you are?20:12
jog0anteaya: no its been down for a long time20:12
anteayaI also need to improve my kibana foo, as you pointed out20:12
anteayajog0: are you still in Spain?20:12
jog0anteaya: thanks, anyway this bug is bugging us20:13
jog0anteaya: yup fly out in the AM20:13
anteayajog0: no kidding20:13
anteayait is definitely a priority for me too20:13
jog0anteaya: thanks20:14
jog0night20:14
anteayamy pleasure, thanks for all your help20:14
anteayanight20:14
*** yfried has joined #openstack-neutron20:20
*** djoreilly has quit IRC20:21
*** otherwiseguy has quit IRC20:28
*** SushilKM__ has quit IRC20:33
anteayajog0: just for the sake of conversation, for some reason I come up empty searching for kibana tutorials20:39
anteayathe best material I got was from clarkb's patch: https://review.openstack.org/#/c/61298/4/README.rst20:40
anteayapoint to lucene docs: http://lucene.apache.org/core/4_0_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#package_description20:40
anteayaso I'll start there20:40
anteayathough I did come up with some nice distraction on ikebana20:40
anteayaso pretty20:40
*** otherwiseguy has joined #openstack-neutron20:44
*** Swami_ has joined #openstack-neutron21:02
*** rwsu has quit IRC21:05
*** ichihara has joined #openstack-neutron21:07
Swami_hi nachi21:10
nati_uenoSwami_: hi21:11
SumitNaiksatamSwami_ nati_ueno: hi21:11
Swami_Ok, summit: mentioned that he will join21:11
Swami_Hi all21:11
SumitNaiksatamSwami_: i am here :-)21:11
Swami_Thanks for joining the meeting in a short notice21:11
Swami_The agenda here is to discuss about the services when we run the L3-Service in a distributed mode versus the centralized mode21:11
*** djbkd has joined #openstack-neutron21:12
Swami_There are some services such as VPN, which does not need to be distributed, but some services such as FW can be distributed. How are we going to achieve this21:12
*** rkukura has quit IRC21:13
*** djbkd has quit IRC21:13
*** alex_klimov has quit IRC21:13
*** rkukura has joined #openstack-neutron21:13
SumitNaiksatamSwami_: that's true, the distribution will create a complication for fwaas21:13
*** rkukura has left #openstack-neutron21:13
SumitNaiksatamSwami_: you have thoughts on this?21:13
Swami_No, I am investigating it right now, and I wanted to have a cleaner approach. I initially was thinking to run all the services in a centralized router and have the basic L3 distributed, but as you mentioned that would be a problem for FW.21:14
*** AlexF has joined #openstack-neutron21:14
Swami_Also if I think of distributing all the services to all nodes, that would be a problem for VPN.21:15
SumitNaiksatamSwami_: ok21:15
Swami_Is there a way that we can identify the router as a core router and apply the services only to those core router and have the traffic forwarded to the right network21:16
Swami_nachi: You mentioned in your email that we can make use of the "provider" flag.21:17
nati_uenoyes21:17
Swami_But the provider flag will only determine what driver to use for the services.21:17
nati_uenoIMO, it is sufficient21:18
nati_uenofor VPN21:18
nati_uenoWe can identify valid combination21:18
SumitNaiksatamSwami_: i am not very clear on the "core" router notion that you mentioned21:19
Swami_sumit: I mentioned something similar to a service router rather than a normal router, so that we only apply the services on that router.21:19
SumitNaiksatamSwami_: ah ok21:19
Swami_But still that seems to be same as the Network node router that we have today.21:19
SumitNaiksatamSwami_: so there will be a single services' router?21:20
Swami_sumit: Yes, and that service router can be attached to any compute node that the tenant wants to add it to.21:20
SumitNaiksatamSwami_: okay, but then the choke point shifts to this service router21:21
SumitNaiksatam?21:21
Swami_Yes, exactly right.- it is no different than a Network node21:21
SumitNaiksatamSwami_: hmmm21:21
SumitNaiksatamSwami_: that said, it could be a starting point21:22
Swami_But if we wanted to distribute the services, say for example do you want to run VPN on all the compute Nodes, just because you have a distributed router setup21:22
Swami_If we have a hybrid model, where we have centralized Router and distributed router and the centralized router will host the centralized services and the distributed router will host the distributed services such as FW, then we may have to try to tie these two networks together through another internal gateway21:24
SumitNaiksatamSwami_: yeah21:24
SumitNaiksatamSwami_: i think we can incrementally work towards a more sophisticated model21:24
Swami_sumit: Yes I agree with you that incremental approach to solve the services problem would be the right approach21:25
SumitNaiksatamSwami_: so with the "services'" router notion, there would two flavors of routers21:26
SumitNaiksatam?21:26
Swami_sumit: Running east-west traffic and having a centralized router ( Network Node) for all services will work, but still it would break the FW.21:26
SumitNaiksatamSwami_: you might need FW for east-west traffic as well21:27
SumitNaiksatamSwami_: so yeah21:27
Swami_sumit: Yes, there should be a regular router providing L3 services and to the extent a Gateway service but any other services should be part of the service router21:27
Swami_sumit: Yes, that's what I mentioned, even if we target the first use case the FW will break.21:27
SumitNaiksatamSwami_: is the current implementation of lbaas (with HA Proxy driver) affected by this at all?21:29
Swami_sumit: I am not sure about the lbaas, that is the reason I include enikanorov, but he did not reply.21:30
SumitNaiksatamSwami_: my guess is that it won't be affected, but better to get confirmation21:30
*** banix has quit IRC21:31
Swami_sumit: I think that it should also have some implications in distributing the HA Proxy.21:31
Swami_But running it centralized should not cause any problem.21:31
SumitNaiksatamSwami_: hmmm may be…but would distributing the agent not still be independent of the router?21:32
Swami_Sumit: In the FW case, if we plan to distribute the FW to all the routers in the node, will that be a major change, or the code should already support it.21:32
SumitNaiksatamSwami_: regarding FW, you mean send the same rules everywhere?21:32
Swami_sumit: yes distributing the agent is independent of the router. But if the service is tied to the router, then we need to take care.21:33
Swami_sumit: Yes21:33
Swami_Will that cause any performance issues.21:33
SumitNaiksatamSwami_: i don't think that should be a big issue code wise21:33
SumitNaiksatamSwami_: performance yes, may be21:33
SumitNaiksatamSwami_: performance degrades linearly with the number of rules21:33
Swami_But in this case the number of rules will not change.21:34
SumitNaiksatamSwami_: so if we can selectively distribute the rules, that would be ideal21:34
SumitNaiksatamSwami_: if apply the same rules at all points in the distributed router, the number of rules will not increase21:35
Swami_sumit: Today when we configure a Firewall, the tenant create a Policy, apply the rules and then associates with a router or with a network21:35
SumitNaiksatamSwami_: i guess what i was thinking is that not all rules might be required at all the distributed points21:35
nati_uenosorry i should go. let's me catch up log later21:35
nati_uenoTL!21:35
*** nati_ueno has quit IRC21:36
SumitNaiksatamSwami_: there is no association/insertion by the tenant21:36
SumitNaiksatamSwami_: the implementation automatically associates with a router21:36
Swami_nachi: Thanks, I will talk to you later.21:36
SumitNaiksatamSwami_: thats the default and only mode21:36
SumitNaiksatamSwami_: we are trying to get away from there, by introducing the insertion context so that we can support different insertion modes21:37
SumitNaiksatamSwami_: including the "network" association you mention21:37
Swami_sumit: So if the same router is created across the compute node, the rules will be automatically applied.21:37
SumitNaiksatamSwami_: yes21:37
*** yfried has quit IRC21:38
Swami_Then theoretically the existing firewall implementation should work if we distribute the router21:38
Swami_sumit: In other words, is there any dependency that the current Firewall should be only centralized.21:40
SumitNaiksatamSwami_: need to think a little more, but i think that should work21:41
Swami_sumit: Ok give it thought and I will keep you in the loop, meanwhile I will also check21:42
SumitNaiksatamSwami_: in the current implementation, l3_agent extends the fwaas base (we follow the mixin approach)21:42
Swami_So if we use the same L3 agent, it should not be a problem21:42
SumitNaiksatamSwami_: so if, fwaas is configured, it should kick in wherever the l3 agent is run21:42
SumitNaiksatamSwami_: yes21:42
SumitNaiksatamSwami_: and the fwaas base implementation loads the fwaas driver21:43
Swami_There were two approaches that we were thinking, either to use the existing L3 agent to support distributed or else to create an new dvr_agent.21:43
SumitNaiksatamSwami_: yeah, hence letting you know how it works today21:43
SumitNaiksatamSwami_: if you plan to create a different agent, then the fwaas dependency will have to be accounted for21:44
Swami_If we were to address the Hybrid model, with centralized and distributed, we might need two agents, otherwise, if we were to only make it either distributed or centralized, then we would go with the current L3-agent.21:44
SumitNaiksatamSwami_: we don't want to create a separate agent for fw21:44
SumitNaiksatamSwami_: yeah21:44
Swami_sumit: Yes agreed21:44
*** jecarey has quit IRC21:45
SumitNaiksatamSwami_: for the perimeter firewall case, the firewall should be deployed at any point where the gateway resides21:45
Swami_sumit: Is service chaining address for Icehouse?21:45
SumitNaiksatamSwami_: yes, its currently targeted21:45
Swami_How will service chaining affect the services.21:46
Swami_Will service chaining give us more flexibility in where to run the services and how to connect it to the internal private network.21:47
SumitNaiksatamSwami_: its not really that service chaining will affect the services' implementation21:47
SumitNaiksatamSwami_: we might have to tweak some things if we run into issues21:48
*** yfried has joined #openstack-neutron21:48
*** marun has quit IRC21:48
SumitNaiksatamSwami_: but more importantly, if services support the insertion context, then the entity that drives the chain implementation can insert each service based on that insertion context21:49
Swami_Mainly service chaining helps the virtual appliance vendors and the hardware vendors to hook into their appliances to the required services.21:49
SumitNaiksatamSwami_: not necessarily, chaining does not make assumptions of virtual appliances or physical hardware21:49
SumitNaiksatamSwami_: sorry, i think thats what you were saying21:50
Swami_In that case will it even make sense to distribute the services to all compute nodes?21:50
SumitNaiksatamSwami_: but that should be independent of chaining right?21:50
SumitNaiksatamSwami_: chaining should allow you to say, that i want a FW -> VPN21:51
Swami_sumit: Yes my understanding is we have chaining and service insertion to add services where and when required.21:51
SumitNaiksatamSwami_: distribution might create implementation complications, for insertion/chaining21:52
SumitNaiksatamSwami_: however, conceptually it seems these should be independent21:52
Swami_sumit: got it21:52
SumitNaiksatamSwami_: distributed aspect of the router is an implementation artifact (at least in my understanding)21:53
Swami_sumit; are you working on the chaining and service insertion.21:53
SumitNaiksatamSwami_: yeah, along with other folks21:53
Swami_sumit: Yes distributed router is completely implementation specific, but it has all these issues that we need to address.21:54
SumitNaiksatamSwami_: true…implementation is a challenge :-)21:54
Swami_Do you have a weekly meeting for the chaining and service insertion, I would like to listen in.21:54
SumitNaiksatamSwami_: we were having earlier, but i suspended it so as not distract from the ongoing efforts around neutron gate stability and nova parity21:55
SumitNaiksatamSwami_: also, we have had so much discussion on this - so its actually time to put a patch up :-)21:56
SumitNaiksatamSwami_: else this will be analysis paralysis forever21:56
Swami_sumit: I would take a look at the current FW code and see if there would be any other implications running it in a distributed way and then I will get back to you.21:56
Swami_sumit: Thanks for your time, and I will discuss with Nachi on the VPN service.21:57
SumitNaiksatamSwami_: sure21:57
Swami_Swami: I will continue to work on the distributed router implementation and probably put some use cases for the services.21:57
SumitNaiksatamSwami_: thanks for starting this discussion21:58
Swami_sumit: Thanks and bye. Catch you later21:58
SumitNaiksatamSwami_: it will help for me to be sync with the distributed router discussion21:58
SumitNaiksatamSwami_: ttyl, bye21:58
*** junpark_ has joined #openstack-neutron21:59
*** junpark_ has quit IRC21:59
*** AlexF has quit IRC22:00
Swami_sumit: sure I will include you in the loop22:00
*** Swami_ has left #openstack-neutron22:00
*** changbl has quit IRC22:03
*** AlexF has joined #openstack-neutron22:03
*** junpark has joined #openstack-neutron22:03
*** julim_ has joined #openstack-neutron22:05
*** suresh12 has quit IRC22:05
*** suresh12_ has joined #openstack-neutron22:05
*** AlexF has quit IRC22:07
*** junpark has quit IRC22:07
*** djbkd has joined #openstack-neutron22:07
*** julim has quit IRC22:07
*** markmcclain has quit IRC22:07
anteayagate-tempest-dsvm-neutron is in very bad shape right now22:10
anteayathis bug is skyrocketed today22:11
anteayadoes anyone have any chance to do some digging22:11
anteayasalv-orlando: you are online22:11
anteayado you have any update on https://bugs.launchpad.net/tempest/+bug/125389622:12
salv-orlandoI am22:12
anteayathank you for being online22:12
salv-orlandoI have unfortunately seen the rise in bug occurrence only a few hours ago22:12
* anteaya nods22:12
anteayaany thoughts at this point?22:12
anteayacan I round up any resources for you to help address this?22:13
salv-orlandoI will try and root cause before bed; otherwise we can go for the usual "revert whatever is related approach"22:13
*** banix has joined #openstack-neutron22:13
salv-orlandomarun has often helped. He should be UTC+8 these days. So perhaps he could be up in an hour or two22:13
salv-orlandoI have no more than two hours before bed time22:13
anteayaunderstood22:14
anteayaanything you can do in that time is much apprciated22:14
anteayaand let me know where it stands so I can recruit other help22:14
anteayaany chance this patch might be playing a role? https://review.openstack.org/#/c/40381/22:15
*** vkozhukalov has quit IRC22:15
anteayait went in Dec. 10th22:15
anteayajog0: mentioned that it is throwing many stacktraces in screen-q-svc.txt22:15
anteayamight be unrelated22:15
anteayasdague: any additional information on 1253896?22:16
salv-orlandoumm 40381 is not really related to timeout failures unless it prevents neutron from notifying agents22:17
anteayad'oh he is in the qa meeting22:17
anteayasalv-orlando: okay, didn't think so22:17
*** ichihara has left #openstack-neutron22:18
*** gdubreui has joined #openstack-neutron22:23
*** clev has quit IRC22:28
*** aveiga has quit IRC22:35
*** dave_tucker has joined #openstack-neutron22:40
*** banix has quit IRC22:42
*** rkukura has joined #openstack-neutron22:44
*** banix has joined #openstack-neutron22:49
anteayaneutron tempest tests -- add link to relevant api to assist reviewers please, adding this in a comment is fine22:57
*** rudrarug_ has joined #openstack-neutron23:00
*** clev has joined #openstack-neutron23:01
*** rudrarug_ has quit IRC23:01
*** dave_tucker has quit IRC23:01
*** rudrarugge has quit IRC23:02
*** pcm_ has quit IRC23:08
*** SumitNaiksatam has quit IRC23:09
*** dave_tucker has joined #openstack-neutron23:10
salv-orlandoanteaya: added a comment for bug 1253896. Still inconclusive so far. Hope the insights I found might be useful for someone else who can take over while I sleep.23:11
anteayavery good23:12
anteayamy thanks23:12
anteayahappy sleep23:12
anteayaneed a recruit who knows the L3 agent and floating ips to continuing working on https://bugs.launchpad.net/neutron/+bug/125389623:14
*** jgrimm has joined #openstack-neutron23:14
anteayamestery: any thoughts who would have that knowledge whom I could ping to work on this?23:15
anteayado you?23:15
*** rkukura has quit IRC23:16
mesteryanteaya: Looking23:18
mesteryanteaya: I actually see this error in my own Tempest runs all the time too :(23:18
anteaya:(23:18
mesteryanteaya: I would like to say I could work on this, but I am stretched fairly thin ATM. I can see about looking into this.23:19
anteayamestery: awesome23:19
mesteryanteaya: I may have someone on our team who can look at this, let me ping him and see.23:19
anteayawho else might you suggest as well23:19
mesteryWill send email tonight once I get a response.23:19
anteayathis is openstack's top bug atm23:19
mesteryanteaya: Understood.23:19
anteayathanks23:19
anteayamestery: also please update the bug report with any progress, and ask your team-mate to do the same23:24
mesteryanteaya: I sent email, he should ping in channel if he is able to help, FYI.23:24
anteayaI'm going to keep recruiting and pestering until a solution is found23:24
anteayaawesome thank you23:25
mesteryanteaya: Makes sense. I told him I could help but would need him to take the lead, so lets see.23:25
anteayak23:25
anteayaI'll wander off and tend to dinner for a bit23:25
* mestery wanders too23:25
*** suresh12_ has quit IRC23:27
*** suresh12 has joined #openstack-neutron23:27
*** djbkd has quit IRC23:30
*** suresh12 has quit IRC23:32
*** dave_tucker has quit IRC23:34
*** dave_tucker has joined #openstack-neutron23:36
*** suresh12 has joined #openstack-neutron23:38
*** alagalah has joined #openstack-neutron23:39
*** otherwiseguy has quit IRC23:47
*** yamahata_ has joined #openstack-neutron23:58
*** salv-orlando has quit IRC23:58

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