Fuel@OPNFV - Our way towards the release

Updated: Sunday Feb 7 - 7.30 PM CET

Currently estimated release date: Feb 26

Release date confidence: 90%

Summary facts:

• Fuel code status: Green
• Fuel plugin/collaboration status: Green/Yellow. Following plugins does not yet work:
  1. KVM4NFV (Missing OVS kernel module for the kernel version used)
  2. BGP-VPN: A patch exists, should be OK on Monday Feb 8
  3. SFC: Though the plugin exists/works, tacker post deployment scripts are missing.
• We will close the window for plugin fixes and Deploy-scenarios Feb 12. Those fixes that don't make it in this time-frame will be scheduled for a follow-up release.
• Fuel QA status: Green - The deployment success rate is almost 100%. Functest and Yardstick is almost 100 % on master/Ericsson-POD2 but it is failing on stable/LF-POD2. Since master and Stable are currently identical, this is rather thought to be an issue with LF-POD2
• Jira ticket status: Green, critical Jira tickets: 0
• Fuel Documentation status: Green - Ongoing, will be finalized the coming week.
• Fuel Foss sanity status: Green - Have been fixed and communicated with LF-legal

We have declared Brahmaputra hard code freeze!

This implies the following policies on new content and bug-fixes:

• No new content is allowed into either master or stable/brahmaputra at this time
• Bug-fixes are allowed into master
• Cherry-picking of bug-fixes from master to stable/brahmaputra requires 2/3 of the committers approval, and no rejections.
• Cherry-picking of bug-fixes from master to stable/brahmaputra requires that it has passed a build and a rellevant deploy cycle.
• Cherry-picking of core Fuel bug-fixes require that either:
  1. Build with invalidated cache passes in master
  2. Verification of that Fuel Core was built with auto invalidated cache in master

The Master branch will be opened up for next release development at the later half of February 2016.

Epoch time for these statistics is since Feb 5 2016 Note: Please note, as of yet - master and stable/brahmaputra are equivalent so except from transients, master and stable/brahmaputra results can in principle be aggregated.

stable/brahmaputra builds (Successful/Failed): master builds (Successful/Failed): Deployments from stable/brahmaputra - red status scenarios not counted for - (Successful/Failed): Deployments from master - red status scenarios not counted for - (Successful/Failed):

Status measured since: Feb 5

Report per: Feb 7 (7.30 PM CET)

Note 1: (m/s) stands for (master/stable)

Note 2: Functest and Yardstick fails on Stable/LF-POD2, we believe this is an issue with LF-POD2 rather than anything else.

Note 3: We have a patch that is not yet merged which presumably fixes the BGP-VPN scenario.

Status measured since: -

Report per: -

Note 1: (m/s) stands for (master/stable)

stable/brahmaputra builds (Successful/Failed): master builds (Successful/Failed): Deployments from stable/brahmaputra - red status scenarios not counted for - (Successful/Failed): Deployments from master - red status scenarios not counted for - (Successful/Failed):