Version update for ML11 release (#178)

* Version update for ML11 release
* Updated remaining versions to the latest release

Author: vitalykorolev

README.md

@@ -36,7 +36,7 @@ Note: In order to use the MarkLogic Image you need to request the Developer Lice
 
 Note: MarkLogic Server Docker images follow a specific tagging format: `{ML release version}-{platform}-{ML Docker release version}`
 
-- 10.0-9.5-centos-1.0.0 - This current release of the MarkLogic Server Developer Docker image includes all features and is limited to developer use
+- 11.0.0-centos-1.0.0 - This current release of the MarkLogic Server Developer Docker image includes all features and is limited to developer use
 - [Older Supported Tags](#older-supported-tags)
 
 # Architecture reference
@@ -47,7 +47,7 @@ Supported Docker architectures: x86_64
 
 Base OS: CentOS
 
-Latest supported MarkLogic Server version: 10.0-9.5
+Latest supported MarkLogic Server version: 11.0.0
 
 Published image artifact details: https://github.com/marklogic/marklogic-docker, https://hub.docker.com/r/marklogicdb/marklogic-db
 
@@ -78,15 +78,15 @@ $ docker run -d -it -p 8000:8000 -p 8001:8001 -p 8002:8002 \
      -e REALM={insert authentication realm} \
      -e LICENSE_KEY="{insert license}" \
      -e LICENSEE="{insert licensee}" \
-     marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+     marklogicdb/marklogic-db:11.0.0-centos-1.0.0
 ```
 Example run:
 ```
 $ docker run -d -it -p 8000:8000 -p 8001:8001 -p 8002:8002 \ 
      -e MARKLOGIC_INIT=true \
      -e MARKLOGIC_ADMIN_USERNAME=admin \
      -e MARKLOGIC_ADMIN_PASSWORD=Areally!PowerfulPassword1337 \
-     marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+     marklogicdb/marklogic-db:11.0.0-centos-1.0.0
 ```
 Wait about a minute for MarkLogic Server to initialize before checking the ports. To verify the successful installation and initialization, log into the MarkLogic Server Admin Interface using the admin credentials used in the command above. Go to http://localhost:8001. You can also verify the configuration by following the procedures outlined in the MarkLogic Server documentation. See the MarkLogic Installation documentation [here](https://docs.marklogic.com/guide/installation/procedures#id_84772).
 
@@ -97,7 +97,7 @@ To create an uninitialized MarkLogic Server with [Docker CLI](https://docs.docke
 
 ```
 $ docker run -d -it -p 8000:8000 -p 8001:8001 -p 8002:8002 \
-     marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+     marklogicdb/marklogic-db:11.0.0-centos-1.0.0
 ```
 The example output will contain a hash of the image ID: `f484a784d99838a918e384eca5d5c0a35e7a4b0f0545d1389e31a65d57b2573d`
 
@@ -131,7 +131,7 @@ $ docker run -d -it -p 8000:8000 -p 8001:8001 -p 8002:8002 \
      -e MARKLOGIC_INIT=true \
      -e MARKLOGIC_ADMIN_USERNAME={insert admin username} \
      -e MARKLOGIC_ADMIN_PASSWORD={insert admin password} \
-     marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+     marklogicdb/marklogic-db:11.0.0-centos-1.0.0
 ```
 
 Above command will start a Docker container `MarkLogic_cont_1` running MarkLogic Server and associate the named Docker volume `MarkLogic_vol_1` with it.
@@ -246,7 +246,7 @@ Create these files on your host machine: `marklogic-centos.yaml`, `mldb_admin_us
 version: '3.6'
 services:
     bootstrap:
-      image: marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+      image: marklogicdb/marklogic-db:11.0.0-centos-1.0.0
       container_name: bootstrap
       hostname: bootstrap
       dns_search: ""
@@ -331,7 +331,7 @@ The following is an example of a three-node MarkLogic server cluster created usi
 version: '3.6'
 services:
     bootstrap_3n:
-      image: marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+      image: marklogicdb/marklogic-db:11.0.0-centos-1.0.0
       container_name: bootstrap_3n
       hostname: bootstrap_3n
       dns_search: ""
@@ -351,7 +351,7 @@ services:
       networks:
       - external_net
     node2:
-      image: marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+      image: marklogicdb/marklogic-db:11.0.0-centos-1.0.0
       container_name: node2
       hostname: node2
       dns_search: ""
@@ -375,7 +375,7 @@ services:
       networks:
       - external_net
     node3:
-      image: marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+      image: marklogicdb/marklogic-db:11.0.0-centos-1.0.0
       container_name: node3
       hostname: node3
       dns_search: ""
@@ -472,7 +472,7 @@ Using Docker secrets, username and password information are secured when transmi
 version: '3.6'
 services:
     bootstrap:
-      image: marklogic-centos/marklogic-server-centos:10.0-9.1-n
+      image: marklogic-centos/marklogic-server-centos:11.0.0-centos-1.0.0
       hostname: bootstrap
       dns_search: ""
       environment:
@@ -497,7 +497,7 @@ services:
       networks:
       - external_net
     node2:
-      image: marklogic-centos/marklogic-server-centos:10.0-9.1-n
+      image: marklogic-centos/marklogic-server-centos:11.0.0-centos-1.0.0
       hostname: node2
       dns_search: ""
       environment:
@@ -525,7 +525,7 @@ services:
       networks:
       - external_net
     node3:
-      image: marklogic-centos/marklogic-server-centos:10.0-9.1-n
+      image: marklogic-centos/marklogic-server-centos:11.0.0-centos-1.0.0
       hostname: node3
       dns_search: ""
       environment:
@@ -661,7 +661,7 @@ $ docker run -d -it -p 7100:8000 -p 7101:8001 -p 7102:8002 \
      --mount src=MarkLogicVol,dst=/var/opt/MarkLogic \
      --network ml-cluster-network \
      --dns-search "marklogic.com" \
-     marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+     marklogicdb/marklogic-db:11.0.0-centos-1.0.0
 ```
 If successful, the command will output the ID for the new container. Give the container a couple of minutes to get initialized. Continue with the next section to create additional nodes for the cluster.
 
@@ -688,7 +688,7 @@ $ docker run -d -it -p 7200:8000 -p 7201:8001 -p 7202:8002 \
      -e MARKLOGIC_GROUP=dnode \
      --mount src=MarkLogicVol,dst=/var/opt/MarkLogic \
      --network ml-cluster-network \
-     marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+     marklogicdb/marklogic-db:11.0.0-centos-1.0.0
 ```
 
 When you complete these steps, you will have multiple containers; one on each VM, and all connected to each other on the 'ml-cluster-network' network. All the containers will be part of same cluster.
@@ -698,7 +698,7 @@ When you complete these steps, you will have multiple containers; one on each VM
 MarkLogic has extensive documentation about upgrades, see [https://docs.marklogic.com/guide/relnotes/chap2](https://docs.marklogic.com/guide/relnotes/chap2). Other than the uninstall and install of the MarkLogic RPMs, the overall processes and compatibility notes for upgrades remain the same when you run MarkLogic in containers. Instead of uninstalling and installing the MarkLogic RPMs, use the following procedure to upgrade a container instance to a newer release of MarkLogic. Be sure to follow the sequence described in the documentation for rolling upgrades [https://docs.marklogic.com/guide/admin/rolling-upgrades](https://docs.marklogic.com/guide/admin/rolling-upgrades) if you need to upgrade with zero downtime.
 
 To upgrade MarkLogic Docker from release 10.x to the latest release, perform following steps:
-Note: In the below example, we are upgrading the container to marklogic-server:10.0-9.1-centos-1.0.0.
+Note: In the below example, we are upgrading the container to marklogic-server:11.0.0-centos-1.0.0.
 
 1. Stop the MarkLogic Docker container.
 Use following command to stop the container:
@@ -714,7 +714,7 @@ $ docker run -d -it -p 8000:8000 -p 8001:8001 -p 8002:8002 \
      -e MARKLOGIC_INIT=true \
      -e MARKLOGIC_ADMIN_USERNAME={insert admin username} \
      -e MARKLOGIC_ADMIN_PASSWORD={insert admin password} \
-    marklogicdb/marklogic-db:10.0-9.1-centos-1.0.0
+    marklogicdb/marklogic-db:11.0.0-centos-1.0.0
 ```
 3. In a browser, open the MarkLogic Admin Interface for the container (http://<vm_ip>:8001/).
 4. When prompted by the Admin Interface to upgrade the databases and configuration files, click the Ok button to confirm the upgrade.
@@ -732,7 +732,7 @@ $ docker run -d -it -p 7000:8000 -p 7001:8001 -p 7002:8002 \
      -e MARKLOGIC_INIT=true \
      -e MARKLOGIC_ADMIN_USERNAME={insert admin username} \
      -e MARKLOGIC_ADMIN_PASSWORD={insert admin password} \
-     marklogicdb/marklogic-db:10.0-9.1-centos-1.0.0
+     marklogicdb/marklogic-db:11.0.0-centos-1.0.0
 ```
 The /space mounted on the Docker volume can now be used as backup directory for backing up/restoring a database using the procedures described in the MarkLogic documentation: https://docs.marklogic.com/guide/admin/backup_restore
 
@@ -752,9 +752,9 @@ The following is a set of steps to run to access a container while it is running
 2. Get the container ID for the MarkLogic container running on the machine. To do this, run the following command:
 
 ```
-$ docker container ps --filter ancestor=marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0 -q
+$ docker container ps --filter ancestor=marklogicdb/marklogic-db:11.0.0-centos-1.0.0 -q
 ```
-In this example command `marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0` is an image ID. Your container ID may be different for your machine.
+In this example command `marklogicdb/marklogic-db:11.0.0-centos-1.0.0` is an image ID. Your container ID may be different for your machine.
 
 Example output:
 
@@ -772,7 +772,7 @@ Here's an example of unfiltered output from that command:
 
 ```
 CONTAINER ID   IMAGE                                                        COMMAND                  CREATED          STATUS          PORTS                                  NAMES
-f484a784d998   marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0   "/usr/local/bin/star…"   16 minutes ago   Up 16 minutes   25/tcp, 7997-7999/tcp, 8003-8010/tcp, 0.0.0.0:8000-8002 8000-8002/tcp   vibrant_burnell
+f484a784d998   marklogicdb/marklogic-db:11.0.0-centos-1.0.0   "/usr/local/bin/star…"   16 minutes ago   Up 16 minutes   25/tcp, 7997-7999/tcp, 8003-8010/tcp, 0.0.0.0:8000-8002 8000-8002/tcp   vibrant_burnell
 ```
 
 3. Run a command to access a remote shell on the container.
@@ -863,7 +863,7 @@ If the process is successful, a message saying the node has left the swarm will
 
 # Known Issues and Limitations
 
-10.0-9.5-centos-1.0.0
+11.0.0-centos-1.0.0
 
 1. Enabling huge pages for clusters containing single-host, multi-container configurations may lead to failure, due to incorrect memory allocation. MarkLogic recommends that you disable huge pages in such architectures.
 2. Database replication will only work for configurations having a single container per host, with matching hostname.
@@ -908,3 +908,4 @@ If the process is successful, a message saying the node has left the swarm will
 - 10.0-9.2-centos-1.0.0-ea4 - MarkLogic Developer Docker image includes all features and is limited to developer use
 - 10.0-9.4-centos-1.0.0-ea4 - MarkLogic Developer Docker image includes all features and is limited to developer use
 - 10.0-9.5-centos-1.0.0-ea4 - MarkLogic Developer Docker image includes all features and is limited to developer use
+- 10.0-9.5-centos-1.0.0 - MarkLogic Developer Docker image includes all features and is limited to developer use

docker-compose/marklogic-centos.yaml

@@ -2,7 +2,7 @@
 version: '3.6'
 services:
     bootstrap:
-      image: marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+      image: marklogicdb/marklogic-db:11.0.0-centos-1.0.0
       container_name: bootstrap
       hostname: bootstrap
       dns_search: ""

docker-compose/marklogic-cluster-centos.yaml

@@ -2,7 +2,7 @@
 version: '3.6'
 services:
     bootstrap_3n:
-      image: marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+      image: marklogicdb/marklogic-db:11.0.0-centos-1.0.0
       container_name: bootstrap_3n
       hostname: bootstrap_3n
       dns_search: ""
@@ -22,7 +22,7 @@ services:
       networks:
       - external_net
     node2:
-      image: marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+      image: marklogicdb/marklogic-db:11.0.0-centos-1.0.0
       container_name: node2
       hostname: node2
       dns_search: ""
@@ -46,7 +46,7 @@ services:
       networks:
       - external_net
     node3:
-      image: marklogicdb/marklogic-db:10.0-9.5-centos-1.0.0
+      image: marklogicdb/marklogic-db:11.0.0-centos-1.0.0
       container_name: node3
       hostname: node3
       dns_search: ""