summaryrefslogtreecommitdiffstats
path: root/docs/submodules/oom.git
AgeCommit message (Collapse)AuthorFilesLines
2019-12-11Update git submodulesDaniel Rose1-0/+0
* 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
2019-12-11Update git submodulesDaniel Rose1-0/+0
* 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>
2019-12-11Update git submodulesBrian Freeman1-0/+0
* 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>
2019-12-11Update git submodulesHarish Venkata Kajur1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesBorislav Glozman1-0/+0
* 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>
2019-12-11Update git submodulesSylvain Desbureaux1-0/+0
* 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>
2019-12-11Update git submodulesSylvain Desbureaux1-0/+0
* 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>
2019-12-11Update git submodulesSylvain Desbureaux1-0/+0
* 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>
2019-12-11Update git submodulesSylvain Desbureaux1-0/+0
* 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>
2019-12-11Update git submodulesSylvain Desbureaux1-0/+0
* 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
2019-12-10Update git submodulesHarish Venkata Kajur1-0/+0
* 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>
2019-12-10Update git submodulesJimmy Forsyth1-0/+0
* 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
2019-12-10Update git submodulesSylvain Desbureaux1-0/+0
* 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
2019-12-06Update git submodulesSylvain Desbureaux1-0/+0
* 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
2019-12-06Update git submodulesSylvain Desbureaux1-0/+0
* 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
2019-12-06Update git submodulesSylvain Desbureaux1-0/+0
* 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>
2019-12-06Update git submodulesLucjan Bryndza1-0/+0
* 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>
2019-12-06Update git submodulesLucjan Bryndza1-0/+0
* 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>
2019-12-06Update git submodulesSylvain Desbureaux1-0/+0
* 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>
2019-12-06Update git submodulesSylvain Desbureaux1-0/+0
* Update docs/submodules/oom.git from branch 'master' to cf7df6be28306495b412a34168a8195db7c0608c - Merge "Nginx ingress controller configuration" - Nginx ingress controller configuration Add Nginx ingress postinstall helm chart. It should be applied after cluster initial setup. Issue-ID: OOM-2099 Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com> Change-Id: Ic942b03d6e754c2fca72316cde0d2e65eba9d0d7
2019-12-04Update git submodulesMike Elliott1-0/+0
* Update docs/submodules/oom.git from branch 'master' to e21978408ab1bee4c571bbb6cc58904d3ee36472 - Merge "Add password generation template" - Add password generation template Currently there is a number of hardcoded passwords in OOM helm charts that are reused for almost all ONAP deployments in different labs. One possible solution for this issue could be to generate a random password for every deployment but this may cause number of issues while doing helm upgrade. That's why instead of generating a random password we generate a password for particular use case, based on chart name, master password provided by the deployer and additional UID. This is done using derivePassword function so check its documentation for more details how this password is derived. From a user perspective, the most important fact is that he or she can achieve reproductible deployment. Every time when ONAP is deployed with the same masterPassword all derived passwords are going to be also the same. Issue-ID: OOM-2052 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I666d597e6daab8b79e630917ad75f17cc70f897b
2019-12-04Update git submodulesMike Elliott1-0/+0
* Update docs/submodules/oom.git from branch 'master' to b16e8fe5947741d6c6c7f3458a87a6efa6a22859 - Merge "[NBI] Use the common galera cluster of ONAP" - [NBI] Use the common galera cluster of ONAP Instead of having our "own" galera cluster, use the common one already proposed by OOM. If a local cluster is needed, you just need to set global.mariadbGalera.localCluster to True. Also create a common chart that create the needed values for the database. Change-Id: I9ad551b76a40732b4ab3fc34ba7cde6ca90fe432 Issue-ID: EXTAPI-348 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-12-03Update git submodulesTimoney, Dan (dt5972)1-0/+0
* Update docs/submodules/oom.git from branch 'master' to 6c1984839109f1dea6514998018f7c10f1dae764 - Update SDNC helm charts to use latest stable version 1.7.6 Update SDNC helm charts to use latest stable version (1.7.6) Change-Id: I98a360cd16e14d8da914278da2509e2c07c2cf5c Issue-ID: SDNC-992 Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
2019-12-01Update git submodulesBorislav Glozman1-0/+0
* Update docs/submodules/oom.git from branch 'master' to 41041fce7009965f5a0da872d5efa4ab1c937f38 - Merge "Typo fix for cds-ui chart." - Typo fix for cds-ui chart. Issue-ID: CCSDK-1953 Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com> Change-Id: Id2ce253ab0ecee2c2fccb18589e76160fbf10853
2019-11-27Update git submodulesBorislav Glozman1-0/+0
* Update docs/submodules/oom.git from branch 'master' to 9b0adea0769b026875ee312d223960c559c700bb - Merge "Create templates for global storage use" - Create templates for global storage use Two helper functions are defined: - common.storageClass: will print the right storage class according to properties set or not: * if no storage class set --> use previous behavior (storage class named `common.fullname-data`. * if a "persistence.storageClassOverride" is set for this specific chart, we use it (if it's "-", we set to default one) * if a "global.persistence.storageClass" has been set (and no storageClassOverride for this chart), we use it (same specificity than storageClassOverride) * if a "persistence.storageClass) has been set (and no storageClassOverride nor global one), we use it (same specificity than storageClassOverride) - common.needPV: will print "True" if we need a PV (no storageClass and storageClassOverride being set). an implementation example with mariadb-galera is provided. Issue-ID: OOM-1500 Change-Id: I20a667e17b00c255c4b828e3c66f9c0df7c8755c Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-11-27Update git submodulesBorislav Glozman1-0/+0
* Update docs/submodules/oom.git from branch 'master' to a362d9ba0fd2ece5cd39d4b43ae92ea88486db35 - Merge "[Policy] Use common mariadb galera chart" - [Policy] Use common mariadb galera chart Instead of using "own" galera chart, reuse chart placed in common part of OOM installation. Will ease move to common galera cluster (which is not done by this commit). Change-Id: I2d7c1e5cdc9289cfb55e288b1697373239ef96e3 Issue-ID: POLICY-1467 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-11-27Update git submodulesDaniel Rose1-0/+0
* Update docs/submodules/oom.git from branch 'master' to d13409e21b17ec8e01d9176f0399c58f14e528bb - Update git submodules * Update kubernetes/robot from branch 'master' to 6e38b492acd3ec44a869055092399b6f18c659b8 - Merge "Add Inventory and Deployment Global property needed for Bulkpm" - Add Inventory and Deployment Global property needed for Bulkpm Change-Id: I9839bc2937446f4062ae922f7d287b1150a1b224 Issue-ID: INT-1375 Signed-off-by: rajendrajaiswal <rajendra.jaiswal@ericsson.com>
2019-11-27Update git submodulesSylvain Desbureaux1-0/+0
* Update docs/submodules/oom.git from branch 'master' to 52c30fbd77243de5428d2e46203569dd69bc02d2 - Merge "Docker changes for dmaap microservice" - Docker changes for dmaap microservice -Add script to start dmaap microservice. -Add new properties -Renaming the DCAE.dmaap properties so that all of the properties share the same prefix (DCAE.dmaap.event) instead of some having a different prefix (DCAE.dmaap.appc). This is required since all dmaap properties are now being read by the a common java class. Change-Id: I66b7cb466ec03f3357ecc473748a54a3a090ef16 Signed-off-by: Patrick Brady <patrick.brady@att.com> Issue-ID: APPC-1744