Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Log 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-2370
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I0238632a3a62ad7cfeee3656afc74144a6337c46
|
|
|
|
Add elasticdb as common chart to oom
Issue-ID: SDNC-1061
Signed-off-by: Alexander Dehn <alexander.dehn@highstreet-technologies.com>
Change-Id: Id8c48113b8d4193d7f13991296f0307a29724c01
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
|
|
Issue-ID: OOM-2365
Signed-off-by: zhangqingjie <zhangqingjie@huawei.com>
Change-Id: I18b1c3198c669e7a7bda368f8d9ce8ba5790555b
|
|
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
|
|
Cleaned up up configs, JDK11 fixes, Hello and Agent works, now a model for Apps
non-root fix
Issue-ID: AAF-1081, AAF-1102
Signed-off-by: Instrumental <jgonap@stl.gathman.org>
Signed-off-by: ChrisC <christophe.closset@intl.att.com>
Change-Id: I4947075029db8abd7d2072b6b82064af8e2daa3e
|
|
"index" function is bad in term of performance in Helm.
Reworked the templates in order to avoid it.
as certificates are retrieved at every boot (and as already present
certs are deleted before), we don't need persistent storage
Also set aafImage as a global variable in order to have a consistent use
accross ONAP
Issue-ID: EXTAPI-375
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ie3f5ae5c2a37d816afc42d2c67ebe8e40e749c79
|
|
Use 6.0.0 in preparation for Frankfurt release
Issue-ID: OOM-2320
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I8ad82dfdf48b56c38c0e85d640b18cc13c8d9e67
|
|
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
|
|
Current service and headlessService templates doesn't handle the fact
that out of cluster ports must be TLS encrypted only.
With a new (backward compatible) DSL, this is now possible.
In values.yaml, all ports in service part with port AND plain_port will
have the ability to be HTTP or HTTPS depending on the context.
Per default, they'll be HTTPS.
TLS choice will be done according this table:
| tlsOverride | global.tlsEnabled | global.serviceMesh.enabled | global.serviceMesh.tls | result |
|-------------|-------------------|----------------------------|------------------------|--------|
| not present | not present | not present | any | true |
| not present | not present | false | any | true |
| not present | not present | true | false | true |
| not present | not present | true | true | false |
| not present | true | any | any | true |
| not present | false | any | any | false |
| true | any | any | any | true |
| false | any | any | any | false |
Service template will create one or two service templates according to this table:
| serviceType | both_tls_and_plain | result |
|---------------|--------------------|--------------|
| ClusterIP | any | one Service |
| Not ClusterIP | not present | one Service |
| Not ClusterIP | false | one Service |
| Not ClusterIP | true | two Services |
If two services are created, one is ClusterIP with both crypted and plain
ports and the other one is NodePort (or LoadBalancer) with crypted port only.
Issue-ID: OOM-1936
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: If766dd73132022d1a6e578fd36113c461bb91ea5
|
|
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
|
|
Proposition of common templates to make service declaration and PV
declaration consistent accross OOM.
Propositions of templates for sub parties of resource definitions
such as metadatas, selector and containerPorts.
I've also made an example with cassandra.
Change-Id: I8b8aa8eb61dafba75e89add1979114a0eefce243
Issue-ID: OOM-1971
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
|
|
ONAP is too big to be deployed using helm install so we need to
use a custom helm plugin helm deploy. This script deloys onap
component by component instead of deploying evrything at
once. Unfortunately this script also modifies the helm release by
appending component name to it.
As a result of this behavior our objects are called for example:
onap-mariadb-galera-mariadb-galera-0
instead of just being called onap-mariadb-galera-0.
This patch simplifies this naming convention by replacing all direct
usages of .Release.Name with common.release macro which strips the
component specific part from the release name.
Issue-ID: OOM-2275
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: Ia8cead50d305adb00eef666d0a1ace74479b5183
|
|
This patch makes heavy use of Orange accomplishments [1][2][3]. This
deployment override will probably succeed "minimal-onap.yaml" used in
e.g. "integration/bootstrap/vagrant-minimal-onap" setup.
Cassandra replicaCount is increased to 3 to allow reaching quorum.
[1] https://gitlab.com/Orange-OpenSource/lfn/onap/onap_oom_automatic_installation
[2] https://wiki.lfnetworking.org/display/LN/Call%20for%20ONAP%20DDF%20Topics%20-%20Prague%202020#CallforONAPDDFTopics-Prague2020-OOM-IntroductionofServicemesh
[3] https://wiki.lfnetworking.org/download/attachments/25364127/OOM%20Service%20Mesh%20Prague.pptx
Issue-ID: ONAPARC-551
Change-Id: Ibaec41f088f11f7fb4e7c476f742d12d29c5740b
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
Issue-ID: OOM-2266
Change-Id: I0c571c765cb099b1f2e7886bc686e24a436f290e
Signed-off-by: Brian Freeman <bf1936@att.com>
|
|
Deployment of AAI component fails unless Cassandra is enabled in the
cluster [1].
This patch also adds Cassandra to the list of enabled components and
fixes minor typos in the documentation.
[1] https://git.onap.org/aai/oom/tree/requirements.yaml#n23
Issue-ID: INT-1402
Change-Id: I5cb57e1909f749bb8d28fac0e5eeb09f6cfe4b33
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
|
|
|
|
|
|
OOM has now templates in order to create the needed PVC, using:
* a PV with a specific class when using a common nfs mount path between
nodes (sames as today use) --> is the default behavior today
* or a storage class if we want to use dynamic PV.
On this case, we use (in order of priority):
- persistence.storageClassOverride if set on the chart
- global.persistence.storageClass if set globally
- persistence.storageClass if set on the chart
I've also aligned the PV creation of the different charts.
I've also aligned the PVC creation of the different charts.
I've removed unused mysql chart and (badly) used nfs-provisioner chart.
I've also make cassandra backup work with dynamic PV (but RWX only for
now).
Change-Id: I0ea3f8c7514ca648d94b6c682684c06b822bbe0a
Issue-ID: OOM-2229
Issue-ID: OOM-2228
Issue-ID: OOM-2227
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Add virtual hosting support to the ingress
common template
Added support for global configuration path
or virtual host based
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: I6b1a0c9cfd0eb5c90a090058d5db70f8ee33731e
Issue-ID: OOM-2125
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.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>
|
|
Helm value override file now supports component-specific settings:
dcae-bootstrap:
enabled: true
dcae-cloudify-manager:
enabled: true
dcae-config-binding-service:
enabled: true
dcae-healthcheck:
enabled: true
dcae-redis:
enabled: true
dcae-servicechange-handler:
enabled: true
dcae-inventory-api:
enabled: true
dcae-deployment-handler:
enabled: true
dcae-policy-handler:
enabled: true
dcae-dashboard:
enabled: true
Issue-ID: OOM-1574
Signed-off-by: Ubuntu <dgl@research.att.com>
Change-Id: I85e0fe6ae19e176d954611549ec954a5fe662307
Signed-off-by: Ubuntu <dgl@research.att.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>
|
|
Issue-ID: OOM-2076
Signed-off-by: Akansha Dua <akansha.dua@amdocs.com>
Change-Id: Ide894e27c417a3e2a010cbc24f18353ffe698ce5
|
|
RKE.
Issue-ID: OOM-2050
Signed-off-by: Ondřej Šmalec <o.smalec@partner.samsung.com>
Change-Id: I72802282d296c6e1f23f96112a6406ded18aa5ab
|
|
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
|
|
Add nginx ingress controller support to the OOM
nginx ingress controller is disabled by default.
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: I97683ede7d99d2c8ca2f512c962d2d8d03467124
Issue-ID: OOM-1508
|
|
Issue-ID: OOM-1980
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
Change-Id: I39ed586738aa1bb5c336973ce0ee55ebebd7f183
|
|
Updating all helm chart versions to 5.0.0 for the El Alto release.
Merge will be co-ordinated with the merge of a separate aai/oom patch.
Please do not merge until this coordination has completed.
Issue-ID: OOM-1980
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
Change-Id: I31daaebeacea33565f13affd2fa28fb15fe948ba
|
|
|
|
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
|
|
The so mariadb was missing so prefix
from the name breaking convention.
Issue-ID: OOM-1921
Signed-off-by: Joey Sullivan <joey.sullivan@amdocs.com>
Change-Id: I5c26ab8943698e420fbdc198f0837e653a708185
|
|
Issue-ID: MODELING-165
Change-Id: I46419561fdc3f1b4fb7a7bcf19185ac6cbd99c1d
Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>
|
|
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>
|
|
Issue-ID: OOM-1500
Change-Id: I15dd98ea8042914220f1b6025e93f65224bb9adb
Signed-off-by: sushil masal <sushil.masal@amdocs.com>
|
|
Issue-ID: OOM-1747
Change-Id: I9a3a1751fdd4cae1ce48d56b4a1b202ba9c3de4b
Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
|
|
Change-Id: Id3fbbc7ad639bfd03ddbfc931abf774407851d74
Issue-ID: OOM-1193
Signed-off-by: Pramod <pramod.kumarsharma@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>
|