This document describes how to install OpenStack plug-ins for interoperability with OpenStack cloud platforms. Then SeerEngine-DC can process requests from the OpenStack cloud platforms.

OpenStack plug-ins include SeerEngine-DC Neutron plug-ins, Nova patch, openvswitch-agent patch, and DHCP failover components.

SeerEngine-DC Neutron plug-ins

Neutron is a type of OpenStack services used to manage all virtual networking infrastructures (VNIs) in an OpenStack environment. It provides virtual network services to the devices managed by OpenStack computing services.

SeerEngine-DC Neutron plug-ins are developed for SeerEngine-DC based on the OpenStack framework.

The SeerEngine-DC Neutron plug-ins allow deployment of the network configuration obtained from OpenStack through REST APIs on SeerEngine-DC, including tenants' networks, subnets, routers, and ports.

CAUTION:

To avoid service interruptions, do not modify the settings issued by the cloud platform on the controller, such as the virtual link layer network, vRouter, and vSubnet settings after the plug-ins connect to the OpenStack cloud platform.

SeerEngine-DC Neutron security plug-ins

The SeerEngine-DC Neutron security plug-ins are designed for SeerEngine-DC and meet the OpenStack requirements. They implement all features of security plugins (such as Fwaas, Lbaas, and Vpnaas). They can synchronize the security configurations obtained from OpenStack to SeerEngine-DC through REST API, which allows tenants to schedule security network resources. The synchronized security configurations include tenants' firewalls (FW), load balancers (LB), and VPNs.

Preparing for installation

Hardware requirements

Table 1 shows the hardware requirements for installing the SeerEngine-DC Neutron plug-ins on a server or virtual machine.

Table 1 Hardware requirements

CPU	Memory size	Disk space
Single-core and multicore CPUs	2 GB and above	5 GB and above

Software requirements

Table 2 shows the software requirements for installing the SeerEngine-DC Neutron plug-ins.

Table 2 Software requirements

Item	Supported versions
OpenStack deployed by using Kolla-Ansible	· OpenStack Ocata · OpenStack Pike · OpenStack Queens · OpenStack Rocky · OpenStack Stein · OpenStack Train · OpenStack Ussuri · OpenStack Victoria · OpenStack Wallaby · OpenStack Xena

Item

Supported versions

OpenStack deployed by using Kolla-Ansible

· OpenStack Ocata

· OpenStack Pike

· OpenStack Queens

· OpenStack Rocky

· OpenStack Stein

· OpenStack Train

· OpenStack Ussuri

· OpenStack Victoria

· OpenStack Wallaby

· OpenStack Xena

IMPORTANT:

Before you install the OpenStack plug-ins, make sure the following requirements are met:

· Your system has a reliable Internet connection.

· OpenStack has been deployed correctly. Verify that the /etc/hosts file on all nodes has the host name-IP address mappings, and the OpenStack Neutron extension services (Neutron-FWaas, Neutron-VPNaas, or Neutron-LBaas) have been deployed. For the deployment procedure, see the installation guide for the specific OpenStack version on the OpenStack official website.

NOTE:

· The SeerEngine-DC Neutron security plug-in cannot be installed on OpenStack Stein, Train, Victoria, Wallaby, or Xena.

· For the installation of converged version of SeerEngine_DC plug-ins (SeerEngine_DC_PLUGIN-version-py2.7.egg), see H3C SeerEngine-DC OpenStack Converged Plug-Ins Installation Guide.

Deploying OpenStack

Before installing the plug-ins, deploy OpenStack by using Kolla Ansible first. For the OpenStack deployment procedure, see the installation guide for the specific OpenStack version on the OpenStack official website.

Preprovisioning basic SeerEngine-DC settings

This procedure preprovisions only basic SeerEngine-DC settings. For the configuration in a specific scenario, see the SeerEngine-DC configuration guide for that scenario.

Table 3 Preprovisioning basic SeerEngine-DC settings

Item	Configuration directory
Fabrics	Automation > Data Center Networks > Fabrics > Fabrics
VDS	Automation > Data Center Networks > Common Network Settings > Virtual Distributed Switch
IP address pool	Automation > Data Center Networks > Resource Pools > IP Address Pools
VNID pools (VLANs, VXLANs, and VLAN-VXLAN mappings)	Automation > Data Center Networks > Resource Pools > VNID Pools > VLANs Automation > Data Center Networks > Resource Pools > VNID Pools > VXLANs [Automation > Data Center Networks > Resource Pools > VNID Pools > VLAN-VXLAN Mappings
Add access devices and border devices to a fabric	Automation > Data Center Networks > Fabrics > Fabrics
L4-L7 device, physical resource pool, and template	Automation > Data Center Networks > Resource Pools > Devices > Physical Devices Automation > Data Center Networks > Resource Pools > Devices > L4-L7 Physical Resource Pools
Border gateway	Automation > Data Center Networks > Common Network Settings > Gateways
Domains and hosts	Automation > Data Center Networks > Fabrics > Domains Automation > Data Center Networks > Fabrics > Domains > Hosts
Interoperability with OpenStack	Automation > Virtual Networking > OpenStack NOTE: · You must specify the cloud platform name. The name is case sensitive and must be the same as the value for the cloud_region_name parameter in the ml2_conf.ini file of the Neutron plug-in. · Make the VNI range is the same as the VXLAN VNI range on the cloud platform.

Installing OpenStack plug-ins by using Kolla Ansible

The SeerEngine-DC Neutron plug-ins can be installed on different OpenStack versions. The installation package varies by OpenStack version. However, you can use the same procedure to install the Neutron plug-ins on different OpenStack versions. This document uses OpenStack Ocata as an example.

The SeerEngine-DC Neutron plug-ins are installed on the OpenStack control node.

Setting up the basic environment

Before installing SeerEngine-DC Neutron plug-ins on the OpenStack control node, set up the basic environment on the node.

To set up the basic environment:

1. Update the software source list, and then download and install the Python tools.

¡ CentOS 8 operating system:

[root@localhost ~]# yum clean all

[root@localhost ~]# yum makecache

[root@localhost ~]# yum install –y python3-pip python3-setuptools

¡ Other CentOS operating systems:

[root@localhost ~]# yum clean all

[root@localhost ~]# yum makecache

[root@localhost ~]# yum install –y python-pip python-setuptools

2. Install runlike.

¡ CentOS 8 operating system:

[root@localhost ~]# pip3 install runlike

¡ Other CentOS operating systems:

[root@localhost ~]# pip install runlike

3. Log in to the controller node and edit the /etc/hosts file. Add the following information to the file.

¡ IP and name mappings of all hosts in this OpenStack environment. To obtain this information, access the controller and select Automation > Data Center Networks > Fabrics > Domains > Hosts.

¡ IP and name mappings of all leaf, spine, and border devices in this scenario. To obtain this information, access the controller and select Automation > Data Center Networks > Resource Pools > Devices > Physical Devices.

[root@localhost ~]# vim /etc/hosts

127.0.0.1 localhost

::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

99.0.83.75 controller

99.0.83.76 compute1

99.0.83.77 compute2

99.0.83.78 nfs-server

99.0.83.79 compute3

99.0.83.74 compute4

Installing the SeerEngine-DC Neutron plug-ins

Obtaining the SeerEngine-DC Neutron plug-in installation package

The SeerEngine-DC Neutron plug-ins are included in the SeerEngine-DC OpenStack package. Obtain the SeerEngine-DC OpenStack package of the required version and then save the package to the target installation directory on the server or virtual machine.

Alternatively, transfer the installation package to the target installation directory through a file transfer protocol such as FTP, TFTP, or SCP. Use the binary transfer mode to prevent the software package from being corrupted during transit.

Installing the SeerEngine-DC Neutron plug-ins on the OpenStack control node

1. Generate the startup script for the neutron-server container.

[root@localhost ~]# runlike neutron_server>docker-neutron-server.sh

2. Modify the neutron.conf configuration file.

a. Use the vi editor to open the neutron.conf configuration file.

[root@localhost ~]# vi /etc/kolla/neutron-server/neutron.conf

b. Configure the neutron.conf configuration file based on the operating system running in the Kolla environment.

- If a CentOS operating system runs in the Kolla environment, see H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for CentOS to configure the neutron.conf configuration file.

- If a Ubuntu operating system runs in the Kolla environment, see H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for Ubuntu to configure the neutron.conf configuration file.

3. Modify the ml2_conf.ini configuration file.

a. Use the vi editor to open the ml2_conf.ini configuration file.

[root@localhost ~]# vi /etc/kolla/neutron-server/ml2_conf.ini

b. Press I to switch to insert mode, and set the parameters in the ml2_conf.ini configuration file. For information about the parameters, see "ml2_conf.ini."

[ml2]

type_drivers = vxlan,vlan

tenant_network_types = vxlan,vlan

mechanism_drivers = ml2_h3c

extension_drivers = ml2_extension_h3c,qos

[ml2_type_vlan]

network_vlan_ranges = physicnet1:1000:2999,port_security

[ml2_type_vxlan]

vni_ranges = 1:500

c. Press Esc to quit insert mode, and enter :wq to exit the vi editor and save the ml2_conf.ini file.

4. Add plug-ins configuration items to the ml2_conf.ini configuration file.

a. Use the vi editor to open the ml2_conf.in configuration file.

[root@localhost ~]# vi /etc/kolla/neutron-server/ml2_conf.ini

b. Configure the ml2_conf.ini file based on the operating system running in the Kolla environment.

- If a CentOS operating system runs in the Kolla environment, see H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for CentOS to configure the [SDNCONTROLLER] configuration group items for the ml2_conf.ini file.

- If a Ubuntu operating system runs in the Kolla environment, see H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for Ubuntu to configure the [SDNCONTROLLER] configuration group items for the ml2_conf.ini file.

5. Copy the plug-ins installation package to the neutron_server container.

¡ .egg file

[root@localhost ~]# docker cp SeerEngine_DC_PLUGIN-E3608-py2.7.egg neutron_server:/

¡ .whl file

[root@localhost ~]# docker cp SeerEngine_DC_PLUGIN-E6311-py3-none-any.whl neutron_server:/

IMPORTANT:

· The SeerEngine_DC_PLUGIN-version-py3.6.egg file will not be provided in E6311 or later.

· The SeerEngine_DC_PLUGIN-version-py3-none-any.whl file will be provided only in E6311 and later.

6. Access the file folder on the neutron_server container where the plug-ins installation package resides and install the plug-in package and websocket-client.

[root@localhost ~]# docker exec -it -u root neutron_server bash

¡ To install the plug-ins installation package:

- .egg file

Before installing the plug-in, verify that easy_install is installed in the same directory as neutron in the virtual environment of the container. If they are not in the same directory, see the instructions in "I find that easy_install is not in the same path as neutron when I am to install the Neutron plug-in on open-source OpenStack Wallaby and Xena with Kolla. What should I do?."

To obtain the neutron path:

(neutron-server) [root@localhost ~]# python3

>>> import neutron

>>> neutron.__path__

['/var/lib/kolla/venv/lib/python3.6/site-packages/neutron']

To obtain the easy_install installation path:

(neutron-server)[ root@localhost ~]# easy_install --version

setuptools 50.3.2 from /usr/lib/python3.6/site-packages (Python 3.6)

(neutron-server) [root@localhost ~]# easy_install SeerEngine_DC_PLUGIN-E3608-py2.7.egg

(neutron-server) [root@localhost ~]# h3c-sdnplugin controller install

- .whl file

(neutron-server) [root@localhost ~]# pip3 install SeerEngine_DC_PLUGIN-E6311-py3-none-any.whl

(neutron-server) [root@localhost ~]# h3c-sdnplugin controller install

IMPORTANT:

· The SeerEngine_DC_PLUGIN-version-py3.6.egg file will not be provided in E6311 or later.

· The SeerEngine_DC_PLUGIN-version-py3-none-any.whl file will be provided only in E6311 and later.

¡ To install websocket-client:

- CentOS 8:

(neutron-server) [root@localhost ~]# yum install –y python3-websocket-client

- Other CentOS versions:

(neutron-server) [root@localhost ~]# yum install –y python-websocket-client

(neutron-server) [root@localhost ~]# easy_install SeerEngine_DC_PLUGIN-E3608-py2.7.egg

(neutron-server) [root@localhost ~]# h3c-sdnplugin controller install

After installation of websocket-client, verify that WebSocket is installed in the same directory as neutron. websocket-client is usable only when they are in the same path. If they are not in the same path, see the instructions in "I find that python3-websocket-client is not in the same path as neutron when I am to install the Neutron plug-in on open-source OpenStack Wallaby and Xena with Kolla. What should I do?"

IMPORTANT:

· Make sure the version of python-websocket-client is 0.56.

· Before executing the h3c-sdnplugin controller install command, make sure no neutron.conf file exists in the /root directory. If such a file exists, delete it or move it to another location.

NOTE:

An error might be reported when the h3c-sdnplugin controller install command is executed. Just ignore it.

7. Create neutron-server container images.

[root@localhost ~]# neutron_server_image=$(docker ps --format {{.Image}} --filter name=neutron_server)

[root@localhost ~]# docker ps | grep $neutron_server_image

16d60524b8b3 kolla/centos-source-neutron-server:rocky "dumb-init --single-? 16 months ago Up 2 weeks neutron_server

[root@localhost ~]# docker commit 16d60524b8b3 kolla/neutron-server-h3c (replace 16d60524b8b3 with the UUID obtained in the preceding command)

[root@localhost ~]# docker rm -f neutron_server

[root@localhost ~]# docker tag $neutron_server_image kolla/neutron-server-origin

[root@localhost ~]# docker rmi $neutron_server_image

[root@localhost ~]# docker tag kolla/neutron-server-h3c $neutron_server_image

[root@localhost ~]# docker rmi kolla/neutron-server-h3c

8. Start the neutron-server container.

[root@localhost ~]# source docker-neutron-server.sh

9. View the startup status of the containers. If their status is Up, they have been started up correctly.

[root@localhost ~]# docker ps --filter "name=neutron_server"

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

289e4e132a9b kolla/centos-source-neutron-server:ocata "dumb-init --single-? 1 minutes ago Up 1 minutes neutron_server

Parameters and fields

This section describes parameters in configuration files and fields included in parameters.

ml2_conf.ini

Parameter	Required value	Description
type_drivers	vxlan,vlan	Driver type. vxlan must be specified as the first driver type.
tenant_network_types	vxlan,vlan	Type of the networks to which the tenants belong. For intranet, only vxlan is available. For extranet, only vlan is available. · In the host overlay scenario and network overlay with hierarchical port binding scenario, vxlan must be specified as the first network type. · In the network overlay without hierarchical port binding scenario, vlan must be specified as the first network type. · In the host overlay, network overlay with hierarchical port binding, and network overlay without hierarchical port binding hybrid scenario, vxlan must be specified as the first network type. In this scenario, you can create a VLAN only from the background CLI, REST API, or Web administration interface.
mechanism_drivers	ml2_h3c	Name of the ml2 driver. To create SR-IOV instances for VLAN networks, set this parameter to sriovnicswitch, ml2_h3c. To create hierarchy-supported instances, set this parameter to ml2_h3c,openvswitch.
extension_drivers	ml2_extension_h3c,qos	Names of the ml2 extension drivers. Available names include ml2_extension_h3c, qos, and port_security. If the QoS feature is not enabled on OpenStack, you do not need to specify the value qos for this parameter. To not enable port security on OpenStack, you do not need to specify the port_security value for this parameter (OpenStack Ocata 2017.1 does not support the port_security value.)
network_vlan_ranges	N/A	Value range for the VLAN ID of the extranet, for example, physicnet1:1000:2999.
vni_ranges	N/A	Value range for the VXLAN ID of the intranet, for example, 1:500.

Upgrading the SeerEngine-DC Neutron plug-ins

CAUTION:

· Services might be interrupted during the SeerEngine-DC Neutron plug-ins upgrade procedure. Make sure you understand the impact of the upgrade before performing it on a live network.

· The plug-ins settings will not be restored automatically after an upgrade in the Kolla environment. Before an upgrade, back up the settings in the /etc/kolla/neutron-server/neutron.conf and /etc/kolla/neutron-server/ml2_conf.ini configuration files. After the upgrade, modify the parameter settings according to the configuration files to ensure configuration consistency before and after the upgrade.

Upgrade with the neutron_server container removed

1. Remove the container installed with the old version of the plug-ins and the container image.

neutron_server_image=$(docker ps --format {{.Image}} --filter name=neutron_server)

a. If no docker-neutron-server.sh scrip file exists, execute the following command. If such a file exists, skip this step.

[root@controller ~]# runlike neutron_server>docker-neutron-server.sh

b. Remove the container installed with the old version of the plug-ins and the container image.

[root@controller ~]# docker rm -f neutron_server

[root@controller ~]# docker rmi $neutron_server_image

c. Restore the default container and image in the Kolla environment.

[root@localhost ~]# docker tag kolla/neutron-server-origin $neutron_server_image

[root@localhost ~]# docker rmi kolla/neutron-server-origin

[root@controller ~]# source docker-neutron-server.sh

IMPORTANT:

Before restarting the neutron_server container, you must restore the configurations in the neutron.conf and neutron.conf files and remove the plug-ins-related configuration.

2. Install the new version of plug-ins. For the installation procedure, see "Installing the SeerEngine-DC Neutron plug-ins".

Upgrade with the neutron_server container retained

To upgrade the plug-ins with the neutron_server container retained, you are required to remove the old version of the plug-ins and then install the view version of the plug-ins on the neutron_server container.

To upgrade the neutron_server container:

1. Access the neutron_server container and remove the old version of the plug-ins.

[root@localhost ~]# docker exec -it -u root neutron_server bash

(neutron-server) [root@localhost ~]# h3c-sdnplugin controller uninstall

Remove service

Removed symlink /etc/systemd/system/multi-user.target.wants/h3c-agent.service.

Restore config files

Uninstallation complete.

(neutron-server) [root@localhost ~]# pip uninstall seerengine-dc-plugin

Uninstalling SeerEngine-DC-PLUGIN-E3608:

/usr/bin/h3c-agent

/usr/bin/h3c-sdnplugin

……

2. Install the new version of the plug-ins.

¡ .egg file

[root@localhost ~]# docker cp SeerEngine-DC-PLUGIN-E3608-py2.7.egg neutron_server:/

[root@localhost ~]# docker exec -it -u root neutron_server bash

(neutron-server) [root@localhost ~]# easy_install SeerEngine-DC-PLUGIN-E3608-py2.7.egg

(neutron-server) [root@localhost ~]# h3c-sdnplugin controller install

¡ .whl file

[root@localhost ~]# docker cp SeerEngine_DC_PLUGIN-E6311-py3-none-any.whl neutron_server:/

[root@localhost ~]# docker exec -it -u root neutron_server bash

(neutron-server) [root@localhost ~]# pip3 install SeerEngine_DC_PLUGIN-E6401-py3-none-any.whl

(neutron-server) [root@localhost ~]# h3c-sdnplugin controller install

IMPORTANT:

· The SeerEngine_DC_PLUGIN-version-py3.6.egg file will not be provided in E6311 and later.

· The SeerEngine_DC_PLUGIN-version-py3-none-any.whl file will be provided only in E6311 and later.

IMPORTANT:

Before executing the h3c-sdnplugin controller install command, make sure no neutron.conf file exists in the /root directory. If such a file exists, delete it or move it to another location.

NOTE:

An error might be reported when the h3c-sdnplugin controller install command is executed. Just ignore it.

3. After installation, follow the latest plug-in installation guide to check configuration file ml2_conf.ini and add new configuration items introduced in the latest version.

a. Use the vi editor to open configuration file ml2_conf.ini.

[root@localhost ~]# vi /etc/kolla/neutron-server/ml2_conf.ini

b. According to the operating system running in the Kolla environment, modify configuration file ml2_conf.ini.

- If a CentOS operating system runs in the Kolla environment, edit configuration file ml2_conf.ini according to the [SEC_SDNCONTROLLER] configuration group of configuration file ml2_conf.ini in H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for CentOS.

- If a Ubuntu operating system runs in the Kolla environment, edit configuration file ml2_conf.ini according to the [SEC_SDNCONTROLLER] configuration group of configuration file ml2_conf.ini in H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for Ubuntu.

4. Exit and then restart the neutron_server container.

(neutron-server)[root@controller01 ~]# exit

[root@controller01 ~]# docker restart neutron_server

5. Create the latest neutron-server container image. For more information, see “7.”

To upgrade the Neutron security plug-in while retaining the neutron_server container, skip this step. After the security plugin upgrade is completed, create the latest neutron-server container image. To upgrade the Neutron security plugin while retaining the neutron_server container, see "Upgrade with the neutron_server container retained."

Installing the SeerEngine-DC Neutron security plug-in on OpenStack

The SeerEngine-DC Neutron security plug-in can be installed on multiple versions of OpenStack.

The SeerEngine-DC Neutron security plug-in is installed on the OpenStack controller node. Before installation, set up the base environment on the node.

Installing the security plug-in on the controller node

Obtaining the installation package

Obtain and copy the security plug-in installation package of the required version to the target installation directory on the server or virtual machine.

Alternatively, transfer the installation package to the target installation directory through a file transfer protocol such as FTP, TFTP, or SCP.

IMPORTANT:

To avoid damaging the installation packages, select binary mode if you are to transfer the package through FTP or TFTP.

Installing the security plug-in on the OpenStack controller node

1. Generate startup scripts for the neutron-server containers. If you have already completed "Installing the SeerEngine-DC Neutron plug-ins.", you may choose to skip this step.

[root@localhost ~]# runlike neutron_server>docker-neutron-server.sh

2. Edit the neutron.conf configuration file.

a. Use the vi editor to open the neutron.conf configuration file.

[root@localhost ~]# sudo vi /etc/kolla/neutron-server/neutron.conf

b. Press I to switch to insert mode, and then edit the configuration file. For more information about the parameters, see "Parameters and fields."

For OpenStack Kilo, Liberty, Mitaka, Newton, Ocata, Pike, and Queens, it supports firewall services such as firewall_h3c. Please edit the neutron.conf configuration file as follows:

[DEFAULT]

service_plugins = firewall_h3c,h3c_security_core,lbaasv2,vpnaas

[service_providers]

service_provider=FIREWALL:H3C:networking_sec_h3c.fw.h3c_fwplugin_driver.H3CFwaasDriver:default

service_provider=LOADBALANCERV2:H3C:networking_sec_h3c.lb.h3c_lbplugin_driver_v2.H3CLbaasv2PluginDriver:default

service_provider=VPN:H3C:networking_sec_h3c.vpn.h3c_vpnplugin_driver.H3CVpnPluginDriver:default

For OpenStack Rocky, it supports firewall services such as firewall_h3c and firewall_v2.

- Taking firewall_h3c as an example, edit the neutron.conf configuration file as follows:

[DEFAULT]

service_plugins = firewall_h3c,h3c_security_core,lbaasv2,vpnaas

[service_providers]

service_provider=FIREWALL:H3C:networking_sec_h3c.fw.h3c_fwplugin_driver.H3CFwaasDriver:default

service_provider=LOADBALANCERV2:H3C:networking_sec_h3c.lb.h3c_lbplugin_driver_v2.H3CLbaasv2PluginDriver:default

service_provider=VPN:H3C:networking_sec_h3c.vpn.h3c_vpnplugin_driver.H3CVpnPluginDriver:default

- Taking firewall_v2 as an example, edit the neutron.conf configuration file as follows:

service_plugins = h3c_l3_router,firewall_v2,h3c_security_core,lbaasv2,vpnaas

[service_providers]

service_provider = FIREWALL_V2:H3C:networking_sec_h3c.fw2.h3c_fwpluginv2_driver.H3CFwaasV2Driver:default

service_provider=LOADBALANCERV2:H3C:networking_sec_h3c.lb.h3c_lbplugin_driver_v2.H3CLbaasv2PluginDriver:default

service_provider=VPN:H3C:networking_sec_h3c.vpn.h3c_vpnplugin_driver.H3CVpnPluginDriver:default

IMPORTANT:

For OpenStack Pike, when the load balancer supports multiple resource pools of the Context type, you must preprovision a resource pool named dmz or core on the controller, and then change the value of the service provider parameter to LOADBALANCERV2:DMZ:networking_sec_h3c.lb.h3c_lbplugin_driver_v2.H3CLbaasv2PluginDMZDriver:default or LOADBALANCERV2:CORE:networking_sec_h3c.lb.h3c_lbplugin_driver_v2.H3CLbaasv2PluginCOREDriver:default accordingly.

¡ For OpenStack Kilo2015.1, Liberty, and Mitaka, configure the neutron.conf configuration file as follows when Load balancer V1 is configured in OpenStack:

[DEFAULT]

service_plugins = firewall_h3c,lbaas,vpnaas

[service_providers]

service_provider=FIREWALL:H3C:networking_sec_h3c.fw.h3c_fwplugin_driver.H3CFwaasDriver:default

service_provider=LOADBALANCER:H3C:networking_sec_h3c.lb.h3c_lbplugin_driver.H3CLbaasPluginDriver:default

service_provider=VPN:H3C:networking_sec_h3c.vpn.h3c_vpnplugin_ko_driver.H3CVpnPluginDriver:default

¡ For OpenStack Ussuri, the security plug-ins only supports configuring the firewall service firewall_v2. Please configure the neutron.conf configuration file as follows:

[DEFAULT]

service_plugins = h3c_l3_router,firewall_v2,segments,h3c_security_core

[service_providers]

service_provider = FIREWALL_V2:H3C:networking_sec_h3c.fw2.h3c_fwpluginv2_driver.H3CFwaasV2Driver:default

¡ For OpenStack Newton and Ocata, you can specify only Load balancer V2 and edit the service_provider parameter for the VPN service as follows:

service_provider=VPN:H3C:networking_sec_h3c.vpn.h3c_vpnplugin_ko_driver.H3CVpnPluginDriver:default

IMPORTANT:

The service_provider parameter value for the VPN services is different between OpenStack Pike, Queens, and Rocky and OpenStack Kilo2015.1, Liberty, Mitaka, Newton, and Ocata. Be clear about the differences.

c. Press Esc to quit insert mode, and enter :wq to exit the vi editor and save the neutron.conf file.

3. Edit the neutron.conf configuration file.

a. Use the vi editor to open the neutron.conf configuration file.

[root@localhost ~]# vi /etc/kolla/neutron-server/neutron.conf

b. Press I to switch to insert mode, and then edit the configuration file. For more information about the parameters, see "Parameters and fields."

[SEC_SDNCONTROLLER]

url = https://127.0.0.1: 30000

username = admin

password =Pwd@12345

domain = sdn

timeout = 1800

retry = 10

white_list = False

use_neutron_credential = False

firewall_force_audit = False

sec_output_json_log = False

vendor_rpc_topic = VENDOR_PLUGIN

enable_https = False

neutron_plugin_ca_file =

neutron_plugin_cert_file =

neutron_plugin_key_file =

enable_iam_auth = False

enable_firewall_metadata = False

enable_router_nat_without_firewall = False

enable_firewall_object_group = False

cloud_region_name = default

4. If you have set the white_list parameter to True, perform the following tasks:

¡ Delete the username, password, and domain parameters for SEC_SDNCONTROLLER in the ml2_sec_conf_h3c.ini configuration file.

¡ Add an authentication-free user to the controller.

- Enter the IP address of the host where the Neutron server resides.

- Specify the role as Admin.

5. If you have set the use_neutron_credential parameter to True, perform the following steps:

a. Modify the neutron.conf configuration file.

# Use the vi editor to open the neutron.conf configuration file.

# Press I to switch to insert mode, and add the following configuration. For information about the parameters, see "neutron.conf."

[keystone_authtoken]

admin_user = neutron

admin_password = KEYSTONE_PASS

# Press Esc to quit insert mode, and enter :wq to exit the vi editor and save the neutron.conf file.

b. Add an admin user to the controller.

# Configure the username as neutron.

# Specify the role as Admin.

# Enter the password of the neutron user in OpenStack.

6. Copy the installation package to the neutron_server container.

[root@localhost ~]# docker cp SeerEngine_DC_SEC_PLUGIN-E3603P01-py2.7.egg neutron_server:/

7. Install the package.

[root@localhost ~]# docker exec –it –u root neutron_server bash

[root@localhost ~]# easy_install SeerEngine_DC_SEC_PLUGIN-E3603P01-py2.7.egg

[root@localhost ~]# h3c-sdnplugin controller install

IMPORTANT:

Before executing the h3c-sdnplugin controller install command, make sure no neutron.conf file exists in the /root directory. If such a file exists, delete it or move it to another location.

NOTE:

An error might be reported when the h3c-sdnplugin controller install command is executed. Just ignore it.

8. Generate the images for the neutron-server container.

[root@localhost ~]# neutron_server_image=$(docker ps --format {{.Image}} --filter name=neutron_server)

[root@localhost ~]# docker ps | grep $neutron_server_image

16d60524b8b3 kolla/centos-source-neutron-server:rocky "dumb-init --single-? 16 months ago Up 2 weeks neutron_server

[root@localhost ~]# docker commit 16d60524b8b3 kolla/neutron-server-h3c (replace 16d60524b8b3 with the UUID obtained in the preceding command)

[root@localhost ~]# docker rm -f neutron_server

[root@localhost ~]# docker tag $neutron_server_image kolla/neutron-server-origin

NOTE:

If you have already completed "Installing the SeerEngine-DC Neutron plug-ins.", it is unnecessary to execute the docker tag command.

[root@localhost ~]# docker rmi $neutron_server_image

[root@localhost ~]# docker tag kolla/neutron-server-h3c $neutron_server_image

[root@localhost ~]# docker rmi kolla/neutron-server-h3c

9. Start the neutron-server service.

[root@localhost ~]# source docker-neutron-server.sh

10. Verify the status of the services.

[root@localhost ~]# # docker ps –filter "name=neutron_server"

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

289e4e132a9b kolla/centos-source-neutron-server:ocata "dumb-init –single-?

1 minutes ago Up 1 minutes neutron_server

Parameters and fields

This section describes parameters in configuration files and fields included in parameters.

neutron.conf

Parameter	Description
service_plugins	Extension plug-ins loaded to OpenStack. The security plug-in supports the following firewall services, and you can change the values as follows: · For the open-source firewall plug-in not in agent mode, change firewall in the value to firewall_h3c. · Based on H3C's self-developed firewall 2.0 service: firewall_v2 (only supports OpenStack Rocky and Ussuri). To configure firewall services, add h3c_security_core to the value. In the /etc/kolla/neutron-server/ directory of neutron_server, you can configure the service_provider only once for the same service. Do not configure the service_provider parameter in fwaas_driver.ini after you configure it in neutron.conf. This rule applies also to Lbaas and Vpnaas. When configuring the firewall service as firewall_h3c, please change the value of the driver field for [fwaas] in the /etc/kolla/neutron-server/fwaas_driver.ini directory to networking_sec_h3c.fw.h3c_fwplugin_driver.H3CfwaasDriver. When configuring the firewall service as firewall_v2, please change the value of the driver field for [fwaas] in the /etc/kolla/neutron-server/fwaas_driver.ini directory to networking_sec_h3c.fw2.h3c_fwpluginv2_driver.H3CFwaasV2Driver.
service_provider	Directory where the extension plug-ins are saved.
admin_user	Admin username for Keystone authentication in OpenStack, for example, neutron.
admin_password	Admin password for Keystone authentication in OpenStack. (Replace KEYSTONE_PASS with the real Neutron user password for Keystone authentication.)

neutron_conf

Parameter	Description
url	URL address for accessing Unified Platform.
username	Username for logging in to Unified Platform, for example, admin. You do not need to configure a username when the use_neutron_credential parameter is set to True.
password	Password for logging in to Unified Platform, for example, Pwd@12345. You do not need to configure a password when the use_neutron_credential parameter is set to True. If the password contains a dollar sign ($), enter a backward slash (\) before the dollar sign.
domain	Name of the domain where the controller resides, for example, sdn.
timeout	The amount of time that the Neutron server waits for a response from the controller in seconds, for example, 1800 seconds. As a best practice, set the waiting time greater than or equal to 1800 seconds.
retry	Number of connection request attempts, for example, 10.
white_list	Whether to enable or disable the authentication-free user feature on OpenStack. · True—Enable. · False—Disable.
use_neutron_credential	Whether to use the OpenStack Neutron username and password to communicate with the controller. · True—Use. False—Do not use.
firewall_force_audit	Whether to audit firewall policies synchronized to the controller by OpenStack. The default value is True for OpenStack Kilo 2015.1 and False for other OpenStack versions. · True—Audits firewall policies synchronized to the controller by OpenStack. The auditing state of the synchronized policies on the controller is True (audited). · False—Does not audit firewall policies synchronized to the controller by OpenStack. The synchronized policies on the controller retain their previous auditing state.
sec_output_json_log	Whether to output REST API messages between the SeerEngine-DC Neutron security plugins and SeerEngine-DC controller to the OpenStack operating logs in JSON format. · True—Enable. · False—Disable.
vendor_rpc_topic	RPC topic of the vendor. This parameter is required when the vendor needs to obtain Neutron data from the SeerEngine-DC Neutron plug-ins. The available values are as follows: · VENDOR_PLUGIN—Default value, which means that the parameter does not take effect. · DP_PLUGIN—RPC topic of DPtech. The value of this parameter must be negotiated by the vendor and H3C.
enable_https	Whether to enable HTTPS bidirectional authentication. The default value is False. · True—Enable. · False—Disable. Only OpenStack Pike supports this parameter.
neutron_plugin_ca_file	Save location for the CA certificate of the controller. As a best practice, save the CA certificate in the /usr/share/neutron directory. Only OpenStack Pike supports this parameter.
neutron_plugin_cert_file	Save location for the Cert certificate of the controller. As a best practice, save the Cert certificate in the /usr/share/neutron directory. Only OpenStack Pike supports this parameter.
neutron_plugin_key_file	Save location for the Key certificate of the controller. As a best practice, save the Key certificate in the /usr/share/neutron directory. Only OpenStack Pike supports this parameter.
enable_iam_auth	Whether to enable IAM interface authentication. · True—Enable. · False—Disable. When connecting to Unified Platform, you can set the value to True to use the IAM interface for authentication. The default value is False. Only OpenStack Newton supports this parameter. This parameter is obsolete.
enable_firewall_metadata	Whether to allow the CloudOS platform to issue firewall-related fields such as the resource pool name to the controller. This parameter is used only for communication with the CloudOS platform. Only OpenStack Pike supports this parameter.
enable_router_nat_without_firewall	Whether to enable NAT when no firewall is configured for the tenant. · True—Enable NAT when no firewall is configured. This setting automatically creates default firewall resources to implement NAT if the vRouter has been bound to an external network. · False—Not enable NAT when no firewall is configured. The default value is False. Only OpenStack Pike supports this parameter.
cloud_region_name	If one cloud platform is connected to the controller, you can modify this parameter only when the following requirements are met: · The cloud platform is connected to the controller for the first time after upgrade. · No tenant resources are newly created on the controller. Make sure the value for this parameter is the same as the name configured on the controller and configure the cloud platform as the default platform. If multiple cloud platforms are connected to the controller, the rules for the single cloud platform interoperability scenario applies for the first cloud platform. For the other cloud platforms, you must change the value of this parameter to be the same as the value for these cloud platforms, and make sure they are the same as those configured on the controller. This parameter cannot be modified after the cloud platforms are connected to the controller.

Upgrading the SeerEngine-DC Neutron security plug-in

To upgrade the SeerEngine-DC Neutron security plug-in, first remove the old version and then install the new version. For more information, see "Installing the security plug-in on the controller node."

CAUTION:

· Service might be interrupted during the upgrade. Before performing an upgrade, be sure you fully understand its impact on services.

· Before upgrading the security plug-in, backup the configuration file "/etc/kolla/neutron-server/neutron.conf" as Kolla environment cannot automatically inherit plugin configuration. After upgrading the security plug-in, manually modify the parameter values based on the backup to ensure consistency with the previous configuration.

After you upgrade the version of converged plug-ins to E6304P01 or later, some parameters in the ml2_sec_conf_h3c.ini configuration file are moved to the Web interface of the controller. After installing the new converged plug-ins version and the new controller version, you must change the values of those parameters to their original values before upgrade.

1. Save the ml2_sec_conf_h3c.ini.bak or ml2_sec_conf_h3c.ini.h3c_bak file in the /etc/neutron/plugins/ml2 directory of the controller node.

2. Log in to the controller, click Automation on the top navigation bar, and then select Virtual Networking > OpenStack from the left navigation pane. Click Add OpenStack-Based Cloud Platform, and then click the Parameter Settings tab to edit the parameters based on the information in the ml2_sec_conf_h3c.ini.bak or ml2_sec_conf_h3c.ini.h3c_bak file. Table 4 shows mappings between parameters on the controller and in the configuration file. Table 5 shows the parameters that become obsolete after upgrade.

CAUTION:

If OpenStack-based cloud platform has been configured on the controller before the upgrade, after upgrading, you need to click Edit in the corresponding Actions section to enter the Edit OpenStack-Based Cloud Platform page. Confirm the parameters under the Security Settings tab, and then click Apply.

Table 4 Mappings between parameters on the controller and in the configuration file

Parameters in the ml2_sec_conf_h3c.ini file before upgrade	Parameters on the Web interface of the controller after upgrade
directly_external: OFF	Firewall: On for All
directly_external: ANY	Firewall: Off for All
directly_external: SUFFIX directly_external_suffix: name (The name argument represents the suffix of the name of the vRouter.)	Firewall: Off for vRouters Matching Suffix
tenant_gw_selection_strategy: match_gateway_name tenant_gateway_name: name (The name argument represents the name of the border gateway.)	External Connectivity Settings: Single-Segment Tenant Border Gateway Policy: Match Border Gateway Name
enable_multi_gateways: True	External Connectivity Settings: Single-Segment Tenant Border Gateway Policy: Match Physical Network Name of vRouter External Network
enable_multi_segments: True	External Connectivity Settings: Multi-Segment Tenant Border Gateway Policy: Match Segmented Physical Network Name of External Network
auto_create_resource: True	Auto Create Resource: On
resource_mode: CORE_GATEWAY firewall_type: CGSR	Firewall Resource Type: Service Gateway Firewall Resource Mode: Exclusive
resource_mode: CORE_GATEWAY firewall_type: CGSR_SHARE	Firewall Resource Type: Service Gateway Firewall Resource Mode: Shared
resource_mode: CORE_GATEWAY firewall_type: NFV_CGSR	Firewall Resource Type: Service Gateway Firewall Resource Mode: NFV
resource_mode: SERVICE_LEAF firewall_type: ACSR	Firewall Resource Type: Service Leaf Firewall Resource Mode: Exclusive
resource_mode: SERVICE_LEAF firewall_type: ACSR_SHARE	Firewall Resource Type: Service Leaf Firewall Resource Mode: Shared
lb_type: CGSR	LB Resource Mode: Exclusive
lb_type: CGSR_SHARE	LB Resource Mode: Shared
lb_type: NFV_CGSR	LB Resource Mode: NFV
resource_share_count: 1	Shared Resource Nodes: 1
lb_resource_mode: SP	LB Resource Pool Mode: Single Resource Pool
lb_resource_mode: MP	LB Resource Pool Mode: Multiple Resource Pools
lb_enable_snat: True	SNAT for Loadbalancer: On
lb_member_slow_shutdown: True	Real Service Slow Shutdown: On
enable_lb_xff: True	XFF for Loadbalancer: On
enable_lb_certchain: True	Send Full Certificate Chain on SSL Server: On

Table 5 Obsolete parameters after upgrade

Parameter	Description
firewall_type	Type of the firewalls created on the SeerEngine-DC controller. The following firewall type is no longer supported: CGSR_SHARE_BY_COUNT—Context-based gateway service type firewall, all using the same context when the number of contexts reaches the threshold set by the cgsr_fw_context_limit parameter. This firewall type is available only when the value of the resource_mode parameter is CORE_GATEWAY. Only OpenStack Pike supports this firewall type.
fw_share_by_tenant	Whether to enable exclusive use of a gateway service type firewall context by a single tenant and allow the context to be shared by service resources of the tenant when the firewall type is CGSR_SHARE or ACSR_SHARE.
cgsr_fw_context_limit	Context threshold for context-based gateway service type firewalls. The value is an integer. When the threshold is reached, all the context-based gateway service type firewalls use the same context. This parameter takes effect only when the value of the firewall_type parameter is CGSR_SHARE_BY_COUNT. Only OpenStack Pike supports this parameter.
nfv_ha	Whether the NFV and NFV_SHARE resources support stack. · True—Support. · False—Do not support.

Upgrade with neutron_server container removed

1. Remove the containers installed with the old version of the security plug-in and its image.

neutron_server_image=$(docker ps --format {{.Image}} --filter name=neutron_server)

a. If no docker-neutron-server.sh scrip file exists, execute the following command. If such a file exists, skip this step.

[root@localhost ~]# runlike neutron_server>docker-neutron-server.sh

b. Remove the containers installed with the old version of the security plug-in and its image.

[root@localhost ~]# docker rm -f neutron_server

[root@localhost ~]# docker rmi $neutron_server_image

c. Restore the default container and image in the Kolla environment.

[root@localhost ~]# docker tag kolla/neutron-server-origin $neutron_server_image

[root@localhost ~]# docker rmi kolla/neutron-server-origin

[root@controller ~]# source docker-neutron-server.sh

IMPORTANT:

Before restarting the neutron_server container, you must restore the configurations in the neutron.conf file and remove the plug-ins-related configuration.

2. Install the new version of the security plug-in. For the installation procedure, see "Installing the SeerEngine-DC Neutron security plug-in on OpenStack".

Upgrade with neutron_server container retained

To upgrade the plug-ins with neutron_server containers retained, you are required to remove the old version of the security plug-in and then install the new version of the security plug-in on the container.

To upgrade the neutron_server container:

1. Access the neutron_server container and remove the old version of the security plug-in.

[root@controller ~]# docker exec -it -u root neutron_server bash

(neutron-server) [root@controller ~]# h3c-secplugin controller uninstall

Remove service

Removed symlink /etc/systemd/system/multi-user.target.wants/h3c-sec-agent.service.

Restore config files

Uninstallation complete.

(neutron-server) [root@controller ~]# pip uninstall seerengine-dc-sec-plugin

Uninstalling SeerEngine-DC-SEC-PLUGIN-E3608:

/usr/bin/h3c-sec-agent

/usr/bin/h3c-secplugin

……

2. Install the new version of the security plug-in.

[root@controller ~]# docker cp SeerEngine_DC_SEC_PLUGIN-D3609-py2.7.egg neutron_server:/

[root@controller ~]# docker exec -it -u root neutron_server bash

(neutron-server) [root@controller ~]# easy_install SeerEngine_DC_SEC_PLUGIN-D3609-py2.7.egg

(neutron-server) [root@controller ~]# h3c-secplugin controller install

3. After installation, check the [SEC_SDNCONTROLLER] configuration item in configuration file neutron.conf and add new configuration items introduced in the latest version. For more information, see 3.

4. Exit and then restart the neutron_server container.

(neutron-server)[root@controller01 ~]# exit

[root@controller01 ~]# docker restart neutron_server

5. Create the latest neutron-server container image. For more information, see “8.”

IMPORTANT:

Before executing the h3c-secplugin controller install command, make sure no neutron.conf file exists in the /root directory. If such a file exists, delete it or move it to another location.

NOTE:

An error might be reported when the h3c-secplugin controller install / uninstall command is executed. Just ignore it.

Installing OpenStack plug-ins by using Kubernetes

Installing/Upgrading the SeerEngine-DC Neutron plug-ins

Installing SeerEngine-DC Neutron plug-ins

Obtaining the SeerEngine-DC Neutron plug-in installation package

Obtaining the containerized installation and deployment script of the plug-ins

Obtain the containerized installation and deployment script of the plug-in of the required version. The software package name is in the format of SeerEngine_DC_PLUGIN_SHELL_INSTALL-version.zip. version represents the version of the software package. Decompress the software package. The neutron_h3c_plugin_init.sh file is the script for deploying the Neutron plug-ins in Kubernetes.

Installing the SeerEngine-DC Neutron plug-ins on the neutron-server nodes in Kubernetes

1. On all nodes running neutron-server, create the /neutron_plugin_dir/net_packages folder, which must be of the same level as the /root/ folder.

[root@localhost ~]# mkdir /neutron_plugin_dir/net_packages

2. Obtain the .rpm or .whl offline package for the basic environment from Internet. According to the operating system and Python versions in the neutron-server pod, select a proper offline package for the basic environment, including the following contents:

¡ Python3: python3-pip, python3-setuptools

¡ Python2: python-pip, python-setuptools

¡ python-websocket-client of version 0.56: As a best practice, use the .whl offline package for the basic environment.

3. Put the plug-in installation packages and the package for the basic environment to each /neutron_plugin_dir/net_packages path, and put the shell script to the /neutron_plugin_dir/ path.

NOTE:

You must modify the permission to the shell script to 755.

[root@neutron_server]# chmod 755 neutron_h3c_plugin_init.sh

4. Edit configuration files ml2_conf.ini and neutron.conf.

Configure the configuration files based on the operating system running on the host.

¡ If a CentOS operating system runs on the host, see H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for CentOS to configure configuration files ml2_conf.ini and neutron.conf.

¡ If an Ubuntu operating system runs on the host, see H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for Ubuntu to configure configuration files ml2_conf.ini and neutron.conf.

5. Edit the deployment YAML file for neutron-server:

a. Edit the command and args fields in the YAML file.

command: [“/bin/bash”, “-c”, “--“]

args: [ “/neutron_plugin_dir/neutron_h3c_plugin_init.sh; /bin/bash /root/start_neutron_server.sh” ]

b. Add the mountPath field to the YAML file.

mountPath: /neutron_plugin_dir/

c. Add the hostPath field to the YAML file.

hostPath:

path: /neutron_plugin_dir/

NOTE:

· Because deployment is flexible in the containerization environment, the locations of files ml2_conf.ini and neutron.conf on the host vary. Modify the corresponding configuration files according to your specific environment.

· Because the neutron-server pod can be deployed in various methods, the YAML file to be edited is different if it is not deployed by using a deployment. Edit the file according to your specific Kubernetes environment.

Deleting the native neutron-server pod

If the neutron-server pod is started with a deployment, execute the following command to delete the neutron-server pod.

[root@localhost ~]# kubectl delete deployments neutron-server-deployment –n namespace

Restarting the neutron-server pod

[root@localhost ~]# kubectl create -f neutron-server-deployment.yaml

NOTE:

Because deployment is flexible in the Kubernetes environment, you can change the shaded fields in the preceding commands as needed.

Checking the controller node state

Log in to the controller. Navigate to the Automation > Data Center Networks > Virtual Networking > OpenStack page. View the state of the controller node. If a green flag is displayed for the controller node, the plug-ins can be used normally.

NOTE:

To avoid container restart failure, do not delete any files or dependencies in the /neutron_plugin_dir/ path.

Upgrading the SeerEngine-DC Neutron plug-ins

1. Replace the Neutron plug-in installation packages in the /neutron_plugin_dir/net_packages path on the related nodes.

2. For information about deleting the native neutron-server pod, see “Deleting the native neutron-server pod.”

3. For information about restarting the neutron-server pod, see “Restarting the neutron-server pod.”

Installing/Upgrading the SeerEngine-DC Neutron security plug-in

Installing the SeerEngine-DC Neutron security plug-in

Obtaining the installation package for SeerEngine-DC Neutron security plug-in

IMPORTANT:

Obtaining the containerized security plug-in installation script

Obtain the containerized security plug-in installation script of the required version. The software package is named SeerEngine_DC_SEC_PLUGIN_SHELL_INSTALL-version.zip, where version refers to the software package version number. After decompressing the software package, neutron_h3c_plugin_init.sh is the script used for deploying the Neutron security plug-in for Kubernetes.

Installing the SeerEngine-DC Neutron security plug-in in Kubernetes neutron-server

1. On all neutron-server running nodes, create folder /neutron_plugin_dir/sec_packages, and make sure the path of this folder is at the same level as /root/.

[root@localhost ~]# mkdir /neutron_plugin_dir/sec_packages

2. Place the previous plug-in installation package into each /neutron_plugin_dir/sec_packages directory, and place the shell script in the /neutron_plugin_dir/ directory.

NOTE:

Modify the shell script permissions to 755.

[root@neutron_server]# chmod 755 neutron_h3c_sec_plugin_init.sh

3. Edit the neutron.conf configuration file. For more information, see the associated installation guide.

¡ For the CentOS operating system, see H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for CentOS.

¡ For the Ubuntu operating system, H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for Ubuntu.

4. Edit the ml2_conf.ini configuration file.

Add configuration items related with [SEC_SDNCONTROLLER] to ml2_conf.ini based on the host operating system. For more information, see the modification of the ml2_sec_conf_h3c.ini file in the associated installation guide.

¡ For the CentOS operating system, see H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for CentOS.

¡ For the Ubuntu operating system, H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for Ubuntu.

5. Edit the deployment yaml file for neutron-server.

a. Edit the commond and args settings in the yaml file as follows.

command: [“/bin/bash”, “-c”, “--“]

args: [“/neutron_plugin_dir/neutron_h3c_plugin_init.sh; /bin/bash /neutron_plugin_dir/neutron_h3c_sec_plugin_init.sh; /bin/bash /root/start_neutron_server.sh” ]

NOTE:

If the task in "Installing/Upgrading the SeerEngine-DC Neutron plug-ins" has been executed, place /neutron_plugin_dir/neutron_h3c_sec_plugin_init.sh after neutron_plugin_dir/ neutron_h3c_plugin_init.sh.

b. Add the mountPath setting to the yaml file. (Skip this step if the task in "Installing/Upgrading the SeerEngine-DC Neutron plug-ins" has been executed.)

mountPath: /neutron_plugin_dir/

c. Add the hostPath setting to the yaml file. (Skip this step if the task in "Installing/Upgrading the SeerEngine-DC Neutron plug-ins" has been executed.)

hostPath:

path: /neutron_plugin_dir/

NOTE:

· Because of the deployment flexibility of the containerized environment, the location of the neutron.conf file on the host might vary. You need to edit the corresponding configuration file according to the specific environment.

· Because of the various deployment methods for the neutron-server Pod, the edited yaml file might vary when deployment is not used. You need to edit it according to the specific Kubernetes environment.

Deleting the native neutron-server pod

If neutron-server is started in deployment mode, execute the following command to delete the neutron-server Pod.

[root@localhost ~]# kubectl delete deployments neutron-server-deployment –n namespace

Restarting the neutron-server pod

[root@localhost ~]# kubectl create -f neutron-server-deployment.yaml

NOTE:

· Because of the deployment flexibility of the Kubernetes environment, the content displayed in gray in the previous commands needs to be edited according to the specific environment.

· To avoid container restart failure, do not delete all files and dependency packages from the /neutron_plugin_dir/ directory.

Upgrading the SeerEngine-DC Neutron security plug-in

1. Replace the Neutron security plug-in installation package in the /neutron_plugin_dir/sec_packages path of the corresponding node.

2. For more information about deleting the native neutron-server Pod, see "Deleting the native neutron-server pod."

3. For more information about restarting the neutron-server Pod, see "Restarting the neutron-server pod."

Upgrading non-converged plug-ins to converged plug-ins

1. Upgrade the controller to a version that supports converged plug-ins.

2. Remove non-converged plug-ins:

a. Access the neutron-server container:

[root@neutron_server ~]# docker exec -itu root neutron_server bash

b. Remove the plug-ins on the controller node:

- Versions earlier than E3702

[root@localhost ~]# h3c-vcfplugin controller uninstall

- E3702 and its later versions

[root@localhost ~]# h3c-sdnplugin controller uninstall

c. Remove the software packages from all nodes:

CentOS 8 operating system:

[root@localhost ~]# pip3 uninstall seerengine-dc-plugin

Other CentOS operating systems:

[root@localhost ~]# pip uninstall seerengine-dc-plugin

IMPORTANT:

Commands for removing plug-ins vary depending on the software version.

3. Install converged plug-ins:

a. Install converged plug-ins and security plug-ins as shown in "Installing OpenStack plug-ins."

b. Use the vi editor to open the ml2_conf.ini configuration file.

[root@localhost ~]# vi /etc/neutron/plugins/ml2/ml2_conf.ini

c. Press I to switch to insert mode, and set the parameters in the ml2_conf.ini configuration file. Press Esc to quit insert mode, and enter :wq to exit the vi editor and save the ml2_conf.ini file.

[VCFCONTROLLER]

sdnc_rpc_url = ws://127.0.0.1:30000

sdnc_rpc_ping_interval = 60

websocket_fragment_size = 102400

cloud_region_name = default

ml2_conf.ini

sdnc_rpc_url

Set the value to the IP address and WebSocket type interface number of Unified Platform when Metadata is enabled or DHCP fail-safe is supported.

Configure this parameter based on the URL of Unified Platform. For example, if the URL of Unified Platform is http://127.0.0.1:30000, set this parameter to ws://127.0.0.1: 30000.

cloud_region_name

If one cloud platform is connected to the controller, you can modify this parameter when the cloud platform is connected to the controller for the first time after the upgrade and no tenant resources are newly created on the controller. Make sure the value of this parameter is the same as the name configured on the controller and configure the cloud platform as the default platform.

If multiple cloud platforms are connected to the controller, the rules for the single cloud platform interoperability scenario applies for the first cloud platform. For the other cloud platforms, you must change the value of this parameter to be the same as the value for these cloud platforms, and make sure they are the same as those configured on the controller.

This parameter cannot be modified after the cloud platforms are connected to the controller. You must specify different values for the vxlan vni_ranges parameter for different cloud platforms.

d. Delete the backup files generated for non-converged plug-ins or change their file name suffixes. Those backup files include ml2_conf_h3c.ini.bak and ml2_conf_h3c.ini.h3c_bak. If you do not perform this operation, some parameters of non-converged plug-ins might be modified or initialized upon next-time security plug-in upgrades.

4. Configure parameters on the controller:

Some parameters in the ml2_conf_h3c.ini configuration file for non-converged plug-ins have been moved to the Web interface of the controller. After installing converged plug-ins, you must change the values of the parameters to the values before upgrade.

a. Save the ml2_conf_h3c.ini.bak or ml2_conf_h3c.ini.h3c_bak file in the /etc/neutron/plugins/ml2 directory of the controller node.

b. Log in to the controller, click Automation on the top navigation bar, and then select Virtual Networking > OpenStack from the left navigation pane. Click Add OpenStack-Based Cloud Platform, and then click the Parameter Settings tab to edit the parameters based on the information in the ml2_conf_h3c.ini.bak or ml2_conf_h3c.ini.h3c_bak file.

Table 6 Mappings between parameters on the controller and in the configuration file

Parameters in the ml2_conf_h3c.ini file before upgrade	Parameters on the Web interface of the controller after upgrade
cloud_region_name	Name
hybrid_vnic	VLAN to VXLAN Conversion
enable_metadata: True enable_dhcp_hierarchical_port_binding: True	Network Node Access Policy: VLAN
enable_metadata: True enable_dhcp_hierarchical_port_binding: False	Network Node Access Policy: VXLAN
enable_metadata: False enable_dhcp_hierarchical_port_binding: False	Network Node Access Policy: No Access
ip_mac_binding	IP-MAC Anti-Spoofing
directly_external: OFF	Firewall: On for All
directly_external: ANY	Firewall: Off for All
directly_external: SUFFIX directly_external_suffix: name where name represents the suffix of the name of the vRouter.	Firewall: Off for vRouters Matching Suffix
tenant_gw_selection_strategy: match_gateway_name tenant_gateway_name: name, where name represents the name of the border gateway.	External Connectivity Settings: Single-Segment Tenant Border Gateway Policy: Match Border Gateway Name
enable_multi_gateways: True	External Connectivity Settings: Single-Segment Tenant Border Gateway Policy: Match Physical Network Name of vRouter External Network
enable_bind_router_gateway_with_specified_name: True NOTE: This field is available only for non-converged OpenStack Mitaka. This field takes precedence over the tenant_gw_selection_strategy field.	External Connectivity Settings: Single-Segment Tenant Border Gateway Policy: Match External Network Name of vRouter
enable_multi_segments: True	External Connectivity Settings: Multi-Segment Tenant Border Gateway Policy: Match Segmented Physical Network Name of External Network
deploy_network_resource_gateway	Preconfigure Border Gateway for External Network
network_force_flat	Forcibly Convert External Network to Flat Network
enable_network_l3vni: False	Automatic Allocation of L3VNIs for External Networks: Off
dhcp_lease_time	DHCP Lease Duration
generate_vrf_based_on_router_name: False	VRF Name Generation Method on vRouter: Auto
generate_vrf_based_on_router_name: True	VRF Name Generation Method on vRouter: Use vRouter Name
vds_name	Default VDS name.
auto_create_resource: True	Auto Create Resource: On
resource_mode: CORE_GATEWAY firewall_type: CGSR	Firewall Resource Type: Service Gateway Firewall Resource Mode: Exclusive
resource_mode: CORE_GATEWAY firewall_type: CGSR_SHARE	Firewall Resource Type: Service Gateway Firewall Resource Mode: Shared
resource_mode: CORE_GATEWAY firewall_type: NFV_CGSR	Firewall Resource Type: Service Gateway Firewall Resource Mode: NFV
resource_mode: SERVICE_LEAF firewall_type: ACSR	Firewall Resource Type: Service Leaf Firewall Resource Mode: Exclusive
resource_mode: SERVICE_LEAF firewall_type: ACSR_SHARE	Firewall Resource Type: Service Leaf Firewall Resource Mode: Shared
lb_type: CGSR	LB Resource Mode: Exclusive (Service Gateway)
resource_mode: CORE_GATEWAY lb_type: CGSR_SHARE	Resource Type: Service Gateway LB Resource Mode: Shared (Service Gateway)
resource_mode: CORE_GATEWAY lb_type: NFV_CGSR	Resource Type: Service Gateway LB Resource Mode: NFV (Service Gateway)
resource_share_count: 1	Shared Resource Nodes: 1
lb_resource_mode: SP	LB Resource Pool Mode: Single Resource Pool
lb_resource_mode: MP	LB Resource Pool Mode: Multiple Resource Pools
lb_enable_snat: True	SNAT for Loadbalancer: On
lb_member_slow_shutdown: True	Real Service Slow Shutdown: On
enable_lb_xff: True	XFF for Loadbalancer: On
enable_lb_certchain: True	Send Full Certificate Chain on SSL Server: On

Table 7 Obsolete parameters after upgrade

Parameter	Description
firewall_type	Type of the firewalls created on the SeerEngine-DC controller. The following firewall type is no longer supported: CGSR_SHARE_BY_COUNT—Context-based gateway service type firewall, all using the same context when the number of contexts reaches the threshold set by the cgsr_fw_context_limit parameter. This firewall type is available only when the value of the resource_mode parameter is CORE_GATEWAY. Only OpenStack Pike supports this firewall type.
fw_share_by_tenant	Whether to enable exclusive use of a gateway service type firewall context by a single tenant and allow the context to be shared by service resources of the tenant when the firewall type is CGSR_SHARE or ACSR_SHARE.
cgsr_fw_context_limit	Context threshold for context-based gateway service type firewalls. The value is an integer. When the threshold is reached, all the context-based gateway service type firewalls use the same context. This parameter takes effect only when the value of the firewall_type parameter is CGSR_SHARE_BY_COUNT. Only OpenStack Pike supports this parameter.
nfv_ha	Whether the NFV and NFV_SHARE resources support stack. · True—Support. · False—Do not support.

5. Configure the following settings on the controller page:

a. Configure the VNI range to be same as the vni_ranges parameter value in the ml2_conf.ini configuration file before the upgrade.

b. Make sure a VXLAN pool exists on the controller after the upgrade. If no VXLAN pools exist or the VXLAN pool resources are insufficient, add a new VXLAN pool and make sure the VXLAN pool range does not contain the segment IDs of the existing vRouters.

CAUTION:

6. Restart the neutron-server service.

[root@localhost ~]# docker restart neutron_server

(Optional.) Configuring the metadata service for network nodes

Configure the Metadata service for network nodes by referring to the plug-ins installation guide specific to the operating system.

· For the CentOS operating system, see H3C SeerEngine-DC Controller Converged OpenStack Plug-ins Installation Guide for CentOS.

· For the Ubuntu operating system, see H3C SeerEngine-DC Controller Converged OpenStack Plug-ins Installation Guide for Ubuntu.

FAQ

The Python tools cannot be installed using the yum command when a proxy server is used for Internet access. What should I do?

Configure HTTP proxy by performing the following steps:

1. Make sure the server or the virtual machine can access the HTTP proxy server.

2. At the CLI of the CentOS system, use the vi editor to open the yum.conf configuration file. If the yum.conf configuration file does not exist, this step creates the file.

[root@localhost ~]# vi /etc/yum.conf

3. Press I to switch to insert mode, and provide HTTP proxy information as follows:

¡ If the server does not require authentication, enter HTTP proxy information in the following format:
proxy = http://yourproxyaddress:proxyport

¡ If the server requires authentication, enter HTTP proxy information in the following format:
proxy = http://yourproxyaddress:proxyport
proxy_username=username
proxy_password=password

Table 8 describes the arguments in HTTP proxy information.

Table 8 Arguments in HTTP proxy information

Field	Description
username	Username for logging in to the proxy server, for example, sdn.
password	Password for logging in to the proxy server, for example, 123456.
yourproxyaddress	IP address of the proxy server, for example, 172.25.1.1.
proxyport	Port number of the proxy server, for example, 8080.

proxy = http://172.25.1.1:8080

proxy_username = sdn

proxy_password = 123456

4. Press Esc to quit insert mode, and enter :wq to exit the vi editor and save the yum.conf file.

After the plug-ins are installed successfully, what should I do if the controller fails to interconnect with the cloud platform?

Follow these steps to resolve the interconnection failure with the cloud platform:

1. Make sure you have strictly followed the procedure in this document to install and configure the plug-ins.

2. Contact the cloud platform vendor to determine whether a configuration issue exists on the cloud platform side.

3. If the issue persists, contact after-sales engineers.

Live migration of a VM to a specified destination host failed because of a service exception on the destination host. What should I do?

To resolve the issue:

1. View the VM state. If the live migration operation has been rolled back, the VM is in normal state, and services are not affected, you can perform live migration again after the destination host recovers.

2. Compare resource information to identify whether residual configuration exists on the destination host. If residual configuration exists, determine whether services will be affected.

¡ If services will not be affected, retain the residual configuration.

¡ If services will be affected, contact the technical support to delete the residual configuration.

The Inter X700 Ethernet network adapter series fails to receive LLDP messages. What should I do?

Use the following procedure to resolve the issue. An enp61s0f3 Ethernet network adapter is used as an example.

1. View detailed information about the Ethernet network adapter and record the value for the bus-info field.

sdn@ubuntu:~$ ethtool -i enp61s0f3

driver: i40e

version: 2.8.20-k

firmware-version: 3.33 0x80000f0c 1.1767.0

expansion-rom-version:

bus-info: 0000:3d:00.3

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

2. Use one of the following solutions:

¡ Solution 1. If this solution fails, use solution 2.

# Execute the following command:

sdn@ubuntu:~$ sudo ethtool --set-priv-flags enp61s0f3 disable-fw-lldp on

# Identify whether the value for the disable-fw-lldp field is on.

sdn@ubuntu:~$ ethtool --show-priv-flags enp61s0f3 | grep lldp

disable-fw-lldp : on

If the value is on, the network adapter then can receive LLDP messages. For this command to remain effective after a system restart, you must write this command into the user-defined startup program file.

# Open the self-defined startup program file.

sdn@ubuntu:~$ sudo vi /etc/rc.local

# Press I to switch to insert mode, and add this command to the file. Then press Esc to quit insert mode, and enter :wq to exit the vi editor and save the file.

ethtool --set-priv-flags enp61s0f3 disable-fw-lldp on

Make sure this command line is configured before the exit 0 line.

¡ Solution 2.

# Execute the echo "lldp stop" > /sys/kernel/debug/i40e/bus-info/command command. Enter the recorded bus info value for the network adapter, and add a backslash (\) before each ":".

sdn@ubuntu:~$ sudo -i

sdn@ubuntu:~$ echo "lldp stop" > /sys/kernel/debug/i40e/0000\:3d\:00.3/command

The network adapter can receive LLDP messages after this command is executed. For this command to remain effective after a system restart, you must write this command into the user-defined startup program file.

# Open the self-defined startup program file.

sdn@ubuntu:~$ sudo vi /etc/rc.local

# Press I to switch to insert mode, and add this command to the file. Then Press Esc to quit insert mode, and enter :wq to exit the vi editor and save the file.

echo "lldp stop" > /sys/kernel/debug/i40e/0000\:3d\:00.3/command

Make sure this command line is configured before the exit 0 line.

VM instances fail to be created in a normal environment. What should I do?

1. Identify whether WebSocket client is installed. If WebSocket client is not installed, identify whether controller cluster has rebooted.

2. If controller cluster has rebooted, restart the neutron-server service and then create VM instances.

As a best practice, install WebSocket client and enable WebSocket client connection with the controller RPC service to prevent data loss in a controller cluster reboot.

In what scenarios do I need to install the Nova patch

You need to install the Nova in the following scenarios:

· In the KVM host- or network-based overlay scenario, a VM is a member of the load balancer, and the load balancer is required to detect the member status.

· vCenter network-based overlay scenario.

For the patch configuration method, see H3C SeerEngine-DC Controller OpenStack Plug-Ins Installation Guide for CentOS or H3C SeerEngine-DC Controller OpenStack Plug-Ins Installation Guide for Ubuntu. For the patch installation procedure, see "Installing the SeerEngine-DC Neutron plug-ins."

In what scenarios do I need to install the openvswitch-agent patch

The open source openvswitch-agent process on an OpenStack compute node might fail to deploy VLAN flow tables to open source vSwitches when the following conditions exist:

· The KVM technology is used on the node.

· The hierarchical port binding feature is configured on the node.

To resolve this issue, you must install the openvswitch-agent patch.

I find that easy_install is not in the same path as neutron when I am to install the Neutron plug-in on open-source OpenStack Wallaby and Xena with Kolla. What should I do?

This procedure is performed in the environment where the CentOS Stream 8 operating system runs and python3.6.8 is used.

1. Access the neutron_server container.

[root@localhost ~]# docker exec -it -u root neutron_server bash

2. Upgrade the setuptools version to 50.3.2.

(neutron-server)[ root@localhost ~]# /var/lib/kolla/venv/bin/python -m pip install --upgrade setuptools==50.3.2

3. Copy easy_install to the virtual environment bin directory and rename it as easy_install_h3c to avoid conflict.

(neutron-server)[ root@localhost ~]# cp /usr/bin/easy_install /var/lib/kolla/venv/bin/easy_install_h3c

4. Use the vi editor to open the easy_install_h3c configuration file.

(neutron-server)[ root@localhost ~]# vi /var/lib/kolla/venv/bin/easy_install_h3c

5. Press I to switch to insert mode, and replace the first line #!/usr/libexec/platform-python with #!/var/lib/kolla/venv/bin/pythoned .

6. Press Esc to quit insert mode, and enter :wq to exit the vi editor and save the easy_install configuration file.

7. Execute the following command to verify that the plug-in is in the same directory as the neutron.

(neutron-server)[ root@localhost ~]# easy_install_h3c --version

setuptools 50.3.2 from /var/lib/kolla/venv/lib/python3.6/site-packages (Python 3.6)

8. Execute the easy_install_h3c command to install the plug-in package.

(neutron-server)[ root@localhost ~]# easy_install_h3c SeerEngine_DC_PLUGIN-E3608-py2.7.egg

CAUTION:

After easy_install_h3c is used for installation of the plug-in, you must use easy_install_h3c rather than easy_install for later installations of the plug-in.

I find that python3-websocket-client is not in the same path as neutron when I am to install the Neutron plug-in on open-source OpenStack Wallaby and Xena with Kolla. What should I do?

This procedure is performed in the environment where the CentOS Stream 8 operating system runs and python3.6.8 is used.

1. Obtain the websocket and neutron paths in the container.

(neutron-server)[root@localhost /]# python

Python 3.6.8 (default, Jan 19 2022, 23:28:49)

[GCC 8.5.0 20210514 (Red Hat 8.5.0-7)] on linux

>>> import websocket

>>> websocket.__path__

['/usr/lib/python3.6/site-packages/websocket']

>>> import neutron

>>> neutron.__path__

['/var/lib/kolla/venv/lib/python3.6/site-packages/neutron']

2. If the WebSocket path is different from the neutron path, perform the following procedure. If the paths are the same, websocket-client can be used.

3. Uninstall the python3-websocket-client installed with yum.

(neutron-server)[root@localhost /]# yum remove python3-websocket-client

4. View the pip3 path in the container. If the pip3 path is consistent with the neutron path, use pip3 to install python3-websocket-client.

Ensure Internet connectivity for python3-websocket-client installation.

(neutron-server)[root@localhost /]# pip3 -V

pip 21.3.1 from /var/lib/kolla/venv/lib/python3.6/site-packages/pip (python 3.6)

(neutron-server)[root@localhost /]# pip3 install websocket-client==0.56.0

5. If the websocket-client still cannot be used, contact technical support.

If information for connecting the Neutron database is encrypted, the Neutron plug-ins might fail to inherit the portforwardings data table because of failure to access the database. What should I do?

To resolve the issue:

1. Uninstall the Neutron plug-ins.

(neutron-server) [root@localhost ~]# h3c-sdnplugin controller uninstall

2. Reinstall the Neutron plug-ins and specify the db_connection parameter.

To obtain the value of the db_connection parameter, access the neutron.conf file and identify the value of the connection parameter under the database group. The password for accessing the Neutron database is encrypted in the value. Change it to the unencrypted password.

(neutron-server) [root@localhost ~]# h3c-sdnplugin controller install --db_connection mysql+pymysql://neutron:PASSWORD@controller/neutron

connection = mysql+pymysql://neutron:PASSWORD@controller/neutron

H3C SeerEngine-DC Controller Converged OpenStack Plug-Ins Installation Guide for Containers-E63xx-5W307

SeerEngine-DC Neutron security plug-ins

Hardware requirements

Installing OpenStack plug-ins by using Kolla Ansible

Installing the SeerEngine-DC Neutron plug-ins

Parameters and fields

Upgrade with the neutron_server container removed

neutron_conf

Upgrade with neutron_server container removed

Upgrade with neutron_server container retained

Obtaining the SeerEngine-DC Neutron plug-in installation package

Obtaining the containerized installation and deployment script of the plug-ins

Installing the SeerEngine-DC Neutron plug-ins on the neutron-server nodes in Kubernetes

Checking the controller node state

Obtaining the installation package for SeerEngine-DC Neutron security plug-in

Obtaining the containerized security plug-in installation script

Installing the SeerEngine-DC Neutron security plug-in in Kubernetes neutron-server

Restarting the neutron-server pod

To resolve the issue:

In what scenarios do I need to install the Nova patch

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us