Age | Commit message (Collapse) | Author | Files | Lines |
|
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 the dummy password values to OBF: so that the properties files
will load correctly at application start-up.
Change-Id: I1903026ca57db460c41163e1f7dc42a02fd3c2e2
Issue-ID: AAI-2110
Signed-off-by: Leonard, Mark (ml401d) <ml401d@att.com>
|
|
OOM has now templates in order to create the needed PVC, using:
* a PV with a specific class when using a common nfs mount path between
nodes (sames as today use) --> is the default behavior today
* or a storage class if we want to use dynamic PV.
On this case, we use (in order of priority):
- persistence.storageClassOverride if set on the chart
- global.persistence.storageClass if set globally
- persistence.storageClass if set on the chart
I've also created a PV/PVC couple for logs of ES as it was hardcoded in
the deployment.
Change-Id: Ic2da694da008803f5afc1a0e0de38a1428c5b40e
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: OOM-2184
Change-Id: I75f7e8239fe1f1027fffae6b3e2a848a593351ae
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
|
|
Data Router pods writes logs directly in the PVC within generic name
files:
debian@control01-onap-master:~$ ls -l /dockerdata-nfs/onap-pomba/pomba/data-router/logs/application.log
-rw-r--r-- 1 root root 125 Nov 5 09:56 /dockerdata-nfs/onap-pomba/pomba/data-router/logs/application.log
debian@control01-onap-master:~$ ls -l /dockerdata-nfs/onap-pomba/pomba/data-router/logs/
total 4
drwxr-xr-x 2 root root 76 Nov 5 09:56 AAI-DR
-rw-r--r-- 1 root root 125 Nov 5 09:56 application.log
drwxr-xr-x 3 root root 18 Nov 5 09:54 data-router
debian@control01-onap-master:~$ ls -l /dockerdata-nfs/onap-pomba/pomba/data-router/logs/data-router/
total 0
drwxrwxrwx 2 root root 6 Nov 5 09:54 logs
debian@control01-onap-master:~$ ls -l /dockerdata-nfs/onap-pomba/pomba/data-router/logs/data-router/logs/
total 0
debian@control01-onap-master:~$ ls -l /dockerdata-nfs/onap-pomba/pomba/data-router/logs/AAI-DR/
total 12
-rw-r--r-- 1 root root 0 Nov 5 09:56 audit.log
-rw-r--r-- 1 root root 0 Nov 5 09:56 debug.log
-rw-r--r-- 1 root root 7519 Nov 5 09:56 error.log
-rw-r--r-- 1 root root 666 Nov 5 09:56 metrics.log
Thus if two pods were writing, there would be issue as each one would
want to write.
Then this PVC must be used by one POD only and RWO is sufficent
Change-Id: I0087487fba715b4b0804de51544238f08fed1d3c
Issue-ID: LOG-1114
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Elasticsearch PVC is only used by elasticsearch POD. As ES doesn't
support several writes per different instances on the same folder, RWO
PVC is sufficient.
Change-Id: I6b7c91174f4f485dc6e3b6e34111fe4fc2bb0469
Issue-ID: LOG-1114
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: LOG-1120
Signed-off-by: Prudence Au <prudence.au@amdocs.com>
Change-Id: Ie4621751739a3bab67f6ad928aa124d8328a4455
|
|
Updating all helm chart versions to 5.0.0 for the El Alto release.
Merge will be co-ordinated with the merge of a separate aai/oom patch.
Please do not merge until this coordination has completed.
Issue-ID: OOM-1980
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
Change-Id: I31daaeb |