04:00:37 <SridarK_> #startmeeting fwaas
04:00:38 <openstack> Meeting started Wed Aug  3 04:00:37 2016 UTC and is due to finish in 60 minutes.  The chair is SridarK_. Information about MeetBot at http://wiki.debian.org/MeetBot.
04:00:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
04:00:41 <openstack> The meeting name has been set to 'fwaas'
04:00:42 <xgerman> o/
04:00:43 <openstack> njohnston: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
04:00:46 <njohnston> oops just missed it
04:00:56 <SridarK_> #chair xgerman njohnston
04:00:57 <openstack> Current chairs: SridarK_ njohnston xgerman
04:01:22 <xgerman> Sridark_ beat you to it
04:01:26 <SridarK_> njohnston: it seems to be ok
04:01:33 <njohnston> yep!
04:01:51 <xgerman> +1
04:01:51 <SridarK_> sorry is there a problem ?
04:01:59 <xgerman> Nope
04:02:08 <SridarK_> ok :-)
04:02:18 <SridarK_> lets get started
04:02:19 <hoangcx> Hi
04:02:25 <SridarK_> njohnston: welcome back from PTO
04:02:46 <SridarK_> we can do the usual run thru of the usual things
04:03:05 <SridarK_> #topic fwaas v2
04:03:14 <njohnston> Thanks!  I'm on PTo the rest of the week as well, but back just long enough to be here with you all.
04:03:25 <SridarK_> njohnston: oh ok
04:03:30 <SridarK_> did not realize
04:03:53 <SridarK_> njohnston: thx
04:03:59 <xgerman> Thanks for your dedication
04:04:09 <SridarK_> dont see shweta online
04:04:27 <SridarK_> yushiro: i think u had some comments on the ext patch
04:04:46 <SridarK_> she was going to push up a version to address ur comments
04:04:54 <yushiro> SridarK_, yeah.  Today, shweta has updated it.
04:05:01 <SridarK_> ok great
04:05:27 <SridarK_> i was thinking to see if we can remove the resources we are not targetting immediately
04:05:40 <SridarK_> address group for one as an example
04:06:02 <SridarK_> if we can get a set of patches merged, with the basic set of resources
04:06:23 <SridarK_> any thoughts from the team ?
04:06:54 <yushiro> SridarK_, I agree with you.  we should shape our target for newton.
04:07:02 <njohnston> I completely agree
04:07:09 <njohnston> we need to have a laser focus on delivery
04:07:37 <xgerman> +1
04:08:03 <SridarK_> great i think we are on the same page then, these resources will need methods, UTs etc - seems like we can spend more time to get the basic set of resources solid
04:08:17 <SridarK_> ok then we can refactor accordingly
04:08:31 <njohnston> yep
04:08:44 <SridarK_> it seems that firewall_rules, firewall_policy & firewall_group can be the first target
04:09:00 <yushiro> SridarK_, OK.  I understood.
04:09:10 <SridarK_> ok thx for the feedback
04:09:25 <SridarK_> next on the db - plugin
04:09:59 <SridarK_> the integration has been going well - i have the basic create workflow working - just need to tweak the port association
04:10:28 <SridarK_> njohnston: i will push a few more updates to the db patch tomorrow
04:10:42 <njohnston> Sounds good.  Looks like the tests are all failing on the error: AttributeError: 'module' object has no attribute 'core_opts'
04:10:48 <SridarK_> yushiro: will address ur comments
04:11:03 <SridarK_> njohnston: yes will fix that
04:11:09 <njohnston> thx
04:11:20 <yushiro> SridarK_, OK.
04:11:40 <SridarK_> yushiro: thx for the workflow documentation
04:11:50 <yushiro> SridarK_, You're welcome.
04:12:06 <SridarK_> i certainly used curl to trigger things where i could not hack the CLI :-)
04:12:58 <SridarK_> once i have the db and plugin patch updated, will reach out to mfranc213: for integration with agent patch
04:14:06 <SridarK_> with that and with significant clean up - we can target to push out the ext, db, plugin and agent (+driver modifications) out
04:14:22 <njohnston> excellent
04:14:31 <yushiro> SridarK_, great :)
04:14:31 <SridarK_> this should give us a working L3 model with the old agent rpc
04:14:45 <xgerman> Nice!
04:14:54 <SridarK_> we can continue to strive for mid next week
04:15:18 <SridarK_> njohnston: i will try to push as much as i can on to the db patch until u are back
04:15:24 <SridarK_> from PTO
04:15:38 <njohnston> Thanks!  I will be back Monday... let me know what I can do to help
04:16:05 <yushiro> SridarK_, I'll comment DB & migration patch later.
04:16:14 <SridarK_> njohnston: ok we will sync - i will need to be out on Thu, Fri also - but let me see how much i can get in and we can sync up on mon
04:16:28 <njohnston> sounds good
04:17:18 <SridarK_> ok lets move to the agent side of things
04:17:45 <SridarK_> yushiro: pls go ahead - i think mfranc213: is not on and padkrish is also out
04:18:24 <SridarK_> based on previous discussions, we will focus on mfranc213:'s patch for the agent
04:18:33 <yushiro> SridarK_, Yes.  2 weeks ago, I've commented mfranc213's patch and replied some comments last week.
04:18:50 <SridarK_> yushiro: great thx
04:18:54 <yushiro> SridarK_, Currently, I'm waiting patch update for mfranc213.
04:19:29 <SridarK_> yushiro: ok i will likely sync with her or early on Thu after i wrap up things on db & plugin
04:19:43 <SridarK_> *tomorrow or early on Thu
04:19:50 <njohnston> I just pinged her too, so she'll see it in the morning
04:19:51 <yushiro> SridarK_, Great.  Thanks.
04:20:04 <SridarK_> yushiro: did u have some thing else to discuss
04:20:09 <SridarK_> on this topic
04:20:27 <yushiro> SridarK_, OK. I have just 1 notification.
04:20:30 <SridarK_> i know padkrish and u have also been discussing the versioned objects
04:20:42 <SridarK_> yushiro: ok
04:21:52 <yushiro> SridarK_, Currently, I'm trying to deploy devstack environment with L2-agent and versioned objects in order to test.
04:22:10 <SridarK_> yushiro: ok thx for looking into this
04:22:31 <yushiro> SridarK_, Maybe I'll finish it within Friday.
04:22:35 <SridarK_> ok
04:22:41 <yushiro> That's all for me :)
04:23:05 <SridarK_> lets move to the driver
04:23:14 <SridarK_> chandanc_: SarathMekala: thx for the email and updated doc and patch
04:23:46 <chandanc_> Thanks Sridar
04:24:02 <SridarK_> #link https://docs.google.com/document/d/1yGsGwVNZuptPCzMMgBH4AHVkdoeWvQxsT5Wql7-jtHI/edit?usp=sharing
04:24:11 <chandanc_> We will need your feedback and support to get the patch reviewed by neutron developers
04:24:11 <SridarK_> doc from chandanc_ & SarathMekala
04:24:35 <SridarK_> #link https://review.openstack.org/#/c/348177/
04:24:42 <SridarK_> neutron patch
04:25:12 <SridarK_> chandanc_: will do - just give me a day,  i pinged mickeys earlier today to remind him as well
04:25:19 <SridarK_> if he has not done so already
04:25:32 <chandanc_> I saw Armando changed the bug report for the patch and told to use the blueprint instead
04:26:38 <SridarK_> chandanc_: yes i think u can also update the commit msg
04:27:06 <chandanc_> ya the next amend with change the commit msg too
04:27:23 <yushiro> chandanc_, OK, good.
04:27:26 <SridarK_> we can sync on the irc or over email / call tomorrow or the day after
04:27:35 <SridarK_> request all to take a look as well
04:27:36 <chandanc_> ok sure
04:27:41 <SarathMekala> sure
04:28:07 <SridarK_> any other thing u guys would like to bring up ?
04:28:34 <SarathMekala> we are fixing the UT test failures
04:28:43 <chandanc_> nothing at this stage, we will start with the fwaas driver next
04:28:50 <SarathMekala> and will be working on the Firewall dirver this week
04:29:20 <SridarK_> ok perfect, thanks
04:29:29 <SridarK_> #topic L3 Agent ext
04:29:53 <SridarK_> njohnston: over to u - not sure if u are caught up having been on PTO
04:29:58 <njohnston> Hi!  So I haven't been able to do much, but I was able to answer the notes carl_baldwin made on https://review.openstack.org/#/c/339246/
04:30:15 <SridarK_> ok and i think mfranc213 is on it too
04:30:31 <njohnston> Hopefully that is now ready to go; I'll have to read the minutes of the L3 meeting to see if they mention it there
04:30:41 <SridarK_> njohnston: ok
04:30:52 <njohnston> mfranc213 represented us on the L3 meeting last week, perhaps she can do the same again
04:31:12 <SridarK_> njohnston: sounds good
04:31:22 <njohnston> That's it for me
04:31:29 <SridarK_> ok perfect
04:31:40 <xgerman> Yep
04:32:04 <SridarK_> #topic CLI
04:32:49 <SridarK_> yushiro: will u be able to dig into this more ?
04:33:19 <yushiro> SridarK_, Sorry, currently I can't.
04:33:37 <SridarK_> yushiro: ok
04:33:38 <yushiro> SridarK_, But I will.
04:33:51 <SridarK_> yushiro: oh ok
04:34:00 <xgerman> Thx
04:34:02 <SridarK_> yushiro: thx
04:34:08 <yushiro> I'd like to sync with njohnston about CLI.
04:34:45 <njohnston> What can I tell you about the CLI?
04:35:32 <yushiro> In my understanding, you are trying to put the patch into OSC and python-neutronclient.
04:36:06 <njohnston> Actually, I believe the CLI just needs to be implkemented in python-neutronclient
04:36:27 <njohnston> because OSC is incorporating python-neutronclient as a plugin
04:36:59 <njohnston> that us my theoretical understanding, but I still am not quite sure how it works.  The best person to talk to about it is probably rtheis.
04:38:27 <yushiro> njohnston, OK. I understand.  Thank you.
04:39:17 <SridarK_> thx yushiro: njohnston:, as mentioned by njohnston: the deadline for this is a week earlier than neutron-fwaas
04:39:48 <xgerman> :-(
04:39:54 <SridarK_> so once we have a plugin in place to field the CRUD - we should be able to get this in soon after and b4 the deadline
04:40:01 <SridarK_> xgerman: +1 yes sigh
04:40:53 <SridarK_> yushiro: hopefully this will not be too much once we get the basic stuff in place - we can all jump on this to help
04:41:37 <SridarK_> thats all i had, any thing else to discuss on this ?
04:42:22 <njohnston> nope
04:42:32 <yushiro> SridarK_, OK. Thanks.
04:42:58 <SridarK_> #topic Open Discussion
04:43:50 <SridarK_> yushiro: u had a question on project_id vs tenant_id - sorry i meant to respond back and forgot
04:43:53 <SridarK_> https://github.com/openstack/neutron-fwaas/commit/c3e491cae388713bb175d803de6a216a8816b816
04:44:11 <yushiro> SridarK_, Yes, let me explain about that.
04:44:34 <SridarK_> i think more work is in progress in neutron and this sort of handles it as a mapping in my understanding
04:44:57 <yushiro> SridarK_, Neutron has already done about keystone v3. (https://review.openstack.org/#/c/335786/20)
04:45:20 <yushiro> If this patch will be merged, all of neutron resources can use 'project_id' instead of 'tenant_id'.
04:45:34 <njohnston> yes indeed
04:45:52 <SridarK_> +1
04:46:12 <yushiro> So, I understand we don't need to do for 'project_id'.  I'm sorry for confusing...
04:46:44 <xgerman> Yep, project_id is the future
04:46:50 <njohnston> plus this already merged for fwaas: https://review.openstack.org/#/c/342326/
04:47:21 <yushiro> xgerman, njohnston I see.  Thank you.
04:48:00 <SridarK_> yushiro: ok hope ur question is answered
04:48:10 <yushiro> SridarK_, Yes, thanks.
04:48:14 <yushiro> All, let me confirm an attribute named 'admin status' for FirewallRule.
04:48:24 <SridarK_> we have called out project_id in our resource definitions
04:49:12 <SridarK_> yushiro: yes this needs more thought with the Rule being shared across policies - i am not sure we really need this
04:49:34 <SridarK_> yushiro: we can have an admin status for the firewall group
04:49:53 <xgerman> Yep, that makes more sense
04:50:38 <yushiro> SridarK_, xgerman OK. So, we should insert 'admin status' into firewall group
04:50:55 <SridarK_> yushiro: yes i just did so in my testing
04:51:09 <SridarK_> i think that will be useful
04:51:17 <yushiro> Ok.  I'll review it for migration patch.
04:51:25 <SridarK_> yushiro: ok thx
04:51:59 <SridarK_> along those lines, we also had a notion of PENDING states when the plugin was messaging with the agent
04:52:16 <SridarK_> i think once we have versioned objects - we may not need this at all
04:52:50 <SridarK_> xgerman: i will sync with u / yushiro / padkrish to get some clarfications on this
04:53:19 <xgerman> Ok, sounds good. E-mail likely best
04:53:31 <SridarK_> xgerman: ok will do
04:53:36 <SridarK_> xgerman: thx
04:53:42 <yushiro> SridarK_, Sounds great!  I sometimes confuse b/w fwaas v2.0 spec and current imprementation.
04:54:04 <yushiro> It'll be helpful for me.
04:54:06 <xgerman> Don't we all :-)
04:54:36 <SridarK_> yushiro: no worries at all - thanks for asking the questions - it helps to think thru this again
04:55:02 <SridarK_> other things folks would like to discuss ?
04:55:30 <yushiro> Sorry SridarK_ , last question.  In firewall_group, we should have 'admin_status' or 'status'?
04:55:52 <SridarK_> yushiro: one model is we have both
04:56:13 <xgerman> Status is the status of the system, admin_status is what the admin wants
04:56:13 <yushiro> SridarK_, OK, I understand!
04:56:20 <SridarK_> admin_status is more like administrative state - an admin could ..
04:56:36 <yushiro> xgerman, Thanks for your information :)
04:56:36 <SridarK_> ok i think u guys have answered it :-)
04:57:04 <yushiro> Yes, perfect.
04:57:46 <SridarK_> ok if nothing else - we can wrap things up
04:58:15 <xgerman> Yeah, t-2
04:58:28 <SridarK_> ok then - thanks all for attending and the discussion
04:58:36 <xgerman> Thx
04:58:43 <njohnston> thanks all
04:58:51 <SridarK_> Bye all
04:58:52 <SarathMekala> thanks o/
04:58:55 <SridarK_> #endmeeting