[GENIUS-143] Implement ITM Egress Tunnel Table (of-tunnels) Created: 01/Jun/18  Updated: 24/Aug/18

Status: Open
Project: genius
Component/s: None
Affects Version/s: None
Fix Version/s: Neon

Type: New Feature Priority: High
Reporter: Faseela K Assignee: Faseela K
Resolution: Unresolved Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Cloners
clones GENIUS-128 Change Feature Title (add topic tag, ... In Progress
Sub-Tasks:
Key
Summary
Type
Status
Assignee
GENIUS-158 getEgressActionsForTunnel() should re... Sub-task Open Faseela K  
GENIUS-159 Egress Tunnel Table entry should be c... Sub-task Resolved Faseela K  
GENIUS-160 Genius CSIT enhancements for Egress T... Sub-task Verified Karthika Panneer  
GENIUS-161 Genius Pipeline updation for ITM Egre... Sub-task Resolved Faseela K  
Epic Link: bp/fluorine

 Description   

Change Blueprint Title (add topic tag, keep in parenthesis)

Description

Currently ITM does not program a common flow table to contain the egress tunnel information. Due to this all applications need to be aware of the underlying tunnel port to program in their application pipeline. This feature aims to abstract out the underlying port information in a table that can be programmed by ITM, and applications can point to this table in their flows. The group will be created irrespective of the tunnel port being created, and applications need not act upon tunnel created/deleted events.

Specification Gerrit : https://git.opendaylight.org/gerrit/#/c/71659/

Gerrits Topic : https://git.opendaylight.org/gerrit/#/q/topic:of-tunnels+(status:open+OR+status:merged)

Dependencies

https://git.opendaylight.org/gerrit/#/c/69227/


Generated at Wed Feb 07 20:00:01 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.