Content Comparison

...

This document lists the Hardware & Software requirements and provides a walkthrough to set up all-in-one deployment (a.i.o) using aio.sh.

Hardware Requirements

Concept	Amount
CPUs	8
Memory	32GB
Hard Disk	150GB

Software Requirements

Ubuntu Server 16.04 LTS

...

Prepare the environment and clone the repo

$ sudo apt-get update -y
$ sudo apt-get upgrade -y
$ sudo apt-get install -y python-pip

$ git clone https://git.onap.org/multicloud/k8s/

$ git fetch "https://gerrit.onap.org/r/multicloud/k8s" refs/changes/34/84734/6 && git checkout FETCH_HEAD

$ cd hosting_providers/vagrant

$ ./installer.sh | tee kud_installer.log

Since the baremetal setup and vagrant deployment use the same installer script to complete deployment some of the ansible roles within Baremetal and Vagrant are conflicting. Until this is resolved please cherry-pick this patch to get a successful deployment.

...

Create the host.ini file for Kubespray and Ansible

cat <<EOL > inventory/hosts.ini
[all]
Localhost ansible_ssh_host=10.10.110.21 ansible_ssh_port=22
# The ansible_ssh_host IP is an example here. Please update the ansible_ssh_host IP accordingly

[kube-master]
localhost

[kube-node]
localhost

[etcd]
localhost

[ovn-central]
localhost

[ovn-controller]
localhost

[virtlet]
localhost

[k8s-cluster:children]
kube-node
kube-master
EOL

KUD consumes kubespray for provisioning a Kubernetes base deployment. As part of the deployment process, this tool downloads and configures kubectl binary.

Ansible uses SSH protocol for executing remote instructions. The following instructions create and register ssh keys which avoid the usage of passwords.

Generate ssh-keys

$ echo -e "\n\n\n" | ssh-keygen -t rsa -N ""
$ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
$ chmod og-wx ~/.ssh/authorized_keys

Enabling Nested-Virtualization

...

Enable nested virtualization

$sudo ./node.sh

Deploying KUD Services

Finally, the KUD provisioning process can be started through the use of the installer.sh bash script. The output of this script is collected in the kud_installer.log file for future reference.

Bring the cluster up by running the following