Ol8 onprem doc (#803)

* update docs for on-prem install

---------

Co-authored-by: Andy Tael <andy.tael@yahoo.com>

Author: gotsysdba

docs-source/spring/content/on-premises/ol8/_index.md

@@ -6,89 +6,116 @@ This is an description of installing on a Oracle Linux 8 desktop.
 
 Read the [On-Premises](../../on-premises) documentation and ensure that your desktop meets the minimum system requirements.
 
-## Install
+## Setup
 
-### Additional Operating System Packages
+### Create a Non-Root User
 
-Install additional operating system packages by executing these commands:
+Create a new user. While any user name can be created, the rest of this documentation refers to the non-root user as `obaas`:
+
+As `root`, process the following:
 
 ```bash
-dnf -y module install container-tools:ol8
-dnf -y install conntrack podman curl
-dnf -y install oracle-database-preinstall-21c
-dnf -y install langpacks-en
-dnf module install -y python39
-dnf -y update
+useradd obaas
 ```
 
-Set the default Python3 to Python 3.9 by running this command:
+### Download Oracle Backend for Spring Boot and Microservices
+
+Download [Oracle Backend for Spring Boot](https://github.com/oracle/microservices-datadriven/releases/download/OBAAS-1.0.1/onprem-ebaas_latest.zip) and unzip into a new directory.
+
+As the `obaas` user, run this command:
 
 ```bash
-sudo alternatives --set python3 /usr/bin/python3.9
+unzip onprem-ebaas_latest.zip -d ~/obaas
 ```
 
-### Install Minikube
+### Setup SSH-Key Access for obaas user
 
-As the `root` user, install Minikube:
+Future access to the `obaas` user requires a direct login (not `sudo` or `su`).  To setup ssh-key access as `obaas`, run the following commands:
 
 ```bash
-curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64
-install minikube-linux-amd64 /usr/local/bin/minikube
+mkdir ~/.ssh
+vi ~/.ssh/authorized_keys
 ```
 
-### Create a Non-Root User
+Paste the public key of your client machines into the `~/.ssh/authorized_keys` file, and change the permissions as follows:
 
-Create a new user. While any user name can be created, the rest of this documentation refers to the non-root user as `obaas`:
+```bash
+chmod 700 .ssh
+chmod 600 .ssh/authorized_keys
+```
 
-As `root`, process the following:
+### Update the operating system
+
+Assuming the source was unzipped to `~obaas/obaas`, as the `root` user, update the operating system by running the `ol8_onprem.sh` script from the unzipped package:
 
 ```bash
-useradd obaas
-echo "obaas ALL=(ALL) NOPASSWD: /bin/podman" >> /etc/sudoers
+~obaas/obaas/ol8_onprem.sh
 ```
 
+This script performs the following actions:
+
+* Install required operating system Packages
+* Install Minikube
+* Set Python3 as the default python
+* Enable cgroup v2
+* Enable IP Tables
+* Update the container runtime configuration
+
+### (Optional) OCI Host Filesystem
+
+If this is being installed on an OCI Compute instance, grow the filesystem:
+
+As `root`:
+
+```bash
+/usr/libexec/oci-growfs
+```
+
+### Reboot
+
+**IMPORTANT** After the operating system has been updated, `reboot` the host.
+
+## Install
+
+The remaining steps require **direct login** as the `obaas` user without using `sudo` or `su`.
+
 ### Download the Database or Oracle REST Data Services (ORDS) Images
 
-The _Desktop_ installation provisions an Oracle database into the Kubernetes cluster. The images must be downloaded
-from [Oracle Cloud Infrastructure Registry (Container Registry)](https://container-registry.oracle.com/) before continuing.
-As the `obaas` user, process these steps:
+The _Desktop_ installation provisions an Oracle database into the Kubernetes cluster. The images must be downloaded from [Oracle Cloud Infrastructure Registry (Container Registry)](https://container-registry.oracle.com/) before continuing.
+
+While directly logged into the `obaas` user, process these steps:
 
 1. Log in to the Container Registry. For example:
 
    `podman login container-registry.oracle.com`
 
-2. Pull the database image. For example:
+1. Pull the database image. For example:
 
    `podman pull container-registry.oracle.com/database/enterprise:19.3.0.0`
 
-3. Pull the ORDS image. For example:
+1. Pull the ORDS image. For example:
 
    `podman pull container-registry.oracle.com/database/ords:21.4.2-gh`
 
+#### Troubleshooting
+
+If the `podman pull` command fails, navigate in a web browser to [Oracle container registry](https://container-registry.oracle.com), click the "database" tile and select "enterprise".  On the right hand side of the page, if prompted, sign-in.  Select "Language" and accept the Terms.  Try the `podman pull` command again.
+
 ### Start MiniKube
 
-As the `obaas` user, run these commands:
+While directly logged into the `obaas` user, run these commands:
 
 ```bash
-echo "PATH=\$PATH:/usr/sbin" >> ~/.bashrc
+minikube config set rootless true
 minikube config set driver podman
-minikube start --cpus max --memory 7900mb --disk-size='40g' --container-runtime=cri-o
+minikube start --cpus max --memory 16G --disk-size='40g' --container-runtime=containerd
 minikube addons enable ingress
-```
-
-### Download Oracle Backend for Spring Boot and Microservices
-
-Download [Oracle Backend for Spring Boot](https://github.com/oracle/microservices-datadriven/releases/download/OBAAS-1.0.0/onprem-ebaas_latest.zip) and unzip into a new directory.
-
-As the `obaas` user, run these commands:
-
-```bash
-unzip onprem-ebaas_latest.zip -d ~/obaas
+echo "KUBECONFIG=~/.kube/config" >> ~/.bashrc
 ```
 
 ### Install Ansible
 
-As the `obaas` user, change to the source directory and install Ansible by running these commands:
+While directly logged into the `obaas` user, change to the source directory and install Ansible by running these commands:
 
 ```bash
 cd ~/obaas
@@ -110,14 +137,12 @@ Assuming the source was unzipped to `~/obaas`, run the following command as the
 
 ### Open a Tunnel
 
-In order to push the images to the Container Registry in the Kubernetes cluster, open a new terminal and process this command
-as the `obaas` user:
-
-As the `obaas` user, run these commands:
+In order to push the images to the Container Registry in the Kubernetes cluster, open a new terminal and process this command while being directly logged into the `obaas` user:
 
 ```bash
+cd ~/obaas
 source ./activate.env
-kubectl port-forward service/private -n container-registry 5000:5000 &`
+kubectl port-forward service/private -n container-registry 5000:5000  > /dev/null 2>&1 &
 ```
 
 ### Build the Images
@@ -126,31 +151,36 @@ Build and push the images to the Container Registry in the Kubernetes cluster.
 
 Assuming the source was unzipped to `~/obaas`, run the following command as the `obaas` user:
 
-`ansible-playbook ~/obaas/ansible/images_build.yaml`
+```bash
+cd ~/obaas
+source ./activate.env
+ansible-playbook ~/obaas/ansible/images_build.yaml
+```
 
 After the images are built and pushed, the port-forward is no longer required and can be stopped.
 
 ### Deploy Microservices
 
 Assuming the source was unzipped to `~/obaas`, run this command as the `obaas` user:
 
-`ansible-playbook ~/obaas/ansible/k8s_apply.yaml -t full`
+```bash
+cd ~/obaas
+source ./activate.env
+ansible-playbook ~/obaas/ansible/k8s_apply.yaml -t full
+```
 
 ## Notes
 
 ### config-server and obaas-admin Pod Failures
 
-The Pods in the `config-server` and `obaas-admin` namespaces rely on the database that is created in
-the `oracle-database-operator-system`. During the initial provisioning, these Pods start well before the database is available
-resulting in initial failures. They resolve themselves once the database becomes available.
+The Pods in the `azn-server`, `config-server`, and `obaas-admin` namespaces rely on the database that is created in the `oracle-database-operator-system`. During the initial provisioning, these Pods start well before the database is available resulting in initial failures. They resolve themselves once the database becomes available.
 
 You can check on the status of the database by running this command:
 
 `kubectl get singleinstancedatabase baas -n oracle-database-operator-system -o "jsonpath={.status.status}"`
 
 ### VPN and Proxies
 
-If you are behind a Virtual Private Network (VPN) or proxy, see https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/ for more
-details on additional tasks.
+If you are behind a Virtual Private Network (VPN) or proxy, see [Minikube Proxies and VPNs](https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/) for more details on additional tasks.
 
 Next, go to the [Getting Started](../getting-started/) page to learn more.