Age | Commit message (Collapse) | Author | Files | Lines |
|
Portal-db is maria-db. It has no logback.xml configuration.
The filebeat in this pod is redundant.
Issue-ID: OOM-517
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
Change-Id: I9118491ff6d9c51851cc915143b9962d98a883e4
|
|
Issue-ID: OOM-406
Change-Id: I03e1da331a551f655ebf023f954d944b02926f37
Signed-off-by: vasundhra <vasundhra.choudhary@amdocs.com>
|
|
Add option to disable any deployment by using conditions in helm
templates. Each deployment will get helm parameter - boolean flag
allowing to disable it. The flags can be listed in the custom
values.yaml file that can be passed to the createAll script with
'-v' command line option.
Change-Id: I32b795de46c72915c2201c94c23f4e061971bb56
Issue-ID: OOM-380
Signed-off-by: yuryn <Yury.Novitsky@Amdocs.com>
|
|
PORTAL-130 renamed various mounts and FQDNs
-it also added an additional logback.xml for portalsdk
What I did was move the 2 logback files into the config/log dir
so that the centralized logging team can update them as required.
Was able to login to the portal using the vnc session
Issue-ID: OOM-340
Change-Id: Id1872422e7d876953ecb0a92ce55a8753d9d7eaa
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
-moving container tags to 1.3
-pulling latest docker config mount files
-changing mariadb password back to original. there was no reason to change
in the first place
-robot health check passes:
Basic Portal Health Check | PASS |
Issue-ID: OOM-340
Change-Id: I77d22b701aa27473a9cfce25031c13f9be845dae
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Deployment of: filebeat containar for each relevant component
+ chown of log dir to root - prevents filebeat complaining about filebeat file
+ ecomp web app renamed onap - fixed dep-pap.yaml
+ fixed multiple volumeMounts in vid-server
Change-Id: I74f8f2abd5feeba1d37b044d2a023674fd41c994
Issue-ID:OOM-110
Signed-off-by: yuryn <Yury.Novitsky@Amdocs.com>
|
|
Pods aren't starting properly. Let's not take any risk, so reverting.
3m 18s 4 kubelet, kubernetes-5 spec.containers{vid-server} Normal Killing Killing container with id docker://vid-server:FailedPostStartHook
This reverts commit 4ca69ea2b6a2aaaf0974953a3c3dec7694fdfcb0.
Deployment of: filebeat containar for each relevant component Issue-ID:OOM-110
Change-Id: I7953ac3b0e2a4ecbdd1a7d2a48cb9a1964bf08ab
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Deployment of: filebeat containar for each relevant component
Issue-ID:OOM-110
Change-Id: I3605a975ee9dbe3e34b8fa6b17fef52e9d29b975
Signed-off-by: Itay Hassid <itay.hassid@amdocs.com>
|
|
Make sure time zones on the containers are in sync with the hosting machines
Change-Id: Ie22608bda63cbcdf564f73adcdd3e829afad05ca
Issue-ID: OOM-299
Signed-off-by: yuryn <Yury.Novitsky@Amdocs.com>
|
|
Deploy multiple namespaces fails due to existing persistence volumes.
"persistent-volume "appc-db" already exists"
Need to change all persistent volume names to include namespace.
Change-Id: I40a3048bef14f813b133ea75e2f664f669183e82
Issue-ID: OOM-294
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
|
|
Issue-Id: OOM-234
Change-Id: Ie18c2744c60b08ec8cfd80804c99da20530f7f65
Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
|
|
on master branch there were changes to portals vm_init script
and docker-compose process that needed to be ported to oom.
src of config are on master in portal/deliveries/
reverted the docker image name changes. upstream master
has introuced a "-" between apps, db and wms. these images
were cauing NPEs during portal spring boot so went back to original
image names until further notice.
Issue-ID: OOM-276
Change-Id: I708628f4b375325f2f2b753d1a374699b763098a
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Addition of persistent volumes for all DBs including
persistence of policy mariadb (with initial configuration data)
Change-Id: I029e724c3f8bba7fe3599b0955a4a3d213c08163
Issue-ID: OOM-268
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
the SDC widget in the onap portal was broken due to an incorrect hostname entry
for the front end endpoint
Issue-ID: OOM-151
Change-Id: Ia51bd805655da66eea7bbb617991f30ae6fd223f
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
fixes invalid host file entry in vnc-portal pod
Change-Id: I85effcc4f9e84ae8d9921816398547abfe82d520
Signed-off-by: nagu <nagaraja_sr@infosys.com>
|
|
parameterization of node ports, and create/delete update to fix multi ONAP instances creation(in diff NS).
Issue-ID: OOM-52
Change-Id: Iaa3f5bc43f70b95cdc349389e25ef8b804a7a329
Signed-off-by: kerenj <keren.joseph@amdocs.com>
|
|
-removed the full namespace from each template. better lets us reuse
variables.
-made secret end up in a configurable namespace
-fixed some bugs where secrets were missing
-updated createAll and delete to make use of namespace prefix
removing the need for seds to replace the word onap.
*** all containers at this point come up in my env. except for
aai model loader which is failing cause its still at 1.0
and its trying to talk to a 1.1 sdc and it doesnt auth properly. ***
Issue-ID:OOM-215
Change-Id: I15815a01469786a391e272fde4bdaa53ff48091c
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
changed portal k8s deployment to support helm parameterization
Issue-ID: OOM-52
Change-Id: I8ad9681b597a87113089f194e1a0e8a9e550bb08
Signed-off-by: kerenj <keren.joseph@amdocs.com>
|