Contributing your first change to OPNFV can be a confusing process. Where do I get the source code? How do I submit a patch? How do I get someone to merge my changes? We’ll help answer these questions and provide an overview of the tools our community uses to communicate, review, plan, and develop contributions. Then, attendees will learn how OPNFV conducts its release planning and execution and get an overview of the milestones, timeline, and process for each major release.

1. Trevor Bramwell
OPNFV Release Engineer
Developer Tools

2. Presentation Overview
• Expectations
• List of Tools
• Individual Tool Overview
4/8/17 Footer Lorem Ipsum Dolor Sit 2

3. Tool Overview
• Gerrit
• Git-Review
• JIRA
• Jenkins
• Mailman
• Confluence
• IRC
• MeetBot
• Etherpad
• Bitergia
4/8/17 Footer Lorem Ipsum Dolor Sit 3

4. Gerrit
• Web based code review and git repository
• Hosts all the OPNFV code repositories
• Interfaces with JIRA and Jenkins
4/8/17 Footer Lorem Ipsum Dolor Sit 4

5. Git-Review
• Git plugin created by OpenStack for working
with Gerrit
• Replaces
– git push origin HEAD:refs/for/master
with
– git review
• Makes downloading patchsets easy
4/8/17 Footer Lorem Ipsum Dolor Sit 5

6. Git-Review: Example
• git review -s
Initial repo setup that adds a git remote called
gerrit and installs a commit-hook. Requires
.gitreview file.
• git review -d <change>,<patch>
Downloads the change to a new branch. No
messing with FETCH_HEAD.
4/8/17 Footer Lorem Ipsum Dolor Sit 6

7. Gerrit/Git-Review Demo
• Prerecorded
– Clone Repository
– Download Patchset
– Add Reviewer
4/8/17 Footer Lorem Ipsum Dolor Sit 7

8. JIRA
• Issue/Bug Tracker
• Can have associated Gerrit change
• Keep project on track with milestones
4/8/17 Footer Lorem Ipsum Dolor Sit 8

9. Jenkins
• Automated building and testing of OPNFV
• Reports build and test results back to Gerrit
• Gatekeeper for merging commits
• Jobs are in source controlled and deployed
with Jenkins Job Builder
4/8/17 Footer Lorem Ipsum Dolor Sit 9

10. Sandbox Locations
• JIRA:
https://jira.opnfv.org/projects/SANDBOX
• Gerrit:
https://gerrit.opnfv.org/gerrit/#/admin/projects/
sandbox
• Jenkins:
https://sandbox.opnfv.org/
4/8/17 Footer Lorem Ipsum Dolor Sit 10

11. Mailman
• Mailing list software
• Majority of discussions and announcement
• Tags used for individual projects
4/8/17 Footer Lorem Ipsum Dolor Sit 11

12. Confluence
• Wiki and information store
• Used for project proposals, process
documentation, and release planning
4/8/17 Footer Lorem Ipsum Dolor Sit 12

13. IRC
• Real time chat protocol
• Messages are only conveyed to chat
participants
4/8/17 Footer Lorem Ipsum Dolor Sit 13

14. MeetBot
• IRC bot for taking meeting notes
• Automatically saves notes for public viewing
at end of meeting
4/8/17 Footer Lorem Ipsum Dolor Sit 14

15. Etherpad
• Collaborative wiki
• Short lived documents, notes, and plans
4/8/17 Footer Lorem Ipsum Dolor Sit 15

16. Bitergia
• Project and tool statistics and reports
• Custom OPNFV ELK dashboard
4/8/17 Footer Lorem Ipsum Dolor Sit 16

17. OPNFV Release Process

18. OPNFV Release Overview
• 6 month cadence for major releases
• 2 minor releases follow at approximately 6 and 12 weeks after
the major release
– The minor releases allow for bug fixes and additional content
that was not ready as of the initial release
• Release artifacts consist of ISOs and RPMs for each supported
installer
– Except Joid which is installed via git clone
• Documentation is published via read-the-docs
4/8/17 Footer Lorem Ipsum Dolor Sit 18

19. OPNFV Projects and Scenarios
• OPNFV feature projects are deployed and tested via “scenario”
• An OPNFV “scenario” is defined as:
– An installer. Currently:
• Apex
• Compass
• Fuel
• Joid
– A set of components. Typically:
• OpenStack
• An SDN controller
• One or more features
– A configuration
4/8/17 Footer Lorem Ipsum Dolor Sit 19

20. Milestone Overview
• Milestones 0 & 1 - Intent-to-Participate Window
– OPNFV projects, previously approved by the TSC, must
express their intent-to-participate between MS0 and MS1.
– In addition, projects must also complete and publish their
release plans by MS1.
• Milestone 2 - Test Case Documentation
– Projects are required to have their test cases documented in
the test case database
4/8/17 Footer Lorem Ipsum Dolor Sit 20

21. Milestone Overview
• Milestone 3 - Installer / OpenStack Integration
– Designed to establish foundation for feature project
development.
– Most critical milestone. Direct impact on feature
development and stabilization
4/8/17 Footer Lorem Ipsum Dolor Sit 21
Upstream Components
(OpenStack, ODL, etc.)
OPNFV
Installers
OPNFV
Features
OPNFV Test
Frameworks

22. Milestone Overview
• Milestone 3 - Installer / OpenStack Integration (continued)
– This milestone may be deconstructed into multiple,
interdependent steps as follows
– Phase 0 -
• Installer / Openstack integration
• Functest / Openstack integration sufficient to support
health check
– Phase 1 (+ 3 weeks)
• Installers pass health check (nosdn)
– Phase 2 (+ 3 weeks)
• Installer + SDN controller passes health check
4/8/17 Footer Lorem Ipsum Dolor Sit 22

23. Milestone Overview
• Milestone 4 - Infrastructure Updates Completed
– Functest supports health check + smoke test
– AKA - test framework complete
– At this point we hope to be able to support feature development and
automated test in a stable environment
• Milestone 5 - Scenario integration
– All feature projects have completed integration with scenarios
• i.e., feature is deployed with a set of components, using a specific
installer, with a designated configuration
4/8/17 Footer Lorem Ipsum Dolor Sit 23

24. Milestone Overview
• Milestone 6 - test case implementation; preliminary
documentation; stable branch window opens
– Test cases documented in MS2 must be implemented
at this point
– Preliminary documentation requirement recently added
to reduce flailing at the end of the release period
• Directory structure
• Placeholder documents
– Stable branch window opens
• Milestone 7 - stable branch window closes
4/8/17 Footer Lorem Ipsum Dolor Sit 24

25. Milestone Overview
• Milestone 8 - Formal test execution completed
• Milestone 9 - JIRA bookkeeping updated
• Milestone 10 - Documentation completed
• Milestone 11 - Release
4/8/17 Footer Lorem Ipsum Dolor Sit 25

27. Questions?

28. All logos © respective
organizations and
projects.