This change is follow-up of a6c4ba2c2b
and removes the template file which is no longer used since support for
networking-cisco was removed.
Change-Id: I60668906b6ed40c137c42c5e169d621878a63a70
Change to modify the cisco ml2 nexus section to remove the use
of the erb template for configuring the per-nexus switch ML2
config sections. The change adds 2 new defined types which
wrap neutron_plugin_ml2 resource usage.
Change-Id: I401371c9e5176de7ce19d4d4e878e9f2e69aab80
Closes-bug: #1495537
Add and update classes for Nexus, Nexus VXLAN, and UCSM drivers.
Use INI provider for driver config except for Nexus switch config.
Co-Authored-By: Tim Swanson <tiswanso@cisco.com>
Change-Id: I78ddc6795394c4ad2b4da9ab0a2c2a2eed18c25f
Adding ability to configure IPv6 control address of VSM,
in the n1kv.conf file, to enable N1kv VEM to talk to VSM
over IPv6
Change-Id: Iac92569ec19a879091111f78474aebb83292999d
This commit makes the following changes, mostly to specs to get them
passing on Puppet 4.x: removes redefinition of $name because it is now
a reserved word and redundant in Puppet 3.x, cleans up the use of
Puppet's old behavior of implicitly converting String to Integers
since Puppet 4.x is pretty strictly typed, sets facts required for
doing flow control and comparison, fixes implicit use of empty string
that is assumed to be the same as false by updating tests that inject
empty string into params to represent a value not being provide by a
user to false instead.
Closes-bug: #1447620
Change-Id: Ibb651f26f33549dbe564dc88167b8f578a03fd77
Also need to remove installing explicit installation of openvswitch
and call vswitch::ovs instead.
Adding testcases to neutron_agents_n1kv_vem_spec.rb and fixing an
error in neutron_plugins_ml2_spec.rb
Change-Id: I2b4ada801610d7081ac3e2469bcacd6ea5ec8e7d
Closes-Bug: 1421449
Background on 'N1KV-VEM’: It is the host-side component of N1KV
implementing the notion of Virtual Ports for VM Interfaces and also
handling the VM data-traffic. VEM is implemented as a couple of
user-space processes and also has a KLM for efficient data-path
switching.
VEM manifests does: setting up the Config-File for VEM service,
Starting VEM service and finally adding physical ports (along with
port-profile) to the VEM
Change-Id: Ibc8f1c4d2d743589e452ae6d1d87b5bfa123bc3a
Takashi Kajinami