China Telecom ONAP Lab

Responsible Party
China Telecom, Contact: Yi Yang yangyi.bri@chinatelecom.cn, Luman Wang wanglm.bri@chinatelecom.cn

Equipment available today and expected from ONAP
Available Equipment
Space:
    Laboratory room
    Rack
Hardware:
    Servers
    Router (IP Backbone and MPLS Backbone)
    Switch
    DC Gateway
    Firewall
    Thin CPE
    IPRAN
Software:
    VNFs (Commercial):
    vCPE
    vEPC
VIM:
    Redhat
    Ubuntu     
    Wind River Titanium Cloud (OpenStack VIM)

Controller:
    DC Controller
    WAN Controller

Others:

     Internet IP address

Power availability
       Stable power supply is available(AC and DC).

Networking availability
      Internal availability: 
               Available networking facilities with support for changes in case of use case requires.

  From external access:

               Remote access to the network via VPN or direct access to the bastion host via a firewall.

Technical support from your company and expected support from ONAP

        Laboratory operation and maintenance are available from China Telecom.

Willing to support the ONAP use cases and member companies?

        Support VoLTE on vEPC, vCPE, vCPE extension &vFW use cases;

Proposal 4 (more detailed information can be provided):

Orange Integration Center

(used for OPNFV - Orange responsible of functest stream; also used for our operational needs – such as vEPC and all Orange PNF testing).

Responsible Party
Orange. Contact Eric Debeau (eric.debeau@orange.com), Odile Duthil (odile.duthil@orange.com), Anne Tréhu (anne.trehu@orange.com)

WAN (2) /IPRANRouter (8)

DC Gateway (2)

TOR (n)

ThinCPE (2)

Cloud OS (for Edge and Core)

WAN/IPRANController

DC Controller

Specific VNFM & EMS

WAN (2) /IPRANRouter (8)

DC Gateway (2)

TOR (n)

Wireless Access Point (4)

VoLTE Terminal Devices (2)

Cloud OS (for Edge and Core)

WAN/IPRANController

DC Controller

Specific VNFM & EMS

Proposal 4 (more detailed information can be provided):

Name of the Lab/Company
Orange Integration Center (used for OPNFV - Orange responsible of functest stream; also used for our operational needs – such as vEPC and all Orange PNF testing).

Responsible Party
Orange. Contact Eric Debeau (eric.debeau@orange.com), Odile Duthil (odile.duthil@orange.com), Anne Tréhu (anne.trehu@orange.com)

Power availability
Stable power supply is available.

Networking availability
Internal availability: available networking facilities with support for changes in case of use case requires
From external access: remote network access by VPN 

Technical support from your company and expected support from ONAP
Laboratory operation and maintenance are done by Orange.

Willing to support the ONAP use cases and member companies?
Willing to support VoLTE (and related subcases such as EPC or end to end automation) & vCPE use cases. Other use cases are welcome.

Proposal 5: ONAP-Test Lab (TLab)

Name of the Lab/Company
     AT&T ONAP Lab

Responsible Party
AT&T Advanced Technologies; Contact Rich Bennett (RB2745@att.com); John Murray (JM2932@att.com) 

Equipment available today and expected from ONAP
Available Equipment
Space:
     Laboratory room
     Rack/Power/Cooling/Network
Hardware:     
     Servers
     Router (SPTN/Router)
     Switches
     VPN Gateway
     JUMP Server/Boot Server
Software
Space:
     VNFs (Open Source):
          vFirewall
          vDNS
          Test/ characterization
     VIM:          
          OpenStack
          Ubuntu  
    Automated Test Software: TBDExpected Equipment from ONAP
Equipment  Laboratory room (in our Lannion Premises)
Hardware:     
     Servers (capacity need to be assessed as the lab is also used for operational testing)
Software:
     VNFs, VIM: opensource can be installed on demand. Commercials: need of supplier agreement. We have redhat, Mirantis        
Interopability
Available Equipment and facilities for interop testing/ performance testing: core network (IMS, Volte, EPC), IP and transmission, fixed and mobile access. Independently from ONAP, the lab is to be connected to major supplier integration labs to work in joint agile delivery mode.

Expected Equipment from ONAP
Depending on needs, additional servers may be needed, as well as equipment for remote connection through VPN.

Power availability
Stable power supply is available.

Networking availability
Internal availability: available networking facilities with support for changes in case of use case requires
From external access: remote network access by VPN 

Technical support from your company and expected support from ONAP
Laboratory operation and maintenance are available from AT&T Advanced Technologies.

Availability according to minimal assets requirement:

Use Cases

VNFs

Server Pod number

Network Hardware

Software

Available Resources in TLab

Development for  vFW/vDNS demo apps

Open sourced  vFW/vDNS

1 (Small)

No

Cloud OS

Yes

DRAFT Initial TLAB Focus for discussion 8/10/2017 openlab Meeting

Demonstrate new ONAP features to developers building production services,

Gather feedback on what developers need to use the ONAP features in production.

Identify ONAP platform issues that need to be resolved for production use

Support/provide an environment for ONAP community work collaboratively and efficiently together to resolve these issues.

 This focus should accelerate adoption of ONAP,  grow community engagement, and reduce time to deliver important platform features.

Proposal 6: WINLAB (industry-university community lab extended to support ONAP)

Name of the Lab/Company

1. WINLAB (www.winlab.rutgers.edu/) at Rutgers University
2. AT&T and other sponsors/partners

Responsible Party

1. Rutgers University contact: Ivan Seskar (seskar@winlab.rutgers.edu)
2. AT&T contact: Tracy Van Brakle (tv8394@att.com)

Equipment available today

1. Indoor - Laboratory room (ORBIT), rack, power, cooling;
   1. Servers
   2. Router (SPTN/Router)
   3. Switch
   4. DC Gateway 
   5. Access Point
   6. Communication Terminals
2. Outdoor - Multi-campus, multi-protocol wireless equipment & networks

Expected Equipment from ONAP Additional servers may be required

Power availability Stable power supply is available but may require augmentation if additional servers are introduced

Networking availability

1. Internal: networking facilities with support for modifications
2. External: remote network access by VPN (self-serve)

Technical support from your company and expected support from ONAP

1. Laboratory operation and maintenance provided by WINLAB
2. ONAP use case support provided by AT&T and other sponsors/partners

Willing to support the ONAP use cases and member companies?

and expected support from ONAP
Laboratory operation and maintenance are done by Orange.

Willing to support the ONAP use cases and member companies?
Willing to support VoLTE (and related subcases such as EPC or end to end automation) & vCPE use cases. Other use cases are welcome.

Proposal 5: ONAP-Test Lab (TLab)

DISCONTINUED

AT&T Advanced Technologies; Contact Rich Bennett (RB2745@att.com); John Murray (JM2932@att.com) 

Equipment available today and expected from ONAP
Available Equipment
Space:
     Laboratory room
     Rack/Power/Cooling/Network
Hardware:     
     Servers
     Router (SPTN/Router)
     Switches
     VPN Gateway
     JUMP Server/Boot Server
Software:
     VNFs (Open Source):
          vFirewall
          vDNS
          Test/ characterization
     VIM:          
          OpenStack
          Ubuntu  
    Automated Test Software: TBD

Expected Equipment from ONAP
Equipment for remote connection through VPN.

Power availability
Stable power supply is available.

Networking availability
Internal availability: available networking facilities with support for changes in case of use case requires
From external access: remote network access by VPN 

Technical support from your company and expected support from ONAP
Laboratory operation and maintenance are available from AT&T Advanced Technologies.

Availability according to minimal assets requirement:

DRAFT Initial TLAB Focus for discussion 8/10/2017 openlab Meeting

Demonstrate new ONAP features to developers building production services,

Gather feedback on what developers need to use the ONAP features in production.

Identify ONAP platform issues that need to be resolved for production use

Support/provide an environment for ONAP community work collaboratively and efficiently together to resolve these issues.

 This focus should accelerate adoption of ONAP,  grow community engagement, and reduce time to deliver important platform features.

Proposal 7: Auto Project Arm Pod (OPNFV project lab offered to ONAP Community)

Name of the Lab/Company

1. (iol.unh.edu) at University of New Hampshire

2. Auto project of OPNFV, sponsored by Arm

Responsible Party

1. University of New Hampshire contact: NFV/IOL staff (nfv-lab@iol.unh.edu)
2. Arm/OPNFV contact: Paul Vaduva (paul.vaduva@enea.com)

Equipment available today

1. 6 Cavium servers make up the OPNFV Pod.  
   1. 48-core, 64G Servers
      1. 1 Jump Host for deploying OPNFV/OpenStack
      2. 3 OpenStack Controllers for an HA configuration
   2. 96-core, 128G Servers
      1. 2 OpenStack Compute Servers 

Expected Equipment from ONAP None at this time

Power availability N/A

Networking availability

1. Internal: The networking availability for users of the lab is within the context of an OpenStack environment.  
2. External: remote network access by VPN - request credentials by emailing: nfv-lab@iol.unh.edu

Technical support from your company and expected support from ONAP

1. Laboratory operation and maintenance provided by UNH IOL staff (nfv-lab@iol.unh.edu)
2. Access to the OpenStack environment and assistance with that environment is provided/coordinated through Joe Kidder Paul Vaduva (JoePaul.kidder@5thlayerVaduva@enea.com).

Willing to support the ONAP use cases and member companies?

1. At this time, the primary focus is ONAP component container development (porting and building), but testing is supported as well as containers are produced.
2. vFW usecase ported to arm64 openstack deployment.