This PS moves the loading of kernel modules required by services to
being perfromed via a chroot on the host, this ensures that the correct
module is found and provides compatibility across distros.
Change-Id: I889fdd047a24bf4b123dadf9f6d6e6e8079d69d1
This PS updates nova to set metadata's clusterIP dynamically and
neutron to set nova_metadata_ip from metadata hosts
If specify a clusterIP, it is hard-coded as before also.
Change-Id: Ib0d6df8272bd8494bb59ffc8e6b2cfa36a901f60
Closes-Bug: #1715553
This PS update the logic used to determine the default tunnel
interface if one is not specified, as the original method could fail with
complex device names.
Change-Id: Ifec81f517ee29bef0926779591ab9cf5fe0e63c4
Grep the output from 'ip route' command matching first word after match.
The OVS was fixed some time ago, but in new linuxbridge the default
tunnel interface was following wrong grep expression.
Making both OVS and linuxbridge to follow the same reg exp.
Change-Id: I222d694b06285d5ec3d848ee157542796dfc1cc7
Closes-Bug: #1700323
This PS moves OpenVSwitch into its own chart - decoupling it from neutron,
both making it easier to deploy and use seperately and permitting
use of other network backends.
Partially implements: blueprint split-nova-and-neutron-infra
Change-Id: Ifd637136b950ddf1ba1c26ce76c9bbdeafc232c3
Adding daemonset for Linux bridge. Using node selector
"linuxbridge enabled".
network.backend added in neutron/values.yaml to support scenario for
different SDNs using the same networking software, like OVS is used
for reference Neutron L2 agent, ODL, OVN and SONA. The other option for
network.backend can be linuxbridge and calico.
network.backend impacts configuration of DHCP, L3 and metadata agents.
Those agents are dependent on ovsdb_connection flag (officially it is
placed in openvswitch_agent.ini file).
Added daemonset_lb_agent flag in manifests section. Currently
OVS and LinuxBridge L2 agents can be turned on/off to be deployed.
OVS L2 agent and OVS as a network virtualization SW can be deployed
independently.
Removed conf.neutron.default.neutron.interface_driver, since it was not
used anywhere.
Marked places in neutron/values.yaml where changes are needed in order
to use linuxbridge for:
- neutron.conf interface_driver
- ML2 mechanism driver
- dhcp and l3 agents interface_driver
Added example of neutron values overrides in:
tools/overrides/mvp/neutron-linuxbridge.yaml
Change-Id: I7cdcfaa9a73af392a0d45f7df29b7b3ae3cc4c76
Implements: blueprint support-linux-bridge-on-neutron
This PS removes the licence header from rendered output from tiller,
significantly reducing the configmap size of charts deployed to the
cluster.
Change-Id: I5d1b246f2068f3b83bf59ba79fe8b88bbc9a6161
Hardened the grep/awk that extracts the default interface for use
as the tunneling interface. The command failed on multiple
Ubuntu machines as-was.
Change-Id: Ib7d0a8e55e67391d6cb7a58910cfc2ed617a4cbc
Rename ml2.ovs.auto_bridge_add to network.auto_bridge_add
Change-Id: Idf0e746df8b91cbbf89373d1516108ce2163083c
Co-Authored-By: Artur Korzeniewski <artur.korzeniewski@intel.com>
This PS add Barbican support, and moves all potentially container
specific logic into the service start script from the api manifests.
Also fixes a permissions issue with the nova-api, which incorrectly
had the NET_ADMIN capability.
Change-Id: I18fc1ea5d7aa70ea7dabb829361a3da57e905100
Fixes to resolve confusion between gotpl and bash variable handling
and also how bash handles empty strings.
These are required to robustly:
1. make use of an external network (for floating IPs)
2. specify *which* interface in the nodes is used for the tunnelled
traffic.
Change-Id: I30fd675cd471a77dc09a6c7f6ee81120a978b38b
Correction of tunnel_types config option in values.yaml, regarding the
_openvswitch_agent.ini.tpl layout.
Added bridge mappings, since it was lost with auto-generate configs.
Removed br-physnet1 and physnet1 in favor of 'external' network config.
Removed default network interface, replacing it with search for interface
with default gateway for tunneling. The interface for external bridge
has to be defined explicitly, otherwise no interface will be added to
external bridge automatically.
In OVS configuration scripts, added handling null port passed.
Change-Id: I90ebe222323b3b1ec8d20a8038c0dfed3de9b58c
Closes-Bug: #1686365
Closes-Bug: #1686367
This change removes any trailing whitespaces found while
running:
find . -type f -exec egrep -l " +$" {} \;
Change-Id: Ic1dc8765a0971a32da4c3116871e9450a55b357f
This PS moves the container start commands to scripts, which makes
debugging and overriding of container launch params easier.
Change-Id: If75087456e42a5214e428107ee5bd53778a1b822
The ports we add to the external network bridge or standard physical
network bridges may be in a down state after they are added. This
ensures we bring them up after adding them to the bridge
Change-Id: I34b1c2fa17bdfd4941c09de8162418ee3d36eaba
OVS agent was pointing at the wrong config file, it should reference
'ml2_conf' rather than 'ml2-conf'.
Change-Id: I39d20d621f3634456498440cd4d35ac117cbe1f7
* Rename common chart to helm-toolkit
* Update useage of helpers to include reference to chart they come from.
* Update helm-toolkit function naming
Also catches several functions missed in previous PS
* Update remaining requirements.yaml to use helm-toolbox
* Dep Check container fix for common -> helm-toolbox renaming
This commit addresses:
* Separating out stacked ovs daemonset into separate daemonsets.
* Fixes line ending issues.
* Enhances agents ovs pre-flight checks by using neutron-sanity-check.
This is a functioning neutron chart that leverages a flat network
but supports vxlan and gre networks in values.yaml. We were unable
to test the vxlan functionality as it tickles the bnx2x cards in our
HP blade lab.
For now, this leverages daemonsets which make sense. It does require
a new label, namely openvswitch=enabled as we need a label that can be
applied both to the control plane and tenant compute hosts as both
require neutron agents and openvswitch. The interfaces today match
our labs, namely enp11s0f0 for the flat network on physnet1 and
enp12s0f0 for the external network. These can be overriden in
values.yaml via set or a global environmental file.
It depends on the keystone endpoint work.
This chart was tested against a working nova chart not commited as
DTadrzak has one open in PR#45
