openstack
/
openstack-helm
Code Issues Proposed changes
openstack-helm/rally
History
Jiří Suchomel a2a5dda47c Added volume related keys to pod mounts to ease the overriding 
If user wants to add an extra volumeMounts/volume to a pod,
amd uses override values e.g. like this

pod:
  mounts:
    nova_placement:
      init_container: null
      nova_placement:
        volumeMounts:
          - name: nova-etc
          ...

helm template parser complains with

Warning: The destination item 'nova_placement' is a table and ignoring the source 'nova_placement' as it has a non-table value of: <nil>

So when we create empty values for such keys in values.yaml, the source
will be present and warning does not need to be shown.

Change-Id: Ib8dc53c3a54e12014025de8fafe16fbe9721c0da
 		2019-03-15 16:29:19 +00:00
..
templates Upgrade rally to 1.3.0 2018-12-20 00:22:49 +00:00
Chart.yaml Revert "Update OSH Author copyrights to OSF" 2018-08-28 17:25:13 +00:00
README.rst Add Rally Chart 2017-10-05 09:19:49 -05:00
requirements.yaml Revert "Update OSH Author copyrights to OSF" 2018-08-28 17:25:13 +00:00
values.yaml Added volume related keys to pod mounts to ease the overriding 2019-03-15 16:29:19 +00:00

README.rst

Rally

This chart provides a benchmarking tool for OpenStack services that allows us to test our cloud at scale. This chart leverages the Kolla image for Rally and includes a templated configuration file that allows configuration overrides similar to other charts in OpenStack-Helm. You can choose which services to benchmark by changing the services listed in the values.yaml file under the enabled_tests key.

Installation

This chart can be deployed by running the following command:

::

helm install --name=rally ./rally --namespace=openstack

This will install Rally into your cluster appropriately. When you run this install command, the chart will bring up a few jobs that will complete the benchmarking of the OpenStack services that you have specified.