Openstack L2 network components for VMware NSX-T (NSXv3)
This project allowes an OpenStack region to implement complex L2 network topology distributed accross many VMware NSX-T managers, where at the same time all these managers will share the same security context.
NSX-T ML2 Mechanism Dirver is an extension to the Modular Layer 2 (ml2) plugin framework. This driver enables OpenStack Neutron to simultaneously utilize NSX-T network technology in combination with other technologies to reach the goal of Hierarchical Port Binding.
NSX-T L2 Agent implements OpenStack network related events into VMware NSX-T constructions. - OpenStack network segments are mapped to NSX-T Logical Switches (VLAN backed) - OpenStack ports are mapped NSX-T Logical Ports - OpenStack port security is mapped to NSX-T IP Discovery and SpoofGuard Switching Profiles (applied per port) - OpenStack QoS Profiles are mapped to NSX-T QoS Switching Profiles - OpenStack Security Groups are mapped to NSX-T Firewall Sections, NS Groups and IP Sets - OpenStack Security Groups Rules are mapped to NSX-T Firewall Section Rules - OpenStack Security Groups Members are mapped to NSX-T IP Sets - OpenStack Security Groups Membership is mapped to NSX-T NS Groups Membership Tags
Control over the debug log of NSX-T DWF Rules
Use :
openstack network log create \
--target <port name/id> \
--resource <security group name / id> \
--resource-type security_group \
<name>
openstack network log set <name> [--enable | --disable]
openstack network log delete <name>
- Configuration:
- logging_url - Redis Cache url, defaults to unix:///var/run/redis/socket/redis.sock
- logging_expire - Redis key expiration time in days, defaults to 1 day
- Flow:
- On log create event or log enable event
- all rules for the resource security group will be updated to start logging
- every rule will use the OpenStack Rule ID as log label
- Redis cache will be updated (with default time out of 24h).
- Redis entry format:
- key (string) - "SG<security group ID>" (string)
- value (string) - "<project ID>" (string)
- On log delete event or log disable event
- all rules for the resource security group will be updated to stop logging
- Redis cache will be updated (with default time out of 24h)
# Install NSX-T 2.3 SDK (download SDK from VMware web site)
sudo pip install vapi_runtime-2.9.0-py2.py3-none-any.whl
sudo pip install vapi_common-2.9.0-py2.py3-none-any.whl
sudo pip install vapi_common_client-2.9.0-py2.py3-none-any.whl
sudo pip install nsx_python_sdk-2.3.0.0.0.10085514-py2.py3-none-any.whl
clone repo into /opt/stack :
cd ./networking-nsx-t
python setup.py install
Modify:
/etc/neutron/neutron.conf as described in /opt/stack/networking-nsx-t/etc/neutron/neutron.conf
/etc/neutron/plugins/ml2/ml2_conf.ini as described in /opt/stack/networking-nsx-t/etc/neutron/plugins/ml2/ml2_conf.ini
For Full list of the agent configuration options check:
/opt/stack/networking-nsx-t/networking_nsxv3/common/config.py
restart neutron server with NSX-T ml2 config:
/usr/local/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini
Start DVS agent:
/usr/local/bin/neutron-nsxv3-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini
openstack network qos policy create <qos_name>
openstack network qos rule create --type bandwidth-limit --max-kbps 64000 --max-burst-kbits 0 --ingress <qos_name>
openstack network qos rule set --max-kbps 64000 --max-burst-kbits 0 --ingress <qos_name> <id>
openstack network qos rule set --max-kbps 32000 --max-burst-kbits 0 --egress <qos_name> <id>
openstack network qos rule create --type dscp-marking --dscp-mark 26 <qos_name>
openstack network qos rule delete
openstack network qos policy delete <qos_name>
openstack security group create <sg_name>
openstack security group rule create --ingress --protocol tcp --remote-ip 192.168.253.253 --dst-port 8281 <sg_name>
openstack security group rule create --ingress --protocol tcp --remote-group <remote_sg_name> --dst-port 443 <sg_name>
openstack security group rule create --egress --protocol udp --remote-ip 192.168.253.253 --dst-port 8080 <sg_name>
openstack security group rule create --egress --protocol udp --remote-group <remote_sg_name> --dst-port 9443 <sg_name>
openstack security group rule create --protocol icmp
openstack security group rule delete <sg_rule_name>
openstack security group delete <sg_name>
openstack port create --network <network_name> \
--allowed-address "ip-address=192.168.253.10,mac-address=fa:16:3e:5f:7d:0b" \
--allowed-address "ip-address=192.168.253.10,mac-address=ff:16:3e:5f:7d:0b" \
--qos-policy <qos_policy_id> \
--security-group <sg_id> \
<port_name>
openstack server create --image <image_name> --flavor "1" --nic "port-id=<port_id>" <server-name>
openstack port create --network <network_native> <trunk_parent_port_name>
openstack port create --network <network_sub_1> \
--allowed-address "ip-address=192.168.253.10,mac-address=fa:16:3e:5f:7d:0b" \
--allowed-address "ip-address=192.168.253.10,mac-address=ff:16:3e:5f:7d:0b" \
--qos-policy <qos_policy_id> \
--security-group <sg_id> \
<trunk_subport_name_1>
openstack port create --network <netwrok_sub_2> \
<trunk_subport_name_2>
openstack network trunk create \
--parent-port <trunk_parent_port_id> \
--subport port=<trunk_subport_id_1>,segmentation-type=vlan,segmentation-id=100 \
--subport port=<trunk_subport_id_2>,segmentation-type=vlan,segmentation-id=200
openstack server create --image <image_name> --flavor "1" --nic "port-id=<trunk-parent-port-id>" <server-name>
Neutron ML2 NSX-T Agent command line interface
# Synchronize OpenStack resource Types with ids
/usr/local/bin/neutron-nsxv3-agent-cli -h
usage: neutron-nsxv3-agent-cli-sync COMMAND
update - Force synchronization between Neutron and NSX-T objects
export - Export Neutron and NSX-T inventories
load - Loads NSX-T Inventory and syncs Neutron inventory on top
clean - Clean up NSX-T objects
Neutron ML2 NSX-T Agent command line interface
positional arguments:
command Subcommand update|export|load|clean
optional arguments:
-h, --help show this help message and exit
# Example for synchronization of members for two security groups
/usr/local/bin/neutron-nsxv3-agent-cli update \
--config-file /etc/neutron/neutron.conf \
--config-file /etc/neutron/plugins/ml2/ml2_conf.ini \
--type security_group_members \
--ids 5af2f34b-cb81-4a9d-bcb4-30f72fca91cd,b0cd1ce8-9fe0-44f6-8b5c-be455e778756
# Clean up NSX-T Manager objects both Policy and Management
/usr/local/bin/neutron-nsxv3-agent-cli clean --config-file ml2.ini --config-file neutron.conf
# Export NSX-T and Neutron inventories into a local file structure under "inventory" folder
/usr/local/bin/neutron-nsxv3-agent-cli export --config-file ml2.ini --config-file neutron.conf
# Load NSX-T Manager from the local file inventory.
# Synchronize NSX-T Manager objects state based on the local file Neutron inventory
/usr/local/bin/neutron-nsxv3-agent-cli load --config-file ml2.ini --config-file neutron.conf
The agent exports the following metrics.
# HELP nsxv3_agent_active_queue_size Active synchronization queue size
# TYPE nsxv3_agent_active_queue_size gauge
nsxv3_agent_active_queue_size{nsxv3_manager_hostname="nsxm-l-01a.corp.local"} 4.0
# HELP nsxv3_agent_passive_queue_size Passive synchronization queue size
# TYPE nsxv3_agent_passive_queue_size gauge
nsxv3_agent_passive_queue_size{nsxv3_manager_hostname="nsxm-l-01a.corp.local"} 72.0
- Finalize migration to Policy API (applicable for NSX-T version >= 3.2.0)
- Change implementation of Logical Switces, Ports and Policies from Management to Policy API
- Promote Logical Switces, Ports and Policies to Segments by keeping the same system IDs
- Merge Security Group Logging from feature branch.
- Finalize the list of supported ICMP Rules by NSX-T .
- Add unit and functional tests for port trunking functionality
- Optimize the speed and number of Neutron DB queries