Age | Commit message (Collapse) | Author | Files | Lines |
|
Workaround for retrieving ONAP root CA and keeping SO container being
run by no root user.
Issue-ID: SO-2730
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ib1b48c0a6fcca359a780640b8c705e75fd78dc1a
|
|
Use common secret template in so-sdnc-adapter component.
For now passwords are stil hardcoded but this will be removed in
further commits.
Issue-ID: OOM-2328
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I57c88fcdbaded8fc73fd066f39519be0eae3d670
|
|
Issue-ID: SO-1110
Signed-off-by: sunilb <sb00577584@techmahindra.com>
Change-Id: Ic468a1b28d681d14e862f4405890d996b42660f6
|
|
Here we have the ability to optionally disable AAF integration.
A global variable global.security.aaf.enabled=true
will turn on AAF security. with global.security.aaf.enabled=false
it will use spring.security to ensure backward compatibilty. updated
based on review comments
Issue-ID: SO-2452
Signed-off-by: Ramesh Parthasarathy(rp6768)<ramesh.parthasarathy@att.com>
Change-Id: Ia83622ad681cfd122ee906ccd1654b10b5e31fe4
|
|
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
|
|
If there are other inter-pod dependencies that should be
managed, please comment to let me know so they can be added.
Also addressed the missing globals section in the pods values.yaml
files and incorrect pull policy management to make them follow
the standard conventions
Change-Id: I3625f8452d90182391e1ff4af5fddfe9d0948a32
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-1472
|
|
Issue-ID: OOM-1145
Change-Id: I1510339a820802554b6e8b9a201619ef66be17a0
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
SO helm chart has been cleaned up and theseZ changes have been verified with SO rancher env
Change-Id: If6a26f5c346f77936aeaf4102341f14759714bf1
Issue-ID: SO-1073
Signed-off-by: Ramesh Parthasarathy(rp6768)<rp6768@att.com>
|
|
Certififacte has been added in the base docker image,
https://gerrit.onap.org/r/#/c/66209/ so no need to add it again.
Also, it was being mount at the wrong place.
Also, using latest docker images.
Change-Id: I55355dac9bfb2691f493317f77c0f363a78af7ee
Issue-ID: OOM-1407
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Issue-ID: OOM-1322
Change-Id: I5248ae206da6b5d65b0830f454813e6e14ec7284
Signed-off-by: vaibhav16dec <vaibhav.chopra@amdocs.com>
|
|
This check-in is an updated version of helm charts for so
containers based on review comments
Change-Id: I690430622ecbdcaf099a6165844142841db436dd
Issue-ID: SO-709
Signed-off-by: Ramesh Parthasarathy(rp6768)<rp6768@att.com>
|