The 6WIND virtual accelerator Pluginfor Fuel Documentation

Release 1.0-1.0.3-1

6WIND SA

June 03, 2016

CONTENTS

1 Introduction 11.1 Key terms, acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4 Supported platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.5 Licensing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Installation Guide 42.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.3 Installing 6WIND virtual accelerator Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.4 Configuring 6WIND virtual accelerator Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 User Guide 93.1 Configuring 6WIND virtual accelerator parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.2 Use updated libvirt and qemu packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.3 Sanity checks after deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4 Known issues 12

5 Appendix 13

i

CHAPTER

ONE

INTRODUCTION

This document contains instructions for installing and configuring 6WIND virtual accelerator plugin for Fuel.

1.1 Key terms, acronyms and abbreviations

6WIND virtual acceleratorVA 6WIND Virtual AcceleratorMOS Mirantis Openstack

1.2 Overview

Virtual Accelerator is a product of the 6WIND speed series that provides packet processing acceleration for virtualnetwork infrastructures.

Virtual Accelerator runs inside the hypervisor and removes the performance bottlenecks by offloading virtual switchingfrom the networking stack. The cpu resources necessary for packet processing are drastically reduced, so that less coresare required to process network traffic at higher rates and Linux stability is increased.

In addition to simple virtual switching (using OVS or the Linux bridge), Virtual Accelerator supports an extensive setof networking protocols to provide a complete virtual networking infrastructure.

Virtual Accelerator is fully integrated with Linux and its environment, so that existing Linux applications do not needto be modified to benefit from packet processing acceleration.

Virtual Accelerator is available for Intel x86-based servers and supports major Linux distributions.

Virtual Accelerator is provided in three flavors according to the required feature set:

• baseline: simple virtual switching and ip forwarding

• L3: baseline + advanced L3 features such as vrf, filtering and nat

• ipsec: L3 + ipsec features

1.3 Features

High performance I/Os leveraging dpdk, with multi-vendor nic support from Intel, Mellanox and Emulex

• Intel 10G/40G XL710

• Intel 10G 82598, 82599, X540

1

The 6WIND virtual accelerator Plugin for Fuel Documentation, Release 1.0-1.0.3-1

• Mellanox 10G/40G ConnectX®-3 EN and ConnectX®-3 Pro EN series

• Mellanox 10G/25G/50G/100G ConnectX®-4 EN and ConnectX®-4 Lx EN series

• Emulex 10G/40G OneConnect® OCe14000 family

• Intel 1G 82575, 82576, 82580, I210, I211, I350, I354

High performance virtual switching

• OVS acceleration

• Linux Bridge

High performance virtual networking

In addition to virtual switching, Virtual Accelerator supports a complete set of networking protocols, based on the6WIND Gate technology, that can be used to design innovative virtual networking infrastructures.

• Virtual Accelerator baseline

– Forwarding (ipv4 and ipv6)

– vxlan

– vlan

– gre

– Linux bridge filtering

• Virtual Accelerator L3

– vrf

– Filtering (ipv4 and ipv6)

– nat

– Tunneling (IPinIP)

• Virtual Accelerator ipsec

– Intel Multi-Buffer and QuickAssist crypto

– ipsec (ipv4 and ipv6)

– ike (v1 and v2)

Support of standard Virtio drivers

Virtual Accelerator comes with a high performance Virtio back-end driver for communication with any guest runningVirtio front-end drivers (can be based on dpdk, Linux, or other OSes).

Seamless integration with management and orchestration tools

Virtual Accelerator is fully integrated with Linux and its environment, so that existing Linux applications do not needto be modified to benefit from packet processing acceleration. Standard Linux APIs are preserved, including iproute2,iptables, brctl, ovs-ofctl, ovs-vsctl, etc.

1.3. Features 2

The 6WIND virtual accelerator Plugin for Fuel Documentation, Release 1.0-1.0.3-1

Virtual Accelerator is also validated with the Mirantis Openstack cloud operating system:

• Supports Mirantis Openstack 7.0

1.4 Supported platforms

Virtual Accelerator is provided as a set of binary packages and is validated on the following distributions:

• ubuntu-14.04

• redhat-7

• centos-7

See also:

Refer to the Virtual Accelerator Release Notes for detailed information about the latest validated versions of the Linuxdistributions.

1.5 Licensing information

6WIND virtual accelerator Commercial

1.4. Supported platforms 3

CHAPTER

TWO

INSTALLATION GUIDE

2.1 Prerequisites

This guide assumes that you have installed Fuel and all the nodes of your future environment are discovered andfunctional. Note, the 6WIND virtual accelerator Fuel plugin will download virtual accelerator packages from a remoterepository. Make sure that nodes can correctly reach Internet.

To correctly deploy the 6WIND virtual accelerator Fuel plugin you will need a credentials package (in base64 format).

If you have already purchased 6WIND software you should have this package, otherwise contact 6WIND supportteam. On the other hand, if you just want to evaluate the 6WIND virtual accelerator you still need to contact 6WIND.

2.2 Requirements

This plugin is intended to be installed on nodes running Fuel 7.0 (version 7.0.0) Verify this typing the followingcommand:

fuel --version

In order to correctly install the 6WIND virtual accelerator plugin on Fuel compute(s) the following requirements aremandatory:

1. Use KVM as hypervisor virtualization driver

2. Deploy on compute node(s) with at least 4GB of RAM and 2 cpus

3. Internet connectivity on Master node (since the plugin will download software from 6WIND remote repositories)

4. A dedicated link for Neutron networking tunnels between Compute and Network

This version of plugin supports only VLAN as networking tunneling option. It is mandatory to use a dedicated physicalnetwork interface for your tunnel instead of the default Fuel setup that puts this interface on the same used for pxe andmanagement. Support for VxLAN and for bridged VLAN will be available in future releases.

The 6WIND virtual accelerator needs qemu and libvirt supporting vhostuser and multiqueue features to correclty runits fast packet processing stack. In particular on the compute nodes the following packages are needed:

1. libvirt-bin (1.3.1-1ubuntu6)

2. qemu (2.5+dfsg-5ubuntu6)

Note that Mirantis official repositories do not provide these packages. For this reason the default behavior for the pluginis to retrieve the 6WIND libvirt and qemu packages and replace the Mirantis ones in the early stages of deployment.

4

The 6WIND virtual accelerator Plugin for Fuel Documentation, Release 1.0-1.0.3-1

2.3 Installing 6WIND virtual accelerator Plugin

1. Download 6WIND virtual accelerator plugin from the Fuel Plugins Catalog.

2. Copy the downloaded rpm to the Fuel Master node:

scp 6wind-virtual-accelerator-1.0-1.0.3-1.noarch.rpm <Fuel Master node ip>:/tmp/

3. Log into the Fuel Master node and install the plugin

ssh <the Fuel Master node ip>fuel plugins --install /tmp/6wind-virtual-accelerator-1.0-1.0.3-1.noarch.rpm

4. Now verify that the plugin is correctly installed

fuel plugins3 | 6wind-virtual-accelerator | 1.0.3 | 3.0.0

2.4 Configuring 6WIND virtual accelerator Plugin

1. First you have to create environment in Fuel Web UI.

2. Please select KVM hypervisor type for your environment.

2.3. Installing 6WIND virtual accelerator Plugin 5

The 6WIND virtual accelerator Plugin for Fuel Documentation, Release 1.0-1.0.3-1

3. Please select Neutron networking. The 6WIND virtual accelerator supports only VLAN segmentation.

4. Activate the plugin in the Fuel Web UI Settings tab

5. Configure fields with correct values:

• Provide base64 credentials package you received from 6WIND support team

• Refer to next chapter for detailed field description and configuration. In particular if you have a licensefile you should upload it at this time in the Advanced Paramaters menu.

6. Add nodes and assign them the following roles:

• At least 1 Controller

• At least one node with both Compute and 6WIND Virtual Accelerator roles. Make sure that the chosennode has at least 2 cpus and 4 GB of RAM

2.4. Configuring 6WIND virtual accelerator Plugin 6

The 6WIND virtual accelerator Plugin for Fuel Documentation, Release 1.0-1.0.3-1

7. Configure nodes to use a dedicated link for Neutron networking.

• Select the Compute and 6WIND Virtual Accelerator node and configure its interfaces.

• Drag the Private interface to the dedicated NIC used to connect to Controller.

2.4. Configuring 6WIND virtual accelerator Plugin 7

The 6WIND virtual accelerator Plugin for Fuel Documentation, Release 1.0-1.0.3-1

• Perform these two steps for the Controller node too and choose the NIC accordingly.

8. Verify nodes network connectivity (in the Fuel Web UI Network tab)

9. Press Deploy changes to deploy the environment.

2.4. Configuring 6WIND virtual accelerator Plugin 8

CHAPTER

THREE

USER GUIDE

This section provides a deeper explanation of plugin parameters and a description of required steps to verify thateverything is working fine after deployment.

Note that this User Guide provides information on 6WIND virtual accelerator plugin for Fuel (and not on the 6WINDvirtual accelerator software itself). Contact 6WIND to obtain more details on how to retrieve the virtual acceleratorsoftware and its documentation.

When configuring the 6WIND virtual accelerator Fuel plugin, you have to provide credentials for virtual acceleratorsoftware download. The plugin will then install and run the virtual accelerator using its default configuration values.

3.1 Configuring 6WIND virtual accelerator parameters

The 6WIND virtual accelerator plugin makes possible to modify these default configuration parameters before deploy-ment. In order to do this you need to activate the Advanced parameters checkbox in the 6WIND Virtual Acceleratorfuel plugin section in the Web UI Settings tab.

At this point some additional fields will show up and you will be able to edit with your desired values. Please contact6WIND support team or refer to 6WIND virtual accelerator documentation for more information on the meaning ofthese fields.

9

The 6WIND virtual accelerator Plugin for Fuel Documentation, Release 1.0-1.0.3-1

If you already have a virtual accelerator configuration file, you can upload it to the nodes having the 6WIND VirtualAccelerator role enabled. Note, this file will replace the default virtual accelerator configuration file and overload allthe defined configuration paramaters.

It is strongly recommended to provide a license file if you have one. Without license the plugin will still correcltyinstall the 6wind virtual accelerator but it will run in evaluation mode (48 hours). At the end of the evaluation periodyou will experience significant performance degradation and loss of connectivity for your instances since there will benomore any hugepages backing.

3.2 Use updated libvirt and qemu packages

As briefly described in the installation section, in order to correctly spawn virtual machines using the acceleratednetwork stack 6WIND virtual accelerator provides, the compute nodes need to run recent versions of libvirt and qemupackages.

By default the 6WIND virtual accelerator Fuel plugin retrieves and installs its updated libvirt and qemu packagesfrom a remote repository maintained by 6WIND. It is possible to force the plugin to keep the default libvirt and qemupackages provided by the Linux distribution.

To do this simply unselect the Use updated external packages checkbox. Note, default libvirt and qemu packageson MOS 7.0 do not have all the features required for proper 6WIND virtual accelerator integration. Thus we stronglyadvise to keep the Use updated external packages enabled.

3.3 Sanity checks after deployment

The installation section of this document described how to correctly start a Fuel deployment using the 6WIND virtualaccelerator plugin. At the end of this process the 6WIND virtual accelerator and its dependent components should beall up and running.

As first step make sure that the system uses the proper libvirt and qemu versions.

1. Check libvirt version (should be 1.3.1-1ubuntu6)

aptitude show libvirt-bin | grep Version

2. Check qemu version (should be 2.5+dfsg-5ubuntu6)

aptitude show qemu-system-x86 | grep Version

The next step is checking that the 6WIND virtual accelerator software and its Openstack extensions have been correctlyinstalled.

1. Check 6WIND virtual accelerator package status (should be State: installed)

aptitude show virtual-accelerator | grep State

2. Check 6WIND openstack extensions package status (should be State: installed)

aptitude show 6wind-openstack-extension | grep State

If this check is successful, verify that that ALL the following services are correctly running (each of them should bestart/running):

service virtual-accelerator statusservice openvswitch-switch statusservice neutron-plugin-openvswitch-agent status

3.2. Use updated libvirt and qemu packages 10

The 6WIND virtual accelerator Plugin for Fuel Documentation, Release 1.0-1.0.3-1

service libvirtd statusservice nova-compute status

If some of the services are not properly running, please restart ALL of them in the same order used before for theirstatus check. Otherwise if everything is active you should be able to correctly spawn virtual machines. To do thatplease refer to 6WIND Openstack extensions official documentation.

3.3. Sanity checks after deployment 11

CHAPTER

FOUR

KNOWN ISSUES

The current implementation of the 6WIND virtual accelerator plugin uses a credentials package in base64 format for6WIND software download. This behavior should be replaced using a regular credentials package instead of its base64encoding. Unfortunately a bug in Fuel 7.0 does not make possible to correctly retrieve this package from the uploadutility. https://bugs.launchpad.net/fuel/+bug/1545795

12

CHAPTER

FIVE

APPENDIX

1. 6WIND virtual accelerator overview

13