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
Copy file name to clipboardExpand all lines: README.md
+31-3Lines changed: 31 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Oracle is finding ways for organizations using WebLogic Server to run important
18
18
* Scale WebLogic domains by starting and stopping Managed Servers on demand, or by integrating with a REST API to initiate scaling based on WLDF, Prometheus, Grafana, or other rules.
19
19
* Publish operator and WebLogic Server logs into Elasticsearch and interact with them in Kibana.
20
20
21
-
The fastest way to experience the operator is to follow the [Quick Start guide](site/quickstart.md), or you can peruse our [documentation](site), read our [blogs](https://blogs.oracle.com/weblogicserver/how-to-weblogic-server-on-kubernetes), or try out the [samples](kubernetes/samples/README.md).
21
+
The fastest way to experience the operator is to follow the [Quick Start guide](site/quickstart.md), or you can peruse our [documentation](site), read our [blogs](https://blogs.oracle.com/fusionmiddlewaresupport/updated-weblogic-kubernetes-support-with-operator-20-v2), or try out the [samples](kubernetes/samples/README.md).
22
22
23
23
```diff
24
24
+ The current release of the operator is 2.0-rc2, a release candidate for our 2.0 release.
@@ -81,7 +81,7 @@ The [User guide](site/user-guide.md) provides detailed information about all asp
81
81
82
82
Please refer to our [samples](kubernetes/samples/README.md) for information about the available sample code.
83
83
84
-
# Need more help? Have a suggestion? Come and say "Hello!"
84
+
# Need more help? Have a suggestion? Come and say, "Hello!"
85
85
86
86
We have a **public Slack channel** where you can get in touch with us to ask questions about using the operator or give us feedback
87
87
or suggestions about what features and improvements you would like to see. We would love to hear from you. To join our channel,
@@ -100,7 +100,7 @@ Please take a look at our [wish list](https://github.com/oracle/weblogic-kuberne
100
100
101
101
## API documentation
102
102
103
-
Documentation for APIs is provided here:
103
+
Documentation for APIs:
104
104
105
105
* The operator provides a REST API that you can use to obtain configuration information and to initiate scaling actions. For details about how to use the REST APIs, see [Using the operator's REST services](site/rest.md).
106
106
@@ -145,3 +145,31 @@ Only pull requests from committers that can be verified as having signed the OCA
145
145
## Introducing a new dependency
146
146
147
147
Please be aware that pull requests that seek to introduce a new dependency will be subject to additional review. In general, contributors should avoid dependencies with incompatible licenses, and should try to use recent versions of dependencies. Standard security vulnerability checklists will be consulted before accepting a new dependency. Dependencies on closed-source code, including WebLogic Server, will most likely be rejected.
Copy file name to clipboardExpand all lines: integration-tests/README.md
+60-53Lines changed: 60 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,45 +16,51 @@ Wercker runs only Quick test use cases, Jenkins run both Quick and Full test use
16
16
17
17
Java integration tests cover the below use cases:
18
18
19
-
Quick test use cases.
19
+
Quick test use cases -
20
+
21
+
|||
22
+
| --- | --- |
23
+
| Operator Configuration | operator1 deployed in weblogic-operator1 namespace and manages domains in default and test1 namespaces |
24
+
| Domain Configuration | Domain on PV using WLST, traefik load balancer |
25
+
26
+
Basic Use Cases
20
27
21
28
1. create operator operator1 which manages default and test1 namespaces, verify its deployed successfully, pod created, operator Ready and verify external REST service if configured
22
29
2. create domain domain1 in default namespace and verify the pods, services are created and servers are in Ready
23
30
3. verify admin external service by accessing admin REST endpoint with nodeport in URL
24
31
4. verify admin t3 channel port by exec into the admin pod and deploying webapp using the channel port for WLST
25
32
5. verify web app load balancing by accessing the webapp using loadBalancerWebPort
33
+
34
+
Advanced Use Cases
35
+
26
36
6. verify domain life cycle(destroy and create) should not any impact on Operator managing the domain and web app load balancing and admin external service
27
37
7. cluster scale up/down using Operator REST endpoint, webapp load balancing should adjust accordingly.
28
38
8. Operator life cycle(destroy and create) should not impact the running domain
39
+
40
+
Also the below use cases are covered for Quick test
41
+
29
42
9. verify liveness probe by killing managed server 1 process 3 times to kick pod auto-restart
30
43
10. shutdown the domain by changing domain serverStartPolicy to NEVER
31
44
32
-
Full test use cases
33
-
34
-
* keep the first operator running
35
-
* create another domain domain2 in default namespace and verify the domain by doing the checks 2 - 5 listed in quick test
36
-
* shutdown and delete domain domain2
37
-
* create another domain domain3 with dynamic cluster using WDT in test1 namespace and verify the domain by doing the checks 2 - 5 listed in quick test
38
-
* verify cluster scaling by doing scale up for domain3 using WLDF scaling
39
-
* shutdown and delete domain domain3
40
-
* create another operator operator2 which manages test2 namespace and verify domain1 is not affected
41
-
* create another domain domain4 with dynamic cluster in default namespace and domain domain5 with Configured cluster using WDT in test2 namespace and verify the domain by doing the checks 2 - 5 listed in quick test
42
-
* verify scaling for domain5 cluster from 2 to 3 servers and back to 2, plus verify no impact on domain4
43
-
* cycle domain4 down and back up, plus verify no impact on domain5
44
-
* shutdown and delete both domain4 and domain5
45
-
* create domain6 in the default namespace with serverStartPolicy="ADMIN_ONLY", and verify that only admin server is created. on Jenkins, this domain will also test NFS instead of HOSTPATH PV storage
46
-
* shutdown and delete domain6
47
-
* create domain7 in the default namespace with pvReclaimPolicy="Recycle", and verify that the PV is deleted once the domain and PVC are deleted
48
-
* shutdown and delete domain7
49
-
* create domain domain8 and test that create domain fails when its pv is already populated by a shutdown domain
50
-
* create another domain domain9 with APACHE load balancer and access admin console via LB port. shutdown domain.
51
-
* create another domain domain10 with mostly default values from sample domain inputs, mainly exposeAdminT3Channel and exposeAdminNodePort which are false by default and verify domain startup and cluster scaling using operator rest endpoint works.
52
-
* create another domain domain11 with listen address not set for admin server and t3 channel and incorrect file for admin server log
53
-
* verify automatic situational config override works by bringing up the domain and by doing checks 2 - 5 listed in quick test
54
-
* create another domain domain12 with some junk value for t3 channel public address and using custom situational config override replace with valid public address
55
-
* verify the domain by doing checks 2 - 5 listed in quick test
56
-
45
+
Full test use cases -
57
46
47
+
|||
48
+
| --- | --- |
49
+
| Operator Configuration | operator2 deployed in weblogic-operator2 namespace and manages domains test2 namespace |
50
+
| Domain Configuration | Domain on PV using WDT, Domain with serverStartPolicy ADMIN_ONLY, Domain with auto and custom situational configuration, Two domains managed by two operators, Domain with Recycle weblogicDomainStorageReclaimPolicy, Domain with default sample values |
51
+
52
+
53
+
Basic Use Cases described above are verified in all the domain configurations. Also the below use cases are covered:
54
+
55
+
| Domain | Use Case |
56
+
| --- | --- |
57
+
| Domain on PV using WDT | WLDF scaling |
58
+
| Domain with ADMIN_ONLY | making sure 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. |
59
+
| 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 |
60
+
| 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. |
61
+
| Domain with Recycle policy | create domain with pvReclaimPolicy="Recycle" Verify that the PV is deleted once the domain and PVC are deleted |
62
+
| Domain with default sample values | create domain using mostly default values for inputs |
63
+
58
64
59
65
# Directory Configuration and Structure
60
66
@@ -85,6 +91,7 @@ Defaults for RESULT_ROOT & PV_ROOT:
85
91
86
92
87
93
'Physical' subdirectories created by test:
94
+
88
95
Local tmp files: RESULT_ROOT/acceptance_test_tmp/...
@@ -108,14 +115,13 @@ Below configuration files are used from src/integration-tests/resources:
108
115
OperatorIT.properties
109
116
operator1.yaml
110
117
operator2.yaml
111
-
domain1.yaml
112
-
domain2.yaml
113
-
domain3.yaml
114
-
domain4.yaml
115
-
domain5.yaml
116
-
domain6.yaml
117
-
domain7.yaml
118
-
domain8.yaml
118
+
operator_bc.yaml
119
+
operator_chain.yaml
120
+
domainonpvwlst.yaml
121
+
domainonpvwdt.yaml
122
+
domainadminonly.yaml
123
+
domainrecyclepolicy.yaml
124
+
domainsampledefaults.yaml
119
125
```
120
126
121
127
src/integration-tests/resources/OperatorIT.properties - This file is used for configuring common attributes for all integration tests
@@ -138,12 +144,11 @@ externalRestEnabled: true
138
144
javaLoggingLevel: FINE
139
145
```
140
146
141
-
src/integration-tests/resources/domain1.yaml - input/customized properties for PV/Load Balancer/WebLogic Domain. Any property can be provided here from kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/create-domain-inputs.yaml and kubernetes/samples/scripts/create-weblogic-domain-pv-pvc/create-pv-pvc-inputs.yaml. For all the properties that are not defined here, the default values in the sample inputs are used while generating inputs yaml.
147
+
src/integration-tests/resources/domainonpvwlst.yaml - input/customized properties for PV/Load Balancer/WebLogic Domain. Any property can be provided here from kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/create-domain-inputs.yaml and kubernetes/samples/scripts/create-weblogic-domain-pv-pvc/create-pv-pvc-inputs.yaml. For all the properties that are not defined here, the default values in the sample inputs are used while generating inputs yaml.
142
148
143
149
```
144
150
adminServerName: admin-server
145
-
domainName: base_domain
146
-
domainUID: domain1
151
+
domainUID: domainonpvwlst
147
152
clusterName: cluster-1
148
153
configuredManagedServerCount: 4
149
154
initialManagedServerReplicas: 2
@@ -172,7 +177,7 @@ staticPrepare() - initializes the application properties from OperatorIT.propert
172
177
173
178
staticUnPrepare() - releases the cluster lease on wercker env.
174
179
175
-
test methods - test1CreateFirstOperatorAndDomain, test2CreateAnotherDomainInDefaultNS, test3CreateDomainInTest1NS, etc
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.
0 commit comments