OPNFV(Colorado) Compass4nfv Installation Instructions

1. Abstract

This document describes how to install the Colorado release of OPNFV when using Compass4nfv as a deployment tool covering it’s limitations, dependencies and required system resources.

2. Version history

Date	Ver.	Author	Comment
2016-09-13	2.1.0	Yuenan Li (HUAWEI)	Adjusted the docs structure
2016-09-12	2.0.0	Yuenan Li (HUAWEI)	Rewritten for Compass4nfv C release
2016-01-17	1.0.0	Justin chi (HUAWEI)	Rewritten for Compass4nfv B release
2015-12-16	0.0.2	Matthew Li (HUAWEI)	Minor changes & formatting
2015-09-12	0.0.1	Chen Shuai (HUAWEI)	First draft

3. Compass4nfv configuration

This document describes providing guidelines on how to install and configure the Colorado release of OPNFV when using Compass as a deployment tool including required software and hardware configurations.

Installation and configuration of host OS, OpenStack, OpenDaylight, ONOS, Ceph etc. can be supported by Compass on Virtual nodes or Bare Metal nodes.

The audience of this document is assumed to have good knowledge in networking and Unix/Linux administration.

3.1. Preconditions

Before starting the installation of the Colorado release of OPNFV, some planning must be done.

3.1.1. Retrieving the installation ISO image

First of all, The installation ISO is needed for deploying your OPNFV environment, it included packages of Compass, OpenStack, OpenDaylight, ONOS and so on.

The stable release ISO can be retrieved via OPNFV software download page

The daily build ISO can be retrieved via OPNFV artifacts repository:

http://artifacts.opnfv.org/compass4nfv.html

NOTE: Search the keyword “compass4nfv/Colorado” to locate the ISO image.

E.g. compass4nfv/colorado/opnfv-2016-09-18_08-15-13.iso

The name of iso image includes the time of iso building, you can get the daily ISO according the building time. The git url and sha1 of Compass4nfv are recorded in properties files, According these, the corresponding deployment scripts can be retrieved.

3.1.2. Getting the deployment scripts

To retrieve the repository of Compass4nfv on Jumphost use the following command:

• git clone https://gerrit.opnfv.org/gerrit/compass4nfv

NOTE: PLEASE DO NOT GIT CLONE COMPASS4NFV IN ROOT DIRECTORY(INCLUDE SUBFOLDERS).

To get stable /colorado release, you can use the following command:

• git checkout colorado.1.0

3.2. Setup Requirements

If you have only 1 Bare Metal server, Virtual deployment is recommended. if more than or equal 3 servers, the Bare Metal deployment is recommended. The minimum number of servers for Bare metal deployment is 3, 1 for JumpServer(Jumphost), 1 for controller, 1 for compute.

3.2.1. Jumphost Requirements

The Jumphost requirements are outlined below:

1. Ubuntu 14.04 (Pre-installed).
2. Root access.
3. libvirt virtualization support.
4. Minimum 2 NICs.
   • PXE installation Network (Receiving PXE request from nodes and providing OS provisioning)
   • IPMI Network (Nodes power control and set boot PXE first via IPMI interface)
   • External Network (Optional: Internet access)
5. 16 GB of RAM for a Bare Metal deployment, 64 GB of RAM for a Virtual deployment.
6. CPU cores: 32, Memory: 64 GB, Hard Disk: 500 GB, (Virtual Deloment needs 1 TB Hard Disk)

3.3. Bare Metal Node Requirements

Bare Metal nodes require:

1. IPMI enabled on OOB interface for power control.
2. BIOS boot priority should be PXE first then local hard disk.
3. Minimum 3 NICs.
   • PXE installation Network (Broadcasting PXE request)
   • IPMI Network (Receiving IPMI command from Jumphost)
   • External Network (OpenStack mgmt/external/storage/tenant network)

3.4. Network Requirements

Network requirements include:

1. No DHCP or TFTP server running on networks used by OPNFV.
2. 2-6 separate networks with connectivity between Jumphost and nodes.
   • PXE installation Network
   • IPMI Network
   • Openstack mgmt Network*
   • Openstack external Network*
   • Openstack tenant Network*
   • Openstack storage Network*
3. Lights out OOB network access from Jumphost with IPMI node enabled (Bare Metal deployment only).
4. External network has Internet access, meaning a gateway and DNS availability.

The networks with(*) can be share one NIC(Default configuration) or use an exclusive NIC(Reconfigurated in network.yml).

3.5. Execution Requirements (Bare Metal Only)

In order to execute a deployment, one must gather the following information:

1. IPMI IP addresses of the nodes.
2. IPMI login information for the nodes (user/pass).
3. MAC address of Control Plane / Provisioning interfaces of the Bare Metal nodes.

4. Installation Guide (Bare Metal Deployment)

4.1. Nodes Configuration (Bare Metal Deployment)

The below file is the inventory template of deployment nodes:

“compass4nfv/deploy/conf/hardware_environment/huawei-pod1/dha.yml”

The “dha.yml” is a collectively name for “os-nosdn-nofeature-ha.yml os-ocl-nofeature-ha.yml os-odl_l2-moon-ha.yml etc”.

You can write your own IPMI IP/User/Password/Mac address/roles reference to it.

• name – Host name for deployment node after installation.
• ipmiVer – IPMI interface version for deployment node support. IPMI 1.0 or IPMI 2.0 is available.
• ipmiIP – IPMI IP address for deployment node. Make sure it can access from Jumphost.
• ipmiUser – IPMI Username for deployment node.
• ipmiPass – IPMI Password for deployment node.
• mac – MAC Address of deployment node PXE NIC .
• roles – Components deployed.

Set TYPE/FLAVOR and POWER TOOL

E.g. .. code-block:: yaml

TYPE: baremetal FLAVOR: cluster POWER_TOOL: ipmitool

Set ipmiUser/ipmiPass and ipmiVer

E.g.

ipmiUser: USER
ipmiPass: PASSWORD
ipmiVer: '2.0'

Assignment of different roles to servers

E.g. Openstack only deployment roles setting

hosts:
  - name: host1
    mac: 'F8:4A:BF:55:A2:8D'
    interfaces:
       - eth1: 'F8:4A:BF:55:A2:8E'
    ipmiIp: 172.16.130.26
    roles:
      - controller
      - ha

  - name: host2
    mac: 'D8:49:0B:DA:5A:B7'
    interfaces:
      - eth1: 'D8:49:0B:DA:5A:B8'
    ipmiIp: 172.16.130.27
    roles:
      - compute

NOTE: IF YOU SELECT MUTIPLE NODES AS CONTROLLER, THE ‘ha’ role MUST BE SELECT, TOO.

E.g. Openstack and ceph deployment roles setting

hosts:
  - name: host1
    mac: 'F8:4A:BF:55:A2:8D'
    interfaces:
       - eth1: 'F8:4A:BF:55:A2:8E'
    ipmiIp: 172.16.130.26
    roles:
      - controller
      - ha
      - ceph-adm
      - ceph-mon

  - name: host2
    mac: 'D8:49:0B:DA:5A:B7'
    interfaces:
      - eth1: 'D8:49:0B:DA:5A:B8'
    ipmiIp: 172.16.130.27
    roles:
      - compute
      - ceph-osd

E.g. Openstack and ODL deployment roles setting

hosts:
  - name: host1
    mac: 'F8:4A:BF:55:A2:8D'
    interfaces:
       - eth1: 'F8:4A:BF:55:A2:8E'
    ipmiIp: 172.16.130.26
    roles:
      - controller
      - ha
      - odl

  - name: host2
    mac: 'D8:49:0B:DA:5A:B7'
    interfaces:
      - eth1: 'D8:49:0B:DA:5A:B8'
    ipmiIp: 172.16.130.27
    roles:
      - compute

E.g. Openstack and ONOS deployment roles setting

hosts:
  - name: host1
    mac: 'F8:4A:BF:55:A2:8D'
    interfaces:
       - eth1: 'F8:4A:BF:55:A2:8E'
    ipmiIp: 172.16.130.26
    roles:
      - controller
      - ha
      - onos

  - name: host2
    mac: 'D8:49:0B:DA:5A:B7'
    interfaces:
      - eth1: 'D8:49:0B:DA:5A:B8'
    ipmiIp: 172.16.130.27
    roles:
      - compute

4.2. Network Configuration (Bare Metal Deployment)

Before deployment, there are some network configuration to be checked based on your network topology.Compass4nfv network default configuration file is “compass4nfv/deploy/conf/hardware_environment/huawei-pod1/network.yml”. You can write your own reference to it.

The following figure shows the default network configuration.

+--+                          +--+     +--+
|  |                          |  |     |  |
|  |      +------------+      |  |     |  |
|  +------+  Jumphost  +------+  |     |  |
|  |      +------+-----+      |  |     |  |
|  |             |            |  |     |  |
|  |             +------------+  +-----+  |
|  |                          |  |     |  |
|  |      +------------+      |  |     |  |
|  +------+    host1   +------+  |     |  |
|  |      +------+-----+      |  |     |  |
|  |             |            |  |     |  |
|  |             +------------+  +-----+  |
|  |                          |  |     |  |
|  |      +------------+      |  |     |  |
|  +------+    host2   +------+  |     |  |
|  |      +------+-----+      |  |     |  |
|  |             |            |  |     |  |
|  |             +------------+  +-----+  |
|  |                          |  |     |  |
|  |      +------------+      |  |     |  |
|  +------+    host3   +------+  |     |  |
|  |      +------+-----+      |  |     |  |
|  |             |            |  |     |  |
|  |             +------------+  +-----+  |
|  |                          |  |     |  |
|  |                          |  |     |  |
+-++                          ++-+     +-++
  ^                            ^         ^
  |                            |         |
  |                            |         |
+-+-------------------------+  |         |
|      External Network     |  |         |
+---------------------------+  |         |
       +-----------------------+---+     |
       |       IPMI Network        |     |
       +---------------------------+     |
               +-------------------------+-+
               | PXE(Installation) Network |
               +---------------------------+

4.3. Start Deployment (Bare Metal Deployment)

1. Edit deploy.sh

Set OS version and OpenStack version for deployment nodes.

Compass4nfv Colorado supports three OS version based openstack mitaka.

E.g.

######################### The environment for Openstack ######################
# Ubuntu16.04 Newton
#export OS_VERSION=xenial
#export OPENSTACK_VERSION=newton_xenial

# Ubuntu14.04 Mitaka
#export OS_VERSION=trusty
#export OPENSTACK_VERSION=mitaka

# Ubuntu16.04 Mitaka
#export OS_VERSION=xenial
#export OPENSTACK_VERSION=mitaka_xenial

# Centos7 Mitaka
#export OS_VERSION=centos7
#export OPENSTACK_VERSION=mitaka

# Redhat7 OSP9
#export OS_VERSION=redhat7
#export OPENSTACK_VERSION=osp9

Set ISO image that you want to deploy

E.g.

# ISO_URL is your iso's absolute path
export ISO_URL=file:///home/compass/compass4nfv.iso
# or
# export ISO_URL=http://artifacts.opnfv.org/compass4nfv/colorado/opnfv-colorado.1.0.iso

Set Jumphost PXE NIC. (set eth1 E.g.)

E.g.

########## Hardware Deploy Jumphost PXE NIC ##########
# you need comment out it when virtual deploy
export INSTALL_NIC=eth1

Set scenario that you want to deploy

E.g.

nosdn-nofeature scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/hardware_environment/huawei-pod1/os-nosdn-nofeature-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network.yml

ocl-nofeature scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/hardware_environment/huawei-pod1/os-ocl-nofeature-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network_ocl.yml

odl_l2-moon scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/hardware_environment/huawei-pod1/os-odl_l2-moon-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network.yml

odl_l2-nofeature scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/hardware_environment/huawei-pod1/os-odl_l2-nofeature-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network.yml

odl_l3-nofeature scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/hardware_environment/huawei-pod1/os-odl_l3-nofeature-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network.yml

onos-nofeature scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/hardware_environment/huawei-pod1/os-onos-nofeature-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network_onos.yml

onos-sfc deploy scenario sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/hardware_environment/huawei-pod1/os-onos-sfc-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network_onos.yml

2. Run deploy.sh

./deploy.sh

5. Installation Guide (Virtual Deployment)

5.1. Nodes Configuration (Virtual Deployment)

The below file is the inventory template of deployment nodes:

”./deploy/conf/vm_environment/huawei-virtual1/dha.yml”

The “dha.yml” is a collectively name for “os-nosdn-nofeature-ha.yml os-ocl-nofeature-ha.yml os-odl_l2-moon-ha.yml etc”.

You can write your own address/roles reference to it.

• name – Host name for deployment node after installation.
• roles – Components deployed.

Set TYPE and FLAVOR

E.g.

TYPE: virtual
FLAVOR: cluster

Assignment of different roles to servers

E.g. Openstack only deployment roles setting

hosts:
  - name: host1
    roles:
      - controller
      - ha

  - name: host2
    roles:
      - compute

NOTE: IF YOU SELECT MUTIPLE NODES AS CONTROLLER, THE ‘ha’ role MUST BE SELECT, TOO.

E.g. Openstack and ceph deployment roles setting

hosts:
  - name: host1
    roles:
      - controller
      - ha
      - ceph-adm
      - ceph-mon

  - name: host2
    roles:
      - compute
      - ceph-osd

E.g. Openstack and ODL deployment roles setting

hosts:
  - name: host1
    roles:
      - controller
      - ha
      - odl

  - name: host2
    roles:
      - compute

E.g. Openstack and ONOS deployment roles setting

hosts:
  - name: host1
    roles:
      - controller
      - ha
      - onos

  - name: host2
    roles:
      - compute

5.2. Network Configuration (Virtual Deployment)

Before deployment, there are some network configuration to be checked based on your network topology.Compass4nfv network default configuration file is “compass4nfv/deploy/conf/vm_environment/huawei-virtual1/network.yml”. You can write your own reference to it.

The following figure shows the default network configuration.

+--+                          +--+
|  |                          |  |
|  |      +------------+      |  |
|  +------+  Jumphost  +------+  |
|  |      +------+-----+      |  |
|  |             |            |  |
|  |             +------------+  |
|  |                          |  |
|  |      +------------+      |  |
|  +------+    host1   +------+  |
|  |      +------+-----+      |  |
|  |             |            |  |
|  |             +------------+  |
|  |                          |  |
|  |      +------------+      |  |
|  +------+    host2   +------+  |
|  |      +------+-----+      |  |
|  |             |            |  |
|  |             +------------+  |
|  |                          |  |
|  |      +------------+      |  |
|  +------+    host3   +------+  |
|  |      +------+-----+      |  |
|  |             |            |  |
|  |             +------------+  |
|  |                          |  |
|  |                          |  |
+-++                          ++-+
  ^                            ^
  |                            |
  |                            |
+-+-------------------------+  |
|      External Network     |  |
+---------------------------+  |
       +-----------------------+---+
       |    Installation Network   |
       +---------------------------+

5.3. Start Deployment (Virtual Deployment)

1. Edit deploy.sh

Set OS version and OpenStack version for deployment nodes.

Compass4nfv Colorado supports three OS version based openstack mitaka.

E.g.

######################### The environment for Openstack ######################
# Ubuntu16.04 Newton
#export OS_VERSION=xenial
#export OPENSTACK_VERSION=newton_xenial

# Ubuntu14.04 Mitaka
#export OS_VERSION=trusty
#export OPENSTACK_VERSION=mitaka

# Ubuntu16.04 Mitaka
#export OS_VERSION=xenial
#export OPENSTACK_VERSION=mitaka_xenial

# Centos7 Mitaka
#export OS_VERSION=centos7
#export OPENSTACK_VERSION=mitaka

# Redhat7 OSP9
#export OS_VERSION=redhat7
#export OPENSTACK_VERSION=osp9

Set ISO image that you want to deploy

E.g.

# ISO_URL is your iso's absolute path
# export ISO_URL=file:///home/compass/compass4nfv.iso
# or
# export ISO_URL=http://artifacts.opnfv.org/compass4nfv/colorado/opnfv-colorado.1.0.iso

Set scenario that you want to deploy

E.g.

nosdn-nofeature scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/vm_environment/os-nosdn-nofeature-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network.yml

ocl-nofeature scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/vm_environment/os-ocl-nofeature-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network_ocl.yml

odl_l2-moon scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/vm_environment/os-odl_l2-moon-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network.yml

odl_l2-nofeature scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/vm_environment/os-odl_l2-nofeature-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network.yml

odl_l3-nofeature scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/vm_environment/os-odl_l3-nofeature-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network.yml

onos-nofeature scenario deploy sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/vm_environment/os-onos-nofeature-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network_onos.yml

onos-sfc deploy scenario sample

# DHA is your dha.yml's path
export DHA=./deploy/conf/vm_environment/os-onos-sfc-ha.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network_onos.yml

2. Run deploy.sh

./deploy.sh

6. Offline Deploy

Compass4nfv uses offline approuch to deploy cluster and support complete offline deployment on a jumphost without access internet. Here is the offline deployment instuction:

6.1. Preparation for offline deploy

1. Download compass.iso from OPNFV artifacts repository (Search compass4nfv in http://artifacts.opnfv.org/ and download an appropriate ISO. ISO can also be generated by script build.sh in compass4nfv root directory.)
2. Download the Jumphost preparation package from our httpserver. (Download the jumphost environment package from here. It should be awared that currently we only support ubuntu trusty as offline jumphost OS.)
3. Clone the compass4nfv code repository.

6.2. Steps of offline deploy

1. Copy the compass.iso, jh_env_package.tar.gz and the compass4nfv code repository to your jumphost.
2. Export the local path of the compass.iso and jh_env_package.tar.gz on jumphost. Then you can perform deployment on a offline jumphost.

E.g.

Export the compass4nfv.iso and jh_env_package.tar.gz path

# ISO_URL and JHPKG_URL should be absolute path
export ISO_URL=file:///home/compass/compass4nfv.iso
export JHPKG_URL=file:///home/compass/jh_env_package.tar.gz

Run deploy.sh

./deploy.sh

7. Expansion Guide

7.1. Bare Metal Expansion

7.1.1. Edit NETWORK File

The below file is the inventory template of deployment nodes:

”./deploy/conf/hardware_environment/huawei-pod1/network.yml”

You can edit the network.yml which you had edited before the first deployment.

NOTE: External subnet’s ip_range should be changed as the first 6 IPs are already taken by the first deployment.

7.1.2. Edit DHA File

The below file is the inventory template of deployment nodes:

”./deploy/conf/hardware_environment/expansion-sample/hardware_cluster_expansion.yml”

You can write your own IPMI IP/User/Password/Mac address/roles reference to it.

• name – Host name for deployment node after installation.
• ipmiIP – IPMI IP address for deployment node. Make sure it can access from Jumphost.
• ipmiUser – IPMI Username for deployment node.
• ipmiPass – IPMI Password for deployment node.
• mac – MAC Address of deployment node PXE NIC .

Set TYPE/FLAVOR and POWER TOOL

E.g. .. code-block:: yaml

TYPE: baremetal FLAVOR: cluster POWER_TOOL: ipmitool

Set ipmiUser/ipmiPass and ipmiVer

E.g.

ipmiUser: USER
ipmiPass: PASSWORD
ipmiVer: '2.0'

Assignment of roles to servers

E.g. Only increase one compute node

hosts:
   - name: host6
     mac: 'E8:4D:D0:BA:60:45'
     interfaces:
        - eth1: '08:4D:D0:BA:60:44'
     ipmiIp: 172.16.131.23
     roles:
       - compute

E.g. Increase two compute nodes

hosts:
   - name: host6
     mac: 'E8:4D:D0:BA:60:45'
     interfaces:
        - eth1: '08:4D:D0:BA:60:44'
     ipmiIp: 172.16.131.23
     roles:
       - compute

   - name: host6
     mac: 'E8:4D:D0:BA:60:78'
     interfaces:
        - eth1: '08:4D:56:BA:60:83'
     ipmiIp: 172.16.131.23
     roles:
       - compute

7.1.3. Start Expansion

1. Edit deploy.sh

Set the EXPANSION to true.

E.g.

######################### Deploy or Expansion ###############################
# Modify network.yml and virtual_cluster_expansion.yml or
# hardware_cluster_expansion.yml.
# Edit the DHA and NETWORK envionment variables.
# External subnet's ip_range and management ip should be changed as the
# first 6 IPs are already taken by the first deployment.
# VIRT_NUMBER decide how many virtual machines needs to expand when virtual expansion

export EXPANSION="true"
export MANAGEMENT_IP_START="10.1.0.55"
#export VIRT_NUMBER=1
export DEPLOY_FIRST_TIME="false"

Set OS version and OpenStack version for deployment nodes.

E.g.

######################### The environment for Openstack ######################
# Ubuntu16.04 Newton
#export OS_VERSION=xenial
#export OPENSTACK_VERSION=newton_xenial

# Ubuntu14.04 Mitaka
#export OS_VERSION=trusty
#export OPENSTACK_VERSION=mitaka

# Ubuntu16.04 Mitaka
#export OS_VERSION=xenial
#export OPENSTACK_VERSION=mitaka_xenial

# Centos7 Mitaka
#export OS_VERSION=centos7
#export OPENSTACK_VERSION=mitaka

# Redhat7 OSP9
#export OS_VERSION=redhat7
#export OPENSTACK_VERSION=osp9

NOTE: The OS version and OpenStack version should be same as the first deployment.

Set ISO image that you want to deploy

E.g.

# ISO_URL is your iso's absolute path
export ISO_URL=file:///home/compass/compass4nfv.iso
# or
# export ISO_URL=http://artifacts.opnfv.org/compass4nfv/colorado/opnfv-colorado.1.0.iso

NOTE: The ISO should be same as the first deployment.

Set scenario that you want to expansion

E.g.

# DHA is your dha.yml's path
export DHA=./deploy/conf/hardware_environment/expansion-sample/hardware_cluster_expansion.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network.yml

Set jumpserver PXE NIC

E.g.

INSTALL_NIC=${INSTALL_NIC:-eth1}

Check the environment variable.

2. Run deploy.sh

./deploy.sh

7.2. Virtual Expansion

7.2.1. Edit NETWORK File

The below file is the inventory template of deployment nodes:

”./deploy/conf/vm_environment/huawei-virtual1/network.yml”

You can edit the network.yml which you had edited before the first deployment.

NOTE: External subnet’s ip_range should be changed as the first 6 IPs are already taken by the first deployment.

7.2.2. Edit DHA File

The below file is the inventory template of deployment nodes:

”./deploy/conf/vm_environment/virtual_cluster_expansion.yml”

Set TYPE and FLAVOR

E.g.

TYPE: virtual
FLAVOR: cluster

Assignment of roles to servers

E.g. Only increase one compute node

hosts:
  - name: host6
    roles:
      - compute

E.g. Increase two compute nodes

hosts:
  - name: host6
    roles:
      - compute

  - name: host7
    roles:
      - compute

7.2.3. Start Expansion

1. Edit add.sh

Set the EXPANSION to true.

E.g.

######################### Deploy or Expansion ###############################
# Modify network.yml and virtual_cluster_expansion.yml or
# hardware_cluster_expansion.yml.
# Edit the DHA and NETWORK envionment variables.
# External subnet's ip_range and management ip should be changed as the
# first 6 IPs are already taken by the first deployment.
# VIRT_NUMBER decide how many virtual machines needs to expand when virtual expansion

export EXPANSION="true"
export MANAGEMENT_IP_START="10.1.0.55"
export VIRT_NUMBER=1
export DEPLOY_FIRST_TIME="false"

Set OS version and OpenStack version for deployment nodes.

E.g.

######################### The environment for Openstack ######################
# Ubuntu16.04 Newton
#export OS_VERSION=xenial
#export OPENSTACK_VERSION=newton_xenial

# Ubuntu14.04 Mitaka
#export OS_VERSION=trusty
#export OPENSTACK_VERSION=mitaka

# Ubuntu16.04 Mitaka
#export OS_VERSION=xenial
#export OPENSTACK_VERSION=mitaka_xenial

# Centos7 Mitaka
#export OS_VERSION=centos7
#export OPENSTACK_VERSION=mitaka

# Redhat7 OSP9
#export OS_VERSION=redhat7
#export OPENSTACK_VERSION=osp9

NOTE: The OS version and OpenStack version should be same as the first deployment.

Set ISO image that you want to deploy

E.g.

# ISO_URL is your iso's absolute path
export ISO_URL=file:///home/compass/compass4nfv.iso
# or
# export ISO_URL=http://artifacts.opnfv.org/compass4nfv/colorado/opnfv-colorado.1.0.iso

NOTE: The OS version and OpenStack version should be same as the first deployment.

Set scenario that you want to expansion

E.g.

# DHA is your dha.yml's path
export DHA=./deploy/conf/vm_environment/virtual_cluster_expansion.yml

# NETWORK is your network.yml's path
export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network.yml

Check the environment variable.

2. Run deploy.sh

./deploy.sh

8. References

8.1. OPNFV

OPNFV Home Page

OPNFV Genesis project page

OPNFV Compass4nfv project page

OPNFV Compass4nfv release notes

8.2. OpenStack

OpenStack Mitaka Release artifacts

OpenStack documentation

8.3. OpenDaylight

OpenDaylight artifacts

8.4. ONOS

ONOS artifacts

8.5. Compass

Compass Home Page