(Created page with "Before reading this document I ask you to accept our policy: we suggest to use not more than one server for each country. Of course, exceptions to this rule can be discussed....")
 
m
Line 6: Line 6:
 
- back-end
 
- back-end
  
BrandMeister does all work of switching DMR calls, comunication with repeaters, other servers and running specific DMR applications like [[ARS]], [[RRS]], [[LRRP]], IP transport, [[Parrot]], etc. It uses MySQL database in read-only mode to read user profiles and routes, Memcached is used in read-write mode to manage routes and Mosquitto is used to send network events. Currently we use centralized work-around solution based on Python for back-end. It processes events received from Mosquitto and writes data to the database. All servers have slave databases that have replica from master database placed near current back-end. We planned to develop the target back-end system named [[CallDirector]] but now we have no free time for it. We are ready for collaboration to develop it. CallDirector should use mesh-network technilogies and active-active replication schema to syncronize profile data.
+
BrandMeister does all work of switching DMR calls, comunication with repeaters, other servers and running specific DMR applications like [[Motorola/ARS|ARS]], [[Hytera/RRS|RRS]], [[LRRP]], IP transport, [[Parrot]], etc. It uses MySQL database in read-only mode to read user profiles and routes, Memcached is used in read-write mode to manage routes and Mosquitto is used to send network events. Currently we use centralized work-around solution based on Python for back-end. It processes events received from Mosquitto and writes data to the database. All servers have slave databases that have replica from master database placed near current back-end. We planned to develop the target back-end system named [[CallDirector]] but now we have no free time for it. We are ready for collaboration to develop it. CallDirector should use mesh-network technilogies and active-active replication schema to syncronize profile data.
  
At this moment you need to prepare the host. After that you need to install MySQL server, Memcaced and Apache2, PHP5, php5 memcached plug-in from debian distribution. Install mosquitto from the mosquitto repositories. Install dbus-beta plug-for PHP5 in using pecl utility. Configure iptables (I'll give you an example). Next we should configure MySQL for the slave replica (and to use UTC as time-zone for RDBMS), confiugre Mosquitto to forward topics to current back-end server. Please provide me IP of the server to allow access.
+
At this moment you need to prepare the host. After that you need to install MySQL server, Memcaced and Apache2, PHP5, php5 memcached plug-in from debian distribution. Install mosquitto from the mosquitto repositories. Install dbus-beta plug-for PHP5 in using pecl utility. Configure [[Network_Ports|iptables]]. Next we should configure MySQL for the slave replica (and to use UTC as time-zone for RDBMS), confiugre Mosquitto to forward topics to current back-end server. Please provide me IP of the server to allow access.
  
 
After these steps you will be able to install BrandMeister package. You need to do configuration after installation. BrandMeister will do automatic activation on the first run. I am strongly recommend you to delegate the responsibility of deployment to our team. In this case please follow next steps:
 
After these steps you will be able to install BrandMeister package. You need to do configuration after installation. BrandMeister will do automatic activation on the first run. I am strongly recommend you to delegate the responsibility of deployment to our team. In this case please follow next steps:

Revision as of 11:07, 24 November 2015

Before reading this document I ask you to accept our policy: we suggest to use not more than one server for each country. Of course, exceptions to this rule can be discussed.

BrandMeister solution contains 3 main parts: - real-time front-end BrandMeister DMR Server - middle-ware MySQL, Memcached, Mosquitto - back-end

BrandMeister does all work of switching DMR calls, comunication with repeaters, other servers and running specific DMR applications like ARS, RRS, LRRP, IP transport, Parrot, etc. It uses MySQL database in read-only mode to read user profiles and routes, Memcached is used in read-write mode to manage routes and Mosquitto is used to send network events. Currently we use centralized work-around solution based on Python for back-end. It processes events received from Mosquitto and writes data to the database. All servers have slave databases that have replica from master database placed near current back-end. We planned to develop the target back-end system named CallDirector but now we have no free time for it. We are ready for collaboration to develop it. CallDirector should use mesh-network technilogies and active-active replication schema to syncronize profile data.

At this moment you need to prepare the host. After that you need to install MySQL server, Memcaced and Apache2, PHP5, php5 memcached plug-in from debian distribution. Install mosquitto from the mosquitto repositories. Install dbus-beta plug-for PHP5 in using pecl utility. Configure iptables. Next we should configure MySQL for the slave replica (and to use UTC as time-zone for RDBMS), confiugre Mosquitto to forward topics to current back-end server. Please provide me IP of the server to allow access.

After these steps you will be able to install BrandMeister package. You need to do configuration after installation. BrandMeister will do automatic activation on the first run. I am strongly recommend you to delegate the responsibility of deployment to our team. In this case please follow next steps:

  1. Prepare a server: the solution requires a publically available server based on Debian x64 version 8.x with public static IP. You can use VM based on vmWare or KVM. Please do not use OpenVZ.
  2. Give us access to deploy initial configuration of BrandMeister. It requires to install and configure several components such as MySQL, Memcached, Mosquitto.
  3. You need some time to learn paradigm of the system, how to manage and program the configuration. We will support you.
  4. The server will be under your full control, we should have access to update and make fixes the system.

Please send your questions and requests to our Yahoo group or directly to me.

73 de R3ABM

Before reading this document I ask you to accept our policy: we suggest to use not more than one server for each country. Of course, exceptions to this rule can be discussed.

BrandMeister solution contains 3 main parts: - real-time front-end BrandMeister DMR Server - middle-ware MySQL, Memcached, Mosquitto - back-end

BrandMeister does all work of switching DMR calls, comunication with repeaters, other servers and running specific DMR applications like ARS, RRS, LRRP, IP transport, Parrot, etc. It uses MySQL database in read-only mode to read user profiles and routes, Memcached is used in read-write mode to manage routes and Mosquitto is used to send network events. Currently we use centralized work-around solution based on Python for back-end. It processes events received from Mosquitto and writes data to the database. All servers have slave databases that have replica from master database placed near current back-end. We planned to develop the target back-end system named CallDirector but now we have no free time for it. We are ready for collaboration to develop it. CallDirector should use mesh-network technilogies and active-active replication schema to syncronize profile data.

At this moment you need to prepare the host. After that you need to install MySQL server, Memcaced and Apache2, PHP5, php5 memcached plug-in from debian distribution. Install mosquitto from the mosquitto repositories. Install dbus-beta plug-for PHP5 in using pecl utility. Configure iptables (I'll give you an example). Next we should configure MySQL for the slave replica (and to use UTC as time-zone for RDBMS), confiugre Mosquitto to forward topics to current back-end server. Please provide me IP of the server to allow access.

After these steps you will be able to install BrandMeister package. You need to do configuration after installation. BrandMeister will do automatic activation on the first run. I am strongly recommend you to delegate the responsibility of deployment to our team. In this case please follow next steps:

  1. Prepare a server: the solution requires a publically available server based on Debian x64 version 8.x with public static IP. You can use VM based on vmWare or KVM. Please do not use OpenVZ.
  2. Give us access to deploy initial configuration of BrandMeister. It requires to install and configure several components such as MySQL, Memcached, Mosquitto.
  3. You need some time to learn paradigm of the system, how to manage and program the configuration. We will support you.
  4. The server will be under your full control, we should have access to update and make fixes the system.

Please send your questions and requests to our Yahoo group or directly to me.

73 de R3ABM