Configure multitenant AMQP

This section describes how to configure multi-tenant AMQP for multiple datacenters.

For a distributed platform, Abiquo you will create a virtual host for the API and watchtower, and then separate virtual hosts for each datacenter.

To use multitenant AMQP, use a separate set of remote services for each cloud location (datacenter or public cloud region). Do not share any remote services

1 RabbitMQ multitenant properties
2 API configuration
3 Watchtower configuration
4 How to add a new data center
- 4.1 Check permissions in the new datacenter
- 4.2 Check properties in the new datacenter
5 How to run a monolithic Abiquo with multi-tenant enabled

RabbitMQ multitenant properties

Property name	Description	Context
abiquo.rabbitmq.multitenant	To enable multitenant, set to `true`. By default it is disabled (`false)`	API
abiquo.rabbitmq.virtualHost	Logical separation where the configured Abiquo service manages AMQP entities. The default virtual host is `/`	API + RS
abiquo.rabbitmq.username	Username to connect to broker + virtualHost	API + RS
abiquo.rabbitmq.password	Password to connect to broker + virtualHost	API + RS
abiquo.datacenter.id	Unique datacenter ID. For a complete description see Abiquo configuration properties#datacenter	RS

API configuration

To configure the API for multitenant AMQP.

In the abiquo.properties file, set abiquo.rabbitmq.multitenant to true
Create a virtual host for the API. The default virtual host is / and you can use this if you do not have a monolithic environment. (See the separate section below for monolithic configuration)

Create an Abiquo API user with full access to the configured virtual host. Replace admin and admin with values for your environment.

rabbitmqctl add_user admin admin
rabbitmqctl set_permissions -p / admin ".*" ".*" ".*"

Watchtower configuration

The Watchtower server must use the same virtual host as the API, and it can also use the same user.

On the Watchtower server, edit the watchtower properties files at these locations
/etc/abiquo/watchtower/emmett.properties /etc/abiquo/watchtower/delorean.properties
In each file, configure the following properties. If you do not have a separate datanode, enter the IP address of the API server. For a datanode services cluster, enter the three IP addresses, separated by commas.
abiquo.rabbitmq.username = {$RABBITMQ_USER} abiquo.rabbitmq.password = {$RABBITMQ_PASSWORD} abiquo.rabbitmq.addresses = {$SERVICES_IP_ADDRESS}:5672 abiquo.rabbitmq.virtualHost = /
Restart the abiquo-emmett and abiquo-delorean services

See Abiquo configuration properties and search for .rabbitmq..

How to add a new data center

Each datacenter in Abiquo has a unique ID configured with the abiquo.datacenter.id property. Use the value of this property as the name of a new virtual host for the datacenter.

Create a new virtual host named with the value of the abiquo.datacenter.id property value
Add a new user for the new datacenter
Configure access to the new virtual host for the Abiquo API user
Configure access to the new virtual host for the datacenter user

Check permissions in the new datacenter

To list permissions on the virtual hosts use the following commands. Log in as the api user to access the API virtual host.

Check properties in the new datacenter

On the Remote services servers (including separate V2V servers), edit the abiquo.properties file and check that the properties match the configured values.

How to run a monolithic Abiquo with multi-tenant enabled

To configure a monolithic installation:

Configure the API virtual host as the same as the monolithic datacenter (value of property abiquo.datacenter.id
Configure access to the datacenter virtual host for Abiquo API user
Note that you do not need a separate user for the datacenter

You can add any other datacenters (that are not monolithic) as described in the previous section.