Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: OOM-2187
Change-Id: I2ae6b0f2482641b3f482121354596574b684b2d1
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
Issue-ID: OOM-2179
Change-Id: I6f1591a6c7033812cc714d75c63d7c1b3ba197b6
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
Issue-ID: OOM-2188
Change-Id: I30c2e0dea0a1fc12fd82090610c7e38f577cc811
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
Issue-ID: OOM-2174
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: Ib6c159d54ca65577934f70de137bfc13336992ec
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Missing apiVersion causes linting failure and therefore make common
fails
Issue-ID: OOM-2156
Signed-off-by: Tomáš Levora <t.levora@partner.samsung.com>
Change-Id: Idb0aeb998fc99cc8e409247c6b5e20d140297a3e
|
|
Issue-ID: POLICY-1841
Signed-off-by: Jim Hahn <jrh3@att.com>
Change-Id: I2ab0b7f40a9b60531dccd6175c76d0a18726816e
|
|
Issue-ID: CCSDK-1822
Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com>
Change-Id: Id06aacd6081178384d5c13680182fb339e7cfff4
|
|
Instead of using "homegrown" mariadb chart, move to use the common
mariadb-galera chart in order to be aligned with most of the other users
of mariadb and eventually to move into the common mariadb galera
instance.
Change-Id: I0c8ed6adfea0d64f97e7d9378464039915d389c7
Issue-ID: EXTAPI-347
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
postgres doesn't support that many posgtres instances write into the
same folder so moving to RWO mode is harmless
Change-Id: I3faf715606a7bb479917faf022efbf6635d602f8
Issue-ID: OOM-2080
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Used PVC(s) are actually created in the statefulset
Change-Id: I24f2c3ff0934178c9af06bfee60b4b6e35cfe953
Issue-ID: OOM-2155
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
-Enabled HTTPS for frontend and backend
-Updated paths and passwords for a certificates
Issue-ID: SDC-2479
Signed-off-by: Robert Bogacki <r.bogacki@samsung.com>
Signed-off-by: Krystian Kedron <k.kedron@partner.samsung.com>
Change-Id: Ic4b379bc2eb73a984221fa06ddc0fe8f0fa2116b
|
|
|
|
|
|
|
|
|
|
Issue-ID: CCSDK-1822
Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com>
Change-Id: Ib75741d85cfe8d0d5129dac6d11d0a3468627320
|