Age | Commit message (Collapse) | Author | Files | Lines |
|
Pomba is not a component which will be part of the release.
As such, we don't start it even in "all" ONAP.
Issue-ID: OOM-2371
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I400601dee8e65b1c05948e3ccad99e84eb9c9119
|
|
|
|
EJBCA Server is used to test that CMPv2 Certificate handling is well
done in ONAP.
Issue-ID: AAF-1083
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I5e2d25b68b5cd80d3c7bf282ce871dd81e711ff6
|
|
Issue-ID: OOM-2360
Enable NBI Module in 5G Network Slicing use case override file
Signed-off-by: zhangqingjie <zhangqingjie@huawei.com>
Change-Id: I05d53cd82a037b076b0935ad6a629d094415a3dc
|
|
Issue-ID: DCAEGEN2-1866
Change-Id: I0179e1e75529ad8017b1a5c23747dbd80aa6f625
Signed-off-by: Jack Lucas <jflucas@research.att.com>
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: OOM-2329
supply a ONAP installation config file for 5G Network Slicing usecase,
so that the user can easily install a minimum-scope ONAP with as few
resources as possible.
Signed-off-by: zhangqingjie <zhangqingjie@huawei.com>
Change-Id: I728a0229296d62120418f654e4c3f50a2805a69e
|
|
SO can handle keystone v3 but override file must be capable to handle
this.
If openStackKeystoneVersion is set to "KEYSTONE_V3" in
so-catalog-db-adapter config part, SO will be able to use keystone v3
for OpenStack
Issue-ID: OOM-2221
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I14db318d25842a08ef380f6edb708e26dae050ad
|
|
Issue-ID: OOM-2266
Change-Id: I0c571c765cb099b1f2e7886bc686e24a436f290e
Signed-off-by: Brian Freeman <bf1936@att.com>
|
|
Example ingress configuration with vhosting
support.
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: OOM-2125
Change-Id: I62c818f8941871cbebdfbf1984e7b6eee7e1180d
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
Issue-ID: OOM-2059
Change-Id: I02bbdd5b06e7194434d761bcf1aebbd749c6f1d7
Signed-off-by: Brian Freeman <bf1936@att.com>
|
|
Nginx ingress controller configuration sample adopted
to the new ingress configuration common templates.
Issue-ID: OOM-1508
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: I1e8f069dbcff8ae3c927bad763d1bc2595cc9311
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
Issue-ID: OOM-2085
Signed-off-by: Abdelmuhaimen Seaudi <abdelmuhaimen.seaudi@orange.com>
Change-Id: Iaabdf44581c6b0dc5e0600454a5ff9bcaeaba16c
|
|
Issue-ID: OOM-2085
Signed-off-by: Abdelmuhaimen Seaudi <abdelmuhaimen.seaudi@orange.com>
Change-Id: I21fed8c9cf33967f62f156cac96deefdcb4f8d47
Signed-off-by: Abdelmuhaimen Seaudi <abdelmuhaimen.seaudi@orange.com>
|
|
Add example nginx ingress controller configuration
overrides for testing purposes.
Change-Id: Ibac181c4e79fab4cd5b63b28bf4f25912bfe4724
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: OOM-1508
|
|
|
|
Issue-ID: OOM-1959
Change-Id: I835be9a5eccf72e8e6534da1e5090f21d10c7a5a
Signed-off-by: Brian Freeman <bf1936@att.com>
|
|
The modeling generic parser needs to be enabled in general override
file onap/overrides/onap-all.yaml
Issue-ID: MODELING-175
Signed-off-by: Tomáš Levora <t.levora@partner.samsung.com>
Change-Id: Ia175145b2c9a3c4ca4da1fe8cbf119b41fc9782a
|
|
Change-Id: Ibe57c857b4d9367b77878757821c2e9c44c61a7b
Issue-ID: OOM-1598
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Change-Id: I2a0428bfec238231b299c9f35364979b116a5d67
Issue-ID: OOM-1598
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Currently when you deploy onap with no override file, the behavior is
to deploy everything. In order to deploy a subset of components, an
override file must contain all components and then disable the ones
you don't want. As we prepare to transfer helm chart ownership to the
teams, it will simplify the creation of project specific development
override files, if the default behavior for deploying onap was
reversed. Allowing override files to only contain the components
they care to enable (and configure) and ignore the rest as they
would be disabled by default.
From this point on, it will be necessary to use an override file
(as integration uses for testing) to enable all components. This
patch includes an onap-all.yaml override file that may be used for
this purpose.
helm deploy dev local/onap -f onap/overrides/onap-all.yaml
No configuration is part of this override. Its purpose is only to
enable the components and is intended to be used in combination with
other override files that provide environment specific configuration.
Change-Id: I4b74a3a8a35a178298af7205762e2aca7c65dda3
Issue-ID: OOM-1692
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|