The python-neutronclient is deprecated. We should use openstackclient
and openstacksdk for the equivalent functionality.

Change-Id: Iaf49d6b7942343104e0b40b6db89b78a793b858b

Introduce a job 'kolla-ansible-ubuntu-source-zun' to test kolla
with Zun enabled. To reduce CI resource, this job will be triggered
only if there are changes on the Zun's ansible roles.

Change-Id: I0ba207e1d3761da2d6992c5834d4f59e7e1d6628

Kolla Ansible now claims [1] to support executing as a user other than
root.  We should ensure that this is tested in CI.

This change removes the 'become' from hosts in the inventory, and sets
the remote user to 'kolla', as configured via the bootstrap-servers
command. The bootstrap-servers command and other ansible commands
executed before it still need to execute as the zuul user and not as
kolla, since kolla does not exist yet.

The autogenerated SSH private key in passwords.yml is now added to the
zuul user's SSH config, such that it can SSH as the kolla user, which
has authorised this key.

[1]
https://blueprints.launchpad.net/kolla-ansible/+spec/ansible-specific-task-become

Change-Id: I8f3587e2908bc5b8889cd6fbc01981a6186d33e6

This patch is to test and revert the change

Change-Id: If930306a357e40ad02c4d7f71779701a9a52b94a
revert: Ie8feb03e9a07a6486a8b375d3304c9e6f1f8b890

Depends-On: I75e00312b36e1678b90a42cf58d24652323eff27
Change-Id: Ia716fabffca41eff816e59bbf9f4cab79ee8b72f

Without this, kolla-ansible check fails with the following error:

Unable to retrieve file contents
Could not find or access '/path/to/kolla-ansible/ansible/check.yml'"}

Also adds the check command to the CI tests, to ensure that it does not
break again.

Change-Id: I9fc2f9999f55cb742ac3ac38579dcf26524a9fc7
Closes-Bug: #1790653

In order to migrate to the latest release of rabbitmq (3.7), we need to
first remove this deprecated plugin which is no longer supported (the
problems it solved are now addressed in rabbitmq itself).

This avoids a circular dependency in CI where the new images depend on
the new clustering and the new clustering depends on the new images.

Change-Id: I921459f3e40b9e0d4af9497384e49aabf0abe79b

The reconfigure output was previously overwriting the post-deploy
output.

Change-Id: Idada4b0b1d34b6a37a99f022407c74aff043497a

Cinder removed some parameters from the API.
Openstack client is not updated yet and failing.

Revert this change once is fixed.

Change-Id: Ie8feb03e9a07a6486a8b375d3304c9e6f1f8b890

Depends on needs chrony image to succeed deploy

Change-Id: Id4bcbffad2392d8b2dabd8359330139448c6f7b7

openrc should be admin-openrc.sh

Change-Id: I9b3d874fe39488206ce880247b51d0a26826eeb6

include is marked as deprecated since ansible 2.4[0]

[0] https://docs.ansible.com/ansible/2.4/include_module.html#deprecated



Co-Authored-By: confi-surya <singh.surya64mnnit@gmail.com>
Change-Id: Ic9d71e1865d1c728890625aeddf424a5734c0a8a

Without these jobs, a compute node that is rebooted or powered off may
violently kill off the VMs running inside of it. This has been kept
separate from the main portion of kolla-ansible since no current role
modifies the systemd jobs of the system.

Change-Id: I0a4424f97b5ad872ff0398258c1dc42d31d0ef07

For large installations it makes sense to use a higher number of forks
than the default.

Change-Id: I34cdc146a4ed2185fb36fbb34ab72916ec98bee5

User can use custom directory for nova instance.
For example using a shared file system as backend.

Change-Id: I11fe4891719a2e2a34888d8b798df5602e294e4f

To destroy a kolla-ansible environment a confirmation string should be passed
along with kolla-ansible command: kolla-ansible destroy -i ~/multinode \
--yes-i-really-really-mean-it
However, this string is not evaluated right and just putting --y starts destroy
process: ./kolla-ansible destroy -i ~/multinode --y

Change-Id: I5983f9c7fd3859d60741dfd23ad10dfd91872eeb
Closes-Bug: #1701313

remove unused validate-all-json.sh and validate-all-dockerfiles.

Change-Id: Ia534c200f771c23d015ab32b0cc952ca36354451
Closes-Bug: #1778146

Deploys a bifrost container using kolla-ansible bifrost-deploy.

IPA and disk images are downloaded rather than built to improve
reliability.

Currently only minimal testing of the deployment is performed, creating
and deleting an ironic node. Ideally we would perform a bare metal node
deployment.

The job is based on CentOS, as Ubuntu bifrost deployment is currently
failing with a python-MySQLdb error.

Change-Id: Ic45094594c21116b5b0d6a606f568fc7954175e3

When running the kolla-ansible destroy playbook most of the files
under /etc/kolla are cleaned up.  This change will cause the
clean-up to skip the kolla-cli related directories.  When running
the deployment code in a container or a separate VM this is not
an issue, but when doing an all-in-one or running the deployment
process from one of the systems being deployed onto it would have
previously destroyed the kolla-cli inventory and any generated
certificates used for TLS.

Change-Id: Icd62e177964b8fb31052131785c6d7b138975a28

This fixes an issue with cmd2 >= 0.9.0 requiring python3.

Change-Id: I5f88f0b0540785f8e7b7ab7c5252c6a51f314922
Closes-Bug: #1773938

ovs-dpdkctl.sh doesn't work properly

Closes-Bug: #1770045
Change-Id: Ia450553296f7613f4883b79e9dd1eb3bc950e9c6
Signed-off-by: johjuhyun <juhyun.joh@samsung.com>

- rename action and serial to kolla_ansible and kolla_serial
- use become instead of "sudo <command>" in shell
- Remove quota for failed_when and changed_when in rabbitmq tasks

Change-Id: I78cb60168aaa40bb6439198283546b7faf33917c
Implements: blueprint migrate-to-ansible-2-2-0

This patch enforces the removal of the container
network namespace when the environment is destroyed.

Closes-Bug: #1769651

Change-Id: I9b0bbbb5a59e6067a745635c555051ef97b79f9a
Signed-off-by: Jorge Niedbalski <jorge.niedbalski@linaro.org>

the /etc/kolla/adminrc.sh should be export before
init vpn script, this ps to add test for credentials
set to avoid it missing.

Change-Id: Ib849d5f5804221c507c2466f2f08179340188c24

openstack cli now supports --network foo rather than having to find the
network uuid. Thanks to mgoddard for the tip.

Change-Id: I9ce94a86c6950b81ef3ec70fe10ee565cc1f1171

More info please check[0][1].

[0] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128902.html
[1] https://ara.readthedocs.io/en/latest/advanced.html

Change-Id: I5cf68c0bb54878e328387143712dec9582be04a1

This patchset implements yamllint test to all *.yml
files.

Also fixes syntax errors to make jobs to pass.

Change-Id: I3186adf9835b4d0cada272d156b17d1bc9c2b799

- Ceph images are not being built when using depends-on a kolla build
  job.
- Sync inventory files with current ones which causes ceph to fail due
  missing groups.
- Small corrections in ceph config.yml syntax.
- fix preparse the disk only once
- enable ceph nfs only when enable_ceph_nfs is true

Co-Authored-By: Jeffrey Zhang <zhang.lei.fly@gmail.com>
Change-Id: Id0c7963bf59e2af4944834dcd16589a638e78ba5

Adding translate, new line in for loop /etc/default/ovs-dpdkctl.conf
Removed '' around pci_whitelist args for DPDK. When multiple entries
present vswitchd does not start.

Closes-bug: #1718240

Change-Id: I8196d56fe78e9ec1a0504059b98bcb9d1ee33f76

Fixed misspelling in both comments and code function names 

Change-Id: Iaed5f246a9b02fd64433671fd0c0ee41b40bd222

- Horizon

This will copy only yaml or json policy file if they exist.

Change-Id: Ib8875ca54dc9dc69abc8338413f7724d9d4ecc45
Implements: blueprint support-custom-policy-yaml
Co-authored-By: Duong Ha-Quang <duonghq@vn.fujitsu.com>

Nodepool nodes saves the cirros image in /opt/cache/files/, we can make
use of it to save some time and remove an external dependency on the
cirros website.

Change-Id: I81b431d8659b1da8b36d660f2a8f1cfa42461a14

Before cleanup containers and hosts, it should be ensure the
docker serivce running but the destroy action missing it,
this patch to fix it

Change-Id: I85ca806c1fd395daf937b585d466e16fbad4e20c
Closes-Bug: #1741852

Nova does not yet defaults to UEFI ;(

Change-Id: I9f26d373f73d15fa571545b3c867beb07da88f48

Change-Id: Ia4fbe1f2895593d1f6099f174736e8267b87e8d6

Another step to migrate to new CI

Change-Id: Id9bf9b4b1114f5be66f6c028a0db16d869efeceb
Depends-On: Iaacdca31b27b7033ec08499bcea7061b9d3ec279

Change-Id: I551bd6787dea8dcdfadd09161d295b1290480e8e

Currently init-runonce script changes directory to the
script's base directory (/usr/...) before doing anything else.
This unnecessarily _forces_ a non-root user to use sudo for
running this script thereby raising privileges for code which
doesn't want it. Also downloading temporary stuff in places like
/usr... seems not a good choice.

Hence deleting the said code part and letting the deployer work
comfortably from any directory.

Made documentation changes accordingly.

Change-Id: Ib3c7ed97aa5f53c115b6337aaf572b5fdc7a71f3
Closes-Bug: #1732963

Change-Id: Id71c1ecda9f8647a0eb290fe02a12afb3df09988

Change-Id: Ie865b7175b46f939b629d5378d98d0aeba963df2
Closes-Bug: #1729778