When all mariadb nodes are stopped gracefully, mariadb galera will
write it's last executed position into the grastate.dat file. Need find
the node with largest seqno number in that file and recovery from that
node.
Closes-Bug: #1627717
Change-Id: I6e97c190eec99c966bffde0698f783e519ba14bd
* add serial for reconfigure
* set playbook serial by using variable
* fix serial for barbican, influxdb and vmtp
Closes-Bug: #1624607
Change-Id: I66530c7736e1673a592eddbde75637825d12d9e2
Change the argument for including images as part of destroy from '-e
destroy_include_images=yes' to a more consistent --include-images.
TrivialFix
Change-Id: I0a29c69121697cab751578093cc7ca58011eb853
- This change extends kolla-ansible
with a deploy-server command to enroll and deploy
physical servers with bifrost.
Change-Id: Iaa9f34b00e676569f6e3df679b7454b1ec0b8e34
Implements: blueprint bifrost-support
- This change addes the ability to deploy
and bootstrap bifrost.
- This change introduces a deploy-bifrost
command to kolla-ansible.
Change-Id: I62afcf348661add900c98904e90a15a0eddffd4b
Implements: blueprint bifrost-support
The cleanup command in the external API is a misnomer and should
be called destroy.
Change-Id: I083e80699e09bb24266ce1bf549772a5de92a49e
Closes-Bug: 1610364
All files used by kolla-ansible do not have a file ending.
keyfile was added as an anomoly. I noticed this during a review
that coolsvap had underway where he did a similar thing. I think
--key is fine.
TrivialFix
Change-Id: I99867a1a04a4dd881dcb2af39946122ea6b7d8a3
In order for the ansible configuration to be consumable,
we need to be able to generate it without deploying anything.
Change-Id: I2bbdd74d62d00f509a4fa5e4100906ed658d3974
Implements: blueprint generate-config
This playbook only matters for multinode since AIO can recover from
power outage without additional configuration.
DocImpact
Implements: blueprint mariadb-lights-out
Change-Id: I903c3bcd069af39814bcabcef37684b1f043391f
Working towards the blueprint that will add TLS protection
for the external endpoints, kolla needs certificates.
When kolla deploys OpenStack, the external VIP will need
a server side certifcate. Clients that access those endpoints will
need the public CA certificate that signed that certificate.
This ansible script will create these two certificates to make
it easy to use TLS in a test environment. The generated
certificate files are:
/etc/kolla/certificates/haproxy.pem (server side certificate)
/etc/kolla/certificates/haproxy-ca.pem (CA certificate)
The generated certificates are not suitable for use in a
production environment, but will be useful for testing and
verifying operations.
Partially-implements: blueprint ssl-kolla
Change-Id: I208777f9e5eee3bfb06810c7b18a2727beda234d
The gate currently doesn't provide any context when ansible fails. This
commit adds a new --verbose option to `kolla-ansible` that is passed to
`ansible-playbook`, and sets the default to -vvv for `kolla-ansible
deploy` in the gate.
TrivialFix
Change-Id: If248a4186b140e1ec0d2e787c27481cec7e81eec
Remove the '..' in the path like:
/home/jenkins/workspace/gate-kolla-dsvm-deploy-centos-binary/tools/../ansible/inventory/all-in-one
TrivialFix
Change-Id: I80724a9e876ed1826c65e08b55cfa08124d70eb9
The passed keyfile path is used to decrypt the passwords.yml
which encrypted by the ansible vault.
Partially-Implements: blueprint encrypt-sensitive-info
DocImpact
Change-Id: Ifaebf464478cde99e896c13b375cfaf9282ee576
we can deploy specific services by using tags feature. It is very
useful, especially in develop/test stage.
TrivaiFix
Change-Id: I21cc55e6f1a32a5c57570bc2c2fb9b084e513af8
pip install default prefix in Ubuntu is /usr/local, and Kolla tools scripts
didnt respect that. So I added few OS checks in this scripts.
I improve config path check in build.py. Added more verbose error if we can't
find config directory.
Change-Id: Ide521ed205b0dc1fc27e237a9a8f4da0168e664f
Closes-Bug: #1512302
This is a quick hack to get kolla-ansible working with pip installed
kolla, kolla-ansible will need to be rewritten at some point in python.
Closes-Bug: #1495797
Change-Id: I7cf8c4baae76ff8f31514f64bed934848a1c3e40
The purpose for having defaults.yml on the command line was originally
for variable inheritance. Over the past month we have slowly changed
how things are inherited (like ports) allowing us to place these
'defaults' into the group_vars/all.yml location as they should be
values that go unchanged (but can be overridden).
Change-Id: I2becec66bf431bfc9d88fc825b5380c1e173ca70
Partially-Implements: blueprint update-configs