Age | Commit message (Collapse) | Author | Files | Lines |
|
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 sub-components of the SO that are depend on the latest SO core component.
Issue-ID: SO-3473
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: I7528df6aeac00bb2c64b4659185ab7f72d4f2aff
|
|
Update:
- cnf adapter to 1.8.0
- nssmf adapter to 1.8.0
- oof adapter to 1.8.2
Issue-ID: SO-3473
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I10af676b741941cc9ecf4e6ea373363dd7c66b35
|
|
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
|
|
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>
|