(→Minimum Hardware Requirements) |
|||
| Line 15: | Line 15: | ||
==Minimum Hardware Requirements== | ==Minimum Hardware Requirements== | ||
| + | |||
Whether the server is on hardware or cloud/virtual, it needs to be physically located in your country. | Whether the server is on hardware or cloud/virtual, it needs to be physically located in your country. | ||
The recommended server specifications are: | The recommended server specifications are: | ||
| − | * 2 vCPU | + | * 2 vCPU minimum, 4vCPU preferred. |
| − | * 4GB | + | * 4GB memory minimum 8GB preferred. |
* 10GB ~ 20GB disk space | * 10GB ~ 20GB disk space | ||
| − | * Static | + | * Static public IPv4 address assigned to the machine directly (no nat) |
* Minimal 100mbit up and down | * Minimal 100mbit up and down | ||
** at least 2TB of traffic per month | ** at least 2TB of traffic per month | ||
| + | ''(use the preferred recommendation if you expect a large number of nodes on the master server)'' | ||
| + | |||
| + | ==Hypervisor notes== | ||
| + | * KVM or ESXi are well supported | ||
| + | * The Xen hypervisor is not supported. Please make sure it is not the one your provider uses. | ||
| + | * The provider inode is known to cause issues with hosting a Brandmeister master server. We recommend you do not install on this platform. | ||
==Installation and Configuration== | ==Installation and Configuration== | ||
The BrandMeister solution consists of 3 main parts:
BrandMeister does all the work of switching DMR calls and communication with repeaters or other servers as well as running specific DMR applications like ARS, RRS, LRRP, IP transport, Parrot, etc. Currently we use a centralised solution based on Python to make data distribution. It processes events received from MQTT and writes data to the master database which have to be replicated to local databases of each master server.
Whether the server is on hardware or cloud/virtual, it needs to be physically located in your country. The recommended server specifications are:
(use the preferred recommendation if you expect a large number of nodes on the master server)
If you would like to install a master server in your country, please create a support request on the BrandMeister Support Portal. You do not need to set up a server prior to contacting the BrandMeister Team.
If you have additional questions, please contact PD0ZRY or R3ABM
The BrandMeister solution consists of 3 main parts:
BrandMeister does all the work of switching DMR calls and communication with repeaters or other servers as well as running specific DMR applications like ARS, RRS, LRRP, IP transport, Parrot, etc. Currently we use a centralised solution based on Python to make data distribution. It processes events received from MQTT and writes data to the master database which have to be replicated to local databases of each master server.
Whether the server is on hardware or cloud/virtual, it needs to be physically located in your country. The recommended server specifications are:
(use the preferred recommendation if you expect a large number of nodes on the master server)
If you would like to install a master server in your country, please create a support request on the BrandMeister Support Portal. You do not need to set up a server prior to contacting the BrandMeister Team.
If you have additional questions, please contact PD0ZRY or R3ABM
BrandMeister