Add parameters for the subnets of each network in network_data
yaml. Associates the base subnet of each network with the first
segment of the network. (All networks have an implicit first
network segment when they are created.)
Additional segments and subnets defined in the ``subnets`` key
of each composable network is created with subnet to segment
association.
Partial: blueprint tripleo-routed-networks-templates
Change-Id: I53559ed1445f66fa50508ac9898cbec07914b3fc
Change: I11e38f82eb9040f77412fe8ad200fcc48031e2f8 introduced mtu
property for composable networks. This change set the MTU of the
Tenant network as the global_physnet_mtu for neutron, unless the
NeutronGlobalPhysnetMtu is overridden. The default MTU used if
no MTU is defined for the Tenant network is 1500. (The same
default was previously used for the NeutronGlobalPhysnetMtu
parameter.)
Change-Id: I5e60d52ad571e1cdb3b82cd1d9947e33fa682bf8
Neutron has support[1] to set the guaranteed MTU for
networks and network segments so that this is exposed
to plug-ins. In interest of supporting the use of
plug-ins to configure network devices in the future
this change adds MTU property on neutron networks.
The new (optional) property 'mtu' in the network
defenitions in 'network_data.yaml' is used to control
the MTU settings. By default the mtu is '1500'.
We already configure the MTU on the ctlplane neutron
networks, this adds the MTU to composable networks.
Also update the nic-config sample templates to include
mtu settings. A heat value resource is added to
nic-config templates to get the required minimum
viable MTU value for bridges, bonds and member
interfaces to ensure the MTU is large enough to allow
the largest configured MTU to traverse the path.
Closes-Bug: #1790537
Change-Id: I11e38f82eb9040f77412fe8ad200fcc48031e2f8
Neutron services failing with below Error when running
with podman(0.12.1) and container-selinux(2.77):-
relabel failed "/run/netns": operation not supported
Until this is fixed in podman/container-selinux, temporary
remove selinux relabel on /run/netns.
Depends-On: https://review.openstack.org/#/c/626546/
Change-Id: Iedbeac17a0c530ecdc7e8cbba5ddd4ffb22bb616
Partial-Bug: #1809218
In order to specify which version of python we should use for the
deployment, we need to pass in the python interpreter into the
postconfig where we are directly calling the ansible heat hook.
Change-Id: I9dfc72269f800395a9864c457a5a43f7590c8e75
Related-Blueprint: python3-support
The when statement was duplicated in the docker-registry
service, plus the equals operator was wrong.
Closes-Bug:#1808974
Change-Id: I1650acfd67b87be18ab03385ce35cccdf708f046
These are containerized scenario multinode jobs that were
wrongly named.
Depends-On: https://review.openstack.org/#/c/619337
Change-Id: I804b7a39159445cb75ecc8e93897fd7f0f24b630
This changes moves podman service from puppet to deployment directory.
Change-Id: I31b8299b43158347f4f1f61f1e1fdf38b0a2102f
Related-Blueprint: services-yaml-flattening
Numerous files have incorrect modes set. Correct these so that executables
have 755 and yaml files are 644 to address rpmlint errors.
Change-Id: I8db36209b41a492f6b85e3469994de884bf556e8
This change combines the previous puppet and docker files into a single
file that performs the docker service installation and configuration.
Depends-On: https://review.rdoproject.org/r/#/c/16994/
Change-Id: I9556a07d72fabfbd5f6f35eaf3d7a1bd88ef7470
Related-Blueprint: services-yaml-flattening
