Doc updates for wcsites and oam (#42)

Doc updates for wcsites and oam

Author: sbattagi

docs-source/content/oam/configure-ingress/ingress-nginx-setup-for-oam-domain-setup-on-K8S.md

@@ -101,13 +101,13 @@ Use helm to install NGINX.
 1. Install NGINX using the following helm command:
 
    ```bash
-   $ helm install nginx-ingress --set controller.extraArgs.default-ssl-certificate=<domain_namespace>/<ssl_secret> --set controller.service.type=NodePort --set controller.admissionWebhooks.enabled=false stable/ingress-nginx
+   $ helm install nginx-ingress -n <domain_namespace> --set controller.extraArgs.default-ssl-certificate=<domain_namespace>/<ssl_secret> --set controller.service.type=NodePort --set controller.admissionWebhooks.enabled=false stable/ingress-nginx
    ```
 	
    For example:
 	
    ```bash
-   $ helm install nginx-ingress --set controller.extraArgs.default-ssl-certificate=accessns/accessinfra-tls-cert --set controller.service.type=NodePort --set controller.admissionWebhooks.enabled=false stable/ingress-nginx
+   $ helm install nginx-ingress -n accessns --set controller.extraArgs.default-ssl-certificate=accessns/accessinfra-tls-cert --set controller.service.type=NodePort --set controller.admissionWebhooks.enabled=false stable/ingress-nginx
    ```
     
    The output will look similar to the following:
@@ -116,16 +116,16 @@ Use helm to install NGINX.
    NAME: nginx-ingress
    LAST DEPLOYED: Thu Sep 24 07:31:51 2020
 
-   NAMESPACE: default
+   NAMESPACE: accessns
    STATUS: deployed
    REVISION: 1
    TEST SUITE: None
    NOTES:
    The nginx-ingress controller has been installed.
    Get the application URL by running these commands:
-     export HTTP_NODE_PORT=$(kubectl --namespace default get services -o jsonpath="{.spec.ports[0].nodePort}" nginx-ingress-controller)
-     export HTTPS_NODE_PORT=$(kubectl --namespace default get services -o jsonpath="{.spec.ports[1].nodePort}" nginx-ingress-controller)
-     export NODE_IP=$(kubectl --namespace default get nodes -o jsonpath="{.items[0].status.addresses[1].address}")
+     export HTTP_NODE_PORT=$(kubectl --namespace accessns get services -o jsonpath="{.spec.ports[0].nodePort}" nginx-ingress-controller)
+     export HTTPS_NODE_PORT=$(kubectl --namespace accessns get services -o jsonpath="{.spec.ports[1].nodePort}" nginx-ingress-controller)
+     export NODE_IP=$(kubectl --namespace accessns get nodes -o jsonpath="{.items[0].status.addresses[1].address}")
 
      echo "Visit http://$NODE_IP:$HTTP_NODE_PORT to access your application via HTTP."
      echo "Visit https://$NODE_IP:$HTTPS_NODE_PORT to access your application via HTTPS."
@@ -216,7 +216,7 @@ Use helm to install NGINX.
 1. Find the node port of NGINX using the following command:
 
    ```bash
-   $ kubectl --namespace default get services -o jsonpath="{.spec.ports[1].nodePort}" nginx-ingress-ingress-nginx-controller
+   $ kubectl --namespace accessns get services -o jsonpath="{.spec.ports[1].nodePort}" nginx-ingress-ingress-nginx-controller
    ```
    
    The output will look similar to the following:

docs-source/content/oam/patch-and-upgrade/upgrade_an_operator_release.md

@@ -12,15 +12,15 @@ The new Oracle WebLogic Server Kubernetes Operator Docker image must be installe
 1. Pull the Oracle WebLogic Server Kubernetes Operator 3.X.X image by running the following command on the master node:
 
    ```bash
-   $ docker pull oracle/weblogic-kubernetes-operator:3.X.X
+   $ docker pull ghcr.io/oracle/weblogic-kubernetes-operator:3.X.X
    ```
 
    where `3.X.X` is the version of the operator you require.
 
 1. Run the docker tag command as follows:
 
    ```bash
-   $ docker tag oracle/weblogic-kubernetes-operator:3.X.X weblogic-kubernetes-operator:3.X.X
+   $ docker tag ghcr.io/oracle/weblogic-kubernetes-operator:3.X.X weblogic-kubernetes-operator:3.X.X
    ```
 
    where `3.X.X` is the version of the operator downloaded.
@@ -49,14 +49,14 @@ The new Oracle WebLogic Server Kubernetes Operator Docker image must be installe
 
    ```bash
    $ cd <work directory>/weblogic-kubernetes-operator-3.X.X/weblogic-kubernetes-operator
-   $ helm upgrade --reuse-values --set image=oracle/weblogic-kubernetes-operator:3.X.X --namespace <sample-kubernetes-operator-ns> --wait weblogic-kubernetes-operator kubernetes/charts/weblogic-operator
+   $ helm upgrade --reuse-values --set image=weblogic-kubernetes-operator:3.X.X --namespace <sample-kubernetes-operator-ns> --wait weblogic-kubernetes-operator kubernetes/charts/weblogic-operator
    ```
 
    For example:
 
    ```bash
    $ cd /scratch/OAMDockerK8S/weblogic-kubernetes-operator-3.X.X/weblogic-kubernetes-operator
-   $ helm upgrade --reuse-values --set image=oracle/weblogic-kubernetes-operator:3.X.X --namespace opns --wait weblogic-kubernetes-operator kubernetes/charts/weblogic-operator
+   $ helm upgrade --reuse-values --set image=weblogic-kubernetes-operator:3.X.X --namespace opns --wait weblogic-kubernetes-operator kubernetes/charts/weblogic-operator
    ```
 
 

docs-source/content/oam/post-install-config/_index.md

@@ -152,7 +152,7 @@ For production environments, the following WebLogic Server tuning parameters mus
 
       
    ```bash
-   $ kubectl gets pods -n accessns
+   $ kubectl get pods -n accessns
    ```
 
    The output will look similar to the following:

docs-source/content/oam/prepare-your-environment/_index.md

@@ -116,31 +116,31 @@ The Oracle WebLogic Server Kubernetes Operator Docker image must be installed on
 
 1. Pull the Oracle WebLogic Server Kubernetes Operator 3.0.1 image by running the following command on the master node:
    ```bash
-   $ docker pull oracle/weblogic-kubernetes-operator:3.0.1
+   $ docker pull ghcr.io/oracle/weblogic-kubernetes-operator:3.0.1
    ```
 
 
    The output will look similar to the following:
 
 
    ```bash
-   Trying to pull repository docker.io/oracle/weblogic-kubernetes-operator ...
-   3.0.1: Pulling from docker.io/oracle/weblogic-kubernetes-operator
+   Trying to pull repository ghcr.io/oracle/weblogic-kubernetes-operator ...
+   3.0.1: Pulling from ghcr.io/oracle/weblogic-kubernetes-operator
    bce8f778fef0: Already exists
    de14ddc50a70: Pull complete
    77401a861078: Pull complete
    9c5ac1423af4: Pull complete
    2b6f244f998f: Pull complete
    625e05083092: Pull complete
    Digest: sha256:27047d032ac5a9077b39bec512b99d8ca54bf9bf71227f5fd1b7b26ac80c20d3
-   Status: Downloaded newer image for oracle/weblogic-kubernetes-operator:3.0.1
-   oracle/weblogic-kubernetes-operator:3.0.1
+   Status: Downloaded newer image for ghcr.io/oracle/weblogic-kubernetes-operator
+   ghcr.io/oracle/weblogic-kubernetes-operator:3.0.1
    ```
 
 1. Run the docker tag command as follows:
 
    ```bash
-   $ docker tag oracle/weblogic-kubernetes-operator:3.0.1 weblogic-kubernetes-operator:3.0.1
+   $ docker tag ghcr.io/oracle/weblogic-kubernetes-operator:3.0.1 weblogic-kubernetes-operator:3.0.1
    ```
 
    After installing the Oracle WebLogic Server Kubernetes Operator 3.0.1 Docker image, repeat the above on the worker nodes.
@@ -823,6 +823,33 @@ In this section you prepare the environment for the OAM domain creation. This in
 	
 	**Note**: The persistent volume directory needs to be accessible to both the master and worker node(s) via NFS. Make sure this path has full access permissions, and that the folder is empty. In this example `/scratch/OAMDockerK8S/accessdomainpv` is accessible from all nodes via NFS. 
 
+1. On the master node run the following command to ensure it is possible to read and write to the persistent volume:
+
+   ```bash 
+   cd <work directory>/accessdomainpv
+   touch filemaster.txt
+   ls filemaster.txt
+   ```
+   
+   For example:
+   
+   ```bash
+   cd /scratch/OAMDockerK8S/accessdomainpv
+   touch filemaster.txt
+   ls filemaster.txt
+   ```
+   
+   On the first worker node run the following to ensure it is possible to read and write to the persistent volume:
+   
+   ```bash
+   cd /scratch/OAMDockerK8S/accessdomainpv
+   ls filemaster.txt
+   touch fileworker1.txt
+   ls fileworker1.txt
+   ```
+   
+   Repeat the above for any other worker nodes e.g fileworker2.txt etc. Once proven that it's possible to read and write from each node to the persistent volume, delete the files created.
+
 1. Edit the `create-pv-pvc-inputs.yaml` file and update the following parameters to reflect your settings. Save the file when complete:
 
     ```bash

docs-source/content/oam/prerequisites/_index.md

@@ -21,7 +21,7 @@ In this release, OAM domains are supported using the “domain on a persistent v
 * Helm 3.1.3+ (check with `helm version`).
 * You must have the `cluster-admin` role to install the operator.
 * We do not currently support running OAM in non-Linux containers.
-* A running Oracle Database 12.2.0.1 or later. The database must be a supported version for OAM as outlined in [Oracle Fusion Middleware 12c certifications](https://www.oracle.com/technetwork/middleware/fmw-122140-certmatrix-5763476.xlsx).
+* A running Oracle Database 12.2.0.1 or later. The database must be a supported version for OAM as outlined in [Oracle Fusion Middleware 12c certifications](https://www.oracle.com/technetwork/middleware/fmw-122140-certmatrix-5763476.xlsx). It must meet the requirements as outlined in [About Database Requirements for an Oracle Fusion Middleware Installation](http://www.oracle.com/pls/topic/lookup?ctx=fmw122140&id=GUID-4D3068C8-6686-490A-9C3C-E6D2A435F20A) and in [RCU Requirements for Oracle Databases](http://www.oracle.com/pls/topic/lookup?ctx=fmw122140&id=GUID-35B584F3-6F42-4CA5-9BBB-116E447DAB83).
 
 ### Limitations
 

docs-source/content/oam/troubleshooting/_index.md

@@ -36,7 +36,7 @@ If the OAM domain creation fails when running `create-domain.sh`, run the follow
    Using the output you should be able to diagnose the problem and resolve the issue. 
 
    Clean down the failed domain creation by following steps 1-4 in [Delete the OAM domain home]({{< relref "/oam/manage-oam-domains/delete-domain-home" >}}). Then 
-   [recreate the PC and PVC]({{< relref "/oam/prepare-your-environment/#create-a-kubernetes-persistent-volume-and-persistent-volume-claim" >}}) then execute the [OAM domain creation]({{< relref "/oam/create-oam-domains" >}}) steps again.
+   [recreate the PV and PVC]({{< relref "/oam/prepare-your-environment/#create-a-kubernetes-persistent-volume-and-persistent-volume-claim" >}}) then execute the [OAM domain creation]({{< relref "/oam/create-oam-domains" >}}) steps again.
 
 2. If any of the above commands return the following error:
 
@@ -49,11 +49,7 @@ If the OAM domain creation fails when running `create-domain.sh`, run the follow
    
    a) The directory has 777 permissions: `chmod -R 777 <work directory>/accessdomainpv`.
    
-   b) If it does have the permissions, check if an `oracle` user exists and the `uid` and `gid` equal `1000`, for example:
-   
-   ```bash
-   $ uid=1000(oracle) gid=1000(spg) groups=1000(spg),59968(oinstall),8500(dba),100(users),1007(cgbudba)
-   ```
+   b) If it does have the permissions, check if an `oracle` user exists and the `uid` and `gid` equal `1000`.
    
    Create the `oracle` user if it doesn't exist and set the `uid` and `gid` to `1000`.
    
@@ -64,4 +60,4 @@ If the OAM domain creation fails when running `create-domain.sh`, run the follow
    ```
    
    Clean down the failed domain creation by following steps 1-4 in [Delete the OAM domain home]({{< relref "/oam/manage-oam-domains/delete-domain-home" >}}). Then 
-   [recreate the PC and PVC]({{< relref "/oam/prepare-your-environment/#create-a-kubernetes-persistent-volume-and-persistent-volume-claim" >}}) and then execute the [OAM domain creation]({{< relref "/oam/create-oam-domains" >}}) steps again.
+   [recreate the PV and PVC]({{< relref "/oam/prepare-your-environment/#create-a-kubernetes-persistent-volume-and-persistent-volume-claim" >}}) and then execute the [OAM domain creation]({{< relref "/oam/create-oam-domains" >}}) steps again.

docs-source/content/soa-domains/appendix/quickstart-deployment-on-prem.md

@@ -447,7 +447,8 @@ Follow [these steps]({{< relref "/soa-domains/installguide/prepare-your-environm
 1. Pull the operator image:
 
     ```
-    $ docker pull oracle/weblogic-kubernetes-operator:3.0.1
+    $ docker pull ghcr.io/oracle/weblogic-kubernetes-operator:3.0.1
+    $ docker tag ghcr.io/oracle/weblogic-kubernetes-operator:3.0.1  oracle/weblogic-kubernetes-operator:3.0.1
     ```
 
 1. Obtain the Oracle Database image and Oracle SOA Suite Docker image from the [Oracle Container Registry](https://container-registry.oracle.com):

docs-source/content/soa-domains/installguide/prepare-your-environment/_index.md

@@ -55,7 +55,8 @@ and accept the license agreement for the [WebLogic Server image](https://hub.doc
 1. Pull the operator image:
 
     ```bash
-    $ docker pull oracle/weblogic-kubernetes-operator:3.0.1
+    $ docker pull ghcr.io/oracle/weblogic-kubernetes-operator:3.0.1
+    $ docker tag ghcr.io/oracle/weblogic-kubernetes-operator:3.0.1  oracle/weblogic-kubernetes-operator:3.0.1
     ```
 
 ### Set up the code repository to deploy Oracle SOA Suite domains
@@ -400,7 +401,7 @@ $
 $ ./drop-rcu-schema.sh \
   -s SOA1 \
   -t soaessosb \
-  -d soasuite:12.2.1.4 \
+  -d oracle-db.default.svc.cluster.local:1521/devpdb.k8s \
   -n default \
   -q Oradoc_db1 \
   -r Oradoc_db1