Age | Commit message (Collapse) | Author | Files | Lines |
|
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
Change-Id: I2cc90fe7a22a04d47d406b854c3a75502e539a25
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
|
|
Fix the image name and SQL for mariadb as it has been updated
Issue-ID: CLAMP-467
Change-Id: I0bb9bf48b86a8eb3cc7a0f74dd5a5f20e46e8b44
Signed-off-by: sebdet <sebastien.determe@intl.att.com>
|
|
Today when deploying CLAMP with OOM, the PersistentVolumeClaim needs the
"ReadWriteMany" (or "RWX") capability.
According to Kubernetes Documentation (https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes),
ReadWriteMany stands for "the volume can be mounted as read-write by many nodes".
That means that a particular PVC needs to be read and written from many pods.
That also means that your code takes that into account and do the work to avoid
write at the same place at the same time.
An issue on RWX mode is that most "official" storage driver from Kubernetes doesn't
support it (13 over the 19 drivers doesn't support it, espacially OpenStack, Amazon
and Google storage classes).
CLAMP PVC is used only for one ES instance. Thus we don't need RWX.
Change-Id: I3a17195bca4f0f01b5cdb0d8e803bb2a8ab2dd38
Issue-ID: CLAMP-488
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
resolve security isue on kibana and release early drop CLAMP
Issue-ID: CLAMP-419
Change-Id: I098f30d251f020470c0f1af1ce309a6a1a3b814d
Signed-off-by: osgn422w <gervais-martial.ngueko@intl.att.com>
|
|
Updating all helm chart versions to 5.0.0 for the El Alto release.
Merge will be co-ordinated with the merge of a separate aai/oom patch.
Please do not merge until this coordination has completed.
Issue-ID: OOM-1980
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
Change-Id: I31daaebeacea33565f13affd2fa28fb15fe948ba
|
|
Issue-ID: CLAMP-341
Change-Id: I5bd3cf20ec445e6972ce40f06f3d40e6056a1d43
Signed-off-by: Krysiak Adam <adam.krysiak@nokia.com>
|
|
All charts are being bumped from 3.0.0 to 4.0.0 for the Dublin release.
In addition the requirement.yaml files have been updated to allow for
chart versions that include timestamp suffix. A following on patch will
take care of changes to the OOM Makefiles to support injection of the
timestamp versions.
Change-Id: Ie03d86fad2027e975e8b9106e3a828e4335037cb
Issue-ID: OOM-1642
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
For Casablanca release, flavors have been set up for choosing the
"right" resource requests and limits.
Although the deployment is using the right way for that, clamp-xxx
charts values.yaml was not.
This commit makes values.yaml aligned with flavors
Change-Id: I025965d3d7820345f8459a5c5821091a29b2c5c7
Issue-ID: CLAMP-250
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
+ add logstash configuration for a 2nd aggregated index
+ use new restore scripts for restoring dashboards
Change-Id: I9176fa3b551591fdaf968e5b2496d510581aca22
Issue-ID: CLAMP-222
Signed-off-by: ac2550 <ac2550@intl.att.com>
|
|
Issue-ID: OOM-1145
Change-Id: I1510339a820802554b6e8b9a201619ef66be17a0
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
All Chart versions and requirement dependencies have been updated to 3.0 for Casablanca release.
Change-Id: Iea57e5da09ea8a8bac0a415b9a6196151cbea10b
Issue-ID: OOM-1354
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Issue-ID: OOM-1418
Change-Id: I0a822fc302899e3ccea55b9e4ae956f7ecc744ec
Signed-off-by: vaibhavjayas <vaibhav.jayas@amdocs.com>
|
|
Issue-ID: OOM-1369
Change-Id: I7ad1f9654f90ffe9c67dcf567c3ca694366bc66a
Signed-off-by: Mukul <mukul.joshi@amdocs.com>
|
|
Fix CLamp settings in CLAMP, like resource allocation
Issue-ID: CLAMP-174
Change-Id: I6c95ef8773d459edf7dc7577aa8ea9884176100b
Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
|
|
|
|
There is a missing parameter in clamp values.yaml: persistence.mountSubPathLogs,
which causes /dockerdta-nfs/ReleaseName directory to be come with permissions 777.
Issue-ID: OOM-1086
---
modified: clamp/charts/clamp-dash-es/values.yaml
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
Change-Id: Iddd80f77e7e42b06dd4b55c302d4d45127ea1b72
|
|
Issue-ID: CLAMP-162
Change-Id: I7174d1a18452e444d6806564662ab3d2ba0bc252
Signed-off-by: ac2550 <ac2550@intl.att.com>
|
|
Issue-ID: OOM-1029
Change-Id: I13d44d09bce42250b434d459612c0be6b46239c0
Signed-off-by: Priyanka <Priyanka.Jain3@amdocs.com>
|
|
Change-Id: I851750c2c394fad4c5187e2a18cfa0460a16c729
Issue-ID: CLAMP-154
Signed-off-by: ac2550 <ac2550@intl.att.com>
|