Friday, 2016-09-02

*** vishwanathj has joined #openstack-fwaas00:11
*** SumitNaiksatam has quit IRC00:24
*** mickeys has quit IRC00:33
*** mickeys has joined #openstack-fwaas00:34
*** mickeys has quit IRC00:38
*** diogogmt has joined #openstack-fwaas00:43
*** yamamoto_ has joined #openstack-fwaas01:38
*** SumitNaiksatam has joined #openstack-fwaas01:39
*** SumitNaiksatam has quit IRC01:53
*** yushiro has left #openstack-fwaas02:03
*** yushiro has quit IRC02:03
*** diogogmt has quit IRC03:41
*** yushiro has joined #openstack-fwaas04:07
*** SarathMekala has joined #openstack-fwaas04:31
*** SridarK has joined #openstack-fwaas04:39
SridarKyushiro: hi04:40
yushiroSridarK: Hi, good evening04:40
SridarKyushiro: GM04:40
SridarKi think Armando put a -204:40
SridarKfor the CLI04:41
yushiroYes exactly...04:41
yushiromany many apologize for it.  hmm, I'm find to do what I can do now.04:42
yushiro*finding04:42
SridarKyushiro: no worries -04:42
SridarKi think u can still address any outstanding comments with Akihiro04:42
yushiroYes, he also commented at midnight in Japan timezone.04:43
SridarKand u can work with him to have things ready04:43
yushiroyeah.  I contacted to him yesterday.04:44
yushiroMaybe you already know,  njohnston has posted to remove policy.json in neutron and also posted policy.d in fwaas04:45
SridarKyushiro: cool - i am not sure where we are with things - he may open it up tomorrow - i think since Akihiro is on the review - u can work thru him04:45
SridarKyes that has to get in also - i think today they needed to stop everything to get RC1, bug fixes can go in04:46
SridarKi know i have to take care of the rule update issue04:46
SridarKso dont worry too much i think if the patch is ready - we may still have a chance04:47
yushiroOK.  I'll change my mind from now.04:47
yushiroBTW,04:47
yushiroI found another issue when deleting firewall-rule04:47
SridarKyushiro: pls dont be hard on urself, lets stay optimistic04:47
yushiroSridarK: OK, thanks.04:48
yushiroSo, let me sync about this issue.04:48
yushiroJust a moment, please.04:48
SridarKyushiro: ah ok - yes there are some issues on the the rule handling - njohnston opened a bug to track it04:48
yushiroOh, sorry. I didn't check bug report.  I'll take a look at launchpad.04:49
SridarKwe decided to get it in so we can unblock the dependencies to get the agent patches merged04:49
SridarKif u see something just send me an email, i will start work on the fw rule related issues04:49
SridarKtomorrow i will work on that - tonight i am going to bed early04:50
yushiroSridarK: Sure.  If I find a new issue, may I file a bug-report ?04:50
SridarKyushiro: yes pls go ahead04:51
SarathMekalayushiro if need help i can pitch in04:51
yushiroSridarK: OK. I'll do it.04:51
yushiroSarathMekala: many thanks.04:51
SridarKif u can keep the rule related issues in a single bug id that will be good and easier to get in04:51
SridarKi was going to ask everyone to help with more testing and documentation, we can all keep a devstack setup to do more testing04:52
SridarKyushiro: i also updated ur etherpad on the testing and added more curl cmds or we can cherry pick the CLI patch so we get more testing with that04:53
SarathMekalasure will bring up my devstack setup today and will do some testing04:53
SridarKok great thx04:53
yushiroSridarK: OK. I'll check it.04:54
yushiroNow, we can test both CLI and server-side behavior :)04:54
SridarKyushiro: yes exactly04:54
*** mickeys has joined #openstack-fwaas04:55
SridarKyushiro: after this i will ask u for some more explanation on osc-utils - that seem to give me some issues when i was trying to see why Jenkins failure happened on ur patch yesterday04:55
SridarKbut may next week or after04:55
SridarKok i am going to sign off early tonight04:56
yushiroSridarK: quick question.  If I file a bug, is 'fwaas' tag  OK?04:56
SridarKpls send me an email if something needs my attention04:56
SridarKyushiro: yes that is good04:56
yushiroOK, I got it!  Please have a break.  Good night!!04:56
*** chandanc_ has joined #openstack-fwaas04:57
SridarKchandanc_: hi, thx for the help - we made the merge in the nick of time04:57
chandanc_hey SridarK , ya just saw that04:58
SridarK:-)04:58
chandanc_it was great04:58
chandanc_what is the plan now ?04:58
SridarKwe do more testing04:58
*** yamamoto_ has quit IRC04:58
SridarKwe shd atleast try fix the critical bugs04:59
chandanc_ok sure, and how long do we have for that ?04:59
SridarKmay be a week or so04:59
chandanc_oh04:59
SridarKi dont recall - but will be best to focus on critical issues only to avoid any regression05:00
chandanc_I just realized that we totaly forgot about the router port delete05:00
SridarK?05:00
chandanc_cleaning up fw rules on router port delete05:01
SridarKoh yes05:01
SridarKthat can be  a bug worth fixing05:01
chandanc_would like to fix it for sure05:01
SridarKcould u look at that and also do some testing around that05:01
yushirochandanc_: you mean 'remove-router-interface' for router?05:01
chandanc_sure05:01
chandanc_yes yushiro05:01
yushiroah, I see.05:02
yushirothanks05:02
SridarKyushiro: yes then we will need to clean out the stale rules05:02
chandanc_sorry yushiro , i could not test your CLI, i will pick it up next05:02
SridarKchandanc_: yes i think we can all test with the CLI patch05:02
SridarKyushiro: one question05:02
yushiroSridarK: OK05:03
SridarKthe v1 CLI will be intact correct ?05:03
SridarKbecause we are keeping v1 as the default05:03
chandanc_hmm, i think we can have a confusion on the rule and policy05:04
chandanc_which are common in v1 and v205:04
SridarKyes05:04
yushiroSridarK: Hmm, there are some differences b/w v1 and v2.  Akihiro said that we should align OSC format/options .05:05
SridarKwe could call it firewall-group-rules and firewall-group-policy (worst case)05:05
SridarKyushiro: ok - u know best on that05:06
chandanc_+105:06
yushirocreate              policy-delete       policy-show         rule-list           update05:06
yushirodelete              policy-insert-rule  policy-update       rule-show05:06
yushirolist                policy-list         rule-create         rule-update05:06
yushiropolicy-create       policy-remove-rule  rule-delete         show05:06
yushiroThese are  v1 potentials05:06
yushirogroup create        group show          policy list         rule create         rule show05:07
yushirogroup delete        policy create       policy remove rule  rule delete05:07
yushirogroup list          policy delete       policy set          rule list05:07
yushirogroup set           policy insert rule  policy show         rule set05:07
yushiroThese are v2 potentials(latest patch)05:07
SridarKok05:07
SridarKso they can coexist05:08
chandanc_i see the 2nd one is OSC style, 1st one is neutron cli05:08
chandanc_right ?05:08
yushiroright.05:08
-openstackstatus- NOTICE: The logs volume is full causing jobs to fail with POST_FAILURE. This is being worked on, please do not recheck until notified.05:08
*** ChanServ changes topic to "The logs volume is full causing jobs to fail with POST_FAILURE. This is being worked on, please do not recheck until notified."05:08
chandanc_will we ever convert v1 to OSC05:08
chandanc_?05:09
yushiroI think it is also necessary05:09
yushiroIMO, the goal is both v1 and v2 commands can use with OSC.05:10
chandanc_oh, in that case will there be a conflict between the v1 and v205:10
SridarKfor v2 - where u say group (is that actually firewall-group)05:11
yushiroSridarK: correct.  sorry I pasted after typing 'firewall'05:11
SridarKok05:12
yushiroPlease add 'firewall ' as a prefix05:12
chandanc_is it possible to have "firewall_v2 " as prefix ? just a thought05:13
SridarKor u could consider firewall-group as the prefix05:14
SridarKand if at all we move v1 to OSC - that can have firewall as the prefix05:14
yushirochandanc_, SridarK : adding prefix is good idea.05:15
chandanc_+105:15
yushiroSridarK,: ah, that's good idea.  now: firewall group ...   your idea: 'firewall group' ...05:15
SridarKcan it be firewall-group ?05:16
yushiroSridarK: ah, maybe OSC can not specify '-' (hyphen) as a command.  It seems space separated commands.05:17
SridarKah also firewall_group is not allowed ?05:17
chandanc_SridarK, that will make commands like firewall_group group create :(05:18
SridarKok i think Akihiro will have a good idea - in the past he has helped me to define some of these very clearly05:18
yushiroI'll try it but I think it's difficult.05:18
SarathMekalahow about this:05:18
SarathMekalafirewall group05:18
SarathMekalafirewall policy05:18
SarathMekalafirewall rule05:18
SridarKchandanc_: then there will be no group05:18
SarathMekalais this the current impl?05:19
chandanc_no group will be there, but word repetation :)05:19
yushirocommand definition is as follows:05:19
SridarKchandanc_: ok got it i see what u are saying now05:19
yushirofirewall_group_create = neutronclient.osc.v2.fwaas.firewallgroup:CreateFirewallGroup05:19
yushiroat setup.cfg05:20
chandanc_ok that makes it clear05:20
chandanc_they are spliting at _05:20
yushiroIMO, no specify '-' or '_" or ' ',  just  'firewallgroup'  like lbaasv2 command05:20
yushiro(openstack) firewall05:21
yushirofirewallgroup create        firewallpolicy delete       firewallrule create05:21
yushirofirewallgroup delete        firewallpolicy insert rule  firewallrule delete05:21
yushirofirewallgroup list          firewallpolicy list         firewallrule list05:21
yushirofirewallgroup set           firewallpolicy remove rule  firewallrule set05:21
yushirofirewallgroup show          firewallpolicy set          firewallrule show05:21
yushirofirewallpolicy create       firewallpolicy show05:21
yushiroI just editted setup.cfg05:21
chandanc_hey why not firewallv2 like lbasv205:21
SarathMekalayushiro, is it possible to define it like -- firewall group create -- its very similar to CLI on the devices05:22
SridarKok i have to step away - i will look at the logs in the morning05:22
chandanc_Sure SridarK , thanks for all the help in debugging :)05:22
SridarKi think we have the problem definition clear, after ur discussion - yushiro u can also get somee inputs from Akihiro05:23
yushiroSridarK: Sure. I'll contact with him more deeply.05:23
SridarKchandanc_: no thank u for all the help - was a bit crazy but glad we got that in05:23
SridarKit will make our case stronger for the CLI patch also05:23
chandanc_:) ya true05:23
yushiroSarathMekala: I think it's the most simple05:23
SridarKok talk to u all tomorrow05:24
yushirochandanc_: Lbaas v2 is not specified 'v2'.05:25
yushiroas a command.05:25
yushiroe.g.  lbaas-loadbalancer-create05:25
yushiro  lbaas-loadbalancer-delete05:26
chandanc_oh, they dont have any conflict ?05:26
yushirothey don't have OSC plugin, however, they can avoid conflict  using 'prefix'05:27
yushirov1:  lb-healthmonitor-show     v2: lbaas-healthmonitor-show05:27
chandanc_ya, prefix is the correct solution05:27
yushiroHowever, I'm not sure OSC can use '-'(hyphen) or not.05:28
chandanc_better to avoid - or _05:28
yushirofor example:05:28
yushiroI defined  firewallpolicy_insert_rule = neutronclient.osc.v2.fwaas.firewallpolicy:FirewallPolicyInsertRule05:29
yushirooops, sorry05:29
yushirofirewallv2_policy_insert_rule = neutronclient.osc.v2.fwaas.firewallpolicy:FirewallPolicyInsertRule05:29
yushiro(openstack) firewallv2 policy05:30
yushirocreate       delete       insert rule  list         remove rule  set          show05:30
yushiroResult is above.05:30
yushiroThe point is   'insert rule'  is one word.05:30
chandanc_got it05:31
yushiroWhat I'd like to say is that 1st and 2nd command should be separated '_'05:31
yushiroI mean  'firewall_group_create"   --->   firewall group create    'firewall_policy_insert_rule'  -> firewall policy   'insert rule'05:31
chandanc_firewallv2_policy_insertrule05:31
chandanc_ugly :(05:32
yushiroreally?  It's not ugly ;)05:32
chandanc_ok :)05:32
yushirohmm, I still confusing.. It's difficult05:33
chandanc_i think we understand the issue, you can propose your suggestion in mail ,05:34
chandanc_yes agree05:34
chandanc_you have something in mind ?05:34
yushirofirewallv2  group create  :  I feel  'we create the group of 'firewallv2''05:34
*** ChanServ changes topic to "#openstack-fwaas"05:34
-openstackstatus- NOTICE: Space has been freed up on the log server. If you have POST_FAILURE results it is now safe to issue a 'recheck'05:34
yushiroI think that  ' we create  'firewall group'05:34
yushiroHow do you think?05:35
chandanc_firewallv2  group create LGTM05:35
yushiro1.  We will create  the group  of firewallv2   |  2. We will create 'firewall group'05:35
yushirochandanc_, : OK,  thanks for your opinion.05:36
chandanc_another option is fwaas(v1) vs firewall(v2)05:36
chandanc_again, better propose in mail05:37
yushirooh, sorry.  I talked much.05:37
chandanc_:) not at all05:37
chandanc_njohnston, and mfranc213 can also help05:38
yushiroYes.05:38
chandanc_yushiro, I will test the CLI patch and let you know.05:38
chandanc_AFK for 30 mins05:39
yushirochandanc_: thanks.05:39
*** chandanc_ is now known as chandanc_afk05:39
yushiroCRUD can run05:39
yushiro(I'm reflecting the comment from akihiro.)05:41
*** mickeys has quit IRC05:51
*** yamamoto_ has joined #openstack-fwaas05:55
*** mickeys has joined #openstack-fwaas06:32
*** vishwanathj is now known as vishwanathj_zzz06:45
*** mickeys has quit IRC08:01
*** _SarathMekala_ has joined #openstack-fwaas08:06
*** SarathMekala has quit IRC08:09
*** mickeys has joined #openstack-fwaas08:16
*** mickeys has quit IRC08:17
*** mickeys has joined #openstack-fwaas08:17
*** mickeys has quit IRC08:21
*** SarathMekala_ has joined #openstack-fwaas09:05
*** _SarathMekala_ has quit IRC09:08
*** yushiro has quit IRC09:30
*** yamamoto_ has quit IRC09:38
*** SarathMekala_ has quit IRC09:49
*** SarathMekala has joined #openstack-fwaas10:07
*** _SarathMekala_ has joined #openstack-fwaas10:08
*** SarathMekala_ has joined #openstack-fwaas10:11
*** SarathMekala has quit IRC10:12
*** SarathMekala has joined #openstack-fwaas10:15
*** _SarathMekala_ has quit IRC10:15
*** SarathMekala_ has quit IRC10:18
*** chandanc_afk has quit IRC11:03
*** chandanc_afk has joined #openstack-fwaas11:04
*** chandanc_afk has quit IRC11:10
*** chandanc_ has joined #openstack-fwaas11:10
*** xdcc has joined #openstack-fwaas11:11
*** _SarathMekala_ has joined #openstack-fwaas11:30
*** SarathMekala has quit IRC11:32
*** _SarathMekala_ has quit IRC11:35
*** chandanc_ has quit IRC12:31
*** chandanc_ has joined #openstack-fwaas13:23
*** mickeys has joined #openstack-fwaas14:04
*** mickeys has quit IRC14:20
*** diogogmt has joined #openstack-fwaas14:28
-openstackstatus- NOTICE: The Gerrit service on review.openstack.org is restarting quickly to relieve resource pressure and restore normal performance15:21
*** mickeys has joined #openstack-fwaas15:38
*** mickeys has quit IRC15:49
njohnstonI'm not missing something - the statement "FWaaS management options are available in the Dashboard." is false, right?16:45
njohnstonJust asking because that is what is stated here: http://docs.openstack.org/admin-guide/networking-introduction.html#enable-fwaas16:46
chandanc_you mean v2 right ?16:47
SridarKnjohnston: for v1 we do have complete Horizon support16:54
*** mickeys has joined #openstack-fwaas17:09
*** mickeys has quit IRC17:10
*** SridarK has quit IRC17:23
-openstackstatus- NOTICE: The infrastructure team is taking Gerrit offline for maintenance, beginning shortly after 18:00 UTC for a potentially 4 hour maintenance window.17:37
-openstackstatus- NOTICE: Gerrit is now going offline for maintenance, reserving a maintenance window through 22:00 UTC.18:03
*** ChanServ changes topic to "Gerrit is now going offline for maintenance, reserving a maintenance window through 22:00 UTC."18:03
*** SridarK has joined #openstack-fwaas18:38
*** ChanServ changes topic to "#openstack-fwaas"19:12
-openstackstatus- NOTICE: Gerrit is completing an online re-index, you may encounter slowness until it is complete19:12
*** chandanc_ has quit IRC19:30
*** SridarK has quit IRC19:34
*** xdcc has quit IRC19:59
*** SridarK_ has joined #openstack-fwaas21:54
*** SridarK_ has quit IRC22:02
*** SridarK_ has joined #openstack-fwaas23:14

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