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
Currently CLUSTER and deployment namespace both default to ceph, so these
variables can be used exchangeably.But once deployment namespace changes,
MON daemonset will not be able to get its IP from ceph namespace.
This fix swaps CLUSTER with NAMESPACE and solves this problem
Change-Id: I0cf6afafb71f3972e24d13d479192e7a4e155de4
Signed-off-by: Huamin Chen <hchen@redhat.com>
This PS implements the ceph radosgw and also provides keystone
intergration, allowing ceph to provide a swift like service if
desired for object storage.
In addtion it updates the endpoint lookups to use valid yaml when
dealing with keystone services with a '-' in their name.
Change-Id: I9162ad657df2f77c1bc1afa93a8b999894b1b470
This PS provides the same level of configuration tuneability and control to
the ceph chart as other charts within openstack-helm.
Change-Id: I620c3fdb31abe67ee5b4b4766b1523e02bb7f814
Add neutron prefix to lb-agent and ovs-agent.
Rename ovs-db and ovs-vswitchd to openvswitch-db and openvswitch-vswitchd.
Change-Id: Iad69b0c00d17e59a9f0eb66003e4512ccaeab128
This PS fixes some issues and inconsistencies with the way labels
were applied to the ingress controller.
Change-Id: I98a71e75836f4c4673502ae1f7f7e13a4d19bf95
Creation of one source of truth for kubeadm-aio docs. The kubeadm-aio
README now links to developer all-in-one document.
Change-Id: I9e405036e50cfd5336e0e6ce901d5e5d6850fae4
Closes-Bug: #1711727
This removes sys.exits which are never called and moves one try-except
block to the lines in which the exception is actually raised.
Change-Id: Idb5bde84136208dc39d877b4b66b39a433d85375
This PS adds namespace and fqdn support to endpoint lookup functions,
it also permits over-riding of the puplic endpoint for ingress.
Change-Id: Ib61c5c00a214d75fe85fbffe9080c2ae88bd8cb9
There is a race where the libvirtd.pid file appears but the socket has
not (yet) been created; this adds a timeout-loop waiting specifically
for the socket.
Change-Id: Ib2ede3b8d5c49bc650bf8a64cbffc03444bb2dd0
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
This PS moves libvirt into its own chart - decoupling it from nova,
both making it easier to deploy and use seperately and permitting
use of other compute backends.
Partially implements: blueprint split-nova-and-neutron-infra
Change-Id: I06237157244c3cdb5503eafa01229d061b1614f0
This PS makes horizon image agnostic and also use PyMySQL for the
database backend, in addition to making the policy fully configurable.
Change-Id: I95f269139539a9397c3cc05327f02dd28ee4917c
This ps disables the resouce constraints upon the ingress controller
which was accently left on by default.
Change-Id: I573a4c52f727570aafcd4a1eb16c5c13131323a8
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 moves to use a container sultaible for use as the heat engine
for all possible admin jobs - it is lighter than the kolla-toolbox image
and makes it easy to swap out to other image sets. This is as the heat
engine container should contain the openstack client (with all required
libs for the cloud) and the oslo_db supporting libs required by the db
management jobs, as well as the oslo_messaging libs required for future
rabbitmq management expansion.
Change-Id: I5451c15c8fb49c85b4f254cc60156420bee2efea
