Page History

Technology (Reference Model)

Opening – Recap and Day Ahead

Facilitator: Jonathan Beltran, AT&T

Reference Model: Release 2 Scope

Facilitator: Walter Kozlowski, Telstra, Rabi Abdel, Vodafone, Mark Shostak, AT&T

Reference Model Updates:

Refine 1-7 based on ‘maturity level’ (Incl. backlog from Day 1)

Finalize 8-11 Scope

Meaningful targets – how to manage from R1, what is backlog from R3, R4?

Detailed Release Timeline – Feedback / Doability / Issues / Concerns / Gaps

Technology WG overview

Facilitator: Rabi Abdel, Vodafone

Document Structure, Current Contributions framework, How to get involved

Chapter 8 (R1) – NFVI Security

Facilitator: Beth Cohen, Verizon

This section needs to be expanded in Release 2.  How much is this specific to NFVI?  How much can we base this on existing security standards and best practices?  Which standards apply?

• 8.1 Common standards.
• 8.1.1 Potential attack vectors
• 8.1.2 Testing demarcation points.
• 8.2 Operator responsibility.
• 8.3 VNF Vendors responsibility.
• 8.4 NFVI Vendors responsibility.

Chapter 9 (R1) - Reference Model Development

Facilitator: Mark Shostak, AT&T

Infra OA&M

Chapter 7 (R1) – Reference Model Development

Facilitator: Mark Shostak, AT&T

API Interfaces

Chapter 3 (R1) - Reference Model Development

Facilitator: Sabine Demel, DT; Mark Shostak, AT&T

(Description TBD)

Chapter 5 (R1) - Reference Model Development

Facilitator: Karine Sevilla, Orange 

(Description TBD)

Chapter 6 (R1) - Reference Model Development

Facilitator: Pankaj Goyal, AT&T

(Description TBD)

Chapter 1, 2, 4 (R1) – Reference Model Development

Facilitator: Beth Cohen, Verizon, Tom Kivlin, Vodafone Group

A guided discussion of what needs to be in the introduction (Chapter 1), based on the content of the other chapters.  Chapters 2 and 4 are both well along in the development of the content, the objective in this discussion is to validate the approach that the initial team created.  Does this match with the  understanding of the requirements by the vendor community?  Are there missing pieces that need to be added? 

Day 2 –  Wrap Up

Facilitator: Jonathan Beltran, AT&T

Opening – Recap and Day Ahead

Facilitator: Jonathan Beltran, AT&T

Technology (Reference Architecture)

Panel Discussion: Reference Architecture: Principles

Facilitator: Walter Kozlowski, Telstra

Panel: Karine Sevilla, Pankaj Goyal, Rabi Abdel

How to Engage and Create

Role of Reverence Model and Reference Architectures 

Reference Architectures Principles

Reference Architecture #1: Straw-man Proposal

Facilitator: Rabi Abdel, Vodafone; Mark Shostak, AT&T

Create ToC for Reference Architecture R1

Setting meaningful targets, backlog

Detailed Release Timeline – Feedback / Doability / Issues / Concerns / Gap

Including adoption of OVP VNF Certification and NFVi verification 

(align this with other open source bodies also)

How to cooperate on and create when we leave here.

Support and Sponsorship

Enhancements to Test projects / OVP & CVC ecosystem

Facilitators: Rabi Abdel, Vodafone, Heather Kirksey, Linux Foundation

Vision: 

Describe current OVP/CVC vision and relation to CNTT, impact on OPNFV, ONAP, etc.

Understanding the ecosystem (who, what, where, how?):

Existing Test project / OVP ecosystem. CI/CD processes and procedures, security, etc. What in-flight projects are impacted? Which does CNTT feed? Which feed CNTT? Which are obsoleted? Where are there opportunities for improvement? What else does CNTT need to consider?

Realization:

What are the real steps in the journey? How do we reveal the reference platform profiles and architectures into OPNFV code? How do we go from model to arch to implementation to various project code updation? How could/should it work from a practical perspective?

What will help us facilitate release management?

OPNFV Project Plan:

What shall be our approach? What are the key components? 

Reference Implementation / OVP & CVC ecosystem

Facilitator: Jim Baker - Linux Foundation, Bin Hu - AT&T, Fu Qiao - China Mobile 

OVP Infrastructure:

What enables smooth transitions? Where and how do reference models, architectures, implementations get hosted? How to make seamless translations between GSMA OPNFV addressable works? Demarcations with other bodies? 

Potential topic list:

1. OPNFV plans (leveraging CVC, TAC and OPNFV TSC) to ingest CNTT deliverables in terms of reference architecture implementations from CNTT, enhancements to certification entrance / exit criteria from CNTT and/or test case contributions from CNTT as it relates to NFVI VNF certification.
2. OPNFV request of CNTT to support, aid, contribute, etc. to #1 above

‘Project Management’:

What needs to be aligned to ensure all workloads come up and all work (so that VNF certification testing can begin?); Tasks? Deliverables? Processes? Release Timetables

Where Do We Go From Here

Panel Discussion: Adoption Strategy / Membership

Facilitator: Mark Cottrell, AT&T, Rabi Abdel, Vodafone, David Hutton, GSMA, Heather Kirksey, Linux Foundation, Jeff Collins, Ericsson, Jonne Soininen, Nokia

Establish metric targets as part of value propositions:

VNF Operational efficiency & Innovation acceleration, Cut amount of internal testing to be done by SPs, Accelerate Time To Market, Improve Quality, Reduce Costs, Reduce Barriers To Entry

Examples:

Reduction in testing and integration costs, Reduction in certification time, Reduction in defects, Reduction in operational costs…

What is overall message: 

“This is a GSMA OPNFV jointly supported activity...”, Adoption of Ref Model and Architectures (as part of RFQ process), Collaborative Marketing

Leveraging Media Relationships: 

Telecom TV. SM alliances. SDX Central articles. Talking to analysts. Meetup Groups.

Closing Session & Next Steps

Facilitator: Jonathan Beltran, AT&T

Accomplishments:

What did we get done? What did we gain alignment/agreement on? What did we sign-off on?

What still needs work?

Follow ups:

What do we need follow up on? Who are they assigned to?

Next steps:

What are our next steps? With OPNFV / OVP / CVC? With GSMA? With Task Force? With other stakeholders?

Calendar and Schedule:

Review and confirm remote meetings. Review and confirm face-to-face meetings

Session Review:

Give everyone an opportunity to speak into all the topics of the day: What went well? What didn’t go so well? What should we change?

Closing Round Table Remarks: David Hutton, GSMA, Heather Kirksey, Linux Foundation