Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I287b830f86da0fe0adc440cf9e645f8d244aefe1
Issue-ID: OOM-2368
Signed-off-by: afenner <andrew.fenner@est.tech>
|
|
Proposition of common templates to make service declaration and PV
declaration consistent accross OOM.
Propositions of templates for sub parties of resource definitions
such as metadatas, selector and containerPorts.
I've also made an example with cassandra.
Change-Id: I8b8aa8eb61dafba75e89add1979114a0eefce243
Issue-ID: OOM-1971
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
This reverts commit 239bb3e18494584587ee1a6eb482f022b9e32d44.
Reason for revert: mandatory template functions not merged yet
Issue-ID: OOM-2252
Change-Id: I80444a7103e12aea4568f03ded08e348bba927fb
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
When service mesh is enabled, cassandra needs to listen to `127.0.0.1`
instead of POD_IP but must broadcast using POD_IP.
Change-Id: If96acd56a092a893f524a69ee83406c9cb70b3e7
Issue-ID: OOM-2252
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
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
|
|
OOM has now templates in order to create the needed PVC, using:
* a PV with a specific class when using a common nfs mount path between
nodes (sames as today use) --> is the default behavior today
* or a storage class if we want to use dynamic PV.
On this case, we use (in order of priority):
- persistence.storageClassOverride if set on the chart
- global.persistence.storageClass if set globally
- persistence.storageClass if set on the chart
I've also aligned the PV creation of the different charts.
I've also aligned the PVC creation of the different charts.
I've removed unused mysql chart and (badly) used nfs-provisioner chart.
I've also make cassandra backup work with dynamic PV (but RWX only for
now).
Change-Id: I0ea3f8c7514ca648d94b6c682684c06b822bbe0a
Issue-ID: OOM-2229
Issue-ID: OOM-2228
Issue-ID: OOM-2227
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: OOM-2089
Signed-off-by: Akansha Dua <akansha.dua@amdocs.com>
Change-Id: Ia1086deda37ba6e613afcc6bd064e7bf4ee692b9
|
|
Disabling cassandra livenessProbe causes the
charts generated yaml to append readinessProbe
after containerPort because of go ‘-‘ command.
Issue-ID: OOM-1922
Signed-off-by: Joey Sullivan <joey.sullivan@amdocs.com>
Change-Id: If19c8639d1a5c0968b7156e39945a3ca15dd18b5
|
|
Change-Id: I337aaf258b1a3716d97e31ea3f53014738f3db55
Issue-ID: OOM-1835
Signed-off-by: mahendrr <mahendra.raghuwanshi@amdocs.com>
|
|
Change-Id: Ib7b0e3c0a6a2c81906e3e44e648926e9379da232
Issue-ID: OOM-1733
Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
|
|
Issue-ID: OOM-1198
Change-Id: Ie49a34cfbe5bdb2620312e8780dccbc0b86a0d6e
Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
|
|
Change-Id: If156e738a26c7c19043657c97ac327125c5162db
Issue-ID: OOM-1486
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Change-Id: I9899178bde859ee00fd62c700e8a2a5dd3dd8ac8
Issue-ID: OOM-1177
Signed-off-by: prpatel <pradeep.patel2@amdocs.com>
|