Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Jakub Latusek <j.latusek@samsung.com>
Change-Id: I9725eb1baf99f32d47f146dce2c61d3ae45ca0ab
Issue-ID: OOM-2562
|
|
ONAP is too big to be deployed using helm install so we need to
use a custom helm plugin helm deploy. This script deloys onap
component by component instead of deploying evrything at
once. Unfortunately this script also modifies the helm release by
appending component name to it.
As a result of this behavior our objects are called for example:
onap-mariadb-galera-mariadb-galera-0
instead of just being called onap-mariadb-galera-0.
This patch simplifies this naming convention by replacing all direct
usages of .Release.Name with common.release macro which strips the
component specific part from the release name.
Issue-ID: OOM-2275
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: Ia8cead50d305adb00eef666d0a1ace74479b5183
|
|
Change-Id: I2d1ff878c215becc9856af184eb0b11defd75e1d
Issue-ID: OOM-1064
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
This change provides a single centralized location
(onap parent chart) to change/install secrets, persistent
volumes, service account(s), RBAC and configuration
overrides. It also eliminates the need for a 2-step install
of setup and application charts.
Users would customize the onap parent chart to install both
the deployment-specific resources and one or more "enabled"
sub charts, using a command like the following:
helm install local/onap -f dev.yaml
where dev.yaml (or prod.yaml, etc.) provides the customization
of application subcharts to deploy.
Change-Id: Idbef28ffa404ea35922a4c3994605bdc27f3471e
Issue-ID: OOM-817
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|