summaryrefslogtreecommitdiffstats
path: root/kubernetes/so/charts
AgeCommit message (Collapse)AuthorFilesLines
2018-09-07Flavors defintion in resource limitvaibhav16dec16-81/+122
Issue-ID: OOM-1322 Change-Id: I5248ae206da6b5d65b0830f454813e6e14ec7284 Signed-off-by: vaibhav16dec <vaibhav.chopra@amdocs.com>
2018-09-06Fix from robot testing and resolve mergeBrian Freeman7-13/+13
Issue-ID: SO-713 Change-Id: Icafe6b039cc793c3724c387c06a2e80153e307bb Signed-off-by: Brian Freeman <bf1936@att.com>
2018-09-05helm chart for so containersRamesh Parthasarathy64-58/+3275
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>
2018-06-11Use 2.0.0-ONAP tag instead beijing branch2.0.0-ONAP2.0.0-ONAPGary Wu1-1/+1
To ensure reproducible deployments, change gerrit branches to 2.0.0-ONAP tag instead of using the beijing branch since the beijing branches are not locked. Change-Id: I30bbece5fa2e0b8622db948d45e08a46ecf43ece Issue-ID: INT-506 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2018-06-07Change gerrit branches to beijingGary Wu1-1/+1
Change-Id: I840e9aada77fa297273ef5b32663f70ca4aac371 Issue-ID: INT-506 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2018-06-07Increase SO DB probe initial delaysGary Wu1-2/+2
SO healthcheck still fails on TLAB due to so db taking too long to initialize. Increase liveliness and readiness probe initial delays to 450. Change-Id: Ib765937dfd31944c8958e1736b5d579fffbb427d Issue-ID: OOM-1127 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2018-06-06Fix SO startup problemBorislavG1-2/+2
SO healthcheck fails due to so db taking long time to initialize. Current solution: increase liveliness and readiness timeouts to 300. Issue-ID: OOM-1127 Change-Id: I18c77d1599769385245de6dceaacfc2c40cdeed3 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-05-10Improve docker registry secret managementBorislavG1-1/+0
Change-Id: I2d1ff878c215becc9856af184eb0b11defd75e1d Issue-ID: OOM-1064 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-05-08Add latest SO configuration changesMike Elliott1-2/+2
Adds watchdog config and tables, oof configuration, aai athentication, etc. Change-Id: I43b5432d12c69ef45cdbeff5ab3427fbf5e9d1d0 Issue-ID: OOM-1039 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com> Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-05-08reducing configmap for SOMandeep Khinda13-2408/+75
-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>
2018-04-19Fix SO healthcheck on multi-node clusterMike Elliott3-11/+7
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>
2018-03-28Apache2 license addition for sql and js filesvaibhav_16dec8-0/+120
Issue-ID: OOM-825 Change-Id: I0cd8748adc7aa1a66cefd4a2b7d660d671a550b3 Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
2018-03-22Fix license for PV and PVC yamlsMike Elliott2-0/+4
When conditions are used at the start of the yaml the hashed (#) comments of the license are not parsable by the json parser. There license comments have been wrapped in {{/* */}}. Change-Id: I16c539ae4280f8ecacfdedb1f8caad894f3a081f Issue-ID: OOM-821 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-03-22License addition in all yamlsvaibhav_16dec8-0/+112
Issue-ID: OOM-821 Change-Id: I627ac962afe8cd6bf2859a30a0e88f6c9ac89d34 Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
2018-03-02adding a selector in so/mariadb/pvcJerome Doucerain2-1/+5
to be sure the pvc will properly be bound to the expected pv a label has been added to the pv and a selector on matchlabels has been added to the pvc Issue-ID: OOM-786 Change-Id: Ic1c89efc2632623f9bf6467ebc1fd24b3cb4fb93 Signed-off-by: Jerome Doucerain <jerome.doucerain@bell.ca>
2018-03-09iterating on new helm structure for SOMandeep Khinda8-46/+13
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>
2018-03-06make so chart one namespace compatiblekerenj8-16/+16
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>
2018-02-23Add standardized helm chart for soMike Elliott22-0/+2771
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>