14:02:45 <[1]JonasB> #startmeeting weekly fuel meeting 14:02:45 <collabot> Meeting started Thu Jun 18 14:02:45 2015 UTC. The chair is [1]JonasB. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:45 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 14:02:45 <collabot> The meeting name has been set to 'weekly_fuel_meeting' 14:02:52 <[1]JonasB> #info Jonas Bjurel 14:02:56 <szilard> #info Szilard Cserey 14:02:56 <mskalski> #info Michal Skalski 14:03:34 <[1]JonasB> There will not be so many this week, Stefan and Daniel are ill 14:03:46 <etualuo> #info Tuan Luong 14:04:21 <szilard> I wish them fast recovery 14:05:42 <[1]JonasB> Welcome Tuan 14:06:01 <etualuo> Good to be here 14:06:03 <etualuo> :) 14:06:25 <[1]JonasB> So for today - I think we should discuss Autodeploy, ODL and the ODL pres./Demo Anything more? 14:07:03 <szilard> that's seems a good plan 14:07:05 <[1]JonasB> #topic CI Autodeploy in LF1 14:07:14 <[1]JonasB> Szilard - shoot 14:07:36 <szilard> #info I'm updating ci/deploy.sh so it can call deploy.py python file 14:07:57 <szilard> #info almost ready just have to push the patch and review with the help of Faith 14:08:08 <szilard> sorry Fatih 14:08:29 <[1]JonasB> #info Have you cherry-picked the patches for Arno/Stable? 14:08:38 <szilard> #info I also pushed another patch, to be able to get the exit status 14:09:05 <szilard> #info yes I did exactly as Arnaud suggested, so thanks a lot Arnaud for the review help 14:09:31 <szilard> #info it's so good to have others helping in the review process 14:10:18 <szilard> #info I'm also planning to convert everything to Ansible 14:10:41 <[1]JonasB> #Szilard, thanks for a great work done! 14:10:42 <szilard> #info now that everything is in Python, we have to restructure it into Ansible modules and write Ansible playbook 14:11:19 <[1]JonasB> #info lets discuss the priorities next week :-) 14:11:28 <[1]JonasB> Should we go on to ODL 14:11:31 <szilard> welcome :) I'm also grateful for Stefan's leading and showing the way to write the autodeployment app 14:11:56 <[1]JonasB> #topic ODL integration and Demo 14:11:56 <szilard> I just followed what Stefan invented, so I'm also grateful to him 14:12:11 <mskalski> hi 14:12:13 <[1]JonasB> Michal.... 14:12:15 <mskalski> #info We got a repo on stackforge for plugin code: 14:12:23 <mskalski> #link https://github.com/stackforge/fuel-plugin-opendaylight 14:12:32 <mskalski> I will move plugin code there 14:12:32 <[1]JonasB> cool 14:12:47 <mskalski> #info I will prepare a short demo on 25.06 of fuel 6.1 and ODL plugin - this will be on webex, I or Szymon will send invitation tommorow 14:13:20 <mskalski> Regarding plugin development, not only north-south but also east-west l3 require new driver for neutron which is not present in juno 14:13:32 <mskalski> but if we leave br-floating bridge on controller nodes communication between tenants networks is possible 14:13:47 <mskalski> moreover if I find a way to add one flow on br-floating through ODL the north-south is also possible - by using neutron agent 14:14:38 <[1]JonasB> Sounds like a plan! 14:15:19 <szilard> what's the best way to hold demo's here in OPNFV, I see people using different technologies 14:15:39 <[1]JonasB> So I have met with the sevice function chaining project. They are very open for tight cooperation with our team. 14:16:17 <szilard> sounds interesting 14:16:46 <[1]JonasB> I think it would be a great opportunity to work with Brady Johnsson and the SFC team to learn more on ODL, and have them starting of based on the ODL work Daniel and Michal has done 14:16:47 <szilard> service function chaining - what's the codename 14:17:40 <[1]JonasB> No code name 14:17:51 <mskalski> does this team have a page on opnfv wiki? 14:18:00 <[1]JonasB> They have their first kickoff meeting 4PM CET next wed. 14:18:09 <[1]JonasB> #link https://wiki.opnfv.org/meetings?&#service_function_chaining_sfc_project_team_meeting 14:18:20 <szilard> Thanks 14:18:47 <mskalski> [1]JonasB: What they will do? 14:20:12 <[1]JonasB> mskalski: They will use ODL as the controller to classify and steer flows through a pipeline of applications. 14:20:35 <mskalski> [1]JonasB: ok, thanks 14:22:07 <[1]JonasB> E.g. Steer flows wich have been classified containing a http-get through a chain containing a firewall, a DPI, a rate limiter,.... While other flows are directly forwarded to the destination. 14:23:33 <[1]JonasB> mskalski: Whats the limitation in number of users for the webex bridge you're setting up? 14:23:59 <mskalski> [1]JonasB: no I think there is no limit 14:24:30 <[1]JonasB> mskalski: Good, then I can send out a broader invitation inside Ericsson 14:25:05 <[1]JonasB> Anything more to discuss today? 14:25:08 <mskalski> [1]JonasB: btw session will be probably recorded for offline view 14:25:31 <[1]JonasB> mskalski: Ok, better to point them to the recordings then. 14:26:11 <[1]JonasB> 3 14:26:24 <[1]JonasB> 2 14:26:35 <[1]JonasB> 1 14:26:52 <[1]JonasB> Thanks ecerybody 14:26:57 <[1]JonasB> #endmeeting