Monday, 2016-04-04

*** mfuruta has joined #openstack-neutron00:00
*** salv-orlando has joined #openstack-neutron00:02
*** baoli has joined #openstack-neutron00:05
*** baoli has quit IRC00:10
*** achanda has quit IRC00:18
*** panda has quit IRC00:26
*** panda has joined #openstack-neutron00:26
*** salv-orlando has quit IRC00:28
*** wolverineav has joined #openstack-neutron00:29
*** wolverineav has quit IRC00:34
*** vhosakot has joined #openstack-neutron00:37
*** thorst has joined #openstack-neutron00:37
*** thorst has quit IRC00:45
*** markvoelker has joined #openstack-neutron00:47
*** hoangcx has joined #openstack-neutron00:53
*** achanda has joined #openstack-neutron00:57
*** thorst has joined #openstack-neutron00:58
*** hichihara has joined #openstack-neutron00:58
*** thorst has quit IRC01:00
*** lnicolas has joined #openstack-neutron01:07
*** achanda has quit IRC01:07
*** vhosakot has quit IRC01:11
*** namnh has joined #openstack-neutron01:12
*** lujinluo has joined #openstack-neutron01:22
*** bjornar has joined #openstack-neutron01:25
*** salv-orlando has joined #openstack-neutron01:27
*** wolverineav has joined #openstack-neutron01:31
*** djan_ has joined #openstack-neutron01:34
*** djan has quit IRC01:34
*** wolverineav has quit IRC01:36
*** vhosakot has joined #openstack-neutron01:41
*** vhosakot has quit IRC01:42
*** vhosakot has joined #openstack-neutron01:42
*** jckasper has joined #openstack-neutron01:43
*** thorst has joined #openstack-neutron01:44
*** salv-orlando has quit IRC01:44
*** baoli has joined #openstack-neutron01:46
*** nplanel has joined #openstack-neutron01:46
*** bapalm has joined #openstack-neutron01:51
*** thorst has quit IRC01:53
*** thorst has joined #openstack-neutron01:53
*** vhosakot has quit IRC02:01
*** thorst has quit IRC02:02
*** vhosakot has joined #openstack-neutron02:02
*** ramishra_ has joined #openstack-neutron02:04
*** ramishra_ has quit IRC02:05
*** kengo_sakai has joined #openstack-neutron02:05
*** achanda has joined #openstack-neutron02:07
*** cshahani has quit IRC02:09
*** ramishra has quit IRC02:09
*** ramishra has joined #openstack-neutron02:09
*** djan has joined #openstack-neutron02:11
*** cshahani has joined #openstack-neutron02:12
*** ramishra has quit IRC02:12
*** djan_ has quit IRC02:12
*** bjornar has quit IRC02:13
*** achanda has quit IRC02:13
*** liusheng has quit IRC02:20
*** liusheng has joined #openstack-neutron02:22
*** yamamoto has quit IRC02:27
*** baoli has quit IRC02:28
*** yamamoto has joined #openstack-neutron02:31
*** wolverineav has joined #openstack-neutron02:32
*** sridhar_ram has joined #openstack-neutron02:35
*** wolverineav has quit IRC02:37
*** sridhar_ram1 has joined #openstack-neutron02:38
openstackgerritVictor Morales proposed openstack/neutron: Address Scope added to OVO  https://review.openstack.org/29782102:39
*** sridhar_ram has quit IRC02:40
openstackgerritSongming Yan proposed openstack/python-neutronclient: Fix the problem of router delete  https://review.openstack.org/29653502:45
*** links has joined #openstack-neutron02:46
*** brad_behle has joined #openstack-neutron02:49
*** yamamoto has quit IRC02:50
openstackgerritVictor Morales proposed openstack/neutron: Agent to OVO  https://review.openstack.org/29788702:55
*** thorst has joined #openstack-neutron02:59
*** kengo_sakai has quit IRC03:00
*** kengo_sakai has joined #openstack-neutron03:00
*** kengo_sakai has quit IRC03:00
*** kengo_sakai has joined #openstack-neutron03:01
*** lujinluo has quit IRC03:03
*** salv-orlando has joined #openstack-neutron03:03
*** wolverineav has joined #openstack-neutron03:06
*** thorst has quit IRC03:07
*** achanda has joined #openstack-neutron03:09
*** salv-orlando has quit IRC03:13
*** markvoelker has quit IRC03:14
*** achanda has quit IRC03:16
*** jamespd has quit IRC03:21
*** jamespd has joined #openstack-neutron03:22
*** salv-orlando has joined #openstack-neutron03:22
*** annp has joined #openstack-neutron03:26
*** jamielennox is now known as jamielennox|away03:27
*** salv-orlando has quit IRC03:27
*** fedexo has joined #openstack-neutron03:30
*** jamielennox|away is now known as jamielennox03:37
*** jckasper has quit IRC03:38
*** jckasper has joined #openstack-neutron03:38
*** jckasper has quit IRC03:38
*** abregman has quit IRC03:40
*** dave-mcc_ has quit IRC03:49
*** lujinluo has joined #openstack-neutron04:01
*** yamamoto has joined #openstack-neutron04:01
*** akshai_ has joined #openstack-neutron04:03
*** thorst has joined #openstack-neutron04:05
*** akshai has quit IRC04:06
*** puck has quit IRC04:07
*** thorst has quit IRC04:12
*** achanda has joined #openstack-neutron04:13
*** shivrao has joined #openstack-neutron04:14
*** puck has joined #openstack-neutron04:15
*** markvoelker has joined #openstack-neutron04:15
*** achanda has quit IRC04:18
*** iyamahat has joined #openstack-neutron04:20
*** markvoelker has quit IRC04:21
*** panda has quit IRC04:26
*** panda has joined #openstack-neutron04:26
*** oshvartz has quit IRC04:30
*** numans has joined #openstack-neutron04:30
*** itzikb has quit IRC04:30
*** vhosakot has quit IRC04:31
*** kobis has joined #openstack-neutron04:33
*** sridhar_ram1 has quit IRC04:36
*** netsin has quit IRC04:38
*** baoli has joined #openstack-neutron04:40
*** salv-orlando has joined #openstack-neutron04:42
*** baoli has quit IRC04:45
*** salv-orlando has quit IRC04:45
*** elo has quit IRC04:45
*** achanda has joined #openstack-neutron04:46
*** Shahid_ has joined #openstack-neutron04:47
*** elo has joined #openstack-neutron04:51
*** abregman has joined #openstack-neutron04:54
*** Marga_ has joined #openstack-neutron04:55
*** mkolesni_ has joined #openstack-neutron04:56
*** akshai_ has quit IRC04:58
*** kobis has quit IRC04:58
*** kengo_sa_ has joined #openstack-neutron04:59
*** xek has quit IRC04:59
*** xek has joined #openstack-neutron05:00
*** irenab has quit IRC05:02
*** shausy has joined #openstack-neutron05:06
*** cshahani has quit IRC05:07
*** thorst has joined #openstack-neutron05:10
*** shivrao has quit IRC05:10
*** amotoki has joined #openstack-neutron05:11
*** vhosakot has joined #openstack-neutron05:15
*** thorst has quit IRC05:17
openstackgerritAkihiro Motoki proposed openstack/neutron: release note to deprecate prevent_arp_spoofing option  https://review.openstack.org/30031105:18
*** amotoki has quit IRC05:18
*** anilvenkata has joined #openstack-neutron05:19
*** kawa2014 has joined #openstack-neutron05:20
*** oanson has joined #openstack-neutron05:23
*** vikram_ has joined #openstack-neutron05:28
*** yasemin has joined #openstack-neutron05:28
*** hynekm has joined #openstack-neutron05:31
*** yfried has quit IRC05:31
*** netsin has joined #openstack-neutron05:34
*** lajos-katona has joined #openstack-neutron05:36
*** amotoki has joined #openstack-neutron05:37
*** shausy has quit IRC05:37
*** shausy has joined #openstack-neutron05:38
*** irenab has joined #openstack-neutron05:43
*** numans has quit IRC05:47
*** kengo_sa_ has quit IRC05:52
*** oshvartz has joined #openstack-neutron05:55
*** annp has quit IRC06:02
*** gampel1 has joined #openstack-neutron06:04
*** vhosakot has quit IRC06:07
*** ekuris_ has joined #openstack-neutron06:07
*** gal_ is now known as gsagie06:10
*** wolverineav has quit IRC06:12
*** wolverineav has joined #openstack-neutron06:13
*** wolverineav has quit IRC06:13
openstackgerritLujin Luo proposed openstack/neutron: Clean up excess dhcp-agents scheduled to a network  https://review.openstack.org/28827106:13
*** moshele has joined #openstack-neutron06:13
*** salv-orlando has joined #openstack-neutron06:13
*** thorst has joined #openstack-neutron06:15
*** netsin has quit IRC06:15
*** numans has joined #openstack-neutron06:16
*** salv-orlando has quit IRC06:16
*** numans_ has joined #openstack-neutron06:18
*** apoorv has joined #openstack-neutron06:20
*** ihrachys has joined #openstack-neutron06:21
*** ihrachys has quit IRC06:21
*** thorst has quit IRC06:21
*** ekuris_ has quit IRC06:22
*** ekuris has joined #openstack-neutron06:23
*** salv-orlando has joined #openstack-neutron06:24
*** eddima has joined #openstack-neutron06:27
*** jhershbe has joined #openstack-neutron06:27
*** iyamahat has quit IRC06:28
*** salv-orlando has quit IRC06:28
*** scheuran has joined #openstack-neutron06:28
*** korzen has joined #openstack-neutron06:33
*** Marga_ has quit IRC06:33
*** Marga_ has joined #openstack-neutron06:33
*** nlahouti has joined #openstack-neutron06:34
vikram_amotoki: ping06:34
*** sridharg has joined #openstack-neutron06:34
vikram_amotoki: about "https://review.openstack.org/#/c/268726/", i was thinking od neutron-draas?06:35
vikram_*of06:35
amotokivikram_: pong06:35
vikram_amotoki: dynamic-routing looks big06:35
vikram_amotoki: neutron-dynamic-routing looks big06:35
amotokivikram_: i am not sure 'dr' is a clear name for folks who are not familiar with neutron....06:35
vikram_amotoki: ok, let's collect some more feedback then06:36
amotokivikram_: I asked my colleagues involved in openstack cloud integration and they answered06:36
amotokineutron supports DR?06:36
vikram_i understand06:37
amotokiDR in their mind is disater recovery06:37
vikram_ok06:37
vikram_How about *aaS06:37
vikram_for this repo... like VPN and FW?06:37
amotokiI think 'aaS' solves nothing.06:38
amotoki'aaS' just means normal users can provision their own resources or somthing06:38
vikram_I was thinking we are trying to provide a routing service06:38
amotokiI think we are provide dynacmic routing service on top of neutron router06:39
vikram_ok06:43
*** ushkalim has joined #openstack-neutron06:45
*** achanda has quit IRC06:48
*** anshul has joined #openstack-neutron06:48
*** gampel2 has joined #openstack-neutron06:50
*** yfried has joined #openstack-neutron06:50
*** gampel1 has quit IRC06:52
*** kengo_sa_ has joined #openstack-neutron06:55
*** apoorv has quit IRC06:57
*** garyk has joined #openstack-neutron06:58
*** yamahata has quit IRC06:58
openstackgerritlokesh s proposed openstack/python-neutronclient: log SHA! hash of  X-Auth-Token value  https://review.openstack.org/29863706:58
*** nmagnezi has joined #openstack-neutron06:58
*** yfried has quit IRC06:59
*** iyamahat has joined #openstack-neutron07:00
*** djan_ has joined #openstack-neutron07:00
*** yfried has joined #openstack-neutron07:00
*** djan has quit IRC07:01
*** nyechiel_ has joined #openstack-neutron07:02
*** ihrachys has joined #openstack-neutron07:03
*** apoorv has joined #openstack-neutron07:03
*** achanda has joined #openstack-neutron07:03
*** kengo_sa_ has quit IRC07:03
*** itzikb has joined #openstack-neutron07:04
*** yamamoto has quit IRC07:04
*** sayalilunkad has joined #openstack-neutron07:05
*** iyamahat has quit IRC07:05
*** cristicalin has joined #openstack-neutron07:05
*** yamahata has joined #openstack-neutron07:05
*** ushkalim has quit IRC07:06
*** yamamoto has joined #openstack-neutron07:06
*** fedexo has quit IRC07:08
*** prapulla has joined #openstack-neutron07:09
prapullahow many routers can be created in each tenant to external network? any limitation to create router in openstack neutron environment07:11
prapullawe are using openstack kilo version07:13
*** wolverineav has joined #openstack-neutron07:13
*** jschwarz has joined #openstack-neutron07:13
*** iyamahat has joined #openstack-neutron07:13
-openstackstatus- NOTICE: Gerrit is going to be restarted due to bad performance07:14
*** Shahid_ has quit IRC07:15
openstackgerritHa Van Tu proposed openstack/neutron-fwaas: Fix "Not applying Firewall rules immediately" problem  https://review.openstack.org/30096007:16
*** salv-orlando has joined #openstack-neutron07:17
*** mickeys has joined #openstack-neutron07:17
*** hdaniel has joined #openstack-neutron07:18
*** wolverineav has quit IRC07:19
*** nlahouti has quit IRC07:19
*** thorst has joined #openstack-neutron07:19
openstackgerritHa Van Tu proposed openstack/neutron-fwaas: Fix "Not applying Firewall rules immediately" problem  https://review.openstack.org/30096007:19
*** mickeys has quit IRC07:20
*** iyamahat has quit IRC07:20
*** mickeys has joined #openstack-neutron07:20
*** achanda has quit IRC07:24
*** jpena|off is now known as jpena07:24
*** achanda has joined #openstack-neutron07:24
*** mickeys has quit IRC07:25
*** jlanoux has joined #openstack-neutron07:26
*** yamahata has quit IRC07:27
*** thorst has quit IRC07:27
*** yamamoto has quit IRC07:29
*** cristicalin has quit IRC07:29
*** yamamoto has joined #openstack-neutron07:30
*** cristicalin has joined #openstack-neutron07:30
openstackgerritHa Van Tu proposed openstack/neutron-fwaas: Fix "Not applying Firewall rules immediately" problem  https://review.openstack.org/30096007:30
*** dedery has joined #openstack-neutron07:31
*** achanda has quit IRC07:32
*** davideag_ has joined #openstack-neutron07:34
*** garyk has quit IRC07:36
*** yfried has quit IRC07:36
*** yfried has joined #openstack-neutron07:36
*** garyk has joined #openstack-neutron07:36
*** davideagnello has quit IRC07:37
*** jlibosva has joined #openstack-neutron07:37
*** reedip__ has quit IRC07:37
*** brad_behle_ has joined #openstack-neutron07:39
*** gampel1 has joined #openstack-neutron07:39
*** adreznec has quit IRC07:39
*** panda has quit IRC07:39
*** agireud has quit IRC07:40
*** gampel2 has quit IRC07:40
*** cristicalin has quit IRC07:40
*** grassass has quit IRC07:40
*** prapulla has quit IRC07:41
*** adreznec has joined #openstack-neutron07:41
*** dedery_ has joined #openstack-neutron07:41
*** brad_behle has quit IRC07:41
*** prapulla has joined #openstack-neutron07:42
*** dedery has quit IRC07:43
*** bigjools has quit IRC07:43
*** rcernin has joined #openstack-neutron07:43
*** grassass has joined #openstack-neutron07:43
*** agireud has joined #openstack-neutron07:43
*** reedip__ has joined #openstack-neutron07:43
*** bigjools has joined #openstack-neutron07:43
*** bigjools has joined #openstack-neutron07:43
*** panda has joined #openstack-neutron07:44
*** pavel_bondar has quit IRC07:50
*** salv-orlando has quit IRC07:53
*** fawadkhaliq has joined #openstack-neutron07:54
*** salv-orlando has joined #openstack-neutron07:56
*** yfried has quit IRC07:58
*** mgoddard has joined #openstack-neutron07:59
*** kiseok7 has joined #openstack-neutron08:00
*** kengo_sa_ has joined #openstack-neutron08:00
*** jamielennox is now known as jamielennox|away08:01
*** neeti has joined #openstack-neutron08:05
*** kengo_sa_ has quit IRC08:05
openstackgerritJakub Libosvar proposed openstack/neutron: ovsfw: Remove vlan tag before injecting packets to port  https://review.openstack.org/30054208:06
*** shashank_hegde has quit IRC08:08
*** fawadkhaliq has quit IRC08:10
*** devvesa has joined #openstack-neutron08:11
reedipamotoki, vikram : cant we use networking-dynamic-routing ( I am just thinking of a way to avoid neutron at the initial level itself, if we are to change the name later on)08:12
amotokireedip: why not discuss in the review?08:13
reedipamotoki: I already mentioned it but got no feedback(yet)08:14
reedip:)08:14
*** numans has quit IRC08:14
*** anilvenkata has quit IRC08:15
*** wolverineav has joined #openstack-neutron08:15
*** yfried has joined #openstack-neutron08:16
*** anilvenkata has joined #openstack-neutron08:18
*** rossella_s has joined #openstack-neutron08:18
*** jistr has joined #openstack-neutron08:19
*** Shahid_ has joined #openstack-neutron08:19
*** rdo has joined #openstack-neutron08:19
*** wolverineav has quit IRC08:20
*** ushkalim has joined #openstack-neutron08:23
openstackgerritJakub Libosvar proposed openstack/neutron: Change get_root_helper_child_pid to stop when it finds cmd  https://review.openstack.org/29479808:24
*** thorst has joined #openstack-neutron08:25
anilvenkatajschwarz, Hi John08:25
*** yasemin has left #openstack-neutron08:26
*** numans has joined #openstack-neutron08:27
*** hkominos has joined #openstack-neutron08:30
*** djan has joined #openstack-neutron08:31
hkominosHi guys. Quick question. Is there some sort of mechanism which "cleans up" network interfaces in neutron?08:31
*** thorst has quit IRC08:31
amotokihkominos: what kind of clean up do you expect? cleanup of ovs-interface?08:32
*** achanda has joined #openstack-neutron08:32
jschwarzanilvenkata, heya08:32
jschwarzanilvenkata, I saw your question - will answer shortly08:32
*** djan_ has quit IRC08:34
*** dedery_ is now known as dedery08:35
*** itzikb has quit IRC08:36
*** itzikb has joined #openstack-neutron08:36
*** slaweq has joined #openstack-neutron08:36
*** achanda has quit IRC08:36
hkominosLet me explain. I have 2 compute nodes and has nova-docker. When i ssh to the host with novadocker i see a couple of network interfaces (tap,qbr etc) which are not connected to anything. I mean that they were not destroyed when the containers failed to boot08:37
anilvenkatajschwarz, ok08:37
*** lezbar has joined #openstack-neutron08:38
hkominosSo i Was wondering if there is a process which periodically cleans the Hosts from these unused interfaces + unplugs them from ovs-bridges.08:38
hkominoscause i see them now with tag 409508:38
*** lezbar has quit IRC08:38
*** lezbar has joined #openstack-neutron08:39
*** mdavidson has quit IRC08:39
amotokihkominos: actually nova vif driver is responsible to manage qbr. I think there is a case where vif-driver is not cleanup properly08:40
amotokihkominos: i see the same situation.08:40
hkominosSo is it just a bug ?08:41
hkominosbecause i have a theory as to why it did not cleanup08:41
amotokihkominos: I think so.08:41
*** neiljerram has joined #openstack-neutron08:44
openstackgerritJakub Libosvar proposed openstack/neutron: devref: Update ovs-firewall  https://review.openstack.org/29992608:45
*** saggi has joined #openstack-neutron08:45
*** davidsha has joined #openstack-neutron08:46
*** amotoki has quit IRC08:49
*** amotoki has joined #openstack-neutron08:49
openstackgerritlokesh s proposed openstack/python-neutronclient: log SHA! hash of  X-Auth-Token value  https://review.openstack.org/29863708:51
*** devvesa has quit IRC08:55
*** numans has quit IRC08:56
*** numans has joined #openstack-neutron08:57
*** gampel2 has joined #openstack-neutron08:57
*** djan has quit IRC08:57
*** devvesa has joined #openstack-neutron08:57
openstackgerritAndreas Scheuring proposed openstack/neutron: lb: interface name hashing for too long vlan interface names  https://review.openstack.org/24695408:57
*** devvesa has quit IRC08:58
*** mfuruta has quit IRC09:00
*** gampel1 has quit IRC09:01
*** lujinluo has quit IRC09:01
*** EinstCrazy has joined #openstack-neutron09:01
*** cshahani has joined #openstack-neutron09:03
*** kawa2014 has quit IRC09:06
*** haukebruno has joined #openstack-neutron09:06
*** claudiub has joined #openstack-neutron09:06
*** cshahani has quit IRC09:08
*** sambetts|afk is now known as sambetts09:14
openstackgerritPavel Bondar proposed openstack/neutron: Update ml2 delete_subnet to deallocate via ipam  https://review.openstack.org/30098409:14
openstackgerritHa Van Tu proposed openstack/neutron-fwaas: Fix "Not applying Firewall rules immediately" problem  https://review.openstack.org/30096009:15
*** bjornar has joined #openstack-neutron09:16
*** amotoki has quit IRC09:17
*** amotoki has joined #openstack-neutron09:18
*** itzikb has quit IRC09:20
openstackgerritMerged openstack/neutron: Increase ports per network and add SLA for rally  https://review.openstack.org/22658609:22
*** thorst has joined #openstack-neutron09:30
*** javeriak has joined #openstack-neutron09:32
*** mdavidson has joined #openstack-neutron09:35
*** javeriak has quit IRC09:37
*** thorst has quit IRC09:37
*** sakthi_chn has joined #openstack-neutron09:37
slaweqajo_: ihrachys: hello09:37
slaweqcan You maybe take a look on https://review.openstack.org/#/c/300210 and maybe also on https://review.openstack.org/#/c/300679/09:38
slaweqthx in advance :)09:38
ajo_slaweq, ack, doing, I failed to deploy LB for some reason09:39
slaweqajo_: thx a lot09:41
slaweqI will wait for Your comments09:41
openstackgerritIhar Hrachyshka proposed openstack/neutron: Cleaned up tox_install.sh  https://review.openstack.org/30099409:44
*** itzikb has joined #openstack-neutron09:45
sakthi_chnhi,09:47
ajo_slaweq, : a bit of nitpick here: https://review.openstack.org/#/c/300679/3  <-- garyk09:47
ajo_garyk: may be the logging I ask for not that valuable. Thoughts?09:47
ajo_other than that It looks good to me.09:47
sakthi_chnIn my lab network has been fluctuate frequently, I didn't get any errors in log can anyone suggest what is the main problem09:48
openstackgerritAnn Kamyshnikova proposed openstack/neutron: WIP: New engine facade from oslo_db  https://review.openstack.org/30001709:49
sakthi_chnCreating more routers causes any problem, or using more vlan creates any problem09:49
slaweqajo_: ok, I can add some debug logging msg there if You think it will be usefull09:49
*** links has quit IRC09:53
*** links has joined #openstack-neutron09:54
*** ociuhandu has quit IRC09:59
*** slaweq_ has joined #openstack-neutron10:01
*** yamamoto has quit IRC10:03
*** slaweq_ has quit IRC10:03
*** yamamoto has joined #openstack-neutron10:04
*** achanda has joined #openstack-neutron10:05
*** marios has quit IRC10:05
*** marios has joined #openstack-neutron10:06
*** numans_ has quit IRC10:11
*** achanda has quit IRC10:11
*** sdague has joined #openstack-neutron10:12
*** thorst has joined #openstack-neutron10:14
*** numans has quit IRC10:16
*** yamamoto has quit IRC10:16
*** wolverineav has joined #openstack-neutron10:17
*** yamamoto has joined #openstack-neutron10:17
*** thorst has quit IRC10:21
*** numans_ has joined #openstack-neutron10:21
*** wolverineav has quit IRC10:21
*** numans_ has quit IRC10:22
*** numans has joined #openstack-neutron10:22
*** kawa2014 has joined #openstack-neutron10:23
*** hoangcx has quit IRC10:23
*** yamamoto has quit IRC10:26
*** anilvenkata is now known as anilvenkata_afk10:29
*** salv-orl_ has joined #openstack-neutron10:30
*** vikram_ has quit IRC10:30
*** vikram_ has joined #openstack-neutron10:31
*** salv-orlando has quit IRC10:32
slaweqajo_: about debug log in https://review.openstack.org/#/c/300679/ do You think it should be good idea to add debug message in both cases: bw_limit_update and bw_limit_delete?10:37
slaweqor only for update?10:37
*** ociuhandu has joined #openstack-neutron10:40
*** jlanoux has quit IRC10:46
*** openstackgerrit has quit IRC10:48
*** openstackgerrit has joined #openstack-neutron10:49
openstackgerritKevin Benton proposed openstack/neutron: De-dup user-defined SG rules before iptables call  https://review.openstack.org/30102910:49
*** rodrigods has quit IRC10:50
*** rodrigods has joined #openstack-neutron10:50
*** Shahid_ has quit IRC10:52
*** nmagnezi has quit IRC10:57
*** swat30 has quit IRC10:58
jschwarzkevinbenton, yo11:00
jschwarzkevinbenton, could you have a look at https://review.openstack.org/#/c/257059/30/neutron/db/l3_agentschedulers_db.py ? we're waiting for your opinion on the matter11:00
*** hichihara has quit IRC11:02
*** dedery_ has joined #openstack-neutron11:03
*** dedery has quit IRC11:05
*** moshele has quit IRC11:06
*** moshele has joined #openstack-neutron11:08
*** saggi has quit IRC11:08
*** nmagnezi has joined #openstack-neutron11:10
*** namnh has quit IRC11:11
*** krotscheck_vaca is now known as krotscheck11:13
*** yamamoto has joined #openstack-neutron11:14
*** yamamoto_ has joined #openstack-neutron11:15
jschwarzakamyshnikova, thanks for the response to amuller in https://review.openstack.org/#/c/284400/ :)11:17
*** yamamoto has quit IRC11:19
*** irenab has quit IRC11:19
akamyshnikovajschwarz, np :)11:19
*** gampel2 has quit IRC11:19
*** numan_ has joined #openstack-neutron11:19
*** rtheis has joined #openstack-neutron11:22
*** saggi has joined #openstack-neutron11:23
garykajo_: yes, the logging request is a good idea11:24
slaweqgaryk: ok, I will add it for both cases (update and delete)11:27
garykthanks!11:27
openstackgerritSlawek Kaplonski proposed openstack/neutron: Improve handle port_update and port_delete events in ovs qos agent  https://review.openstack.org/30067911:29
slaweqgaryk: done :)11:29
*** Shahid_ has joined #openstack-neutron11:30
garykthanks.11:32
anilvenkata_afkjschwarz, here js+tab is giving your name :)11:38
*** claudiub has quit IRC11:39
*** anilvenkata_afk is now known as anilvenkata11:39
amotokislaweq: some suggestion on logging message in your review.11:39
anilvenkatajschwarz, https://review.openstack.org/#/c/284400/11/neutron/scheduler/l3_agent_scheduler.py current code has a problem, I gave a comment11:40
jschwarzanilvenkata, aye I saw11:41
anilvenkatajschwarz, do u agree11:41
jschwarzanilvenkata, multitasking a bit and it's not working :<11:41
*** thorst has joined #openstack-neutron11:41
*** jaypipes has joined #openstack-neutron11:42
anilvenkatajschwarz, mean u tries with what I suggested and still see issue?11:42
anilvenkatatried11:42
*** Murali has joined #openstack-neutron11:42
jschwarzanilvenkata, means I read the comments but still didn't have time to think about them in depth because I'm failing at multiplexing my attention today for some reason11:42
jschwarz:<11:42
*** baoli has joined #openstack-neutron11:42
anilvenkatajschwarz, :)11:43
jschwarzanilvenkata, also I saw that the changes at line 166 aren't really needed I think11:43
slaweqamotoki: thx11:43
slaweqI will push fix in few minutes11:43
jschwarzanilvenkata, so I'm also thinking about that11:43
jschwarzanilvenkata, anyway which comment did you mean? the one in line 328 or 342?11:44
anilvenkatajschwarz, https://review.openstack.org/#/c/284400/11/neutron/scheduler/l3_agent_scheduler.py L32811:44
korzenhi ihrachys do we have upgrade meeting today at 5pm?11:44
*** baoli_ has joined #openstack-neutron11:44
anilvenkatajschwarz, L342 can be taken up later11:44
ihrachyskorzen: yeah. bloody summer time switch moved all upstream meetings +1h11:44
jschwarzanilvenkata, ok let me open up the code11:45
*** jlanoux has joined #openstack-neutron11:45
*** claudiub has joined #openstack-neutron11:45
korzenihrachys, ok thx I was making sure that the meeting was not scheduled at CET time and stayed at 4pm :)11:45
openstackgerritDaniel Berrange proposed openstack/os-vif: linux_bridge: convert over to use privsep module  https://review.openstack.org/28772511:45
openstackgerritDaniel Berrange proposed openstack/os-vif: ovs: convert over to use privsep module  https://review.openstack.org/29940611:45
openstackgerritDaniel Berrange proposed openstack/os-vif: ovs: move code from plugin into linux_net helper  https://review.openstack.org/29940511:45
ihrachyskorzen: it's all UTC11:45
*** davidsha has quit IRC11:46
openstackgerritSlawek Kaplonski proposed openstack/neutron: Improve handle port_update and port_delete events in ovs qos agent  https://review.openstack.org/30067911:46
slaweqamotoki: pushed fix for log message11:46
amotokislaweq: thanks11:47
*** baoli has quit IRC11:48
*** EinstCrazy has quit IRC11:50
anilvenkatajschwarz, https://review.openstack.org/#/c/284400/11/neutron/scheduler/l3_agent_scheduler.py update with code sample11:50
anilvenkataupdated11:50
jschwarzanilvenkata, so I'm looking at this now11:50
jschwarzanilvenkata, I'm not clear what you want me to change11:50
* jschwarz is looking11:50
ajo_garyk++ thanks11:50
Muralihello everybody11:52
MuraliCould some one help me to come out of this error http://paste.ubuntu.com/15611079/11:52
Muraliits part of writing our own agent like ovs-agent11:53
Muraliany help is appriciated11:53
jschwarzanilvenkata, so I'm not sure create_object_with_dependency is the proper use case here11:53
anilvenkatajschwarz, code after create_object_with_dependency is prone to race11:55
jschwarzanilvenkata, how so?11:55
jschwarzanilvenkata, anyway bind_router's return value has nothing to do with the 'port_binding.l3_agent_id=agent.id' that comes after11:56
*** marcusvrn_ has joined #openstack-neutron11:56
jschwarzanilvenkata, so using create_object_with_dependency won't work without making some modifications to it (which I'd like to avoid, of course)11:56
anilvenkatajschwarz, for example if rpc worker called created a new port through  create_object_with_dependency and then bound the port to agent through "port_binding.l3_agent_id = agent['id']" then if api worker's concurrently L33611:56
*** mvk_ has joined #openstack-neutron11:57
anilvenkatajschwarz, api worker's L336 will be success, but L342 will fail11:57
*** neelashah has joined #openstack-neutron11:58
jschwarzanilvenkata, I'm afraid I don't fully understand your example11:58
jschwarzanilvenkata, cna you clarify?11:58
anilvenkatajschwarz, ok I will update as a comment in the patch11:59
*** pavel_bondar has joined #openstack-neutron11:59
jschwarzanilvenkata, we can do it here also :)11:59
*** mvk has quit IRC12:00
*** eddima1 has joined #openstack-neutron12:00
anilvenkatajschwarz, I am saying if rpc worker and api worker are executing in parallel for a router12:01
jschwarzanilvenkata, ok12:01
*** amuller has joined #openstack-neutron12:01
*** irenab has joined #openstack-neutron12:02
anilvenkatajschwarz, first rpc worker executed till https://review.openstack.org/#/c/284400/11/neutron/scheduler/l3_agent_scheduler.py L28712:02
*** mvk_ has quit IRC12:03
*** eddima has quit IRC12:03
*** eddima1 is now known as eddima12:03
jschwarzanilvenkata, ah I now see what you mean12:03
anilvenkatajschwarz, then api worker executed till L33712:03
anilvenkatajschwarz, for api worker L342 will fail12:04
anilvenkatajschwarz, at the same time for rpc worker L296 will fail12:04
jschwarzanilvenkata, heh I didn't even notice they were backwards until now12:05
anilvenkatajschwarz, so both workers can't able to bind properly in both RouterL3AgentBinding and  L3HARouterAgentPortBinding tables12:05
anilvenkatajschwarz, :)12:05
jschwarzanilvenkata, the rpc worker shouldn't fail at line 29612:05
anilvenkatajschwarz, why already router is bind in L33612:06
jschwarzanilvenkata, well actually if the API worker throws an exception then the router is deleted and the rpc worker will fail12:06
anilvenkatajschwarz, rpc will get a duplicate entry db error12:06
jschwarzanilvenkata, the transaction will be rolled back and bind_router will be reverted12:06
jschwarzno?12:06
anilvenkatajschwarz, trying to follow12:07
jschwarzanilvenkata, grabbing myself some water, brb12:08
anilvenkatajschwarz, which rollback for rpc worker12:08
anilvenkatajschwarz, enjoy :)12:08
*** kengo_sakai has quit IRC12:08
*** dedery has joined #openstack-neutron12:08
*** nmagnezi_ has joined #openstack-neutron12:08
*** dedery has quit IRC12:08
*** tmorin has joined #openstack-neutron12:08
*** achanda has joined #openstack-neutron12:09
jschwarzanilvenkata, if line 372 fails, the whole transaction (including bind_router) is rolled back12:09
*** davidsha has joined #openstack-neutron12:09
*** dedery has joined #openstack-neutron12:09
*** kengo_sakai has joined #openstack-neutron12:09
anilvenkatajschwarz, L372 from https://review.openstack.org/#/c/284400/11/neutron/scheduler/l3_agent_scheduler.py?12:10
jschwarzanilvenkata, 342, sorry12:10
jschwarzanilvenkata, so the api worker goes to line 342 and it raises an exception (because the rpc worker was at line 287)12:11
jschwarzanilvenkata, this means that the transaction is rolled back and the router is deleted12:11
jschwarzanilvenkata, this will cause the rpc worker to run line 296 and fail (because the router doesn't exist anymore)12:12
jschwarzanilvenkata, in short, because of the race everything is reverted, so no problems ;-)12:12
*** dedery_ has quit IRC12:12
*** nmagnezi has quit IRC12:12
*** kengo_sakai has quit IRC12:13
anilvenkatajschwarz, "router deleted" means12:14
*** achanda has quit IRC12:14
*** markvoelker has joined #openstack-neutron12:15
anilvenkatajschwarz, and none of the worker succesfully bound the router because of race right?12:15
jschwarzanilvenkata, it means that the Router db object was deleted (because the API worker that created it raised an exception)12:16
jschwarzanilvenkata, and yes12:16
jschwarzso no problems here :)12:16
anilvenkatajschwarz, but we want one of the worker should sucessfully bind and the other should see duplicate entry and ignore his binding12:17
jschwarzanilvenkata, that is the ultimate goal, yes12:17
jschwarzanilvenkata, but it's not something this patch means to achieve12:17
jschwarzanilvenkata, this is what the huge auto_schedule_routers wants to do12:18
jschwarzanilvenkata, https://review.openstack.org/#/c/285480/12:18
anilvenkatajschwarz, if we follow the same order  in binding, the second one will see duplicate entry right?12:18
*** wolverineav has joined #openstack-neutron12:18
jschwarzanilvenkata, yes, and it will throw an exception12:19
jschwarzanilvenkata, which is fine because we want it to revert anyway12:19
jschwarzanilvenkata, (create_ha_port_and_bind() just created one too many port bindings objects - we need to delete it)12:20
anilvenkatajschwarz, yes, revert his(second guys) change12:20
anilvenkatajschwarz, so why can't we follow the "same order" as we discussed here in the patch?12:21
jschwarzanilvenkata, we could12:21
*** pradk has quit IRC12:21
jschwarzanilvenkata, but since the "reverse order" doesn't hurt us, I must ask what's the benefit of doing this switch vs what the risks are12:22
jschwarzanilvenkata, the benefit is that the code will be more consistent, but the risks are that this small change will introduce more race conditions12:22
*** wolverineav has quit IRC12:23
anilvenkatajschwarz, in the "reverse order" both workers will fail to bind, if "same order" one worker will succeed and other will see duplicate entry and ignore trying the binding12:23
anilvenkatajschwarz, we can avoid race by forcing synchroniation12:24
*** edmondsw has joined #openstack-neutron12:24
jschwarzanilvenkata, that's not completely accurate - if the API worker fails, it will remove the router and will cause the RPC worker to also fail12:24
jschwarzanilvenkata, so it only fixes 50% of the cases12:25
jschwarzanilvenkata, in this sense 100% failure rate might be better than 50% failure rate12:25
*** panda has quit IRC12:26
anilvenkatajschwarz, "if the API worker fails, it will remove the router and will cause the RPC worker to also fail" this is with "same order"?12:26
jschwarzanilvenkata, this is with both orders12:26
*** panda has joined #openstack-neutron12:27
anilvenkatajschwarz, where is it removing(which line)? removing from what(which table)?12:27
*** javeriak has joined #openstack-neutron12:27
jschwarzanilvenkata, if line 342 raises a DBDuplicateEntry, such an error will propagate upwards all the way to create_router12:28
*** pradk has joined #openstack-neutron12:28
jschwarzanilvenkata, this will at the end remove the actual Router() DB object that was originally created and return a 500 HTTP error to the user12:28
*** eddima1 has joined #openstack-neutron12:30
*** tmorin has quit IRC12:30
anilvenkatajschwarz, then if we follow "same order", if rpc worker succesfully binds, for api worker we won't his L342, right?12:31
*** eddima has quit IRC12:31
*** eddima1 is now known as eddima12:31
anilvenkatajschwarz, L337 will take u to next router and no HTTP 500 error12:32
*** josecastroleon has joined #openstack-neutron12:32
*** salv-orl_ has quit IRC12:33
anilvenkatajschwarz, api worker won't hit L342 if rpc worker succesfully binds, right?12:33
*** salv-orlando has joined #openstack-neutron12:34
anilvenkatajschwarz, why we need to delete the router we can handle the race12:35
*** dedery_ has joined #openstack-neutron12:36
*** jpena is now known as jpena|lunch12:36
*** apoorv has quit IRC12:36
openstackgerritSayali Lunkad proposed openstack/neutron: Introduces ovo objects for security groups  https://review.openstack.org/28473812:37
*** salv-orlando has quit IRC12:38
*** p01nt3r75 has joined #openstack-neutron12:38
*** numans has quit IRC12:38
*** nplanel has quit IRC12:38
jschwarzanilvenkata, sorry, back12:38
*** javeriak has quit IRC12:39
*** mvk_ has joined #openstack-neutron12:39
*** dedery has quit IRC12:39
jschwarzanilvenkata, if the rpc worker successfully binds, the api worker WILL fail in line 342 (DBDuplicateEntry)12:40
jschwarzanilvenkata, this will cause create_router() to fail for the API worker12:40
jschwarzanilvenkata, and this will return 500 HTTP to the client12:40
*** dedery_ has quit IRC12:41
anilvenkatajschwarz, no it won't fail in L34212:41
anilvenkatajschwarz, because of L336 and L337(if "same order")12:42
anilvenkatajschwarz, if rpc worker binds, L337 will hit for api worker12:42
*** numan_ has quit IRC12:43
jschwarzanilvenkata, ahhh lol12:43
jschwarzanilvenkata, when you said "same order" i was thinking of putting the "port_binding.l3_agent_id" stuff after bind_router12:44
jschwarzie. change the way create_ha_port_and... works12:44
anilvenkatajschwarz, yes12:44
jschwarzerm.12:44
jschwarzok so lets say this is the case12:44
amotokiajo_: one question on qos dscp spec. can operators choose which qos feature is enabled or not?12:45
jschwarzanilvenkata, yes so in this case it indeed won't throw an error12:45
jschwarzso both will work12:45
ajo_amotoki, no, it's bound to the plugin they use12:45
anilvenkatajschwarz, yes12:45
jschwarzanilvenkata, my head hurts now12:45
jschwarz:<12:45
*** vikram_ has quit IRC12:45
ajo_amotoki, they can enable or not qos, and then they will get whatever the plugin provides, but it's all admin-only by default12:45
anilvenkatajschwarz, looks like I have eaten up your brain :) sorry12:45
ajo_amotoki, it could be an RFE (filtering the available rules)12:46
jschwarzanilvenkata, no apologies needed12:46
*** Unterd0g has quit IRC12:46
jschwarzanilvenkata, ok but still12:46
amotokiajo_: thanks. it hit me now, but I am not sure there is such need actually.12:46
jschwarzanilvenkata, in the "reverse order" this will still act the same12:47
jschwarzno?12:47
jschwarzah no because they will conflict12:47
jschwarzyes so this needs to be changed.12:47
*** vikram_ has joined #openstack-neutron12:48
anilvenkatajschwarz, my comment makes sense?12:48
*** Unterd0g has joined #openstack-neutron12:48
jschwarzanilvenkata, it does now, after we've discussed this in length12:49
*** prithiv has joined #openstack-neutron12:49
anilvenkatajschwarz, :)12:49
jschwarzanilvenkata, could you please try to describe the same scenario as we've discussed here in the review page?12:49
anilvenkatajschwarz, sure12:49
jschwarzanilvenkata, once you do I'll upload a new patchset that fixes this12:49
jschwarzanilvenkata, nice catch, btw :)12:49
anilvenkatajschwarz, thanks John12:49
*** javeriak has joined #openstack-neutron12:50
*** Marga_ has quit IRC12:51
*** nplanel has joined #openstack-neutron12:55
*** jhershbe has quit IRC12:55
*** jlibosva has quit IRC12:58
*** jlibosva has joined #openstack-neutron13:02
*** dane_leblanc has joined #openstack-neutron13:03
*** asingh has joined #openstack-neutron13:04
*** javeriak has quit IRC13:04
*** jlibosva1 has joined #openstack-neutron13:06
*** ranjithd has joined #openstack-neutron13:07
*** jlibosva has quit IRC13:08
*** salv-orlando has joined #openstack-neutron13:11
*** javeriak has joined #openstack-neutron13:12
*** haleyb_ has joined #openstack-neutron13:16
*** prapulla has quit IRC13:18
*** Marga_ has joined #openstack-neutron13:18
*** links has quit IRC13:21
*** yfried has quit IRC13:21
*** akshai has joined #openstack-neutron13:21
*** yfried has joined #openstack-neutron13:22
*** prithiv has quit IRC13:23
*** prithiv has joined #openstack-neutron13:23
*** tiswanso has joined #openstack-neutron13:23
*** mfranc213 has joined #openstack-neutron13:24
*** cleong has joined #openstack-neutron13:27
*** kawa2014 has quit IRC13:27
*** vhosakot has joined #openstack-neutron13:27
*** kawa2014 has joined #openstack-neutron13:27
*** neelashah has quit IRC13:30
*** lajos-katona has quit IRC13:30
*** dane_leblanc has quit IRC13:34
*** bizarrodan is now known as dansmith13:35
*** al_indigo has joined #openstack-neutron13:38
al_indigoHello! I want to make one simple thing. I have Liberty cloud, networking is based on Neutron, 6 projects and 2 external networks. I want two projects to be able to allocate floating IPs only from the first external network, and the rest four projects - from the second.13:39
al_indigoI have tried RBAC to provide access for external networks for separate projects so they are hidden in "Networks" tab for the correct projects.13:40
*** dencaval has quit IRC13:40
al_indigoNethertheless each user in each project still can allocate IPs from any of two external nets. How can I do it correctly?13:41
*** gampel1 has joined #openstack-neutron13:41
al_indigo(one external network is really external Internet, and the second is internal network and I do not want to intersect them in any way)13:41
al_indigoAnyone?13:42
*** dane_leblanc has joined #openstack-neutron13:44
*** mgoddard_ has joined #openstack-neutron13:45
*** pradk_ has joined #openstack-neutron13:45
*** pradk has quit IRC13:45
*** pradk_ is now known as pradk13:46
*** vhoward has joined #openstack-neutron13:46
*** dslevin has joined #openstack-neutron13:48
*** janzian has joined #openstack-neutron13:48
*** dslevin has quit IRC13:48
*** hynekm has quit IRC13:48
*** mgoddard has quit IRC13:48
*** dslevin has joined #openstack-neutron13:49
*** dslevin has quit IRC13:49
*** jpena|lunch is now known as jpena13:50
*** dslevin has joined #openstack-neutron13:50
slaweqajo_: amotoki: should I do something more with https://review.openstack.org/#/c/300679/13:52
slaweqor it will be now merged automatically if gate tests will pass?13:52
ajo_slaweq, once tests pass13:52
slaweqok, thx13:52
slaweqI thought that but I don't see it in queue on http://status.openstack.org/zuul/13:53
slaweqand that's why I'm asking :)13:53
*** shausy has quit IRC13:55
*** mgoddard_ has quit IRC13:55
*** shausy has joined #openstack-neutron13:55
*** mgoddard has joined #openstack-neutron13:55
*** yamamoto_ has quit IRC13:56
*** yamamoto has joined #openstack-neutron13:56
*** dslevin has left #openstack-neutron13:57
*** moshele has quit IRC13:58
*** mlavalle has joined #openstack-neutron13:58
*** josecastroleon has quit IRC13:59
openstackgerritVictor Howard proposed openstack/neutron-specs: Spec for ML2/OVS QoS support with dscp markings  https://review.openstack.org/19028513:59
*** ekuris has quit IRC14:00
*** jlibosva1 has quit IRC14:00
*** javeriak_ has joined #openstack-neutron14:01
*** Marga_ has quit IRC14:02
*** jhershbe has joined #openstack-neutron14:02
*** enriquetaso has joined #openstack-neutron14:02
*** javeriak has quit IRC14:03
*** singhj has joined #openstack-neutron14:03
*** shausy has quit IRC14:03
*** shausy has joined #openstack-neutron14:04
*** mkolesni_ has quit IRC14:04
*** woodburn has joined #openstack-neutron14:06
*** EkulTails has joined #openstack-neutron14:07
*** kawa2014 has quit IRC14:07
*** abregman has quit IRC14:08
*** sridharg has quit IRC14:09
*** korzen has quit IRC14:09
*** knikolla has joined #openstack-neutron14:09
*** nplanel has quit IRC14:09
*** shausy has quit IRC14:09
*** moshele has joined #openstack-neutron14:09
*** shausy has joined #openstack-neutron14:10
*** anilvenkata has quit IRC14:11
*** kawa2014 has joined #openstack-neutron14:11
*** achanda has joined #openstack-neutron14:12
*** asingh has quit IRC14:12
*** Shahid_ has quit IRC14:14
*** jhershbe has quit IRC14:14
*** javeriak_ has quit IRC14:14
*** ivase_ has joined #openstack-neutron14:15
*** doug-fish has joined #openstack-neutron14:15
*** ajmiller has joined #openstack-neutron14:16
*** achanda has quit IRC14:17
*** oanson has quit IRC14:17
*** krtaylor has quit IRC14:18
*** regXboi has joined #openstack-neutron14:20
*** wolverineav has joined #openstack-neutron14:20
slaweqajo_: do You think I could try to work on https://bugs.launchpad.net/neutron/+bug/1560961 maybe?14:20
openstackLaunchpad bug 1560961 in neutron "[RFE] Allow instance-ingress bandwidth limiting" [Wishlist,Confirmed]14:20
slaweqit is not assigned to anyone for now14:20
ajo_slaweq, hdaniel contacted me today about it14:20
slaweqah, ok14:21
ajo_hdaniel, but may be you can both coordinate14:21
*** neelashah has joined #openstack-neutron14:21
hdanielslaweq: hi, I missed the context here14:21
ajo_it will need LB & OVS implementation, in fact I owe him a link to the old OVS implementation by gsagie which just did ingress :)14:21
slaweqI thought about it14:21
amotokislaweq: I think it is a good idea to show your interest in that bug :)14:21
*** asingh has joined #openstack-neutron14:21
slaweqin fact I made ingress limit by mistake for linuxbrige agent :)14:22
slaweqso I have some "experience" in that :P14:22
*** claudiub has quit IRC14:22
slaweqhdaniel: so If You will work on that and want some help, just tell me14:24
openstackgerritEyal proposed openstack/neutron: Simplify chained comparison  https://review.openstack.org/30115614:24
slaweqI would like to do help on that if it would be possible14:24
hdanielslaweq: I see. if you have something going on there - I don't mind moving aside14:24
*** wolverineav has quit IRC14:24
*** haplo37 has joined #openstack-neutron14:27
*** edmondsw has quit IRC14:27
*** EinstCrazy has joined #openstack-neutron14:28
*** javeriak has joined #openstack-neutron14:28
slaweqajo_: amotoki: so I talked with hdaniel and I will take it now14:29
hdanielajo_: ^14:29
slaweqand hdaniel will help me on it14:29
ajo_slaweq++ , hdaniel++14:29
ajo_sounds like a plan, but slaweq I believe that still requires drivers approval14:29
slaweqI was thinking about implement first ovs and lb agents14:30
slaweqwith tc in both cases14:30
ajo_slaweq, I'm not sure SR-IOV can handle VM-ingres14:31
slaweqit should be quite easy to do14:31
*** shausy has quit IRC14:31
slaweqabout SR-IOV I don't know too14:31
ajo_moshele,  ^  ?14:31
*** achanda has joined #openstack-neutron14:31
slaweqbut IMHO for start work those two agents would be fine, no?14:32
*** banix has joined #openstack-neutron14:32
ajo_slaweq, yes: plus API, objects and DB models14:32
ajo_slaweq, you may need to add a direction to the bw limit rule :)14:33
mosheleajo_: sorry, what is the question?14:33
*** prateek has joined #openstack-neutron14:33
ajo_moshele, if SR-IOV can handle ingress bandwidth limit14:33
*** prateek is now known as parora14:33
slaweqajo_: yep14:33
slaweqI will do it14:33
mosheleajo_: we can to ip link ... --min-rate on the vf (but I have test it)14:34
mosheleajo_: I mean haven't test it14:34
ajo_slaweq, refer to https://review.openstack.org/#/c/211520/  for OVS14:35
*** amotoki has quit IRC14:35
ajo_:-)14:35
ajo_slaweq, and add gsagie as co-author, it was his original job14:35
*** asingh has quit IRC14:35
ajo_moshele, I don't mean min/max, I mean ingress/egress14:35
ajo_moshele, I know currently max handles egress, but I guess not ingress, right?14:36
slaweqajo_: ok, thx14:36
ajo_once the packet is there, they don't drop it14:36
Sam-I-Amingress limiting is sort of a farse14:36
mosheleajo_: right I need to check this with the driver team14:36
*** tonytan4ever has joined #openstack-neutron14:36
Sam-I-Amit pretty much needs to be implemented as egress filtering somewhere else to be effective14:36
ajo_moshele, ack, it only makes sense for TCP or flow controlled protocols, since UDP for example will not care if you start dropping the ingress packets above max...14:37
ajo_well, the application will certainly notice it..14:37
ajo_but not the sender14:37
*** singhj has quit IRC14:37
ajo_Sam-I-Am, not totally a farse :)14:37
ajo_Sam-I-Am, it works for TCP14:37
Sam-I-Amyeah, but not everything14:38
*** singhj has joined #openstack-neutron14:38
*** andymaier has joined #openstack-neutron14:38
ajo_Sam-I-Am, but of course, for other protocols, we may need ECN, or out of band communication to the network infrastructure, or other nodes14:38
Sam-I-Amand it might be easier to dink with window sizes than typical limiting functions14:38
*** achanda has quit IRC14:38
ajo_to tell the other end... throttle down...14:38
*** tmorin has joined #openstack-neutron14:38
*** rmart04 has joined #openstack-neutron14:42
*** ababich has joined #openstack-neutron14:45
*** asingh has joined #openstack-neutron14:46
*** andymaier has quit IRC14:47
*** jprovazn has joined #openstack-neutron14:48
*** tmorin has quit IRC14:49
*** singhj has quit IRC14:51
*** jlibosva has joined #openstack-neutron14:52
*** parora has quit IRC14:52
*** kbringard has joined #openstack-neutron14:53
*** itzikb has quit IRC14:54
*** korzen has joined #openstack-neutron14:57
*** crose has joined #openstack-neutron14:58
*** mickeys has joined #openstack-neutron14:59
ihrachysupgrades meeting in #openstack-meeting-alt in 1 min :)15:00
rossella_syeah15:00
*** mlavalle has quit IRC15:00
*** daneyon has joined #openstack-neutron15:00
*** edmondsw has joined #openstack-neutron15:02
*** krtaylor has joined #openstack-neutron15:02
*** haleyb_ has quit IRC15:02
*** Prem_ has joined #openstack-neutron15:02
*** iyamahat has joined #openstack-neutron15:03
*** vishwanathj has joined #openstack-neutron15:03
*** mlavalle has joined #openstack-neutron15:03
*** daneyon_ has joined #openstack-neutron15:04
*** mickeys has quit IRC15:04
dasmo/15:05
*** mhickey has joined #openstack-neutron15:05
*** imcsk8 has joined #openstack-neutron15:06
*** daneyon has quit IRC15:07
*** neelashah has quit IRC15:08
*** asingh has quit IRC15:08
*** singhj has joined #openstack-neutron15:09
*** javeriak has quit IRC15:10
*** EinstCrazy has quit IRC15:10
openstackgerritJohn Schwarz proposed openstack/neutron: Fix a race with auto_schedule of HA routers  https://review.openstack.org/28440015:11
openstackgerritJohn Schwarz proposed openstack/neutron: Add ALLOCATING state to routers  https://review.openstack.org/25705915:11
openstackgerritJohn Schwarz proposed openstack/neutron: Remove auto_schedule_routers codepath  https://review.openstack.org/28548015:11
*** cshahani has joined #openstack-neutron15:12
*** haleyb_ has joined #openstack-neutron15:13
*** singhj has quit IRC15:13
*** hkominos has quit IRC15:15
*** singhj has joined #openstack-neutron15:15
*** asingh has joined #openstack-neutron15:16
*** oshvartz has quit IRC15:16
*** kbringard has quit IRC15:16
*** swat30 has joined #openstack-neutron15:16
*** kbringard has joined #openstack-neutron15:16
*** asingh has quit IRC15:17
*** prithiv has quit IRC15:18
*** haleyb_ has quit IRC15:18
*** yamahata has joined #openstack-neutron15:19
*** singhj has quit IRC15:20
*** vikram_ has quit IRC15:20
*** prithiv has joined #openstack-neutron15:22
*** p01nt3r75 has quit IRC15:22
*** jlibosva has quit IRC15:22
*** daneyon_ has quit IRC15:22
*** jlibosva has joined #openstack-neutron15:23
*** daneyon has joined #openstack-neutron15:23
*** neelashah has joined #openstack-neutron15:27
*** abregman has joined #openstack-neutron15:29
*** asingh has joined #openstack-neutron15:31
*** johnsom has joined #openstack-neutron15:31
*** bjornar has quit IRC15:32
mhickeyihrachys, korzen, rossella_s: Hey. Just sorting out merge conflicts on some patches. One one after merging, I am getting error in: neutron.tests.unit.objects.test_subnetpool.SubnetPoolPrefixDbObjectTestCase.test_update_no_field_to_update_no_field_update15:32
mhickeyHave you seen an issue lately/15:32
mhickey?15:32
ihrachysmhickey: well, you probably broke some test with it15:33
mhickeyihrachys: I figure!15:33
*** nlahouti has joined #openstack-neutron15:33
mhickeyihrachys: let me dig a bit more; just wondering if it was something already known15:34
*** asingh has quit IRC15:36
*** fedexo has joined #openstack-neutron15:37
*** asingh has joined #openstack-neutron15:38
*** Swami has joined #openstack-neutron15:40
*** jistr has quit IRC15:41
*** salv-orlando has quit IRC15:42
openstackgerritDarek Smigiel proposed openstack/neutron: API tests: Check extensions with proper functions  https://review.openstack.org/29789015:42
*** asingh has quit IRC15:43
*** Sukhdev has joined #openstack-neutron15:43
*** asingh has joined #openstack-neutron15:43
electrocucarachaihrachys: before the upgrades meeting I was trying to implement bgp.15:44
*** shashank_hegde has joined #openstack-neutron15:44
electrocucarachaihrachys: I had some progress but it's failing with "neutron.objects.base.NeutronSyntheticFieldMultipleForeignKeys: Synthetic field peers shouldn't have more than one foreign key"15:45
dasmelectrocucaracha: BGP? "Big Giant Pencil"? http://lists.openstack.org/pipermail/openstack-dev/2016-April/091217.html15:45
dasm;)15:45
electrocucarachadasm: hahaha that one15:45
*** tbachman has quit IRC15:46
electrocucarachashould I submit the change as it is?  only for future references?15:47
electrocucarachaihrachys: ^^15:47
*** david-lyle_ has quit IRC15:48
*** david-lyle has joined #openstack-neutron15:48
*** amotoki has joined #openstack-neutron15:48
*** xenogear has joined #openstack-neutron15:50
*** xenogear has joined #openstack-neutron15:50
*** josecastroleon has joined #openstack-neutron15:51
*** javeriak has joined #openstack-neutron15:52
*** tbachman has joined #openstack-neutron15:54
ihrachyselectrocucaracha: you can if it's worth reusing :)15:56
*** tbachman has quit IRC15:56
electrocucarachaihrachys: hahaha good point15:57
*** singhj has joined #openstack-neutron15:57
electrocucarachawhat I have found valuable is that this is raising neutron.objects.base.NeutronSyntheticFieldMultipleForeignKeys, not sure if we have to adapt the current implementation15:58
*** asingh has quit IRC15:58
*** asingh has joined #openstack-neutron15:59
*** banix has quit IRC15:59
*** crose has quit IRC16:00
*** jschwarz has quit IRC16:01
*** eddima has quit IRC16:02
*** jhershbe has joined #openstack-neutron16:03
ajo_ihrachys, : http://developer.openstack.org/api-ref-networking-v2-ext.html#updateLoadBalancerv216:06
*** tiswanso has quit IRC16:06
ajo_you can see the vip from that api, but you have no control16:06
ihrachysajo_: yes, because that's port fixed IP16:07
ajo_yes16:07
ihrachysajo_: you can't easily grab the port and move to another load balancer16:07
ajo_ihrachys, if you see how octavia does that16:07
ajo_ihrachys, you will see it creates a port (not used)16:07
ajo_and then it grabs the ip address of that port, and adds it to allowed address pairs of the amphora (s?)16:07
ajo_brb16:08
*** vikram has joined #openstack-neutron16:08
*** haukebruno has quit IRC16:09
*** mhickey has quit IRC16:10
*** anshul has quit IRC16:11
*** claudiub has joined #openstack-neutron16:11
*** scheuran has quit IRC16:11
*** tiswanso has joined #openstack-neutron16:12
*** javeriak has quit IRC16:15
openstackgerritAssaf Muller proposed openstack/neutron: Change get_root_helper_child_pid to stop when it finds cmd  https://review.openstack.org/29479816:15
*** banix has joined #openstack-neutron16:16
*** yfried has quit IRC16:16
*** ushkalim has quit IRC16:17
amulleramotoki: ihrachys: ^16:17
jlibosvaamuller: have you read my latest general comment? thoughts?16:18
*** ramishra has joined #openstack-neutron16:20
*** wolverineav has joined #openstack-neutron16:22
*** sakthi has joined #openstack-neutron16:22
*** fedexo has quit IRC16:22
sakthihi16:22
amullerjlibosva: by 'changing how processes are stopped' you mean that we check their cmdline?16:23
sakthirequired help in  nw architecture16:23
*** josecastroleon has quit IRC16:23
*** tbachman has joined #openstack-neutron16:24
*** javeriak has joined #openstack-neutron16:24
*** gampel1 has left #openstack-neutron16:25
sakthiIn my lab I have two separate network, initially both are working fine, now one of the network keep on fluctuating continuously. but I didnt get any error log in any neutron-server as well as l3 agent16:25
*** viveknarasimhan has joined #openstack-neutron16:25
*** p01nt3r75 has joined #openstack-neutron16:26
*** panda has quit IRC16:26
*** wolverineav has quit IRC16:26
*** panda has joined #openstack-neutron16:27
*** Marga_ has joined #openstack-neutron16:27
jlibosvaamuller: no, I mean the former behavior was to stop the 'childest' process. At the bottom of process tree. We need to make sure we don't rely on this behavior (eg. in IPmonitor or ovsdbmonitor)16:28
jlibosvaamuller: which brings us to the question whether we will need to define, who will be killed on stop()16:28
sakthiplease clarify the following: 1) creating more virtual routers raising any problem 2) Using  more VLAN tags creating any problem16:28
jlibosvaamuller: like in systemd16:28
*** josecastroleon has joined #openstack-neutron16:29
yottatsaHi! Is there any working VLAN trunking for OpenStack Neutron? https://specs.openstack.org/openstack/neutron-specs/specs/kilo/nfv-vlan-trunks.html16:29
amotokijlibosva: according to the docstirng of get_root_helper_child_pid, the original code does not assume a process invoked by rootwrap has more child(ren).16:30
amotokijlibosva: my current understanding is that the proposed change is to find a direct child invoked by rootwrap. is it correct?16:31
jlibosvaamotoki: who reads docstrings when writing code :) I'm just saying we can fix fullstack with it but break some other part16:31
jlibosvaamotoki: yes, that's correct16:31
jlibosvaamotoki: and I think it was meant like this from beginning16:31
*** nmagnezi_ has quit IRC16:31
amulleryottatsa: not at this time16:32
*** barra204 has quit IRC16:32
amulleryottatsa: oh sorry I read the wrong spec16:32
amotokijlibosva: agree. it was the intention but was actually not in the code.16:32
amulleryottatsa: yeah it should work with linux bridge agent16:32
*** sakthi has quit IRC16:32
yottatsaamuller what about ovs?16:32
amulleryottatsa: that doesn't work16:33
*** neeti has quit IRC16:33
*** korzen has quit IRC16:33
yottatsaamuller thnx!16:33
*** ramishra has quit IRC16:33
*** gvrangan_ has joined #openstack-neutron16:33
*** oanson has joined #openstack-neutron16:34
*** igordcard_ has quit IRC16:34
*** rossella_s has quit IRC16:34
*** ramishra has joined #openstack-neutron16:35
*** rossella_s has joined #openstack-neutron16:35
*** igordcard has joined #openstack-neutron16:35
*** igordcard has quit IRC16:35
*** winggundamth has quit IRC16:35
*** winggundamth has joined #openstack-neutron16:36
amotokijlibosva: i am not sure we need termination mode. it is worth checked if someone relies on the previous behavior as you mentioned.16:36
*** igordcard has joined #openstack-neutron16:36
*** igordcard has quit IRC16:36
*** Marga_ has quit IRC16:36
*** igordcard has joined #openstack-neutron16:37
amullerjlibosva: functional tests and the tempest scenario tests use the OVS agent with the ovsdb monitor16:38
amullerjlibosva: and the L3 HA functional tests use the ip monitor16:38
amullerjlibosva: tests passed16:38
amullerjlibosva: that's good enough for me16:38
*** shashank_hegde has quit IRC16:39
thorstHi all.  Can the SR-IOV agent reside on the same compute node as a Linux Bridge/OVS agent?  To allow some workloads to have access to SR-IOV, but others get the standard networking.16:39
thorstI didn't see that in the networking guide and was wondering if that is possible.16:40
yottatsathorst yep16:40
thorstyottatsa: Awesome.  TIL.  Thx!16:40
*** wolverineav has joined #openstack-neutron16:40
yottatsathorst the only thing you should check: interface you're using for SR-IOV should not be used for vlan-segmentated OVS/LB16:41
thorstyottatsa: why is that?16:41
*** igordcard has quit IRC16:41
thorsto...nevermind16:41
*** vikram has quit IRC16:42
thorstthat makes sense16:42
*** garyk has quit IRC16:42
*** banix has quit IRC16:43
yottatsaIf you enable SR-IOV on NIC, internal switch on it will prohibit using unrequested VLAN tags on PF, so your OVS didn't get any VLAN traffic on PF (though I'm not sure about LB)16:43
*** salv-orlando has joined #openstack-neutron16:43
*** Marga_ has joined #openstack-neutron16:44
yottatsaeasy speaking, PF will be access, not trunk16:44
*** jhershbe has quit IRC16:46
*** numan_ has joined #openstack-neutron16:46
*** ramishra has quit IRC16:46
*** nmagnezi_ has joined #openstack-neutron16:47
*** igordcard has joined #openstack-neutron16:47
*** rcernin has quit IRC16:48
*** asingh has quit IRC16:48
*** moshele has quit IRC16:49
*** SteffanW has joined #openstack-neutron16:49
*** bjornar has joined #openstack-neutron16:50
*** igordcard has quit IRC16:50
*** igordcard has joined #openstack-neutron16:50
*** salv-orlando has quit IRC16:52
*** asingh has joined #openstack-neutron16:52
*** busterswt has joined #openstack-neutron16:54
thorstyottatsa: yeah, that makes a lot of sense.  Thx!16:54
*** oanson has quit IRC16:54
*** oanson has joined #openstack-neutron16:55
*** banix has joined #openstack-neutron16:55
*** javeriak has quit IRC16:55
openstackgerritDaniel Berrange proposed openstack/os-vif: vif_plug_ovs: merge both plugins into one  https://review.openstack.org/30124316:58
*** josecastroleon has quit IRC16:59
ihrachysjlibosva: do you have an ETA for std attr decorator patch?17:00
*** singhj has quit IRC17:00
*** javeriak has joined #openstack-neutron17:00
*** igordcard has quit IRC17:02
*** rmart04 has quit IRC17:03
*** rossella_s has quit IRC17:03
jlibosvaamuller: not sure I'm glad you're fine with tempest passing considering it's enough :D I don't think we test whether processes are cleaned up properly in functional tests17:03
*** rossella_s has joined #openstack-neutron17:04
*** oanson has quit IRC17:04
jlibosvaamuller: but that was just a thought I wanted to expand17:04
jlibosvaihrachys: I'll try to hurry. Let's say it will be the first thing I do tomorrow. I can show you what I have now and you tell me whether it's fine so I continue with accomodating UTs17:04
amullerjlibosva: test_ip_monitor_lifecycle17:05
jlibosvaI'm afraid it could be less readable17:05
ihrachysjlibosva: now?17:05
jlibosvaihrachys: if you're still next to me then why not :)17:05
*** armax has joined #openstack-neutron17:07
*** p01nt3r75 has quit IRC17:07
*** viveknarasimhan has quit IRC17:09
*** prithiv has quit IRC17:09
*** prithiv has joined #openstack-neutron17:09
*** ircuser-1 has quit IRC17:10
*** amuller is now known as amuller_afk17:10
*** shashank_hegde has joined #openstack-neutron17:11
*** hdaniel has quit IRC17:12
*** prithiv has quit IRC17:13
*** kbringard1 has joined #openstack-neutron17:13
*** neelashah has quit IRC17:14
*** tmorin has joined #openstack-neutron17:14
*** wolverineav has quit IRC17:15
*** kbringard has quit IRC17:15
*** josecastroleon has joined #openstack-neutron17:15
*** tbachman has quit IRC17:15
*** Sukhdev has quit IRC17:16
*** shashank_hegde has quit IRC17:19
*** jhershbe has joined #openstack-neutron17:19
*** rickyrem has joined #openstack-neutron17:19
*** gvrangan has joined #openstack-neutron17:20
*** afaranha has quit IRC17:20
*** claudiub|2 has joined #openstack-neutron17:21
openstackgerritMerged openstack/neutron: Improve handle port_update and port_delete events in ovs qos agent  https://review.openstack.org/30067917:21
*** gvrangan_ has quit IRC17:21
*** jlanoux has quit IRC17:22
*** nmagnezi_ has quit IRC17:23
*** amotoki has quit IRC17:23
openstackgerritlokesh s proposed openstack/python-neutronclient: log SHA1 hash of  X-Auth-Token value  https://review.openstack.org/29863717:24
openstackgerritNate Johnston proposed openstack/neutron: QoS DSCP use mod_flow instead of mod_flows  https://review.openstack.org/30063517:24
*** claudiub has quit IRC17:24
*** ihrachys has quit IRC17:24
*** gvrangan has quit IRC17:24
jlibosvaamuller_afk: that's exactly what I meant. If ip monitor spawns child processes, we don't check they are left orphaned17:25
*** john-davidge has joined #openstack-neutron17:25
john-davidgecarl_baldwin: Ping17:26
*** sridhar_ram has joined #openstack-neutron17:26
carl_baldwinjohn-davidge: pong17:26
* carl_baldwin mobile atm17:27
john-davidgecarl_baldwin: Hey Carl, looks like I rubbed you the wrong way with my comment on https://review.openstack.org/#/c/288774 last week. Apologies if it came off that way. The part you say should be clear was not clear to me, so I though that was a legitimate question. Anyway, wanted to clear the air.17:29
carl_baldwinjohn-davidge: no worries, sorry for my reply.17:29
*** jlibosva has quit IRC17:30
*** jhershbe has quit IRC17:30
john-davidgecarl_baldwin: No worries :) I assume you were having a bad day!17:30
*** SauloAislan has joined #openstack-neutron17:30
carl_baldwinLast week was a long week17:30
john-davidgecarl_baldwin: Last month was a long month!17:31
*** tiswanso has quit IRC17:33
*** tiswanso has joined #openstack-neutron17:33
*** claudiub|2 has quit IRC17:33
*** oanson has joined #openstack-neutron17:33
*** claudiub has joined #openstack-neutron17:35
*** xenogear has quit IRC17:35
*** davidsha has quit IRC17:38
*** vhosakot has quit IRC17:39
*** kevo has joined #openstack-neutron17:39
SauloAislanHello, I want to save external information in neutron-network body. I would put in description field, but network doesn't have. Any suggestions?17:40
*** vhosakot has joined #openstack-neutron17:41
*** afaranha has joined #openstack-neutron17:41
*** mvk_ has quit IRC17:42
*** shashank_hegde has joined #openstack-neutron17:44
*** josecastroleon has quit IRC17:45
*** eilert has joined #openstack-neutron17:45
*** wolverineav has joined #openstack-neutron17:46
*** moshele has joined #openstack-neutron17:46
*** wolverineav has quit IRC17:46
*** jpena is now known as jpena|off17:46
*** wolverineav has joined #openstack-neutron17:46
*** oanson has quit IRC17:48
*** rickyrem has quit IRC17:49
*** dave-mccowan has joined #openstack-neutron17:50
*** s3wong has joined #openstack-neutron17:51
haleybSauloAislan: networks have a description field starting in Mitaka17:53
*** nlahouti has quit IRC17:55
SauloAislanThanks haleyb17:56
*** amuller_afk is now known as amuller18:00
*** sambetts is now known as sambetts|afk18:00
*** nlahouti has joined #openstack-neutron18:01
*** yamamoto has quit IRC18:01
*** yamamoto has joined #openstack-neutron18:01
*** anilvenkata has joined #openstack-neutron18:02
*** vhosakot has quit IRC18:02
*** doug-fish has quit IRC18:03
*** doug-fish has joined #openstack-neutron18:03
*** doug-fish has quit IRC18:03
*** davideag_ has quit IRC18:04
*** tidwellr has joined #openstack-neutron18:04
*** nlahouti has quit IRC18:06
*** jlibosva has joined #openstack-neutron18:10
*** salv-orlando has joined #openstack-neutron18:11
*** neelashah has joined #openstack-neutron18:11
SauloAislanHello haleyb, neutron-network body has another field (tags). Can i use this field? My problem is to save an external network id in neutron-network body.18:13
*** ircuser-1 has joined #openstack-neutron18:13
*** numan_ has quit IRC18:14
haleybSauloAislan: tags is meant for something else, I don't have the spec handy at the moment18:14
*** banix has quit IRC18:15
*** neelashah has quit IRC18:15
*** mfranc213 has quit IRC18:17
*** nlahouti has joined #openstack-neutron18:17
SauloAislanOk haleyb, i will use description. Thanks.18:17
*** daneyon_ has joined #openstack-neutron18:18
*** ircuser-1 has quit IRC18:20
*** daneyon has quit IRC18:20
anilvenkatakevinbenton, Can you please review https://review.openstack.org/#/c/255237/ ?18:21
*** shivrao has joined #openstack-neutron18:21
*** ircuser-1 has joined #openstack-neutron18:21
openstackgerritRitesh Anand proposed openstack/neutron: Add IPv6 Prefix Delegation support for DVR  https://review.openstack.org/27765718:22
*** neelashah has joined #openstack-neutron18:22
*** mgoddard_ has joined #openstack-neutron18:23
*** jprovazn has quit IRC18:23
*** ircuser-1 has quit IRC18:24
*** javeriak has quit IRC18:25
*** ircuser-1 has joined #openstack-neutron18:25
*** nlahouti has quit IRC18:26
*** rickyrem has joined #openstack-neutron18:26
*** mgoddard has quit IRC18:27
*** salv-orlando has quit IRC18:27
*** mgoddard_ has quit IRC18:28
*** banix has joined #openstack-neutron18:29
*** singhj has joined #openstack-neutron18:31
*** salv-orlando has joined #openstack-neutron18:32
*** davideagnello has joined #openstack-neutron18:33
*** garyk has joined #openstack-neutron18:33
*** jlibosva has quit IRC18:34
*** sleviim has joined #openstack-neutron18:35
*** sleviim has quit IRC18:35
*** nyechiel_ has quit IRC18:36
*** mgoddard has joined #openstack-neutron18:37
openstackgerritDarek Smigiel proposed openstack/python-neutronclient: Add project-id to neutronclient  https://review.openstack.org/29842518:37
*** nlahouti has joined #openstack-neutron18:38
*** kawa2014 has quit IRC18:38
*** rickyrem1 has joined #openstack-neutron18:38
*** kawa2014 has joined #openstack-neutron18:38
*** rickyrem has quit IRC18:39
*** Sukhdev has joined #openstack-neutron18:39
*** jlibosva has joined #openstack-neutron18:41
*** tbachman has joined #openstack-neutron18:41
kfox1111so, I've got a neutron that's misbehaving again. it seems like nova may be hitting neutron harder then it can handle. its spawned thousands of openssl cms commands which are waiting for input from neutron.18:41
*** salv-orlando has quit IRC18:43
openstackgerritDarek Smigiel proposed openstack/neutron-specs: Moving to Keystone v3 API  https://review.openstack.org/25736218:43
*** gvrangan has joined #openstack-neutron18:44
*** matrohon has joined #openstack-neutron18:49
*** moshele has quit IRC18:52
*** tmorin has quit IRC18:56
*** vhosakot has joined #openstack-neutron18:58
*** amuller has quit IRC18:59
*** nlahouti has quit IRC19:00
*** SteffanW has quit IRC19:04
*** kawa2014 has quit IRC19:05
*** kawa2014 has joined #openstack-neutron19:05
*** EkulTails1 has joined #openstack-neutron19:06
*** Marga_ has quit IRC19:06
*** EkulTails has quit IRC19:06
*** Marga_ has joined #openstack-neutron19:06
*** slaweq_ has joined #openstack-neutron19:07
*** kawa2014 has quit IRC19:07
*** nlahouti has joined #openstack-neutron19:08
*** salv-orlando has joined #openstack-neutron19:09
*** Marga_ has quit IRC19:12
*** mgoddard has quit IRC19:14
*** salv-orlando has quit IRC19:14
*** salv-orlando has joined #openstack-neutron19:14
*** imcsk8 is now known as imcsk8|lunch19:15
*** salv-orlando has quit IRC19:16
*** anshul has joined #openstack-neutron19:16
*** netsin has joined #openstack-neutron19:16
*** salv-orlando has joined #openstack-neutron19:16
*** salv-orlando has quit IRC19:17
*** ociuhandu has quit IRC19:17
*** salv-orlando has joined #openstack-neutron19:17
*** daneyon has joined #openstack-neutron19:18
*** ranjithd has quit IRC19:19
*** daneyon_ has quit IRC19:20
*** ranjithd has joined #openstack-neutron19:21
*** slaweq_ has quit IRC19:23
*** yamahata has quit IRC19:24
*** iyamahat has quit IRC19:25
openstackgerritBrian Haley proposed openstack/python-neutronclient: Log SHA1 hash of X-Auth-Token value  https://review.openstack.org/29863719:26
dasmclayton: hey man. are you here?19:27
clayton?19:27
dasmi have an error in jenkins with your test19:27
claytonlink?19:27
dasmand i'd like to know how to find what happened19:27
dasmclayton: https://review.openstack.org/#/c/297890/19:27
dasmclayton: maybe you'll be able to help me19:28
claytonlooking19:28
claytonthat appears to have failed dsvm-functional because the test took too long19:28
claytonthere is a 90min gap in the log here http://logs.openstack.org/90/297890/4/check/gate-neutron-dsvm-functional/69997de/console.html#_2016-04-04_17_27_05_72719:29
dasmclayton: yeah. i've noticed this one19:30
dasm2016-04-04 17:27:05.727 | 2016-04-04 17:27:05.710 |19:30
dasm2016-04-04 19:06:23.229 | /home/jenkins/workspace/gate-neutron-dsvm-functional/devstack-gate/functions.sh: line 1148: 30460 Killed                  timeout -s 9 ${REMAINING_TIME}m bash -c "source $WORKSPACE/devstack-gate/functions.sh && $cmd"19:30
claytonI think that's just a bad nodepool node19:30
dasmclayton: so, just recheck? maybe we should think how to improve this issue?19:30
claytonI'd just recheck, someone with more experience might say otherwise19:31
dasmclayton: ok, i'll recheck. but i'm curious how we can get rid of this kind of situation.19:32
dasmclayton: thanks19:32
*** nlahouti has quit IRC19:34
*** matrohon has quit IRC19:38
*** Sukhdev has quit IRC19:38
*** iyamahat has joined #openstack-neutron19:44
claytonnp19:44
*** kbringard has joined #openstack-neutron19:48
*** tbachman_ has joined #openstack-neutron19:48
*** tbachman has quit IRC19:48
*** tbachman_ is now known as tbachman19:48
openstackgerritvenkata anil proposed openstack/neutron: create HA router resources before router creation  https://review.openstack.org/30131619:50
*** kbringard1 has quit IRC19:50
*** EkulTails1 has quit IRC19:50
*** shakamunyi has joined #openstack-neutron19:51
jaypipescarl_baldwin: question on the routed networks spec... in the section on DHCP Scheduling, the spec mentions that the scheduler will take care to ensure that all such segments have a DHCP server. How does the scheduler know the physical topology of the network in order to place a DHCP agent on a node that has network connectivity to the broadcast domain the segment handles?19:51
carl_baldwinjaypipes: the host / segment mapping discussed in the spec.19:51
jaypipescarl_baldwin: guh, ok, sorry just getting to that part :) sorry for bothering you.19:52
carl_baldwinjaypipes: No worries.  Glad to help.19:52
*** prometheanfire has joined #openstack-neutron19:52
prometheanfireso, it's my understanding that ipv6-only tenant networks work in mitaka?19:52
anilvenkatajohn-davidge, can u please review PD change https://review.openstack.org/#/c/241227/19:54
john-davidgeanilvenkata: Sure19:54
anilvenkatajohn-davidge, thanks John19:54
*** banix has quit IRC19:57
*** shakamunyi has quit IRC19:57
*** mmf_ has joined #openstack-neutron19:57
*** banix has joined #openstack-neutron19:58
*** tonytan4ever has quit IRC19:58
*** neelashah1 has joined #openstack-neutron19:59
*** asingh has quit IRC20:00
openstackgerritRichard Theis proposed openstack/python-neutronclient: Devref: Newton updates for transition to OSC  https://review.openstack.org/29939920:00
*** asingh has joined #openstack-neutron20:00
*** neelashah has quit IRC20:02
*** eilert has quit IRC20:03
busterswtkevinbenton ping20:08
*** anilvenkata has quit IRC20:10
*** abhiraut has joined #openstack-neutron20:12
kevinbentonbusterswt: pong20:14
busterswtkevinbenton have a sec to look at iptables_manager and _apply_synchronized? Came up on some regressions from kilo -> liberty that seems to be related to the iptables diff20:15
*** EkulTails has joined #openstack-neutron20:15
*** Marga_ has joined #openstack-neutron20:15
kevinbentonbusterswt: yes20:16
*** Marga_ has quit IRC20:16
busterswtkevinbenton we have a large environment with a neutron router and ~1,000 floating IPs, and it takes ~120 secs to get through apply_synchronized. Take a look at this gist if you can:20:18
busterswtkevinbenton https://gist.github.com/busterswt/479e4e5484df7e91017da48b38fa581420:18
*** shashank_hegde has quit IRC20:18
*** shashank_hegde has joined #openstack-neutron20:18
busterswtkevinbenton takes a bit to loop through all of those, and there's no difference other than the mask and the --to switch20:19
kevinbentonbusterswt: ack. are you able to apply a patch to test a change?20:21
busterswtsure.20:21
*** baoli_ has quit IRC20:23
kevinbentonbusterswt: ok. how much longer will you be online today?20:23
*** eddima has joined #openstack-neutron20:23
*** ZZelle_ has joined #openstack-neutron20:24
busterswtkevinbenton i will be on for another 1.5 hrs or so. But it can wait until tomorrow or later if that works for you. Non-prod environment.20:24
kevinbentonbusterswt: ack20:24
*** eddima has quit IRC20:24
*** akshai has quit IRC20:25
*** panda has quit IRC20:26
*** edmondsw has quit IRC20:26
*** panda has joined #openstack-neutron20:27
*** neelashah1 has quit IRC20:30
*** Sukhdev has joined #openstack-neutron20:31
openstackgerritKevin Benton proposed openstack/neutron: WIP: match snat/dnat format used by iptables  https://review.openstack.org/30133520:31
kevinbentonbusterswt: ^^20:31
kevinbentonbusterswt: give that a try20:31
busterswtkevinbenton checking20:31
*** nlahouti has joined #openstack-neutron20:31
kevinbentonbusterswt: i also need to push another patch to weed out these other l3 agent rules. i don't think we have good coverage of their interaction with the iptables manager20:32
*** Sukhdev has quit IRC20:32
*** elo has quit IRC20:32
*** elo has joined #openstack-neutron20:33
*** eilert has joined #openstack-neutron20:34
openstackgerritKevin Benton proposed openstack/neutron: [DO NOT MERGE]: iptables diff canary  https://review.openstack.org/30133820:34
*** p01nt3r75 has joined #openstack-neutron20:34
*** njohnsto_ has joined #openstack-neutron20:35
*** tbachman has quit IRC20:40
*** cleong has quit IRC20:43
busterswtkevinbenton much. better. Total time for _apply_synchronized: Scheduling router: 2.59, Creating/associating floating IP: 0.569520:45
haleybkevinbenton: oh, more iptables-save/restore mismatches :(20:45
*** crose has joined #openstack-neutron20:45
*** pjm6 has joined #openstack-neutron20:47
pjm6Hi there20:47
*** sthillma has joined #openstack-neutron20:47
pjm6i'm having some troubles with neutron with an existing network20:47
pjm6my VM makes a dhcp request, I receive in the router of that network, and in the compute node I receive the reply, but for some reason the reply never gets to the VM20:48
pjm6anyone have a tip on what debug I could do more?20:48
*** sthillma has quit IRC20:48
openstackgerritDarek Smigiel proposed openstack/python-neutronclient: Add project-id to neutronclient  https://review.openstack.org/29842520:49
kevinbentonbusterswt: excellent20:50
kevinbentonhaleyb: yeah, all of my tests on the convergence were for security groups20:50
kevinbentonhaleyb: nothing to cover the l3 rules20:50
haleybpjm6: that usually means a security group rule is dropping it, if you run tcpdump on the bridge and see it, but not on the tap, then that's it20:50
*** hoangcx has joined #openstack-neutron20:51
pjm6I see in the TCPDUMP the reply20:51
*** njohnsto_ has quit IRC20:51
pjm6sorry caps20:51
pjm6can I paste here haleyb ?20:51
kevinbentonpjm6: paste on paste.openstack.org and then link here20:51
*** sc68cal has joined #openstack-neutron20:51
*** nyechiel_ has joined #openstack-neutron20:52
busterswtkevinbenton thanks for the quick turnaround.20:52
pjm6thanks kevinbenton20:52
pjm6http://paste.openstack.org/show/fHPSlEIxZESNvIuSPYvQ/20:52
kevinbentonbusterswt: yeah, i'll need to get some tests added to that patch and then we can get it merged and back-ported20:53
*** rickyrem1 has quit IRC20:53
kevinbentonbusterswt: so it will take a while before it lands in a stable branch20:53
pjm6so haleyb, this could be the problem of the tap?20:53
*** hichihara has joined #openstack-neutron20:53
busterswtkevinbenton sure thing. we're not in much of a rush right now, but look forward to the backport20:53
*** sc68cal has quit IRC20:53
*** crose has quit IRC20:54
busterswtkevinbenton do i need to file a bug? or are we good?20:54
kevinbentonbusterswt: don't worry about it. i got it covered20:55
busterswtkevinbenton sweet! thanks :)20:55
pjm6well the reply I don't see in the tap in the fact20:55
pjm6only the request20:55
openstackgerritCarl Baldwin proposed openstack/neutron: Revert "DVR: Fix issue of SNAT rule for DVR with floating ip"  https://review.openstack.org/30134820:56
*** jlibosva has quit IRC20:56
*** sc68cal has joined #openstack-neutron20:57
*** ihrachys has joined #openstack-neutron20:57
*** mvk_ has joined #openstack-neutron20:57
*** iyamahat has quit IRC20:57
*** iyamahat has joined #openstack-neutron20:58
*** akshai has joined #openstack-neutron20:58
pjm6haleyb, i think it works :D20:58
*** gvrangan has quit IRC20:59
*** Sukhdev has joined #openstack-neutron21:02
*** gvrangan has joined #openstack-neutron21:02
*** rossella_s has quit IRC21:02
*** tmorin has joined #openstack-neutron21:03
*** rossella_s has joined #openstack-neutron21:03
*** thorst has quit IRC21:04
*** thorst has joined #openstack-neutron21:05
*** ociuhandu has joined #openstack-neutron21:06
*** thorst_ has joined #openstack-neutron21:07
haleybpjm6: ok, so it was a security group rule?21:08
pjm6Yes, I didn't have any UDP working21:08
*** mgoddard has joined #openstack-neutron21:08
pjm6I just let 67 and 68 and starts working...21:08
haleybpjm6: normally those are allowed by default, so don't know why they went away21:09
pjm6now I will try to see how the IP address could be shown correctly on horizon21:09
*** xenogear has joined #openstack-neutron21:09
pjm6hmm, maybe I did something wrong21:09
*** thorst has quit IRC21:10
pjm6even with an external dhcp, the IP address should be shown correctly in horizon , right?21:10
*** thorst_ has quit IRC21:11
haleybpjm6: yes, it should21:13
pjm6well it seems that after I make a reboot the VM was stopped in the cloud init info21:13
*** vhoward has quit IRC21:16
*** banix has quit IRC21:16
*** mmf_ has quit IRC21:17
*** john-davidge has quit IRC21:17
*** hoangcx has quit IRC21:17
*** john-davidge has joined #openstack-neutron21:18
*** neiljerram has quit IRC21:18
*** njohnsto_ has joined #openstack-neutron21:20
*** rickyrem has joined #openstack-neutron21:23
*** claudiub|2 has joined #openstack-neutron21:26
*** hoangcx has joined #openstack-neutron21:28
*** thorst has joined #openstack-neutron21:29
*** claudiub has quit IRC21:29
*** ivase_ has quit IRC21:32
*** thorst has quit IRC21:33
*** alex_xu has quit IRC21:39
*** yalie has quit IRC21:40
*** tiswanso has quit IRC21:41
*** regXboi has quit IRC21:44
*** yalie has joined #openstack-neutron21:45
*** imcsk8|lunch is now known as imcsk821:45
*** xenogear has quit IRC21:45
*** mgoddard has quit IRC21:46
*** alex_xu has joined #openstack-neutron21:47
*** xenogear has joined #openstack-neutron21:47
*** haplo37 has quit IRC21:51
pjm6well I have to go, see if I figure this out21:53
pjm6thank you for the help haleyb :)21:54
haleybnp21:54
kfox1111anyone know why neutron woudl spawn off a bagillion openssl cms processes?21:55
*** tmorin has quit IRC21:55
*** nyechiel_ has quit IRC21:57
sc68calSam-I-Am: so.... we have a lot of config options for OVS and OVSDB21:57
*** slaweq_ has joined #openstack-neutron21:58
openstackgerritMerged openstack/python-neutronclient: Log SHA1 hash of X-Auth-Token value  https://review.openstack.org/29863721:58
*** SauloAislan has quit IRC21:59
*** tmorin has joined #openstack-neutron21:59
mlavallearmax, kevinbenton: so you need hands for https://review.openstack.org/#/c/105078/?22:00
*** rtheis has quit IRC22:01
*** hoangcx has quit IRC22:01
kevinbentonmlavalle: probably. can you ping me later this week? i'll try to get the spec revised22:01
Sam-I-Amsc68cal: moo?22:01
*** david-lyle_ has joined #openstack-neutron22:02
*** david-lyle has quit IRC22:03
*** sdague has quit IRC22:03
mlavallekevinbenton, armax : there is an IBM dev based out of China. I don't know his level of expertise. I have a conversation with him on Thursday. He might be a newby. Would that be useful?22:03
*** david-lyle_ is now known as david-lyle22:03
kevinbentonmlavalle: might not be too good. the hard part with the flavors is a lot of refactoring of the current tightly coupled l3 stuff22:04
mlavallekevinbenton, armax: we want to help him get up to speed contributing upstream22:04
*** singhj has quit IRC22:04
armaxmlavalle: hard to tell right now, but once we get something off the ground he can definitely help in some area22:04
kevinbentonmlavalle: but i think we may have some stuff that he could work on WRT to writing API tests22:04
ZZelle_mlavalle, hi22:05
mlavallekevinbenton, armax: ok, I'll ping you guys again on Friday after my conversation with him and will share my findings22:05
armaxok22:05
mlavalleZZelle_: hi22:05
armaxthanks mlavalle22:05
*** pjm6 has quit IRC22:06
*** ujjain has quit IRC22:06
mlavallearmax: the key point with him is that we want to focus him 100% upstream Neutron. So please keep that in mind. He might be useful for other things22:06
kevinbentonack22:06
ZZelle_mlavalle, i am not exactly sure to understand what i mean in http://lists.openstack.org/pipermail/openstack-dev/2016-March/090920.html22:06
ZZelle_what you mean :)22:07
*** njohnsto_ has quit IRC22:07
*** abhiraut has quit IRC22:08
mlavalleZZelle_: first of all, thanks for the follow up ;-) I am working on this patchset for routed networks https://review.openstack.org/#/c/285548/22:09
*** ujjain has joined #openstack-neutron22:10
*** ujjain has quit IRC22:10
*** ujjain has joined #openstack-neutron22:10
*** busterswt has quit IRC22:10
mlavalleZZelle_: The idea is to be able to map segments and hosts and reflect that in the DB. I was pointed to your patchset by carl_baldwin: https://review.openstack.org/#/c/205631/3322:10
Sam-I-Amsc68cal: you back stateside?22:11
*** slaweq__ has joined #openstack-neutron22:11
*** slaweq_ has quit IRC22:11
sc68calSam-I-Am: yep. on Amtrak right now, pulling into philly. I'll ping you tomorrow22:12
*** sc68cal has quit IRC22:12
Sam-I-Amaight. i might be out most of the morning22:12
Sam-I-Amalso, dont crash22:12
*** janzian has quit IRC22:13
mlavalleZZelle_: after an IRC conversation with rkukura and kevinbenton on Thursday, we agreed that the next revision of my patchset will use filter_hosts_with_segment_access here: https://review.openstack.org/#/c/205631/33/neutron/plugins/ml2/managers.py22:13
mlavalleZZelle_: the thinking is to call the mechanism drivers to decide host acces to a segment. Makes sense?22:14
ZZelle_mlavalle, yes and no, because the main limitation of filter_hosts_with_segment_access is how it scales22:14
*** eric_lopez has joined #openstack-neutron22:15
mlavalleSam-I-Am: LOL22:15
*** elo has quit IRC22:16
*** EkulTails has quit IRC22:16
*** tbachman has joined #openstack-neutron22:17
ZZelle_mlavalle, the main trouble with this method is that we iterate over all segments and all agents on host for every candidate host22:19
mlavalleZZelle_: the way I intend to use it is to limit the search to one host and segments that might be accesible by it22:20
ZZelle_mlavalle, so it's fine22:20
mlavalleZZelle_: as soon as I push the next revision, I'll add it to the reviewers22:21
ZZelle_mlavalle, because iirc carl_baldwin wanted to use it on every compute host iirc22:21
ZZelle_mlavalle, thx22:21
mlavalleZZelle_: I'll add you to the reviewers22:21
mlavalleZZelle_: thanks again for your interest. Highly appreciated :-)22:22
*** abhiraut has joined #openstack-neutron22:24
*** tpsilva has quit IRC22:27
*** knikolla has quit IRC22:30
ZZelle_carl_baldwin, hi22:30
*** andymaier has joined #openstack-neutron22:30
carl_baldwinZZelle_: Hi22:32
*** singhj has joined #openstack-neutron22:32
*** andymaier has quit IRC22:32
ZZelle_carl_baldwin, about https://review.openstack.org/205631 and https://review.openstack.org/28554822:33
*** tidwellr has quit IRC22:34
ZZelle_carl_baldwin, is there still an intention to speed up host filter based on network access when len(hosts) becomes large?22:34
ZZelle_typically applied on all compute hosts?22:35
carl_baldwinZZelle_: If I recall, the thing that concerned me was looking through all of the JSON blobs from all of the agents rows, right?22:36
ZZelle_carl_baldwin, yep22:36
*** singhj has quit IRC22:36
ihrachyssalv-orlando: kevinbenton: silly question on API sorting/pagination: why is it controlled by config option?22:37
*** markvoelker has quit IRC22:37
carl_baldwinYes.  The table that mlavalle is adding to store the mapping should help with that.22:37
carl_baldwinZZelle_: ^22:37
ZZelle_carl_baldwin, one approach is to persist which host is able to connect to which segment (or perhaps which network) => the filtering computation is done once and persisted in db22:40
carl_baldwinZZelle_: That's essentially what mlavalle is doing.22:40
carl_baldwinZZelle_: https://review.openstack.org/#/c/285548/2/neutron/db/migration/alembic_migrations/versions/newton/expand/8fd3918ef6f4_add_segment_host_mapping.py22:41
* mlavalle following with interest conversation between carl_baldwin and ZZelle_22:41
ZZelle_carl_baldwin, an other approach is to persist json blob as text columns => the filtering becomes a db query but we must know every attribute used in the filtering ==> so in general not working for out-of-tree mechanisms22:42
*** tbachman has quit IRC22:43
carl_baldwinZZelle_: Do you see any advantage to that latter approach?22:43
ZZelle_carl_baldwin, db consistency22:44
*** david-lyle has quit IRC22:44
carl_baldwinZZelle_: Could you elaborate?22:45
ZZelle_carl_baldwin, any update to agent's configuration introduces inconsistencies between segment-host-map and agent-configuration22:45
ZZelle_carl_baldwin, as agent config impacts segment-host-map22:45
carl_baldwinZZelle_: Wouldn't they both be updated at the same time?22:46
ZZelle_carl_baldwin, any update would be quite costly22:47
*** david-lyle has joined #openstack-neutron22:47
carl_baldwinZZelle_: How so?22:49
*** tmorin has quit IRC22:50
ZZelle_carl_baldwin, if you add/remove a physnet, it implies in the worse 4096 db inserts or deletes22:50
ZZelle_carl_baldwin, if you add/remove a physnet, it implies in the worse case 4096 db inserts or deletes22:51
*** slaweq__ has quit IRC22:51
carl_baldwinZZelle_: I'm not picturing this scenario.22:53
ZZelle_carl_baldwin, sorry i am wrong, you should recompute everything for the associated host22:53
*** Marga_ has joined #openstack-neutron22:54
ZZelle_carl_baldwin, any change in compute host agent configurations impacts segment-map-hosts?22:55
carl_baldwinZZelle_: Yes, that should be right.  mlavalle could you confirm? ^22:55
ZZelle_typically bridge_mapping for OVS22:55
*** Marga_ has quit IRC22:56
*** Marga_ has joined #openstack-neutron22:56
mlavallecarl_baldwin, ZZelle_: that is correct22:56
*** Marga_ has quit IRC22:56
*** Marga_ has joined #openstack-neutron22:57
mlavallecarl_baldwin, ZZelle_: I have to leave now. will catch up with you tomorrow morning22:58
ZZelle_carl_baldwin, mlavalle, so adding a new physnet on an agent implies to recheck every segment that are not currently supported by the host (if you use check_segment_for_agent)22:58
*** vhosakot has quit IRC22:58
*** vhosakot has joined #openstack-neutron22:59
ZZelle_it's the same if you removes a physnet: you have to check every segment currently supported by the host (as a segment can be supported by multiple agents)22:59
*** mlavalle has left #openstack-neutron23:00
*** mlavalle has quit IRC23:00
*** rickyrem has quit IRC23:06
*** alex_xu has quit IRC23:09
*** alex_xu has joined #openstack-neutron23:11
*** ihrachys has quit IRC23:11
*** akshai has quit IRC23:17
*** chlong has joined #openstack-neutron23:18
*** salv-orlando has quit IRC23:21
*** jckasper has joined #openstack-neutron23:25
*** barajasfab has joined #openstack-neutron23:26
openstackgerritKevin Benton proposed openstack/neutron: L3 agent: match format used by iptables  https://review.openstack.org/30133523:27
kevinbentonhaleyb: check that out when you get a sec ^^23:27
kevinbentonhaleyb: found a nice easy spot to put a test in the functional stuff to prevent regressions23:27
kevinbentoncarl_baldwin: you should probably take a quick look at that as well to make sure i didn't break anything obvious23:28
*** gsagie has quit IRC23:28
*** banix has joined #openstack-neutron23:28
*** saggi has quit IRC23:29
*** vhosakot has quit IRC23:31
*** abregman has quit IRC23:31
openstackgerritKevin Benton proposed openstack/neutron: [DO NOT MERGE]: iptables diff canary  https://review.openstack.org/30133823:37
*** markvoelker has joined #openstack-neutron23:37
*** djan has joined #openstack-neutron23:38
*** gsagie has joined #openstack-neutron23:39
*** saggi has joined #openstack-neutron23:41
*** vhosakot has joined #openstack-neutron23:42
*** busterswt has joined #openstack-neutron23:44
*** bustersw_ has joined #openstack-neutron23:45
*** jckasper has quit IRC23:46
*** rook-lappy has joined #openstack-neutron23:47
*** jckasper has joined #openstack-neutron23:47
*** busterswt has quit IRC23:48
*** jckasper has quit IRC23:51
*** akshai has joined #openstack-neutron23:52
*** bdemers has quit IRC23:54
*** bdemers has joined #openstack-neutron23:56
*** thorst has joined #openstack-neutron23:56
*** akshai_ has joined #openstack-neutron23:58
carl_baldwinkevinbenton: ack23:58

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