Common NFVI Telco Taskforce CNTT Structure

CNTT | Organizational Structure CNTT Governance External Communities Technical Steering RM Core RA1 Core RA2 Core RI 1 Core RC NFVI RM Ops RA1 Ops RA2 Ops RI 1 Labs RC VNF RM Compliance RA1 Dev RA2 Dev RI 1 Dev RC Dev

CNTT | Governance Workstreams and Structure External Communities Leads: TBA. TBA Governance Steering Community Strategies & Oversight Lifecycle Management Recruiting, Engagement, & Adoption Marketing & Communications Business | Technical Metrics Technical F2F Work Shops

CNTT | Governance Workstreams Leads/Co-Leads WSL Responsibilities: Define strategies, process, roadmap, & measures to achieve work stream objectives and success Drive content creation for each corresponding workstream Deliver on the strategy & plan Assign issues Track status and issues Seek community consensus Administer approval process . Drive workstream meetings and agenda Discuss unresolved issues Raise any concern to Governance meetings Community Strategies & Oversight TBA, TBA Lifecycle Management TBA, TBA Recruiting, Engagement, & Adoption TBA, TBA Marketing & Communications TBA, TBA Business | Technical Metrics TBA, TBA Technical F2F Work Shops TBA, TBA Leads/Co-Leads – take into considerations [distribute continent] Note: If you would like to be considered for a lead/co-lead role, please send an email to Jonathan Beltran (jb788y@att.com) and Rabi Abdel (abdel.rabi@Vodafone.com). Note: If you would like to participate in any of these WS, please add your details into https://wiki.lfnetworking.org/display/LN/CNTT+Workstreams Lead, Co-Lead

CNTT | Governance Workstream Scope WSL: TBA, TBA Scope: Community Strategies & Oversight WSL: TBA, TBA Scope: Lifecycle Management WSL: TBA, TBA Scope: Recruiting, Engagement, & Adoption Define community strategies that align with Common NFVI mission, objectives & outcomes Review & assess community success measures for required action(s) Ensure compliance within the community to policies, process, & principles Define process & tools required to create and manage GSMA / OPNFV feedback loop to RM, RA, RI, & RC Collect feedback on lifecycle activities | processes | ecosystem to plan, track, & measure improvement initiatives Drive culture of continuous improvement across Common NFVI Lifecycle Framework Recruit operators & suppliers to bring diverse perspective and contributions into the community Drive membership engagement activities to address community resource demands Engage industry leaders with Common NFVI value proposition to drive adoption rate Drive adoption roadmap with VNF Vendors Work Stream List: Work Stream List: Work Stream List: Add your name to Work Stream List Add your name to Work Stream List Add your name to Work Stream List Lead, Co-Lead

CNTT | Governance Workstream Scope WSL: TBA, TBA Scope: Marketing & Communications WSL: TBA, TBA Scope: Business | Technical Metrics WSL: TBA, TBA Scope: Technical F2F Work Shops Identify and pursue opportunities to market community services through publication of white papers, press releases, business cases, & media events Track community external speaking engagements Create | maintain community messaging to ensure alignment in external communications Define, create, & publish business value metrics based on ROI, Time to Market, etc. Define, create, & publish success metrics for community processes and deliverables Define, create, & publish contribution rates within the community Define, create & publish adoption rates within the Industry Conduct work shops ~4X yearly Create agendas that focus on issue resolution & community alignment Ensure work shop logistical requirements are planned & managed Ensure work shop artifacts are collected, organized, & stored Seek opportunities to engage partner communities in work shops Work Stream List: Work Stream List: Work Stream List: Add your name to Work Stream List Add your name to Work Stream List Add your name to Work Stream List Lead, Co-Lead

CNTT | Technical Workstreams and Structure Technical Steering RM Core RA1 Core RA2 Core RI 1 Core RC NFVI RM Ops RA1 Ops RA2 Ops RI 1 Labs RC VNF RM Compliance RA1 Dev RA2 Dev RI 1 Dev RC Dev

CNTT | Technical Steering TSL: TBA, TBA Responsibilities: Define Vision and Direction Define Workstreams Scope. Set Roadmap and Priorities. Track status and issues. Bring in alignment between workstreams. Seek community consensus and host voting when needed. Drive Technical Steering Meetings and agenda. Create New workstreams when needed. RM Core RA1 Core RA2 Core RI 1 Core RC NFVI RM Ops RA1 Ops RA2 Ops RI 1 Labs RC VNF RM Compliance RA1 Dev RA2 Dev RI 1 Dev RI 1 Dev Lead, Co-Lead

CNTT | Deciding on Technical Roadmap F2F Workshops CNTT Governance GitHub Issues Backlog Input Input Input Technical Steering Roadmap Items Roadmap Items Roadmap Items Roadmap Items Snowdon Cruachan RM Core RA1 Core RA2 Core RI 1 Core RC NFVI RM Ops RA1 Ops RA2 Ops RI 1 Labs RC VNF RM Compliance RA1 Dev RA2 Dev RI 1 Dev RC Dev

CNTT | Technical Workstreams Leads/Co-Leads WSL RM Core TBA, TBA RM Ops TBA, TBA Responsibilities: Drive content creation for their corresponding chapters. Deliver on the Roadmap. Assign PRs and issues to Committers. Track status and issues. Seek community consensus. Administer approval process and merge approved PRs. Drive technical meetings and agenda. Discuss PRs that has not got to a conclusion online. Raise any concern to Technical Steering meetings. RM Compliance TBA, TBA RA1 Core TBA, TBA RA1 Ops TBA, TBA RA1 Dev TBA, TBA RA2 Core TBA, TBA RA2 Ops TBA, TBA RA2 Dev TBA, TBA Leads/Co-Leads – take into considerations [distribute continent] RI 1 Core TBA, TBA RI 1 Labs TBA, TBA Note: If you would like to be considered for a lead/co-lead role, please send an email to Jonathan Beltran (jb788y@att.com) and Rabi Abdel (abdel.rabi@Vodafone.com). RI 1 Dev TBA, TBA Note: If you would like to participate as a committer into any of those WS, please add your details into https://wiki.lfnetworking.org/display/LN/CNTT+Workstreams RC NFVI Lead, Co-Lead TBA, TBA RC VNF TBA, TBA RC Dev TBA, TBA

CNTT | RM Technical Workstreams Scope WSL: TBA, TBA Scope: Ch01: Introduction Ch02: Requirements Analysis Ch03: Modelling Ch04: Infrastructure Abstraction Ch05: NFVI Feature set Appendix-A: VNF Guidelines RM Core WSL: TBA, TBA Scope: Ch06: Interfaces & APIs Ch07: Security Ch09: Operations and LCM RM Ops WSL: TBA, TBA Scope: Certification needs/LCM for both VNF and NFVI. Self Certification and badges requirements. (types, hierarchy, etc) Ch08: Compliance and Verification RM Compliance Add your name to Committers List Add your name to Committers List Add your name to Committers List Lead, Co-Lead

CNTT | RA 1 Technical Workstreams Scope WSL: TBA, TBA Scope: Ch01: Introduction Ch02: Requirements Ch03: High Level Architecture Ch04: Component Level Architecture RA 1 Core WSL: TBA, TBA Scope: Ch05: Interfaces & APIs Ch06: Security Ch07: Operations and LCM RA 1 Ops WSL: TBA, TBA Scope: Gaps analysis of existing technologies, partnership with OpenStack projects and leading development effort to address them. Lead and manage available Engineering resources pool. Ch08: Gaps & Development RA 1 Dev Add your name to Committers List RA 1 Dev (for Suzie guy) Add your name to Committers List Add your name to Committers List Add your name to Developers List Lead, Co-Lead

CNTT | RA 2 Technical Workstreams Scope WSL:, TBA, TBA Scope: Main components selection and choices, strategy, roadmap, etc. Ch01: Introduction Ch02: Requirements Ch03: High Level Architecture Ch04: Component Level Architecture Committers List: RA 2 Core WSL: TBA, TBA Scope: Standard interfaces and APIs, Security and LCM. Ch05: Interfaces & APIs Ch06: Security Ch07: Operations and LCM Committers List: RA 2 Ops WSL: TBA, TBA Scope: Gaps analysis of existing technologies, partnership with existing communities (such as TUG) and leading development effort to address them. Lead and manage available engineering resources pool. Ch08: Gaps & Development RA 2 Dev Add your name to Committers & Developers List Add your name to Committers List Add your name to Committers List Lead, Co-Lead

CNTT | *RI 1 Technical Workstreams Scope WSL: TBA, TBA Scope: Eco-system requirements (Labs, tooling, installers, releases and automation requirements) NFVI, RI, and VNF Requirements. Ch01: Introduction Ch02: NFVI + VNF Target State & Spec Ch03: RI Requirements. Ch04: Lab Requirements Ch05: Installers Requirements RI 1 Core WSL: TBA, TBA Scope: Procure initial target lab Ensure all entry / exit criteria met Assist with lab selection options (LAAS, Community, Self Service) Release Alignment Ch06: Lab Operations RI 1 Labs WSL: TBA, TBA Scope: Covers installers, automation, etc. Gap analysis with required actions for existing eco-system within LFN/OPNFV community projects Assign Engineering resources into community projects to address gaps Lead and manage Engineering resources pool Ch07: Gap analysis RI 1 Dev Spirent! Add your name to Committers & Developers List Add your name to Committers List Add your name to Committers List *RI 1 workstreams are part of the CNTT-RI project within OPNFV Lead, Co-Lead

CNTT | RC Technical Workstreams Scope WSL: TBA, TBA Scope: LCM for C&V framework for NFVI Define E2E Framework Requirements, process and automation for NFVI Certification Ensure Platform Stability, Operability, & Performance for target RAs Leverage and Influence Community C&V Strategies. Provide TC Traceability to RA/RM Requirements and make sure the testing bar is high. Ch01: Introduction Ch02: NFVI E2E C&V Framework Requirements Ch03: NFVI Test Case Requirements Ch04: NFVI TC Traceability to RA Requirements. RC NFVI WSL: TBA, TBA Scope: LCM for C&V framework for VNF Define E2E Framework Requirements, process, and automation for VNF Certification. Ensure Platform Stability, Operability, & Performance. Leverage and Influence Community C&V Strategies. Provide TC Traceability to RM Requirements and make sure the testing bar is high. Ch05: VNF E2E C&V Framework Requirements Ch06: VNF Test Case Requirements Ch07: VNF TC Traceability to RM Requirements. RC VNF WSL: TBA, TBA Scope: Covers framework tools, NFVI + VNF Testing. Make sure all test cases needed are implemented Partner with existing LFN testing projects to identify/address gaps. Place Engineering Resources into community projects to address gaps. Manage and lead available engineering resources pool. Ch08: NFVI Tests Traceability to TC Requirements. Ch09: VNF Tests Traceability to TC Requirements. Ch10: Gap analysis RC Dev Spirent! Add your name to Committers List Add your name to Committers List Add your name to Committers & Developers List Lead, Co-Lead

Common NFVI Telco Taskforce Contribution Process

CNTT | Where everything is? https://github.com/cntt-n/CNTT https://cntt-n.github.io/CNTT/ https://github.com/cntt-n/CNTT/wiki Reference Model RM https://github.com/cntt-n/CNTT/tree/master/doc/ref_model Reference Architecture RA https://github.com/cntt-n/CNTT/tree/master/doc/ref_arch Reference Implementation RI https://github.com/cntt-n/CNTT/tree/master/doc/ref_impl

CNTT | Committers Committers are individuals who has special permission on GitHub that give them write access to the repository. It allows them to: Create PRs directly on the main repository (without the need to fork). Allow them to edit a PR (if given permission from the creator) Allow them to approve a PR and contribute to the approval process. Committers are expected to be active on the workstream they are contributing to and will be selected by the WSL to be part of the approval process for any given PR. Any committer who has not been active on GitHub for more than 3 months will loose their write access from CNTT repository. Add your name to committer lists in here: https://wiki.lfnetworking.org/display/LN/CNTT+Workstreams

CNTT | What do you need to do to be able to contribute Get a GitHub ID https://github.com If you are planning to create a PR or participate in PR approval process, please sign up to a given workstream as a committer. Any individual (Committer or not) can comment on any PR/Issue, or request a review on proposed PRs.

CNTT | Issues & Labels Issue Types: Roadmap Item: This issue type indicates a request for feature to be added for an upcoming release. This issue type should only be created by Technical Steering Leads. Fix needed: This issue type indicates a request to fix a bug or to introduce an enhancement. This issue type can be created by any individual. Backlog: This issue type indicate a feature request (to be considered during technical steering meeting) for future releases. Enhancement: This issue type indicate an enhancement request

CNTT | Issues & Labels All issues must be clearly titled, described, and tagged with the right labels when created. Issue Labels (one or more to be selected form pre-defined set): Roadmap Item: To indicate this issue is for a roadmap item. Fix needed: To indicate this issue is for a fix request. Backlog: To indicate this issue is for a backlog feature request. Workstream Name: To indicate which project this issue targeting. Chapter Number: To indicate which Chapter this issue targeting. General: To indicate that this issue is not corresponding to any particular chapter/file. Major/Minor: To indicate if the issue request a major or minor change. Enhancement: Suggested Enhancement.

CNTT | Pull Requests (PRs) PRs must only be created by a committer who has an issue assigned to him/her by the respective WSL. PRs must only be created when there is an issue present and a decision to create a PR is made. A PR must reference the issue it is resolving into the description field. One person only is allowed to edit a given PR (unless given permission to other committers). One PR should only create/modify content within the scope of a single workstream.

CNTT | Pull Requests approval process Once a PR is created, it needs to get the following approvals before it is merged into master. From Two committers from the Operators community. From Two committers form the Vendors community. WSL approval (to make sure process is followed and consensus is reached). Final Approval by TSL (temporarily until content is stable and process is followed) Only One approval is permitted per each organization for a given PR. The selection of which Committers to approve a PR is made by the WSL and should take those factors into consideration: 2 from Operators, 2 from vendors (when possible) Committers needs to be actively discussing the PR to be selected for approval. Committers needs to be active in the workstream. PRs will be merged online by the TSL once consensus is reached and all approvals are received. If WSL is the person who is creating the PR, he needs to request a fifth approval from the committers list.

CNTT | PR approval process flow Issue created 1 Issue assigned to committer 2 PR Created 3 WSL Committer Approval Process Committer A Operator ✓ Committer B Operator ✓ Committer A Vendor ✓ Committer B Vendor ✓ Temporarily until stable content/process PR being reviewed & Edited 4 Committer TSL Approval TSL WSL Approval WSL PR reached consensus & approved 5 Individuals 48 hours cool off period Community Reflecting community feedback If no consensus reached PR Merged 6 Discuss and/or Vote Technical Steering Meeting 4A

Common NFVI Telco Taskforce Meeting Structure

CNTT | Workstreams Meetings The purpose of Workstream Meetings is the following: Deliver on the roadmap agreed. Track status of content. Resolve any PRs that has not got consensus from the community. Encourage content creation and assign issues to committers to resolve. Identify concerns and Raise to technical steering meeting. The purpose of the meeting is not to approve PRs or merge them (this should be mainly done online) Create 3 minute video of how to use GitHub. Leads/Co-Leads

CNTT | Meetings Structure It is up to WSL to decide on the frequency and duration of workstream meetings. It is advised to accommodate different time zones For example: one week US-EU Friendly and one EU-ASIA Friendly or (US-ASIA Friendly) Recommended to send a doodle poll for those who showed interest to participate to decide on the best time for the meeting. Meeting times and zoom ids should be kept in: https://github.com/cntt-n/CNTT/wiki/Meetings To request a zoom Id for your workstream meeting, please contact Jonathan Beltran or Jim Baker to create a zoom id for you. Create 3 minute video of how to use GitHub. Leads/Co-Leads

Common NFVI Telco Taskforce GitHub Tutorials

CNTT | How to Create an Issue

Common NFVI Telco Taskforce End