Parthenon /ˈpɑːθənɒn/ (n.) A temple built to house something important.
1. Your deployment
2. Recommendation
3. Hostnames / IPs
4. Estate plan
Tell us about the deployment
Already have a plan? Load it to change it
Availability
Components on this box
Untick anything you don't want installed.
Search
Calls
Monitoring
Recommended architecture
Add a server by hand
Diagram
Every arrow is a firewall rule, pointing the way the connection is opened. Dotted is monitoring
and logging, thick is call media, which goes straight to the server and never through the proxy.
Suggested install order
Hostnames and addresses
Each server needs the address the others will reach it on. A hostname works if
every server can resolve it.
Estate plan
Copy the plan.
On each server, in the install order below, run
sudo ./install.sh --estate my-estate.yml, or paste the plan when it asks.
Install order
Design decisions
What this shape gives you, and what it doesn't.
Decision
What it means
Firewall requirements
For the network team. Mattermost Parthenon opens these on each server. Anything
between your own network segments is theirs to open.
Source
Destination
Port
Protocol
What it carries
Outbound
Connections these servers have to be able to make. Mattermost Parthenon cannot
open these for you, because they leave your network.
Source
Destination
Port
Protocol
What it carries
When
Infrastructure requirements
For the server team. Mattermost's published figures for this size, per server.
Server
Runs
vCPU
RAM
Disk
Notes
RHEL 9 or 10, Debian 12 or later, or Ubuntu 24.04 or later, on x86_64 or arm64, and outbound access to the vendor download sites
or an offline bundle.