Monday, 2016-08-15

*** vishwanathj has joined #openstack-fwaas01:43
*** vishwanathj has quit IRC01:43
*** yamamoto has joined #openstack-fwaas03:22
*** vishwanathj has joined #openstack-fwaas04:25
*** chandanc__ has joined #openstack-fwaas04:25
*** yushiro has joined #openstack-fwaas04:32
yushiroping SridarK04:35
SridarKyushiro: hi04:35
yushiroSridarK, Hi. Currently, I'm reviewing v2 database patch.04:35
yushiroThanks for your update(Patchset38)04:36
SridarKyushiro: ok great, there are still some UT that i am debugging04:36
SridarKyushiro: but it is great that u are reviewing, so u will have enough context as i keep updating04:37
yushiroSridarK, Thanks.  Please let me clarify.04:37
SridarKyushiro: i am mainly running thru the UT failures, i think list api's have some issue also04:38
yushiroSridarK, Oh, thanks.  Currently, I'm trying to run UT too in order to review more deeply.04:39
SridarKyushiro: ok there are some failures - so sorry - i am trying to fix - i am trying to clean up b4 i go to bed tonight04:40
yushiroSridarK, no warries.  Your work is great.  OK, currently, I focus on PS38.04:42
SridarKyushiro: thx04:43
yushiroSridarK, Oh, I forgot the confirmation.  In my understanding, when creating firewall-group, a mandatory param is only project_id, isn't it?04:43
yushiroI referred v2 SPEC.04:44
SridarKyushiro: yes that is correct, there is an issue on the ext patch the policy fields do not have a default04:44
yushiroSridarK, Ah, yes. That is what I'd like to comment :)04:45
yushiroSridarK, thank you.04:45
SridarKyushiro: ok great - we are on the same pg - i hit the issue on testing - i have put a comment in the ext patch04:45
SridarK:-)04:46
yushiroYeah.04:46
yushiroOK. I'll turn back to review.  Thank you so much!!04:46
yushiroIf you need some help or review, please let me know!04:47
*** vishwanathj has quit IRC04:55
SridarKyushiro: many thanks -04:56
*** mickeys has quit IRC05:05
*** mickeys has joined #openstack-fwaas05:05
*** mickeys has quit IRC05:10
*** vishwanathj has joined #openstack-fwaas05:15
*** vishwanathj is now known as vishwanathj_zzz05:16
*** chandanc__ has quit IRC05:25
*** yamamoto has quit IRC06:18
*** chandanc__ has joined #openstack-fwaas06:22
*** yamamoto has joined #openstack-fwaas06:59
*** chandanc__ has quit IRC07:04
*** mickeys has joined #openstack-fwaas07:29
*** mickeys has quit IRC07:33
*** mickeys has joined #openstack-fwaas08:30
*** mickeys has quit IRC08:31
*** mickeys has joined #openstack-fwaas08:31
*** mickeys has quit IRC08:33
*** mickeys has joined #openstack-fwaas08:34
*** mickeys has quit IRC08:38
*** yamamoto has quit IRC09:50
*** yamamoto_ has joined #openstack-fwaas10:32
mfranc213ping chandanc, chandanc_11:50
*** chandanc__ has joined #openstack-fwaas11:55
*** yamamoto_ has quit IRC12:06
*** yamamoto has joined #openstack-fwaas12:07
*** yamamoto has quit IRC12:07
*** yamamoto has joined #openstack-fwaas12:07
SridarKnjohnston: ping12:56
*** raalee has joined #openstack-fwaas13:13
njohnstongood morning all13:13
mfranc213hello everyone13:20
mfranc213ping chandanc_13:26
njohnston^^ chandanc__ (two underscores)13:26
mfranc213thank you njohnston13:27
SridarKnjohnston: hi13:30
njohnstonSridarK: Hello.  You had a busy weekend!  Sorry I couldn't participate much - family events - but I am catching up on the activity.13:31
SridarKnjohnston: no worries, so now a good chunk of the UTs are good13:31
SridarKnjohnston: i think a few more tweaks and we should be good13:32
njohnstonExcellent.  Do you want me to work on that, or something else?13:32
SridarKnjohnston: i am in the middle of the firewall_group UTs13:33
SridarKlet me clean this up and we can sync up13:33
njohnstonsounds good13:33
SridarKnjohnston: how is the L3Agent ext13:33
SridarKnjohnston: meanwhile could u start looking at what will be needed on that front, L3Agent ext + versioned obj things13:34
SridarKi think that will be the next push, and u have more context on these areas13:35
mfranc213SridarK: do you want to put me to work also?  i worked on UTs for the driver over the weekend but don't want to step on chandanc__'s toes if he's already working on those.  won't do anything with that until talking to him.13:36
SridarKmeanwhile let me see how the db patch is heading and we can sync - i hit some issue with on the tests with the project id tht has been nagging13:36
SridarKmfranc213: surely, i think all we may need is one more refactor to move the files to _v2 (my last comment)13:37
SridarKnjohnston: are u okay with this or pls let me know if we want to do this differently13:37
njohnstonI think that sounds like a solid plan.  Let me know when a good time to sync with you is; my schedule is wide open.13:38
mfranc213SridarK: will check it out and ping with questions.  thank yoiu.13:39
SridarKhow abt we do a sync btwn njohnston: , mfranc213: , chandanc__ and myself13:39
njohnstonsounds good13:39
mfranc213sounds v good.13:39
*** chandanc__ has quit IRC13:40
SridarKi have some mtgs at 8am pacific - so if we see chandanc come online - we can do before that13:40
mfranc213thank you13:40
SridarKgreat thx mfranc213:, njohnston:13:41
*** yushiro has quit IRC13:47
*** yushiro has joined #openstack-fwaas13:51
*** yamamoto has quit IRC13:52
*** yamamoto has joined #openstack-fwaas13:52
yushiroHi,13:53
yushiroIs SridarK here?13:55
*** yamamoto has quit IRC13:57
njohnstonHe was here ~15 minutes ago - should be back soon I think13:57
*** yamamoto has joined #openstack-fwaas14:10
njohnstonFYI all, it appears that the change "Fix db migration after project_id changes" - https://review.openstack.org/#/c/352216/ - is causing OSA DB migration issues.14:12
njohnstonSee: https://bugs.launchpad.net/neutron/+bug/161329914:12
openstackLaunchpad bug 1613299 in openstack-ansible "Unknown column 'r.project_id' in FWaaS migrations" [High,New]14:12
njohnstonI have a revert patch ready: https://review.openstack.org/#/c/355483/14:13
njohnstonI suggest we revert, and then approach it again and figure out why this didn't occur on devstack.14:13
SridarKyushiro: here14:14
yushiroSridarK, Hi.  Today, I tried to run UTs for DB patch and realized about 'tenant_id'.14:16
SridarKyushiro: ok - i have been hitting some UT issues around there which i was debugging14:17
SridarKnjohnston: can u pls check in with HenryG as well14:17
SridarKon the revert14:17
yushiroHenryG is try to support Keystone v3 and modify from 'tenant_id' to 'project_id' on DB.14:18
yushiroHowever, all of neutron resources still have 'tenant_id' at request body.14:18
njohnstonI thought there was something in that essentially made 'tenant_id' a synonym of 'project_id'.14:20
SridarKyushiro: yes this was my experience too14:20
njohnstonat the database layer14:20
SridarKyushiro: i got a malformed req error14:20
yushiroAnd, base neutron codes doesn't support to specify 'project_id' in request body.14:20
SridarKand i added in the project_id14:20
SridarKnjohnston: yes u are correct at the db layer14:21
SridarKyushiro: i had to add in project_id in the UT14:21
SridarKthis kind of derailed me for a long time14:22
yushironjohnston, Ah, in DB layer.. I see.14:22
SridarKyushiro: but are u saying that we need to send in 'tenant_id'14:22
yushiroSridarK, hmm Yes. Because of policy check.14:24
yushiroSridarK, If we don't have 'tenant_id' it violates at policy.py14:25
SridarKyushiro: ok good - i was going so crazy in debugging this14:25
yushiroIn UT, we send 'new_create_request' --> (snip) --> populate_tenant_id --> verify_attributes ---> policy check14:27
yushiropopulate_tenant_id will insert 'tenant_id' if we don't specify this14:27
SridarKyushiro: yes which is why we had UTs without the tenant_id except in some cases14:28
yushiroverify_attributes compares request body and extension's dict.  Here is the difficult point.14:29
yushiroSridarK, Sorry, I think my explanation is difficult to understand :(  let me see...14:33
SridarKyushiro: no that makes sense14:33
SridarKyushiro: one other thing - while running the UT, i noticed that when the create api is called14:34
SridarKand i checked for 'tenant_id' or 'project_id' it is always None14:34
SridarKand is_admin is True14:35
SridarKso when i run the test to make sure that i cannot access resources on another tenant - that does not quite work14:36
SridarKi can write an email to u with some debugs to make it more clear14:36
SridarKit could be related to what u say14:37
yushiroSridarK, OK.  Maybe I've hit the same situation today.  Please send me :)14:39
*** vishwanathj_zzz is now known as vishwanathj14:40
SridarKyushiro: how long will u be up ?14:40
yushiroSridarK, Sorry, I have to go office tomorrow.  Therefore, I can be up untill 1:00am.14:42
SridarKyushiro: ok i have to be in a mtg shortly - will try to get this to u quickly else u can look at it first thing ur morning14:43
njohnstonSridarK xgerman yushiro: Could you take a look at https://review.openstack.org/#/c/355483/ so we can unbreak OSA?  I think HenryG may be travelling to the midcycle, so I am not sure we should wait for him, since the alternative is returning to status quo ante.14:43
xgermansure14:43
SridarKnjohnston: yes waiting on Jenkins14:44
njohnstonok good, wasn't sure.  thanks!14:44
yushironjohnston, Sure! but please wait tomorrow's morning :)14:45
SridarKyamamoto: can u pls also look at https://review.openstack.org/#/c/355483/14:46
yamamotoSridarK: ?14:47
yushironjohnston, midcycle! That's why HenryG does not response today.  I didn't know that. Thank you.14:47
xgermanok, holler, when the jenkins job finishes and I can +2/A14:48
yamamotoSridarK: will look tomorrow14:48
SridarKyamamoto: it seems https://review.openstack.org/#/c/352216/ is causing an issue, njohnston: is chasing that14:48
SridarKyamamoto: ok i realize it is very late for u14:48
yamamotoSridarK: thank you for understanding14:49
njohnstonI got a response from HenryG, he thinks we can just fix the bad column name as opposed to reverting.14:49
SridarKyamamoto: no worries, GN - we can pick up a discussion later14:49
njohnstonHe gave a suggestion for how to write a test job that would pick up this issue, because the way devstack and the gate jobs do it wouldn't exercise this code path.14:50
SridarKnjohnston: ok great14:50
njohnstonNew change to fix is: https://review.openstack.org/35551114:59
*** yamamoto has quit IRC15:14
*** yamamoto has joined #openstack-fwaas15:14
*** yamamoto has quit IRC15:20
yushironjohnston, I just reviewed https://review.openstack.org/35551115:21
*** chandanc__ has joined #openstack-fwaas15:23
SridarKyushiro: so i did a quick experiment15:27
njohnstonThanks yushiro and xgerman!15:27
SridarKnjohnston: i am watching Jenkins15:27
SridarKyushiro: i replaced 'project_id' with 'tenant_id'15:28
SridarKin a create req15:28
yushiroyes.15:28
SridarKand it seems like i get a Bad Req15:28
*** raalee has quit IRC15:30
SridarKyushiro: http://paste.openstack.org/show/557588/15:30
yushiroOK.  I think you got 'Unrecognized attribute(s)'...  ah, Yes.15:30
yushiroI just watched pasted link.15:31
SridarKbut if i had project_id it seems to make it to the CR method15:31
yushiroSridarK, Yes, you're right. in populate_tenant_id, it is validated when 'is_create' is True.15:32
yushiroSridarK, I think you got an error from verify_attributes in api/v2/attributes.py15:32
*** diogogmt has joined #openstack-fwaas15:33
yushiroyour req-body: xxx, yyy, 'tenant_id', zzz.   extension's dict: xxx, yyy, 'project_id', zzz.15:33
yushiroI think verify_attributes compares dict keys b/w req-body and extension's dict.15:34
SridarKyushiro: hmm so we need tenant_id outside of the ext dict ?15:35
yushiroIn order to prevent from this error, Yes.  But this is inconsistency.15:36
SridarKyushiro: how would i set that ?15:36
SridarKyes it seems odd15:36
yushiroHere is just bad workaround.  1. Please specify 'tenant_id' in req-body(You've already done)  2. replace 'project_id' to 'tenant_id' into ext dict.15:38
yushiroHmm.... I think current neutron does not support to specify 'project_id' instead of 'tenant_id'.15:40
*** mickeys has joined #openstack-fwaas15:40
yushiroI tried to reach out HenryG today because he try to support keystone v3 but I couldn't :(15:41
SridarKactually, as i understand - i think i have only touched the ext dict15:44
*** mickeys has quit IRC15:44
SridarKchandanc__: ping15:47
SridarKyushiro: i will do more debugging during the day - will try to catch up with u tonight - so we can close this out15:57
SridarKtonight - pacific (so during ur day time)15:57
yushiroSridarK, I understand.  Thanks for your information.15:58
SridarKyushiro: thx15:58
SridarKyushiro: can u pls do a quick scan of the ext patch to make sure ur comments are addressed16:00
yushiroSridarK, Sure.16:01
SridarKyushiro: so she can address any more, i am going to review that in a bit after i get done with mtgs etc16:01
njohnstonI was pulled away for some neutron bug deputy duty... but I think I am back now.16:01
SridarKnjohnston: no worries, i think chandanc__ is away (it is a local holiday for him)16:02
SridarKnjohnston: maybe we can sync along with mfranc213 a bit later in the day16:02
njohnstonok.  In the mean time, let me know if I can help with the DB patch.  I'm just Zuul-gazing right now.16:03
yushiroSridarK, OK, my comment is reflected on her latest patchset.16:04
yushiroHowever, it seems that UT doesn't run correctly.  I'll check/review it tomorrow.16:05
SridarKyushiro: ok cool i will review later today16:05
njohnstonAre we talking about https://review.openstack.org/#/c/264489/ ?16:06
SridarKnjohnston: yes16:07
SridarKnjohnston: can u pls also take a look16:07
njohnstonWill do.  But the most recent comment on that from Yushiro is on 8/13, which is why I asked.16:08
SridarKi had a set of comments over the weekend16:08
njohnstonOk, re-reading what yushiro said I realized I was mistaken, I thought he had added a new comment.16:08
njohnstonChecking it now...16:08
mfranc213SridarK: yes to a sync a bit later in the day.  let me know.16:09
SridarKnjohnston: yes she pushed a PS earlier today16:09
yushiroSridarK, njohnston BTW,16:13
yushiroSridarK, njohnston Does anyone focus on policy.json?16:13
yushiroI think rule is necessary.  ex. "delete_firewall_group": "rule:admin_or_owner",16:14
njohnstonyushiro: Agreed, definitely.16:14
yushironjohnston, SridarK OK. Let me confirm 1 thing.16:15
yushironjohnston, SridarK We should add  1. neutron/etc/policy.json  2. neutron/tests/etc/policy.json, shouldn't we?16:16
SridarKyushiro: pls go ahead, sorry slow response in another mtg16:16
yushiroSridarK, Sure. No warries.16:16
njohnstonyushiro: definitely16:16
yushiroI just ran UT(create_firewall_group) on DB patch and realized.16:17
yushironjohnston, OK.  I'm confusing that...   In case of 'firewall_group',  it is easy because just to add is enough.16:18
yushironjohnston, However, in case of 'firewall_policy' and 'firewall_rule'16:19
yushironjohnston, SridarK sorry, I'll paste the link.  Just a moment please....16:20
njohnstonsure thing16:20
*** mickeys has joined #openstack-fwaas16:21
SridarKyushiro: catching up16:21
yushironjohnston, SridarK Here is current policy definition about FWaaS and my thought. http://paste.openstack.org/show/557591/16:24
yushiroCould you please check it?16:24
njohnstonWe will want these methods to have "_v2" appended to them, yes?16:25
yushironjohnston, Hmmm, it is difficult.  Because, these methods is automatically generated.16:29
yushironjohnston, But, it's better to append "_v2" I think.16:30
SridarKsorry back16:30
SridarKyes i am not sure on the v2 either16:31
SridarKnjohnston: i just got done with some mtgs, shall we do a quick sync along with mfranc213:16:32
mfranc213here16:32
mfranc213:)16:32
SridarK:-)16:32
njohnstonsure16:32
SridarKok cool let me set up a call -16:33
mfranc213okay16:33
SridarKyushiro: i think it is really late, shall we continue the discussion over email, perhaps we can discuss this more during our day16:33
yushiroSridarK, OK.  Oh, it's 1:33 JST. Hahaha16:34
yushiroI'll go to bed.  Good night, SridarK and njohnston.  Let me discuss or send e-mail tomorrow.16:34
njohnstonThanks for all your work yushiro!16:34
yushirothank you16:34
SridarKyushiro: thx much16:35
SridarKGN16:35
*** yushiro has left #openstack-fwaas16:35
*** chandanc__ has quit IRC16:41
njohnstonJenkins is happy with https://review.openstack.org/#/c/355511/ BTW, it is ready for +A17:01
njohnstonThanks SridarK!17:05
*** chandanc__ has joined #openstack-fwaas17:37
*** chandanc__ has quit IRC18:04
njohnstonxgerman: Question for you.  I'm pretty sure I grok what I am typing, but my apologies if I don't.  I feel pretty sure that LBaaS v1 added methods to the neutron API in the same way that FWaaS does.  How does/did LBaaS furnish what it will need in terms of a policy.json to govern access to those API methods?18:16
xgermanI think we made them all admin18:17
njohnstonRight, but you didn't add the policy.json items directly into the main Neutron policy.json.  How would those items get added so that Neutron would know the policy was admin_only for those methods?  Will it read additional policy,json files for *-aas projects?18:21
xgermanmmh, @blogan likely knows the details18:31
xgermanblogan18:31
njohnstonxgerman: thanks!  pinging him now18:36
xgermanyeah, I tried to get to him myself, too18:36
xgermansorry, this has been so long back...18:36
njohnstonNot a problem, thanks for the pointer for blogan!18:37
xgermany.w. — dougwig might also able to help18:37
dougwigI recall discussing that a policy.d directory would be good for neutron, but don't think it got implemented.19:38
*** greghaynes has joined #openstack-fwaas20:11
*** yamamoto has joined #openstack-fwaas21:10
*** yamamoto has quit IRC21:11
*** yamamoto has joined #openstack-fwaas22:26
*** diogogmt has quit IRC23:31

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