15
© ETSI 2017 OSM PROOF OF CONCEPT FRAMEWORK Vanessa Little (VMware) OSM TSC

OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

  • Upload
    others

  • View
    0

  • Download
    0

Embed Size (px)

Citation preview

Page 1: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2017

OSM PROOF OF CONCEPT FRAMEWORKVanessa Little (VMware)

OSM TSC

Page 2: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2016© ETSI 2017© ETSI 2017

OSM PROOF OF CONCEPT

2

• The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are:

• Relevant to contribute to further development of OSM

• Showcase OSM in real-world useful scenarios and use cases

• Multi-vendor and/or component PoCs are welcome

Page 3: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2017

• Endorsed by the OSM Community

• Centrally located on the OSM Web Portal

• Assigned an official PoC number

• Awards and Recognition:

• OSM "Best New Feature Showcase Award”

• Industry Event Awards

• Technology Awards

3

BENEFITS OF AN OFFICIAL POC

Page 4: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2017

In order to be recognized as an official OSM PoC, it must:

1. Have at least one member that is an active OSM member or participant

2. Use Core OSM components

3. Be presented for comment to the OSM Community

4. Be approved by the Technical Steering Committee

4

POC CRITERIA

Page 5: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2016© ETSI 2017© ETSI 2017

HOW TO SUBMIT AN OFFICIAL OSM POC

Process Highlights:

• Join ETSI OSM

• Send a formal PoC proposal to the OSM_TECH mailing list with the purpose to

• Inform the OSM community

• Get feedback from the OSM community

• OSM TSC will acknowledge receipt of the proposal and communicate approval to the OSM_TECH mailing list.

5

Page 6: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2016© ETSI 2017© ETSI 2017

HOW TO SUBMIT AN OFFICIAL OSM POC - CONTINUED

• Send relevant information to OSM MARCOM for publishing on OSM website.

• Present PoC results in TECH meetings with the purpose to:• Regularly provide updates to OSM community and get feedback

• Complete the PoC - videos and supporting documentation

For more details, see the OSM wiki at: https://osm.etsi.org/wikipub/index.php/OSM_PoC_Framework

6

Page 7: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2017

A PoC Proposal must contain the following elements:

• PoC Title

• PoC Team Members (companies and main technical and marketing contacts -name email-)

• Short Abstract

• Key Takeaways

• PoC Technical Overview in OSM powerpoint template

• OSM version and Components leveraged by the PoC

• Demo dates, venues and links/videos if available

7

POC PROPOSAL OVERVIEW

Page 8: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2016© ETSI 2017© ETSI 2017

POC AND MARCOM

The PoC Team will provide the following information to the OSM MARCOM Task Force:• Trademarks and Permissions: Does the POC require ETSI OSM to obtain permission to use

any trademarks used in the POC?

• Licensing of Components: Will the POC text and images be contributed under APL 2.0 or CCL?

• Press Releases and Public Notifications: Will the POC participants provide supporting quotes?

• Marketing Programs:• Web

• Video

• Social media channels

• Events

8

Page 9: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2016© ETSI 2017© ETSI 2017

POC #2 OSM WITH VMWARE INTEGRATED OPENSTACK IN MEC ARCHITECTURES

• BY: VMware, RIFT.io, Fortinet, DataArt

• Additional Software used: ffmpeg, vyatta router, ixia traffic sim

• SCOPE: OSM Rel THREE as an orchestrator to deploy and maintain edge services in several different use cases including:• Video transcode at the network Edge with ffmpeg

• Fortinet as an sGW in vRan edge scenarios

• SD-WAN with vyatta vrouter

• Operational intelligence for distributed architectures.

9

Page 10: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2016© ETSI 2017© ETSI 2017

POC #2 TOPOLOGY

10

Core Data CenterManagement Cluster Resource Cluster

Micro Data Center 1MDC 1 Cluster Micro Data Center 2 MDC 2 Cluster

NSX DLR

NSX EdgeVMware Integrated

OpenStack

Orchestration

vCloud NFV

VNFvRouter

VNFVNF

NSXFabric

NSXFabric

NSXFabric

VNFvRouter

VNF VNFVideo EncodersGW

NSX DLR

NSX Edge VNFvRouter

VNFVNF

NSX DLR

NSX Edge

Micro Data Center 2

Page 11: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2016© ETSI 2017© ETSI 2017

PART 1: CONFIGURING NETWORK TO DEPLOY MULTIPLE DATA CENTERS

11

• Configure Virtual Infrastructure Manager (VMware Integrated OpenStack) in OSM

• Configure compute & network availability zones in VMware Integrated OpenStack for the Core Data Center and Micro Data Centers

Page 12: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2016© ETSI 2017© ETSI 2017

PART 2: DEPLOY SD-WAN SERVICES

12

• Deployment of vRouter VNF via OSM

• Configure and deploy VPN tunnels between the Core Data Center and Edge Data Centers

• Provision resources for VNF within VMware Integrated OpenStack

CONFIDENTIAL

Page 13: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2016© ETSI 2017© ETSI 2017

PART 3: DEPLOY DYNAMIC VIDEO TRANSCODING AT THE EDGE

13

• Deployment of Video Transcoding VNF in MicroDC via OSM

• Provision resources for VNF within VMware Integrated OpenStack

CONFIDENTIAL

Page 14: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2016© ETSI 2017© ETSI 2017

PART 4: SIMULATED VRAN WITH SGW AT EDGE

14

• Deployment of FortigatesGW VNF in a vRAN via OSM

• Provision resources for VNF within VMware Integrated OpenStack

• Deploy VNF at Edge Data Center

• Apply and modify security policies for Edge Data Center

CONFIDENTIAL

Page 15: OSM PROOF OF CONCEPT FRAMEWORK · OSM PROOF OF CONCEPT 2 •The Open Source Mano community encourages members to design and deploy Proofs of Concept (PoCs) that are: •Relevant to

© ETSI 2017

QUESTIONS?