da7bc575ec
This introduces a mechanism for generating the logging.conf file for the openstack services via the values. This allows us to define loggers, handlers, and formatters for the services and the modules they're composed of. This also allows us to take advantage of the oslo fluent handler and formatter. The fluent handler and formatter give us the following benefits: sending logs directly to fluentd instead of routed to stdout/stderr and then through fluentbit to fluentd, project specific tags on the logged events (enables us to define more robust filters in fluentd for aggregation if required), full traceback support, and additional metadata (modules that created logged event, etc) Depends-On: https://review.openstack.org/577796 Change-Id: I63340ce6b03191d93a74d9ac6947f0b49b8a1a39
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.