You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ti...@apache.org on 2023/05/08 07:47:49 UTC
[pulsar-site] branch main updated: cleanup we are no longer supporting DC/OS (#561)
This is an automated email from the ASF dual-hosted git repository.
tison pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 5aa79404ec2 cleanup we are no longer supporting DC/OS (#561)
5aa79404ec2 is described below
commit 5aa79404ec2e3a0ac4e3392292aef50e02593425
Author: tison <wa...@gmail.com>
AuthorDate: Mon May 8 15:47:43 2023 +0800
cleanup we are no longer supporting DC/OS (#561)
Signed-off-by: tison <wa...@gmail.com>
---
docs/deploy-dcos.md | 185 ----------------------
static/.htaccess | 1 +
static/assets/dcos_bookie_log.png | Bin 668472 -> 0 bytes
static/assets/dcos_bookkeeper_in_zookeeper.png | Bin 264657 -> 0 bytes
static/assets/dcos_bookkeeper_run.png | Bin 524502 -> 0 bytes
static/assets/dcos_bookkeeper_status.png | Bin 115364 -> 0 bytes
static/assets/dcos_broker_in_zookeeper.png | Bin 402876 -> 0 bytes
static/assets/dcos_broker_log.png | Bin 689765 -> 0 bytes
static/assets/dcos_broker_run.png | Bin 200575 -> 0 bytes
static/assets/dcos_broker_status.png | Bin 144495 -> 0 bytes
static/assets/dcos_command_execute.png | Bin 129195 -> 0 bytes
static/assets/dcos_command_execute2.png | Bin 699589 -> 0 bytes
static/assets/dcos_consumer.png | Bin 1620672 -> 0 bytes
static/assets/dcos_grafana_dashboard.png | Bin 102136 -> 0 bytes
static/assets/dcos_grafana_endpoint.png | Bin 277004 -> 0 bytes
static/assets/dcos_metrics.png | Bin 389670 -> 0 bytes
static/assets/dcos_monitor_status.png | Bin 136506 -> 0 bytes
static/assets/dcos_producer.png | Bin 1542880 -> 0 bytes
static/assets/dcos_prom_endpoint.png | Bin 224700 -> 0 bytes
static/assets/dcos_prom_targets.png | Bin 240218 -> 0 bytes
static/assets/dcos_uninstall.png | Bin 115389 -> 0 bytes
versioned_docs/version-2.10.x/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.11.x/deploy-dcos.md | 185 ----------------------
versioned_docs/version-2.2.0/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.2.1/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.3.0/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.3.1/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.3.2/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.4.0/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.4.1/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.4.2/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.5.0/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.5.1/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.5.2/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.6.0/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.6.1/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.6.2/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.6.3/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.6.4/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.7.0/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.7.1/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.7.2/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.7.3/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.7.4/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.7.5/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.8.x/deploy-dcos.md | 200 ------------------------
versioned_docs/version-2.9.x/deploy-dcos.md | 200 ------------------------
versioned_docs/version-3.0.x/deploy-dcos.md | 185 ----------------------
versioned_sidebars/version-2.10.x-sidebars.json | 4 -
49 files changed, 1 insertion(+), 5559 deletions(-)
diff --git a/docs/deploy-dcos.md b/docs/deploy-dcos.md
deleted file mode 100644
index 0b3bd4b1a45..00000000000
--- a/docs/deploy-dcos.md
+++ /dev/null
@@ -1,185 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#work-with-connector).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
- curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-dcos marathon group add PulsarGroups.json
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) is green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-git clone https://github.com/streamlio/pulsar-java-tutorial
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-mvn clean package
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-```
-
-Execute this command to run the producer:
-
-```bash
-mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
- dcos marathon group remove /pulsar
- ```
-
diff --git a/static/.htaccess b/static/.htaccess
index 7cdcea35129..a846c6edd76 100755
--- a/static/.htaccess
+++ b/static/.htaccess
@@ -18,6 +18,7 @@ RewriteCond expr "%{REQUEST_URI} !~ m|^/docs/\d+\.\d+\.x|"
RewriteCond expr "%{REQUEST_URI} !~ m|^/docs/\d+\.\d+\.x/.*|"
RewriteRule "^docs/(.*)$" "/docs/3.0.x/$1" [R=301,DPI,L]
+RewriteRule "^docs/(.+/)?deploy-dcos/?$" "/docs/$1install-deploy-upgrade-landing" [R=301,DPI,L]
RewriteRule "^docs/(.+/)?develop-binary-protocol/?$" "/docs/$1developing-binary-protocol" [R=301,DPI,L]
RewriteRule "^docs/(.+/)?administration-dashboard/?$" "/docs/$1administration-pulsar-manager" [R=301,DPI,L]
RewriteRule "^docs/(.+/)?security-tls-keystore/?$" "/docs/$1security-tls-authentication" [R=301,DPI,L]
diff --git a/static/assets/dcos_bookie_log.png b/static/assets/dcos_bookie_log.png
deleted file mode 100644
index 31ac263847b..00000000000
Binary files a/static/assets/dcos_bookie_log.png and /dev/null differ
diff --git a/static/assets/dcos_bookkeeper_in_zookeeper.png b/static/assets/dcos_bookkeeper_in_zookeeper.png
deleted file mode 100644
index 80680bc3307..00000000000
Binary files a/static/assets/dcos_bookkeeper_in_zookeeper.png and /dev/null differ
diff --git a/static/assets/dcos_bookkeeper_run.png b/static/assets/dcos_bookkeeper_run.png
deleted file mode 100644
index 8cda68ca326..00000000000
Binary files a/static/assets/dcos_bookkeeper_run.png and /dev/null differ
diff --git a/static/assets/dcos_bookkeeper_status.png b/static/assets/dcos_bookkeeper_status.png
deleted file mode 100644
index 5e09a0c027a..00000000000
Binary files a/static/assets/dcos_bookkeeper_status.png and /dev/null differ
diff --git a/static/assets/dcos_broker_in_zookeeper.png b/static/assets/dcos_broker_in_zookeeper.png
deleted file mode 100644
index 3563e34669b..00000000000
Binary files a/static/assets/dcos_broker_in_zookeeper.png and /dev/null differ
diff --git a/static/assets/dcos_broker_log.png b/static/assets/dcos_broker_log.png
deleted file mode 100644
index dfb78a7c0ba..00000000000
Binary files a/static/assets/dcos_broker_log.png and /dev/null differ
diff --git a/static/assets/dcos_broker_run.png b/static/assets/dcos_broker_run.png
deleted file mode 100644
index 9afeadb57b4..00000000000
Binary files a/static/assets/dcos_broker_run.png and /dev/null differ
diff --git a/static/assets/dcos_broker_status.png b/static/assets/dcos_broker_status.png
deleted file mode 100644
index d42f233dd71..00000000000
Binary files a/static/assets/dcos_broker_status.png and /dev/null differ
diff --git a/static/assets/dcos_command_execute.png b/static/assets/dcos_command_execute.png
deleted file mode 100644
index a5c4c4281ab..00000000000
Binary files a/static/assets/dcos_command_execute.png and /dev/null differ
diff --git a/static/assets/dcos_command_execute2.png b/static/assets/dcos_command_execute2.png
deleted file mode 100644
index 5670cd0a9b2..00000000000
Binary files a/static/assets/dcos_command_execute2.png and /dev/null differ
diff --git a/static/assets/dcos_consumer.png b/static/assets/dcos_consumer.png
deleted file mode 100644
index 8b9b64afb44..00000000000
Binary files a/static/assets/dcos_consumer.png and /dev/null differ
diff --git a/static/assets/dcos_grafana_dashboard.png b/static/assets/dcos_grafana_dashboard.png
deleted file mode 100644
index b937003dd39..00000000000
Binary files a/static/assets/dcos_grafana_dashboard.png and /dev/null differ
diff --git a/static/assets/dcos_grafana_endpoint.png b/static/assets/dcos_grafana_endpoint.png
deleted file mode 100644
index 20e5894435d..00000000000
Binary files a/static/assets/dcos_grafana_endpoint.png and /dev/null differ
diff --git a/static/assets/dcos_metrics.png b/static/assets/dcos_metrics.png
deleted file mode 100644
index 7e065126544..00000000000
Binary files a/static/assets/dcos_metrics.png and /dev/null differ
diff --git a/static/assets/dcos_monitor_status.png b/static/assets/dcos_monitor_status.png
deleted file mode 100644
index bfc20892370..00000000000
Binary files a/static/assets/dcos_monitor_status.png and /dev/null differ
diff --git a/static/assets/dcos_producer.png b/static/assets/dcos_producer.png
deleted file mode 100644
index 21a7cfcdf2c..00000000000
Binary files a/static/assets/dcos_producer.png and /dev/null differ
diff --git a/static/assets/dcos_prom_endpoint.png b/static/assets/dcos_prom_endpoint.png
deleted file mode 100644
index 36c9b8c83e2..00000000000
Binary files a/static/assets/dcos_prom_endpoint.png and /dev/null differ
diff --git a/static/assets/dcos_prom_targets.png b/static/assets/dcos_prom_targets.png
deleted file mode 100644
index 0d362f3284f..00000000000
Binary files a/static/assets/dcos_prom_targets.png and /dev/null differ
diff --git a/static/assets/dcos_uninstall.png b/static/assets/dcos_uninstall.png
deleted file mode 100644
index 4ef4f569fa2..00000000000
Binary files a/static/assets/dcos_uninstall.png and /dev/null differ
diff --git a/versioned_docs/version-2.10.x/deploy-dcos.md b/versioned_docs/version-2.10.x/deploy-dcos.md
deleted file mode 100644
index b84c0b2aaf9..00000000000
--- a/versioned_docs/version-2.10.x/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) is green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.11.x/deploy-dcos.md b/versioned_docs/version-2.11.x/deploy-dcos.md
deleted file mode 100644
index 0b3bd4b1a45..00000000000
--- a/versioned_docs/version-2.11.x/deploy-dcos.md
+++ /dev/null
@@ -1,185 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#work-with-connector).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
- curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-dcos marathon group add PulsarGroups.json
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) is green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-git clone https://github.com/streamlio/pulsar-java-tutorial
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-mvn clean package
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-```
-
-Execute this command to run the producer:
-
-```bash
-mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
- dcos marathon group remove /pulsar
- ```
-
diff --git a/versioned_docs/version-2.2.0/deploy-dcos.md b/versioned_docs/version-2.2.0/deploy-dcos.md
deleted file mode 100644
index f64ef19f656..00000000000
--- a/versioned_docs/version-2.2.0/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploying Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you will need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your DC/OS cluster's resources.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command will deploy Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When running DC/OS, a ZooKeeper cluster is already running at `master.mesos:2181`, thus there's no need to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that they have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed info, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, there are 3 bookies under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed info, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you'll see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL will display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that we have a fully deployed Pulsar cluster, we can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-There's a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo that you can clone. This repo contains a simple Pulsar consumer and producer (more info can be found in the repo's `README` file).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. Endpoint details for each broker instance can be fetched from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. This can also be replaced by the client agent IP address.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it will produce more messages.
-
-Now compile the project code using command:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.2.1/deploy-dcos.md b/versioned_docs/version-2.2.1/deploy-dcos.md
deleted file mode 100644
index 0ea26e6fe99..00000000000
--- a/versioned_docs/version-2.2.1/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) are green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.3.0/deploy-dcos.md b/versioned_docs/version-2.3.0/deploy-dcos.md
deleted file mode 100644
index 0ea26e6fe99..00000000000
--- a/versioned_docs/version-2.3.0/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) are green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.3.1/deploy-dcos.md b/versioned_docs/version-2.3.1/deploy-dcos.md
deleted file mode 100644
index 0ea26e6fe99..00000000000
--- a/versioned_docs/version-2.3.1/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) are green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.3.2/deploy-dcos.md b/versioned_docs/version-2.3.2/deploy-dcos.md
deleted file mode 100644
index 0ea26e6fe99..00000000000
--- a/versioned_docs/version-2.3.2/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) are green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.4.0/deploy-dcos.md b/versioned_docs/version-2.4.0/deploy-dcos.md
deleted file mode 100644
index 0ea26e6fe99..00000000000
--- a/versioned_docs/version-2.4.0/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) are green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.4.1/deploy-dcos.md b/versioned_docs/version-2.4.1/deploy-dcos.md
deleted file mode 100644
index 0ea26e6fe99..00000000000
--- a/versioned_docs/version-2.4.1/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) are green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.4.2/deploy-dcos.md b/versioned_docs/version-2.4.2/deploy-dcos.md
deleted file mode 100644
index 0ea26e6fe99..00000000000
--- a/versioned_docs/version-2.4.2/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) are green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.5.0/deploy-dcos.md b/versioned_docs/version-2.5.0/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.5.0/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.5.1/deploy-dcos.md b/versioned_docs/version-2.5.1/deploy-dcos.md
deleted file mode 100644
index 0ea26e6fe99..00000000000
--- a/versioned_docs/version-2.5.1/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) are green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.5.2/deploy-dcos.md b/versioned_docs/version-2.5.2/deploy-dcos.md
deleted file mode 100644
index 0ea26e6fe99..00000000000
--- a/versioned_docs/version-2.5.2/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) are green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.6.0/deploy-dcos.md b/versioned_docs/version-2.6.0/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.6.0/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.6.1/deploy-dcos.md b/versioned_docs/version-2.6.1/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.6.1/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.6.2/deploy-dcos.md b/versioned_docs/version-2.6.2/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.6.2/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.6.3/deploy-dcos.md b/versioned_docs/version-2.6.3/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.6.3/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.6.4/deploy-dcos.md b/versioned_docs/version-2.6.4/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.6.4/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.7.0/deploy-dcos.md b/versioned_docs/version-2.7.0/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.7.0/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.7.1/deploy-dcos.md b/versioned_docs/version-2.7.1/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.7.1/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.7.2/deploy-dcos.md b/versioned_docs/version-2.7.2/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.7.2/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.7.3/deploy-dcos.md b/versioned_docs/version-2.7.3/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.7.3/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.7.4/deploy-dcos.md b/versioned_docs/version-2.7.4/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.7.4/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.7.5/deploy-dcos.md b/versioned_docs/version-2.7.5/deploy-dcos.md
deleted file mode 100644
index ce2aafea4c4..00000000000
--- a/versioned_docs/version-2.7.5/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all builtin [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains .
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.8.x/deploy-dcos.md b/versioned_docs/version-2.8.x/deploy-dcos.md
deleted file mode 100644
index b1a8b2fff95..00000000000
--- a/versioned_docs/version-2.8.x/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-If you want to enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, you can choose to use `apachepulsar/pulsar-all` image instead of
-`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system used for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool that [Mesosphere](https://mesosphere.com/) creates and maintains.
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-In order to run Pulsar on DC/OS, you need the following:
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` according to match your resources of DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster already runs at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click on the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications in the process of deploying.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click on the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, 3 [bookies](reference-terminology.md#bookie) should be shown as green, which means that the bookies have been deployed successfully and are now running.
-
-
-
-You can also click into each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker Group
-
-Similar to the BookKeeper group above, click into the **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click into each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in Zookeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor Group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click into the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. The [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets) URL display all the bookies and brokers.
-
-
-
-### Grafana
-
-Click into `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file of the repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java).
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent, which runs a broker. The client agent IP address can also replace this.
-
-Now, change the message number from 10 to 10000000 in main method of [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) so that it can produce more messages.
-
-Now compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You can see the producer producing messages and the consumer consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer run, you can access running metrics information from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in the following two ways:
-
-1. Using the DC/OS GUI, you can choose **Delete** at the right end of Pulsar group.
-
- 
-
-2. You can use the following command:
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-2.9.x/deploy-dcos.md b/versioned_docs/version-2.9.x/deploy-dcos.md
deleted file mode 100644
index b84c0b2aaf9..00000000000
--- a/versioned_docs/version-2.9.x/deploy-dcos.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
-original_id: deploy-dcos
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
-
- $ curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
-
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-
-$ dcos marathon group add PulsarGroups.json
-
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) is green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-
-$ git clone https://github.com/streamlio/pulsar-java-tutorial
-
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-
-$ mvn clean package
-
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-
-```
-
-Execute this command to run the producer:
-
-```bash
-
-$ mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
-
- $ dcos marathon group remove /pulsar
-
- ```
-
diff --git a/versioned_docs/version-3.0.x/deploy-dcos.md b/versioned_docs/version-3.0.x/deploy-dcos.md
deleted file mode 100644
index 0b3bd4b1a45..00000000000
--- a/versioned_docs/version-3.0.x/deploy-dcos.md
+++ /dev/null
@@ -1,185 +0,0 @@
----
-id: deploy-dcos
-title: Deploy Pulsar on DC/OS
-sidebar_label: "DC/OS"
----
-
-:::tip
-
-To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#work-with-connector).
-
-:::
-
-[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
-
-Apache Pulsar is available as a [Marathon Application Group](https://mesosphere.github.io/marathon/docs/application-groups.html), which runs multiple applications as manageable sets.
-
-## Prerequisites
-
-You need to prepare your environment before running Pulsar on DC/OS.
-
-* DC/OS version [1.9](https://docs.mesosphere.com/1.9/) or higher
-* A [DC/OS cluster](https://docs.mesosphere.com/1.9/installing/) with at least three agent nodes
-* The [DC/OS CLI tool](https://docs.mesosphere.com/1.9/cli/install/) installed
-* The [`PulsarGroups.json`](https://github.com/apache/pulsar/blob/master/deployment/dcos/PulsarGroups.json) configuration file from the Pulsar GitHub repo.
-
- ```bash
- curl -O https://raw.githubusercontent.com/apache/pulsar/master/deployment/dcos/PulsarGroups.json
- ```
-
-Each node in the DC/OS-managed Mesos cluster must have at least:
-
-* 4 CPU
-* 4 GB of memory
-* 60 GB of total persistent disk
-
-Alternatively, you can change the configuration in `PulsarGroups.json` accordingly to match your resources of the DC/OS cluster.
-
-## Deploy Pulsar using the DC/OS command interface
-
-You can deploy Pulsar on DC/OS using this command:
-
-```bash
-dcos marathon group add PulsarGroups.json
-```
-
-This command deploys Docker container instances in three groups, which together comprise a Pulsar cluster:
-
-* 3 bookies (1 [bookie](reference-terminology.md#bookie) on each agent node and 1 [bookie recovery](http://bookkeeper.apache.org/docs/latest/admin/autorecovery/) instance)
-* 3 Pulsar [brokers](reference-terminology.md#broker) (1 broker on each node and 1 admin instance)
-* 1 [Prometheus](http://prometheus.io/) instance and 1 [Grafana](https://grafana.com/) instance
-
-
-> When you run DC/OS, a ZooKeeper cluster will be running at `master.mesos:2181`, thus you do not have to install or start up ZooKeeper separately.
-
-After executing the `dcos` command above, click the **Services** tab in the DC/OS [GUI interface](https://docs.mesosphere.com/latest/gui/), which you can access at [http://m1.dcos](http://m1.dcos) in this example. You should see several applications during the deployment.
-
-
-
-
-
-## The BookKeeper group
-
-To monitor the status of the BookKeeper cluster deployment, click the **bookkeeper** group in the parent **pulsar** group.
-
-
-
-At this point, the status of the 3 [bookies](reference-terminology.md#bookie) is green, which means that the bookies have been deployed successfully and are running.
-
-
-
-You can also click each bookie instance to get more detailed information, such as the bookie running log.
-
-
-
-To display information about the BookKeeper in ZooKeeper, you can visit [http://m1.dcos/exhibitor](http://m1.dcos/exhibitor). In this example, 3 bookies are under the `available` directory.
-
-
-
-## The Pulsar broker group
-
-Similar to the BookKeeper group above, click **brokers** to check the status of the Pulsar brokers.
-
-
-
-
-
-You can also click each broker instance to get more detailed information, such as the broker running log.
-
-
-
-Broker cluster information in ZooKeeper is also available through the web UI. In this example, you can see that the `loadbalance` and `managed-ledgers` directories have been created.
-
-
-
-## Monitor group
-
-The **monitory** group consists of Prometheus and Grafana.
-
-
-
-### Prometheus
-
-Click the instance of `prom` to get the endpoint of Prometheus, which is `192.168.65.121:9090` in this example.
-
-
-
-If you click that endpoint, you can see the Prometheus dashboard. All the bookies and brokers are listed on [http://192.168.65.121:9090/targets](http://192.168.65.121:9090/targets).
-
-
-
-### Grafana
-
-Click `grafana` to get the endpoint for Grafana, which is `192.168.65.121:3000` in this example.
-
-
-
-If you click that endpoint, you can access the Grafana dashboard.
-
-
-
-## Run a simple Pulsar consumer and producer on DC/OS
-
-Now that you have a fully deployed Pulsar cluster, you can run a simple consumer and producer to show Pulsar on DC/OS in action.
-
-### Download and prepare the Pulsar Java tutorial
-
-You can clone a [Pulsar Java tutorial](https://github.com/streamlio/pulsar-java-tutorial) repo. This repo contains a simple Pulsar consumer and producer (you can find more information in the `README` file in this repo).
-
-```bash
-git clone https://github.com/streamlio/pulsar-java-tutorial
-```
-
-Change the `SERVICE_URL` from `pulsar://localhost:6650` to `pulsar://a1.dcos:6650` in both [`ConsumerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ConsumerTutorial.java) file and [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file.
-
-The `pulsar://a1.dcos:6650` endpoint is for the broker service. You can fetch the endpoint details for each broker instance from the DC/OS GUI. `a1.dcos` is a DC/OS client agent that runs a broker, and you can replace it with the client agent IP address.
-
-Now, you can change the message number from 10 to 10000000 in the main method in [`ProducerTutorial.java`](https://github.com/streamlio/pulsar-java-tutorial/blob/master/src/main/java/tutorial/ProducerTutorial.java) file to produce more messages.
-
-Then, you can compile the project code using the command below:
-
-```bash
-mvn clean package
-```
-
-### Run the consumer and producer
-
-Execute this command to run the consumer:
-
-```bash
-mvn exec:java -Dexec.mainClass="tutorial.ConsumerTutorial"
-```
-
-Execute this command to run the producer:
-
-```bash
-mvn exec:java -Dexec.mainClass="tutorial.ProducerTutorial"
-```
-
-You see that the producer is producing messages and the consumer is consuming messages through the DC/OS GUI.
-
-
-
-
-
-### View Grafana metric output
-
-While the producer and consumer are running, you can access the running metrics from Grafana.
-
-
-
-
-## Uninstall Pulsar
-
-You can shut down and uninstall the `pulsar` application from DC/OS at any time in one of the following two ways:
-
-1. Click the three dots at the right end of Pulsar group and choose **Delete** on the DC/OS GUI.
-
- 
-
-2. Use the command below.
-
- ```bash
- dcos marathon group remove /pulsar
- ```
-
diff --git a/versioned_sidebars/version-2.10.x-sidebars.json b/versioned_sidebars/version-2.10.x-sidebars.json
index 3ff9b896718..aa22f441d0d 100644
--- a/versioned_sidebars/version-2.10.x-sidebars.json
+++ b/versioned_sidebars/version-2.10.x-sidebars.json
@@ -310,10 +310,6 @@
"type": "doc",
"id": "version-2.10.x/deploy-bare-metal-multi-cluster"
},
- {
- "type": "doc",
- "id": "version-2.10.x/deploy-dcos"
- },
{
"type": "doc",
"id": "version-2.10.x/deploy-docker"