Also changed ovs-agent-init to take care of configuring default external
bridge and interface for cosistency with lb-agent.
Change-Id: I1d893b73a784f55594c30f17ef022348d68f0f1b
This PS adds the local registry image managment to OSH from OSH-Infra.
With this the delta between helm-toolkits in the Repo's is removed,
allowing the toolkit from OSH-Infra to be used and the one from OSH
to be depreciated.
Change-Id: If5e218cf7df17261fe5ef249d281f9d9637e2f6a
Co-Authored-By: Pete Birley <pete@port.direct>
Move to v0.3.1 of kubernetes-entrypoint which has 2
breaking changes to pod dependencies, and also adds support for
depending on jobs via labels.
Change-Id: I49d2cea11fbe5c5919ae22a020b877ebbb285992
This version is already being used by some charts, so this brings the
rest of the charts in line and allows them to use a new feature,
pod dependencies, that this version provides.
Change-Id: Ie8289eb09b31cd8f98c2c5b4dd5bbe469078e6d8
This PS moves static dependencies under a 'static' key to allow
expansion to cover dynamic dependencies.
Change-Id: I38990b93aa79fa1f70af6f2c78e5e5c61c63f32c
This PS updates the values file layout for images to allow simple
parsing of the images in use by charts, allowing them to be queried
and modified much more simply. By moving the image tags to a 'tags'
key, we can extend the options used simply to accomodate extra
options simply (eg prefixing the tag for use with an internal
registry) or pre-pulling the images to reduce chart deploy failure.
Change-Id: I9ec1dbb00d997ab6cb021bf0b698f7aae740e95d
With auto_bridge_add defined as:
auto_bridge_add:
# nothing here
helm doesn't treat is as am empty table so issues warnings such as:
2017/10/03 19:24:37 warning: destination for auto_bridge_add is a table. Ignoring non-table value <nil>
This happens most of the time as we use `helm --values=...` to augment
values.yaml in the chart.
This change clarifies it is indeed a table and the warnings no long
appear.
Change-Id: Ib733ed72df49e134a9199e4024b2893629b990dc
Removing the network.interface.tunnel value from openvswitch chart not
to confuse the users.
After splitting out openvswitch from neutron chart, the value in config
network.interface.tunnel is not used in openvswitch chart.
Tunnel interface is specific to neutron's L2 agent only, not openvswitch
itself.
Change-Id: I40a645398bac8ca56c9e4e96bdbfafcbcc95e9b8
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