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”

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

  • 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 .
  • name – Host name for deployment node after installation.
  • roles – Components deployed.

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

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/network_cfg.yaml”. 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. Set PXE/Installation NIC for Jumphost. (set eth1 E.g.)
export INSTALL_NIC=eth1

2.Set OS version and OpenStack version for deployment nodes.

Compass4nfv Colorado supports three OS version based openstack mitaka.

Ubuntu 14.04 mitaka:

export OS_VERSION=trusty
export OPENSTACK_VERSION=mitaka

Ubuntu 16.04 mitaka:

export OS_VERSION=xenial
export OPENSTACK_VERSION=mitaka_xenial

Centos 7 mitaka:

export OS_VERSION=centos7
export OPENSTACK_VERSION=mitaka
  1. Set ISO image that you want to deploy
export ISO_URL=file:///${YOUR_OWN}/compass.iso
or
export ISO_URL=http://artifacts.opnfv.org/compass4nfv/colorado/opnfv-colorado.1.0.iso
  1. Run deploy.sh with inventory and network configuration
./deploy.sh --dha ${YOUR_OWN}/dha.yml --network ${YOUR_OWN}/network.yml

E.g.

  1. nosdn-nofeature scenario deploy sample
./deploy.sh \
    --dha ./deploy/conf/hardware_environment/huawei-pod1/os-nosdn-nofeature-ha.yml \
    --network ./deploy/conf/hardware_environment/huawei-pod1/network.yml
  1. ocl-nofeature scenario deploy sample
./deploy.sh \
    --dha ./deploy/conf/hardware_environment/huawei-pod1/os-ocl-nofeature-ha.yml \
    --network ./deploy/conf/hardware_environment/huawei-pod1/network_ocl.yml
  1. odl_l2-moon scenario deploy sample
   ./deploy.sh \
       --dha ./deploy/conf/hardware_environment/huawei-pod1/os-odl_l2-moon-ha.yml \
       --network ./deploy/conf/hardware_environment/huawei-pod1/network.yml

4. odl_l2-nofeature scenario deploy template
./deploy.sh \
    --dha ./deploy/conf/hardware_environment/huawei-pod1/os-odl_l2-nofeature-ha.yml \
    --network ./deploy/conf/hardware_environment/huawei-pod1/network.yml
  1. odl_l3-nofeature scenario deploy sample
./deploy.sh \
    --dha ./deploy/conf/hardware_environment/huawei-pod1/os-odl_l3-nofeature-ha.yml \
    --network ./deploy/conf/hardware_environment/huawei-pod1/network.yml
  1. onos-nofeature scenario deploy sample
./deploy.sh \
    --dha ./deploy/conf/hardware_environment/huawei-pod1/os-onos-nofeature-ha.yml \
    --network ./deploy/conf/hardware_environment/huawei-pod1/network_onos.yml
  1. onos-sfc deploy scenario sample
./deploy.sh \
    --dha ./deploy/conf/hardware_environment/huawei-pod1/os-onos-sfc-ha.yml \
    --network ./deploy/conf/hardware_environment/huawei-pod1/network_onos.yml