The ungleich Matrix infrastructure » History » Version 7
Timothée Floure, 01/12/2020 04:01 PM
Add link to matrix federation tester
1 | 1 | Timothée Floure | h1. The ungleich Matrix infrastructure |
---|---|---|---|
2 | |||
3 | *%{color:red}This document concerns the infrastructure side of our MaaS offer and is intended for ungleich staff. See [[Ungleich Matrix-as-a-Service (MaaS)]] page for end-user/customer documentation.%* |
||
4 | |||
5 | h2. Status |
||
6 | |||
7 | This document is *A DRAFT*. This service is not in production. |
||
8 | 2 | Timothée Floure | |
9 | 4 | Timothée Floure | h2. Environment |
10 | 2 | Timothée Floure | |
11 | Our Matrix deployments make use of the "Synapse (reference) Matrix homeserver":https://github.com/matrix-org/synapse/ and "Riot web client":https://about.riot.im/. We use Debian buster as base Operating system, leveraging the "matrix-synapse package from the buster-backports repository":https://packages.debian.org/buster-backports/matrix-synapse. The riot client (= static files) is directly fetched from "upstream releases on github":https://github.com/vector-im/riot-web/releases. |
||
12 | |||
13 | 5 | Timothée Floure | The matrix deployments run on ipv6only VMs, HTTP(S) traffic - including federation - being proxy by the [[How to use the IPv4-to-IPv6-Proxy|ungleich v4-to-v6 proxy]]. Federation is delegated using a @/.well-known/@ URI as described in [[Ungleich Matrix-as-a-Service (MaaS)|the customer FAQ]]. |
14 | 2 | Timothée Floure | |
15 | 6 | Timothée Floure | !maas.jpg! |
16 | |||
17 | 2 | Timothée Floure | h2. Tooling |
18 | |||
19 | The whole MaaS setup is defined in the *manifest/matrix-as-a-service* of *dot-cdist* file, which wraps the *__ungleich_matrix* type. This type leverages: |
||
20 | |||
21 | * *__matrix_synapse* |
||
22 | * *__matrix_riot* |
||
23 | * *__ungleich_nginx_static_type* |
||
24 | * *__postgres_role* and *__postgres_database* from upstream cdist. |
||
25 | |||
26 | 7 | Timothée Floure | *Matrix Federation Tester: https://federationtester.matrix.org/* |
27 | |||
28 | 4 | Timothée Floure | h2. Monitoring |
29 | 1 | Timothée Floure | |
30 | 4 | Timothée Floure | We plan to leverage consul's service discovery to feed system (node exporter) and matrix (synapse) metrics to prometheus/grafana. |
31 | 2 | Timothée Floure | |
32 | 4 | Timothée Floure | h2. Ungleich Deployments |
33 | 2 | Timothée Floure | |
34 | 4 | Timothée Floure | We maintain our own deployments alongside the customer MaaS, both for our own usage and for testing. |
35 | |||
36 | 2 | Timothée Floure | h3. matrix-staging.ungleich.ch |
37 | |||
38 | 4 | Timothée Floure | Staging instance used to tests the deployment pipeline and Matrix updates. |
39 | 2 | Timothée Floure | |
40 | h3. matrix.ungleich.ch |
||
41 | |||
42 | 4 | Timothée Floure | Production instance for ungleich, will be bridged to "chat.ungleich.ch":https://chat.ungleich.ch at some point. |
43 | 2 | Timothée Floure | |
44 | h2. Application Services |
||
45 | |||
46 | 4 | Timothée Floure | We do not support any application service as of today. |
47 | 1 | Timothée Floure |