Remove a Node From Carbonio Infrastructure

Contents

Remove a Node From Carbonio Infrastructure#

There are a number of scenarios in which an existing Carbonio Node must be removed from a Carbonio infrastructure within an organisation, for example:

Lifecycle Completion

The VM hosting the Node has fulfilled its purpose, such as completing a specific task, project, or testing phase.

Resource Optimisation

Free up computing resources like CPU, memory, and storage that can be used for other purposes or tasks within an organisation.

Costs

In cloud environments, disposing of unused or underutilised VMs reduces costs.

Obsolescence

The Operating system or applications running on the VM are outdated or no longer supported.

Preliminaries#

Before starting the procedure described in the remainder of this section, you need to:

  1. Have CLI access to the new Node and to the Nodes featuring the Directory Server and the Mailstore & Provisioning Roles

  2. Identify which Node (or Nodes) should be removed or replaced and which Roles they are equipped with

  3. Install these Roles on other Nodes

  4. Take note of the FQDN of the Node to be removed, because it will be needed. It will be denoted as serverHostname in the procedure.

At this point you can start the removal procedure. If you plan to remove more than one Node, execute the following steps for each Node.

Step 1, leave Carbonio Mesh

On the Node that will be dismissed, generate a Carbonio Mesh token:

# export CONSUL_HTTP_TOKEN=$(gpg -qdo - \
/etc/zextras/service-discover/cluster-credentials.tar.gpg | \
tar xOf - consul-acl-secret.json | jq .SecretID -r)

Remove the Node from the cluster:

# consul leave
Step 2, remove the Node from the Carbonio infrastructure

Log in to the Node on which the Mailstore & Provisioning Role is installed and remove the server from the infrastructure. As the zextras user, execute the command

zextras$ carbonio prov ds serverHostname
Step 3, verify removal

Log in to the Node equipped with the Directory Server Role and dump the LDAP main database: as the zextras user, execute the command

zextras$ /opt/zextras/libexec/zmslapcat /tmp/

The output will be file /tmp/ldap.bak; check that the file does no longer contain any reference to the old FQDN, i.e.,

zextras$ grep serveHostname /tmp/ldap.bak

Hint

The command can be run as either the root or zextras user.

The output of the command should be empty, meaning that the old Node is not part of the Carbonio infrastructure anymore. You can now power off the Node and decommission it.

Contents