Age | Commit message (Collapse) | Author | Files | Lines |
|
This fix is adjusting OOM helm charts components resources limits and requests
Issue-ID: OOM-3199
Signed-off-by: Vladimir Turok <vladimir.turok@t-systems.com>
Change-Id: I56aeba925cda4984277ac7bbf23cfd158263d30f
|
|
Release 1.12.2 SO Core images.
Corrects the rest-call to support new SDNC version
for London
Issue-ID: SO-4109
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@t-mobile.pl>
Change-Id: I8ee70cf864f4f77a752766f9e03030585063ea2c
|
|
London release image updates - for test purpose only so far.
Issue-ID: SO-4091
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@t-mobile.pl>
Change-Id: Iec7fe7c04dc645f2f65910e7df4e1b60e980c19c
|
|
- Create Authoriation Policies for SO
- Add in initial authorized serviceaccounts for each sub component service
Issue-ID: OOM-3128
Change-Id: Id18b7bb6cdb180b1173966e797032118b5b20621
Signed-off-by: AndrewLamb <andrew.a.lamb@est.tech>
|
|
Remove AAF and TLS related chart entries
Use OOM templates for deployment and service definitions
Remove so-appc-orchestrator, as it is not supported anymore
Issue-ID: OOM-3106
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: I6256aa0fbbe172752cc3d8f83edde0880de7f629
|
|
Kohn release image updates - for test purpose only so far.
Issue-ID: SO-3993
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@t-mobile.pl>
Change-Id: I8abea088f33dc7d384bafc64d8fa02caf59afb87
|
|
Patch on SO charts dedicated to allign the service port names
according to Istio naming schema.
Change the mariadb job to wait for the sidecar and kill it afterwards.
Remove CertInitializer TLS job, if AAF is not enabled
Added all missing changed from https://gerrit.onap.org/r/c/oom/+/124231
Issue-ID: OOM-2824
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: I5b333ab19673ad248fd2e3bd138a99fe15025f5e
|
|
First images of SO for Jakarta release.
Issue-ID: SO-3912
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
Change-Id: I666a5a7e3be27cf24c2c557c9ce2f696213d1aff
|
|
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: Ib883fcafe4424d4ec78a999899c99af2ae95a6cc
|
|
|
|
Bump of SO Istanbul images after E2E integration tests
Issue-ID: SO-3767
Issue-ID: SO-3768
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@orange.com>
Change-Id: I13c7ea23329a5da38f20638a9e6010f1a28f35fe
|
|
These properties define a time window where the history cleanup job
is allowed to run. Without these properties the cleanup job would not
be triggered automatically.
Also set mso.bpmn-history-ttl (days). This ttl value will be applied
to all bpmn definitions, which will set a removal date for historic
data.
Remove old historyTimeToLive property which is no longer used.
Issue-ID: SO-3770
Signed-off-by: Jozsef Csongvai <jozsef.csongvai@bell.ca>
Change-Id: I5baee0a3ba8700b4ce177e3af4d480a8ae737e5f
|
|
|
|
Includes the So core components. Also installs compatible
CDS version 1.1.5
Issue-ID: SO-3740
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: Ic40426e569fd9f15e50d6697eb031f169c7eb38b
Signed-off-by: Dan Timoney <dtimoney@att.com>
|
|
so-bpmn-infra deployment init container waits on
so-mariadb-config pod to complete instead of checking job
status itself. This causes issues when the completed config
job container finishes and gets cleaned up due to garbage
collector, after which so-bpmn-infra pod gets stuck in init
state forever.
Fixing other instances of waiting for so-mariadb-config job
as well.
Issue-ID: OOM-2799
Signed-off-by: Prabhjot Singh Sethi <prabhjot@aarnanetworks.com>
Change-Id: Ib6d1b53d52c178386a743558c4b45b8f8748487b
|
|
Add service account to requirements.yaml, values.yaml and
deployment/statefulset
Issue-ID: OOM-2718
Signed-off-by: farida azmy <farida.azmy.ext@orange.com>
Change-Id: Ic17b8d9307216a7feeceefe6a1e6f0fe4839a637
|
|
The fix for blocking issue of
1. SO-CDS interaction and
2. post instantiate flag
Issue-ID: SO-3628
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: Id09c1e04e8063dd1fb5cae47b5c17bc43d028d57
|
|
Some SO components have changed their names:
* so-monitoring is now so-admin-cockpit
* so-etsi-nfvo-ns-lcm has a new repository
* so-vnfm-adapter is now so-etsi-sol003-adapater
Issue-ID: SO-3473
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I75be10b42fc7b44ac0f654853953f6139f3b1c13
|
|
SO core components 1.8.1 and sub-components 1.8.2.
Also the DB scripts to support the camunda 7.14.
Issue-ID: SO-3566
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: Ia0efe1116b6435c3aa19beb3b0a938a2f2ae0bea
[Rebase and resolve conflicts]
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
|
|
Update SO containers to 1.7.11, solve CNF and E2E NW slicing bugfixes:
Containers:
+ name: 'so/vnfm-adapter'
+ name: 'so/catalog-db-adapter'
+ name: 'so/request-db-adapter'
+ name: 'so/openstack-adapter'
+ name: 'so/sdnc-adapter'
+ name: 'so/vfc-adapter'
+ name: 'so/sdc-controller'
+ name: 'so/bpmn-infra'
+ name: 'so/so-monitoring'
+ name: 'so/api-handler-infra'
+ name: 'so/nssmf-adapter'
+ name: 'so/mso-cnf-adapter'
+ name: 'so/so-oof-adapter'
+ name: 'so/so-etsi-nfvo-ns-lcm'
Change-Id: I6755bef5a6ee019afa6ad41ec20c42f9703182d8
Signed-off-by: Damian Nowak <damian.nowak@nokia.com>
Issue-ID: SO-3431
|
|
This commit makes SO chart to use the new generator for repositories and
images.
Issue-ID: OOM-2364
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ife4e1fcfff565b3ada7e726913826e2c9f76bc07
|
|
SO 1.7.10 containers are release containers
so-bpmn-infra: 1.7.10
so-catalog-db-adapter: 1.7.10
so-monitoring: 1.7.10
so/nssmf-adapter: 1.7.10
so/openstack-adapter: 1.7.10
so/request-db-adapter: 1.7.10
so/sdc-controller: 1.7.10
so/sdnc-adapter: 1.7.10
so/vnfm-adapter:1.7.10
so/api-handler-infra:1.7.10
Issue-ID: SO-3346
Change-Id: I450734f8b4704c767c330deff8a830ae84ba3d2c
Signed-off-by: Kalkere Ramesh, Sharan <sk720x@att.com>
|
|
|
|
SO 1.7.9 containers are release containers
so-bpmn-infra: 1.7.9
so-catalog-db-adapter: 1.7.9
so-monitoring: 1.7.9
so/nssmf-adapter: 1.7.9
so/openstack-adapter: 1.7.9
so/request-db-adapter: 1.7.9
so/sdc-controller: 1.7.9
so/sdnc-adapter: 1.7.9
so/vnfm-adapter:1.7.9
so/api-handler-infra:1.7.9
Issue-ID: SO-3216
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: I14d3347225dc1a6c072dbb2e56e5bb985867f25a
|
|
Some SO components are using readiness check init container. In "gating"
mode, so image and readiness image are not coming from the same
repository.
By using readinessCheck charts, we can control that.
Issue-ID: OOM-2617
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I44a4e9daf72d1a42d3d84b6d56b588cd7d44fb08
|
|
so-db-secrets was used to create secrets
for db creds. But now, they are being created
from secrets metaconfig. It is not needed
Issue-ID: OOM-2534
Signed-off-by: Krishna Moorthy <krishna.moorthy6@wipro.com>
Change-Id: I0f0514b0b704e4643253b793ea4bd9ad92329759
|
|
SO BPMN infra uses "v1" version for VNF handling, which is not
compatible with multicloud.
This patch allows to choose which version to use, defaulting to "v2"
version.
Issue-ID: SO-3342
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I548f9f1e264ea7a21ee2d604e5de5c3b65599943
|
|
Move subcharts to components folder in order to be able to
enable/disable them one by one.
Also use certInitializer to retrieve truststore in order to be able to
discuss with other ONAP components.
Issue-ID: SO-2046
Change-Id: Ia5c2a590a2ad75e4b69be0748e9d79fda996af37
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|