The intention for the patch is to increase the stability of
OpenStack installation:
1. Use a single RabbitMQ cluster for all OpenStack services.
2. Use 2 replicas for RabbitMQ clusters instead of 3; RabbitMQ
does not implement a quorum mechanism which allows us to have
even number of nodes, this should provide better performance
by reducing the number of instances where the data should be
replicated. This should also reduce the odds of getting
RabbitMQ partitioning.
Co-authored-by: Drew Walters <andrew.walters@att.com>
Change-Id: Id981e2650efc24a9e67cf87a0abd414a96f40088
Added service specific version of helm toolkit for all OSH services
in treasuremap global chart and version definitions. Kept the current
version of htk for all services to limit the changes in this commit.
Change-Id: I35cf8fce32f1e414aebd284054feb36f8305b628
Add name and component labels to the memcached, ceph-config charts and
horizon charts and ucp chart groups in the global so they can be
referenced by customized sites.
Change-Id: I54aad9582841fc2d91a103aeb28b162660bd1b0f
This modifies the RabbitMQ Armada charts to wait specifically
for the RabbitMQ StatefulSets to complete prior to proceeding.
This is more robust than the default Pod waiting, as Pod waiting
for SS's has a race condition such that all Pods are likely
Running and Ready prior to any action having been taken, during
and upgrade scenario.
This change leverages recent Armada resource-based wait functionality.
Change-Id: I3867ce6966047d6b877a9bfa872defc0eda9693a
This adapts manifests to be in line of using git reference
for refering to global/secrets repos instead of versioned folders.
Change-Id: I0100fb90666e335bd99d304b3804c180b25a9d16
Depends-On: https://review.openstack.org/#/c/577886/