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

Compare with Current View Page History

« Previous Version 61 Next »

CNTT Structure

 

Governance Steering

GSL: 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

TSL: 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

WSL: 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 community members

Name (Org)EmailGitHub ID





















Lifecycle Management

WSL: 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 community members

Name (Org)EmailGitHub ID





















Recruiting, Engagement, & Adoption

WSL: 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 community members

Name (Org)EmailGitHub ID





















Marketing & Communications

WSL: 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 community members

Name (Org)EmailGitHub ID





















Business | Technical Metrics

WSL: 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 community members

Name (Org)EmailGitHub ID





















Technical F2F Workshop

WSL: 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 community members

Name (Org)EmailGitHub ID





















Technical Workstreams


Reference Model Workstreams

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

CNTT RM  Core

WSL: 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

Committers List

Name (Org)EmailGitHub ID
Beth Cohen (Vz)beth.cohen@verizon.combfcohen
Ahmed ElSawaf (STC)aelsawaf.c@stc.com.saASawwaf
Bernard Tsai (DT)bernard.tsai@telekom.deBernardTsai-DT
Mark Shostak (AT&T)Mark.Shostak@att.commarkshostak
Karine Sevilla (Orange)karine.sevilla@orange.comkarinesevilla
Petar Torre (Intel)petar.torre@intel.com
Trevor Cooper (Intel)trevor.cooper@intel.comtrevgc
Rabi Abdel (VF)

abdel.rabi@vodafone.com

rabi-abdel
Cédric Ollivier (Orange)cedric.ollivier@orange.comcollivier
Xavier Grall (Orange)xavier.grall@orange.comxavier-grall
Pankaj Goyal (AT&T)pgoyal@att.compgoyal01
Samuel Hellec (Orange)samuel.hellec@orange.comsamuelhellec
Herbert Damker (DT)herbert.damker@telekom.dehdamker
Gergely Csatari (Nokia)gergely.csatari@nokia.comCsatariGergely
Tom Kivlin (VF)tom.kivlin@vodafone.comtomkivlin
Walter Kozlowski (Telstra)walter.kozlowski@team.telstra.comwkozlowski
Mehmet Toy (Vz)mehmet.toy@verizon.com



CNTT RM  Ops

WSL: TBA, TBA


Scope

The following Chapters of the Reference Model:

Ch06: Interfaces & APIs

Ch07: Security

Ch09: Operations and LCM

Committers List

Name (Org)EmailGitHub ID
Pankaj Goyal (AT&T)pgoyal@att.compgoyal01
Tom Kivlin (VF)tom.kivlin@vodafone.comtomkivlin
Walter Kozlowski (Telstra)

walter.kozlowski@team.telstra.com

wkozlowski
Mike Bustamente (AT&T)

mb100w@att.com

mbustame
Damian Eagle (Telstra)damian.j.eagle@team.telstra.comd-j-eagle






CNTT RM  Comp

WSL: TBA, TBA


Scope

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

Ch08: Compliance and Verification

Committers List

Name (Org)EmailGitHub ID
Mike Fix (AT&T)mf4716@att.commf4716
Kyle Greenwell (Vz) Kyle.Greenwell@VerizonWireless.comkagreenwell
JONATHAN BELTRAN (AT&T)jb788y@att.comjbeltranatl






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

WSL: TBA, TBA


Scope

The following Chapters of the Reference Model:

Ch01: Introduction

Ch02: Requirements

Ch03: High Level Architecture

Ch04: Component Level Architecture

Committers List

Name (Org)EmailGitHub ID
Pankaj Goyal (AT&T)pgoyal@att.compgoyal01
Beth Cohen (Vz)beth.cohen@verizon.combfcohen
Rabi Abdel (VF)

abdel.rabi@vodafone.com

rabi-abdel
Ian Gardner (VF)ian.gardner@vodafone.comiangardner22
Herbert Damker (DT)herbert.damker@telekom.dehdamker
Karine Sevilla (Orange)karine.sevilla@orange.comkarinesevilla
Samuel Hellec (Orange)samuel.hellec@orange.comsamuelhellec
Mehmet Toy (Vz)mehmet.toy@verizon.com
Gergely Csatari (Nokia)gergely.csatari@nokia.comCsatariGergely
Ahmed ElSawaf ( STC)aelsawaf.c@stc.com.saASawwaf

CNTT RA 1 (OS) Ops

WSL: TBA, TBA


Scope

The following Chapters of the Reference Model:

Ch05: Interfaces & APIs

Ch06: Security

Ch07: Operations and LCM

Committers List

Name (Org)EmailGitHub ID
Pankaj Goyal (AT&T)pgoyal@att.compgoyal01









CNTT RA 1 (OS) Dev (upstream)

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

Committers List

Developers List

Name (Org)EmailGitHub IDName (Org)EmailGitHub ID
Sukhdev Kapursukhdev@juniper.net
sukhdevkapur



Pankaj Goyal (AT&T)pgoyal@att.compgoyal01














K8s Reference Architecture Workstreams

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

CNTT RA 2 (K8s) Core

PTL: 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

Name (Org)EmailGitHub ID
Tamas Zsiros (E///)tamas.zsiros@gmail.comTamasZsiros
Tom Kivlin (VF)tom.kivlin@vodafone.comtomkivlin
Rabi Abdel (VF)abdel.rabi@vodafone.comrabi-abdel
Gergely Csatari (Nokia)gergely.csatari@nokia.comCsatariGergely
Pankaj Goyal (AT&T)pgoyal@att.compgoyal01
Ahmed ElSawaf ( STC)aelsawaf.c@stc.com.saASawwaf






CNTT RA 2 (K8s) Ops

WSL: TBA, TBA


Scope

Standard interfaces and APIs, Security and LCM.

Ch05: Interfaces & APIs

Ch06: Security

Ch07: Operations and LCM

Committers List

Name (Org)EmailGitHub ID
Gergely Csatari (Nokia)gergely.csatari@nokia.comCsatariGergely









CNTT RA 2 (K8s) Dev (upstream)

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

Committers List

Developers List

Name (Org)EmailGitHub IDName (Org)EmailGitHub ID
Rabi Abdel (VF)abdel.rabi@vodafone.comrabi-abdel


Sukhdev Kapursukhdev@juniper.net
sukhdevkapur



Gergely Csatari (Nokia)gergely.csatari@nokia.comCsatariGergely


Pankaj Goyal (AT&T)pgoyal@att.compgoyal01


Ahmed ElSawaf ( STC)aelsawaf.c@stc.com.saASawwaf


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

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


Committers List

Name (Org)EmailGitHub ID












CNTT RI 1 Labs

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


Committers List

Name (Org)EmailGitHub ID












CNTT RI 1  Dev (upstream)

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


Committers List

Developers List

Name (Org)EmailGitHub IDName (Org)EmailGitHub ID






























Reference Certification Workstreams


CNTT RC NFVI

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.


Committers List

Name (Org)EmailGitHub ID












CNTT RC VNF

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.


Committers List

Name (Org)EmailGitHub ID












CNTT RC  Dev (upstream)

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


Committers List

Developers List

Name (Org)EmailGitHub IDName (Org)EmailGitHub ID






























  • No labels