Minimal Assets for Physical Lab

Community Labs: Incubation

On Line Labs:

ONAP-POD-01 Integration and Deployment Lab - Oregon, USA

• Sponsored By: Intel

• Managed By: VMware and Wind River Titanium Cloud

• Responsible Party:  Stephen Gooch and Eddy Raineri
  

  
  

• Connection: VPN:
  

  • Update Integration / Developer Lab Access, then Open JIRA: https://jira.onap.org/projects/OPENLABS
    
    - Component MULTI_GEOLAB
    - List which project you belongs to, and update Integration / Developer Lab Access
    - Assign to Stephen Gooch

  
  

  • From the JIRA, a form letter is sent with an encrypted zip file. There are two files in this zip:
    
    

    1. login.txt (your username and password)
    2. pod-onap-01.ovnp (Open VPN CA same for all)
    
    Edit pod-onap-01.ovpn to include login information:
    
    1. Linux/Mac: auth-user-pass login.txt
    2. Windows: auth-user-pass “C:\\Program Files\\OpenVPN\\config\\login.txt
    
    (You many need to add “http-proxy url:port” or “socks-proxy url:port”. Discuss with your IT reprehensive.)
  
  

  • Execute:
    
    1. Linux/Mac: 

    $ sudo openvpn –config pod-onap-01.ovpn

    
    2. Windows: Install the Open VPN client
                          Import pod-onap-01.ovpn
                          Select Connect
    
    

  • 600 Cores, 5T RAM, 70TB Storage
    
    
  • Infrastructure Software = Wind River Titanium Cloud (Openstack Newton Based)
    
    
    

  • Deployment testing with MultiVIM/Cloud:

For testing with  MultiVIM/Cloud use the following two clouds. Both are based on OpenStack

• • • Wind RIver Titanium Edge SX (Single blade Newton Based)

    • VMware VIO 4.1

      
      

  • Lab Infrastructure

• VMware VIO 4.1 Infrastructure

VMware VIO 4.1 infrastructure employs the below nodes.

• node-1 as part of VMware Intergrated Openstack 4.1 installation
• node-2 as part of VMware Intergrated Openstack 4.1 installation

• node-3 is used to deploy a router to provide access to and from VM deployed on Wind RIver Titanium Edge SX cloud
  
  

• VMware VIO 4.1 Deployment details

  • VIO 4.1 is deployed in Compact mode
  • VIO 4.1 networking details
  • VLANs
    • VLAN 100 (192.168.100.0/24)
    • VLAN 101 (192.168.101.0/24)
    • VLAN 102 (192.168.102.0/24) - For External Network i.e. Floating IPs
  • Gateways
    • VLAN 100 - 192.168.100.1
    • VLAN 101 - 192.168.101.1
    • VLAN 102 - 192.168.102.1

  • DNS Server - 8.8.8.8

• VMware VIO 4.1 Access details

  • Auth URL: https://192.168.101.2:5000/v3

  • Horizon Access: https://192.168.101.2
  • VIO Certificate: Required to access the Auth URL and VIO services. Following is the procedure to install the VIO certificate on a VM (Assuming Ubuntu VM)
    • Download the below attached vio.crt.tar
    • Extract the vio.crt file using command:
      tar xvf vio.crt.tar
    • Move vio.crt in /usr/local/share/ca-certificates
    • Update the CA certificates list by executing
      sudo update-ca-certificates -f
      
      
    vio.crt.tar
  
  
  • The Project details, project user, password and RC file will be provided as per the request submitted for the lab resources.
  • To use the Auth URL and to execute the openstack commands, add the following in the RC file to provide the Certificate path for python. Here, assuming the VM is Ubuntu and VIO certificate is already installed on the VM:
    export REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt

• VMware VIO 4.1 Access from systems/ VMs deployed on Non-VIO nodes (For e.g. on Windriver cloud, or Jumphosts)

  • VIO 4.1 resources can be accessed through the Router configured on Node 3

  • The router has static routes configures to forward any requests to/from IPs on VLAN 100, 101 and 102 which are used by VIO 4.1

  • Configure 10.12.9.1 as the gateway on your VM to access IPs on VLAN 100, 101, 102.
  • For. e.g. to Access the VIO AUTH URL (https://192.168.101.2:5000/v3) set the gateway of your VM to 10.12.9.1 and then try curl -i https://192.168.101.2:5000/v3
  • To access the VIO Horizon, Set the HTTP proxy to http_proxy=10.12.9.1:3128, Or, in the Web Browser set the proxy for all protocols to 10.12.9.1 & port 3128

• After connecting the VM.  You can use a local Linux machine or the supplied jumpstation for OpenStack CLI access.

• Download OpenStack RC File from UI:
  • Project -> Compute -> Access & Security -> API Access
    
    
• Upload file to jumpstation (or local machine).  If running on local machine, ask stephen.gooch@windriver.comfor remote CLI SDK.
  
  

• Source and run OpenStack commands

  user@pod-onap-01-vjhost:~$ source ./Integration-openrc.sh

  
  Please enter a path for your CA certificate pem file, #or press enter if you are not using HTTPS 
  Please enter your OpenStack Password for project integration as user username:

  
  

  $ sudo openvpn –config pod-onap-01.ovpn 

• Jumpstation IP   10.12.5.50

Proposals:

Proposal 1:

1. Name of the Lab/Company
   China Mobile ONAP Lab
   
   
2. Responsible Party
   China Mobile, Contact: Chengli Wang  wangchengli@chinamobile.com, Wenyao Guan guanwenyao@chinamobile.com 
   
   
3. Equipment available today and expected from ONAP
   Available Equipment
   Space:
        Laboratory room
        Rack
   Hardware:     
        Servers
        Router (SPTN/Router)
        Switch
        DC Gateway
        Thin CPE
        Access Point
        Communication Terminal
   Software:
        VNFs (Commercial):
             vCPE
             vIMS 
             vEPC
        VIM:          
             Redhat          
             Ubuntu  
             VMware VIO
             Wind River Titanium Cloud (OpenStack VIM)
       Controller:
             DC Controller
             SPTN Controller
             WAN Controller
   
   Expected Equipment from ONAP
   Equipment for remote connection through VPN.
   
   
4. Power availability
   Stable power supply is available.
   
   
5. 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 
   
   

6. Technical support from your company and expected support from ONAP
    Laboratory operation and maintenance are available from China Mobile.

7. Availability according to minimal assets requirement:

   
   

   Use Cases	VNFs	Server Pod number	Network Hardware	Software	Available Resources in CMCC lab
   Development or vFW/vDNS demo apps	Open sourced vFW/vDNS	1 (Small)	No	Cloud OS	Yes
   vCPE	vCPE	2 (Medium)	WAN/SPTN Router (2) DC Gateway (2) TOR (n) ThinCPE (1)	Cloud OS (for Edge and Core) WAN/SPTN Controller DC Controller Specific VNFM & EMS	Almost available (lack of 1 DC gateway)
   VoLTE	vIMS/vEPC	2 (Large)	WAN/SPTN Router (2) DC Gateway (2) TOR (n) Wireless Access Point (2) VoLTE Terminal Devices (2)	Cloud OS (for Edge and Core) WAN/SPTN Controller DC Controller Specific VNFM & EMS	Almost available (lack of 1 DC gateway)

Willing to support the ONAP use cases and member companies?
 Support VoLTE & vCPE use cases.

Proposal 2:

1. Name of the Lab/Company
   
   Reliance Jio R&D Labs
2. Responsible Party
   
   Reliance Jio Infocomm
   
   
3. Equipment available today and expected from ONAP
   Available Equipment
   
   Available Equipment and facilities include the following for interop testing and performance testing: 
   
   VoLTE core network, 
   WiFi Core Network
   EPC core network,
   FTTx Core network
   IP/MPLS Core Network - all topologies.
   OSS and BSS applications
   Access network functions - Radio, Fixed and WiFi
   Fully functional devices lab (LTE and Fixed) for UE support.
   Security Testing practice for aiding security aspects of the ONAP Platform installation and the VNFs on top of Openstack.
   Installation of ONAP and Openstack available for swift testing on a NFVI.
   
        
   Expected Equipment from ONAP
   
   Based on the infra requirements, pods can be installed and commissioned for creating a infrastructure with remote connectivity via VPN for realizing the use cases and testing them end to end. Equipment would consist of Racks (Open CG Rack 19 compliant or others), Installation material and blade servers (Intel based).
   
   
4. Power availability
        Stable power supply is available - with redundancy.
   
   
5. Networking availability
   Networking facilities are available in the lab with support for on-demand changes if needed by a use case.
   
   
6. Technical support from your company and expected support from ONAP
        Laboratory operation and maintenance are available from Reliance Jio.
   
   
7. Willing to support the ONAP use cases and member companies?
        Willing to support the ONAP use cases on VoLTE and vCPE. Other use cases that may come up in the future can also be tried out.

Proposal 3: