Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
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
|
|
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
|
|
|
|
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>
|
|
Improve common secret template by adding:
- ability to generate secrets if they are not provided
- ability to fail the deployment if marked secret is not provided
- support for using already existing secret instead of creating
a new one
Issue-ID: OOM-2053
Change-Id: Ic101f384f7c767702f646eb0e879ec80bf9a6334
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
|
|
Separated from change:
I65f9891f1d3586c0633b252a47b461c887d5b8ad
to allow the template to be easily merged to master.
Issue-ID: OOM-1971
Change-Id: I8dd4128bfa6e614ba5ddd084c45ca008e4da87ad
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
[Separate from other changes, add license header,
update commit message]
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.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 used "range" for PV creation of the statefulset
I've created one file per PV (one for mdsal, one for certs).
sdnc-prom was using hostpath directly on deployment, move to a PV/PVC.
Change-Id: Id9eed3b13ac85595c386e380f41cfbc38b52c69f
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Workaround is no longer needed, after CATALINA_OPTS
parameters are late-evaluated.
See commit https://gerrit.onap.org/r/c/vid/+/99583 (change
id Ife2a2e92b3745691cc45590d1afd1688d918048f).
Issue-ID: VID-650
Change-Id: Ibb27d050632e8ce9b96da6e4033840380d1f3f72
Signed-off-by: Ittay Stern <ittay.stern@att.com>
|
|
The log config error results in log output failure
Change-Id: I6451e678c3ac509ed676699ac048200feebc6ab8
Issue-ID: MULTICLOUD-966
Signed-off-by: Bin Yang <bin.yang@windriver.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>
|
|
Now using org.onap.logging libs, improved formatting, and
full MDC key/values dump.
Added outgoingRequests logging of upstream in-out traffic.
See also:
VID logs to Logging Specification v1.2 (Casablanca)
https://wiki.onap.org/pages/viewpage.action?pageId=28378955
Issue-ID: VID-253
Change-Id: If1378319d6c77fef0d08adc8e5e08c98cab50580
Signed-off-by: Ittay Stern <ittay.stern@att.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 created a PV/PVC couple for logs of ES as it was hardcoded in
the deployment.
Change-Id: Ic2da694da008803f5afc1a0e0de38a1428c5b40e
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update kubernetes/robot from branch 'master'
to bc1480dc6c66d23ed04feaff93fca10da6a65a8f
- Merge "Use global storage templates for PVC"
- Use global storage templates for PVC
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
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ie65e55bca92eb0ada674636f049ecb054b65c5da
|
|
* Update kubernetes/robot from branch 'master'
to dbb4ed7385a22871a0ffb719f04e0f0f257d0ab3
- Merge "Add distributeVCPE"
- Add distributeVCPE
Issue-ID: INT-1397
Change-Id: I172fc986207a61c91b2dc9b1efa5c58bd689ea06
Signed-off-by: Brian Freeman <bf1936@att.com>
|
|
* Update kubernetes/robot from branch 'master'
to a7e566c2c15914ad409ab4135891c0c092c300f0
- Add /etc/hosts
Issue-ID: PORTAL-782
Change-Id: I8f7abd28c357cf6525c3368f38035a45126bf2ae
Signed-off-by: Brian Freeman <bf1936@att.com>
|
|
* Update kubernetes/aai from branch 'master'
to c56543fa8c464f839cde7d80ff2023d6448e4b28
- Fix the startup issue of data router liveness
so that the pod does die before it even had
a chance to start the application
Issue-ID: AAI-2727
Change-Id: I94246883cc5b46c7e9873e70214599653514d7d8
Signed-off-by: Harish Venkata Kajur <vk250x@att.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|