OPNFV SFQM BrahmaputraRelease Planning

Maryam TahhanAugust 09 2015

Project Box

Minimum viable requirements(Cant release without these)

• DPDK Keep Alive Sample application• DPDK NIC stats extensions: i40e and VF stats.

Want but at risk requirements(Like to have, but high risk)

Working plan requirements(Minimum Viable, low risk, but high effort needed)

• CollectD DPDK stats Plugin

Outplan requirements(Future requirements not in this release.)

Detailed Requirementsin later slides

Risks Assessment

Description Likelihood Impact Trigger Mitigation Contingency Owner Status

DPDK Keep Alive Sample application

High Low DPDK KA app testing fails

Work with DPDK upstream

Don't release DPDK KA

Maryam Ongoing

DPDK NIC stats extensions: i40e and VF stats

High High DPDK NIC stats testing fails

Work with DPDK upstream

Don't release DPDK i40e or VF stats

Maryam Ongoing

CollectD DPDK stats Plugin

High low CollectD testing fails

Work with CollectD upstream

Don't upstream CollectD plugin

Maryam Ongoing

Impact

Likelihood

We care about these

Low-Low

High-Low High-High

Low-High

Minimal Viable Detailed RequirementsThe OPNFV SFQM Brahmaputra Release cannot release without these:DPDK Stats ExtensionsDeliverables:

• IXGBE error/extended stats Exposure• i40e error/extended stats Exposure• Sample App that retrieves stats on the Host• Sample App that retrieves stats on the Guest• Sample App that retrieves Host stats on the Host

Description: Development activity to support the exposure of NIC MAC/PHY Level Counters, particularly for packet drops and errors.Functional Requirements:

• Expose error/drop registers to DPDK Sample Apps• Expose VF including error/drop registers to DPDK Sample Apps• Extend Exposed registers to include those not in struct hw_stats• Extend Exposed registers to include Sums that are not in struct hw_stats

Performance Requirements: Does NOT impact performance.Targeted DPDK release: DPDK 2.1 and DPDK 2.2 (November 30th 2015)

Taken from the “Project Box” on previous slides

Notice:This is still a draft

Minimal Viable Detailed Requirements contThe OPNFV SFQM Brahmaputra Release cannot release without these:DPDK Stats Extensions

• Status:

Taken from the “Project Box” on previous slides

Notice:This is still a draft

Feature Expose error/drop registers

Expose VF registers

Expose additional registers

Expose totals registers

IXGBE DPDK 2.1(DONE) DPDK 2.2 DPDK 2.2 DPDK 2.2

i40e DPDK 2.2 DPDK 2.2 DPDK 2.2 DPDK 2.2

Sample App on Host/Guest

DPDK 2.1(DONE) N/A N/A N/A

Sample App on Guest for Host stats

N/A N/A N/A N/A

DPDK 2.2 == In Progress

The OPNFV SFQM Brahmaputra Release cannot release without these:• CollectD DPDK stats Plugin

• Deliverable: CollectD Plugin for DPDK stats• Description: CollectD Plugin that runs on the host and polls stats from

DPDK• Functional Requirements:

Runs on the Guest/Host.Collects PF/VF Stats.

• Performance Requirements: Does NOT impact performance.• Targeted DPDK release: upstream to github by the end of October as there

is no release cadence for CollectD.• Status: To be started.

Taken from the “Project Box” on previous slides

Notice:This is still a draft

Minimal Viable Detailed Requirements

Minimal Viable Detailed RequirementsThe OPNFV SFQM Brahmaputra Release cannot release without these:FEATURE: DPDK KEEP ALIVE (KA)

• Deliverable: DPDK Keep Alive Sample App on Guest (A simple forwarding app with DPDK KA functionality)

• Description: Development activity to support detection of ‘failed’ DPDK cores and notification to a HA/SA middleware. The purpose is to detect Packet Processing Core fails (e.g. infinite loop) and ensure the failure of the core does not result in a fault that is not detectable by a management entity.

• Functional Requirements:Runs on the Guest.Runs on the Host.Configurable timeouts.Measures detection time.Has a hook function where HA/SA middleware can hook in for fault management notifications.

• Performance Requirements: Does NOT impact performance.• Targeted DPDK release: DPDK 2.2 (November 30th 2015)• Status: In Progress

Taken from the “Project Box” on previous slides

Notice:This is still a draft

Preliminary DependenciesThis is a preliminary list of the OPNFV SFQM dependencies. Later, I’ll create a Milestone timeline for better visibility.

• DPDK• CollectD

Dependencies - DPDK - CollectD

WW = Work Week

DPDK

Week … X-11 X-10 X-9 X-8 X-7 X-6 X-5 X-4 X-3 X-2 X-1 X

… WW37 WW38 WW39 WW40 WW41 WW42 WW43 WW45 WW46 WW47 WW48 WW49

 

Patches for the new release are developed and submitted to the mailing list.Features to be developed include: DPDK Keep Alive, DPDK extended stats features and CollectD plugin for DPDK statistics

Community review, testing and rework of patches. No new patches submitted during this time. Patches without open issues applied

Testing of Release Candidate 1 and subsequent RCs. Bug Fixing

Testing of final RC. Only fixes to high priority bugs accepted during this time

Final Version of all patches submitted to mailing list 

for reviewFinal Verision of all 

patches applied, RC1 built Final RC builtRelease available: DPDK

Keepalive and DPDK extended stats features

are part of DPDK 2.2

Additional RCs as Required

CollectD release Schedule is unknown, There doesn't seem to be a standard release cadence. Plan is to have collectD DPDK plugin pushed to github/upstreamed by the end of October

SFQM High level Milestone Schedule

End of November 2015

Mid November 2015

Mid/End October 2015

End of Sept 2015