4af3091c15
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> |
||
---|---|---|
.. | ||
applications/stx-openstack/stx-openstack-helm | ||
helm-charts | ||
platform/stx-platform/stx-platform-helm | ||
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".