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
gen-oslo-openstack-helm generated configuration file templates in
incorrect form, causing setting mulitple values in Values.yaml to
produce something like:
foo=barfoo=baz
This commit fixes this in the generator and updates config file
templates to generate configs correctly:
foo=bar
foo=baz
Change-Id: Iea661dcf1710987b2e111d7141ba888f01c44a50
Closes-Bug: 1699581
This PS adds OpenStack-Helm formatted configuration files for
all the standard Neutron Plugins, which was missed in the original
PR on GitHub.
Change-Id: I1467ca0f3d0308657ff39cc0e096089826de9575
The Neutron Chart had a large amount of extranious whitespace at the
end of lines, this commit rectifies that.
Change-Id: I2280563934e07958d0ac5b2a93b0840a8b6424ab
* Improve neutron chart with vxlan support.
Added VLAN and VXLAN as possible tenant networking options.
Also, changed default tenant network type to VXLAN.
Creation of flat networking is still possible.
* Add helm-toolkit to joinListWithComma
* Return to flat as default tenant network.
* 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
