Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
ONAP projects using HTTP port to connect to DMaaP Message Router (MR), please start using HTTPS port
Issue-ID: EXTAPI-371
Signed-off-by: MatthieuGeerebaert <matthieu.geerebaert@orange.com>
Change-Id: I965f57599bb11fe0ee85a1fa66a55bf292399c58
|
|
Instead of having our "own" galera cluster, use the common one already
proposed by OOM.
If a local cluster is needed, you just need to set
global.mariadbGalera.localCluster to True.
Also create a common chart that create the needed values for the
database.
Change-Id: I9ad551b76a40732b4ab3fc34ba7cde6ca90fe432
Issue-ID: EXTAPI-348
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: EXTAPI-341
Signed-off-by: MatthieuGeerebaert <matthieu.geerebaert@orange.com>
Change-Id: I94b41e338d80939934c7d42fd518d0984cf89b92
|
|
Instead of using "homegrown" mariadb chart, move to use the common
mariadb-galera chart in order to be aligned with most of the other users
of mariadb and eventually to move into the common mariadb galera
instance.
Change-Id: I0c8ed6adfea0d64f97e7d9378464039915d389c7
Issue-ID: EXTAPI-347
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
TMF Forum moved from v3 to v4 (no backward compatibility)
template must reflect it
problem detected when running End to end case using NBI for instantiation
Issue-ID: EXTAPI-247
Change-Id: I937eca3a00d37df83c6871c65a00d37ad516d03a
Signed-off-by: mrichomme <morgan.richomme@orange.com>
|
|
Change-Id: Ie24091607ae131599ca107a5191a9cd55dc58991
Issue-ID: OOM-1725
Signed-off-by: aosull01 <adrian.osullivan@huawei.com>
|
|
Issue-ID: OOM-1145
Change-Id: I1510339a820802554b6e8b9a201619ef66be17a0
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Issue-ID: OOM-1153
Change-Id: Icd62d392b2e2a275a273b7f6260ad39d68987f50
Signed-off-by: vaibhavjayas <vaibhav.jayas@amdocs.com>
|
|
- update nbi image version
- add new configs for msb integration
Change-Id: Ia5ba5e7a539464d54c5286b37e092b0858a6f3a3
Issue-ID: EXTAPI-147
Signed-off-by: Quoc Nghia Nguyen <quocnghia.nguyen@orange.com>
|
|
Issue-ID: OOM-1303
Change-Id: I7c3407e01619aa4463f7f8285cfad57ce17ee294
Signed-off-by: Prateekinlinux <prateek.khosla@amdocs.com>
|
|
PS-3 MK: the sample value for openStackVNFTenantId is being
interpolated as a number because it is all numeric.
Going with the quoting it at the template level.
Changing the value to 12345abcde probably would work too.
Change-Id: I2f81430e56f465543d3701a2d8cd4b562e7e987d
Issue-ID: OOM-1116
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
The pair-wising tests failed based on OOM.
sdc-be should be used instead of sdc-fe
https must be used for aai
Change-Id: I95109b3f99fb75b5017e017e964ed05b2435d26d
Issue-ID: EXTAPI-92
Signed-off-by: Eric Debeau <eric.debeau@orange.com>
|
|
NBI (North Bound Interface) is one of the new project added for Beijing
release.
Features added
==============
MongoDB common chart
--------------------
Ability to start a mongo container, with a chart consistent with other
common charts (readiness, liveness, persistence, resources, nfs,
service, ...).
Specific configuration:
* name of the db to create if needed
NBI chart
---------
Ability to start a mariadb container, with a chart consistent with other
common charts (readiness, liveness, persistence, resources, nfs,
service, ...).
Specific configuration:
* name of the db to create if needed
* name of the user that has access to the db
* password of the user that has access to the db
* root password of the database
Ability to start a NBI container, with a chart consistent with other
common charts (readiness, liveness, persistence, resources, nfs,
service, ...).
Specific configuration:
* log level
* cloudOwner
* ecompInstanceId
* openStackRegion
* openStackServiceTenantName
* sdc_authorization
* aai_authorization
* so_authorization
ONAP chart
----------
Added a requirement on NBI chart, possibility to enable/disable and
configuration to push to the chart.
Current Status
==============
- [*] adding a common chart for mongodb
- [*] make mongo chart compiling
- [*] testing the mongodb common role
- [*] creating a mariadb chart inside nbi helm
- [*] testing the mariadb chart
- [*] make mariadb chart compiling
- [*] make nbi use these charts
- [*] make nbi chart compiling
- [*] test the whole solution
- [*] create a service for nbi
Change-Id: I8dd3e79768c83b1553a05c892cf418f840931255
Issue-ID: EXTAPI-54
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|