Thursday, 2013-12-19

marunsalv-orlando: ping00:02
salv-orlandogood morning marun00:02
marunsalv-orlando: hiya :)00:02
marunsalv-orlando: I am hoping to convince you to approve the dhcp patch00:02
salv-orlandothe one I reviewed today?00:03
salv-orlandoor yesterday for you00:03
marunsalv-orlando: yes.00:03
*** mlavalle has quit IRC00:03
marunsalv-orlando: on the first point, the patch continues to ensure that an agent that is marked as disabled (admin_state_up = False) does not receive notifications00:03
dkehnmarun: do you know who or whom wrote the devstack/lib/floating_ips, I've got a few question00:04
marunsalv-orlando: the changes are that notifications are sent to enabled agents regardless of whether they are active (as per timely heartbeat), and that an error is logged if a notification cannot be sent.00:04
salv-orlandoyes, I was just wondering if that could be part of the db query (the admin_state filter) but is a minor point00:04
*** HenryG has quit IRC00:05
*** otherwiseguy has quit IRC00:05
marunsalv-orlando: i aimed for a simple patch.  the agent scheduler helper methods don't separate enabled from active and I didn't want to unfocus to cleanup.00:05
salv-orlandomarun: got the change I was just wondering if the logic should be "send always to all enabled agents" or "send to active agents if any, otherwise to all enabled"00:05
salv-orlandoseems you've implemented the second00:05
marunsalv-orlando: ah, I get it00:06
marundkehn: I think nati_ueno is the person to talk to.00:06
salv-orlandoat first glance it looks simpler to always send to all enabled agents and warn if none if active00:06
dkehnmarun: thx00:06
nati_uenowhat's up?00:06
salv-orlandobut I don't know if there's something I'm missing00:06
marunsalv-orlando: No, that's a good call.00:07
salv-orlandok00:07
marunsalv-orlando: There is no reason to avoid sending to inactive agents.00:07
marunsalv-orlando: the only question is whether to log if none or active or some are inactive.00:07
marunsalv-orlando: ?00:07
dkehnnati_ueno: we are timeing out on the https://github.com/openstack-dev/devstack/blob/master/exercises/floating_ips.sh#L14300:07
dkehnnati_ueno: the instance is active, and pingable from just a general ping not via the netns00:08
salv-orlandoI think you want to emit a warning if no agent is active. If there is at least one active agent I don't see a need to warn. Perhaps a log with debug level wit the number of active agents might help for debugging purposes.00:08
dkehnnati_ueno: this is just running the devstack locally00:08
nati_uenodkehn: did you enable namespace in local?00:09
marunsalv-orlando: I'm not sure we want still more debug logging :(00:09
dkehnnati_ueno: from the devstack format wouldn't  that be in the floating_ips?00:09
marunsalv-orlando: we really need a more granular logging system.  too much noise in debug logging right now00:09
nati_uenodkehn: Default is namespace enabled.00:10
dkehnnati_ueno: when I do a ip netns list that ns shows00:10
nati_uenodkehn: it is wired if we can ping to the IP without namespace00:10
marunsalv-orlando: as per your second comment, there has been a policy change wrt copyright notices - they are no longer required for empty files.00:10
nati_uenos/wired/strange/00:11
marunsalv-orlando: http://docs.openstack.org/developer/hacking/#openstack-licensing00:11
dkehnnati_ueno: yes I can ping it directly "ping 10.1.0.4" returns ping respomnses00:11
marunsalv-orlando: Now that I think about it, I'll file a bug for that.00:11
*** dave_tucker is now known as dave_tucker_zzz00:11
nati_uenodkehn: The network is private. so It shouldn't be pinggable from outside00:12
nati_uenodkehn: Could you try devstack with clean VM?00:12
dkehnnati_ueno: you mean from the host00:12
nati_uenodkehn: Even if it is from host, it shouldn't be pinggable00:12
dkehnsure, but I've done that more times than I can count00:12
dkehnnati_ueno: ok00:13
nati_uenodkehn: so, it get timeout on devstack on clean vm?00:13
salv-orlandomarun: summarising are you going to push a new patch set for always notified all enabled agents?00:13
dkehnnati_ueno: yes00:13
marunsalv-orlando: yes.00:13
*** banix has joined #openstack-neutron00:13
nati_uenodkehn: Are we facing same issue in the gating?00:13
salv-orlandomarun: cool. I am around for another hour and can +2 right away if needed.00:14
dkehnnati_ueno: check most of the grenade failures00:14
marunsalv-orlando: ok, cool.00:14
salv-orlandootherwise, I'll be up again in 6 hours00:14
dkehnnati_ueno: upper00:14
dkehnnati_ueno: yepper00:14
*** layer427expert has joined #openstack-neutron00:14
nati_uenodkehn: sounds like some degration00:14
nati_uenodkehn: could you share the result of ovs-vsctl show ?00:15
dkehnnati_ueno: http://paste.openstack.org/show/55399/00:15
anteayadkehn: I don't see a devstack/lib/floating_ips file00:16
dkehnanteaya: https://github.com/openstack-dev/devstack/blob/master/exercises/floating_ips.sh00:16
nati_uenodkehn: Thx. Could you also share neturon port-list -c id -c device_owner00:16
anteayathe exercises00:16
anteayayes okay00:17
*** dave_tucker_zzz is now known as dave_tucker00:18
*** layer427expert has joined #openstack-neutron00:18
dkehnnati_ueno: http://paste.openstack.org/show/55400/00:18
anteayalayer427expert: did you get your use of git review sorted out to your satisfaction?00:18
nati_uenodkehn: Thanks. "neturon port-list -c id -c device_owner "  <-- could you add -c id -c device_owner  ?00:19
dkehnnati_ueno: sure, sorry00:19
layer427expertKind of I did but I am still dealing with PEP8 issues.... Local testing is claiming things are good but remote does not00:19
nati_uenodkehn: np00:19
layer427experttrying to sort that out but everything else is good.00:19
anteayalayer427expert: do you have a link to your patch?00:19
layer427expertThanks!00:19
anteayaI can look at the pep800:20
layer427expertYahttp://logs.openstack.org/64/62464/8/check/gate-neutron-pep8/9dff757/console.html00:20
dkehnnati_ueno: http://paste.openstack.org/show/55401/00:20
anteayathanks00:20
layer427experthttps://review.openstack.org/#/c/62464/00:20
dkehnnati_ueno: http://paste.openstack.org/show/55402/   just in case00:21
nati_uenodkehn: Thanks. It looks like neutron debug command is broken.00:21
dkehnnati_ueno: what lead use to that conclusion?00:21
nati_uenodkehn: The port Port "tap8d47266e-2d"'s vlan id is 409500:21
anteayalayer427expert: okay for starters https://review.openstack.org/#/c/62464/ is over 2000 lines in the patch00:21
nati_uenodkehn: it should be 100:22
salv-orlandoneutron core devs -> the patch https://review.openstack.org/#/c/58860/ was already approved by I blocked it because it failed on the gate queue for bug 1253896. I looked at logs to exclude any relation with such bug and performed several rechecks, which were all successfull. If you can approve again I reckon it's safe to merge.00:22
anteayalayer427expert: okay so this is a patch for https://blueprints.launchpad.net/neutron/+spec/a10networks-lbaas-driver00:23
layer427expertyesyes00:23
dkehnnati_ueno: in the devstack flow where does that get built up00:23
anteayawhich you submitted, approved and assigned to yourself00:23
anteayahas anyone else reviewed this blueprint?00:23
nati_uenodkehn: here https://github.com/openstack-dev/devstack/blob/master/lib/neutron#L84700:23
salv-orlandolayer427expert: perhaps your commit message refers only to changes in the last patch set? or do 2,000 lines just fix pep8 errors (being ironic here)00:24
layer427expertNot in the community... It was late I can assign it to who ever.00:24
anteayaand over 1000 lines in your other patch00:24
anteayalets talk a bit00:24
layer427expertI reformated the files based on pep00:24
layer427expertHowever I think the commit file was not edited properly.00:24
anteayawe try to go with small changes to the code base00:25
anteaya200 line of code per patch or less is optimal for a reviewer00:25
dkehnnati_ueno: so taking the Q_USE_DEBUG_COMMAND=True out of the localrc would stop that?00:25
nati_uenodkehn: yes.00:25
anteayaunless there are rare circumstances00:26
anteayayou can make one patch dependant on another00:26
layer427expertanteaya:so I should pull the patches and then rebase then start from scratch?00:26
layer427expertabandon00:26
layer427expertis what I meant00:26
dkehnnati_ueno: hmm, good to know bu I'm pretty sure this is how tgrenade sets it up00:26
anteayaso that you can control the order the patches are merged00:26
anteayalayer427expert: no you don't need to abandon00:26
anteayalet's just talk a minute00:26
anteayawhat is your motivation for the blueprint?00:26
nati_uenodkehn: I'm new to granade, so could you share some docs on that?00:27
anteayawhat do you want to see happen and how does that improve the project?00:27
nati_uenodkehn: so where we get this error?00:27
layer427expertWill it enables our customer to utilize our platform with out a modification of Neutron.00:27
anteayaokay that's fair00:28
dkehnanteaya: so I'm basically running devstack-vm-gate.sh which runs the exercises.sh --> which runs the floating_ips.sh, this is basically what grenade testing does00:28
anteayado you see anyone else using this code, or do you think this code is pretty unique to your own needs?00:28
anteayadkehn: I was wondering if that is what it was00:28
dkehnnati_ueno: https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate.sh00:28
nati_uenodkehn: is this granade?00:29
layer427expertWell considering it is specifically for A10 then it will most likely be utilized by A10 Customers.00:29
anteayaand that is awesome, I have a patch up to turn on exercises (non-voting) for our master and havana patches: https://review.openstack.org/#/c/62930/400:29
anteayadkehn: would be glad of a review if you have the time00:29
anteayalayer427expert: okay00:29
anteayawell let's look at it with that in mind00:30
anteayasalv-orlando: can you offer any suggestions00:30
dkehnnati_ueno: yes this is what grenade is it runs the for mentioned scripts with the https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate.sh#L285 set00:30
anteayadoes layer427expert's direction so far seem like he will reach his goal?00:30
dkehnanteaya: huh00:31
dkehnanteaya: I'm about ready to head off for dinner, or at least cooking it, if it can wait till afterwords00:31
anteayadkehn: sure00:33
dkehnanteaya: nati_ueno that probably won;t work with https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate.sh#L7500:33
salv-orlando2,595 lines diff won't make review any shorter. In the past we had similar discussion with driver/plugin implementors regarding splitting the patch in smaller chunks, but in most cases the answer was that it was very difficult or not feasible at all and in general led to patches which were not self-contained anyway. I don't know if this is layer247expert case as well.00:33
anteayaI would shudder at having to review 1000 lines of code in one sitting00:34
dkehnnati_ueno: let me try it without DEBUG on and then I'll localize around the DEBUG sound fair enough00:34
dkehnnati_ueno: or reasonable00:34
layer427expertWhat was implemented is the smallest ~amount of code that can be utilized to enable our devices and virtual appliances.00:34
salv-orlandoI also have to check with markmcclain where we stand for 3rd party testing for drivers. I do not recall the policy now.00:34
salv-orlandolayer427expert: I was kind of sure that was the answer. I guess then the core team has just to swallow it and start reviewing it.00:35
anteayalayer427expert: right, we are just discussing format for patches00:35
nati_uenodkehn: let's me confirmed. It is not working with granade? so devstack without grande works?00:35
layer427expertsalv-orlando: Mark said he want 3rd party testing to occur before review. That is why I was placing the patches in draft00:35
layer427expertIs there a better way?00:36
anteayagrenade doesn't work for neutron right now00:36
nati_uenodkehn: It won't work without Debug command00:36
anteayajlibovar is trying to get it working00:36
dkehnnati_ueno: I see the confusion, no I'm testing with jsut devstack and I'll post my lcoalrc00:36
salv-orlandowork in progress rather than draft maybe. I think the draft makes the patch 'private' as well.00:36
nati_uenodkehn: so there is no relation with granade for this issue?00:36
*** dims_ is now known as dims00:37
anteayastay away from draft00:37
anteayait creates so many problems later in the life of the patch00:37
nati_uenodkehn: if you have a faild gating run with this issue, could you share the url?00:37
dkehnnati_ueno: ythere is a reationship in that this is hat grenade is going to do is run devstack.sh00:37
anteayause work in progress00:37
dkehnnati_ueno: http://logs.openstack.org/63/61663/2/check/check-grenade-dsvm-neutron/5f49167/console.html.gz00:37
dkehnnati_ueno: basically any neutron jenkins run00:38
dkehnnati_ueno: http://logs.openstack.org/63/61663/2/check/check-grenade-dsvm-neutron/5f49167/00:38
nati_uenodkehn:  check-tempest-dsvm-neutron looks success. but check-grenade-dsvm-neutron/ fails00:38
anteayadkehn: yes00:38
nati_uenodkehn: so this issue happens when we run granade + neutron00:39
anteayathat is why I am turning on exercises for neutron for master and havana00:39
anteayaso that this patch can be debugged: https://review.openstack.org/#/c/58695/00:39
anteayait is hitting the same error00:39
dkehnnati_ueno: yes, I devstack-vm-gate.sh basically to get my devstack setup up00:39
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Fixed PEP8 import alphabetical order  https://review.openstack.org/6246400:39
anteayaexercises don't work with havana so they were turned off, but they need to work for grenade00:40
dkehndkehn: goes for food00:43
anteayajog0: did you say you were going to change the priority of this bug: https://bugs.launchpad.net/neutron/+bug/124425500:44
jog0anteaya: I wasn't clear on that, I said that the priority could be changed, its not a gate issue at the moment00:45
jog0but think high is appropriate being setting api workers to 4 shouldn't do this00:46
anteayawould you mind adding that as a comment?00:46
nati_uenodkehn: This line should use neutron https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate.sh#L7600:47
jog0anteaya: done00:47
anteayajog0: thanks00:47
anteayaI think I'll sign off for the night00:47
jog0o/ night00:48
anteayalayer427expert: you don't have to abandon your code00:48
anteayayou can make your patch smaller if that works and link patches as dependances00:49
anteayayou can unabandon anytime if you want00:49
layer427expertI I just realized that we can put it into a work in progress and that would00:49
layer427experteliminate the review00:49
anteayano it won't00:49
layer427expertuntil it is ready00:49
anteayawork in progress is a button00:49
anteayajust press it00:50
anteayaif you want it out of work on progress just submit a new patchset00:50
anteayadon't lose the history of comments on your work00:50
layer427expertSo pressing the button will put it into a non-review state until it is ready to be reviewed?00:50
anteayathat just confuses people00:50
anteayawork in progress means that people can review it if they want00:51
layer427expertOk00:51
anteayabut you are letting them know that you are still working on the patch, it isn't ready to be merged00:51
layer427expertok that is the objective...00:51
anteayayou can reset the work in progress setting with each new patchset00:51
*** krast has quit IRC00:51
layer427expertOk00:51
layer427expertThanks00:51
anteayayes, it just allows reviewers to make the most productive use of their time00:51
anteayayou are welcome00:52
anteayaglad you are here for the chat00:52
anteayafeel free to ask questions00:52
anteayawe will try to help as best we can00:52
layer427expertThanks00:52
anteayayou are welcome00:52
layer427expertAppreciate it.00:52
anteayamy pleasure00:52
anteayaand stay away from draft00:53
anteayait can cause so many issues later when you try to merge00:53
anteayajust use the work in progress button00:53
anteayaokay now signing off00:53
anteayanight and see you tomorrow00:53
*** ashaikh has quit IRC00:55
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Fixed PEP8 import alphabetical order  https://review.openstack.org/6246400:56
*** otherwiseguy has joined #openstack-neutron00:56
*** safchain has joined #openstack-neutron00:59
*** safchain has quit IRC01:00
marunok, i am now pretty concerned at our use of mock01:02
marunthere is no concept of passthrough, so mocking things like logging to check the call count can end up hiding errors (e.g. string substitution errors)01:04
dkehnback01:10
dkehnnati_ueno: you still around01:12
nati_uenodkehn: yes01:12
nati_uenodkehn: This line should use neutron https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate.sh#L7601:12
dkehnnati_ueno: not sure I understand your ^^^^^ remark01:12
nati_uenodkehn: MY_ENABLED_SERVICES=$MY_ENABLED_SERVICES,quantum <-- adding quantum01:12
dkehnnati_ueno: instead of quantum01:12
dkehnnati_ueno: hmm, loads the neutron server and what not ok, is there something else dependent upon the ENABLED_SERVICES01:13
nati_uenodkehn: https://github.com/openstack-dev/devstack/blob/master/lib/neutron#L13001:14
nati_uenodkehn: so some script's using is_service_enabled neutron01:14
nati_uenodkehn: so neutron should be in the service list01:14
nati_uenodkehn: it should be MY_ENABLED_SERVICES=$MY_ENABLED_SERVICES,neutron01:16
dkehnnati_ueno: let me amke a quick run at that01:16
*** safchain has joined #openstack-neutron01:16
salv-orlandoneutron core devs -> the patch https://review.openstack.org/#/c/58860/ was already approved by I blocked it because it failed on the gate queue for bug 1253896. I looked at logs to exclude any relation with such bug and performed several rechecks, which were all successfull. If you can approve again I reckon it's safe to merge.01:16
nati_uenodkehn: Thanks. may be I'm wrong,01:17
*** suresh12 has quit IRC01:17
nati_uenodkehn: but it should worth try01:17
dkehnnati_ueno: let me try it , it would be wonderfull if that all it is01:17
*** suresh12 has joined #openstack-neutron01:17
dkehnnati_ueno: but at minumum there is a labelling issue to resolve01:18
nati_uenodkehn: yeah, I agree01:18
*** rwsu has quit IRC01:18
*** suresh12 has quit IRC01:18
*** safchain has quit IRC01:19
*** thansen has quit IRC01:19
*** suresh12 has joined #openstack-neutron01:19
openstackgerritMaru Newby proposed a change to openstack/neutron: Send DHCP notifications regardless of agent status  https://review.openstack.org/6116801:19
*** rwsu has joined #openstack-neutron01:19
marunnati_ueno: I added a blueprint as you requested for pm debug, feel free to +2  ;)  https://review.openstack.org/#/c/43776/01:21
*** yfujioka has joined #openstack-neutron01:22
nati_uenomarun: Thanks! +2ed01:23
marunnati_ueno: much appreciated01:23
nati_uenomarun: This patch is super cool :)01:23
marunnati_ueno: will be even cooler when I don't have to keep manually applying, heh.01:24
*** thansen has joined #openstack-neutron01:24
nati_uenomarun: ha ha true01:24
*** pcm_ has quit IRC01:25
marunanyone from radware here?01:26
layer427expertno but A10 :)01:28
marunmarkmcclain: Are there any guidelines for how 3rd party testing should interact with gerrit?  Seeing what appears to be gerrit messages from 3rd party jobs makes me think letting jobs spew without restriction is going to be a problem.01:29
*** Jianyong has joined #openstack-neutron01:32
openstackgerritMaru Newby proposed a change to openstack/neutron: Send DHCP notifications regardless of agent status  https://review.openstack.org/6116801:33
dkehnnati_ueno: pretty much the same outcomde01:36
nati_uenodkehn: hmm sorry01:36
dkehnnati_ueno:  timeout 90 sh -c 'while ! sudo /usr/local/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ip netns exec qprobe-4cb65bcd-ff8\01:36
dkehn3-492c-830a-85cebff4670f ping -w 1 -c 1 10.1.0.4; do sleep 1; done'01:36
*** dzyu has joined #openstack-neutron01:36
dkehnnati_ueno: is what its failing on ,same place01:36
dkehnnati_ueno: will put together a past01:37
dkehns/past/paste01:37
nati_uenodkehn: thanks01:37
*** yamahata has joined #openstack-neutron01:39
dkehnnati_ueno: http://paste.openstack.org/show/55409/01:40
nati_uenodkehn: yeah, pretty much same01:41
layer427expertcheck-tempest-dsvm-neutron-pg FAILURE in 33m 02s01:44
layer427expertcheck-tempest-dsvm-neutron-isolated FAILURE in 36m 41s01:44
layer427expertcheck-tempest-dsvm-neutron-pg-isolated FAILURE in 31m 58s01:44
layer427expertI got an error from jenkins with failures on01:44
layer427expertthe above01:44
layer427experthttps://bugs.launchpad.net/bugs/125489001:45
layer427expertBadRequest: Unable to find security_group with name 'secgroup_general--tempest-1401508404' (HTTP 400) (Request-ID: req-5d1419ef-4045-40e5-be58-ddd1abce533f)01:45
layer427expertthis was for check-tempest-dsvm-neutron-isolated01:46
dkehnnati_ueno: not sure if this helps but here's the setup_neutron_debug bash debug: http://paste.openstack.org/show/55410/01:48
nati_uenodkehn: could you mail me zip of /etc/neutron ? my mail address is nachi@ntti3.com01:49
*** julim has quit IRC01:49
dkehnnati_ueno: ok01:50
*** harlowja has quit IRC01:51
openstackgerritDazhao Yu proposed a change to openstack/neutron: Calculate stateless IPv6 address  https://review.openstack.org/5618401:55
dkehnnati_ueno: check your mail01:57
nati_uenodkehn: Thanks! I got email01:58
nati_uenodkehn: hmm config looks good..02:00
nati_uenodkehn: Which version the granade updates from ?02:01
dkehnthre is really no grenade involved in my test I'm pretty much using devstack.sh02:01
dkehnwith devstack-vm-gate.sh , that is modified to drive it02:02
dkehnwhich is what grenade is using by by default02:02
*** layer427expert has quit IRC02:02
nati_uenodkehn: hmm we should identify what's different with neutron gating without granade script and with granade script02:03
dkehnthe reason why this is done this way is to minimize the effects of gate issue during development02:03
*** harlowja has joined #openstack-neutron02:03
nati_uenodkehn: so how to run devstack.sh should be different02:03
nati_uenodkehn: for instance localrc's02:04
dkehnits not differenet, but it deos run the exercises which devstack.sh does not02:04
dkehnsso the gate will use https://github.com/openstack-infra/devstack-gate with different sets of parameters is variouos phase of the gating process02:05
*** clev has joined #openstack-neutron02:06
dkehnduring grenade testing as demonstrated from failed tests you see that exercises are run as part of that02:06
*** layer427expert has joined #openstack-neutron02:11
*** networkstatic_zZ is now known as networkstatic02:24
*** clev has quit IRC02:25
nati_uenodkehn: so you are executing this line? https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate.sh#L24602:26
nati_uenodkehn: running devstack-gate  with DEVSTACK_GATE_GRENADE=102:27
dkehnnati_ueno: no I am not02:27
nati_uenodkehn: so you are running devstack-gate  with DEVSTACK_GATE_GRENADE=0 ?02:28
dkehnnati_ueno: that is correct02:28
dkehnnati_ueno: what I'm doing is basically running stack.sh and then the exercise.sh and thats about it02:29
nati_uenodkehn: so what you are doing is same with check-tempest-dsvm-neutron ?02:29
dkehnnati_ueno: is there a dependancy upon the exercises and grenade?02:29
dkehnnati_ueno: I'm not that familiar with that but its done locally02:30
*** krast has joined #openstack-neutron02:30
*** layer427expert has quit IRC02:30
nati_uenodkehn: check-tempest-dsvm-neutron runs the devstack-gate script without granade02:31
nati_uenodkehn: it looks it is working in the gating env02:31
nati_uenodkehn: this is an example http://logs.openstack.org/46/21946/26/check/check-tempest-dsvm-neutron/01a9c21/02:31
dkehnnati_ueno: ok, then I gues what would be different02:31
nati_uenodkehn: This is localrc http://logs.openstack.org/46/21946/26/check/check-tempest-dsvm-neutron/01a9c21/logs/localrc.txt.gz02:32
nati_uenodkehn: could you share your localrc ? (may be I shared before..)02:32
*** clev has joined #openstack-neutron02:33
dkehnnati_ueno: the log I'm at the log http://logs.openstack.org/46/21946/26/check/check-tempest-dsvm-neutron/01a9c21/console.html does appear to be running exercise.sh02:34
dkehnnati_ueno: am I looking in the wrong place02:34
dkehnnati_ueno: will post it02:34
nati_uenodkehn: Thanks02:35
*** WackoRobie has joined #openstack-neutron02:35
nati_uenodkehn: check-grenade-dsvm-neutron is with granade02:35
dkehnnati_ueno: http://paste.openstack.org/show/55415/02:36
dkehnnati_ueno: yes understand but I don't see the execution of the exercise.sh02:36
nati_uenod,02:38
nati_uenodkehn: Ah you are right.. I didn't know exercise.sh isn't running in check-tempest-dsvm-neutron02:39
dkehnnati_ueno: are you going to be around tomorrow? getting late here02:39
nati_uenodkehn: sure02:40
dkehnnati_ueno: what tz are you in02:40
nati_uenodkehn: pst02:40
dkehnnati_ueno: ok, I'm in MDT02:40
dkehnnati_ueno: close02:40
nati_uenodkehn: oh you are hard worker :)02:40
dkehnnati_ueno: u too02:40
nati_uenodkehn: not so late in PST now02:41
dkehnnati_ueno: thanks tons, really, will contact you tomorrow02:41
nati_uenodkehn: sure TL!02:41
dkehnl8r02:41
*** nati_ueno has quit IRC02:48
*** dave_tucker is now known as dave_tucker_zzz02:49
*** vkozhukalov has joined #openstack-neutron03:06
*** WackoRobie has quit IRC03:07
*** nati_ueno has joined #openstack-neutron03:35
*** WackoRob_ has joined #openstack-neutron03:38
*** WackoRob_ is now known as WackoRobie03:51
*** ashaikh has joined #openstack-neutron03:52
*** WackoRobie has quit IRC03:52
*** WackoRobie has joined #openstack-neutron03:52
*** julim has joined #openstack-neutron03:54
*** suresh12 has quit IRC03:57
*** julim has quit IRC03:57
openstackgerritKevin Benton proposed a change to openstack/neutron: BigSwitch: Fixes floating IP backend updates  https://review.openstack.org/6304704:00
*** nati_ueno has quit IRC04:01
*** WackoRobie has quit IRC04:04
*** WackoRobie has joined #openstack-neutron04:04
openstackgerritKevin Benton proposed a change to openstack/neutron: BigSwitch: Fixes floating IP backend updates  https://review.openstack.org/6304704:06
*** yamahata has quit IRC04:11
*** yamahata has joined #openstack-neutron04:11
*** yamahata__ has quit IRC04:12
*** yamahata__ has joined #openstack-neutron04:13
*** yamahata__ has quit IRC04:13
*** yamahata_ has joined #openstack-neutron04:13
*** banix has quit IRC04:28
*** banix has joined #openstack-neutron04:34
*** banix has quit IRC04:38
*** banix has joined #openstack-neutron04:46
*** nati_ueno has joined #openstack-neutron04:46
*** banix has quit IRC04:47
*** rohit404 has joined #openstack-neutron04:58
*** clev has quit IRC04:59
*** yfried has quit IRC05:00
*** chandankumar has joined #openstack-neutron05:02
*** SumitNaiksatam has quit IRC05:09
*** WackoRobie has quit IRC05:11
*** SumitNaiksatam has joined #openstack-neutron05:25
*** Jianyong has quit IRC05:33
*** harlowja is now known as harlowja_away05:40
*** WackoRobie has joined #openstack-neutron05:41
*** Jianyong has joined #openstack-neutron05:46
*** mlavalle has joined #openstack-neutron05:48
*** mlavalle has quit IRC05:48
*** WackoRobie has quit IRC05:50
*** bashok has joined #openstack-neutron05:52
*** suresh12 has joined #openstack-neutron05:52
*** otherwiseguy has quit IRC05:53
*** garyk has joined #openstack-neutron05:53
*** harlowja_away is now known as harlowja05:59
*** nati_ueno has quit IRC06:05
*** yfried has joined #openstack-neutron06:06
*** majopela has joined #openstack-neutron06:08
*** WackoRobie has joined #openstack-neutron06:16
*** jlibosva has joined #openstack-neutron06:18
*** WackoRobie has quit IRC06:22
*** zz_ajo is now known as ajo06:28
*** ajo is now known as zz_ajo06:29
*** zz_ajo is now known as ajo06:29
*** ajo is now known as zz_ajo06:33
*** nati_ueno has joined #openstack-neutron06:37
openstackgerritJenkins proposed a change to openstack/neutron: Imported Translations from Transifex  https://review.openstack.org/6305606:37
*** SushilKM has joined #openstack-neutron06:47
*** WackoRobie has joined #openstack-neutron06:48
*** Abhishek_ has joined #openstack-neutron06:48
*** amritanshu_RnD has joined #openstack-neutron06:52
*** vkozhukalov has quit IRC06:52
*** WackoRobie has quit IRC06:53
*** alex_klimov has joined #openstack-neutron06:54
*** SushilKM has quit IRC07:02
openstackgerritMaru Newby proposed a change to openstack/neutron: Send DHCP notifications regardless of agent status  https://review.openstack.org/6116807:08
*** ashaikh has quit IRC07:11
*** Abhishek_ has quit IRC07:13
*** irenab_ has joined #openstack-neutron07:14
*** WackoRobie has joined #openstack-neutron07:18
*** WackoRobie has quit IRC07:23
*** suresh12 has quit IRC07:29
*** SushilKM has joined #openstack-neutron07:39
*** fouxm has joined #openstack-neutron07:49
*** nati_ueno has quit IRC07:54
*** SushilKM__ has joined #openstack-neutron08:03
*** SushilKM has quit IRC08:04
*** harlowja is now known as harlowja_away08:04
openstackgerritberlin proposed a change to openstack/neutron: add router_id to response for CRU on fw/vip objs  https://review.openstack.org/5912908:12
openstackgerritSridar Kandaswamy proposed a change to openstack/neutron: Remove FWaaS Noop driver as default and move to unit tests dir  https://review.openstack.org/6306608:19
kruskaklianteaya: thanks, it is a bit late for me, but if I'm awake I'll try to join08:22
*** Mierdin has quit IRC08:24
openstackgerritjun xie proposed a change to openstack/neutron: Change from eager load to lazy load  https://review.openstack.org/6102708:27
*** vkozhukalov has joined #openstack-neutron08:29
openstackgerritSalvatore Orlando proposed a change to openstack/neutron: Process port_update notifications in the main agent loop  https://review.openstack.org/6196408:39
*** djoreilly has joined #openstack-neutron08:45
openstackgerritSimon Pasquier proposed a change to openstack/neutron: neutron-rootwrap-xen-dom0 handles data from stdin  https://review.openstack.org/6234608:51
*** enikanorov has quit IRC08:53
*** marun has quit IRC08:53
*** rohit404 has quit IRC08:53
*** WackoRobie has joined #openstack-neutron08:57
*** jroovers has joined #openstack-neutron08:57
*** jroovers has quit IRC09:01
*** ygbo has joined #openstack-neutron09:02
*** jroovers has joined #openstack-neutron09:06
*** safchain has joined #openstack-neutron09:06
*** yfujioka has quit IRC09:07
openstackgerritAkihiro Motoki proposed a change to openstack/neutron: Use base.BaseTestCase in NVP config test  https://review.openstack.org/6307409:08
*** yongli is now known as yongli_away09:08
*** rohit404 has joined #openstack-neutron09:09
*** amuller has joined #openstack-neutron09:09
*** gongysh has joined #openstack-neutron09:10
gongyshsalv-orlando: ping09:10
gongyshamotoki: ping09:13
amotokigongysh: hi09:15
gongyshamotoki: I found that neutron net-list cannot list the external networks now.09:15
gongyshamotoki: I mean with very non-admin user.09:16
gongyshamotoki: If it is the case, how can I create a router with gateway interface?09:17
amotokigongysh: I am now searching bugs. I saw a related bug to this.09:17
amotokigongysh: in that case non-admin fails to set external gateway.09:17
gongyshamotoki: I remember that should work before.  I mean non-admin could list external networks before.09:19
amotokigongysh: according to my experience we can see ext_net first but at some timing ext_net disappears from net-list.09:20
gongyshamotoki: will u file a bug or send it on maillist?09:23
amotokigongysh: https://bugs.launchpad.net/neutron/+bug/125198209:24
amotokigongysh: in addition https://bugs.launchpad.net/neutron/+bug/1254555 may be related.09:24
amotokigongysh: are you seeing this issue now? The priority was changed to low a few weeks ago. If you see it frequently please update the bug priority.09:27
*** jpich has joined #openstack-neutron09:27
amotokigongysh: i haven't experienced this recently.09:27
gongyshamotoki: ok, I will have an explore09:27
gongyshamotoki: thanks09:27
amotokigongysh: it is really strange behavior....09:28
jroovershi enikanorov__09:36
*** jroovers has quit IRC09:38
*** jorisroovers has joined #openstack-neutron09:38
*** rohit404 has joined #openstack-neutron09:41
salv-orlandogongysh: how can I help you?09:42
gongyshsalv-orlando: <amotoki> gongysh: hi09:47
gongysh<gongysh> amotoki: I found that neutron net-list cannot list the external networks now.09:47
gongysh<gongysh> amotoki: I mean with very non-admin user.09:47
gongysh<gongysh> amotoki: If it is the case, how can I create a router with gateway interface?09:47
gongysh<amotoki> gongysh: I am now searching bugs. I saw a related bug to this.09:47
gongysh<amotoki> gongysh: in that case non-admin fails to set external gateway.09:47
gongysh<gongysh> amotoki: I remember that should work before.  I mean non-admin could list external networks before.09:47
gongysh<amotoki> gongysh: according to my experience we can see ext_net first but at some timing ext_net disappears from net-list.09:47
gongysh<gongysh> amotoki: will u file a bug or send it on maillist?09:47
gongysh<amotoki> gongysh: https://bugs.launchpad.net/neutron/+bug/125198209:47
gongysh<amotoki> gongysh: in addition https://bugs.launchpad.net/neutron/+bug/1254555 may be related.09:47
gongysh<amotoki> gongysh: are you seeing this issue now? The priority was changed to low a few weeks ago. If you see it frequently please update the bug priority.09:47
gongysh* jpich (~jpich@217.173.99.61) has joined #openstack-neutron09:48
gongysh<amotoki> gongysh: i haven't experienced this recently.09:48
gongysh<gongysh> amotoki: ok, I will have an explore09:48
gongysh<gongysh> amotoki: thanks09:48
gongysh<amotoki> gongysh: it is really strange behavior....09:48
salv-orlandoI think enikanorov was working on this. The reason is that context.is_admin uses a policy to validate what it means to be an admin. To do so it loads the policy engine. The policy engine has also a rule for allowing everyone to see external networks. This rule needs to evaluate the router:external field and verify it matches to True (as a boolean value); to do so it uses the converter which is specified in the RESOURCE_ATTRIBUTE_MAP. Ther09:51
salv-orlandoare some cases where this happens before all the extensions are loaded, and this would lead to skipping the conversion, with the result that the policy evaluation fails.09:51
salv-orlandoThis happens usually when a plugin does db operations on initialization09:52
salv-orlandothere are several ways to fix it, and one would be doing the conversion at every evaluation, which is a bit expensive but perhaps negligible.09:52
salv-orlandoI don't know if enikanorov is still actively working on this bug. You can ask him.09:53
salv-orlandogongysh^09:53
gongyshsalv-orlando: ok09:53
gongyshenikanorov_ ping09:54
*** rohit404 has quit IRC09:56
salv-orlandoneutron core devs: please have a look at https://review.openstack.org/#/c/58860/, needs to be re-approved only. It failed the gate and we verified the reason was not the patch itself. We also did a few rechecks to be sre.09:56
*** rohit404 has joined #openstack-neutron09:59
*** yfried is now known as yfried_lunch10:01
*** enikanorov has joined #openstack-neutron10:08
gongyshamotoki: ping10:18
*** jp_at_hp has joined #openstack-neutron10:20
*** dzyu_ has joined #openstack-neutron10:25
*** dzyu has quit IRC10:26
*** dzyu_ is now known as dzyu10:26
*** gongysh has quit IRC10:27
*** networkstatic has quit IRC10:29
*** dzyu has quit IRC10:36
*** rossella_s has joined #openstack-neutron10:38
*** gizmoguy has quit IRC10:39
*** gizmoguy has joined #openstack-neutron10:41
*** Jianyong has left #openstack-neutron10:50
*** krast has quit IRC10:51
openstackgerritberlin proposed a change to openstack/neutron: Add session persistence support for NVP advanced LBaaS  https://review.openstack.org/5914610:56
*** Abhishek_ has joined #openstack-neutron10:57
*** SushilKM__ has quit IRC10:59
*** rohit404 has quit IRC11:18
openstackgerritIsaku Yamahata proposed a change to openstack/neutron: Implement service vm framework(WIP):  https://review.openstack.org/5689211:20
*** djoreilly has quit IRC11:24
*** yamahata has quit IRC11:28
*** pcm_ has joined #openstack-neutron11:28
*** pcm_ has quit IRC11:29
*** pcm_ has joined #openstack-neutron11:30
*** yfried_lunch is now known as yfried11:30
*** SushilKM__ has joined #openstack-neutron11:34
*** rohit404 has joined #openstack-neutron11:40
*** pcm_ has quit IRC11:46
*** rkukura has quit IRC11:48
*** WackoRobie has quit IRC11:50
*** rpodolyaka has joined #openstack-neutron12:02
*** bashok has quit IRC12:06
*** yamahata has joined #openstack-neutron12:14
*** alex_klimov has quit IRC12:15
*** alex_klimov has joined #openstack-neutron12:16
*** jorisroovers has quit IRC12:20
*** WackoRobie has joined #openstack-neutron12:20
*** jroovers has joined #openstack-neutron12:21
*** rpodolyaka has left #openstack-neutron12:28
*** jroovers has quit IRC12:31
*** jroovers has joined #openstack-neutron12:31
openstackgerritSalvatore Orlando proposed a change to openstack/neutron: Improve handling of security group updates  https://review.openstack.org/6310012:41
*** SushilKM__ has quit IRC12:51
*** pcm_ has joined #openstack-neutron12:51
*** HenryG has joined #openstack-neutron13:00
*** clev has joined #openstack-neutron13:00
*** rossella_s has quit IRC13:14
*** aymenfrikha has joined #openstack-neutron13:26
*** Abhishek_ has quit IRC13:29
*** heyongli has joined #openstack-neutron13:31
*** aveiga has joined #openstack-neutron13:35
*** SushilKM__ has joined #openstack-neutron13:36
*** rossella_s has joined #openstack-neutron13:38
*** chandankumar_ has joined #openstack-neutron13:44
*** chandankumar_ has quit IRC13:44
openstackgerritAkihiro Motoki proposed a change to openstack/neutron: Return request-id in API response  https://review.openstack.org/5827013:49
*** WackoRobie has quit IRC13:53
*** WackoRobie has joined #openstack-neutron13:53
*** ygbo has quit IRC13:53
*** heyongli has quit IRC13:54
*** ygbo has joined #openstack-neutron13:55
*** markwash has joined #openstack-neutron13:58
*** yamahata has quit IRC13:58
*** yamahata has joined #openstack-neutron13:59
*** irenab_ has quit IRC14:01
*** jpich has quit IRC14:02
*** rkukura has joined #openstack-neutron14:04
yfriedpasquier-s: posted a comment on bug https://bugs.launchpad.net/tempest/+bug/126261314:05
yfriedpasquier-s: this is due to tenant_isolation issue. I already pushed a fix for this14:06
*** chandankumar has quit IRC14:06
*** peristeri has joined #openstack-neutron14:25
*** aymenfrikha has quit IRC14:28
*** julim has joined #openstack-neutron14:30
*** markmcclain has quit IRC14:30
*** jecarey has quit IRC14:31
*** mattymo has quit IRC14:32
*** mattymo has joined #openstack-neutron14:32
*** rkukura has quit IRC14:33
*** rkukura has joined #openstack-neutron14:34
*** banix has joined #openstack-neutron14:39
*** WackoRobie has quit IRC14:44
*** openstack has joined #openstack-neutron14:49
anteayakruskakli: thanks for considering it14:49
*** amritanshu_RnD has quit IRC14:50
*** yfried has quit IRC14:50
dkehnanteaya: didn't get around to reviewing https://review.openstack.org/#/c/62930/4, I see sdague's comment , which is the best way to handle the non-voting?14:51
anteayamarun: the third party jobs that are running elsewhere return a verified or unverified and a +1/-1 vote with logs to output from the test run14:53
anteayamarun: this gives the reviewers of the patch information and the freedom to merge or not merge as they see fit14:53
anteayamarun: the important part perhaps is in the naming of the test providing the comment so that folks can follow up to find out more if they have questions14:54
anteayamarun: if it becomes a problem of too much information then we can have a conversation when it happens14:55
anteayamarun: jeblair made the point that he has never heard a dev say "my patch has been tested too throughly"14:55
*** jecarey has joined #openstack-neutron14:55
anteayadkehn: thanks, I haven't seen that yet, just getting rolling, I will amend14:56
dkehnanteaya: no prob, me too on the rolling part14:56
dkehnanteaya: when you look at it , just curious which is the better way to handle it14:57
anteayadkehn: I have no personal opinion and if sdague only wants it running on check, I shall offer a patch that conveys such14:57
anteayaI just need to get jlibosva some information so he can keep working, check info is better than what we have now14:58
dkehnanteaya: thx, I'm figuring the are so many way to skin the cat, so to speak, but the cat must be skinned14:58
anteayathe cat must be skinned, aye14:58
dkehnanteaya: something worth raising with fungi14:58
*** markmcclain has joined #openstack-neutron15:01
*** julim has quit IRC15:03
*** clev has quit IRC15:04
*** carl_baldwin has joined #openstack-neutron15:04
anteayadkehn: nah, he will see the patch and my money is he will agree with sean and upvote it15:04
anteayaI just want it merged so we can get some logs on it15:05
EmilienMrkukura: hi, i face a problem with security group api when using ml2, could I ask you to have a look at https://bugs.launchpad.net/puppet-neutron/+bug/1262678 please ?15:06
*** julim has joined #openstack-neutron15:07
pasquier-syfried, thanks for the feedback15:09
rkukuraEmilienM: I'll get back to you momentarily.15:10
EmilienMrkukura: thank you15:11
*** mestery_ has joined #openstack-neutron15:12
openstackgerritCarl Baldwin proposed a change to openstack/neutron: Remove release_lease from the DHCP driver interface  https://review.openstack.org/5628515:12
*** WackoRobie has joined #openstack-neutron15:15
*** djschaap has joined #openstack-neutron15:15
EmilienMenikanorov: could you give me an update about SSL termination in LBaaS ? I'm not sure you spoke about that during the meeting today15:16
*** mestery has quit IRC15:16
*** otherwiseguy has joined #openstack-neutron15:16
enikanorovEmilienM: we did. evgenyf is working on the proposal and is going to post the code soon15:16
*** ashaikh has joined #openstack-neutron15:17
markmcclainenikanorov: evgenyf and I were just discussing it15:17
markmcclainI'm hoping he'll jump in here shortly15:17
enikanorovcool15:18
*** evgenyf has joined #openstack-neutron15:18
markmcclainso the problem we've got to tackle is how we protect the certs and passphrases15:19
evgenyfActually we need protection for private key only, or am I mistaken?15:19
markmcclainright private key15:20
* markmcclain needs more coffee15:20
EmilienMenikanorov: thank you for the update15:20
*** mestery has joined #openstack-neutron15:22
rkukuraEmilienM: I've been recommending setting firewall_driver=dummy_value_to_enable_security_groups_in_server in ml2_conf.ini, as long as the agent has the real firewall driver configured in an agent-specific file.15:22
rkukuraSee http://openstack.redhat.com/Modular_Layer_2_%28ML2%29_Plugin15:22
EmilienMrkukura: thank you, I have to update openstack manuals and puppet-neutron. I can see some people missing these informations.15:24
rkukuraEmilienM: I consider it a bug that the server-side of the security group RPC code uses the firewall_driver config variable to determine whether the API is enabled. I thought I had filed a bug, but couldn't find it.15:24
*** aymenfrikha has joined #openstack-neutron15:24
*** mestery_ has quit IRC15:25
*** aymenfrikha has quit IRC15:27
*** aymenfrikha1 has joined #openstack-neutron15:27
EmilienMrkukura: so I guess I have to configure both ml2 & OVS config files with firewall_driver (ml2 is for enable it and ovs with right driver) right ?15:30
rkukuraEmilienM: I think so. Not sure about other distros, but with RDO and RHOS, the init scripts for the L2 agents give them their own config files, not ml2_conf.ini.15:32
rkukuraEmilienM: So ovs_neutron_plugin.ini should have the real firewall driver, and ml2_conf.ini should have a dummy value to enable the API.15:34
EmilienMrkukura: far enough, thank you a lot Robert, I'm going to update documentation and puppet stuffs.15:35
*** aymenfrikha1 has quit IRC15:35
*** alex_klimov has quit IRC15:36
EmilienMand also in default config file i think.15:36
EmilienMrkukura: is it useful ? ^15:36
rkukuraEmilienM: I don't think firewall_driver needs to be set in neutron.conf, if that's what you mean.15:37
EmilienMrkukura: no i was wondering about ovs config file15:38
*** vkozhukalov has quit IRC15:40
rkukuraEmilienM: It does need to be set in ovs_neutron_plugin.ini if security groups are being used. Beware that there is work going on to implement an ovs-firewall-driver that uses flow rules rather than iptables rules, so in icehouse there may be a choice of which driver to use for openvswitch-agent.15:41
markmcclainevgenyf: so pickup the convo.. we need to make sure that the private keys are secured at all times15:43
markmcclainthat included when the keys are in transit between processes via RPC15:44
markmcclainone of my concerns in that the infrastructure we'll end up creating will overlap with the services of barbican15:45
markmcclainI'd rather contribute the resources necessary to barbican ready for incubation vs creating our own infrastructure15:45
evgenyfI'm not familiar with barbican, is it including RPC security?15:46
EmilienMrkukura: ack. thx again for precious informations.15:47
rkukuraEmilienM: No problem. Let me know if you've got any other questions, and I'll keep an eye out for the reviews.15:48
markmcclainevgenyf: no barbican is a secure store15:48
EmilienMrkukura: awesome, I appreciate your help15:48
markmcclaincurrently it is an ecosystem project that is trying for incubation15:48
markmcclainthe team is working on harmonizing the tech stack with the rest of OpenStack and growing their team15:48
markmcclainbarbican can provide a secure store15:49
evgenyfmarkmcclain:Yes, but still, with a key stored in a secure store, sending it to teh back-end system should be secured to and this is a second problem15:50
*** aymenfrikha has joined #openstack-neutron15:52
markmcclainwell at that point in time the reference can passed15:54
markmcclainand the backend driver can properly retrieve and prepare the request for the appliance15:54
*** rossella_s has quit IRC15:54
evgenyfWhat do you mean by "back-end driver"?15:57
markmcclainthe agent16:00
*** julim has quit IRC16:01
markmcclainenikanorov: any update on https://bugs.launchpad.net/neutron/+bug/125489016:02
evgenyfOk. And this is for the case when secure store is in place. And what about the case then key is not stored in secure place, but is trancient. Is there a way to make the driver-agent communication secured?16:02
*** julim has joined #openstack-neutron16:02
markmcclainI've been seeing this outside of the large ops tests16:02
markmcclainhttp://logstash.openstack.org/#eyJzZWFyY2giOiJcIlRpbWVkIG91dCB3YWl0aW5nIGZvciB0aGluZ1wiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiIxNzI4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxMzg3NDY4ODg5MTUxfQ==16:02
markmcclain85 hits in last 48hrs out of 256 for the last week16:02
*** SushilKM__ has quit IRC16:05
markmcclainevgenyf: right now oslo messaging does not support secure messages16:06
markmcclainthey're working on it16:06
markmcclainso we'd have to contribute to that effort16:07
evgenyfmarkmcclain: ic, anyhow the feature should wait for secured messaging or secured store, right?16:08
markmcclainI think so16:08
markmcclainbut I also think this is an area where we can work with those projects16:09
markmcclainand help further the development vs waiting16:09
markmcclainalso having a real problem to solve is a good use case of the projects16:10
evgenyfsure, I have to get familiar with those projects, thanks Mark16:11
*** amuller has quit IRC16:17
*** Mierdin has joined #openstack-neutron16:17
*** SushilKM__ has joined #openstack-neutron16:18
evgenyfmarkmcclain: Have a nice holidays16:26
*** dims has quit IRC16:26
markmcclainevgenyf: thanks!16:26
markmcclainevgenyf: if you got any questions feel free to ping the mailing list16:26
*** dims has joined #openstack-neutron16:30
*** HenryG_ has joined #openstack-neutron16:38
*** HenryG has quit IRC16:41
*** garyk1 has joined #openstack-neutron16:45
*** evgenyf has quit IRC16:45
*** dims_ has joined #openstack-neutron16:46
*** mlavalle has joined #openstack-neutron16:47
mlavallemtreinish: ping16:48
enikanorovmarkmcclain: not yet. I'm digging in logs. checked few failed test runs so far. Didn't find any specific suspicious errors on nova side. I think I'll have to add  more logging to nova16:51
markmcclainok16:51
*** dims has quit IRC16:52
*** mattymo has quit IRC16:52
*** peristeri has quit IRC16:52
*** garyk has quit IRC16:52
*** amotoki has quit IRC16:52
*** garyk1 has quit IRC16:55
*** mattymo has joined #openstack-neutron16:55
*** amotoki has joined #openstack-neutron16:55
*** SushilKM__ has quit IRC16:56
*** mattymo has quit IRC16:58
*** amotoki has quit IRC16:58
*** SushilKM__ has joined #openstack-neutron17:02
*** thedodd has joined #openstack-neutron17:03
*** peristeri has joined #openstack-neutron17:04
*** mattymo has joined #openstack-neutron17:04
*** amotoki has joined #openstack-neutron17:04
*** jorisroovers has joined #openstack-neutron17:06
*** clev has joined #openstack-neutron17:07
*** jroovers has quit IRC17:09
*** peristeri has quit IRC17:09
*** mattymo has quit IRC17:09
*** amotoki has quit IRC17:09
*** rohit404 has quit IRC17:11
*** amotoki has joined #openstack-neutron17:12
*** networkstatic has joined #openstack-neutron17:13
*** mattymo has joined #openstack-neutron17:15
*** jp_at_hp has quit IRC17:15
*** WackoRobie has quit IRC17:16
*** markmcclain has quit IRC17:17
anteaya<- afk for probably the remainder of the day17:19
*** peristeri has joined #openstack-neutron17:24
*** mlavalle has quit IRC17:25
*** marun has joined #openstack-neutron17:30
*** mlavalle has joined #openstack-neutron17:35
*** ygbo has quit IRC17:36
*** SushilKM__ has left #openstack-neutron17:39
*** vkozhukalov has joined #openstack-neutron17:46
*** dims_ is now known as dims17:50
marunsalv-orlando: ping18:02
*** garyk has joined #openstack-neutron18:03
salv-orlandohi marun18:03
marunhi salvatore18:03
marunI've been thinking about how to guarantee (eventual) state consistency between the dhcp agent and db...18:03
*** jorisroovers has quit IRC18:03
*** jlibosva1 has joined #openstack-neutron18:04
marunsalv-orlando: For the case of a single rpc server, using time-based sequencing might be ok.18:04
marunsalv-orlando: I'm less sure this scales, though.  Having a global sequence id (monotonically increasing, not necessarily contiguous) might be necessary.18:04
*** harlowja_away is now known as harlowja18:04
*** jlibosva2 has joined #openstack-neutron18:05
marunsalv-orlando: have you given this any thought?  I'm assuming the other agents have a similar requirement18:05
openstackgerritCarl Baldwin proposed a change to openstack/neutron: Use information from the dnsmasq hosts file to call dhcp_release  https://review.openstack.org/5626318:05
ijwmarun: I was looking at your discussions there18:05
*** jlibosva has quit IRC18:06
marunijw: and?18:06
ijwSeems like it wants a multicast for updates and, for emergencies like a restart, a call back to request a complete update.  The 'it's dead' spotting right now just doesn't seem to serve a purpose, because (a) we don't take corrective action and (b)18:06
ijw(b) we actually make things worse...18:07
*** jlibosva2 has quit IRC18:07
*** jlibosva1 has quit IRC18:08
ijwThe question I have (and this might be because I don't understand the semantics of AMQP) is, why do we stop sending messages when the DHCP server isn't responding?18:08
ijwI'm used to protocols where you send a message, it gets lost, and you fix it when you notice.18:08
marunijw: what do you mean by 'stop sending messages'?18:11
marunijw: and what do you mean by DHCP server?  Are you talking about the DHCP agent?  dnsmasq?  or...?18:11
*** insanida1e is now known as insanidade18:13
marunijw: the larger issue I'm grappling with is how to ensure18:14
marunijw: that full sync and incremental sync (triggered by notifications) don't step on one another18:14
marunijw: right now there are no guarantees of even eventual consistency, we're just hoping things work out18:15
*** networkstatic has quit IRC18:17
*** evgenyf has joined #openstack-neutron18:20
*** markmcclain has joined #openstack-neutron18:22
*** suresh12 has joined #openstack-neutron18:23
marunmarkmcclain: ping18:27
*** yfried has joined #openstack-neutron18:28
markmcclainmarun: pong18:28
marunmarkmcclain: Hi Mark18:28
*** fouxm has quit IRC18:28
markmcclainhey.. still in Asia or in US again?18:28
marunback in the us at last18:29
marunquell la jet-lag!18:29
*** fouxm has joined #openstack-neutron18:29
markmcclainjet lag isn't fun18:29
marunisrael was bad enough, but asia?18:29
*** fouxm has quit IRC18:30
maruni end up sleeping only 3-4 hours/night and then crashing in the afternoon18:30
markmcclainyeah I've fallen into that pattern before18:30
marunmarkmcclain: You travel way more than me, and after this time I don't think I can envy you anymore.  :)18:32
*** SumitNaiksatam has quit IRC18:32
marunmarkmcclain: so, a couple of questions...18:32
marunmarkmcclain: i'm seeing 3rd party jobs start to come online and spew review comments18:32
enikanorovyeah...18:33
marunmarkmcclain: i'm thinking this is going to be a real problem - automated comments obscuring peoples' comments - once we have all the 3rd party jobs running18:33
marunmarkmcclain: Tempest reviews are starting to see the same thing18:33
marunmarkmcclain: I don't think there's any easy solution, but I would suggest that cleaner gerrit integration is going to be necessary.18:34
marunmarkmcclain: that's all, I'll raise the same question in infra.18:34
marunmarkmcclain: the other thing, working with the dhcp agent has resulted in me being concerned that we can't guarantee even eventual consistency at present18:35
marunmarkmcclain: I'm not sure the other agents could be different18:35
marunmarkmcclain: at least with the dhcp agent, there is no way to determine if a notification is stale after a full sync has occured.18:35
markmcclainmarun: 2 mins.. got pulled into a local conf18:36
marunmarkmcclain: np18:36
markmcclainmarun: def agree that 3rd party testing integration is going to be something that work out as more systems come online18:38
markmcclainour project is the first to really add it a large scale18:39
markmcclainI'm happy to coordinate with -infra if we need to modify anything18:39
markmcclainmarun: as for DHCP18:40
markmcclainI think we have to assume that the notification is valid and when in doubt do a full sync18:40
markmcclaineven if it is horribly stale18:40
marunmarkmcclain: there is no guarantee that we don't get out of sync18:40
markmcclainthe other option is to coalesce all of the pending messages for a queue18:40
marunmarkmcclain: again, not useful18:40
markmcclainand say if we get X delta updates just convert to a full sync18:41
markmcclainthat way data isn't lost and we can process faster18:41
marunthere is no way at present to prevent stale notifications from introducing inconsistency in the local cache18:41
markmcclainwhy is converting teh deltas not useful?18:41
marunbecause if we get notifications during sync, we have no way to know whether they are stale18:42
markmcclainwe could move to the model where the notifications are interpreted as signals to update that cache in a more consistent way18:42
markmcclainthe messages have timestamps18:42
markmcclainso where the systems are using ntp18:42
marunmarkmcclain: that almost works18:43
markmcclainwe have the ability to determine the age of a message18:43
marunmarkmcclain: but the timestamps occur outside of transaction boundaries18:43
markmcclainif is an update we have the delta we have the ability to compare with the cache18:43
markmcclainif it agrees we can ignore the message right?18:43
marunmarkmcclain: that isn't an error case, though18:44
marunmarkmcclain: it's if they differ - who wins?18:44
markmcclainif they differ the tie goes to the db18:44
markmcclainand we init a full sync of that net18:44
marunmarkmcclain: that doesn't help18:44
marun*sigh*18:44
markmcclainwhy not.. the db is the owner of the record right?18:44
markmcclainI don't know of another source of truth18:44
*** clev has quit IRC18:45
marunthe db is the source of truth, yes18:45
marunit's how we access it that's the problem.18:45
marunwhen we do a sync, we get read isolation18:45
markmcclainright18:45
marunduring that transaction, changes can happen18:45
markmcclainright18:46
marunwe need to know which happened before (stale) and after (not stale) the read transaction started18:46
markmcclainbut those changes should generate a new notification18:46
markmcclainwhich should get processed after we've read the db18:46
markmcclainin a normal env18:46
markmcclainwe'll finish the sync18:46
markmcclainthe process that notificaiton18:46
markmcclainwhich will update the cache via applying a delta or full sync18:46
markmcclainit's when stuff goes wrong that you're concerned right?18:47
marunso we should get close if we make sure the timestamp is as close as possible to the start of the read transaction of the sync, and that notifications are as close as possible to the end of the write transaction18:47
markmcclainie lost notification18:47
marunyes, when things go wrong18:47
*** rohit404 has joined #openstack-neutron18:47
marunnot just lost notifications, though18:48
markmcclainok that was the original intent of the periodic full resync18:48
maruni don't think we should need periodic full resync18:48
markmcclainto ensure to proactively rebuild18:48
marunwe should resync when we detect a problem18:48
marun(which is what we actually do right now anyway)18:48
markmcclainshort of building a true presence tracking you ahve to have it18:48
marunwe don't have it18:49
*** evgenyf has quit IRC18:49
marunthe resync only happens when something goes wrong18:49
markmcclainyeah we do fall back when we're out of sync18:49
markmcclainbut it's not perfect18:49
marunwe're just not doing a great job of detecting errors18:49
markmcclainwhich is why there's the full resync janitor thread18:49
marunall it does is check whether a resync is required18:49
marunbut anyway.18:49
markmcclainoh the resync thread just used to set that flag to true18:50
markmcclainmust have been lost18:50
marunit's a mess right now18:50
markmcclainthe other approach is to further integrate DHCP resolution with out db18:50
maruni'm working on moving to a single event loop so that notification processing and resync is coordinated18:50
markmcclainbut dnsmasq does not allow us to do that18:50
markmcclainwe used to have a single loop18:50
marunhmm, without db?18:50
markmcclains/out/our/18:51
marunmarkmcclain: yeah, i don't know what happened.  your original intent has been lost, I think.18:51
markmcclainso we did single loop, but for largish networks that actually caused a backlog18:51
marun(re: single loop)18:51
markmcclaintalk with arosen on the perf problems they encountered18:52
marunmarkmcclain: no reason not to spin greenthreads per-network18:52
markmcclainI know they ran into same bad issues with it18:52
*** evgenyf has joined #openstack-neutron18:52
marunbut right now it's per-event18:52
marunevent -> notification18:52
markmcclainyeah18:52
markmcclainthink having a thread per network is interesting18:52
markmcclainmight be a good balance18:52
maruni think that could work18:53
marunso, I can work on timestamp-based discard.18:53
markmcclainok18:53
* markmcclain brb18:53
marunnp18:53
*** SumitNaiksatam has joined #openstack-neutron18:54
*** banix has quit IRC18:58
*** mlavalle has quit IRC19:01
*** markwash has quit IRC19:01
*** banix has joined #openstack-neutron19:03
*** evgenyf has quit IRC19:05
*** jroovers has joined #openstack-neutron19:09
markmcclainmarun: sorry back19:16
ijwmarun: hey19:18
ijwSorry, I was trying to suggest an approach like BGP - incremental updates to DHCP agents (and an understanding that actually one network may want multiple DHCP agents for redundancy) from the server, full resync if DHCP agent resets or if it sees a message go astray19:19
ijwBut I'm talking based on what I've seen go past in discussion, I haven't read the code (yet, but it's on my v6 joblist)19:20
lifelessijw: so neutron already has support for redundant active-active DHCP agents ;)19:22
ijwlifeless: I wasn't sure if it was in, I did think it was anticipated at least, I know we've talked about it19:23
*** WackoRobie has joined #openstack-neutron19:31
*** rossella_s has joined #openstack-neutron19:34
enikanorovmarkmcclain: i have an update for bug 125489019:35
markmcclainenikanorov: awesome.. what's the update?19:36
rossella_sbeagles: ping19:36
enikanorovapparently in each failed test run an instance got stuck with the task of mounting the fs19:36
enikanorovi don't see it related to neutron anyhow. but my experience there is very limited19:36
beaglesrossella_s: hi.. 1s on phone19:36
enikanorovif not to say none19:36
rossella_sbeagles: NP19:37
enikanorovall of network operations seem to succeed for the instance being spawned. but 'mount' cmd never returns19:37
markmcclaingood to know this information19:38
markmcclaincan update hte bug with your findings?19:38
enikanorovyes, I was going to add it. i'm currently trying to catch the failure with few additional log lines that i've added to nova.19:39
*** otherwiseguy has quit IRC19:40
markmcclainok.. also looks like dims added some stuff to the report too19:40
enikanorovindeed19:44
markmcclainenikanorov: I'm going to mark the bug as invalid for Neutron19:45
markmcclainbut do add your info so that the others working it will have your findings19:45
enikanorovI see DIMS has added pretty verbose explanation. I have nothing to add except that i confirm his findings.19:48
*** HenryG_ has quit IRC19:49
markmcclaintaht's useful data19:49
markmcclainthank you for digging into this19:49
dimsenikanorov, thanks for confirming19:49
marunmarkmcclain: ping19:53
markmcclainmarun: pong19:53
marunso, potential problem with time-based discard.19:53
maruni think there might be a race between getting the timestamp after commit of a write transaction (that sends a notification) and getting the timestamp before initiating a read transaction (for a sync).19:54
maruneven if the transactions are aligned such that the write transaction is committed before the read transaction, the timestamps could suggest that the write transaction didn't happen until after the read transaction began19:56
marunmarkmcclain: does that make sense?19:57
markmcclainit does19:58
markmcclainbut in that case the we would read again would we not?19:58
marunmarkmcclain: why?19:58
marunmarkmcclain: i think the result would be processing a stale notification for the write transaction19:59
*** networkstatic has joined #openstack-neutron19:59
marunmarkmcclain: i'm actually fuzzy about the implications, can you think of a case where processing a stale notification would corrupt local state?20:00
markmcclainthere could be a gap between finalizing the transaction and reading the system tiem20:00
marunmarkmcclain: yes, that's the nature of the problem20:00
marunmarkmcclain: and presumably why systems that need to coordinate on db state use sequence ids of some sort20:01
marunand a gap between reading the system time and starting the read transaction20:01
beaglesrossella_s: hi20:02
rossella_sbeagles: hi20:02
beaglesrossella_s: how are you?20:02
*** networkstatic has quit IRC20:03
rossella_sBetter, almost ok. Thanks20:03
markmcclainmarun: might ahve to consider payload in addtion to timestamp determine if something is stale20:03
*** networkstatic has joined #openstack-neutron20:03
rossella_sI've read the log of your meeting on Tuesday20:03
marunmarkmcclain: it's not really an issue when we only have a single rpc-processing server.  but we're going to need multi-process if not multi-host to scale20:03
rossella_sbeagles: are you meeting again today at 22 UTC, right?20:04
marunmarkmcclain: uh, that sounds like guesswork20:04
beaglesrossella_s: not today actually, most of us weren't available, but we are tomorrow20:04
markmcclainmarun: we can already run dhcp on multiple network hosts20:05
marunmarkmcclain: i dont' mean the agent20:05
marunmarkmcclain: i mean the server20:05
*** carlp has joined #openstack-neutron20:05
rossella_sbeagles: ok, better for me actually. Let's sync tomorrow, is it at 22 UTC?20:05
markmcclainmarun: which server? dnsmasq or neutron?20:05
marunmarkmcclain: the timing race is only a problem if we have more than a single process processing rpc20:05
marunmarkmcclain: neutron20:06
rossella_sbeagles: where are you based? What's your time zone?20:06
beaglesrossella_s: yes.. I suggested that maybe if that time was problematic for anyone we could try a spontaneous sync up earlier20:06
carlpGreetings! I'm trying to figure out how to use the vlan type with ML2. I have the config in place so that physnet1 maps to VLANs 1-100. I'm trying to figure out the neutron invocation which will let me create that provider network and attach a physical NIC. Can someone help me out?20:06
marunmarkmcclain: if we only have a single rpc server, then only one thing runs at a time and there is no possibility of a race20:06
beaglesrossella_s: I am in Newfoundland so it is UTC -3:3020:06
marunmarkmcclain: but if we have multiple processes (on the same host or distributed), then a race if possible20:07
markmcclainmulti-threaded API server already exists20:07
beaglesrossella_s: how about you?20:07
markmcclainmarun: so the transactions could commit at different times already20:07
marunmarkmcclain: not real threads20:07
marunmarkmcclain: oh, crap20:07
rossella_sbeagles: I am in Spain usually, in Italy right now. UTC +120:07
marunmarkmcclain: sorry to be dumb.  so, yeah.  we have a potential race condition, period.20:08
*** djschaap has quit IRC20:08
markmcclainmarun: yes we do20:08
marunmarkmcclain: so, sequence ids?20:08
markmcclainexcept what generates those?20:09
rossella_sbeagles: let's try a spontaneous sync up earlier then.20:09
beaglesrossella_s: cool.. so it might make sense to try and sync up a little earlier20:09
beaglesha20:09
beaglesrossella_s: you beat me to it :)20:09
marunmarkmcclain: well, I'm sure there are distributed systems people that could answer that better than i20:09
marunmarkmcclain: my naive approach might be db-based (since that's the point of synchronization) via an update trigger20:09
markmcclainmarun: that's why I think we have process stale notifications20:09
rossella_sbeagles: :)20:09
markmcclainmarun: and assume that we should re-sync state20:10
marunmarkmcclain: 'spray-and-pray'20:10
beaglesmarun markmcclain you guys have tweaked my attention20:10
markmcclainmarun: not the greatest solution for now20:10
beaglesis this something that is summarizable in a one liner?20:11
marunmarkmcclain: there is no guarantee that a resync fixes the problem20:11
* beagles scrolls20:11
markmcclainbeagles: basically we're discussing how to ensure the DHCP network state is consistent with the db state20:11
*** networkstatic has quit IRC20:12
markmcclainthere are a few races in the process that make it possible for the DHCP cached state to not reflect the proper logical state20:12
marunbeagles: state synchronization between server and agent -> notifications can't always guarantee consistency, but when a full sync is triggered, there is no way at present to determine if a subsequently seen notification is stale20:12
*** Abhishek has joined #openstack-neutron20:14
*** banix has quit IRC20:14
marunmarkmcclain: My takeaway from this is that an rdms is a poor choice for coordinating a distributed system.20:15
marunrdms -> rdbms20:15
markmcclainrelational databases and eventual consistency don't always play well20:16
*** yfried1 has joined #openstack-neutron20:16
*** networkstatic has joined #openstack-neutron20:16
markmcclainthe crazy thing about the whole thing is that we only care that the are in sync a really tiny moment in time20:16
marunmarkmcclain: ok, so I'll give some thought to what are the implications of processing stale notifications and see if we can work around20:16
markmcclainwe only want them to be insync when the DHCPDISCOVER is processed20:17
markmcclainoops DHCPOFFER20:17
markmcclainotherwise the sync state does not matter20:17
ijwmarkmclain: It's a timing thing - we need to be ready for it, really20:18
*** yfried has quit IRC20:18
marunmarkmcclain: sure, it's all super simple ;)20:18
markmcclainijw: being ready does help make things run faster20:18
markmcclaindnsmasq is not the only solution for providing DHCP services20:18
beaglesmemcached?20:18
markmcclainso it might make sense to consider alternatives20:19
marunmarkmcclain: what are you thinking of?20:19
markmcclainbeagles: memcahed presents a problem because dnsmasq reads the data from it's configuration files20:19
marunI'm not sure the inherent complexity of state synchronization can really be done away with20:19
*** networkstatic has quit IRC20:19
*** networkstatic has joined #openstack-neutron20:20
beaglesmarkmcclain: oh.. I thought we were poking it with data, but I guess the problem remains that there needs to be an actor to update it20:21
markmcclainmarun: ISC DHCP is another option that has been tossed around for years but no one has explored it20:21
marunmarkmcclain: although…. if we stored the complete dhcp state in memcache (or something like it), regenerated it on every change, and sent notifications on change...20:21
markmcclainduring Folsom there was a little talk of it as an alternative20:22
*** networkstatic has quit IRC20:22
*** networks_ has joined #openstack-neutron20:22
*** networks_ is now known as networkstatic20:22
markmcclainbeagles: correct20:22
marunmarkmcclain: would using ISC remove the burden of state synchronization?20:22
markmcclainpossibly.. the ISC does have an API20:28
markmcclainnot sure if we're trading one problem for another20:28
ijwTwo ways to work this - we pass the state over, or DHCP calls back for it20:30
markmcclainijw: correct20:30
ijwIf we pass it over we need to revisit that sync protocol.20:30
marunmarkmcclain: i think there is less chance to get out of sync if we have an incremental api20:31
*** networkstatic has quit IRC20:31
markmcclainincremental APIs can easily get out of sync20:31
markmcclainespecially in systems where were messages can be lost20:31
ijwmarkmcclain: they do, but they're also a solved problem20:32
markmcclainijw: right20:32
*** otherwiseguy has joined #openstack-neutron20:32
ijwYou always need the 'help I lost a message' and 'help I need a full table' options20:32
markmcclainI think long term a callback mech is really the road to go down20:32
marunmarkmcclain: do tell?20:32
ijwYeah, but then I'll turn this around - if we can't get it right here we have the same problem with everything else we're keeping in sync (or not)20:32
markmcclainijw: DHCP is kind of special child because we're basically replicating the entire DB20:33
markmcclainthe other sub children of the prob only replicate smaller parts of the db20:34
ijwmarkmcclain: depends on how you view it - with OVS you're putting together a subset of the l2 table and then syncing it to the agent; it's the same issue, and what happens there if you lose a message?20:34
marunmarkmcclain: I think you're right that stale notifications are probably not so bad for the race in question.  the incidence should be low enough to only be a single add/update/delete for a given network, and we can just filter it out.20:35
markmcclainijw: the OVS l2 agent has it's troubles too20:35
marunijw: losing a message isn't really the problem20:36
ijwmarkmcclain: Case in point.  If this is a recurring problem, can we solve this once and for everything?20:36
markmcclainijw:  something I'm working on20:36
marunljw: failure on either end will mean a restart, and a sync will ensure the message is not lost20:36
marunnot lost -> doesn't matter20:37
ijwmarun: If I understand your comments in the bug, the issue is that we stop sending messages when a DHCP agent appears to die.20:37
markmcclaininternally we've been looking at multi-process, multi-threaded approach20:37
marunljw: there is a patch under review that fixes that20:37
markmcclainit also coalesces events to be more intelligent about how it asks the db questions when updating20:38
*** jecarey has quit IRC20:38
*** rohit404 has quit IRC20:38
markmcclainstill working making it work in proper HA mode20:38
marunmarkmcclain: that helps things scale, but I don't think that addresses the issue of state synchronization20:39
*** rossella_s has quit IRC20:39
maruni.e reliability20:39
markmcclainmarun: actually it does20:39
ijwOK, so could we have an incrementing state version?  That's an old favourite for making sure we know whether a message is relevant or not20:39
marunmarkmcclain: do tell?20:39
markmcclainbecause the event processing and syncs are handled in a predictable order20:39
marunmarkmcclain: how do you coordinate them?20:39
markmcclainat worst it might sync an extra time or two if message is that stale20:39
marunmarkmcclain: How do you detect that an extra sync is necessary?20:40
markmcclainbased on the pending messages for a network20:40
marunmarkmcclain: or rather, how are you discarding stale notifications?20:40
*** networkstatic has joined #openstack-neutron20:41
markmcclainwe look at the queue for network20:41
marunmarkmcclain: uh20:41
markmcclainand actually process the messages mostly in order20:41
markmcclainbut occasionally process them out of order20:41
markmcclainbecause you can infer that certain ones will fail20:41
markmcclainor are redundant20:42
marunmarkmcclain: what a headache20:42
markmcclainwe're planning to share for more feedback once we work out the HA side of it20:43
marunmarkmcclain: i'm having trouble sorting out if the complexity we're talking about is inherent or accidental20:43
marunmarkmcclain: so is this modifications to neutron?20:43
markmcclainit's drop in replacement20:43
markmcclainfor the agent20:43
marunuh20:43
marunand you're only going to show it at the end?20:43
markmcclainwell we want something works :)20:44
marunthat seems problematic, especially coming from the ptl20:44
marunif 3rd parties try to do that, we smack them20:44
markmcclainnot going to drop something at the end20:44
markmcclainbecause it is a PoC that solves on particular use case20:44
*** mlavalle has joined #openstack-neutron20:44
maruni get it - its good for dreamhost20:44
*** garyk has quit IRC20:45
marunbut giving the project a drop-in replacement for something significant is problematic from a support/maintenance perspective, as i'm sure you're away20:45
marunaware20:45
markmcclainwe are but is supports a system which is unique to us20:45
*** networkstatic has quit IRC20:45
maruni mean, we ask for blueprints and designs for significant work to educate and engage stakeholders20:46
markmcclainso there will always be bits that where we have to tie to legacy20:46
*** garyk has joined #openstack-neutron20:46
marunI get why you're doing it - a business case needs solving.20:46
markmcclainif it proves workable then it also could serve as a blueprint to solve the more general case20:47
marunI'm not sure the approach is consistent with how Neutron is supposed to run, though.20:47
marunIf it were anyone but you, I think it would be a big problem.20:47
markmcclainthe interesting thing about this particular solution is that it increases complexity in a few places20:47
markmcclainand you know how I generally feel about doing that :)20:48
marunFair enough20:48
markmcclaindebugging the thing is not always the easiest either20:48
marunI still think doing this in the open would be preferable, though, for all the same reasons I've yelled at other contributors for taking a similar approach.20:48
markmcclainyeah we're close to opening it20:49
marunHow soon?20:49
markmcclainit's the legacy ties that prevent20:49
markmcclainI'm hoping before the end of the year20:49
ijwmarkmcclain: I don't suppose you have a design you could share rather than code?  Firstly it would be easier to critique and secondly (and given your IP issues) it might be more useful20:50
marunWe still need to support havana and a drop-in replacement probably won't be backportable, and if there are lessons to be learned from this work in maintaining the existing stuff it would be good to see it sooner than later.20:50
marunbtw, I'm going to be completely offline dec 25->jan 520:50
* ijw is completely offline now.20:50
markmcclainijw: no designs yet20:51
*** jroovers has quit IRC20:51
*** vkozhukalov has quit IRC20:51
markmcclainthis is somethign we've been wanting to talk about as you know we prefer to work in the open20:51
markmcclainjust have to get all fo the proper signoffs20:51
ijwI'm trying to picture what you've said, actually, haven't really got it yet20:52
markmcclainit's very similar to marun's threaded approach20:53
markmcclain*event-loop threaded20:53
markmcclainbut is also multiprocess because well eventlet like to deadlock alot20:53
* ijw could wish we started with Twisted20:54
markmcclainijw: developing with concurrency in mind from the beginning is much better than the current way we do it20:54
*** networkstatic has joined #openstack-neutron20:55
maruni'm glad we don't have twisted20:55
ijwIndeed, but I'm less worried about concurrency in a process and more worried about how we deal with all the distributed system failures, cos they're the ones that generally bite20:56
marunbut i kinda wish we didn't have eventlet20:56
ijwmarun: you see, that's your problem, you don't like to live dangerously20:56
ijwnode.js ftw20:56
markmcclainmarun: we can't get rid of eventlet until oslo.messaging supports alternative concurrency libs20:56
* beagles bites tongue20:56
ijwI have never uysed node.js, I'd like to point out.  On the other hand, I have programmed hard realtime systems so I'm a proper grownup when it comes to events and tasks20:57
beagles:)20:57
* marun goes to work on oslo.messaging20:57
ijwMay God have mercy on your soul20:58
*** pcm_ has quit IRC20:58
marunthe fact that oslo.messaging's default rpc dispatcher is so brain-dead doesn't really bode well20:58
beaglesoh god now you are just taunting me20:58
marunor maybe it simply wasn't intended to support state synchronization?20:58
marun(though what else would we need it for?)20:58
ijwmarun: everything in a distributed system can be reduced to a state sync problem, I would argue20:59
marunijw: that's my feeling too20:59
marunjust like ai is search, distributed is sync20:59
ijwI think the original issue is that Openstack was designed with a 'messages always arrive' mentality - Nova used to be awful in Essex and Folsom, Neutron started later and has got to that point20:59
beaglesthe evolution seems to be along the lines: this always works, this sometimes doesn't work so we need to retry, then to oh shit when we retry we don't know if the first thing actually happened, HELP21:04
beaglesthen finally you realize you have to make your data interchange pessimistic but simple and not load everything down with extra chattiness and complexity21:04
beaglessome folks go the latter route.. and we never see them again21:05
*** networkstatic has quit IRC21:05
marunwait, isn't that us? :p21:06
beaglesso am I to take it that eventlet pools and work queues are on a few people's menus?21:06
beagleshehe.. we aren't quite terminal yet I think21:06
beaglesby menu, I mean approaches to tackling  some of the issues?21:07
* beagles twiddles thumbs21:08
beaglesmarkmcclain: wake up  ^^^^21:09
markmcclainsorry was tracking the nova meeting :)21:10
marunbeagles: we're approaching it by way of trying to fix races21:10
beagles:)21:10
marunbeagles: or deadlocks, as the case may be21:10
beaglesI've got it scrolling in another window21:11
markmcclainyeah I don't like eventlet for a lot of reasons21:11
markmcclainand would love to move away from it21:11
markmcclaineventlet also has some Py3 considerations too21:11
* beagles nods at marun21:15
beaglesI'm trying to think of a way to put what I'm thinking as succinctly as possible.21:21
marunthat sounds like it could be good21:24
beaglesThe word spawn appears 68 times in neutron - filtering out the tests and openstack directroy, some is just delegation to another method with spawn in and some are third party plugins...21:25
beaglesso.. not all 68 are particularly relevant...21:25
beaglesgreenthreads or no, spawn asynchronous tasks without proper organization of the work they are performing is a recipe for disaster...21:26
beaglesthe dhcp thing I pointed out some weeks ago is an example...21:27
beaglesI wonder if there is value in picking through each place and imagining ways it could go horribly wrong21:28
beagles(as opposed to me simply asserting that there is definitely stuff going wrong in most of those places ;))21:29
marunthere might be value, but most of the problems are actually db-related21:30
beaglesdamn, I shoud've filtered out the async_process cuz that word is all over that thing21:30
maruni worked pretty hard to make sure it's sane, and anyway it's impact is just the l2 agent21:31
beaglesdhcp you mean? or the async_process thing?21:31
marunasync_process21:35
beaglesah okay.. I'm assuming it is cool :)21:35
beaglesI kind of figured what it does wouldn't be that dangerous21:36
dkehnmarkmcclain: https://review.openstack.org/#/c/59858/ please21:37
beaglesare the db contention issues the db-specific kind like table or page level locks or are more mundane like locking things in different orders21:37
* beagles wanders off an maybe looks it up in the existing info like he should21:39
maruntbd21:40
*** aymenfrikha has quit IRC21:40
marunboot instances at a high enough rate and nova starts timing out.  then investigate why21:40
*** suresh12 has quit IRC21:44
*** suresh12 has joined #openstack-neutron21:44
*** suresh12 has quit IRC21:49
*** roeyc has joined #openstack-neutron21:51
*** hichihara has joined #openstack-neutron21:52
*** rkukura has quit IRC21:56
markmcclaindkehn: approved21:57
dkehnmarkmcclain: thx tons21:57
*** clev has joined #openstack-neutron21:59
*** HenryG has joined #openstack-neutron22:07
*** pcm_ has joined #openstack-neutron22:07
*** pcm_ has quit IRC22:09
*** julim has quit IRC22:09
*** pcm_ has joined #openstack-neutron22:09
ijwOK, we may actually have RAs this century22:10
*** WackoRobie has quit IRC22:10
ijwmarun: how far have you explored the boot timeouts?22:26
marunljw: ?22:27
*** roeyc has quit IRC22:27
ijwhigh rate startup boot timeouts22:29
ijwAlso, seriously mate, that's an 'i'22:29
*** hichihara has left #openstack-neutron22:30
*** yamahata has quit IRC22:37
*** nati_ueno has joined #openstack-neutron22:38
*** carlp has quit IRC22:46
openstackgerritA change was merged to openstack/neutron: Remove start index 0 in range()  https://review.openstack.org/6110022:46
*** safchain has quit IRC22:48
*** clev has quit IRC22:59
jog0new critical bug https://bugs.launchpad.net/neutron/+bug/126290623:03
openstackgerritSalvatore Orlando proposed a change to openstack/neutron: Improve handling of security group updates  https://review.openstack.org/6310023:04
jog0markmcclain: ^23:05
*** thedodd has quit IRC23:06
markmcclainjog0: looking23:07
*** clev has joined #openstack-neutron23:10
*** harlowja is now known as harlowja_away23:12
*** b3nt_pin has joined #openstack-neutron23:13
jog0markmcclain: going to talk about it in -qa23:13
openstackgerritEmilien Macchi proposed a change to openstack/neutron: Configure security group when using ML2 plugin  https://review.openstack.org/6324023:14
*** beagles has quit IRC23:14
*** b3nt_pin is now known as beagles23:14
*** Abhishek has quit IRC23:15
*** yfried1 has quit IRC23:17
openstackgerritA change was merged to openstack/neutron: Do not trigger agent notification if bindings do not change  https://review.openstack.org/5886023:18
*** peristeri has quit IRC23:18
*** beagles has quit IRC23:19
openstackgerritdekehn proposed a change to openstack/python-neutronclient: Adds delete of extra-dhcp-opt to the client  https://review.openstack.org/4916623:26
*** b3nt_pin has joined #openstack-neutron23:26
*** otherwiseguy has quit IRC23:27
*** b3nt_pin is now known as beagles23:33
*** gdubreui has joined #openstack-neutron23:34
*** nati_uen_ has joined #openstack-neutron23:34
*** nati_uen_ has quit IRC23:34
*** nati_uen_ has joined #openstack-neutron23:35
*** nati_ueno has quit IRC23:37
*** clev has quit IRC23:38
*** networkstatic has joined #openstack-neutron23:39
*** networkstatic has quit IRC23:43
*** harlowja_away is now known as harlowja23:57
*** mlavalle has quit IRC23:58
*** yamahata has joined #openstack-neutron23:59

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