Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* 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
|
|
* 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: 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
|
|
|
|
* 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
|
|
Issue-ID: OOM-2181
Change-Id: I3a419138e4e553719f7f9f9b958d448f6c5cea24
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
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>
|
|
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>
|
|
Issue-ID: OOM-2180
Change-Id: I18a2f724216a3946a40e0c4f166a3a4eeeca522b
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
|
|
|
|
Issue-ID: INT-1181
Signed-off-by: Joanna Jeremicz <joanna.jeremicz@nokia.com>
Change-Id: I13888ca2334cfb1f59bbcf195726996cd8a79e54
|
|
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>
|
|
|
|
|
|
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>
|
|
Issue-ID: OOM-2175
Change-Id: I15359ebc3116bf453c2a2b3ce706ead6024797bf
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
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>
|
|
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 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>
|
|
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>
|
|
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>
|