Versions Compared

Old Version 20

changes.mady.by.user Marek Chwal

Saved on

compared with

New Version Current

changes.mady.by.user Marek Chwal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Planned deadlines

MilestonePlanned deadlineActual deadlineDescription of the MilestoneComments
M0

 

date as really committed

 

  • Declaration of participation in the simultaneous release
  • Blueprint proposal represented as a Jira EPIC ticket
  • Feature lead assigned to Jira Epic ticket
  • The initial version of Increment Blueprint stored on github/tf-spec/Release folder,
  • The blueprint presented, discussed and approved by TSC
  • Blueprint proposal represented as a Jira EPIC ticket
  • related approvers
  • Release Scope Overview updated accordingly, agreed, approved by TSC
  • The initial version of the Release Plan for the project presented
  • Dependencies between projects/components/areas identified
  • Participating projects and initial Release scope approved by TSC 

 

  • Not all Tech Leaders pointed by Juniper are registered on Tungsten Fabric (lack of login, contact)
  • Description of blueprints not available for TF (links refer to Juniper side)

 

  • Features leaders not registerd in LF/Jira
  • Blueprint approval process not agreed
  • Blueprint template not agreed

 

  • Features leaders not registerd in LF/Jira
  • Blueprint approval process not agreed - rework, approvers still needed
  • Blueprint template agreed, but moved rather to  tf-specs  repo

 

  • Most of blueprint presented/approved (15 out of 19)
  • TFF-12 and TFF-15 will be discussed clarified at  
M1

 


  • all All dependencies between projects existing functionality and requested change/feature discussed and agreed by PTL and related approvers (based on Modules/Commiters)
  • Jira Epic ticket broken down into stories in related Jira project (backlog, plan) - presented and discussed on TWS meeting
  • The final version of Increment Blueprints, Release Scope and Release Plans for participating projects discussed and approved by TSCapprovers

M2

 


  • Technical design fully provided, agreed agreed (documentation on the Confluence/github/tf-spec available)
  • Jira Epic ticket updated with link to technical design
  • Documentation started
  • Feature tests started
  • Feature/Functionality Freeze - Technical Design approved by relevant approvers (Modules/Commiters)

M3

16  


  • External API available for beta-tests
  • Jira Epic ticket updated with information about API availability (documentation link - tf repo)
  • Documentation in progress
  • Tests in progress
  • API Freeze confirmed by Feature Lead (comment on Jira Epic ticket with repo/commit ID link)
Critical - must be aligned with Juniper timeline
M4

30  


 

  • all functionality and APIs available for testing
  • Jira Epic ticket updated with information about final API documentation, executed UI tests documentation
  • Documentation provided - confirmed by Documentation project PTL
  • Code freeze confirmed by Feature Lead (comment on Jira Epic ticket) Code freeze - only bug fixing allowed

From now on, discussion about release candidates may be conducted


RC0

20  


  • Release candidates agreed, approved, tested
  • System tests conducted, quality confirmed by CI/CD PTL (should we have some QA? Security?)
  • Final documentation provided, reviewed, approved by Documentation PTL
  • Marketing information provided to Marketing Advisory Council - confirmed by Brandon Wick?
  • release branch cut off - branch stabilization from now on
  • Release Candidates freeze
Planned scope (current state
  • , confirmed by PTL and TSC(?)

 

delay with testing - so date is moved till mid of December

Release notes, documentation, diff between previous version are needed 

Deployment

 

 

official deployment executed

 

Deployment is still considered at this date (  )

 *(info from TSC meeting - Nick and Alexandre)

14th December is a little shaky due to some recent issues - 21st is more realistic

 Release notes and known error added. We need to clarify Docker Hub images IDs




Scope (based on Jira assignment to FixVersion R2011)

Release board - https://jira.tungsten.io/secure/RapidBoard.jspa?rapidView=5&projectKey=TFF

Jira
serverTungsten Fabric
columnIdsissuekey,summary,issuetype,created,updated,assignee,status,description
columnskey,summary,type,created,updated,assignee,status,

resolution

description
maximumIssues20
jqlQueryfixversion in (

R2011

R21.05) order by Key ASC
serverId82691efe-91a0-3cff-8e71-932ce5d4700b

Jira ChartsborderfalseshowinforfalseserverTungsten Fabricjqlfilter%20%3D%22Release%202011%22statTypestatuseschartTypepiewidthisAuthenticatedtrueserverId82691efe-91a0-3cff-8e71-932ce5d4700b

The initial list of blueprints/features (from Juniper - as a reference)

Feature SummaryFeature LeadModules/Components

Approvers

BluePrint Specification1.

Example: TFF-1 Provision for a knob (per service chain) to prevent reset of AS_PATH and maintain it through a service chain

Provision for a knob (per service chain) to prevent reset of AS_PATH and maintain it through a service chain

Mahesh Sivakumar

Config System, Control Plane, Control NodeNagendra Maynattamai 
Ignatious Johnson christopher

Mahesh Sivakumar Nikhil Bansal

Pranavadatta DN

sangarshan pillareddy

Blueprint

https://review.opencontrail.org/c/tungstenfabric/tf-specs/+/60825

2.Collapsed Spine L2/3 fabricVajrapu Venkata Rama Pradeep KumarFabric, Device Configuration, Fabric UnderlayBlueprint3.Ubuntu 20.04 SupportAndrey PavlovDeployment, Jujuhttps://contrail-jws.atlassian.net/browse/CEM-183714.Charmed OpenStack Ussuri Support

Anastasia Kravets

Deployment, Jujuhttps://contrail-jws.atlassian.net/browse/CEM-183705.Data Plane Mac/IP Learning Mode for vRouterSivakumar GanapathyControl Plane, Control Node, vrouter AgentBlueprint6.Combined FFU+ZIU upgrade from RHOSP13/CN19xx to RHOSP16.1/CN R2011 LTSGleb GalkinDeployment, RHOSPhttps://contrail-jws.atlassian.net/browse/CEM-184057.Optimize the workflow for LR in ERB Mode when creating IRB in the FabricVajrapu Venkata Rama Pradeep KumarFabric, OverlayBlueprint8.Contrail-2003/TCS P0: EVPN Type5 LR : Specific remote VN routes into added to the tenant VN and not the default route

Harsh Kumar

Control Plane, vrouter AgentBlueprint9.BFD/BGP sessions flapping on two computes

Narendranath Karjala

Control Plane, vrouter AgentCEM-16291-DesignDoc10.Qualify 5220 (EVO-based) as a lean spine in ERB fabricSahana Sekhar P CFabric, Device Management, Overlay, Underlayhttps://contrail-jws.atlassian.net/browse/CEM-1630111.DCI -EVPN using L2/3 DCI OTT - Phase 0

Parag Sanghvi

Configuration System, API Server, Fabric, Device Manager Infrastructure, Device Configuration, Overlay, Underlayhttps://review.opencontrail.org/c/tungstenfabric/tf-specs/+/6078112.CaVA - Join to clusterTomasz NowakDeployment, OVA, Operator Frameworkhttps://docs.google.com/document/d/1amNES5_scjPHe6gpSt8mBUCfBh1O25LCK7yXsNxIwls/edit?usp=sharing13.Fabric scale and performance as per PLM requests for R2011

Atul Moghe

Fabric, OverlayBlue Print14.3-tier/5-stage fabric - support for single-plane superspine design (based on 'lean leaf' workaround today)

Abhinav Pandit

Configuration System, API Server, Fabric, Device Manager Infrastructure, Device Configurationhttps://review.opencontrail.org/c/tungstenfabric/tf-specs/+/60791/1/R2011/cem-5002-super-spine-support.md16TF Operator Framework

Prabhjot Singh Sethi 

TF Operator Framework16RBAC support for fabric

Nagendra Prasath Maynattamai Prem Chandran / sajeesh mathew

Config , UI https://review.opencontrail.org/c/tungstenfabric/tf-specs/+/60724