Age | Commit message (Collapse) | Author | Files | Lines |
|
Instead of statefulset + inner work in the container, use deployments in
order to be more reliable
Change-Id: Icf4fe1303ae3489c822558e28bb08b69af2d4970
Issue-ID: OOM-2234
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 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>
|
|
|
|
|
|
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>
|
|
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
|
|
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>
|
|
I've adjusted the Requests / Limits of portal pods according to real
usage of "Orange Openlab" and "Onap daily master".
Calculation is the following:
per deployment:
* CPU/Mem requests is max of average from the two deployments
* CPU/Mem limits is (max of max from the two deployments) * 1.2
Change-Id: I3fce54e6be495a7014bf346d66721976fa2dab8b
Issue-ID: MUSIC-533
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
|
|
Missing apiVersion causes linting failure and therefore make common
fails
Issue-ID: OOM-2156
Signed-off-by: Tomáš Levora <t.levora@partner.samsung.com>
Change-Id: Idb0aeb998fc99cc8e409247c6b5e20d140297a3e
|
|
Used PVC(s) are actually created in the statefulset
Change-Id: I24f2c3ff0934178c9af06bfee60b4b6e35cfe953
Issue-ID: OOM-2155
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: OOM-2059
Signed-off-by: Akansha Dua <akansha.dua@amdocs.com>
Change-Id: I9b8db6ff689c0928ac497b523290e586c0f6f1f8
|
|
Update dgbuilder to use latest release (0.6.3) with https support and
update configuration to enable https
Change-Id: Ia04a3cde6b0f18655301e25dcf125ffcdf1ec120
Issue-ID: OJSI-100
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
Update CCSDK version to RCO (0.6.3) and update SDNC
version to RC0 (1.7.3)
Change-Id: I4af5684ecacd2cf8134a4db51684fb95b488d536
Issue-ID: SDNC-917
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
Update versions of CCSDK and SDNC dockers to 0.6.2 / 1.7.2
Change-Id: Ib8294b292122c924fcbe29a02806dffd5ce935ec
Issue-ID: SDNC-905
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
|
|
Issue-ID: OOM-2089
Signed-off-by: Akansha Dua <akansha.dua@amdocs.com>
Change-Id: Ia1086deda37ba6e613afcc6bd064e7bf4ee692b9
|
|
Issue-ID: OOM-2088
Signed-off-by: Akansha Dua <akansha.dua@amdocs.com>
Change-Id: Ie7f25c812984abc8631a86b2385dd14a365a8ea5
|
|
|
|
|
|
|
|
Update SDNC helm charts to use Neon-based El Alto images
Change-Id: If91320bc663992355f665b3f57f77214e96985cd
Issue-ID: SDNC-874
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
Mariadb PVC are created in 1 to 1 mapping with galera replicas thus we
don't need RWX.
Change-Id: I438855b2d4b2f90932387e056c168b0a995975a5
Issue-ID: OOM-2081
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Today when deploying NBI with OOM, the PersistentVolumeClaim needs the
"ReadWriteMany" (or "RWX") capability.
According to Kubernetes Documentation (https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes),
ReadWriteMany stands for "the volume can be mounted as read-write by many nodes".
That means that a particular PVC needs to be read and written from many pods.
That also means that your code takes that into account and do the work to avoid
write at the same place at the same time.
An issue on RWX mode is that most "official" storage driver from Kubernetes doesn't
support it (13 over the 19 drivers doesn't support it, espacially OpenStack, Amazon
and Google storage classes).
MongoDb PVC is used only for one Mongo instance and it's the same for
maria. Thus we don't need RWX
Change-Id: I4d54cd7853778d8ba6c83551a211abe34d383382
Issue-ID: EXTAPI-305
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: OOM-2050
Signed-off-by: Ondřej Šmalec <o.smalec@partner.samsung.com>
Change-Id: I7d54c4c8adc192d0c27249dde2fad4af2ed0a52a
|
|
|
|
|
|
Fix inproper backend section identation in the
common ingress config template
Change-Id: I04c4eebc408a04aba0679ff5123e1a8503ffd912
Issue-ID: OOM-1508
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
Add ingress common template, template can be
included in a components ingress configuration.
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: Ic18626ca679c8cbc6ce7aee95ac4b9c40dc5bcfe
Issue-ID: OOM-1508
|
|
Update SDNC image versions for El Alto early drop (1.6.1 for SDNC, 0.5.1
for CCSDK)
Change-Id: I48bb223116b4064b7f90847d90bd0453d311b09c
Issue-ID: SDNC-827
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.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
|
|
Disabling cassandra livenessProbe causes the
charts generated yaml to append readinessProbe
after containerPort because of go ‘-‘ command.
Issue-ID: OOM-1922
Signed-off-by: Joey Sullivan <joey.sullivan@amdocs.com>
Change-Id: If19c8639d1a5c0968b7156e39945a3ca15dd18b5
|
|
Update SDNC and CCSDK versions to reflect latest CCSDK/SDNC docker versions
Change-Id: I325a999a77e8e4e9ff7ba3ddbd99b5dc91c46695
Issue-ID: SDNC-793
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
Etcd pod fails to start with file not found error.
The error is being caused because the pod is stuck
in an infinite loop as the readiness probe is not true.
Since, we are anyway checking the pod status, we removed
the readiness probe as it is not needed.
Bumped up version of etcd to 3.2.24
This fixes a known issue:
https://github.com/etcd-io/etcd/pull/4861
Issue-ID: MULTICLOUD-660
Change-Id: I815766b4a8f187d88bb2fcdb71e9d6e24b277d25
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Add quotes around value. Seems that its
expecting a string input.
Issue-ID: MUSIC-403
Signed-off-by: Nelson, Thomas (tn1381) <tn1381@att.com>
Change-Id: I45d318072f76066bf995f1d973cbbdba5fe53f7e
Signed-off-by: Nelson, Thomas (tn1381) <tn1381@att.com>
|
|
Increased readiness time for common cassandra and sdc-cassandra
due to installation failures
Change-Id: I4c7f6f5db5ddeebb1d3bde50a24e848be75ba867
Issue-ID: SDC-2319
Signed-off-by: Tomasz Golabek <tomasz.golabek@nokia.com>
|
|
Update to use latest CCSDK and SDNC releases (0.4.3 and 1.5.2,
respectively).
Change-Id: I1412f5b3744a37db87b498650d06889fb90e2d0f
Issue-ID: CCSDK-1362
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
Issue-ID: VFC-1392
Change-Id: I8b4a97dbac6245c7747a31fdc557ffd8d9a974d5
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
|
|
The chart uses servicename in statefulset.yaml.
This should be fullname instead.
Issue-ID: MULTICLOUD-636
Change-Id: I0e523a5c0e2e2c432f3a159fcb8c9ddcd2240e68
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Based on the helm chart in github helm repo
https://github.com/helm/charts/tree/master/incubator/etcd
etcd required as datastore by k8s Plugin in
multi-cloud project.
Change-Id: Ie6c7d9fc394f2a08cd9d34dda6261da13ef005f3
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
Issue-ID: OOM-1828
|
|
|
|
|
|
Change-Id: I337aaf258b1a3716d97e31ea3f53014738f3db55
Issue-ID: OOM-1835
Signed-off-by: mahendrr <mahendra.raghuwanshi@amdocs.com>
|
|
Update helm charts to use released version of CDS and SDNC artifacts.
Change-Id: If7c537bb1ce8d991244bd2cfa536a95f8c377107
Issue-ID: SDNC-740
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
Issue-ID: OOM-1834
this image has newer JDK version, which is not affected by JDK7 issue resolving long hostnames.
Change-Id: Ibc94a7b88a24c2e83721e4ee1bab03550b65ffde
Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com>
|
|
Change-Id: I0ae425343937389ff2f9bfd41701402398a63a82
Issue-ID: OOM-1832
Signed-off-by: mahendrr <mahendra.raghuwanshi@amdocs.com>
|
|
Change-Id: Ifa98f8610b0a96a28f3a3ded7cb65663e9455158
Issue-ID: INT-1042
Signed-off-by: Yang Xu <yang.xu3@huawei.com>
|