Age | Commit message (Collapse) | Author | Files | Lines |
|
Guilin chart uses 7.0.0 version.
Issue-ID: OOM-2638
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I6a2816dd3870c2a8a0f578e2c7b86804d566dd75
(cherry picked from commit 18d4bd165e12cb4d03baa318e506f0dda381cd89)
|
|
Also update the pods to not use unlimited for the flavor
Change also includes traversal, graphadmin, data router
to be not using the root user
Issue-ID: AAI-3175
Issue-ID: AAI-3180
Change-Id: Ia2237c0ff8025bb2649ef381ae447e6d39961674
Signed-off-by: Harish Venkata Kajur <vk250x@att.com>
|
|
Issue-ID: AAI-3128
Issue-ID: SO-3216
Change-Id: Ibc8ff1dd31f42c3c17dc5491dbf56991c74e2785
Signed-off-by: Harish Venkata Kajur <vk250x@att.com>
|
|
This reverts:
b31e250091cd68edb77f3158691844decda82fc8
46961c4794a17f72643bd491af6c159ea7e53380
which are our main suspects for breaking testing in the master branch.
As this issue prevents many SO related patches from being merged let's
first revert those to make master work once again.
Issue-ID: SO-3216
Change-Id: I7f7daaaef3f7911afb5c8729c296773a630b5fb6
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
|
|
access
The problem is due to the fact in the data-router-oxm.xml file was referencing spring-context-4.2.xsd but it's not part of the spring-context-<xxx>.jar. Therefore, it needs to reach out to the internet to download the internet.
And in spring 5, it started to use versionless spring-context.xsd and it's part of spring-context-5.1.13.jar (which is packaged in data-router 1.6.2).
The fix is to update data-router-oxm.xml to use the versionless spring-context.xsd (and it's only accessible via https).
Change-Id: Icf62978b73ae097fc3bcbaf3e96a8f63706dc4fc
Signed-off-by: Prudence Au <prudence.au@amdocs.com>
Issue-ID: AAI-2958
|
|
Issue-ID: AAI-3017
Change-Id: If46a1bfafbd2edb73cd7d3832468c06fac855911
Signed-off-by: Harish Venkata Kajur <vk250x@att.com>
|
|
Issue-ID: OOM-2445
Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com>
Change-Id: I68624a283b9f3e0cb3f300defefd1ff0130a0b9c
|
|
Issue-ID: AAI-2580
Change-Id: Icd5f1a1b025defcc747cafa97bd65fd764392be6
Signed-off-by: Jimmy Forsyth <jf2512@att.com>
|
|
Use 6.0.0 in preparation for Frankfurt release
Issue-ID: OOM-2320
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I7280bb53c67230afd10483ac4a9b0508e47fb06b
|
|
Issue-ID: AAI-2766
Change-Id: I44d0be5e4009e5c712c098a95e4f2fc58c497ae9
Signed-off-by: Jimmy Forsyth <jf2512@att.com>
|
|
Issue-ID: AAI-2766
Change-Id: Ic87dee2d8d140ab8e58b86ed54a84ad8d690dbb3
Signed-off-by: Jimmy Forsyth <jf2512@att.com>
|
|
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: I450057f5b4a10842f09665ecccc58e4ed727cd89
|
|
Issue-ID: AAI-2763
Change-Id: Ie005febc51040e1dd7fffb104171ee1ee2ccdd98
Signed-off-by: Forsyth, James (jf2512) <jf2512@att.com>
|
|
Issue-ID: AAI-2727
Change-Id: I85fc2b830156e913abc845b91348990ff2127b20
Signed-off-by: Harish Venkata Kajur <vk250x@att.com>
|
|
so that the pod does die before it even had
a chance to start the application
Issue-ID: AAI-2727
Change-Id: I94246883cc5b46c7e9873e70214599653514d7d8
Signed-off-by: Harish Venkata Kajur <vk250x@att.com>
|
|
Issue-ID: AAI-2579
Signed-off-by: Jimmy Forsyth <jf2512@att.com>
Change-Id: Ib9939e7f84b933210c3fb3807235c1493b7197bc
|
|
Issue-ID: AAI-2558
Signed-off-by: Jimmy Forsyth <jf2512@att.com>
Change-Id: I06b4049b2e5c0bae734b4619abd6298a99ae2a11
|