Versions Compared

Key

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

Table of Contents

Planned deadlines

MilestonePlanned deadlineActual deadlineDescription of the MilestoneComments
M0

 

 

  • 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

 

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

 


  • All dependencies between 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 Blueprints, Release Scope and Release Plans for participating projects discussed and approved by approvers

M2

 


  • Technical design fully provided, 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

 


  • 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

 


 

  • 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) - only bug fixing allowed

From now on, discussion about release candidates may be conducted


RC0


  • 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, 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

 

 

 

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 (

Planned scope (current state

based on Jira assignment to FixVersion R2011)

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

Control Plane (Control Node)

Jira
serverTungsten Fabric
columnscolumnIdskeyissuekey,summary,typeissuetype,created,updated,assignee,status,resolution,description
maximumIssues20
jqlQueryfixversion in (R2011) order by Key ASC
serverId82691efe-91a0-3cff-8e71-932ce5d4700b

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

JiraserverTungsten Fabric

  • Configuration System (schema transformer)
  • UI
  • columnskey,summary,type,created,updated,

    due,

    assignee

    ,reporter

    ,

    priority,

    status,

    resolutionserverId82691efe-91a0-3cff-8e71-932ce5d4700bkeyTFF-1

    Blueprint Specification

    2.

    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.

    Ankur Tandon
    • Fabric Management (Device Configuration,Fabric Underlay)

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-2

    Blueprint

    3.Ubuntu 20.04 Support
    • Deployment (Juju)

    Jira
    serverTungsten Fabric
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-3

    Blueprint=N/A

    4.Charmed OpenStack Ussuri Support

    Anastasia Kravets 

    • Deployment (Juju)

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-4

    Blueprint=N/A

    5.Data Plane Mac/IP Learning Mode for vRouter

    Sivakumar Ganapathy 

    • Control Plane (Control Node, vrouter Agent)

    description
    maximumIssues20
    jqlQueryfixversion in (R21.05) order by Key ASC

    Jira
    serverTungsten Fabric
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-5

    Blueprint

    6.Combined FFU+ZIU upgrade from RHOSP13/CN19xx to RHOSP16.1/CN R2011 LTS
    • Deployment (RHOSP)
    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-6
    7.

    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

    Ankur Tandon
    • Fabric Management (Overlay)

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-7

    Blueprint

    8.Contrail-2003/TCS P0: EVPN Type5 LR : Specific remote VN routes into added to the tenant VN and not the default route

    Kumar Harsh 

    • Control Plane (vrouter Agent)

    Jira
    serverTungsten Fabric
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-8

    Blueprint

    9.BFD/BGP sessions flapping on two computes

    Narendranath Karjala

    • Control Plane (vrouter Agent)

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-9

    Blueprint

    10.

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

    • Fabric Management (Device Management, Overlay, Underlay)

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-10

    Data-center fabric automation for underlay IP clos and overlay EVPN-VXLAN features using QFX-5220-132C and QFX-5220-32CD EVO based platforms.

    These platforms will be used as a lean spine/super-spine in ERB architecture.

    11.

    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)
    JiraserverTungsten Fabriccolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

    serverId82691efe-91a0-3cff-8e71-932ce5d4700b

    keyTFF-11

    Blueprint

    12.

    CaVA - Join to cluster

    seems to be cancelled, integrated with TFF-15 - TF Operator

    Tomasz Nowak

    • Deployment (OVA)
    • Operator Framework

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-12

    https://docs.google.com/document/d/1amNES5_scjPHe6gpSt8mBUCfBh1O25LCK7yXsNxIwls/edit?usp=sharing

    seems to be cancelled, integrated with TFF-15 - TF Operator

    13.

    Fabric scale and performance as per PLM requests for R2011

    • Fabric Management (Overlay)

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-13

    Fabric scale with 256 physical devices along with overlay object scale

    • 256K VMI 
    • 4000 VN
    • 2000 VPG
    14.

    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)

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-14

    Blueprint

    15

    TF Operator Framework

    Canceled - not ready for this release

    • Operator Framework

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-15

    TF Operator Framework

    16RBAC support for fabricConfig , UI 

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-16

    Blueprint

    17

    New website for TF

    Canceled - not a part of code release and not proceeded 

    UI
    •  Brandon Wick

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-17

    TFF-17 New website for Tungsten Fabric

    18LogicalRouter: Selecting router type on creationControl Plane

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-18

    seems like small fix to web UI which is already done

    19Support for Intel DDPhaji mohamedContrail Dataplane (DPDK vRouter)

    Jira
    serverTungsten Fabric
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId82691efe-91a0-3cff-8e71-932ce5d4700b
    keyTFF-19

    https://github.com/tungstenfabric/tf-specs/blob/master/intel_ddp_support.md