OPNFV VSPERF Brahmaputra Release Planning Maryam Tahhan August 09 2015.

Slides:



Advertisements
Similar presentations
Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com.
Advertisements

Coherent Web Sustaining Engineering Plan 1. The Coherent Web team will: Utilize two-week development “sprints” to plan and track implementation activities.
© 2014 Sungard AS. All rights reserved. Cloudstack - Way to contribute June 2014 Girish Chaudhari.
Systems Analysis and Design in a Changing World, 6th Edition
SAIC-F QA Internal Process (DRAFT ) Sudha Chudamani QA Team, Frederick National Lab Jan 2, 2013.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
Case Submittal Best Practice
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
OPNFV SFQM Brahmaputra
What is the Spiral Development Model? Lifted From
CSE9020 Schedule, / 1 The Suggested Schedule Week Content/Deliverable 1. 4/3Unit Overview, Project Description, Meetings, Group Formation 2. 11/3Project.
EVS Product Development Life Cycle Charles Griffin 9/19/2007
Sampleminded® Support Overview Last Updated: 1/22/
1 © Cable Television Laboratories, Inc Do not share this material with anyone other than CableLabs Members, and vendors under CableLabs NDA if applicable.
Project-X 3.0 Quality Criteria. QA Criteria Milestones Ø System Integration Complete (September) ùReady to start building production servers. Ø Project-X.
Page 1 TEST in the large RELEASE REWORK ASSESS packaged application documentation models and source code management documents requirement alloc. matrix.
Targets for project progress 2015: graduation review – clear documentation and PoC implementation specify general framework and API requirements gap analysis.
9/23/2009 NOTICE! These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of.
VSPERF – Test and Performance Subgroup Demo 26/08/2015 Maryam Tahhan.
Massachusetts All-Payer Claims Database: Technical Assistance Group (TAG) September 8, 2015.
Maryam Tahhan Al Morton Benchmarking Virtual Switches in OPNFV draft-vsperf-bmwg-vswitch-opnfv-01.
SunGuide SM Software Development Project End of the Year ITS Working Group Meeting December 7, 2005.
Text Firefox Metro Project Production Pipeline. Text Our Approach.
Maryam Tahhan, Al Morton, Jack Morgan. VSPERF Deep Dive: Virtual Switch performance In OPNFV 1.
CUSTOMER USER ACCEPTANCE TEST (CUAT) STATUS FEMA Implementation into EmpowHR CUAT –Migration Certificates provided August 16, 2012 –3 projects tested:
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
Tools Report Engineering Node August 2007
Software Development.
Open source development model and methodologies.
Project Overview and Current Status
Preparation of the Self-Study and Documentation
OPNFV testing strategy
Nodal Status Report: Program Controls Update
Towards a single virtualized data path for VPP
Global Grid Forum GridForge
OpenDaylight Packetcable Plugin Working Group Call
Release BETA Integration Tool Status Geneva – 1 March 2007
OpenSAF Developer Days 2008 OpenSAF Release Management Session 15-07
September 20, 2017 Agile Techniques Workshop Susan Futey
Reporting the Course level RWR Assessment data
Experience with jemalloc
What do you need to know about XP?
Teaching slides Chapter 3.
Teaching slides Chapter 1.
Johanna Rothman Know What “Done” Means Chapter 11
Formulation of Abstract Machine for SPM Based on Finite State Machine
Introduction to CAST Technical Support
Process, timeline and overview
Customer Service Phone App
Software Development Process
Your_name, your_company
Figure 3: Risk Analysis Model
Your_name, your_company
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
Amendment Invoice Task Force Progress Report
OVS DPDK Community Update
Hackfest April 2017 Orange labs. Paris
Priorities and contents of releases
Strategic Planning Timeline Overview
Managing Work in the New Computing Environment March 14, 2003
Amendment Invoice Task Force Progress Report
Beta releases and Product Management
Extreme Programming.
How to request a final transcript in Naviance/Family Connection.
Class Schedule Project Update
Proposal on TSC policy for ONAP release Maintenance
Class Schedule Project Update
City of Santa Paula Water and Sewer Rate Study Results Public Workshop
Presentation transcript:

OPNFV VSPERF Brahmaputra Release Planning Maryam Tahhan August

Project Box Minimum viable requirements (Cant release without these) Tech debt - Affinitize vswitch threads for Vanilla OVS Tech debt - Affinitize vswitch threads for DPDK enabled OVS Convert Documentation to RST format and follow the layout setout by opnfv_documentation Fix derived performance figures Bidi Tests for all deployment scenarios Want but at risk requirements (Like to have, but high risk) ●Enable PVVP - vhost cuse ●Enable PVVP - vhost user Working plan requirements (Minimum Viable, low risk, but high effort needed) Default config picks up OVS variants from 'make‘ 'make' creates all required variants of vSwitch Update Sysmetrics implementation Enable memory utilization metric collection for RFC 2544 tests Enable CPU utilization metric collection for RFC 2544 tests Outplan requirements (Future requirements not in this release.) Detailed Requirements in later slides

Minimal Viable Detailed Requirements The OPNFV SFQM Brahmaputra Release cannot release without these: Please see the Backlog tab in VSPERF_Rel_B_Highlevel Plan.xlsx; anything with the Rel B tag will be included in release B. Any other stories that are complete in time will also make it into the release.VSPERF_Rel_B_Highlevel Plan.xlsx Taken from the “Project Box” on previous slides Notice: This is still a draft

Preliminary Dependencies This is a preliminary list of the OPNFV VSPERF dependencies. None

Dependencies None, project is self contained WW = Work Week DPDK Week … X-11X-10X-9X-8X-7X-6X-5X-4X-3X-2X-1X … WW37WW38WW39WW40WW41WW42WW43WW45WW46WW47WW48WW49 Patches for the new release are developed and submitted to the mailing list. Features to be developed include: See the Backlog tab in the Release Plan workbook; anything with the Rel B tag will be included in release B. Any other stories that are complete in time will also make it into the release. 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 review Final Version of all patches applied, RC1 built Final RC builtRelease available Additional RCs as Required VSPERF High level Milestone Schedule End of November 2015 Mid November 2015 Mid/End October 2015 End of Sept 2015