OSM PoC 2 - OSM with VIO in MEC architectures: Difference between revisions
From OSM Public Wiki
(Created page with "= PoC Team Members = VMware, RIFT.io, Fortinet, DataArt ''VMware, RIFT.io and DataArt are OSM members or participants'' * VMware: Suzanne McCormac [mailto:mccormacs@vmware...") |
|||
Line 19: | Line 19: | ||
= PoC Proposal = | = PoC Proposal = | ||
*[[media:OSM_POC_2_Overview.pdf|Initial Proposal: OSM PoC#2 Overview]] | *[[media:OSM_POC_2_Overview.pdf | Initial Proposal: OSM PoC#2 Overview]] | ||
= PoC Report = | = PoC Report = |
Revision as of 15:08, 4 October 2017
PoC Team Members
VMware, RIFT.io, Fortinet, DataArt
VMware, RIFT.io and DataArt are OSM members or participants
- VMware: Suzanne McCormac mccormacs@vmware.com
- RIFT.io: George Hamilton george.hamilton@riftio.com
- Fortinet: Thorsten Jaeger tjaeger@fortinet.com
- DataArt: Michael Lazar Michael.Lazar@dataart.com
Abstract
This POC will showcase leveraging OSM Rel THREE as an orchestrator to deploy and maintain edge services in several different use cases that make use of the same hardware footprint, as well as discuss the overall infrastructure topology. These use cases include video transcode at the network Edge with ffmpeg, using Fortinet as an sGW in vRan edge scenarios, SD-WAN with vyatta vrouter and operational intelligence for distributed architectures.
Key Takeaways
- OSM can be leveraged for distributed multi-data center service scenarios
- OSM is compatible with VMware Integrated Openstack version 4.0 (Ocata) with NSX as SDN
- Multi-Access Edge Computing scenarios are possible with OSM and Ocata based openstacks
- End to end service monitoring using existing tools
PoC Proposal
PoC Report
Coming soon!
OSM Components
- OSM Rel THREE
Demos
Coming soon!