Repository for OpenStack Helm infrastructure-related code
85208fe98a
This moves the ldap chart to openstack-helm-infra from openstack-helm, allowing for ldap to provide an authentication mechanism for components of the LMA stack, and can still be used for keystone in openstack-helm, as openstack-helm-infra is a required project Change-Id: I211bc47c7a3ae875614102c8f64daa1099f702e8 |
||
---|---|---|
calico | ||
elasticsearch | ||
flannel | ||
fluent-logging | ||
grafana | ||
helm-toolkit | ||
kibana | ||
kube-dns | ||
ldap | ||
nagios | ||
nfs-provisioner | ||
playbooks | ||
prometheus | ||
prometheus-alertmanager | ||
prometheus-kube-state-metrics | ||
prometheus-node-exporter | ||
prometheus-openstack-exporter | ||
redis | ||
registry | ||
roles | ||
tiller | ||
tools | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
Makefile | ||
README.rst |
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
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. Any bugs or blueprints filed in the OpenStack-Helm-Infra Launchpad will be closed and requests will be made to file them in the appropriate location.