Previously, kolla did not support neutron lbaas functionality.
Only Lbaasv2 is supported in Mitaka. Additional information can
be found here:
http://docs.openstack.org/mitaka/networking-guide/adv-config-lbaas.html
Magnum uses Neutron Lbaas to provide high availability to COE API
and Etcd endpoints within a bay. Therefore, Neutron Lbaas is required
for Kolla to support Magnum.
Co-Authored-By: Serguei Bezverkhi <sbezverk@cisco.com>
Partial-Bug: #1551992
Change-Id: I05360b7c447c601fcb3c2b6b2a913ef5cc0f3a1b
Currently Ubuntu source installation loads arping package which is version
2.11. It does not support -U keyword which is used by lbaas.
iputil-arping package should be used instead.
Change-Id: I64c5e5b40e561d309281204b4f6aeaf0fb395cb5
Closes-Bug: #1586085
At the moment the title of the index page of the developer documentation is
"Kolla’s Mission". Other projects use "Welcome to X’s developer documentation!".
Change-Id: Iadddc7fbe3d1eeafe5ed1926a3e090b5de70e7ee
Small sphinx syntax fixes, better wording, removed pronouns, and
anything else we can think of.
Change-Id: Id7ca8d4673f987d10b520cb1eab77802a043c223
Partially-implements: blueprint documentation-rework
Remove information about build time on specific hardware and reasons
for not pushing images per commit that are not relevant for
a quickstart guide.
Link to detailed instruction about image building from the quickstart
guide and update the image building guide to use `kolla-build` command
by default instead of `tools/build.py`.
Change-Id: If821370acdaaa860c96597aa373687f5f10d3121
Partially-implements: blueprint documentation-rework
All the images follow the same naming schema where the container
name is part of the ansible variable name. Currently, the
kolla_toolbox container is named ansible_image_full. Change
this to match what the container name is.
Could impact operators who are specifying ansible_image_full
in globals.yml.
TrivialFix
Change-Id: I9f0cbe4bd69ce17489310a1f5734a254e6ebe27b
An operator may want to specify the location of custom config
files so that kolla can detect their location and merge
them with the default configs generated.
Partially implements: blueprint multi-project-config
Change-Id: Ibfb38d07a36dfa7fe25381adc34cc1d3cbe7d1e1
Give outside projects the ability to consume kolla-ansible as a
config generation mechanism by allowing for the developer to define
a directory structure within /etc/kolla that fits a project's needs.
For example, kolla-kubernetes does not define configuration in terms
of serivces, but in terms of pods (groups of services).
Partially implements: blueprint multi-project-config
Change-Id: If08443aefcaf5fa5604b243b39a6a2d54e431cff
this is a wordround fix for the rabbitmq failed when deploy on CentOS in
the CI gate. the ideal fix should set the hostname in setup_gate.sh
script. But it do not work as expect with unknown reason
Partial-Bug: #1581301
Change-Id: Ia692794aadf11d3ebe75e4e2bf6b42d9a5f3996f
In order for the ansible configuration to be consumable,
we need to be able to generate it without deploying anything.
Change-Id: I2bbdd74d62d00f509a4fa5e4100906ed658d3974
Implements: blueprint generate-config
Kolla should have a doc with an overview of security within
the project.
Partially implements: blueprint documentation-rework
Change-Id: I0a8b902fe1b9adf6617779646bf0bbaee1a36c4f
* sudo is not needed as script already runs as root, using sudo would
require http_* env vars to be carried through.
* Add a systemd unit file to configure docker proxy support
* Update /etc/bashrc if available proxy
TrivialFix
Change-Id: If2571389ec3dc5bce9e819acf962d202b3166b97
* enable the openstack logging debug in the gate
* copy the /etc/kolla files out
* copy the /var/log files out
TrivialFix
Change-Id: I9cf5fa773ec5f41c6ea93325076a64dd24ce22da
