aboutsummaryrefslogtreecommitdiffstats
path: root/kud/hosting_providers
AgeCommit message (Collapse)AuthorFilesLines
2021-04-30Merge "Upgrade vagrant version from 2.4 to 2.2.14"Ritu Sood1-1/+1
2021-04-30Merge "Use group libvirt instead of libvirtd"Ritu Sood1-1/+0
2021-03-30Set helm stable repo URL value to updated URLTodd Malsbary2-0/+2
Issue-ID: MULTICLOUD-1323 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: Iac2046b6df4f76efc7f7745567740fffb9b8e72a
2021-03-30Use group libvirt instead of libvirtdTodd Malsbary1-1/+0
This fixes the following error when running ./setup.sh -p libvirt: usermod: group 'libvirtd' does not exist Newer versions of Ubuntu appear to have renamed the libvirtd group to libvirt. Issue-ID: MULTICLOUD-1322 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I54ffc4558cb8945e8c9f9ca751518b20a6de64d0
2021-03-30Upgrade vagrant version from 2.4 to 2.2.14Todd Malsbary1-1/+1
This fixes the following error when running ./setup.sh -p libvirt: Installing the 'vagrant-libvirt' plugin. This can take a few minutes... Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is: nokogiri requires Ruby version < 3.1.dev, >= 2.5. Issue-ID: MULTICLOUD-1321 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: Ia867df9df3ec1cc27e2f17df4a72ffc88f6bdf44
2021-03-09Correct get-pip.py url for python2.7Konrad Bańka2-2/+2
It turned out prior url has been further changed and pip is unavailable by it. Issue-ID: MULTICLOUD-1255 Signed-off-by: Konrad Bańka <k.banka@samsung.com> Change-Id: Id5c9285f74bda17c28ac56de8a847ab74005beba
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-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
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 "Enable pod security policies"Eric Multanen2-2/+68
2020-12-09Enable pod security policiesTodd Malsbary2-2/+68
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 Malsbary1-2/+2
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-11-19Merge "Build and deploy sriov module only on supported hosts."Ritu Sood2-0/+4
2020-10-30Upgrade kubespray from 2.12.6 to 2.14.1Todd Malsbary4-11/+11
- 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-05Build and deploy sriov module only on supported hosts.Todd Malsbary2-0/+4
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-23Add plugin_fw.sh test for v2 and run as part of installer.Todd Malsbary1-0/+6
To deploy to multiple clusters, set the KUD_PLUGIN_FW_CLUSTERS environment variable to the following format (an array of cluster data objects): [ { "metadata": { "name": "NAME", "description": "DESCRIPTION", "userData1": "USER_DATA_1", "userData2": "USER_DATA_2" }, "file": "KUBECONFIG_PATH" }, { ... } ] Issue-ID: MULTICLOUD-1217 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I4c80fbcef1162b441c4dfba4ce2bfd3ac419bc25
2020-09-23Enable installer.sh to use --plugins emco in place of onap4k8s.Todd1-20/+9
Issue-ID: MULTICLOUD-1181 Signed-off-by: Todd <todd.malsbary@intel.com> Change-Id: Ibfdf401d40398bf6b94543dedf4c860951d50de7
2020-08-10Integrate Topology Managerchenjie11-2/+2
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-07-17Merge "Update host_providers/vagrant/setup.sh for virtualbox"Ritu Sood1-1/+1
2020-07-17Update vagrant readme to include info about sample yml filesLarry Sachs1-0/+8
Updates the kud/hosting_providers/vagrant/README.md to include info about the ./config/samples/pdf.yml.* sample files. Issue-ID: MULTICLOUD-1129 Change-Id: I5ab02948932d8a9e9e5a8cfc65350726183cd78d Signed-off-by: Larry Sachs <larry.j.sachs@intel.com>
2020-07-08Update host_providers/vagrant/setup.sh for virtualboxLarry Sachs1-1/+1
host_providers/vagrant/setup.sh -p virtualbox update to /etc/apt/sources.list is now 'bionic' (was 'trusty') Issue-ID: MULTICLOUD-1122 Signed-off-by: Larry Sachs <larry.j.sachs@intel.com> Change-Id: I0cd989466bab4a571b9e18a5e666c8516b168c1d
2020-07-08Update Baremetal Deployment READMELarry Sachs1-8/+113
Updates the Baremetal README.md with info from https://wiki.onap.org/display/DW/Kubernetes+Baremetal+deployment+setup+instructions These scripts were tested on Ubuntu 18.04 Issue-ID: MULTICLOUD-1108 Change-Id: I16d41f3459deef16d156aa85a115aee57b78cf09 Signed-off-by: Larry Sachs <larry.j.sachs@intel.com>
2020-06-22Containerized base installation directory changeYao Le1-2/+2
Change the directory to $HOME instead of /tmp which will refresh after reboot. Same with what we do in vagrant installation. Issue-ID: MULTICLOUD-1050 Signed-off-by: Yao Le <le.yao@intel.com> Change-Id: I413ac0b6c668851841e1bc39d0aafe132ec56ef8
2020-06-06optimize size and time using "--no-cache-dir"Pratik Raj3-8/+8
Using "--no-cache-dir" flag in pip install ,make sure dowloaded packages by pip don't cached on system . This is a best practise which make sure to fetch ftom repo instead of using local cached one . Further , in case of Docker Containers , by restricing caching , we can reduce image size. In term of stats , it depends upon the number of python packages multiplied by their respective size . e.g for heavy packages with a lot of dependencies it reduce a lot by don't caching pip packages. Further , more detail information can be found at https://medium.com/sciforce/strategies-of-docker-images-optimization-2ca9cc5719b6 Issue-ID: MULTICLOUD-1080 Signed-off-by: Pratik Raj <rajpratik71@gmail.com> Change-Id: Ib79fae7e69eb669e39bc3eb52373668367460ba2
2020-06-01Merge "Update the Kubernetes Version to 1.16"Huang Haibin2-8/+10
2020-06-01Merge "Add support for pmem-csi plugin and e2e test"Huang Haibin1-2/+2
2020-05-30Add support for pmem-csi plugin and e2e testChen, Tingjie1-2/+2
Issue-ID: MULTICLOUD-1046 Change-Id: I1853e071a99702c5e6f7ba9ca819746576fd0aca Signed-off-by: Chen, Tingjie <tingjie.chen@intel.com>
2020-06-23Update single-node KUD installation variablesKonrad Bańka1-1/+1
Single host installation requires some kubespray variables defined differently from what is currently defined by default. All-in-one installation script has been updated to provide these differences. CI-building script has been updated and removed applying variables there, as it's not specific just for CI, but for every single-node installation. Issue-ID: MULTICLOUD-1093 Signed-off-by: Konrad Bańka <k.banka@samsung.com> Change-Id: I26c1835d87df41c087b8dfff9f52095083b6c160
2020-05-27Update the Kubernetes Version to 1.16Yao Le2-8/+10
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-26Fix the Multus Baremetal containerization testingr.kuralamudhan1-1/+1
- interface name will be different in each Baremetal - Multus testing good for Vagrant and AIO testing only Issue-ID: MULTICLOUD-1037 Co-authored-by: yu marin <weifei.yu@intel.com> Signed-off-by: Kuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com> Change-Id: I50786f07f0dbd9aadffda69d02597c85e2675203
2020-05-26Adding Multus test in vagrant and containerization installerKuralamudhan Ramakrishnan2-2/+2
Issue-ID: MULTICLOUD-1037 Co-authored-by: yu marin <weifei.yu@intel.com> Signed-off-by: Kuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com> Change-Id: Id07394cc454b3660fb5f06982fea020e93b26039
2020-05-20Update docker version in containerization soltuionr.kuralamudhan1-0/+2
Change docker version to fix kubespray issue in containerization soltuion Co-authored-by: Ritu Sood <ritu.sood@intel.com> Co-authored-by: Le yao <le.yao@intel.com> Signed-off-by: Kuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com> Issue-ID: MULTICLOUD-1073 Change-Id: Id575c64b1630127f1a06ce89ba5b89249d004956
2020-05-20Update docker versionRitu Sood1-0/+2
Change docker version to fix kubespray issue Signed-off-by: Ritu Sood <ritu.sood@intel.com> Issue-ID: MULTICLOUD-1073 Change-Id: I79571677f81efbb12a963b7527d918eddaf8db1f
2020-05-14remove the outdated SDWAN testingr.kuralamudhan1-17/+0
Issue-ID: MULTICLOUD-1071 Signed-off-by: Kuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com> Change-Id: Ia3818ee16393d8e8b2d465d354ce777192baca9e
2020-05-11Fixing README.md for containerization installationKuralamudhan Ramakrishnan2-4/+42
Issue-ID: MULTICLOUD-1068 Signed-off-by: Kuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com> Change-Id: I8ced72f4d9f13b9cb2305fc3778cdd65e933d778
2020-05-08Integrate Openness EAAChenjieXu2-2/+2
Openness EAA provides application/service registration and authentication. EAA is integrated by running EAA via ONAP4K8S. Issue-ID: MULTICLOUD-1044 Signed-off-by: ChenjieXu <chenjie.xu@intel.com> Change-Id: I66dffc5bcfc66675f6b62672e32496ec7f71454c
2020-05-05add cmk in KuDLiang Ding8-11/+37
- 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-30Merge "Change the base installation directory"Huang Haibin1-2/+2
2020-04-14Change the base installation directoryYao Le1-2/+2
The /tmp will refresh after reboot, so change it to &HOME Issue-ID: MULTICLOUD-1050 Signed-off-by: Yao Le <le.yao@intel.com> Change-Id: I47a030b0e33f48c653b21d81d52f7cf717b6d34f
2020-04-07Update Vagrant VM image to Ubuntu-18.04Yao Le3-6/+6
Fix bug ICN-260 KUD Multi Vagrant 18.04 issue Fix bug ICN-303 Compute01 no spcae left in KUD Multi Vagrant Fix bug ICN-285 Nameserver issues behind a proxy Issue-ID: MULTICLOUD-1004 Signed-off-by: Yao Le <le.yao@intel.com> Change-Id: I9e5c6c0e618ebd63babe650f06ca21ff10669cc4
2020-04-07Merge "Revert "Update Vagrant VM Version""Huang Haibin3-6/+6
2020-04-07Revert "Update Vagrant VM Version"Le Yao3-6/+6
This reverts commit f802b87c1d3caecc74789d435358d4f8ff2555a3. Reason for revert: Will rebuild with Nameserver issue solved Issue-ID: MULTICLOUD-1004 Change-Id: Ieafee94e4fe909c30ef8a4167d242f40e114d767 Signed-off-by: Yao Le <le.yao@intel.com>
2020-03-24Update Vagrant VM VersionYao Le3-6/+6
Fix bug ICN-260 KUD Multi Vagrant 18.04 issue Fix bug ICN-303 Compute01 no spcae left in KUD Multi Vagrant Issue-ID: MULTICLOUD-1004 Signed-off-by: Yao Le <le.yao@intel.com> Change-Id: Ic74d4ec2c9ae4bbe42c71f13380f779f842e496d
2020-03-24Merge "Update Vagrant VM Version"Huang Haibin3-6/+6
2020-03-09Merge "Adding QAT device plugin to KuD"Ritu Sood1-2/+2
2020-02-27Adding QAT device plugin to KuDakhilakishore1-2/+2
Basic working skeleton. Adding install script adding vars and updated the playbook. Working on Kernel mode updates and driver installation. Removing SRIOV vars Adding script to change the SSL value for 2 kinds of config files. Updating daemonset image. Adding prereq packages for qat. Minor edits for bashate.Adding testcase and conditions to Ansible tasks for clean, uninstall and install the driver. Updating the plays to use templating. Adding qat-kernel mode test case. Signed-off-by: akhilakishore <akhila.kishore@intel.com> Issue-ID: MULTICLOUD-860 Change-Id: I5ad99e7211c859dc3cb054df644edd3fa77b2596
2020-02-26Updating Readme to reflect accurate setup instructionsAkhila Kishore1-2/+8
Adding sudo to setup for VM based deployment. Additionally adding the link to Vagrant documentation for CLI. Signed-off-by: Akhila Kishore <akhila.kishore@intel.com> Issue-ID: MULTICLOUD-908 Change-Id: I1af5b1c4e201ad4363a8fae1004189e55c514261
2020-02-20KuD cleanup script.Akhila Kishore1-0/+87
This script offers means to cleanup, Docker and Ansible and their configurations. Updated the script to use docker go templating as opposed to regex for docker operations. Further modified the script to include if/else for docker operations for better code readability. Signed-off-by: Akhila Kishore <akhila.kishore@intel.com> Issue-ID: MULTICLOUD-981 Change-Id: Ia6484ebb039daf0b1cb8e698fa7bfa758eeaa568
2020-01-21Reverting vagrant images back to 16.04 VM deploymentAkhila Kishore1-2/+2
Currently we face issue with VM based deployment causing vagrant up to fail and quit abruptly. Signed-off-by: Akhila Kishore <akhila.kishore@intel.com> Issue-ID: MULTICLOUD-974 Change-Id: I9a9e28357f1f56d17643d8f2a31f4cdca70fb456