Change needed to add header blocks to all Dockerfiles, similar to the
base.
Use case is to easily run something before packages are installed, e.g.
to COPY a local rpm in that can be added to the package list.
Change-Id: I1bbfdf0b762da0a392aa8bf47781315b45377bee
Closes-Bug: 1618969
Add a service check for Cinder when using iscsi/LVM, that the
appropriate volume group exists.
TrivialFix
Change-Id: I54e01911709db73549334760498b4246fe6271d7
Co-Authored-By: Vladislav Belogrudov <vladislav.belogrudov@oracle.com>
When running kolla-ansible as non-root users the tmp files will
be created with become user as owner and mode 0600. This way the user
running kolla-ansible is not able to read the generated files. This
is necessary because of the use of the lookup method, which will
not run as become user.
TrivialFix
Change-Id: If86d114c05a9b2e7fa240718611d78e93100ebdf
Useful for upgrade etc., which is preferablly done serially.
Example usage: tools/kolla-ansible deploy OR tools/kolla-ansible upgrade
Closes-Bug: #1576708
DocImpact
Change-Id: I34b2e16f8ce53e472a4682a4738c4ac0f5abf00c
Wait until the mariadb cluster is fully functional
- check existence of mariadb.pid is insufficient because the cluster
may not be fully prepared
Change-Id: I611b38f7dbc8032c42aee2a040fb1210b4bee7eb
closes-bug: #1614363
- One of the usecase supported by tools/cleanup-containers
was the ablity to remove container with a regex so that
you could redepoloy just that single componet.
- By cleaning up ovs in cleanup-containers that is nolonger
possible.
- This change move the cleanup of ovs from,
tools/cleanup-contianers to tools/cleanup-hosts
TrivialFix
Change-Id: If2001130f4a2400555ce4d9ac5ee506482e4c25e
Our philosophy document is one of our most important documents
in he documentation repository. I appreciate in general the notion
of reorganizing many of our docs, but this one should be left alone
and possibly protected by a roll-call vote in the future.
This reverts commit aa517c4bf965f06dc9bcb20220d675ff6e77e94c.
Change-Id: Ic17861e823095a1891ac25ddaf429b66e352e30e
For centos, we should be using the RDO repositories to provide
rabbitmq-server. This version is updated with bug fixes and provides
a more stable experience then using rabbitmq.com builds.
Co-Authored-by: Jeffrey Zhang <zhang.lei.fly@gmail.com>
Co-Authored-by: Michal (inc0) Jastrzebski <inc007@gmail.com>
Closes-Bug: #1621460
Change-Id: Ib0eafc5da4397756fbdd837520b15543180ce229
In some part in the code we import objects. In the Openstack style
guidelines they recommend to import only modules.
http://docs.openstack.org/developer/hacking/#imports
Change-Id: I4b55cae8c2672f82025a95112b14d441d66f9d6d