Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: CCSDK-1953
Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com>
Change-Id: Id2ce253ab0ecee2c2fccb18589e76160fbf10853
|
|
Issue-ID: CCSDK-1952
Patch1: added missing properties from Change-Id: Idb3c7f67b3f22bd6069f75c193ae458c346fb2ac
Patch2: added missing vault mapping.
Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com>
Change-Id: I218f31cebe1f3fd24b1aead3fa93efb141465d23
|
|
Instead of using "own" galera chart, reuse chart placed in common part
of OOM installation.
Will ease move to common galera cluster (which is not done by this
commit).
Change-Id: I2d7c1e5cdc9289cfb55e288b1697373239ef96e3
Issue-ID: POLICY-1467
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
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>
|
|
|
|
Remove charts for multicloud-lenovo
Issue-ID: MULTICLOUD-737
Signed-off-by: Changjun Wang <310397125@qq.com>
Change-Id: Id0ddd57ef620be7b03c524289efb70163d0f8828
|
|
|
|
|
|
|
|
|
|
|
|
Issue-ID: OJSI-140
Signed-off-by: Huabing Zhao <zhao.huabing@zte.com.cn>
Change-Id: I84f3272cbf2307a8015259842f30cc4e1b77c552
|
|
Issue-ID: OJSI-186
Signed-off-by: Huabing Zhao <zhao.huabing@zte.com.cn>
Change-Id: I2e6e422e500ab84c48f6d6fa6acefc8feb826783
|
|
Issue-ID: OJSI-141
Signed-off-by: Huabing Zhao <zhao.huabing@zte.com.cn>
Change-Id: I9d510ca293b7e43eecddd75fbfaa0e5acf74077e
|
|
Issue-ID: OJSI-139
Signed-off-by: Huabing Zhao <zhao.huabing@zte.com.cn>
Change-Id: I643c4c7a51b05b462d280c903363d2372d3664db
|
|
Instead of using "own" galera chart, reuse chart placed in common part
of OOM installation.
Will ease move to common galera cluster (which is not done by this
commit).
Change-Id: I843c89ed4899055e9502268089d0e01f28fe37ae
Issue-ID: VID-704
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: POLICY-2229
Change-Id: Iffb9f40b174eae1e3b714e4ec5e8997c58d01a35
Signed-off-by: HOCKLA <ah999m@att.com>
|
|
-Add script to start dmaap microservice.
-Add new properties
-Renaming the DCAE.dmaap properties so that all of the
properties share the same prefix (DCAE.dmaap.event) instead
of some having a different prefix (DCAE.dmaap.appc). This is
required since all dmaap properties are now being read by the
a common java class.
Change-Id: I66b7cb466ec03f3357ecc473748a54a3a090ef16
Signed-off-by: Patrick Brady <patrick.brady@att.com>
Issue-ID: APPC-1744
|
|
Issue-ID: OOM-2206
Signed-off-by: Abdelmuhaimen Seaudi <abdelmuhaimen.seaudi@orange.com>
Change-Id: I5a66830a7aa128a0d75ed44ff5a06ae989be1d70
|
|
* Update kubernetes/robot from branch 'master'
to 31450dcb11d18b81098b43d0d0b7ecdb0d69e238
- SO VNFM HTTPS
Issue-ID: SO-2517
Change-Id: I86c59908271b6a0686162c127edd6eb256b3ce6b
Signed-off-by: Brian Freeman <bf1936@att.com>
|
|
|
|
|
|
change to poke 8181 port
Issue-ID: APPC-1792
Change-Id: I16160dde01c11c6625b407a1f5db4a24bc291df5
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
Configured the VNFM adapter to support https as is being used by the health check request
Signed-off-by: MichaelMorris <michael.morris@est.tech>
Issue-ID: SO-2517
Change-Id: I2076a02788c2f74b90939a9e3684f917079cf7b2
|
|
Helm value override file now supports component-specific settings:
dcae-bootstrap:
enabled: true
dcae-cloudify-manager:
enabled: true
dcae-config-binding-service:
enabled: true
dcae-healthcheck:
enabled: true
dcae-redis:
enabled: true
dcae-servicechange-handler:
enabled: true
dcae-inventory-api:
enabled: true
dcae-deployment-handler:
enabled: true
dcae-policy-handler:
enabled: true
dcae-dashboard:
enabled: true
Issue-ID: OOM-1574
Signed-off-by: Ubuntu <dgl@research.att.com>
Change-Id: I85e0fe6ae19e176d954611549ec954a5fe662307
Signed-off-by: Ubuntu <dgl@research.att.com>
|
|
|
|
|
|
|
|
Issue-ID: EXTAPI-341
Signed-off-by: MatthieuGeerebaert <matthieu.geerebaert@orange.com>
Change-Id: I94b41e338d80939934c7d42fd518d0984cf89b92
|
|
* Update kubernetes/robot from branch 'master'
to 5526182fa60a7a61c8158c98b6be8dfc66c8330b
- Revert VNFM https
Issue-ID: OOM-2163
Change-Id: Ib5d07e2ddecbe8cdaf6d5e3ac7ae195cf6d33db4
Signed-off-by: bdfreeman1421 <bf1936@att.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Issue-ID: OOM-2164
Signed-off-by: Shaaban Ebrahim <shaaban.eltanany.ext@orange.com>
Change-Id: Iace0b322d5d1a02ca25c0791936b0fc1a1e950e3
|
|
I've adjusted the Requests / Limits of portal pods according to real
usage of "Orange Openlab" and "Onap daily master".
Calculation is the following:
per deployment:
* CPU/Mem requests is max of average from the two deployments
* CPU/Mem limits is (max of max from the two deployments) * 1.2
Moved portal-widget CPU limit to 1 as it's not starting if set to lower
than that.
Full values are available on jira ticket
(https://jira.onap.org/browse/PORTAL-517).
Change-Id: Ic02fef386e05351a6fa9e47bf47d5c2046f490e3
Issue-ID: PORTAL-517
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Signed-off-by: Lorraine Welch <lb2391@att.com>
|
|
DB and auth credentials are never extracted from this file thus it's
better to remove them to avoid confusion.
Issue-ID: OOM-2051
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I66b0cb61b17439496ed0e0c8d9529ad730823d61
|
|
Data Router pods writes logs directly in the PVC within generic name
files:
debian@control01-onap-master:~$ ls -l /dockerdata-nfs/onap-pomba/pomba/data-router/logs/application.log
-rw-r--r-- 1 root root 125 Nov 5 09:56 /dockerdata-nfs/onap-pomba/pomba/data-router/logs/application.log
debian@control01-onap-master:~$ ls -l /dockerdata-nfs/onap-pomba/pomba/data-router/logs/
total 4
drwxr-xr-x 2 root root 76 Nov 5 09:56 AAI-DR
-rw-r--r-- 1 root root 125 Nov 5 09:56 application.log
drwxr-xr-x 3 root root 18 Nov 5 09:54 data-router
debian@control01-onap-master:~$ ls -l /dockerdata-nfs/onap-pomba/pomba/data-router/logs/data-router/
total 0
drwxrwxrwx 2 root root 6 Nov 5 09:54 logs
debian@control01-onap-master:~$ ls -l /dockerdata-nfs/onap-pomba/pomba/data-router/logs/data-router/logs/
total 0
debian@control01-onap-master:~$ ls -l /dockerdata-nfs/onap-pomba/pomba/data-router/logs/AAI-DR/
total 12
-rw-r--r-- 1 root root 0 Nov 5 09:56 audit.log
-rw-r--r-- 1 root root 0 Nov 5 09:56 debug.log
-rw-r--r-- 1 root root 7519 Nov 5 09:56 error.log
-rw-r--r-- 1 root root 666 Nov 5 09:56 metrics.log
Thus if two pods were writing, there would be issue as each one would
want to write.
Then this PVC must be used by one POD only and RWO is sufficent
Change-Id: I0087487fba715b4b0804de51544238f08fed1d3c
Issue-ID: LOG-1114
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Elasticsearch PVC is only used by elasticsearch POD. As ES doesn't
support several writes per different instances on the same folder, RWO
PVC is sufficient.
Change-Id: I6b7c91174f4f485dc6e3b6e34111fe4fc2bb0469
Issue-ID: LOG-1114
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Elasticsearch PVC is only used by elasticsearch POD. As ES doesn't
support several writes per different instances on the same folder, RWO
PVC is sufficient
Change-Id: Ie2cb4eadf8ee0c8ff1acf7e2ba172763c89583f3
Issue-ID: LOG-1114
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
As ansible server is a statefulset with PVC
template written in the statefulset, you'll
have one PVC per ansible server.
Thus ReadWriteMany (RWX) is not necessary and
RWO is sufficient.
Change-Id: I735891be2a098303ce85e21da7c8dc8b1ea20371
Issue-ID: APPC-1710
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Forgot Mariadb PVC in previous commit
(https://gerrit.onap.org/r/c/oom/+/94610).
Change-Id: I9e3d96eab8b6d6ada7d2ab406a8e72249c909aa4
Issue-ID: CLAMP-488
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update kubernetes/aai from branch 'master'
to 81954e51ef4c04fb08182d779f4871dfca766221
- Update schema service to use v17 to v19
Issue-ID: AAI-2607
Change-Id: Ia49109e37af5092a5394d69a69dd9ad0fb14e2d7
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
|
|
|
|
|
|
I've adjusted the Requests / Limits of portal pods according to real
usage of "Orange Openlab" and "Onap daily master".
Calculation is the following:
per deployment:
* CPU/Mem requests is max of average from the two deployments
* CPU/Mem limits is (max of max from the two deployments) * 1.2
Change-Id: I3fce54e6be495a7014bf346d66721976fa2dab8b
Issue-ID: MUSIC-533
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
|