© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 OFED 1.x Process and Beyond Jeff Squyres.

Slides:



Advertisements
Similar presentations
Project Management For the last day and a half we’ve talked about the APD process – how to get the funding and approval for your project. There is one.
Advertisements

Campus Networking Best Practices This Presentation and related materials will be available at: Help Desk Services.
Software engineering tools for web development Jim Briggs 1CASE.
Branching, Switching and tagging Francesco Furfari CNR-ISTI Italy.
Web Development Engineering Processes Introduction to Web Development Outsourcing Processes.
Proposed AMIT SMT Methodology and Release Strategy March 9, 2010.
Beta Testing: The Contractor’s Perspective Trns·port User Group Meeting October 2005.
Coherent Web Sustaining Engineering Plan 1. The Coherent Web team will: Utilize two-week development “sprints” to plan and track implementation activities.
 User assignments (product owner)  ‘circle’  1 st sprint: ◦ Scrum Boards (informative workspace)  Product -, release -, sprint -, defect backlog 
1 Test Planning CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 9, 2007.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Rich Hypermedia for NB Requirements and Release Process Version 3.3 CSEM Consulting ICS 225 – Spring 2002.
Health Informatics Series
Low level CASE: Source Code Management. Source Code Management  Also known as Configuration Management  Source Code Managers are tools that: –Archive.
Source Code Management Or Configuration Management: How I learned to Stop Worrying and Hate My Co-workers Less.
IS&T Project Management: How to Engage the Customer September 27, 2005.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 ANNOUNCING Command Lookup Tool 2.0 Something new is happening!
Web Development Process Description
COMPGZ07 Project Management Presentations Graham Collins, UCL
ONLINE TECHNICAL REPORT SYSTEM Team Crash Course Ryan Ashe, Eileen Balci, James Kirk, Taylor Paschal.
OFED 1.x Roadmap & Release Process November 06 Jeff Squyres, Woodruff, Robert J, Betsy Zeller, Tziporet Koren,
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicOFA Open MPI 1 Open MPI Progress Jeff Squyres.
“Kuality” Assurance What does that look like? Scott Heise Indiana University KFS - Quality Assurance Manager Paul Sandoval University of Arizona KRA –
Unified Process versus Extreme Programming. Outline Compare and contrast UP and XP  Processes / Disciplines  Management  Artefacts Risk management.
Medium Size Software, Inc. SQA Plan: The Batch Processing Application.
1 Lecture 19 Configuration Management Software Engineering.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.1 ISP Help Desk Working at a Small-to-Medium Business or ISP – Chapter 2.
The B uff. The Buffs Agenda 1. Recent iteration and Progress 2. Plan for next iteration 3. Prototype demonstration.
Software Development Process and Management (or how to be officious and unpopular)
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.
Development Methodology N. Draper. Introduction Development Process Test driven development Continuous Integration –Automated build and test Trac Ticket.
1 מודל ניהול הצוותים של MSF. 2 Causes of failure  Poorly-defined objectives  Insufficient planning  Lack of executive support  Organizational barriers.
Sampleminded® Support Overview Last Updated: 1/22/
NoZama Group Development Plan 1/31/02. Functionality First Release Price Comparison User Profile Book Recommendation …With limited functionality.
Team Skill 6: Building the Right System Managing Change (28)
T Project Review WellIT PP Iteration
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Basic Approach Development driven by time boxing May sacrifice requirements in order to keep schedule (time boxed) Steer project as you go based on user.
Management of the SEAMCAT tool European Communications Office Jean-Philippe Kermoal (ECO) October 2010 EUROPEAN COMMUNICATIONS OFFICE Nansensgade 19 DK-1366.
Project Workflow Harry. Contents Trac Review board.
Workshop on How to Publish Data in VO ESAC, June 25-June Tips & tricks by the Ivoa Document Coordinator Bruno Rino
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.1 ISP Help Desk Working at a Small-to-Medium Business or ISP – Chapter 2.
Initiation Project Management Minder Chen, Ph.D. CSU Channel Islands
© 2012 Václav Rajlich Software Engineering: The Current Practice Ch Conclusion of software change The last phase of software change The activities.
CS223: Software Engineering Lecture 16: The Agile Methodology.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
RMS Issue Request Form October 12, Purpose Provide RMS and its Working groups/Taskforces with clarity and understanding around issues Provide structure.
1. What is Demand Management? …aims to understand, anticipate, prioritize and influence customer demand for services. Demand Management 2.
Virtual Lab Overview 5/21/2015 xxxxxxxxxx NWS/MDL/CIRA.
OPeNDAP Development and Security Policies. Development Policies All of our software uses LGPL or GPL –LGPL is used by most of the code –We want it to.
BioRainbow Development Process Description. Development Process Overview We use combination of MSF development technology ( Extreme.
Version Control How and why to control changes in a software artifact.
Management of the SEAMCAT tool
Project Overview and Current Status
Dilbert Scott Adams.
Managing the Project Lifecycle
Global Grid Forum GridForge
OpenSAF Developer Days 2008 OpenSAF Release Management Session 15-07
Quality Assurance: Early Work Items
Methodical Accelerator Design
Quality Control in the dCache team.
OSOR - new opportunities for sharing statistical software
© University of Liverpool
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
TDL Open Source Project (TOP) Input to MTS#70,
Branches And Releases Branch for Urgent Bug Branch for Feature A
Project Iterations.
Presentation transcript:

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 OFED 1.x Process and Beyond Jeff Squyres

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 2 Goals  Overview of Open MPI development  DISCUSS -- not just information broadcast This meeting starts the discussion Agree on what the processes are Document the processes Publish the processes

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 3 Open MPI  Similar to OFA Multiple organizations Open source Common releases  Consensus driven  Separate administrative and technical issues

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 4 Open MPI  Technical roles Developers Release managers: determine when a release is made, what patches go in, etc. Gatekeepers: minions of the RM’s that do the technical work  Administrative group Only invoked upon demand Legal, marketing, etc. Conflict resolution

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 5 Open MPI development  Single code SVN Development occurs at the trunk -- free for all Stable release branches, all commits are reviewed and approved Frequent temporary branches for destabilization work  Bug tracking, milestones, wiki: Trac Open a ticket for everything Release managers prioritize and decide what go into each release / milestone  Frequent communication Weekly developer teleconferences, s, IM Do not rely on for archived information: SVN, web site, etc.

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 6 Open MPI releases  Release meeting at the beginning of a series Determine feature set Determine priorities of each priority (e.g., 1-5 scale, 5 = “blocker” meaning if not complete/fixed, holds up the release)  Determine the schedule Estimate how long each feature takes, make a plan Create milestones for when to drop testable pre-releases

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 7 Processes to discuss  What are the features of a release? Who decides / how do we decide?  What are the phases of the release? What is the exact schedule? Who decides / how do we decide?  What levels of changes are acceptable at each phase? How big / little / when / where / etc.?  What is the flow from OFA development to release? How does one submit a patch? How do we decide what version of what goes into OFED?

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 8 Processes to discuss  What is the release criteria for a release? How do we decide?  What is the testing matrix? Who is testing what?  What guarantees are we providing to the customer?

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 9 You talk now

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 10 OFA