Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
Removing https communication as SO SOL003 Adapter has used its own keystore for communications with bpmn-infra and etsi-nfvo
with hardcoded password.Common way of certicates will break existing communication so going for HTTP path due to time constraint .
Will revisit security in Honululu as part of https://jira.onap.org/browse/SO-3350 epic.
Change-Id: I521d9be9007f229919fb5d88f476a692faae10e1
Issue-ID: SO-3349
Signed-off-by: Mukesh <mukeshsharma@est.tech>
|
|
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
|
|
|
|
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
|
|
Signed-off-by: Jakub Latusek <j.latusek@samsung.com>
Change-Id: I15281199766092663aa2c0f8b96ae16979ccaa5f
Issue-ID: OOM-2562
|
|
Issue-ID: SO-3205
Signed-off-by: Priyadharshini <priyadharshini.b96@wipro.com>
Change-Id: Ic25f2a1421cc7a2370f1793b6c6735a55b4d78c9
|
|
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>
|