#opnfv-ovsnfv: Weekly Open vSwitch for NFV meeting (January 4th 2015)

Meeting summary

1. 1. https://etherpad.opnfv.org/p/ovsnfv-meet (mdgray, 13:06:09)
   
   
2. Roll Call (mdgray, 13:06:15)
   1. Mark Gray (mdgray, 13:06:22)
   2. Tom Herbert (tfherbert, 13:06:34)
   3. Billy O'Mahony (billyoma, 13:06:40)
   4. Yuki Kasuya (YukiKasuya, 13:07:26)
   5. Larry Lamers (ljlamers_, 13:09:58)
   
   
3. Documentation (mdgray, 13:10:27)
   1. Documentation freeze coming up on the 19th January (mdgray, 13:10:38)
   2. https://wiki.opnfv.org/documentation (mdgray, 13:11:00)
   3. https://wiki.opnfv.org/documentation/configguide (mdgray, 13:11:14)
   4. We need to update the documentation for Brahmaputra. (mdgray, 13:12:26)
   5. At the least we need to give documentation for how to deploy. (mdgray, 13:13:27)
   6. Tom brought up the need for an NSH-enabled rpm to allow deployment of SFC on Apex (mdgray, 13:25:19)
   7. Previously we had agreed to not fork OVS. (mdgray, 13:25:47)
   8. Suggestion was made to add scripts in ovsnfv repo that would allow a third-party (e.g. another project) to make a change to OVS (e.g. a patch) and then test it against all OVSNFV test cases. (mdgray, 13:26:52)
   9. In this way, the OVSNFV project will not maintain any forked code but any project (including the OVSNFV project itself) could make changes to OVS and deploy and test those changes in an OPNFV environment. (mdgray, 13:28:14)
   10. Tom will look at making his scripts generic like this. (mdgray, 13:28:27)
   11. Argument needed in build script so RPM will be built with external patches. (tfherbert, 13:29:04)
   12. As much as possible, the goal should be that no forked code or forked binary should be present in our repo (mdgray, 13:29:53)
   13. Converge on a single build script for an rpm. (mdgray, 13:31:05)
   14. Back to documentation. If we don't document what we are doing it wont be visible outside this call (mdgray, 13:33:34)
   
   
4. Release E milestone (mdgray, 13:33:49)
   1. https://wiki.opnfv.org/releases/brahmaputra/release_plan/ovsnfv_milestone_e_report (mdgray, 13:34:26)
   2. This closes tomorrow. Debra is looking for updates. (mdgray, 13:34:40)
   3. Daniel Smith brought up FuncTest and clarified that he expects that to run FuncTest after a deploy, it should be reasonably trivial - Famous last words :) (mdgray, 13:42:22)
   4. Dan Smith suggested setting up CI pipeline even if it fails. (mdgray, 13:42:44)
   5. Some work has been done on this. (mdgray, 13:42:52)
   6. https://gerrit.opnfv.org/gerrit/#/c/5147/ (mdgray, 13:43:06)
   7. Dan's feedback on this would be welcome. (mdgray, 13:44:25)
   
   
5. Fuel development update (mdgray, 13:50:19)
   1. *Fuel* is in a good place. However, our puppet modules aren't working correctly. OVS is getting installed correctly but things aren't getting started correctly (mdgray, 13:53:44)
   2. Dan suggested just doing a reboot. Dan will send instructions for how to do this. (mdgray, 13:54:10)
   
   
6. RPM development update (mdgray, 13:58:38)
   1. RPMs are in artifacts and the daily builds are working (mdgray, 13:58:53)
   2. We mustn't forget about Fuel projects Work Packages: (billyoma, 13:59:40)
   3. http://artifacts.opnfv.org/ovsnfv//opnfv-2016-01-04-openvswitch-debuginfo-2.5.90-1.x86_64.rpm (tfherbert, 14:00:17)
   4. (billyoma, 14:01:26)
   5. Two more important milestones for you to follow: (billyoma, 14:01:31)
   6. Two more important milestones for you to follow: (billyoma, 14:02:19)
   7. 1) WP4 due Jan 15: Hard code freeze, rebase to Fuel 8, and Liberty. We will help you on this as long as you Own the task (billyoma, 14:02:19)
   8. 2) After WP4 January 15, stabelizing, testning and support to releng, functest and yardstick - we will have Frequent stabelization gating meetings from WP4 until release. (billyoma, 14:02:19)
   9. 3) Feb 2 - release date (billyoma, 14:02:19)

Action items

1. (none)

People present (lines said)

1. mdgray (34)
2. billyoma (12)
3. collabot` (3)
4. tfherbert (3)
5. YukiKasuya (1)
6. ljlamers_ (1)