Age | Commit message (Collapse) | Author | Files | Lines |
|
Currently in ONAP the imagePullSecrets is hardcoded to
'onap-docker-registry-key' which is created by the
repository-wrapper component.
With this change the secrets can be configured via setting
global.imagePullSecrets and optionally per image if it is
configured as map (image.pullSecrets)
Issue-ID: OOM-3284
Change-Id: I8644f9b46043b6014219c42928e057b149df43a4
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
|
|
Some settings are still wrongly interpreted (e.g. 0.02Gi)
Therefor they are changed to non-floating numbers (e.g. 20Mi)
Issue-ID: OOM-3273
Change-Id: Icc88dead1ac5b1df8629d6adcc438a739e20522e
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
|
|
Update all resource settings to the kubernetes recommended
normalized form. Fix ReadinessCheck resource limits.
Issue-ID: OOM-3273
Change-Id: Ie10903b801e4dc1689bcec092162d711a431a7a6
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
|
|
To avoid "lock" situations all clients of the mariadb-galera
cluster should use the "primary" service, which connects
to the master node.
This service is provided by the mariadb-operator.
Additionally for SO the bugfix for "local" DB configuration
is fixed.
Additionally missing readiness checks added to so-cnfm-lcm and
so-etsi-nfvo-ns-lcm to wait for the DB job to complete
Issue-ID: OOM-3261
Issue-ID: OOM-2697
Change-Id: I3d44f8b6d84d112c0271bfccebc4fa533c4e6aff
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
|
|
To support both Operator and non-operator deployments
the service name should be either mariadb-galera-primary or
mariadb-galera
Issue-ID: OOM-3236
Change-Id: Ic7721e08ec6a257b537024cb4a4751d6155ee28c
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
|
|
Add template functions for the mariadb-operator resources
and update the mariadb-galera chart to support them
Change the flag to "useOperator" in cassandra to the global setup
and additional labels for cassandra resources
Changed Policy DB users to support the new mariadb User
and fixed db.sh script to wait for the DB user creation
Use the new readiness image 5.0.1 with the "app-name" option
Change the MariaDB-Galera Service to the "primary" to avoid Deadlocks
Fix previous SDNC patch (https://gerrit.onap.org/r/c/oom/+/135308) and
temporary disable MariaDB for SDNR, as it is not compatible to
MariaDB 11
Issue-ID: OOM-3236
Change-Id: Ie63fcc9c6d5fa802d38c592b449e7ff8553c2ab9
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
|
|
Update chart versions to 13.0.0 for Montreal
Issue-ID: OOM-3173
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: Ie53fd021f01e459c464e44f4459a73ba0b00c172
|
|
Fix of resources template indent and therefore resources in components
Issue-ID: OOM-3104
Signed-off-by: miroslavmasaryk <miroslav.masaryk@telekom.com>
Change-Id: I825a3860db00cae4bb80b2aa2d82ac1a42b33124
|
|
Update chart versions 12.0.0 for London
Issue-ID: OOM-3046
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: Ic196235ff4f6ae14a7ecad799bd75a9666b2594a
|
|
All Makefiles are updated to support SKIP_LINT option,
have a defined order of compilation (common -> components)
to support the parallel compilation of charts using:
make all -j8 (for 8 Jobs). Additionally use cm-push instead
of push to use the new K8S/Helm version
Issue-ID: OOM-3011
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: If9903c9d5bc646b5ce54075acc616e98c4b6706e
|
|
Adding basic requirements for Service Mesh compatibility for VFC
Issue-ID: OOM-2991
Change-Id: I2c5d83772a13d9657858ae959c5ed336eccea89e
Signed-off-by: AndrewLamb <andrew.a.lamb@est.tech>
|
|
Use version 11.0.0 for Kohn
Issue-ID: OOM-2971
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: Icc0e0839fc6def2035383b5fa4c9153fc15fafda
|
|
Updates the container version of VFC components for Jakarta
Change-Id: I455d04eb92e1dbfa99732f2d2d72fdc65010ed87
Issue-ID: VFC-1931
Signed-off-by: dengyh <dengyuanhong@chinamobile.com>
|
|
Move all Chart.yaml to use apiVersion: 2
Move dependencies from requirements.yaml to Chart.yaml
Changes to all makeFiles
Changes to helm deploy plugin
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Change-Id: I03c5290eee9e40f76eacbf171e774204cf5fb1c0
Issue-ID: OOM-2845
|
|
Ability to turn off filebeat is needed as it is being deprecated. To
achieve that existing log helper template is used.
Issue-ID: OOM-1
Signed-off-by: Maciej Wereski <m.wereski@partner.samsung.com>
Change-Id: Ib3389c8e2f9221683862d3482c82f73f7f637441
|
|
Use version 9.0.0 for Istanbul
Also update the doc.
Issue-ID: OOM-1
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I03e11799bf487226784c98b04116f005c89d1e70
|
|
Update the image version for VFC components
Change-Id: I9370b23598dd98f259a142ef5f87ed83a0e3f49d
Issue-ID: VFC-1877
Signed-off-by: dyh <dengyuanhong@chinamobile.com>
|
|
Have following updates for VFC:
- Add section under .Values.global for shared mariadb instance default
info with a condition to instantiate local instance.
- Update the related section of Mariadb-galera under .Values
- Add condition under requirments.yaml to install local mariadb instance
* Note: Since Components initiate their own DBs and Users, there is no
need to initiate the common mariadb-galera with mariadb-init, instead
root password will injected to components to be able to create the DBs.
Have following updates for nslcm, vnflcm, vnfmgr and vnfres:
- Update .Values to accommodate for the new changes in parent .Values
file.
- Update root secret with the condition of having local mariadb or using
the common.
- Update deployments to include the definitions of mariadb service and
port defined in (common/_mariadb.tpl)
Issue-ID: OOM-2840
Signed-off-by: Mahmoud Abdelhamid <mahmoud.abdelhamid@orange.com>
Change-Id: Ia6a8e91ca3978928c4bf336a3a86ab1c6d64597a
|
|
In order to save some space
Issue-ID: OOM-2763
Signed-off-by: andreasgeissler <andreas-geissler@telekom.de>
Change-Id: Ibbd8d5f713307ada76a0d04ede57d3c7696bcfe5
|
|
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
|
|
|
|
Update the image version for VFC components
Issue-ID: VFC-1803
Change-Id: I4b7d7f5118de04849fe6fcb027f32db4305781e0
Signed-off-by: dyh <dengyuanhong@chinamobile.com>
|
|
Updating the documentation and bumping version to 8.0.0
Issue-ID: OOM-1
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I6f942f1466fed64264c44fb8fc0e1ffc93a98f18
|
|
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
|
|
Update charts and requirements to 7.0.0.
Create release notes for Guilin
Update documentation
Issue-ID: OOM-2638
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I965ed6b6ebb7d74bfddaff73edd3dd55a657841c
|
|
This commit makes VFC template to use the new generator for repositories and
images.
As new templates doesn't work well with "sub charts", we move also
subcharts to components folder.
Issue-ID: OOM-2364
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I469198fdfd3aec756e250764875a9ebcfd0a108d
|
|
1.Update image of nslcm 2.Update annotations
Change-Id: Ib34a1596e43f08e13d1c3f691b7428e8ed103e59
Issue-ID: VFC-1763
Signed-off-by: dyh <dengyuanhong@chinamobile.com>
|
|
Signed-off-by: Jakub Latusek <j.latusek@samsung.com>
Change-Id: Ic9e6fec5e5f6897a35d1c2c1036a947e30432efb
Issue-ID: OOM-2562
|
|
Change-Id: I48cfa7fc3d1386f991a4eab6af36053fcac219f5
Issue-ID: VFC-1757
Signed-off-by: dyh <dengyuanhong@chinamobile.com>
|
|
Issue-ID: VFC-1743
Change-Id: I4c758593e39043a2e8dbf1cfaca36e9f2960529a
Signed-off-by: dengyh <dengyuanhong@chinamobile.com>
|
|
Console handler added to log configuration file.
Issue-ID: OOM-2514
Signed-off-by: Dominik Mizyn <d.mizyn@partner.samsung.com>
Change-Id: Id58644149f5603dffc35375191125793a6250e8e
|
|
Issue-ID: VFC-1751
Change-Id: I27c96ead9ab0bf5054d9abc4c6664262a0430111
Signed-off-by: dengyh <dengyuanhong@chinamobile.com>
|
|
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
|
|
Two main process in vfc-redis: redis + mysql
Issue-ID: VFC-1727
Change-Id: Ied784a4ff8270d23f3609a7942dbfb8d81e74084
Signed-off-by: dengyh <dengyuanhong@chinamobile.com>
|
|
Change-Id: I21f65eebaa0f4655c37bba2ccbd965b6111a2c61
Issue-ID: VFC-1710
Signed-off-by: dyh <dengyuanhong@chinamobile.com>
|
|
Issue-ID: OOM-2469
Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com>
Change-Id: Ib7c794cca28ac2494eedba31903dcbd9348820c7
|
|
ems driver component is removed from scope of Guilin Release
Issue-ID: VFC-1690
Change-Id: I90acd6d11163873594fd04a8b3a521a30ec54cc0
Signed-off-by: dyh <dengyuanhong@chinamobile.com>
|
|
Change-Id: I7f432f2db6df8912b874a2bd11c0424ea9e2389d
Issue-ID: VFC-1644
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|
|
Use 6.0.0 in preparation for Frankfurt release
Issue-ID: OOM-2320
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I8ad82dfdf48b56c38c0e85d640b18cc13c8d9e67
|
|
Change-Id: Iedfa51903c695ab29ee3060a85c1537c42335f6d
Issue-ID: VFC-1644
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|
|
Issue-ID: OOM-2051
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I26c3b15e837ead96477d95312cb450a623ec16ae
|
|
Because Modeling project has created etsicatalog repo to intent to provide common ETSI catalog service,
VF-C catalog migrates to modeling can help reduce duplication of work and promote unified architecture.
This has reported in Architecture meeting 2019-10-15,and also been confirmed during VF-C Frankfurt Architecture Review.
So the corresponding catalog chart need also be removed
Change-Id: I63172ee17d8ffcdb59ac730c05d85b9a63e4d7a0
Issue-ID: VFC-1649
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|
|
microserice
Becaue now oom can register the microservice to msb automatically,
if without K8S, we can also register vfc microservice to msb
automatically by vfc container itself.
IF it is set to false, vfc contanier will not register again, if it is
set to true, vfc will register by itself.
we use this flag to determine who is responbile for serice registeration
and it can reduce duplicate registration.
Change-Id: Ie79a8803725ae0c762d9c39a04f922d9823c46e2
Issue-ID: VFC-1601
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|
|
|
|
Change-Id: I57b66de5d562b5170b841c5615f84f14f75ce16a
Issue-ID: VFC-1644
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|
|
Issue-ID: VFC-1600
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I9f83c6f6eaace60c3e974218810e5943c5758c06
|
|
Change-Id: I8602f2cbe425a061470e62d2a6fc490904f42256
Issue-ID: VFC-1601
Signed-off-by: yangyan <yangyanyj@chinamobile.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
Change-Id: Ibc8825b97cbe8939cf085d1cdd17e0a67e45c96b
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Change-Id: I156e5d688023d96954a106e6b6e81f7911f91e2b
Issue-ID: VFC-1523
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|