config

History

Al Bailey 609d84d846 Remove magnum from baremetal. Magnum is no longer packaged on bare metal. The sysinv and upgrades code related to magnum has been removed. The helm configuration for magnum remains, although it is not currently supported in containers either. The magnum-ui is not installed in platform or containerized horizon so the code to enable it is removed. Some upgrade code remains, due to the fact that that utility is in the process of being re-written. Story: 2004764 Task: 34333 Change-Id: I56873b4e04aac2e7d0cd57909beea00ecc2c1b9a Signed-off-by: Al Bailey <Al.Bailey@windriver.com>		2019-06-27 11:57:09 -05:00
..
applications/stx-openstack/stx-openstack-helm	Remove magnum from baremetal.	2019-06-27 11:57:09 -05: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".