Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This aims to fix the changes done in
https://gerrit.onap.org/r/c/oom/+/111509 which broke ejbca/netbox/awx
readiness image name pattern.
Change-Id: I65d2f19a96d43c61167d63eb047e960dc213c985
Issue-ID: OOM-2584
Signed-off-by: Bartek Grzybowski <b.grzybowski@partner.samsung.com>
|
|
netbox is only used for testing purpose.
moving the service to ClusterIP is sufficient for that.
Issue-ID: REQ-364
Issue-ID: OOM-2556
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Id8d005a9bcb3fbb29cbf7e82d03a92e245deaaff
|
|
Add configuration to EJBCA that allows to create keystores with
extendedKeyUsage containing serverAuth.
Issue-ID: AAF-1121
Signed-off-by: Remigiusz Janeczek <remigiusz.janeczek@nokia.com>
Change-Id: I6fc1d228acb4edc089be11d66186cfb5006e9ad1
|
|
Readiness container v3.x and up are now present in ONAP main repository.
They're also not using root user anymore and then script path has
changed.
Finally, "job_complete" script has been integrated in main "ready"
script.
As those changes are significant, we must upgrade all the components at
once.
Depends-On: I5afa83892043f4844afe12e61724a8d368a9f2e0
Issue-ID: OOM-2545
Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com>
Change-Id: I0b4eb5dd86390273532d67d0a9696e1cfcadf110
|
|
Issue-ID: OOM-2452
Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com>
Change-Id: I82aa47855716bb2647aea6aac29484b325d80ef0
|
|
Issue-ID: SDNC-1136
Change-Id: I863bd7b280701c503ba45af6ba8e85f48ea18cfb
Signed-off-by: egernug <gerard.nugent@est.tech>
|
|
netbox was using readiness image to run its job. This is not the
proper usage of this image and recently it started failing because
bash is no longer available in this image.
As the script does not containt bash-specific construcitons let's
change the image to curl one and just use whatever shell is there.
Issue-ID: OOM-2406
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I0cc99c6d8fe0dbe59ee982d255753d149fcdd3eb
|
|
postgres was not working with dynamic PV because of lost+found folder.
We changed the mount path to make it work.
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Id15fd089c56e339dbc5939cd28207b535e8ab86b
|
|
EJBCA Server is used to test that CMPv2 Certificate handling is well
done in ONAP.
Issue-ID: AAF-1083
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I5e2d25b68b5cd80d3c7bf282ce871dd81e711ff6
|
|
Instead of forcing installation of all contrib components, make the
installation of these components enabled with a toggle, so each person
can choose to install a subset, all or none.
Issue-ID: OOM-2352
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Ie112fe1f1864587b9ac69f18967a3c28d16bdbbe
|
|
Use 6.0.0 in preparation for Frankfurt release
Issue-ID: OOM-2320
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I8ad82dfdf48b56c38c0e85d640b18cc13c8d9e67
|
|
|
|
|
|
|
|
Extract ingress controller IP address which
is same as node where the metalLB is deployed
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: OOM-2289
Change-Id: I16e6d1704e54b679cb39caa3c720538a5ff60a60
|
|
If Ingress controller is exposed via NodePort
it listens on non standard port, so it can be
quite problematic. Exposing via LoadBalancer
doesn't work properly on bare metal Kubernetes
cluster, so external LB solution is needed.
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: I9a2032e8501caca7c3a564f6bbcf969fdde31da2
Issue-ID: OOM-2346
|
|
Remove unneeded NLB annotation, because NLB
doesn't work correctly in the current version of
kurnetes switch to Metallb
Change-Id: I1111a39a639627892a74f12b428a2daa5ff5ff09
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: OOM-2341
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
Initial version of the script configures
ingress controller service as LoadBalancer
and switches it immediately to NodePort
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: OOM-2341
Change-Id: If741fd2413978ed76bf0678a83c42ac2905042ca
|
|
Underscore configuration should be true
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: PORTAL-806
Change-Id: I88b840e4b8ccd6c635c835ded6e783843aabc10c
|
|
|
|
|
|
Add nginx ingress postinstall optional step for
enable nginx ingress controller service with
LoadBalancer option
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: OOM-2099
Change-Id: I195bfaee5e7e268b0f16da4c75b44c17bd695086
|
|
Add info option for displaying target machine
configuration manual when DNS server is already
deployed on the cluster
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: OOM-2289
Change-Id: Ia876fd9ee51fbe852fae2f9daf8f769ff32efe46
|
|
Also add requirements for Frankfurt release
Issue-ID: OOM-1960
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: Idaa4925515737221c90c4bf9141406fa1d428f15
|
|
|
|
Testing ingress controller based on virtual hosts
requires a lot of entries in the /etc/hosts.
The better way is to create DNS server for testing purposes.
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: OOM-2289
Change-Id: I2ab104c7391e9634972931ac7e79bec5711d2b39
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: PORTAL-806
Change-Id: I9bd2cc1f01a13d198d705affe3cc56be96dd5ce0
|
|
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
|
|
Helm by default creates some useful templates in _helpers.tpl
file. This is fine for stand alone charts but when they become
part of ONAP those helpers are no longer needed as our common
components already provides all required functions
Issue-ID: OOM-2278
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I659e4b45b031e87cc87f7bbbb22bf9e23cd74e61
|
|
As latest are buggy
Change-Id: I8bad9075bc7f4cbcb4bd8274bfbef3d24b15f843
Issue-ID: OOM-2260
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: I278e62821ca98e41f63306e502cca1019ba18756
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Add Nginx ingress postinstall helm
chart. It should be applied after
cluster initial setup.
Issue-ID: OOM-2099
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Change-Id: Ic942b03d6e754c2fca72316cde0d2e65eba9d0d7
|
|
postgres doesn't support that many posgtres instances write into the
same folder so moving to RWO mode is harmless
Change-Id: I3faf715606a7bb479917faf022efbf6635d602f8
Issue-ID: OOM-2080
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Change-Id: Id9fe832a3eb3bfb23e96c711ac8455d1a8cb1156
Issue-ID: CCSDK-1316
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.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
|
|
So both vFW and vDNS use cases can re-use the same ip pool
Change-Id: I9a72bc3947ecaf0868011891dd2df8a2b34261d9
Issue-ID: SDNC-761
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Change-Id: I8293ba9bfa8070ecd34d645b04120c5c7d4b9552
Issue-ID: OOM-1598
Signed-off-by: Michael O'Brien <michael@obrienlabs.org>
|
|
- proper readiness check so the job
stop failing
- pull from netboxcommunity, not onap proxy
Change-Id: I2c1b653a5043e5e961c06666a7ac88c0d9201052
Issue-ID: OOM-1562
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
|
|
Change-Id: I84d5349d702e3c9c1fc575350226c8b3ef542336
Issue-ID: OOM-1670
Signed-off-by: Michael O'Brien <michael@obrienlabs.org>
|
|
Change-Id: I62ab2842ff950c1fbbb0b53ce6863d13c551ea57
Issue-ID: OOM-1722
Issue-ID: OOM-1723
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.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>
|
|
imagePullSecrets was not present and thus preventing connecting to
registry where creds are mandatory.
Change-Id: I087fa77bd33341fa82527b3bc8ae04f323bd0f03
Issue-ID: OOM-1562
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Also rename and use a .py extension
Change-Id: I98d6820dc21faa27ae3dd88cfbe82a65d62d9ba4
Issue-ID: OOM-1527
Signed-off-by: Nicolas Edel <nicolas.edel@orange.com>
|
|
Change-Id: I9282754ec9d53ad78847235dd00c6e403bed7687
Issue-ID: OOM-1527
Signed-off-by: Nicolas Edel <nicolas.edel@orange.com>
|
|
For vFWNG use cases, the ip pool gets created
prior to the use case even being designed.
Just noticed OpenStack is using .1 for Gateway
and .2 for DHCP, hence these two IPs can't be
assign to any port, else, process will fail.
Change-Id: Id8232ce2fe81f1e03ee8f97f3b251b5b22b4fcba
Issue-ID: OOM-1522
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Issue-ID: OOM-1145
Change-Id: I1510339a820802554b6e8b9a201619ef66be17a0
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|