Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: OOM-2459
Signed-off-by: Katarzyna Wasiel <katarzyna.wasiel@nokia.com>
Change-Id: I0c52e0c0de799cd90270794f51ad000f05122265
|
|
Update image for Frankfurt release.
Change-Id: Idc26b081694b8d7270fea81a30d595d41b6b9240
Issue-ID: OOM-2397
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
|
|
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: MULTICLOUD-1036
Signed-off-by: Konrad Bańka <k.banka@samsung.com>
Change-Id: I81161664e257fc4d5c459ee6255ffa5e3f4371c7
|
|
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
|
|
image can't be pulled from registry.hub.docker.com repository hence
changing it to working one.
non-working ==> registry.hub.docker.com/onap/multicloud/framework-artifactbroker:1.4.2
working ==> nexus3.onap.org:10001/onap/multicloud/framework-artifactbroker:1.4.2
Issue-ID: MULTICLOUD-844
Signed-off-by: Ondřej Šmalec <o.smalec@partner.samsung.com>
Change-Id: I1449cc0ff4a2fb4a5f4230515e9422f32cdbf5b5
|
|
Update docker image version to latest version from
docker hub.
Issue-ID: OOM-2117
Change-Id: I4de4fec038c6a305363df95feba171bfba0cd410
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
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
|
|
bump multicloud-k8s image to 0.4.0
Issue-ID: MULTICLOUD-641
Signed-off-by: Liexiang Yue <yueliexiang@chinamobile.com>
Change-Id: I14914e42426657bc40837b4d34b716f38c948465
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
add artifact broker to k8s plugin by specified forwarder
update another plugins configuration to use multicloud instead of
policy per the confirmation from SDC PTL
make the port configureable
update the concerned type to include VF_MODULES_METADATA
add /data dir into k8s artifactbroker
P7: Remove tabs from config.json
Change-Id: I614b85ef512740e9bb44d431760d8e7424fb804b
Issue-ID: MULTICLOUD-631
Signed-off-by: liboNet <libo.zhu@intel.com>
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Add etcd to requirements.yaml and
add the service name to the configuration file
Issue-ID: MULTICLOUD-638
Change-Id: Idef37e50f535dcb79e39e5cebfd2c95c660b8e3c
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Add helm charts for multicloud-k8s
Add support for access via msb internal gateway
Use 9015 port instead to align with other Multicloud
services
Add Makefile under multicloud to do helm dep up for k8s
as k8s uses the mongo chart in its requirements.yaml
Update licenses
Issue-ID: ONAPARC-363
Change-Id: I31aaf9e97a3807501af5bf7e56b3df53dfc22074
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|