Age | Commit message (Collapse) | Author | Files | Lines |
|
Update the pod annotations to exclude the cluster communication
ports from the SM sidecars.
Fix mysql protocol setup fodddr istio and update mariadb-init job
to support istio sidecar communication.
This is separated from a patch for CDS SM compatibility
Issue-ID: OOM-2820
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: I9e839e019c948614fea7d4b3b5930270f7e7a7c6
|
|
Update the port names of metrics and mariadb to match the
istio requirements and update the timeouts.
Fix mysql protocol setup for istio and update mariadb-init job
to support istio sidecar communication.
This is separated from a patch for CDS SM compatibility
Issue-ID: OOM-2820
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: I02c19c9fcfbd76a2cede0b924174ad81b45d719e
|
|
We have stability issues with MariaDB (which didn't occur on istanbul).
Issue-ID: OOM-2963
Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl>
Change-Id: I23b31db06dd87a45a47c8b2741b36e6387e5d1ec
|
|
We observed from time to time issues with fetching data from
mariadb-galera. We suppose that can be related with too low
persistence volume size of mariadb-galera.
Increase that value and observe gating and daily.
Issue-ID: SDC-3949
Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl>
Change-Id: I964351b755e11a513da42f1c11da86bb1130ad96
|
|
The backup job stopped working after upgrade to bitnami images.
Mariabackup was not designed to work remotely, it is supposed to run
on the database server. Because of this we need to mount the data pvc
into the backup job pod. It will however connect to the database daemon
using a hostname, so we need to connect to the first replica in the
cluster. Also had to set readOnlyRootFilesystem=false and add emptyDir
volumes to solve various permission issues.
Issue-ID: OOM-2932
Signed-off-by: Jozsef Csongvai <jozsef.csongvai@bell.ca>
Change-Id: I776903f9ec541f8dc5818b2ba4c1292226ec2bc6
|
|
Setting the "prometheus: kube-prometheus" label selector for mariadb-galera
ServiceMonitor object is invalid since mariadb-galera-metrics service has
common labels assigned.
Without this change Prometheus (in kube-prometheus-stack) does not select
the mariadb-galera-metrics service for scraping and relevant target is
not created.
Change-Id: I64dfe83ff7fb448125f8726cf3ca33048ced04a8
Issue-ID: OOM-2925
Signed-off-by: Bartek Grzybowski <b.grzybowski@partner.samsung.com>
|
|
Use version 10.6.5-debian-10-r28 instead of 10.6.5.
Also align clamp and so to use the same version as the other ones
Issue-ID: OOM-1
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ie1db09b03daa1bb7792ee0ff6a73bd3483213e75
|
|
Bump version to the one asked by SECCOM.
Issue-ID: OOM-1
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I99a4c1e412a2288b595d78470dc433466586529b
|
|
DB connection from Policy Framework components fail intermittently with
Connection refused error. Upon investigation, identified that
mariadb-metrics readiness is failing with timeout, and thereby affecting
the db connectivity intermittently.
So, changing readiness timeout from 1 second to 5 seconds so that
there is enough time to get back the /metrics response
and readiness can pass. Also making the properties configurable.
Similar issue could happen in other components too.
Change-Id: I8dfbfeb0fe791c1bce373dd9d7124d26457c4919
Issue-ID: POLICY-3637
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Update mariadb-galera chart to add internalport value under (.Values.
service) to resolve the port settings needed for the template (common.
mariadbPort) under (common/_mariadb.tpl).
This parameter will use the default value of mariadb 3306 which can be
changed in component charts.
Issue-ID: OOM-2773
Signed-off-by: Mahmoud Abdelhamid <mahmoud.abdelhamid@orange.com>
Change-Id: I0d59ba42f07426b14ec7bc7f157392b5f10b9006
|
|
|
|
Instead of long initial delay on readiness and liveness probes, use
startup probes and be more aggressive on readiness and liveness.
Issue-ID: OOM-2740
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I86015a4a0c4ab313929c5bd103dedced1df88ec3
|
|
With stability tests, we see that mariadb gets OOM killed and has some
CPU throttling.
Putting higher limits in order to make it no happen.
Scaling also replicas from VFC and APPC db from 3 to 1.
Issue-ID: INT-1883
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I2699b34ac5fcaa805c6fc01592c5a5f607b17fae
|
|
Camunda has given a guide in order to configure camunda
(https://docs.camunda.org/manual/latest/user-guide/process-engine/database/mariadb-galera-configuration/).
Applying it to ONAP camunda configuration.
gitlint-ignore: B1, body-max-line-length
Issue-ID: INT-1883
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ie0cb1c70e4271496ffd5e51ce1d816785f88689f
|
|
Mariadb DB Galera containers version is outdated and unmaintained. We
need them to move to a new image provider.
As new image provider is not compatible with our old templates, we
also update the templates (by reworking bitnami mariadb-galera chart).
An update of global mariadb image is also done in order to match mariadb
galera version.
Issue-ID: OOM-1720
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ib9976227759e90022183d4f37fc655143be4d6ac
|
|
This commit makes mariadb galera template to use the new generator for
repositories and images.
As mariadb are coming from dockerhub, we're using directly this
repository.
Issue-ID: OOM-2364
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I7010ea3214c34fbee1ee697a127a1e43bfd16aed
|
|
This change modifies VID to use the shared DB instance of mariadb.
In addition, we create a mechanism in mariadb-init to allow a shared DB
user to run a script after the DB has been created.
The script can be passed as a configMap (as is the case with VID) or it
can be a standalone script that is passed as a string.
Issue-ID: OOM-1226
Change-Id: Ie51823338562a6fbe7472025d62cd4dba688168d
Signed-off-by: RPMishra <rpmishra@aarnanetworks.com>
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
requests/limits for "small" deployments are too big compared to actual
usage.
Issue-ID: OOM-2230
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I2e3f6dae57714ddc85d2fc04a3793fe034ccc8ef
|
|
Readiness container v3.x and up are now present in ONAP main repository.
They're also not using root user anymore and then script path has
changed.
Finally, "job_complete" script has been integrated in main "ready"
script.
As those changes are significant, we must upgrade all the components at
once.
Depends-On: I5afa83892043f4844afe12e61724a8d368a9f2e0
Issue-ID: OOM-2545
Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com>
Change-Id: I0b4eb5dd86390273532d67d0a9696e1cfcadf110
|
|
When upgrading from a version to another, it may be impossible to do it
"simply" because of changes in immutable properties of statefulsets. We
change that here by creating a temporary deployment which will hold the
whole databases during the time the old statefulset gets destroyed and
the new one gets created.
Issue-ID: OOM-2316
Signed-off-by: tringuyen <tri.nguyen@tatacommunications.com>
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I318d72830d5002f50597e23e0753e292f8b47c53
|
|
After we upgraded our helm version we started getting below issues
with emails:
Warning: Merging destination map for chart 'curator'.
Overwriting table item 'image', with non table value:
onap/sdnc-image:1.8.2
To fix this let's just use "" instead of () for our daily operations.
Issue-ID: OOM-2412
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I5f2c215c281036a7eb921d6a805527c807a4aca9
|
|
The time has come! All ONAP charts use now common secret template at
least for the mariadb-galera root password (and most of them also for
user part). This means that it should be now safe to remove hardcoded
mariadb-galera root password and depend on common secret template to
generate it for every deployment.
No more secretpassword!:D
Issue-ID: OOM-2342
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: Ib9d8bbcc45bfd85a4d762c716c03dba23d901009
|
|
When deploying a shared mariadb-galera instance using common chart
a dummy database is created based on the default values n the chart.
This is obviously unnecessary and creates an obviousl security issue.
That's why let's make sure that when we deploy a shared mariadb
instance no dummy databases are created.
Issue-ID: OOM-2053
Change-Id: I1130cb8eb555b15a2d8b365102d69e32259233eb
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
|
|
Usage of plain strings is very fragile especially when you try
to change them. That's why instead of depending on strings let's
just define a few convenience templates to be used in projects
that use mariadb-galera chart.
Issue-ID: OOM-2249
Change-Id: Ib867d34090b06a15ea3898a9524f5e3d04a656c0
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
|
|
Instead of defining the secret in some custom way let's use the common
template (common.secret). To avoid some issues in ONAP components that
depend on this chart let's do not remove for now the default username
and password. We will do this when all services properly utylize
secrets to store mariadb credentials.
Issue-ID: OOM-2053
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I78e224299cccd9632192ee03a45cd077e6f0906f
|
|
Two helper functions are defined:
- common.storageClass: will print the right storage class according to
properties set or not:
* if no storage class set --> use previous behavior (storage class
named `common.fullname-data`.
* if a "persistence.storageClassOverride" is set for this specific chart,
we use it (if it's "-", we set to default one)
* if a "global.persistence.storageClass" has been set (and no
storageClassOverride for this chart), we use it (same specificity than
storageClassOverride)
* if a "persistence.storageClass) has been set (and no
storageClassOverride nor global one), we use it (same specificity
than storageClassOverride)
- common.needPV: will print "True" if we need a PV (no storageClass and
storageClassOverride being set).
an implementation example with mariadb-galera is provided.
Issue-ID: OOM-1500
Change-Id: I20a667e17b00c255c4b828e3c66f9c0df7c8755c
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: OOM-2088
Signed-off-by: Akansha Dua <akansha.dua@amdocs.com>
Change-Id: Ie7f25c812984abc8631a86b2385dd14a365a8ea5
|
|
Mariadb PVC are created in 1 to 1 mapping with galera replicas thus we
don't need RWX.
Change-Id: I438855b2d4b2f90932387e056c168b0a995975a5
Issue-ID: OOM-2081
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: VFC-1392
Change-Id: I8b4a97dbac6245c7747a31fdc557ffd8d9a974d5
Signed-off-by: yangyan <yangyanyj@chinamobile.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, mariadb-galera
charts values.yaml was not. This commit makes values.yaml aligned with
flavors.
Change-Id: If51e8c5ad41dda7fa35c3aaaa58e60752094f133
Issue-ID: OOM-1528
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: OOM-1145
Change-Id: Ic2770086914e7cf1a96f2b6e5fd04bf1bd3f75d8
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
The service name was being used as the port name. There is a 15 character
limit for a port name in Helm. This patch allows another chart to configure
the port name that is used via service.portName.
Change-Id: Ie4b805a5e58a53b10480961e543267ca8bb1dc00
Issue-ID: CCSDK-523
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
|
|
Change-Id: I3537415a9266bc388aca146f86984c8a1585ce4e
Issue-ID: OOM-1205
Signed-off-by: pramod <pramod.kumarsharma@amdocs.com>
|
|
Issue-ID: OOM-1356
Change-Id: I656f4ce722cd239933aa5a088308da5e9de7a7db
Signed-off-by: vaibhavjayas <vaibhav.jayas@amdocs.com>
|
|
Change-Id: I2d1ff878c215becc9856af184eb0b11defd75e1d
Issue-ID: OOM-1064
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Issue-ID: OOM-906
Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
A new common helm chart that will deploy a Galera cluster for MariaDB.
Please note that this chart is still work in progress and more features
will be added or improved.
Change-Id: Ia4487666798f83d2869c35bcfaacc5516068f194
Issue-ID: OOM-758
Signed-off-by: vitalied <vitalied@amdocs.com>
|