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 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
M1

 


  • All dependencies between projects discussed and agreed
  • Jira Epic ticket broken down into stories (backlog, plan) - presented and discussed on TWS meeting
  • The final version of Blueprints, Release Scope and Release Plans for participating projects discussed and approved by TSC

M2

 


  • Technical design fully provided, agreed (documentation on the Confluence available)
  • Documentation started
  • Feature tests started
  • Feature/Functionality Freeze - Technical Design approved by TSC(?)

M3

 


  • External API available for beta-tests
  • Documentation in progress
  • Tests in progress
  • API Freeze
Critical - must be aligned with Juniper timeline
M4

 


  • all functionality and APIs available for testing
  • Code freeze - only bug fixing allowed

RC0

 


  • Release candidates agreed, approved, tested
  • release branch cut off - branch stabilization from now on
  • Release Candidates freeze




Planned scope (current state based on Jira assignment to FixVersion R2011)

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




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


Feature nameFeature LeadModules (Components)

Approvers
(from Modules Committers)

BluePrint Specification links
1.

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

  • Control Plane (Control Node)
  • Configuration System (schema transformer)
  • UI

Blueprint Specification


2.Collapsed Spine L2/3 fabricVajrapu Venkata Rama Pradeep Kumar 
  • Fabric Management (Device Configuration,Fabric Underlay)
Blueprint
3.Ubuntu 20.04 Support
  • Deployment (Juju)

4.Charmed OpenStack Ussuri Support

Anastasia Kravets 

  • Deployment (Juju)
https://contrail-jws.atlassian.net/browse/CEM-18370
5.Data Plane Mac/IP Learning Mode for vRouterSivakumar Ganapathy 
  • Control Plane (Control Node, vrouter Agent)


6.Combined FFU+ZIU upgrade from RHOSP13/CN19xx to RHOSP16.1/CN R2011 LTS
  • Deployment (RHOSP)
https://contrail-jws.atlassian.net/browse/CEM-18405
7.Optimize the workflow for LR in ERB Mode when creating IRB in the FabricVajrapu Venkata Rama Pradeep Kumar
  • Fabric Management (Overlay)
Blueprint
8.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 Agent)
9.BFD/BGP sessions flapping on two computes

Narendranath Karjala

  • Control Plane (vrouter Agent)
CEM-16291-DesignDoc
10.Qualify 5220 (EVO-based) as a lean spine in ERB fabricSahana Sekhar P C
  • Fabric Management (Device Management, Overlay, Underlay)
https://contrail-jws.atlassian.net/browse/CEM-16301
11.DCI -EVPN using L2/3 DCI OTT - Phase 0

Parag Sanghvi

  • Configuration System (API Server)
  • Fabric Management (Device Manager Infrastructure, Device Configuration, Overlay, Underlay)
https://review.opencontrail.org/c/tungstenfabric/tf-specs/+/60781
12.CaVA - Join to clusterTomasz Nowak
  • Deployment (OVA)
  • Operator Framework
https://docs.google.com/document/d/1amNES5_scjPHe6gpSt8mBUCfBh1O25LCK7yXsNxIwls/edit?usp=sharing
13.Fabric scale and performance as per PLM requests for R2011
  • Fabric Management (Overlay)
Blue Print
14.3-tier/5-stage fabric - support for single-plane superspine design (based on 'lean leaf' workaround today)

Abhinav Pandit

  • Configuration System (API Server)
  • Fabric Management (Device Manager Infrastructure, Device Configuration)
https://review.opencontrail.org/c/tungstenfabric/tf-specs/+/60791/1/R2011/cem-5002-super-spine-support.md
15TF Operator Framework
  • Operator Framework
TF Operator Framework
16RBAC support for fabricConfig , UI https://github.com/tungstenfabric/tf-specs/blob/master/R2011/fabric-rbac.md
17New website for TFUI
  • Brandon Wick
TFF-17 New website for Tungsten Fabric
18Support for Intel DDPContrail Dataplane (DPDK vRouter)https://github.com/tungstenfabric/tf-specs/blob/master/intel_ddp_support.md