Page tree
Skip to end of metadata
Go to start of metadata

Brahmaputra.3.0 release plan

Meeting Logistics

  • Logistics: IRC channel #opnfv-release
  • Times:
  • Tuesdays 06:30 PST
  • Fridays 07:00 PST

Introduction

This Release Plan addresses the Brahmaputra.3.0 stable update of the OPNFV Brahmaputra release.

Scenario status

  • Green - Scenario fully working
  • Yellow - Scenario partly working (Minor bugs)
  • Red - Scenario Broken (Major issues)

Scenario Contact

Scenario

Apex

Compass

JOID

Fuel

Open Issues

Current status

 

os-ocl-nofeature

NS

 

 

 

troubleshooting new components

Troubleshooting ongoing, deploying but not passing test cases

Tim Irnich

os-odl_l2-sdnvpn

Yellow

 

 

Green

APEX: Functest not yet running, ODL internal transport tunnels not correctly set up.

Fuel: deploys and passes functest in CI, Yardstick not working (no Floating IP in ODL VPN Service). Apex: scenario deploys, configuration needs fixing

Brady

os-odl_l2-sfc

Yellow

 

 

Yellow

Missing Tests,Minor Bugs

Test development and deployment ongoing. Bug with ODL Classifier not pushing flows SFC_Bug. Apex: bug with offsetting flows APEX-116.

 

os-nosdn-ovs

NS

 

 

NS

Low test pass rate

Troublehsooting test results

kvm4nfv

os-nosdn-kvm

NS

 

 

Yellow

Kernel Drivers

Activities ongoing to complete

None

os-odl_l3-nofeature

Red

 

 

Red

Major ODL Bugs

ODL_L3_bug, ODL L3 sends local traffic to GW

None

os-odl_l2

Green

 

 

Green

Intermittent heat configuration issues

Release ready

onosfw

os-onos

Yellow

 

 

Green

Intermittent heat configuration issues

Release ready. Apex: deploys/functions, but sends local external traffic to gw - ONOS bug (to be fixed in Colorado)

Installer

os-nosdn

Green

 

 

Green

 

 

Schedule

Activity

Date

Scenario Troubleshooting

March 28 - April 20

3.0 Scenario troubleshooting freeze

April 20, 2016

3.0 Scenario readiness deadline

April 21, 2016

Test & Documentation complete. Tag repos.

April 27, 2016

Brahmaputra.3.0 Release

April 28, 2016

Brahmaputra git tagging instructions

PTLs of Brahmaputra participating projects will apply the tags in respective repos.

SHA1s to Apply Tags on for SR1

SHA1s of the repos are identified by PTLs. If the project is integrated to other projects (such as installer projects) it is important to communicate with these projects as well.

To select the SHA1 to apply the tag for, you can use Gerrit web interface or the git commands as listed below.

  • Using Gerrit Web Interface:
  • Using Git command
    • git checkout stable/brahmaputra
    • git log --graph

Tagging

  • git fetch origin
  • git checkout stable/brahmaputra
  • git checkout <SHA1>
  • git tag -am "brahmaputra.3.0" brahmaputra.3.0
  • git push origin brahmaputra.3.0

If you get the error
! [remote rejected] brahmaputra.3.0 -> brahmaputra.3.0 (prohibited by Gerrit)
This is because you are not the author of the commit being tagged. email helpdesk and I will add forge rights to refs/tags/* on your repo.

Please contact aricg and/or other Octopus members on #opnfv-octopus channel if you experience any issues.

Release Meeting minutes

  • No labels