config

History

Kevin Smith bc7f16ca7c Neutron Router Rebalancing on L3 Agents Turn off router_auto_schedule so as not to conflict with router reschedule/rebalance. Change-Id: I710a698ebb31d48060903fb3966fa379b56ad190 Story: 2003857 Task: 30115 Signed-off-by: Kevin Smith <kevin.smith@windriver.com>		2019-03-20 15:36:33 -04:00
..
applications/stx-openstack/stx-openstack-helm	Neutron Router Rebalancing on L3 Agents	2019-03-20 15:36:33 -04:00
helm-charts	Fix the dependencies in the ceph-pools-audit chart	2019-03-12 23:15:45 -04: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".