Change-Id: If832e5535b0788dfcfe38cd6cf88f0e0001bacd5
Closes-Bug: #1668001

The newest version of ARA, 0.11, deprecated "ara generate" in favor
of "ara generate html". "ara generate" will be removed sometime in
the future so let's adjust it right away.

Change-Id: I31bff0a7e130c329da44b46506f5b12fa8d6deb8
Closes-Bug: #1665746

There is inconsistent use of either `/usr/bin/python` or
`/usr/bin/env python`. This makes for unexpected results when a
user might be using a virtualenv.

Change-Id: Ibb030f920a8869f9113ade70b66a921cc815060d

Currently it is not possible to use kolla-ansible when it has been
installed in a virtualenv. Virtualenv-based installation may be
desirable when a suitable system package (e.g. RPM, .deb) is not
available, as it allows the user to install kolla-ansible and its
dependencies without affecting the system-wide packages.

This change checks for the presence of the $VIRTUAL_ENV environment
variable to determine whether we are running in an virtualenv. Since
kolla-ansible is not a python script, this comes with the caveat that we
must source the virtualenv activation script ($VIRTUAL_ENV/bin/activate)
before executing kolla-ansible.

Change-Id: I19efb96605bee3b16df3a0b78cd681e5f15499f6
Closes-Bug: #1530319

In commit 177fbea7 the project
was renamed to kolla-ansible, and this broke the BASEDIR
in the kolla-ansible wrapper.

Closes-bug: #1665262

Change-Id: I89fe15e5723f39f453a8173f7ced3f623a8bccc5

* Rename kolla namespace to kolla_ansible
* remove oslo.config.opts entry points which is uesless
* delete useless tools/version-check.py script

Change-Id: I005dd7223ff23afbb2ce8cbfd0ebec0969102798

Ansible use jinja2 < 2.9, but requirements/upper-constraints.txt
requires jinja2===2.9.5. Installing ansible shouldn't use upper
constraints provides by OpenStack.

Change-Id: Ib37e8d06373a61959b41b8737085d5f001650e42

Change-Id: Ifc2af94e30183c86166ec2946d107becd53fd82f

Change-Id: I059b0aafbf93cf8c131beba47ca6f6718ec5fb36
Closes-Bug: #1586548

Change-Id: Ibff560ffa7023e9629e8ea1762121c595c3fb3f4

When using init-runonce script multiple default
security groups are present and raise error:
More than one security_group exists with the name 'default'.

Add a check to create rules to admin's default sec group.

Change-Id: Iaf93467d70ae41fdbcd2b37d6c5639a32d939394

* add fluentd role
* remove heka configure

Co-Authored-By: yangzb09 <yangzb09@qq.com>

Partially-Implements: blueprint add-fluentd-role

Change-Id: Ica804a99f5bb8b157f406299c5982b7b6283b3e3

- This change introduces a new tool for configuring
  host interfaces for use with ovs and dpdk.
- The ovs-dpdkctl tool will be executed via systemd
  when a system first boots to bind interfaces to
  dpdk compaible drivers.
- The ovs-dpdkctl tool will be injected into the
  ovsdb container to allow external configuration of
  ovs bridges and ports for use with dpdk.

Change-Id: Ie8f32d097f0a6816c2ddd03ade926c00837da322

* disable selinux
* Pin docker-engine version

Change-Id: I22c4bdafbeb4d2979ce29a71032cf6569e1f210b

Pull images from tarballs.openstack.org site[0] when there is no
Depends-On in current commit message.

[0] http://tarballs.openstack.org/kolla/images/

Change-Id: I2e5d4d7ed6418624494121e0a530ec95fd045970

kolla-ansible destroy properly fails if qemu processes
are running in compute nodes.
Manually executing ./cleanup-container won't because
$COMPUTE variable is not defined anywhere.

Change-Id: I304c59ec682a93035e631490bbba7b355b1fcae2
Closes-Bug: #1656864

Change-Id: I2b456b1626875d863f896ad7fc6c0024f5ed110f

qemu-ga should be excluded

Change-Id: I89474758a45e52c6c2da7307764344863e065aed
Closes-Bug: #1655838

TrivialFix

Change-Id: I363d09a2565af5b7d4c67afec8fc0c5ae70c8540

Change-Id: I522feee353a7afcdca6862ce4e262e14e36df3a2

Change-Id: Ifacc2462db2bcd7c8091a23c30e9442ec0140c97
Closes-Bug: #1653863

Move ovs-cleanup step to cleanup-containers,
otherwise bridges will not be removed because neutron_openvswitch_agent
container does not exists after running cleanup-containers.

Add logic to cleanup ovs bridges only when openvswitch_db
is removed and openvswitch-agent is running,
so when removing other container from a parameter at script
invocation ovs-cleanup will not be executed.

Change-Id: Ie5fea40426df0e9e465fc173aba185f61098f676
Closes-Bug: #1640178

horizon is a key service and need to be test in the gate.

Change-Id: I89fc1a32b54483c4331c31fb6349dee317c1bc2a

With 4.4 kernel we can use the improved overlay2 driver instead of
btrfs for significantly better performance when creating layers.

Change-Id: I0b84a2b34fdb71c07798d94b546d3105a2742321
Related-Id: I3b0dfd6db5298dfb34ec160eed910ca76feeb423

Read EXTRA_OPTS from env make it possible that using arbitrary
ansible-playbook parameters in kolla-ansible script. like

    EXTRA_OPTS='--limit control' kolla-ansible deploy

Change-Id: I10e0dafb6138d91facdb66a2f487cdeca4689c28

TrivialFix

Change-Id: I22970a9885eda670ec17d6b8c1b368ed2e10a732

OpenStack requirements constrains is well tested. Use it in case of
installing upstream broken package.

This also fixes latest requests 2.12.2 break docker-py, which makes
kolla gate red.

Change-Id: I3e4ec4af2a6e1280313733e8f31f2eea7669dbc1

* rename package name from kolla to kolla-ansible
* remove docker for data_files
* remove kolla docker
* remove kolla-build console_scripts

Change-Id: I53abbf79dffb54eb785a39ba04d375bc4e4f27b0

Typical usage:
   cp /etc/kolla/passwords.yml /etc/kolla/passwords.yml.old
   kolla-genpwd
   kolla-mergepwd --old /etc/kolla/passwords.yml.old \
                  --new /etc/kolla/passwords.yml     \
                  --final /etc/kolla/passwords.yml

Change-Id: Ibbc598909e28e096145841aec929d0cfcf8f7cab
Implements: blueprint kolla-merge-passwords

Updates cleanup-containers to disclude lines related to
dom0 qemu processes.

Change-Id: I0b71ed29b9a2f239ebfdaa66b7cbe41eeaf2773c
Partially-Implements: blueprint xen-hypervisor-support

Behavior of stop playbook is very similar to the destroy
playbook.  This is meant when you may just want to bring down
the service for some sort of maintenance but not destroy all
the associated data. Also added support for the new playbook
into the kolla-ansible command.

Change-Id: Icf0ca91de71dc8ead3a024de3e5b9e49116560d1
Implements: blueprint ansible-stop-host-playbook

Disable ipv6 will lose the vm

Change-Id: I7316d013d9281946c1c566279cd64ecbe6b67d37
Closes-Bug: #1643858

Change-Id: I6f9190eccb2e1a1c5bd450ba63833f35f5d09aac

* Build kolla image by using kolla project's code
* bump openstack_release to 4.0.0
* Remove tox deploy related env, it is useless now.

Depends-On: I132ee005bce993cbadf411697817c2e95548dc81
Change-Id: Id899eb39d476b95130fbeb43adf4fd49ef32be32

set openstack_service_workers to 1 in gate.

Closes-Bug: #1640416
Change-Id: I59560fd543f25e0b60b3f11f1c941adf595b3131

All json file in Kolla are json.j2 file, it shold be render as jinja
template, then validate by using json.

Change-Id: Ibabbe435116fd255d68347e00407156db76fedfe
Closes-Bug: #1634447

* Merge prechecks.yml and site.yml playbook
* Create empty precheck.yml into all roles.

Change-Id: I8a138558a26c0a2a66c5fd48ed37be657c99c1dd
Implements: blueprint condition-pre-check

TrivialFix

Change-Id: I3cfa94d9f6202664a06c24d691376eb8759b922a

TrivialFix

Change-Id: I65ba1828fccee52194eb2b76c4055c922236d97b

ARA 0.9.2 was released which deprecates the previous callback location
in favor of a new one. The deprecated location still works but let's
move to the new one right away.

Change-Id: I8a10d5855ab6f813e52cc6efce5bcfe91d9c3f92