This is only for the Neutron thin containers. The Neutron agents
are still in a fat container. I'll replace in another patch.
Change-Id: I8533af52bfa3f268aa8ffb1c16ae49f5a300da27
Partially-Implements: blueprint replace-config-external
VIP takes time (10-30 seconds) to appear on one of network nodes.
Ansible does not wait for the VIP and starts keystone. The latter
fails because it cannot connect to database thru the VIP.
Change-Id: Ie951ee22565bdbe8ccb68522648758a7174ba156
Closes-Bug: #1494253
First keepalived container is started with priority 0 but the
latter should be in range 1-255. This gives error and keepalived
resumes with default priority 100.
Change-Id: Ib11d0072a96b818d86c81a32e78118c0c82b74d8
Closes-Bug: #1494237
Libvirt shuts down existing virtual machines. To solve this problem,
the /var/lib/libvirt directory needs to be persisted. By persisting
this directory in the nova data container, libvirt can communicate
with the sockets setup by the previous data container.
Change-Id: I362c533f8493984123686fe6e3f8e43d97434ca6
Closes-Bug: #1494060
Make nova-libvirt and nova-compute use a data container called
nova_data. This data container contains /var/lib/nova/instances
data so upgrades to nova-compute work properly.
Change-Id: I89362eb0857f7b07503c35178475bc91d0d19ca8
Closes-Bug: #1486333
Stagger the start times of the rabbitmq daemon so rabbitmq neither
crashes and also properly forms a cluster. This problem exists in
the latest rabbitmq 3.5.4 available on rabbitmq.com for download.
Change-Id: Iac4186b3c3b586de38467294399c7ed9415244de
Closes-Bug: #1490780
Swift replicator services require rsync to function. This patch adds a
new container which is included automatically on each of the Swift
storage nodes.
Change-Id: If10fbe610ca4df21ef0f2c7a1025035d627cb4ba
Partial-Bug: #1477993
Haproxy needs to have gathered facts from all hosts that it will use
information about. In this case it must talk to all of the api hosts
as well as the database and rabbitmq hosts before generating the
configuration file.
Change-Id: I99b7dbebd5a6193e192ee258ddf576d18db90ed7
Closes-Bug: #1482406
Deploy the core services for murano-api and murano-engine containers.
Implements: bp ansible-murano
Change-Id: Ibcc618665a3509465ba8f9249a417e8848087eef
The stack-create operation fails. The current implementation of
Heat Ansible role does not implement trusts. Tell heat it should use
the non-trusts authentication model.
Also add a [keystone_clients] section which is required in newer
versions of heat to properly resolve the keystone v3 API endpoint
required for trust communication.
This fix spawns a Tech-Debt Bug to implement trusts in heat: #1492736
Change-Id: I06dd6436cc34a37b4966fddc888fade982ea51bd
Closes-Bug: #1492648
The default incoming database connection count is limited to 151
connections. These are not sufficient in a 100 node 3 controller
deployment to launch several heat stacks simulatenously.
Data measured on bare metal shows that 250 connections are needed
to launch one 25 VM heat stack with 3 controller nodes with 209
tasks (default enablement).
Change-Id: If60b540010d6d173a393fa91fa30cb3ba572cfc0
Closes-Bug: #1492719
Currently bootstrap containers are waited to exit but are not
checked for exit status and ansible runs further tasks. If
bootstrapping fails we notice it at much later time.
Change-Id: I137fc11b0f9d1f03d2ded08a213e8dbd62741f92
Closes-Bug: #1492337
Default value for auth_strategy changed for Cinder in Liberty
release from 'noauth' to 'keystone'. Therefore relying on
default value makes Cinder fail in Kilo. This patch covers
both releases by setting auth strategy to 'keystone' explicitely
Change-Id: Ic1f45fd43e0a94ca1dbfc63e90e2756c40453352
Closes-Bug: #1492233
The register operation was using database_user which is also a global
variable in group_vars/all.yml. This results in Heat being undeployable
because database_user is overwritten.
Change-Id: I78b2db34b7c99142040390c7258b7e81d3770835
Closes-bug: #1491980
When running register task for MariaDB we should firstly check
if operation failed before trying to parse result from json output
Change-Id: Ic331ec20990277d30b147826ff24affb27d52383
Closes-Bug: #1491751
If a bootstrap fails at some stage and leaves a rabbitmq_data
container on a host, it will not bootstrap again and rabbitmq
fails to start due to root permissions on /var/lib/rabbitmq.
This patch improves the check for a valid, existing
rabbitmq_data
Closes-Bug: #1490602
Change-Id: I6a00aaef38b4ab6a60dcfb5ed2f808513b9f8c84
Nova-compute is curerntly generating a backtrace when trying to nova
boot a VM. The backtrace is described in the bug log. Bind-mounting
/sys/fs/cgroup:/sys/fs/cgroup in the libvirt container resolves the
problem.
Change-Id: I5a56b61fd260728fb76e19bcbdf403b80a4ec5a6
Closes-Bug: #1490326
Initially it did not use this client due to the fact that the client
didn't seem to want to work in the containers. Now it works fine and
it should be used instead of the deprecated keystone client
Change-Id: Ib0e172c677e200e5df01c478b7ea257b30c0df0b
Closes-Bug: #1490126
