Age | Commit message (Collapse) | Author | Files | Lines |
|
Current repository templates handles only ONAP "nexus" repository
configuration.
So, all images coming from another repository (currently, OOM is using 4
repository, including nexus one) cannot simply be retrieved from another
one.
This commit add new templates, in a specific chart, in order to change
that.
Now, each for repository can be overidden and all 4 can have a
credentials.
Also, in order to minimize global variables, templates aimed to
retrieve usual utility images (busybox, envsubst, readiness, ...) are
created.
Issue-ID: OOM-2634
Change-Id: I27eb33d830d56ec28f9de68599f5108a262983b3
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
[Reduce code size, add missing busyboxRepository]
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
|
|
Signed-off-by: Jakub Latusek <j.latusek@samsung.com>
Change-Id: I9725eb1baf99f32d47f146dce2c61d3ae45ca0ab
Issue-ID: OOM-2562
|
|
Change-Id: I0f3278d513430ddf18abd3580a48f0d7a0bccc78
Signed-off-by: Jakub Latusek <j.latusek@samsung.com>
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
|
|
Issue-ID: OOM-1500
Change-Id: I15dd98ea8042914220f1b6025e93f65224bb9adb
Signed-off-by: sushil masal <sushil.masal@amdocs.com>
|
|
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>
|