
8
c334f7ec9857 kolla/centos-source-h3c-agent: pike "dumb-init --single-? 1
minutes ago Up 1 minutes h3c_agent
Parameters and fields
This section describes parameters in the
ml2_conf.ini
configuration file and fields included in
parameters.
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.
•
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.
For intranet, only
vxlan
is available.
For extranet, only
vlan
is available.
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 (The Ocata
2017.1 plug-ins do 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.