config

History

marvin 4af3091c15 Change rpc_response_max_timeout default to 60 seconds In stx.1.0, stx-neutron hard-coded the rpc_response_max_timeout value to 60 seconds. With the migration to containers and upstream neutron, the default is now set to 600 seconds. To align with the previous starlingx behavior, the rpc_response_max_timeout set to 60 seconds by the system through a neutron helm override. Change-Id: Ibf0f591ac9cb05dac09add37b3c31f6f5b66446d Closes-Bug: #1836413 Signed-off-by: marvin <weifei.yu@intel.com>		2019-07-18 00:40:56 +00:00
..
applications/stx-openstack/stx-openstack-helm	Change rpc_response_max_timeout default to 60 seconds	2019-07-18 00:40:56 +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".