Addresses consistency issues that appear with autoincrement fields in
the existing chart, as demonstrated in [1]. It should allow automatic
recovery of 2 out of the 3 (default) cluster members.
It does not address automatic recovery of a complete shutdown of all
cluster nodes.
[1] https://review.openstack.org/#/c/465977/
Change-Id: I84c86e1862f03a6d381bf219b821ea3636049f0b
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
Add openvswitch based firewall, which is better than hybrid iptables one.
It does not interfere with k8s iptables rules on compute nodes.
The advantage is that VMs have access to the OpenStack API.
Change-Id: Ic6baef5867db962b3cb4709d7e6dce8a9a13584f
Closes-Bug: #1686371
in neutron chart,
line 112~116 values.yaml are not used after 2017-04-11, moved
into conf.
and l3_ha_network_type should not be gre, because ml2 network type
is set vxlan.
Closes-Bug: #1691706
Change-Id: I5d993d6adffe7d7e938ce17d98ac780384b0a100
Adding lost parameter to neutron to nova API call: "auth_type: password"
Also correcting the project_name and username to neutron-> keystone
communication.
Change-Id: I516a2d5fb17b0ac2ca170b249185a914b34c8250
oslo_concurrency value was not correctly defined in neutron/values.yaml.
The template structure expects to have oslo_concurrency.oslo.concurrency
fields, while values.yaml had oslo_concurrency.oslo_concurrency fields.
Change-Id: I4930acf290093a5d8b43cf37171380207cecba6b
This PS moves Neutron to Kolla produced and published images:
* This is part of a larger effort to move to a single image source
Change-Id: I948b32ebabe5acd02dbe0ca6e2f556ae5db29e03
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.
* Add resources limits and requests for each chart
* Refactor the resources limits and requests to follow a patern
* Fix some coding issues
* fix issues resulting from feedback on the resources PR
* Reset some variables to a static value in the neutron chart.
* Substituting variable entrypoint by dependency_check in the concerned files
* Few adjustments
* Update deploy-region.yaml
* Update deployment.yaml
* Add resources limits and requests for each chart
Squah all commits in one.
* Add resources limits and requests for some charts
* cleaning
* Fix indendation issue
* Update deployment.yaml
* Update daemonset-ovs-vswitchd.yaml
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
