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
Makes sense specify where the docker volume path is present
for image storage in the kolla host as kolla-vagrant does in the
bootstrapping step. With this way users will know where exactly
their images are stored when re-utilize registry containers
Change-Id: I7f5c46ebab8ec4287a40cd6bd34e75eeb919a24f
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
