networking-fujitsu

FUJITSU plugins/drivers for OpenStack Neutron.

ML2 driver for FUJITSU Converged Fabric Switch(CFX2000)

How to Install

pip install networking-fujitsu

Configuration

Please edit /etc/neutron/plugins/ml2/ml2_conf.ini as follows:

  1. Add fujitsu_cfab to mechanism_drivers option.

    mechanism_drivers = openvswitch,fujitsu_cfab
    
  2. Both type_drivers and tenant_network_types in [ml2] section should include vlan. Only VLAN network type is supported.

    [ml2]
    type_drivers = vlan
    tenant_network_types = vlan
    
  3. The following parameters should specify after [fujitsu_cfab] section.

address

The IP address or the host name of the CFX2000 to connect to using telnet protocol. This is a mandatory parameter and it has no default value. Only one address can be specified.

address = 192.168.0.1
username

The CFX2000 username to use. Please note that the user must have administrator rights to configure CFX2000. The default value is admin.

username = admin
password

The CFX2000 password to use. The default value is admin.

password = admin
physical_networks

List of <physical_network>:<vfab_id> tuples specifying physical network names and corresponding VFAB IDs. All possible physical network names must be specified in this parameter. If a physical network name not specified in this parameter is used, a runtime exception will be raised. It is valid to use same VFAB ID for different physical networks as long as VLAN IDs are exclusive. Please note that VFAB must be created and configured in CFX2000 beforehand.

physical_networks = physnet1:1,physnet2:2
share_pprofile

Whether to share a CFX2000 pprofile among Neutron ports using the same VLAN ID. If it is true, the pprofile name will be based on the VLAN ID, and the pprofile will be used for all Neutron ports using the same VLAN ID. If it is false, the pprofile name will be based on the MAC address, and each Neutron port will use dedicated pprofile. The default value is False.

share_pprofile = True
pprofile_prefix

The prefix string for pprofile names. The pprofile name will be “<pprofile_prefix> + <vlan_id>” or “<pprofile_prefix> + <MAC_address>” according to the share_pprofile parameter. If pprofile_prefix is specified, the mechanism driver will not use the existing pprofiles which do not have the prefix. If pprofile_prefix is not specified, the mechanism driver will use the existing pprofile if it corresponds to the VLAN ID when share_pprofile is true, or if the name ends with the MAC address when share_pprofile is false.

pprofile_prefix = neutron-
save_config

Whether to save configuration. If it is true, CFX2000’s configuration will be saved every time the configuration is committed. The default value is True.

save_config = False

CFX2000 Configuration

As well as the standard configuration of CFX2000, the following configurations are needed for the mechanism driver.

  1. Enable AMPP using ARP/DHCP.

    By default, only RARP packets are examined for AMPP. It is possible to add ARP/DHCP packets to be examined for AMPP.

    evb ampp arp on
    evb ampp dhcp on
    

    Note

    evb ampp dhcp is not supported in earlier versions of CFX2000 firmware. Therefore, please create the subnet with enable_dhcp is FALSE before ampp dhcp function is supported.

  2. Create and configure VFABs.

    It is necessary to create and configure the VFAB beforehand. It is recommended that the ports connected to the network nodes are configured as VLAN through mode.

    ifgroup 0 ether 1/1/0/1-1/1/0/18
    ifgroup 1 ether 1/1/0/19-1/1/0/26
    ifgroup 2 ether 1/2/0/1
    vfab 1 cir-ports ifgroup 1
    vfab 1 ampp-area 0
    vfab 1 through ifgroup 2
    interface 1/2/0/1
    vfab through mode on
    

    Note

    vfab through commands are only available on CFX2000 firmware V02.30 and later.

Baremetal provisioning

CFX2000 driver also supports baremetal tenant network isolation. This feature is available on firmware V02.40 and later. In order to use this feature, the following pre-configuration is necessary:

Configure network mode for VFAB which is specified as physical_networks.

vfab 1 mode network

Note

While baremetal provisioning is running, PLEASE DO NOT EDIT CFX2000 configuration directory.

ML2 driver for FUJITSU FOS Switch(Draft)

How to Install

pip install networking-fujitsu

Neutron Configuration

Note

Please edit /etc/neutron/plugins/ml2/ml2_conf.ini as follows: Following configurations are common to all FOS switches in fossw_ips.

Add fujitsu_fossw to mechanism_drivers option.

mechanism_drivers = openvswitch,fujitsu_fossw

Both type_drivers and tenant_network_types in [ml2] section should include vlan or vxlan. (This driver supports VLAN and VXLAN of neutron network)

[ml2]
type_drivers = vlan,vxlan
tenant_network_types = vlan,vxlan

The following parameters should specify after [fujitsu_fossw].

fossw_ips (Mandatory)
The List of IP addresses of all FOS switches.
fossw_ips = 192.168.0.1,192.168.0.2,...
username (Mandatory)
The FOS switches username to use. Please note that the user must have administrator rights to configure FOS switches.
username = admin
password (Optional)
The FOS switches password to use.
password = admin
port (Optional)
The port number which is used for SSH connection. The default value is 22.
port = 22
timeout (Optional)
The timeout of SSH connection. The default value is 30.
timeout = 30
udp_dest_port (Optional)
The port number of VXLAN UDP destination on the FOS switches. All VXLANs on the switches use this UDP port as the UDP destination port in the UDP header when encapsulating. The default value is 4789.
udp_dest_port = 4789
ovsdb_vlanid_range_min (Optional)
The minimum VLAN ID in the range that is used for binding VNI and physical port. The range of 78 VLAN IDs (starts from this value) will be reserved. The default value is 2 (VLAN ID from 2 to 79 will be reserved).
ovsdb_vlanid_range_min = 2

Note

DO NOT include VLAN IDs specified by ovsdb_vlanid_range_min into network_vlan_ranges in /etc/neutron/plugins/ml2/ml2_conf.ini.

ovsdb_port (Optional)
The port number which OVSDB server on the FOS switches listen. The default value is 6640.
ovsdb_port = 6640

FOS Switch Configuration

The following configurations are necessary for all FOS switches in case of VXLAN network.

  1. Enable IP routing.

    configure
    ip routing
    
  2. Enable vxlan service.

    vxlan enable
    
  3. Set VTEP IP address for switch side.

    vxlan vtep source-ip 192.167.3.111
    
  4. Set port number of VXLAN UDP destination, which is specified as udp_dest_port

    vxlan udp-dst-port 4789
    
  5. Set IP address for physical port which is connected to OpenStack controller node. The value of IP address equals to VTEP IP address of switch.

    interface 0/10
    ip address 192.167.3.111 255.255.255.0
    
  6. Enable routing of the physical port.

    routing
    
  7. Return to Privileged EXEC mode.

    end
    
  8. Set port number of OVSDB server in the FOS switch, which is specified as ovsdb_port.

    ovsdb
    ovsdb tcp port 6640
    
  9. Check ovsdb_vlanid_range_min and confirm that the VLAN ID within the range from ovsdb_vlanid_range_min to ovsdb_vlanid_range_min + 77 are not defined.

    show vlan
    
  10. Save configurations.

    copy system:running-config nvram:startup-config