Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
Add ingress configuration file for so-monitoring component.
Ingress configuration can be changed in onap-all.yaml
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: I122e52fc1ed9db78bb0249715e8cd25a9d6318a3
Issue-ID: OOM-1508
|
|
Issue-ID: OOM-1772
Change-Id: If206ae7cc2f4273889376e1bb3fa77bacfaae3cc
Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
|
|
|
|
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
|
|
It is assumed that all the external interfaces will go thru MSB
and internal interfaces will use kube dns
Change-Id: Ieb51f315e8a64af6986cd5f001d1713562154b09
Issue-ID: SO-1104
Signed-off-by: Ramesh Parthasarathy(rp6768)<ramesh.parthasarathy@att.com>
|
|
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-1412
Change-Id: Ie6abd2569fd2a987fb2b7469381f23bfac099445
Signed-off-by: vaibhavjayas <vaibhav.jayas@amdocs.com>
|
|
All SO override files are updated with correct kube dns address for inter application communications based on review comments
Change-Id: I6e1487f3d5a7db49df3e40fb41b6b148aacfee8d
Issue-ID: SO-1022
Signed-off-by: Ramesh Parthasarathy(rp6768)<rp6768@att.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>
|
|
Issue-ID: OOM-1068
Change-Id: I7ff15fa9eb6c29852c089ad10e0c63faba05fe00
Signed-off-by: Brian Freeman <bf1936@att.com>
|
|
The presence of these disrupts the SO boot process resulting in
the misconfiguration found by the defect
Issue-ID: OOM-1052
Change-Id: I527698c6ccbdd42b3435ca33dc97cb09da7afd97
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Swapping out aai.crt for onap-ca.crt.
Change-Id: I4537fcc02c17ed19a0b3c5fa3581037c9999dd5c
Issue-ID: OOM-1068
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
-cloning project files during pod init-phase
-injecting SQL through a shared volume
Issue-ID: OOM-858
Change-Id: Idc845910d5386c3228fb9a557fb3238823242cea
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Aligned service names (and numerous other minor fixes) with latest best practices
and standard templates.
Change-Id: I740fe299053805df60abcd6a6043031d8beda7e8
Issue-ID: OOM-909
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Change-Id: Ia742842cf1878c5786f71949013ed8afedd13c39
Issue-ID: OOM-909
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
updated the endpoints and service in a single namespace onap deployment prospective
updated the parameters order for the image source to allow override
Issue-ID: OOM-743
Change-Id: I6a379ec4661d465f95478b383d60c3b2eecc0f72
Signed-off-by: Jerome Doucerain <jerome.doucerain@bell.ca>
|
|
Issue-ID: OOM-821
Change-Id: I627ac962afe8cd6bf2859a30a0e88f6c9ac89d34
Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
|
|
with this change we can now do the following:
can deploy umbrella chart with currently working components:
helm install local/onap --name onap --namespace onap-all
helm install local/onap --name onap-2 --namespace onap-all-2 \
--set global.nodePortPrefix=303
- umbrella includes setup chart
can deploy a-la-carte component by component into a single namespace
- Need to deploy a setup chart first. cannot be made a helm dependency
as there will be conflicts if each app chart has the same setup dependency.
helm install local/setup --name onap-setup --namespace onap-apps
helm install local/so --name so1 --namespace onap-apps \
--set global.nodePortPrefix=304
helm list
NAME REVISION STATUS CHART NAMESPACE
onap 1 DEPLOYED onap-2.0.0 onap-all
onap-2 1 DEPLOYED onap-2.0.0 onap-all-2
onap-setup 1 DEPLOYED setup-2.0.0 onap-apps
so1 1 DEPLOYED so-2.0.0 onap-apps
Unfortunately, the config maps all have fixed names, so installing
the same app in the a-la-carte fashion will fail due to a collision.
Not worrying about this as I'm not sure we want to support this.
-made the common and setup charts standalone to remove relative file paths
from requirements.yaml
This will help when there are different levels of subcharts that
need to include common
Issue-ID: OOM-786
Issue-ID: OOM-789
Issue-ID: OOM-788
Change-Id: I20bacae6f0f20e8f3bb1527af1e7e53f187341d5
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
changed namespace to be nsPrefix only
added component name as prefix to chart name
changed all templated to use name instead of fullname
Issue-ID: OOM-784
Change-Id: If2288ba14e5f74a7f7ba4c2f9bf46eecc36feca7
Signed-off-by: kerenj <keren.joseph@amdocs.com>
|
|
This is a standardization (based on helm community best practices)
of a Helm chart for the Service Orchestrator (so) in ONAP.
How to deploy the so chart (outside of the parent onap chart) from
the local oom/kubernetes codebase.
** need to create/update dependencies defined in the chart's
** requirements.yaml
helm dep update so/
** deploy the so helm chart with the "release" name of 'onap'
helm install so/ -n onap
Change-Id: I22471eb9fe0dec32941e14dc63857222c80ebe20
Issue-ID: OOM-727
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|