Wednesday, 2016-08-17

*** yushiro has joined #openstack-fwaas00:09
*** diogogmt has quit IRC00:28
yushiroHi njohnston, I've just commented your patch(https://review.openstack.org/#/c/311159)00:47
yushiroWould you please confirm it?00:47
*** chandanc_ has joined #openstack-fwaas01:14
*** diogogmt has joined #openstack-fwaas01:25
*** chandanc_ has quit IRC01:38
*** padkrish has joined #openstack-fwaas02:06
*** chandanc_ has joined #openstack-fwaas02:40
*** SridarK_ has quit IRC02:43
*** padkrish has quit IRC02:49
*** padkrish has joined #openstack-fwaas02:50
*** padkrish has quit IRC02:54
*** diogogmt has quit IRC03:28
*** padkrish has joined #openstack-fwaas03:28
*** yushiro has quit IRC03:31
*** padkrish_ has joined #openstack-fwaas03:49
*** padkrish has quit IRC03:52
*** SarathMekala has joined #openstack-fwaas03:52
*** yushiro has joined #openstack-fwaas03:59
*** davidlenwell has quit IRC04:42
*** davidlenwell has joined #openstack-fwaas04:55
yushiroping SarathMekala05:00
SarathMekalahi Yushiro05:00
yushiroSarathMekala, hi. Would you tell me more about your last words on IRC meeting?05:01
SarathMekalaIn V1, we can create a firewall with State as DOWN05:01
SarathMekalathis will prevent the plugin from creating the namespace05:02
*** SridarK has joined #openstack-fwaas05:02
yushiroSarathMekala, 'State' means 'admin_state_up' or 'status' ?05:02
SarathMekalaadmin_state_up i think05:02
SarathMekalanot sure what status stands for05:02
SridarKSarathMekala: admin_state is the administrative state05:03
SridarKstatus is operational status05:03
SarathMekalaYeah.. it should be the admin_state only05:03
yushiroSarathMekala, OK. I see. you say 'admin_state'.05:03
SarathMekalayeah.. there can be scenarios where a tenant precreates a firewall05:04
SarathMekalabut brings it up later05:04
SarathMekalaone more scenario is... during update operation a firewall admin_state can be brought down.. at which point the namespace has to be cleaned up05:05
SridarKSarathMekala: yes, if the firewall is not bound to port(s) we can also mark status as INACTIVE05:05
yushiroSridarK, SarathMekala Yes.05:05
SarathMekalayeah..05:05
SarathMekalaadmin_state down + ports associated will not have a namespace05:06
SarathMekalaadmin_state up + ports associated (or not) will have a namespace05:06
SarathMekalacorrection: by namespace I mean the FW rules on the iptable namespace05:07
SridarKSarathMekala: i think to be clear - u mean rules in a namespace05:07
SridarKok we said the same thing :-)05:07
SarathMekala:-)05:07
yushiroSarathMekala, Yes, however, no rule exists on firewall_group if firewall_group doesn't have 'ingress_firewall_policy_id' and 'egress_firewall_policy_id'05:07
yushiroAh, sorry. I'll AFK.... I'll go back here later...05:08
SarathMekalaright.. I am telling about one more scenario for your consideration05:08
*** yushiro is now known as yushiro_afk05:08
SarathMekalaok.. catch u later05:08
SridarKSarathMekala: yes correct05:08
SridarKbut the key thing is if there is no policy on the fwg, even if we associate ports - there is nothing really to push into the namespace05:09
SridarKso we keep the operational state (status) as INACTIVE05:09
SarathMekalaYeah.. agreed... operation state is fine as per the discussion05:10
SridarKor we enforce the need for atleast one policy05:10
SridarKto create a fwg05:10
SarathMekalaSG has a default security group05:10
SarathMekalacan we have a similar concept here for both ingress/egress05:11
SridarKone thing to look at is if in the default sec grp, i we take out all the rules05:11
SridarKwhat happens05:12
SarathMekalasee your point.. thats why SG does not allow to remove all the rules from default :)05:13
chandanc_in SG when a VM is launched, the default SG is always attached but the tenant can change it to his custom SG05:13
SridarKyes that is correct05:13
chandanc_Can check it05:13
SridarKwe will need some notion of specifying something like a default fwg that is applied to all vms05:14
SridarKon create05:14
chandanc_Here is a analogy for your case "for i in None " and "for i in []". I think the second case is still valid05:15
chandanc_what do you think :)05:15
SridarKchandanc_: yes agree :-)05:16
SridarKlets discuss more on email05:16
chandanc_sure05:16
SridarKlet me go back to debugging05:16
SarathMekalasure05:16
SridarK:-(05:16
SridarKmany thx for pulling together on this05:17
chandanc_lets catch up on mail05:17
SarathMekalano problem05:17
SarathMekalaAFK for teabreak05:18
*** yushiro_afk is now known as yushiro06:27
yushiroI just turned back.06:27
SridarKyushiro: can u pls scan the ext patch06:38
SridarKif u are good we can get it in06:39
yushiroSridarK, Sure. I'll do it. Just a moment please.06:39
SridarKok np06:39
SridarKtake ur time06:39
yushiroSridarK, I checked it . All of my comments are reflected.  However, I noticed that there is no test for firewall_group.06:44
yushiroSridarK, Should I comment about that?06:45
SridarKyushiro: maybe we can add that later ?06:47
SridarKi can pick it up along with the plugin patch06:47
yushiroSridarK: I think so.  We can add it later.  It looks good for 'firewall_groups' on ext patch.06:50
SridarKyushiro: ok good06:51
SridarKpls go ahead and i do the +A06:51
yushiroOK. I'll put +206:52
SridarKi also saw that all comments were addressed - mainly tenant_id and default06:52
SridarKon policies06:52
yushiroYeah. These are reflected. In this stage, we should keep "None" for both 'ingress_firewall_policy_id' and 'egress_firewall_policy_id', shouldn't we?06:56
yushiroas a default value.06:56
SridarKyushiro: yes i think so too06:58
yushiroSridarK, OK!! thanks06:58
SridarKi will add the validation to make sure that at least one is present on CR06:58
SridarKand we will not allow UPD that will result in no policy on the fwg06:59
yushiroSridarK, that make sense. additionally, we should take care of UPD 'admin_state_up'  as SarathMekala  mentioned.07:00
SridarKyushiro: yes agreed07:00
yushiroSridarK: I just put +2 on ext patch.07:00
SridarKyushiro: thanks - i did the +A07:02
yushiro:-)07:03
SridarKyushiro: tomorrow i will help on the db patch as needed and we can try to have that ready, then i can clean up the plugin07:04
yushiroSridarK, I understand.  I'll review DB and plugin patches.  Today, I'll put the CLI patch.07:05
SridarKyushiro: thx - i will sign off now07:10
yushiroSridarK, good night.07:17
*** yushiro has quit IRC07:56
*** padkrish_ has quit IRC08:05
*** chandanc_ has quit IRC08:08
*** mickeys has quit IRC08:39
*** mickeys has joined #openstack-fwaas08:39
*** mickeys has quit IRC08:44
*** chandanc_ has joined #openstack-fwaas08:52
*** openstack has joined #openstack-fwaas10:16
*** chandanc_ has quit IRC10:18
*** SarathMekala has quit IRC10:18
*** chandanc_ has joined #openstack-fwaas10:30
*** SarathMekala has joined #openstack-fwaas10:31
*** yamamoto has joined #openstack-fwaas10:50
*** yamamoto has quit IRC10:56
*** yamamoto has joined #openstack-fwaas10:57
*** yamamoto has quit IRC11:02
*** chandanc_ has quit IRC11:03
*** yamamoto has joined #openstack-fwaas11:03
*** yamamoto has quit IRC11:07
*** yamamoto has joined #openstack-fwaas11:07
*** SarathMekala has quit IRC11:09
*** yamamoto has quit IRC11:09
*** yamamoto has joined #openstack-fwaas11:09
*** yamamoto has quit IRC11:40
*** yamamoto has joined #openstack-fwaas11:46
*** yamamoto has quit IRC12:15
*** yamamoto has joined #openstack-fwaas12:28
*** yamamoto has quit IRC12:32
*** yamamoto has joined #openstack-fwaas12:55
mfranc213SridarK: ping13:05
SridarKmfranc213: GM13:21
mfranc213good morning SridarK--you are up early and were up late!13:22
mfranc213I wonder if you could look quickly at what I've done here and let me know if these changes are okay.  If not, I will revert: https://review.openstack.org/#/c/337699/12..13/neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent_v2.py13:22
SridarK:-) for the next couple of days need to keep chugging13:22
SridarKmfranc213: ok let me look13:22
mfranc213ty13:22
SridarKmfranc213: i think we can keep the reference as project in all the text and method names, but found out yesterday that setting the key as 'project_id' still has some issues with the infrastructure13:26
SridarKso across the ext patch and db patch we reverted back to using tenant_id as the attribute13:27
mfranc213yes, i read the meeting notes so wasn't sure what to do.13:27
SridarKso i think when ever u have time as u spin thru the patch - u can change 'project_id' back to 'tenant_id' where it is actually used as a key13:28
mfranc213so router['project_id'] should be router['tenant_id'] ?13:28
mfranc213(just want to be doubly sure :) )13:28
SridarKyes exactly13:29
mfranc213thank you SridarK.  i will fix.13:29
SridarKlet me put a comment on gerrit as well13:29
*** yamamoto has quit IRC13:29
mfranc213perfect13:29
*** yamamoto has joined #openstack-fwaas13:30
*** mickeys has joined #openstack-fwaas13:34
SridarKmfranc213: Done and thx13:35
mfranc213SridarK: thank you!13:35
SridarKmfranc213: np - i also msged padkrish that u were look for him - and thx for the follow up on the email - that will be the next hunk of things to get in13:36
mfranc213SridarK: thank you for doing that.13:37
SridarKmfranc213: np13:37
SridarKnjohnston: ping13:37
mfranc213SridarK: nate is out of the office for a bit.13:38
*** chandanc_ has joined #openstack-fwaas13:39
SridarKmfranc213: ok thx for the heads up - i just wanted to coordinate on the db patch - so i can work thru some of the comments without overwriting anything that he may have done13:39
SridarKi will not push anything up13:39
mfranc213SridarK: i believe he will be back in the office in 1/2 hour of so.13:39
SridarKmfranc213: ok cool thx13:40
mfranc213SridarK: would you be able to give me your opinion on something else?13:40
SridarKmfranc213: sure pls go ahead13:40
mfranc213SridarK: i've put this TODO in here, but now i think i should do something else: i think we should have a fwaas_base_v2.py instead? https://review.openstack.org/#/c/337699/13/neutron_fwaas/services/firewall/drivers/fwaas_base.py13:40
mfranc213and so all the methods can be abc.abstractmethods13:40
mfranc213one file for v1, and the other for v213:41
mfranc213?13:41
SridarKlet me look13:41
SridarKmfranc213: i think that makes sense to have a separate file for _v213:43
mfranc213SridarK: i will do that now.13:43
mfranc213thank you!13:43
SridarKmfranc213: ok great thx13:43
njohnstonGood morning all.14:16
njohnstonSridarK: pong14:16
xgermangood morning — sorry I missed last nights meeting14:27
*** yamamoto has quit IRC14:27
*** yamamoto has joined #openstack-fwaas14:29
*** yamamoto has quit IRC14:34
*** padkrish has joined #openstack-fwaas14:39
*** padkrish_ has joined #openstack-fwaas14:42
*** chandanc_ has quit IRC14:43
*** padkrish has quit IRC14:44
*** diogogmt has joined #openstack-fwaas14:47
SridarKnjohnston: Hi sorry i stepped away14:58
njohnstonSridarK: No problem14:59
SridarKxgerman: no worries - i think we had a good discussion and things are moving14:59
SridarKnjohnston: would u like me to work thru yushiro's last set of comments as i look thru some of the UTs15:00
njohnstonSridarK: If you have updates to 311159, please proceed15:00
njohnstonI'm on something else for the moment, I have no pending changes to 31115915:00
SridarKnjohnston: i will get started on that - but if u things to push at some point - we can sync with each other15:00
SridarKand coordinate15:01
njohnstonSridarK: sounds good15:01
njohnstonSridarK: I hope you, Paddu, and Shweta aren't affected by this: https://www.sdxcentral.com/articles/news/cisco-lay-off-14000-employees/2016/08/15:07
SridarKnjohnston: this is the major news for today - we have not heard anything and trying to stay optimisitic15:07
SridarKnjohnston: thx for asking15:07
*** yamamoto has joined #openstack-fwaas15:32
mfranc213padkrish_ ping15:33
padkrish_mfranc213: hello15:33
mfranc213hello there.  i've read ihar's comments and am ready to implement the changes if that's okay with you15:34
SridarKmfranc213: padkrish_ : if i am not mistaken - the comments were made in the context of the Address Group resource15:37
mfranc213yes and Firewall Group15:37
SridarKwe removed Address Group15:37
*** yamamoto has quit IRC15:37
SridarKas a todo for the future15:37
padkrish_mfranc213: I also wanted to discuss some of those with you....we need to remove some of those to keep in sync with the DB patch15:38
SridarKbut the idea applies to FirewallGroup15:38
njohnstonpadkrish_: correct15:38
SridarKwe removed in the ext and i removed it in the db patch also15:38
padkrish_ok...mfranc213# if you are ready with the changes, pls go ahead15:39
padkrish_i don't have the patches anyways, so it's ok15:39
mfranc213padkrish_: okay, i'll go ahead.  thank you paddu.15:40
*** padkrish_ has quit IRC15:57
*** padkrish has joined #openstack-fwaas16:19
*** yushiro has joined #openstack-fwaas16:48
yushirohi, good evening.16:48
yushiroI've just updated CLI patch and sorry for late.16:49
*** padkrish has quit IRC16:49
yushiroGood night...zzz16:50
*** yushiro has left #openstack-fwaas16:50
*** padkrish has joined #openstack-fwaas17:00
*** padkrish has quit IRC17:08
*** yamamoto has joined #openstack-fwaas17:34
*** padkrish has joined #openstack-fwaas17:37
*** yamamoto has quit IRC17:38
SridarKnjohnston: i took care of yushiro's comments on the db patch. I will interleave on the UT issues and the plugin patch for the rest of the day18:17
SridarKnjohnston: so u can continue to chug along, i will check in with u so we dont overwrite anything18:18
njohnstonOK, I have grabbed your latest PS, and I will deep dive into the remaining UT issues, starting with test_update_shared_firewall_policy_with_unshared_rule18:18
SridarKnjohnston: perfect18:18
SridarKmfranc213: i missed ur comment on the nullable fields - one of us will pick that up on the next PS18:18
mfranc213SridarK: yes, i think you were pushing the next PS right at the moment I was leaving my comment :)18:19
njohnstonI am looking at the spec to compare to make sure that all the non-nullable fields are marked as such.  SridarK, that would be the opposite of what is in the "Req" column in https://specs.openstack.org/openstack/neutron-specs/specs/newton/fwaas-api-2.0.html#data-model-impact right?18:24
njohnstoni.e. if "Req" = YES, then nullable=False, correct?18:25
*** padkrish has quit IRC18:34
SridarKnjohnston: yes ur correct18:35
*** padkrish has joined #openstack-fwaas18:35
SridarKmfranc213: yes i think i was doing the pep8 dance and did not notice, anyways njohnston is on it18:36
*** padkrish has quit IRC18:37
*** padkrish has joined #openstack-fwaas18:50
*** padkrish has quit IRC18:51
*** padkrish has joined #openstack-fwaas18:56
*** padkrish has quit IRC18:59
mfranc213ahh the pep8 dance--similar to the polka19:06
*** padkrish has joined #openstack-fwaas19:08
*** padkrish has quit IRC19:10
*** padkrish has joined #openstack-fwaas19:11
njohnstondown to just 14 failed tests and chugging along19:18
*** padkrish has quit IRC19:19
*** padkrish has joined #openstack-fwaas19:32
-openstackstatus- NOTICE: The volume for logs.openstack.org filled up rather suddenly, causing a number of jobs to fail with a POST_FAILURE result and no logs; we're manually expiring some logs now to buy breathing room, but any changes which hit that in the past few minutes will need to be rechecked and/or approved again19:44
SridarKnjohnston: cool19:49
njohnstonOf the remaining 14 that are broken, 9 of the test names start with test_update_firewall, 2 test_create_firewall, and 3 test_delete_firewall20:13
njohnstonI just posted my progress to 31115920:18
njohnstonI think most of the rest of things that need to be done are probably just making sure that references to 'firewall' get changed to 'firewall_group', or in some cases references to 'firewall_rule_id' get changed to 'ingress_firewall_rule_id' (or egress as the case may be).20:20
SridarKnjohnston: ok tell which ones u want me to take on20:30
njohnstonSure thing; I'll upload the list to a paste, 1 sec20:40
njohnstonok, the openstack paste is not responding, so http://pastebin.com/QeYfZNwz20:42
njohnstonthat is what is still not working; I fixed 2 more, just pushed a new version of 311159.  So there are 12 left.20:42
njohnstonSridarK: better URL: http://pastebin.com/raw/QeYfZNwz20:43
SridarKnjohnston: ok i will work thru this list20:45
njohnstonI'll be on later to tackle them again, whichever ones you don't make headway on20:46
SridarKnjohnston: perfect - will keep u posted20:46
*** padkrish has quit IRC21:35
*** padkrish has joined #openstack-fwaas21:44
*** mickeys has quit IRC22:07
*** yamamoto has joined #openstack-fwaas22:30
*** padkrish has quit IRC22:42
*** padkrish has joined #openstack-fwaas22:44
*** padkrish has quit IRC23:25
*** padkrish has joined #openstack-fwaas23:29
*** padkrish has quit IRC23:29
*** yushiro has joined #openstack-fwaas23:43
yushiromorning!23:43
yushiroxgerman, njohnston chandan, Thanks for your e-mail.  I'll reply to you soon.23:44
*** diogogmt has quit IRC23:56

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