config

History

Angie Wang 6e029f2a63 Update stx branding in horizon local_settings In the commit https://review.openstack.org/#/c/623231/, the stx branding was moved from stx-horizon to stx-gui and renamed from "titanium" to "starlingx". This updates the horizon local_settings in aramda manifests to search for "starlingx" themes in order to bring up the containerized horizon. Change-Id: I4eec0a19d808398cce4f7ec14fb93d188a9aac5a Story: 2004520 Task: 28529 Signed-off-by: Angie Wang <angie.wang@windriver.com>		2018-12-16 15:01:53 -05:00
..
applications/stx-openstack/stx-openstack-helm	Update stx branding in horizon local_settings	2018-12-16 15:01:53 -05:00
helm-charts/rbd-provisioner	Enhancements for the rbd-provisioner helm chart	2018-12-13 19:13:15 +00: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".