.. This work is licensed under a Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 .. (c) Ferenc Cserepkei, Brady Allen Johnson, Manuel Buil and others Abstract ======== This document provides information on how to install the OpenDayLigh SFC features in OPNFV with the use of os_odl-l2_sfc-(no)ha scenario. SFC feature desciription ======================== For details of the scenarios and their provided capabilities refer to the scenario description documents: - http://artifacts.opnfv.org/sfc/colorado/docs/scenarios_os-odl_l2-sfc-ha/index.html - http://artifacts.opnfv.org/sfc/colorado/docs/scenarios_os-odl_l2-sfc-noha/index.html The SFC feature enables creation of Service Fuction Chains - an ordered list of chained network funcions (e.g. firewalls, NAT, QoS) The SFC feature in OPNFV is implemented by 3 major components: - OpenDayLight SDN controller - Tacker: Generic VNF Manager (VNFM) and a NFV Orchestrator (NFVO) - OpenvSwitch: The Service Function Forwarder(s) Hardware requirements ===================== The SFC scenarios can be deployed on a bare-metal OPNFV cluster or on a virtual environment on a single host. Bare metal deployment on (OPNFV) Pharos lab ------------------------------------------- Hardware requirements for bare-metal deployments of the OPNFV infrastructure are given by the Pharos project. The Pharos project provides an OPNFV hardware specification for configuring your hardware: http://artifacts.opnfv.org/pharos/docs/pharos-spec.html Virtual deployment ------------------ To perform a virtual deployment of an OPNFV SFC scenario on a single host, that host has to meet the following hardware requirements: - SandyBridge compatible CPU with virtualization support - capable to host 5 virtual cores (5 physical ones at least) - 8-12 GBytes RAM for virtual hosts (controller, compute), 48GByte at least - 128 GiBiBytes room on disk for each virtual host (controller, compute) + 64GiBiBytes for fuel master, 576 GiBiBytes at least - Ubuntu Trusty Tahr - 14.04(.5) server operating system with at least ssh service selected at installation. - Internet Connection (preferably http proxyless) Pre-configuration activites - Preparing the host to install Fuel by script ========================================================================== .. Not all of these options are relevant for all scenario's. I advise following the .. instructions applicable to the deploy tool used in the scenario. Before starting the installation of the SFC scenarios some preparation of the machine that will host the Colorado Fuel cluster must be done. Installation of required packages --------------------------------- To be able to run the installation of the basic OPNFV fuel installation the Jumphost (or the host which serves the VMs for the virtual deployment) needs to install the following packages: :: sudo apt-get install -y git make curl libvirt-bin libpq-dev qemu-kvm \ qemu-system tightvncserver virt-manager sshpass \ fuseiso genisoimage blackbox xterm python-pip \ python-git python-dev python-oslo.config \ python-pip python-dev libffi-dev libxml2-dev \ libxslt1-dev libffi-dev libxml2-dev libxslt1-dev \ expect curl python-netaddr p7zip-full sudo pip install GitPython pyyaml netaddr paramiko lxml scp \ scp pycrypto ecdsa debtcollector netifaces enum During libvirt install the user is added to the libvirtd group, so you have to logout then login back again Download the installer source code and artifact ----------------------------------------------- To be able to install the scenario os_odl-l2_sfc-(no)ha one can follow the way CI is deploying the scenario. First of all the opnfv-fuel repository needs to be cloned: :: git clone -b 'stable/colorado' ssh://@gerrit.opnfv.org:29418/fuel This command copies the whole colorado branch of repository fuel. Now download the appropriate OPNFV Fuel ISO into an appropriate folder: :: wget http://artifacts.opnf