Monday, 2014-01-27

*** iwamoto has joined #openstack-neutron00:00
*** clev has quit IRC00:00
*** clev has joined #openstack-neutron00:05
*** suresh12 has quit IRC00:08
*** matsuhashi has joined #openstack-neutron00:09
*** clev has quit IRC00:16
*** sweston has quit IRC00:23
*** matsuhashi has quit IRC00:33
*** suresh12 has joined #openstack-neutron00:39
*** matsuhashi has joined #openstack-neutron00:48
*** suresh12 has quit IRC00:48
*** clev has joined #openstack-neutron00:49
*** WackoRobie has quit IRC00:55
openstackgerritArata Notsu proposed a change to openstack/neutron: Fix ValueError in ip_lib.IpRouteCommand.get_gateway()  https://review.openstack.org/6591701:02
*** nati_ueno has joined #openstack-neutron01:06
*** clev has quit IRC01:09
openstackgerritHemanth Ravi proposed a change to openstack/neutron: One Convergence Neutron Plugin Implementation.  https://review.openstack.org/6924601:09
*** dave_tucker is now known as dave_tucker_zzz01:19
*** nati_ueno has quit IRC01:23
*** markwash has joined #openstack-neutron01:24
*** suresh12 has joined #openstack-neutron01:29
*** markwash has quit IRC01:31
*** suresh12 has quit IRC01:33
*** markwash has joined #openstack-neutron01:34
*** WackoRobie has joined #openstack-neutron01:37
*** Jianyong has joined #openstack-neutron01:37
*** WackoRobie has quit IRC01:41
*** dave_tucker_zzz is now known as dave_tucker01:56
*** dave_tucker is now known as dave_tucker_zzz02:07
*** WackoRobie has joined #openstack-neutron02:07
*** aymenfrikha has quit IRC02:10
*** WackoRobie has quit IRC02:12
*** xuhanp has joined #openstack-neutron02:15
*** xianghui has joined #openstack-neutron02:17
*** dave_tucker_zzz is now known as dave_tucker02:23
*** matsuhashi has quit IRC02:26
*** AlexF_ has joined #openstack-neutron02:26
*** markmcclain has joined #openstack-neutron02:31
*** matsuhashi has joined #openstack-neutron02:32
*** AlexF_ has quit IRC02:35
*** WackoRobie has joined #openstack-neutron02:39
*** WackoRobie has quit IRC02:44
*** dims has quit IRC02:50
*** emagana has joined #openstack-neutron02:59
*** thuc has joined #openstack-neutron02:59
*** zhhuabj has quit IRC03:04
*** xianghui has quit IRC03:08
*** thuc_ has joined #openstack-neutron03:11
*** thuc has quit IRC03:14
*** WackoRobie has joined #openstack-neutron03:16
*** matsuhashi has quit IRC03:18
*** xianghui has joined #openstack-neutron03:25
*** AlexF_ has joined #openstack-neutron03:30
*** AlexF_ has quit IRC03:31
openstackgerritZhiQiang Fan proposed a change to openstack/python-neutronclient: Remove cliff-tablib from test-requirements  https://review.openstack.org/4988603:58
*** markmcclain has quit IRC04:05
*** alex_klimov has joined #openstack-neutron04:06
*** WackoRobie has quit IRC04:09
*** alex_klimov has quit IRC04:09
*** dave_tucker is now known as dave_tucker_zzz04:09
*** chandankumar_ has joined #openstack-neutron04:10
*** suresh12 has joined #openstack-neutron04:16
*** amotoki has quit IRC04:24
*** chandankumar_ has quit IRC04:24
*** amotoki has joined #openstack-neutron04:25
*** ramishra has joined #openstack-neutron04:28
*** chandankumar_ has joined #openstack-neutron04:29
openstackgerritMohammad Banikazemi proposed a change to openstack/neutron: Adds the new IBM SDN-VE plugin  https://review.openstack.org/6645304:36
*** ramishra has quit IRC04:39
*** matsuhashi has joined #openstack-neutron04:40
*** thedodd has joined #openstack-neutron04:49
*** thuc has joined #openstack-neutron04:49
*** thuc_ has quit IRC04:53
*** chandankumar_ has quit IRC04:53
*** thuc has quit IRC04:53
*** thedodd has quit IRC04:54
*** aymenfrikha has joined #openstack-neutron05:00
*** ramishra has joined #openstack-neutron05:05
*** chandankumar_ has joined #openstack-neutron05:23
*** markwash has quit IRC05:26
*** markwash has joined #openstack-neutron05:30
*** ramishra has quit IRC05:51
*** chandankumar_ has quit IRC05:52
*** ramishra has joined #openstack-neutron05:57
*** ykaneko has joined #openstack-neutron06:00
*** suresh12 has quit IRC06:07
*** xianghui has quit IRC06:11
*** aymenfrikha has quit IRC06:17
*** networkstatic is now known as network_gone2Mcd06:20
openstackgerritJenkins proposed a change to openstack/neutron: Imported Translations from Transifex  https://review.openstack.org/6650106:20
*** markwash has quit IRC06:23
*** Jianyong has quit IRC06:24
*** xianghui has joined #openstack-neutron06:25
*** xianghui has quit IRC06:32
*** chandankumar_ has joined #openstack-neutron06:38
*** irenab has joined #openstack-neutron06:38
*** alex_klimov has joined #openstack-neutron06:41
*** chandankumar_ has quit IRC06:46
*** alex_klimov has left #openstack-neutron06:55
*** xianghui has joined #openstack-neutron06:56
*** ramishra has quit IRC07:00
openstackgerritKevin Benton proposed a change to openstack/neutron: Base ML2 bulk support on the loaded drivers  https://review.openstack.org/6899607:03
*** nati_ueno has joined #openstack-neutron07:06
*** network_gone2Mcd is now known as networkstatic07:08
*** nati_ueno has quit IRC07:13
openstackgerritKevin Benton proposed a change to openstack/neutron: Enables BigSwitch/Restproxy ML2 VLAN driver  https://review.openstack.org/6494407:16
openstackgerritXiaolin Zhang proposed a change to openstack/neutron: Adds https support for metadata agent  https://review.openstack.org/6718107:23
*** yamahata has joined #openstack-neutron07:24
*** itzikb has joined #openstack-neutron07:25
*** Jianyong has joined #openstack-neutron07:26
*** afazekas has joined #openstack-neutron07:32
*** AlexF_ has joined #openstack-neutron07:36
ajoI'd like to improve the netns_cleanup_util https://bugs.launchpad.net/neutron/+bug/127309507:51
ajohttps://github.com/openstack/neutron/blob/master/neutron/agent/netns_cleanup_util.py07:51
*** BBG_Stephen has joined #openstack-neutron07:51
ajocould anybody confirm this "bug"  , I mean, I confirm it's like that, can actually be seen in the code: https://github.com/openstack/neutron/blob/master/neutron/agent/netns_cleanup_util.py07:51
*** iwamoto has quit IRC08:00
*** rohit404 has joined #openstack-neutron08:05
openstackgerritYohei Matsuhashi proposed a change to openstack/python-neutronclient: Enable to select specific network service type  https://review.openstack.org/5453408:11
*** safchain has joined #openstack-neutron08:14
*** luqas has joined #openstack-neutron08:17
*** jlibosva has joined #openstack-neutron08:18
*** amuller has joined #openstack-neutron08:19
*** Mierdin has quit IRC08:25
openstackgerritÉdouard Thuleau proposed a change to openstack/neutron: Implement local ARP responder onto OVS agent  https://review.openstack.org/4922708:27
*** anand has joined #openstack-neutron08:28
*** lari_ has quit IRC08:28
*** lari_ has joined #openstack-neutron08:29
*** AlexF_ has quit IRC08:30
*** matsuhashi has quit IRC08:36
*** matsuhashi has joined #openstack-neutron08:37
openstackgerritÉdouard Thuleau proposed a change to openstack/neutron: OVS lib defer apply doesn't handle concurrency  https://review.openstack.org/6391708:43
*** roeyc has joined #openstack-neutron08:47
*** lari_ has quit IRC08:48
QlawyHi, I have binding_failed for dhcp assigned port on neutron08:48
*** jistr has joined #openstack-neutron08:48
Qlawydebug logging show nothing :/08:49
Qlawy NT-EB3E7F5 Device 9c49c453-246a-4ec3-b183-63ba90885050 requested by agent ovsb64db7a65b46 on network 17dd358c-6372-4f88-8061-bab9906e88e7 not bound, vif_type: binding_failed08:49
*** ygbo has joined #openstack-neutron08:53
*** lari_ has joined #openstack-neutron08:55
*** jpich has joined #openstack-neutron08:59
*** jlibosva has quit IRC08:59
*** jlibosva has joined #openstack-neutron09:01
*** xianghui has quit IRC09:03
ykanekoHello, could anyone review this patch? https://review.openstack.org/#/c/67652/09:08
*** dave_tucker_zzz is now known as dave_tucker09:09
openstackgerritSascha Peilicke proposed a change to openstack/neutron: Don't document non-existing flag '--hide-elapsed'  https://review.openstack.org/6747709:12
openstackgerritSascha Peilicke proposed a change to openstack/neutron: Support passing 'neutron_insecure' to neutronclient  https://review.openstack.org/6569609:13
*** ihrachys has quit IRC09:13
*** matrohon has joined #openstack-neutron09:15
*** xianghui has joined #openstack-neutron09:17
*** rossella_s has joined #openstack-neutron09:19
*** sweston has joined #openstack-neutron09:26
*** sweston has quit IRC09:26
*** sweston has joined #openstack-neutron09:29
*** sweston has quit IRC09:30
*** jlibosva has quit IRC09:31
*** sweston has joined #openstack-neutron09:31
*** sweston has quit IRC09:32
*** sweston has joined #openstack-neutron09:33
*** sweston has quit IRC09:33
*** sweston has joined #openstack-neutron09:34
*** rkukura has quit IRC09:34
*** sweston has quit IRC09:36
*** sweston has joined #openstack-neutron09:37
*** rkukura has joined #openstack-neutron09:40
*** bashok has joined #openstack-neutron09:42
*** jlibosva has joined #openstack-neutron09:46
*** dave_tucker is now known as dave_tucker_zzz09:51
*** sweston has quit IRC09:51
*** afazekas has quit IRC09:52
*** luqas has quit IRC09:52
*** dave_tucker_zzz is now known as dave_tucker09:54
*** jp_at_hp has joined #openstack-neutron09:56
*** sweston has joined #openstack-neutron09:57
*** ihrachys has joined #openstack-neutron09:59
*** rohit404 has quit IRC10:10
ajoamotoki, ping10:11
ajohttps://review.openstack.org/21489   ,   https://bugs.launchpad.net/neutron/+bug/111599910:11
amotokiajo: pong10:11
ajoI was looking into this, do you remind more or less the state of the review?, there was some stopper? could I go on with it?10:12
*** zzelle has joined #openstack-neutron10:13
*** chandankumar_ has joined #openstack-neutron10:13
ajobtw, I understand the changes in : https://review.openstack.org/#/c/21489/14/quantum/agent/netns_cleanup_util.py10:14
*** afazekas has joined #openstack-neutron10:15
ajobut not the other changes like this: https://review.openstack.org/#/c/21489/14/quantum/agent/linux/external_process.py   (may be they come from a rebase, or they got mixed, or I'm missing something important)10:15
ajoamotoki, ^  (sorry, I forgot to prefix you on the lines above)10:16
amotokiajo: i think the progress of the patch is stopped now. isaku10:17
ajoDo you mind if I restart it myself? ,10:17
amotokiis still working on neutron. it is better to ask him10:17
ajooh, sorry10:17
amotokii am not the author of the patch. isaku10:18
ajosomehow I confused, and I thought it was you the commiter10:18
amotokiisaku is the author. He changed companies last year.10:18
ajoAh, ok I saw you on the bug10:18
ajoand somehow I assumed you where the author10:18
amotoki :-)10:19
ajook, I will start this patch again10:19
ajoI think I will reuse his work, but take a simpler approach as an start10:19
amotokiyamahata: around? ajo and i are talking about your abandoned patch.10:19
ajoyamahata_ ^10:20
ajooh, it's yamahata , thanks amotoki10:20
amotokiI am not sure what timezone he is now. sometimes japan, sometime us.10:21
ajobad time for US, and a little bit late for Japan ':D10:21
*** luqas has joined #openstack-neutron10:34
*** chandankumar_ has quit IRC10:37
*** djoreilly has joined #openstack-neutron10:42
*** djoreilly_ has joined #openstack-neutron10:43
*** mflobo has joined #openstack-neutron10:51
*** mflobo has quit IRC10:52
*** mflobo has joined #openstack-neutron10:52
*** alexpilotti has joined #openstack-neutron10:58
*** chandankumar_ has joined #openstack-neutron11:02
*** alexpilotti has quit IRC11:03
*** chandankumar_ has quit IRC11:08
*** roeyc has quit IRC11:11
*** chandankumar_ has joined #openstack-neutron11:15
*** alexpilotti has joined #openstack-neutron11:25
*** sweston has quit IRC11:25
*** xianghui has quit IRC11:29
openstackgerritXiaolin Zhang proposed a change to openstack/neutron: Adds https support for metadata agent  https://review.openstack.org/6718111:29
*** pcm_ has joined #openstack-neutron11:34
*** pcm_ has quit IRC11:35
*** pcm_ has joined #openstack-neutron11:35
*** chandankumar_ has quit IRC11:39
*** matsuhashi has quit IRC11:40
*** emagana has quit IRC11:41
*** matsuhashi has joined #openstack-neutron11:45
*** djoreilly has left #openstack-neutron11:47
*** djoreilly_ has quit IRC11:48
*** itzikb has quit IRC11:50
yamahataamotoki, ajo hello?12:03
ajohi yamahata , I dropped you an email :)12:03
ajoI'm entering a meeting right now12:03
ajoIt's just to check the status of the patch above, and ask you if I could go on with the patch12:04
*** chandankumar_ has joined #openstack-neutron12:05
yamahataajo, feel free to do so.12:06
yamahataajo, I'm willing to revive myself if you hasn't started it.12:07
*** chandankumar_ has quit IRC12:08
*** amarao has joined #openstack-neutron12:10
*** matsuhashi has quit IRC12:12
*** WackoRobie has joined #openstack-neutron12:12
*** amotoki has quit IRC12:12
*** matsuhashi has joined #openstack-neutron12:13
amaraoAs far as I can see, neutron has no idea about availability zones? Is any way to partition neworking nodes except by the different networks?12:13
*** ykaneko has quit IRC12:21
*** markwash has joined #openstack-neutron12:21
*** dims has joined #openstack-neutron12:23
*** WackoRobie has quit IRC12:26
*** luqas has quit IRC12:40
ajoyamahata, I didn't start12:40
ajoI was looking into the same problem and I just found your commit, so if you can revive it and rebased, it would be awesome :)12:41
ajoyou probably understand the problem much better than me at this moment.12:41
*** emagana has joined #openstack-neutron12:41
*** ewindisch has quit IRC12:46
*** salv-orlando has joined #openstack-neutron12:48
*** emagana has quit IRC12:50
*** heyongli has joined #openstack-neutron12:52
*** chandankumar_ has joined #openstack-neutron12:54
*** xianghui has joined #openstack-neutron12:57
*** ijw has joined #openstack-neutron12:59
*** ijw has quit IRC13:00
*** ijw has joined #openstack-neutron13:00
openstackgerritSalvatore Orlando proposed a change to openstack/neutron: Test do not review  https://review.openstack.org/6936513:12
*** ewindisch has joined #openstack-neutron13:14
*** rossella_s has quit IRC13:16
*** vkozhukalov has joined #openstack-neutron13:20
*** ijw_ has joined #openstack-neutron13:21
*** chandankumar_ has quit IRC13:22
*** chandankumar_ has joined #openstack-neutron13:23
*** markwash has quit IRC13:24
*** ijw has quit IRC13:24
*** ijw_ is now known as ijw13:25
ajoyamahata, can you revive https://review.openstack.org/21489 then? :-)13:29
*** rossella_s has joined #openstack-neutron13:29
*** WackoRobie has joined #openstack-neutron13:30
*** ijw_ has joined #openstack-neutron13:32
*** MichielHN has quit IRC13:33
*** ijw has quit IRC13:33
*** jecarey has quit IRC13:34
*** ijw_ is now known as ijw13:35
*** luqas has joined #openstack-neutron13:37
*** b3nt_pin is now known as beagles13:40
yamahataajo, sure will do tomorrow.13:43
*** chandankumar_ has quit IRC13:44
*** Jianyong has quit IRC13:45
*** markwash has joined #openstack-neutron13:48
ajogreat, thank you very much, just let me know if you need a hand or anythin13:50
*** mattymo has joined #openstack-neutron13:57
mattymoDoes anyone have a recommendation for neutron quotas?13:57
*** thuc has joined #openstack-neutron13:57
*** amuller_ has joined #openstack-neutron13:59
*** amuller has quit IRC14:00
*** heyongli has quit IRC14:01
*** ijw has quit IRC14:03
*** ijw_ has joined #openstack-neutron14:03
*** rohit404 has joined #openstack-neutron14:04
*** morganfainberg|z is now known as morganfainberg14:06
*** alagalah has quit IRC14:09
*** thuc_ has joined #openstack-neutron14:09
*** rustlebee is now known as russellb14:12
*** thuc has quit IRC14:12
*** dims has quit IRC14:13
*** ijw_ has quit IRC14:14
*** aymenfrikha has joined #openstack-neutron14:15
*** dims has joined #openstack-neutron14:15
*** ijw has joined #openstack-neutron14:16
*** ijw has quit IRC14:17
*** ijw has joined #openstack-neutron14:17
*** chandankumar_ has joined #openstack-neutron14:23
*** jecarey has joined #openstack-neutron14:24
*** djoreilly has joined #openstack-neutron14:24
*** jgrimm has quit IRC14:26
*** chandankumar_ has quit IRC14:27
*** rohit404 has quit IRC14:27
*** irenab has quit IRC14:28
*** chandankumar_ has joined #openstack-neutron14:29
openstackgerritAndres Buraschi proposed a change to openstack/python-neutronclient: Adding weight column to Neutron lb member list CLI  https://review.openstack.org/6576614:29
*** thuc_ has quit IRC14:29
*** thuc has joined #openstack-neutron14:30
*** julim has joined #openstack-neutron14:31
*** rohit404 has joined #openstack-neutron14:31
*** julim has quit IRC14:32
*** chandankumar_ has quit IRC14:33
*** chandankumar_ has joined #openstack-neutron14:34
*** thuc has quit IRC14:35
*** julim has joined #openstack-neutron14:35
*** anand has quit IRC14:37
*** chandankumar_ has quit IRC14:44
*** peristeri has joined #openstack-neutron14:47
*** thuc has joined #openstack-neutron14:52
*** chandankumar_ has joined #openstack-neutron14:56
*** networkstatic has quit IRC15:02
*** amuller_ has quit IRC15:03
*** clev has joined #openstack-neutron15:03
*** otherwiseguy has joined #openstack-neutron15:03
*** chandankumar_ has quit IRC15:06
*** networkstatic has joined #openstack-neutron15:07
*** rwsu has joined #openstack-neutron15:16
*** sgran has quit IRC15:20
*** amuller_ has joined #openstack-neutron15:20
*** thuc has quit IRC15:23
*** thuc has joined #openstack-neutron15:23
*** amuller__ has joined #openstack-neutron15:24
*** xianghui has quit IRC15:25
*** amuller_ has quit IRC15:25
*** irenab has joined #openstack-neutron15:26
*** morganfainberg is now known as morganfainberg|z15:27
*** thuc has quit IRC15:28
*** aveiga has joined #openstack-neutron15:31
*** jgrimm has joined #openstack-neutron15:32
*** IanGovett has joined #openstack-neutron15:33
*** bashok has quit IRC15:33
*** markmcclain has joined #openstack-neutron15:34
*** alagalah has joined #openstack-neutron15:37
*** cdub has joined #openstack-neutron15:37
*** markmcclain has quit IRC15:38
openstackgerritYves-Gwenael Bourhis proposed a change to openstack/neutron: Fixing lost vlan ids on interfaces  https://review.openstack.org/6637515:38
cdubmestery: you have an ml2/odl multi-node setup handy?15:40
mesterycdbu: I do, but at the moment, waiting for a fix from Madhu around DHCP not working.15:41
mesteryI can revert to an older OpenFlow 1.0 though, which should work.15:41
mesteryWhat do you need?15:41
cdubmestery: trying to get hsin-yi up and going w/ non-devstack based deployment15:41
* mestery nods.15:42
mesteryI've got a fairly full slate of meetings, but can answer quiestions on IRC and help where needed.15:42
mesteryAre you looking for configuration file examples for multi-node?15:42
cdubmestery: and she keeps hitting various problems (not to the point of actually testing, still in deploy phase)15:42
* mestery nods.15:42
cdubmestery: and i think part of her issue is that she hasn't set up devstack, so doesn't know what config should look like in the end15:42
*** xuhanp has quit IRC15:43
cdubmestery: yeah...i think config files would help15:43
mesterycdub: Yes, that's a problem I think. :)15:43
mesteryCool.15:43
mesteryI'll create a paste with example config files now ...15:43
*** mlavalle has joined #openstack-neutron15:43
cdubmestery: thanks15:43
*** markmcclain has joined #openstack-neutron15:44
cdubmestery: i've been pointing her to snippets based on devstack (code not results of running)15:44
mesterycdub: OK. Do you want more than just ml2_conf.ini for both control and compute nodes?15:44
mesterycdub: ---> http://paste.openstack.org/show/61946/15:45
cdubmestery: yeah, for example she's switched over from ml2/gre,vxlan and has leftover ovs agent (which she found confusing)15:45
*** markwash has quit IRC15:45
mesterycdub: OK, got it.15:46
*** amarao has quit IRC15:46
cdubmestery: and another issue is loading type driver w/out setup.cfg/egg-info alias for 'opendaylight'15:46
cdubi've hacked her around it for now15:46
mesterycdub: That must be a packaging issue, right? Shoot me more info on that one and I'll see what I can do.15:47
cdubheh, all info above ;)15:47
mesteryha!15:48
mestery:)15:48
mesteryOK, check out the paste I sent, lets start there and see how far we can go.15:48
cdubtype driver won't load by classname afaict15:48
cdubonly by alias15:48
*** ewindisch is now known as zz_ewindisch15:48
cdubmestery: *nod* thanks!15:48
mesteryYes, ML2 uses stevedore for that functionality AFAIK.15:48
cdubyeah, i just thought perhaps a direct classname was still possible15:49
* cdub thought wrong15:49
*** MM_at_HP has joined #openstack-neutron15:50
MM_at_HPMorning15:50
*** vkozhukalov has quit IRC15:50
anteayamorning MM_at_HP15:51
roaetG'day all.15:51
anteayahello roaet15:51
mesterycdub: Why do you need or want to use the direct class name?15:51
* roaet waves to anteaya15:51
anteayaroaet: going to join us for gate-blocking-bug day?15:51
anteayawe could use your help?15:51
anteayawe are in #openstack-gate15:51
roaetI will try. I have one bug here I gotta work today, but in theory it shouldn't be bad. After that I shall!15:52
roaetI will join the channel though15:52
anteayathanks15:52
cdubmestery: because we aren't building w/ ml2, just copying it over15:53
mesterycdub: OK, makes sense now.15:53
cdubmestery: IOW, it's all still initial hack to prop it up and give it a go15:54
anteayaroaet: here are some instructions: http://lists.openstack.org/pipermail/openstack-dev/2014-January/025337.html15:54
* roaet looks15:54
roaetI was looking at a bug the other day and I was really stumped. I didn't know how to continue. So I will hopefully learn from this day.15:54
roaetanteaya: 'fingerprint' means to recheck bug #?15:57
anteayafingerprint means logstash query15:57
anteayathe query that is unique to that failure signature15:57
anteayaand only collects failures, check build_status to ensure you are collecting only failures15:58
anteayathe idea is that it is specific enough to be discoverable and contain useful information for the person(s) who work to find the fix15:58
roaetAh i see.15:58
anteayathanks for asking15:58
anteayagood questions15:58
*** jistr has quit IRC15:58
anteayaalso if a bug stumps you, share the bug url and ask for help15:59
roaetSo is that just a matter of looking at an uncategorized bug, then finding an accurate logstash?15:59
anteayaif I am here I will take a look as well15:59
openstackgerritYves-Gwenael Bourhis proposed a change to openstack/neutron: Fixing lost vlan ids on interfaces  https://review.openstack.org/6637515:59
anteayaroaet: finding an accurate query yes15:59
anteayathen see if the bug has a bug report already, if not, file a bug report16:00
*** zz_ewindisch is now known as ewindisch16:00
roaetgot it.16:00
roaetI can work on that during the busywait16:00
anteayathen add the logstash fingerprint and a url to the query to the bug report16:00
anteayathen submit a patch to the elastic-recheck repo with that bug's number as the title of the file and the contents being the logstash query16:01
anteayathanks16:01
*** markwash has joined #openstack-neutron16:02
anteayaas an example: http://bit.ly/Ml2R4r is not a good fingerprint yet16:02
anteayaif you click on build_status on the left, it captures successes as well as failures16:03
anteayaI need to refine it16:03
*** clev has quit IRC16:03
roaetok.16:03
roaetNow what do you mean push to the elastic recheck repo?16:03
anteayaI don't think I ever use the word push16:04
anteayasubmit is the word I use16:04
anteayahttps://review.openstack.org/#/c/69386/116:04
*** clev has joined #openstack-neutron16:05
anteayasubmit a patch to the elastic-recheck repo like the example above16:05
roaetAhhhh.16:05
roaetAlright that makes a lot more sense16:05
anteayasince in our workflow, we never push and we never merge16:05
*** roeyc has joined #openstack-neutron16:05
anteayagerrit does that16:05
anteayagood16:05
*** HenryG has quit IRC16:06
*** pcm__ has joined #openstack-neutron16:08
*** pcm_ has quit IRC16:11
*** pcm__ has quit IRC16:12
*** pcm_ has joined #openstack-neutron16:13
*** matsuhashi has quit IRC16:15
*** julim has quit IRC16:16
*** irenab has quit IRC16:19
*** julim has joined #openstack-neutron16:19
*** mfink has joined #openstack-neutron16:22
jlibosvamarkmcclain: hi, can I ask something wrt changing down_revisions in db migration?16:22
markmcclainjlibosva: sure… what's your question?16:23
jlibosvamarkmcclain: there is this issue: https://bugs.launchpad.net/neutron/+bug/1271231 , basically creation of securitygroups table didn't get into havana release16:23
*** clev has quit IRC16:23
jlibosvamarkmcclain: that means this table is not created as a part of neutron-db-manage upgrade head during devstack deployment and is attempted to be created later, when doing neutron upgrade via grenade16:24
jlibosvaat this time, table is already created by neutron itself16:24
*** thuc has joined #openstack-neutron16:24
markmcclainyeah.. create_all() is still executes in Havana16:25
jlibosvamarkmcclain: I had an idea of fix, that I'll send patch to stable/havana and master branch, where I'll change the dependency in chain in order to have creation of this table on correct place. I was told you will not like it :)16:25
*** thuc_ has joined #openstack-neutron16:25
jlibosvamarkmcclain: so I'd like to hear (read) your opinion on such fixes16:25
*** irenab has joined #openstack-neutron16:26
*** AlexF_ has joined #openstack-neutron16:27
*** amuller__ has quit IRC16:27
markmcclaindepends on the fix16:27
markmcclainif create_all() is always ensuring this table exists than add the migrations makes sense16:27
jlibosvamarkmcclain: I wanted to change down_revision variable in several versions scripts16:28
jlibosvaspecifically 49f5e553f61f_ml2_security_groups.py to be executed before "havana" stamp16:29
*** thedodd has joined #openstack-neutron16:29
*** thuc has quit IRC16:29
*** ewindisch is now known as zz_ewindisch16:30
*** dguitarbite has joined #openstack-neutron16:32
*** jistr has joined #openstack-neutron16:34
*** morganfainberg|z is now known as morganfainberg16:36
markmcclainI think that we could move this one to before havana16:39
markmcclainjlibosva: and avoid breaking migrations for folks tracking either the master branch or the stable branches16:40
*** aveiga has quit IRC16:42
jlibosvamarkmcclain: ok, so I'll make a patch that changes the order in chain for both branches, right?16:44
markmcclainmove it first in master16:45
markmcclainand then backport it to stable16:45
jlibosvaok16:46
jlibosvamarkmcclain: thank you16:46
markmcclainyou're welcome16:46
*** emagana has joined #openstack-neutron16:47
*** Mierdin has joined #openstack-neutron16:55
*** AlexF_ has quit IRC16:58
*** thedodd has quit IRC17:00
*** thedodd has joined #openstack-neutron17:01
*** morganfainberg is now known as morganfainberg|z17:07
*** ijw has quit IRC17:08
*** roeyc has quit IRC17:08
*** ijw has joined #openstack-neutron17:08
*** dave_tucker is now known as dave_tucker_zzz17:10
*** dave_tucker_zzz is now known as dave_tucker17:10
*** rohit404 has quit IRC17:15
openstackgerritJakub Libosvar proposed a change to openstack/neutron: Move db migration of ml2 security groups to havana  https://review.openstack.org/6941617:17
*** dave_tucker is now known as dave_tucker_zzz17:19
*** MM_at_HP has quit IRC17:23
*** HenryG has joined #openstack-neutron17:24
*** tongli has joined #openstack-neutron17:30
*** markmcclain has quit IRC17:31
*** markmcclain has joined #openstack-neutron17:32
*** markmcclain has quit IRC17:33
*** markmcclain has joined #openstack-neutron17:33
*** jpich has quit IRC17:36
*** thedodd has quit IRC17:38
*** afazekas has quit IRC17:38
openstackgerritArmando Migliaccio proposed a change to openstack/neutron: improve UT coverage for nicira_db operations  https://review.openstack.org/6669317:39
*** thedodd has joined #openstack-neutron17:39
*** marun has joined #openstack-neutron17:39
*** dave_tucker_zzz is now known as dave_tucker17:39
*** vkozhukalov has joined #openstack-neutron17:40
*** marun has quit IRC17:41
*** ivar-lazzaro has joined #openstack-neutron17:42
*** ygbo has quit IRC17:50
*** luqas has quit IRC17:53
*** ijw has quit IRC17:59
*** dguitarbite has quit IRC18:00
*** ijw has joined #openstack-neutron18:00
*** dave_tucker is now known as dave_tucker_zzz18:00
*** dave_tucker_zzz is now known as dave_tucker18:03
*** ijw has quit IRC18:04
*** nati_ueno has joined #openstack-neutron18:05
*** julim has quit IRC18:05
*** harlowja_away is now known as harlowja18:05
*** safchain has quit IRC18:06
*** ijw has joined #openstack-neutron18:13
*** zzelle_ has joined #openstack-neutron18:15
*** ijw has quit IRC18:16
*** ijw has joined #openstack-neutron18:17
openstackgerritJakub Libosvar proposed a change to openstack/neutron: Check during db migration if service* tables exist  https://review.openstack.org/6943318:25
*** nati_ueno has quit IRC18:25
*** thedodd has quit IRC18:26
*** nati_ueno has joined #openstack-neutron18:26
*** nati_ueno has quit IRC18:26
*** nati_ueno has joined #openstack-neutron18:27
*** jistr has quit IRC18:32
*** MM_at_HP has joined #openstack-neutron18:40
openstackgerritShiv Haris proposed a change to openstack/neutron: This migration changes the id field for the brocadenetworks table from int to string (uuid). This brocade specific table indexes using uuid  https://review.openstack.org/6819918:41
*** jprovazn has joined #openstack-neutron18:44
*** jlibosva has quit IRC18:48
*** marun has joined #openstack-neutron18:56
*** thedodd has joined #openstack-neutron19:00
*** afazekas has joined #openstack-neutron19:04
yjiang5_1irenab: hi19:05
*** itzikb has joined #openstack-neutron19:06
yjiang5_1ijw: hi19:08
*** vkozhukalov has quit IRC19:08
*** afazekas is now known as afazekas_pub19:21
*** dguitarbite has joined #openstack-neutron19:21
*** hshen__ has joined #openstack-neutron19:25
*** armax has joined #openstack-neutron19:28
*** dguitarbite has quit IRC19:28
*** dguitarbite has joined #openstack-neutron19:29
*** jprovazn has quit IRC19:34
*** clev has joined #openstack-neutron19:36
*** djoreilly has quit IRC19:39
openstackgerritShiv Haris proposed a change to openstack/neutron: Change index of brocade networks table from int to string  https://review.openstack.org/6819919:49
pcm_nati_ueno: ping19:56
*** gdubreui has joined #openstack-neutron19:59
*** thuc_ has quit IRC20:00
*** thuc has joined #openstack-neutron20:01
*** thuc_ has joined #openstack-neutron20:01
sc68calmarkmcclain: updated my part of the agenda for the meeting20:05
*** thuc has quit IRC20:05
*** rossella_s has quit IRC20:05
*** openstackgerrit has quit IRC20:06
*** openstackgerrit has joined #openstack-neutron20:06
*** julim has joined #openstack-neutron20:06
markmcclainsc68cal: thank you20:06
*** nati_uen_ has joined #openstack-neutron20:08
*** nati_ueno has quit IRC20:09
pcm_Anyone: Had some questions on vendor drivers for VPN service...20:11
pcm_Vendor device I have will require different identification for some items (e.g. IKE policy).20:12
pcm_Was thinking of generating and persisting a mapping of OpenStack VPN IDs to device's IDs.20:12
pcm_Should I do that persisting in service driver or device driver side?20:13
openstackgerritAbhishek Raut proposed a change to openstack/neutron: Support Port Binding Extension in Cisco N1kv plugin  https://review.openstack.org/6883320:15
*** IanGovett has left #openstack-neutron20:15
*** clev has quit IRC20:16
anteayabased on the conversation in -gate, I have to ask, how did neutron code become dependant on a kernel other than the one we gate on?20:19
anteayaeveryone tests using precise, correct?20:19
enikanorov_i think ppl are testing with what they have at hand20:20
*** clev has joined #openstack-neutron20:21
anteayaso is there an awareness of the enviroment we gate on?20:22
enikanorov_why does it matter?20:22
anteayaha ha ha ha20:23
anteayaonly because neutron regurarly breaks tests20:24
anteayaand people constantly try to shorehorn broken code into master20:24
anteayabecause it works for them20:24
enikanorov_what kind of neutron's broken code cause kernel crash?20:24
enikanorov_you do understand that it is unreladed, don't you?20:25
anteayahow did neutron get to be using a kernel we don't gate on?20:25
enikanorov_easily. just because we can't gate on the whole matrix20:25
anteayaI am asking a fundamental workflow problem20:26
enikanorov_fundamental problem is that kernel should not crash20:26
anteayagood habits breed good code20:26
enikanorov_we can't fix it by fixing our code20:26
*** snowblind2 has joined #openstack-neutron20:26
anteayaand being oblivious to what is going on around them is a constant issue20:27
*** dsockwell has quit IRC20:27
enikanorov_yeah, it's better to use interface without relying on implementation20:27
anteayathey why bother haing neutron in the gate at all?20:28
anteayait seems to be really hard to manage20:28
enikanorov_it is hard when the bottom of software stack is not as stable as we expect20:29
enikanorov_there's not much the top of the stack can do about it20:29
*** dsockwell has joined #openstack-neutron20:29
marunanteaya: people test on os's different from ubuntu, btw20:29
marunanteaya: the general rh policy is to validate on fedora/rhel before sending for review and falling back to ubuntu testing only when we experience gate failure.20:30
enikanorov_i think if gating on rhel/fedora was introduced, we'd have # of bugs doubled20:31
anteayamarun: which version of fedora/rhel?20:31
marunanteaya: depends on the person.20:32
anteayarhel/fedora is officially supported20:32
anteayaso no kernel version is specified?20:32
marunanteaya: usually the latest stable release20:32
marunanteaya: We don't depend on developers to discover gate problems.20:32
marunanteaya: that's what we have the gate for!20:33
anteayagreat20:33
marunanteaya: it's not that we don't test20:33
anteayawho fixes it when bad coded gets in?20:33
marunanteaya: but we need a consistent test to validate merges20:33
anteayaI thought that was the gate20:33
marunanteaya: I'm afraid I'm not clear on what you're driving at.20:34
anteayado you not feel the gate is a consistent test to validate merges20:34
openstackgerritMohammad Banikazemi proposed a change to openstack/neutron: Adds the new IBM SDN-VE plugin  https://review.openstack.org/6645320:34
enikanorov_anteaya: you do realize that it was kernel that failed gate tests, not neutron or nova?20:34
anteayaI am driving at workflow20:34
marunanteaya: at present?  The evidence would appear to point to 'no'.20:34
marunanteaya: But it's getting better.20:34
marunanteaya: workflow?20:35
anteayawell I still haven't seen any patches up to address the isolated tests20:35
marunanteaya: can you be more specific?20:35
anteayayes20:35
anteayasure20:35
anteayastart from a common env20:35
marunanteaya: how common?20:35
anteayaiterated code locally, tests pass20:35
anteayasubmit code20:36
*** jbrende has joined #openstack-neutron20:36
anteayawill I have been using ubuntu precise myself20:36
anteayaanyone who asks me about how to set up testing is suggested to use ubuntu precise20:36
marunanteaya: and rh developers will be using fedora or rhel20:36
anteayasure20:37
anteayawhich is officially supported20:37
mesteryThe software in Ubuntu Precies is ancient.20:37
mesteryReally old. Kernel and OVS are both super old there.20:37
anteayamestery: they are lts20:37
*** nati_uen_ has quit IRC20:37
mesterylts with lots of known performance issues, yes. :)20:37
marunmestery: is kernel still old if you install the latest release?20:37
anteayaand what we gate on20:37
enikanorov_"old" means 1 year?20:37
marun12.04-3 has 3.820:37
enikanorov_that kind of funny20:37
mesteryOVS 1.4 is 2+ years old enikanorov_20:37
anteayawe gate on lts20:38
*** nati_ueno has joined #openstack-neutron20:38
mesteryNo one in their right mind would run that anywhere near production20:38
marunmestery: if only that was the root of our problem it would be an easy fix!20:38
enikanorov_even 2...20:38
anteayawhen the next lts support comes out we will use that20:38
mesterymarun: Not the root, but certianly not helping either20:38
anteayamestery: take that up with jeblair20:38
marunmestery: not helping, but we have things in our control that have more influence on reliability20:38
mesterymarun: Agreed. :)20:38
marun:)20:39
enikanorov_i wonder how operators deploy into prod at all: new software are not proven, old one is... too old20:39
marunisn't that what mirantis is for?  ;)20:39
mesterymarun: Ha! :)20:39
enikanorov_yes, that's the part of our tricky plan :)20:40
* mestery loves it when a plan comes together.20:40
nati_uenopcm_: pong20:41
marunmestery: I'll tell you what I want to see happen.20:41
marunmestery: no more vm nonsense when we're debugging things.  lxc/docker support for neutron so we can iterate faster.20:42
mesteryRoger!20:42
pcm_nati_ueno: Had some Qs on VPN. Emailed to openstack-dev. Can you take a peek at some point?20:42
*** frankbutt has joined #openstack-neutron20:42
*** frankbutt has left #openstack-neutron20:43
ijwyjiang5_1: hey, you called?20:43
marunanteaya: huh20:43
marunanteaya: I've been testing with 12.04-3 which defaults to the backported raring kernel.20:44
marunanteaya: no wonder reproduction has been so hard :(20:44
nati_uenopcm_: sure20:45
pcm_nati_ueno: Thanks!20:45
*** carl_baldwin has joined #openstack-neutron20:47
openstackgerritArmando Migliaccio proposed a change to openstack/neutron: Remove extra network scheduling from vmware nsx plugin  https://review.openstack.org/6946520:48
*** jlibosva has joined #openstack-neutron20:48
*** ajo has quit IRC20:54
*** terrylhowe has joined #openstack-neutron20:54
anteayamarun: might be a part of it, yeah20:55
sc68calWe use 12.04 LTS in production, with the ubuntu cloud archive for more updated kernels and OVS20:59
sc68calhttps://wiki.ubuntu.com/ServerTeam/CloudArchive21:00
*** sweston has joined #openstack-neutron21:00
*** zz_ewindisch is now known as ewindisch21:01
*** banix has joined #openstack-neutron21:01
*** ivar-lazzaro has quit IRC21:05
*** sn6i23a has joined #openstack-neutron21:05
*** Sukhdev has joined #openstack-neutron21:05
mesterysc68cal: Thanks for the data point helping to prove no one uses OVS 1.4 in production at any sort of resonable scale :)21:06
*** irenab has quit IRC21:06
sc68calI have a bug that I need to file for Neutron, where some calls to the ovs_lib blows up when you use it with OVS 1.421:06
*** irenab has joined #openstack-neutron21:07
sc68calI think it's the timeout parameter that it sends on the CLI, it makes 1.4 barf21:07
*** jgrimm has quit IRC21:07
sc68calsince it's not a valid option I think21:07
sc68calin 1.421:07
sc68calI think calls to mod_flow in the ovs_lib, when using neutron and 1.4, it blows up. Sort of recalling it in bits and pieces now21:07
yjiang5_1ijw: Just wondering if Neutron support sR-IOV compute node now.21:08
*** ajo has joined #openstack-neutron21:10
hshen__mestery: Hi kyle, I have neutron running with odl driver now. But it fails when creating network21:11
mesteryhshen__: OK, it must be because of Neutron to ODL communication?21:11
hshen__2014-01-27 21:06:26.490 2329 ERROR neutron.plugins.ml2.managers [-] Mechanism driver 'opendaylight' failed in create_network_postcommit21:12
*** jgrimm has joined #openstack-neutron21:12
hshen__mestery: this is from neutron server log21:12
mesteryYes: What version of ODL are you running?21:12
mesteryYou should grab the very latest build21:12
*** irenab has quit IRC21:13
hshen__mestery: Mine is Janurary 16.21:15
mesteryhshen__: That is really old :)21:16
ijwyjiang5_1: OK, apparently I'm writing a document that describes the pci_stats and the pci_flavor_attrs interactions.  Might not get to it before tomorrow evening GMT, though - I just wanted to make you aware so that you look at it when I've done21:16
mesteryI would recommend getting the latest and run with OpenFlow 1.3 support.21:16
ijwyjiang5_1: and Neutron doesn't support it yet, irenab is writing the code at the moment21:16
yjiang5_1ijw: thanks.21:16
mesteryPop over to #opendaylight-ovsdb and look here: https://gist.github.com/anonymous/7bd7076ff74774cacd9c21:16
yjiang5_1ijw: Sorry I didn't ask clearly. I'm talking about Robert's mail. I think currently Neutron (w/o network nova scheduler ) requires all host has same network environment, right? that means, if we have SR-IOV only mode, it will cause trouble.21:18
ijwHaven't read it yet, hang on21:18
hshen__mestery: : OK. Let me grab a new odl.21:18
ijwDunno what he's written, but the idea was that Neutron-capable ports would have an extra-info attr that indicated their network attachment, Neutron would check it and would fail a VM start if it wasn't both there and suitable21:19
yjiang5_1ijw: for example, if we have a system w/o OVS support, it will be wrong if a VM is scheduled on it and the nic type is not specified as SR_IOV. So to that reason, we can't support SR-IOV only compute node.21:19
ijw(Decent scheduling to be sorted later, but that's no worse than provider networks now)21:19
ijwyjiang5_1: I don't think there's such a thing as an 'SRIOV only' compute node, I think he wants a compute node that is used only by VMs that have at least some SRIOV requirement21:20
ijwI see the logic, in some respects, but it's confusing the issue a bit because this isn't something we're working on before Juno21:20
yjiang5_1ijw: For "a compute node that is used only by VMs that have at least some SRIOV requirement" , why do we have such requirement? IIUC, in Irena's doc, only if a port is requires explicitly with SR-IOV requirement, it will not use SR-IOV resource, right?21:22
yjiang5_1ijw: sorr,  only if a port is requires explicitly with SR-IOV requirement, *otherwise* it will not use SR-IOV resource, right21:22
ijwyjiang5_1: I think the problem he's trying to solve is (in a mixed machine cloud) we make sure that SRIOV supporting machines are not overloaded with VMs that don't need SRIOV resources21:22
ijwSo a VM with *no* SRIOV requirements will not only not map in SRIOV ports but it will avoid that machine altogether21:23
yjiang5_1ijw: got it. So I think that should be implemented as a weight filter. After all, it's just one factor of host selection.21:23
*** alagalah has quit IRC21:25
yjiang5_1ijw: One extreme example is, a host is the only one left in the cloud with GPU assignment support,  and is one of multiple host with SR-IOV support. When a user requires a GPU with vNIC network, we will assign this host to that VM still.21:25
*** networkstatic has quit IRC21:28
*** networkstatic has joined #openstack-neutron21:28
ijwyjiang5_1: OK, I've read his email now.  I'm with Irena - I would expect there to always be a software switch in addition to the SRIOV devices.  I think we should eventually add something to avoid using resources on machines with scarce limited resources, absolutely - though doing that for PCI in isolation is not a general solution, it could be useful.21:34
*** afazekas_pub has quit IRC21:35
yjiang5_1ijw: I agree with you that we need avoid using host w/ SRIOV NIC, I just think it should be achieved through weight to keep it as just one factor. Of course, admin can always use host aggregate to achieve it.21:37
ijwyjiang5_1: I'm still not sure I understand what sriov_group actually is.21:37
ijwRobert keeps using it but not really defining it21:37
ijwyjiang5_1: Yeah, weight is preferable but I think the point was that because it's an enhancement then we can leave it till last rather than do it first21:38
*** tongli has quit IRC21:38
yjiang5_1ijw: totally agree.21:38
hshen__mestery: OK. got odl controller lastest version running and I am able to create network.21:41
mesteryhshen__: Nice!21:41
*** thuc_ has quit IRC21:41
*** thuc has joined #openstack-neutron21:42
*** thuc has quit IRC21:42
*** thuc has joined #openstack-neutron21:43
hshen__mestery: But I got VM binding failed.21:47
*** alexpilotti has quit IRC21:47
mesteryhshen__: Very weird.21:47
*** alexpilotti_ has joined #openstack-neutron21:47
hshen__he reason is in mechanism_odl.py, we cehck the constants.TYPE_LOCAL. The "constants" is imported  from neutron.plugins.common. When I check /usr/lib/python2.6/site-packages/neutron/plugins/common/constants.py, I don't see any TYPE_LOCAL defined21:48
hshen__mestery: so the neutron server log complains this:21:48
hshen__mestery:21:48
hshen__2014-01-27 21:42:00.950 2329 TRACE neutron.plugins.ml2.managers     if network_type in [constants.TYPE_LOCAL, constants.TYPE_FLAT,21:48
hshen__2014-01-27 21:42:00.950 2329 TRACE neutron.plugins.ml2.managers AttributeError: 'module' object has no attribute 'TYPE_LOCAL'21:48
hshen__2014-01-27 21:42:00.950 2329 TRACE neutron.plugins.ml2.managers21:48
mesteryhshen__: Yes, there were changes there, what versoin of underlying RDO are you using?21:49
mesteryYou may need to adjust some imports if it's Icehouse, but a bit older.21:49
hshen__This is RDO havana21:49
mesteryAh21:49
mesteryOK, so you will definitely need to adjust those then :)21:49
hshen__OK. where could I adjust?21:49
mesteryI'm not sure where that is in Havana, you may have to search a bit.21:50
*** ajo has quit IRC21:51
*** ajo has joined #openstack-neutron21:52
*** bjornar has joined #openstack-neutron21:59
hshen__mestery: mm.. let me find out.22:00
*** dims has quit IRC22:00
*** dims has joined #openstack-neutron22:02
*** markwash has quit IRC22:03
*** WackoRob_ has joined #openstack-neutron22:04
*** WackoRob_ has quit IRC22:04
*** samuelbercovici has joined #openstack-neutron22:04
*** markwash has joined #openstack-neutron22:04
*** WackoRob_ has joined #openstack-neutron22:04
*** markwash has quit IRC22:05
enikanorov_salv-orlando: markmcclain: samuelbercovici: so going back to the patch, we want to set additional parameters to providers22:05
enikanorov_the patch does that in 'configuration way'22:05
markmcclainwhat are tenant's configuring?22:06
enikanorov_the alternative would be to create 'flavors' in the db, dynamically, which is not easy to do, because providers are conf objects, not persistent22:06
*** pcm_ has quit IRC22:06
salv-orlandohi folks - I will be in & out in this discussion as I'm multitasking on a few things22:06
openstackgerritArmando Migliaccio proposed a change to openstack/neutron: Fix error while connecting to busy NSX L2 Gateway  https://review.openstack.org/6948222:07
enikanorov_markmcclain: setting up flavors is admin's task, tenant only uses it22:07
samuelbercovicithe specifc use case we have is that we have the the same driver able to provide lbaas in an HA manner and in a non-ha manner, I am not sure how this would be done using "flavors"22:07
markmcclainmarkmcclain: right22:07
markmcclainthat's what we'd need to figure out22:08
*** WackoRobie has quit IRC22:08
enikanorov_so my concern with dynamic flavors that they will be based on non-persistent object, so we would need a kind of configuration validation on neutron-service restart22:08
markmcclainmuch of this discussion about HA load balancers reminds me of the HA router discussion22:09
*** WackoRob_ has quit IRC22:09
enikanorov_HA loadbalancer here however is a very specific use case22:09
samuelbercovicimarkmcclain: do you say that a "sub" property of the provider could be "flavors"?22:09
*** SumitNaiksatam has quit IRC22:09
samuelbercoviciif so, that is still a configuration option, right?22:09
markmcclainno.. I think that providers should be removed from the API22:09
*** armax has left #openstack-neutron22:09
enikanorov_markmcclain: in favor of flavors?22:10
markmcclainyes22:10
enikanorov_that makes sense.22:10
enikanorov_but it seems that providers (in fact, drivers) should still be somewhere as we need mapping from driver to flavor22:10
markmcclainflavors provide a couple of benefits: tenants don't care about the implementation, can enable a multiple vendor strategy22:11
markmcclainthe mapping is scheduling22:11
markmcclainour current API requires the tenant to know too much about the backend22:11
enikanorov_i think that tenants may or may not want about the backend22:12
samuelbercoviciso instead of specifying providers, you soecify flavors?22:12
enikanorov_yes22:12
enikanorov_that is more flexible22:13
enikanorov_but i'm not sure i get how the mapping is done between drivers and flavors22:13
markmcclainenikanorov: if a deployer wants to give the tenant more control22:13
markmcclainenikanorov_: that's what needs to be determined22:13
salv-orlandowe can unless the tenant must provide some specific detail to configure an HA load balancer, for instance. Sambercovici, would that be possible?22:13
samuelbercoviciand then when selecting a flavor, it would select one of the providers that can address this flavor?22:14
*** jlibosva has quit IRC22:14
markmcclainright22:14
samuelbercovicicurrently our driver is configure slightly different if it provide ha vs. non-ha22:14
salv-orlandoi.e., having the tenant just saying "I want a 'yellow-diamond-flavor' loadbalancer, and then map it to a HA lb driver in the backend?22:14
salv-orlandoor a white-diamond-flavor and then it map to the non-HA version?22:15
enikanorov_honestly it doesn't seem more consistent than what is on the review :)22:15
samuelbercoviciso if we add a "property" to the provider, saying it can support 'yellow-diamond-flavor' , this requires (at least in radware case) some specific paramater that will instantiate another driver with different parameters22:15
enikanorov_because we would still need to do pretty complex matching22:15
enikanorov_samuelbercovici: it would be capabilities matching, i think22:16
enikanorov_otherwise it would not make sense22:16
markmcclainenikanorov_: I don't see how this any more complex than what the other projects are doing22:16
salv-orlandoI have a feeling that we're making it a bit more complex than what it is, but I'm sure it's just me not being informed. so I'll shut down now and learn in the background22:17
*** jecarey has quit IRC22:17
enikanorov_i think our flavors are a bit more complex than, say, nova's22:17
enikanorov_because it is not a fixed set of parameters, and in general that set is vendor-specific22:17
samuelbercovicienikanorov_: correct.22:18
EmilienMmarkmcclain: hey Mark, if you want to have a look at blockers to have Grenade / Neutron working: https://review.openstack.org/#/c/69416/22:19
markmcclainenikanorov_: I think we need about making that set of parameters more fixed and evolving over time22:19
enikanorov_markmcclain: that moves us back to the question if vendors are able to expose their specific features22:20
markmcclainenikanorov_: given that we aren't exposing base features now22:20
markmcclainI think we're considering items out of order22:20
markmcclainEmilienM: I'll take a look22:20
enikanorov_what particular base features do you mean?22:21
markmcclainlet's say l4, ssl, or l722:22
openstackgerritMohammad Banikazemi proposed a change to openstack/neutron: Adds the new IBM SDN-VE plugin  https://review.openstack.org/6645322:22
markmcclainright now we're requiring users to know too much about the deployment22:22
samuelbercovicimarkmcclain: not sure how this is related to the providors/flavors discussion22:24
enikanorov_my initial question on particular features is realted to flavors, however22:24
enikanorov_i'm wondering how can particular vendor configure different flavors for its solution22:25
enikanorov_if flavor parameters are fixed and not specific to that vendor22:25
markmcclainenikanorov_: vendors don't configure flavors22:25
markmcclainit is the deployers who configure22:25
enikanorov_right22:25
enikanorov_so deployers want to configure fast and cheap LBs22:25
samuelbercovicithere are specifics that define how the vendor's driver needs to be set-up to deliver the APIs and the SLA required22:26
enikanorov_and for vendor A and B it could be different set of parameters22:26
salv-orlandoI think that allowing tenants to specify required SLA in terms of capability and/or performance criteria is a rabbit hole where we'd better not go. Just my personal opinion here though22:27
markmcclainsalv-orlando: I agree22:28
enikanorov_the idea is that deployers define that22:28
enikanorov_tenants choose presets, e.g. flavors22:28
samuelbercoviciso if a deployer does dev&test and needs no ha deployment and then later on for integ and prod ha is required, there need to be something that some one selects22:29
samuelbercoviciwho is this someone and what does he needs to select and when22:29
samuelbercovici?22:29
*** thuc has quit IRC22:29
samuelbercoviciopps deployer == tenant22:30
enikanorov_i think 'flavor' is the right term here22:30
openstackgerritNachi Ueno proposed a change to openstack/neutron: Add enable_security_group option  https://review.openstack.org/6728122:30
*** thuc has joined #openstack-neutron22:30
enikanorov_flavor is selected by tenant, configured by deployer22:30
samuelbercoviciguys, do you agree with enikanorov_?22:31
enikanorov_we kind of moved out of the line of initial question which is in my opinion is 'how that flavor looks like?'22:32
*** ewindisch is now known as zz_ewindisch22:32
markmcclainenikanorov_: yes flavors are selected by tenant22:32
samuelbercovicigr822:32
markmcclainand configured by deployers based on their deployment22:32
enikanorov_of course. we need to agree on how flavor is constructed22:33
samuelbercoviciso the deployer define flavors, lets say plain and ha, and tenant can select the flavor when creating the pool22:33
*** sweston has quit IRC22:33
samuelbercovicithe information that radware can support plan and ha and that for plain a specific radweare driver configuration is needed neeeds to somehow happen22:34
salv-orlandothis workflow looks good to me. I think next up is how flavour should be defined to make this happen22:34
*** thuc has quit IRC22:34
*** mfink has quit IRC22:34
markmcclainyeah.. we need to really think about the definition process22:35
salv-orlandofor instance let's take the basic case, 1:1 to mapping between flavour and drivers. Won't work with the radware case unless they make two wrappers drivers which differently configure the same drivers according to the particular flavor22:35
markmcclainbecause this applies to more than just LBaaS22:35
enikanorov_1:1 mapping is what providers are now22:35
salv-orlandoOr one could have driver and a list of params which are passed to a driver init function. So you could use the same driver in different configurations22:36
enikanorov_salv-orlando: that is very close to what patch implements22:36
enikanorov_the only issue with it is that it doesn't move us towards flavor framework22:37
enikanorov_which is, however, for deployers mostly22:37
salv-orlandoI am just thinking aloud here.22:37
enikanorov_and tenant still chooses something, is it provider or flavor22:37
samuelbercoviciI agree, that22:37
samuelbercoviciopps..disregard22:38
salv-orlandoI think both enikanorov_ are samuelbercovici are then suggesting we should go with icehouse with the current proposed approach and then look at flavours for the next release?22:38
samuelbercovicisalv-orlando: even if we had flavors, we would still need somthing like the proposed patch and then map the flvors to the appropriate providers22:39
enikanorov_salv-orlando: my opinion is that proposed configuration-approach is consistent with what we have right now (providers)22:39
salv-orlandook, so we come full full circle back to the starting point, as usual22:39
markmcclainI'm still concerned about the technical debt22:40
enikanorov_basically yes, I'd say it is fine for Icehouse22:40
enikanorov_i don't fully understand what is techical debt here22:40
openstackgerritCarl Baldwin proposed a change to openstack/neutron: Reduce severity of log messages in validation methods  https://review.openstack.org/6903722:41
enikanorov_the intent is to add flavors, which a tenant-facing description of the service capability22:41
enikanorov_we may implement it this or that way, from tenant perspective it should not change22:41
enikanorov_for deployer it may change, however22:41
pcarverenikanorov_: Do you have use cases other than HA vs non-HA? I've worked with Alteon and F5 load balancers and I'm trying to think of any other feature beyond whether it's a single or pair that might fall under "flavor"22:42
pcarverI can think of lots of complex features, but for most of what I can think of "flavor" isn't enough.22:42
enikanorov_pcarver: bandwidth limits?22:42
enikanorov_or connection limits22:43
pcarverHmm, when I think of bandwidth I think more of metering and billing, but I suppose you could put in limits.22:43
enikanorov_billing is related, but orthogonal22:43
samuelbercovicisalv-orlando: I would understand that a "flavor" would enable higher selection logic to scheule the implementation based on it vs. specificaly selecting a provider. none-the-less, the capability to convey the meaning via the specific needed configuration could be done in way of the proposed proposal or in a very similar alternative. I would not like to see solving one be tied with providing the other if possible.22:44
enikanorov_for istance, you may want to schedule high-loaded lbs to certain appliances22:44
samuelbercovicipcarver: there might be sepcifc configuration related to how to connect to the overlay network22:44
*** silvrax has quit IRC22:45
*** ajo has quit IRC22:45
samuelbercovicialso, specifying whether using HW or SW base lbs22:46
pcarverOk, if you want to support bandwidth or connection limits at all rather than letting the dollars rule, then I see why flavors would be a simpler approach than fully extending the API to allow the tenant to tailor those settings.22:47
*** gdubreui has quit IRC22:47
enikanorov_i'm not against extending the API, absolutely22:47
pcarverIf you had a low cost, low end model of LB and a high cost high end model would those be the same provider in the current approach?22:47
enikanorov_pcarver: if those models are operated by the same driver, then yes22:48
pcarverok, in that case I definitely see why you need another means to distinguish.22:49
samuelbercovicipcarver: in radware case, its the same driver with different configuration, hence the discussed patch to allow registering different providers using the same driver and pssing differetn configuration oprions to the driver22:49
samuelbercovicimarkmcclain: salv-orlando: can we agree to go forward on this?22:51
enikanorov_is it better to not add feature, or to add feature that most probably will change?22:52
*** sweston has joined #openstack-neutron22:52
samuelbercovicienikanorov_: I think that it will not change. the "falvors" will be mapped on top so can't see a reason to change.22:53
salv-orlandoI think you both agree that this feature goes in the right direction and you both want to move to flavours. And I say you both, but I assume I am saying the whole lbaas community.22:53
enikanorov_i don't see why one needs flavors with what is done in that patch22:53
markmcclainenikanorov_: we need flavors because providers do not provide a multiple vendor solution22:54
samuelbercovicito address the following use case: I have both radware and lets say citrix, both can be used as "gold" standard and as a tenant I don't care which will be used22:54
enikanorov_markmcclain: how is that?22:54
markmcclainright now the provider dictates the driver22:55
salv-orlandoI think it's been 18 months we have been discussing this now.22:55
enikanorov_markmcclain: yep22:55
samuelbercoviciso as a tenant, I want to just say vip on "gold" and let the system choose the actual implementation for me22:55
enikanorov_markmcclain: do you mean tenant choses provider, and neutron schedules to *some* driver that is ok with provider?22:55
samuelbercovicienikanorov_: did you mean provider == flavor?22:56
enikanorov_samuelbercovici: right now i'm trying to understand why providers don't give multivendor solution22:57
salv-orlandoI just think that when I say m1.micro when booting a VM, this actually translates into CPU, RAM, and disk specs. I don't have anything like that in neutron.22:57
markmcclainsalv-orlando: you're also not choosing the underlying virt tech either22:57
enikanorov_salv-orlando: exactly. and possibly that can be diffrent for each vendor22:58
markmcclainit could be kvm, xen, hyperv, esx, etc22:58
markmcclainthat's the way LB flavors should work22:58
markmcclainbased on the attributes set agree on for flavors the system should schedule the pool to a LB instance22:58
enikanorov_hmm22:58
enikanorov_i think that is solved by filter scheduler22:59
enikanorov_the ability to amend the choice22:59
enikanorov_(in nova)22:59
markmcclainthe are lots of different ways to impact scheduling22:59
salv-orlandook, let's not digress into the capacity scheduling which is something specific to the hypervisor22:59
markmcclainwe first have to disconnect the logical configuration from the backend that implements23:00
salv-orlandolike RAM available. This might apply to LB as well in the future, but I don't see yet that possibly happening23:00
enikanorov_ability to disconnecting logical config from the backend is a strict requirement for vendors23:01
*** thuc has joined #openstack-neutron23:01
enikanorov_but i see your point23:01
enikanorov_funny thing is that such kind of scheduling was proposed in grizzly, but apparently it was a bit forward-looking at that point23:02
markmcclainenikanorov_: the proposal in Grizzly tried to do too many things at once23:02
salv-orlandoI don't think anybody here was talking about capability based scheduling as it was proposed for grizzly23:02
carl_baldwinHi, I've got a couple of approved changes that need reverifying.  I added "reverify bug 1253896" to the comments on Friday but nothing has happened.  Am I missing something?23:03
enikanorov_not capability, but it actually was about chosing the driver23:03
enikanorov_and scheduling to available device23:03
salv-orlandoI think we have digressed enough from the point where we started.23:03
enikanorov_yes, and trying to move back23:04
enikanorov_flavors framework with the requirement of making logical configuration fully independent from backend implementation has a number of prerequisities23:04
salv-orlandoSummarizing, is there value in having flavours which might translate into a service offering concept similar to what nova flavour do for VM? If the answer is no, and it's agreed, let's forget about it.23:05
enikanorov_that service (lbaas) need to comply first23:05
*** sweston has quit IRC23:05
*** Sukhdev has quit IRC23:05
enikanorov_btw, isn't flavor and service offering a synonyms?23:05
salv-orlandothey would be if the neutron team reaches consensus on a model common to all advanced services.23:08
enikanorov_salv-orlando: my take is that we need flavors. that however doesn't mean to me that we should not provide simpler and less flexible solution while better solution is on the way23:08
salv-orlandoreaching a consensus has always been impossible on this regard.23:08
markmcclaincarl_baldwin: link?23:08
carl_baldwinRight, https://review.openstack.org/#/c/67475/ and https://review.openstack.org/#/c/67558/23:09
salv-orlandoreverify has been turned off for good I think23:09
*** thuc has quit IRC23:09
salv-orlandothey need again a +123:09
salv-orlando+A sorry, but the neutron core team is not approving anything until the gate is unwedged, as this would probably just cause a reset of gate queue23:10
markmcclaincarl_baldwin: let's run a recheck first23:10
carl_baldwinFair enough.23:10
markmcclainsalv-orlando: agree we need to build consensus across all of the advance services23:10
*** jgrimm has quit IRC23:12
carl_baldwinmarkmcclain: I'll watch for the rechecks to complete, assuming they are successful, what will trigger the gate to run?23:12
salv-orlandoanyone can share the links to montreal ether pads?23:12
markmcclainif the recheck passes23:12
*** clev has quit IRC23:12
carl_baldwinmarkmcclain: That makes sense.  Thanks.23:12
markmcclainthan a core can add another +A to it23:12
enikanorov_ok, i'll initiate a discussion on flavors on the ml soon23:13
enikanorov_thanks for your time23:13
salv-orlandoyeah, a +A will put it back on the gate queue. carl_baldwin… however, with the current kernel issue we have we need to be *very* lucky to pass check and then gate ;)23:13
enikanorov_its 3:12 damn23:13
samuelbercovicimarkmcclain: the proposal is not trying to replace flavors and it will be an underlying building block fo it.23:13
samuelbercovicianyway, lets see the ML response23:14
carl_baldwinsalv-orlando: understood, thanks.23:15
samuelbercovicibye23:15
salv-orlandoadieu23:15
*** oda-g has joined #openstack-neutron23:16
*** oda-g has left #openstack-neutron23:16
*** jecarey has joined #openstack-neutron23:17
*** samuelbercovici has quit IRC23:17
*** jbrende has quit IRC23:18
hshen__mestery: I fix the issue. Now VMs are up. But it looks like openstack cannot spawn VM in other compute node.23:18
hshen__mestery: I have 4 VMs on the host of control node. And the network looks OK. They can ping each other. But I got erro when spawning VM5 with "no valid host" error.23:18
hshen__mestery: Besides, I don't see any change in ODL GUI window.23:19
hshen__mestery: Could you give some suggestion?23:19
*** jbrende has joined #openstack-neutron23:21
*** aymenfrikha has left #openstack-neutron23:25
*** sdague has quit IRC23:27
*** sdague has joined #openstack-neutron23:28
*** bjornar has quit IRC23:29
*** ijw has quit IRC23:29
*** zzelle_ has quit IRC23:30
*** ijw has joined #openstack-neutron23:31
*** banix has quit IRC23:33
*** dims has quit IRC23:33
*** ijw has quit IRC23:36
*** morganfainberg|z is now known as morganfainberg23:41
*** doude_ has joined #openstack-neutron23:44
*** thedodd has quit IRC23:45
*** yamahata__ has joined #openstack-neutron23:46
openstackgerritYoucef Laribi proposed a change to openstack/neutron: Implements an LBaaS driver for NetScaler devices  https://review.openstack.org/5752423:46
*** mlavalle has quit IRC23:48
*** mflobo_ has joined #openstack-neutron23:48
*** doude has quit IRC23:48
*** yamahata has quit IRC23:48
*** mflobo has quit IRC23:48
*** dims has joined #openstack-neutron23:48
*** thuc has joined #openstack-neutron23:49
*** puck has quit IRC23:50
*** gdubreui has joined #openstack-neutron23:52
*** thuc_ has joined #openstack-neutron23:53
*** peristeri has quit IRC23:53
*** hshen__ has quit IRC23:54
*** thuc has quit IRC23:55
*** networkstatic has quit IRC23:56
*** zzelle_ has joined #openstack-neutron23:56
*** BBG_Stephen has quit IRC23:59

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