c357733d71
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
56 lines
1.2 KiB
YAML
56 lines
1.2 KiB
YAML
---
|
|
schema: armada/Manifest/v1
|
|
metadata:
|
|
schema: metadata/Document/v1
|
|
name: full-site
|
|
layeringDefinition:
|
|
abstract: false
|
|
layer: global
|
|
labels:
|
|
name: full-site-global
|
|
storagePolicy: cleartext
|
|
data:
|
|
release_prefix: airship
|
|
chart_groups:
|
|
- podsecuritypolicy
|
|
- kubernetes-proxy
|
|
- kubernetes-container-networking
|
|
- kubernetes-dns
|
|
- kubernetes-etcd
|
|
- kubernetes-haproxy
|
|
- kubernetes-core
|
|
- ingress-kube-system
|
|
- ucp-ceph-update
|
|
- ucp-ceph-config
|
|
- ucp-core
|
|
- ucp-keystone
|
|
- ucp-divingbell
|
|
- ucp-armada
|
|
- ucp-deckhand
|
|
- ucp-drydock-scaled
|
|
- ucp-promenade
|
|
- ucp-shipyard
|
|
- ucp-prometheus-openstack-exporter
|
|
- osh-infra-ingress-controller
|
|
- osh-infra-ceph-config
|
|
- osh-infra-radosgw
|
|
- osh-infra-logging
|
|
- osh-infra-monitoring
|
|
- osh-infra-mariadb
|
|
- osh-infra-dashboards
|
|
- openstack-ingress-controller
|
|
- openstack-ceph-config
|
|
- openstack-tenant-ceph
|
|
- openstack-mariadb
|
|
- openstack-rabbitmq
|
|
- openstack-memcached
|
|
- openstack-keystone
|
|
- openstack-radosgw
|
|
- openstack-glance
|
|
- openstack-cinder
|
|
- openstack-compute-kit
|
|
- openstack-heat
|
|
- osh-infra-prometheus-openstack-exporter
|
|
- openstack-horizon
|
|
...
|