Age | Commit message (Collapse) | Author | Files | Lines |
|
ONAP is too big to be deployed using helm install so we need to
use a custom helm plugin helm deploy. This script deloys onap
component by component instead of deploying evrything at
once. Unfortunately this script also modifies the helm release by
appending component name to it.
As a result of this behavior our objects are called for example:
onap-mariadb-galera-mariadb-galera-0
instead of just being called onap-mariadb-galera-0.
This patch simplifies this naming convention by replacing all direct
usages of .Release.Name with common.release macro which strips the
component specific part from the release name.
Issue-ID: OOM-2275
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: Ia8cead50d305adb00eef666d0a1ace74479b5183
|
|
https://gerrit.onap.org/r/c/oom/+/98938 forgot to remove selectors for
PVC and prevent it to work with storage class.
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ieb45ecbe8c046d6c3bc72e47776df3c9d64de2e5
|
|
|
|
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>
|
|
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>
|
|
Updating all helm chart versions to 5.0.0 for the El Alto release.
Merge will be co-ordinated with the merge of a separate aai/oom patch.
Please do not merge until this coordination has completed.
Issue-ID: OOM-1980
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
Change-Id: I31daaebeacea33565f13affd2fa28fb15fe948ba
|
|
Issue-ID: AAF-826
Change-Id: Ia8c23170ccaaa52c528d89417d95ddb3478ab00d
Signed-off-by: Instrumental <jonathan.gathman@att.com>
|
|
Also upped SMS/SSHSM versions
Issue-ID: AAF-823
Change-Id: I27de5079cd678d0206238873b81cb55b5612a67a
Signed-off-by: Gathman, Jonathan (jg1555) <jg1555@us.att.com>
|
|
All charts are being bumped from 3.0.0 to 4.0.0 for the Dublin release.
In addition the requirement.yaml files have been updated to allow for
chart versions that include timestamp suffix. A following on patch will
take care of changes to the OOM Makefiles to support injection of the
timestamp versions.
Change-Id: Ie03d86fad2027e975e8b9106e3a828e4335037cb
Issue-ID: OOM-1642
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Issue-ID: OOM-1563
Change-Id: I383dbec29291ba5b13d613f60d8eb343b9c59dda
Signed-off-by: dkamdocs <devesh.kumar@amdocs.com>
|
|
Sync docker tags with the release manifest from integration
repo commit 90e136c83ec5434abaeb9939b995f86aa4089850.
Change-Id: I771393adb429087752dc52df2cd2812dc9ff6a11
Issue-ID: INT-663
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Add charts that support hardware security in AAF
This includes two sub charts, abrmd and distcenter
By default tpm requirement is disabled via the global.tpm flag.
Issue-ID: AAF-409
Change-Id: Ia3f5948891638bc281ad4585818274fc71564bdd
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|