d467d685a3
It was observed that when increasing amount of conductor workers from default "1" to higher value the readiness probe fails to check rabbitmq connections for conductor processes - it happens since the script is trying to obtain rabbitmq connections for parent conductor process which in case of workers>1 doesn`t open rabbit connections but spawns child processes which handle rabbitmq connections instead. This patch removes the "check-all-pids" option, keeps the logic but simplifies and fastens he code - instead of checking all processes when "check-all-pids" option was set (however regardless of "sock_count value" if only one process opens connection the check returns positive result) processes will be checked one-by-one until the first one with open rabbitmq connection(s) is found. Change-Id: I72be0bbdefcba77a55b6ceed6e192c9621c069eb
OpenStack-Helm
Mission
The goal of OpenStack-Helm is to provide a collection of Helm charts that simply, resiliently, and flexibly deploy OpenStack and related services on Kubernetes.
Communication
- Join us on Slack - #openstack-helm
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-4 on freenode
- Meeting Agenda Items: Agenda
Storyboard
Bugs and enhancements are tracked via OpenStack-Helm's Storyboard.
Installation and Development
Please review our documentation. For quick installation, evaluation, and convenience, we have a kubeadm based all-in-one solution that runs in a Docker container. The Kubeadm-AIO set up can be found here.
This project is under active development. We encourage anyone interested in OpenStack-Helm to review our Installation documentation. Feel free to ask questions or check out our current Storyboard backlog.
To evaluate a multinode installation, follow the Bare Metal install guide.
Repository
Developers wishing to work on the OpenStack-Helm project should always base their work on the latest code, available from the OpenStack-Helm git repository.