Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
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
|
|
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
|
|
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
|
|
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 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
|
|
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>
|
|
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>
|
|
Change-Id: I9c1321955c59b6f29c454aced0c00f713f5384ea
Issue-ID: VFC-1467
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|
|
Issue-ID: OOM-1776
Change-Id: I092815a6e5eebfe10cf213d995578238d73d0e48
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|
|
Issue-ID: OOM-1623
Change-Id: Idd9ecfaa99a7e4e8b57e12a5c442a4a1a3c3a6a0
Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>
|
|
Issue-ID: VFC-975
Change-Id: I03534929bfa30efb22354d044d19b1459718ac11
Signed-off-by: Bharath Thiruveedula<bharath.thiruveedula@verizon.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>
|
|
Change-Id: I6b40fcff3f0f09e7633f7fac38665e755bf90167
Issue-ID: VFC-728
Signed-off-by: Denes Nemeth <denes.nemeth@nokia.com>
|
|
Issue-ID: OOM-821
Change-Id: I627ac962afe8cd6bf2859a30a0e88f6c9ac89d34
Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
|
|
Change-Id: I5fcd4d577c1fda4de27842807c7cf7a5d372756e
Issue-ID: OOM-722
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Modify all-service.yaml,values.yaml, etc
Change-Id: Ieb98334a31a48654cee6436ac48a69f16948a380
Issue-ID: OOM-506
Signed-off-by: maopengzhang <zhang.maopeng1@zte.com.cn>
|
|
- add nokia driver
- add workflow engine activiti
- fix workflow deps
- update versions to released ones (TB updated)
Change-Id: Ia8df5fdd1df13e4d237aa628fb2c4fceb2d033cc
Issue-ID: OOM-473
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Add VFC containers to ONAP K8S
MK:- fixed issues related to port names longer than 15chars
- scoped pods to the onap-vfc namespace.
All deployments still fail due to missing docker images in nexus3
Yan:- fixed docker images in nexus3
MK (patchset 7)
- adding image pull secrets or they all fail
- address Alexis comments by removing trailing spaces &
removing activii (with the comments left in it crashes out)
MK: (patchset 8)
- removing trailing whitespaces
Change-Id: Iab9f641aaa580511c0e4a073a71da723aaf07315
Issue-ID: OOM-19
Signed-off-by: maopengzhang <zhang.maopeng1@zte.com.cn>
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|