Scenario Full Redundant

Scenario Full Redundant#

This scenario features all Carbonio functionalities and its intended use is any infrastructure that requires scalability and redundancy.

Due to the large number of Nodes (15) that compose the Carbonio infrastructure, this scenario is designed to be deployed by using the Ansible Playbook.

Remember to configure the internal network before starting the deployment.

The Roles installed on the 15 Nodes are:

  • Node 1: Mesh & Directory, Database

  • Node 2: Mesh, Directory Replica

  • Node 3: Mesh, Monitoring

  • Node 4: MTA AV/AS

  • Node 5: MTA AV/AS

  • Node 6: Proxy

  • Node 7: Proxy

  • Node 8: Mailstore & Provisioning

  • Node 9: Mailstore & Provisioning

  • Node 10: WSC, Files, Tasks

  • Node 11: WSC, Files, Tasks

  • Node 12: Docs & Editor, Preview

  • Node 13: Docs & Editor, Preview

  • Node 14: Video Server & Video Recording

  • Node 15: Video Server & Video Recording

Hint

To reduce the number of the VMs or IP addresses required by this scenario, you can use the same VM for example for one of the proxies and one of the Carbonio VideoServer, provided that the resources assigned to that VM suffices to accommodate both services.

Network Configuration#

The following ports must be opened on the external network, i.e., they are required for proper access to Carbonio from the Internet.

Table 6 Forwarded ports in Scenario “Full Redundant”.#

Public hostname

Ports & Service

Balanced to

mx.example.com

  • TCP 25/465/587 SMTP/S

srv4.example.com srv5.example.com

mail.example.com

  • TCP 80/443 HTTP/S

  • TCP 143/993 IMAP/S

  • TCP 110/995 POP/S

  • TCP 8636 LDAP Addresbook

srv6.example.com srv7.example.com

video.example.com

  • UDP 20000/40000 Video Streaming

    [read next section]

srv14.example.com srv15.example.com

UDP Video Streaming#

The incoming UDP streaming to the Carbonio VideoServer can be split as follows:

  1. Using one public IP address for the Carbonio VideoServer: forward one half of the UDP stream (ports 20000 to 30000) to svr14.example.com, the other half (30001/40000) to srv15.example.com

  2. Using two public IP addresses: forward one public IP to svr14.example.com (with full range 20000/40000), the other IP to srv15.example.com (with full range 20000/40000)

Contents