You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 68 Next »

CNTT Structure

 

Governance Steering

Lead/Co-Leads: TBA, TBA

Scope

  • Drive Governance Meeting Agenda
  • Bring in alignment between workstreams.
  • Seek community consensus and host voting when needed.
  • Create New workstreams when needed.



Technical Steering

Lead/Co-Leads: TBA, TBA

Scope

  • Primary Liaison with CNTT Governance.
  • Define Vision and Direction
  • Define Workstreams Scope.
  • Set Roadmap and Priorities.
  • Track status and issues.
  • Align with Governance Direction and needs.
  • Bring in alignment between workstreams.
  • Seek community consensus and host voting when needed.
  • Drive Technical Steering Meetings and agenda.
  • Create New technical workstreams when needed.



Governance Workstreams

Community Strategy & Oversight

Workstream Lead/Co-Lead: TBA, TBA

Scope

  • 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


Workstream Contributors

Name (Org)EmailGitHub ID
Jim Baker (LFN)jbaker@linuxfoundation.orgmtnskiier


















Lifecycle Management

Workstream Lead/Co-Lead: TBA, TBA

Scope

  • 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


Workstream Contributors

Name (Org)EmailGitHub ID





















Recruiting, Engagement, & Adoption

Workstream Lead/Co-Lead: TBA, TBA

Scope

  • 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 


Workstream Contributors

Name (Org)EmailGitHub ID





















Marketing & Communications

Workstream Lead/Co-Lead: TBA, TBA

Scope

  • 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
  • Collaboration tools and eco-system


Workstream Contributors

Name (Org)EmailGitHub ID





















Business | Technical Metrics

Workstream Lead/Co-Lead: TBA, TBA

Scope

  • 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


Workstream Contributors

Name (Org)EmailGitHub ID





















Technical F2F Workshop

Workstream Lead/Co-Lead: TBA, TBA

Scope

  • 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


Workstream Contributors

Name (Org)

EmailGitHub ID
Jim Baker (LFN)jbaker@linuxfoundation.orgmtnskiier


















Technical Workstreams


Reference Model Workstreams

Following are CNTT workstreams that are contributing to the development of CNTT Reference Model.

CNTT RM  Core

Workstream Lead/Co-Lead: TBA, TBA


Scope

The following Chapters of the Reference Model:

Ch01: Introduction

Ch02: Requirements Analysis

Ch03: Modelling

Ch04: Infrastructure Abstraction

Ch05: NFVI Feature set

Appendix-A: VNF Guidelines

Workstream Contributors

Name (Org)EmailGitHub ID






















































CNTT RM  Ops

Workstream Lead/Co-Lead: TBA, TBA


Scope

The following Chapters of the Reference Model:

Ch06: Interfaces & APIs

Ch07: Security

Ch09: Operations and LCM

Workstream Contributors

Name (Org)EmailGitHub ID





















CNTT RM  Comp

Workstream Lead/Co-Lead: TBA, TBA


Scope

  • Certification needs/LCM for both VNF and NFVI.
  • Self Certification and badges requirements. (types, hierarchy, etc)

Ch08: Compliance and Verification

Workstream Contributors

Name (Org)EmailGitHub ID















OS Reference Architecture Workstreams

Following are CNTT workstreams that are contributing to the development of Open Stack based Reference Architecture.

CNTT RA 1 (OS) Core

Workstream Lead/Co-Lead: TBA, TBA


Scope

The following Chapters of the Reference Model:

Ch01: Introduction

Ch02: Requirements

Ch03: High Level Architecture

Ch04: Component Level Architecture

Workstream Contributors

Name (Org)EmailGitHub ID






























CNTT RA 1 (OS) Ops

Workstream Lead/Co-Lead: TBA, TBA


Scope

The following Chapters of the Reference Model:

Ch05: Interfaces & APIs

Ch06: Security

Ch07: Operations and LCM

Workstream Contributors

Name (Org)EmailGitHub ID












CNTT RA 1 (OS) Dev (upstream)

Workstream Lead/Co-Lead: 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

Workstream Contributors

Name (Org)EmailGitHub IDName (Org)EmailGitHub ID
























K8s Reference Architecture Workstreams

Following are CNTT workstreams that are contributing to the development of K8s based Reference Architecture.

CNTT RA 2 (K8s) Core

Workstream Lead/Co-Lead: TBA, TBA


Scope

Main components selection and choices, strategy, roadmap, etc.

Ch01: Introduction

Ch02: Requirements

Ch03: High Level Architecture

Ch04: Component Level Architecture

Workstream Contributors

Name (Org)EmailGitHub ID
























CNTT RA 2 (K8s) Ops

Workstream Lead/Co-Lead: TBA, TBA


Scope

Standard interfaces and APIs, Security and LCM.

Ch05: Interfaces & APIs

Ch06: Security

Ch07: Operations and LCM

Workstream Contributors

Name (Org)EmailGitHub ID












CNTT RA 2 (K8s) Dev (upstream)

Workstream Lead/Co-Lead: 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 analysis & Development

Workstream Contributors

 

Name (Org)EmailGitHub IDName (Org)EmailGitHub ID






























OPNFV Reference Implementation (CNTT-RI) Workstreams

Following are CNTT Workstreams that are contributing to the development of OPNFV based Reference Implementation. (as part of OPNFV CNTT-RI project)

CNTT RI 1 Core

Workstream Lead/Co-Lead: TBA, TBA


Scope

  • Eco-system requirements (Labs, tooling, installers, releases and automation requirements)
  • NFVI, RI, and VNF Requirements.


Ch01: Introduction

Ch02: RI Requirements.

Ch03: NFVI + VNF Target State & Spec

Ch04: Lab Requirements

Ch05: Installers Requirements


Workstream Contributors

Name (Org)EmailGitHub ID












CNTT RI 1 Labs

Workstream Lead/Co-Lead: 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


Workstream Contributors

Name (Org)EmailGitHub ID












CNTT RI 1  Dev (upstream)

Workstream Lead/Co-Lead: TBA, TBA


Scope

  • Covers installers, automation, etc.
  • Integration of installers and components.
  • 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: Integration

Ch08: Gap analysis & Development


Workstream Contributors

 

Name (Org)EmailGitHub IDName (Org)EmailGitHub ID






























Reference Certification Workstreams


CNTT RC NFVI

Workstream Lead/Co-Lead: 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.


Workstream Contributors

Name (Org)

EmailGitHub ID












CNTT RC VNF

Workstream Lead/Co-Lead: 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.


Workstream Contributors

Name (Org)EmailGitHub ID












CNTT RC  Dev (upstream)

Workstream Lead/Co-Lead: TBA, TBA


Scope

  • Covers framework tools, NFVI + VNF Testing.
  • E2E Framework Integration (From OpenSrouce projects)
  • 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: E2E Framework Integration.

Ch09: NFVI Tests Traceability to TC Requirements.

Ch10: VNF Tests Traceability to TC Requirements.

Ch11: Gap analysis & Development


Workstream Contributors

 

Name (Org)EmailGitHub IDName (Org)EmailGitHub ID






























  • No labels