• 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 

• 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

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

• External API available for beta-tests
• Documentation in progress
• Tests in progress
• API Freeze

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

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

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

Collapsed Spine L2/3 fabric

A collapsed spine architecture has no leaf layer. Instead, the Layer 3 IP-based underlay and the EVPN-VXLAN overlay functionality that normally runs on leaf switches is collapsed onto the spine switches.

• Fabric Management (Device Configuration,Fabric Underlay)

• Deployment (Juju)

Anastasia Kravets 

• Deployment (Juju)

• Control Plane (Control Node, vrouter Agent)

• Deployment (RHOSP)

Optimize the workflow for LR in ERB Mode when creating IRB in the Fabric

In ERB fabric, creating IRB unit for each VN on a device only if there is a local port (VPG) for the associated VN.

This is done to reduce the device scale wrt. configuration and the traffic convergence time in some of the scenarios

• Fabric Management (Overlay)

Harsh Kumar 

• Control Plane (vrouter Agent)

Narendranath Karjala

• Control Plane (vrouter Agent)

Qualify 5220 (EVO-based) as a lean spine in ERB fabric

Supporting QFX-5220-132C and QFX-5220-32CD EVO based platforms. These platforms will be used as a lean spine/super-spine in ERB architecture.

• Fabric Management (Device Management, Overlay, Underlay)

DCI -EVPN using L2/3 DCI OTT - Phase 0

To stretch L2 virtual networks across fabrics in a multi-tenant environment by leaking the tenant virtual network route targets across the fabric

• Configuration System (API Server)
• Fabric Management (Device Manager Infrastructure, Device Configuration, Overlay, Underlay)

• Deployment (OVA)
• Operator Framework

Fabric scale and performance as per PLM requests for R2011

Fabric scale with 256 physical devices along with overlay object scale

• 256K VMI 
• 4000 VN
• 2000 VPG

• Fabric Management (Overlay)

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

Connecting multiple pods via super-spine layer which will behave either as lean device (IP transit) or Route-Reflector. 

Ankur Tandon

• Configuration System (API Server)
• Fabric Management (Device Manager Infrastructure, Device Configuration)

• Operator Framework

• Brandon Wick