summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2021-02-26Add k8splugin releases file for 0.8.0Lukasz Rajewski1-0/+8
Add k8splugin releases file for 0.8.0 Issue-ID: MULTICLOUD-1294 Signed-off-by: Lukasz Rajewski <lukasz.rajewski@orange.com> Change-Id: I30991d735fc96054b0fd726a42b3b1f7d69c7201
2021-02-24Merge "Move Day2 Config Values API to new endpoint"Bin Yang6-132/+211
2021-02-23Correct pip url due to using python2.7Konrad Bańka1-1/+1
Issue-ID: MULTICLOUD-1255 Signed-off-by: Konrad Bańka <k.banka@samsung.com> Change-Id: I800c4bdbe1fecc61f196ac3098910ae4278bf0cf
2021-02-23Move Day2 Config Values API to new endpointKonrad Bańka6-132/+211
Issue-ID: MULTICLOUD-1280 Signed-off-by: Konrad Bańka <k.banka@samsung.com> Change-Id: Ibeb0920b4ce083f4294b83c887fc7c793a2c3df5
2021-01-29get-pip.py error on Python 2.7Ritu Sood1-1/+1
invalid syntax error when KUD is deployed sys.stderr.write(f"ERROR: {exc}") SyntaxError: invalid syntax Issue-ID: MULTICLOUD-1255 Signed-off-by: Ritu Sood <ritu.sood@intel.com> Change-Id: Ia4ecbad5735617a5606cbce2ed93a58cb7322cb5
2021-01-24Merge "Fix the nodeSelector indent and define name"Ritu Sood3-5/+5
2021-01-13Provide simple v3 chart mock testKonrad Bańka4-0/+55
Issue-ID: MULTICLOUD-1267 Signed-off-by: Konrad Bańka <k.banka@samsung.com> Change-Id: Ib05167a6e0e2c69268bcd85c0ae3fa30fdd78e39
2020-12-16Rollback helm library to version not failing v3 chartsKonrad Bańka2-485/+129
This change reverts fef2f1a959341d2abaea6dadaecccc4952c284c9 commit that updated helm library to a version, that no longer allowed helm v3 charts by explicitly failing when parsing them. Proper support of helm v3 is still not implemented in k8splugin, but at least it shouldn't fail on v3 packages that don't implement v3-specific features. Also apart from revert, go.mod/sum have been also tidied. Issue-ID: MULTICLOUD-1267 Signed-off-by: Konrad Bańka <k.banka@samsung.com> Change-Id: I992004d30802134039f0a6aca2d07a42db9c2459
2020-12-15Merge "MULTICLOUD-1257 updated gui flow"Ritu Sood64-1853/+8310
2020-12-10Merge "Containerized base installation directory change"Eric Multanen1-2/+2
2020-12-09Run all addon tests even when one failsTodd Malsbary2-4/+14
Previously the installer would exit immediately after a failure by one of the addon tests. Now, record the failure and run subsequent tests, then exit if any fail. Issue-ID: MULTICLOUD-1258 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I4fcad9b51b58277344de4fed0e40e87493dc3663
2020-12-10Merge "Fix broken virtlet image URL"Eric Multanen1-1/+1
2020-12-10Merge "Fix sriov test in baremetal deploy"Eric Multanen1-9/+4
2020-12-10Merge "Remove duplicate dict key"Eric Multanen0-0/+0
2020-12-10Merge "Enable pod security policies"Eric Multanen6-4/+107
2020-12-09Remove duplicate dict keyTodd Malsbary1-2/+0
Issue-ID: MULTICLOUD-1262 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: Ie83fad2ad8146b3b33d3a3f0438ff7fe1ac4e475
2020-12-09Enable pod security policiesTodd Malsbary6-4/+107
The intention with this change is to disable CAP_NET_RAW (which can be a security vulnerability) for created Pods. kubespray provides the podsecuritypolicy_enabled variable for enabling privileged (for kube-system) and restricted (for everyone else) policies. Enabling this requires binding the KUD_ADDONs to the privileged policy and specifying the security context correctly for Pods running in the default namespace. As of this change, the only difference between the privileged and restricted security policies is the dropping of CAP_NET_RAW in the restricted policy. To use the default restricted policy provided with kubespray, additional changes must be made to the Pods that are run in the default namespace (such as runing as a non-root user, not requesting privileged mode, etc.). Issue-ID: MULTICLOUD-1256 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I7d6add122ad4046f9116ef03a249f5c9da1d7eec
2020-12-07Fix QAT addon deploy and testTodd Malsbary5-103/+82
Note that as mentioned in install_qat.sh, the kernel command line must include "intel_iommu=on iommu=pt" for the deploy and test to succeed. The underlying issue is that the playbook was expecting to be run on the same host it executed on and was looking for files in the wrong places. Issue-ID: MULTICLOUD-1261 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I5f59b9147f34f077fcdc63d7fc5f80b56977054c
2020-12-03Fix sriov test in baremetal deployTodd Malsbary1-9/+4
The test incorrectly checked the node running the test for sriov feature support. This fix now checks the cluster for it. Issue-ID: MULTICLOUD-1260 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I869823cc062968c8ac7b9fa037d425244a03799c
2020-12-02Fix broken virtlet image URLTodd Malsbary1-1/+1
Issue-ID: MULTICLOUD-1259 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I92cc722818b9023b4aa29d191cf92e2c319f957b
2020-11-27MULTICLOUD-1257 updated gui flowvikaskumar64-1853/+8310
Issue-ID: MULTICLOUD-1257 Change-Id: I5c1432c037952abeed6066cb067192076031f9cd Signed-off-by: vikaskumar <vkumar@aarnanetworks.com>
2020-11-23Fix the nodeSelector indent and define nameLe Yao3-5/+5
Deploy the sdewan controller on master node Change sdewan-contoller-manager to sdewan-crd-controller Issue-ID: MULTICLOUD-1253 Signed-off-by: Le Yao <le.yao@intel.com> Change-Id: Ic55744914266278f1c344c10af587d41f4426918
2020-11-19Fix CrashLoopBackoff in emco-fluentd PodTodd Malsbary1-0/+4
The emco-fluentd pod is stuck in CrashLoopBackOff due to a failure to resolve the "cluster.local" name. Explicitly set the fluentd.clusterDomain value to the actual cluster name during helm install. Issue-ID: MULTICLOUD-1244 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: Ia6424e7ce8d4544511ad88c478e65fa8c4df0c52
2020-11-19Merge "Build and deploy sriov module only on supported hosts."Ritu Sood7-89/+100
2020-11-19Merge "Update multus-daemonset.yml to that of multus-cni v3.6 release"Ritu Sood1-17/+45
2020-11-19Merge "Upgrade kubespray from 2.12.6 to 2.14.1"Ritu Sood33-123/+75
2020-11-19Merge "Update images used in onap4k8s and emco helm charts"Ritu Sood7-13/+13
2020-11-19Merge "Use same host in both copy and run of deploy_optane.sh"Ritu Sood2-9/+9
2020-11-19Merge "Ignore 404 when deleting non-existent project in emco.sh"Ritu Sood1-1/+1
2020-11-19Merge "Wait for service to be listening before running tests"Ritu Sood2-0/+12
2020-11-19Merge "Properly escape query string to jq"Ritu Sood1-2/+2
2020-11-19Merge "Move test inside if block to prevent premature exit"Ritu Sood1-3/+2
2020-11-19Merge "Fix typo in deployments/helm/v2/emco/Chart.yaml"Ritu Sood1-1/+1
2020-11-18Improve early-detection of empty templateKonrad Bańka7-13/+104
Previous empty template detection pattern matched only against templates resolved to empty-or-whitespace-only files. This change makes it handle other case of empty yaml correctly, namely, yaml containing comments only. Issue-ID: MULTICLOUD-1252 Signed-off-by: Konrad Bańka <k.banka@samsung.com> Change-Id: I9132e167ec607c8a4a4ca5584141ed043c6ddd4f
2020-11-11Update multus-daemonset.yml to that of multus-cni v3.6 releaseTodd Malsbary1-17/+45
The only change to the upstream yml is the removal of the kube-multus-ds-ppc64le DaemonSet and the replacement of "default-cni-network" with "cni0". Note also that the v3.6 yml actually uses the v3.4.1 image tag. The yml now points to a v3.4.1 image with the addition of code to merge the results from all delegates to support Virtlet. Issue-ID: MULTICLOUD-1230 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I0e18644a567facfac1fd7dc1c053002b2d906288
2020-10-30Upgrade kubespray from 2.12.6 to 2.14.1Todd Malsbary33-123/+75
- Replace move of ansible.cfg from kubespray distribution to /etc/ansible with ANSIBLE_CONFIG environment variable. Ansible modifies ansible.cfg during installation, and the paths in it are relative. - kubespray 2.14.1 requires a kubernetes version > 1.16. Use the default versions of kubernetes and helm provided by kubespray 2.14.1. - kubespray 2.14.1 replaces helm 2 with helm 3. This removes support for helm init and helm serve. It is no longer necessary to call helm init, and the helm serve repository is replaced with file relative URLs. This also triggered a subsequent update of the kubernetes-helm ansible module to include the newer helm versions. - Add "storageType: hostPath" to etcd/values.yaml. Helm deploy of etcd will fail without this due to nil PersistentVolume.metadata.labels.type. - The mitogen module used by kubespray/ansible requires python2 on the hosts. Use the linear strategy to bypass mitogen and install python2 on the cluster hosts. Issue-ID: MULTICLOUD-1230 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I9f50bb4e123fdcacab6b6a97e79cd09fb5c96634
2020-10-30Use same host in both copy and run of deploy_optane.shTodd Malsbary2-9/+9
NOTE: This is not a complete fix, it is only a workaround so that installer.sh can succeed when Optane hardware is not present. Without this, "No such file or directory" is reported during the "Apply Optane PMEM CSI Daemonset" task of the configure-optane playbook. This error was observed with kubespray 2.14.1 and not with 2.12.6. Issue-ID: MULTICLOUD-1234 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I1e23741d704ab117a84b4ed11e2f7ac02f0f2ec2
2020-10-30Update images used in onap4k8s and emco helm chartsTodd Malsbary7-13/+13
This was triggered by the failure of plugin_fw.sh when run via the containerized installer. The full list of changes is: - etcd-amd64: 3.2.24 => 3.3.17. Note that 3.4.9 is the latest as of this commit, but 3.4.9 removed the coreutils necessary to run the k8s Command (i.e. hostname, seq, ...). - readiness-check: 2.0.0 => 2.2.2 - mongo: 4.0.8 => 4.4.1 - nfs-provisioner: 1.0.8 => 2.3.0 - filebeat: 5.5.0 => 7.9.3 - multicloud-k8s: 0.5.0 => 0.7.0 - fluentd: 1.10.2-debian-10-r11 => 1.11.4-debian-10-r7 Issue-ID: MULTICLOUD-1245 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: Ic0454086c390f6b24a77fcf2ea0e5d24507fa153
2020-10-30Ignore 404 when deleting non-existent project in emco.shTodd Malsbary1-1/+1
The delete is run at the start of the test, it is expected that the resource does not exist. Issue-ID: MULTICLOUD-1243 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I1b060ec8f17fd4b9b76ed03d8dc3bd7c21756690
2020-10-30Wait for service to be listening before running testsTodd Malsbary2-0/+12
Issue-ID: MULTICLOUD-1242 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I5aa45daf92ebfbee32d154dc17f7d2afd72bf255
2020-10-30Properly escape query string to jqTodd Malsbary1-2/+2
Without this change, the '.request.release-name' query causes jq to get confused by the '-' and fail the test script: jq: error: name/0 is not defined at <top-level>, line 1: .request.release-name jq: 1 compile error Issue-ID: MULTICLOUD-1241 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I386cd46db8e44c92bc24d8eb8a9e3964d9b87d39
2020-10-30Move test inside if block to prevent premature exitTodd Malsbary1-3/+2
grep returns a non-zero error code if the pattern is not found. This would cause the topology-manager.sh test to exit prematurely instead of capturing and logging the error and returning zero as intended. Issue-ID: MULTICLOUD-1240 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I29c4d30630c0f803325c2ed024d4c0b9e8a0e911
2020-10-30Fix typo in deployments/helm/v2/emco/Chart.yamlTodd Malsbary1-1/+1
Issue-ID: MULTICLOUD-1239 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: Ibf7c7d2a64889b72cdc67a587548fb6a0dac6ba0
2020-10-16Merge "Update EMCO OpenAPI spec with DCM APIs"Eric Multanen1-0/+909
2020-10-16Merge "Restore commented unit test TestDeleteLogicalCloud"Eric Multanen5-39/+48
2020-10-16Merge "delete should return 404 error for invalid name"Eric Multanen1-1/+6
2020-10-10Restore commented unit test TestDeleteLogicalCloudIgor D.C5-39/+48
Restore the previously commented-out unit test TestDeleteLogicalCloud. That test was disabled due to a failure introduced by interacting with AppContext for the first time in module/logicalcloud.go and it not being ready to do so. This commit restores it and modifies code so dependent mocks can plug in correctly. This was done in order to keep testing the code that was previously being tested, not so much to add additional coverage. Although it would be a significant undertaking, the different types and interfaces in pkg/module should be redesigned to achieve better decoupling and thus make unit testing more straightforward. Issue-ID: MULTICLOUD-1143 Change-Id: I1e6b7bb9111fc6883f0c9cee887329a9e0b27fbd Signed-off-by: Igor D.C <igor.duarte.cardoso@intel.com>
2020-10-09Update EMCO OpenAPI spec with DCM APIsIgor D.C1-0/+909
Update emco_apis.yaml with all new API paths provided by DCM and its /logical-clouds URL prefix. Update schemas and parameters too. Issue-ID: MULTICLOUD-1143 Change-Id: I9d94cb2954c2f0131ffb8c3061a87a6b6a235cba Signed-off-by: Igor D.C <igor.duarte.cardoso@intel.com>
2020-10-08Fix mispelled key name in kubeconfigIgor D.C1-1/+1
Fixes the mispelled "currentcontext" with the right key name "current-context" which was introduced as a regression with or before the latest version of the kubeconfig code (probably a bad search/replace). This 1-character long bug was preventing the generated kubeconfigs from being correctly interpreted by kubectl. Thus, kubectl couldn't set any context of the kubeconfig as the current context. Observable output before this fix: $ kubectl get pods The connection to the server localhost:8080 was refused - did you specify the right host or port? Issue-ID: MULTICLOUD-1143 Change-Id: I617d1e20b7be2567729b84d3746b22e4ceaf8b9d Signed-off-by: Igor D.C <igor.duarte.cardoso@intel.com>
2020-10-08Updating the API definitionRitu Sood1-184/+203
API definition updated to add generic placemnent intent under deployment group Issue-ID: MULTICLOUD-1096 Signed-off-by: Ritu Sood <ritu.sood@intel.com> Change-Id: Ida830de0f17038925651bc604440b11547b7320d