Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
Update charts and requirements to 7.0.0.
Create release notes for Guilin
Update documentation
Issue-ID: OOM-2638
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I965ed6b6ebb7d74bfddaff73edd3dd55a657841c
(cherry picked from commit 4f9902b6e7b5c70588160266276904ab81832867)
|
|
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>
(cherry picked from commit df29b1e09931b7e0f4c7cd4bfb363a707a201deb)
|
|
|
|
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 secret was used to give truststore to SO components.
As we're using dynamic certificate retrieval, it's not needed anymore.
Issue-ID: OOM-2534
Issue-ID: SO-3348
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I0eb2e052096923fc69bf5f1a1876d9a76a22102b
|
|
Signed-off-by: Jakub Latusek <j.latusek@samsung.com>
Change-Id: I15281199766092663aa2c0f8b96ae16979ccaa5f
Issue-ID: OOM-2562
|
|
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>
|