SDNVPN Colorado documentation

This document will give the user instructions on how to deploy the SDN VPN scenarios verfied for the Colorado release of the OPNFV platform, using the Fuel installer.

A sister document covers installation using the APEX installer.

Introduction

This document provides guidelines on how to install and configure the os-odl_l2_bgpvpn_ha and os-odl_l2_bgpvpn_ha scenarios of OPNFV including required software and hardware configurations.

Description of bgpvpn scenarios Internal transport tunnel mesh Install Neutron BGPVPN additions (networking-bgpvpn) Neutron odl additions (networking-odl) install and configure Quagga (incl. config on ODL side) configure OVS to connect to ODL and set up the right bridges (network architecture) set up iptables to allow connections between OVS and ODL set up HA proxy so that ODL can be reached

Hardware requirements

Bare metal deployment on Pharos Lab

Hardware requirements for bare-metal deployments of the OPNFV infrastucture are specified by the Pharos project. The Pharos project provides an OPNFV hardware specification for configuring your hardware at: http://artifacts.opnfv.org/pharos/docs/pharos-spec.html.

Virtual deployment hardware requirements

To perform a virtual deployment of an OPNFV scenario on a single host, that host has to meet the hardware requirements outlined in the <missing spec>.

Preparing your host to install Fuel by script

Before starting the installation of the <scenario> scenario some preparation of the machine that will host the Fuel VM must be done.

Setting up the host

Installation of required packages

Fuel server installation and scenario deployment

This section describes the installation of the OPNFV installation server (jumphost) as well as the deployment of the os-odl_l2-bgpvpn-ha or os-odl_l2-bgpvpn-noha OPNFV reference platform stack across a server cluster.

Preparation

clone fuel repo download opnfv iso create dea.yaml and dha.yaml based on existing examples from FUel repo

Installation procedures

We describe several alternative procedures in the following.

Full automatic jumphost installation and deployment

call deploy.sh with scenario string

Automatic Fuel server installation and manual scenario deployment

call deploy.sh with -e option to only install FUel server i.e. no platform deployment Log into Fuel web GUI and configure scenario options, including activation of SDN VPN feature PXE boot compute nodes from Fuel server Trigger deployment through web GUI

Update Fuel server settings without re-installation

In case of having to change the jumphost settings without having the reinstall the whole jumphost, it is possible to call deploy-sh with the -f option, which will only update the settings without reinstalling the host, saving a lot of time.

Indices