Jump to: navigation, search

Service Function Chaining:Lithium Release Plan

Introduction

This release plan has been submit for Milestone M2.

Release Deliverables

Name Description
YANG Models
Yang Model for feature
SFF Load Balancing
Classifier Control and Data Plane Impl
SFC+GBP Integration Proof Of Concept
Service Function Selection Algorithms
New Tests
Tests for feature
SFF Load Balancing
Classifier Control and Data Plane Impl
sfc_dcloud_regression.py that exercise NSH Metadata, ACLs, and Classifiers
SFC+GBP Integration Proof Of Concept
Service Function Selection Algorithms

Release Milestones

Milestone Offset 2 Date Deliverables
M1 1/8/2015
Name Status Description
Intent to Participate Done Intent to participate in Lithium Simultaneous Release, sent Dec 18, 2014
Project Lead elected Done Brady Johnson, brady.allen.johnson@ericsson.com, received 7/12 committer votes
Test Contact Specified Done Post-M2, Brady Johnson, previously Konstantin Blagov, kblagov@cisco.com
Release Plan Done Candidate Release Plan
M2 2/5/2015
Name Status Description
Release Plan Done Final Release Plan
Project Checklist Done Project Checklist completed
M3 3/19/2015
Name Status Description
Functionality Freeze
SFF Load Balancing SFF Load Balancing feature
Classifier Control and Data Plane Impl Classifier Control and Data Plane Impl feature
GBP+SFC Integration GBP+SFC Integration Proof Of Concept
Southbound REST Listener Southbound REST Listener feature
Service Function Selection Algorithm Algorithms to choose SF at Rendered Service Path creation
M4 4/16/2015
Name Status Description
API Freeze
SFF Load Balancing SFF Load Balancing API frozen
Classifier Control and Data Plane Impl Classifier Control and Data Plane Impl API frozen
GBP+SFC Integration GBP+SFC Integration Proof Of Concept API frozen
Service Function Selection Algorithm SF Selection Algorithms API frozen
M5 5/14/2015
Name Status Description
Code Freeze
SFF Load Balancing SFF Load Balancing code freeze
Classifier Control and Data Plane Impl Classifier Control and Data Plane Impl code freeze
Southbound REST Listener Southbound REST Listener code freeze
GBP+SFC Integration GBP+SFC Integration Proof Of Concept code freeze
Service Function Selection Algorithm SF Selection Algorithms code freeze
RC0 N/A
Name Description
Deliverable Name Deliverable Description
RC1 N/A
Name Description
Deliverable Name Deliverable Description
RC2 N/A
Name Description
Release Review Release Review Description
Deliverable Name Deliverable Description
Formal Release TBD
Name Description
Deliverable Name Deliverable Description
SR1 Release N/A
Name Status Description
Release patch Release patch to the stable/lithium branch and bump versions
SR2 Release N/A
Name Status Description
Release patch Release patch to the stable/lithium branch and bump versions

Externally Consumable APIs

  • SFF Load Balancing feature
    • This feature will enhance the existing SFC API
    • The load balancing feature and Opendaylight communicate through the SFC Southbound REST interface
    • Bundles providing the API: sfc-sb-rest
    • REST API commands include:
      • For Service Function Group (SFG): read existing SFG, write new SFG, delete existing SFG, add Service Function (SF) to SFG, and delete SF from SFG
      • For Service Function Group Algorithm (SFG-Alg): read, write, delete
      • Service Function groups and algorithms defined in: sfc-sfg and sfc-sfg-alg
  • SFCOFL2 SFC OpenFlow Renderer feature
    • This feature uses the existing SFC API and does not add anything extra
  • Classifier Control and Data Plane Impl
    • This features exposes API to configure classifier (corresponds to service-function-classifier.yang)
  • Southbound REST Plugin
    • Provides Southbound REST API designated to listening REST devices, supports POST/PUT/DELETE operations on these data types:
      • Access List (ACL)
      • Service Function (SF)
      • Service Function Group (SFG)
      • Service Function Forwarder (SFF)
      • Rendered Service Path (RSP)
  • SFC OVS
    • Provides API to configure/control OVS through SFC
    • Support for these device types:
      • Service Function Forwarder (SFF)
      • (to be done) Service Function (SF)
      • (to be done) Classifier
  • GBP + SFC Integration Proof of Concept
    • This integration is a proof of concept to be performed in the Lithium time-frame. Post Lithium, this will be a "permanent" feature.
    • In the sfc-rsp yang model, the following have been added for this PoC
      • rpc read-rendered-service-path-first-hop
      • rpc read-rsp-first-hop-by-sft-list
      • rendered-service-path-first-hop-info (used by the preceding 2 RPCs)
  • Service Function Selection Algorithms
    • Provides Service Function selection algorithms at RenderedServicePath creation
    • Currently supported algorithms:
      • Load Balancing (choose the least loaded SF)
      • Round Robin
      • Random
    • Load Balancing part defined in: sf-desc-mon and sf-desc-mon-rpt

Expected Dependencies on Other Projects

Providing Project Deliverable Name Needed By Acknowledged? Description
OVSDB MD-SAL plugin M2 Yes MD-SAL plugin that supports CRUD and parameter management for the OVS resources: bridge, tunnel, and port

Expected Incompatibilities with Other Projects

There are no foreseen "Expected Incompatibilities with Other Projects".

Compatibility with Previous Releases

Removed APIs and/or Functionality

There will be no APIs nor Functionality removed.

Deprecated APIs and/or Functionality

As of M2, we dont expect to deprecate any APIs nor functionality. To be completed for M4.

Changed APIs and/or Functionality

To be completed for M4.

Themes and Priorities

Requests from Other Projects

As of M2, there have been no Requests from Other Projects

Test Tools Requirements

To be completed

  • Please specify if the project will run System Test (ST) inside OpenDaylight cloud
  • In case affirmative please enumerate any test tool (mininet, etc...) you think will be required for testing your project
    • The goal is to start test tools installation in rackspace as soon as possible
  • In case negative be aware you will be required to provide System Test (ST) reports upon any release creation (weekly Release, Release Candidate, Formal Release, etc...)

Other