You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/how-to/install/wiab-staging.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Introduction
4
4
5
-
**Wire in a Box (WIAB) Staging** is a demo installation of Wire running on a single physical machine using KVM-based virtual machines. This setup replicates the multi-node production Wire architecture in a consolidated environment suitable for testing, evaluation, and learning about Wire's infrastructure—but **not for production use**.
5
+
**Wire in a Box (WIAB) Staging** is a staging installation of Wire running on a single physical machine using KVM-based virtual machines. This setup replicates the multi-node production Wire architecture in a consolidated environment suitable for testing, evaluation, and learning about Wire's infrastructure—but **not for production use**.
6
6
7
7
> **Important:** This is a sandbox environment. Data from a staging installation **cannot be migrated to production**. WIAB Staging is designed for experimentation, validation, and understanding Wire's deployment model.
8
8
@@ -27,7 +27,7 @@ Key differences from production:
27
27
- Calling services run with limited resources (replicas=1).
28
28
-[Calling services](../../understand/overview.md#calling) will share the same k8s cluster as Wire stateful services hence, all infrastructure will be DMZ (De-militarized zone).
29
29
30
-
If you need a fully supported, highly-available, multi-datacenter deployment, use the **Production** path instead (see `ansible-VMs.md` and `helm-prod.md`).
30
+
If you need a fully supported, highly-available, secure, multi-datacenter deployment, use the **Production** path instead (see `ansible-VMs.md` and `helm-prod.md`).
31
31
32
32
## Requirements
33
33
@@ -73,11 +73,11 @@ We would require 7 VMs as per the following details, you can choose to use your
73
73
74
74
-**kubenodes (kubenode1, kubenode2, kubenode3):** Run the Kubernetes cluster and host Wire backend services
75
75
-**datanodes (datanode1, datanode2, datanode3):** Run distributed data services:
76
-
- Cassandra (distributed database)
77
-
- PostgreSQL (operational database)
78
-
- Elasticsearch (search engine)
79
-
- Minio (S3-compatible object storage)
80
-
- RabbitMQ (message broker)
76
+
- Cassandra
77
+
- PostgreSQL
78
+
- Elasticsearch
79
+
- Minio
80
+
- RabbitMQ
81
81
-**assethost:** Hosts static assets like container images and debian binaries to be used by kubenodes and datanodes during installation.
0 commit comments