Age | Commit message (Collapse) | Author | Files | Lines |
|
Instead of copy-pasting code around aaf_agent usage let's use a common
template that automates this.
Issue-ID: AAF-1134
Change-Id: I266017e4acbcdac89a31dfba775380fd5cd9acfe
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
|
|
Change-Id: I11fe412600d1061e5667a5531d36cecbecdd34e3
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Issue-ID: OOM-2369
|
|
Change-Id: I6e56012ca7baabef1bcd4f475245606fc44d9d91
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Issue-ID: DMAAP-1420
|
|
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: OOM-2051
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: Id21c3e75c1e7a79066ac25c83c4788929412effd
|
|
Currently, persistence was not enabled, preventing creation of relevant
PV/PVC for DMaaP DR.
Setting this persistence as it should be the normal behavior
Issue-ID: OOM-2332
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ic36c0956d40333529d6325af38e33a9bc6838946
|
|
|
|
Change-Id: I4882750ff11343b387dde0452f7bf65a4f612f80
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Issue-ID: DMAAP-1405
|
|
Change-Id: I7a37ab9a69fdb3232f68b908ea97a788fbab55a1
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Issue-ID: DMAAP-1404
|
|
Let's use common secret template to generate user credentials for
DMAAP data router DB DB and depend on mariadb-galera to generate
secure enough root password.
Issue-ID: OOM-2287
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I82d22a2db2dc9fba655f99f837be689f4a32a871
|
|
Change-Id: I48313446853d9175ec41f288350bedbf6190c30c
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Issue-ID: DMAAP-1388
|
|
Change-Id: I3c34258810908b4eb26864f33ee1fc56216906a8
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Issue-ID: DMAAP-1389
|
|
# Also, need to add ready check for aaf-cm
Change-Id: I757f56f5eaa79c1cbecec43aeb99f2701afd7fae
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Issue-ID: DMAAP-1195
|
|
# Also adding AAF ready check for dr-node
Change-Id: I7e6fc29a7f5607cc168f9fd61642a40a9185c55b
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Issue-ID: DMAAP-1367
|
|
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
|
|
AAF config needs to have aaf locate service up and running in order to
work properly (if not, it won't really crash but won't have done the
real work).
As per
https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#understanding-init-containers,
"Each init container must complete must complete successfully before the
next one starts".
Adding a wait for readiness container before aaf config init containers
should then do the job.
Change-Id: Ida047728e4f14320ada8052c707b458450f4923b
Issue-ID: DMAAP-1362
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.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 split the 3 PV from dr-node into 3 files and used range so the
number of PV is the same as number of PODs.
Change-Id: I46b4e62042ea8330bef8cdc1561fa8bbf3f25d12
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: OOM-2179
Change-Id: I6f1591a6c7033812cc714d75c63d7c1b3ba197b6
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
Change-Id: I0bca8c7a16f8b19a266d9961715b8a04971d7b73
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Issue-ID: DMAAP-1269
|
|
Change-Id: I6467c37800ec96bd1b030f0576ce690d408ff5b6
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Issue-ID: INT-1296
|
|
- Remove bootstrapped PM_MAPPER topic
- Remove bootstrapped bulk_pm_feed
Issue-ID: DCAEGEN2-1517
Change-Id: I1ddb83bc587f8392f22633cd637c9ac735b5042c
Signed-off-by: JoeOLeary <joseph.o.leary@est.tech>
|
|
Change-Id: I21496226c2e3babec417e70de03425a0600ccbaa
Issue-ID: DMAAP-1287
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
|
|
Mainly adding release label there."
|
|
Mainly adding release label there.
Issue-ID: OOM-2043
Signed-off-by: Ondřej Šmalec <o.smalec@partner.samsung.com>
Change-Id: Ieeedec79fd85b7ede4752a973ec42ea648f7d6a0
Signed-off-by: Ondřej Šmalec <o.smalec@partner.samsung.com>
|
|
Issue-ID: OOM-2083
Signed-off-by: Marco Platania <platania@research.att.com>
Change-Id: I0318115d85d8507ecba1133d6c8c1a2bc6333b63
|
|
# Increase docker images
# Refactor global vars
# Fix logstash paths etc
# Remove default feed script
Change-Id: Ib15fecc57d6f7f2d4049eff7903c08bc3adb78da
Issue-ID: DMAAP-1283
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
|
|
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
|
|
https://gerrit.onap.org/r/c/86515/ disabled the use of HTTP ports in
Message Router by default and so 3904 is not there on a fresh install.
This commit change the use of default message router port and scheme in
robot testsuite
Change-Id: I92d267b9482c21606fb9b437f6c64a18f044184a
Issue-ID: DMAAP-1152
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
|
|
Change-Id: I6d59e09b0273241c5c98cc60e323940bf84bacdd
Issue-ID: DMAAP-1152
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
|
|
Change-Id: If58484506ce4ae5369a31ec1d5ef374dfb8cceff
Issue-ID: DMAAP-1186
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
|
|
Change-Id: Ifa98f8610b0a96a28f3a3ded7cb65663e9455158
Issue-ID: INT-1042
Signed-off-by: Yang Xu <yang.xu3@huawei.com>
|
|
|
|
Update image version to 2.1.0 that has year long certs
Change-Id: If17c569c6db879b6fcee9221307560a54f9cb422
Issue-ID: DMAAP-1134
Signed-off-by: econwar <conor.ward@est.tech>
|
|
Change-Id: I6eedbd6efa9da1076fe708f7112b3dc344fbfe7f
Issue-ID: DMAAP-1161
Signed-off-by: EmmettCox <emmett.cox@est.tech>
|
|
Change-Id: Ib2767848a40888f8dbd903541d7ee53241e20f5a
Issue-ID: DMAAP-1016
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
|
|
|
|
add Mirror Maker
MR AAF integration
Fix BC images and minor BC bugs
Kafka upgrade to 1.1.1
Issue-ID: DMAAP-823
Change-Id: Ia7a1321a6fbfa9bfc65f90bca40ef236c2dbadef
Signed-off-by: sunil.unnava <sunil.unnava@att.com>
|
|
Change-Id: I5767e3de46e8c67bbc2f5fca2fb133d90db899ed
Issue-ID: DCAEGEN2-1038
Signed-off-by: emartin <ephraim.martin@est.tech>
|
|
Change-Id: I7c4acbed96f67d540f6eb228a196b8ad68260f29
Issue-ID: DMAAP-1072
Signed-off-by: egernug <gerard.nugent@est.tech>
|
|
Not sure what made this commit be separate.
It is intended to be patchset 4 on https://gerrit.onap.org/r/#/c/82150/
But please merge them together.
Change-Id: Ia4c2341e450f0e2910b3ae19becefb6e798e3ef6
Signed-off-by: dglFromAtt <dgl@research.att.com>
Issue-ID: DMAAP-904
|
|
This was originally committed under 81992 but got a merge conflict.
I messed up resolving it so I abandoned 81992 and created this new
commit.
patchset2: replaced Release.Name for common.fullname in one of the
charts
patchset3: at Borislav's request, changed other references to
common.fullname so the approach is consistent throughout the
configmaps used for initialization.
Along the way, hit a limit of 53 chars on some resource name.
So changed the directory
from the verbose dmaap-bus-controller to the more terse dbc.
Change-Id: I1078003de094fee95c681f7fdaecb567235b7b3e
Signed-off-by: dglFromAtt <dgl@research.att.com>
Issue-ID: DMAAP-904
Signed-off-by: dglFromAtt <dgl@research.att.com>
|
|
Change-Id: I540f7f2eb927896eb3f0c03b900f3bf6b9bc7ce5
Issue-ID: DMAAP-866
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
|
|
This will help enable edge deployment
Issue-ID: DMAAP-1068
Change-Id: I61df2887069a0302341c0004914158398ecd58d9
Signed-off-by: econwar <conor.ward@est.tech>
|