3d6557279f
Due to Python's GIL [1], we can't use multiple threads for running OpenStack services without a performance penalty, since the execution ends up serialized, which defeats the purpose. Instead, we should use several processes, since this approach doesn't have this limitation. [1] https://wiki.python.org/moin/GlobalInterpreterLock This patch updates processes and threads accordingly for: aodh panko nova Related issue was fixed in different deployment tools like puppet https://bugs.launchpad.net/puppet-keystone/+bug/1602530 Change-Id: Ia8eb4a1f3ed826e206edb94c680f40bcec44e9d7
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.