Scenario Essential#

This scenario involves the presence of a single tenant and it is suitable for small infrastructures up to thousands of accounts that do not need the full spectrum of Carbonio features. The scenario can be deployed either using the Ansible Playbook, or manually, Node by Node. In both cases, make sure you configure the internal network.

Ansible Playbook#

This 3 Nodes scenario can be installed using Ansible: you need to setup a workstation to run Ansible playbooks (please refer to section Prepare the Ansible Environment and following for directions on setting up the workstation), then download the Ansible inventory (see below this paragraph), replace the FQDN and values present in the file according to your planned Carbonio infrastructure (please refer to Section Prepare Inventory). Once edited the inventory, you can Install Carbonio Using Ansible.

Inventory - “Essential” Scenario

Download the inventory

















Once edited the inventory, you can launch Carbonio installation by issuing from the workstation, the command (as the root user)

# ansible-playbook -u root -i ../../data/carbonio-inventory-essential carbonio-install.yml

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 2 Opened ports in Scenario Essential.#

Public hostname

Ports & Service


  • TCP 25/465/587 SMTP/S

  • TCP 80/443 HTTP/S

  • TCP 143/993 IMAP/S

  • TCP 110/995 POP/S

  • TCP 8636 LDAP Addresbook

Manual Roles Installation#

In case you do not want to install Carbonio on this scenario using Ansible, you can proceed with the manual installation of the various Roles on the Nodes, according to the following guidelines.

Before starting the installation, bear in mind to:

  • Always start with the installation of Mesh and Directory Roles

  • When installing multiple Roles on a Node, the tasks listed in Bootstrap Carbonio* and Join Carbonio Mesh steps can be made only once, after all packages of the Roles have been installed

Node 1

Node Name/FQDN:

Type of services: Clustered services

Roles installed:

Node 2

Node Name/FQDN:

Type of services: Proxy and MTA

Roles installed:

Node 3

Node Name/FQDN:

Type of services: Mails, Calendars, Contacts, and Tasks

Roles installed: