Page tree
Skip to end of metadata
Go to start of metadata

Project owner name and contact info:  Mark Gray <mark.d.gray@intel.com>

OVS Colorado Release Priority Feature List Candidates

This Page lists features which have been submitted by community and OVS team as requirements for OVSNFV. It is expected that the output here will fold into higher level of OVS feature list for REL C

JIRA Items

Colorado JIRA Epics

These are deliverables for this project in the colorado timeline

Loading
T Key Summary Assignee Reporter P Status Resolution Created Updated Due

Dependent Project Epics

These are deliverables required by this project in the colorado timeline

FUEL-118 - Getting issue details... STATUS

PHAROS-136 - Getting issue details... STATUS

Project timeline 

These dates are tentative, still waiting on confirmed Milestone dates from David:

  • Feature Code Freeze mid to late June 
  • Test Code Freeze July 
  • Integration ReadyEarly August 

Upstream Dependencies

  •  Fuel 9 

  • Openstack Mitaka

  • OpenStack Neutron

Purpose of the Priority List

  • Establish a definitive list of features/improvements
  • Analyse each feature and prioritize based on the categories defined below
  • Impact - measure of significance/improvement would the feature help with achieving our overall objective (i.e. does this address industry use case or a customer pain point)
  • Priority – How important is the feature to the community/user
  • Effort- How long will it take? Time, resources, testing

Feature

Description

Priority

Effort

Impact

Jira

Comments

Fuel Feature List

 

 

 

 

 

 

Functest Fuel Successful Integration

Run with Clean results

High

XL

H

OVSNFV - 24

Work with CI team to get Functest running without errors (Billy)

Yardstick Fuel Successful Integration

Run with Clean results

High

XL

H

OVSNFV- 25 & 26

Work with CI team to get Yardstick running without errors (Billy)

Remove NIC dependency

example vlan tag ports needs to be fixed, the packets from Physical guest to OVS is excelerated. For pharos depolyments where different networks are sharing one interafce using vlan tags

High

L

H

 

In discussion with Mirantis to complete this work

Alignment with Fuel 9

Ensure our backlogs are in synch and we are not duplicating work with Mirantis while also ensuring we are in synch with prioritises

High

L

H

OVSNFV- 23

 

Working with latest upstream code

Run latest OVS code for regression testing

Medium

M

L

 

 

Feature

Description

Priority

Effort

Impact

Jira

Comments

Apex Feature List

 

 

 

 

 

 

Functest successful run with clean results

Successful completion with reported results.

High

XL

High

 

 

Yardstick Sucessful run with clean results

Successful completion with reported results.

High

XL

High

 

 

Apex Consume ovs4opnfv generated RPM

Define Deployment options for DPDK and non-DPDK.

 

 

 

 

Work with Apex for successful integration (TFH)

NSH for vxLan

NSH/vLAN available for DPDK and non-DPDK.

Medium

XL

High

 

Depends on upstream support for NSH/vxLAN

Integration with NeutronDPDK 2.2.0 and OVS 2.5 or later required for DPDK usability goals.HighXLHigh Upstream Neutron Support in neutron network-ovs-dpdk repo
Support by upstream Neutron Triple-OApex should be aligned with upstream triple-O in its ability to consume ovs4opnfv or equivalent DPDK/OVS RPMHighXLHigh  

Feature

Description

Priority

Effort

Impact

Jira

Comments

OVS Feature List

 

 

 

 

 

 

Priority Path through OVS

scheduling priority packets before others. Dataplane Approaches include NIC queues, multi-queue at guest interface, and multiple guest interfaces. Control plane approach involves Auxiliary control connections to OF controller.

High

 

 

OVSNFV- 22

follow up meeting at Hackfest (March) produces current list of alternatives.

 

 

  • No labels