Difference between revisions of "Joining BrandMeister with your own server"

(→‎Installation and Configuration)
 
(→‎Hypervisor notes)
 
(3 intermediate revisions by 2 users not shown)
Line 14: Line 14:
 
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|ARS]], [[Hytera/RRS|RRS]], [[Motorola/LRRP|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.
 
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|ARS]], [[Hytera/RRS|RRS]], [[Motorola/LRRP|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.
  
−
==Hardware specifications==
+
==Minimum Hardware Requirements==
 +
 
 +
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 ~ 8GB memory
+
* 4GB memory minimum 8GB preferred.
−
* 10GB ~ 20GB disk space
+
* 16GB ~ 24GB disk space
−
* Static Public IPv4 address assigned to the machine directly (no nat)
+
* 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)''
  
−
==Installation and Configuration==
+
==Hypervisor notes==
−
# Prepare a server: this solution requires a publicly available server based on '''Debian x64 version 10.x with public static IP'''. You can use a VM based on vmWare or KVM. '''Please do not use OpenVZ or VirtualBox'''.
+
* KVM or ESXi are well supported
−
# Configure the necessary [[Network_Ports|iptables]]. '''We deploy the initial configuration of BrandMeister for you'''. '''Please do not install any package listed in previous sections'''.
+
* The Xen hypervisor is not supported. Please make sure it is not the one your provider uses.
−
# You will need some time to learn the paradigm of the system as well as how to manage and program the configuration. We will support you.
+
  
−
We strongly recommend that you delegate the responsibility of server deployment to our team. The server will always be under your full control, but we should have access to update and make fixes to the system.
+
==Installation and Configuration==
−
 
+
If you would like to install a master server in your country, please create a support request on the [https://support.brandmeister.network/servicedesk/customer/user/login?destination=portals BrandMeister Support Portal]. You do not need to set up a server prior to contacting the BrandMeister Team.
−
Please send your questions and requests to our [http://www.facebook.com/groups/BrandmeisterDMR/ Facebook Group] or directly to Rudy ([[PD0ZRY]]) or me.
+
  
−
73 de [[R3ABM]]
+
If you have additional questions, please contact [[PD0ZRY]] or [[R3ABM]]

Latest revision as of 21:47, 19 April 2023

  1. English
  2. Deutsch
  3. Español
  4. Français
  5. hrvatski
  6. Nederlands

Policy

  • We suggest using no more than one server for each country. Of course exceptions to this rule can be discussed.
  • Country should have more than 10 repeaters or country is far away from current Master
  • You have to be ready to have at least 2 TB of traffic every month (~ 5 Mbit/sec average on most cold server)

What is BrandMeister

The BrandMeister solution consists of 3 main parts:

  • Realtime frontend: BrandMeister DMR Server
  • Supplementary and REST API frontend: Apache + PHP
  • Middleware and backend: Tarantool, Mosquitto, D-BUS IPC

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.

Minimum Hardware Requirements

Whether the server is on hardware or cloud/virtual, it needs to be physically located in your country. The recommended server specifications are:

  • 2 vCPU minimum, 4vCPU preferred.
  • 4GB memory minimum 8GB preferred.
  • 16GB ~ 24GB disk space
  • Static public IPv4 address assigned to the machine directly (no nat)
  • Minimal 100mbit up and down
    • 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.

Installation and Configuration

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

Retrieved from "https://wiki.brandmeister.network/index.php?title=Joining_BrandMeister_with_your_own_server&oldid=19016"
  1. English
  2. Deutsch
  3. Español
  4. Français
  5. hrvatski
  6. Nederlands

Policy[edit]

What is BrandMeister[edit]

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.

Hardware specifications[edit]

The recommended server specifications are:

Installation and Configuration[edit]

  1. Prepare a server: this solution requires a publicly available server based on Debian x64 version 10.x with public static IP. You can use a VM based on vmWare or KVM. Please do not use OpenVZ or VirtualBox.
  2. Configure the necessary iptables. We deploy the initial configuration of BrandMeister for you. Please do not install any package listed in previous sections.
  3. You will need some time to learn the paradigm of the system as well as how to manage and program the configuration. We will support you.

We strongly recommend that you delegate the responsibility of server deployment to our team. The server will always be under your full control, but we should have access to update and make fixes to the system.

Please send your questions and requests to our Facebook Group or directly to Rudy (PD0ZRY) or me.

73 de R3ABM