There are multiple ways to establish connection between external VOLTTRON platforms. Given that VOLTTRON now supports ZeroMq and RabbitMQ type of message bus with each using different type authentication mechanism, the number of different ways that agents can connect to external platforms has significantly increased. Various multi-platform deployment scenarios will be covered in this section.
Agents can directly connect to external platforms to send and receive messages. Forward historian, Data Mover agents fall under this category. The deployment steps for forward historian is described in Forward Historian Deployment and data mover historian in DataMover Historian Deployment
The platforms maintain the connection with other platforms and agents can send to and receive messages from external platforms without having to establish connection directly. The deployment steps is described in Multi Platform Router Deployment
RabbitMQ has ready made plugins such as shovel and federation to connect to external brokers. This feature is leveraged to make connections to external platforms. This is described in Multi Platform RabbitMQ Deployment
A web based admin interface to authenticate multiple instances (ZeroMq or RabbitMQ) wanting to connect to single central instance is now available. The deployment steps is described in Multi Platform Multi-Bus Deployment
VOLTTRON Central is a platform management web application that allows platforms to communicate and to be managed from a centralized server. The deployment steps is described in VOLTTRON Central Demo
Data Collector is the deployment box that has the drivers and is collecting data from devices which will be forwarded to a VOLTTRON Central.
Volttron Central (VC) is the deployment box that has the historian which will save data from all Data Collectors to the central database.
VOLTTRON_HOME is assumed to the default on both boxes (/home/<user>/.volttron).
VOLTTRON_HOME is the directory used by the platform for managing state and configuration of the platform and agents installed locally on the platform. Auth keys, certificates, the configuration store, etc. are stored in this directory by the platform.
- Forward Historian
- Setup for two ZMQ VOLTTRON instance or a ZMQ and RabbitMQ VOLTTRON instance
- Setup for two RabbitMQ VOLTTRON instances
- Testing Forward Historian
- DataMover Historian
- Multi-Platform Between Routers
- Getting Started
- Multi-Platform Configuration
- Configuration and Authentication in Setup Mode
- Setup Configuration and Authentication Manually
- Start Platform driver on VOLTTRON instance 1
- Start Listener agents on VOLTTRON instance 2 and 3
- Stopping All the Platforms
- Multi-platform RabbitMQ Deployment
- Multi-Platform Communication With RabbitMQ SSL
- Using the Federation Plugin
- Multi-Platform RPC With Federation
- Multi-Platform PubSub With Federation
- Installation Steps
- Using the Shovel Plugin
- Multi-Platform PubSub With Shovel
- Multi-Platform RPC With Shovel
- Installation Steps for Pubsub Communication
- Multi-Platform Multi-Bus
- Node Setup
- Virtual Machine Setup
- Instance Setup
- Central Instance Setup
- Node-ZMQ Instance Setup
- Node-RMQ Instance Setup
- VOLTTRON Central Deployment