b72f3d0f3c
OpenStack services already moved to use policy in code. No need to have policy file at this point, at least no need to put default policy rule to policy.yaml file anymore. To put in duplicate rules, will cause unnecessay logs and process. Also not healthy for policy in code maintain as the `default` rules in openstack-helm might override actual default rules in code which we might not even mean to change it at all. Change-Id: I29ea57aa80444ed64673818e597c9ca346ba7b2f
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 IRC: #openstack-helm on oftc
- Community IRC Meetings: [Every Tuesday @ 1500 UTC], #openstack-helm in IRC (OFTC)
- Meeting Agenda Items: Agenda
- Join us on Slack
- #openstack-helm
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 minikube based all-in-one solution that runs in a Docker container. The 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.
Contributing
We welcome contributions. Check out this document if you would like to get involved.