Tuesday, 2016-08-16

*** diogogmt has joined #openstack-fwaas00:11
*** vishwanathj has quit IRC01:44
*** yushiro has joined #openstack-fwaas02:08
*** chandanc_ has joined #openstack-fwaas02:49
chandanc_Hello Sridar, Nate and Margaret, Sorry I didnot realize that my presence was required on IRC y'day. Please let me know if we need to sync-up02:51
SridarKchandanc_: no worries02:57
SridarKi know Mon was a holiday locally02:57
SridarKwe just wanted to sync up quickly02:57
chandanc_Hey SridarK, I read through the logs y'day night02:57
chandanc_ya02:57
chandanc_is there anything to be discussed now ? I saw Margaret has the patch in02:58
SridarKchandanc_: mfranc213: pushed up some UT as well, anyways u saw her email also02:58
chandanc_ya02:58
chandanc_I think there is no need to be worried about my changes02:58
chandanc_i will sync with her if more changes are to be pushed02:59
SridarKchandanc_: not really, i got stuck in one set of tests - something funny with tenant_id being driven on the db patch from UT02:59
SridarKso i am debugging that02:59
chandanc_ok sure02:59
SridarKi was going to sync with yushiro on that02:59
SridarKnothing specific else - i will be around except for dinner at some point - so if there is something we can sync03:00
chandanc_I will be in meeting next 2 hours, but send me a mail if need be03:00
SridarKchandanc_: ok thx03:00
SridarKyushiro: ping03:00
yushiroSridarK, poing03:00
yushiropong. hahaha03:00
SridarKyushiro: :-)03:00
chandanc_I have a small suggestion for L3 patch but nothing major, responding to Margaret's mail03:01
SridarKyushiro: will u have some time to discuss the tenant_id stuff03:01
SridarKchandanc_: ok03:01
yushiroSridarK, oh, I have lunch time now, so, I can free at 13:00 JST(1 hour later)03:02
SridarKyushiro: yes that will work03:03
SridarKyushiro: ok thx03:03
yushiroSridarK, OK. currently, I'm summarizing e-mail about tenant_id and policy.json.  Let me discuss about that later.03:03
SridarKyushiro: ok03:04
yushiroI'll go for lunch. bye.03:04
*** yushiro is now known as yushiro_lunch_ti03:04
*** mickeys has quit IRC03:08
*** mickeys has joined #openstack-fwaas03:09
*** mickeys has quit IRC03:10
*** mickeys has joined #openstack-fwaas03:10
*** chandanc_ has quit IRC03:16
*** chandanc_ has joined #openstack-fwaas03:21
*** vishwanathj has joined #openstack-fwaas03:25
*** yushiro_lunch_ti has quit IRC03:29
*** diogogmt has quit IRC03:34
*** vishwanathj has quit IRC03:54
*** yushiro has joined #openstack-fwaas04:01
yushiroSridarK, Hi, I'm online now :-)04:03
yushiroand thanks for your e-mail.04:04
SridarKyushiro: hi04:08
SridarKyushiro: yes i hope i was clear in explaining the issue04:08
*** chandanc_ has quit IRC04:09
SridarKit was quite strance to see that the context is not set in the CR method for the resource04:09
SridarK*strange04:09
*** chandanc_ has joined #openstack-fwaas04:09
yushiroSridarK, Yes, that's strange about your result of 'context'.04:11
SridarKyushiro: i think i somehow there is some error in how the context is getting set for the UT04:12
yushiroI see.  SridarK , please let me confirm.  you defined ctx = context.Context('not_admin', 'tenant1'), didn't you?04:14
SridarKyushiro: yes, let me double check04:15
SridarKyushiro: yes that is for the firewall group04:16
SridarKi see the issue in step 1 to create the policy itself04:17
*** vishwanathj has joined #openstack-fwaas04:17
yushiroSridarK, OK. I see...  Here is my environment result.  I think it same as you. http://paste.openstack.org/show/558036/04:20
SridarKyushiro: ok, there is no tenant_id or project_id04:23
SridarKyushiro: http://paste.openstack.org/show/558038/04:28
yushiroSridarK, yes... If correct, we can get both 'tenant_id' and 'project_id'. https://github.com/openstack/neutron/blob/master/neutron/context.py#L7004:28
SridarKby breaking in the test file - it is quite the same i see as well04:28
yushiroSridarK, Yes, it's same.04:29
SridarKi think for the resources, it is fine04:30
SridarKbut now when a firewall_policy CR comes along - shouldnt i be seeing the tenant_id/project_id - reflecting this tenant04:31
SridarKyushiro: in ur env, can u put in a breakpoint in neutron_fwaas/db/firewall/v2/firewall_db_v2.py:42004:32
SridarKif u have picked the latest rev of the patch04:33
SridarKand look a the context04:33
yushiroSridarK, Sure. just a moment, please.04:33
SridarKok no worries04:33
*** chandanc__ has joined #openstack-fwaas04:34
*** chandanc_ has quit IRC04:35
yushiroSridarK, Sorry for late. I set 'pdb.set_trace()' in L.420.04:57
SridarKyushiro: ok04:57
SridarKnp thx for looking04:57
yushiro(Pdb) p context.tenant_id05:01
yushiro     None05:01
SridarKah yes05:08
SridarKnow isnt this a problem05:08
*** chandanc__ has quit IRC05:10
yushiroSridarK, I think argument 'context=ctx' is missing at new_create_request05:12
yushiro'_create_firewall_policy' at test_firewall_db_v2.py, please add following codes and try it:05:12
yushiroctx = kwargs.get('context', None)05:13
yushirofw_policy_req = self.new_create_request(FWP, data, fmt, context=ctx)05:13
yushirooh, sorry.  s/FWP/'firewall_policy'05:13
SridarKyushiro: hmm ok05:13
SridarKactually the fwg does have this in the new_create ...05:16
SridarKbut let me try this05:17
yushiroSridarK, sorry. I was wrong.  there is no change.05:23
SridarKyushiro: yes somehow for fwg - i was passing a context - then i get a bad req05:23
*** chandanc__ has joined #openstack-fwaas05:39
yushiroSridarK, If we don't specify context in new_create_request, strange? context will be set.06:19
yushirotenant_id : None,  is_admin: True,  like that.06:19
yushiroSo, firewall_policy passes populate_tenant_id at api/v2/attributres.py06:20
yushiroHowever, in case of POST firewall_group, we specify context which is not admin, then this request is validated in populate_tenant_id.06:21
yushiroSridarK, I passed POST firewallgroup.  However, still exist 'tenant_id' issue.06:39
*** SarathMekala has joined #openstack-fwaas07:05
SridarKyushiro: ok07:25
SridarKyushiro: many thx - i think i am very tired - so will go sleep some. Perhaps if u find out something more - pls send me an email. I will resume in our morning time07:28
yushiroSridarK, Yes.  please take care of yourself and good night.07:29
SridarKyushiro: thx and have a great day07:29
*** mickeys has quit IRC08:17
*** mickeys has joined #openstack-fwaas08:17
*** mickeys has quit IRC08:22
*** yamamoto has quit IRC08:44
*** yushiro has quit IRC08:45
*** yamamoto has joined #openstack-fwaas09:31
*** yamamoto has quit IRC09:41
*** yamamoto has joined #openstack-fwaas09:46
*** yamamoto has quit IRC09:46
*** yamamoto has joined #openstack-fwaas09:48
*** yamamoto has quit IRC10:25
*** chandanc__ has quit IRC11:00
*** yamamoto has joined #openstack-fwaas11:03
*** SarathMekala has quit IRC11:10
*** yamamoto has quit IRC12:33
*** yamamoto has joined #openstack-fwaas12:39
*** yamamoto has quit IRC12:43
*** mickeys has joined #openstack-fwaas13:03
*** yamamoto has joined #openstack-fwaas13:07
*** yamamoto has quit IRC13:07
*** mickeys has quit IRC13:07
*** diogogmt has joined #openstack-fwaas13:33
*** diogogmt has quit IRC13:42
*** yamamoto has joined #openstack-fwaas14:07
*** chandanc_ has joined #openstack-fwaas14:09
*** yamamoto has quit IRC14:13
*** chandanc_ has quit IRC14:20
*** chandanc_ has joined #openstack-fwaas14:20
*** diogogmt has joined #openstack-fwaas14:37
*** mickeys has joined #openstack-fwaas14:42
SridarKnjohnston: ping15:40
njohnstonSridarK: Good morning15:40
SridarKnjohnston: GM15:40
SridarKquick update: still on the UT issue - seems like it could be a project_id thing - so testing something along those lines15:41
SridarKwill let u know as soon as i find something15:41
SridarKif this is done - we can try to quickly wrap up the db patch today15:42
njohnstonSridarK: Thanks, I think that would be perfect.15:42
SridarKnjohnston: ok cool - will continue on this at some point will need to drive in to work and will be online again15:43
njohnstonSridarK: We need to merge https://review.openstack.org/#/c/264489/ before the DB patch though, yes?15:43
SridarKnjohnston: yes - this may have impact there too15:43
SridarKwill know shortly, on this issue - every time i see a light at the end of a tunnel - turns out to be an oncoming locomotive. :-)15:45
chandanc_:)15:45
njohnstonWhat can we do to get 264489 merged today?  Is there anything I can help with?  I am posting my rationale for FIREWALL_PREFIX now.15:45
SridarKnjohnston: once i know, it will need a change - once we close on that - we shd be good15:46
*** chandanc_ is now known as chandanc_AFK_1hr15:48
njohnstonOK, comment on 264489 posted, we need to alter 311159 instead.15:50
SridarKnjohnston: ok - i have been running the UT with /fwaas as the PREFIX15:54
SridarKso i think we are good15:55
njohnstonwithout the "v2.0"?15:55
njohnstonCool, as long as it works for you - the proof is in the pussing, as they say!15:55
njohnstonpudding15:55
SridarKnjohnston: yes :-) i think that v2.0 is the endpoint URL16:00
njohnstonSo where is the configuration that determines if FWaaS is operating in v1 or v2 mode?  Or, are both v1 and v2 calls always supported at the same time, but they will have different methods, with the v2 methods having "_v2" appended?16:01
njohnstonI am reflecting on Chandan's comment https://review.openstack.org/#/c/355755/1/etc/policy.json@161 and I wanted to make sure I wasn't moving forward based on preconceptions16:01
SridarKnjohnston: the plugin will set that16:02
SridarKor rather 1) based on which plugin is pointed to by neutron.conf16:03
SridarK2) which extension(s) are loaded by this plugin16:03
SridarKin the plugin patch : https://review.openstack.org/#/c/267046/3/neutron_fwaas/services/firewall/fwaas_plugin_v2.py L#8916:04
SridarKsupported_extension_aliases = ["fwaas_v2"]16:05
njohnstonAnd even though that is an array, there will only ever be one value?16:06
*** chandanc_AFK_1hr has quit IRC16:07
*** chandanc_AFK_1hr has joined #openstack-fwaas16:08
njohnstonHow can one inspect the API to determine if FWaaS v1 or v2 is being used?16:08
SridarKit will be localhost:9696/v2.0/fw/<resoucename> for v116:09
SridarKit will be localhost:9696/v2.0/fwaas/<resourcename for v216:10
SridarKand u would use appropriately based on which plugin is loaded16:10
njohnstonNo, I mean is there an API call that you can call and get "{ 'fwaas_version': '2.0' }" back or something like that, so you could know in advance whether you should call /fw/ or /fwaas/16:11
SridarKi guess it will be a mapping based on which plugin is loaded16:13
SridarKu can check which ext are loaded16:14
njohnstonYes, but in a public cloud setting if you're a customer you don't have the ability to look at what plugin is loaded.  But I guess that is a teeny tiny point, and something that would need to be handled in the larger Neutron context.16:16
SridarKa neutron ext-list should tell u, but yes this is a wider issue16:21
njohnstonSridarK: Just checking, when I run the UTs, I get "TypeError: Can't instantiate abstract class Firewall_db_mixin_v2 with abstract methods create_address_group, delete_address_group, get_address_group, update_address_group" - are you getting that as well?16:22
SridarKnjohnston: i removed these, i think now the ext patch also removed it16:23
njohnstonExcellent, must be an old copy of 26448916:26
SridarKnjohnston: ok16:26
SridarKnjohnston: it seems that if we use project_id instead of tenant_id - there is an issue - i just put a comment in the ext patch16:30
SridarKnjohnston: to test this - i replaced all occurrences in our db patch set as well. As soon as Shweta updates - i will push out the changes for our patch16:32
njohnstonsounds good.16:32
SridarKwith that we can divy things up and move fwd in parallel16:32
njohnstonI am leaving a comment; there is a minor change to 311159 that would avoid a deprecation notice16:32
njohnstonI don't want to step on your next patchset :-)16:33
SridarKi just got an email from yushiro who also has been digging into the tenant_id vs project_id and he is off the same opinion16:33
SridarKnjohnston: sounds good16:33
SridarKi will get ready and head to work shortly16:34
chandanc_AFK_1hrHello Nate and SridarK, please let me know if you need to run any integration tests, i can probably bring-up a fresh devstack in the morning and test the patches16:42
*** chandanc_AFK_1hr is now known as chandanc_16:42
*** xdcc has joined #openstack-fwaas16:44
SridarKchandanc_: ok thx - will let u know - will be back online in an hour17:04
*** chandanc_ has quit IRC17:15
*** SridarK has quit IRC17:18
*** SridarK_ has joined #openstack-fwaas18:02
SridarK_njohnston: i just pushed up a PS for the tenant_id change to our db patch18:45
*** xdcc has quit IRC18:45
njohnstonexcellent, I will take a look at it18:54
njohnstonlet me make sure what I am seeing for test results mirrors what you are seeing, SridarK_.  I see 3 main types of errors:19:05
njohnston1. "AttributeError: 'module' object has no attribute 'migration_callback'"19:06
njohnstonSridarK_: Do you want me to post fixes to a new PS, or leave comments in gerrit?19:17
SridarK_njohnston: sorry back - office interruption19:26
njohnstonnp19:27
SridarK_njohnston: no we can divy up for sure - i will also go back to the plugin patch19:27
SridarK_quick call ?19:27
njohnstonsure; phone or online?19:28
SridarK_we can do online so we can screen share - give me a few mins - let me find a conf room19:29
njohnstonok19:29
njohnstonSridarK_: If the extension patch is not updated, that would explain why most of my errors are:19:37
njohnston    {"NeutronError": {"type": "HTTPBadRequest", "message": "Unrecognized attribute(s) 'tenant_id'", "detail": ""}}19:37
SridarK_njohnston: yes this is because the ext patch is not updated19:38
njohnstonDo we have an ETA for that?19:38
SridarK_njohnston: a quick work around could be to just manually replace project_id with tenant_id in the ext file19:39
SridarK_there are only 4 or 5 in the ext file19:39
njohnstonyep, doing that now... is Shweta currently working on the extension?  I could push a new Ps for it.19:39
njohnston(not sure what timezone Shweta is in)19:39
SridarK_she is working on it - i think she is on a customer mtg19:40
SridarK_she is in EDT19:40
njohnstonokie dokie19:40
SridarK_njohnston: mfranc213: http://paste.openstack.org/show/558522/19:45
SridarK_has the list of errors, 3 categories19:46
SridarK_0) - will need to be removed19:46
SridarK_1) mostly we need to tweak some of the names etc19:47
mfranc213hi SridarK_ i'm going to let you and Nate beat that one down.  i'm finishing up the UT for the driver and agent-extension stuff.  actually have all UT working;19:47
SridarK_mfranc213: ok that is fine19:47
mfranc213a UT error in the ciso_fwaas_plugin was introduced after a rebase.19:47
mfranc2132 UT failures actually.19:47
mfranc213am investigating these now.19:48
SridarK_mfranc213: i will get a patch out now to remove the cisco stuff19:48
mfranc213oh, so i can ignore?19:48
SridarK_yes19:48
mfranc213b/c them i'm done.19:48
mfranc213thank you Sridar19:48
SridarK_ok19:48
SridarK_i just need one clarification and then i will have that out19:48
SridarK_u still have these other patches to merge19:49
SridarK_2) has some of the tenant_id kind of things19:49
SridarK_njohnston: i can poke at (2) since i was in that area,19:50
SridarK_but i shd also get back to the plugin and clean things up there and get the UT going19:50
njohnstonlet me work on it :-)19:50
SridarK_ok then u will start down the list on (1)19:51
njohnstonyep19:51
SridarK_u can look at test_create_firewall_group & test_create_firewall_group_with_dvr19:52
SridarK_the fixes shd be along those lines19:52
njohnstonthanks19:53
SridarK_njohnston: i forgot the libconstants - i quickly wanted to get the changes out of my workspace20:00
njohnstonnot a problem, I'll take care of it20:00
SridarK_njohnston: thx20:00
mfranc213hello chandanc_ please see https://review.openstack.org/#/c/337699/11..1220:08
mfranc213i hope you can look carefully especially at the changes in test_iptables_fwaas_v2.py20:08
mfranc213and iptables_fwaas_v2.py.  let me know if you see things that need to be fixed and, if so, whether you would like me to fix them or would like to do it yourself.20:09
SridarK_njohnston: mfranc213: just got done with my mtg - if we need a sync we can do that now or later in the day too20:13
njohnstonI am still crawling on the DB patch, so I am good for now20:14
mfranc213SridarK_ njohnston suggested i look at the OVO stuff now.20:15
SridarK_ok then, i wont push anything20:15
mfranc213does that sound good or is there something else you would like me to look at?20:15
SridarK_mfranc213: OVO ?20:15
SridarK_versioned obj20:15
SridarK_?20:15
mfranc213yeah.  oslo versioned objects.20:15
mfranc213sorry for the abbrev :)20:16
SridarK_mfranc213: no i think that would be perfect20:16
mfranc213how come you need to wait to push the next plugin PS?  i'm a little confused... (sorry)20:17
SridarK_mfranc213: no i was talking abt the db20:18
mfranc213oh, i get it!20:18
SridarK_:-)20:18
mfranc213thank you SridarK_  diving into versioned objects now...20:19
SridarK_mfranc213: great thx20:19
mfranc213padkrish: i'm going to start looking at the comments on https://review.openstack.org/#/c/342476/ now.  don't want to step on your toes; so please let me know if i shouldn't issue a PS before checking with you.20:24
njohnstonbrb, relocating20:35
njohnstonSridarK_: Quick question.  It looks like there is no analogue to the "firewall" method in FirewallPluginDbTestCase - http://git.openstack.org/cgit/openstack/neutron-fwaas/tree/neutron_fwaas/tests/unit/db/firewall/test_firewall_db.py#n277 - did that get renamed/refactored into something else?  Or is it just not needed in v2?21:07
SridarK_it will be firewall_group21:08
*** yamamoto has joined #openstack-fwaas21:08
SridarK_L#28121:09
njohnstonThanks - I wasn't sure because the argument list is a bit different, but I guess that is because firewall_policy_id has bifurcated into ingress and egress variants in v221:10
*** yamamoto has quit IRC21:15
SridarK_njohnston: yes that is correct21:16
SridarK_i think i have fixed all these helper methods21:17
SridarK_i was just passing in a policy id and used the same for ingress & egress21:17
njohnstonI was in progress of doing the same thing, I'll finish it up and push a PS21:24
SridarK_ok21:32
njohnstonSridarK_: I pushed another PS for 311159; it looks like some of the negative unit tests are failing and for good reasons.  For example, test_update_shared_firewall_policy_with_unshared_rule should error out but it doesn't, so we get an expectation mismatch, where it was looking for an http return code of 409 but it got 200 instead.21:44
njohnstonI want to see if going through the gate catches any other syntax-y stuff, but that is the main part of the errors at this point.21:44
SridarK_njohnston: ah ok - yes that is a good point. i think some places with public could be broken. i can take  a look at this test, when i hit a logical point on the plugin21:45
njohnstonsounds good21:46
*** yamamoto has joined #openstack-fwaas22:46

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