While it's possible to edit distro/package unit files installed to
/lib/systemd/system, a cleaner solution exists.  systemd will pick up
'drop-in' unit files located in '/etc/systemd/system/[unit name].d/'.
A drop-in unit file only has to include fields that override those in
the main unit file, and the drop-in unit and main unit file can change
independently.

This change updates the quickstart doc to use drop-in unit files to
configure docker.service instead of editing the main unit file.

See: https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html

Change-Id: Iddbebf658741937e3c4157fc0a021751f10fabd2

During multi-node, it is possible for master target node images to
be older then the Ansible master playboks if the repository is
updated.  Add documentation to explain this situation.

Change-Id: I2ccf57004147873e89f23fbb996d01f550e90c3f

Deploy Manila in kolla

Co-Authored-By: Mauricio Lima <mauriciolimab@gmail.com>
Change-Id: I1397e0f10dcbcfd182497fbaf0ebe9d5de718cc5

Change-Id: I3c5b6f73b19968c9ae26b12e64864c72a5e2b7f2

We need the gcc and other dependencies
installed before we can do any tox related
commands.

Installation of git was never checked in QSG.
I happened to create a baremetal CentOS server
with minimal install and there was no git.
Added steps to install git.

Moved the steps related to git clone and other
kolla configuration after basic installation.
since tox fails for gcc.

In the quickstart guide we are generating
the configuration using tox but tox is not
installed before doing so. Adding steps to
install tox before generating conf.

Change-Id: Ic8a756e66d33963e47607ed60c4c768e0859152d

Instead, rely on kolla-ansible post-deploy to generate a configuration
file with valid environment variables.

Change-Id: Ie62932afc96e2486410a1d4e14162a88b1733c22
Closes-Bug: #1555972

We added a requirement on libvirt python bindings with the script to
retrieve the latest DHCP lease for vagrant developers' environment.

Add it to the vagrant documentation.

Change-Id: I3e7e97922f5b855155fda96b914a4947af007c47

Although not strictly mandatory, it's less confusing to have
a kolla-build.conf file in /etc/kolla that users can modify it they
want to customize their builds, rather than to rely on defaults
settings and command line options.

The `tox -e genconfig` was already documented in "Image building" doc.

Change-Id: Ia44e6f28ce18601cdaba5109ea12cd50fa8372b2
Closes-Bug: #1532066

Change-Id: Ia385364e3fd8fc3441ebd07adcd981154f34ebb8

Fix a few small typos and formatting.

Change-Id: I5bf1f1aba518aa4df605b9e9133953f9fa256c4c

There is a critical data loss in Liberty 1.0.0.  It is only fair we
warn Operators not to use 1.0.0 and then revert this change once
1.1.0 is released.

Change-Id: I65a18ddbbdbf2fc5f62f62ff7a1650049b61fada

People commonly want to use loopback devices to evaulate or develop on
Swift.  The steps for this are slightly different than those for
physical block devices.

Also make some small fix ups to the title formatting.

Change-Id: I0c1cb4a261f264dc56bd065ab137e5ee79e773f8

Relates-to: blueprint kolla-ssl

Change-Id: Id82d22c2195be5d897c781f28087a1ea422b8bea

Add documentation for the commit I084e5d1cc8f9993d65167878f9983ad58a68e86e.
Explain how 'build.py' picks up automatically env proxy variables.

Change-Id: Ia8513babd4ff72ed52e167b361d6b54393598a78
Closes-Bug: #1538108

Every now and then people ask about plugins for Kolla. This conversation
may need to be revisted in more detail soon, but till then it's worth
highlighting what we do currently support in Kolla.

Right now adding the block as shown in this patch will make the plugin
archive available in the image, but currently only Neutron has
Dockerfile directives to automatically install them if present. The same
can be added very easily for other commonly pluggable services such as
Horizon.

Change-Id: Ia52d5ccf753667c5452b19fcaf4bf5b893a59fd0

After change change 284856, there were some comments
about ambiguity in docs.

Change-Id: I90129c475b87bf63f2e5c870dba7bd07893c8c9c

Closes-Bug: #1551052
Change-Id: Ic226287bbf1f1e8d5cc2e1d80ce2975448b1f95c

Vagrant and Heat, while really cool tech, are not very well maintained
in Kolla. They are not always up to date, and as a result, are not
recommended for evaluation purposes by this change.

TrivialFix

Change-Id: Ic8b8519431ed5c50a9a46b2e8b8f822d0982b1cf

Due to poor planning on our variable names we have a situation where
we have "internal_address" which must be a VIP, but "external_address"
which should be a DNS name. Now with two vips "external_vip_address"
is a new variable.

This corrects that issue by deprecating kolla_internal_address and
replacing it with 4 nicely named variables.

kolla_internal_vip_address
kolla_internal_fqdn
kolla_external_vip_address
kolla_external_fqdn

The default behaviour will remain the same, and the way the variable
inheritance is setup the kolla_internal_address variable can still be
set in globals.yml and propogate out to these 4 new variables like it
normally would, but all reference to kolla_internal_address has been
completely removed.

Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5
Partially-Implements: blueprint ssl-kolla

Signed-off-by: Michael Trimm <mitrimm@cisco.com>
Change-Id: Iccd3c53526caf8b109ba4ede117eebf66958782d

Made changes in section Managing Ceph to correct the grammatical mistake.

Signed-off-by: Richa Yadav <ricyadav@cisco.com>

Change-Id: I2ed13f766dd39a7ac816af86664986b8d2700d80

- Provided info on installing ansible via yum from EPEL and pointed
  readers to the EPEL docs to learn how to install/enable the repo

Change-Id: I4bf87fbf90779be85293eb65fe7cd2ffe548d6ae

In Deploying Kolla section of the quickstart.rst IP addr needed to
be changed IP address.

Change-Id: I4f3895d6f05340a0608b2b66170a769bd1454fb7
Signed-off-by: Asha Saravanamohan <assarava@cisco.com>

Change-Id: I882fb31bc21be4b4f22e61938c1d8f6775d69323

Since docker 1.10.1 is required, and docker 1.8.2 does not work with Kolla,
Remove the downgrade instructions

TrivialFix

Change-Id: I461572a40b6fc96f73593cf989967449e4bc8e0a
Signed-off-by: Jason Myers <jason@jasonamyers.com>

The operators aren't mindreaders.  Lets throw them a bone about
how to properly evaluate Kolla.  This can probably be expanded
on.

TrivialFix

Change-Id: I70d0f6a63417dc9f361d8c14bbb512e1dcc44ed0

TrivialFix

Change-Id: Iaf4fe7747e1cf5c04cd37cb30985a75f0b1650e4

Partially implements: blueprint heka

Change-Id: If0db8a5c9b8426687f64002a65e1dd9cbe041d1c

Part 1

Change-Id: Idf3d45a5a5d9da731e986765ee0376288a60254f
Closes-Bug:1545926

TrivialFix

Change-Id: I93f9ec574b4d46a53086ca11946bfa1003e26fa0

The documentation had old information about running
docker registry version 1.  Documentation improvement
uses exclusively Docker register version 2.

TrivialFix

Change-Id: I320341c1a646eeeec35fb928a970f4d7e8a13bb9

Change-Id: Iadbd4a0d77aee692abd9ab4f81ba67ead8949b1e

TrivialFix
Change-Id: I885995498ac70251e317c49c9374c9850165af89

Change-Id: Iee3f14c002bc0f9242d341842e5c88630bf5f485

This is needed for thin containers.

Change-Id: I57a49a3ac35facc157fff846560787027be9a08f

Change-Id: Idc390774ba3bf63860bfaee1494b6e0180d112c1

For CentOS, install from distro packaging by default.  Explain
how to install on DEB based systems from packaging when they
update to a newer version of Ansible.  Finally, clean up the
ordering of the dependencies for a pip based install.

TrivialFix

Change-Id: I9564a03c2e75fd30b5ec9c7d64f5defb709d7fde

We are using the mount propagation in Docker 1.10.

TrivialFix

Change-Id: Ic2ef1fbce9dba217eac75f3743cef7f6ac702b00

This change let Swift detect and use physical disk for storage. The
old named volume for storage isn't really useful for any serious setup.
Also updated swift-guide.rst accordingly.

Change-Id: I4f577b7b69d8bcd8b3961500946241c65a16db22
Partially-Implements: blueprint swift-physical-disk

TrivialFix

Change-Id: Ia7dc521a83b13799345ca8b89ba4130aba039d60