You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
Currently this page is only editable by members of the TSC. Edit access will be granted to anyone wishing to act as the representeivcde from their carrier to and carriers specifically granted access.
Please use this table to help keep us up to date on where you are in the process.
Thanks! -kenny
SP Name | Contact | Early Engineering Evaluation | Formal Lab Deployment | Stage/Test Deployment | Production Deployment |
---|
AT&T | Ryan Hallahan |
|
|
|
|
Bell Canada | David S |
|
|
|
|
China Mobile | |
|
|
|
|
Cable Labs |
|
|
|
|
|
China Telecom | |
|
|
|
|
China Unicom |
|
|
|
|
|
Comcast |
|
|
|
|
|
Deutsche Telekom | | - Before Amsterdam 1st ONAP installations in evaluation lab
| - Since 2017
- ONAP deployment for evaluation purpose and use case implementations (vIMS, vEPC, Closed Loop)
- Openstack based internal lab with 6-8 ONAP tenants
- GitLab based automated deployment of ONAP in various releases
- Heat-based deployment (Amsterdam, Beijing)
- OOM-based deployment (Beijing, Casablanca, Master)
|
|
|
KDDI |
|
|
|
|
|
KT |
|
|
|
|
|
LG-UPlus |
|
|
|
|
|
Orange | Eric Debeau |
|
|
|
|
PCCW |
|
|
|
|
|
Reliance Jio | Former user (Deleted) |
|
|
|
|
SK Telecom |
|
|
|
|
|
Sprint |
|
|
|
|
|
Swisscom | David Perez Caparros | - Nov 2017, ONAP Amsterdam (Heat and OOM based) + ONAP use cases (vFWCL, vLB) on vanilla OpenStack Ocata
| - OPNFV Fraser NFVI lab
- ONAP Beijing installation (Heat based) for evaluation (Closed Loop, vFWCL)
- ONAP Casablanca/Master (OOM-based) for evaluation and BBS use case development & testing
|
|
|
Telecom Italia | |
|
|
|
|
Tencent |
|
|
|
|
|
Turk Telekom | Murat Turpçu |
|
|
|
|
Verizon | Viswanath Kumar Skand Priya |
|
|
|
|
Vodafone | Susana Sabater |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|