Update Baremetal Deployment README

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>

1 files changed, 113 insertions, 8 deletions

diff --git a/kud/hosting_providers/baremetal/README.md b/kud/hosting_providers/baremetal/README.md
index 5e1edf79..aabdf2b8 100644
--- a/kud/hosting_providers/baremetal/README.md
+++ b/kud/hosting_providers/baremetal/README.md
@@ -4,23 +4,128 @@
 
 This project offers a means for deploying a Kubernetes cluster
 that satisfies the requirements of [ONAP multicloud/k8s plugin][1]. Its
-ansible playbooks allow to provision a deployment on Baremetal. 
-
+ansible playbooks allow to provision a deployment on Baremetal.
 
 ![Diagram](../../../docs/img/installer_workflow.png)
 
+## Kubernetes Baremetal Deployment Setup Instructions
+
+1. Hardware Requirements
+1. Software Requirements
+1. Instructions to run KUD on Baremetal environment
+1. aio.sh Explained
+1. Enabling Nested-Virtualization
+1. Deploying KUD Services
+1. Running test cases
+
+## Bare-Metal Provisioning
+
+The Kubernetes Deployment, aka KUD, has been designed to be consumed by Virtual Machines as well as Bare-Metal servers. The `aio.sh` script contains the bash instructions for provisioning an All-in-One Kubernetes deployment on a Bare-Metal server.
+
+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
+CPUs -- 8
+
+Memory -- 32GB
+
+Hard Disk -- 150GB
+
+## Software Requirements
+Ubuntu Server 18.04 LTS
+
+## Instructions to run KUD on Baremetal environment
+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/`
+
+## Run script to setup KUD
+
+`$ k8s/kud/hosting_providers/baremetal/aio.sh`
+
+## [aio.sh](aio.sh) Explained
+This bash script provides an automated process for deploying an All-in-One Kubernetes cluster. Given that the ansible inventory file created by this script doesn't specify any information about user and password, it's necessary to execute this script as the root user.
+
+Overall, this script can be summarized in three general phases:
+
+1. Cloning and configuring the KUD project.
+1. Enabling Nested-Virtualization.
+1. Deploying KUD services.
+
+KUD requires multiple files(bash scripts and ansible playbooks) to operate. Therefore, it's necessary to clone the *ONAP multicloud/k8s* project to get access to the *vagrant* folder.
 
-## Deployment
+Ansible works with multiple systems, the way for selecting them is through the usage of the inventory. The inventory file is a static source for determining the target servers used for the execution of ansible tasks.
 
-The [installer](installer.sh) bash script contains the minimal
-Ubuntu instructions required for running this project.
+The *aio.sh* script creates an inventory file for addressing those tasks to localhost. The inventory file needs to be explicitly updated with the ansible_ssh_host=*with the IP address of the machine or host-IP* along with *ansible_ssh_port*. This is necessary to have some of the test cases run.
 
-NOTE: for cmk bare metal deployment, preset 1/2 CPUs for
-      shared/exlusive pools respectively to fit CI server machines
-      users can adjust the parameters to meet their own requirements.
+### Create the host.ini file for Kubespray and Ansible
+```
+
+cat <<EOL > ../vagrant/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](https://github.com/kubernetes-sigs/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
+KUD installs [Virtlet](https://github.com/Mirantis/virtlet) Kubernetes CRI for running Virtual Machine workloads. Nested-virtualization gives the ability to run a Virtual Machine within another. The [node.sh](../vagrant/node.sh) bash script contains the instructions for enabling Nested-Virtualization.
+
+#### Enable nested virtualization
+`$ sudo ../vagrant/node.sh`
+
+### Deploying KUD Services
+Finally, the KUD provisioning process can be started through the use of the [installer](../vagrant/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
+`$ ../vagrant/installer.sh | tee kud_installer.log`
+
+## Running test cases
+The *kud/tests* folder contain the health check scripts that guarantee the proper installation/configuration of Kubernetes add-ons. Some of the examples for test scripts are *virtlet.sh, multus.sh, ovn4nfv.sh* etc.
 
 ## License
 
 Apache-2.0
 
 [1]: https://git.onap.org/multicloud/k8s
+