/
Table Type Patterns: Beryllium: Release Plan

Table Type Patterns: Beryllium: Release Plan

Contents

Introduction

This is a release plan for Table Type Patterns. The project goals for this release are:

  • to support live OpenFlow control through a TTP-constrained OpenFlow API

  • to offer a utility that supports comparison and matching of "flow-match-actions" between two TTPs

  • to provide an ability for developers to leverage the comparison utility to map "app TTPs" to "device TTPs"

Release Deliverables

Name

External API

Description

Name

External API

Description

Bug fixing

n/a

High-priority bug fixes.

Flow_paths

CLI only

Tracking all flow management options for a TTP

Comparison

CLI only?

Comparing Flow_paths for two separate TTPs (typically app and device level)

Dynamic Map (tentative)

no programmatic API

Enable human guided dynamic map of App TTP request to Device TTP

Auto-load to TTP repository (tentative)

via TTP YANG model and augmentations

read TTPs from disk (or remote URLs) into the TTP repository

DIDM driver (tentative)

via DIDM?

provide a DIDM driver based on the dynamic maps

TTP pipeline snippets and composition (very tentative)

unknown, based on interest or work

provide a way to describe snippets of OpenFlow pipeline and compose them to make full pipelines originally targeting vSwitches

TTP 1.1 support (tentative)

via updated YANG model

adopt changes as needed from to-be-published TTP 1.1 spec

Release Milestones

Milestone

Offset 2 Date

Deliverables

Milestone

Offset 2 Date

Deliverables

M1

8/7/2015





M2

9/3/2015





M3

10/15/2015





M4

11/12/2015





M5

12/17/2015





RC0

1/7/2016





RC1

6/4/2015





RC2

1/14/2016





RC3

1/21/2016





Formal Release

2/4/2016





SR1 Release

3/17/2016





SR2 Release

4/28/2016





SR3 Release

7/28/2016





SR4 Release

10/20/2016





Externally Consumable APIs

Note: While the CLI tool is intended for external consumption in that we expect people outside to use it, it is not intended for programmatic consumption and so the API is not listed in this table.

Short Name

Description

Type (at M2)

Type (at M3)

Type (release)

Contract

Supporting Code

Short Name

Description

Type (at M2)

Type (at M3)

Type (release)

Contract

Supporting Code

TTP YANG model

Model for TTPs, DB of avail. TTPs, augmentation to nodes providing active and supported TTPs

Stable (may be some edits)

Stable (may be some edits)

Stable

YANG models

none now

TTP Driver

At least one app to device TTP driver

Tentative

Provisional

Dropped

none yet, likely using DIDM API

none now

Pipeline Snippet Utilities

Tools create, chain, use TTPs as pipeline snippets

Tentative

Dropped

Dropped

none yet

none now

Expected Dependencies on Other Projects

Providing Project

Deliverable Name

Needed By

Acknowledged?

Description

Providing Project

Deliverable Name

Needed By

Acknowledged?

Description

controller

features

M3

No

basic controller features

odlparent

features

M3

No

odlparent values

openflowplugin

features

M3

No

flow programming and extensions

openflowjava

features

M3

No

 ??

yangtools

features

M3

No

yangtools for compiling yang

Expected Incompatibilities with Other Projects

(Need to complete this... CurtB)

Compatibility with Previous Releases

Removed APIs and/or Functionality

Deprecated APIs and/or Functionality

Changed APIs and/or Functionality

Themes and Priorities

  • Increase the usefulness of tool funtions for the "parser" utility

  • Invest significantly in documentation

  • Provide some deployable controller TTP functionality

Requests from Other Projects

Active Requests

Test Tools Requirements

(This needs further development.)

Other

Related content