... because it was required for very old versions of Ubuntu and Debian
and no longer required in recent versions.
Change-Id: Ib5d3ab7cd79470e446a13475d5886c76048bfe5b
It turned out the external_ids property is not reflected on the ovs
bridge after initial creation. This change fixes it and ensures that
the property is applied to the bridge.
Closes-Bug: #1958905
Change-Id: I7c1c2384b8d70b568caffe8d3cc82002cf2502f6
This change implements unit tests for the exec resource which was added
by [1].
[1] 1fe71cf5e359c8f83f11b2673620be822423bf47
Change-Id: I1dd62d917783f66b11e953ab1c8be6a259553782
This change adds support for other_config:dpdk-socket-limit, which
is available since openvswitch 2.12.0[1].
[1] https://github.com/openvswitch/ovs/commit/8411b6ccec
Change-Id: I6a8c65685442477d368820cbb7fcc3a21cddbedd
dpdk-socket-mem accepts a comma-separated list of memory amounts per
socket. This change allows usage of native Array to define per-socket
amounts.
Change-Id: I8faeb44b708cf371e98b56a375a6dcc07d82df3e
Some parameters like vlan_limit or hw-offload expect integer values
and boolean values. However current vs_config accepts only strings
and we need to convert integer or boolena to string in manifests
explicitly.
This change makes vs_config accept integers and booleans so that
we can use more "native" types to define values.
Change-Id: I6f1dfd33cc85d84a53e346f45359ce382e5fda26
This change ensures hardware offload is disabled. Previously when
hw_offload is false, puppet-vswitch didn't manage the configuration,
thus offload was kept enabled if it was enabled in advance.
Change-Id: I654c0f7f5a5efb845484cb610ff07effd4f33aa9
$::os_service_default is not used in puppet-vswitch. This change
deprecates usage of it to prepare replacing it by undef, which is
commonly used instead.
Change-Id: Ibfe94720e28f5ce46977b2db2afa82a6888c28cb
This change defines manifest_dir and module_path expicitly in unit
tests so that modules installed under fixtures directory is properly
loaded.
Closes-Bug: #1930403
Change-Id: I549c03eebd718994f39831d24387a928bc109c08
These two distros are never tested in gate, and there are almost no
activities to keep these support updated for a while.
Change-Id: I6110cd9a62f33e2d046fc2c835aaec73c4532889
There are no requirement of service restart after updating
the cmd-insert-inv-prov parameter in ovs documentation[1], and
it seems that the parameter can be applied with keeping the service
running.
[1] https://docs.openvswitch.org/en/latest/topics/dpdk/bridge/#emc-insertion-probability
Let's remove notify so that changing the value doesn't trigger
service restart.
Change-Id: I2e9f7d3b27547d33914f07005045b55d8ba82514
This change implement support for the hw-offload option in dpdk. This
parameter is already supported in non-dpdk deployment but is also valid
for dpdk deployment.
Change-Id: Ibd285bf73fa10e6e9cd338625662063dc9a1d753
This change introduces support for the vlan_limit option.
This parameter is currently set to 1 by default, but we should set
it to 2 to enable vlan_transparent, which requires nested vlans.
Related-Bug: #1918418
Change-Id: Id9aaab2a1e3ad2d2d43cd5cddf389d20abaf4461
We're referencing some additional $::os facts that we need to properly
set for openstacklib to work with.
Change-Id: I00e5caf3cf5409ec4a12695750960900e721e9f5
In pike release, we have migrated manifests from ovs2.5 to ovs2.6 and
retained the backward compatibility. Removing the ovs2.5 changes
in this cycle as it is no longer used.
Change-Id: I286b2f4d090dda34ec95f24f77baefcb7687ff85
New type for configuring SSL in OVS. Bootstrap mode allows the switch
to accept an initial CA certificate offered by the controller.
Otherwise specify the location of the CA certificate to use in comparing
the controller's cert. OVS only supports a single instance of SSL
configuration so the provider limits the resource declaration to a
single instance named 'system'.
Partially-Implements: blueprint opendaylight-ssl-support
Change-Id: Ic026ee0bc4f385e0f8cd7076b3044feeb935ae45
Signed-off-by: Tim Rozet <trozet@redhat.com>
Ovs 2.8 has support for hardware offload [1]
This patch provides an option to configure it.
[1] https://patchwork.ozlabs.org/patch/767853/
Change-Id: I3c0d24a31f0a1cac2cb8c5da8125051d4348eed6
In OvS 2.7, setting dpdk-init=true enables DPDK
and reconfigures the vswitch with the dpdk parameters
earlier configured in ovsdb. In order to avoid
restarting openvswitch after enabling DPDK and to
use this feature, all the dpdk parameters shall be
configured in ovsdb before enabling DPDK.
Change-Id: I3a33f8287bbabe2bcaf7f4556dd78d5b9d6914b6
Signed-off-by: Karthik S <ksundara@redhat.com>
Configuration of DPDK parameters pmd-cpu-mask, dpdk-lcore-mask,
dpdk-socket-mem are addressed as per OVS2.6, while maintaining
backward compatibility with OVS 2.5
Implements: blueprint ovs-2-6-dpdk
Change-Id: I3227189691df85f265cf84bd4115d8d4c9f979f3
Signed-off-by: karthik s <ksundara@redhat.com>
The deprecated parameter 'core_list' shall be removed for Pike
Closes-Bug: #1664859
Change-Id: I2329aa122b9cacb3c7de18a21353f53ea1d988ed
Signed-off-by: karthik s <ksundara@redhat.com>
According to info in https://bugs.launchpad.net/tripleo/+bug/1640812
when setting a OVS bridge with physical interface we need to
define fail_mode in OVS_EXTRA parameter of ifcfg to make
sure it's set at the desired mode after reboot.
This patch adds new parameter fail_mode to vs_port (as ifcfg is created
as part of vs_port, not vs_bridge) and defaults it to required value "standalone".
Similar patch was implemented to os-net-config in
e479535b50
Change-Id: I5f7448e3504c9190d7fe5f4a7958c604ef91a058
Closes-Bug: #1656795
The parameter -l in DPDK_OPTIONS is applied to both list cores to be
used by PMD and the list of cores that all the OVS threads should run
on. This will impact the DPDK performance, as cores on which PMD are
running, should be completely isolated (no other process should) use
it. For this, we are configuring, -l option with list of host cpus and
the list PMD cores will be configured using ovs-vsctl config command.
Fixes-Bug: #1649836
Change-Id: Ib95281bcbde34c18d26ee11d4e2603b267db563b
The change Ie3ee722b9fe6b5b1798fa52bd68ae3b656a8bdf8 switched the
default Ubuntu version that we test from trusty to xenial. Unfortunately
the vswitch::ovs tests assumed trusty for the platform params and were
not properly checking against trusty vs xenial. This change updates the
default platform params for Ubuntu to reflect the differences.
Change-Id: I88333bb571a924ad192aca86aa032c86a509a989
- use ::vswitch::params for service parameters
- on debian jessie openvswitch has now proper init scripts
with status. This patch avoids restarting ovs on each
puppet run on jessie.
- this patch breaks debian versions older than wheezy
(which are not supported by debian anymore)
Change-Id: I48c81b9987935c848009b4bf3ed010c70ab1a404
Co-Authored-By: Alex Schultz <aschultz@redhat.com>
This change updates the testing for puppet-vswitch to leverage the
rspec-puppet-facts to test all operatingsystems supported by Puppet
Openstack.
Change-Id: Ic2dec231d2dc2a06d9eb656ffc0f9411f8dc614e
This change updates the module to use the rspec-puppet-facts as defined
in the puppet-openstack_spec_helper.
Change-Id: I6df0fb713772b68249eb38051f3a275e9d75336f
For Red Hat family, the OVS with DPDK will be provided
in the same package as OVS, named as openvswitch. This
is applicable for OVS2.5 version onwards, targeted for
newton. As of now, Ubuntu is packaging DPDK separately.
After getting clarity on Ubuntu DPDK packaging, the
required changes will be done for Ubuntu also, if any.
Change-Id: I91feedd48949aac520c719ab589a1542462ff887
driverctl will be used to bind the pci with the DPDK driver,
but the DPDK driver modules has to be loaded for it. Adding
sysconfig modules files to load driver module on reboot.
Implements: blueprint tripleo-ovs-dpdk
Depends-On: I79308ac5949a47a707d42bb2566407b9e8adfb9c
Change-Id: I46331a882eca97d8b2ea0229ff768ce629971a6d
To use DPDK, nics has to be bind with DPDK drivers. Once
binded, the nics will not be listed in the kernel commands.
We have to update the list of PCI address of the nics which
are bound to the DPDK drivers with openvswtich DPDK_OPTIONS
as whitelist. For which, the list of PCI address of the
nics which are bound to the given DPDK drivers are listed
via a custom facter. This whitelist is fed as input to the
DPDK_OPTIONS.
Co-Authored-By: Jaganathan Palanisamy <jpalanis@redhat.com>
Implements: blueprint tripleo-ovs-dpdk
Change-Id: I4fbca23e07468ee58dfce10a6deaf2f25da654c7
