Cisco VTS General Parameters

This section provides details about the Cisco VTS general parameters.

##################
### VTS General ###
### VTSPassword: 'Cisco123!'
###################

VTSUsername: 'admin'
VTSPassword: 'YLdKnf3qSsKA2JWQT9a0Sg=='
VTSServer: '30.30.30.3'
VTSVMMID: 'c958399f-5af6-3517-b902-771b7c1d37e6'

Neutron ML2 Parameters

This section provides details about the Neutron ML2 parameters.

###################
### Neutron ML2 ###
###################
NeutronCorePlugin: 'neutron.plugins.ml2.plugin.Ml2Plugin' 
NeutronMechanismDrivers: 'sriovnicswitch,cisco_vts' 
NeutronTypeDrivers: 'vxlan,vlan,flat' 
NeutronServicePlugins: 'cisco_vts_router,trunk'


#NeutronInterfaceDriver: ‘cisco_controller.drivers.agent.linux.interface.NamespaceDriver'

• NeutronCorePlugin—This is the Core neutron plugin for neutron tenant network. Default value is “neutron.plugins.ml2.plugin.Ml2Plugin”.

• NeutronMechanismDrivers—These are the mechanism drivers for neutron tenant network. To specify multiple values, use a comma-separated string. To enable VTS-specific mechanism driver, add cisco_vts to this list. For enabling SR-IoV interfaces on the compute, add sriovnicswitch.

• NeutronTypeDrivers—These are the tenant network types for neutron tenant network. To specify multiple values, use a comma-separated string.

• NeutronServicePlugins—This is the neutron service plugin for neutron tenant network. To enable L3 networking, add cisco_vts_router. To enable trunk mode operation (VLAN aware VMs) add trunk to the list of type drivers.

• NeutronInterfaceDriver—Specifies the interface driver used by the Neutron DHCP Agent. When deploying the VTF on nodes running the Neutron DHCP Agent this setting needs to be passed (uncommented). Valid values are (default) ‘neutron.agent.linux.interface.OVSInterfaceDriver’ and ‘cisco_controller.drivers.agent.linux.interface.NamespaceDriver'.

This section provides details about the VTS Agent parameters.

########################
### VTS Agent Config ###
########################
VTSPhysicalNet: 'physnet101'
VTSRetries: 15
VTSTimeout:
VTSPollingInterval: 6

• VTSPhysicalNet—VTSPhysicalNet should be set to the ‘physnet’ used for the tenant networks for OVS on the compute. The environment file in the Heat templates should have the mapping of the tenant OVS bridge to the physnet name.

• VTSRetries—Number of times VTS agent retries a neutron request. Default is 15.

• VTSTimeout—Cisco VTS agent times out a request. Default value is 120 seconds.

• VTSPollingInterval—Cisco VTS agent polling interval for a request. Default value is 6 seconds.

VPFA Configuration Parameters

This section provides details about VPFA configuration parameters. These are mandatory to be configured

###################
### VPFA Config ###
###################
UnderlayIpNewtorksList: '21.0.0.0/8,10.10.10.0/24,50.50.0.0/16,40.40.0.0/16,42.42.42.0/24' 
VTSR_u_IpAddressList: '10.10.10.133,10.10.10.134'
VPFAHostname: '<some_name>'
NetworkConfigMethod: 'static'
NetworkNameServerIP: '' 
VifTypeCompute: 'vhostuser'
VifTypeController: 'tap'

• UnderlayIpNetworksList—List of underlay IP networks for VTF reachability. To specify multiple values, use a comma-separated string.

• VTSR_u_IpAddressList—List of underlay IP address assigned to VTS.

• VPFAHostname—Hostname assigned to VPFA.

• NetworkConfigMethod—VPFA network configuration method. Default value is “static”.

• NetworkNameServerIP—DNS IP assigned to VPFA.

• VifTypeCompute—VPFA VIF type for compute is “vhostuser”.

• VifTypeController—VPFA VIF type for Controller node is “tap”.

VPP Configuration Parameters

This section provides details about VPP configuration parameters.

#####################################
### VPP Configuration Parameters ###
#####################################
## MTU for Tun/tap interfaces 
VppTunTapMtu: '9000'
##The CPUs listed below need to be part of the grub isol CPU list (configured elsewhere) 
VppCpuMainCoreController: '6'
VppCpuMainCoreCompute: '6'
## Comma delimited workers list 
VppCpuCorelistWorkersCompute: '7,8,9'
VppCpuCorelistWorkersController: '7,8,9'
## Avoid dumping vhost-user shared memory segments to core files
VppVhostUserDontDumpMem: True

Note	All CPU values given above are examples and need to be adapted to the actual deployment, or left commented out (that is, these are optional).

• VppTunTapMtu—MTU for VPP tap interface.

• VppCpuMainCoreController—Pin VPP to a CPU core on controller.

• VppCpuMainCoreCompute—Pin VPP to a CPU core on compute.

• VppCpuCorelistWorkersCompute—Pin VPP worker threads to a CPU core on compute.

• VppCpuCorelistWorkersController—Pin VPP worker threads to a CPU core on controller

• VppVhostUserDontDumpMem—Do not dump vhost-user memory segments in core files.

PerNodeData Parameters

PerNodeData: |
    {
      "< Node1 UUID >": {
          "cisco_vpfa::vtf_underlay_ip_v4": "10.0.0.2",
          "cisco_vpfa::vtf_underlay_mask_v4": "24",
          "cisco_vpfa::network_ipv4_gateway": "10.0.0.1"},
      "< Node2 UUID >": {
          "cisco_vpfa::vtf_underlay_ip_v4": "10.0.0.3",
          "cisco_vpfa::vtf_underlay_mask_v4": "24",
          "cisco_vpfa::network_ipv4_gateway": "10.0.0.1"}
    }

• UUID—Immutable machine UUID derived from Step 2 for the overcloud node.

• “cisco_vpfa::vtf_underlay_ip_v4”—Underlay IPv4 address assigned to VTF.

• "cisco_vpfa::vtf_underlay_mask_v4"—Underlay IPv4 netmask assigned to VTF.

• "cisco_vpfa::network_ipv4_gateway"—Underlay IPv4 network gateway assigned to VTF.