Skip to content

Commit 86b886b

Browse files
author
lijianguo
committed
chore(docs): add rabbitmq docs
1 parent e7c1f57 commit 86b886b

8 files changed

Lines changed: 35 additions & 25 deletions

File tree

‎src/_includes/install-workflow.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,12 +52,14 @@ $ kubectl --namespace=drycc get pods
5252
NAME READY STATUS RESTARTS AGE
5353
drycc-builder-hy3xv 1/1 Running 5 5m
5454
drycc-controller-g3cu8 1/1 Running 5 5m
55+
drycc-controller-celery-cmxxn 3/3 Running 0 5m
5556
drycc-database-rad1o 1/1 Running 0 5m
5657
drycc-logger-fluentd-1v8uk 1/1 Running 0 5m
5758
drycc-logger-fluentd-esm60 1/1 Running 0 5m
5859
drycc-logger-sm8b3 1/1 Running 0 5m
5960
drycc-minio-4ww3t 1/1 Running 0 5m
6061
drycc-registry-asozo 1/1 Running 1 5m
62+
drycc-rabbitmq-0 1/1 Running 0 5m
6163
```
6264

6365
Once all of the pods are in the `READY` state, Drycc Workflow is up and running!

‎src/installing-workflow/index.md‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ $ helm install --namespace drycc \
6363
drycc/workflow
6464
```
6565

66-
By default, registry uses docker hub, at present, we support three registries. They are:
66+
By default, registry uses docker hub, at present, we support three registries. They are:
6767

6868
* redhat quay `quay.io`
6969
* docker hub `docker.io`
@@ -82,6 +82,7 @@ $ helm install --namespace drycc \
8282
--set fluentd.image_registry=quay.io \
8383
--set redis.image_registry=quay.io \
8484
--set influxdb.image_registry=quay.io \
85+
--set rabbitmq.image_registry=quay.io \
8586
--set logger.image_registry=quay.io \
8687
--set minio.image_registry=quay.io \
8788
--set monitor.image_registry=quay.io \
@@ -116,6 +117,7 @@ $ kubectl --namespace=drycc get pods
116117
NAME READY STATUS RESTARTS AGE
117118
drycc-builder-574483744-l15zj 1/1 Running 0 4m
118119
drycc-controller-3953262871-pncgq 1/1 Running 2 4m
120+
drycc-controller-celery-cmxxn 3/3 Running 0 4m
119121
drycc-database-83844344-47ld6 1/1 Running 0 4m
120122
drycc-influxdb-2729788615-m9b5n 1/1 Running 0 4m
121123
drycc-logger-176328999-wjckx 1/1 Running 4 4m
@@ -127,6 +129,7 @@ drycc-monitor-telegraf-wmcmn 1/1 Running 1 4m
127129
drycc-nsqd-3597503299-6mn2x 1/1 Running 0 4m
128130
drycc-registry-756475849-lwc6b 1/1 Running 1 4m
129131
drycc-registry-proxy-96c4p 1/1 Running 0 4m
132+
drycc-rabbitmq-0 1/1 Running 0 4m
130133
```
131134

132135
Once all of the pods are in the `READY` state, Drycc Workflow is up and running!

‎src/installing-workflow/ingress.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,12 +18,12 @@ $ helm install drycc/workflow --namespace drycc \
1818
--set global.platform_domain=drycc.cc \
1919
--set builder.service.type=NodePort \
2020
--set builder.service.nodePort=32222
21-
```
21+
```
2222

2323
If you want to use Load Balancer on a bare machine, you can look at [metallb](https://github.com/danderson/metallb)
2424

2525
Where `global.platform_domain` is a **required** parameter that is traditionally not required for Workflow that is explained in the next section. In this example we are using `drycc.cc` for `$hostname`.
26-
26+
2727
Helm will install a variety of Kubernetes resources in the `drycc` namespace.
2828
Wait for the pods that Helm launched to be ready. Monitor their status by running:
2929

@@ -48,12 +48,14 @@ $ kubectl --namespace=drycc get pods
4848
NAME READY STATUS RESTARTS AGE
4949
drycc-builder-hy3xv 1/1 Running 5 5m
5050
drycc-controller-g3cu8 1/1 Running 5 5m
51+
drycc-controller-celery-cmxxn 3/3 Running 0 5m
5152
drycc-database-rad1o 1/1 Running 0 5m
5253
drycc-logger-fluentd-1v8uk 1/1 Running 0 5m
5354
drycc-logger-fluentd-esm60 1/1 Running 0 5m
5455
drycc-logger-sm8b3 1/1 Running 0 5m
5556
drycc-minio-4ww3t 1/1 Running 0 5m
5657
drycc-registry-asozo 1/1 Running 1 5m
58+
drycc-rabbitmq-0 1/1 Running 0 5m
5759
```
5860

5961
## Install a Kubernetes Ingress Controller

‎src/managing-workflow/upgrading-workflow.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,7 @@ $ kubectl --namespace=drycc get pods
5454
NAME READY STATUS RESTARTS AGE
5555
drycc-builder-2448122224-3cibz 1/1 Running 0 5m
5656
drycc-controller-1410285775-ipc34 1/1 Running 3 5m
57+
drycc-controller-celery-694f75749b-cmxxn 3/3 Running 0 5m
5758
drycc-database-e7c5z 1/1 Running 0 5m
5859
drycc-influxdb-ah8io 1/1 Running 0 5m
5960
drycc-logger-cgjup 1/1 Running 3 5m
@@ -73,6 +74,7 @@ drycc-registry-proxy-4m3o4 1/1 Running 0 5m
7374
drycc-registry-proxy-no3r1 1/1 Running 0 5m
7475
drycc-registry-proxy-ou8is 1/1 Running 0 5m
7576
drycc-registry-proxy-zyajl 1/1 Running 0 5m
77+
drycc-rabbitmq-0 1/1 Running 0 5m
7678
```
7779

7880
### Step 3: Upgrade the Drycc Client

‎src/quickstart/provider/azure-acs/install-azure-acs.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,12 +71,14 @@ $ kubectl --namespace=drycc get pods
7171
NAME READY STATUS RESTARTS AGE
7272
drycc-builder-hy3xv 1/1 Running 5 5m
7373
drycc-controller-g3cu8 1/1 Running 5 5m
74+
drycc-controller-celery-cmxxn 3/3 Running 0 5m
7475
drycc-database-rad1o 1/1 Running 0 5m
7576
drycc-logger-fluentd-1v8uk 1/1 Running 0 5m
7677
drycc-logger-fluentd-esm60 1/1 Running 0 5m
7778
drycc-logger-sm8b3 1/1 Running 0 5m
7879
drycc-minio-4ww3t 1/1 Running 0 5m
7980
drycc-registry-asozo 1/1 Running 1 5m
81+
drycc-rabbitmq-0 1/1 Running 0 5m
8082
```
8183

8284
Once all of the pods are in the `READY` state, Drycc Workflow is up and running!

‎src/quickstart/provider/minikube/install-minikube.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,12 +54,14 @@ $ kubectl --namespace=drycc get pods
5454
NAME READY STATUS RESTARTS AGE
5555
drycc-builder-hy3xv 1/1 Running 5 5m
5656
drycc-controller-g3cu8 1/1 Running 5 5m
57+
drycc-controller-celery-cmxxn 3/3 Running 0 5m
5758
drycc-database-rad1o 1/1 Running 0 5m
5859
drycc-logger-fluentd-1v8uk 1/1 Running 0 5m
5960
drycc-logger-fluentd-esm60 1/1 Running 0 5m
6061
drycc-logger-sm8b3 1/1 Running 0 5m
6162
drycc-minio-4ww3t 1/1 Running 0 5m
6263
drycc-registry-asozo 1/1 Running 1 5m
64+
drycc-rabbitmq-0 1/1 Running 0 5m
6365
```
6466

6567
Once all of the pods are in the `READY` state, Drycc Workflow is up and running!

‎src/troubleshooting/kubectl.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,15 +12,17 @@ running, run:
1212
NAME READY STATUS RESTARTS AGE
1313
drycc-builder-gqum7 0/1 ContainerCreating 0 4s
1414
drycc-controller-h6lk6 0/1 ContainerCreating 0 4s
15+
drycc-controller-celery-cmxxn 0/3 ContainerCreating 0 4s
1516
drycc-database-56v39 0/1 ContainerCreating 0 4s
16-
drycc-influxdb-f9ftm 0/1 Pending 0 3s
17+
drycc-influxdb-f9ftm 0/1 Pending 0 3s
1718
drycc-logger-fluentd-xihr1 0/1 Pending 0 2s
1819
drycc-logger-grupg 0/1 ContainerCreating 0 3s
1920
drycc-minio-c2exb 0/1 Pending 0 3s
2021
drycc-monitor-grafana-9ccur 0/1 Pending 0 3s
2122
drycc-monitor-stdout-novxs 0/1 Pending 0 3s
2223
drycc-monitor-telegraf-dc3y3 0/1 Pending 0 2s
2324
drycc-registry-5bor6 0/1 Pending 0 3s
25+
drycc-rabbitmq-0 0/1 ContainerCreating 0 3s
2426

2527
!!! tip
2628
To save precious keystrokes, alias `kubectl --namespace=drycc` to `kd` so it is easier to type

‎src/understanding-workflow/components.md‎

Lines changed: 16 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -97,20 +97,6 @@ images generated from the builder component. Registry persists the Docker image
9797
images to either local storage (in development mode) or to object storage
9898
configured for the cluster.
9999

100-
## Router
101-
102-
**Project Location:** [drycc/router](https://github.com/drycc/router)
103-
104-
The router component is based on [Nginx][] and is responsible for routing
105-
inbound HTTP(S) traffic to your applications. The default workflow charts
106-
provision a Kubernetes service in the `drycc` namespace with a service type of
107-
`LoadBalancer`. Depending on your Kubernetes configuration, this may provision
108-
a cloud-based loadbalancer automatically.
109-
110-
The router component uses Kubernetes annotations for both Application discovery
111-
as well as router configuration. For more detailed documentation and possible
112-
configuration view the router [project documentation][router-documentation].
113-
114100
## Logger: fluentd, logger
115101

116102
The logging subsystem consists of two components. Fluentd handles log shipping
@@ -135,21 +121,32 @@ documentation][logger-documentation].
135121

136122
**Project Location:** [drycc/monitor](https://github.com/drycc/monitor)
137123

138-
The monitoring subsystem consists of three components: Telegraf, InfluxDB and Grafana.
124+
The monitoring subsystem consists of two components: Telegraf and Grafana.
139125

140126
Telegraf is the is the metrics collection agent that runs using the daemon set API. It runs on
141127
every worker node in the cluster, fetches information about the pods currently running and ships it
142128
to InfluxDB.
143129

144-
InfluxDB is a database that stores the metrics collected by Telegraf. Out of the box, it does not
145-
persist to disk, but you can set it up to back it with a persisitent volume or swap this out with
146-
a more robust InfluxDB setup in a production setting.
147-
148130
Grafana is a standalone graphing application. It natively supports InfluxDB as a datasource and
149131
provides a robust engine for creating dashboards on top of timeseries data. Workflow provides a few
150132
dashboards out of the box for monitoring Drycc Workflow and Kubernetes. The dashboards can be used
151133
as a starting point for creating more custom dashboards to suit a user's needs.
152134

135+
## InfluxDB
136+
137+
**Project Location:** [drycc/influxdb](https://github.com/drycc/influxdb)
138+
139+
InfluxDB is a database that stores the metrics collected by Telegraf. Out of the box, it does not
140+
persist to disk, but you can set it up to back it with a persisitent volume or swap this out with
141+
a more robust InfluxDB setup in a production setting.
142+
143+
## Rabbitmq
144+
145+
**Project Location:** [drycc/rabbitmq](https://github.com/drycc/rabbitmq)
146+
147+
RabbitMQ is the most widely deployed open source message broker.
148+
Controller use celery with rabbitMQ to execute the asynchronous task.
149+
153150
## See Also
154151

155152
* [Workflow Concepts][concepts]
@@ -166,7 +163,5 @@ as a starting point for creating more custom dashboards to suit a user's needs.
166163
[configure-objectstorage]: ../installing-workflow/configuring-object-storage.md
167164
[logger-documentation]: https://github.com/drycc/logger
168165
[release]: ../reference-guide/terms.md#release
169-
[router-documentation]: https://github.com/drycc/router
170-
[router]: #router
171166
[using-buildpacks]: ../applications/using-buildpacks.md
172167
[using-dockerfiles]: ../applications/using-dockerfiles.md

0 commit comments

Comments
 (0)