Networking Mlnx Baremetal 1.0.2

Description:

networkingmlnxbaremetal 1.0.2

networking-mlnx-baremetal

Overview
This project aims to provide a OpenStack Neutron ML2 mechanism driver for
binding or unbinding partition key for mellanox infiniband port when
provisioning baremetal node using OpenStack Ironic component.
Those baremetal nodes are expected to have “VLAN” or “VXLAN” ethernet segment
bound by other driver[1], and networking-mlnx-baremetal will bind partition
key which have exactly the same segmentation-id as former ethernet segment for
Mellanox infiniband ports on the same node.
This hierarchical network topologies is supported by Neutron and mentioned
on spec Hierarchical Port Binding. The final network topology looks like:
+-----------------+ +-------------+
| Mellanox Switch | | Core Switch |
+---+-----+-------+ +-------+-----+
| | |
| | |
| | +------+-----+
| | | ToR Switch |
| | +--+------+--+
| | |
| | | |
| | | |
| | IB +--------------+ eth | |
| +------+ Ironic Node +------+ |
| PKey +--------------+ VXLAN |
| |
| IB +--------------+ eth |
+------------+ Ironic Node +-------------+
PKey +--------------+ VXLAN

Currently, this driver is only tested along with networking-huawei driver
and Ironic ramdisk deploy interface on OpenStack stable/train release.

Installation
Before using this driver, it should be installed on OpenStack Neutron
controller node. You may install it:
From PyPi:
$ pip install networking-mlnx-baremetal
or
$ easy_install networking-mlnx-baremetal
Or from source:
$ git clone https://github.com/IamFive/networking-mlnx-baremetal.git
$ cd networking-mlnx-baremetal
$ git checkout stable/train
$ pip install -r requirements.txt -c upper-constraints.txt
$ python setup.py install

Usage

Configuration
This driver will load configuration options in two namespaces:

mlnx.baremetal.driver: configuration options for driver itself
mlnx.ironic.client: configuration options for connecting to Ironic controller

So, after networking-mlnx-baremetal is installed, you may run this
command to get a full list of mlnx.baremetal.driver configuration options:
$ oslo-config-generator --namespace mlnx.baremetal.driver
The default configurations may looks like:
[DEFAULT]

[mlnx:baremetal]

#
# From mlnx.baremetal.driver
#

# UFM REST API endpoint. (string value)
#endpoint = http://127.0.0.1

# Username for UFM REST API authentication. (string value)
#username = <None>

# Password for UFM REST API authentication. (string value)
#password = <None>

# Either a Boolean value, a path to a CA_BUNDLE file or directory with
# certificates of trusted CAs. If set to True the driver will verify
# the UFMhost certificates; if False the driver will ignore verifying
# the SSL certificate. If it's a path the driver will use the
# specified certificate or one of the certificates in the directory.
# Defaults to True. Optional. (string value)
#verify_ca = True

# HTTP timeout in seconds. (integer value)
#timeout = 10

# Comma-separated list of physical_network which this driver should
# watch. * means any physical_networks including None. (list value)
#physical_networks = *
Of course, you should generate options for mlnx.ironic.client too, then
update those options and add them to neutron config-file.

Enable driver
The entry point name of this driver is mlnx_ib_bm. To enable, add
mlnx_ib_bm to ML2 mechanism driver list:
[ml2]
tenant_network_types = vxlan
mechanism_drivers = mlnx_ib_bm,other_vxlan_driver,...,openvswitch

Config Ironic-Inspector
By default, inspector will only detect PXE port information. To also get
infiniband port, add_port should be set to all.
[processing]
processing_hooks = $default_processing_hooks,extra_hardware,lldp_basic,local_link_connection
add_ports=all
Also, remember Mellanox infiniband hardware driver should be packaged in
inspect ramdisk image.