wip

Author: markxnelson

site/creating-domain.md

@@ -4,8 +4,6 @@
 
 The WebLogic domain must be installed into the folder that will be mounted as `/shared/domain`. The recommended approach is to use the provided `create-weblogic-domain.sh` script; however, instructions are also provided for manually installing and configuring a WebLogic domain (see [Manually creating a domain](manually-creating-domain.md)).
 
-Note that there is a short video demonstration of the domain creation process available [here](https://youtu.be/Ey7o8ldKv9Y).
-
 ## Important considerations and restrictions for WebLogic domains in Kubernetes
 
 When running a WebLogic domain in Kubernetes, there are some additional considerations that must be taken into account to ensure correct functioning:

site/manually-creating-domain.md

@@ -1,9 +1,5 @@
-**TODO** finish this
-
 # Manually creating a WebLogic domain
 
-**PLEASE NOTE**: This page is a work in progress. We have some rough notes here and are working on writing better documentation for how to set up this procedure.
-
 If you are creating the domain manually, for example, using a WLST script, the domain must be configured to meet these requirements:
 
 *	Domain directory should be in `/shared/domain`.
@@ -13,7 +9,7 @@ If you are creating the domain manually, for example, using a WLST script, the d
 
 ## Use the scripts to create the sample YAML files
 
-The `create-weblogic-domain.sh` script can be executed with the `-g` option, which will cause it to generate the YAML files but take no action at all against the Kubernetes environment.  This is a useful way to create the sample YAML files needed to manually create a domain.
+The `create-weblogic-domain.sh` script can be executed without the `-e` option, which will cause it to just generate the YAML files but take no action at all against the Kubernetes environment.  This is a useful way to create the sample YAML files needed to manually create a domain.
 
 First, make a copy of `create-weblogic-domain-inputs.yaml` and customize it.
 
@@ -22,17 +18,16 @@ Next, choose and create a directory that generated operator-related files will b
 Then, execute the script, pointing it at your inputs file and output directory:
 
 ```
-./create-weblogic-domain.sh –g \
+$ ./create-weblogic-domain.sh –g \
   –i create-weblogic-domain-inputs.yaml \
   -o /path/to/weblogic-operator-output-directory
 ```
 
 The following YAML files will be generated in the `/path/to/weblogic-operator-output-directory/weblogic-domains/<domainUID>` directory:
 
-*	`weblogic-domain-pv.yaml` can be customized and used to create the persistent volume for this domain.
-*	`weblogic-domain-pvc.yaml` can be customized and used to create the persistent volume claim for this domain.
+*	`domain.yaml` can be customized and used to create the domain custom resource.
 *	`create-weblogic-domain-job.yaml` can be ignored when creating the domain manually.
-*	`domain-custom-resource.yaml` can be customized and used to create the domain resource.
+*   `delete-domain-job.yaml` can be used to delete a domain, and can also be ignored when creating the domain manually.
 
 ## Preparing to create a persistent volume
 
@@ -51,54 +46,53 @@ The file `weblogic-domain-pv.yaml` contains a template to create a persistent vo
 *	Storage class name
 *	The amount of storage to allocate
 *	The physical location of the persistent volume (edit). Prior to creating the persistent volume, you need to ensure this location exists and has read/write/execute permissions set for the account that Kubernetes is running from.
-*	The access mode is Read/Write Many. You must use a provider that supports Read/Write Many.
+*	The access mode is Read/Write/Many. You must use a provider that supports Read/Write/Many.
 *	The contents of the volume are retained across restarts of the Kubernetes environment.
 
 ## Creating the persistent volume
 
-To create the persistent volume, issue the following command:
-
-```
-kubectl create –f weblogic-domain-pv.yaml
-```
+The [sample](/kubernetes/samples/scripts/create-weblogic-domain-pv-pvc/README.md) dmonstrates how to create
+the persistent volume and persistent volume claim.  These must be created before continuing. 
 
 To verify the persistent volume was created, use this command:
 
 ```
-kubectl describe pv PV_NAME
+$ kubectl describe pv PV_NAME
 ```
 
 Replace `PV_NAME` with the name of the persistent volume.
 
 ## Preparing to create the persistent volume claim
 
-The file, `weblogic-domain-pvc.yaml`, contains a template to claim a portion of the persistent volume storage. The customizable items are:
+The [sample](/kubernetes/samples/scripts/create-weblogic-domain-pv-pvc/README.md) dmonstrates how to create
+the persistent volume and persistent volume claim.  These must be created before continuing. 
+The customizable items are:
 
 *	Persistent volume claim name
 *	Namespace name
 *	Storage class name. This value is used to match a persistent volume with the same storage class.
 *	The amount of storage being claimed from the persistent volume.
-*	The access mode is Read/Write Many.
+*	The access mode is Read/Write/Many.
 
 ## Creating the persistent volume claim
 
 To create the persistent volume claim, issue the following command:
 
 ```
-kubectl create –f weblogic-domain-pvc.yaml
+$ kubectl create –f weblogic-domain-pvc.yaml
 ```
 
 To verify the persistent volume was created, use this command:
 
 ```
-kubectl describe pvc PVC_NAME
+$ kubectl describe pvc PVC_NAME
 ```
 
 Replace `PVC_NAME` with the name of the persistent volume claim.
 
 ## Preparing to create the domain resource
 
-The file, `domain-custom-resource.yaml`, contains a template to create the domain resource.  The customizable items are:
+The file, `domain.yaml`, contains a template to create the domain resource.  The customizable items are:
 
 *	Domain name
 *	Namespace name
@@ -110,13 +104,13 @@ The file, `domain-custom-resource.yaml`, contains a template to create the domai
 To create the domain resource, issue the following command:
 
 ```
-kubectl create –f domain-custom-resource.yaml
+$ kubectl create –f domain.yaml
 ```
 
 To verify that the domain resource was created, use this command:
 
 ```
-kubectl describe domain DOMAINUID –n NAMESPACE
+$ kubectl describe domain DOMAINUID –n NAMESPACE
 ```
 
 Replace `DOMAINUID` with the name of the domain’s domainUID and `NAMESPACE` with the namespace the domain was created in.