aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/common/cassandra/values.yaml
AgeCommit message (Collapse)AuthorFilesLines
2020-02-26Cassandra 3 Upgradeshrek20001-1/+2
Move OOM to use SDC cassandra 3 Issue-ID: SDC-2595 Signed-off-by: shrek2000 <oren.kleks@amdocs.com> Change-Id: Ie58f3420cad70fbed7931656a98951e69a4b7b4b Signed-off-by: shrek2000 <oren.kleks@amdocs.com>
2020-02-04[COMMON] Create templates for services and PVSylvain Desbureaux1-8/+13
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>
2019-12-05[Common] Use global storage templates for PVCSylvain Desbureaux1-2/+2
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>
2019-10-04Increasing Max Heap size to 2GBAkansha Dua1-1/+1
Issue-ID: OOM-2059 Signed-off-by: Akansha Dua <akansha.dua@amdocs.com> Change-Id: I9b8db6ff689c0928ac497b523290e586c0f6f1f8
2019-09-04backup charts for cassandraAkansha Dua1-1/+18
Issue-ID: OOM-2089 Signed-off-by: Akansha Dua <akansha.dua@amdocs.com> Change-Id: Ia1086deda37ba6e613afcc6bd064e7bf4ee692b9
2019-05-30Readiness time increased due to errorsTomasz Golabek1-1/+1
Increased readiness time for common cassandra and sdc-cassandra due to installation failures Change-Id: I4c7f6f5db5ddeebb1d3bde50a24e848be75ba867 Issue-ID: SDC-2319 Signed-off-by: Tomasz Golabek <tomasz.golabek@nokia.com>
2019-05-02Bumped version of Casssandra 2.1.7 to 2.2.14Oleg Mitsura1-1/+1
Issue-ID: OOM-1834 this image has newer JDK version, which is not affected by JDK7 issue resolving long hostnames. Change-Id: Ibc94a7b88a24c2e83721e4ee1bab03550b65ffde Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com>
2019-04-30Downgrade Common Cassandra version to 2.1.17 for Dublinmahendrr1-1/+1
Change-Id: I0ae425343937389ff2f9bfd41701402398a63a82 Issue-ID: OOM-1832 Signed-off-by: mahendrr <mahendra.raghuwanshi@amdocs.com>
2019-02-20Instantiate common cassandra clusterMahendra Raghuwanshi1-21/+27
Issue-ID: OOM-1198 Change-Id: Ie49a34cfbe5bdb2620312e8780dccbc0b86a0d6e Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
2018-10-17Cassandra common chartingprpatel1-0/+132
Change-Id: I9899178bde859ee00fd62c700e8a2a5dd3dd8ac8 Issue-ID: OOM-1177 Signed-off-by: prpatel <pradeep.patel2@amdocs.com>