Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Issue-ID: CCSDK-1669
Signed-off-by: ShaabanEltanany <shaaban.eltanany.ext@orange.com>
Change-Id: Id7343225f8c46c38d3c44c6c9ffdfe895742e5d6
|
|
|
|
|
|
|
|
|
|
* 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
|
|
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 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 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
|
|
|
|
Issue-ID: DMAAP-1321
Signed-off-by: Ubuntu <dgl@research.att.com>
Change-Id: I55a6d41c1955d3ea1bcc0799b5121212af102471
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Issue-ID: VID-725
Change-Id: I00bed189eae8a615f4db9531814a88ed2b000362
Signed-off-by: Brian Freeman <bf1936@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
Change-Id: Ice44eda13aad44564d61f9e954cd11085a81d56f
Issue-ID: OOM-1227
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
Change-Id: I2cc90fe7a22a04d47d406b854c3a75502e539a25
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
* 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
|