18:32:05 #startmeeting Networking FWaaS 18:32:05 Hi All 18:32:06 Meeting started Wed Dec 10 18:32:05 2014 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:32:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:32:09 The meeting name has been set to 'networking_fwaas' 18:32:35 #info the Spec Approval deadline is 12/15 18:32:43 #info Kilo-1 is 12/18 18:33:32 #info Services’ split is underway, and FWaaS plugin and driver artifacts are in a separate repo 18:34:14 we will try to focus on the discussion related to the split, and try to keep it short so as to allow people to go back and participate in the split related effort 18:34:42 #topic FWaaS code split and work items 18:35:19 the currently documented list of outstanding items is identified here: #link https://etherpad.openstack.org/p/services_split 18:37:02 btw, the new code repository is: #link http://git.openstack.org/cgit/openstack/neutron-fwaas 18:37:35 SumitNaiksatam: i am looking at the UT re-enabling - i think i need the alembic changes ? 18:37:59 SridarK: yeah 18:38:10 SumitNaiksatam: i saw ur comment in brandon's spec 18:38:13 SridarK: i tested the two alembic patches yesterday 18:38:26 SridarK: however that does not have the actual migrations 18:38:27 i am patching soon and will keep on the UT 18:38:48 SridarK: ok good 18:38:52 SumitNaiksatam: i was a little confused on the interaction with neutron there 18:39:00 SridarK: go ahead 18:39:04 but hopefully for UT - it may work 18:39:34 SumitNaiksatam: so if i patch in brandon's fwaas alembic changes is that good enough 18:39:44 to get UT moving 18:40:02 SridarK: actually i am not sure that is required for the UT to work 18:40:24 SumitNaiksatam: ok hmm that was my thought initially - but ran into some issues 18:40:32 SridarK: when we run UTs, we dont run the alembic migration, the DB models are loaded into in memory db 18:40:37 SumitNaiksatam: anyways let me bang on this more and i will reach out 18:40:46 SumitNaiksatam: exactly that was my understanding too 18:41:01 SridarK: the reason the alembic migrations are required is because the gate will not work without those 18:41:13 SumitNaiksatam: yes for sure 18:41:33 SridarK: and they need the gate to work for the pending patches to merge 18:41:55 SridarK: i think they have temporarily disabled the gate on the services’ tests 18:42:15 SumitNaiksatam: ok i was trying to get some things going in parallel so if there are issues - we will be ready with the alembic stuff, then devstack changes all go in 18:42:29 * we will be ready when 18:42:57 SumitNaiksatam: let me bang on this some more and i will ping u later 18:43:10 SridarK: yes absolutely 18:43:21 SumitNaiksatam: thanks 18:43:23 SridarK: there was a patch in the morning to fix a path in the varmour UTs 18:43:28 SridarK: did you pick that up? 18:43:36 SumitNaiksatam: hmm no 18:43:44 I will look 18:43:55 SridarK: this the latest commit on the tree: #link http://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=a3000c57f42f3a6818545edee1993a393d781c4a 18:45:56 hello all 18:46:03 SumitNaiksatam: i believe i have just picked it up in my new refresh 18:46:06 sorry my inetrent was down a bit 18:46:11 SumitNaiksatam: thanks 18:46:14 badveli: hi 18:46:17 SridarK: cool 18:46:21 badveli: np 18:46:22 hello sridark 18:46:26 hello sumit 18:46:45 i am little confused by this: #link https://review.openstack.org/#/c/140572/4/lib/neutron_plugins/services/firewall 18:47:25 since we still have shims in neutron to the service plugins: #link https://review.openstack.org/#/c/140515/5/neutron/services/firewall/fwaas_plugin.py 18:47:55 SumitNaiksatam: i looked at this - thought this is just the path to our plugin 18:48:19 devstack uses this to set up neutron.conf i believe 18:49:26 so u think with shims this is not needed ? 18:49:51 SridarK: yeah i would think so 18:49:59 i have put my comment 18:50:19 SumitNaiksatam: ok 18:51:30 SridarK: anything else that is in flight that we havent covered with regards to the split? 18:51:42 SumitNaiksatam: none that i know off 18:51:55 SumitNaiksatam: i am sure things will pop up 18:51:56 i have not yet cloned the repository 18:52:04 the migration scripts will have to be moved 18:53:10 have anyone tested with the new split 18:53:38 Swami: not quite there yet 18:53:39 no 18:53:59 Swami: the UTs are currently disabled 18:54:03 ok 18:55:07 the service repos however have a reference to the neutron repos 18:55:26 so the neutron imports should work 18:56:22 SridarK: so what was the error you were seeing? 18:57:31 SumitNaiksatam: the error was related to FirewallRules table - 18:57:51 SumitNaiksatam: i am trying to work thru one set of tests 18:58:07 SumitNaiksatam: but i have not started a new run with an updated tree 18:58:23 SumitNaiksatam: let me do that first before raising some false alarms 18:58:52 SridarK: okay sure 18:59:09 anyone have questions on the split, or in general? 18:59:27 #topic Docs 18:59:45 Swami: just a check, anything more needed from our end on the DVR doc? 18:59:58 in last week’s meeting we had a couple of suggestions 19:03:00 okay perhaps Swami is not around 19:03:04 #topic Bugs 19:03:26 I did not notice any new bugs (apart from the ones we are dealing with on the services’ split) 19:03:36 SridarK: badveli: anything show up on your radar? 19:03:54 sorry got bounced out and have rejoined 19:04:17 SridarK: ah, i thought i was on the wrong side of the network split! :-) 19:04:33 SumitNaiksatam: :-) 19:04:46 SumitNaiksatam: sorry I missed your comment. 19:04:53 I think for now we are ok. 19:04:54 Swami: no worries 19:05:00 Swami: ok great 19:05:23 SridarK_: badveli: any new critical bugs you noticed? 19:05:34 SumitNaiksatam: nothing new 19:05:41 SridarK_: okay 19:05:42 19:05:53 nothing major 19:06:15 badveli: anything less than major but new? 19:07:18 i did not find anything 19:08:04 #topic Blueprints/Specs 19:08:29 as mentioned earlier 12/15 is the deadline to get the pending specs approved 19:09:19 our community specs under review: #link https://review.openstack.org/#/c/138672/ (firewall router association) 19:09:32 #link https://review.openstack.org/#/c/94133 (service objects) 19:10:04 ah sorry that last link is incorrect 19:10:10 i got excited for a min! 19:10:21 yes 19:11:08 #link https://review.openstack.org/131596 (service groups) 19:11:29 badveli: what about the DVR E-W traffic? 19:11:37 yes we have it 19:11:38 19:11:46 badveli: link? 19:11:55 https://review.openstack.org/#/c/140222/ 19:12:23 badveli: ah good 19:12:42 SumitNaiksatam: on the router association, thanks for ur review, others - could really use some more comments - we have discussed this quite a bit so hopefully there are no major surprises 19:13:11 SridarK_: yeah, will give it another read, thanks for your deligence 19:13:17 i also reviewed the router association spec. Looks good 19:13:23 SumitNaiksatam: thanks 19:13:27 natarajk: thanks 19:13:32 badveli: it was great that you could meet the proposal deadline 19:13:41 thanks sumit 19:14:01 badveli: thanks for putting together the blueprint spec out. 19:14:14 thanks swami 19:14:18 Swami: thanks for the technical discussion and options provided! 19:14:33 on the vendor blueprints 19:14:52 we have: #link https://review.openstack.org/#/c/129836/ 19:15:13 thanks to multiple review comments - thanks folks 19:15:23 badveli: can you update the wiki page: https://wiki.openstack.org/wiki/Meetings/FWaaS#Blueprint_Tracking 19:15:35 with the propose links to your two specs? 19:15:42 SridarK_: thanks 19:15:57 the second one is vishwanathj’s: #link https://review.openstack.org/#/c/136953/ 19:16:02 yes sumit 19:16:18 and we have two from RuiZang, #link https://review.openstack.org/#/c/134198/ #link https://review.openstack.org/#/c/91286/ 19:16:31 vishwanathj: RuiZang: i will try to get to those soon 19:16:40 SumitNaiksatam: thanks 19:16:42 vishwanathj: thanks for addressing comments - have a few more minor clarifications - pushing that out in a few mins - after that i think i am good 19:16:49 SumitNaiksatam, Thanks 19:16:59 RuiZang: i will also take a look 19:17:05 SridarK, I will upload a new spec based on your comments. 19:17:12 SridarK_: thanks 19:17:27 RuiZang, Please take a look at Brocade spec and I will look at yours as well 19:17:37 vishwanathj: sure thing ;) 19:18:37 anything spec to discuss in the context of any of the above specs (i belive we have 3 + 4 = 7 specs in review) 19:19:45 we have not yet heard anything from mark about the mail that gregory had send out 19:20:08 badveli: okay 19:20:32 badveli: thanks for that update! 19:20:39 #topic Open Discussion 19:20:46 i am not sure what would be the next steps, they had mentioned initially a security group reviewer and an api reviewere 19:20:59 19:21:07 what would be our next steps? 19:21:11 badveli: yeah, i am not sure either, i guess we just have to keep trying 19:21:57 badveli: i think the process that was asked to be followed has been followed 19:22:06 yes sumikt 19:22:15 thanks sumit 19:22:19 anthing else that anyone wants to bring up for today! 19:22:26 badveli: thanks for your persistence on that 19:23:18 thanks sumit, and all the reviewers 19:24:15 alrigth, thanks all! 19:24:18 bye 19:24:20 bye 19:24:22 Ok Bye 19:24:23 bye 19:24:26 #endmeeting