aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/portal/charts/portal-mariadb
AgeCommit message (Collapse)AuthorFilesLines
2018-04-16Update readiness-check versionBorislavG1-1/+1
Readiness check version is not sinchronized in many pods This causing deployment failures. Issue-ID: OOM-936 Change-Id: Ieef91df17836adcdf24db536440d0a1624a50591 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-04-11fixing invalid portal db imagesMandeep Khinda2-6/+6
Finding strange issues with image pulling and names subst. When using registry.hub.docker.com and an Always pull policy the Job pod would sit there pulling images forever even though they are actually up to date and present. Therefore reverting back to plain old oomk8s/blah Issue-ID: OOM-746 Change-Id: Iec5de0e1314ac85fa4e8de6599922f1e0fd0e367 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-04-06Correcting portal k8s configmap service namesMandeep Khinda2-3/+3
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-04-05Removing portal schema from configmapMandeep Khinda6-389/+108
-Trying a new way to initialize maria db's. -Docker image contains project sources and sql files are fetched and executed agains't the target database. -duplicates are silently ignored. -A script that takes some basic params will do the heavy lifting -A 2nd job to make some OOM specific changes (carry over from amsterdam) -docker image has been pushed to oomk8s under the 2.0.0 number Issue-ID: OOM-858 Change-Id: I56d0c9c5aa1d3c4a9df2998634b9147db626d1fb Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-03-29Standardizing ONAP PortalMandeep Khinda11-0/+807
-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>