summaryrefslogtreecommitdiffstats
path: root/kubernetes/portal/values.yaml
AgeCommit message (Collapse)AuthorFilesLines
2018-09-28Portal HTTPs supportst782s1-1/+4
Issue-ID: PORTAL-389 Change-Id: Ibdb91bcf1164d6c79312597416a0fa3214361f8f Signed-off-by: st782s <statta@research.att.com>
2018-08-30Apache2 License additiontoshrajbhardwaj1-1/+2
Issue-ID: OOM-1306 Change-Id: I1a617718006ee845d675fead74ce075c3390ac2f Signed-off-by: toshrajbhardwaj <toshrajbhardwaj@gmail.com>
2018-05-01exposing portal on port 8989 outside the clusterMandeep Khinda1-0/+5
-introducing a loadBalancer object instead of node port. this will let us use port 8989 instead of 300xx -removing port forwarding helper script -making URLs configurable for flexibility Issue-ID: OOM-633 Change-Id: I92a0205e6ed68b2217c08d124ddfaf1a1f73a6cd Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-04-27OOM direct portal accessMandeep Khinda1-5/+5
-must include suffix of "onap.org" in URL for single signon -this isn't truly configurable - portal-app needs to be rebuilt See: portal/docs/tutorials/portal-sdk/single-signon.rst -must update local etc hosts with "fake" dns names -must use kubectl to portforward application ports into the pods -fixed zookeeper service name, -this is needed to be able to login (auth) -adding helper script to launch port-forwarding Issue-ID: OOM-633 Change-Id: I019f33f71a673467c420d1e44ee6c42da4a95f4b Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-04-06Correcting portal k8s configmap service namesMandeep Khinda1-2/+20
The service.name is really a port name and was being used wrong. Need a better way than this to get dependant chart names. This gets it working. Issue-ID: OOM-842 Change-Id: I6a78a5adb0e69524a90aa3386009a0d87ebed73c Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-03-29Standardizing ONAP PortalMandeep Khinda1-19/+8
-synched up with Beijing (master) -pods come up without cassandra music: sed: couldn't edit /docker-entrypoint-initdb.d/\ zzz_portal.cql: not a regular file ONAPPORTAL webapp in tomcat is failing to star resulting in HTTP 404 robot health Not sure how logging works in beijing so removed some of the ubuntu-init dir creation. need someone familiar with logging to investigate -addressed some CI comments. -removing configmap now that portaldb was fixed Issue-ID: OOM-746 Change-Id: I123d1ec6889db40b1721475a43665ef8efefc057 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-03-27Add standardized helm chart for logBorislavG1-0/+3
Change-Id: Ic9f0eb567716224893955d9379e9ed9308b9ea79 Issue-ID: OOM-740 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-03-22License addition in all yamlsvaibhav_16dec1-0/+14
Issue-ID: OOM-821 Change-Id: I627ac962afe8cd6bf2859a30a0e88f6c9ac89d34 Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
2018-02-25portal persistence folder parametrizationkerenj1-0/+1
Issue-ID: OOM-145 Change-Id: Ie41334345d1a3799d1bb0add8a2a97dc6918bd03 Signed-off-by: kerenj <keren.joseph@amdocs.com>
2018-02-22portal - readiness image updatekerenj1-1/+1
changes can be seen in reviews: 31743 and 31721 Issue-ID: OOM-514 Change-Id: I7373540d34ba605abb372690f7636d353b99b414 Signed-off-by: kerenj <keren.joseph@amdocs.com>
2018-02-15Replica Scaling of Portal and Vid Containervaibhav_16dec1-0/+4
Issue-ID: OOM-690 Change-Id: Ia26adc82d04add9b1e18c51b361c21755512c137 Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
2018-01-24portal config segmayank1-0/+1
Issue-ID: OOM-557 Change-Id: I79f73ce84102caae5fdd4570cf1acb26cb3eeb4c Signed-off-by: mayank <mayank.gupta@amdocs.com>
2018-01-17Refresh /etc/hosts in VNC - reviewedyuryn1-1/+0
Change-Id: Ie2c9648e067867d00c035dd9f35560be2ecd6724 Issue-ID: OOM-413 Signed-off-by: yuryn <Yury.Novitsky@Amdocs.com>
2017-12-08Migrate to R1 released docker imagesAlexis de Talhouët1-3/+3
Change-Id: Iac46cbae69404d17e1f4e59f85ed18fc7ecd01dd Issue-ID: OOM-432 Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com> (cherry picked from commit f033f949c49cc195be1f3a6bdf79759f7e0983ca)
2017-10-25synching up portal config againMandeep Khinda1-3/+3
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>
2017-10-17Synching up portal configMandeep Khinda1-3/+3
-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>
2017-09-27added filebeat to all componentsyuryn1-0/+1
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>
2017-09-26Revert "added filebeat to all components"Alexis de Talhouët1-1/+0
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>
2017-09-24added filebeat to all componentsItay Hassid1-0/+1
Deployment of: filebeat containar for each relevant component Issue-ID:OOM-110 Change-Id: I3605a975ee9dbe3e34b8fa6b17fef52e9d29b975 Signed-off-by: Itay Hassid <itay.hassid@amdocs.com>
2017-09-21Update to use newly named portal containersMike Elliott1-4/+4
Portal container names now include a hyphen. K8s deployment descriptors updated to point to new containers. Change-Id: I7b6b08a9d707b1b9747c6f45de70df7392cfca8f Issue-Id: OOM-310 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2017-09-11synching portal config with upstreamMandeep Khinda1-0/+2
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>
2017-08-31NodePort Helm Parametrizationkerenj1-0/+1
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>
2017-08-25refactor helm files to use namespace prefixMandeep Khinda1-1/+1
-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>
2017-08-24portal K8S-Helm Parameterizationkerenj1-0/+10
changed portal k8s deployment to support helm parameterization Issue-ID: OOM-52 Change-Id: I8ad9681b597a87113089f194e1a0e8a9e550bb08 Signed-off-by: kerenj <keren.joseph@amdocs.com>