summaryrefslogtreecommitdiffstats
path: root/kud/deployment_infra
AgeCommit message (Collapse)AuthorFilesLines
2021-05-05Add qat addon helm chartTodd Malsbary11-1/+971
This chart contains the upstream qat plugin from intel-device-plugins-for-kubernetes together with a qat driver installer. Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I3467ba204276999dac4087bdf68ac0d4439861ad
2021-05-05Merge "Add cmk addon helm chart"Ritu Sood9-0/+654
2021-05-05Merge "Add sriov-network addon helm chart"Ritu Sood6-0/+317
2021-05-05Merge "Add ovn4nfv addon helm chart"Ritu Sood17-0/+1232
2021-05-05Merge "Add sriov-network-operator addon helm chart"Ritu Sood20-0/+1384
2021-05-04Add ovn4nfv addon helm chartTodd Malsbary17-0/+1232
This chart follows the upstream installation guide with the following exceptions: - The node-role.kubernetes.io/master:NoSchedule taint is not removed. The YAML files already included the necessary tolerations. - No node labeling is done. Instead, the ovn-control-plane node selector is for the master role, and the nfn-operator pod affinity is for "role: ovn-control-plane". This ensures that the ovn-control-plane and nfn-operator run are scheduled on the same master node, equivalent to the labelling approach used upstream. Also, additional allowed capabilities are needed to run the pods with the restricted PodSecurityPolicy. These capabilities are requested by the Pods, but not available in the default set of allowed capabilities. Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I54ae12434572e2e2dd1fe2ec9298d04557331d94
2021-05-04Add sriov-network addon helm chartTodd Malsbary6-0/+317
This chart deploys the CR used by the sriov-network-operator. Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I9364868d3e58fd64e51a77aaa934284fad86a1b1
2021-05-04Add sriov-network-operator addon helm chartTodd Malsbary20-0/+1384
This chart contains the upstream sriov-network-operator from k8snetworkplumbingwg together with an iavf driver installer. Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: Ic925c66f8e2b28b7604240c3ed35b1a56883b60b
2021-04-30Merge "Remove unused cmk kud vars"Ritu Sood1-4/+0
2021-04-30Merge "Add nfd addon helm chart"Ritu Sood11-0/+619
2021-04-30Merge "Add multus addon helm chart"Ritu Sood10-0/+433
2021-04-30Merge "Add Makefile for addon helm charts"Ritu Sood2-0/+52
2021-04-29Add cmk addon helm chartTodd Malsbary9-0/+654
The chart follows the instructions laid out in the CMK operator manual, with the following notes: - The nodes are prepared by running each CMK subcommand as a Pod instead of running cmk cluster-init. The first reason for this is that the existing addon only deploys CMK to the worker nodes in the cluster. This is not possible using cluster-init without explicitly providing the list of worker nodes to cluster-init, and this list is unknown by helm. Instead it is sufficient to rely on the node-role.kubernetes.io/master:NoSchedule taint. The second reason is that cluster-init creates resources which are unknown to helm, thus uninstall does not behave as expected. - The v1.4.1 version of CMK is chosen. In v1.5.2, the description key of the cmk-nodereport resource is not correct. - All values listed as possibly requiring modification are exposed in values.yaml Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: Ibc75462de3729cd88edeb4b15602d57fe12791ca
2021-04-29Remove unused cmk kud varsTodd Malsbary1-4/+0
Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I0c1d43de8506233eb62bde52641bb7fc95b422fc
2021-04-28Add X710 to iavf driver NICsTodd Malsbary2-9/+3
Issue-ID: MULTICLOUD-1336 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I7a0ee4302c020e6b7ec785d6a85af636b6a85ecc
2021-04-09Add multus addon helm chartTodd Malsbary10-0/+433
- Support for calico configuration is present but currently disabled. Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I2d2161564c4da2e165e5cf13cea92fae4935f8b2
2021-04-06Add Makefile for addon helm chartsTodd Malsbary2-0/+52
Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I90a9cf23a8fb01cbc579d2b6670b476494c2a7bb
2021-03-30Add nfd addon helm chartTodd Malsbary11-0/+619
This change adds iavf, qat, and pci device labels to the node feature discovery config. Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: Ie6296caf898983149483ac581428f2c80405bca8
2021-01-24Merge "Fix the nodeSelector indent and define name"Ritu Sood3-5/+5
2020-12-10Merge "Fix broken virtlet image URL"Eric Multanen1-1/+1
2020-12-10Merge "Enable pod security policies"Eric Multanen4-2/+39
2020-12-09Enable pod security policiesTodd Malsbary4-2/+39
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 Malsbary3-91/+75
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-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-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 Sood5-89/+96
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 Sood8-48/+27
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 Malsbary8-48/+27
- 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-05Build and deploy sriov module only on supported hosts.Todd Malsbary5-89/+96
Building on the target host fixes a couple issues: - In the containerized installer, the container image does not include the necessary kernel headers to build the module. - The build and target host must have the same kernel version. There is no guarantee of this. The deploy uses NFD, similar to the QAT playbook. Issue-ID: MULTICLOUD-1228 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I58705b73b8ce6d381b4649d5a20b8644e51e1b13
2020-09-23Merge "Add playbooks for v2 emco chart."Ritu Sood3-1/+112
2020-09-23Add playbooks for v2 emco chart.Todd Malsbary3-1/+112
Rename v2/onap4k8s to v2/emco, and rename sanity-check-for-v2.sh to emco.sh. This allows --plugins emco to be passed to installer.sh in place of --plugins onap4k8s. Issue-ID: MULTICLOUD-1181 Signed-off-by: Todd <todd.malsbary@intel.com> Change-Id: Idb427a8aa4c8aaff181965a540078c8cf6dd88aa
2020-09-23Create helm chart for ICN/SDEWAN controllersYao Le12-0/+1755
Create helm chart for sdewan-controller in KUD Issue-ID: MULTICLOUD-1104 Signed-off-by: Yao Le <le.yao@intel.com> Change-Id: Ic5d8daecdecba52c05d3ed38fa91ebd555ce5533
2020-09-01Replace invalid literal true with valid string "true" in yaml.Todd Malsbary1-1/+1
Prior to this change qat_plugin_privileges.yaml fails to kubectl apply due to a validation error. Issue-ID: MULTICLOUD-1182 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: Ibe73c1b39d1164fe05ea5cdede74dc93f846c943
2020-08-10Integrate Topology Managerchenjie12-0/+73
Integrate topology manager by utilizing ansible scripts from openness. Issue-ID: MULTICLOUD-1102 Signed-off-by: ChenjieXu <chenjie.xu@intel.com> Change-Id: Ibaaf77e44c97edffe1ae03bf77c2422c89783e75
2020-05-27Bug fix for the qat device plugin deploymentKuralamudhan Ramakrishnan1-0/+9
Issue-ID: MULTICLOUD-1075 Signed-off-by: Kuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com> Change-Id: I0b02a3872b525a061bbdaf87aabad8b3fee539cc
2020-06-01Merge "Update the Kubernetes Version to 1.16"Huang Haibin5-7/+25
2020-06-01Merge "Add support for pmem-csi plugin and e2e test"Huang Haibin9-0/+1074
2020-05-30Add support for pmem-csi plugin and e2e testChen, Tingjie9-0/+1074
Issue-ID: MULTICLOUD-1046 Change-Id: I1853e071a99702c5e6f7ba9ca819746576fd0aca Signed-off-by: Chen, Tingjie <tingjie.chen@intel.com>
2020-05-27Update the Kubernetes Version to 1.16Yao Le5-7/+25
Update kubespray to 2.12 to deploy Kubernetes 1.16 Issue-ID: MULTICLOUD-1063 Signed-off-by: Yao Le <le.yao@intel.com> Change-Id: I537f6395e5d05d8b72411dd1e0789e19972f1947
2020-05-26Bug fix for the ImagePullBackOff error in qat testKuralamudhan Ramakrishnan1-1/+1
Issue-ID: MULTICLOUD-1076 Signed-off-by: Kuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com> Change-Id: I2b6bfb265ce5e055987788f6f28fc475a8b5b46c
2020-05-25sriov baremetal installation fixKuralamudhan Ramakrishnan2-5/+11
Signed-off-by: Kuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com> Issue-ID: MULTICLOUD-1074 Change-Id: I5c497aef954945c4baee10ff5613b220ed9b8152
2020-05-21Update scripts for ovn4nfv in multicloud-k8sRuoyu1-12/+26
* Update the image version to integratedcloudnative/ovn4nfv-k8s-plugin * Update the CRD of provider network to support direct provider network Issue-ID: MULTICLOUD-1070 Change-Id: Icfa321bbd354de47af4db65b2021c87facc26871 Signed-off-by: Ruoyu <ruoyu.ying@intel.com>
2020-05-05add cmk in KuDLiang Ding4-0/+479
- deploy cmk related pods - untaint compute nodes if necessary - run cmk unit tests: allocate CPUs from exclusive and shared pools - deploy a testing nginx pod along with cmk testing pods - preset 1/2 CPUs for shared/exlusive pools to fit CI server machines users can adjust the parameters to meet their own requirements Test Results: - many rounds of vagrant/5 VMs(controller01/02/03 and compute01/02) based test are all OK - 14 rounds tests on my local server (S2600WFQ (36C/72T) )and PC(HP Z228 (4C/4T)) with all-in-one bare metal deployment are all OK - CI(a 4C/4T machine) results of latest patch set also show that the test of bare metal deployment is OK - NOTE: both my local test and CI use the same testing method of calling aio.sh after applying the latest patch set. Change-Id: I046a4a63b94f92f23347ab76c21a661521e01119 Issue-ID: MULTICLOUD-879 Signed-off-by: Liang Ding <liang.ding@intel.com>
2020-04-27Merge "Install criproxy binary in /usr/local/bin instead of /tmp. Issue-ID: ↵Ritu Sood2-1/+4
MULTICLOUD-1051"
2020-04-21Upgrate the out-of-date link in virtlet testYao Le1-1/+1
The fedora 29 image link is out of date. It is not reachable now. So upgrade the link to fedora 31. Issue-ID: MULTICLOUD-1057 Signed-off-by: Yao Le <le.yao@intel.com> Change-Id: I5f384cb906bf080c55ea4ea2a27b1514722c8b76
2020-04-19Install criproxy binary in /usr/local/bin instead of /tmp.Eric Tang2-1/+4
Issue-ID: MULTICLOUD-1051 Signed-off-by: Eric Tang <qcorba@gmail.com> Change-Id: I96443ee539de0e2a18011148f86f97e70634cae3 Signed-off-by: Eric Tang <qcorba@gmail.com>