Differences

This shows you the differences between two versions of the page.

--- releases:brahmaputra:daily_status [2016/02/04 21:30]
Debra Scott old revision restored (2016/02/04 05:11)
+++ releases:brahmaputra:daily_status [2016/02/25 05:20] (current)
Debra Scott
@@ Line 1: / Line 1: @@
-**2/3/16**
+**2/24/16**
-Countdown to Release: **TBD days**
+Countdown to Release: **1 days**
-[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] under revision with proposed milestones dates until we work out details. TCS approved release delay but chose to wait one more week before setting date in hopes that by then some issues will be resolved allowing for better estimations of time; Etherpad currently proposed release date is 3/8; we also have a matrix of the scenarios and their pass/fail/stable status
-**===============================================================================================================**
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-24-14.30.html|2/24/16]]
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-03-14.30.html|2/3/16]]
 __**Top Accomplishments & Important Updates since last report**__
-.Excellent progress by test teams today
+The team is actively finalizing documentation and tagging artifacts for release with target completion Thursday morning Pacific Time.
-.ARMband project unfortunately did not meet freeze and is therefore dropped from this release
-.Functest becoming more stable on scenarios that it has been able to run.
+As of 21:15 Pacific Time (05:15 UTC) we have 15 projects reporting they are complete with tagging, 6 projects reporting "in process" and 12 "waiting for report of status".
-.Yardstick
-       -odl sceanrios - same problems on ping and ssh
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-       -works for ONOS (Compass) and nosdn (Compass and Fuel7) - need to retest fro fuel8
+**2/23/16**
-       -on-demand tests (not CI PODs) - HA, KVM - works
-       -Parser test case OK (will be run on weekly)
-       -vTC verified daily and weekly on Ericsson POD1
-       -ipv6 test case runs on Compass Huawei SC POD
-       -working on bug fixes, docs and troubleshooting
+Countdown to Release: **2 days**
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] TSC agreed upon a phased release with primary release date of 2/25/16. All scenarios that are stable and tested ready to release on that date will be released. Any currently in-plan scenarios that are not ready on 2/25/16 will be allowed to join a follow-on release on March 28th; if deemed necessary a 3rd release could follow in late-April
+**===============================================================================================================**
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-23-14.30.html|2/23/16]]
- **===============================================================================================================**
+__**Top Accomplishments & Important Updates since last report**__
+.Troubleshooting of scenarios is frozen. Final updates of documentation is in progress. PTLs will then review the documentation, and the branch will be tagged for release on Thursday Feb 25.
-__**Top Issues**__
+.Clarification of release as it affects projects and scenarios that have not fully passed testing:
+With TSC discussion it was agreed that, because we do not cut anything out of the released bits even if a scenario or feature has not completely passed validation, we will document the status of all scenarios and features whether fully passed validation, passed with known limitations or bugs, or not yet tested.
-**Issue:** have release date. Test cycles for each scenario take a significant amount of time. Even if all installers & scenarios are working properly it takes 7 days to run test through them all.
+The following projects do not have a passing scenario that supports them and therefore will <del>not be supported in</del> will be documented in accordance with whatever testing status they achieved and/or known limitations or known bugs for the first release of Brahmaputra: NFVOVS, KVM4NFV, SFC, BGP-VPN, Doctor. All are highly likely to make full validation at the second release of Brahmaputra or if needed, in the third release of Brahmaputra in late April.
-**Owner:** Debra
-**Status:** TSC voted to delay release rather than trying to phase release. Debra & key community members to identify remaining work and develop reasonably accurate schedule to propose to TSC. Current estimate is Mar 7 release
-**Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
+SFC, Doctor, and Joid (one scenario) were able to get patches in prior to the Sunday troubleshooting freeze and are attempting to complete additional testing prior to Thursday release. This affects test teams and documentation (minor at most).
-**Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
-**Status:** .regression on Tempest suite (investigation to knwo if it is in Functest or upstream)
-            .functest: vPing and vIMS OK on Apex now
-            .tables up to date and graphs reflect the results in real time
-            .Scenarios run at least once: nodsn, odl_l2, onos and odl_l3 for apex and fuel some time ago
-       -for nosdn, the results are good (we are just testing OpenStack..)
-       -for odl_l2 and onos we start getting stable scenario but need more run to have significant trend
-       -for odl_l3 just few runs so difficult to have a clear view
+.Majority of projects are now working toward fix & stabilization of scenarios for the 2nd Brahmaputra release (scenario additions)
+**===============================================================================================================**
-Yardstick:   -odl sceanrios - same problems on ping and ssh
+__**Top Issues**__
-                  works for ONOS (Compass) and nosdn (Compass and Fuel7) - need to retest for fuel8
+**Issue:** Determining process for tagging the release that takes into account the change (larger number of projects) and the additional phase/s of the Brahmaputra Release compared to Arno
-                  -vTC verified daily and weekly on Ericsson POD1
+**Owner:**Debra, Uli, Aric
-                  -working on bug fixes, docs and troubleshooting
+**Status:**Assigned 2/23. Must be closed 2/24.
-                  -on-demand tests (not CI PODs) - HA, KVM - works
-                  -Parser test case OK (will be run on weekly)
-             -working on bug fixes, docs and troubleshooting
-**Issue:** Getting RC0 out
-**Owner:** Debra
-**Status:**  Closed, we have reached code freeze
-**Issue:** Fuel is not ready to code freeze. Upstream Fuel is not stable.
-**Owner:** Jonas Bjurel
-**Status:** Closed, Fuel reached release
-**Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
-**Owner:** Ray Paik
-**Status:**Scott discussed status during TSC meeting; Chris to post instructions online for license inclusion
-**Issue:** OpenContrail does not deploy
-**Owner:** Stuart Mackey
-**Status:** Resolved
-**Issue:** Scenarios are frozen, but significant number not working yet, or have not been tried
-**Owner:** test teams
-**Status:** Validating OpenContrail scenarios in Compass & JOID in preparation for code freeze tomorrow.
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
-**Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
-**Owner:**Don Dugger/Raghuveer Reddy
-**Status:** 1/22 no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
 **===============================================================================================================**
 __**Pod Status:**__
-Inconsistent reports of pods being down. Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
 [[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
+All pods are currently working and in use. LF Pod 3 is up and running. Yardstick requests that this pod remain reserved for troubleshooting Yardstick for at least the next 2 weeks.
+Intel pod5 is giving bad results for functest, some tests take too much for some reason we don't know. Requesting that Orange Pod could be Pharos approved pod for testing purposes
 **===============================================================================================================**
 **Scenario Status:**
-Apex: 5 scenarios on Jenkins: 4 work from deploy point of view odl_l2 is about 90 pass/10 fail, odl_l3 worse pass rate Not successfully deployed yet: ocl- working on it
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
-Compass: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl. From deployment point of view, 3 working, 1 not. Deployed successfully: openstack, odl_l2, onos. Once test has verified plugin is working will add ocl scenarios back in on wiki...
+Scenarios which are stable across installers are:
+- apex/odl_l2
+- compass/odl_l2
+- compass/onos
+- compass-nosdn
+- fuel/nosdn
+- fuel/old_l2
+- fuel/onos
-Fuel: Fuel@OPNF in general seems to be in a pretty good shape.
+The following scenarios were not stabilized by the troubleshooting freeze and are moved to second Brahmaputra release or later. Joid/odl_l2 is attempting to complete additional test runs before Thursday release in order to be documented as a working scenario. If successful it will be removed from this list and added to the list above:
-o It is fairly coherent and stable!
+-apex/odl_l3-ha
-o All plugins/features/scenarios (except one which I expect tomorrow) have been merged
+-apex/onos-ha
-o Since Fuel upstream is not released yet, rebasing is needed from time to time
+-apex/odl_l2-sfc
-(not really problematic)
+-apex/ocl-nofeature-ha
-o Build system is in good shape
+-compass/ocl-nofeature-ha
-o Deploy system is in good shape
+-fuel/odl-l3-ha
-o Building, deploying and smoke-test fine in our internal labs
+-fuel/odl_l2-bgpvpn-noha
+-fuel/nosdn-kvm-ha
+-fuel/nosdn-ovs_kvm-ha
+-joid/nosdn-nofeature
+-joid/odl_l2-ha
+-joid/onos-ha
+-joid/ocl-nofeature-ha
--          Issues:
-o Configuration issues with CI-deploy, probably not a CI-issue but rather a Fuel8
-   configuration issue. We will put all the manpower on this after the freeze, and
-   should be resolved on Monday latest.
-o ONOS L3 scenario for external connectivity requires an exemption as it’s requirements
-   are not fully compatible with all of the labs (Pharos)! We will work on that next week.
--          Plan for the coming 24 hours:
-o Tomorrow we cherry-pick all patches from master (related to B-release) to stable, expect
-   some intermediate flux in build/verify/merge results!
-o From this point – strict cherry-picking policies will apply, policed by Jonas.
-Joid: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl. From deployment point of view, 3 working, 1 not activated/attempted yet. Deployed successfully: openstack, odl_l2, onos. Not successfully deployed yet: none. Once ocl scenario is validated in CI will add it back into wiki for this installer
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)  can report status but there were no PODs available for tests yesterday...and most of the scenario have not been run, or run once several days ago so it is not easy to report you something that really makes sense...
+Functest (Jose Lausuch)
-the scenario are probaly amost good the wiki (very difficult to maintain on a wiki)
+.updated https://wiki.opnfv.org/functextnexttaks
-- https://wiki.opnfv.org/vping_brahmaputra_page
-- https://wiki.opnfv.org/odl_brahmaputra_page
-- https://wiki.opnfv.org/onos_brahmaputra_page
-- https://wiki.opnfv.org/tempest_brahmaputra_page
-- https://wiki.opnfv.org/vims_brahmaputra_page
-the most realistic results are provided by the dashboard as it is directly reflecting the results pushed in CI..(they are crual but they do not lie...:))
+Yardstick (Ana Cuna):
-here the view per POD assuming that opnfv-jump-1=apex, huawei-us=compass, opnfv-jump-2=fuel, intel-pod5=joid
+.We noticed data coming in the dashboard: http://130.211.154.108/grafana/dashboard/db/yardstick-main
+.Notice dashboard is not ready, work in progress (use opnfv/opnfv if you want to see the data)
+.sign up or use opnfv/opnfv to view
-Yardstick:ONOS - reviewing open patches in yardstick repo to prepare for code freeze. ODL scenario troubleshooting in. Some docs ready - not all yet
 **===============================================================================================================**
 __**Installer Status:**__
-**Apex** (Tim Rozet):  need second pod in infrastucture
+**Apex** (Tim Rozet):
@@ Line 140: / Line 99: @@
 **Compass4nfv** (Weidong Shao)
+.Please refer to https://etherpad.opnfv.org/p/Compass4nfv_brahmaputra_status
 **Fuel** (Jonas Bjurel)
 [[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
 **===============================================================================================================**
 __**Project Updates:**__ (as provided)
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
-**Availability：**（Qiao Fu) All documents freezed and are in the stable Brahmaputure brance.
+**Availability：**（Qiao Fu)
 **Bottlenecks:** (Hongbo Tian)
@@ Line 158: / Line 120: @@
 **HA**(Fu Qaio)
 **IPv6:** (Bin Hu) -
 **NFV4KVM:** (Don Dugger, Raghuveer Reddy)
 **ONOSFW:** (Ashlee Young)
@@ Line 169: / Line 130: @@
 **OPNFVdocs** (Chris Price)
+Held a meeting today with project documentation leads. Documents are largely in place waiting final reviews. Test projects are documenting results. All projects that have not previously done so are finalizing release notes.
 **OVNO** (Stuart Mackie)
 **Parser**
+**Promise** (Gerald Kunzmann)
 **Prediction** (Hai Liu)
@@ Line 191: / Line 156: @@
 **Action Items**__Underlined Text__
 **Action:**
 **Owner:**
 **Status:**
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------**2/22/16**
+Countdown to Release: **3 days**
-**1/26/16**
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] TSC agreed upon a phased release with primary release date of 2/25/16. All scenarios that are stable and tested ready to release on that date will be released. Any currently in-plan scenarios that are not ready on 2/25/16 will be allowed to join a follow-on release on March 28th; if deemed necessary a 3rd release could follow in late-April
-Countdown to Release: **TBD days**
-[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]]
 **===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-26-14.30.html|1/26/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-22-14.30.html|2/22/16]]
 __**Top Accomplishments & Important Updates since last report**__
+.Troubleshooting of scenarios is frozen. Final updates of documentation is in progress. PTLs will then review the documentation, and the branch will be tagged for release on Thursday Feb 25.
-.TSC voted to move code freeze to Friday 1/29 and to extend release date (to be defined). Debra and key community members to evaluate remaining work and recommend new release date with solid schedule to achieve that.
+.The following scenarios passed functest and yardstick criteria before the troubleshooting freeze:
+- apex/odl_l2
+- compass/odl_l2
+- compass/onos
+- compass-nosdn
+- fuel/nosdn
+- fuel/old_l2
+- fuel/onos
+The following projects do not have a passing scenario that supports them and therefore will not be supported in the first release of Brahmaputra: NFVOVS, KVM4NFV, SFC, BGP-VPN, Doctor. All are highly likely to make the second release of Brahmaputra in late March.
- **===============================================================================================================**
+**===============================================================================================================**
 __**Top Issues**__
-**Issue:** We are at high risk of missing release date. Test cycles for each scenario take a significant amount of time. Even if all installers & scenarios are working properly it takes 7 days to run test through them all.
-**Owner:** Debra
-**Status:** TSC voted to delay release rather than trying to phase release. Debra & key community members to identify remaining work and develop reasonably accurate schedule to propose to TSC.
-**Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
-**Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
-**Status:**
-Yardstick:ONOS - successfully run with Compass. ODL scenario - debugging on-going, Yardstick will not run with ODL. Narrowing down subsystems involved. Working on SFC test cases. Working on influxdB+grafana
-**Issue:** Getting RC0 out
-**Owner:** Debra
-**Status:**  Installer code freeze extended due to Fuel trying to stabilize with upstream. Compass also troubleshooting some functest and other instability with the code base, need some extra time in getting Compass code stable. Apex, JOID ready to freeze
-**Issue:** Fuel is not ready to code freeze. Upstream Fuel is not stable.
-**Owner:** Jonas Bjurel
-**Status:** autodeploy issue, hopefully solved now. Testing. Scenarios being rebased
 **Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
 **Owner:** Ray Paik
-**Status:**Projects have made good progress on getting patches in to fix the files. Scott is making another license scan to see what if anything is outstanding. Thank you to all who have responded to this request in such a timely manner.
+**Status:**closed. Received approval through board vote to allow a few projects to use non-Apache licenses  (KVMFORNFV, ONOSFW, and VSWITCHPERF (with a single file with non-Apache-2.0 license).
-**Issue:** OpenContrail does not deploy
-**Owner:** Stuart Mackey
-**Status:** Apex still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
-**Issue:** Scenarios are frozen, but several not working yet, or have not been tried
-**Owner:** test teams
-**Status:**  Next step is creating Jenkins jobs and testing each scenario. In process with test teams leading. [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** 1/22 no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** Closed. Pushed to 2nd Brahmaputra release in late March. From Fuel team: This project is focusing on yardstick SLA test-cases aside of a true deployment (using bridges instead of OVS). They install a new kernel for which tere is no OVS kernel driver in the packages. All though they’re working on it. I’m not sure they will make it for our time plan – not even sure we need to wait for it since it is as a “technology project” verified by yardstick, but not yet deploying in a real environment. I would vote this to included in SR1 of Fuel@OPNFV B-release.
 **===============================================================================================================**
 __**Pod Status:**__
-All pods up and running
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
 [[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
-**===============================================================================================================**
+All pods are currently working and in use. LF Pod 3 is up and running. Yardstick requests that this pod remain reserved for troubleshooting Yardstick for at least the next 2 weeks.
-**Scenario Status:** Scenarios are frozen. No feature project has reported that their scenarios are missing or unsupported. Candidate scenarios are having Jenkins jobs created for them. Test teams troubleshooting scenarios and test software.
-Reviewed scenarios in table and noted those that will not be implemented this release
-Apex: 5 scenarios on Jenkins: 4 work from deploy point of view odl_l2 is about 90 pass/10 fail, odl_l3 worse pass rate Not successfully deployed yet: ocl- working on it
+Intel pod5 is giving bad results for functest, some tests take too much for some reason we don't know. Requesting that Orange Pod could be Pharos approved pod for testing purposes
-Compass: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl. From deployment point of view, 3 working, 1 not. Deployed successfully: openstack, odl_l2, onos. Not successfully deployed yet: ocl (removed from this installer)
+**===============================================================================================================**
+**Scenario Status:**
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
-Fuel: 8 scenarios on Jenkins: pure openstack, odl_l2, odl_l3, onos, bgpvpn, ovs, kvm, kvm_ovs. From deployment point of view, 5 working, 1 not working, 2 not activated/attempted yet. Deployed successfully: openstack, odl_l2, odl_l3, onos, bgpvpn Not successfully deployed yet: ovs. Not activated/attempted: kvm, kvm_ovs.
+Scenarios which are stable across installers are:
+- apex/odl_l2
+- compass/odl_l2
+- compass/onos
+- compass-nosdn
+- fuel/nosdn
+- fuel/old_l2
+- fuel/onos
-Fuel has Fuel7 on stable/brahmaputra branch and Fuel8 uplift work is WIP on master branch.
+The following scenarios were not stabilized by the troubleshooting freeze and are moved to second Brahmaputra release or later:
+-apex/odl_l3-ha
+-apex/onos-ha
+-apex/odl_l2-sfc
+-apex/ocl-nofeature-ha
+-compass/ocl-nofeature-ha
+-fuel/odl-l3-ha
+-fuel/odl_l2-bgpvpn-noha
+-fuel/nosdn-kvm-ha
+-fuel/nosdn-ovs_kvm-ha
+-joid/nosdn-nofeature
+-joid/odl_l2-ha
+-joid/onos-ha
+-joid/ocl-nofeature-ha
-Joid: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl. From deployment point of view, 3 working, 1 not activated/attempted yet. Deployed successfully: openstack, odl_l2, onos. Not successfully deployed yet: none. Not activated/attempted: ocl (removed from this installer)
+-joid/ocl-nofeature-ha
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)  Current situation
+Functest (Jose Lausuch)
+.updated https://wiki.opnfv.org/functextnexttaks
-Functest regression yesterday night due to sdnvpn integration, fixed now
+Yardstick (Ana Cuna):
-.vPing/SSH Ok on manual tests with compass, not working with all scenarios yet
+.We noticed data coming in the dashboard: http://130.211.154.108/grafana/dashboard/db/yardstick-main
-we defined 2 vPING: vPing SSH and vPing userdata/cloudinit
+.Notice dashboard is not ready, work in progress (use opnfv/opnfv if you want to see the data)
-https://wiki.opnfv.org/vping_brahmaputra_page
+.sign up or use opnfv/opnfv to view
-vPing/SSH should be OK now on compass (wait for next run). Table to be updated for apex as well I think
-http://testresults.opnfv.org/testapi/dashboard?project=functest&case=vPing&installer=apex and you can change the installer. wait for the test dashboard of LF...
-Yardstick (Ana Cunha)  first successful run with joid yesterday (os scenario),  writing for a patch for workaround for odl scenario - remains to be tested on the labs
-On-going work for grafana dashboard and documentation
-Started to document results for ha
 **===============================================================================================================**
 __**Installer Status:**__
-**Apex** (Tim Rozet):  Still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
+**Apex** (Tim Rozet):
-**JOID** (Narinder Gupta) JOID deployed successfully on all three labs yesterday including the virtual deployment. Unfortunately functest had some issues yesterday which seems to be resolved today.
+**JOID** (Narinder Gupta)
+**Compass4nfv** (Weidong Shao)
+.Please refer to https://etherpad.opnfv.org/p/Compass4nfv_brahmaputra_status
-**Compass4nfv** (Weidong Shao) there were some functest and other instability with the code base, and we will need some extra time in getting Compass code stable
 **Fuel** (Jonas Bjurel)
 [[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-)
-Struggling with an autodeploy issue, hopefully solved now. Testing. Scenarios being rebased
 **===============================================================================================================**
 __**Project Updates:**__ (as provided)
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
+**Availability：**（Qiao Fu)
-Scenario view status: Reviewed scenarios in table and noted those that will not be implemented this release
-Apex: 5 scenarios on Jenkins: 4 work from deploy point of view
-odl_l2 is about 90 pass/10 fail, odl_l3 worse pass rate
-Not successfully deployed yet: ocl- working on it
-Compass: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl.
-From deployment point of view, 3 working, 1 not.
-Deployed successfully: openstack, odl_l2, onos.
-Not successfully deployed yet: ocl (removed from this installer)
-Fuel: 8 scenarios on Jenkins: pure openstack, odl_l2, odl_l3, onos, bgpvpn, ovs, kvm, kvm_ovs.
-From deployment point of view, 5 working, 1 not working, 2 not activated/attempted yet.
-Deployed successfully: openstack, odl_l2, odl_l3, onos, bgpvpn
-Not successfully deployed yet: ovs.
-Not activated/attempted: kvm, kvm_ovs.
-Fuel has Fuel7 on stable/brahmaputra branch and Fuel8 uplift work is WIP on master branch.
-Joid: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl.
-From deployment point of view, 3 working, 1 not activated/attempted yet.
-Deployed successfully: openstack, odl_l2, onos.
-Not successfully deployed yet: none.
-Not activated/attempted: ocl (removed from this installer)
-**ARMband:**
-**Availability：**（Qiao Fu) HA project has got all the rst file merged and ready for release. Will upload a full set of rst file for the two release doc later today.
 **Bottlenecks:** (Hongbo Tian)
-**Copper:** (Bryan Sullivan) at risk
+**Copper:** (Bryan Sullivan)
 **Doctor** (Ryota, Ildiko)
-**IPv6:** (Bin Hu) -
+**HA**(Fu Qaio)
-**LSOAPI** (Kevin Leuhrs) at risk
+**IPv6:** (Bin Hu) -
 **NFV4KVM:** (Don Dugger, Raghuveer Reddy)
 **ONOSFW:** (Ashlee Young)
@@ Line 356: / Line 286: @@
 **OPNFVdocs** (Chris Price)
-Issues:
+Held a meeting today with project documentation leads. Documents are largely in place waiting final reviews. Test projects are documenting results. All projects that have not previously done so are finalizing release notes.
-Docs working on central content. Working with projects on project content.  Patches outstanding on many projects.
-Awaiting final scenario list to progress to completion. Working with projects on project content.  Patches outstanding on many projects. Unable to code freeze until installers freeze.
+**OVNO** (Stuart Mackie)
-ONOSFW reviewing reviewing onosfw docs. Projects are working on docs, some feature projects are waiting for the integration to be complete to document that for the config guide
-**OVNO** (Stuart Mackie) Apex still working on patch for plugin
 **Parser**
+**Promise** (Gerald Kunzmann)
 **Prediction** (Hai Liu)
@@ Line 382: / Line 312: @@
 **Action Items**__Underlined Text__
 **Action:**
 **Owner:**
 **Status:**
-**Action:**
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------**2/19/16**
-**Owner:**
-**Status:**
-__**Action:**__
-**Owner:**
-**Status:**
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-**1/25/16**
 Countdown to Release: **6 days**
-[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]]
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] TSC agreed upon a phased release with primary release date of 2/25/16. All scenarios that are stable and tested ready to release on that date will be released. Any currently in-plan scenarios that are not ready on 2/25/16 will be allowed to join a follow-on release on March 28th; if deemed necessary a 3rd release could follow in late-April
 **===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-25-14.30.html|1/25/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-19-14.30.html|2/19/16]]
 __**Top Accomplishments & Important Updates since last report**__
+.Sunday freeze of scenario troubleshooting was approved by the PTL vote. This will accommodate a couple of installer projects that need more time to validate fixes. The team will ensure that all troubleshooting of scenarios freeze on Sunday February 21 at 6pm Pacific. This will still give test teams adequate time to document outcomes since they had not planned to document over the weekend. PTLs will then review the documentation, and the branch will be tagged for release by Thursday Feb 25.
-.Fuel made great strides over the weekend. ONOS scenarios working. Still unable to freeze.
-.Yardstick successfully ran ONOS scenario with Compass.
-.Functest now relatively stable from CI perspective. ONOS scenarios working.
+**===============================================================================================================**
- **===============================================================================================================**
 __**Top Issues**__
-**Issue:** We are at high risk of missing release date. Test cycles for each scenario take a significant amount of time. Even if all installers & scenarios are working properly it takes 7 days to run test through them all.
-**Owner:** Debra
-**Status:** Additional options being proposed: 1. Release with what we have and move everything else to C Release  2. Delay release for up to 3 weeks 3. staggered/phased release of scenario support as a potential. Phase 1: Release what we can on Feb 2; Phase 2: Release what is ready 1-2 weeks later, Phase 3: final release 1-2 weeks after phase 2. These have been brought up to the TSC via email for consideration next TSC meeting.
-**Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
-**Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
-**Status:** Functest now relatively stable from CI perspective (except just joid). Still work on the different vPing (and then vIMS) testcases (that need ssh access from the VMs). Onos OK.
-Yardstick:ONOS - successfully run with Compass. ODL scenario - debugging on-going, Yardstick will not run with ODL. Narrowing down subsystems involved. Working on SFC test cases. Working on influxdB+grafana
-**Issue:** Getting RC0 out
-**Owner:** Debra
-**Status:**  Installer code freeze extended due to Fuel trying to stabilize with upstream. Compass also troubleshooting some functest and other instability with the code base, need some extra time in getting Compass code stable. Apex, JOID ready to freeze
-**Issue:** Fuel is not ready to code freeze. Upstream Fuel is not stable.
-**Owner:** Jonas Bjurel
-**Status:** Requesting code freeze delay until 1/29 and suggesting release slip 3 weeks
 **Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
 **Owner:** Ray Paik
-**Status:**Projects have made good progress on getting patches in to fix the files. Scott is making another license scan to see what if anything is outstanding. Thank you to all who have responded to this request in such a timely manner.
+**Status:**waiting on outcome of board vote whether to allow a few projects to use non-Apache licenses  (KVMFORNFV, ONOSFW, and VSWITCHPERF (with a single file with non-Apache-2.0 license).
-**Issue:** OpenContrail does not deploy
-**Owner:** Stuart Mackey
-**Status:** Apex still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
-**Issue:** Scenarios are frozen, but several not working yet, or have not been tried
-**Owner:** test teams
-**Status:**  Next step is creating Jenkins jobs and testing each scenario. In process with test teams leading. [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** 1/22 no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** Update needed. From Fuel team: This project is focusing on yardstick SLA test-cases aside of a true deployment (using bridges instead of OVS). They install a new kernel for which tere is no OVS kernel driver in the packages. All though they’re working on it. I’m not sure they will make it for our time plan – not even sure we need to wait for it since it is as a “technology project” verified by yardstick, but not yet deploying in a real environment. I would vote this to included in SR1 of Fuel@OPNFV B-release.
 **===============================================================================================================**
 __**Pod Status:**__
-All pods up and running
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
 [[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
+All pods are currently working and in use. LF Pod 3 is up and running. Yardstick requests that this pod remain reserved for troubleshooting Yardstick for at least the next 2 weeks.
+Intel pod5 is giving bad results for functest, some tests take too much for some reason we don't know. Requesting that Orange Pod could be Pharos approved pod for testing purposes
 **===============================================================================================================**
-**Scenario Status:** Scenarios are frozen. No feature project has reported that their scenarios are missing or unsupported. Candidate scenarios are having Jenkins jobs created for them. Test teams troubleshooting scenarios and test software.
+**Scenario Status:**
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
+Scenarios which are stable across installers are: Fuel: nosdn-no-feature, odl-l2, onos;Compass: no-sdn, odl-l2, onos-l2-l3
+Scenarios approaching stability are: Fuel: kvm, ovs, bgp-vpn
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)  Current situation
+Functest (Jose Lausuch)
-*****************
+.updated https://wiki.opnfv.org/functextnexttaks
-Functest Functest tests more stable, Some tests run in CI over the week end, Functest now relatively stable from CI perspective (except just joid I had to cancel). Still work on the different vPing (and then vIMS) testcases (that need ssh access from the VMs). Onos OK. ODL, maybe an update to be done, but we are integrating upstream suite, and it is not fully clear that the suite has been adapted to new version of ODL.
+.If we manage to get rid of those tempest errors on fuel due to insufficient ips : https://gerrit.opnfv.org/gerrit/#/c/10159/ we will be green for fuel
-https://wiki.opnfv.org/doku.php?id=vPing_brahmaputra_page
+.Wuwenbin has a patch to resolve Fuel/onos vPing test scenario patch is in & only waiting on Jonas to re-enable the onos scenario
-https://wiki.opnfv.org/doku.php?id=vIMS_brahmaputra_page
+.Decided to consider orange-pod2 for the release to get the results from
-Test DB migrated this morning (9 UTC) http://testresults.opnfv.org/testapi/pods
+.Got more results on that pod and it looks good.
-Still work ahead to tune some cases, and collect the error causes
+.For compass no changes, everything looks fine
+.Apex, we found some causes for some tempest tests, but still a bit under 90%, same issues with vPing with ONOS... .Discussions needed with community whether we don't consider that test case for the green light
-Yardstick (Ana Cunha)  ONOS first succesfull run on Compass, continue troubleshooting ODL scenarios
+Yardstick (Ana Cuna):
+.Looks like yardstick apex odl l2 scenario has 3 successful runs, waiting for next run
+.We noticed data coming in the dashboard: http://130.211.154.108/grafana/dashboard/db/yardstick-main
+.Notice dashboard is not ready, work in progress (use opnfv/opnfv if you want to see the data)
+.sign up or use opnfv/opnfv to view
 **===============================================================================================================**
 __**Installer Status:**__
-**Apex** (Tim Rozet):  Still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
+**Apex** (Tim Rozet):
-**JOID** (Narinder Gupta) JOID we are ready for code freeze as last pending issue related to Orange pod has been fixed
+**JOID** (Narinder Gupta)
+**Compass4nfv** (Weidong Shao)
+.Please refer to https://etherpad.opnfv.org/p/Compass4nfv_brahmaputra_status
-**Compass4nfv** (Weidong Shao) there were some functest and other instability with the code base, and we will need some extra time in getting Compass code stable
 **Fuel** (Jonas Bjurel)
 [[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-)      Build
-The building issues have been resolved to the point that it builds flawlessly in the
-OPNFV CI engine. Daily masters are produced every night since Friday. Work ongoing
-with getting it to build inside Ericsson corporate network. Stefan probably
-nailed it as it seems to be an issue with the 3.13.0-66 kernel.
-)      Deployment.
-I have successfully deployed the daily master image from Friday CI build:
-http://artifacts.opnfv.org/fuel/opnfv-2016-01-22_16-05-16.iso
-It works more or less flawlessly, a few minor comments:
-- The ssh service is not started as early as it used to do, it is not started when Fuelmenu
-  pops up which will be an issue for auto deploy. # service sshd start fixes it
-- Fuelmenu will sometimes tell you that the URLs for the bootimage cannot be found,
-  if you make sure you can reach url resources eg. Through open a consol from fuelmenu
-  and type nslookup www.google.com – just don’t care, select “save & continue” and the
-  “quit without saving” you should be good.
-- Selecting centos boot image didn’t work for me
-)      Early this week we need to prioritize getting autodeploy to work.
-But to my mind, this seems to be stable enough for plugin work. Please start commit rebased plugins to
-Master.
--          As I have indicated to TSC (Chris and Frank), my judgement is that we need another 3 week after Feb 2 to complete the things and have them in a good shape. The other option is to release with Fuel7/Kilo which is quite stable and a good veichle for developing stabilizing the scenarios  and the test pipe-line.
--          Issue with Jenkins server caused delays on Sunday but were resolved and builds are working again.
 **===============================================================================================================**
 __**Project Updates:**__ (as provided)
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
-**ARMband:**
+**Availability：**（Qiao Fu)
 **Bottlenecks:** (Hongbo Tian)
-**Copper:** (Bryan Sullivan) at risk
+**Copper:** (Bryan Sullivan)
-**Doctor** (Ryota, Ildiko) Apex patch for AODH is merged. Doctor will make the release.
+**Doctor** (Ryota, Ildiko)
-**IPv6:** (Bin Hu) -
+**HA**(Fu Qaio)
-**LSOAPI** (Kevin Leuhrs) at risk
+**IPv6:** (Bin Hu) -
 **NFV4KVM:** (Don Dugger, Raghuveer Reddy)
 **ONOSFW:** (Ashlee Young)
@@ Line 540: / Line 418: @@
 **OPNFVdocs** (Chris Price)
-Issues:
+Work ongoing.  Toolchain in place, editorial, structure, release content improving daily.
-Docs working on central content. Working with projects on project content.  Patches outstanding on many projects.
+Missing some content, will chase the stragglers.
-Awaiting final scenario list to progress to completion. Working with projects on project content.  Patches outstanding on many projects. Unable to code freeze until installers freeze.
-ONOSFW reviewing reviewing onosfw docs. Projects are working on docs, some feature projects are waiting for the integration to be complete to document that for the config guide
+**OVNO** (Stuart Mackie)
-**OVNO** (Stuart Mackie) Apex
 **Parser**
+**Promise** (Gerald Kunzmann)
 **Prediction** (Hai Liu)
@@ Line 554: / Line 433: @@
-**SFC** (Brady Johnson) Apex patch is merged, SFC scenario is supported in the release
+**SFC** (Brady Johnson)
 **SDNVPN** (Tim Irnich)
@@ Line 565: / Line 444: @@
 **===============================================================================================================**
 **Action Items**__Underlined Text__
-**Action:**
+**Action:** Create a dashboard view of Yardstick that shows all scenarios, all tests run per scenerio, all tests remaining to be run, and all tests that fail; Include feature support
-**Owner:**
+**Owner:** Ana Cuna
-**Status:**
+**Status:** assigned 2/4/16
-**Action:**
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------**2/18/16**
-**Owner:**
-**Status:**
-__**Action:**__
+Countdown to Release: **7 days**
-**Owner:**
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] TSC agreed upon a phased release with primary release date of 2/25/16. All scenarios that are stable and tested ready to release on that date will be released. Any currently in-plan scenarios that are not ready on 2/25/16 will be allowed to join a follow-on release on March 28th; if deemed necessary a 3rd release could follow in late-April
-**Status:**
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------**1/26/16 and 1/27/16**
-Countdown to Release: **TBD days**
-[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] under revision with proposed milestones dates until we work out details and report to TSC on 2/2/16 for their vote
 **===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-27-14.30.html|1/27/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-18-14.30.html|2/18/16]]
-[[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-28-14.30.html|1/28/16]]
 __**Top Accomplishments & Important Updates since last report**__
+.Test team rescinded the proposal to freeze scenario troubleshooting on Friday and instead proposed Sunday so as to accommodate a couple of installer projects that need more time to validate fixes. The team proposes that all troubleshooting of scenarios freeze on Sunday February 21 at 6pm Pacific. This will still give test teams adequate time to document outcomes since they had not planned to document over the weekend. PTLs will then review the documentation, and the branch will be tagged for release by Thursday Feb 25. The project PTLs are voting on this proposal via email. So far the vote is overwhelmingly positive. Close of voting is 8am Pacific on Friday, February 19.
-.TSC vote in progress to move code freeze to Friday 1/29 and to extend release date (to be defined). Debra and key community members to evaluate remaining work and recommend new release date with solid schedule to achieve that.
+.Have root cause for ONOS Vping Functest issues
-.LSOAPI officially notified they are dropping out of Brahmaputra 1/28 see meeting minutes with announcement and justifications: http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-01-28-17.04.html
+**===============================================================================================================**
-.Fuel team is nearly ready to freeze. Driving hard to meet Friday deadline.
-.ARMBand is busy rebasing to Fuel 8, may not make a Friday code freeze but very close. Driving hard to finish.
-.Functest much more stable
- **===============================================================================================================**
 __**Top Issues**__
-**Issue:** We are at high risk of missing release date. Test cycles for each scenario take a significant amount of time. Even if all installers & scenarios are working properly it takes 7 days to run test through them all.
-**Owner:** Debra
-**Status:** TSC voted to delay release rather than trying to phase release. Debra & key community members to identify remaining work and develop reasonably accurate schedule to propose to TSC.
-**Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
-**Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
-**Status:** All Functest scenario blue in Jenkins on Stable branch. Still troubleshooting vPing (and then vIMS). For vPing problem = floating IP not reachable. LF POD1 (apex/odl_l3) broken while running Functest (Neutron errors occured at the beginning of the first tests). One critical issue seen in CI is that after ODL L3 baremetal deploys, and functest executes - the nodes start spamming packets in the network. This does not happen on the ODL L2 or ONOS deployments. The nodes then flood our jenkins slave with 1 million packets per second, and the LF gateway router shuts the port to our VLAN.  Looks like a giant broadcast storm. This is not a POD issue.
-Yardstick:ONOS - ODL scenario troubleshooting in compass continues, for Fuel - will continue on Fuel8
-Some docs ready - not all yet
-**Issue:** Getting RC0 out
-**Owner:** Debra
-**Status:**  Installer code freeze extended due to Fuel trying to stabilize with upstream. Fuel should be ready on Friday. Apex, JOID, Compass ready to freeze. ARMBand is struggling to rebase to Fuel 8, may not be ready to freeze and as such may miss this release. Release is planning to freeze on Friday unless TSC disagrees.
-**Issue:** Fuel is not ready to code freeze. Upstream Fuel is not stable.
-**Owner:** Jonas Bjurel
-**Status:** Excellent progress by Fuel team. It is fairly coherent and stable! Now cherry picking to stable.
 **Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
 **Owner:** Ray Paik
-**Status:**No update 1/27-28 Projects have made good progress on getting patches in to fix the files. Scott is making another license scan to see what if anything is outstanding. Thank you to all who have responded to this request in such a timely manner.
+**Status:**update needed. After re-run 3 projects have licensing files that need review and approval by OPNFV Board Legal team
-**Issue:** OpenContrail does not deploy
-**Owner:** Stuart Mackey
-**Status:** JOID & Compass now have working plugins. Getting those into CI/build and testing. Apex still trying to get contrail to work, no update
-**Issue:** Scenarios are frozen, but several not working yet, or have not been tried
-**Owner:** test teams
-**Status:**  This should be closed now. Validating OpenContrail scenarios in Compass & JOID in preparation for code freeze tomorrow.
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** 1/22 no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** Update needed. From Fuel team: This project is focusing on yardstick SLA test-cases aside of a true deployment (using bridges instead of OVS). They install a new kernel for which tere is no OVS kernel driver in the packages. All though they’re working on it. I’m not sure they will make it for our time plan – not even sure we need to wait for it since it is as a “technology project” verified by yardstick, but not yet deploying in a real environment. I would vote this to included in SR1 of Fuel@OPNFV B-release.
 **===============================================================================================================**
 __**Pod Status:**__
-Troubleshooting Intel Pod 2 for Apex support
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
 [[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
-**===============================================================================================================**
+All pods are currently working and in use. LF Pod 3 is up and running. Yardstick requests that this pod remain reserved for troubleshooting Yardstick for at least the next 2 weeks.
-**Scenario Status:** Scenarios are frozen. No feature project has reported that their scenarios are missing or unsupported. Candidate scenarios are having Jenkins jobs created for them. Test teams troubleshooting scenarios and test software.
-Reviewed scenarios in table and noted those that will not be implemented this release
-Apex: 5 scenarios on Jenkins: 4 work from deploy point of view odl_l2 is about 90 pass/10 fail, odl_l3 worse pass rate Not successfully deployed yet: ocl- working on it
+Intel pod5 is giving bad results for functest, some tests take too much for some reason we don't know. Requesting that Orange Pod could be Pharos approved pod for testing purposes
-Compass: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl. From deployment point of view, 3 working, 1 not. Deployed successfully: openstack, odl_l2, onos. Once test has verified plugin is working will add ocl scenarios back in on wiki...
+**===============================================================================================================**
+**Scenario Status:**
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
-Fuel: Fuel@OPNF in general seems to be in a pretty good shape.
+Scenarios which are stable across installers are: Fuel: nosdn-no-feature, odl-l2, onos;Compass: no-sdn, odl-l2, onos-l2-l3
-o It is fairly coherent and stable!
-o All plugins/features/scenarios (except one which I expect tomorrow) have been merged
-o Since Fuel upstream is not released yet, rebasing is needed from time to time
-(not really problematic)
-o Build system is in good shape
-o Deploy system is in good shape
-o Building, deploying and smoke-test fine in our internal labs
--          Issues:
+Scenarios approaching stability are: Fuel: kvm, ovs, bgp-vpn
-o Configuration issues with CI-deploy, probably not a CI-issue but rather a Fuel8
-   configuration issue. We will put all the manpower on this after the freeze, and
-   should be resolved on Monday latest.
-o ONOS L3 scenario for external connectivity requires an exemption as it’s requirements
-   are not fully compatible with all of the labs (Pharos)! We will work on that next week.
--          Plan for the coming 24 hours:
-o Tomorrow we cherry-pick all patches from master (related to B-release) to stable, expect
-   some intermediate flux in build/verify/merge results!
-o From this point – strict cherry-picking policies will apply, policed by Jonas.
-Joid: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl. From deployment point of view, 3 working, 1 not activated/attempted yet. Deployed successfully: openstack, odl_l2, onos. Not successfully deployed yet: none. Once ocl scenario is validated in CI will add it back into wiki for this installer
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)  All Functest scenario blue in Jenkins on Stable branch. No progress on vPing (and then vIMS) but troubleshooting slots mainly in the evening or at night. For vPing problem = floating IP not reachable. Functest doc update, new patch to be submitted today. LF POD1 (apex/odl_l3) broken while running Functest (Neutron errors occured at the beginning of the first tests)
+Functest (Jose Lausuch)
-Test dashboard draft ready http://testresults.opnfv.org/proto/  Should not be too difficult to add new tests/projects and comparison per scenario and/or pod. If you look at the Tempest test case, it gives a good idea of the stability. See Tim' mail yesterday one critical issue I have seen in our CI is that after ODL L3 baremetal deploys, and functest executes - the nodes start spamming packets in the network. This does not happen on the ODL L2 or ONOS deployments. The nodes then flood our jenkins slave with 1 million packets per second, and the LF gateway router shuts the port to our VLAN.  Looks like a giant broadcast storm. This is not a POD issue. As I write this, I noticed it just happened again and I need to go power off the baremetal nodes.
+I updated and created a new way of showing how close/far are we to release a certain scenario: https://wiki.opnfv.org/functextnexttaks
-Yardstick:ONOS - reviewing open patches in yardstick repo to prepare for code freeze. ODL scenario troubleshooting in. Some docs ready - not all yet
+.Not much progress since yesterday...
-**===============================================================================================================**
+There was a discussion yesterday during pharos meeting about taking orange-pod2 as reference for results for JOID.. we will continue trobuleshooting the intel pods for the momment, running the 3 target scenarios for JOID and see what happens...
-__**Installer Status:**__
+Run times are still high on intel labs, 6hours last one...not acceptable....with SSD it is still high, SSDs were tried but failed to fix it
+.Fair to say that for Joid to make the deadline would have to accept results on Orange POD
+.Worked with Bob on ONOS Vping lastnight, we have a root cause now.
-**Apex** (Tim Rozet):  Still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
+Yardstick (Ana Cuna):
-**JOID** (Narinder Gupta) JOID deployed successfully on all three labs yesterday including the virtual deployment. Unfortunately functest had some issues yesterday which seems to be resolved.
-**Compass4nfv** (Weidong Shao) there were some functest and other instability with the code base, and we will need some extra time in getting Compass code stable
-**Fuel** (Jonas Bjurel)
-[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-)
-Struggling with an autodeploy issue, hopefully solved now. Testing. Scenarios being rebased
 **===============================================================================================================**
-__**Project Updates:**__ (as provided)
+__**Installer Status:**__
+**Apex** (Tim Rozet):
+.We have patches for SFC and SDNVPN that are ready to go, though we may
+hold them to devote time to running the tests.
-Scenarios:
+.I belive that we have all the functionality for Functest and Yardstick
-Apex: 5 scenarios on Jenkins: 4 work from deploy point of view
+across ODL-L2, ODL-L3 and ONOS but it seems there are limitation and
-odl_l2 is about 90 pass/10 fail, odl_l3 worse pass rate
+gaps in the testing being able to complete.
-Not successfully deployed yet: ocl- working on it
-Compass: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl.
+.That said, I am working hard to try and help resolve these issues and we
-From deployment point of view, 3 working, 1 not.
+will work to get as much passed in FT and YS as soon as we can
-Deployed successfully: openstack, odl_l2, onos.
-Now successfully deployed: ocl (removed from this installer) will add the scenario back in once CI & test are verified
-Fuel: 8 scenarios on Jenkins: pure openstack, odl_l2, odl_l3, onos, bgpvpn, ovs, kvm, kvm_ovs.
+**JOID** (Narinder Gupta)
-From deployment point of view, 5 working, 1 not working, 2 not activated/attempted yet.
+.yesterday ran two more times both nosdn and onos
-Deployed successfully: openstack, odl_l2, odl_l3, onos, bgpvpn
+.we have four runs nosdn, and three onos
-Not successfully deployed yet: ovs.
-Not activated/attempted: kvm, kvm_ovs.
-Fuel has Fuel7 on stable/brahmaputra branch and Fuel8 uplift work is WIP on master branch.
+**Compass4nfv** (Weidong Shao)
+.Please refer to https://etherpad.opnfv.org/p/Compass4nfv_brahmaputra_status
-Joid: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl.
-From deployment point of view, 3 working, 1 not activated/attempted yet.
-Deployed successfully: openstack, odl_l2, onos.
-Not successfully deployed yet: none.
-Now activated/attempted: ocl (removed from this installer). Will add the scenario back in once CI & test are verified
-**ARMband:** (Joe Kidder) [My opinion is that we won’t be able to freeze on Friday, as we’re still catching up to Fuel 7 capability, and the Fuel project has moved on to 8.]
+**Fuel** (Jonas Bjurel)
-Fuel 7:
+[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-We are almost complete building the set of arm64 repos needed for a Fuel deployment  and populating a public mirror (these are mainly the mos7 repo and things like that).
-We are in the process of doing modifications to cobbler [this is an approximate description] to do the work of Fuel using arm64 rather than x86 (amd64).
-Fuel 8:
-We have started building/populating the arm64 repos (similar to Fuel 7).
-We have not started the Fuel 8 arm64 porting yet.  This may be more straightforward than with Fuel7, however.
-Fuel 6.1 for HA functionality checking and preliminary Functest debug while waiting for Fuel 7/8 deployments to be ready.
-We are working on solving an HA bringup issue…some missing virtual interface
-  Assessment is that we won’t be able to freeze the porting (at best we’ll be close for Fuel 7, and maybe getting started with Fuel 8 by Friday, but that would be great progress).
-  We’re still going to be going full steam ahead.  We want to be ready/available as soon as possible regardless of whether we make the release.
-**Availability：**（Qiao Fu) HA project has got all the complete rst files merged and ready for release.
+**===============================================================================================================**
+__**Project Updates:**__ (as provided)
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
-**Bottlenecks:** (Hongbo Tian) 1, code is freezed in stable/brahmaputra branch
+**Availability：**（Qiao Fu)
-https://gerrit.opnfv.org/gerrit/gitweb?p=bottlenecks.git;a=shortlog;h=refs/heads/stable/brahmaputra
-https://git.opnfv.org/cgit/bottlenecks/?h=stable%2Fbrahmaputra
-, bottlenecks/rubbos has been successfully integrated into fuel/compass CI pipeline
-https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-daily-fuel-rubbos-lf-master/29/
-https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-daily-fuel-rubbos-lf-master/29/console
-https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-compass-rubbos-huawei-us-deploy-bare-1-daily-brahmaputra/15/
-https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-compass-rubbos-huawei-us-deploy-bare-1-daily-brahmaputra/15/console
-Test result stored in the DB
+**Bottlenecks:** (Hongbo Tian)
-,bottlenecks/vstf has been successfully integrated into fuel CI pipeline
-https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-daily-fuel-vstf-lf-master/32/
-https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-daily-fuel-vstf-lf-master/32/console
-Test result stored in the DB
+**Copper:** (Bryan Sullivan)
-, documents
-http://artifacts.opnfv.org/bottlenecks/brahmaputra/bottlenecks_brahmaputra_docs/index.html
-http://artifacts.opnfv.org/bottlenecks/brahmaputra/bottlenecks_brahmaputra_docs/bottlenecks_brahmaputra_docs.pdf
-**Copper:** (Bryan Sullivan) completing & integrating documentation for post-install add on
 **Doctor** (Ryota, Ildiko)
-**HA**(Fu Qaio) The HA team has successfully merged the docs for Brahmaputra release. For the convenience of documentation work, I merged all the separate section files into one .rst file. I also try to generate pdf versions based on these .rst file and seems everything is OK.
+**HA**(Fu Qaio)
-Currently, I upload these files onto our project master repo, and put them into two separate folders: R2_Requirement and R2_Scenarios, each include .rst file and .pdf file for our two release documents, that is the HA requirement doc and HA scenario analysis doc.
 **IPv6:** (Bin Hu) -
-**LSOAPI** (Kevin Leuhrs) project withdraws from the OPNFV Brahmaputra release, and plans no further activities. Today’s project meeting minutes record the announcement to terminate the project and summarizes rationale:
-Project meetings wiki page: https://wiki.opnfv.org/meetings/lsoapi?&#january_27_2016
-Link to  minutes for today’s meeting:
-http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-01-28-17.04.html
 **NFV4KVM:** (Don Dugger, Raghuveer Reddy)
 **ONOSFW:** (Ashlee Young)
@@ Line 795: / Line 560: @@
 **OPNFVdocs** (Chris Price)
-Issues:
+Work ongoing.  Toolchain in place, editorial, structure, release content improving daily.
-Docs working on central content. Working with projects on project content.  Patches outstanding on many projects.
+Missing some content, will chase the stragglers.
-Awaiting final scenario list to progress to completion. Working with projects on project content.  Patches outstanding on many projects. Unable to code freeze until installers freeze.
-ONOSFW reviewing reviewing onosfw docs. Projects are working on docs, some feature projects are waiting for the integration to be complete to document that for the config guide
+**OVNO** (Stuart Mackie)
-**OVNO** (Stuart Mackie) Apex still working on patch for plugin
 **Parser**
+**Promise** (Gerald Kunzmann)
 **Prediction** (Hai Liu)
@@ Line 820: / Line 586: @@
 **===============================================================================================================**
 **Action Items**__Underlined Text__
-**Action:** Reminder needs to be sent to all team that reservation system is set up for CI POD use so as to avoid various teams work impacting others negatively, especially since pods are now running long test runs.
+**Action:** Create a dashboard view of Yardstick that shows all scenarios, all tests run per scenerio, all tests remaining to be run, and all tests that fail; Include feature support
-**Owner:**  Debra
+**Owner:** Ana Cuna
-**Status:** Done, reminder sent out  Please visit https://wiki.opnfv.org/pharos_rls_b_labs#production_ci_resources_reservation
+**Status:** assigned 2/4/16
-**Action:**
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------**2/17/16**
-**Owner:**
-**Status:**
-__**Action:**__
+Countdown to Release: **8 days**
-**Owner:**
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] TSC agreed upon a phased release with primary release date of 2/25/16. All scenarios that are stable and tested ready to release on that date will be released. Any currently in-plan scenarios that are not ready on 2/25/16 will be allowed to join a follow-on release on March 28th; if deemed necessary a 3rd release could follow in late-April
-**Status:**
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-**1/26/16**
-Countdown to Release: **TBD days**
-[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]]
 **===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-26-14.30.html|1/26/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-17-14.30.html|2/17/16]]
 __**Top Accomplishments & Important Updates since last report**__
+.No issues reported with the following: The team proposes that all troubleshooting of scenarios freeze on Friday February 19 at close of business Pacific. This will ensure that test teams have adequate time to document outcomes, PTLs review the documentation, and the branch tagged for release by Thursday Feb 25. Any concerns with this timing should be addressed to Debra.
-.TSC voted to move code freeze to Friday 1/29 and to extend release date (to be defined). Debra and key community members to evaluate remaining work and recommend new release date with solid schedule to achieve that.
+.Since yesterday we have 2 consecutive good runs with NFVOVS with Functest
+.JOID: got the bug fix on onos and deploymnet was successful in intel pod6. odl_l2 runs fine on all pods. Still requesting Orange pod be Pharos for JOID test
- **===============================================================================================================**
+.The following scenarios pass 4 iterations of functest + yardstick so are ready to document and release: Fuel: nosdn-no-feature, odl-l2, onos; Compass: no-sdn, odl-l2, onos-l2-l3
+**===============================================================================================================**
 __**Top Issues**__
-**Issue:** We are at high risk of missing release date. Test cycles for each scenario take a significant amount of time. Even if all installers & scenarios are working properly it takes 7 days to run test through them all.
-**Owner:** Debra
-**Status:** TSC voted to delay release rather than trying to phase release. Debra & key community members to identify remaining work and develop reasonably accurate schedule to propose to TSC.
 **Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
 **Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
-**Status:**
+**Status:**closed. Some scenarios are now passing, others are still being troubleshot
-Yardstick:ONOS - successfully run with Compass. ODL scenario - debugging on-going, Yardstick will not run with ODL. Narrowing down subsystems involved. Working on SFC test cases. Working on influxdB+grafana
-**Issue:** Getting RC0 out
-**Owner:** Debra
-**Status:**  Installer code freeze extended due to Fuel trying to stabilize with upstream. Compass also troubleshooting some functest and other instability with the code base, need some extra time in getting Compass code stable. Apex, JOID ready to freeze
-**Issue:** Fuel is not ready to code freeze. Upstream Fuel is not stable.
-**Owner:** Jonas Bjurel
-**Status:** autodeploy issue, hopefully solved now. Testing. Scenarios being rebased
 **Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
 **Owner:** Ray Paik
-**Status:**Projects have made good progress on getting patches in to fix the files. Scott is making another license scan to see what if anything is outstanding. Thank you to all who have responded to this request in such a timely manner.
+**Status:**update needed. After re-run 3 projects have licensing files that need review and approval by OPNFV Board Legal team
-**Issue:** OpenContrail does not deploy
-**Owner:** Stuart Mackey
-**Status:** Apex still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
-**Issue:** Scenarios are frozen, but several not working yet, or have not been tried
-**Owner:** test teams
-**Status:**  Next step is creating Jenkins jobs and testing each scenario. In process with test teams leading. [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** 1/22 no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** Update needed. From Fuel team: This project is focusing on yardstick SLA test-cases aside of a true deployment (using bridges instead of OVS). They install a new kernel for which tere is no OVS kernel driver in the packages. All though they’re working on it. I’m not sure they will make it for our time plan – not even sure we need to wait for it since it is as a “technology project” verified by yardstick, but not yet deploying in a real environment. I would vote this to included in SR1 of Fuel@OPNFV B-release.
 **===============================================================================================================**
 __**Pod Status:**__
-All pods up and running
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
 [[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
-**===============================================================================================================**
+All pods are currently working and in use. LF Pod 3 is up and running. Yardstick requests that this pod remain reserved for troubleshooting Yardstick for at least the next 2 weeks.
-**Scenario Status:** Scenarios are frozen. No feature project has reported that their scenarios are missing or unsupported. Candidate scenarios are having Jenkins jobs created for them. Test teams troubleshooting scenarios and test software.
-Reviewed scenarios in table and noted those that will not be implemented this release
-Apex: 5 scenarios on Jenkins: 4 work from deploy point of view odl_l2 is about 90 pass/10 fail, odl_l3 worse pass rate Not successfully deployed yet: ocl- working on it
+Intel pod5 is giving bad results for functest, some tests take too much for some reason we don't know. Requesting that Orange Pod could be Pharos approved pod for testing purposes
-Compass: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl. From deployment point of view, 3 working, 1 not. Deployed successfully: openstack, odl_l2, onos. Not successfully deployed yet: ocl (removed from this installer)
+**===============================================================================================================**
+**Scenario Status:**
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
-Fuel: 8 scenarios on Jenkins: pure openstack, odl_l2, odl_l3, onos, bgpvpn, ovs, kvm, kvm_ovs. From deployment point of view, 5 working, 1 not working, 2 not activated/attempted yet. Deployed successfully: openstack, odl_l2, odl_l3, onos, bgpvpn Not successfully deployed yet: ovs. Not activated/attempted: kvm, kvm_ovs.
+Scenarios which are stable across installers are: Fuel: nosdn-no-feature, odl-l2, onos;Compass: no-sdn, odl-l2, onos-l2-l3
-Fuel has Fuel7 on stable/brahmaputra branch and Fuel8 uplift work is WIP on master branch.
+Scenarios approaching stability are: Fuel: kvm, ovs, bgp-vpn
-Joid: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl. From deployment point of view, 3 working, 1 not activated/attempted yet. Deployed successfully: openstack, odl_l2, onos. Not successfully deployed yet: none. Not activated/attempted: ocl (removed from this installer)
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)  Current situation
+Functest (Jose Lausuch)
+I updated and created a new way of showing how close/far are we to release a certain scenario: https://wiki.opnfv.org/functextnexttaks
-Functest regression yesterday night due to sdnvpn integration, fixed now
+.Major problem found in all installers/scenarios with vIMS. I need to ask the vIMS guy from orange why it is lately failing.
-.vPing/SSH Ok on manual tests with compass, not working with all scenarios yet
+.Fuel if we didn't take into consideration that vIMS failure, we are close to give a green light (sun) to all the fuel scenarios if we fix a few tempest issues
-we defined 2 vPING: vPing SSH and vPing userdata/cloudinit
+.Compass is all green, except same problem with vIMS
-https://wiki.opnfv.org/vping_brahmaputra_page
+.Apex, troubleshooting has been done and some fixes have been updated, we need stable deployments to get fresh results and see how it behaves. Apex daily running rightnow that we hope to get new results from
-vPing/SSH should be OK now on compass (wait for next run). Table to be updated for apex as well I think
+.Joid I created 2 tables, because the results are too differnt in orange-pod2 vs intel-pod5...
-http://testresults.opnfv.org/testapi/dashboard?project=functest&case=vPing&installer=apex and you can change the installer. wait for the test dashboard of LF...
+.Orange-pod2 looks promising, but I don't know if we consider it CI POD or not.. trevor_intel?
+Yardstick (Ana Cuna):
+.no new scenarios since yesterday, next 24h: documentation and troubleshooting
-Yardstick (Ana Cunha)  first successful run with joid yesterday (os scenario), fails on odl scenario
-On-going code writing for a patch for workaround for odl scenario - remains to be tested on the labs
-On-going work for grafana dashboard and documentation
-Started to document results for ha
 **===============================================================================================================**
 __**Installer Status:**__
-**Apex** (Tim Rozet):  Still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
+**Apex** (Tim Rozet):
+.Apex is just waiting for daily to run for new results so we know how to proceed.
+.Apex is finishing testing on SDNVPN and should have that ready soon
+.Apex also has SFC ready for senerio validation once we get FT and YS running again
+**JOID** (Narinder Gupta)
+.today we got the bug fix on onos and deploymnet was successful in intel pod6. odl_l2 runs fine on all pods.  i have enabled installer with vpn and sfc enablement for odl also
-**JOID** (Narinder Gupta) JOID deployed successfully on all three labs yesterday including the virtual deployment. Unfortunately functest had some issues yesterday which seems to be resolved today.
+**Compass4nfv** (Weidong Shao)
+.Please refer to https://etherpad.opnfv.org/p/Compass4nfv_brahmaputra_status
-**Compass4nfv** (Weidong Shao) there were some functest and other instability with the code base, and we will need some extra time in getting Compass code stable
 **Fuel** (Jonas Bjurel)
 [[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-)
+.Since yesterday we have 2 consecutive good runs with NFVOVS
+.We have 4 successful deployments with KVM4NFV but tests are failing.
+.KVM4NFV have been informed, don't know if they are working on it?
+.BGPVPN scenario will start in a couple of hours.
+.We might have a solution for the ODL-L3 scenario, testing it, will give results tomorrow.
-Struggling with an autodeploy issue, hopefully solved now. Testing. Scenarios being rebased
 **===============================================================================================================**
 __**Project Updates:**__ (as provided)
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
+**Availability：**（Qiao Fu)
-Scenario view status: Reviewed scenarios in table and noted those that will not be implemented this release
-Apex: 5 scenarios on Jenkins: 4 work from deploy point of view
-odl_l2 is about 90 pass/10 fail, odl_l3 worse pass rate
-Not successfully deployed yet: ocl- working on it
-Compass: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl.
-From deployment point of view, 3 working, 1 not.
-Deployed successfully: openstack, odl_l2, onos.
-Not successfully deployed yet: ocl (removed from this installer)
-Fuel: 8 scenarios on Jenkins: pure openstack, odl_l2, odl_l3, onos, bgpvpn, ovs, kvm, kvm_ovs.
-From deployment point of view, 5 working, 1 not working, 2 not activated/attempted yet.
-Deployed successfully: openstack, odl_l2, odl_l3, onos, bgpvpn
-Not successfully deployed yet: ovs.
-Not activated/attempted: kvm, kvm_ovs.
-Fuel has Fuel7 on stable/brahmaputra branch and Fuel8 uplift work is WIP on master branch.
-Joid: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl.
-From deployment point of view, 3 working, 1 not activated/attempted yet.
-Deployed successfully: openstack, odl_l2, onos.
-Not successfully deployed yet: none.
-Not activated/attempted: ocl (removed from this installer)
-**ARMband:**
-**Availability：**（Qiao Fu) HA project has got all the rst file merged and ready for release. Will upload a full set of rst file for the two release doc later today.
 **Bottlenecks:** (Hongbo Tian)
-**Copper:** (Bryan Sullivan) at risk
+**Copper:** (Bryan Sullivan)
 **Doctor** (Ryota, Ildiko)
-**IPv6:** (Bin Hu) -
+**HA**(Fu Qaio)
-**LSOAPI** (Kevin Leuhrs) at risk
+**IPv6:** (Bin Hu) -
 **NFV4KVM:** (Don Dugger, Raghuveer Reddy)
 **ONOSFW:** (Ashlee Young)
@@ Line 995: / Line 707: @@
 **OPNFVdocs** (Chris Price)
-Issues:
+.Fuel reports that their documents are ready
-Docs working on central content. Working with projects on project content.  Patches outstanding on many projects.
-Awaiting final scenario list to progress to completion. Working with projects on project content.  Patches outstanding on many projects. Unable to code freeze until installers freeze.
-ONOSFW reviewing reviewing onosfw docs. Projects are working on docs, some feature projects are waiting for the integration to be complete to document that for the config guide
+**OVNO** (Stuart Mackie)
-**OVNO** (Stuart Mackie) Apex still working on patch for plugin
 **Parser**
+**Promise** (Gerald Kunzmann)
 **Prediction** (Hai Liu)
@@ Line 1020: / Line 733: @@
 **===============================================================================================================**
 **Action Items**__Underlined Text__
-**Action:**
+**Action:** Create a dashboard view of Yardstick that shows all scenarios, all tests run per scenerio, all tests remaining to be run, and all tests that fail; Include feature support
-**Owner:**
+**Owner:** Ana Cuna
-**Status:**
+**Status:** assigned 2/4/16
-**Action:**
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------**2/15-16/16**
-**Owner:**
-**Status:**
-__**Action:**__
+Countdown to Release: **9 days**
-**Owner:**
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] TSC agreed upon a phased release with primary release date of 2/25/16. All scenarios that are stable and tested ready to release on that date will be released. Any currently in-plan scenarios that are not ready on 2/25/16 will be allowed to join a follow-on release on March 28th; if deemed necessary a 3rd release could follow in late-April
-**Status:**
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-**1/25/16**
-Countdown to Release: **6 days**
-[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]]
 **===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-25-14.30.html|1/25/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-15-14.30.html|2/15/16]]
+[[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-16-14.30.html|2/16/16]]
 __**Top Accomplishments & Important Updates since last report**__
+.The team proposes that all troubleshooting of scenarios freeze on Friday February 19 at close of business Pacific. This will ensure that test teams have adequate time to document outcomes, PTLs review the documentation, and the branch tagged for release by Thursday Feb 25. Any concerns with this timing should be addressed to Debra.
-.Fuel made great strides over the weekend. ONOS scenarios working. Still unable to freeze.
+.Releng team will be responsible for tagging Stable Branch for release with the help of LF (Aric).
-.Yardstick successfully ran ONOS scenario with Compass.
+.JOID: Using orange pod2 we have nearly 100% pass for install/functest/yardstick, but on intel-pod5/6 are bad, and we think it is due to some missconfiguration/network issue in the pod/jumphost; request is out to use Orange Pod 2 for official Pharos lab testing
-.Functest now relatively stable from CI perspective. ONOS scenarios working.
+.The following scenarios pass 4 iterations of functest + yardstick so are ready to document and release: Fuel: nosdn-no-feature, odl-l2, onos; Compass: no-sdn, odl-l2, onos-l2-l3
+**===============================================================================================================**
- **===============================================================================================================**
 __**Top Issues**__
-**Issue:** We are at high risk of missing release date. Test cycles for each scenario take a significant amount of time. Even if all installers & scenarios are working properly it takes 7 days to run test through them all.
-**Owner:** Debra
-**Status:** Additional options being proposed: 1. Release with what we have and move everything else to C Release  2. Delay release for up to 3 weeks 3. staggered/phased release of scenario support as a potential. Phase 1: Release what we can on Feb 2; Phase 2: Release what is ready 1-2 weeks later, Phase 3: final release 1-2 weeks after phase 2. These have been brought up to the TSC via email for consideration next TSC meeting.
 **Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
 **Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
-**Status:** Functest now relatively stable from CI perspective (except just joid). Still work on the different vPing (and then vIMS) testcases (that need ssh access from the VMs). Onos OK.
+**Status:**closed. Some scenarios are now passing, others are still being troubleshot
-Yardstick:ONOS - successfully run with Compass. ODL scenario - debugging on-going, Yardstick will not run with ODL. Narrowing down subsystems involved. Working on SFC test cases. Working on influxdB+grafana
-**Issue:** Getting RC0 out
-**Owner:** Debra
-**Status:**  Installer code freeze extended due to Fuel trying to stabilize with upstream. Compass also troubleshooting some functest and other instability with the code base, need some extra time in getting Compass code stable. Apex, JOID ready to freeze
-**Issue:** Fuel is not ready to code freeze. Upstream Fuel is not stable.
-**Owner:** Jonas Bjurel
-**Status:** Requesting code freeze delay until 1/29 and suggesting release slip 3 weeks
 **Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
 **Owner:** Ray Paik
-**Status:**Projects have made good progress on getting patches in to fix the files. Scott is making another license scan to see what if anything is outstanding. Thank you to all who have responded to this request in such a timely manner.
+**Status:**update needed. After re-run 3 projects have licensing files that need review and approval by OPNFV Board Legal team
-**Issue:** OpenContrail does not deploy
-**Owner:** Stuart Mackey
-**Status:** Apex still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
-**Issue:** Scenarios are frozen, but several not working yet, or have not been tried
-**Owner:** test teams
-**Status:**  Next step is creating Jenkins jobs and testing each scenario. In process with test teams leading. [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** 1/22 no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** Update needed. From Fuel team: This project is focusing on yardstick SLA test-cases aside of a true deployment (using bridges instead of OVS). They install a new kernel for which tere is no OVS kernel driver in the packages. All though they’re working on it. I’m not sure they will make it for our time plan – not even sure we need to wait for it since it is as a “technology project” verified by yardstick, but not yet deploying in a real environment. I would vote this to included in SR1 of Fuel@OPNFV B-release.
 **===============================================================================================================**
 __**Pod Status:**__
-All pods up and running
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
 [[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
+All pods are currently working and in use. LF Pod 3 is up and running. Yardstick requests that this pod remain reserved for troubleshooting Yardstick for at least the next 2 weeks.
 **===============================================================================================================**
-**Scenario Status:** Scenarios are frozen. No feature project has reported that their scenarios are missing or unsupported. Candidate scenarios are having Jenkins jobs created for them. Test teams troubleshooting scenarios and test software.
+**Scenario Status:**
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
+Scenarios which are stable across installers are: Fuel: nosdn-no-feature, odl-l2, onos;Compass: no-sdn, odl-l2, onos-l2-l3
+Scenarios approaching stability are: Fuel: kvm, ovs, bgp-vpn
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)  Current situation
+Functest (Jose Lausuch)
-*****************
+Functest-Fuel: its almost green on all scenarios, some issues with Tempest to be troubleshooted today. Probably due to subnet range too small in the public network. I contacted Jonas and will look into it soon
-Functest Functest tests more stable, Some tests run in CI over the week end, Functest now relatively stable from CI perspective (except just joid I had to cancel). Still work on the different vPing (and then vIMS) testcases (that need ssh access from the VMs). Onos OK. ODL, maybe an update to be done, but we are integrating upstream suite, and it is not fully clear that the suite has been adapted to new version of ODL.
-https://wiki.opnfv.org/doku.php?id=vPing_brahmaputra_page
-https://wiki.opnfv.org/doku.php?id=vIMS_brahmaputra_page
-Test DB migrated this morning (9 UTC) http://testresults.opnfv.org/testapi/pods
-Still work ahead to tune some cases, and collect the error causes
-Yardstick (Ana Cunha)  ONOS first succesfull run on Compass, continue troubleshooting ODL scenarios
+Functest-Compass: green, but we get problems in tempest with onos scenario as well, we think it is due to the fact that nova-metadata is not supported and some tempest cases use ssh-keys to VMs using that service. Maybe we just document why it fails and the limitations
+Functest scenario/installer/testcase results https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary
+its not 100% up to date because of the wiki issue
+I will change those values to green if only 4+ runs successful
+The issues with ODL ONOS may be identified as a fault in the ML2 device driver. We would need to carry through the release and solve on stable, document that limitation and release it
+Thats what we were planning to do for Compass, because Compass+ODL gets 0 errors... but when plugging onos, we get those 11 errors that related to the same thing
+We will need to raise tickets to document against.
+Functest-joid: request for orange-pod2 to become CI POD and report the results to the DB and also to artifacts. The results of JOID on orange -pod2 are almost 100% succesful, but on intel-pod5/6 are bad, and we think it is due to some missconfiguration/network issue in the pod/jumphost. Still troubleshooting with narinder
+Functest-apex: waiting for having a stable deployment to continue testing the SSH-to-floating-ip issue. Last week I managed to have that working manually tested on LF-pod1, but the test is not reproducible.
+Yardstick (Ana Cuna):
+.Following scenarios ready: compass - nosdn, odl_l2, onos; fuel - nosdn, odl_l2, onos
+.next 24h: working on more scenarios wuth fuel, results report and dashboard
+.scenarios on apex and joid not working for yardstick yet
@@ Line 1117: / Line 817: @@
 __**Installer Status:**__
-**Apex** (Tim Rozet):  Still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
+**Apex** (Tim Rozet):
+.Apex has somehow overlooked our SDNVPN patch and it's not been merged in. We spent yesterday  review it and testing it and it should be completed today or tomorrow
+.Apex plan for the next 24-hrs is to try and come to resolution on functest and yardstick
+**JOID** (Narinder Gupta)
+.small issue using a wrong flavor by vPing tests... to be fixed today. Also, problem creating a flavor for Promise testcase... The last job gave some execution problems also with Tempest. Investigation needed on intel-pod5.
+.gsutil needed on intel-pod5 in order to push the logs to artifacts.
-**JOID** (Narinder Gupta) JOID we are ready for code freeze as last pending issue related to Orange pod has been fixed
+**Compass4nfv** (Weidong Shao)
+.Please refer to https://etherpad.opnfv.org/p/Compass4nfv_brahmaputra_status
-**Compass4nfv** (Weidong Shao) there were some functest and other instability with the code base, and we will need some extra time in getting Compass code stable
+.vPing tests OK. 0 errors in Tempest when using ODL-L2 scenario and some errors when using ONOS scenario. Rally almost 100% success on both scenarios.
 **Fuel** (Jonas Bjurel)
 [[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-)      Build
+.Following scenarios have been qualified for release: nosdn-no-feature, odl-l2, onos
+.following scenarios is running towards completion: kvm, ovs, bgp-vpn
-The building issues have been resolved to the point that it builds flawlessly in the
+.Still troubleshooting ODL-L3.
-OPNFV CI engine. Daily masters are produced every night since Friday. Work ongoing
+.biggest issue is the ODL issue which we are trouble shooting on.
-with getting it to build inside Ericsson corporate network. Stefan probably
-nailed it as it seems to be an issue with the 3.13.0-66 kernel.
-)      Deployment.
-I have successfully deployed the daily master image from Friday CI build:
-http://artifacts.opnfv.org/fuel/opnfv-2016-01-22_16-05-16.iso
-It works more or less flawlessly, a few minor comments:
-- The ssh service is not started as early as it used to do, it is not started when Fuelmenu
-  pops up which will be an issue for auto deploy. # service sshd start fixes it
-- Fuelmenu will sometimes tell you that the URLs for the bootimage cannot be found,
-  if you make sure you can reach url resources eg. Through open a consol from fuelmenu
-  and type nslookup www.google.com – just don’t care, select “save & continue” and the
-  “quit without saving” you should be good.
-- Selecting centos boot image didn’t work for me
-)      Early this week we need to prioritize getting autodeploy to work.
-But to my mind, this seems to be stable enough for plugin work. Please start commit rebased plugins to
-Master.
--          As I have indicated to TSC (Chris and Frank), my judgement is that we need another 3 week after Feb 2 to complete the things and have them in a good shape. The other option is to release with Fuel7/Kilo which is quite stable and a good veichle for developing stabilizing the scenarios  and the test pipe-line.
--          Issue with Jenkins server caused delays on Sunday but were resolved and builds are working again.
 **===============================================================================================================**
 __**Project Updates:**__ (as provided)
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
-**ARMband:**
+**Availability：**（Qiao Fu)
 **Bottlenecks:** (Hongbo Tian)
-**Copper:** (Bryan Sullivan) at risk
+**Copper:** (Bryan Sullivan)
-**Doctor** (Ryota, Ildiko) Apex patch for AODH is merged. Doctor will make the release.
+**Doctor** (Ryota, Ildiko)
-**IPv6:** (Bin Hu) -
+**HA**(Fu Qaio)
-**LSOAPI** (Kevin Leuhrs) at risk
+**IPv6:** (Bin Hu) -
 **NFV4KVM:** (Don Dugger, Raghuveer Reddy)
 **ONOSFW:** (Ashlee Young)
@@ Line 1179: / Line 860: @@
 **OPNFVdocs** (Chris Price)
-Issues:
+.ryota is puhsing a bunch of patches to automate the toolchain and finalise some compilation issues. May result in patches on other projects. Keep your eyes open for some filepath patches.
-Docs working on central content. Working with projects on project content.  Patches outstanding on many projects.
+.work ongoing for release notes and reporting docs in parallel.
-Awaiting final scenario list to progress to completion. Working with projects on project content.  Patches outstanding on many projects. Unable to code freeze until installers freeze.
-ONOSFW reviewing reviewing onosfw docs. Projects are working on docs, some feature projects are waiting for the integration to be complete to document that for the config guide
-**OVNO** (Stuart Mackie) Apex
+**OVNO** (Stuart Mackie) ready to run functest; will use pod outside of CI so as not to disturb resources for Brahmaputra 1st release date
 **Parser**
+**Promise** (Gerald Kunzmann)
 **Prediction** (Hai Liu)
@@ Line 1193: / Line 875: @@
-**SFC** (Brady Johnson) Apex patch is merged, SFC scenario is supported in the release
+**SFC** (Brady Johnson)
 **SDNVPN** (Tim Irnich)
@@ Line 1204: / Line 886: @@
 **===============================================================================================================**
 **Action Items**__Underlined Text__
-**Action:**
+**Action:** Create a dashboard view of Yardstick that shows all scenarios, all tests run per scenerio, all tests remaining to be run, and all tests that fail; Include feature support
-**Owner:**
+**Owner:** Ana Cuna
-**Status:**
+**Status:** assigned 2/4/16
-**Action:**
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------**2/12/16**
-**Owner:**
-**Status:**
-__**Action:**__
+Countdown to Release: **13 days**
-**Owner:**
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] TSC agreed upon a phased release with primary release date of 2/26/16. All scenarios that are stable and tested ready to release on that date will be released. Any currently in-plan scenarios that are not ready on 2/26/16 will be allowed to join a follow-on release on March 28th; if deemed necessary a 3rd release could follow in late-April
-**Status:**
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-**1/22/16**
-Countdown to Release: **11 days**
-[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]]
 **===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-22-14.30.html|1/22/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-12-14.30.html|2/12/16]]
 __**Top Accomplishments & Important Updates since last report**__
-.Fuel unable to freeze due to upstream instability, requests delay of freeze until 1/29 and suggests 3 week delay to release or else fall back to previous upstream release of Fuel which is quite stable but that also requires fallback to OpenStack Kilo.
-.BREAKING NEWS: Successful run of bgpvpn noha scenario with Fuel with stable/Brahmaputra on LF-POD2
+**===============================================================================================================**
-.Apex got SFC and Aodh (Doctor) support merged
-.Functest stabilizing, successful runs 11/11 with ONOS, Apex, and Compass
-.Yardstick had first successful run with ONOS and Compass
- **===============================================================================================================**
 __**Top Issues**__
-**Issue:** We are at high risk of missing release date. Test cycles for each scenario take a significant amount of time. Even if all installers & scenarios are working properly it takes 7 days to run test through them all.
-**Owner:** Debra
-**Status:** Additional options being proposed: 1. Release with what we have and move everything else to C Release  2. Delay release for up to 3 weeks 3. staggered/phased release of scenario support as a potential. Phase 1: Release what we can on Feb 2; Phase 2: Release what is ready 1-2 weeks later, Phase 3: final release 1-2 weeks after phase 2. These have been brought up to the TSC via email for consideration next TSC meeting.
 **Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
 **Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
-**Status:** Functest tests more stable, several successfull run done since 24h, ONOS scenarios first successfull runs with Apex and Compass: 11/11  runs. Some concerns on the config of some PoDs, we were able to run the same tempest suite on 3 different PoDs with the same scenario (very inconsistent results)
+**Status:**
+Yardstick:  -working on bug fixes, docs and troubleshooting
-Yardstick: Continuing to troubleshoot troubleshooting ODL and ONOS scenarios. Not possible to run yardstick on ODL, ONOS yet - debugging Yardstick software.
+**Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
-.Integration with SFC started
+**Owner:** Ray Paik
-.Results documentation for on-demand test cases started
+**Status:**after re-run 3 projects have licensing files that need review and approval by OPNFV Board Legal team
-**Issue:** Functest & Yardstick have difficulty troubleshooting issues when underlying configurations are changed as installers are not frozen. They start troubleshooting one issue and then when they come back the next day the Installer code has been updated and they have to start from scratch.
-**Owner:** All teams
-**Status:** Fatih started a wiki for reservation of PODs so that teams are not stomping over each others work. Better communication & coordination is needed with regard to lab use considering the time it takes to set up and troubleshoot. All teams please adhere to the requested schedule or if the proposed schedule doesn't work for your team then please contact Fatih to work out the issues.
-**Issue:** Getting RC0 out
-**Owner:** Debra
-**Status:**  Installer code freeze extended again for 1 day due to Fuel trying to stabilize with upstream. 1/22 installer/documents freeze date delayed. Compass: There were some functest and other instability with the code base, and we will need some extra time in getting Compass code stable. Apex, JOID ready to freeze
-**Issue:** Fuel is not ready to code freeze. Upstream Fuel is not stable.
-**Owner:** Jonas Bjurel
-**Status:** Requesting code freeze delay until 1/29 and suggesting release slip 3 weeks
-**Issue:** OpenContrail does not deploy
-**Owner:** Stuart Mackey
-**Status:** Components of the needed patch for OpenContrail/Liberty are identifed and being scripted, This is one of the patches Apex is waiting for before freezing their code. They could freeze today if Fuel were ready but that would drop OpenContrail support.
-**Issue:** Scenarios are frozen, but need to be planned out or mapped to lab/test cycle
-**Owner:** test teams
-**Status:**  Next step is creating Jenkins jobs and testing each scenario. In process with test teams leading. [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
-**Issue:** Doctor install requirements - Aodh as critical component
-**Owner:** Ildiko, Ryota
-**Status:** Apex patch for AODH is working, getting it integrated since freeze is delayed. Doctor will make the release.
 **Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** 1/22 no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** from Fuel team: This project is focusing on yardstick SLA test-cases aside of a true deployment (using bridges instead of OVS). They install a new kernel for which tere is no OVS kernel driver in the packages. All though they’re working on it. I’m not sure they will make it for our time plan – not even sure we need to wait for it since it is as a “technology project” verified by yardstick, but not yet deploying in a real environment. I would vote this to included in SR1 of Fuel@OPNFV B-release.
 **===============================================================================================================**
 __**Pod Status:**__
-All pods up and running
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
 [[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
+All pods are currently working and in use. LF Pod 3 is up and running. Yardstick requests that this pod remain reserved for troubleshooting Yardstick for at least the next 2 weeks.
 **===============================================================================================================**
-**Scenario Status:** Scenarios are frozen. No feature project has reported that their scenarios are missing or unsupported. Candidate scenarios are having Jenkins jobs created for them. Test teams troubleshooting scenarios and test software.
+**Scenario Status:**
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
+scenario’s which are approaching stable across installers are: nosdn ,onos ,odl(be) - once integrated, odll3(be), ova, doctor, sdnvpn.  We are reasonably confident of having those release ready in a couple of weeks.
+To be stabilised include SFC, KVM and OCL which could potentially come in under a stable release or in C.  Dependant on the project teams efforts and targets.
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)  Current situation
+Functest (Morgan Richomme)
-*****************
-Functest Functest tests more stable, several successfull run done since 24h, all tables updated.
-ONOS first successfull run on apex and compass 11/11
-Some concerns on the config of some PoDs, we were able to run the same tempest suite on 3 different PoDs with the same scenario. We got very different results..on Orange Pod 91% OK, On Intel POD5 35%, Intel POD5 14ù, Intel POD6 34%
-Here it is a question of network config of the POD. Other concern it looks like ODL suite may be provide different results according to ODL version...looks like all the installers do not use the same version, however all have verified they use Lithium 3 https://wiki.opnfv.org/tempest_brahmaputra_page https://wiki.opnfv.org/onos_brahmaputra_page
-Test DB ready for migration, mail sent for transfer to LF on Monday
-Yardstick (Ana Cunha)  ONOS first succesfull run on Compass, continue troubleshooting ODL scenarios
+Yardstick (Ana Cuna)
@@ Line 1309: / Line 948: @@
 __**Installer Status:**__
-**Apex** (Tim Rozet):  SFC and Aodh (Doctor) support merged
+**Apex** (Tim Rozet):
+.Apex Still in debug mode, working specifically on the ODL-L3 vPing debug today
+.Other bugs are still in flight and making progress
+.Waiting info from OpenContrail for fixes needed re: Liberty
+**JOID** (Narinder Gupta)
+.in orange pod2 we have mutiple successful run now for install/functest/yardstick even few test cases are failing but we are good from installer prospective. Also intel pod5 and intel pod6 installs were successfull but functest are failing on test cases which needs to be debugged
-**JOID** (Narinder Gupta) JOID we are ready for code freeze as last pending issue related to Orange pod has been fixed
+**Compass4nfv** (Weidong Shao)
-**Compass4nfv** (Weidong Shao) there were some functest and other instability with the code base, and we will need some extra time in getting Compass code stable
 **Fuel** (Jonas Bjurel)
 [[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
--          Upstream continues to give us surprises, but stability has improve significantly the last few days.
+.Everything is in, don't expect anything more to go in, Docs ready. All efforts on troubleshooting the ssh issue with Yardstick and ODL.
+.Fuel resources moving into yardstick.
--          Some good news. Fatih ran bgpvpn noha scenario with Fuel with stable/Brahmaputra on LF-POD2 and it deployed like a charm! See: https://build.opnfv.org/ci/job/fuel-deploy-opnfv-jump-2-daily-brahmaputra/43/console. Next stage in advancement is to run the bgpvpn ha scenario (it is already developed and awaiting testing!). Super great work from Nikolas, Tim and Prem (and Fatih of course)
--          We now believe that we could code-freeze Fuel@OPNFV Friday next week, with a few more days needed for the features/plug-ins.
--          As I have indicated to TSC (Chris and Frank), my judgement is that we need another 3 week after Feb 2 to complete the things and have them in a good shape. The other option is to release with Fuel7/Kilo which is quite stable and a good veichle for developing stabilizing the scenarios  and the test pipe-line.
 **===============================================================================================================**
 __**Project Updates:**__ (as provided)
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
-**ARMband:**
+**Availability：**（Qiao Fu)
 **Bottlenecks:** (Hongbo Tian)
-**Copper:** (Bryan Sullivan) at risk
+**Copper:** (Bryan Sullivan)
-**Doctor** (Ryota, Ildiko) Apex patch for AODH is merged. Doctor will make the release.
+**Doctor** (Ryota, Ildiko)
-**IPv6:** (Bin Hu) -
+**HA**(Fu Qaio)
-**LSOAPI** (Kevin Leuhrs) at risk
+**IPv6:** (Bin Hu) -
+.ready for release, will help Yardstick analyze ping 6 results
 **NFV4KVM:** (Don Dugger, Raghuveer Reddy)
@@ Line 1345: / Line 985: @@
 **ONOSFW:** (Ashlee Young)
+.helping JOID get some charm fixes committed
+.will help analyze the test results once Yardstick has 4 good runs
 **OpenvSwitch** (Mark Gray)
@@ Line 1350: / Line 992: @@
 **OPNFVdocs** (Chris Price)
-Issues:
+.pushing functest results doc patch, working on user guide, working on config guide, working on overview docs.
-The code freeze date will not be met given the current state of Brahmaputra documentation.
+.also have an activity to improve pdf toolchain formatting
+.We have a workaround for table formatting, need to check.  Also looking at blank pages.
-**OVNO** (Stuart Mackie) Apex getting close to supporting OpenContrail, continuing to work on it since Fuel has delayed code freeze. Need to integrate new neutron plugin for Liberty.
+**OVNO** (Stuart Mackie) We appear to have OpenContrail working on Liberty. Testing continues today
+Will let Apex know what changes were made from standard V2.21. Join can test with JOID as well?
 **Parser**
+**Promise** (Gerald Kunzmann)
 **Prediction** (Hai Liu)
@@ Line 1362: / Line 1008: @@
-**SFC** (Brady Johnson) Apex patch is merged, SFC scenario is supported in the release
+**SFC** (Brady Johnson)
 **SDNVPN** (Tim Irnich)
@@ Line 1373: / Line 1019: @@
 **===============================================================================================================**
 **Action Items**__Underlined Text__
-**Action:**
+**Action:** Create a dashboard view of Yardstick that shows all scenarios, all tests run per scenerio, all tests remaining to be run, and all tests that fail; Include feature support
-**Owner:**
+**Owner:** Ana Cuna
-**Status:**
+**Status:** assigned 2/4/16
-**Action:**
-**Owner:**
-**Status:**
-__**Action:**__
-**Owner:**
-**Status:**
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+**2/11/16**
-**1/21/16**
+Countdown to Release: **15 days**
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] TSC agreed upon a phased release with primary release date of 2/26/16. All scenarios that are stable and tested ready to release on that date will be released. Any currently in-plan scenarios that are not ready on 2/26/16 will be allowed to join a follow-on release on March 28th; if deemed necessary a 3rd release could follow in late-April
-Countdown to Release: **12 days**
-[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]]
 **===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-21-14.30.html|1/21/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-11-14.30.html|2/11/16]]
 __**Top Accomplishments & Important Updates since last report**__
-.Fuel unable to freeze today. Will be better prepared to estimate additional time needed by tomorrow
+.JOID: using orange pod2 we have mutiple successful run now for install/functest/yardstick
+.Still no scenarios that reach quality goal of 4 successful runs functest + yardstick
-.Apex will be ready to freeze this evening
+**===============================================================================================================**
-.JOID and Compass ready to freeze
-.Apex very close to having SFC and AODH added, so sfc scenario will be working, and Doctor support will be there. Great work by the team.
-.
-.
- **===============================================================================================================**
 __**Top Issues**__
-**Issue:** We are at high risk of missing release date. Test cycles for each scenario take a significant amount of time. Even if all scenarios are working properly it takes 7 days to run test through them all.
-**Owner:** Debra
-**Status:** Proposing we look at staggered/phased release of scenario support as a potential. If we prioritize scenarios, let one or two highest priority scenarios out ASAP, preferably Feb 2; we could then take additional time to test more scenarios and release them 2 weeks later, and if necessary release more in another 2 weeks. This could potentially allow additional time for test projects and allow focus on smaller set of issues. Would need TSC discussion/decision on this approach. Test team are not sure if this will relieve their issues or not. It depends on the nature of the issues they identify with their tests suites. Debra to bring this idea up for consideration by TSC. We should know better very soon if this is a viable option to relieve test efforts.
 **Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
 **Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
-**Status:** Functest running again, back to Tuesday's status of investigating lack stability in test results.
+**Status:**
+Yardstick:  -working on bug fixes, docs and troubleshooting
-Yardstick: Continuing to troubleshoot troubleshooting ODL and ONOS scenarios. Not possible to run yardstick on ODL, ONOS yet - debugging Yardstick software.
+**Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
-.Integration with SFC started
+**Owner:** Ray Paik
-.Results documentation for on-demand test cases started
+**Status:**after re-run 3 projects have licensing files that need review and approval by OPNFV Board Legal team
-**Issue:** Functest & Yardstick have difficulty troubleshooting issues when underlying configurations are changed as installers are not frozen. They start troubleshooting one issue and then when they come back the next day the Installer code has been updated and they have to start from scratch.
-**Owner:** All teams
-**Status:** Fatih started a wiki for reservation of PODs so that teams are not stomping over each others work. Better communication & coordination is needed with regard to lab use considering the time it takes to set up and troubleshoot. All teams please adhere to the requested schedule or if the proposed schedule doesn't work for your team then please contact Fatih to work out the issues.
-**Issue:** Getting RC0 out
-**Owner:** Debra
-**Status:**  Installer code freeze extended again for 1 day due to Fuel trying to stabilize with upstream. New installer/documents freeze date 1/22. Apex, JOID & Compass all ready to freeze
-**Issue:** Fuel is not ready to code freeze. Upstream pip issue has a workaround but waiting merge iupstream.
-**Owner:** Jonas Bjurel
-**Status:** Upstream pip issue has a workaround but waiting merge in upstream.
-**Issue:** OpenContrail does not deploy
-**Owner:** Stuart Mackey
-**Status:** Components of the needed patch for OpenContrail/Liberty are identifed and being scripted, This is one of the patches Apex is waiting for before freezing this evening.
-**Issue:** Scenarios are frozen, but need to be planned out or mapped to lab/test cycle
-**Owner:** test teams
-**Status:**  Next step is creating Jenkins jobs and testing each scenario. In process with test teams leading. [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
-**Issue:** Doctor install requirements - Aodh as critical component
-**Owner:** Ildiko, Ryota
-**Status:** Apex patch for AODH is working, getting it integrated. Doctor will make the release.
 **Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** 1/20 no new update.  We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** from Fuel team: This project is focusing on yardstick SLA test-cases aside of a true deployment (using bridges instead of OVS). They install a new kernel for which tere is no OVS kernel driver in the packages. All though they’re working on it. I’m not sure they will make it for our time plan – not even sure we need to wait for it since it is as a “technology project” verified by yardstick, but not yet deploying in a real environment. I would vote this to included in SR1 of Fuel@OPNFV B-release.
 **===============================================================================================================**
 __**Pod Status:**__
-All pods up and running
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
 [[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
+All pods are currently working and in use. LF Pod 3 is up and running. Yardstick requests that this pod remain reserved for troubleshooting Yardstick for at least the next 2 weeks.
 **===============================================================================================================**
-**Scenario Status:** Scenarios are frozen. No feature project has reported that their scenarios are missing or unsupported. Candidate scenarios are having Jenkins jobs created for them. Test teams troubleshooting scenarios and test software.
+**Scenario Status:**
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
+scenario’s which are approaching stable across installers are: nosdn ,onos ,odl(be) - once integrated, odll3(be), ova, doctor, sdnvpn.  We are reasonably confident of having those release ready in a couple of weeks.
+To be stabilised include SFC, KVM and OCL which could potentially come in under a stable release or in C.  Dependant on the project teams efforts and targets.
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)  Current situation
+Functest (Morgan Richomme)
-*****************
+.vPing/SSH apex  fuel/odl_l3 troubleshooting in progress
-Functest running again, back to Tuesday's status of investigating lack stability in test results.  Rally will create a new version on Monday, but we applied the temporary patch in order to work, we force the use of a pip version < 8. New vPing seems OK (tested on apex, fuel and joid). Integration functest/promise initiated. Results are still not stable. We can see that the integration of ODL lead to a significant degradation of tempest results (which we may understand) but it is not the same on the different installers. So we have to understand the errors. Without controller almost 100% OK, with other scenario different figures and different errors. Looking into potential of a scenario config issue with Fuel for ODL-L3.  https://wiki.opnfv.org/tempest_brahmaputra_page
+   -seems that workaround on non parallelisation of tests in Tempest lead to better results, wait and see iterations for confirmation
+.last apex run 92% OK and joid run 98%
-Yardstick (Ana Cunha)  troubleshooting Joid, Compass, Fuel and Apex, working on integrated test result db.
+.new doc to write for the results, wait for Chris merge before starting with scneario already ready (compass scenario)
-Requested help with SSH issues.
+Yardstick (Ana Cuna)
+.odl l2 with joid: fault in orange pod 2
+   -seems not to be yardstick problem: Cannot connect to the Docker daemon. Docker daemon is running on this host.
+   -continue troubleshooting
+   -functest last run was failed but previous were OK, we also got an unexpected failure at the end of last functest run...I need to connect to the machine because no clear message. We got 2 runs through before this latest issue
+.next 24 hours: troubleshooting and fixing docs
 **===============================================================================================================**
 __**Installer Status:**__
-**Apex** (Tim Rozet): Integrating patches and plan to freeze this evening
+**Apex** (Tim Rozet):
+.Apex Still in debug mode, working specifically on the ODL-L3 vPing debug today
+.Other bugs are still in flight and making progress
+.Waiting info from OpenContrail for fixes needed re: Liberty
+**JOID** (Narinder Gupta)
+.in orange pod2 we have mutiple successful run now for install/functest/yardstick even few test cases are failing but we are good from installer prospective. Also intel pod5 and intel pod6 installs were successfull but functest are failing on test cases which needs to be debugged
-**JOID** (Narinder Gupta) ready to freeze, working on docs
+**Compass4nfv** (Weidong Shao)
-**Compass4nfv** (Weidong Shao) ready to freeze
 **Fuel** (Jonas Bjurel)
 [[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-Not read to freeze, working with upstream problems. Upstream Fuel not yet entirely stable, were working on it and hope to have better answers tomorrow
+.Everything is in, don't expect anything more to go in, Docs ready. All efforts on troubleshooting the ssh issue with Yardstick and ODL.
+.Fuel resources moving into yardstick.
 **===============================================================================================================**
 __**Project Updates:**__ (as provided)
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
-**ARMband:**
+**Availability：**（Qiao Fu)
 **Bottlenecks:** (Hongbo Tian)
-**Copper:** (Bryan Sullivan) at risk
+**Copper:** (Bryan Sullivan)
-**Doctor** (Ryota, Ildiko) Apex patch for AODH is working, getting it integrated. Doctor will make the release.
+**Doctor** (Ryota, Ildiko)
-**IPv6:** (Bin Hu) -
+**HA**(Fu Qaio)
-**LSOAPI** (Kevin Leuhrs) at risk
+**IPv6:** (Bin Hu) -
+.ready for release, will help Yardstick analyze ping 6 results
 **NFV4KVM:** (Don Dugger, Raghuveer Reddy)
@@ Line 1507: / Line 1127: @@
 **ONOSFW:** (Ashlee Young)
+.helping JOID get some charm fixes committed
+.will help analyze the test results once Yardstick has 4 good runs
 **OpenvSwitch** (Mark Gray)
-**OPNFVdocs** (ChrisPriceAB:)
+**OPNFVdocs** (Chris Price)
-Issues:
+.pushing functest results doc patch, working on user guide, working on config guide, working on overview docs.
-The code freeze date will not be met given the current state of Brahmaputra documentation.
+.also have an activity to improve pdf toolchain formatting
+.We have a workaround for table formatting, need to check.  Also looking at blank pages.
+**OVNO** (Stuart Mackie) We appear to have OpenContrail working on Liberty. Testing continues today
+Will let Apex know what changes were made from standard V2.21. Join can test with JOID as well?
 **Parser**
+**Promise** (Gerald Kunzmann)
 **Prediction** (Hai Liu)
@@ Line 1522: / Line 1150: @@
-**SFC** (Brady Johnson) Apex integrating a patch that will have this scenario running
+**SFC** (Brady Johnson)
 **SDNVPN** (Tim Irnich)
@@ Line 1533: / Line 1161: @@
 **===============================================================================================================**
 **Action Items**__Underlined Text__
-**Action:**
+**Action:** Create a dashboard view of Yardstick that shows all scenarios, all tests run per scenerio, all tests remaining to be run, and all tests that fail; Include feature support
-**Owner:**
+**Owner:** Ana Cuna
-**Status:**
+**Status:** assigned 2/4/16
-**Action:**
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-**Owner:**
+**2/10/16**
-**Status:**
-__**Action:**__
+Countdown to Release: **16 days**
-**Owner:**
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] TSC agreed upon a phased release with primary release date of 2/26/16. All scenarios that are stable and tested ready to release on that date will be released. Any currently in-plan scenarios that are not ready on 2/26/16 will be allowed to join a follow-on release on March 28th; if deemed necessary a 3rd release could follow in late-April
-**Status:**
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------**1/20/16**
-Countdown to Release: **13 days**
-[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]]
 **===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-20-14.30.html|1/20/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-10-14.30.html|2/10/16]]
 __**Top Accomplishments & Important Updates since last report**__
-.Unless there is significant progress by 1/21, we are at a tipping point where we need to consider the high likelihood of schedule slip. We cannot release without a basic level of Functest and Yardstick. If these were working perfectly today it would still require a minimum of 7 days to validate the test scenarios to provide a baseline for beginning the test cycle, however, each scenario is requiring significant time to troubleshoot & fix. Alternatives to look at may include prioritize & focus on smaller set of scenarios, and follow up with others in a two or three phase release.
+.First iteration of doctor on apex scenario OK from CI perspective
-.JOID reached RC0
-.LSOAPI: the Cablelabs team is following up on last action items. LSOAPI is running in a local lab, they will continue to pursue running in a Pharos lab. They will also work on documentation. They are using a post install deployment option. They are at high risk for missing this release.
+.We appear to have OpenContrail working on Liberty.
-.Installer/documentation code freeze extended to 1/21. This potentially delays test work although they have started with those installers that are able to lockdown. (as of today that is Apex, JOID, Compass4nfv)
+**===============================================================================================================**
- **===============================================================================================================**
 __**Top Issues**__
@@ Line 1569: / Line 1185: @@
 **Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
 **Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
-**Status:** Functest all tests failed due to problem with pip (we should not the only ones impacted...). Installation of rally is not possible...but it is not Rally's fault. https://en.wikipedia.org/wiki/Pip_(package_manager)
+**Status:** -regression on Tempest suite (investigation to know if it is in Functest or upstream) continues.
-Before this, we updated the different tables https://wiki.opnfv.org/vping_brahmaputra_page
+            -ODL Beryllium resolves blocking vping and SSH issues. TSC voted to move from ODL Lithium to ODL Beryllium for this release in order to resolve blocking issues
+            -working through scenarios in logical order coordinated with Yardstick, deployment and feature projects as needed to allow for additional testing & troubleshooting
+            -JOID regression testing with Be is in progress, all other installers report it is supported
+Yardstick:  -working on bug fixes, docs and troubleshooting
-Continuing to troubleshoot troubleshooting ODL and ONOS scenarios. With Yardstick, cleaning up one issue uncovered another. Functest tests suite runnable from CI perspective, heterogeneous and not reproducible results (due to lack of stability).
+**Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
+**Owner:** Ray Paik
+**Status:**after re-run 3 projects have licensing files that need review and approval by OPNFV Board Legal team
-**Issue:** Getting RC0 out
-**Owner:** Debra
-**Status:**  Installer code freeze extended for 2 days due to Pods being down this past weekend. New installer/documents freeze date 1/21. Apex & JOID scenario test/troubleshooting in progress; Fuel validation of upstream integration in progress. Compass is ready to freeze aside from test trying to run and then troubleshooting scenarios (like Apex & JOID).
-**Issue:** Fuel is not ready to code freeze. Pods down over weekend prevented testing/progress with validation of integrated upstream code. Ran into issue in OpenStack PIP. OpenStack community is looking into this.
-**Owner:** Jonas Bjurel
-**Status:** see above issue status getting RC0 out
-**Issue:** OpenContrail does not deploy
-**Owner:** Stuart Mackey
-**Status:** no update for 1/20 Compass got vrouter and GUI up, Apex has a build and will test, JOID waiting for a patch
-**Issue:** Scenarios are not fully known, planned out or mapped to lab/test cycle
-**Owner:** Debra
-**Status:**  Next step is creating Jenkins jobs and testing each scenario. In process with test teams leading. Assistance needed from both Installer teams and Feature teams to troubleshoot & close issues. Closed. Scenarios are frozen. No feature projects which are able to deploy with installers have reported that their scenarios are not supported. [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
-**Issue:** Doctor install requirements - Aodh as critical component
-**Owner:** Ildiko, Ryota
-**Status:** 1/20 Still at high risk. Apex has a patch up but not working. Fuel patch is not completed. Looking now at post-install integration. May not make this release.
 **Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** 1/20 no new update.  We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** from Fuel team: This project is focusing on yardstick SLA test-cases aside of a true deployment (using bridges instead of OVS). They install a new kernel for which tere is no OVS kernel driver in the packages. All though they’re working on it. I’m not sure they will make it for our time plan – not even sure we need to wait for it since it is as a “technology project” verified by yardstick, but not yet deploying in a real environment. I would vote this to included in SR1 of Fuel@OPNFV B-release.
 **===============================================================================================================**
 __**Pod Status:**__
-All pods back up and running
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
 [[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
+All pods are currently working and in use. LF Pod 3 is up and running. Yardstick requests that this pod remain reserved for troubleshooting Yardstick for at least the next 2 weeks.
 **===============================================================================================================**
-**Scenario Status:** Scenarios are frozen. No feature project has reported that their scenarios are missing or unsupported
+**Scenario Status:**
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
+scenario’s which are approaching stable across installers are: nosdn ,onos ,odl(be) - once integrated, odll3(be), ova, doctor, sdnvpn.  We are reasonably confident of having those release ready in a couple of weeks.
+To be stabilised include SFC, KVM and OCL which could potentially come in under a stable release or in C.  Dependant on the project teams efforts and targets.
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)  Current situation
+Functest (Morgan Richomme)
-*****************
+.2 new scenario candidate for "Release ready" status last night fuel/nosdn-ovs and joid/odl_l2 (on Orange POD), waiting for iteration to confirm
-as you can see from a CI perspective, we were able to run successfully Functest
+.Still having vPing issues on Onos and old_l3 scenario
-https://build.opnfv.org/ci/view/functest/
+.Making progress on Tempest.
+.Docs updated
+.First iteration of doctor on apex scenario OK from CI perspective (did not discuss with Ryota on the test content)
+POD to troubleshoot the onos and l3 scenbario's?
+ -Ericsson POD2 could be used for troubleshooting. Jose has access to it. LF POD1/apex can also be used.
+.Over next 24 hours ee will continue on the 2 last items vPing and Tempest
+Yardstick (Ana Cuna)
+.problems detected with yardstick installation last night - fix merged
+.new server for yardstick db is made available from LF, need access rights and user replication to continue, connection refused from yardstick data to previous server - no data was recorded last night. Aric has been contacted
+.request that no one uses the new server other than yardstick, for next two weeks, to avoid disturbances
+.for next 24 hours: check runs, fix problems and work on database
-the following scenario were "runnable" on Stable/Brahamputra branch:
-- compas/odl_l2-nofeature-ha
-- fuel/odl_l2-nofeature-ha
-- joid-odl_2-nofeature-ha
-and on Master (because not available
+**===============================================================================================================**
-- apex/onos-nofeature-ha
+__**Installer Status:**__
-but it is only from a CI point of view
+**Apex** (Tim Rozet):
-when we dive into the details, the results are not at the same level and it is difficult to get stable results
+.a few more bugs to fix that are listed in JIRA
-=> different  from one run to another, we are far from a stable run as defined during le summit (and as far as I understood there are still some major patchs on some installer side)
+.most are already in flight
+.top priority in next 24 hours is figuring out why Functest and yardstick are not succeeding
+.Intel Pod 7 available; we have access to it and are getting the env verified to hook back up to jenkins
-see details on
+**JOID** (Narinder Gupta)
-- https://wiki.opnfv.org/vping_brahmaputra_page
+.we had successfull run on orange pod2 for all deploy, funtest, yardstick.
-- https://wiki.opnfv.org/tempest_brahmaputra_page
+.Functest reported only 4 temptest failure. Intel pod5 we are seeing more failure which needs to be debugged. Morgan might get access to intel pods soon to get it debugged further
-- https://wiki.opnfv.org/vims_brahmaputra_page
-for odl tests some are 18/18 OK some 0 and it is not stable
+**Compass4nfv** (Weidong Shao)
-feature projects
+**Fuel** (Jonas Bjurel)
-*****************
+[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-regarding the integration of feature projects
+Continue running & troubleshooting scenarios.
-we are ready for:
-- doctor
-- promise
-- ovno
-- onos
-but as far as I know now, none of these tests have been run from CI
+o   NFVKVM: This project is focusing on yardstick SLA test-cases aside of a true deployment (using bridges instead of OVS). They install a new kernel for which tere is no OVS kernel driver in the packages. All though they’re working on it. I’m not sure they will make it for our time plan – not even sure we need to wait for it since it is as a “technology project” verified by yardstick, but not yet deploying in a real environment. I would vote this to included in SR1 of Fuel@OPNFV B-release.
-fist manual test done on onos
-docs
+o   SFC, though we have been integrating SFC base features into fuel, the SFC team have gone with architecture that requires tacker as an orchestrater (although tacker is explicitly outside of the B-release). The SFC team has started on a Tacker Fuel plugin – and as the plug-in architechture provides proper fensing to the core of Fuel, we can wait and see if they come with something that works. Their deadline is Thu Feb 11 – but I don’t expect them to make it, hope I’m cut by surprise!
-*****
-docs have been initiated
-- a user guide => http://artifacts.opnfv.org/functest/docs/userguide/index.html
-- a config/installation guide => http://artifacts.opnfv.org/functest/docs/configguide/index.html
-- a developper guide => http://artifacts.opnfv.org/functest/docs/devguide/index.html
-work in progress
+Reporting:I have included my reporting into this ether-pad: https://etherpad.opnfv.org/p/steps_to_brahmaputra as a link
+Fuel@OPNFV’s input to the status and the plans:
+-          This is our end-game status, that will be updated daily: https://wiki.opnfv.org/fuel_opnfv/b_release_status
-as a conclusion
+-          This is our end-game plan, updated twice a week: https://wiki.opnfv.org/fuel_opnfv_b-wp
-I would say that the status is Yellow/Red due
-- to stability issues
-- late integration of feature projects
-- difficulty to get env to work (no system available on Monday)
-some work could be postponed to RC1 (if we follow apex approach, we could do something similar)
-Yardstick (Ana Cunha)  troubleshooting Joid, Compass, Fuel and Apex, working on integrated test result db.
-Requested help with SSH issues.
-**===============================================================================================================**
-__**Installer Status:**__
-**Apex** (Tim Rozet): no new status for 1/19 see 1/18 status below
-**JOID** (Narinder Gupta) Intel pod6 passed with working scenario. We have working B release. Still working on documentation and debugging orange pod2
-**Compass4nfv** (Weidong Shao) no new status for 1/20 see 1/18 status below
-**Fuel** (Jonas Bjurel)
-[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-Still working on rebasing Fuel plugins. We will start running master scenarios on Ericsson POD 2 now that it is up
-Working on problems with master build. Some issues with upstream yet.
 **===============================================================================================================**
 __**Project Updates:**__ (as provided)
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
-**ARMband:**
+**Availability：**（Qiao Fu)
 **Bottlenecks:** (Hongbo Tian)
@@ Line 1696: / Line 1279: @@
 **Copper:** (Bryan Sullivan)
-**Doctor** (Ryota, Ildiko) There is not good progress in aodh support in apex and the upstream project [1,2].
+**Doctor** (Ryota, Ildiko)
-Being complete by tomorrow is not realistic...
-I think we can create post-installer, but the concern is whether we can complete the development by the deadline.
+**HA**(Fu Qaio)
-[1] https://review.openstack.org/#/c/241408/
-[2] https://gerrit.opnfv.org/gerrit/#/c/6631/
 **IPv6:** (Bin Hu) -
-**LSOAPI** (Kevin Leuhrs) at risk
 **NFV4KVM:** (Don Dugger, Raghuveer Reddy)
-**ONOSFW:** (Ashlee Young)
+**ONOSFW:** (Ashlee Young) Most of the team is still on holiday, but looking into vPing issues and making an update to docs
 **OpenvSwitch** (Mark Gray)
-**OPNFVdocs** (ChrisPriceAB:) no new update for 1/20
+**OPNFVdocs** (Chris Price) working on release notes and results publishing and structure today, will continue tomorrow
-Issues:
-The code freeze date will not be met given the current state of Brahmaputra documentation.
+**OVNO** (Stuart Mackie) We appear to have OpenContrail working on Liberty. Testing continues today
+Will let Apex know what changes were made from standard V2.21. Join can test with JOID as well?
 **Parser**
-**Prediction** (Hai Liu) Prediction project has completed requirements document. Code is under development, not ready yet. It is not  integrated to a installer now.
+**Promise** (Gerald Kunzmann)
+**Prediction** (Hai Liu)
 **Qtip** (Vikram)
@@ Line 1730: / Line 1310: @@
 **SDNVPN** (Tim Irnich)
-first successful deployment in CI happened yesterday, thanks to Fatih for setting up Jenkins.
-https://build.opnfv.org/ci/job/fuel-deploy-virtual-daily-brahmaputra/8/console
-We will now rebase our plugins to Fuel8 and as soon as we can deploy ODL Be we can start running our E2E tests in CI as well.
-Big thanks to all contributors!
 **SFQM** (Maryam Tahhan)
-**StorPerf** (Mark Beierle) Just this week I found out I have Intel POD 9 in Pharos:  https://wiki.opnfv.org/get_started/intel_pod9 I did not realize that we were going to get any resources, so I am pleasantly surprised.
+**StorPerf** (Mark Beierle)
-There will be documentation (currently in the wiki) that will be moved into .rst files so that it can be picked up by the documentation toolchain.  This will then be published by releng to the same location as the other documentation, and I think I might look into having it part of the StorPerf docker image too.
 **===============================================================================================================**
 **Action Items**__Underlined Text__
-**Action:**
+**Action:** Create a dashboard view of Yardstick that shows all scenarios, all tests run per scenerio, all tests remaining to be run, and all tests that fail; Include feature support
-**Owner:**
+**Owner:** Ana Cuna
-**Status:**
+**Status:** assigned 2/4/16
-**Action:**
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-**Owner:**
-**Status:**
-__**Action:**__
+**2/8/16-2/9/16**
-**Owner:**
-**Status:**
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------**1/19/16**
+Countdown to Release: **17 days**
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] TSC agreed upon a phased release with primary release date of 2/26/16. All scenarios that are stable and tested ready to release on that date will be released. Any currently in-plan scenarios that are not ready on 2/26/16 will be allowed to join a follow-on release on March 28th; if deemed necessary a 3rd release could follow in late-April
-Countdown to Release: **14 days**
-[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]]
 **===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-19-14.30.html|1/19/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-09-14.30.html|2/9/16]]
 __**Top Accomplishments & Important Updates since last report**__
-  .LSOAPI PTL is no longer employed at Cablelabs, work is ongoing to connect with him & identify path forward, if he is
+.After investigation with deployment tools, the TSC approved a Change Request to release with ODL Beryllium instead of ODL Lithium.
-  not planning to participate in the project as a private contributor then the community will need to vote on a replacement.
-  .Installer/documentation code freeze extended to 1/21. This potentially delays test work although they have started with those installers that are able to lockdown.
+.Functest
+       -Continuing to work through scenarios. Tempest functionality remains an issue in some scenarios.[[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary|here]] Keep in mind that this is a static page, if you need more current information then visit the test dashboard
- **===============================================================================================================**
+**===============================================================================================================**
 __**Top Issues**__
+**Issue:** We have passed target release date of Feb 2.
+**Owner:** Debra
+**Status:** TSC voted to target a phased release schedule with first release target for Feb 26. Additional release dates for scenarios that need more time are proposed for late March and, if needed, late April.
 **Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
 **Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
-**Status:** wip, Ana put out a call for help with SSH issues during Release team meeting. Functest tests suite runnable from CI perspective, heterogeneous and not reproducible results (due to lack of stability). Need installers to stabilize then can troubleshoot scenario issues.
+**Status:** -regression on Tempest suite (investigation to know if it is in Functest or upstream) continues.
+            -ODL Beryllium resolves blocking vping and SSH issues. TSC voted to move from ODL Lithium to ODL Beryllium for this release in order to resolve blocking issues
+            -working through scenarios in logical order coordinated with Yardstick, deployment and feature projects as needed to allow for additional testing & troubleshooting
+            -JOID regression testing with Be is in progress, all other installers report it is supported
+Yardstick:  -working on bug fixes, docs and troubleshooting
-**Issue:** Getting RC0 out
+**Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
-**Owner:** Debra
+**Owner:** Ray Paik
-**Status:**  Installer code freeze extended for 2 days due to Pods being down this past weekend. New installer/documents freeze date 1/21. Apex & JOID scenario test/troubleshooting in progress; Fuel validation of upstream integration in progress. Compass work in progress.
+**Status:**after re-run 3 projects have licensing files that need review and approval by OPNFV Board Legal team
-**Issue:** Fuel is not ready to code freeze. Pods down over weekend prevented testing/progress with validation of integrated upstream code.
+**Issue:** Scenarios are frozen, but significant number not working yet, or have not been tried
-**Owner:** Jonas Bjurel
+**Owner:** test teams
-**Status:** see above issue status
+**Status:** Closed. Test projects are stabilizing and now running through previously untested scenarios. Continuing to run & debug scenarios in coordinated manner.
-**Issue:** OpenContrail does not deploy
-**Owner:** Stuart Mackey
-**Status:** Compass got vrouter and GUI up, Apex has a build and will test, JOID waiting for a patch
-**Issue:** Scenarios are not fully known, planned out or mapped to lab/test cycle
-**Owner:** Debra
-**Status:**  Closed. Scenarios are frozen. No feature projects which are able to deploy with installers have reported that their scenarios are not supported. [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
-**Issue:** Doctor install requirements - Aodh as critical component
-**Owner:** Ildiko, Ryota
-**Status:** Apex has a patch up but not working. Fuel patch is not completed. Looking now at post-install integration. May not make this release.
 **Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** 1/15/16  We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before next Tues installer code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
 **===============================================================================================================**
 __**Pod Status:**__
--Intel POD2 is back up
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
--CI PODs for Fuel back online
+[[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
-LF-POD2: is up
+All pods are currently working and in use.
-Ericsson-POD2: is bac up
-[[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
 **===============================================================================================================**
-**Scenario Status:** Scenarios are frozen. No feature project has reported that their scenarios are missing or unsupported
+**Scenario Status:**
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
+scenario’s which are approaching stable across installers are: nosdn ,onos ,odl(be) - once integrated ,odll3(be) ,ova, doctor, sdnvpn.  We are reasonably confident of having those release ready in a couple of weeks.
+To be stabilised include SFC, KVM and OCL which could potentially come in under a stable release or in C.  Dependant on the project teams efforts and targets.
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)  Current situation
+Functest (Morgan Richomme)
-*****************
+       -we fixed a patch that triggers some regression on Functest
-as you can see from a CI perspective, we were able to run successfully Functest
+       -we are now analyzing the errors linked to Tempest on the different installers
-https://build.opnfv.org/ci/view/functest/
+       -please review test status on wiki https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary
+       -we identified during the weekly meeting the list miles (some vPing on odl_l3 and onos scenario) + boosting Tempest results on apex, fuel and joid
+       -Apex: Tempest failed to run so we don't actually know if it fixed it or not Vping passed on L3 ODL and yardstick passed on ODL L2
+       -Kicking off a new Apex run now that Be is the target ODL version
+       -http://artifacts.opnfv.org/logs/functest/opnfv-jump-1/brahmaputra/2016-02-03_19-05-12/brahmaputra/tempest/tempest.log
+example of log pushed to artifact (here tempest log on apex)
-the following scenario were "runnable" on Stable/Brahamputra branch:
+       -http://artifacts.opnfv.org/logs/functest/opnfv-jump-1/brahmaputra/2016-02-03_19-05-12/brahmaputra/rally/opnfv-neutron.html
-- compas/odl_l2-nofeature-ha
-- fuel/odl_l2-nofeature-ha
-- joid-odl_2-nofeature-ha
-and on Master (because not available
+Yardstick:ONOS -
-- apex/onos-nofeature-ha
+       -
+       -continuing rebasing for fuel8
+*===============================================================================================================**
+__**Installer Status:**__
-but it is only from a CI point of view
+**Apex** (Tim Rozet):
-when we dive into the details, the results are not at the same level and it is difficult to get stable results
-=> different  from one run to another, we are far from a stable run as defined during le summit (and as far as I understood there are still some major patchs on some installer side)
-see details on
-- https://wiki.opnfv.org/vping_brahmaputra_page
-- https://wiki.opnfv.org/tempest_brahmaputra_page
-- https://wiki.opnfv.org/vims_brahmaputra_page
-for odl tests some are 18/18 OK some 0 and it is not stable
+**JOID** (Narinder Gupta) Continue to work on OpenContrail issues. It deploys now but doesn't run with OpenStack Liberty. We migrated to Be yesterday and last night run was success from installer prospective
-feature projects
+**Compass4nfv** (Weidong Shao)
-*****************
-regarding the integration of feature projects
-we are ready for:
-- doctor
-- promise
-- ovno
-- onos
-but as far as I know now, none of these tests have been run from CI
+**Fuel** (Jonas Bjurel)
-fist manual test done on onos
+[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
+Overall status on Fuel and its OPNFV feature collaboration projects:
+Since the end of last working week, Fuel has converged dramatically and we’re getting consistent positive data from the deploys.
+We have performed massive runs over the week-end, and I can’t find one deployment with known working scenarios that has failed yet,
+we have performed 20 official OPNFV deploys - distributed over the known good scenarios and master/stable branch (The branches are currently almost identical)
+– and no single one failed.
+In addition we have ran 10 unofficial deploys with Fuel health check running (on my pretty hefty workstation), and no single one failed there either!
+Without going into details, I’m positively surprised about the consistency!
+A few issues:
+There are 2 issues though:
+-          We seem to have an issue with LF-POD2 setup, causing func-test and yard-stick to fail, hitting the stability for stable.
-docs
+I will swap the ci runs such that stable/Brahmaputra runs on Ericsson-POD2 and master on LF-POD2 and after that
-*****
+we will start troubleshooting on LF-POD2. We need both, but statistics on stable/brahmaputra is more important
-docs have been initiated
-- a user guide => http://artifacts.opnfv.org/functest/docs/userguide/index.html
-- a config/installation guide => http://artifacts.opnfv.org/functest/docs/configguide/index.html
-- a developper guide => http://artifacts.opnfv.org/functest/docs/devguide/index.html
-work in progress
+than that on master right now!
-as a conclusion
+-          We have issues with a few plugins:
-I would say that the status is Yellow/Red due
-- to stability issues
-- late integration of feature projects
-- difficulty to get env to work (no system available on Monday)
-some work could be postponed to RC1 (if we follow apex approach, we could do something similar)
+o   BGP-VPN: No big deal, there is a patch for it and we will merge it to master tomorrow, and to stable on Tue.
+o   NFVKVM: This project is focusing on yardstick SLA test-cases aside of a true deployment (using bridges instead of OVS),
-Yardstick (Ana Cunha)  troubleshooting Joid, Compass, Fuel and Apex, working on integrated test result db.
+they install a new kernel for which tere is no OVS kernel driver in the packages. All though they’re working on it
-Requested help with SSH issues.
+I’m not sure they will make it for our time plan – not even sure we need to wait for it since it is as a “technology project”
+verified by yardstick, but not yet deploying in a real environment. I would vote this to included in SR1 of Fuel@OPNFV B-release.
+o   SFC, though we have been integrating SFC base features into fuel, the SFC team have gone with architecture that requires
+tacker as an orchestrater (although tacker is explicitly outside of the B-release). The SFC team has started on a Tacker Fuel
+plugin – and as the plug-in architechture provides proper fensing to the core of Fuel, we can wait and see if they come with
+something that works. Their deadline is Thu Feb 11 – but I don’t expect them to make it, hope I’m cut by surprise!
-**===============================================================================================================**
-__**Installer Status:**__
+Reporting:
+I have included my reporting into this ether-pad: https://etherpad.opnfv.org/p/steps_to_brahmaputra as a link
+BTW: Would it be possible to retrofit/rebase the Brahmaputra release WIKI to something where it is easy to find what is
+on our top prio today – at least I have difficulties to follow it right now.
+Fuel@OPNFV’s input to the status and the plans:
+-          This is our end-game status, that will be updated daily: https://wiki.opnfv.org/fuel_opnfv/b_release_status
-**Apex** (Tim Rozet): no new status for 1/19 see 1/18 status below
+-          This is our end-game plan, updated twice a week: https://wiki.opnfv.org/fuel_opnfv_b-wp
-**JOID** (Narinder Gupta) JOID team is working on documentation part of it and most likely would be completed by tomorrow. From functionality wise it is complete but documentation need some work to finish.
-**Compass4nfv** (Weidong Shao) no new status for 1/19 see 1/18 status below
-**Fuel** (Jonas Bjurel) no new status for 1/19 see 1/18 status below
-[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-Pod downtime caused severe damage to week-end work. Had planned to test upstream Fuel for our code freeze.
 **===============================================================================================================**
 __**Project Updates:**__ (as provided)
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
-**ARMband:**
+**Availability：**（Qiao Fu)
 **Bottlenecks:** (Hongbo Tian)
-**Copper:** (Bryan Sullivan) Call out for helping hands if anyone is available
+**Copper:** (Bryan Sullivan)
-**Doctor** (Ryota, Ildiko) There is not good progress in aodh support in apex and the upstream project [1,2].
+**Doctor** (Ryota, Ildiko)
-Being complete by today is not realistic...
-I think we can create post-installer, but the concern is whether we can complete the development by the deadline.
+**HA**(Fu Qaio)
-[1] https://review.openstack.org/#/c/241408/
-[2] https://gerrit.opnfv.org/gerrit/#/c/6631/
 **IPv6:** (Bin Hu) -
-**LSOAPI** (Kevin Leuhrs) at risk, potential loss of PTL
 **NFV4KVM:** (Don Dugger, Raghuveer Reddy)
@@ Line 1927: / Line 1485: @@
-**OPNFVdocs** (ChrisPriceAB:)
+**OPNFVdocs** (Chris Price)
-Issues:
-The code freeze date will not be met given the current state of Brahmaputra documentation.
+**OVNO** (Stuart Mackie)
 **Parser**
-**Prediction** (Hai Liu) Prediction project has completed requirements document. Code is under development, not ready yet. It is not  integrated to a installer now.
+**Promise** (Gerald Kunzmann)
+**Prediction** (Hai Liu)
 **Qtip** (Vikram)
@@ Line 1941: / Line 1501: @@
 **SDNVPN** (Tim Irnich)
-first successful deployment in CI happened yesterday, thanks to Fatih for setting up Jenkins.
-https://build.opnfv.org/ci/job/fuel-deploy-virtual-daily-brahmaputra/8/console
-We will now rebase our plugins to Fuel8 and as soon as we can deploy ODL Be we can start running our E2E tests in CI as well.
-Big thanks to all contributors!
-**SFQM** (Maryam Tahhan) For SFQM all the contributions went upstream to DPDK – DPDK won’t be integrated with an installer for release B – it was more a case of getting the features in place to allow us to integrate with an installer in the next release – do we will only be releasing documentation as part of rel B
-**StorPerf**
+**SFQM** (Maryam Tahhan)
+**StorPerf** (Mark Beierle)
 **===============================================================================================================**
 **Action Items**__Underlined Text__
-**Action:** add Contrail scenarios to scenario staging page on wiki
+**Action:** Create a dashboard view of Yardstick that shows all scenarios, all tests run per scenerio, all tests remaining to be run, and all tests that fail; Include feature support
-**Owner:**  Stuart Mackie
+**Owner:** Ana Cuna
-**Status:** done
+**Status:** assigned 2/4/16
-**Action:**Review Scenarios and make sure your test case configuration requirements are covered (details in Scenario status)
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-**Owner:**Feature project PTLs
+**2/5/16**
-**Status:** Done
-__**Action:**__Send out a reminder to feature projects to finalize scenarios
+Countdown to Release: **TBD days**
-**Owner:**Debra
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] under revision with proposed milestones dates until we work out details. TSC approved release delay but chose to wait one more week before setting date in hopes that by then some issues will be resolved allowing for better estimations of time; Etherpad currently proposed release date is 3/8; we also have a matrix of the scenarios and their pass/fail/stable status which will help drive decisions
-**Status:** done
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------**1/18/16**
-Countdown to Release: **15 days**
-[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]]
 **===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-18-14.30.html|1/18/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-05-14.30.html|2/5/16]]
 __**Top Accomplishments & Important Updates since last report**__
-  .Scenarios are frozen. Soliciting updates from all feature projects to see which if any will be dropped due to no test scenario.
+.Yardstick runs successfully with ODL Beryllium without work around; Investigating impact to other projects if we switch to Be from Li for all ODL scenarios, this will be discussed on the email lists
-  .ONOS code is fully merged and works in virtual deployments with Apex
-  .Apex will cut an RC1 later this week
+.Functest
-  .KVM4NFV has an updated script to create the KVM Fuel plugin with OVS support, trying to integrate before freeze
+       -A full list of tests they have run per scenario, which tests have passed or failed, which features are supported by those scenarios, and which remain to be tested for the first time is available [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary|here]] Keep in mind that this is a static page, if you need more current information then visit the test dashboard
-  .PolicyTest project will not release with Brahmaputra, will target C release
+       -according to success criteria, we have already 1 validated scenario: compass/onos
-  .Copper, LSOAPI will pursue post-install deployment options
+       -another one just needs iterations to be validated: compass/nosdn
-  .Doctor still working on potential installer deployment but likely will pursue post-install deployment
  **===============================================================================================================**
 __**Top Issues**__
-**Issue:** Getting RC0 out
+**Issue:** have passed intended release date. Test cycles for each scenario take a significant amount of time. Even if all installers & scenarios are working properly it takes 7 days to run test through them all. Need to set a plan to identify new release date
 **Owner:** Debra
-**Status:** dependencies to be closed on labs, CI, tests, and installers
+**Status:** TSC voted to delay release rather than trying to phase release. Debra & key community members to identify remaining work and develop reasonably accurate schedule to propose to TSC. On Tuesday TSC was not comfortable setting a date while such significant issues remained in troubleshooting status for test projects. Major breakthroughs have been achieved in the past 2 days making better reasoned schedule estimates possible. Current estimate is Mar 8 release; Functest has created a wiki page that gives good overview of all tests run in each scenario and which features these scenarios support. Working on same visibility for Yardstick. These, along with test runs through all scenarios will help us identify what is ready to release now and what might need more work. Proposal is made for all hw resources to be applied to stable branch testing until this is complete
-Apex has RC0, other installers are working on final integration & bugs. Installer code freeze Jan 19.
-**Issue:** Fuel is not ready to code freeze. Pods down over weekend prevented testing/progress with validation of integrated upstream code.
+**Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
-**Owner:** Jonas Bjurel
+**Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
-**Status:** LF POD 2 is back up but waiting full deployment to validate everything is working. Ericsson POD 2 had hardware issue with switch. Working to bring it back up.
+**Status:** -regression on Tempest suite (investigation to know if it is in Functest or upstream) continues.
+            -working through scenarios in logical order coordinated with Yardstick, deployment and feature projects as needed to allow for additional testing & troubleshooting
+Yardstick:   -odl scenarios - identified that with ODL Beryllium, Yardstick passes. With ODL Lithium a workaround is required. Investigating impact on other projects if the supported version of ODL is switched ot Be for all ODL scenarios
+             -working on bug fixes, docs and troubleshooting
-**Issue:** OpenContrail does not deploy
+**Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
-**Owner:** Stuart Mackey
+**Owner:** Ray Paik
-**Status:** Compass got vrouter and GUI up, Apex has a build and will test, JOID waiting for a patch
+**Status:**Scott discussed status during TSC meeting; Chris to post instructions online for license inclusion. Projects have made good progress on correcting issues. Scott rerunning scan to see if any projects need to address additional issues
-**Issue:** Scenarios are not fully known, planned out or mapped to lab/test cycle
+**Issue:** Scenarios are frozen, but significant number not working yet, or have not been tried
-**Owner:** Debra
+**Owner:** test teams
-**Status:**  [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
+**Status:** Continuing to run & debug scenarios in coordinated manner, see above status
-**Issue:** Doctor install requirements - Aodh as critical component
-**Owner:** Ildiko, Ryota
-**Status:** Apex has a patch up, we are trying to get it to work.
-**Issue:** NFVKVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
+**Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** New 1/15/16  We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before next Tues installer code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
 **===============================================================================================================**
 __**Pod Status:**__
--Intel POD2 is not up, so there is only 1 POD for Apex
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
--all CI PODs for Fuel has been down since Thursday last week. Just coming back online on Monday.
-LF-POD2: A deployment is running on it at the moment to see if Peter Bandzi's fixes solved the issue
-. we could not get to jumphost via SSH, once we turned off other nodes from pod2 then we were able to access
-. issue we have wrongly configured PXE bridge on jumphost, after reconfig on linux nbow it looks that it is ok.... at least deployment still in progrees (but nodes were recognized by fuel now). LF POD2 status will be updated when/once the deployment succeeds
-Ericsson-POD2: Reason HW fault we had problem with switch - WIP. Contact person Erik Reukers who have been working together with the vendor of the failed equipment over the week-end.
 [[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
 **===============================================================================================================**
-**Scenario Status:** Scenarios are frozen
+**Scenario Status:**
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
-[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-working on common database for test results: ·       We’re consolidating all test result aggregation/visualization on a single server:
-o   Testresults.opnfv.org (also testdashboard.opnfv.org)
+Functest (Morgan Richomme)
+       -no update since yesterday. please review test status on wiki https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary
+       -
+       -http://artifacts.opnfv.org/logs/functest/opnfv-jump-1/brahmaputra/2016-02-03_19-05-12/brahmaputra/tempest/tempest.log
+example of log pushed to artifact (here tempest log on apex)
-·       The sever will have
+       -http://artifacts.opnfv.org/logs/functest/opnfv-jump-1/brahmaputra/2016-02-03_19-05-12/brahmaputra/rally/opnfv-neutron.html
-o   Test results data base (MongoDB) – which Morgan just installed
+Yardstick:ONOS -
+       -breakthrough with ODL scenarios using ODL Beryllium
+       -continuing rebasing in progress for fuel8
+       -working on building easy to read status report
+*===============================================================================================================**
+__**Installer Status:**__
-o   Yardstick specific data base (InfluxDB) – Ana is about to bring this up
+**Apex** (Tim Rozet):
-o   ELK stack for test dashboard (already installed – needs integration with MongoDB) – Peter is the PoC for ELK
-o   Grafana (for Yardstick visualization) – Ana completed InfluxdB and Grafana installed, port assignment updated: https://wiki.opnfv.org/opnfv_test_dashboard#test_results_server
+**JOID** (Narinder Gupta)
-o   Morgan created  cronjob calling (every hour) a script consuming the  API locally
-it generates results int he following folder (based on the work done by the project to consolidate their results)
-├── res
+**Compass4nfv** (Weidong Shao)
-│   ├── bottleneck
-│   ├── functest
-│   ├── qtip
-│   ├── vsperf
-│   └── yardstick
-and if we go in one particular folder, we got json results
+**Fuel** (Jonas Bjurel)
+[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-│   ├── functest
+**===============================================================================================================**
-│   │   ├── res_functest_Tempest_apex.json
+__**Project Updates:**__ (as provided)
-│   │   ├── res_functest_Tempest_compass.json
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
-│   │   ├── res_functest_Tempest_fuel.json
-│   │   ├── res_functest_Tempest_joid.json
-│   │   ├── res_functest_Tempest.json
-│   │   ├── res_functest_vIMS_apex.json
-│   │   ├── res_functest_vIMS_compass.json
-│   │   ├── res_functest_vIMS_fuel.json
-│   │   ├── res_functest_vIMS_joid.json
-│   │   ├── res_functest_vIMS.json
-│   │   ├── res_functest_vPing_apex.json
-│   │   ├── res_functest_vPing_compass.json
-│   │   ├── res_functest_vPing_fuel.json
-│   │   ├── res_functest_vPing_joid.json
-│   │   └── res_functest_vPing.json
-so we have post processed results that should be easily "graphable"
+**Availability：**（Qiao Fu)
-Functest (Morgan Richomme)  see above, working on integrated test result db
+**Bottlenecks:** (Hongbo Tian)
+**Copper:** (Bryan Sullivan)
-Yardstick (Ana Cunha)  see above, no new update still troubleshooting Joid, Compass, Fuel and Apex, working on integrated test result db
+**Doctor** (Ryota, Ildiko)
+**HA**(Fu Qaio)
-**===============================================================================================================**
+**IPv6:** (Bin Hu) -
-__**Installer Status:**__
-**Apex** (Tim Rozet):
+**NFV4KVM:** (Don Dugger, Raghuveer Reddy)
-we will build another candidate (RC1) sometime within the next few days.
-Progress since last update:
+**ONOSFW:** (Ashlee Young)
-.  Awesome work by Dan and Michael to get the RPM split done, our RPMs are now split into 3:
-apex/opnfv-apex-2.1-20160117.noarch.rpm
-apex/opnfv-apex-common-2.1-20160117.noarch.rpm
-apex/opnfv-apex-undercloud-2.1-20160117.noarch.rpm
-.  ONOS code is fully merged and works in virtual deployments (baremetal and functest results pending) - thanks Bob and ONOS team for all the help integrating
-.  Scenarios were all added Friday to Apex Jenkins: https://build.opnfv.org/ci/view/apex/ (ONOS and ODL L2 are now part of our CI verify and daily)
-.  ODL L3 patch has been pushed and passed initial round of CI: https://gerrit.opnfv.org/gerrit/#/c/6995/6
-TODO:
+**OpenvSwitch** (Mark Gray)
-.  Dan is working on OpenContrail integration.
-.  Michael is working on getting AODH support for Doctor into Apex.  Patch WIP: https://gerrit.opnfv.org/gerrit/#/c/6631/
-.  I'm working on getting SFC support.  Plan is to build Apex RPM with Be version of ODL included, and I'm writing up some ansible modules to update kernel, install NSH OVS, and Tacker.
-.  Yardstick was integrated into Apex, but is failing during run.  Will debug that with Yardstick team.
-For our RC1 build my goal is to include ONOS and ODL L3.  As soon as we feel those are both stable, with good functest results, we will build RC1.
+**OPNFVdocs** (Chris Price)
-**JOID** (Narinder Gupta)
+**OVNO** (Stuart Mackie)
+**Parser**
-**Compass4nfv** (Weidong Shao)
+**Promise** (Gerald Kunzmann) We have successfully verified Promise in both Joid and Fuel scenarios: https://wiki.opnfv.org/promise_brahmaputra_page
+Promise functest results are already pushed to the functest database http://testresults.opnfv.org/testapi/results?case=promise
+(you will still see some failures, but those are due to issues with the scenarios, not Promise code)
+**Prediction** (Hai Liu)
+**Qtip** (Vikram)
-**Fuel** (Jonas Bjurel)
-[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-Pod downtime caused severe damage to week-end work. Had planned to test upstream Fuel for our code freeze. Now may need to request additional days before we freeze. Almost all scenarios run fine virtual on stable.
-We have some more rebasment work to do, but we are close! since tonight we’re back with one lab running stable, we’re still without the lab for master and cannot test re-basements or bug-fixes L
-Upstream is no longer broken, but at this point say it is reliable is a stretch!
-From stable we’re successfully running most of the 6x2 scenarios (x2 because BM and virtual).
-Although a lot of results point to the positive quarter of the pie, I’m reluctant to declare victory just yet – not the least because our week-end engagement was
-a complete turn-down (little can be achieved without labs).
-What is done (some still waiting final verification on master due to lab outage):
--          Documentation 95% ready
--          Fuel8/Liberty uplift ready
+**SFC** (Brady Johnson)
--          Fuel8 rebasing of ODL + NSH, GPB + Berryllium ready
+**SDNVPN** (Tim Irnich)
--          ONOS uplift to Fuel 7
--          Almost all of the 6x2 scenarios are running on virtual deployment and stable/Brahmaputra
+**SFQM** (Maryam Tahhan)
-What is left till code-freeze:
+**StorPerf** (Mark Beierle)
--          Be able to verify un picked changes on master to stable – pending lab availability (HW replacement is ongoing in Ericsson POD-2)
--          Re-basement of following OPNFV collaborative project plug-ins:
+**===============================================================================================================**
+**Action Items**__Underlined Text__
+**Action:** Create a dashboard view of Yardstick that shows all scenarios, all tests run per scenerio, all tests remaining to be run, and all tests that fail; Include feature support
+**Owner:** Ana Cuna
+**Status:** assigned 2/4/16
-o   VSPERF
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+**2/3/16 and 2/4/16**
-o   VFVOVS
+Countdown to Release: **TBD days**
+[[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]] under revision with proposed milestones dates until we work out details. TSC approved release delay but chose to wait one more week before setting date in hopes that by then some issues will be resolved allowing for better estimations of time; Etherpad currently proposed release date is 3/8; we also have a matrix of the scenarios and their pass/fail/stable status which will help drive decisions
+**===============================================================================================================**
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-03-14.30.html|2/3/16]]
+[[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-02-04-14.30.html|2/4/16]]
-o   NFVKVM
+__**Top Accomplishments & Important Updates since last report**__
-o   BGP-VPN
+.Excellent progress by test teams today in overcoming blocking issues
-o   SFC-OVS
+.Functest
+       -becoming more stable on scenarios that it has been able to run.They successfully identified and fixed the issue they were having with vPing and SSH on ODL scenarios.
-Work on this is ongoing, but is to a large degree outside the Fuel project boundaries – although we want them to succeed – and do everything in our power to help them (remember our abilities are constrained by our relatively small work-force).
+       -A full list of tests they have run per scenario, which tests have passed or failed, which features are supported by those scenarios, and which remain to be tested for the first time is available [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary|here]] Keep in mind that this is a static page, if you need more current information then visit the test dashboard
-We believe we can declare code-freeze end this week/beginning next, meaning the installer integration code is frozen for development, however – we need to be flexible to changes from upstream and side-stream – that will always be our
+       -according to success criteria, we have already 1 validated scenario: compass/onos
-Challenge.
+       -another one just needs iterations to be validated: compass/nosdn
-**===============================================================================================================**
+.Yardstick
-__**Project Updates:**__ (as provided)
+       -have a work around in place for networking issues with ODL scenarios, these issues seem to be Lithium related, troubleshooting continues
-**ARMband:**
-Fuel Port for arm64 support in Fuel 7 (and then Fuel 8) is two pieces:
-Setting up public mirror containing arm64-based packages needed to build target images for controller and compute nodes
-This work is in progress – we have our mirror set up and are now building and populating.
-We hope to have the mirror and repos with packages available mid-week.
-Modifying the code in Fuel to support arm64, where it needs to change
-This work is also in progress.
-I am not exactly sure when this will be up and working, but it should be pretty soon.
-Functest work currently being targeted at running against Arno SR1.
-Currently getting our 5-node HA pod up and running Arno SR1 (using Fuel 6.1 in this case).
-When this works and when our Fuel 7 porting work is done, we will shift this to run Fuel 7 (and then Fuel 8) and
-  Our plan for release testing is to integrate our lab with Jenkins when we have Functest running against Fuel 7/8 (Brahmaputra).  At that point we hope to run as many scenarios as can be targeted at a Fuel-based environment – some of these may not run on arm64, and we’ll either debug or document those.
-  Our documentation plan is fuzzy at the moment.  We will likely base it on the Fuel project's documentation for how to set up, configure, and install OPNFV, with arm64 exceptions and specifics.
+ **===============================================================================================================**
-**Bottlenecks:** (Hongbo Tian) Bottlenecks has two test tools named rubbos and vstf.
+__**Top Issues**__
-Rubbos runs successfully on fuel  Brahmaputra branch, compass  Brahmaputra branch.
-Vstf runs successfully on fuel Brahmaputra branch.
-Bottlenecks tests are performed in LF POD2(NOSDN scenario) and Huawei  POD(NOSDN scenario)
-By now, for SDN scenarios both pods installed openstack have network ssh connect failure issues, it’s the problem caused by the installers when they want to integrate openstack and ODL, they are working to solve this.
-**Copper:** (Bryan Sullivan) Planning to check out a new hosting service for OPNFV testbeds provided by Ravello, that Iben has been arranging. Have a post-install script working, but not fully scripted/automated yet… so I would not call it per the goal. I do have a smoke test scenario I have also scripted, and it works.
+**Issue:** have release date. Test cycles for each scenario take a significant amount of time. Even if all installers & scenarios are working properly it takes 7 days to run test through them all.
+**Owner:** Debra
-If I can get one of the RC builds running there it may accelerate test/development of my B release goals. But for now I'm at the same state as of New Years. Still trying to get project supporters to be more active, not sure why that isn't happening (other than that this is complex stuff, and/or they are busy on other projects).
+**Status:** TSC voted to delay release rather than trying to phase release. Debra & key community members to identify remaining work and develop reasonably accurate schedule to propose to TSC. On Tuesday TSC was not comfortable setting a date while such significant issues remained in troubleshooting status for test projects. Major breakthroughs have been achieved in the past 2 days making better reasoned schedule estimates possible. Current estimate is Mar 8 release
-For now, my B release goal is to have at least one installer completed and ready to demo at the March Hackfest.
+**Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
+**Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
+**Status:** -regression on Tempest suite (investigation to knwo if it is in Functest or upstream) continues.
+            -working through scenarios in logical order coordinated with Yardstick, deployment and feature projects as needed to allow for additional testing & troubleshooting
+Yardstick:   -odl scenarios - have workaround in place for vping and ssh which allows for further testing & debug
+             -working on bug fixes, docs and troubleshooting
-**Doctor** (Ryota, Ildiko) I have update only on Fuel, which is that we will need to write a plug-in to deploy Aodh, which is the alarming component we need. Ryota can give you an update on Apex.
+**Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
+**Owner:** Ray Paik
+**Status:**Scott discussed status during TSC meeting; Chris to post instructions online for license inclusion. Projects have made good progress on correcting issues. Scott rerunning scan to see if any projects need to address additional issues
-If we will not be finished with the installer coverage I think we will shoot for the post install script.
+**Issue:** Scenarios are frozen, but significant number not working yet, or have not been tried
+**Owner:** test teams
+**Status:** Continuing to run & debug scenarios in coordinated manner
-**IPv6:** (Bin Hu) -          Major accomplishment:
+**Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
+**Owner:**Don Dugger/Raghuveer Reddy
+**Status:** no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
+**===============================================================================================================**
+__**Pod Status:**__
-o   CI integration with Huawei’s Pharos Lab in Santa Clara is completed.
+Request Jira ticket be logged for any and all issues as email responses are difficult to keep track of. We need clearer communication.
-o   Worked with Apex, Compass Fuel and Joid for installation scenarios and command line parameters, and related sourcing credential methods. Currently it is up to date.
+[[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
-o   Complete content transfer to opnfvdoc template so that toolchain can pick it up into an integrated document
+**===============================================================================================================**
+**Scenario Status:**
+All scenarios which features they support and which have passed/failed/not run yet in functest is located [[https://wiki.opnfv.org/functextnexttaks#brahmaputra_summary]]
+Have asked for a similar view to be constructed for Yardstick
-o   Draft Preview Version of Release Document (IPv6): http://artifacts.opnfv.org/ipv6/docs/reldoc/index.html
+**===============================================================================================================**
+__**Release Test Status:**__
--          To-Do:
-o   Continue testing and debugging auto script for ODL-L2 scenario for Yardstick
+Functest (Morgan Richomme)
+       -according to success criteria, we have already 1 validated scenario: compass/onos
+       -another one just needs iterations to be validated: compass/nosdn
+       -some are closed but the criteria of 90% of success on Tempest is not reached
+       -support on troubleshooting the Tempest error / scenario / installer welcome --
+       -morning errors on CI were not due to tests but to result pushed in artifacts (need config on jumphosts), now artifacts are pushed
+       -joid has better results on non CI POD (Orange POD2) regarding Tempest (92%), so just considering CI POD could be unfair for installer if PODs have some network issues
-§  vPing test case failed, probably due to bugs in Compass and Fuel installer. Kubi is working on it.
+       -http://artifacts.opnfv.org/logs/functest/opnfv-jump-1/brahmaputra/2016-02-03_19-05-12/brahmaputra/tempest/tempest.log
+example of log pushed to artifact (here tempest log on apex)
-o   Continue to work on / polish / clarify documentation as needed
+       -http://artifacts.opnfv.org/logs/functest/opnfv-jump-1/brahmaputra/2016-02-03_19-05-12/brahmaputra/rally/opnfv-neutron.html
-o   Continue to work with Installers for any update of command line parameters of deployment scenarios, as needed and applicable
+Yardstick:ONOS -
+       -works for ONOS (Compass) and nosdn (Compass and Fuel7) - rebasing in progress for fuel8
+       -on-demand tests (not CI PODs) - HA, KVM - works
+       -Parser test case OK (will be run on weekly)
+       -vTC verified daily and weekly on Ericsson POD1
+       -ipv6 test case runs on Compass Huawei SC POD
+       -working on bug fixes, docs and troubleshooting
+**===============================================================================================================**
+__**Installer Status:**__
--          Issues:
+**Apex** (Tim Rozet):
-o   None
--          Blockers:
+**JOID** (Narinder Gupta)
-o   None.
+**Compass4nfv** (Weidong Shao)
+**Fuel** (Jonas Bjurel)
-Regarding “specific scenarios that will support ipv6 testing during Brahmaputra”, see our preview release document: http://artifacts.opnfv.org/ipv6/docs/reldoc/index.html. In short:
+[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
--          Scenario 3 and 4 are supported by Apex and Fuel (OS+ODL-L2)
-o   Auto testing script (Yardstick) is being tested and debugged (see the first item of To-Do above)
+**===============================================================================================================**
+__**Project Updates:**__ (as provided)
+Please find current Jira dashboards for each project here [[https://wiki.opnfv.org/releases/brahmaputra/release_plan#current_jira_dashboards]]
--          OpenStack-only scenario is supported by Fuel, Compass and Joid.
+**Availability：**（Qiao Fu)
-o   Auto testing script (Yardstick) is working
+**Bottlenecks:** (Hongbo Tian)
-o   This scenario is not officially listed as B release (because it is OpenStack only), but already supported by 3 installers
+**Copper:** (Bryan Sullivan)
-**LSOAPI** (Kevin Leuhrs)
+**Doctor** (Ryota, Ildiko)
-**NFV4KVM:** (Don Dugger, Raghuveer Reddy) have an updated script to create the KVM Fuel plugin with OVS support, don’t know if it’ll be integrated by tomorrow, we’re still hoping to get it in.
+**HA**(Fu Qaio)
-Raghu has been looking into scenarios
+**IPv6:** (Bin Hu) -
+**NFV4KVM:** (Don Dugger, Raghuveer Reddy)
 **ONOSFW:** (Ashlee Young)
-**OpenvSwitch** (Mark Gray) We have code upstreamed to stable/Brahmaputra and are running it against the CI. I guess this is the scenario that we will support
+**OpenvSwitch** (Mark Gray)
-https://build.opnfv.org/ci/job/fuel-os-nosdn-ovs-noha-opnfv-jump-2-daily-brahmaputra/
-It is currently queued for execution.
+**OPNFVdocs** (Chris Price)
+**OVNO** (Stuart Mackie)
-**OPNFVdocs** (ChrisPriceAB:) The toolchain is now in place and he have a pending patch which outlines the schema and output for the composite files.
+**Parser**
-https://gerrit.opnfv.org/gerrit/#/c/7017/
-http://artifacts.opnfv.org/review/7017/configguide/index.html
-http://artifacts.opnfv.org/review/7017/userguide/index.html
-When integrated projects update their composite content on master they should see it popping up in the above links.  Un-integrated projects should reach out to Sofia or I to get their content in place asap.
-Current focus:
+**Prediction** (Hai Liu)
-Ensure the templates are being filled by projects now that we can publish them here.
-Editorials on text and structure for the incoming documentation
-Cherry-picking our patch backlog to stable.
-Issues:
-The code freeze date will be difficult (nigh impossible) to meet given the current state of Brahmaputra documentation.
-**Parser** completed testing work with yardstick, and I think yardstick team could provide you which scenario would support Parser test.
-From installer side, Compass would be able to install Parser’s yang2tosca module, and Parser’s heat2tosca is already merged in Heat therefore all the installers would be able to install heat2tosca when they install Heat. Parser also support standalone installation should user decide to do so.
-One work I am doing now is to try to cherry pick our latest docs update to B release stable branch.
-**Policytest** (Keith Burns) too many tangential issues with OVS, openstack and SFC to make this a reality. We can test vanilla GBP Policy in Openstack, this has worked since lithium, but my focus has been too fractured to get this done for this release to have time to deal with all the unfamiliar JIRA process. Will target C release.
-**Prediction** (Hai Liu) Prediction project has completed requirements document. Code is under development, not ready yet. It is not  integrated to a installer now.
 **Qtip** (Vikram)
@@ Line 2275: / Line 1795: @@
 **SDNVPN** (Tim Irnich)
-Deployment through Fuel has been successfully tested in an Ericsson lab but not in a Pharos lab. Our main achievement last week was to get our first deployment scenario merged so that we are now ready with all we need for CI integration except having Jenkins jobs set up. I am expecting this to happen on Monday.
-We are not intending testing deployment in a Pharos lab outside CI.
-Progress with documentation has been slowed down by the ODL code freeze deadline Thu last week which we had to prioritize (resources are overlapping with ODL VPN Service project) so I expect this to get back to speed now.
-In parallel we have started to work with rebasing our plugins to Fuel 8.0 and are preparing for the ODL Beryllium inclusion what will happen in the context of rebasing the ODL plugin.
-**StorPerf** pursuing post-install configuration. follow the StorPerf instructions on how to get the StorPerf docker image downloaded into your OPNFV lab and run it manually.
-**===============================================================================================================**
+**SFQM** (Maryam Tahhan)
-**Action Items**__Underlined Text__
-**Action:** add Contrail scenarios to scenario staging page on wiki
-**Owner:**  Stuart Mackie
-**Status:** assigned 1/15
-**Action:**Review Scenarios and make sure your test case configuration requirements are covered (details in Scenario status)
+**StorPerf** (Mark Beierle)
-**Owner:**Feature project PTLs
-**Status:** Deadline Jan 15, in progress. Due close of business 5pm Pacific.
-__**Action:**__Send out a reminder to feature projects to finalize scenarios
+**===============================================================================================================**
-**Owner:**Debra
+**Action Items**__Underlined Text__
-**Status:** done
+**Action:**
+**Owner:**
+**Status:**
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-**1/15/16**
-Countdown to Release: **18 days**
+**1/28/16**
+Countdown to Release: **TBD days**
 [[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]]
 **===============================================================================================================**
-**Minutes from daily standup** [[http://meetbot.opnfv.org/eavesdrop/%23opnfv-release/%23opnfv-release.2016-01-15.log.html|1/15/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-28-14.30.html|1/28/16]]
-__**Top Accomplishments since yesterday**__
+__**Top Accomplishments & Important Updates since last report**__
+.TSC voted to move code freeze to Friday 1/29 and to extend release date (to be defined). Debra and key community members to evaluate remaining work and recommend new release date with solid schedule to achieve that.
-  .Compass got vrouter and GUI up for OpenContrail
-  .Apex has a build for OpenContrail and will test
  **===============================================================================================================**
 __**Top Issues**__
+**Issue:** We are at high risk of missing release date. Test cycles for each scenario take a significant amount of time. Even if all installers & scenarios are working properly it takes 7 days to run test through them all.
+**Owner:** Debra
+**Status:** TSC voted to delay release rather than trying to phase release. Debra & key community members to identify remaining work and develop reasonably accurate schedule to propose to TSC.
+**Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
+**Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
+**Status:**
+Yardstick:ONOS - successfully run with Compass. ODL scenario - debugging on-going, Yardstick will not run with ODL. Narrowing down subsystems involved. Working on SFC test cases. Working on influxdB+grafana
 **Issue:** Getting RC0 out
 **Owner:** Debra
-**Status:** dependencies to be closed on labs, CI, tests, and installers
+**Status:**  Installer code freeze extended due to Fuel trying to stabilize with upstream. Compass also troubleshooting some functest and other instability with the code base, need some extra time in getting Compass code stable. Apex, JOID ready to freeze
-Apex has RC0, other installers are working on final integration & bugs. Installer code freeze Jan 19.
+**Issue:** Fuel is not ready to code freeze. Upstream Fuel is not stable.
+**Owner:** Jonas Bjurel
+**Status:** autodeploy issue, hopefully solved now. Testing. Scenarios being rebased
+**Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
+**Owner:** Ray Paik
+**Status:**Projects have made good progress on getting patches in to fix the files. Scott is making another license scan to see what if anything is outstanding. Thank you to all who have responded to this request in such a timely manner.
 **Issue:** OpenContrail does not deploy
 **Owner:** Stuart Mackey
-**Status:** Compass got vrouter and GUI up, Apex has a build and will test, JOID waiting for a patch
+**Status:** Apex still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
-**Issue:** Scenarios are not fully known, planned out or mapped to lab/test cycle
+**Issue:** Scenarios are frozen, but several not working yet, or have not been tried
-**Owner:** Debra
+**Owner:** test teams
-**Status:** Need this in order to define test schedules: Pharos  (Trevor Cooper or Fatih Degirmenci) and Test teams (Morgan Richomme- Functest, Ana Cunha- Yardstick) participating to define. Deadline for projects to sign up for scenarios has been extended to Friday Jan 15. Still a significant # of scenarios without owners. These cannot be expected to be setup and used without a shepherd to ensure they get into the schedule and actually set up as Jenkins jobs. Debra will send out one more reminder today. Since Asia is already on weekend we'll give them until 6am Pacific time on Sunday to complete (that catches their Monday) [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
+**Status:**  Next step is creating Jenkins jobs and testing each scenario. In process with test teams leading. [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
-**Issue:** Doctor install requirements - Aodh as critical component
-**Owner:** Ildiko, Ryota
-**Status:** Apex has a patch up, we are trying to get it to work.
-**Issue:** NFVKVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
+**Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** New 1/15/16  We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before next Tues installer code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** 1/22 no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
 **===============================================================================================================**
 __**Pod Status:**__
--LFPod2 disconnected - need troubleshooting, not possible to run fuel Stable scenario
+All pods up and running
+[[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
 **===============================================================================================================**
-**Scenario Status:** DEADLINE Friday Jan 15 6pm Pacific (Sunday 6am Pacific for Asia)
+**Scenario Status:** Scenarios are frozen. No feature project has reported that their scenarios are missing or unsupported. Candidate scenarios are having Jenkins jobs created for them. Test teams troubleshooting scenarios and test software.
+Reviewed scenarios in table and noted those that will not be implemented this release
-Feature projects need to validate whether their test cases can run in an existing scenario configuration that is listed in the table or whether they need special scenario. If the former, they need to validate with the test teams that their tests are planned for the scenario & lab during the time that scenario is set up. If the latter, they need to sign up to own their unique scenario, ensure a lab is scheduled to have that scenario, and ensure their tests are integrated into CI & completed. Scenarios and tests will be mapped together & scheduled based on the information charted on these pages [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
+Apex: 5 scenarios on Jenkins: 4 work from deploy point of view odl_l2 is about 90 pass/10 fail, odl_l3 worse pass rate Not successfully deployed yet: ocl- working on it
+Compass: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl. From deployment point of view, 3 working, 1 not. Deployed successfully: openstack, odl_l2, onos. Not successfully deployed yet: ocl (removed from this installer)
+Fuel: 8 scenarios on Jenkins: pure openstack, odl_l2, odl_l3, onos, bgpvpn, ovs, kvm, kvm_ovs. From deployment point of view, 5 working, 1 not working, 2 not activated/attempted yet. Deployed successfully: openstack, odl_l2, odl_l3, onos, bgpvpn Not successfully deployed yet: ovs. Not activated/attempted: kvm, kvm_ovs.
+Fuel has Fuel7 on stable/brahmaputra branch and Fuel8 uplift work is WIP on master branch.
+Joid: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl. From deployment point of view, 3 working, 1 not activated/attempted yet. Deployed successfully: openstack, odl_l2, onos. Not successfully deployed yet: none. Not activated/attempted: ocl (removed from this installer)
+[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)  no new update  for 1/15 see previous status below
+Functest (Morgan Richomme)  Current situation
-Yardstick (Ana Cunha) no new update for 1/15 see previous status below.
+Functest regression yesterday night due to sdnvpn integration, fixed now
+.vPing/SSH Ok on manual tests with compass, not working with all scenarios yet
+we defined 2 vPING: vPing SSH and vPing userdata/cloudinit
+https://wiki.opnfv.org/vping_brahmaputra_page
+vPing/SSH should be OK now on compass (wait for next run). Table to be updated for apex as well I think
+http://testresults.opnfv.org/testapi/dashboard?project=functest&case=vPing&installer=apex and you can change the installer. wait for the test dashboard of LF...
+Yardstick (Ana Cunha)  first successful run with joid yesterday (os scenario),  writing for a patch for workaround for odl scenario - remains to be tested on the labs
+On-going work for grafana dashboard and documentation
+Started to document results for ha
 **===============================================================================================================**
 __**Installer Status:**__
-**Apex** (Tim Rozet): no new update  for 1/15 see previous status below
+**Apex** (Tim Rozet):  Still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
-**JOID** (Narinder Gupta) no new update  for 1/15 see previous status below
+**JOID** (Narinder Gupta) JOID deployed successfully on all three labs yesterday including the virtual deployment. Unfortunately functest had some issues yesterday which seems to be resolved today.
+**Compass4nfv** (Weidong Shao) there were some functest and other instability with the code base, and we will need some extra time in getting Compass code stable
-**Compass4nfv** (Weidong Shao)
+**Fuel** (Jonas Bjurel)
-Status/process about Compass:
+[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
+)
-    ODL Lithium L2 cluster, ONOS Emu L2/L3 cluster, OpenStack Liberty HA , Ceph storage are supported in virtual or baremetal deployment.
+Struggling with an autodeploy issue, hopefully solved now. Testing. Scenarios being rebased
-Status in CI pipeline:
+**===============================================================================================================**
+__**Project Updates:**__ (as provided)
-    Scenario name has aligned for CI pipeline.
-    The CI pipeline platforms for branch(master) and branch(Bramaputra) has been set up.
-    The vitrual deployment verify is for patch verify and the baremetal deployment for daily verify.
-Status about Test project:
+Scenario view status: Reviewed scenarios in table and noted those that will not be implemented this release
+Apex: 5 scenarios on Jenkins: 4 work from deploy point of view
-    Functest and Yardstick has been integrated in CI Daily verify jobs.
+odl_l2 is about 90 pass/10 fail, odl_l3 worse pass rate
+Not successfully deployed yet: ocl- working on it
-    Functest Test result:
+Compass: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl.
-        vPing:  Pass
+From deployment point of view, 3 working, 1 not.
-        ODL:     15 Pass/ 3 Fail
+Deployed successfully: openstack, odl_l2, onos.
-        Tempest:  207 Pass/ 3 Fail
+Not successfully deployed yet: ocl (removed from this installer)
-        Rally:     8 Pass/ 1 Fail
-        vIMS:    deployed success but not run testcase. in troubling shouting now.
-        ONOS:  11 pass / 0 Fail
-    YardStick test result:
+Fuel: 8 scenarios on Jenkins: pure openstack, odl_l2, odl_l3, onos, bgpvpn, ovs, kvm, kvm_ovs.
-           Run successfully!
+From deployment point of view, 5 working, 1 not working, 2 not activated/attempted yet.
+Deployed successfully: openstack, odl_l2, odl_l3, onos, bgpvpn
+Not successfully deployed yet: ovs.
+Not activated/attempted: kvm, kvm_ovs.
-    Bottlenecks:
+Fuel has Fuel7 on stable/brahmaputra branch and Fuel8 uplift work is WIP on master branch.
-            Working in process.
-Status about SDN Controllers:
+Joid: 4 scenarios on Jenkins: pure openstack, odl_l2, onos, and ocl.
+From deployment point of view, 3 working, 1 not activated/attempted yet.
+Deployed successfully: openstack, odl_l2, onos.
+Not successfully deployed yet: none.
+Not activated/attempted: ocl (removed from this installer)
-    ODL and ONOS has been integrated as a virtual daliy job(not enough Baremetal environment)
+**ARMband:**
-    And OpenContrail is working in process : virtual instance just started up successfully but not integrated in CI pipeline.
-We still have a lot of work to do for Bramaputra release, we are a young team and I think we will make it.
+**Availability：**（Qiao Fu) HA project has got all the rst file merged and ready for release. Will upload a full set of rst file for the two release doc later today.
-At last thanks help from you, specially to Meimei, faith, Carey, Leo, Valentin, Stuart, qi Liang, Morgan, Matthew and so on.
+**Bottlenecks:** (Hongbo Tian)
+**Copper:** (Bryan Sullivan) at risk
-**Fuel** (Jonas Bjurel)
+**Doctor** (Ryota, Ildiko)
-[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-no new update for 1/15 see previous status below
-TOP-3 issues:
+**IPv6:** (Bin Hu) -
-)    Rebasing to Fuel 8 puts a lot of preasure to the team, it’s affiliates, etc. (Fuel 8 is an upstream project
-dependency – this was always accounted for – but now we’re here with the reality)
-)    Massive number of deployment scenarios and lab permutations – creates a lot of work.
+**LSOAPI** (Kevin Leuhrs) at risk
-)    Integration with Functest and Yardstick has just started – expect a lot of trouble-shooting, especially
+**NFV4KVM:** (Don Dugger, Raghuveer Reddy)
-as almost all components are new!
+**ONOSFW:** (Ashlee Young)
-**===============================================================================================================**
+**OpenvSwitch** (Mark Gray)
-__**Project Updates:**__ (as provided)
-**ARMband:** no new update for 1/15 see previous status below
-**Bottlenecks:** (Hongbo Tian) no new update 1/15 see previous status below
+**OPNFVdocs** (Chris Price)
+Issues:
+Docs working on central content. Working with projects on project content.  Patches outstanding on many projects.
+Awaiting final scenario list to progress to completion. Working with projects on project content.  Patches outstanding on many projects. Unable to code freeze until installers freeze.
+ONOSFW reviewing reviewing onosfw docs. Projects are working on docs, some feature projects are waiting for the integration to be complete to document that for the config guide
-**Copper:** (Bryan Sullivan) no new update 1/15 see previous status below
+**OVNO** (Stuart Mackie) Apex still working on patch for plugin
-**IPv6:** (Bin Hu) no new update 1/15 see previous status below
+**Parser**
-**LSOAPI** (Kevin Leuhrs) no update for 1/15 see previous status below
+**Prediction** (Hai Liu)
-**NFV4KVM:** (Raghuveer Reddy) no update for 1/15 see previous status below
+**Qtip** (Vikram)
-**ONOSFW:** (Ashlee Young) no update for 1/15 in good shape see previous status below
-**OpenvSwitch** (Mark Gray)  Our main deliverable is a Fuel Plugin for OVS-DPDK. We have that pretty much complete. I am hoping to have it complete today (fingers crossed) as we already have it working with some manual configuration. We have done some smoke testing and it looks ok but we haven’t done a full Functest. There are a few small issues which we will document. The CI for this plugin is done but we have not triggered it yet. We will do this when the plugin is complete. We also need to do a rebase to the latest fuel code.
+**SFC** (Brady Johnson)
-My current thoughts are that, worst case, we will have a plugin with some limitations and some noted bugs. It may not pass all functest tests. So I would say "experimental" support. However, I will have a better idea in the next day or two.
+**SDNVPN** (Tim Irnich)
-Biggest issue now is that we haven’t tested our CI integration.
-**OPNFVdocs** (ChrisPriceAB:) for Docs we now have the composite toolschain working and I will be adding the ready config guide files from other repo's to the master file over the weekend. docs composite document toolchain is now ready. Work is ongoing to get feature desciption documents in place for the central release docs an ensure they reflect and refer to in a meaningful way the project specific documentation. we will likely request a docs exemption on code freeze until we have a accurate reflection of the complete functionality of the Brahmaputra release.  (including stability etc)
+**SFQM** (Maryam Tahhan)
+**StorPerf** (Mark Beierle)
-**Qtip** (Vikram) 1. QTIP is integrated with Jenkins and deployed on Dell POD3. Other labs which have Fuel can run QTIP now.
-. QTIP integration with releng dashboard is underway. Few bugs need to be resolved.
-. QTIP documentation is under progress - target 1/18/2016.
-**SFC** (Brady Johnson) Upstream ODL SFC, GBP, and Netvirt should be ready by the end of this week
-Tim Rozet is working together with Ricky Noriega on preparing the OPNFV SFC testing env
-Ricky is setting up the env and working on writing the Yardstick test cases
-Tim is working on preparing Tacker via post-install scripts
-The first round of testing will focus on using the Apex installer, and Ana Cunha is aware of this and will make sure it will be possible
-The OVS NSH patch will most likely not be ready in time for Brahmaputra, but we have a work-around in place that has been shown to work
-Until NSH is implemented in OVS 2.5, we will use a private branch of OVS (the so called "Pritesh patch")
 **===============================================================================================================**
 **Action Items**__Underlined Text__
-**Action:** add Contrail scenarios to scenario staging page on wiki
+**Action:**
-**Owner:**  Stuart Mackie
+**Owner:**
-**Status:** assigned 1/15
+**Status:**
-**Action:**Review Scenarios and make sure your test case configuration requirements are covered (details in Scenario status)
+**Action:**
-**Owner:**Feature project PTLs
+**Owner:**
-**Status:** Deadline Jan 15, in progress. Due close of business 5pm Pacific.
+**Status:**
-__**Action:**__Send out a reminder to feature projects to finalize scenarios
+__**Action:**__
-**Owner:**Debra
+**Owner:**
-**Status:** done
+**Status:**
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-**1/14/16**
+**1/25/16**
-Countdown to Release: **19 days**
+Countdown to Release: **6 days**
 [[https://etherpad.opnfv.org/p/steps_to_brahmaputra|__**Upcoming deadlines:**__]]
 **===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-14-14.30.html|1/14/16]]
+**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-25-14.30.html|1/25/16]]
-__**Top Accomplishments since yesterday**__
+__**Top Accomplishments & Important Updates since last report**__
+.Fuel made great strides over the weekend. ONOS scenarios working. Still unable to freeze.
+.Yardstick successfully ran ONOS scenario with Compass.
+.Functest now relatively stable from CI perspective. ONOS scenarios working.
-  .Apex has RC0 artifact
-  .Promise has  integrated with Fuel
-  .ODL Beryllium Beta integrated with Fuel
  **===============================================================================================================**
 __**Top Issues**__
+**Issue:** We are at high risk of missing release date. Test cycles for each scenario take a significant amount of time. Even if all installers & scenarios are working properly it takes 7 days to run test through them all.
+**Owner:** Debra
+**Status:** Additional options being proposed: 1. Release with what we have and move everything else to C Release  2. Delay release for up to 3 weeks 3. staggered/phased release of scenario support as a potential. Phase 1: Release what we can on Feb 2; Phase 2: Release what is ready 1-2 weeks later, Phase 3: final release 1-2 weeks after phase 2. These have been brought up to the TSC via email for consideration next TSC meeting.
+**Issue:** Functest & Yardstick do not produce stable results. Troubleshooting scenarios. Need assistance from installer & feature project teams to fault isolation and fix.
+**Owner:** Morgan Richomme (Functest), Ana Cuna (Yardstick)
+**Status:** Functest now relatively stable from CI perspective (except just joid). Still work on the different vPing (and then vIMS) testcases (that need ssh access from the VMs). Onos OK.
+Yardstick:ONOS - successfully run with Compass. ODL scenario - debugging on-going, Yardstick will not run with ODL. Narrowing down subsystems involved. Working on SFC test cases. Working on influxdB+grafana
 **Issue:** Getting RC0 out
 **Owner:** Debra
-**Status:** dependencies to be closed on labs, CI, tests, and installers
+**Status:**  Installer code freeze extended due to Fuel trying to stabilize with upstream. Compass also troubleshooting some functest and other instability with the code base, need some extra time in getting Compass code stable. Apex, JOID ready to freeze
-Apex has RC0, other installers are working on final integration & bugs. Installer code freeze Jan 19.
+**Issue:** Fuel is not ready to code freeze. Upstream Fuel is not stable.
+**Owner:** Jonas Bjurel
+**Status:** Requesting code freeze delay until 1/29 and suggesting release slip 3 weeks
+**Issue:** A large number of projects had code file licensing issues (either missing licenses or non-Apache licenses).
+**Owner:** Ray Paik
+**Status:**Projects have made good progress on getting patches in to fix the files. Scott is making another license scan to see what if anything is outstanding. Thank you to all who have responded to this request in such a timely manner.
 **Issue:** OpenContrail does not deploy
 **Owner:** Stuart Mackey
-**Status:** deployed with Compass, found nova issues; Apex has a build- gave them details on how to modify for Liberty; Need to patch Juju charm for JOID
+**Status:** Apex still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
-**Issue:** Scenarios are not fully known, planned out or mapped to lab/test cycle
+**Issue:** Scenarios are frozen, but several not working yet, or have not been tried
-**Owner:** Debra
+**Owner:** test teams
-**Status:** Need to define test schedules: Pharos  (Trevor Cooper or Fatih Degirmenci) and Test teams (Morgan Richomme- Functest, Ana Cunha- Yardstick) participating to define. Deadline for projects to sign up for scenarios has been extended to Friday Jan 15. Feature projects need to validate whether their test cases can run in an existing scenario configuration or whether they need special scenario. If the former, they need to validate with the test teams that their tests are planned for the scenario & lab during the time that scenario is set up. If the latter, they need to sign up to own their unique scenario, ensure a lab is scheduled to have that scenario, and ensure their tests are integrated into CI & completed. Scenarios and tests will be mapped together & scheduled based on the information charted on these pages [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
+**Status:**  Next step is creating Jenkins jobs and testing each scenario. In process with test teams leading. [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
-**Issue:** Doctor install requirements - Aodh as critical component
-**Owner:** Ildiko, Ryota
-**Status:** Changes in Ceilometer for Liberty require that an Aodh plugin is developed for deployment of Doctor. Ildiko requested assistance from an installer team as she has no experience writing these type of plugin. One installer deploying is required to ensure the project remains in Brahmaputra release. Tim Rozet talked to the author of puppet-aodh, works just fine with liberty and is stable. Ryota is working with Michael Chapman on Apex team trying to get it working with Apex. Ildiko is working with Mirantis to try to get it working with Fuel.
-**Issue:** NFVKVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
+**Issue:** NFV4KVM – plugin does not work with Fuel, The NFV4KVM does install a working kernel on the compute node.
 **Owner:**Don Dugger/Raghuveer Reddy
-**Status:** New 1/15/16  We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before next Tues installer code freeze, but certainly should be able to solve the problem for an SR1 release.
+**Status:** 1/22 no new update.  Fuel has bigger issues at the moment. We have discovered that OVS appears to require kernel modules that are not there. Working on creating a fix to the Fuel plugin creation scripts that will fix this problem, potentially will have a fix before code freeze, but certainly should be able to solve the problem for an SR1 release.
 **===============================================================================================================**
 __**Pod Status:**__
--Labs for CI/test stabilized, 8 working pods designated for CI/test
+All pods up and running
--additional pods coming online for dev work or backup to CI/test
--latest status always available here:
-https://wiki.opnfv.org/pharos_rls_b_labs#status_of_production_ci_resources_for_release_b
+[[https://wiki.opnfv.org/pharos_rls_b_labs|Pharos lab status]]
 **===============================================================================================================**
-**Scenario Status:** DEADLINE Friday Jan 15
+**Scenario Status:** Scenarios are frozen. No feature project has reported that their scenarios are missing or unsupported. Candidate scenarios are having Jenkins jobs created for them. Test teams troubleshooting scenarios and test software.
-Feature projects need to validate whether their test cases can run in an existing scenario configuration that is listed in the table or whether they need special scenario. If the former, they need to validate with the test teams that their tests are planned for the scenario & lab during the time that scenario is set up. If the latter, they need to sign up to own their unique scenario, ensure a lab is scheduled to have that scenario, and ensure their tests are integrated into CI & completed. Scenarios and tests will be mapped together & scheduled based on the information charted on these pages [[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
+[[https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios]] and [[https://wiki.opnfv.org/brahmaputra_testing_page]]
 **===============================================================================================================**
 __**Release Test Status:**__
-Functest (Morgan Richomme)
-functest troubleshooting in progress
-wiki pages initiated to have a summary per testcases [[https://wiki.opnfv.org/functextnexttaks]]
-lots of tests failed (mainly network issues) and integration of companion projects just started (promise, onos) lacking also stability from one run to another
-[[https://wiki.opnfv.org/vping_brahmaputra_page]]
+Functest (Morgan Richomme)  Current situation
-[[https://wiki.opnfv.org/vims_brahmaputra_page]]
+*****************
-[[https://wiki.opnfv.org/tempest_brahmaputra_page]]
+Functest Functest tests more stable, Some tests run in CI over the week end, Functest now relatively stable from CI perspective (except just joid I had to cancel). Still work on the different vPing (and then vIMS) testcases (that need ssh access from the VMs). Onos OK. ODL, maybe an update to be done, but we are integrating upstream suite, and it is not fully clear that the suite has been adapted to new version of ODL.
+https://wiki.opnfv.org/doku.php?id=vPing_brahmaputra_page
+https://wiki.opnfv.org/doku.php?id=vIMS_brahmaputra_page
+Test DB migrated this morning (9 UTC) http://testresults.opnfv.org/testapi/pods
+Still work ahead to tune some cases, and collect the error causes
-ONOS test case integration started, we have now onos labs so it should be ok
+Yardstick (Ana Cunha)  ONOS first succesfull run on Compass, continue troubleshooting ODL scenarios
-Yardstick (Ana Cunha) for fuel: odl scenario fails (ssh timeout), for compass: working last night, however one new fault found today, for joid: troubleshooting, for apex: started yardstick integration on baremetal with help from apex team
@@ Line 2542: / Line 2091: @@
 __**Installer Status:**__
-**Apex** (Tim Rozet): Accomplishments since Yesterday:
+**Apex** (Tim Rozet):  Still trying to get contrail to work, running into some openstack version issues where some contrail pieces rely on juno
-we have built an RC0 candidate artifact!  This build supports ODL Lithium 3.3, OpenStack Liberty HA, network isolation, Ceph in a virtual or baremetal environment.
-[[http://artifacts.opnfv.org/index.html]]
-apex/brahmaputra/opnfv-apex-2.7-brahmaputra.1.rc0.noarch.rpm
-apex/brahmaputra/opnfv-apex-2.7-brahmaputra.1.rc0.src.rpm
-apex/brahmaputra/opnfv-brahmaputra.1.rc0.iso
-apex/brahmaputra/opnfv-brahmaputra.1.rc0.properties
-Functest results on artifact:
+**JOID** (Narinder Gupta) JOID we are ready for code freeze as last pending issue related to Orange pod has been fixed
-Tempest cases: 110 Pass/8 Fail
-ODL cases: 15 Pass/3 Fail
-VPING: 1 Pass/0 Fail
-Rally: 6 Pass/2 Fail
-VIMS: Aborted
-Functest caught a bug for us that we will fix post RC0: [[https://jira.opnfv.org/browse/APEX-59]], which also caused VIMS to abort.
+**Compass4nfv** (Weidong Shao) there were some functest and other instability with the code base, and we will need some extra time in getting Compass code stable
-TODO looking past RC0:
+**Fuel** (Jonas Bjurel)
-.  Found an issue where ONOS build artifact was not being included in our build.  Patch currently up to fix that. (Waiting on #2)
+[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
+)      Build
-.  However, because of #1, our artifact (rpm) size grows over 4GB which is the limit of cpio, and breaks the rpm build.  Dan is working on splitting our rpm into separate rpms which will fix this problem. Patch currently being tested: [[https://gerrit.opnfv.org/gerrit/#/c/6227/]]
+The building issues have been resolved to the point that it builds flawlessly in the
+OPNFV CI engine. Daily masters are produced every night since Friday. Work ongoing
+with getting it to build inside Ericsson corporate network. Stefan probably
+nailed it as it seems to be an issue with the 3.13.0-66 kernel.
-.  Test ONOS and make sure it works with our integration. (Depends on #1, #2)
+)      Deployment.
+I have successfully deployed the daily master image from Friday CI build:
+http://artifacts.opnfv.org/fuel/opnfv-2016-01-22_16-05-16.iso
+It works more or less flawlessly, a few minor comments:
+- The ssh service is not started as early as it used to do, it is not started when Fuelmenu
+  pops up which will be an issue for auto deploy. # service sshd start fixes it
+- Fuelmenu will sometimes tell you that the URLs for the bootimage cannot be found,
+  if you make sure you can reach url resources eg. Through open a consol from fuelmenu
+  and type nslookup www.google.com – just don’t care, select “save & continue” and the
+  “quit without saving” you should be good.
+- Selecting centos boot image didn’t work for me
-.  Dan was able to get OpenContrail to build as an RPM.  Stuart has provided us configuration info.  Next step is to see if the RPM works and if we can install/configure OpenContrail.
+)      Early this week we need to prioritize getting autodeploy to work.
-.  Michael is working on getting AODH support for Doctor into Apex.  Patch WIP: [[https://gerrit.opnfv.org/gerrit/#/c/6631/]]
-.  I'm working on getting SFC support.  Plan is to build Apex RPM with Be version of ODL included, and I'm writing up some ansible modules to update kernel, install NSH OVS, and Tacker.
-.  Yardstick was integrated into Apex, but is failing to run.  Will debug that with Yardstick team.
-**JOID** (Narinder Gupta)
-.seeing few failure which i will be fixing it today.
-.onos also plugin is availble in joid
-.opencontrail migration for Kilo is complete. Plugin built in joid but a few bug fix needs to be done by juniper team for liberty support. Liberty changes needed in charm.
-**Compass4nfv** (Weidong Shao) No update
-**Fuel** (Jonas Bjurel)
-[[https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608|Tickets and backlog jira dashboard]]
-Top priorities/outstanding issues:
+But to my mind, this seems to be stable enough for plugin work. Please start commit rebased plugins to
-) Finalize upstream Fuel 8 rebasing - tomorrow Fri
+Master.
-) Finalize plugin rebasing to Fuel 8 - next week (Tue)
-) Getting all 25 scenarios work/deploying - next week (Fri)
-) Implementing scenario logic for scenarios requireing different Network topologies than Pharos prescribed standard
-     Network set-up (ONOS an NFVOVS) – next week (Tue)
-) Documentation ready, due Tue next week
-Top news:
-)    OpenContrail will not be part Fuel@OPNFV Brahmaputra SR0 release
-)    Promise has  integrated with Fuel – tests to progress during next week!
+-          As I have indicated to TSC (Chris and Frank), my judgement is that we need another 3 week after Feb 2 to complete the things and have them in a good shape. The other option is to release with Fuel7/Kilo which is quite stable and a good veichle for developing stabilizing the scenarios  and the test pipe-line.
-)    ODL Beryllium Beta integrated with Fuel – patch will be merged early next week!
+-          Issue with Jenkins server caused delays on Sunday but were resolved and builds are working again.
-)    BGP-VPN added deployment scenarios – to be tested tomorrow/over the week-end!
-Today integrated plug-ins and their status:
--       ODL (L2, L3, SFC, BGP-VPN, Beryllium) – OK
--       ONOS - OK
--       OVS (NSH, GPB, DPDK) - OK
--       NFVOVS (DPDK) – OK
--       VSPERF - OK
--       BGPVPN – OK
--       NFVKVM – NOK, lacking needed kernel modules for successful deployment – will not fix for the B-release
-TOP-3 issues:
-)    Rebasing to Fuel 8 puts a lot of preasure to the team, it’s affiliates, etc. (Fuel 8 is an upstream project
-dependency – this was always accounted for – but now we’re here with the reality)
-)    Massive number of deployment scenarios and lab permutations – creates a lot of work.
-)    Integration with Functest and Yardstick has just started – expect a lot of trouble-shooting, especially
-as almost all components are new!
 **===============================================================================================================**
 __**Project Updates:**__ (as provided)
-**ARMband:** no new update for 1/14
+**ARMband:**
-Port Fuel Installer to support Pharos lab populated with arm64 servers
-Creating initial bootstrap
-Done for Arno SR1 environment
-This is done using semi-manually using tools and headstart on an arm64 build-server.
-Putting together Fuel-7 (and eventually 8) mechanism
-This is done by adding arm64 support to the real Fuel7/8 mechanisms
-This is being done on a b-release pod with 2x (non-HA) Applied Micro servers.
-Status: We are now updating Fuel-7 as it comes from the b-release to be capable of building bootstrap
-Providing arm64 repos (primarily a gap for MOS repos – everything else expected to be upstream)
-Working on creating mirror for repos that are arm64-specific and not available upstream yet.
-Working within the Fuel7 context…and then Fuel8.
-Porting Fuel machinery to support arm64 as well as x86
-Moving forward with creating patch with changes to b-release Fuel7 (doing work first, then making patch)
-Porting Functest to arm64
-Constructing an HA pod running against Arno SR1 to get Functest running against that more standard environment
-This is 2 SoftIron (AMD) and 1 AMD servers for the three controllers, and two Caviums for the computes.
-Will then move that work forward to work against the B-release environment.
-Additionally, we are investigating building an arm64-based jump server hosting a Fuel Master VM in order to simplify/streamline the parts of Fuel that need to perform binary builds (alternative is cross-compilation or remote arm64 build-server).
-We have been working with an x86 jump server up until now
-**Bottlenecks:** (Hongbo Tian) no new update 1/14
+**Bottlenecks:** (Hongbo Tian)
-   .integrated  with CI pipline on the LF POD2 and fuel(installer). It runes successfully. There are no issues toward meeting the release.
-**Copper:** (Bryan Sullivan) no new update 1/14
+**Copper:** (Bryan Sullivan) at risk
-has abandoned installer integration and is focusing on post-install deployment and verification tests
-**IPv6:** (Bin Hu) no new update 1/14
+**Doctor** (Ryota, Ildiko) Apex patch for AODH is merged. Doctor will make the release.
-Completed:
-   .Automated setup script for OpenStack-only scenario is completed, and merged into Yardstick
-   .Automated setup script (draft) for ODL-L2 scenario  is done, and under internal code review
-   .Documentation (draft) is completed
-Full documentation
-B Release specific (draft)
-To-Do:
-   .CI integration with Huawei’s Pharos Lab in Santa Clara
-   .Complete code review of auto script for ODL-L2 scenario
-   .Move content of B Release specific document to central document repository so that opnfvdoc project can collect and generate one document of B release
-   .Get installer project’s documentation to verify the options and parameters of installer for our scenarios (OS-only and ODL-L2)
-   .Once we verified the options and parameters are correct, we can lock down our documentation.
-**LSOAPI** (Kevin Leuhrs) no update for 1/14 has not run on a pharos compliant lab. A colleague who has been working on the Apex project and installing OPNFV onsite (with varying levels of stability and success) may be able to get a virtual installation here that we can use. We will add scenario descriptions. We will likely need help developing a script providing post-installation for the continuous integration environment and to get the CI deploying the scenarios automatically.
+**IPv6:** (Bin Hu) -
-**NFV4KVM:** (Raghuveer Reddy) no update for 1/14
+**LSOAPI** (Kevin Leuhrs) at risk
-   .We have completed the testing on locally but have not tested on the lab yet.
-   .Waiting for PODs were we plan to do KVM4NFV testing are to be ready. We are hoping the POD to be ready in the next few days
-**ONOSFW:** (Ashlee Young) no update for 1/14
+**NFV4KVM:** (Don Dugger, Raghuveer Reddy)
-  .integrated with CI and look to be in good shape with all of the installers, other than the issues they might be having directly.
-  .We have our scenarios up on the scenarios wiki too.
-  .Reached out to Weidong regarding physical pharos compass status, waiting to hear back. Think for the most part we're in decent shape.
-   .Saw the note from Apex that the Apex ISO is too large now, so waiting to hear back if Apex needs a new RPM from us
-**===============================================================================================================**
-**Action Items**__Underlined Text__
-**Action:** Update scenario & test web pages https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios and https://wiki.opnfv.org/brahmaputra_testing_page
-**Owner:** Morgan Richomme
-**Status:** done
-**Action:**Review Scenarios and make sure your test case configuration requirements are covered (details in Scenario status)
+**ONOSFW:** (Ashlee Young)
-**Owner:**Feature project PTLs
-**Status:** Deadline Jan 15, in progress
-__**Action:**__Send out a reminder to key projects to participate in daily standup or at least send a status if not able to attend
+**OpenvSwitch** (Mark Gray)
-**Owner:**Debra
-**Status:** done
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+**OPNFVdocs** (Chris Price)
-**1/13/16**
+Issues:
+Docs working on central content. Working with projects on project content.  Patches outstanding on many projects.
+Awaiting final scenario list to progress to completion. Working with projects on project content.  Patches outstanding on many projects. Unable to code freeze until installers freeze.
+ONOSFW reviewing reviewing onosfw docs. Projects are working on docs, some feature projects are waiting for the integration to be complete to document that for the config guide
-**Countdown to Release: 20 days**
+**OVNO** (Stuart Mackie) Apex
-**===============================================================================================================**
-**Minutes from daily standup** [[http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-01-13-14.30.html|1/13/16]]
-**Top Accomplishments:**__Underlined Text__
-**This week:**
-  .Labs needed for CI & Test were greatly stabilized
-  .Installers made progress integrating with CI & validating in lab environments
-  .Compass made progress with OpenContrail Deploy
-  .ARMband making good progress on porting Fuel installer to support Pharos lab populated with arm64 servers and porting Functest to ARM
- .IPv6 Automated setup script for OpenStack-only scenario is completed, and merged into Yardstick. Automated setup script (draft) for ODL-L2 scenario  is done, and under internal code review
- .ONOSFW Integrated with CI pipeline
-**===============================================================================================================**
-__**Top Issues**__
+**Parser**
-**Issue:** Getting RC0 out
-**Owner:** Debra
-**Status:** dependencies to be closed on labs, CI, tests, and installers
-Branch is created, labs needed for test are stabilized, installers are working on final integration & bugs. Installer code freeze moved to Jan 19.
-**Issue:** OpenContrail does not deploy
+**Prediction** (Hai Liu)
-**Owner:** Stuart Mackey
-**Status:** deployed with Compass, found nova issues; Apex has a build- gave them details on how to modify for Liberty; Need to patch Juju charm for JOID
-**Issue:** Scenarios are not fully known, planned out or mapped to lab/test cycle
+**Qtip** (Vikram)
-**Owner:** Debra
-**Status:** Need to define test schedules: Pharos  (Trevor Cooper or Fatih Degirmenci) and Test teams (Morgan Richomme- Functest, Ana Cunha- Yardstick) participating to define. Deadline for projects to sign up for scenarios has been extended to Friday Jan 15. Feature projects need to validate whether their test cases can run in an existing scenario configuration or whether they need special scenario. If the former, they need to validate with the test teams that their tests are planned for the scenario & lab during the time that scenario is set up. If the latter, they need to sign up to own their unique scenario, ensure a lab is scheduled to have that scenario, and ensure their tests are integrated into CI & completed. Scenarios and tests will be mapped together & scheduled based on the information charted on these pages https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios and https://wiki.opnfv.org/brahmaputra_testing_page
-**Issue:** Doctor install requirements - Aodh as critical component
-**Owner:** Ildiko, Ryota
-**Status:** Changes in Ceilometer for Liberty require that an Aodh plugin is developed for deployment of Doctor. Ildiko requested assistance from an installer team as she has no experience writing these type of plugin. One installer deploying is required to ensure the project remains in Brahmaputra release. Tim Rozet talked to the author of puppet-aodh, works just fine with liberty and is stable. Ryota is working with Michael Chapman on Apex team trying to get it working with Apex. Ildiko is working with Mirantis to try to get it working with Fuel.
-**===============================================================================================================**
+**SFC** (Brady Johnson) Apex patch is merged, SFC scenario is supported in the release
-__**Pod Status:**__
--Labs for CI/test stabilized, 8 working pods designated for CI/test
--additional pods coming online for dev work or backup to CI/test
--latest status always available here:
-https://wiki.opnfv.org/pharos_rls_b_labs#status_of_production_ci_resources_for_release_b
+**SDNVPN** (Tim Irnich)
-**===============================================================================================================**
-__**Scenario Status:**__ DEADLINE Friday Jan 15
-Feature projects need to validate whether their test cases can run in an existing scenario configuration that is listed in the table or whether they need special scenario. If the former, they need to validate with the test teams that their tests are planned for the scenario & lab during the time that scenario is set up. If the latter, they need to sign up to own their unique scenario, ensure a lab is scheduled to have that scenario, and ensure their tests are integrated into CI & completed. Scenarios and tests will be mapped together & scheduled based on the information charted on these pages https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios and https://wiki.opnfv.org/brahmaputra_testing_page
-**===============================================================================================================**
-__**Release Test Status:**__
-**Functest** (Morgan Richomme) Functest has been run accross all the installers. Troubleshooting in progress in the different internal test case; integration of companion projects just started
+**SFQM** (Maryam Tahhan)
-**Yardstick** (Ana Cunha) troubleshooting compass and joid, activation of new scenarios caused yardstick to fail in LF POD2. SFC, NFFG and SDNVPN. scripts in progress. On track for IPv6, KVM, Parser, HA, Generic NFVI test cases (Yardstick owned) . OVSNFV have decided to focus on Functest.
+**StorPerf** (Mark Beierle)
 **===============================================================================================================**
-__**Installer Status:**__
+**Action Items**__Underlined Text__
-**Apex** (Tim Rozet): Accomplishments since Monday:
+**Action:**
-.  Ceph is working and merged.
+**Owner:**
-.  Network isolation is fully working (admin, private, public, storage networks created and used in deployment).
+**Status:**
-.  Was able to get functest to run with 118 pass/27 fail (Thanks Jose and Morgan for the help).  There was a slight error in functest where some of our keystone users got deleted, so I am hoping on the next run there will be more passes: http://213.77.62.197/results?project=functest&case=Tempest&installer=apex
-Current status for RC0:
+**Action:**
-I believe all the patches are in place to provide us an RC0 artifact.  The only remaining issue is functest failed to start again on our daily last night, so we need to fix that so we can get a valid artifact.
+**Owner:**
+**Status:**
-TODO for RC0:
+__**Action:**__
-.  Fix functest execution in our daily.
+**Owner:**
-.  Merge current master code to stable/b and produce RC0 candidate via daily job.
+**Status:**
-TODO looking past RC0:
-.  Found an issue where ONOS build artifact was not being included in our build.  Patch currently up to fix that.
-.  However, because of #1, our artifact (rpm) size grows over 4GB which is the limit of cpio, and breaks the rpm build.  Dan is working on splitting our rpm into separate rpms which will fix this problem.
-.  Test ONOS and make sure it works with our integration.
-.  Dan was able to get OpenContrail to build as an RPM.  Waiting on Stuart for more information on what we need to do to integrate.
-.  Michael is working on getting AODH support for Doctor into Apex.
-.  I'll work on getting SFC supported.
-**JOID** (Narinder Gupta)
-**Compass4nfv** (Weidong Shao)
-**Fuel** (Jonas Bjurel)
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+[[http://wiki.opnfv.org/releases/brahmaputra/release_plan/archived_standup_status|Archived Status]]
-**===============================================================================================================**
-__**Project Updates:**__ (as provided)
-**ARMband:**
-Port Fuel Installer to support Pharos lab populated with arm64 servers
-Creating initial bootstrap
-Done for Arno SR1 environment
-This is done using semi-manually using tools and headstart on an arm64 build-server.
-Putting together Fuel-7 (and eventually 8) mechanism
-This is done by adding arm64 support to the real Fuel7/8 mechanisms
-This is being done on a b-release pod with 2x (non-HA) Applied Micro servers.
-Status: We are now updating Fuel-7 as it comes from the b-release to be capable of building bootstrap
-Providing arm64 repos (primarily a gap for MOS repos – everything else expected to be upstream)
-Working on creating mirror for repos that are arm64-specific and not available upstream yet.
-Working within the Fuel7 context…and then Fuel8.
-Porting Fuel machinery to support arm64 as well as x86
-Moving forward with creating patch with changes to b-release Fuel7 (doing work first, then making patch)
-Porting Functest to arm64
-Constructing an HA pod running against Arno SR1 to get Functest running against that more standard environment
-This is 2 SoftIron (AMD) and 1 AMD servers for the three controllers, and two Caviums for the computes.
-Will then move that work forward to work against the B-release environment.
-Additionally, we are investigating building an arm64-based jump server hosting a Fuel Master VM in order to simplify/streamline the parts of Fuel that need to perform binary builds (alternative is cross-compilation or remote arm64 build-server).
-We have been working with an x86 jump server up until now
-**Bottlenecks:** (Hongbo Tian)
-   .integrated  with CI pipline on the LF POD2 and fuel(installer). It runes successfully. There are no issues toward meeting the release.
-**Copper:** (Bryan Sullivan) has abandoned installer integration and is focusing on post-install deployment and verification tests
-**IPv6:** (Bin Hu)
-Completed:
-   .Automated setup script for OpenStack-only scenario is completed, and merged into Yardstick
-   .Automated setup script (draft) for ODL-L2 scenario  is done, and under internal code review
-   .Documentation (draft) is completed
-Full documentation
-B Release specific (draft)
-To-Do:
-   .CI integration with Huawei’s Pharos Lab in Santa Clara
-   .Complete code review of auto script for ODL-L2 scenario
-   .Move content of B Release specific document to central document repository so that opnfvdoc project can collect and generate one document of B release
-   .Get installer project’s documentation to verify the options and parameters of installer for our scenarios (OS-only and ODL-L2)
-   .Once we verified the options and parameters are correct, we can lock down our documentation.
-**LSOAPI** (Kevin Leuhrs) has not run on a pharos compliant lab. A colleague who has been working on the Apex project and installing OPNFV onsite (with varying levels of stability and success) may be able to get a virtual installation here that we can use. We will add scenario descriptions. We will likely need help developing a script providing post-installation for the continuous integration environment and to get the CI deploying the scenarios automatically.
-**NFV4KVM:** (Raghuveer Reddy)
-   .We have completed the testing on locally but have not tested on the lab yet.
-   .Waiting for PODs were we plan to do KVM4NFV testing are to be ready. We are hoping the POD to be ready in the next few days
-**ONOSFW:** (Ashlee Young)
-  .integrated with CI and look to be in good shape with all of the installers, other than the issues they might be having directly.
-  .We have our scenarios up on the scenarios wiki too.
-  .Reached out to Weidong regarding physical pharos compass status, waiting to hear back. Think for the most part we're in decent shape.
-   .Saw the note from Apex that the Apex ISO is too large now, so waiting to hear back if Apex needs a new RPM from us
-**===============================================================================================================**
-__**Action Items**__
-**Action:** Update scenario & test web pages https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios and https://wiki.opnfv.org/brahmaputra_testing_page
-**Owner:** Morgan Richomme
-**Status:** assigned 1/13, due 1/14
-**Action:**Review Scenarios and make sure your test case configuration requirements are covered (details in Scenario status)
-**Owner:**Feature project PTLs
-**Status:** Deadline Jan 15
-**Action:**Send out a reminder to key projects to participate in daily standup or at least send a status if not able to attend
-**Owner:**Debra
-**Status:** assigned 1/13, due 1/14
-**===============================================================================================================**

Wiki

User Tools

Site Tools

Differences

Page Tools