Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Jakub Latusek <j.latusek@samsung.com>
Change-Id: Ic9e6fec5e5f6897a35d1c2c1036a947e30432efb
Issue-ID: OOM-2562
|
|
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>
|
|
Issue-ID: OOM-2469
Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com>
Change-Id: Ib7c794cca28ac2494eedba31903dcbd9348820c7
|
|
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
|
|
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
|
|
Change-Id: Ib3390afb9c1e154d9cadf9d7dc7707b35d37a8fe
Issue-ID: VFC-1494
Signed-off-by: yangyan <yangyanyj@chinamobile.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: VFC-1396
Change-Id: I4c1a88e5dc85caef96498d8749d4a262eebe02f5
Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>
|
|
Issue-ID: VFC-1396
Change-Id: Ia8617e6c54c3a504e9f68dbe34ee16f37117e26c
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|
|
Issue-ID: VFC-1374
Change-Id: I7075ea58836d5a1dafb72eeaf99f90c52d909db6
Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>
|
|
Issue-ID: VFC-1373
Change-Id: Ia232ab4ab7b3fdddeb7777d2f756cc62f1f01410
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|
|
Issue-ID: OOM-1776
Change-Id: I092815a6e5eebfe10cf213d995578238d73d0e48
Signed-off-by: yangyan <yangyanyj@chinamobile.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>
|
|
Sync docker tags with the release manifest from integration
repo commit b37a3cfdaf92c4855660d2f0c1b20eb482b99bd4.
Change-Id: Iabb203836d0c0adb5604a9303d4a108142ec6757
Issue-ID: INT-663
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Sync docker tags with the release manifest. It is
assumed that the release manifest is the
"single source of truth" and that the versions in
the helm charts are out of date.
Change-Id: I2902e60b25f57409dd616780a626e63c92d26769
Issue-ID: INT-663
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
resolving merge conflict and aligning with resource
template
bumping up small/large limits so pods actually run
Issue-ID: OOM-1166
Change-Id: Ied1a88f99f288544272e106677bba3f3131e48cb
Signed-off-by: GregSulek <gsulek@amdocs.com>
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.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: VFC-1031
Change-Id: Icab173a0927d3b82ea38733b6541e197ae01930f
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|
|
Issue-ID: VFC-975
Change-Id: I03534929bfa30efb22354d044d19b1459718ac11
Signed-off-by: Bharath Thiruveedula<bharath.thiruveedula@verizon.com>
|
|
Issue-ID: VFC-1003
Change-Id: I965aa3887e26c828b8d671edd6e423c33508af91
Signed-off-by: Huabing Zhao <zhaohuabing@gmail.com>
|
|
Sync OOM docker versions with docker-manifest.csv commit
a6e05c8c18624a1794abb1d3a3ab879a7a06bcfe
Change-Id: If8df538638670e0f1080d41d40d06de54ab1d93a
Issue-ID: OOM-1053
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Change-Id: I2d1ff878c215becc9856af184eb0b11defd75e1d
Issue-ID: OOM-1064
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Update the docker image versions in the OOM helm charts
with the versions specified in the docker-manifest.csv
in the integration repo.
Change-Id: I38bd9e98ae1b15ed4bbc68051b8516f311aa8db0
Issue-ID: OOM-1053
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Issue-ID: OOM-906
Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Readiness check version is not sinchronized in many pods
This causing deployment failures.
Issue-ID: OOM-936
Change-Id: Ieef91df17836adcdf24db536440d0a1624a50591
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Change-Id: I26e27cfb3b973bbffd0a94e3ec8411f5218cdf4f
Issue-ID: OOM-804
Signed-off-by: mahendrr <mahendra.raghuwanshi@amdocs.com>
|
|
Change-Id: Ie7064b59032c6cd81ee37466c89a5dee74530939
Issue-ID: OOM-750
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|