c30935ca08
This outlines the foundation for a logging, monitoring and alerting platform for openstack-helm. It should result in a path forward for the technical requirements and the proper default configurations to provide operational benefits The goal is to gain feedback and consensus on the path forward for these services Change-Id: I069c2ad860d265fab8155972b19a71021685f2ce
OpenStack-Helm
Mission
The goal of OpenStack-Helm is to enable deployment, maintenance, and upgrading of loosely coupled OpenStack services and their dependencies individually or as part of complex environments.
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
Launchpad
Bugs and blueprints are tracked via OpenStack-Helm's Launchpad.
Installation and Development
Please review our documentation at Read the Docs. 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, and the gate scripts, use are supported on any fresh Ubuntu, CentOS or Fedora machine.
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 Issues and Bugs.
To evaluate a multinode installation, follow the Bare Metal install guide.