You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Java integration tests cover the following use cases:
4
+
5
+
## Basic test Configuration & Use Cases
6
+
7
+
|||
8
+
| --- | --- |
9
+
| Operator Configuration | operator1 deployed in `weblogic-operator` namespace and manages domains in `default` and `jrfdomains` namespaces |
10
+
| Domain Configuration | Domain on PV using WLST, Traefik load balancer |
11
+
12
+
**Basic Use Cases**
13
+
14
+
1. Create operator `weblogic-operator` which manages `default` and `jrfdomains` namespaces, verify it's deployed successfully, pods created, operator ready and verify external REST service, if configured.
15
+
2. Create domain `jrfdomain` in `jrfdomains` namespace and verify the pods, services are created and servers are in ready state.
16
+
3. Verify the admin external service by accessing the admin REST endpoint with `nodeport` in URL.
17
+
4. Verify exec into the admin pod and deploying webapp using the admin port with WLST.
18
+
5. Verify web app load balancing by accessing the webapp using `loadBalancerWebPort`.
19
+
20
+
**Advanced Use Cases**
21
+
22
+
6. Verify domain life cycle (destroy and create) should not have any impact on operator managing the domain and web app load balancing and admin external service.
23
+
7. Cluster scale up/down using operator REST endpoint, webapp load balancing should adjust accordingly.
24
+
8. Operator life cycle (destroy and create) should not impact the running domain.
25
+
26
+
Also the below use cases are covered for each test:
27
+
28
+
9. Verify the liveness probe by killing managed server 1 process 3 times to kick pod auto-restart.
29
+
10. Shutdown the domain by changing domain `serverStartPolicy` to `NEVER`.
30
+
31
+
32
+
## Full test Configuration & Use Cases
33
+
34
+
Additional Operator Configuration:
35
+
36
+
|||
37
+
| --- | --- |
38
+
| Operator Configuration |`operator2` deployed in `weblogic-operator2` namespace and manages domains in `test2` namespace |
39
+
40
+
Basic Use Cases described above are verified in all the domain configurations. Also the below use cases are covered:
41
+
42
+
| Domain | Use Case |
43
+
| --- | --- |
44
+
| Domain on PV using WLST | as above in basic use cases |
45
+
| Domain with ADMIN_ONLY | verify only admin server is started and managed servers are not started. Shutdown domain by deleting domain CRD. Create domain on existing PV dir, pv is already populated by a shutdown domain. |
46
+
| Domain with situational config | create domain with listen address not set for admin server and t3 channel/NAP and incorrect file for admin server log location. Introspector should override these with sit-config automatically. Also, with some junk value for t3 channel public address and using custom situational config override replace with valid public address using secret. Also, on Jenkins this domain uses NFS instead of HOSTPATH PV storage |
47
+
| Two domains managed by two operators | verify scaling and restart of one domain doesn't impact another domain. Delete domain resources using delete script from samples. |
48
+
| Two domains in the same namespace managed by one operator | create two FMW Infra Domains in the same namespace managed by one operator. Verify scaling and restart of one domain doesn't impact another domain. |
49
+
| Two domains in the different namespaces managed by one operator | create two FMW Infra Domains in the different namespaces managed by one operator. Domain1 uses VOYAGER load balancer. Domain2 uses TRAEFIK load balancer. Verify scaling and restart of one domain doesn't impact another domain. |
50
+
| Domain with Recycle policy | create domain with pvReclaimPolicy="Recycle" and using Configured cluster. Verify that the PV is deleted once the domain and PVC are deleted |
51
+
| Domain with default sample values | create domain using mostly default values for inputs |
52
+
53
+
Test cases cover the bugs found:
54
+
55
+
| Domain | Use Case |
56
+
| --- | --- |
57
+
| Domain on PV using WLST | cluster rolling restart with restartVersion and maxUnavailable set to 2, verify the not-ready server counts can not exceed maxUnavailable value |
58
+
| Domain on PV using WLST | in create domain input file, set exposeAdminNodePort to false and exposeAdminT3Channel to true, verify the managed server pods are created |
59
+
| Domain on PV using WLST | in create domain input file, set createDomainScriptsMountPath to non-default value, verify the create domain sample script works |
60
+
| Domain on PV using WLST | in createFMWDomain.py file, set administration_port_enabled to true, verify the admin sever pod is running and ready and all managed server pods are created |
61
+
| Domain on PV using WLST | in create domain input file, set exposeAdminT3Channel to true, verify the admin t3 channel is exposed |
Copy file name to clipboardExpand all lines: integration-tests/README.md
+44-1Lines changed: 44 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,8 @@ Shared cluster runs only Quick test use cases, Jenkins runs both Quick and Full
16
16
17
17
Use Cases covered in integration tests for the operator is available [here](USECASES.MD)
18
18
19
+
JRF Use Cases are covered [here](JRFUSECASES.MD)
20
+
19
21
# Directory Configuration and Structure
20
22
21
23
Directory structure of source code:
@@ -226,8 +228,20 @@ SHARED_CLUSTER=true:
226
228
| IMAGE_NAME_OPERATOR | Docker image name for operator. Default is weblogic-kubernetes-operator |
227
229
| IMAGE_PULL_POLICY_OPERATOR | Default 'Never'. |
228
230
| IMAGE_PULL_SECRET_OPERATOR | Default ''. |
229
-
| IMAGE_PULL_SECRET_WEBLOGIC | Default ''.
231
+
| IMAGE_PULL_SECRET_WEBLOGIC | Default ''.|
230
232
233
+
The below env variables are required for SHARED_CLUSTER=true:
234
+
235
+
| Variable | Description |
236
+
| --- | --- |
237
+
| REPO_REGISTRY | OCIR Server to push/pull the Operator image |
238
+
| REPO_USERNAME | OCIR Username |
239
+
| REPO_PASSWORD | OCIR token |
240
+
| REPO_EMAIL | OCIR email |
241
+
| DOCKER_USERNAME | Docker username to pull the Weblogic image |
242
+
| DOCKER_PASSWORD | Docker password |
243
+
| DOCKER_EMAIL | Docker email |
244
+
| K8S_NODEPORT_HOST | DNS name of a Kubernetes worker node. |
231
245
232
246
Successful run will have the output like below:
233
247
```
@@ -282,6 +296,35 @@ Failed run will have the output like
282
296
```
283
297
JUnit test results can be seen at "integration-tests/target/failsafe-reports/TEST-oracle.kubernetes.operator.ITOperator.xml". This file shows how much time each test case took to run and the failed test results if any.
284
298
299
+
# How to run JRF domain In Operator related tests
300
+
* Setup docker access to FMW Infrastructure 12c Image and Oracle Database 12c Image
301
+
302
+
Method 1
303
+
- Setup a personal account on hub.docker.com
304
+
- Then sign in to hub.docker.com and signup for access to Oracle Database 12c Images via https://hub.docker.com/_/oracle-database-enterprise-edition
305
+
- Then export the following before running the tests:
306
+
```
307
+
export DOCKER_USERNAME=<docker_username>
308
+
export DOCKER_PASSWORD=<docker_password>
309
+
export DOCKER_EMAIL=<docker_email>
310
+
```
311
+
- Setup an account in phx.ocir.io
312
+
- Then sign in to phx.ocir.io to get access to FMW Infrastructure 12c Image: **_phx.ocir.io/weblogick8s/oracle/fmw-infrastructure:12.2.1.3_**
313
+
- export the following before running the tests:
314
+
```
315
+
export REPO_USERNAME=<ocir_username>
316
+
export REPO_PASSWORD=<ocir_password>
317
+
export REPO_EMAIL=<ocir_email>
318
+
```
319
+
320
+
Method 2
321
+
- Make sure the FMW Infrastructure image i.e. **_phx.ocir.io/weblogick8s/oracle/fmw-infrastructure:12.2.1.3_** and the Oracle database image i.e. **_store/oracle/database-enterprise:12.2.0.1_** already exist locally in a docker repository the k8s cluster can access
322
+
323
+
* Command to run the tests:
324
+
```
325
+
mvn clean verify -P jrf-integration-tests 2>&1 | tee log.txt
| Replace/Append Configuration with config file written in non yml format via exporter console| Try to replace/append monitoring exporter configuration with config file written in non yml format, verify configuration has not changed |
115
115
| Replace/Append Configuration with corrupted yml file via exporter console| Try to replace/append monitoring exporter configuration with config file written in corrupted yml format, verify configuration has not changed |
116
116
| Replace/Append Configuration with dublicated values in the config file via exporter console| Try to replace/append monitoring exporter configuration with dublicated values in the config file, verify configuration has not changed |
117
-
| Replace/Append Configuration with invalid credentials via exporter console| Try to replace/append monitoring exporter configuration with varios combos for invalid credentials, verify configuration has not changed and `401 Unauthorized` exception was thrown |
117
+
| Replace/Append Configuration with invalid credentials via exporter console| Try to replace/append monitoring exporter configuration with varios combos for invalid credentials, verify configuration has not changed and `401 Unauthorized` exception was thrown |
118
+
119
+
| Logging with Elastic Stack | Use Case |
120
+
| --- | --- |
121
+
| Search log level | Use Elasticsearch Count API to query logs of level=INFO and verify that total number of logs for level=INFO is not zero and failed count is zero |
122
+
| Search Operator log | Use Elasticsearch Search APIs to query Operator log info and verify that log hits for type=weblogic-operator are not empty |
123
+
| Search Weblogic log | Use Elasticsearch Search APIs to query Weblogic log info and verify that log hits for Weblogic servers are not empty |
0 commit comments