Remove the hardcoded callback path with python2.7 and use the
virtualenv python to determine the path where ARA is installed so
that no matter if we're running py2 or py3, it will work.

Change-Id: Ica0b94aeebabaeca8416a9768fadd12d3925e7b2

Ironic inspector should honour the Ansible inventory group
ironic-inspector. Ironic inspector may not be required at all. If
Ironic inspector is required then it should only run on a single
node, and this should be reflected by the inventory.

This change makes a number of Ironic inspector-related tasks dependent
upon the host's membership of the ironic-inspector group. Also, we
couple the ironic-dnsmasq container with the ironic-inspector group
rather than ironic-conductor, as the service is for inspector rather
than Ironic.

Change-Id: Ifd90753b0fe1a55c11b7723c28e1d14ab3d32737
Closes-Bug: #1665257

Required for dockerhub publisher

Change-Id: I0231bd07415ef05b3f4f937e32a9df4cd0643672

Lately, after we increased number of jobs, infra started to experience
network traffic issues due to us downloading registries. This
per-nodepool cache should help and also speed up actual gate.

Change-Id: I621a9c91e4508ef208a28137a736fd8468388219
Depends-On: I527d32f9b43dabb7640bfb056e2bf828b7c1dfa9

The pypi package 'docker-py' [1] has been renamed to 'docker' [2].
It is better to move to the new 'docker' package because the old
package will be deprecated and all the new features will go into
the new package only.

Package 'docker' has been added to requirements [3]. The old
package 'docker-py' is still allowed to be in the global requirements
during the transition period but it should be removed after all or
most of the projects finsih the migration.

[1] https://pypi.python.org/pypi/docker-py
[2] https://pypi.python.org/pypi/docker
[3] https://review.openstack.org/#/c/423715/

Change-Id: Ibcd5a57a1fbf55dcc5a690e41f20917f95b63da0

When cleanup-images is launch without parameters the following error is
triggered:
./cleanup-images: line 72: break: only meaningful in a `for', `while',
or `until' loop

This patch fix it.

Change-Id: Ie8c63420a4e9b0d49a4e6be4172c8f0be912b556
Closes-Bug: #1702496

User can use custom directory to store images.
For example using a shared file system as backend.

Change-Id: Iab7a9a51e619bdbf8f7bd4626ebe4d703e6d4819

When using depends-on, gates will not build cinder
and ceph images, causing ceph deploy gates to fail.

Change-Id: I441c742251754db27374331f774041c214678eba

Kolla support latest docker engine right now.

Closes-Bug: #1661549
Change-Id: I5074fd16bdd158df8e97f909dead0a59a14fdf42

Change-Id: Ie206f0f245648df855ceb6140e60de664dac74fc

First non-trivial scenario we'll be testing in gates will be cinder +
ceph. This patchset is supposed to create framework to easily add new
testing scenarios.

Change-Id: I6790eaf5cf3297af04a64e4169a39b6e2cd1890f

Add a new variable 'kolla_devmode', which when enabled, clones and
bindmounts service source code into the containers.

This commit adds the relevant changes for Heat, more services can be
added and built upon.

Usage:
* Set 'kolla_devmode: yes'

* Code is cloned to /opt/stack/{{ project_name }} on target
  node(s)

* Users can develop in these repos, and simply restart the container to
  pick up / test changes.

Debugging can be done from the host via 'remote_pdb'[0].

[0] https://pypi.python.org/pypi/remote-pdb

Implements: blueprint mount-sources
Change-Id: Ic0431b10d723bf84eeefc72039376fe0058dd902

This patches changes deploy_gate quite a bit so in reality all
deployments will now assume multinode (even if it's single node). After
that we will refactor it even further to enable easy addition of new
scenerios.

Change-Id: I1faada46e6a7aa026128b2f01d77eabb04759439

Revert this when neutron bug[0] is fixed.

[0] https://bugs.launchpad.net/neutron/+bug/1694420

Change-Id: Id9f84608826351b9675cd6a6f2a183e91ce33bf6
Partial-Bug: #1694420

Kolla-ansible does not have as its allowed parameters
ansible's limit.

Change-Id: I86821fe39e6f0f61e513a0677bf177234c203103
Closes-Bug: #1693801

ARA behaves well gzipped and shaves a lot of the size due to it being
composed mostly of text.

Change-Id: I7a3f21af365d13ba783d200a75d18b50429a1488

Change-Id: If81fb5a7f7e87f1b6d15b09437353a5264364ef1

Change-Id: I0fac4cef9e961b1d64f269bfc27804e77f4ea842
Closes-bug: #1689422

Change-Id: I9665338318f8ad4690e4908748065623d0537741

Make command line more friendly. :)

Change-Id: I8113c72aa00b1c07cb2b77c73e7dd8c7ee833bcc

During cleanup-host, we need remove swift references from fstab.

Change-Id: I18e9a84b0664eb834cf397bcf6d2406abcab47a7
Closes-Bug: #1689285

ssh/config permissions are 664 currently, causing error
`Bad owner or permissions on /home/jenkins/.ssh/config`

http://logs.openstack.org/68/461368/1/check/gate-kolla-ansible-dsvm-deploy-centos-binary-centos-7-nv/0a94da7/console.html#_2017-05-01_12_06_08_440775

config file should only be writen by owner.

Closes-Bug: #1687408
Change-Id: Id804f11a91858fa297e5236beb2110e3511eabec

As a change to remove puppet from infra nodepool,
ssh-keyscan is needed for each node.[0]

Host key checking was disabled by default by jenkins
user. [1]

Refs:
[0] http://lists.openstack.org/pipermail/openstack-dev/2017-April/116036.html
[1] https://review.openstack.org/#/c/460731/
Change-Id: I0f4000f18b7a2b3266c95c3f7a5109e3603c94a7

Allow remove all kolla images
Allow remove specific kolla version images
Allow remove dangling images
Allow remove single images, all images matched

Usage examples:
   * cleanup-images --all
     - Remove all kolla images
   * cleanup-images --image-version 4.0.0
     - Remove all images matching 4.0.0 kolla_version
   * cleanup-images --dangling
     - Remove all dangling images
   * cleanup-images --image nova
     - Remove all nova images
   * cleanup-images --image nova-scheduler
     - Only remove nova-scheduler image

Implements: blueprint add-cleanup-images-cli-options
Change-Id: I997272098879350e13e0ac00762ae3485e618355

sourcing validate-docker-execute.sh script is not needed anymore and
should be removed.

Change-Id: Ie40ddcd36e71337d94f49467bfb0f8aae50353f7

This seems to have got lost during repo split. Adding it back in now.

Change-Id: Ic0b0f5efb12eab58e7872b30611a39640dc44cc2
Closes-Bug: #1629224
(cherry picked from commit e1a2f99014a1aeb3697e8ec3c999cdc12380376b)

fix typo for specs/kubernetes-deployment.rst, tools/ovs-dpdkctl.sh, tools/setup_gate.sh

'managment' -> 'management'
'seperated' -> 'separated'
'occuring' -> 'occurring'
'discribed' -> 'described'
'recomended' -> 'recommended'
'thier' -> 'their'

Change-Id: Ie59c600698c965cebd9a541b951d704eda9301cb

Refer to
https://docs.openstack.org/ocata/install-guide-rdo/glance-verify.html

Change-Id: Ic2a32a3f17a11f1f6e8ecf0f7271d7d1f12ca5bc

- when run tools/cleanup-containers mariadb, the mariadb volume remove
failed, because the "volumes_to_remove" can't catch the mariadb
volume, this patch to fix it.

- remove the unnecessary "()"

more test infomation, see http://paste.openstack.org/show/603359/

Closes-Bug: #1674207

Change-Id: I82f5922fcc84d222f74d2551a2c697bf78136a2d

Currently we omit the os_distro property when uploading the
cirros image to glance.  Nova assumes it to need vfat disk
incase the image is Windows.

This change sets the property to "linux" causing ext4 to be
used instead.

TrivialFix

Change-Id: I3fdb71f5be7702a2dc223946fae82131c6c46154
Signed-off-by: Dave Walker (Daviey) <email@daviey.com>

Add a new subcommand 'check' to kolla-ansible, used to run the
smoke/sanity checks.

Add stub files to all services that don't currently have checks.

Change-Id: I9f661c5fc51fd5b9b266f23f6c524884613dee48
Partially-implements: blueprint sanity-check-container

Run playbooks in serial are unnecessary and may cause some issue. This
patch disables serial.

This patch also removes the serial for MariaDB playbook. MariaDB handle
this internally.

Partial-Bug: #1668185
Change-Id: I3b4216dd82607475e9bd9b44590b631be4abdbdd

Change-Id: Iad58edcbbf98405349bda175821b9966fdb10d34

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