Merge branch 'develop' into sitConfigMS

Author: sankarpn

docs-source/content/release-notes.md

@@ -12,10 +12,11 @@ draft: false
 | March 4, 2019 | v2.0.1 | no  | OpenShift support is now certified.  Many bug fixes, including fixes for configuration overrides, cluster services, and domain status processing.  
 | January 24, 2019 | v2.0 | yes; not compatible with 1.x releases, but is compatible with 2.0-rc2. | Final version numbers and documentation updates.  
 | January 16, 2019 | v2.0-rc2 | yes | Schema updates are completed, and various bugs fixed.
-| December 20, 2018 | v2.0-rc1 | yes | Operator is now installed via Helm charts, replacing the earlier scripts.  The operator now supports the domain home on persistent volume or in Docker image use cases, which required a redesign of the domain schema.  You can override the domain configuration using configuration override templates.  Now load balancers and Ingresses can be independently configured.  You can direct WebLogic logs to a persistent volume or to the pod's log.  Added lifecycle support for servers and significantly enhanced configurability for generated pods.  The final v2.0 release will be the initial release where the operator team intends to provide backward compatibility as part of future releases.
-| March 20, 2018 | v1.1 | yes | Several files and input parameters have been renamed.  This affects how operators and domains are created.  It also changes generated Kubernetes artifacts, therefore customers must recreate their operators and domains.
-| April 4, 2018 | v1.0 | yes | Many Kubernetes artifact names and labels have changed. Also, the names of generated YAML files for creating a domain's PV and PVC have changed.  Because of these changes, customers must recreate their operators and domains.
-| May 7, 2018 |   | no | Added support for dynamic clusters, the Apache HTTP Server, the Voyager Ingress Controller, and for PV in NFS storage for multi-node environments.
+| December 20, 2018 | v2.0-rc1 | yes | Operator is now installed via Helm charts, replacing the earlier scripts.  The operator now supports the domain home on persistent volume or in Docker image use cases, which required a redesign of the domain schema.  You can override the domain configuration using configuration override templates.  Now load balancers and Ingresses can be independently configured.  You can direct WebLogic logs to a persistent volume or to the pod's log.  Added life cycle support for servers and significantly enhanced configurability for generated pods.  The final v2.0 release will be the initial release where the operator team intends to provide backward compatibility as part of future releases.
+| September 11, 2018 | v1.1  | no | Enhanced the documentation and fixed various bugs.
+| May 7, 2018 | v1.0  | no | Added support for dynamic clusters, the Apache HTTP Server, the Voyager Ingress Controller, and for PV in NFS storage for multi-node environments.
+| April 4, 2018 | 0.2 | yes | Many Kubernetes artifact names and labels have changed. Also, the names of generated YAML files for creating a domain's PV and PVC have changed.  Because of these changes, customers must recreate their operators and domains.
+| March 20, 2018 |  | yes | Several files and input parameters have been renamed.  This affects how operators and domains are created.  It also changes generated Kubernetes artifacts, therefore customers must recreate their operators and domains.
 
 ### Known issues
 

docs-source/content/security/secrets.md

@@ -8,6 +8,7 @@ description: "Kubernetes secrets for the WebLogic operator"
 #### Contents
 * [WebLogic domain credentials secret](#weblogic-domain-credentials-secret)
 * [WebLogic domain image pull secret](#weblogic-domain-image-pull-secret)
+* [WebLogic operator image pull secret](#weblogic-operator-image-pull-secret)
 * [WebLogic operator configuration override secrets](#weblogic-operator-configuration-override-secrets)
 * [WebLogic operator external REST interface secret](#weblogic-operator-external-rest-interface-secret)
 * [WebLogic operator internal REST interface secret](#weblogic-operator-internal-rest-interface-secret)
@@ -71,14 +72,36 @@ username:  8 bytes
 #### WebLogic domain image pull secret
 
 The WebLogic domain that the operator manages can have images that are protected
-in the registry. The `imagePullSecrets` setting can be used to specify the
+in the registry. The `imagePullSecrets` setting on the `Domain` can be used to specify the
 Kubernetes `Secret` that holds the registry credentials.
 
 {{% notice info %}}
 For more information, see [Docker Image Protection]({{<relref "/security/domain-security/image-protection.md#weblogic-domain-in-docker-image-protection">}})
 under **Domain security**.
 {{% /notice %}}
 
+#### WebLogic operator image pull secret
+
+The Helm chart for installing the operator has an option to specify the
+image pull secret used for the operator's image when using a private registry.
+The Kubernetes `Secret` of type `docker-registry` should be created in the namespace
+where the operator is deployed.
+
+Here is an example of using the `helm install` command to set the image name and image pull secret:
+```bash
+$ helm install kubernetes/charts/weblogic-operator \
+  --set "image=my.io/my-operator-image:1.0" \
+  --set "imagePullSecrets[0].name=my-operator-image-pull-secret" \
+  --name my-weblogic-operator --namespace weblogic-operator-ns \
+  --wait
+```
+
+{{% notice info %}}
+For more information, see
+[Install the operator Helm chart]({{<relref "/userguide/managing-operators/installation/_index.md#install-the-operator-helm-chart">}})
+under **User Guide**.
+{{% /notice %}}
+
 #### WebLogic operator configuration override secrets
 
 The WebLogic operator supports embedding macros within configuration override templates

docs-source/content/userguide/managing-operators/installation/_index.md

@@ -40,6 +40,12 @@ If `weblogic-operator-namespace` exists, then it will be used.  If it does not e
 
 You can verify the operator installation by examining the output from the `helm install` command.
 
+{{% notice note %}}
+When the operator image is stored in a private registry, see
+[WebLogic operator image pull secret]({{<relref "/security/secrets.md#weblogic-operator-image-pull-secret">}})
+for more information on specifying the registry credentials.
+{{% /notice %}}
+
 #### Alternatively, install the operator Helm chart from GitHub chart repository
 
 Add this repository to the Helm installation:

integration-tests/README.md

@@ -97,6 +97,10 @@ Configuration Overrides Usecases
 | JMS Resource Override | Override UniformDistributedTopic Delivery Failure Parameters, `redelivery-limit` and `expiration-policy`. The JMX test client verifies the serverConfig MBean tree for the expected delivery failure parameters, `redelivery-limit` and `expiration-policy`. |
 | WLDF Resource Override | Override `wldf-instrumentation-monitor` and `harvester` in a diagnostics module. The test client verifies the new instrumentation monitors/harvesters set by getting the WLDF resource from serverConfig tree with expected values.  |
 
+| Session Migration | Use Case |
+| --- | --- |
+| Primary Server Repick | A backup server becomes the primary server when a primary server fails|
+| HTTP Session Migration | Verify in-memory HTTP session State replication |
 
 # Directory Configuration and Structure
 

integration-tests/src/test/java/oracle/kubernetes/operator/BaseTest.java

@@ -63,6 +63,7 @@ public class BaseTest {
   private static String leaseId = "";
   private static String branchName = "";
   private static String appLocationInPod = "/u01/oracle/apps";
+  private static String appLocationOnHost;
   private static Properties appProps;
 
   // Set QUICKTEST env var to true to run a small subset of tests.
@@ -183,6 +184,8 @@ public static void initialize(String appPropsFile) throws Exception {
       }
     }
 
+    appLocationOnHost = getProjectRoot() + "/integration-tests/src/test/resources/apps";
+
     logger.info("appProps = " + appProps);
     logger.info("maxIterationPod = " + appProps.getProperty("maxIterationsPod"));
     logger.info(
@@ -545,6 +548,14 @@ public static String getBranchName() {
     return branchName;
   }
 
+  public static String getAppLocationInPod() {
+    return appLocationInPod;
+  }
+
+  public static String getAppLocationOnHost() {
+    return appLocationOnHost;
+  }
+
   private void copyScalingScriptToPod(
       String dirPathToCreate, String domainUID, String podName, String domainNS) throws Exception {