Contents

Introduction

This document describes the steps to create a single and multi-edge node. Edge Nodes are deployed at physical locations called Edge Nodes.

Edge Node Configuration

Rover (Single-Node Cluster)

This configuration file is written as a series of shell key/value assignments.

BUILD_INTERFACE=vlan41

BUILD_WEBIP=192.168.2.44
BUILD_WEBPORT=8090

SRV_NAME=aknode42

SRV_OOB_IP=192.168.41.42
SRV_OOB_USR=root
SRV_OOB_PWD=XXXXXXXX

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

SRV_OEM=Dell

SRV_IPXE_INF=net4
SRV_BLD_INF=enp94s0f0
SRV_BOOT_DEVICE=sdg

SRV_BLD_SCRIPT=script-hwe-16.04.4-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_VLAN=41

SRV_MTU=9000
SRV_IP=192.168.2.42
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=enp94s0f0
SRV_SLAVE2=enp94s0f1

Unicycle (Three-Node Cluster) 

This configuration file is written in YAML.

site_name

site_name: hp_akraino

ipmi_admin_password

ipmi_admin_password: XXXXXXXX

networks

networks:
  bonded: yes
  primary: bond0
  slaves:
  - name: ens3f0
  - name: ens3f1
  oob:
    # Note: host, storage, pxe, and
    # neutron use similar notation
    vlan: 40
    interface: bond0.40
    cidr: 192.168.41.0/24
    routes:
      gateway: 192.168.41.1
    ranges:
      reserved:
        start: 192.168.41.2
        end: 192.168.41.4
      static:
        start: 192.168.41.5
        end: 192.168.41.254
   ksn:
     vlan: 44
     interface: bond0.44
     cidr: 172.29.1.0/24
     local_asnumber: 65531
     ranges:
       static:
         start: 172.29.1.5
         end: 172.29.1.254
     additional_cidrs:
     - 172.29.1.136/29
     ingress_cidr: 172.29.1.137/32
     peers:
     - ip: 172.29.1.1
       scope: global
       asnumber: 65001
     # keep peer ip address
     # in case of only peer
     vrrp_ip: 172.29.1.1

sriovnets

sriovnets:
- physical: sriovnet1
  interface: ens6f0
  vlan_start: 100
  vlan_end: 4000
  whitelists:
    "0000:af:02.0": enp175s2
    "0000:af:02.1": enp175s2f1
    "0000:af:03.2": enp175s3f2

storage

storage:
  osds:
  - data: /dev/sdb
    journal: /path/to/journal-sdb
  - data: /dev/sdc
    journal: /path/to/journal-sdc
  osd_count: 2

genesis

genesis:
  name: csonjrsv30
  oob: 192.168.41.30
  host: 192.168.2.30
  storage: 172.31.1.30
  pxe: 172.30.1.30
  ksn: 172.29.1.30
  neutron: 10.0.101.30

masters

masters:
- name: csonjrsv31
- name: csonjrsv32

workers

workers:
- name: csonjrsv33
- name: csonjrsv34

servers

servers:
- name: csonjrsv31
  oob: 192.168.41.31
  host: 192.168.2.31
  storage: 172.31.1.31
  pxe: 172.30.1.31
  ksn: 172.29.1.31
  neutron: 10.0.101.31

hardware

hardware:
  vendor: HP
  generation: 10
  hw_version: 3
  bios_version: 2.8

disks

disks:
- name: sdj
  labels:
    bootdrive: true
  partitions:
  - name: root
    size: 20g
    mountpoint: /

genesis_ssh_public_key

genesis_ssh_public_key: "ssh-rsa ..."

kubernetes

kubernetes:
  api_service_ip: 10.96.0.1
  etcd_service_ip: 10.96.0.2
  pod_cidr: 10.99.0.0/16
  service_cidr: 10.96.0.0/15

regional_server

regional_server:
  ip: 135.16.101.85

Populating PostgreSQL

To deploy a Unicycle (Three-Node Cluster) or a Rover (Single-Node Cluster) Edge Node, perform the following steps:

• Check if the Akraino (Docker Containers) packages are stood up.
• Connect to PostgreSQL database providing the host IP (name).

user name = admin
password = abc123

• Locate the directory from which Postgres loads any required files:

> show data_directory

• Copy the configuration file to this directory on the appropriate Edge Node.
• Execute the following SQL insert, bearing in mind these value substitutions:
  • edge_site_id: Any unique increment value. This is usually 1 but does not have to be.
  • edge_site_name: Human-readable Edge Node name.
  • region_id: Edge Node region number. Use select * from akraino.Region; to determine the appropriate value. Observe the region number associations returned from the query: Use 1 for US East, 2 for US West, and so on.
  • edge_site_ip: IP address of the node where the deployment is done
  • edge_site_user:  User name of the node (for edge_site_ip)
  • edge_site_pwd: Password of the node (for edge_site_ip)

> insert into akraino.edge_site(edge_site_id, edge_site_name, edge_site_ip, edge_site_user, edge_site_pwd, input_file,
  crt_login_id, crt_dt, upd_login_id, upd_dt, region_id)
  values( 1, 'Atlanta', 'ip-address', 'user', '****', bytea(pg_read_file('input-file-name')), user, now(), user, now(),1);

Akraino Portal Operations

Portal Pre-configuration

• In the Tomcat (Portal) container, navigate to /usr/local/tomcat/webapps/AECPortalMgmt/App.Config.js

.constant('hostUrl','127.0.0.1:8080')
.constant('camundaUrl',’127.0.0.1:8073')

• In the Tomcat (Portal) container, navigate to /usr/local/tomcat/webapps/AECPortalMgmt/WEB-INF/classes/app.properties

apacheds.ldap.url = ldap://127.0.0.1:10389/dc=akraino,dc=com

postgres.db.url = jdbc:postgresql://127.0.0.1:6432/postgres

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.

Build or Deploy an Edge Node

From the Portal home page:

• Select one Edge Node.
• For the selected Edge Node, select a Blueprint (Rover or Unicycle) from the drop down menu.
• When using the Unicycle blueprint, the Build button is enabled.
  • Select Build to begin the build process.
  • The Build status is updated to Build Complete, once the process is finished.
  • Observe that the Deploy button is enabled.
  • Select Deploy to begin the deploy process.
  • The Deploy status is updated to Completed once the process is finished.
• When using the Rover blueprint, the Deploy button is enabled.
  • Select Deploy to begin the deploy process.

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 side menu in the portal.
• Select a deployed site in the Run Tests page.
• Click on Run Tempest to trigger tempest test
• 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

Configuration

This configuration file is written as a YAML dictionary named parameters.

This dictionary will be selectively inserted into the ONAP VM environment file, depending on overall configuration.

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

Installation

• Navigate to the add-ons page via the sidebar menu.
• Select a deployed site on the Install ONAP page.
• Choose Install ONAP to begin installation.
• The ONAP status changes to Complete once the job is finished.
• ONAP VM will be created successfully after the job is finished. It takes several hours until ONAP becomes operational.

Onboarding a Sample VNF

• Navigate to the Akraino Sites page.
• Select a deployed site. The VNF Onboard button becomes enabled.
• Choose VNF Onboard and supply the VNF Type.
• Choose Onboard to begin the sample VNF installation.