Age | Commit message (Collapse) | Author | Files | Lines |
|
Cleaned up up configs, JDK11 fixes, Hello and Agent works, now a model for Apps
non-root fix
Issue-ID: AAF-1081, AAF-1102
Signed-off-by: Instrumental <jgonap@stl.gathman.org>
Signed-off-by: ChrisC <christophe.closset@intl.att.com>
Change-Id: I4947075029db8abd7d2072b6b82064af8e2daa3e
|
|
SMS requests/limits were set too low and thus it prevents start when on
small flavors
Issue-ID: AAF-1105
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ib591c972ceaa4186dd16ca5cebd86b58c0288718
|
|
aaf-locate anf aaf-cm limits may have been a bit too stringent.
giving some space to these components
Issue-ID: OOM-2230
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Id295f3e42bd7220144e5990322e9e6043e087e0e
|
|
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>
|
|
SMS healthcheck breaks because of expired certificates
This patch fixes that issue.
Issue-ID: AAF-845
Change-Id: I2004e29e3271a829989e1f46ebcd7e07e1b6185a
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
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>
|
|
Nodeport exposes aaf-sms outside the cluster
which is a security risk without the proper
authentication systems in place.
We will add external access if needed in the
future.
Issue-ID: OOM-1739
Change-Id: Ibefbd1c5656262131f00a2e53dbf5804f2ead084
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Update SMS version to 3.0.1 to reflect latest image
Issue-ID: AAF-390
Change-Id: Ie4b6c45bf2dc3e8352810809b2c88523240b6d43
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.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>
|
|
cleaning up merge conflict
implementing template
reducing overly large resource limits
adding limits to aaf-sms.
Issue-ID: OOM-1146
Change-Id: Idac679dc9be94ab92ea95c38f9f237af65307131
Signed-off-by: dsingh.278 <dsingh.278@gmail.com>
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Change-Id: Ic8f11dc20c425aab144fe28a5e761552eb7b025b
Issue-ID: OOM-1422
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Using an initContainer and to start SMS only after
vault and consul have already started. This prevents
restarts of the sms container.
Issue-ID: AAF-421
Change-Id: Ied3264711d5d931a1d18523eadcc84e188ededa5
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Sync docker image versions from docker manifest commit
b075c2738d81c258f2157eb329241b00e27938ec
Change-Id: I3aab98252d3318431cc4ce49221f552d7bc57b7d
Issue-ID: OOM-1053
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
SMS got a new SAN certificate and we are
using that in this deployment now.
Applications will now query on https://aaf-sms.onap
This should also fix the failing healthcheck
for SMS
-P3: Changing liveness and readiness probes to use
https instead of tcp which was throwing up TLS error
spam on the server
Issue-ID: AAF-284
Change-Id: I654eced0bb75c8b5c807c45773f308d824dfb571
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Change-Id: I2d1ff878c215becc9856af184eb0b11defd75e1d
Issue-ID: OOM-1064
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
Update the docker image versions in the OOM helm charts
with the versions specified in the docker-manifest.csv
in the integration repo.
Change-Id: I38bd9e98ae1b15ed4bbc68051b8516f311aa8db0
Issue-ID: OOM-1053
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
SMS uses vault for its backend which needs
an unseal operation to proceed.
Quorumclient provides the unseal operation
via 3 replicas that store each unseal shard
and provide it during unseal.
Issue-ID: AAF-255
Change-Id: I62db7a450e1e81aa6bfb2cc5b9da29ce99efd24b
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|