Tuesday, 2013-12-17

*** mlavalle has quit IRC00:03
*** suresh12 has quit IRC00:07
*** suresh12 has joined #openstack-neutron00:12
jog0markmcclain: ping00:17
jog0how many lines do you want for your quantum rename00:17
jog0stackalytics wise00:17
*** amotoki has joined #openstack-neutron00:21
*** marun has joined #openstack-neutron00:31
jog0https://review.openstack.org/#/c/62504/00:33
*** yamahata has joined #openstack-neutron00:33
*** dims has quit IRC00:37
*** ashaikh has quit IRC00:37
*** dims has joined #openstack-neutron00:39
*** dims has quit IRC00:47
*** Mr_W has joined #openstack-neutron00:56
*** manjiri has joined #openstack-neutron00:59
*** manjiri has left #openstack-neutron01:00
*** dims has joined #openstack-neutron01:02
*** banix has joined #openstack-neutron01:04
*** dcahill has quit IRC01:10
openstackgerritSalvatore Orlando proposed a change to openstack/neutron: Process port_update notifications in the main agent loop  https://review.openstack.org/6196401:11
*** suresh12 has quit IRC01:15
*** suresh12 has joined #openstack-neutron01:17
openstackgerritIsaku Yamahata proposed a change to openstack/neutron: ml2: gre, vxlan type driver can leak segment_id  https://review.openstack.org/6169401:17
*** banix has quit IRC01:23
*** Jianyong has joined #openstack-neutron01:24
*** tnadeau has quit IRC01:32
openstackgerritA change was merged to openstack/neutron: Imported Translations from Transifex  https://review.openstack.org/6230101:34
*** djbkd has quit IRC01:39
*** ljjjustin has joined #openstack-neutron01:41
*** gdubreui has quit IRC01:45
*** ljjjustin has quit IRC01:46
openstackgerritNachi Ueno proposed a change to openstack/neutron: Improve vif attributes related with firewalling  https://review.openstack.org/2194601:46
*** ljjjustin has joined #openstack-neutron01:48
*** nati_ueno has quit IRC02:01
*** dave_tucker has quit IRC02:11
*** Mr_W has left #openstack-neutron02:12
*** banix has joined #openstack-neutron02:12
*** dzyu has joined #openstack-neutron02:17
*** networkstatic has quit IRC02:24
*** banix has quit IRC02:24
*** scotty916 has joined #openstack-neutron02:28
*** nati_ueno has joined #openstack-neutron02:30
*** scotty916 has quit IRC02:34
*** jp_at_hp1 has quit IRC02:40
openstackgerritberlin proposed a change to openstack/neutron: Fix VPNaaS Service driver should check whether router has gateway  https://review.openstack.org/6046102:46
*** gdubreui has joined #openstack-neutron02:46
openstackgerritberlin proposed a change to openstack/neutron: Fix VPNaaS Service driver should check whether router has gateway  https://review.openstack.org/6046102:47
*** neagle has joined #openstack-neutron02:47
*** aymenfrikha has joined #openstack-neutron02:48
*** vkozhukalov has joined #openstack-neutron02:48
*** aymenfrikha has left #openstack-neutron02:48
*** SushilKM has joined #openstack-neutron02:48
*** neagle has quit IRC02:50
*** banix has joined #openstack-neutron02:50
*** SushilKM has quit IRC02:52
*** dims has quit IRC02:53
*** dims has joined #openstack-neutron02:53
*** SushilKM has joined #openstack-neutron03:03
openstackgerritIsaku Yamahata proposed a change to openstack/neutron: ml2/type_gre: Adds missing clear_db to test_type_gre.py  https://review.openstack.org/6253003:06
*** yamahata__ has quit IRC03:06
*** yamahata__ has joined #openstack-neutron03:06
openstackgerritIsaku Yamahata proposed a change to openstack/neutron: ml2/type_gre: Adds missing clear_db to test_type_gre.py  https://review.openstack.org/6253003:11
*** ljjjustin has quit IRC03:21
*** clev has joined #openstack-neutron03:36
*** otherwiseguy has quit IRC03:40
*** clev has quit IRC03:41
openstackgerritDazhao Yu proposed a change to openstack/neutron: Calculate stateless IPv6 address  https://review.openstack.org/5618403:47
*** aveiga has quit IRC03:53
*** jecarey has joined #openstack-neutron03:54
openstackgerritA change was merged to openstack/neutron: NVP plugin: Avoid timeouts if creating routers in parallel  https://review.openstack.org/6086103:58
openstackgerritA change was merged to openstack/neutron: Include lswitch id in NSX plugin port mappings  https://review.openstack.org/5457803:58
openstackgerritA change was merged to openstack/neutron: NVP: propagate net-gw update to backend  https://review.openstack.org/6232203:58
*** suresh12 has quit IRC04:08
*** chandankumar has joined #openstack-neutron04:16
*** banix has quit IRC04:25
*** iwamoto has joined #openstack-neutron04:27
*** banix has joined #openstack-neutron04:29
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Added A10 LBaaS Driver to branch.  https://review.openstack.org/6246404:38
*** SushilKM has quit IRC04:38
*** ashaikh has joined #openstack-neutron04:45
*** csd_ has quit IRC04:51
*** csd_ has joined #openstack-neutron04:52
*** jecarey has quit IRC04:59
openstackgerritberlin proposed a change to openstack/neutron: Support advanced NVP IPsec VPN Service  https://review.openstack.org/5520705:03
*** qs201 has joined #openstack-neutron05:05
*** qs201 has quit IRC05:07
*** networkstatic has joined #openstack-neutron05:10
*** djbkd has joined #openstack-neutron05:12
*** yfried has joined #openstack-neutron05:14
openstackgerritberlin proposed a change to openstack/neutron: Fix VPNaaS Service driver should check whether router has gateway  https://review.openstack.org/6046105:15
*** banix has quit IRC05:25
*** csd_ has quit IRC05:31
*** csd_ has joined #openstack-neutron05:32
*** gdubreui has quit IRC05:32
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Wrapped text  https://review.openstack.org/6254405:35
*** garyk has quit IRC05:35
*** csd_ has quit IRC05:40
*** csd_ has joined #openstack-neutron05:41
*** krast has joined #openstack-neutron05:47
openstackgerritBerezovsky Irena proposed a change to openstack/neutron: Add update from agent to plugin on device up  https://review.openstack.org/5360905:47
*** krast has quit IRC05:48
*** krast has joined #openstack-neutron05:48
*** krast has quit IRC05:49
*** krast has joined #openstack-neutron05:49
krasthi guys~  has some open source like vmware nsx?05:50
*** SushilKM has joined #openstack-neutron06:00
*** SushilKM__ has joined #openstack-neutron06:04
*** dzyu has quit IRC06:04
*** SushilKM has quit IRC06:04
*** bashok has joined #openstack-neutron06:05
*** dzyu has joined #openstack-neutron06:06
openstackgerritMaru Newby proposed a change to openstack/neutron: Send DHCP notifications regardless of agent status  https://review.openstack.org/6116806:07
*** SushilKM__ has quit IRC06:14
*** SushilKM has joined #openstack-neutron06:14
openstackgerritberlin proposed a change to openstack/neutron: Support advanced NVP IPsec VPN Service  https://review.openstack.org/5520706:19
*** inara` has quit IRC06:30
*** alex_klimov has joined #openstack-neutron06:34
*** inara has joined #openstack-neutron06:37
openstackgerritJenkins proposed a change to openstack/neutron: Imported Translations from Transifex  https://review.openstack.org/6256106:38
*** alex_klimov has quit IRC06:39
*** SushilKM has quit IRC06:40
*** amritanshu_RnD has joined #openstack-neutron06:41
*** alex_klimov has joined #openstack-neutron06:41
*** harlowja is now known as harlowja_away06:43
*** SushilKM has joined #openstack-neutron06:43
*** HenryG has quit IRC06:43
*** marun has quit IRC06:49
*** vkozhukalov has quit IRC06:51
*** djbkd has quit IRC06:52
*** dzyu has quit IRC06:53
*** djbkd has joined #openstack-neutron06:54
*** djbkd has quit IRC06:54
*** dzyu has joined #openstack-neutron06:54
*** garyk has joined #openstack-neutron06:56
*** Abhishek_ has joined #openstack-neutron07:07
*** HenryG has joined #openstack-neutron07:10
*** jlibosva has joined #openstack-neutron07:28
*** Abhishek_ has quit IRC07:30
*** afazekas has joined #openstack-neutron07:37
*** zhhuabj has joined #openstack-neutron08:04
*** amotoki has quit IRC08:09
*** iwamoto has quit IRC08:09
openstackgerritSalvatore Orlando proposed a change to openstack/neutron: Process port_update notifications in the main agent loop  https://review.openstack.org/6196408:13
*** fouxm has joined #openstack-neutron08:14
*** jorisroovers has joined #openstack-neutron08:15
*** vkozhukalov has joined #openstack-neutron08:26
*** dzyu_ has joined #openstack-neutron08:30
*** dzyu has quit IRC08:30
*** dzyu_ is now known as dzyu08:30
*** marios has quit IRC08:37
*** marios has joined #openstack-neutron08:38
*** amuller has joined #openstack-neutron08:43
*** HenryG has quit IRC08:43
*** HenryG has joined #openstack-neutron08:44
*** ygbo has joined #openstack-neutron08:47
*** fouxm has quit IRC08:59
*** salv-orlando has quit IRC09:00
*** jistr has joined #openstack-neutron09:00
*** jpich has joined #openstack-neutron09:07
*** networkstatic has quit IRC09:07
*** irenab_ has joined #openstack-neutron09:09
*** fouxm has joined #openstack-neutron09:17
*** yamahata has quit IRC09:19
*** Mierdin has quit IRC09:23
*** ashaikh has quit IRC09:23
*** safchain has joined #openstack-neutron09:24
irenab_Hi, having a get_py27 failures and need some advise. There are two tests  that fails that are not related to the patch: https://review.openstack.org/#/c/53609/. Please advise09:27
enikanorovirenab_: looking09:34
*** vkozhukalov has quit IRC09:35
irenab_thanks!09:36
openstackgerritgongysh proposed a change to openstack/neutron: merge add-flow() calls  https://review.openstack.org/6134109:37
*** Abhishek_ has joined #openstack-neutron09:39
enikanorovirenab_: i believe your patchset has nothing to do with the test failure. please file a bug for neutron.tests.unit.openvswitch.test_ovs_tunnel.TunnelTestWithMTU.test_daemon_loop failre and do 'recheck bug xxx' where xx is the new bug id09:44
irenab_enikanorov: what project should I submit the bug to?09:45
enikanorovneutron09:45
irenab_enikanorov: the problem is when I run this test stand alone it passes OK...09:46
enikanorovdoes it fail in your environment?09:47
enikanorovanyway, file a bug if it is anykind of persistent or random failures09:48
irenab_enikanorov: thank you, will file a bug. And yes, now it happend in my env too09:49
*** dzyu has quit IRC09:50
*** vkozhukalov has joined #openstack-neutron09:50
*** nati_ueno has quit IRC09:53
*** nati_ueno has joined #openstack-neutron09:55
*** dzyu has joined #openstack-neutron10:01
*** krast has quit IRC10:21
*** fouxm has quit IRC10:24
*** fouxm has joined #openstack-neutron10:25
*** Jianyong has quit IRC10:28
*** Jianyong has joined #openstack-neutron10:29
*** fouxm has quit IRC10:29
*** dzyu has quit IRC10:34
*** fouxm has joined #openstack-neutron10:37
*** vkozhukalov has quit IRC10:40
*** jp_at_hp has joined #openstack-neutron10:41
*** vkozhukalov has joined #openstack-neutron10:52
*** Jianyong has quit IRC10:52
openstackgerritRajesh Mohan proposed a change to openstack/neutron: Implements: blueprint fwaas-service-insertion Implements: blueprint neutron-services-insertion-chaining-steering  https://review.openstack.org/6259911:04
openstackgerritTomoko Inoue proposed a change to openstack/neutron: Can't create a firewall for admin tenant when at least one other tenant has a firewall.  https://review.openstack.org/6260011:05
*** amuller_ has joined #openstack-neutron11:10
*** nati_ueno has quit IRC11:10
*** nati_ueno has joined #openstack-neutron11:11
*** amuller has quit IRC11:11
*** nati_uen_ has joined #openstack-neutron11:12
*** pcm has joined #openstack-neutron11:14
*** safchain has quit IRC11:14
*** nati_ueno has quit IRC11:15
*** pcm has quit IRC11:16
*** pcm has joined #openstack-neutron11:16
*** marun has joined #openstack-neutron11:17
*** salv-orlando has joined #openstack-neutron11:28
marunso is it just me or is devstack broken without this patch? https://review.openstack.org/#/c/6166311:29
marunI know it's not acceptable in its current form, but are people just applying the patch manually or ??11:30
*** unicell has joined #openstack-neutron11:36
*** unicell has joined #openstack-neutron11:36
*** zoresvit has joined #openstack-neutron11:45
*** salv-orlando has quit IRC11:47
*** HenryG has quit IRC11:50
*** chandankumar has quit IRC11:53
*** chandankumar has joined #openstack-neutron11:53
openstackgerritCyril Roelandt proposed a change to openstack/python-neutronclient: Remove a debugging print statement  https://review.openstack.org/6261711:58
*** salv-orlando has joined #openstack-neutron12:10
*** salv-orlando has quit IRC12:10
*** Abhishek_ has quit IRC12:17
*** bashok has quit IRC12:22
*** ihrachyska has joined #openstack-neutron12:23
*** dave_tucker has joined #openstack-neutron12:24
*** ian12 has joined #openstack-neutron12:30
*** marios_ has joined #openstack-neutron12:33
*** marios_ has quit IRC12:33
*** jorisroovers has quit IRC12:40
openstackgerritCyril Roelandt proposed a change to openstack/python-neutronclient: Python 3: fix a call to ugettext()  https://review.openstack.org/6262612:43
*** afazekas has quit IRC13:02
*** nati_uen_ has quit IRC13:06
*** yamahata has joined #openstack-neutron13:17
*** afazekas has joined #openstack-neutron13:22
*** ian12 has quit IRC13:28
*** afazekas has quit IRC13:51
*** geekinutah has quit IRC13:55
*** geekinutah has joined #openstack-neutron13:56
*** HenryG has joined #openstack-neutron14:00
*** heyongli has joined #openstack-neutron14:07
openstackgerritOleg Bondarev proposed a change to openstack/neutron: LBaaS: agent monitoring and instance rescheduling  https://review.openstack.org/5974314:19
anteayaenikanorov: nice guidance on addressing failing tests in logs, thank you14:21
*** banix has joined #openstack-neutron14:22
*** afazekas has joined #openstack-neutron14:23
*** jorisroovers has joined #openstack-neutron14:23
*** yamahata__ has quit IRC14:27
*** yamahata__ has joined #openstack-neutron14:28
*** julim has joined #openstack-neutron14:31
*** yamahata has quit IRC14:32
*** irenab_ has quit IRC14:32
*** markmcclain has quit IRC14:33
*** yamahata has joined #openstack-neutron14:34
anteayathis patchset is needed for a critical bug fix, it would be great to get some reviews on it please: https://review.openstack.org/#/c/21946/14:39
anteayaeveryone welcome to review14:39
*** heyongli has quit IRC14:45
openstackgerritAvishay Balderman proposed a change to openstack/neutron: LBaaS L7 model (WIP)  https://review.openstack.org/6172114:47
*** mtreinish has quit IRC14:48
*** heyongli has joined #openstack-neutron14:51
*** mtreinish has joined #openstack-neutron14:51
*** jecarey has joined #openstack-neutron14:57
*** chandankumar has quit IRC14:59
*** markmcclain has joined #openstack-neutron15:01
*** SushilKM has quit IRC15:02
kruskakliwhen patch-set is created at Gerrit, my Jenkins build is triggered. However, I'm currently running my tests against 'master' but I guess I should run on the topic-branch, or?15:03
kruskakliif so, can I get hold of the topic branch in quation from my Jenkins build script?15:04
kruskakliin question..15:04
anteayakruskakli: you should be able to15:05
anteayazuul filters on the topic branch I do believe15:06
* anteaya digs15:06
kruskaklihm..ok Iäll try to dump my environment from within my build script to see if any info exist about the topic-branch15:06
anteayakruskakli: this might be a place to begin: http://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/trigger/gerrit.py15:07
anteayaI'll keep looking15:07
kruskakliok, thanx15:07
anteayaI'm going to go with event branch is what we are after: http://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/trigger/gerrit.py#n5015:08
anteayakruskakli: you know you can set up a zuul yourself and use it for 3rd party testing?15:09
anteayahttp://ci.openstack.org/running-your-own.html15:10
kruskaklianteaya: I have a very simple start script that initiates a rather complex test case running in a vagrant instance15:10
kruskakliso if just can get hold of the topic-branch I would be fine15:10
anteayaokay15:11
anteayawell do you see the link I gave you?15:11
*** edle has joined #openstack-neutron15:11
anteayathat is how zuul identifies the topci branch15:11
anteayadoes that help you?15:11
kruskakliI hope so, I'll see if my bash script gets that info among the environment variables15:12
kruskaklifrom Jenkins that is15:12
edlehello I have an issue with nova  compute and api logs complaining about Neutron client authentication failed: Connection to neutron failed: Unable to find the server at has anyone ran into this issue?15:12
*** safchain has joined #openstack-neutron15:13
anteayaedle: do you have a url for a patch?15:13
*** otherwiseguy has joined #openstack-neutron15:15
edleurl for a patch?  im not sure what you mean url for a patch15:15
*** amritanshu_RnD has quit IRC15:15
anteayaedle: is this a development question?15:16
*** jdev789 has joined #openstack-neutron15:16
edlenot a development question15:16
anteayaah okay15:17
larsksedle: Does "keystone endpoint-get --service network" show the correct URL for your neutron server?15:17
larsksAnd can you contact that url (e.g., using curl) from your compute nodes?15:17
*** ian12 has joined #openstack-neutron15:18
edlelarsks: yes shows the correct url network.publicURL | http://10.198.0.191:9696/15:19
larsksHow about the setting of neutron_url in /etc/nova/nova.conf?15:20
edlewhen i run curl url i get {"versions": [{"status": "CURRENT", "id": "v2.0", "links": [{"href": "http://10.198.0.191:9696/v2.0", "rel": "self"}]}]}15:20
*** dave_tucker has quit IRC15:20
edlein the nova.conf i have neutron_url=http://10.198.0.191:9696 and neutron_admin_auth_url=http://10.198.0.191:35357/v2.015:21
larsksHmm.  All that looks fine.  If you run your nova services with debug logging enabled, maybe you'll see a more useful error message?15:23
*** heyongli has quit IRC15:23
edleok ill try that15:23
*** yamahata has quit IRC15:26
larsksedle: What shows up after the "at " in your error message? Is it empty? That error actually comes from the httplib2 module, and seems to suggest a dns problem (which is odd, because you're using ip addresses).15:28
larsksIf there's a backtrace with that error, can you post it somewhere?15:28
*** John______ has joined #openstack-neutron15:29
openstackgerritAssaf Muller proposed a change to openstack/neutron: Add VXLAN example to ovs_neutron_plugin.ini  https://review.openstack.org/6268415:30
John______Does 'security groups' rules apply for both Fixed IPs and Floating IPs or just to Floating IPs?15:30
larsksJohn______: security groups are realized as iptables rules on your compute hosts.  They know nothing about floasting ips...which is to say, it doesn't matter if you use a floating ip or fixed ip to contact your host, you'll still hit the same security groups.15:31
*** amuller_ has quit IRC15:33
edlein nova api log its Caught error: Connection to neutron failed: Maximum attempts reached then File "/usr/lib/python2.7/site-packages/nova/api/openstack/__init__.py", line 119, in __call__ 2013-12-16 16:45:41.772 1432 TRACE nova.api.openstack     return req.get_response(self.application) 2013-12-16 16:45:41.772 1432 TRACE nova.api.openstack   File "/usr/lib/python2.7/site-packages/webob/request.py", line 1296, in send 2013-1215:34
kruskakliaha, a new patch-set, I get: GERRIT_BRANCH=master in my env.vars15:34
openstackgerritOleg Bondarev proposed a change to openstack/neutron: LBaaS: agent monitoring and instance rescheduling  https://review.openstack.org/5974315:35
edlecompute logs show Neutron client authentication failed: Connection to neutron failed: Unable to find the server at and Error: Connection to neutron failed: Maximum attempts reached  File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1037, in _build_instance 2013-12-17 09:31:40.537 21221 TRACE nova.compute.manager [instance: e4712dae-c8c9-429e-9e9d-7fda3638b2a6]     set_access_ip=set_access_ip) 2013-12-17 015:36
larsksedle: I don't see anything there that helps.  Sorry!15:36
larsksDo you see any errors in the neutron server logs?15:36
anteayakruskakli: well done15:37
anteayakruskakli: anything for topic branch?15:37
openstackgerritDan Prince proposed a change to openstack/neutron: Update the descriptions for the log cfg opts  https://review.openstack.org/6268715:37
John______Thanks larsks. So no iptables rules are define at a netns level, only at compute level?15:38
edlein neutron server logs i Mapping physical network extnet to bridge br-bond0 2013-12-17 08:36:52.359 19613 ERROR neutron.openstack.common.rpc.amqp [-] Exception during message handling, would that mess up communication with nova?15:38
anteayalarsks: are you active in #openstack at all?15:38
larsksJohn______: Well, there are no *security group* related iptables rules defined at a netns level.  All the security group rules are associated with linux bridge devices on your compute node.15:39
larsksanteaya: Occasionally.15:39
anteayalarsks: can I ask you to take this conversations to that channel please?15:39
anteayas/this/these15:39
John______Thanks larsks and sorry anteaya15:39
larsksSure.15:40
edlein l3agent logs i get ERROR neutron.common.legacy [-] Skipping unknown group key: firewall_driver15:40
anteayalarsks: thanks15:40
anteayaJohn______: I understand your position, so if we can get your questions answered in #openstack, that works best15:40
*** carl_baldwin has joined #openstack-neutron15:45
*** mlavalle has joined #openstack-neutron15:50
*** alex_klimov has quit IRC15:50
*** vkozhukalov has quit IRC15:51
anteayaanother call for reviews on https://review.openstack.org/#/c/21946/ the latest patch passed the check tests and it fixes a critical bug15:51
*** John______ has quit IRC15:52
*** salv-orlando has joined #openstack-neutron15:53
*** alexpilotti has joined #openstack-neutron15:54
openstackgerritSylvain Afchain proposed a change to openstack/neutron: Re-submit "ML2 plugin should not delete ports on subnet deletion"  https://review.openstack.org/6269615:54
*** jecarey has quit IRC15:56
salv-orlandomarun: it seems it is unless you enable load balancing15:57
marunsalv-orlando: ?15:57
salv-orlandobecause lbaas migrations will add the 'agents' table which ends up being missing15:57
marunsalv-orlando: ah, the migrations15:58
salv-orlandomarun: why that happened its a question mark for me too15:58
marunsalv-orlando: so it only affects people like me that don't configure devstack for lbaas15:58
mlavallebeagles: ping16:01
salv-orlandomarun: likewise16:01
beaglesmlavalle pong.. s'bout that time, yeah?16:02
mlavallebeagles: yeah16:02
markmcclainyep.. I think we're all here16:02
*** arosen-home has joined #openstack-neutron16:02
beaglesokay.. sweet16:02
arosen-homeHi sorry i was running a few min late.16:03
beaglesarosen-home: just in time :)16:03
beaglessooo...16:03
beaglesreally, a lot of the work I felt was required for nova-parity/deprecating nova-network has been happening16:04
openstackgerritArmando Migliaccio proposed a change to openstack/neutron: Add support for NSX/NVP Metadata services  https://review.openstack.org/4941516:04
beaglesmlavalle has been working on the API gaps and testing thereof16:04
beaglesor driving if that is a better word to use16:04
*** dhellmann has joined #openstack-neutron16:04
beaglesanteaya et al. have been driving getting the gate on the go16:04
beaglesand from reading mlavalle's older work on it and anteaya's they've got a handle on it so from the parity perspective... the question would be that whether those efforts are going to hit the goals that are required by the parity effort16:06
anteayaetherpad links, nova-parity: https://etherpad.openstack.org/p/icehouse-neutron-nova-parity-prelim-outline16:07
anteayatempest: https://etherpad.openstack.org/p/icehouse-summit-qa-neutron16:07
anteayabeagles: let's start with your evaluation16:08
anteayado you think the current efforts will hit the nova-parity goals?16:08
marunsalv-orlando: btw, am making good progress on dhcp agent rework.  the tests are the hardest part.16:08
salv-orlandomarun: they always are16:08
beaglesanteaya: if you are referring to the milestones, then I think it is obvious they do not16:09
marunsalv-orlando: shouldn't have to be :(  I've started being tougher in review on testing.  I think it should matter as much as the code16:09
beaglesanteaya: at least with respect to time frames... cuz that is all blown at this point16:09
anteayahow can we reframe it so that we acknowledge what work has been done16:10
beaglesif we are talking about details, I'm not sure that etherpad for the milestones is sufficient16:10
anteayaand is being done?16:10
mlavalleI think we need a sort of "checklist" or explicit "yardstick" that tells us when we have achieved parity16:11
beagles+116:11
mlavalleso we can all drive towards that goal16:11
anteayahere is my problem16:11
beaglesway back when I started with this https://wiki.openstack.org/wiki/NovaNetNeutronParity (in  a different form, mind)16:11
anteayaas a group neutron is great creating very detailed evaluations of status16:11
anteayathe issue is getting actual code to come out of this work16:12
anteayaI'm not in favour of another report16:12
beaglesme neither...16:12
anteayaso how do we increase the volume of work done in this area?16:12
beaglesa simple checklist of what needs to be done, who is doing it, when its done and if its verified...16:12
anteayasince actually producing code is the crux of the issue16:12
beaglesI'm not sure if we need to increase it so much as put it in a directed form16:13
anteayaor someone active in channel recrutiing people and answering questions16:13
anteayasince even the best tool with result in questions16:13
anteayaand if folks don't have a place to ask them, they give up16:13
beagleslet me put it a different way, with respect to parity, how do we know if we are done?16:14
*** HenryG has quit IRC16:14
markmcclainit's really 2 parts16:14
*** jistr has quit IRC16:14
markmcclain1 we have a solution for multi-host16:14
*** HenryG has joined #openstack-neutron16:14
markmcclain2 we have test parity with existing nova-net tests16:14
markmcclainespecially when we're proxying calls16:15
salv-orlandothere also some 'minor' features such as auto-assign floating ips that can be potentially classified as 'low-hanging-fruit'16:15
salv-orlandoand where we could leverage new contributors a lot. I have already assigned the one mentioned above16:15
salv-orlandoand following the dev16:15
salv-orlandobut if there were a list of high-priority features needed for feature-parity it would be better16:16
salv-orlandothis is of course as far as feature parity is concerned, which is also instrumental to testing parity16:16
anteayasalv-orlando: following up with the dev is great, mentoring counts for a lot16:17
*** garyk has quit IRC16:17
salv-orlandofor testing parity, I think the plan would be to sort out full isolation/parallel (and we're almost there), then have a detailed report of what we need for the full tempest job to run16:18
salv-orlandoon neutron16:18
beaglesis "quality of default implementation" implict in the test parity high level goal?16:18
salv-orlandothis would kind of produce also, as a side effect, a list of unsupported use cases, which will be hopefully small16:18
mlavalleso there it is, part of the yardstick is to get the full tempest job run, correct?16:18
salv-orlandoIdk perhaps I'm steering the conversation in the wrong direction.16:19
beaglesthe way I see it, there are two perspectives - complementary - but not the same16:20
beaglessimple feature parity vs. what it takes to deprecate nova-networking16:20
markmcclainmlavalle: yes we need to move away from the asymmetirc testing we've got now16:21
beaglesfrom an engineering perspective, the former is more palatable16:21
beaglesin the bigger picture, the latter is the more relevant16:21
*** SushilKM has joined #openstack-neutron16:21
beaglesdoes that make sense to everybody?16:23
salv-orlandoI think the former is just one dimension for measuring parity16:23
salv-orlandowhen you have parity along all dimensions, people would say it's ok to deprecate nova-network16:24
*** jecarey has joined #openstack-neutron16:24
beaglesnice way to put it16:24
salv-orlandoso - features, currently neutron supports more features than nova-ntetwork, but nova-net features are not a subset of neutron features16:24
salv-orlandosecond - quality. This is way harder to measure, but I think there's a general consensus that similar gate reliability would be a satisfactory measures16:25
mlavallesalv-orlando, exactly right… that's part of the challenge of getting the full tempest job run fixed16:25
salv-orlandomeaning you run the same jobs, and they have a similar success rate16:25
mlavallethings don't translate directly16:25
salv-orlandoI can't think of any other dimension for measuring parity now, anyone?16:26
* markmcclain runs to another meeting… will read scollback16:26
*** markmcclain has quit IRC16:26
beaglesunless it is implied by features, use-case is a dimension16:27
beagleseg. how can the features be combined and deployed16:27
beaglesthe rationale behind describing how FlatManager can be emulated in neutron is a use case16:28
beaglesI know I'm talking semantics here, but...16:28
*** jecarey_ has joined #openstack-neutron16:28
beaglesfeature parity alone does not imply that use-cases are met16:28
salv-orlandothat's fine. It's a dimension, albeit not linearly independent from the others16:29
* anteaya reminds people to click the topmost righthand button in an etherpad and add your name16:29
beaglese.g we have floating IPs but the FlatDHCPManager with L3 would be considered  broken from a user perspective16:30
salv-orlandofor instance I would consider multi-host a use case rather than a feature16:30
beagles+216:30
*** SushilKM has quit IRC16:30
salv-orlandoHow far are we from itemising features and use cases so that gaps can be easily identified and dealt with?16:31
*** jecarey has quit IRC16:31
beaglessome not far at all...16:32
beaglesI need to grab some bandwidth to figuring out how to best describe some of them, but I think I've alluded to them in https://wiki.openstack.org/wiki/NovaNetNeutronRecipes16:34
beaglesmulti-host remains a big ?16:34
beaglesbut...16:35
beaglesI apologize, I took this off the rails a bit...16:35
sgranmulti-host needs a VRRP gateway, IMHO16:36
beagleswhat I was really hoping to clarify in this discussion was whether mlavalle feels that he has the API/full-tempest-gateway stuff in hand ...16:36
*** Mierdin has joined #openstack-neutron16:36
beaglesand also anteaya...16:36
sgranDHCP agents can already be auto-scheduled to all compute hosts, for instance16:36
beaglesat one point I fretted about having to champion that myself and I was relieved to see others taking it ;)16:37
beagles(with respect to parity that is)16:37
anteayaI have been focusing on the gate and bugs16:37
mlavallebeagles: I expect to have the gap analysis for the API tests to be finished this week16:37
anteayamlavalle: but here is the thing16:37
beaglesif so then I feel comfortable focusing on the use-case thing etc.16:37
anteayaa great gap analysis isn't getting the gap closed16:38
*** SushilKM has joined #openstack-neutron16:38
anteayahow is it going getting new tempest tests written16:38
beaglesand contributing to mlavalle and anteaya's efforts, because without success in their efforts it's all for naught16:38
anteayaand merged?16:38
marunisn't gap analysis a necessary precursor to prioritizing?16:38
salv-orlandomlavalle: the bottom line of what anteaya suggest is to pipeline gap analysis and gap closing, I think16:38
anteayayes, we have to get some tests in tempest16:39
anteayaso far I have seen work from enikanorov EmilienM rosella_s yfried and jlibosva16:39
anteayafor tempest patches16:39
anteayahave a I missed anyone?16:39
mlavalleagree, with you, The gap analysis is good so we can invite other contributos to participate….16:39
salv-orlandoyes, but just to make sure I am not confused. Are we talking about "API tests"?16:39
salv-orlandoor are we including also "scenario tests" in this analysis16:40
anteayaI'm operating from the perspective that points on this etherpad need to be covered: https://etherpad.openstack.org/p/icehouse-summit-qa-neutron16:40
anteayamlavalle: seems to be focusing on the api tests, which is great, but we need a broader focus to address all the issues16:41
anteayamlavalle: do you want to stay focused on the api?16:41
mlavalleanteaya: not necessarilly. I want to do the best for the group. In our original conversation, we agreed I was going to do the gap analysis to drive to contributos to write api tests16:42
* beagles backs up...16:43
anteayamlavalle: oh, I was operating under the understanding that you were going to take on that task entirely16:43
anteayawhich includes tests being merged16:43
beagleswhat API are we talking about, neutron's API or the API that is exercised via nova?16:43
anteayathis might be my mis-understanding16:43
mlavalleanteaya: yes i can do that16:43
beagleswe need the former but the latter is essential16:43
anteayamlavalle: you can champion tests being merged into tempest?16:43
salv-orlandoI think we are perhaps keeping derailing this conversation. Perhaps we should let beagles lead the discussion.16:43
beagles:)16:44
beaglesokay... the discussion has been good and I appreciate it, but to save time I'll be direct16:44
mlavalleanteaya: let's continue this conversation after the meeting16:44
beagleswe need full exercising and vetting of the interaction between nova and neutron, that means the module that is in nova/networking/neutronv216:45
beaglesbehavior/testing etc all has to be vetted16:45
beagleswe need the use case thing16:45
beagleswe need the gates16:45
beaglesand full testing would be awesome, but outliers can be triaged16:46
beaglesand we need to be solid and reasonably fast for normal workflows16:46
beagles(for default implementation)16:46
beagleswho has what?16:46
beaglesI have use-cases16:46
arosen-homeI've been working on the interaction between nova <-> neutron lately. I can take lead on that.16:47
beaglessweet!16:47
salv-orlandoI have speeding up the ovs agent16:48
salv-orlandomarun has speeding and reliability for the dhcp agent16:48
salv-orlandothis much I know. I do not see at the moment issues needing intervention on the l3 agent16:48
salv-orlandonati-ueno, markmcclain and in part myself did several fixes in havana (it was kind of broken before)16:49
marunarosen-home: i'd like to talk to you about nova/neutron integration, maybe co-work this week?16:49
salv-orlandoI am also working on enabling parallel testing, and should deliver that by I-216:49
beaglesanteaya: you've got gates covered right?16:50
beaglesand mlavalle full tempest?16:50
arosen-homemarun:  I fly out tomorrow :/16:50
beagles(damn it is a crappy time of year to get stuff done)16:50
marunarosen-home: ah, next year then :D16:50
anteayabeagles: affirmative16:50
arosen-homemarun:  sure thing.16:50
marunarosen-home: i'll be back for the 6th16:50
arosen-homesorry guys but i have to run and catch the train. I'll  read back up when i reconnect .16:51
beaglesarosen-home: cheers, and thanks16:51
salv-orlandoadios arosen16:51
anteayaarosen-home: thanks for being here16:51
*** arosen-home has quit IRC16:51
anteayabeagles: if you need to see me do anything more or better regarding the gate, please tell me16:51
beaglesanteaya: no doubt ;)16:52
salv-orlandoI am pretty confident we can bring the various neutron agents making up the default framework to a decent reliability and scalability status16:52
beaglesoooo16:53
marunnothing like a rewrite ;)16:53
* beagles cuts and pasts16:53
salv-orlandobecause I think those specific items are covered16:53
beaglespastes16:53
beaglesmlavalle: what am I missing?16:53
mlavallebeagles: i can help with the full tempest job…. I thought someone else was taking tking care of that, but if that is not the case i'll glad to help16:54
mlavallecan I ask a stupid question?16:55
beaglesmlavalle: I don't want to dump it on you!!! :) Was it me that you thought was doing it? ;)16:55
beaglesfire away16:55
mlavallebeagles: yeah… but we can work together on it16:56
salv-orlandowe had rossella_s working on the full tempest job. she was doing some analysis of what items needs to be fulfilled16:56
beaglesmlavalle: okay.. cool... I had this feeling you taking it :) but I can keep it for sure.16:57
salv-orlandobut I had no update from here in a while. Perhaps she's been syncing with you guys?16:57
beaglesright rossella_s wasn't feeling well and couldn't make it today16:57
beagleslet's do it this way.. I'll keep it and hookup with you and rossella_s as soon as our tz's intersect again16:58
beaglesmlavalle: where are you TZ wise?16:58
mlavallebeagle rosella_s and I can synch up on that….. in any case i'll be glad to help16:58
mlavallestupid question: nova deprecation is not going to happen when we say we have achieved parity…. That decision is beyond us…. Do we have a buy in with those making the decision as to what parity means?16:58
beaglesfwiw: I'd like to see if I can scrounge some manpower for some directed efforts, so that would work out great16:58
beaglesmlavalle: you are right on that point...16:59
*** afazekas has quit IRC16:59
salv-orlandomlavalle: not able to answer that question. You might want a nova-core for that. From my perspective it's about filling feature/use case gaps and ensuring users can trust neutron as much as nova-network16:59
anteayamlavalle: including sdague and russellb in any nova-parity conversation would increase buy in on the result16:59
beaglesmlavalle: having arosen on board doesn't hurt... I didn't have much to report at the nova meetings the past two weeks16:59
edlehi larsks i fixed my issue i checked everything in the docs and was exhausted of what the issues can  be so i rebooted the server and that fixed it16:59
beaglesmlavalle: but this week I have something to say16:59
beaglesso... we can get buy-in17:00
anteayaedle: please chat in #openstack for support questions, thank you17:00
beaglesfwiw: that is about the least stupid question I think I've ever heard :)17:01
mlavalleanteaya: shouldn't that conversation somehting we should have quickly? So we are all pointing in the right direction?17:01
anteayamlavalle: sure17:01
anteayaI just need to know what your bottom line is17:02
anteayamy bottom line is tests in tempest17:02
anteayayou are doing good work17:02
*** rohit404 has joined #openstack-neutron17:02
anteayabut none of it counts for all of openstack unless it results in tests17:02
anteayaI just need to hear what you want17:02
mlavallemy bottom line is tests in tempest…. no oubt about it…. the gap analysis has been an exercise in trying to get more people to help, that's all17:03
anteayalet's evaluate it on those terms then17:03
anteayahow have you done in that regard?17:03
* beagles snickers17:04
anteayanot a questions to evoke snickers17:04
beaglesanteaya: open source is a tough gig in that respect17:04
anteayaa reality check17:04
anteayano kidding17:04
beaglesa lot of times it is a "if you build it they will come"17:04
anteayaparticularly in this neighbourhood17:04
anteayabe we have to start with being honest with ourselves and with each other17:05
* beagles nods17:05
anteayabeagles: sure, if you are ploughing up your own corn field17:05
anteayabut if we aren't getting the results we need when we need them17:05
anteayawe have to start by saying so17:05
*** garyk has joined #openstack-neutron17:05
anteayaand I can't put words in your mouth mlavalle17:06
anteayaso I have to hear what you have to say in this regard17:06
anteayaplease17:06
beaglesthat's good grist actually...17:06
mlavallenot well, there are not enough test in tempest yet17:07
beaglesI'll reach out to see if there are any resources that can be focused17:07
*** Abhishek_ has joined #openstack-neutron17:07
anteayamlavalle: great, thanks for stating my own evaluation of the situation17:07
enikanorovmlavalle: I have two engineers in my team (in addition to myself) who can help with tempest tests17:07
beaglesno promises, but I can at the very least complain17:07
enikanorovand in fact already working on some patches17:07
anteayamlavalle: do you have any thoughts on how to improve the situation, or would you like some suggestions?17:07
enikanorovmostly on load balancer tests right now17:08
anteayaenikanorov: do you have urls for those patches?17:08
enikanorovanteaya: sure. Let me find17:08
anteayathat would help mlavalle track progress17:08
anteayaenikanorov: thanks17:08
*** jlibosva has quit IRC17:08
anteayamlavalle: do you have any thoughts for improvement or would you like some suggestions?17:09
mlavalleanteaya: the gap analysis is an effort of making clear what needs to be done, so others can help. In that way, it is not just me…. There is alot that needs to be implemented in the api tsts17:09
mlavalleI'm also open to suggestions17:09
anteayamlavalle: okay here are my suggestions17:10
anteayatrack the names of anyone who has submitted a neutron tempest patch17:10
anteayacheck their review page everyday17:10
enikanorovactually it's easier to give a link to their gerrit queue, since they both have > 2 two tempest patches on review:17:10
enikanorovhttps://review.openstack.org/#/dashboard/7249 https://review.openstack.org/#/dashboard/729317:10
anteayaensure they have all they need in terms of reviews to get their patch merged17:10
anteayaif you don't see activity on a patch, ask them why, offer to help with blocks, co-ordinate with -qa to get questions answered17:11
anteayaalso ask for reviews on any patches ready to be merged and get them merged17:11
anteayawhen current developers find that you are supportive and will drive their (tested and qualified) patches into master17:12
anteayathey will be motivated to submit another patch17:12
anteayado this work the first thing of everyday17:12
anteayaenikanorov: great17:12
anteayaare ann and elena in channel right now?17:13
mlavalleanteaya: good suggestions….. how about finishing the gap analysis?17:14
enikanorovno, i think they working day has ended like an hour ago17:14
anteayamlavalle: can you do both?17:14
enikanorov*their17:14
anteayaenikanorov: okay thanks, can you ask them to ping both myself and mlavalle in channel tomorrow17:14
*** jorisroovers has quit IRC17:14
mlavalleanteaya: sure…. I just want to make sure that part is still considred valuable…. since we are in feedback mode17:14
anteayaand post any blockages they are finding in their work17:14
anteayamlavalle: if you can do both, my personal vote is on both, with tests in tempest getting first priority17:15
anteayaanyone else with an opinion?17:15
enikanorovok, i'll tell them17:16
anteayaenikanorov: thanks17:17
beaglesI'm vascillating on priority AND assignment.. if it were possible I'd suggest mlavalle prioritize finishing the gap and see if makes more sense to get somebody to shepherd the test creation17:17
beaglessomebody else that is17:17
anteayado we have any volunteers for shepherding test creation?17:17
beaglesbut that's just because it sucks to have a chicken and egg problem when the chicken is half created17:17
beagleslet's look for one17:18
anteayabeagles: ah if someone where interested they would be following along17:19
*** ashaikh has joined #openstack-neutron17:19
anteayawere17:19
mlavallebeagles: what do you see me doing besides the test sheperding?17:19
beaglescertainly out of the pool of likely candidates, they are not all listening at the moment17:19
anteayahow much time are we going to give to that task?17:19
anteayawe have about 3 weeks of actually working time remaining before i217:19
anteayataking out holidays as actual working time17:20
anteayaI will be offline for a significant chunk of that17:20
beaglesmlavalle: I don't know :) In all seriousness, if it is most appropriate that you shepherd it then by all means.17:21
anteayaI'm not against handing off a task to a willing volunteer, by all means, delegation and sharing is the only way to meet our goals17:22
anteayabut waiting for said volunteer to show up is very unproductive17:22
beaglesno doubt17:23
beaglesany volunteers for such an effort would have to be proactively sought out17:23
anteayaI'm all for that17:23
anteayabut in the mean time17:23
mlavalleyeah, that's the idea of the gap analysis…. get other people to write tests…. and to tell you the truth, I am not waiting for any volunteers…. I see my communicty job as getting neutron tests in tempest17:23
beaglesmlavalle: cool17:24
anteayaare you able to sheperd patches right now?17:24
anteayamlavalle: ^17:24
mlavalleif you mean what you described about reviewing and guiding people, yes17:24
anteayagreat17:25
anteayathanks17:25
anteayalet me know how I can support you17:25
mlavalleand also, once the I finsh the gap analysis, writing api tests myself17:25
anteayagreat17:26
mlavallemy focus lately on the gap analysis has been an attemot to scale the effort up17:26
anteayadid we need to discuss anything else on this topic?17:26
anteayaI understand17:26
beaglesthe API coverage or parity?17:27
anteayawe seem to have dicussed both17:27
beagles:)17:27
mlavallebefore you and Beagles go, I want to know who is working on the ful tempest gate job. I think that is importnat and thought that was being covered17:27
anteayaI think salv-orlando felt rosella_s was but hasn't heard from her and she is sick today17:28
anteayamlavalle do you and beagles want to talk to her about that and find out if she is indeed working on it, and if yes what her status is?17:29
mlavalleA couple of weeks ago, you asked me to talk to her and I did17:29
anteayadid you follow up with her since that time?17:29
mlavalleI was hoping today's meeting was the ocassion…. but since she is sick, i'll follow up with her17:29
anteayamlavalle: thanks17:30
mlavallespecifically, I will probe whether she thinks she is the point person for that…. If not, that's ok, but we need to know17:30
anteayaif you can do so in channel, so much the better then the rest of us can read the logs/scrollback and follow along17:31
anteayayes17:31
anteayaI totally agree17:31
anteayawe need to know what her understanding of her commitment is17:31
anteayaher bottom line in this regard17:31
anteayanot to change that but to address gaps if need be17:31
mlavallecorrect17:32
anteayagreat17:32
beaglesat the moment the full tempest run chokes on similar things to the smoke testing17:32
beaglesthe multiple network thing...etc17:32
anteayabeagles: do you have any urls for the chokes?17:32
beaglesto properly assess each test at the moment would be to run each test in isolation17:33
beagleswhat?17:33
beaglesdid I just write?17:33
beaglesgah17:33
* anteaya stands by17:33
beaglesbasically you would have to run each test independently17:33
beaglesand no17:33
beaglesbut you know the deal17:33
anteayaokay17:33
anteayawell actually I don't17:33
beaglesif a previous test screws up the cleanup, the subsequent tests do not run17:34
beaglesbecause there are multiple networks for that tenant17:34
anteayaah17:34
beaglesand because neutron doesn't order networks, then it cannot create by default order and requires that the client specify one17:34
anteayais rossella_s aware of this situation?17:36
anteayaor do we know?17:36
anteayamlavalle beagles are the two of you available for a daily status meeting?17:36
anteayaat least for the rest of this week?17:36
anteaya2200 utc would work fine for me17:36
mlavallebeagles: to talk about the full tempest job?17:37
mlavalleanteaya^^^17:37
anteayato talk about progress17:37
anteayaon any issue dealing with nova-parity and tempest17:38
anteayadkehn: where do you clone from for your devstack?17:39
anteayagit.o.o or github?17:39
mlavalleThursday I won't be available…. tomorrow and friday I'm fine17:39
dkehnanteaya: trunk17:39
beaglesI think same17:39
beaglesalso not avail today17:39
anteayabeagles: we did today already, let's talk tomorrow and friday17:39
anteayaand thanks17:39
dkehnanteaya: the only thing that is manipulated there is the lcoalrc17:39
dkehns/lcoalrc/localrc17:40
beagleswhat.. you aren't going to get loads of stuff done this afternoon!17:40
anteayadkehn: I'm reading your comment on https://review.openstack.org/#/c/21946/17:40
anteayaand I had a conversation yesterday, with mattymo about him not seeing all the recent commits in his git log when he cloned from github17:41
anteayadkehn: do you see https://review.openstack.org/#/c/57600/ in your devstack git log?17:41
dkehnanteaya: basically if you don't mock the udevadm it no work locally17:41
dkehnhaven't checked.17:41
anteayak17:41
*** zoresvit has quit IRC17:41
dkehnanteaya: I was assuming it was merge, says it was merged, until I tested it here and then checked the code17:42
anteayalet's look at git logs17:42
anteayaI'll check git.o.o17:42
*** zoresvit has joined #openstack-neutron17:43
anteayadkehn: merged: http://git.openstack.org/cgit/openstack/neutron/log/?qt=grep&q=I0e16295be66513c2257831bf62fd6a0c19f3b8a417:43
*** vkozhukalov has joined #openstack-neutron17:44
dkehnanteaya: ok, let me do a freesh clone and see if its there then I'll do a fetch and see if its there again,17:45
anteayadkehn: sorry here is the merge: http://git.openstack.org/cgit/openstack/neutron/commit/?id=512b4e71fb4bc864e240fe34286ce67c7332da4c17:45
anteayadkehn: k17:45
dkehnanteaya: this is what I did before17:45
yfriedmarun: I was told that a +1 from a neutron dev will get my tempest patches higher priority for review. can you please take a look? I tagged you on all of them.17:46
dkehnanteaya: without the the checking part17:46
*** ygbo has quit IRC17:46
*** alagalah has quit IRC17:46
anteayayfried: link to urls? mlavalle and I would like to help you get your tempest patches merged17:47
anteayaactually linking mlavalle to all your patches as well would be good, he is supporting neutron tempest patches17:48
yfriedhttps://review.openstack.org/#/c/55101/17:48
yfriedhttps://review.openstack.org/#/c/55146/17:48
yfriedhttps://review.openstack.org/#/c/60757/17:48
yfriedhttps://review.openstack.org/#/c/56889/17:48
yfriedhttps://review.openstack.org/#/c/62702/17:48
yfriedhttps://review.openstack.org/#/c/62697/17:48
*** SumitNaiksatam has quit IRC17:48
yfriedanteaya: mlavalle tnx17:48
yfriedmlavalle: what's you're name on gerrit? can't find it to tag you17:49
anteayamiguel17:49
mlavalleyfried: minsel17:49
anteayaah sorry17:49
*** zoresvit has quit IRC17:49
anteayadid I spell your first name correctly at least?17:49
anteayaI am a horrible speller17:49
mlavalleanteaya; mi name is Miguel….. minsel was assigned to me by Launchpad when I originally signed up…. I don't know why17:50
yfriedmlavalle: tnx17:51
yfriedmlavalle: you can expect me to spam you with tempest patches from now on..17:51
yfried:)17:51
anteayayfried: go go go17:51
mlavalleyfried: that's coll… that's what we want :-)17:52
mlavallecool^^^17:52
*** jlibosva has joined #openstack-neutron17:52
anteayajlibosva: hello, how goes the grenade patch?17:53
anteayadid you get my message I left in the comments17:53
yfriedanteaya: mlavalle: btw - since tempest-network is my main focus currently, I would love pointers, suggestions, and ideas for tests17:54
anteayayfried: awesome17:55
anteayawhat are you using for guidance so far?17:55
jlibosvaanteaya: I found problem probably in ovs17:55
anteayajlibosva: okay, what do you want to do about that?17:55
*** markmcclain has joined #openstack-neutron17:55
jlibosvaanteaya: I'm trying to figure out why floating_ip test is failing17:55
anteayado you need to file a bug? or talk to someone about it?17:56
anteayajlibosva: okay let's start by linking to the failing test so others can follow along17:56
jlibosvaanteaya: I want to talk to someone, I have a lot of failed to get flags for network device qr-7f907021-82: No such device in ovs log17:56
jlibosvathe ports are in ovs-vsctl though17:56
anteayajlibosva: great17:56
*** nati_ueno has joined #openstack-neutron17:56
anteayajlibosva: let's have a link to something17:57
anteayaso the conversation can focus on the stacktrace17:57
yfriedanteaya: I was using our (RedHat) test plan but I think I got the basic stuff done.17:57
anteayayfried: okay, mlavalle is going to look at your patches and then he can better asses17:57
anteayayfried: have you seen this etherpad: https://etherpad.openstack.org/p/icehouse-summit-qa-neutron17:57
jlibosvaanteaya: you want me to put the logs to pastebin or somewhere?17:57
anteayajlibosva: yes please17:58
yfriedanteaya: mlavalle: I'm also using this to coordinate but so far I'm the only one - https://blueprints.launchpad.net/tempest/+spec/neutron-advanced-scenarios17:58
marunyfried: ok17:58
*** ihrachyshka has joined #openstack-neutron17:58
yfriedso me, myself, and I are working in perfect coordination17:58
*** safchain has quit IRC17:58
sdagueso danpb brought up an interesting point in nova, nova doesn't specify a timeout for ovs commands at all (it waits forever), which is a different approach than on neutron -  https://review.openstack.org/#/c/61105/417:59
*** ihrachyska has quit IRC17:59
sdaguehas anyone thought about making that timeout super huge, like 300s, so only gets hit in the worse possible cases17:59
anteayayfried: well perfect coordination is nice, can you add your name to the scenario tests on the etherpad please, as well as a link to the blueprint and your patches18:00
dkehnanteaya: figured it out, din't do a rebase18:00
dkehnanteaya: will update the review18:00
*** zz_ajo is now known as ajo18:00
anteayadkehn: so the issue was local to you?18:00
anteayadkehn: thanks18:00
yfriedanteaya: I see someone already wrote my name18:01
anteayamarkmcclain: sdague poses a good question if you are around18:01
anteayasalv-orlando: ^18:01
anteayayfried: we don't let good workers get passed us18:01
anteaya:D18:01
*** jecarey_ has quit IRC18:01
markmcclainsdague: we could make the timeout larger18:02
anteayayfried: I don't see your name under scenario tests, just at the bottom of the etherpad in the list18:02
salv-orlandoin a meeting will get back at you later18:02
*** nati_uen_ has joined #openstack-neutron18:02
dkehnmarkmcclain: any luck with the devstack, from yesterdays migration issues?18:02
mlavallemarun: I am going to review yfried patches now, but a core Neutron reviewer like you will have more weight in getting his patched merged. Are you going to take a look on them?18:02
marunmlavalle: i will18:02
mlavallemarun: thanks18:02
yfriedanteaya: tnx for the compliment, but it seems to me that in this area you don't have much choice :)18:03
anteayayfried: buddy you are singing my song18:03
yfriedanteaya: I'm right there under "Scenario Tests"18:03
sdaguemarkmcclain: the nova objections were basically that small timeouts would actually cause races, and if ovs was deadlocking for some reason, that's a different bug18:04
*** nati_uen_ has quit IRC18:04
*** ian13 has joined #openstack-neutron18:04
anteayayfried: I'm blind, yes you were there all along18:04
*** nati_uen_ has joined #openstack-neutron18:04
*** nati_uen_ has quit IRC18:05
yfriedanteaya: now I just need to see what is this doc and what am I listed for. hope no one has dibs on my kidney without asking me18:05
anteayanati_ueno: nice work on your patch18:05
*** nati_ueno has quit IRC18:05
*** nati_uen_ has joined #openstack-neutron18:05
anteayayfried: don't answer any craigslist ads18:05
openstackgerritrcurran proposed a change to openstack/neutron: *** PROPOSAL ONLY. ***  https://review.openstack.org/6158318:06
*** ian12 has quit IRC18:07
anteayanati_uen_: yfried would like https://review.openstack.org/#/c/21946/ tested against https://review.openstack.org/#/c/62702/18:08
anteayanati_uen_: are you able to coordinate with him to make this happen?18:08
*** jdev789 has quit IRC18:08
markmcclainsdague: the other downside with large timeouts is that they hide commands which aren't executing fast enough18:12
*** clev has joined #openstack-neutron18:12
markmcclainsometimes those indicate other problems18:12
sdaguemarkmcclain: that's true, but "fast enough" is easy to prematurely shoot something in the head as well18:13
sdagueanyway, I wanted to bring up the thought, because not having an ovs timeout on nova hasn't seemed to cause a problem18:13
*** ian13 has quit IRC18:14
*** ashaikh has quit IRC18:15
*** dhellmann is now known as dhellmann_18:17
*** suresh12 has joined #openstack-neutron18:20
*** SumitNaiksatam has joined #openstack-neutron18:21
*** harlowja_away is now known as harlowja18:22
anteayajlibosva: waiting to hear from you when you have something18:23
anteayado you have to run the tests again to get the stacktraces?18:24
*** terry_howe has joined #openstack-neutron18:24
jlibosvaanteaya: I;m on meeting18:24
jlibosvaanteaya: no, it happens after stack.sh18:24
jlibosvaanteaya: http://paste.openstack.org/show/55182/18:24
anteayagreat, I'll look at the paste, thanks18:25
openstackgerritrcurran proposed a change to openstack/neutron: Calls in delete methods should be in reverse order as create  https://review.openstack.org/6158318:26
terry_howeI'm working on the unified CLI and it seems to me the neutron CLI command dhcp-agent-network-add would be better called net-dhcp-add18:28
terry_howedoesn't it make more sense to add DHCP agents to networks than networks to DHCP agents?18:29
anteayacarl_baldwin: are you available for some questions?18:29
carl_baldwinyes18:29
anteayacarl_baldwin: jlibosva is working on this patch: https://review.openstack.org/#/c/58695/18:29
anteayaawesome18:29
anteayaand he is hitting some walls18:29
anteayacarl_baldwin: here is a paste from running stack.sh: http://paste.openstack.org/show/55182/18:30
anteayahe needs some help addressing a floating ip issue18:30
anteayahe is in a meeting atm but the grenade patch is very important18:30
anteayaif you could help him with it we would both be greatful18:31
anteayahi terry_howe do you have a link to a patch or blueprint?18:32
anteayaI just give better responses if I can see the same thing you are working from18:32
carl_baldwinanteaya: I'll take a look.18:33
anteayacarl_baldwin: thanks18:33
*** vkozhukalov has quit IRC18:36
*** fouxm has quit IRC18:37
*** vkozhukalov has joined #openstack-neutron18:37
*** fouxm has joined #openstack-neutron18:38
*** fouxm has quit IRC18:38
*** Abhishek_ has quit IRC18:38
*** networkstatic has joined #openstack-neutron18:38
mlavalleyfried: are you aware of isolated credentials?18:41
*** alexpilotti has quit IRC18:42
*** jistr has joined #openstack-neutron18:44
*** ijw has joined #openstack-neutron18:44
*** garyk has quit IRC18:49
*** garyk has joined #openstack-neutron18:49
*** edle has quit IRC18:53
*** nati_ueno has joined #openstack-neutron18:53
*** networkstatic has quit IRC18:56
*** nati_uen_ has quit IRC18:57
*** ashaikh has joined #openstack-neutron18:57
*** dhellmann_ has left #openstack-neutron18:58
*** SushilKM__ has joined #openstack-neutron18:58
*** SushilKM has quit IRC18:58
*** networkstatic has joined #openstack-neutron18:58
terry_howeanteaya:  I'm thinking of mapping the neutron client commands like this:19:01
terry_howehttps://wiki.openstack.org/wiki/OpenStackClient/Commands#DHCP_Agent19:01
terry_howejust not sure that entirely makes sense to implement it that way19:01
anteayaterry_howe: thanks just heading into a meeting, will look and respond19:01
anteayathanks for the link19:01
jlibosvacarl_baldwin: hi19:04
jlibosvacarl_baldwin: have you seen the errors from http://paste.openstack.org/show/55182/ before?19:05
*** salv-orlando has quit IRC19:05
enikanorovterry_howe: agents host networks, hence cli command name19:05
carl_baldwinjlibosva: Can you give me a specific line number to look at.  There is a lot in that paste.19:06
enikanorovterry_howe: while openstack client is not widely used it is particular project clients which driver usage patterns and names. It doesn't make sense to change cli command name in neutron client19:07
*** ihrachyshka has quit IRC19:07
enikanorov*which drive19:07
jlibosvacarl_baldwin: oh, sure. I think it tries to create a port in ovs (line 165) but then on line 176 you can see that some ioctl calling failed19:08
*** clev has quit IRC19:09
jlibosvacarl_baldwin: I have problems that dhcpdicovery from instances don't get to router nor dhcp namespace19:10
*** nati_ueno has quit IRC19:10
*** nati_ueno has joined #openstack-neutron19:13
carl_baldwinjlibosva: I see those errors in the log.  This isn't something that I have seen before.  Can you confirm that the devices do exist?  Looks like this error is occurring with a number of tap devices.  I also see the same error with some qr-* and qg-* devices.19:15
jlibosvacarl_baldwin: I can see them in ovs-vsctl show19:17
carl_baldwinjlibosva: How about "ip addr show" ?19:18
jlibosvacarl_baldwin: nope19:18
jlibosvacarl_baldwin: just ovs bridges19:19
*** ihrachyshka has joined #openstack-neutron19:20
carl_baldwinI would except to see them in "ip addr show".  I'll admit, though, that my knowledge of the ovs plugin is limited.  I've only recently started to use it in devstack.19:21
*** ashaikh has quit IRC19:23
carl_baldwinjlibosva: Is it possible that we somehow got in to a network namespace somewhere along the way where we shouldn't be?19:23
carl_baldwinjlibosva: Forgive me if I missed some context along the way that would answer my questions.19:23
jlibosvacarl_baldwin: you are right. I can see the one of tap devices in dhcp namespace. But I think that's correct.19:25
*** rpodolyaka1 has joined #openstack-neutron19:25
jlibosvathe one, that reported No device found19:25
*** jdev789 has joined #openstack-neutron19:26
yfriedmlavalle: I know it's a field in the conf that's supposed to allow parallel testing. and that all I know19:27
terry_howeenikanorov I'm not asking to change the neutron cli command name, I'm asking if what I proposed for OSC makes sense19:29
carl_baldwinjlibosva: Right, I think that it is correct that you can see that in the dhcp namespace.  Also, my expectation that you can see it in the default namespace may not be correct with the ovs plugin or driver.  Again, my experience with ovs is limited.19:30
*** harlowja is now known as harlowja_away19:30
enikanorovit may make sense, but it vice versa of what neutron cli has so it will create confusion for users i believe19:30
jlibosvacarl_baldwin: also the logs might not be cause of the issue I run into...I think. It might be security groups as well, right?19:32
jlibosvacarl_baldwin: packets can be thrown away before they enter ovs19:32
carl_baldwinjlibosva: You could be right.19:33
*** dave_tucker_ has joined #openstack-neutron19:38
*** jdev789_1 has joined #openstack-neutron19:39
anteayamestery: any comments for the open discussion in -meeting regarding multi-node testing?19:41
mesteryanteaya: Nothing this work, no.19:42
anteayak19:43
*** jlibosva has quit IRC19:45
*** jlibosva has joined #openstack-neutron19:46
roaetwhat was the magic to fix the lbaas devstack failure thing? add lbass to the localrc where?19:47
*** dave_tucker_ has quit IRC19:48
*** fouxm has joined #openstack-neutron19:49
rpodolyaka1anteaya: hey! did you want to discuss something?19:52
*** fouxm has quit IRC19:53
anteayarpodolyaka1: you had a patch you needed some attention on19:53
anteayacan you link to it please?19:53
*** fouxm has joined #openstack-neutron19:53
rpodolyaka1https://review.openstack.org/#/c/61677/119:53
rpodolyaka1Yong's patch19:53
anteaya7 minutes left in -infra meeting19:53
anteayayou are welcome to outline how we can help you19:54
rpodolyaka1just review it :)19:54
enikanorovit's has -1 from Mark19:54
rpodolyaka1I left some clarifying comments there19:55
rpodolyaka1yep19:55
rpodolyaka1so I might be wrong19:55
enikanorovi guess the bottom line is whether to allow to modify existing migration19:55
rpodolyaka1that's I want more eyes to review it19:55
rpodolyaka1*why19:55
*** gdubreui has joined #openstack-neutron19:56
*** fouxm has quit IRC19:56
enikanorovmarkmcclain: can we discuss https://review.openstack.org/#/c/61677 ? I think Roman has presented good analysis of different cases, and it justifies the approach taken in this patch19:56
*** gdubreui has quit IRC19:56
*** gdubreui has joined #openstack-neutron19:56
*** networkstatic has quit IRC19:56
*** gdubreui has quit IRC19:56
*** SushilKM__ has quit IRC19:59
markmcclainenikanorov: the fact still remains that we cannot revise released migrations19:59
*** networkstatic has joined #openstack-neutron19:59
*** SushilKM__ has joined #openstack-neutron19:59
dkehn //review.openstack.org/#/c/57600/) as one would expect, but after doing a fetch, with not merge issues its gone. I'm sure it19:59
enikanorovmarkmcclain: why?19:59
markmcclainit breaks continuity for those following trunk or stable/havana19:59
enikanorovright, but stable/havana doesn't work for ml220:00
enikanorovbecause the migration is broken20:00
rpodolyaka1enikanorov: in fact, it does...20:00
markmcclainit does for those running create_all()20:00
enikanorovdoesn't it make sense to fix it in stable too?20:00
rpodolyaka1ML2 works only due to create_all()20:00
enikanorovah, ok, I see20:01
rpodolyaka1so why can't we fix this migration in-place? (it's a bad habit, of course, but can't this be an exception?)20:01
rpodolyaka1ML2 would be broken, if create_all() failed20:01
rpodolyaka1so for existing installations the fix will be no-op20:02
rpodolyaka1because that's what we need20:02
rpodolyaka1and we could fix new installations properly20:02
rpodolyaka1even by a dirty hack like patching existing migrations20:02
rpodolyaka1so my point is - users would have noticed their ML2 not working long time ago20:04
rpodolyaka1both trunk chasers and stable/havana ones20:04
rpodolyaka1neutron just woudn't be usable20:04
rpodolyaka1as this migration is almost one year old, we have ML2 merged for a few months now20:04
*** gdubreui has joined #openstack-neutron20:08
anteayadkehn: is you above comment a ghost from the past?20:09
*** ashaikh has joined #openstack-neutron20:09
dkehnanteaya: hmm from the past20:10
anteayarpodolyaka1: the problem for advocating for the breaking of some rules to shoehorn a patch in, is that this approach has kind of been the status quo20:10
dkehnanteaya: past meaning an hour or so ago?20:10
anteayaa situation which I am trying hard to change and fortunately am seeing good results20:10
anteayadkehn: yeah I think that is the time frame when that comment was applicaple20:11
dkehnyepper20:11
*** vkozhukalov has quit IRC20:11
anteayarpodolyaka1: so personally I can't advocate for a relaxing of the rules for one exception20:11
anteayaimportant as that exception might be20:11
anteayarpodolyaka1: is there any other option on the table that will help you achieve your goals?20:12
rpodolyaka1anteaya: no, thank you!20:12
anteayaokay thanks, if you want to talk again please do ping20:12
rpodolyaka1cool!20:13
anteaya:D20:13
*** harlowja_away is now known as harlowja20:14
*** clev has joined #openstack-neutron20:15
enikanorovthe exception could be preferable because the patch does the job in a better way then the fix which floows the rules, that's it20:15
enikanorov*follows20:15
*** salv-orlando has joined #openstack-neutron20:16
*** alexpilotti has joined #openstack-neutron20:17
*** mtaylor is now known as mordred20:20
*** suresh12 has quit IRC20:22
*** jdev789 has quit IRC20:23
*** jdev789_1 has quit IRC20:23
yfriedmlavalle: can you please show me how to use tenant isolation instead of main/alt tenants?20:25
mlavalleyfried: sure, hang on a minute20:26
anteayaenikanorov: if you can make a convincing argument, that perhaps includes addressing a need to change the rules then let me know how I can help you set up that discussion20:27
sc68calmarkmcclain: Is there any current use for the external property of a network, for v6?20:27
markmcclainsc68cal: possibly yes20:28
sc68calwondering if a combo of enable_dhcp=false on a v6 subnet, and external=true on the network could be used to mean that a provider router is announcing RA's20:28
markmcclainI'd rather have an explicit setting on the subnet20:28
markmcclainotherwise the behavior seems a bit too subtle20:28
sc68calok - perhaps subnet_modes = ['provider-slaac'] ?20:29
ijwNot external, but provider:… presumablyt20:29
ijwexternal is slightly different20:29
enikanorovanteaya: the arguments were presented in the review. rpodolyaka1 did the analysis of different cases (including 'trunk chasers'). The alternative solution is possible, but it will require migration rearrangement as far as i understand. which is also not desirable20:29
sc68calijw: Yeah the only real use I know for external is floating ips20:30
ijwI think for v4 this works by disabling DHCP and setting the DHCP server address, and I was trying to come up with something that worked the same way20:30
*** jlibosva has quit IRC20:30
mlavalleyfried: can you open a copuple of modules? let's look at the code. tempest.scenario.manager and tempest.common.isolated_creds20:30
ijwsc68cal: Yeah, that's basically it, I think, and it's not really v6 relevant or appropriate because for v6 routing you need a nexthop, not an address20:31
ijw(when you don't have NAT)20:31
ijwOn the IPv6 front, people, look at https://docs.google.com/document/d/1rOBOOu_OwixMStm6XJOb5PKkJA6eFbL_XCE7wlTfaPY/ - it's intended as where we could take it, not a 'we must do all of this by Icehouse', and in particular I think we'd skip the internal DHCP server stuff20:32
sc68calJust soo close I can taste it - instances get v6 addresses and work correctly, but openstack is clueless about the prefix being advertised northbound20:33
*** jecarey has joined #openstack-neutron20:33
sc68calbecause the moment you add a v6 subnet in openstack the whole thing comes crashing down :)20:33
anteayaenikanorov: okay, thanks for the summary20:33
*** SumitNaiksatam has quit IRC20:34
sc68calijw: do you want to share that google doc on the ML?20:35
sc68calwe'll def talk about it in the subteam meeting20:35
*** suresh12 has joined #openstack-neutron20:35
geekinutahcarl_baldwin: you around?20:36
carl_baldwingeekinutah: yes20:36
ijwYeah, can do.  I was just warming up with it, really20:36
geekinutahI was just looking at https://review.openstack.org/#/c/58017/20:36
yfriedmlavalle: can we talk in 15min?20:37
geekinutahI'm wondering, the whole ip recycling behavior doesn't seem appropriate for an API20:37
mlavalleyfried: yeah, ping me20:37
geekinutahhave you ever considered moving it out and having it be triggered on a more periodic basis?20:37
yfriedmlavalle: are you on US time?20:37
mlavalleyfried: I am in us central time. how about you?20:38
yfriedIsrael.20:38
geekinutahso the API could send a notification or something to another service or thread rather than trying to deal with it in it's runtime20:39
mlavalleyfried: ok, i'll be here for a good while20:39
markmcclaingeekinutah: IP reclamation is not easy20:39
markmcclainwith large ranges we can delay20:40
markmcclainwith smaller ranges collection would need to occur more synchronously20:40
geekinutahyeah, I'm just trying to think around how to do it without serializing other API stuff20:40
carl_baldwinMy thinking was that if an IP has just been released to a pool then one should be immediately available.20:42
yfriedmlavalle: im back20:43
geekinutahoh wait, your patch will only serialize on subnets that need rebuilding20:43
geekinutahI misread it first time around20:43
yfriedmlavalle: both modules are open20:44
carl_baldwingeekinutah: Right, and rebuilding will not come around very often unless the subnet is nearly full.20:44
mlavalleyfried: the big idea is to provide a set of user credentials for each test. That way, each test will run in it's own tenant and won't interfere with others. That is important if we want to run tests in parallel in the gate20:44
* anteaya is afk for a bit20:45
carl_baldwin... or more precisely "unless the pool is nearly exhausted"20:45
mlavalleyfried: right now, tenant isolation is not enabled in the gate for neutron. But we hope it will be soon, to enable parellel testing20:45
* carl_baldwin is running out for a bike ride. Beautiful weather here in Colorado.20:46
mlavallethe isolated_creds module has methods to generate credentials for a primary user, an admin user and a tenant user20:46
*** rpodolyaka1 has quit IRC20:46
mlavalleI menat alt user (last one)20:46
yfriedmlavalle: ok20:47
mlavalleyfried: if you look at class OfficialClientTest in manager.py, there is a method credentials. It generate credentials for the primary user, i.e. demo20:48
mlavalleyfried: this happens if tenant isolation is enabled. Otherwise, it just goes to the config file for the demo credentials.20:49
mlavalletake a look20:49
beaglesmlavalle: quick question.. how easily is that stuff used for a test that itself uses multiple tenants? is it pretty much obvious once you take a peek?20:50
mlavallebeagles: it's pretty easy. you just need to get used that your demo user, alt user and admin user are coming from a class, instead form the config file20:51
beaglesmlavalle: cool20:51
mlavalleyfried: are with me?20:52
yfriedyeah20:52
yfriedlooking at "get_primary_creds"20:52
yfriedmlavalle: ok20:52
mlavalleyfried: now look at NetworkScenarioTest(OfficialClientTest), which inherits from OfficialClientTest20:53
openstackgerritSean M. Collins proposed a change to openstack/neutron: Create a new attribute for subnets, to store v6 dhcp options  https://review.openstack.org/5298320:53
yfriedmlavalle: ?20:54
mlavalleyfried: you will see in the setUpClass method that the tenant id is initialized either from isolated credentials or from the config file20:54
mlavalleyried: for the demo user20:54
mlavalleyfried^^^20:54
yfriedok20:55
mlavalleyfried: in isolated)ceds thera are parallel methods for the alt user: generate credentials, get the tenant id, etc20:55
mlavalleyfried: look at get-alt_creds for example20:56
mlavalleget_alt_creds^^^^20:56
*** fouxm has joined #openstack-neutron20:57
*** SushilKM__ has quit IRC20:58
mlavalleyfried: so what you need to do in your test or somewhere in the classes in manager.py is to check if tenant isolation is enabled and if it is, use isolated_creds to generate the alt_user. Otherwise, you go to the config file20:59
yfriedmlavalle: why aren't there wrapper methods that return creds based on "isolation" flag - ie - you either get your isolated creds from this method or you get them form file20:59
mlavalleyfried: well, i didn't write the credentials isolation piece. But I suspect that we wanted to maintain backwards compatibility21:00
ijwsc68cal: mail sent21:00
*** fouxm has quit IRC21:01
sc68calijw: thanks21:01
*** fouxm has joined #openstack-neutron21:01
ijwIf you want to use your patch to propose the attrs and values that's fine, I can just update the doc to match21:01
yfriedmlavalle: I'm asking if there might be a reason for me not to create a standalone patch with this method21:02
yfriedmlavalle: it seems pretty simple and I'm wondering why it wasn't done already21:02
mlavalleyfried: there is no reason. If you have a better way of doing this, by all means, let's do it21:02
*** jistr has quit IRC21:02
*** geekinutah has left #openstack-neutron21:02
mtreinishyfried: it's actually an oversight I think, we probably want to store the creds in a object level variable for easy reference. In the api tests this is stored in the clients manager object, which it looks like I didn't do when I rewrote the scenario tests to use isolated creds21:03
yfriedmlavalle: all I'm saying is that what you are suggesting should be done regardless of my patch21:03
mtreinishyfried: see http://git.openstack.org/cgit/openstack/tempest/tree/tempest/clients.py#n180 for how it is stored in the api tests21:04
mtreinishyfried: but helper methods would defintely be a welcome addition for the scenario tests21:04
yfriedI'll do it and then rebase the patch on it, but since it's not a problem in the patch, can you please recall your -1 so it is merged?21:05
*** fouxm has quit IRC21:06
yfriedmlavalle: ^21:06
yfriedmlavalle: I don't want to block this patch because of a feature that's not used in other network tests.21:07
*** dims has quit IRC21:08
mlavalleyfried: fair enough. But keep in mind that all network tests should take this into consideration going forward21:08
yfriedmlavalle: np21:08
*** dims has joined #openstack-neutron21:09
mlavalleyfried: in fact, th other scenario test you are working on, basic net ops, was modified by me about a couple of months ago to work with the isolation code21:09
*** yamahata has joined #openstack-neutron21:10
yfriedmlavalle: which part21:11
mlavalleyfried: here, i removed some lines to let the parent class take care of managing credentials and tenant: https://review.openstack.org/#/c/45578/12/tempest/scenario/test_network_basic_ops.py21:14
openstackgerritA change was merged to openstack/neutron: Imported Translations from Transifex  https://review.openstack.org/6256121:17
*** nati_ueno has quit IRC21:20
*** nati_ueno has joined #openstack-neutron21:28
*** 17SADQLUP has joined #openstack-neutron21:31
yfriednati_ueno: do you think you could test your patch against mine?21:32
nati_uenoyfried: hi21:32
nati_uenoyfried: which patch?21:32
yfriednati_ueno:  https://review.openstack.org/#/c/21946/ tested against https://review.openstack.org/#/c/62702/21:33
nati_uenoyfried: Sure the patch need also https://review.openstack.org/#/c/44596/21:34
nati_uenoI can definitely do that, however we have server migration in office in this week, so may be I can't do it in today21:35
openstackgerritSylvain Afchain proposed a change to openstack/neutron: Add param and iptables rules to protect dnsmasq ports  https://review.openstack.org/6199421:36
*** 17SADQLUP has quit IRC21:38
yfriednati_ueno: np. so let me know when you can and if you need help. You'll probably have some rebase issues by next week21:39
nati_uenoyfried: sure Thank you for your sharing test patch21:39
*** briancline has quit IRC21:39
yfriednati_ueno: thank you for fixing it so my patch will finally be merged21:40
nati_uenoyfried: This tempest patch is important, otherwise we could break sec-group function again21:40
*** skromnica has joined #openstack-neutron21:41
yfriednati_ueno: yeah. tell me about it. I'm just amazed no one saw this before me...21:41
nati_uenoyfried: Thank you for your contribution on this :).21:42
yfriednati_ueno: anyway - tnx for the work. I'm guessing it wasn't a 1line fix21:42
nati_uenoyour welcome21:42
yfriedasking again here (redirected from infra):21:43
yfried Hi guys, I'm looking to get the external connectivity (ie - ping 8.8.8.8) on the devstack-neutron gate so this patch can work: https://review.openstack.org/#/c/55146/21:43
yfriedcan any one help me?21:43
*** SushilKM has joined #openstack-neutron21:43
yfriedor to put it another way - are we sure the gate doesn't have external connection at the moment?21:44
nati_uenoyfried: I guess we should setup NAT rule in the VM if we wan't to do this21:45
nati_uenoor correct GW settings in the VM21:45
yfriednati_ueno: and who can do that?21:46
*** skromnica has quit IRC21:46
nati_uenoI can do that, if it is nexe week21:46
nati_uenos/nexe/next/21:46
nati_uenoWe should update devstack21:46
yfriednati_ueno: can you point me to anyone else? I would really like it to happen earlier. this patch have been stuck in review limbo for a while now.21:47
yfriednati_ueno: but tnx for the offer. I will nag you next week if I can't find other volunteers21:48
nati_uenoyfried: how about asking it in the openstack-dev ?21:48
yfriednati_ueno: will do21:48
nati_uenoThe change should be easy, just setup ip masquerade between floating ip range and external network connection in the VM21:50
nati_uenoit should be one or two lines in devstack21:50
*** briancline has joined #openstack-neutron21:52
*** SushilKM has quit IRC21:56
*** clev has quit IRC21:58
*** nati_uen_ has joined #openstack-neutron22:01
*** nati_uen_ has quit IRC22:03
*** SumitNaiksatam has joined #openstack-neutron22:03
*** nati_ueno has quit IRC22:03
*** nati_uen_ has joined #openstack-neutron22:03
*** jroovers has joined #openstack-neutron22:06
*** ian12 has joined #openstack-neutron22:08
*** markmcclain has quit IRC22:10
*** klindgren_ has joined #openstack-neutron22:13
klindgren_Is it expected that when using the ml2 plugin neutron agent-list results in no results being returned, but under the neutron_ml2 database the agents table is populated with agents that are checking in?  This is under devstack on Ubuntu22:14
*** pcm__ has joined #openstack-neutron22:17
*** ian12 has quit IRC22:18
*** dave_tucker has joined #openstack-neutron22:19
*** pcm has quit IRC22:20
*** pcm__ has quit IRC22:26
anteayaterry_howe: sorry for my delayed response22:43
anteayaI think the openstackclient is a great project22:43
anteayait really makes things easier for people to get a handle on openstack as a whole, rather than just one project22:44
anteayagiven the command format for the other projects you have on the wiki, I don't see how else you could format the commands for DHCP agent22:44
anteayaif there are other ways that fit the format used by openstackclient currrently, I am interested to hear them22:45
openstackgerritSukhdev Kapur proposed a change to openstack/neutron: This is just a test for Gerrit for third party testing- plz ignore  https://review.openstack.org/6277122:45
anteayanow how the relationship is conveyed by the command, between network and agent, we would need more opinions on that22:46
openstackgerritSukhdev Kapur proposed a change to openstack/neutron: This is just a test for Gerrit for third party testing- plz ignore  https://review.openstack.org/6277122:49
*** dave_tucker has quit IRC22:51
*** dave_tucker has joined #openstack-neutron22:52
openstackgerritmouad benchchaoui proposed a change to openstack/neutron: Make the metadata namespace proxy transparent  https://review.openstack.org/2813722:56
*** yfried has quit IRC22:56
openstackgerritSylvain Afchain proposed a change to openstack/neutron: L3 Agent can handle many external networks.  https://review.openstack.org/5935922:57
*** dave_tucker has quit IRC22:59
*** dave_tucker has joined #openstack-neutron22:59
*** dims has quit IRC23:01
ijwargh23:01
*** jpich has quit IRC23:01
*** harlowja is now known as harlowja_away23:02
*** harlowja_away is now known as harlowja23:05
anteayaarosen this bug just jumped: https://bugs.launchpad.net/neutron/+bug/125016823:05
anteayaenikanorov: this bug has jumped in frequency as well https://bugs.launchpad.net/nova/+bug/121048323:06
anteayaand markmcclain this bug continues to cause problems: https://bugs.launchpad.net/tempest/+bug/125389623:09
*** aymenfrikha has joined #openstack-neutron23:15
*** dims has joined #openstack-neutron23:16
*** yamahata has quit IRC23:20
anteayacurrently we have a 57% pass chance in the gate across all of openstack23:21
*** djbkd has joined #openstack-neutron23:30
*** jroovers has quit IRC23:36
*** SumitNaiksatam has quit IRC23:56

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