config

History

Daniel Badea 09395bd525 Helm Cinder support multiple Ceph backends Currenty sysinv generates overrides only for default and backup Ceph pools. Adding a new Ceph storage backend does not make it available to stx-openstack application. Iterate all Ceph storage backend and create corresponding Ceph pool overrides which are then used by Cinder Helm chart to setup Cinder configuration and pool access. Change-Id: I2ca84406238e6c7462709822b303e25176fb9c8a Depends-On: I29c7d3ed118f4a6726f2ea887a165f256bc32fd5 Story: 2003909 Task: 30351 Signed-off-by: Daniel Badea <daniel.badea@windriver.com>		2019-06-24 12:35:08 +00:00
..
applications/stx-openstack/stx-openstack-helm	Helm Cinder support multiple Ceph backends	2019-06-24 12:35:08 +00:00
helm-charts	add helm chart for nginx ports control	2019-06-20 00:57:50 +00:00
platform/stx-platform/stx-platform-helm	Enable ceph-audit to run even if stx-openstack is not running	2019-06-03 15:46:00 -05:00
README	Enable StarlingX helm charts for stx-openstack app	2018-11-07 16:14:42 -05:00

README

The expected layout for this subdirectory is as follows:

kubernetes
|-- applications
|   `-- <application>
|       `-- <application>-helm RPM
|           `-- centos
|               `-- build_srpm.data
|               `-- <application>-helm.spec
|           `-- <application>-helm
|               `-- manifests
|                   `-- main-manifest.yaml
|                   `-- alt-manifest-1.yaml
|                   `-- ...
|                   `-- alt-manifest-N.yaml
|               `-- custom chart 1
|                   `-- Chart.yaml
|                   `-- ...
|               `-- ...
|               `-- custom chart N
|                   `-- Chart.yaml
|                   `-- ...
|-- helm-charts
|   `-- chart
|       `-- chart
`-- README

The idea is that all our custom helm charts that are common across applications
would go under "helm-charts". Each chart would get a subdirectory.

Custom applications would generally consist of one or more armada manifest
referencing multiple helm charts (both ours and upstream ones). The application
is packaged as an RPM. These application RPM are used to produce the build
artifacts (helm tarballs + armada manifests) but are not installed on the
system. These artifacts are extracted later for proper application packaging
with additional required metadata (TBD).

These applications would each get their own subdirectory under
"applications".