This is an automated email from the ASF dual-hosted git repository.
sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-manager.git
The following commit(s) were added to refs/heads/master by this push:
new 86b74f5 Add a docker compose file and update README (#287)
86b74f5 is described below
commit 86b74f53bdee9b698a58e21c2a2de003927e1300
Author: Sijie Guo <[email protected]>
AuthorDate: Sat Apr 11 01:49:19 2020 -0700
Add a docker compose file and update README (#287)
* Add a docker compose file and update README
*Motivation*
- Add a docker compose file to show how to deploy a Pulsar Manager with a
Pulsar cluster.
- Update README on how to install Pulsar Manager
* Fix github checkout action
---
.github/workflows/gradle.yml | 2 +-
.gitignore | 6 +-
README.md | 287 +++++++++++++++++++++++++--------------
docker/data/.keep | 0
docker/docker-compose.yml | 30 ++++
docs/img/pulsar-manager-arch.png | Bin 0 -> 20444 bytes
6 files changed, 222 insertions(+), 103 deletions(-)
diff --git a/.github/workflows/gradle.yml b/.github/workflows/gradle.yml
index b8d0e2d..0f94866 100644
--- a/.github/workflows/gradle.yml
+++ b/.github/workflows/gradle.yml
@@ -14,7 +14,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- - uses: actions/checkout@v1
+ - uses: actions/checkout@v2
- name: Set up JDK 1.8
uses: actions/setup-java@v1
with:
diff --git a/.gitignore b/.gitignore
index df371de..77895da 100644
--- a/.gitignore
+++ b/.gitignore
@@ -48,4 +48,8 @@ front-end/data/
dbdata
src/main/resources/local.properties
-*.key
\ No newline at end of file
+*.key
+
+# Docker
+docker/data
+data
\ No newline at end of file
diff --git a/README.md b/README.md
index f9dc381..44931b6 100644
--- a/README.md
+++ b/README.md
@@ -2,158 +2,252 @@
Apache Pulsar manager is a web-based GUI management tool for managing and
monitoring Pulsar.
-## Feature
+A Pulsar Manager is capable of managing multiple Pulsar clusters. A Pulsar
instance or a group
+of Pulsar clusters is defined as an `Environment` in Pulsar Manager. You can
create as many environments
+as you can. The following diagram illustrates the overall architecture of a
Pulsar Manager.
-* Tenants Management
-* Namespaces Management
-* Topics Management
-* Subscriptions Management
-* Brokers Management
-* Clusters Management
-* Dynamic environments with multiple changes
-* Support JWT Auth
+
-## Feature preview
+A running Pulsar Manager instance is comprised of two components: one is the
`frontend` which provides
+the GUI to manage and monitor Pulsar clusters, the other one is the `backend`
which interacts with Pulsar
+clusters for collecting metrics, forwarding admin requests to the requested
Pulsar cluster or brokers.
-### Log in
+Since Pulsar Manager directly interacts with Pulsar brokers and bookies for
management, it is required
+to deploy the Pulsar Manager into the same network as your Pulsar clusters. So
the Pulsar Manager backend
+is able to talk to the brokers and bookies in your Pulsar cluster.
-Use the default account (`pulsar`) and the default password (`pulsar`) to log
in.
+## Install
-
+### Use Docker
-### Configure environment
+1. Start Pulsar standalone.
-The puslar-manager supports multiple environment configurations and can manage
multiple environments conveniently.
+ ```
+ docker pull apachepulsar/pulsar:latest
+ docker run -d -it \
+ -p 6650:6650 \
+ -p 8080:8080 \
+ -v $PWD/data:/pulsar/data \
+ --name pulsar-standalone \
+ apachepulsar/pulsar:latest \
+ bin/pulsar standalone
+ ```
-
+2. Start Pulsar Manager in a separate container.
-### Manage tenants
+> NOTE: the command links the pulsar-manager container with the pulsar
standalone container so they are in the same network.
-
+ ```
+ docker pull apachepulsar/pulsar-manager:v0.1.0
+ docker run -it \
+ -p 9527:9527 \
+ -e REDIRECT_HOST=127.0.0.1 \
+ -e REDIRECT_PORT=9527 \
+ -e DRIVER_CLASS_NAME=org.postgresql.Driver \
+ -e URL='jdbc:postgresql://127.0.0.1:5432/pulsar_manager' \
+ -e USERNAME=pulsar \
+ -e PASSWORD=pulsar \
+ -e LOG_LEVEL=DEBUG \
+ -v $PWD:/data \
+ --link pulsar-standalone \
+ apachepulsar/pulsar-manager:v0.1.0
+ ```
-### Manage namespaces
+ * `REDIRECT_HOST`: the IP address of the front-end server.
+
+ * `REDIRECT_PORT`: the port of the front-end server.
-
+ * `DRIVER_CLASS_NAME`: the driver class name of PostgreSQL.
-### Manage topics
+ * `URL`: the jdbc url of your PostgreSQL database, example:
jdbc:postgresql://127.0.0.1:5432/pulsar_manager. The docker image automatically
start a local instance of PostgresSQL database.
-
+ * `USERNAME`: the username of PostgreSQL.
+ * `PASSWORD`: the password of PostgreSQL.
-### Manage subscriptions
+ * `LOG_LEVEL`: level of log.
-
-### Manage clusters
+### Use Docker Compose
-
+Alternatively, you can start a standalone and Pulsar Manager using the docker
compose file provided in this repository.
-### Manage brokers
+1. Clone this git repoistory.
-
+ ```bash
+ https://github.com/apache/pulsar-manager
+ ```
+2. Go to the docker directory.
-### Topics monitoring
+ ```bash
+ cd docker
+ ```
-The pulsar-manager can monitor topics and subscriptions.
+3. Start the docker composed cluster.
-
+ ```bash
+ docker-compose up
+ ```
-### Manage token
+### Deploy Pulsar Manager to Kubernetes
-
+The Pulsar Manager can be deployed as part of [Pulsar Helm
Chart](https://github.com/streamnative/charts).
+1. Install the Pulsar cluster with Pulsar Manager
+
+ ```bash
+ helm repo add streamnative https://charts.streamnative.io
+ helm repo update
+ helm install <release-name> streamnative/pulsar
+ ```
+
+2. Access the Pulsar Manager.
+
+ The default values will create a `ClusterIP` for the Pulsar Manager you
can use to interact with cluster.
+ To find the IP address of the Pulsar Manager, use the following command:
+ ```bash
+ kubectl get service -n <k8s-namespace>
+ ```
+ After find the ip address of the Pulsar Manager, you can access the Pulsar
Manager at `http://${pulsar-manager-cluster-ip}/#/environments`.
+
+### Build from source code
+
+#### Prerequisites
-## Prerequisites
* Java JDK 1.8
* Node 10.15.3 or later
* Npm 6.4.1 or later
* Pulsar 2.4.0 or later
-* Docker
-## Preparation
+#### Build instructions
-1. Start Pulsar standalone.
+1. Clone the source code.
+
+ ``` bash
+ git clone https://github.com/apache/pulsar-manager
+ ```
+2. Build and start the backend.
+
```
- docker pull apachepulsar/pulsar:2.4.0
- docker run -d -it -p 6650:6650 -p 8080:8080 -v $PWD/data:/pulsar/data
--name pulsar-manager-standalone apachepulsar/pulsar:2.4.0 bin/pulsar standalone
+ cd pulsar-manager
+ ./gradlew build -x test
+ cd build/distributions
+ unzip pulsar-manager.zip or tar -zxvf pulsar-manager.tar
+ ./pulsar-manager/bin/pulsar-manager
```
-2. Build an environment.
+3. Open a new terminal, build and start the front end.
- You can **build an environment with Docker** or **build a local
environment**.
+ ```
+ cd pulsar-manager/front-end
+ npm install --save
+ npm run dev
+ ```
+
+After running these steps, the Pulsar Manager is running locally at
http://127.0.0.1/#/environments.
+
+## Access Pusar Manager
- * Build an environment with Docker
+1. Access Pulsar manager UI at `http://${frontend-end-ip}/#/environments`.
- * `REDIRECT_HOST`: the IP address of the front-end server.
-
- * `REDIRECT_PORT`: the port of the front-end server.
+If you started Pulsar Manager using docker or docker-compose, the Pulsar
Manager is running at port 9527. You can access the Pulsar Manager UI at
http://127.0.0.1/#/environments.
- * `DRIVER_CLASS_NAME`: the driver class name of PostgreSQL.
+If you are deploying Pulsar Manager 0.1.0 using the released container, you
can log in the Pulsar Manager UI using the following credentials.
- * `URL`: the url of PostgreSQL jdbc, example:
jdbc:postgresql://127.0.0.1:5432/pulsar_manager.
+ * Account: `pulsar`
+ * Password: `pulsar`
+
+If you are deploying Pulsar Manager using the latest code, you can create a
super-user using the following command. Then you can use the super user
credentials to log in the Pulsar Manager UI.
- * `USERNAME`: the username of PostgreSQL.
+ ```$xslt
+ curl
+ -H "Content-Type: application/json" \
+ -X PUT http://backend-service:7750/pulsar-manager/users/superuser \
+ -d '{"name": "admin", "password": "apachepulsar", "description":
"test", "email": "[email protected]"}'
+ ```
+ `backend-service`: The IP address or domain name of the backend service.
+
+2. Create an environment.
- * `PASSWORD`: the password of PostgreSQL.
+ An environment represents a Pulsar instance or a group of clusters you
want to manage. A Pulsar Manager is capable of managing multiple environments.
- * `LOG_LEVEL`: level of log.
+ - Click "New Environment" button to add an environment.
+ - Input the "Environment Name". The environment name is used for
identifying an environment.
+ - Input the "Service URL". The Service URL is the admin service url of
your Pulsar cluster.
+ - You need to make sure the service url that Pulsar Manager is able to
access. In this example, both pulsar container and pulsar-manager container are
linked. So you can use pulsar container name as the domain name of the pulsar
standalone cluster. Thus you can type `http://pulsar-standalone:8080`.
- ```
- docker pull apachepulsar/pulsar-manager
- docker run -it -p 9527:9527 -e REDIRECT_HOST=front-end-ip -e
REDIRECT_PORT=front-end-port -e DRIVER_CLASS_NAME=org.postgresql.Driver -e
URL='jdbc-url' -e USERNAME=root -e PASSWORD=pulsar -e LOG_LEVEL=DEBUG
apachepulsar/pulsar-manager /bin/sh
- ```
+## Configure Pulsar Manager
- This is an example:
-
- ```
- docker pull apachepulsar/pulsar-manager:v0.1.0
- docker run -it -p 9527:9527 -e REDIRECT_HOST=http://192.168.0.104 -e
REDIRECT_PORT=9527 -e DRIVER_CLASS_NAME=org.postgresql.Driver -e
URL='jdbc:postgresql://127.0.0.1:5432/pulsar_manager' -e USERNAME=pulsar -e
PASSWORD=pulsar -e LOG_LEVEL=DEBUG -v $PWD:/data
apachepulsar/pulsar-manager:v0.1.0 /bin/sh
- ```
+### Back end
- * Build a local environment
+For more information about the back end, see
[pulsar-manager-backend](https://github.com/apache/pulsar-manager/blob/master/src/README.md).
- (1) Download the source code.
+### Front end
- ```
- git clone https://github.com/apache/pulsar-manager
- ```
+For more information about the front end, see
[pulsar-manager-frontend](https://github.com/apache/pulsar-manager/blob/master/front-end/README.md).
- (2) Build and start the backend.
-
- ```
- cd pulsar-manager
- ./gradlew build -x test
- cd build/distributions
- unzip pulsar-manager.zip or tar -zxvf pulsar-manager.tar
- ./pulsar-manager/bin/pulsar-manager
- ```
+## Features
- (3) Build and start the front end.
+* Tenants Management
+* Namespaces Management
+* Topics Management
+* Subscriptions Management
+* Brokers Management
+* Clusters Management
+* Dynamic environments with multiple changes
+* Support JWT Auth
- ```
- cd pulsar-manager/front-end
- npm install --save
- npm run dev
- ```
+### Log in
-3. Access Pulsar manager website.
+Use the default account (`pulsar`) and the default password (`pulsar`) to log
in.
-If you are deploying Pulsar Manager 0.1.0 using the released container, you
can log in the Pulsar Manager UI using the following credentials.
+
- * Account: `pulsar`
- * Password: `pulsar`
-
-If you are deploying Pulsar Manager using the latest code, you can create a
super-user using the following command.
+### Configure environment
- ```$xslt
- curl -H "Content-Type: application/json" -X PUT
http://backend-service:7750/pulsar-manager/users/superuser -d '{"name":
"admin", "password": "apachepulsar", "description": "test", "email":
"[email protected]"}'
- ```
- `backend-service`: The IP address or domain name of the backend service.
-
- * Pulsar manager website: http://localhost:9527/
+The puslar-manager supports multiple environment configurations and can manage
multiple environments conveniently.
+
+
+
+### Manage tenants
+
+
+
+### Manage namespaces
+
+
+
+### Manage topics
+
+
+
+### Manage subscriptions
+
+
+
+### Manage clusters
+
+
+
+### Manage brokers
+
+
+
+
+### Topics monitoring
+
+The pulsar-manager can monitor topics and subscriptions.
+
+
+
+### Manage token
+
+
+
+## Development
### Default Test database HerdDB
@@ -175,12 +269,3 @@ jdbc:herddb:zookeeper:localhost:2181/herddb
In order to start and setup an HerdDB database follow the instructions on the
[HerdDB documentation](https://github.com/diennea/herddb/wiki).
-## Back end
-
-For more information about the back end, see
[pulsar-manager-backend](https://github.com/apache/pulsar-manager/blob/master/src/README.md).
-
-
-## Front end
-
-For more information about the front end, see
[pulsar-manager-frontend](https://github.com/apache/pulsar-manager/blob/master/front-end/README.md).
-
diff --git a/docker/data/.keep b/docker/data/.keep
new file mode 100644
index 0000000..e69de29
diff --git a/docker/docker-compose.yml b/docker/docker-compose.yml
new file mode 100644
index 0000000..4fbbd56
--- /dev/null
+++ b/docker/docker-compose.yml
@@ -0,0 +1,30 @@
+version: "3.7"
+services:
+ pulsar:
+ image: apachepulsar/pulsar:2.5.0
+ command: bin/pulsar standalone
+ hostname: pulsar
+ ports:
+ - "8080:8080"
+ - "6650:6650"
+ restart: unless-stopped
+ volumes:
+ - "./data/:/pulsar/data"
+ dashboard:
+ image: apachepulsar/pulsar-manager:v0.1.0
+ ports:
+ - "9527:9527"
+ depends_on:
+ - pulsar
+ links:
+ - pulsar
+ volumes:
+ - "./data/:/data"
+ environment:
+ REDIRECT_HOST: "http://127.0.0.1";
+ REDIRECT_PORT: "9527"
+ DRIVER_CLASS_NAME: "org.postgresql.Driver"
+ URL: "jdbc:postgresql://127.0.0.1:5432/pulsar_manager"
+ USERNAME: "pulsar"
+ PASSWORD: "pulsar"
+ LOG_LEVEL: "DEBUG"
\ No newline at end of file
diff --git a/docs/img/pulsar-manager-arch.png b/docs/img/pulsar-manager-arch.png
new file mode 100644
index 0000000..e78b96a
Binary files /dev/null and b/docs/img/pulsar-manager-arch.png differ
