Matthew Heler 6e8c289c13 Add failure domains, and device classes for custom CRUSH rules
Largely inspired and taken from Kranthi's PS.

 - Add support for creating custom CRUSH rules based off of failure
domains and device classes (ssd & hdd)
- Basic logic around the PG calculator to autodetect the number of
OSDs globally and per device class (required when using custom crush
rules that specify device classes).

Change-Id: I13a6f5eb21494746c2b77e340e8d0dcb0d81a591
2018-11-27 09:37:30 -06:00
2018-10-05 16:18:51 +00:00
2018-10-15 13:50:50 +00:00
2018-10-25 06:21:01 +00:00
2018-11-09 13:28:50 -06:00
2018-10-29 15:10:35 +00:00
2018-09-25 18:14:49 +00:00
2018-11-09 22:57:50 +00:00
2018-10-22 10:50:02 +02:00
2017-06-20 08:49:42 +00:00
2018-08-28 09:39:41 -04:00
2018-05-15 13:04:28 -05:00
2018-05-15 13:04:28 -05:00
2018-10-05 16:19:35 +00:00

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.

Description
Helm charts for deploying OpenStack on Kubernetes
Readme 127 MiB
Languages
Smarty 82.1%
Shell 16%
Python 1.4%
Jinja 0.3%
Makefile 0.2%