UCSM Mechanism Driver¶
The following list of variables are used by the cisco_ucsm mechanism driver. A variable’s default value can be changed by adding it to the configuration file included on the neutron-server command line. The sample ucsm configuration file is described here, Sample UCSM Mechanism Driver.
ml2_cisco_ucsm¶
-
ucsm_ip
¶ Type: string Default: <None>
Cisco UCS Manager IP address. This is a required field to communicate with a Cisco UCS Manager.
-
supported_pci_devs
¶ Type: list Default: 1137:0071,8086:10c9
SR-IOV and VM-FEX vendors to be handled by the driver. xxxx:yyyy represents vendor_id:product_id of the PCI networking devices that the driver needs to handle. It is implicit that the SR-IOV capable devices specified here should be supported on the UCS platform.
-
ucsm_https_verify
¶ Type: boolean Default: true
The UCSM driver will always perform SSL certificate checking on the UCS Managers that it is connecting to. This checking can be disabled by setting this global configuration to False. Disabling this check will leave the connection to UCS Manager insecure and vulnerable to man-in-the-middle attacks.
-
ucsm_username
¶ Type: string Default: <None>
Username for UCS Manager. This is a required field to communicate with a Cisco UCS Manager.
-
ucsm_password
¶ Type: string Default: <None>
Password for UCS Manager. This is a required field to communicate with a Cisco UCS Manager.
-
ucsm_virtio_eth_ports
¶ Type: list Default: /ether-eth0,/ether-eth1
Ethernet port names to be used for virtio ports. This config lets the Cloud Admin specify what ports on the UCS Servers can be used for OpenStack virtual port configuration. The names should match the names on the UCS Manager.
-
ucsm_host_list
¶ Type: dict Default: <None>
Hostname to Service profile mapping for UCS Manager controlled hosts. This Service profile should not be associated with a Service Profile Template. If the Service Profile is not specified with a path, the driver assumes that it is at the root level on the UCSM. For example: Hostname1:Serviceprofile1, Hostname2:Serviceprofile2
-
sriov_qos_policy
¶ Type: string Default: ${ml2_cisco_ucsm.sriov_qos_policy}
A pre-defined QoS policy name. This optional config allows the cloud admin to pre-create a QoS policy on the UCSM. If this config is present, the UCSM driver will associate this QoS policy with every Port profile it creates for SR-IOV ports.
-
sp_template_list
¶ Type: unknown type Default: <None>
Service Profile Template config for this UCSM. The configuration to be provided should be a list where each element in the list represents information for a single Service Profile Template on that UCSM. Each element is mapping of a Service Profile Template’s path, its name and a list of all UCS Servers controlled by this template. For example: sp_template_list = SP_Template1_path:SP_Template1:Host1,Host2 SP_Template2_path:SP_Template2:Host3,Host4 This is an optional config with no defaults
-
vnic_template_list
¶ Type: unknown type Default: <None>
VNIC Profile Template config per UCSM. Allows the cloud admin to specify a VNIC Template on the UCSM that is attached to every vNIC connected to a specific physical network. Each element in this list has 3 parts: the physical network that is defined in neutron configuration, the VNIC Template with its path in UCSM, the vNIC on the UCS Servers that is connected to this physical network. For example: vnic_template_list = physnet1:vnic_template_path1:vt1 physnet2:vnic_template_path2:vt2 This is an optional config with no defaults.
ml2_cisco_ucsm_ip:<ip_address>¶
-
ucsm_username
¶ Type: string Default: <None>
Username for UCS Manager. This is a required field to communicate with a Cisco UCS Manager.
-
ucsm_password
¶ Type: string Default: <None>
Password for UCS Manager. This is a required field to communicate with a Cisco UCS Manager.
-
ucsm_virtio_eth_ports
¶ Type: list Default: /ether-eth0,/ether-eth1
Ethernet port names to be used for virtio ports. This config lets the Cloud Admin specify what ports on the UCS Servers can be used for OpenStack virtual port configuration. The names should match the names on the UCS Manager.
-
ucsm_host_list
¶ Type: dict Default: <None>
Hostname to Service profile mapping for UCS Manager controlled hosts. This Service profile should not be associated with a Service Profile Template. If the Service Profile is not specified with a path, the driver assumes that it is at the root level on the UCSM. For example: Hostname1:Serviceprofile1, Hostname2:Serviceprofile2
-
sriov_qos_policy
¶ Type: string Default: ${ml2_cisco_ucsm.sriov_qos_policy}
A pre-defined QoS policy name. This optional config allows the cloud admin to pre-create a QoS policy on the UCSM. If this config is present, the UCSM driver will associate this QoS policy with every Port profile it creates for SR-IOV ports.
-
sp_template_list
¶ Type: unknown type Default: <None>
Service Profile Template config for this UCSM. The configuration to be provided should be a list where each element in the list represents information for a single Service Profile Template on that UCSM. Each element is mapping of a Service Profile Template’s path, its name and a list of all UCS Servers controlled by this template. For example: sp_template_list = SP_Template1_path:SP_Template1:Host1,Host2 SP_Template2_path:SP_Template2:Host3,Host4 This is an optional config with no defaults
-
vnic_template_list
¶ Type: unknown type Default: <None>
VNIC Profile Template config per UCSM. Allows the cloud admin to specify a VNIC Template on the UCSM that is attached to every vNIC connected to a specific physical network. Each element in this list has 3 parts: the physical network that is defined in neutron configuration, the VNIC Template with its path in UCSM, the vNIC on the UCS Servers that is connected to this physical network. For example: vnic_template_list = physnet1:vnic_template_path1:vt1 physnet2:vnic_template_path2:vt2 This is an optional config with no defaults.
sriov_multivlan_trunk¶
-
network_vlans
¶ Type: unknown type Default: <None>
SR-IOV Multi-VLAN trunk config section is an optional config section to accomodate the scenario where an application using an SR-IOV port to communicate would like to send traffic on multiple application specific VLANs not known to OpenStack. This config section is applicable across all UCSMs specified as part of the OpenStack cloud. The names of the neutron networks on which the SR-IOV ports are going to be created have to be known ahead of time and should be associated with a list or range of application VLANs using the following format: <neutron network name>=<comma separated list of VLAN-ids or VLAN-id ranges> For example: test_network1=5,7-9