.. This document is protected/licensed under the following conditions
.. (c) Jonas Bjurel (Ericsson AB)
.. Licensed under a Creative Commons Attribution 4.0 International License.
.. You should have received a copy of the license along with this work.
.. If not, see .
Fuel configuration
==================
This section provides guidelines on how to install and
configure the Brahmaputra release of OPNFV when using Fuel as a
deployment tool including required software and hardware
configurations.
For detailed instructions on how to install the Brahmaputra release using
Fuel, see *Reference 13* in section *"Fuel associated references"* below.
Pre-configuration activities
----------------------------
Planning the deployment
Before starting the installation of the Brahmaputra release of
OPNFV when using Fuel as a deployment tool, some planning must be
done.
Familiarize yourself with the Fuel by reading the
following documents:
- Fuel planning guide, please see *Reference: 8* in section *"Fuel associated references"* below.
- Fuel quick start guide, please see *Reference: 9* in section *"Fuel associated references"* below.
- Fuel operations guide, please see *Reference: 10* in section *"Fuel associated references"* below.
- Fuel Plugin Developers Guide, please see *Reference: 11* in section *"Fuel associated references"* below.
Before the installation can start, a number of deployment specific parameters must be collected, those are:
#. Provider sub-net and gateway information
#. Provider VLAN information
#. Provider DNS addresses
#. Provider NTP addresses
#. Network overlay you plan to deploy (VLAN, VXLAN, FLAT)
#. Monitoring Options you want to deploy (Ceilometer, Syslog, etc.)
#. How many nodes and what roles you want to deploy (Controllers, Storage, Computes)
#. Other options not covered in the document are available in the links above
Retrieving the ISO image
^^^^^^^^^^^^^^^^^^^^^^^^
First of all, the Fuel deployment ISO image needs to be retrieved, the
Fuel .iso image of the Brahmaputra release can be found at *Reference: 2*
Alternatively, you may build the .iso from source by cloning the
opnfv/fuel git repository. Detailed instructions on how to build
a Fuel OPNFV .iso can be found in *Reference: 14* at section *"Fuel associated references"* below.
Hardware requirements
---------------------
Following high level hardware requirements must be met:
+--------------------+------------------------------------------------------+
| **HW Aspect** | **Requirement** |
| | |
+====================+======================================================+
| **# of nodes** | Minimum 5 (3 for non redundant deployment): |
| | |
| | - 1 Fuel deployment master (may be virtualized) |
| | |
| | - 3(1) Controllers (1 colocated mongo/ceilometer |
| | role, 2 Ceph-OSD roles) |
| | |
| | - 1 Compute (1 co-located Ceph-OSD role) |
| | |
+--------------------+------------------------------------------------------+
| **CPU** | Minimum 1 socket x86_AMD64 with Virtualization |
| | support |
+--------------------+------------------------------------------------------+
| **RAM** | Minimum 16GB/server (Depending on VNF work load) |
| | |
+--------------------+------------------------------------------------------+
| **Disk** | Minimum 256GB 10kRPM spinning disks |
| | |
+--------------------+------------------------------------------------------+
| **Networks** | 4 Tagged VLANs (PUBLIC, MGMT, STORAGE, PRIVATE) |
| | |
| | 1 Un-Tagged VLAN for PXE Boot - ADMIN Network |
| | |
| | note: These can be run on single NIC - or spread out |
| | over other nics as your hardware supports |
+--------------------+------------------------------------------------------+
For information on compatible hardware types available for use, please see
*Reference: 11* in section *"Fuel associated references"* below.
Top of the rack (TOR) Configuration requirements
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The switching infrastructure provides connectivity for the OPNFV
infrastructure operations, tenant networks (East/West) and provider
connectivity (North/South); it also provides needed
connectivity for the Storage Area Network (SAN). To avoid traffic
congestion, it is strongly suggested that three physically separated
networks are used, that is: 1 physical network for administration and
control, one physical network for tenant private and public networks,
and one physical network for SAN. The switching connectivity can (but
does not need to) be fully redundant, in such case it and comprises a
redundant 10GE switch pair for each of the three physically separated
networks.
The physical TOR switches are **not** automatically configured from
the OPNFV reference platform. All the networks involved in the OPNFV
infrastructure as well as the provider networks and the private tenant
VLANs needs to be manually configured.
Jumphost configuration
----------------------
The Jumphost server, also known as the "Fuel master" provides needed
services/functions to deploy an OPNFV/OpenStack cluster as well functions
for cluster life-cycle management (extensions, repair actions and upgrades).
The Jumphost server requires 2 (4 if redundancy is required) Ethernet
interfaces - one for external management of the OPNFV installation,
and another for jump-host communication with the OPNFV cluster.
Install the Fuel jump-host
^^^^^^^^^^^^^^^^^^^^^^^^^^
Mount the Fuel Brahmaputra ISO file as a boot device to the jump host
server, reboot it, and install the Fuel Jumphost in accordance with installation instructions, see *Reference 13* in section *"Fuel associated references"*
below.
Platform components configuration
---------------------------------
Fuel-Plugins
^^^^^^^^^^^^
Fuel plugins enable you to install and configure additional capabilities for
your Fuel OPNFV based cloud, such as additional storage types, networking
functionality, or NFV features developed by OPNFV.
Fuel offers an open source framework for creating these plugins, so there’s
a wide range of capabilities that you can enable Fuel to add to your OpenStack
clouds.
The OPNFV Brahmaputra version of Fuel provides a set of pre-packaged plugins
developed by OPNFV:
+--------------------+------------------------------------------------------+
| **Plugin name** | **Short description** |
| | |
+====================+======================================================+
| OpenDaylight | OpenDaylight provides an open-source SDN Controller |
| | providing networking features such as L2 and L3 |
| | network control, "Service Function Chaining", |
| | routing, networking policies, etc. |
| | More information on OpenDaylight in the OPNFV |
| | Brahmaputra release can be found in a separate |
| | section in this document. |
+--------------------+------------------------------------------------------+
| ONOS | ONOS is another open-source SDN controller which |
| | in essense fill the same role as OpenDaylight. |
| | More information on ONOS in the OPNFV |
| | Brahmaputra release can be found in a separate |
| | section in this document. |
| | |
+--------------------+------------------------------------------------------+
| BGP-VPN | BGP-VPN provides an BGP/MPLS VPN service |
| | More information on BGP-VPN in the OPNFV |
| | Brahmaputra release can be found in a separate |
| | section in this document. |
| | |
+--------------------+------------------------------------------------------+
| OVS-NSH | OVS-NSH provides a variant of Open-vSwitch |
| | which supports "Network Service Headers" needed |
| | for the "Service function chaining" feature |
| | More information on "Service Function Chaining" |
| | in the OPNFV Brahmaputra release can be found in a |
| | in a separate section in this document. |
| | |
+--------------------+------------------------------------------------------+
| OVS-NFV | OVS-NFV provides a variant of Open-vSwitch |
| | with carrier grade characteristics essential for |
| | NFV workloads. |
| |