Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: VID-716
Change-Id: Ia6344de1aa524d25a8818e18bfe693cacffc26c8
Signed-off-by: Ittay Stern <ittay.stern@att.com>
|
|
Issue-ID: VID-253
Issue-ID: VID-471
Change-Id: I642bdc7a3926bf3be897f959aa1886617b2978d6
Signed-off-by: Ittay Stern <ittay.stern@att.com>
|
|
|
|
|
|
* Update kubernetes/aai from branch 'master'
to 69f85c4ba9f621e5f5172c0dd637048fe7ef3cfd
- Update charts for released containers
Issue-ID: AAI-2763
Change-Id: Ie005febc51040e1dd7fffb104171ee1ee2ccdd98
Signed-off-by: Forsyth, James (jf2512) <jf2512@att.com>
|
|
|
|
When creating https://gerrit.onap.org/r/c/oom/+/99478, forgot to
backport storage class part of https://gerrit.onap.org/r/c/oom/+/98962.
Issue-ID: OOM-2234
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I3c42b28ad5bea67eda004b0209c8a21783b539f1
|
|
https://gerrit.onap.org/r/c/oom/+/98938 forgot to remove selectors for
PVC and prevent it to work with storage class.
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ieb45ecbe8c046d6c3bc72e47776df3c9d64de2e5
|
|
For some reason unknown to me I was stupid enough to forget to
put ! in a front of variable name in the final vesion of script.
Let's just quickly fix that so that not too many people notice;)
Issue-ID: OOM-2248
Change-Id: I0b8891b94856b21f4b1fad1d6731c461bae2c1aa
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
|
|
* Update kubernetes/robot from branch 'master'
to 4bd799e5dbcbf2131a685bf73319e962ace86f5c
- Move Storage access to RWO
Today when deploying Robot with OOM, the PersistentVolumeClaim needs the
"ReadWriteMany" (or "RWX") capability.
According to Kubernetes Documentation (https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes),
ReadWriteMany stands for "the volume can be mounted as read-write by many nodes".
That means that a particular PVC needs to be read and written from many pods.
That also means that your code takes that into account and do the work to avoid
write at the same place at the same time.
An issue on RWX mode is that most "official" storage driver from Kubernetes doesn't
support it (13 over the 19 drivers doesn't support it, espacially OpenStack, Amazon
and Google storage classes).
Robot PVC is used only for one Robot instance. Thus we don't need RWX.
Issue-ID: INT-1230
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I300e34a9d4be40b36153812d2a99c458cae6b2c9
|
|
|
|
Add support for AAF init container for config and cert generation
Issue-ID: SDNC-755
Signed-off-by: Agarwal, Ruchira (ra1926) <ra1926@att.com>
Change-Id: I06ee7921b6dbb1b4b9ca64cf276a374256af3a45
Signed-off-by: Agarwal, Ruchira (ra1926) <ra1926@att.com>
|
|
|
|
|
|
|
|
|
|
* Update kubernetes/robot from branch 'master'
to 80a8b8c11d94af39ed26701dc10f2d3fc9e9a042
- Merge "Add ingress controler support to ROBOT"
- Add ingress controler support to ROBOT
Issue-ID: OOM-2186
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: Id6b6f6d1a5d9ea83f73b914509098f7711a6418a
|
|
* Update kubernetes/aai from branch 'master'
to c8663688eb2755ca5adc4f570c7acf76b6f9a077
- Merge "Remove the usage of uuidv4 since it was causing the deployment to change at every "helm deploy" causing AAI ha proxy pod to restart and cause AAI outage."
- Remove the usage of uuidv4 since it was causing the deployment
to change at every "helm deploy" causing AAI ha proxy
pod to restart and cause AAI outage.
Issue-ID: OOM-2226
Signed-off-by: Sebastien Premont-Tendland <sebastien.premont@bell.ca>
Change-Id: I03aa47240251fe182ecd841a99a9b99a20c88d65
|
|
* Update kubernetes/robot from branch 'master'
to ff678657c0fa534840d063131432e1994829f660
- Update DCAE username and password
Change-Id: I575be45bbbd2c53a897eac87f303e45cc2fce976
Issue-ID: INT-1375
Signed-off-by: rajendrajaiswal <rajendra.jaiswal@ericsson.com>
|
|
Issue-ID: OOM-2261
Signed-off-by: Avi Ziv<avi.ziv@amdocs.com>
Change-Id: I7f220f8b6b64165c33ed8d707834091240136199
Signed-off-by: Avi Ziv<avi.ziv@amdocs.com>
Change-Id: I7f220f8b6b64165c33ed8d707834091240136199
|
|
|
|
Change-Id: I6b99ccf9bd50d2ec50693df9d4122417b22bcf7a
Issue-ID: SO-2575
Signed-off-by: rope252 <gareth.roper@est.tech>
|
|
As latest are buggy
Change-Id: I8bad9075bc7f4cbcb4bd8274bfbef3d24b15f843
Issue-ID: OOM-2260
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update kubernetes/aai from branch 'master'
to d801a6ee395220b11bfac773c3111489282e735c
- Use the frankfurt release data router image
Issue-ID: AAI-2727
Change-Id: I85fc2b830156e913abc845b91348990ff2127b20
Signed-off-by: Harish Venkata Kajur <vk250x@att.com>
|
|
Replace two sets of commands with a simple loop.
Issue-ID: OOM-2248
Change-Id: I83a748cdad256e7206310d45a987530b4acc621b
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
|
|
|
|
|
|
|
|
Release 6.0.1 supports the current OOM chart setup (without
VID_KEYSTORE_PASSWORD workaround).
Issue-ID: VID-650
Issue-ID: VID-716
Change-Id: Ie326a9b0cc5c892f815470384b92938ab2312c62
Signed-off-by: Ittay Stern <ittay.stern@att.com>
|
|
Issue-ID: CCSDK-2020
Signed-off-by: Jozsef Csongvai <jozsef.csongvai@bell.ca>
Change-Id: Ifebfdaef0907ce441e567d1ff1fc105e0be62243
|
|
Change-Id: Ic73ad605ac3aca689221afed258eb3673398e425
Issue-ID: POLICY-2308
Signed-off-by: a.sreekumar <ajith.sreekumar@est.tech>
|
|
* changes:
Use common secret template in mariadb-galera
Improve common secret template
Add secret template to common templates
|
|
|
|
|
|
For compatibility reasons with the legacy pap, console, brmsgw
and pdp-x.
Issue-ID: POLICY-2320
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: I4fa05e1862acccecb468045a5ff58a84d92b1c26
|
|
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>
|
|
Instead of defining the secret in some custom way let's use the common
template (common.secret). To avoid some issues in ONAP components that
depend on this chart let's do not remove for now the default username
and password. We will do this when all services properly utylize
secrets to store mariadb credentials.
Issue-ID: OOM-2053
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I78e224299cccd9632192ee03a45cd077e6f0906f
|
|
|
|
Issue-ID: OOM-2245
Signed-off-by: Ubuntu <dgl@research.att.com>
Change-Id: Ie5e63a847904c67be1804e97afac8b2a058685a6
Signed-off-by: Ubuntu <dgl@research.att.com>
|
|
|
|
|
|
|
|
Change the dummy password values to OBF: so that the properties files
will load correctly at application start-up.
Change-Id: I1903026ca57db460c41163e1f7dc42a02fd3c2e2
Issue-ID: AAI-2110
Signed-off-by: Leonard, Mark (ml401d) <ml401d@att.com>
|
|
|
|
|
|
|
|
Remove not longer suported and incompatibile option from
the SDC nginx ingress configuration
Issue-ID: OOM-2187
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: I5bddbc8400569cc8a58c48cd15ca00991336e1c8
|
|
Instead of statefulset + inner work in the container, use deployments in
order to be more reliable
Change-Id: Icf4fe1303ae3489c822558e28bb08b69af2d4970
Issue-ID: OOM-2234
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
|
|
Update of the workflow fe and be charts to secure the communications and to start the backend server is https mode with a secured connection to SDC
Issue-ID: OOM-1954
Signed-off-by: IlanaP <ilanap@amdocs.com>
Change-Id: Ia3c4c714e317b8f8b6b4ee9245daa50eea50275f
Signed-off-by: IlanaP <ilanap@amdocs.com>
|