Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Rover (Single-Node Cluster)

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

Contents

Table of Contents
excludeContents

...

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.

Key Name(s)

Notes

Example

BUILD_INTERFACE

Restricts DHCP to only bind to this interface (not required)
BUILD_INTERFACE=vlan41

BUILD_WEBIP BUILD_WEBPORT

IP and port to use when creating the web server
BUILD_WEBIP=192.168.2.44
BUILD_WEBPORT=8090

SRV_NAME

Server hostname
SRV_NAME=aknode42

SRV_OOB_IP SRV_OOB_USR SRV_OOB_PWD

Out-of-band interface information for the server (iDRAC, ilo, etc.)
SRV_OOB_IP=192.168.41.42
SRV_OOB_USR=root
SRV_OOB_PWD=XXXXXXXX

SRV_MAC

MAC address of the server used during the build
SRV_MAC=3c:fd:fe:b8:02:90

SRV_OEM

Server OEM: Dell or HPE (case sensitive)
SRV_OEM=Dell

SRV_IPXE_INF SRV_BLD_INF SRV_BOOT_DEVICE

Network interface used during the build when ipxe.efi and the OS are booted
SRV_IPXE_INF=net4
SRV_BLD_INF=enp94s0f0
SRV_BOOT_DEVICE=sdg

SRV_BLD_SCRIPT

ipxe script based on the OS version and target kernel. Valid values are script-hwe-16.04.4-amd64.ipxe or script-16.04.4-amd64.ipxe

SRV_BLD_SCRIPT=script-hwe-16.04.4-amd64.ipxe

SRV_BIOS_TEMPLATE SRV_BOOT_TEMPLATE SRV_HTTP_BOOT_DEV

XML template used to set BIOS and RAID configuration.
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

VLAN to use during the build and final network configuration
SRV_VLAN=41

SRV_MTU SRV_IP SRV_SUBNET SRV_NETMASK SRV_GATEWAY SRV_DNS SRV_DOMAIN SRV_DNSSEARCH SRV_NTP

Basic network information for DHCP configuration and final server network settings
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

Root password for the server being built
SRV_PWD=XXXXXXXX

SRV_BOND SRV_SLAVE1 SRV_SLAVE2

Network bond information
SRV_BOND=bond0
SRV_SLAVE1=enp94s0f0
SRV_SLAVE2=enp94s0f1

Unicycle (Three-Node Cluster) 

...

Key Name

Notes

Example

site_name
Site Name
site_name: hp_akraino
ipmi_admin_password
The Password required to allow the bare metal server to instantiate via IPMI
ipmi_admin_password: XXXXXXXX
networks

There are six networks:

  • oob
  • host
  • storage
  • pxe
  • ksn
  • neutron
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

NOTE: osd_count must redundantly match the number of osds entries.

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

The genesis or “seed" node refers to a short-lived node used to launch a new deployment. It is he first node built in a new deployment environment.

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

The nodes that make up the control plane

masters:
- name: csonjrsv31
- name: csonjrsv32
workers

The nodes that make up the data plane

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:

...

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

Key Name
Notes
Example
public_net_nameThe name assigned to the OpenStack network that will be created and used by the ONAP VM. An existing network may be used by referencing its name here.
public_net_name: public
public_physical_net_provider_nameThe physical provider network name for the public network. CAUTION: If the physical provider network cannot be found, the automated deployment process will terminate with an error.
  # Assume vlan50 is the VLAN created 
# for the OpenStack Project (tenant)
public_physical_net_provider_name: vlan50
provider_segmentation_idThe VLAN tag of the physical provider network
  # Assume vlan50
provider_segmentation_id: 50
public_physical_net_typeThe physical network type. Specify VLAN or flat. NOTE:When flat is in use, provider_segmentation_id will be ignored. 
  public_physical_net_type: vlan
public_subnet_nameThe subnet name. An existing subnet may be used by referencing its name here.
  public_subnet_name: public-subnet
public_subnet_cidrThe subnet’s CIDR. The ONAP VM will be assigned an IP within this subnet. 
  public_subnet_cidr: 192.168.102.0/24
public_subnet_allocation_startThe allocation start of the IP pool. Together with public_subnet_allocation_end it defines the range of IPs assigned to VMs.
  public_subnet_allocation_start: 192.168.102.100
public_subnet_allocation_endThe allocation end of the IP pool. Together with public_subnet_allocation_start it defines the range of IPs assigned to VMs.
  public_subnet_allocation_end: 192.168.102.200
public_subnet_dns_nameserverThe subnet's DNS server
  public_subnet_dns_nameserver: 8.8.8.8
public_subnet_gateway_ipThe subnet's Gateway IP
  public_subnet_gateway_ip: 192.168.102.1
flavor_nameVM flavor for the ONAP VM. The installation creates m1.onap, x1.onap, xx1.onap flavors, all of which are recommended for use.
  flavor_name: x1.onap
onap_vm_public_keyThe public key used to access the ONAP VM. A URL pointing to the key may be used here.
  onap_vm_public_key: PUBLIC_KEY
http_proxyOptional http proxy URL including port. If the network is accessible without a proxy, please leave empty.
  http_proxy: http://proxy.yourdomain.com:8888
https_proxyOptional https proxy URL including the port. If the network is accessible without a proxy, please leave empty.
  https_proxy: https://proxy.yourdomain.com:8888
no_proxyOptional list of domains, IPs, and CIDRs that do not require a proxy, separated by commas. Do not use spaces. If the network is accessible without a proxy, please leave empty.
  no_proxy: 127.0.0.1
keystone_admin_passwordThe keystone admin password. 
  keystone_admin_password: XXXXXXXX
onap_tenant_passwordThe keystone password for the ONAP project (formerly known as a tenant in OpenStack parlance). 
  onap_tenant_password: XXXXXXXX
onap_artifacts_http_repoOptional HTTP repository URL for ONAP artifacts. When deploying a self-contained Edge Node without Internet access, all ONAP artifacts must be downloaded from ONAP Nexus to a HTTP server, using this URL. If HTTP is not being used to download artifacts, please leave empty.
  onap_artifacts_http_repo: http://192.168.102.220/onap

...