14:02:18 #startmeeting fwaas 14:02:19 Meeting started Tue Jun 27 14:02:18 2017 UTC and is due to finish in 60 minutes. The chair is yushiro. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:20 sure 14:02:22 The meeting name has been set to 'fwaas' 14:02:32 #chair SridarK yushiro xgerman_ 14:02:33 Current chairs: SridarK xgerman_ yushiro 14:02:45 #topic Pike 14:02:54 i can take over at any time too 14:03:04 yushiro: ok pls go ahead 14:03:16 SridarK, sure :) 14:03:30 L2-support 14:03:37 one update from chandan - he is still out on personal leave 14:03:59 when he has a few mins - he will try to ping 14:04:11 so we can help out and pick up some things 14:04:27 i think we can proceed with integration with his latest PS 14:04:44 perhaps we can work out the kinks with integration while he is away 14:05:13 SridarK, sorry. I couldn't rebase his patch last week. 14:05:35 SridarK, Maybe it is necessary to migrate neutron-lib for some constant value. 14:05:50 yushiro: no worries - i got busy this week too 14:06:03 yushiro: lets talk maybe tomorrow or on Wed 14:06:10 Yes. 14:06:39 we can attempt a plugin - L2Agent - Driver integration 14:06:47 and then add in Horizon 14:07:44 OK 14:08:01 cool! 14:08:24 for neutron-lib , well, http://logs.openstack.org/16/443416/8/check/gate-networking-midonet-python27-ubuntu-xenial/ef6756c/console.html is still failing 14:08:24 In l2 part, sorry I couldn't work last week. 14:08:59 reedip_, thank you so much for working about this !! 14:09:03 reedip_, will take a look 14:09:21 yushiro : well but I am not able to get midonet working with current fwaas 14:09:42 ok, so revert until we know what’s up? 14:10:09 is this a issue about the extension name vs the service plugin name? Not sure it is related to L2-support. 14:10:15 yes, that would be better 14:10:24 separate topic? 14:10:34 can you give us the link again and I will +2 right away 14:10:37 amotoki : yes, extension name vs service plugin name for neutron-lib migration 14:10:55 https://review.openstack.org/471699 14:11:02 amotoki, separate topic. it relates neutron-lib migration. 14:11:12 xgerman_ , SridarK ^^ 14:11:23 so you can't break the existing implementation. if you cannot fix it soon, it looks better to revert it. 14:11:31 yushiro , you also please +2 it so that we can revert it for now 14:11:38 amotoki : agreed 14:11:39 reedip_: ok 14:11:41 reedip_, OK, +2 now 14:11:51 aha, reedip_ could you paste a link ? 14:11:57 feel free to ping once you all are fine. 14:12:02 i can approve it. 14:12:07 yushiro : Patch for review : https://review.openstack.org/471699 14:12:35 sorry. it is neutron-fwaas patch. 14:13:01 done done :) 14:13:51 reedip_: thanks for working thru things 14:14:04 reedip_: lets continue forward so we can get this back 14:14:09 reedip_, Yes, thank you!! 14:14:19 SridarK : yep 14:14:32 I will take it up again once the revert is merged 14:14:43 reedip_: lets discuss more when we are on that topic 14:14:52 Sure 14:15:00 SridarK +1 14:15:18 #link https://review.openstack.org/#/c/425769/ 14:15:56 Default fwg, I was got a comment from yamamoto. I'll reflect his comment in this week. 14:16:14 I'll refer security group implementation. 14:16:51 Ok, let's move on. 14:17:02 Next, Neutron-lib adoption: https://review.openstack.org/#/c/421472/ / https://review.openstack.org/456511 14:18:56 you know the update 14:19:03 :) 14:19:08 yeah 14:19:12 So, 14:19:16 nothing else to add, so moving on ? 14:19:22 OK. 14:19:24 move on. 14:20:05 Next, Horizon support: https://review.openstack.org/#/c/475840/ 14:20:09 reedip_: lets set some time for debugging 14:20:26 hi all.. I missed out to checkin one fine 14:20:27 perhaps we can combine some time for L2 integ and neutron-lib 14:20:34 Wed or later 14:20:40 SridarK : let me know when you , xgerman_ and yushiro are free 14:20:43 thanks amotoki for pointing it out 14:20:44 sorry back to topic 14:20:45 it looks better to discuss horizon support as a dedicate topic 14:20:47 Thu seems fine from my side 14:21:04 yeah, I am around most of the time 14:21:11 cool 14:21:37 amotoki.. I will be checking in the api/fwaas_v2.py file now 14:21:47 please take a look 14:22:05 is there any other topic on Pike other than horizon ? 14:22:15 i think #topic horizon is better 14:22:29 ah, OK, change the topic. 14:22:38 #topic horizon 14:22:53 cool.. 14:23:02 sarathmekala__, Ok, please go ahead :) 14:23:08 as you may know, neutron-fwaas-dashboard repo has been setup. 14:23:34 sarathmekala__ already proposed a patch of fwaas v2 support 14:23:39 amotoki: thanks 14:23:49 before moving on, i have several things to be announced. 14:24:02 the first thing is the repository setup. 14:24:15 the core team is neutron-fwaas-core + horizon-core at now. 14:24:38 second, it is now a part of neutron stadium. the governance patch was approved today. 14:24:46 https://governance.openstack.org/tc/reference/projects/neutron.html 14:25:01 you can see neutron-fwaas-dashboard here. 14:25:22 Yeah!! 14:25:25 third, fwaas v1 dashboard split out are almost done. 14:26:20 thank you for telling us. That's a good news. 14:26:25 as part of the initial effort, i self-approved my several patches, but I would like you all to check the final one https://review.openstack.org/476413 to confirm it works well. 14:26:43 amotoki dashboard doesn’t have any tags - is that intentional? 14:26:48 so is this the recommended way of adding horizon support for neutron stadium projects now? use a separate repo for the project's horizon? 14:26:57 yep 14:27:18 answering one by one 14:27:38 xgerman_: we can update the tag(s) once it is setup properly. 14:27:59 xgerman_: I intentionally added no explicit tag in the first inclusion patch. 14:28:06 ok, I think we need a few of them to be considered for. a release 14:28:22 xgerman_: i think it is better to be discussed as a community like here. 14:29:55 igordcard: most horizon support for advanced services (expcet the main horizon repo) will be implemented in separate repos and it will be part of neutron stadium 14:30:20 we did the same thing for neutron-lbaas-dashboard (now it is under octavia though) 14:30:23 amotoki: thanks 14:30:39 features in the main neutron repo will go to the main horizon repo. 14:31:07 that's all from me on the dashboard repo. 14:31:18 sarathmekala__: now your turn :) 14:31:19 amotoki, thanks!! 14:31:51 amotoki.. thanks for your comment 14:31:54 we should probably keep an eye on the tags. My understanding is fuzzy but I knoew there are ramnification when it comes to releasing 14:32:09 I have missed out that file... will add it to the review 14:32:30 I have one question 14:32:47 OK 14:32:51 sarathmekala__: go ahead 14:32:58 if we follow the procedure mentioned in https://review.openstack.org/#/c/476413/ it will work for V2 as well right 14:33:31 i meant the dashboard part 14:33:50 enable_plugin neutron-fwaas-dashboard https://git.openstack.org/openstack/neutron-fwaas-dashboard <> 14:34:11 sarathmekala__: you need to update devstack/plugin.sh to enable neutron-fwaas-v2-dashboard. 14:34:30 sarathmekala__: at now, fwaas v1 and v2 are exclusive. 14:35:00 ok.. thanks.. I will check that code 14:35:07 sarathmekala__: looking at https://github.com/openstack/neutron-fwaas-dashboard/tree/master/devstack i think you can know what we need to do. 14:35:27 sarathmekala__: feel free to ping me if you have questions. 14:35:38 cool.. thanks 14:36:40 if no more questions or topics, i think we can move on. 14:36:42 sarathmekala__: u can follow a similar model for v2 vs v1 as in basic devstack setup 14:37:07 thanks SridarK, I figured out the same :) 14:37:09 amotoki: thx for helping out on this 14:37:35 +1 14:37:44 you're welcome. i hope you sometimes all check -dashboard 14:37:49 +100 14:37:52 *reviews 14:38:08 +1 14:38:27 Sure +1 14:38:56 thats it from my side.. yushiro please move on 14:39:15 sarathmekala__, OK, thanks. 14:39:36 #topic Stadium Compliance 14:40:05 anything else to discuss? 14:40:09 neutron-lib needs to be re-published 14:40:36 and fullstack tests have been expermintally enabled but are failing because they are accessing a wrong folder in gate. Need to relook at it 14:40:55 Once fullstack is done, then atleast we can check that out of the To-Do list 14:41:25 reedip_, thank you. 14:41:55 for neutron-lib, once the revert merges, I will incrementally make the same changes as done in the earlier patch and watch out for the midonet tests 14:42:14 I hope @yamamoto enables the tests in midonet though, they disabled them earlier 14:42:21 reedip_: ok hopefully with this and once we are able to fix things to undo the revert - we are all done 14:42:36 SridarK : Need to check the FwaaS report once 14:42:47 reedip_: yes and also long term - we need to be able to integrate with Midonet CI 14:42:49 It would have the To-Do items 14:43:13 unfortunately there is no easy way for us to know that we could have broken something in Midonet 14:43:24 :-( 14:43:29 hmm, yes.. 14:43:56 we need to work with yamamoto and fix that so we dont go thru this cycle again 14:43:58 Well, thats true 14:44:07 yes SridarK 14:44:38 midonet job (non-voting?) for fwaas patches? (if we really need it) 14:44:38 i am sure we can find some way for a solution 14:44:53 yes that would be a good start 14:45:16 amotoki : we can have that , but need to see how to enable the same in gate 14:45:41 i think yamamoto is glad to help you 14:46:25 amotoki: +1 i am sure we can find some thing quick with yamamoto's help 14:46:27 midonet runs their CI using openstack-ci so it is relatively simple. it can be done just by a project-config update 14:47:17 ok that should make things simple 14:47:37 hmm, lets have a look and put up a NV job if possible 14:47:53 +1 14:48:01 Yes, it's useful for us to trigger fwaas patch with networking-midonet 14:49:13 shall we move on ? 14:49:14 hi 14:49:25 OK. 14:49:29 #topic performance improvement 14:49:45 hoangcx_, anything else to mention? 14:50:11 if you let me know what exactly you want to run in the nv job, i can submit a patch. 14:50:21 o/ 14:52:18 Ok 14:52:26 8 minutes left. 14:52:28 #topic Open Discussion 14:52:37 yamamoto: thx 14:52:46 yamamoto, thank you 14:52:55 np. thank you for taking care of midonet. 14:52:59 SridarK, yushiro, xgerman_ we can have the meeting on Thursday 0200 UTC ( same time ) 14:53:15 yamamoto: yes will be good to see what would be the minimal set of things as u see fit so we dont break midonet in the future 14:53:35 at least if we see anything we can quickly check back with u 14:53:57 reedip_, yes, sure. 14:54:10 reedip_: thx that works, 24 hrs before is also fine 14:54:20 are you changing the meeting time? 14:54:42 amotoki: not for this mtg - we were just setting a time to debug some things 14:54:46 amotoki : no, we are setting up a time for some of the open issues to be handled 14:54:57 SridarK: reedip_: i see, thanks 14:54:59 reedip_, in #openstack-fwaas is OK? 14:55:06 yes 14:55:06 meeting point will be neutron-fwaas, as always 14:55:13 yushiro : yes 14:55:20 OK 14:56:04 btw, i am planning to setup gerrit bot which post comments to #-fwaas when a fwaas or fwaas-dashboard patch is posted. 14:56:18 does it sounds good for you or sound annoying? 14:56:23 amotoki : yes, that works ... we generally miss the patches otherwise 14:56:28 amotoki, +1 14:56:39 it is useful for us. 14:56:50 but I would like the cores to vote on that :) 14:57:13 +1 14:57:14 agreed 14:57:41 thanks. I will propose a project-config change and add the cores to reviews 14:58:02 +1 14:58:09 btw igordcard wanted to mention that the Common Classifier Framework has merged : https://review.openstack.org/#/c/333993/ 14:58:27 yep, thanks reedip_ ! 14:58:33 igordcard : if you have anything to add, go ahead 14:58:40 wow, congrats!! igordcard 14:58:58 the spec merged 10 days ago, I believe we've reached a good enough consensus there 14:59:06 a first batch of code will be submitted before pike-3 14:59:23 to the neutron-classifier repo: https://review.openstack.org/#/q/project:openstack/neutron-classifier 14:59:24 +1 igordcard 14:59:33 igordcard: is it targeted for Queen release? 14:59:57 igordcard: anyway it will be helpful to start relevant reviews! 15:00:04 and consuming services, potentially fwaas can start to look at how to consume the CCF after that initial batch of code 15:00:14 times up guys :) 15:00:21 wow, 0:00 15:00:30 #endmeeting