5890ebf4f8
The current helm chart defaults drops logs of any warnings (and above) for any logger outside of the namespace of the deployed chart. This is a problem, as logging could reveal important information for operators. While this could be done with a value override, there is no reason to hide warning, errors, or critical information that are happening in the cycle of the operation of the software deployed with the helm charts. For example, nothing would get logged in oslo_service, which is a very important part of running OpenStack. This fixes it by logging to stdout all the warnings (and above) for OpenStack apps. Change-Id: I16f77f4cc64caf21b21c8519e6da34eaf5d31498
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-5 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.