9 Commits

Author SHA1 Message Date
Dan Prince
30cfaccb49 flatten the ovn service configurations
This change combines the previous puppet and docker files into a single
file that performs the docker service installation and configuration
for the ovn services.

Related-Blueprint: services-yaml-flattening
Change-Id: I6261863c15f594fed8207ff258f1d9c809a9a864
2019-04-10 10:57:37 -04:00
Kamil Sambor
98c2b78dcb Enable flat network for ovn
Change-Id: I0883b4f1881887cae68da9658d2e237218b694c4
Closes-Bug: #1821171
2019-03-22 09:00:16 +01:00
Lucas Alvares Gomes
a1969b4f48 OVN: Add VLAN to NeutronNetworkType
In the latest version of OVN (2.11 or higher) VLAN is now supported. This
patch is adding VLAN as a supported network type in the validations
for OVN.

Here's the networking-ovn patch adding support for VLAN tenant
network: https://review.openstack.org/#/c/632722/

Change-Id: I869326ef53b8a19323efbc972cc42a67035ab599
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
2019-02-28 09:59:01 +00:00
Zuul
3a8956cee8 Merge "Set the number of RPC workers to 1 for non SRIOV OVN setups" 2018-10-03 16:03:12 +00:00
Daniel Alvarez
7bf7996c79 Remove unused parameter NeutronEnableDHCPAgent
NeutronEnableDHCPAgent is no longer consumed anywhere in OpenStack so
this patch is removing all occurrences of it in the environment files.

Change-Id: I042944c3f24d22fa60d4ed13fd9a56c5b93f465f
Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
2018-10-01 12:43:01 +02:00
Daniel Alvarez
c677a4ba40 Set the number of RPC workers to 1 for non SRIOV OVN setups
OVN based backend setups don't need RPC communications as they
don't deploy Neutron agents (except for the SRIOV case).

For this reason and to minimize the resources used, this patch
is setting the number of RPC workers to the minimum, which is 1.

Change-Id: Icf84516f24873717cb7615233d2e6341414abfc7
Closes-Bug: #1786952
Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
2018-08-16 16:44:18 +00:00
Numan Siddique
5ed628f353 OVN: Set sysctl value 'net.ipv4.ip_nonlocal_bind' to 1
When OVN DBs pacemaker bundle is started on the controller nodes,
all the ovsdb-servers are configured to listen on the virtual ip
(on ports 6641/6642). But only master node is configured with virtual ip.
On the other nodes, we see the below error messages

ovsdb_jsonrpc_server|ERR|ptcp:6641:172.17.1.18: listen failed: Cannot assign
requested address.

The commit [1] addressed this issue in puppet-tripleo by setting the
sysctl value 'net.ipv4.ip_nonlocal_bind' to 1 using puppet's sysctl::value.
But the ovn-dbs.yaml service file is missing this puppet tag when the
container 'ovn_dbs_init_bundle' is started.

We can fix the issue by defining this tag, but this also requires setting
'privileged=true' when starting the docker container.

Instead, this patch makes use of the t-h-t param 'KernelIpNonLocalBind'
which was introduced in this commit [2].

[1] - I6f762534350a3f96696c87ccd2d14545dccc8a0b
[2] - Idd3d432b8f7eb573d94cd56be8e05614510ebddf

Change-Id: I5ae8cd368bcd58810b18e172ee685fdbf0e48d98
Closes-bug: #1781585
2018-07-17 23:47:19 +05:30
Numan Siddique
371e5d6264 ovn: Add dns_servers configuration support
networking-ovn optionally expects list of dns server to be defined in the
config -'ovn/dns_servers'. These will be included in the 'dns_server' DHCP
option field when the VMs send DHCP request if the subnet's dns_nameservers field
is not defined by the user.

This patch sets the hieradata - 'neutron::plugins::ml2::ovn::dns_servers' to the
defined OVNDnsServers t-h-t param.

Change-Id: I80574f7badfcc618254266051c8d6661c08e2be0
Closes-bug: #1774052
2018-06-25 16:10:56 +05:30
Dan Prince
e691bbe026 Default environment/services/* to docker
This updates the relevant environment/services templates so that
they also default to docker. Without this change users of these
services could end up with mismatched (unsupported) deployments.

Additionally, this picks environment/services-docker as the
source of truth when resolving collisions for moving those over
environment/services. So environment/services now contain all of
the containerized services' env files used to be located in
environment/services-docker. The latter will be deleted later to
prevent future desync of contents.

Co-authored-by: Bogdan Dobrelya <bdobreli@redhat.com>
Change-Id: I923731f46ea26582160a11d2dfe85792ab74110b
2018-03-27 11:24:08 +02:00