Age | Commit message (Collapse) | Author | Files | Lines |
|
* Update docs/submodules/oom.git from branch 'master'
to 78211d7aabf6d7612e5c94cecbd40eb3c29a48d6
- Merge "Give user link to submodule instructions"
- Give user link to submodule instructions
Issue-ID: OOM-2245
Signed-off-by: Ubuntu <dgl@research.att.com>
Change-Id: Ie5e63a847904c67be1804e97afac8b2a058685a6
Signed-off-by: Ubuntu <dgl@research.att.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 45af03afbe57b068ebffb45e91c230cc50d4344c
- Merge "[DMaaP] Use global storage templates for PVC"
- [DMaaP] 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
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>
|
|
* Update docs/submodules/oom.git from branch 'master'
to aab7b218f456882edb50eb4b7f4358eadadb3df2
- Merge "VID: Remove VID_KEYSTORE_PASSWORD workaround"
- VID: Remove VID_KEYSTORE_PASSWORD workaround
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>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 8e28f7b7d9f32e3c472a717a8a8c7874e5724f8b
- Merge "[SDNC] Use global storage templates for PVC"
- [SDNC] 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
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>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 1dd281fc7e5d96d585561dd9bdbb90173a698a6a
- Merge "Enable Cassandra for AAI in minimal ONAP environment"
- Enable Cassandra for AAI in minimal ONAP environment
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>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 4a18669124ad341e06ffec59711a477d7223c873
- Merge "Secure FE communications to the workflow backend"
- Secure FE communications to the workflow backend
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>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 448a16ef7f4816620fb45e842a664c6e6dc65c52
- Merge "Remove old nginx configurtion from the SDC"
- Remove old nginx configurtion from the SDC
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 docs/submodules/oom.git from branch 'master'
to 2b1c87f302e8b6ffef589036da49e66bc3e7d1c5
- Merge "VID logging adjustments"
- VID logging adjustments
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>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 9037af96894f8995c6d03e6526b0d6260ff66aac
- Merge "DMaaP switch from HTTP to HTTPS"
- DMaaP switch from HTTP to HTTPS
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
|
|
* Update docs/submodules/oom.git from branch 'master'
to 8501d7cee5a887f9e19d5fe3671ef8180bce526b
- Update git submodules
* 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 docs/submodules/oom.git from branch 'master'
to f817f1b029cbc719e44fafa41a7badc9f55c8ce2
- Update git submodules
* 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 docs/submodules/oom.git from branch 'master'
to f3a92b5028146cd4e3f4965533182ea355118ac5
- Update git submodules
* 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 docs/submodules/oom.git from branch 'master'
to 45f718de8420b77cd5f2250f26bc4f9f73879b50
- Update git submodules
* 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>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 525447ad64582c9d8a94542cc32e89c9986d864d
- Merge "Mavenized image creation for readiness-check"
- Mavenized image creation for readiness-check
Issue-ID: INT-1045
Change-Id: I9c7b7fd26c8f376600aa7efc9c1d9e2eee001cde
Signed-off-by: Dmitry Puzikov <dmitry.puzikov@tieto.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 10ab5daccb4375ca8644ad9d738bbdb2efc7a650
- Merge "Example ingress configuration with vhosts"
- Example ingress configuration with vhosts
Example ingress configuration with vhosting
support.
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: OOM-2125
Change-Id: I62c818f8941871cbebdfbf1984e7b6eee7e1180d
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 0f15ec82c3ef94ac510350d43184299564a9fa85
- Merge "Add ingress configuration for so-monitoring"
- Add ingress configuration for so-monitoring
Add ingress configuration file for so-monitoring component.
Ingress configuration can be changed in onap-all.yaml
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: I122e52fc1ed9db78bb0249715e8cd25a9d6318a3
Issue-ID: OOM-1508
|
|
* Update docs/submodules/oom.git from branch 'master'
to 73a2c25f2a9ea88e6bbce1175104ca46dd9a21d3
- Merge "[APPC] Use global storage templates for PVC"
- [APPC] 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
Change-Id: I04757c8fffc4987c4d49da9f474f3e20367de214
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 05942430664ddd4a35f830c5e7488ecd4122c83d
- Merge "[AAF] Use global storage templates for PVC"
- [AAF] 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
I've also modified statefulset deployment so they can use their own PVC
instead of writing into a specific directory inside
I've also set to 'emptyDir' volumes when persistence is not enabled
(except for aaf-config-pvc and aaf-status-pvc, which means that AAF will
still not work when persistence is disabled).
Change-Id: I05f133f058ebd9678df9ac0b7ef32bb43689e94f
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 5145c61e87e1d73935d395abfba6b9becb5d3b87
- Merge "[Common] Use global storage templates for PVC"
- [Common] 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
I've also aligned the PV creation of the different charts.
I've also aligned the PVC creation of the different charts.
I've removed unused mysql chart and (badly) used nfs-provisioner chart.
I've also make cassandra backup work with dynamic PV (but RWX only for
now).
Change-Id: I0ea3f8c7514ca648d94b6c682684c06b822bbe0a
Issue-ID: OOM-2229
Issue-ID: OOM-2228
Issue-ID: OOM-2227
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 9b5e461732ac47203a3fce5cef12700184b34021
- Merge "Adding sdclistener properties for health check"
- Adding sdclistener properties for health check
Issue-ID: CCSDK-1669
Signed-off-by: ShaabanEltanany <shaaban.eltanany.ext@orange.com>
Change-Id: Id7343225f8c46c38d3c44c6c9ffdfe895742e5d6
|
|
* Update docs/submodules/oom.git from branch 'master'
to 68793f5b5eda291aa35069ad4a82baa22b687974
- Merge "[AAF] No resources limits on PODs"
- [AAF] No resources limits on PODs
There were no resource limits on POD.
Setting them.
Change-Id: I1b57c3f1cd1b1dc71bbad4f7c307b1658d6e23e5
Issue-ID: OOM-2230
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 1bb3c73eb0b9e2cd1c667e8c0997421b84355869
- Merge "[Contrib] Use global storage templates for PVC"
- [Contrib] 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
Change-Id: I278e62821ca98e41f63306e502cca1019ba18756
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to b76e563c2091b311450ada9c9e702bd44f7de734
- Merge "[CDS] Use global storage templates for PVC"
- [CDS] 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
Change-Id: I9ffc9f121fb68993dd7bf96d4909913c3aaa09c3
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 2fcb342c4e8feb654e034bde46547b13f67cb589
- Merge "[PORTAL] Use global storage templates for PVC"
- [PORTAL] 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
Change-Id: I28b4ac5f612de75918973148865cf82f7a7de5e8
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 5fec7b062689ef2e394943194875767df77ece66
- Merge "Add missing [mysqld] group"
- Add missing [mysqld] group
Issue-ID: VID-725
Change-Id: I00bed189eae8a615f4db9531814a88ed2b000362
Signed-off-by: Brian Freeman <bf1936@att.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to cd4bc8e4282d82b91fa930567682eb5e0f0290a8
- Merge "Add cert dist for DMaaP BC"
- Add cert dist for DMaaP BC
Issue-ID: DMAAP-1321
Signed-off-by: Ubuntu <dgl@research.att.com>
Change-Id: I55a6d41c1955d3ea1bcc0799b5121212af102471
|
|
* Update docs/submodules/oom.git from branch 'master'
to 6803a3e1883d627eb72a14c4a51f6cee1aaf5656
- Merge "[CLAMP] Use global storage templates for PVC"
- [CLAMP] 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
Change-Id: I2cc90fe7a22a04d47d406b854c3a75502e539a25
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 9d390192fce4824a1b393ab4252ba95307c10a2b
- Merge "[Modeling] Use global storage templates for PVC"
- [Modeling] 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
Change-Id: I337e760ea71ec57c4f593e068c3cf6ea548a3cfc
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 37c368332d64933817d24a0521a2a109160b446b
- Merge "[DCAE] Use global storage templates for PVC"
- [DCAE] 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
I've also used a "range" for PV creation of redis in order to have only
the needed number.
Change-Id: I6bb326f8aaece11bcf503e9300e5c39a87214f81
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 289bd43809204ca8e4c0662b06c1c775e6333d8c
- Merge "[Multicloud] Use global storage templates for PVC"
- [Multicloud] 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
Change-Id: I8ed04b153aec0b81971a7a1eb97737d905ea4c5c
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 408d8af2ab72c4697a95176b50443837b5f8fc40
- Merge "[VFC] Use global storage templates for PVC"
- [VFC] 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
Change-Id: Ibc8825b97cbe8939cf085d1cdd17e0a67e45c96b
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to d7c871ee5e465c11f36974cfb668844882d139d2
- Merge "[PNDA] Use global storage templates for PVC"
- [PNDA] 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
I've also created a PVC for the job instead of doing a PVC template
inside the job.
Change-Id: I0cc242db0b1412ac792dec74a6542849c30985c9
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to ef7963b2f0a8b5b4d4e0840435dcbdbf98fccb0d
- Merge "[SO] Use global storage templates for PVC"
- [SO] 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
Change-Id: Ice44eda13aad44564d61f9e954cd11085a81d56f
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 95b77050a816e1ea505c11d5082a1dfc3511ee7d
- Merge "[LOG] Use global storage templates for PVC"
- [LOG] 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
Change-Id: I1f39f2c8c9a2d4fe1303fffbefe4dac70ed0e860
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 7be20b6c241f25b9845b448f1d65d97705634380
- Merge "[POLICY] Use global storage templates for PVC"
- [POLICY] 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
Change-Id: Iabd5d12196459bb1fce9021857aeab57a757ee12
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 16b32ddfe9237ffeed3dc9f1422978ca65995e4b
- Merge "[SDC] Use global storage templates for PVC"
- [SDC] 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
Change-Id: Ic34dcbc609edaa79109aacb83bbc019b55e6d02e
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 1f20e128c5ffe2d7996a33bb2a3d61fa923493cd
- Merge "Add ingress configuration for vid"
- Add ingress configuration for vid
Add ingress configuration file for vid component.
Ingress configuration can be changed in onap-all.yaml
Change-Id: Icb1eccccd0488d78a8b44745888203192d9aaa4b
Issue-ID: OOM-1508
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to b500d833613a478a1c9d8ac36a665e25f3ec5ef0
- Merge "Add ingress controller support to portal"
- Add ingress controller support to portal
Add ingress controller support to portal
using default ingress template.
Issue-ID: OOM-2185
Change-Id: I99f230d95a396f159559ee1c1e3bb01d6c8a9ff0
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 4d31247da5a8202f89db9761cae62cbb2c66a585
- Merge "Add ingress controller support to AAF"
- Add ingress controller support to AAF
Change-Id: Ie69b9dac533ed2af80645e6d65318b6b4e81cbd3
Issue-ID: OOM-2170
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 9368b1aa2fd9e8bff7f3f87ef8ddb0a4f67ee1ce
- Merge "Add ingress controler support to UUI"
- Add ingress controler support to UUI
Add ingress controler support to UUI
using ingress common template
Issue-ID: OOM-2190
Change-Id: I02a94788ace71c27464a2606aa3ecf2b11b1b1da
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 7550721979daa2d29888c9ee73b125829f3f1c32
- Merge changes I69ea7e5d,I75f7e823,I2ae6b0f2,I6f1591a6,I30c2e0de, ...
* changes:
Add ingress controler support to OOF
Add ingress controler support to POMBA
Add ingress controler support to SDC
Add ingress controler support to DMAAP
Add ingress controler support to SDNC
Add ingress controler support to CDS
- Add ingress controler support to OOF
Issue-ID: OOM-2182
Change-Id: I69ea7e5dbc30981ec840373dc030f26696ed32db
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
- Add ingress controler support to POMBA
Issue-ID: OOM-2184
Change-Id: I75f7e8239fe1f1027fffae6b3e2a848a593351ae
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
- Add ingress controler support to SDC
Issue-ID: OOM-2187
Change-Id: I2ae6b0f2482641b3f482121354596574b684b2d1
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
- Add ingress controler support to DMAAP
Issue-ID: OOM-2179
Change-Id: I6f1591a6c7033812cc714d75c63d7c1b3ba197b6
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
- Add ingress controler support to SDNC
Issue-ID: OOM-2188
Change-Id: I30c2e0dea0a1fc12fd82090610c7e38f577cc811
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
- Add ingress controler support to CDS
Issue-ID: OOM-2174
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: Ib6c159d54ca65577934f70de137bfc13336992ec
|
|
* Update docs/submodules/oom.git from branch 'master'
to 7be16fd934e32b8181b851b9e6a0596ff284e086
- Update git submodules
* Update kubernetes/aai from branch 'master'
to 552da2c65b6af3f6328fcc6b11af9329d5efa30a
- Update the janusgraph properties for cassandra 3
Issue-ID: AAI-2731
Change-Id: Ic64ba3c97374db4f9ef0961b1e910714db49b4ae
Signed-off-by: Harish Venkata Kajur <vk250x@att.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 996a45bfdad429f82eac3d48ea7a4fd011f9295e
- Update git submodules
* Update kubernetes/aai from branch 'master'
to 6e20d0fb3f4dacda0c6cbccc7cf0424a21432fcf
- Remove old microservices from aai chart
Issue-ID: AAI-2733
Signed-off-by: Jimmy Forsyth <jf2512@att.com>
Change-Id: Ib471d6c3e8aca7a06f18dfd6167131f1d1df0456
|
|
* Update docs/submodules/oom.git from branch 'master'
to 4738758dfc10aa85dbb611d76dca723828ec523f
- Merge "OOM missing CDS BP app properties for HealthCheck."
- OOM missing CDS BP app properties for HealthCheck.
Issue-ID: CCSDK-1952
Patch1: added missing properties from Change-Id: Idb3c7f67b3f22bd6069f75c193ae458c346fb2ac
Patch2: added missing vault mapping.
Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com>
Change-Id: I218f31cebe1f3fd24b1aead3fa93efb141465d23
|
|
* Update docs/submodules/oom.git from branch 'master'
to 72c71c0b832a169c03bcdbaa5997956e30f62c7c
- Update git submodules
* Update kubernetes/aai from branch 'master'
to 18747ec29947084c571d66f37f1a0fe85fbe4702
- 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
I've also created a PV/PVC for elasticsearch has it was hardcoded to
hostPath.
I've also removed hostPath for job logs (aai-traversal logs were not put
into the desired hostPath)
And I moved the 3 jobs of aai-graphadmin into 3 files as it's a better
practice (several object in the same file can lead to unexpected
behavior).
Behavior is supposed to be exactly the same as before.
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I71c6cee8d7c33ef7bd39c40a43c26b377d4ceec3
|
|
* Update docs/submodules/oom.git from branch 'master'
to 9f713a2f32b1adffcfe7f454904217be212b9dc0
- Merge "Update prh to 1.3.2"
- Update prh to 1.3.2
Issue-ID: INT-1181
Signed-off-by: Joanna Jeremicz <joanna.jeremicz@nokia.com>
Change-Id: I13888ca2334cfb1f59bbcf195726996cd8a79e54
|
|
* Update docs/submodules/oom.git from branch 'master'
to 3535b96cf6c7aa17c4663fce9e070f14c219d4a9
- Merge changes I3a419138,Id4c67943,I9767e8ff,I15359ebc,I131e8153
* changes:
Add ingress controler support to MSB
Add ingress controler support to DCAE
Add ingress controler support to VNFSDK
Add ingress controler support to CLAMP
Add ingress controler support to CLI
- Add ingress controler support to MSB
Issue-ID: OOM-2181
Change-Id: I3a419138e4e553719f7f9f9b958d448f6c5cea24
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
- Add ingress controler support to DCAE
Issue-ID: OOM-2178
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: Id4c679431d5d5e0362acbd08757250f1bb5a0616
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
- Add ingress controler support to VNFSDK
Issue-ID: OOM-2192
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: I9767e8ffaa27c68ecdb3a8882d4f718af1488ab0
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
- Add ingress controler support to CLAMP
Issue-ID: OOM-2175
Change-Id: I15359ebc3116bf453c2a2b3ce706ead6024797bf
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
- Add ingress controler support to CLI
Issue-ID: OOM-2176
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: I131e8153024f18ff5a08fa29966ed9be8c850946
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to ac242707c66ff4d6c83e1258a6f9402d2b8fa838
- Add ingress controler support to Consul
Issue-ID: OOM-2177
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: Icf30714776cb038f10377c16d40585280910f9d7
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to d6322c8e3038291b8a4029d10b0bf2de93c13cc6
- Add ingress controler support to LOG
Issue-ID: OOM-2180
Change-Id: I18a2f724216a3946a40e0c4f166a3a4eeeca522b
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
* Update docs/submodules/oom.git from branch 'master'
to 672e49683b77bfbc8bc1cbc14c9180a4575eedc7
- Merge "Vhosts support to the common ingress template"
- Vhosts support to the common ingress template
Add virtual hosting support to the ingress
common template
Added support for global configuration path
or virtual host based
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: I6b1a0c9cfd0eb5c90a090058d5db70f8ee33731e
Issue-ID: OOM-2125
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|