You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/04/28 03:00:26 UTC

[GitHub] [pulsar] Huanli-Meng commented on a change in pull request #10409: Add docker compose

Huanli-Meng commented on a change in pull request #10409:
URL: https://github.com/apache/pulsar/pull/10409#discussion_r621764462



##########
File path: docker-compose/kitchen-sink/README.MD
##########
@@ -0,0 +1,76 @@
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+-->
+# Apache Pulsar Docker Compose
+
+In this folder path, run the following command to start the cluster.
+
+```
+docker-compose up
+```
+
+This will start individual containers for the following services:

Review comment:
       ```suggestion
   This command starts individual containers for the following services:
   ```

##########
File path: docker-compose/kitchen-sink/README.MD
##########
@@ -0,0 +1,76 @@
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+-->
+# Apache Pulsar Docker Compose
+
+In this folder path, run the following command to start the cluster.
+
+```
+docker-compose up
+```
+
+This will start individual containers for the following services:
+
+- ZooKeeper (3)
+- BookKeeper (3)
+- Pulsar (3)
+- Proxy (1)
+- WebSocket (1)
+- Function (1)
+- Pulsar Manager (1)
+- SQL (1)
+
+## Motivation
+
+Most of what is available with Docker and Apache Pulsar uses the standalone version of Apache Pulsar, which is fantastic. But, users need to take care of all of the complexity of Apache Pulsar.
+
+This was created to create a Docker implementation that allows each individual part to be exposed to learn how it all fits together.
+
+## URLs
+
+Assuming localhost the following endpoint will be available:
+
+[web-dashboard - http://localhost:9527](http://localhost:9527) pulsar-admin dashboard, showing various metrics and metadata information about the cluster
+
+[broker-admin - http://localhost:8080](http://localhost:8080) access broker rest interface
+
+[broker-service-url - pulsar//:locahost:6650](pulsar//:locahost:6650)  broker service URL for use with producers and consumers
+
+You can shut it down with the following command in folder path:
+
+```
+docker-compose down
+```
+
+You may need to delete the `./data` folder created by the Pulsar Manager.
+
+## Notes
+
+Docker is notorious for being difficult to manage the startup order of containers. In Pulsar, startup order matters. This may cause some containers to fail and have to be restarted.

Review comment:
       ```suggestion
   Docker is notorious for being difficult to manage the startup order of containers. In Pulsar, startup order is very significant. This may cause some containers to fail and have to be restarted.
   ```

##########
File path: docker-compose/kitchen-sink/README.MD
##########
@@ -0,0 +1,76 @@
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+-->
+# Apache Pulsar Docker Compose
+
+In this folder path, run the following command to start the cluster.
+
+```
+docker-compose up
+```
+
+This will start individual containers for the following services:
+
+- ZooKeeper (3)
+- BookKeeper (3)
+- Pulsar (3)
+- Proxy (1)
+- WebSocket (1)
+- Function (1)
+- Pulsar Manager (1)
+- SQL (1)
+
+## Motivation
+
+Most of what is available with Docker and Apache Pulsar uses the standalone version of Apache Pulsar, which is fantastic. But, users need to take care of all of the complexity of Apache Pulsar.
+
+This was created to create a Docker implementation that allows each individual part to be exposed to learn how it all fits together.
+
+## URLs
+
+Assuming localhost the following endpoint will be available:
+
+[web-dashboard - http://localhost:9527](http://localhost:9527) pulsar-admin dashboard, showing various metrics and metadata information about the cluster
+
+[broker-admin - http://localhost:8080](http://localhost:8080) access broker rest interface

Review comment:
       ```suggestion
   - [broker-admin - http://localhost:8080](http://localhost:8080): access the broker REST interface
   ```

##########
File path: docker-compose/kitchen-sink/README.MD
##########
@@ -0,0 +1,76 @@
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+-->
+# Apache Pulsar Docker Compose
+
+In this folder path, run the following command to start the cluster.
+
+```
+docker-compose up
+```
+
+This will start individual containers for the following services:
+
+- ZooKeeper (3)
+- BookKeeper (3)
+- Pulsar (3)
+- Proxy (1)
+- WebSocket (1)
+- Function (1)
+- Pulsar Manager (1)
+- SQL (1)
+
+## Motivation
+
+Most of what is available with Docker and Apache Pulsar uses the standalone version of Apache Pulsar, which is fantastic. But, users need to take care of all of the complexity of Apache Pulsar.
+
+This was created to create a Docker implementation that allows each individual part to be exposed to learn how it all fits together.
+
+## URLs
+
+Assuming localhost the following endpoint will be available:
+
+[web-dashboard - http://localhost:9527](http://localhost:9527) pulsar-admin dashboard, showing various metrics and metadata information about the cluster

Review comment:
       ```suggestion
   - [web-dashboard - http://localhost:9527](http://localhost:9527): pulsar-admin dashboard, showing various metrics and metadata information about the cluster
   ```

##########
File path: docker-compose/kitchen-sink/README.MD
##########
@@ -0,0 +1,76 @@
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+-->
+# Apache Pulsar Docker Compose
+
+In this folder path, run the following command to start the cluster.
+
+```
+docker-compose up
+```
+
+This will start individual containers for the following services:
+
+- ZooKeeper (3)
+- BookKeeper (3)
+- Pulsar (3)
+- Proxy (1)
+- WebSocket (1)
+- Function (1)
+- Pulsar Manager (1)
+- SQL (1)
+
+## Motivation
+
+Most of what is available with Docker and Apache Pulsar uses the standalone version of Apache Pulsar, which is fantastic. But, users need to take care of all of the complexity of Apache Pulsar.
+
+This was created to create a Docker implementation that allows each individual part to be exposed to learn how it all fits together.
+
+## URLs
+
+Assuming localhost the following endpoint will be available:
+
+[web-dashboard - http://localhost:9527](http://localhost:9527) pulsar-admin dashboard, showing various metrics and metadata information about the cluster
+
+[broker-admin - http://localhost:8080](http://localhost:8080) access broker rest interface
+
+[broker-service-url - pulsar//:locahost:6650](pulsar//:locahost:6650)  broker service URL for use with producers and consumers

Review comment:
       ```suggestion
   - [broker-service-url - pulsar//:locahost:6650](pulsar//:locahost:6650): broker service URL for use with producers and consumers
   ```

##########
File path: docker-compose/kitchen-sink/README.MD
##########
@@ -0,0 +1,76 @@
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+-->
+# Apache Pulsar Docker Compose
+
+In this folder path, run the following command to start the cluster.
+
+```
+docker-compose up
+```
+
+This will start individual containers for the following services:
+
+- ZooKeeper (3)
+- BookKeeper (3)
+- Pulsar (3)
+- Proxy (1)
+- WebSocket (1)
+- Function (1)
+- Pulsar Manager (1)
+- SQL (1)
+
+## Motivation
+
+Most of what is available with Docker and Apache Pulsar uses the standalone version of Apache Pulsar, which is fantastic. But, users need to take care of all of the complexity of Apache Pulsar.
+
+This was created to create a Docker implementation that allows each individual part to be exposed to learn how it all fits together.
+
+## URLs
+
+Assuming localhost the following endpoint will be available:
+
+[web-dashboard - http://localhost:9527](http://localhost:9527) pulsar-admin dashboard, showing various metrics and metadata information about the cluster
+
+[broker-admin - http://localhost:8080](http://localhost:8080) access broker rest interface
+
+[broker-service-url - pulsar//:locahost:6650](pulsar//:locahost:6650)  broker service URL for use with producers and consumers
+
+You can shut it down with the following command in folder path:

Review comment:
       ```suggestion
   You can shut it down with the following command in the folder path:
   ```

##########
File path: docker-compose/kitchen-sink/README.MD
##########
@@ -0,0 +1,76 @@
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+-->
+# Apache Pulsar Docker Compose
+
+In this folder path, run the following command to start the cluster.
+
+```
+docker-compose up
+```
+
+This will start individual containers for the following services:
+
+- ZooKeeper (3)
+- BookKeeper (3)
+- Pulsar (3)
+- Proxy (1)
+- WebSocket (1)
+- Function (1)
+- Pulsar Manager (1)
+- SQL (1)
+
+## Motivation
+
+Most of what is available with Docker and Apache Pulsar uses the standalone version of Apache Pulsar, which is fantastic. But, users need to take care of all of the complexity of Apache Pulsar.
+
+This was created to create a Docker implementation that allows each individual part to be exposed to learn how it all fits together.
+
+## URLs
+
+Assuming localhost the following endpoint will be available:

Review comment:
       ```suggestion
   Assume that localhost addresses for the following endpoints are available:
   ```

##########
File path: docker-compose/kitchen-sink/README.MD
##########
@@ -0,0 +1,76 @@
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+-->
+# Apache Pulsar Docker Compose
+
+In this folder path, run the following command to start the cluster.
+
+```
+docker-compose up
+```
+
+This will start individual containers for the following services:
+
+- ZooKeeper (3)
+- BookKeeper (3)
+- Pulsar (3)
+- Proxy (1)
+- WebSocket (1)
+- Function (1)
+- Pulsar Manager (1)
+- SQL (1)
+
+## Motivation
+
+Most of what is available with Docker and Apache Pulsar uses the standalone version of Apache Pulsar, which is fantastic. But, users need to take care of all of the complexity of Apache Pulsar.
+
+This was created to create a Docker implementation that allows each individual part to be exposed to learn how it all fits together.

Review comment:
       ```suggestion
   This aims to create a Docker implementation that allows each individual part to be exposed to learn how it all fits together.
   ```




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org