This PS names all the heat engine "heat-engine" by default. This should
make the number of dead engines simple to manage following updates.
Change-Id: I369d96c2269a0dbff5c88840f56c921bd389ae27
a) The db-init method ignores the configured admin password.
This seems to work if db-init was scheduled to the same host as
postgresql is running on but fails on a remote connection. This change
sets the PGPASSWORD variable to the provided admin password.
b) Fixed liveness and readiness probe for postgresql
While this seems to work it continously outputs the message
"psql: FATAL: role "root" does not exist"
This change adds the admin username as argument to pg_isready
to stop this message.
Update: Making the linter happy ;-)
Change-Id: I59b47a8724065d08203c29172c15350aaa785203
Closes-Bug: #1749177
This PS moves the DNS nameservers used in the smoketest heat
template to use the k8s DNS on the dev host.
Change-Id: I3a5f9eb2689f01ee2ef216843b80fbe2607eb5bc
Use a utility container for ipcalc on all platforms; this avoids
having to find the package on platforms where it's not easily
available and we avoid argument differences.
Change-Id: I6c6e719f8eeb8d4214ebb0111e9d8f8b659db396
This PS moves to use a lightweight libvirt 1.3.1 image based on
ubuntu xenial for used with newton openstack.
Change-Id: I99f64bba7aca3896fc3d32884c3e6f59ff088f79
This PS spring cleans the memcached chart to reflect the advances
in OSH style. It also updates the image used to the current
supported version.
Change-Id: Iaeb14e9dd169f009916e64b0c91f2581e64afbca
This PS moves the default image in OSH for most services to use LOCI
and also provides a Kolla gate for newton openstack.
Change-Id: Ice6cb9f89bc3ce6e8280e580d215aedda9e71904
This PS sets the ownership of the co-ordination backend location
when using the default file backend. This does not make the service
functional but prevents errors when calling it.
Change-Id: I2b05bc728fef84e404f9a03a5316cd122f246bce
This PS sets the ownership of the co-ordination backend location
when using the default file backend. This does not make the service
functional but prevents fatal errors when loading it.
Change-Id: I69a0838469f889172fb061f0adea34ca11d9c8c3
This PS moves the cleaning net managment to a job.
Additionally the gate scripts are updated to enable single node
operation for development use.
Change-Id: Icb7015bcceaf93bc65f60399caf785fbdcf72413
Adds "helm-toolkit.utils.merge" which is a replacement for the
upstream sprig "merge" function which didn't quite do what we
wanted, specifically it didn't merge slices, it just overrode
one with the other.
Change-Id: I6402ffe043c75eb3a63797ef1be5b56f35b0adc4
When helm crashes/fails it can leave tmpcharts directories behind;
update the 'clean' target to remove these.
Change-Id: Ib0fb6e93262fbc6fd97dfdd491df46283dff4a9e
This PS extends the host targeting utility to create daemonsets
for storage focused charts. This PS supports both block device
and bind mount backed journals and OSDs.
Change-Id: Id90b197ba3e4f383eea7ce6137ed77b3ef4e5625
Previously, the ceph version was checked with "ceph -v".
However, this way is only check for the ceph client version.
So I change the way to check the ceph osd version.
Change-Id: I11f44186f671594e6e9e848f3fddb1d23b994b36
* Changed podManagementPolicy to parallel in order to allow recovery
from secondary or third master
After rebooting the whole cluster on purpose or after a power failure
a primary node the cluster can synchronize with is required. This is
usually done automatically by selecting the node with the highest
transaction id. The current implementation of the stateful set starts
the nodes in sequence, preventing the start of further nodes if the
process terminates with error state. Because of this, the cluster may
not come up if the first or second node are not in primary state.
* Elects first node started in primary state as bootstrap source.
* Display warnings and runs mysqld with wsrep-recover on crashed nodes
* Introduces FORCE_RECOVERY argument for crash recovery
In case the primary selection failed, the cluster bootstrap process
must be manually initiated from the most advanced node (highest
committed transaction id). This information is available from the
grastate.dat file in case of a clean shutdown. On crashed nodes an
InnoDB recovery is required to get the last committed transaction id.
start.sh will handle both cases and gives instructions on how to
recover the cluster on a hard failure. If FORCE_RECOVERY was set to
the name of a POD (mariadb-0, mariadb-1, ...), the bootstrap process
will be initiated from the specified node.
DocImpact
Closes-Bug: #1716461
Change-Id: I96a8cb52124f64920a7d9cf21a8924ede78ebf7b
This enables prometheus monitoring for rabbitmq and mariadb in
the armada gate, as the armada gate has deployed prometheus and
can be used to verify functionality
Change-Id: I219a93e934d19470f16fa319df8c3c0d86608416
kubernetes does clustering for us and with persistent robust PVs
clustering of mariadb isn't useful for most people by default
Change-Id: I460c00c141ffe7d93af5ec09d1599cb8eaa9dcf7
