starlingx/config
Code Issues Proposed changes
96ecfd2542
config/kubernetes
History
Gerry Kopec 7c27a88386 nova overrides: set long rpc timeout and cpu_mode 
long_rpc_timeout: timeout for long running live migration tasks
  Setting to 400s.  This is reduced from the nova default of 1800s to
  give a more timely response and is based on an old custom patch to
  stx-nova where we allowed pre_live_migration to take 300s (if block
  migration) + 6s * number of vifs.
libvirt/cpu_mode: set to host-model so guest can closely match host

Story: 2003909
Task: 30059
Change-Id: Iab26aa7143697e21678eecfb3f3e161a6e0a786c
Signed-off-by: Gerry Kopec <Gerry.Kopec@windriver.com>
2019-07-09 16:01:18 -04:00
..
applications/stx-openstack/stx-openstack-helm nova overrides: set long rpc timeout and cpu_mode 2019-07-09 16:01:18 -04: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".