PLEASE REFER TO R1 NETWORK CLOUD RELEASE DOCUMENTATION

NC Family Documentation - Release 1

THIS DOCUMENTATION WILL BE ARCHIVED

Contents

Introduction

This document describes the steps to create a single and multi-node edge sites. 

Akraino Portal Operations

Login

Visit the portal URL http://REGIONAL_NODE_IP:8080/AECPortalMgmt/ where REGIONAL_NODE_IP is the Portal IP.

Use the following credentials:

• Username: akadmin
• Password: akraino

Upon successful login, the Akraino Portal home page will appear.

Deploy an Edge Site Based on a Rover Blueprint

From the Portal home page:

1. Select an Edge Site MTN1 or MTN2 (these are the two default lab sites hosted in middle town NJ) by clicking on radio button provided in the first column of the table.
2. For the selected Edge Site, select a Rover Blueprint from the drop-down menu.
3. Click on Upload button (in the Sites column), this will open a pop-up dialog
4. Provide the edge site-specific details such as:
   1. Host IP address

   2. Host username

   3. Host password.

5. Click on Browse button, select the input file for Blueprint - Rover (Single-Node Cluster). 
   The input file is a property file that stores information in key-value format.  Sample input file used for ‘Rover’ deploy: 

   Copy and paste the below contents in to a file, and save it as rover.txt. Use this file for uploading as mentioned in step 4.d above.

   Verify the configuration details as applicable to your environment. For more details refer to Appendix - Edge Site Configuration

   rover.txt

   # Copyright 2018 AT&T Intellectual Property.  All other rights reserved.
   #
   # Licensed under the Apache License, Version 2.0 (the "License");
   # you may not use this file except in compliance with the License.
   # You may obtain a copy of the License at
   #
   #     http://www.apache.org/licenses/LICENSE-2.0
   #
   # Unless required by applicable law or agreed to in writing, software
   # distributed under the License is distributed on an "AS IS" BASIS,
   # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   # See the License for the specific language governing permissions and
   # limitations under the License.
   # Add proxy settings if required for your environment
   # export http_proxy=http://your.proxy.com:8080/
   # export https_proxy=http://your.proxy.com:8080/
   #
   # host name for server
   SRV_NAME=aknode45
   # server oem - Dell or HPE (case sensitive)
   SRV_OEM=Dell
   # out of band interface information for server (idrac/ilo/etc)
   SRV_OOB_IP=192.168.41.45
   SRV_OOB_USR=root
   SRV_OOB_PWD=calvin
   # mac address of server to be used during the build - not required for Dell servers
   # SRV_MAC=3c:fd:fe:b8:10:60
   # name of network interface used during build when ipxe.efi is booted and when os is booted
   # ipxe numbers ports from 0-n in pci bus order.
   # the netx value will depend on how many nics are in the server
   # and which pci device number is assigned to the slot
   SRV_IPXE_INF=net8
   # the build interface is the nic used by the Ubuntu installed to load the OS
   SRV_BLD_INF=enp135s0f0
   # the boot device is the device name on which the OS will be loaded
   SRV_BOOT_DEVICE=sdg
   # ipxe script to use - based on the os version and kernel to install
   # valid options are script-hwe-16.04.5-amd64.ipxe or script-16.04.5-amd64.ipxe
   SRV_BLD_SCRIPT=script-hwe-16.04.5-amd64.ipxe
   # template xml file to set bios and raid configuration settings
   SRV_BIOS_TEMPLATE=dell_r740_g14_uefi_base.xml.template
   SRV_BOOT_TEMPLATE=dell_r740_g14_uefi_httpboot.xml.template
   SRV_HTTP_BOOT_DEV=NIC.Slot.7-1-1
   # tempalte to run to configure OS after first boot
   # current options are: firstboot.sh.template, firstboot-genesis.sh.tempate or firstboot-airship-iab.sh.template
   SRV_FIRSTBOOT_TEMPLATE=firstboot.sh.template
   # VLAN to use during build and for final network configuration
   SRV_VLAN=41
   # basic network information for dhcp config and final server network settings
   SRV_MTU=9000
   SRV_IP=192.168.2.45
   SRV_SUBNET=192.168.2.0
   SRV_NETMASK=255.255.255.0
   SRV_GATEWAY=192.168.2.200
   SRV_DNS=192.168.2.85
   SRV_DOMAIN=lab.akraino.org
   SRV_DNSSEARCH=lab.akraino.org
   SRV_NTP=ntp.ubuntu.org
   # root password for server being built
   SRV_PWD=akraino,d
   # network bond information
   SRV_BOND=bond0
   SRV_SLAVE1=enp135s0f0
   SRV_SLAVE2=enp135s0f1
   
   

   

5. Click on Submit. This will upload the input file and the site details into the portal.

6. User will see the file uploaded successfully message in the sites column then Deploy button is enabled.

a.  Click on Deploy to begin the deploy process.
b. This process takes about an hour.
c.  User can click on Refresh (link) to update the status of the deploy on the portal.
d. The deploy status changes from ‘Not started’ to ‘In progress’ to ‘Complete’

7. User can additionally check the log files to track the progress of edge site installation, by logging into the regional_node_ip via ssh, and running this command: tail -f /var/log/akraino/scriptexecutor.log

Tempest Tests

Prerequisites

Specifics around OpenStack are beyond the scope of this guide.

• Validate all OpenStack settings as needed.
• Ensure all necessary OpenStack services are up and running for a particular site.
• Use appropriate values for the OpenStack username, password, region, and desired timeout.      

Running Tempest

• Navigate to ETE testing page using the left navigation menu in the portal.
• Select a deployed edge site in the Run Tests page, by clicking the radio button in the GUI table displayed.  This will enable the "Run Tempest" button.
• Click on "Run Tempest" to trigger the tempest test on the deployed edge site.
• Test status shows "In Progress" upon successful invocation.
• Test status gets updated to 'Complete', once the job gets completed.

Installing ONAP

Prerequisites

Specifics around ONAP are beyond the scope of this guide.

• Verify that a VLAN is created and can be used for OpenStack tenant VM
  • The VLAN ID
  • An IP (or a range of IP) that can be accessed from this VLAN
  • Gateway, DNS, for the IP
• A public private key pair for accessing ONAP VM
• If the Edge Node is behind proxy, the proxy URL
• Obtain the OpenStack keystone admin password

Installation

1. Navigate to the Akraino Blueprint > Add-Ons page via the left navigation menu.
2. Select a deployed edge site on the Install ONAP page.
3. Click on Upload button (in the sites column), this will open a pop-up dialog

4. Click on Browse button, select the input file for ONAP (parameters.env file).  
   The input file is a property file that stores information in key=value format.  Sample input file used for ONAP: 

   Copy and paste the below contents in to a file, and save it as parameters.env. Use this file for uploading as mentioned in step 4 above.

   Verify the configuration details as applicable to your environment. For more details refer to Appendix - ONAP Configuration

   parameters.env

   # Parameters that will be populated by camunda engine
   parameters:
   
     public_net_name: public
   
     public_physical_net_provider_name: bond0
   
     provider_segmentation_id: 50
   
     public_physical_net_type: vlan
   
     public_subnet_name: public
   
     public_subnet_cidr: 172.24.8.0/24
   
     public_subnet_allocation_start: 172.24.8.221
   
     public_subnet_allocation_end: 172.24.8.225
   
     public_subnet_dns_nameserver: 8.8.8.8
   
     public_subnet_gateway_ip: 172.24.8.1
   
     flavor_name: m1.onap
   
     onap_vm_public_key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCWcbAk6SJxvYf4CM75JGWsQ38149Fhu4dUXUmnmASFWuvPJ6sCpoGyMPQdEMEt3wITCFGfS4gw6eQO39NUaS4JqWYjNN6sejernldwyqGwz42H/rn7CL0xhbCql9upWF+2bm5X46UgSwZBYcLxW0BrOh+0lxkON+2qOGZFbtEcOUeOVmRSJdBuxczyGD5i6zusITJ00scqfNTCyRLm8JiHlW9SY43iyj3Lq0cDxYQ97fKX2F+0D/JfnWPu/2v+HaJWDpfpNG/Mo/SVzNAwE997DMY1ZD9jJsoYPr8UWypQQJUMldn3P+ERaswNTXnGbmCnwRGlj7IANnmGCc7koi6t root@csoaiclab01-85
   
     http_proxy:
   
     https_proxy:
   
     no_proxy:
   
     keystone_admin_password: password
   
     onap_tenant_password: amsterdam
   
     onap_artifacts_http_repo:
   
   

5. User will see the "file uploaded successfully" message in the sites column. Then, "Install ONAP" button gets enabled.
6. Click "Install ONAP" to begin the installation.
7. The ONAP status changes from ‘Not started’ to ‘In progress’ to ‘Complete’.
8. ONAP VM will be created successfully after the job completes.  It may take several hours for ONAP to become operational.

Onboarding a Sample VNF

1. Navigate to the Akraino Sites page via the left navigation menu.
2. Select a deployed edge site in the GUI table displayed. The VNF Onboard button becomes enabled.
3. Click VNF Onboard This will open a Pop up dialog.  Choose VNF as vCDN (Sample VNF) from the drop-down
4. Verify all the default entries as applicable to your environment.
5. Click Onboard to begin the sample VNF installation. This process may take few minutes to complete.
6. The VNF Onboard status changes from ‘Not started’ to ‘In progress’ to ‘Complete’.

The Sample VNF creates an Apache Traffic Server cache instance and a Locust load generator client instance in the OpenStack environment for the selected site.  By default, the Sample VNF will create a heat stack name ats-demo.  The heat stack will contain two instances named ats-demo-client and ats-demo-server.  The default configuration of the server instance is to cache the Big Buck Bunny videos from the internet server and then serve the video to the client from its ramdisk. The heat stack will output the client and server URLs.  The client URL will display the Locust load generator dashboard.  The server URL will allow you to play the video in a browser.

OpenStack stack output show ats-demo --all

"output_value": "http://192.168.48.223:8089/", 
"output_key": "client_url", 
"description": "URL for client"

"output_value": "192.168.48.223",
"output_key": "client_ip", 
"description": "IP of the client"

"output_value": "http://192.168.48.226:8080/bbb_sunflower_1080p_30fps_normal.mp4",
"output_key": "server_url", 
"description": "URL for server"

"output_value": "192.168.48.226",
"output_key": "server_ip", 
"description": "IP of the server"

SRV_NAME=aknode45

SRV_OOB_IP=192.168.41.45
SRV_OOB_USR=root
SRV_OOB_PWD=XXXXXXXX

SRV_MAC=3c:fd:fe:b8:02:90

SRV_OEM=Dell

SRV_IPXE_INF=net8
SRV_BLD_INF=enp135s0f0
SRV_BOOT_DEVICE=sdg

SRV_BLD_SCRIPT=script-hwe-16.04.5-amd64.ipxe

SRV_BIOS_TEMPLATE=dell_r740_g14_uefi_base.xml.template
SRV_BOOT_TEMPLATE=dell_r740_g14_uefi_httpboot.xml.template
SRV_HTTP_BOOT_DEV=NIC.Slot.7-1-1

SRV_FIRSTBOOT_TEMPLATE=firstboot.sh.template

SRV_VLAN=41

SRV_MTU=9000
SRV_IP=192.168.2.45
SRV_SUBNET=192.168.2.0
SRV_NETMASK=255.255.255.0
SRV_GATEWAY=192.168.2.200
SRV_DNS=192.168.2.85
SRV_DOMAIN=lab.akraino.org
SRV_DNSSEARCH=lab.akraino.org
SRV_NTP=ntp.ubuntu.org

SRV_PWD=XXXXXXXX

SRV_BOND=bond0
SRV_SLAVE1=enp135s0f0
SRV_SLAVE2=enp135s0f1

jdbc:postgresql://<IP-address-of-DB-host>:6432/postgres
user name = admin
password = abc123

> insert into akraino.edge_site(edge_site_id, edge_site_name, crt_login_id, crt_dt, upd_login_id, upd_dt, region_id)
  values( 1, 'Atlanta', user, now(), user, now(),1);

public_net_name: public

  # Assume vlan50 is the VLAN created 
  # for the OpenStack Project (tenant)
  public_physical_net_provider_name: vlan50

  # Assume vlan50
  provider_segmentation_id: 50

  public_physical_net_type: vlan

  public_subnet_name: public-subnet

  public_subnet_cidr: 192.168.102.0/24

  public_subnet_allocation_start: 192.168.102.100

  public_subnet_allocation_end: 192.168.102.200

  public_subnet_dns_nameserver: 8.8.8.8

  public_subnet_gateway_ip: 192.168.102.1

  flavor_name: x1.onap

  onap_vm_public_key: PUBLIC_KEY

  http_proxy: http://proxy.yourdomain.com:8888

  https_proxy: https://proxy.yourdomain.com:8888

  no_proxy: 127.0.0.1

  keystone_admin_password: XXXXXXXX

  onap_tenant_password: XXXXXXXX

  onap_artifacts_http_repo: http://192.168.102.220/onap