.. This work is licensed under a Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 .. (c) Open Platform for NFV Project, Inc. and its contributors ======== Abstract ======== This document describes how to install the Fraser release of OPNFV when using Fuel as a deployment tool, covering its usage, limitations, dependencies and required system resources. This is an unified documentation for both x86_64 and aarch64 architectures. All information is common for both architectures except when explicitly stated. ============ Introduction ============ This document provides guidelines on how to install and configure the Fraser release of OPNFV when using Fuel as a deployment tool, including required software and hardware configurations. Although the available installation options provide a high degree of freedom in how the system is set up, including architecture, services and features, etc., said permutations may not provide an OPNFV compliant reference architecture. This document provides a step-by-step guide that results in an OPNFV Fraser compliant deployment. The audience of this document is assumed to have good knowledge of networking and Unix/Linux administration. ======= Preface ======= Before starting the installation of the Fraser release of OPNFV, using Fuel as a deployment tool, some planning must be done. Preparations ============ Prior to installation, 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) #. How many nodes and what roles you want to deploy (Controllers, Storage, Computes) #. Monitoring options you want to deploy (Ceilometer, Syslog, etc.). #. Other options not covered in the document are available in the links above This information will be needed for the configuration procedures provided in this document. ========================================= Hardware Requirements for Virtual Deploys ========================================= The following minimum hardware requirements must be met for the virtual installation of Fraser using Fuel: +----------------------------+--------------------------------------------------------+ | **HW Aspect** | **Requirement** | | | | +============================+========================================================+ | **1 Jumpserver** | A physical node (also called Foundation Node) that | | | will host a Salt Master VM and each of the VM nodes in | | | the virtual deploy | +----------------------------+--------------------------------------------------------+ | **CPU** | Minimum 1 socket with Virtualization support | +----------------------------+--------------------------------------------------------+ | **RAM** | Minimum 32GB/server (Depending on VNF work load) | +----------------------------+--------------------------------------------------------+ | **Disk** | Minimum 100GB (SSD or SCSI (15krpm) highly recommended)| +----------------------------+--------------------------------------------------------+ =========================================== Hardware Requirements for Baremetal Deploys =========================================== The following minimum hardware requirements must be met for the baremetal installation of Fraser using Fuel: +-------------------------+------------------------------------------------------+ | **HW Aspect** | **Requirement** | | | | +=========================+======================================================+ | **# of nodes** | Minimum 5 | | | | | | - 3 KVM servers which will run all the controller | | | services | | | | | | - 2 Compute nodes | | | | +-------------------------+------------------------------------------------------+ | **CPU** | Minimum 1 socket with Virtualization support | +-------------------------+------------------------------------------------------+ | **RAM** | Minimum 16GB/server (Depending on VNF work load) | +-------------------------+------------------------------------------------------+ | **Disk** | Minimum 256GB 10kRPM spinning disks | +-------------------------+------------------------------------------------------+ | **Networks** | 4 VLANs (PUBLIC, MGMT, STORAGE, PRIVATE) - can be | | | a mix of tagged/native | | | | | | 1 Un-Tagged VLAN for PXE Boot - ADMIN Network | | | | | | Note: These can be allocated to a single NIC - | | | or spread out over multiple NICs | +-------------------------+------------------------------------------------------+ | **1 Jumpserver** | A physical node (also called Foundation Node) that | | | hosts the Salt Master and MaaS VMs | +-------------------------+------------
.. This work is licensed under a Creative Commons Attribution 4.0 International
.. License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) OPNFV, Huawei Technologies Co.,Ltd and others.
*************************************
Yardstick Test Case Description TC075
*************************************
+-----------------------------------------------------------------------------+
|Network Capacity and Scale Testing |
| |
+--------------+--------------------------------------------------------------+
|test case id | OPNFV_YARDSTICK_TC075_Network_Capacity_and_Scale_testing |
| | |
+--------------+--------------------------------------------------------------+
|metric | Number of connections, Number of frames sent/received |
| | |
+--------------+--------------------------------------------------------------+
|test purpose | To evaluate the network capacity and scale with regards to |
| | connections and frmaes. |
| | |
+--------------+--------------------------------------------------------------+
|configuration | file: opnfv_yardstick_tc075.yaml |
| | |
| | There is no additional configuration to be set for this TC. |
| | |
+--------------+--------------------------------------------------------------+
|test tool | netstar |
| | |
| | Netstat is normally part of any Linux distribution, hence it |
| | doesn't need to be installed. |
| | |
+--------------+--------------------------------------------------------------+
|references | Netstat man page |
| | |
| | ETSI-NFV-TST001 |
| | |
+--------------+--------------------------------------------------------------+
|applicability | This test case is mainly for evaluating network performance. |
| | |
+--------------+--------------------------------------------------------------+
|pre_test | Each pod node must have netstat included in it. |
|conditions | |
| | |
+--------------+--------------------------------------------------------------+
|test sequence | description and expected result |
| | |
+--------------+--------------------------------------------------------------+
|step 1 | The pod is available. |
| | Netstat is invoked and logs are produced and stored. |
| | |
| | Result: Logs are stored. |
| | |
+--------------+--------------------------------------------------------------+
|test verdict | None. Number of connections and frames are fetched and |
| | stored. |
| | |
+--------------+--------------------------------------------------------------+