OSM PoCs: Difference between revisions
From OSM Public Wiki
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
** PoC Team Members: VMware, RIFT.io, Fortinet, DataArt | ** PoC Team Members: VMware, RIFT.io, Fortinet, DataArt | ||
* '''[[OSM PoC 3 - Heimdall Hybrid Web|OSM PoC#3 - Heimdall Hybrid Web: Orchestrating enterprise web 5G vertical scenario]]''' | |||
** PoC Team Members: IT Aveiro, Universidade de Aveiro, Universidade Federal do Rio Grande, Wavecom | |||
''' | '''Would you like to see your OSM PoC listed here? Please follow the instructions in the [[OSM PoC Framework]]''' | ||
Revision as of 07:36, 26 June 2018
- OSM PoC#1 - DevOps in Service Chains & 5G Network Slices
- PoC Team Members: Netrounds, Telenor, Intel, RIFT.io, Arctos Labs
- OSM PoC#2 - OSM with VMware Integrated Openstack in MEC architectures
- PoC Team Members: VMware, RIFT.io, Fortinet, DataArt
- OSM PoC#3 - Heimdall Hybrid Web: Orchestrating enterprise web 5G vertical scenario
- PoC Team Members: IT Aveiro, Universidade de Aveiro, Universidade Federal do Rio Grande, Wavecom
Would you like to see your OSM PoC listed here? Please follow the instructions in the OSM PoC Framework
This Page provides a list and details of OSM Proofs of Concept developed according to the OSM Proof of Concept Framework.
OSM Proofs of Concept are intended to demonstrate OSM as a viable MANO solution. Results and learnings are fed back to ETSI OSM.
No verification or test has been performed by ETSI on any part of these OSM Proofs of Concept.