config

History

chengli3 822b99c016 Support ovs in container As stx cutovers to containerization, most openstack components run in containers, but ovs-dpdk running on the host. This patch is to support ovs running in container, and make it the default setting. We still support running ovs-dpdk on the host. For option ovs-dpdk on the host, run follow command before unlock. ``` system modify --vswitch_type ovs-dpdk ``` Change-Id: I111865de17fc82a1e7c269fb97f53a181fb382b2 Story: 2004649 Task: 28610 Co-authored-by: Huifeng Le <huifeng.le@intel.com> Signed-off-by: chengli3 <cheng1.li@intel.com>		2019-03-27 10:05:07 +08:00
..
applications/stx-openstack/stx-openstack-helm	Support ovs in container	2019-03-27 10:05:07 +08: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".