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

Brahmaputra.2.0 release plan

Meeting Logistics

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

Introduction

This Release Plan addresses the Brahmaputra.2.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

Red

 

 

Red

ODL Be SR1 not yet tested. Apex: SDNVPN configured to use dummy driver

Critical ODL bug fixes included in Beryllium SR1, next step is to consume that version and test OPNFV scenario. Apex: APEX-118

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

February 26- March 17

2.0 Scenario troubleshooting freeze

March 20, 2016

2.0 Scenario readiness deadline

March 21, 2016

Test & Documentation complete. Tag repos.

March 27, 2016

Brahmaputra.2.0 Release

March 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
    • if that doesn't work ("error: pathspec 'origin/stable/bramaputra' did not match any file(s) known to git")
      • git checkout origin/stable/brahmaputra
  • git checkout <SHA1>
  • git tag -am "brahmaputra.2.0" brahmaputra.2.0
  • git push origin brahmaputra.2.0

If you get the error
! [remote rejected] brahmaputra.2.0 -> brahmaputra.2.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