Skip to content

Commit 1b7e236

Browse files
alai8ddsharpe
andauthored
OWLS-83537 - Update domain home in image samples to use WIT instead of docker-images samples (#2290)
* Update domain home in image samples to use WIT instead of docker-images samples Co-authored-by: Derek Sharpe <derek.sharpe@oracle.com>
1 parent 9ef81b2 commit 1b7e236

39 files changed

+2254
-1095
lines changed

documentation/staging/content/quickstart/cleanup.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,3 +73,20 @@ weight: 7
7373
```shell
7474
$ kubectl delete namespace traefik
7575
```
76+
77+
#### Delete the generated image.
78+
79+
1. When no longer needed, delete the generated image by using the `docker rmi` command.
80+
Use the following command to delete an image tagged with `domain-home-in-image:12.2.1.4`:
81+
82+
```shell
83+
$ docker rmi domain-home-in-image:12.2.1.4
84+
```
85+
86+
#### Delete the tools directory.
87+
88+
1. When no longer needed, delete the directory where WebLogic Deploy Tool and WebLogic Image Tool are installed.
89+
90+
```shell
91+
$ rm -rf /tmp/dhii-sample/tools/
92+
```

documentation/staging/content/quickstart/create-domain.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,9 @@ weight: 6
4444
respectively, as you provided when creating the Kubernetes Secret in Step 2.
4545
{{% /notice %}}
4646

47+
For the detailed steps that the `create-domain.sh` script performs, see [Domain Home In Image]({{< relref "/samples/simple/domains/domain-home-in-image/_index.md" >}}).
48+
49+
4750
1. Confirm that the operator started the servers for the domain:
4851

4952
a. Use `kubectl` to show that the Domain was created:

documentation/staging/content/samples/simple/domains/domain-home-in-image/_index.md

Lines changed: 82 additions & 24 deletions
Large diffs are not rendered by default.

documentation/staging/content/samples/simple/domains/domain-home-on-pv/_index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
title: "Domain home on a PV"
33
date: 2019-02-23T17:32:31-05:00
44
weight: 2
5-
description: "Sample for creating a WebLogic domain home on an existing PV or PVC, and the Domain YAML file for deploying the generated WebLogic domain."
5+
description: "Sample for creating a WebLogic domain home on an existing PV or PVC, and the domain resource YAML file for deploying the generated WebLogic domain."
66
---
77

88

9-
The sample scripts demonstrate the creation of a WebLogic domain home on an existing Kubernetes PersistentVolume (PV) and PersistentVolumeClaim (PVC). The scripts also generate the domain YAML file, which can then be used to start the Kubernetes artifacts of the corresponding domain. Optionally, the scripts start up the domain, and WebLogic Server pods and services.
9+
The sample scripts demonstrate the creation of a WebLogic domain home on an existing Kubernetes PersistentVolume (PV) and PersistentVolumeClaim (PVC). The scripts also generate the domain resource YAML file, which can then be used to start the Kubernetes artifacts of the corresponding domain. Optionally, the scripts start up the domain, and WebLogic Server pods and services.
1010

1111
#### Prerequisites
1212

@@ -15,7 +15,7 @@ Before you begin, read this document, [Domain resource]({{< relref "/userguide/m
1515
The following prerequisites must be met prior to running the create domain script:
1616

1717
* Make sure the WebLogic Kubernetes Operator is running.
18-
* The operator requires either Oracle WebLogic Server 12.2.1.3.0 with patch 29135930 applied, or Oracle WebLogic Server 12.2.1.4.0, or Oracle WebLogic Server 14.1.1.0.0. The existing WebLogic Server image, `container-registry.oracle.com/middleware/weblogic:12.2.1.3`, has all the necessary patches applied. For details on how to obtain or create the image, see [WebLogic Server images]({{< relref "/userguide/base-images/_index.md#create-or-obtain-weblogic-server-images" >}}).
18+
* The operator requires an image with Oracle WebLogic Server 12.2.1.3.0 with patch 29135930 applied, or Oracle WebLogic Server 12.2.1.4.0, or Oracle WebLogic Server 14.1.1.0.0. The existing WebLogic Server image, `container-registry.oracle.com/middleware/weblogic:12.2.1.3`, has all the necessary patches applied. For details on how to obtain or create the image, see [WebLogic Server images]({{< relref "/userguide/base-images/_index.md#create-or-obtain-weblogic-server-images" >}}).
1919
* Create a Kubernetes Namespace for the domain unless you intend to use the default namespace.
2020
* In the same Kubernetes Namespace, create the Kubernetes PersistentVolume (PV) where the domain home will be hosted, and the Kubernetes PersistentVolumeClaim (PVC) for the domain. For samples to create a PV and PVC, see [Create sample PV and PVC]({{< relref "/samples/simple/storage/_index.md" >}}). By default, the `create-domain.sh` script creates a domain with the `domainUID` set to `domain1` and expects the PVC `domain1-weblogic-sample-pvc` to be present. You can create `domain1-weblogic-sample-pvc` using [create-pv-pvc.sh](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/scripts/create-weblogic-domain-pv-pvc/create-pv-pvc.sh) with an inputs file that has the `domainUID` set to `domain1`.
2121
* Create the Kubernetes Secrets `username` and `password` of the administrative account in the same Kubernetes Namespace as the domain.
@@ -57,7 +57,7 @@ The script will perform the following steps:
5757
* Create a directory for the generated Kubernetes YAML files for this domain if it does not already exist. The pathname is `/<path to output-directory>/weblogic-domains/<domainUID>`. If the directory already exists, then its contents must be removed before using this script.
5858
* Create a Kubernetes Job that will start up a utility WebLogic Server container and run offline WLST scripts, or WebLogic Deploy Tool (WDT) scripts, to create the domain on the shared storage.
5959
* Run and wait for the job to finish.
60-
* Create a Kubernetes domain YAML file, `domain.yaml`, in the directory that is created above. This YAML file can be used to create the Kubernetes resource using the `kubectl create -f` or `kubectl apply -f` command:
60+
* Create a Kubernetes domain resource YAML file, `domain.yaml`, in the directory that is created above. This YAML file can be used to create the Kubernetes resource using the `kubectl create -f` or `kubectl apply -f` command:
6161
```shell
6262
$ kubectl apply -f /<path to output-directory>/weblogic-domains/<domainUID>/domain.yaml
6363
```
@@ -133,7 +133,7 @@ The following parameters can be provided in the inputs file.
133133

134134
Note that the names of the Kubernetes resources in the generated YAML files may be formed with the value of some of the properties specified in the `create-inputs.yaml` file. Those properties include the `adminServerName`, `clusterName`, and `managedServerNameBase`. If those values contain any characters that are invalid in a Kubernetes Service name, those characters are converted to valid values in the generated YAML files. For example, an uppercase letter is converted to a lowercase letter and an underscore `("_")` is converted to a hyphen `("-")`.
135135

136-
The sample demonstrates how to create a WebLogic domain home and associated Kubernetes resources for a domain that only has one cluster. In addition, the sample provides the capability for users to supply their own scripts to create the domain home for other use cases. The generated domain YAML file could also be modified to cover more use cases.
136+
The sample demonstrates how to create a WebLogic domain home and associated Kubernetes resources for a domain that only has one cluster. In addition, the sample provides the capability for users to supply their own scripts to create the domain home for other use cases. The generated domain resource YAML file could also be modified to cover more use cases.
137137

138138
#### Verify the results
139139

0 commit comments

Comments
 (0)