CentOS on Azure
In this section we walk you through the steps to manually get a basic messaging configuration of the Solace PubSub+ software message broker Docker container up-and-running on a CentOS instance in Microsoft Azure.
It's assumed you have:
- An Azure account with permission to create and run a virtual machine.
- A stable version of Docker Engine installed.
As an alternative to the manual setup procedure shown on this page, there is a quick start guide in Azure that can be used to deploy either a single Solace PubSub+ software message broker or a three-node high availability (HA) cluster.
The number of CPUs and system memory required by your message broker depends on the number of client connections you need to support. By default, fresh installations of the message broker allow up to 100 client connections by default.
The following table lists the minimum number of CPUs, and the minimum value of the total memory that must be provisioned for each connection scaling tier.
Minimum System Resources Required and Recommended For Connection Scaling Tiers
|Client Connections||CPUs*||Required Minimum||Recommended Minimum|
|Virtual Memory (MiB)||Virtual Memory (MiB)||
Physical Memory (MiB)
|up to 100||2||1,903||1,903||930|
|up to 1,000||2||5,301||5,683||3,748|
|up to 10,000||4||12,892||13,266||11,321|
|up to 100,000||8||28,191||28,565||26,620|
|up to 200,000||12||53,816||53970||52,024|
*The monitoring node in a high-availability (HA) group needs only 1 CPU.
The example shown on this page is suitable for use for up to the 1,000 connection scaling tier, and is appropriately configured for testing and PoC activities. If you plan to use your message broker in a production environment, or scale above the 1,000 client connections tier, you should note that there are a number of adjustments that will be need to be made to the example and you should consult the following topics:
- General information applicable to Solace PubSub+ software message broker Docker container configuration can be found at Topics Unique to Docker Images.
- Information about setting the client scaling tier can be found at Scaling Tier Deployment Considerations.
- Information about configuring storage volumes can be found at Storage Configuration.
Use the Azure Dashboard’s Launch setup wizard to create an Azure virtual machine that you can use to run a message broker.
- On the Azure dashboard, click the Virtual Machines icon, and then click +Add.
Follow the setup wizard, and accept the recommended default settings, except as noted in the following steps.
- In the Compute window, search for the host OS you want to use.
For a CentOS 7 host, CentOS-Based 7.2 is recommended.
- In the Choose Virtual Machine Size step, select a size based on the connection scaling tier information presented in the System Requirements section.
Note: Use of the B1S virtual machine is not recommended.
- At a minimum, it is recommended that the network security group include the following inbound rules.
Soure Destination Service Action Any Any SSH(TCP/22) Allow Any Any Custom (TCP/8080) Allow Any Any Custom (TCP/55555) Allow
These port numbers are used for the following services: 22-Host SSH; 8080-SEMP / PubSub+ Manager / SolAdmin; 55555-SMF/non-compressed message data connections. Other ports can be opened as required. For a list of ports associated with message broker services, see Default Configuration for Software Message Brokers.
- Manually install and configure Docker on your CentOS host. Instructions can be found on the Docker Get Docker for CentOS Web page.
You have to set the
iptables options on the host system.
For systemd-based systems, create a
daemon.json file to set the
devicemapper Docker daemon options. For test deployments, it is recommended to set
These options are set in the
daemon.json file located in
/etc/docker/. Follow these steps to set the options.
- If Docker is not stopped, then enter this command.
>sudo systemctl stop docker
- Create the
sudo tee /etc/docker/daemon.json <<-EOF
- Apply the settings.
>sudo systemctl daemon-reload
>sudo systemctl disable docker
>sudo systemctl enable docker
>sudo systemctl start docker
Pull the message broker image from the Docker repository using these two steps:
>sudo systemctl start docker
You can use the
statuscommand to check the status of Docker.
>sudo systemctl status docker
- Pull the image:
>sudo docker pull solace-pubsub-standard
Tip: When loading is finished, you can check the image with the
>sudo docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
solace/solace-pubsub-standard latest b8a61124d92f 10 days ago 1.11GB
This example assumes that you are using Solace PubSub+ Standard. If you want to use another edition, you need to obtain the appropriate message broker package:
- Solace PubSub+ Enterprise Evaluation Edition: Go to the Solace Downloads page. Then select Download in the Solace PubSub+ Enterprise Evaluation Edition Docker Images section. You will be able to download a compressed archive file called
- Solace PubSub+ Enterprise: If you have purchased a Docker image of Solace PubSub+ Enterprise, Solace will give you information for how to download the compressed tar archive package from a secure Solace server. Contact Solace Support at email@example.com if you require assistance.
Once you've obtained the package, start Docker and load the image.
>sudo docker load -i /tmp/solace-pubsub-evaluation-<version>-docker.tar.gz
There are many options that you can set with the
docker create command that is used to build the message broker container. In this example we will show one that sets up a simple configuration suitable for a test deployment that can be used to help you become familiar with Solace PubSub+.
- Create a
>sudo tee /root/docker-create <<-EOF
sudo docker create \
--ulimit core=-1 \
--ulimit memlock=-1 \
--ulimit nofile=2448:42192 \
--env 'username_admin_globalaccesslevel=admin' \
--env 'username_admin_password=admin' \
For production deployments, there are use-case dependent factors that will impact the option and configuration key settings in the
docker createcommand. For example, the POSIX shared memory size,
nofilevalues must be set based on the connection scaling tier. For more information, see Docker Create Options Configuration, Index of Solace PubSub+ software message broker, Container Configuration Tasks, and Scaling Tiers for Software Message Brokers.
In this example, the
adminSolace CLI user and an associated password are defined at container creation through the
username_admin_passwordconfiguration keys. By default, in a message broker container, no Solace CLI users are defined, so setting these configuration keys allows the container to be administered through the Solace SolAdmin management tool without first entering the Solace CLI to create an
In the above
docker createcommand, the values of
<tag>are dependent on the message broker Docker image you previously loaded. For example, if you pulled the
latestPubSub+ Standard image from Docker, the
latest. If you loaded version 18.104.22.1682 of Solace PubSub+ Evaluation Edition, the value of
- Make the
>sudo chmod +x /root/docker-create
Create and run the message broker container on your host.
- Create the container:
Once it’s done running, a long identifier will be displayed that looks something like this:
This is the ID for the message broker container you have just created.
- Start the message broker:
>sudo docker start solace
You can use the
docker pscommand to check on the status of the message broker once it’s running.
>sudo docker ps
STATUScolumn associated with the message broker will display if the container is running and for how long.
You now have a message broker container with a basic configuration that is ready for messaging tasks. To get yourself going, you can access either of the Solace management tools PubSub+ Manager or Solace CLI to start issuing configuration or monitoring commands.
To access the Solace PubSub+ Manager:
- Open a browser and enter http://<your-message broker's-ip-address>:8080.
- Log in as user
To access the Solace CLI:
Enter the following
>sudo docker exec -it solace /usr/sw/loads/currentload/bin/cli -A
Type the following commands to enter configuration mode:
- For a list of Solace CLI commands currently supported on the message broker, refer to Software Message Broker CLI Commands.
Also, in order to fully utilize Solace's message broker features, you should familiarize yourself with the configuration operations common to both Solace PubSub+ software message brokers and appliances. For information, see the topics in the Configuration section.