Age | Commit message (Collapse) | Author | Files | Lines |
|
Keep HTTP port reachable from inside the server.
Issue-ID: OJSI-101
Change-Id: I0468697d8f3d0192a5d8e102501db0d14633fa86
Signed-off-by: gummar <raj.gumma@est.tech>
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: OOM-2051
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: Ieb4027d738041e1bd8d8238b74c3615dce2971eb
|
|
Issue-ID: PORTAL-848
Change-Id: Ica17e60ec7497cf6d310a664c2e414455f8d1ef4
Signed-off-by: statta <statta@research.att.com>
|
|
|
|
integrate portal-sdk with AAF agent init container.
add pv to store init-container certs generated at startup.
add aafEnabled flag to switch on/off aaf integration.
modify tomcat startup to load p12 and enable HTTPS based on flag.
Issue-ID: PORTAL-261
Signed-off-by: ChrisC <christophe.closset@intl.att.com>
Change-Id: Ia2b05b8661bf9e0c03a60467212e80d1c9d02bac
|
|
Issue-ID: PORTAL-796
Change-Id: I41f761e0a90e6cb75e588338b09208f899f3fb58
Signed-off-by: statta <statta@research.att.com>
|
|
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
|
|
|
|
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>
|
|
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>
|
|
|
|
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
Moved portal-widget CPU limit to 1 as it's not starting if set to lower
than that.
Full values are available on jira ticket
(https://jira.onap.org/browse/PORTAL-517).
Change-Id: Ic02fef386e05351a6fa9e47bf47d5c2046f490e3
Issue-ID: PORTAL-517
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Signed-off-by: Lorraine Welch <lb2391@att.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>
|
|
|
|
Proper configuration for HTTPS in the sdc:
-configured the livenessProbe/readinessProbe ports
-changed mount path for dcea-be components
-updated dcea component images
-updated VID and Portal to talk with the SDC
Change-Id: Ibdece8f095aaa79e326cb9c4510e8227a7856b15
Issue-ID: SDC-2548
Signed-off-by: Krystian Kedron <k.kedron@partner.samsung.com>
|
|
Issue-ID: PORTAL-727
Signed-off-by: Welch, Lorraine (lb2391) <lb2391@att.com>
Change-Id: Ic9041f4a0263c7ab6d36176708323dd47c89bf7d
Signed-off-by: Welch, Lorraine (lb2391) <lb2391@att.com>
|
|
Issue-ID: PORTAL-723
Change-Id: I78e7badc9b0c02407bc9d4bbdfb1b0019f54b07a
Signed-off-by: statta <statta@research.att.com>
|
|
|
|
Issue-ID: PORTAL-709
Signed-off-by: Welch, Lorraine (lb2391) <lb2391@att.com>
Change-Id: I70c35ebcaf76fa157da777c28cca6513a22c4465
|
|
Today when deploying Portal 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).
Portal PVC are only used by a mariadb instance or a cassandra instance.
Thus we don't need RWX.
Change-Id: I706e13759d3af829d61d7a33d068263aaf9e9158
Issue-ID: PORTAL-724
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: PORTAL-333
Change-Id: I3f2e88487fdb80ff7b0f1c4a0ebbbd2ccf2a49d4
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
Issue-ID: PORTAL-333
Change-Id: I59a6730cff06c2849864f6f208e971cef2c2e846
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
Issue-ID: PORTAL-579,PORTAL-597
Change-Id: Id945204a400a7b8a6a81fcc1aa44f4b094551d4c
Signed-off-by: statta <statta@research.att.com>
|
|
Issue-ID: PORTAL-596
Signed-off-by: Welch, Lorraine (lb2391) <lb2391@att.com>
Change-Id: I65987549c9353d6a4d072a1ee7cae15a25a3675d
|
|
Issue-ID: PORTAL-467
Signed-off-by: Welch, Lorraine (lb2391) <lb2391@att.com>
Change-Id: Ifddeb4861e3fefd9a6f5462c814ae17bd5477cef
|
|
Issue-ID: PORTAL-557
Change-Id: I22fddb494512fb6fb0a70742d2abdf30e5dad1c8
Signed-off-by: statta <statta@research.att.com>
|
|
Issue-ID: PORTAL-557
Change-Id: I48ac30eefc285ef4ff12dee24af85dced366d52e
Signed-off-by: statta <statta@research.att.com>
|
|
Issue-ID: PORTAL-554
Change-Id: I9467a2e08a8de6bc87756f0c543a77c25c56d86f
Signed-off-by: statta <statta@research.att.com>
|
|
Issue-ID: PORTAL-549
Change-Id: I4b41aed37e823a751aaff529036ae9a3ea0dc737
Signed-off-by: statta <statta@research.att.com>
|
|
Add support to make sure of the schema ms
add support to make use of aaf interaction
update portal props with correct Impl class
add the missing portal property configurations
Issue-ID: AAI-2201
Change-Id: Ic47d62922b1aecaf99f06a50aec10ca674c8b927
Signed-off-by: renealr <reneal.rogers@amdocs.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: PORTAL-399
Change-Id: I7fd4fbbb0707e0b00d652eca812f4079a3f10a59
Signed-off-by: st782s <statta@research.att.com>
|
|
|
|
Issue-ID: AAI-1992
Change-Id: I5391106ff6a08093699d497dd8326905eae20bfa
Signed-off-by: Arul.Nambi <arul.nambi@amdocs.com>
|
|
Change-Id: Ib562b520a10e47662e516314fe6653f38802bbd0
Issue-ID: OOM-1546
Signed-off-by: Eoin Hanan <eoin.hanan@ericsson.com>
|
|
|
|
Change-Id: I75ea788f47598aa07ecb6550b5db7e9e4fdc1d36
Issue-ID: OOM-1533
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
Change-Id: I1130c48d54baa3c388745f8582b6ef952a06e5e3
Issue-ID: OOM-1519
Signed-off-by: Eoin Hanan <eoin.hanan@ericsson.com>
|
|
Sync docker tags with the release manifest from integration
repo commit 1e16c7e67d1fdeadab3789b07d6d2f47b7d0ffd7.
Change-Id: If580d0000108ce9ff70ad128b9bc93bf4364376b
Issue-ID: INT-663
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Issue-ID: PORTAL-466
Change-Id: I8ae36d7117acba3013e25b657260ea2368429321
Signed-off-by: Welch, Lorraine (lb2391) <lb2391@att.com>
|
|
Issue-ID: OOM-1425
Change-Id: I5ced234211fc2a1beacfcaae639cf6fced210ca1
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Issue-ID: PORTAL-457
Change-Id: I77e3585683b4cda9483a9de88a390caf8bfad4b6
Signed-off-by: st782s <statta@research.att.com>
|
|
If you try and change the service type from a nodeport
to a cluster IP things break. We never really exercise
this code path in testing but if you want to experiment
with a totally internal network environment you need to be
able to turn off node ports.
Issue-ID: OOM-1475
Change-Id: I1a0f4b0a4c390f3353e1611b6002b93e54bb5044
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Issue-ID: PORTAL-454
Change-Id: I3c5cb0e4d0bde01ed557098432dabd36d1843fac
Signed-off-by: statta <statta@research.att.com>
|
|
Change-Id: Ie83c1c07c110af14c9b9af30d4e663b26683a456
Issue-ID: MSB-293
Signed-off-by: Huabing Zhao <zhaohuabing@gmail.com>
|
|
Sync docker tags with the release manifest. It is
assumed that the release manifest is the
"single source of truth" and that the versions in
the helm charts are out of date.
Change-Id: I2902e60b25f57409dd616780a626e63c92d26769
Issue-ID: INT-663
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Issue-ID: PORTAL-429
Change-Id: Id8b790b612ff928634b5faaaa7ead16dc5f46aa6
Signed-off-by: statta <statta@research.att.com>
|