Common operations on X-as-a-Service » History » Version 3
Timothée Floure, 03/20/2020 01:49 PM
Customer contact template.
1 | 1 | Timothée Floure | h1. Common operations on X-as-a-Service |
---|---|---|---|
2 | |||
3 | h2. Matrix-as-a-Service |
||
4 | |||
5 | 3 | Timothée Floure | h3. Contact customer for setup informations |
6 | |||
7 | Do not forget to replace @$CUSTMER@! |
||
8 | |||
9 | <pre> |
||
10 | Hello $CUSTOMER, |
||
11 | |||
12 | I will deploy your Matrix homeserver but need a few configuration details from |
||
13 | you first. I do not know how familiar you are with Matrix or technical terms: |
||
14 | do not hesitate to tell me if I go to fast or to slow for you. |
||
15 | |||
16 | First of all, each Matrix homeserver is linked to domain name (you users will look |
||
17 | like `@username:domain.tld`) for federation. I can offer you two options here, |
||
18 | but remember that the chosen domain name cannot be changed afterward: |
||
19 | |||
20 | * Your own domain (e.g. domain.tld). |
||
21 | * One domain controlled by ungleich (e.g. $CUSTOMER.0co2.cloud, |
||
22 | $CUSTOMER.ungleich.cloud). |
||
23 | |||
24 | Secondly, I will deploy a Riot web matrix client for convenience (you can use |
||
25 | the desktop or smartphone clients as well) and need a domain for that as well: |
||
26 | |||
27 | * Your own domain (e.g. matrix.domain.tld) |
||
28 | * One domain controlled by ungleich (e.g. matrix.$CUSTOMER.0c02.cloud). |
||
29 | |||
30 | Lastly, I will configure the Matrix homeserver for you. You can ask us to set |
||
31 | any configuration option but we at least need to know your preferences in term |
||
32 | of registration: |
||
33 | * Should it be backed by an existing user directory (LDAP)? |
||
34 | * Should registrations be filtered by domain of email address? (e.g. anyone |
||
35 | with a @domain.tld email address can register). |
||
36 | * Should anyone be allowed to register? |
||
37 | |||
38 | Feel free to ask me any matrix-related question, as I am a heavy matrix user |
||
39 | myself. |
||
40 | |||
41 | Best Regards, |
||
42 | |||
43 | -- |
||
44 | </pre> |
||
45 | |||
46 | 1 | Timothée Floure | h3. Deploy new MaaS instance |
47 | |||
48 | TODO -> ask @fnux for now. |
||
49 | |||
50 | 2 | Timothée Floure | * Allocate ONE VM. |
51 | * Add HDD storage. |
||
52 | * Add FSTAB entry for /var/ on HDD |
||
53 | * mount data disk on /mnt |
||
54 | * mv /var to /mnt |
||
55 | * remove /var; mount -a to remount /var to on new disk |
||
56 | * reboot to make sure everything's OK. |
||
57 | * Upgrade VM: update/upgrade. |
||
58 | * Add DNS entry in matrix.ungleich.cloud |
||
59 | * Add server to matrix-as-a-service manifest, deploy |
||
60 | * Have customer configure his domain. |
||
61 | * Create initial admin use. |
||
62 | |||
63 | 1 | Timothée Floure | h3. Upgrade a running MaaS instance |
64 | |||
65 | TODO -> ask @fnux for now. |
||
66 | |||
67 | h3. Deploy Matterbridge application service |
||
68 | |||
69 | TODO -> ask @fnux for now. |