Most of them are outdated, but provide historical design context.
They are not user documentation and should not be treated as such.
Documentation is available here.
Introduction of messaged based communication using JSON-RPC on top of various transport protocols
Using a phased approach, we are going to a point where messaging is the main communication model between the engine and VDSM as well as the numerous VDSM subsystems. The biggest difference between current implementation and the goal is communication model change from synchronous HTTP to asynchronous TCP. The XML message format is going to be replaced with JSON, which will reduce parsing time.
Advantages Of JsonRPC Over XmlRPC
- Less data send over the wire
- Faster parsing of message content
- Asynchronous communication
- Enable broker usage by using stomp 1.2 protocol
- Maintains connection and uses heart beats to check its health
- Name: Saggi Mizrahi (smizrahi)
- Email: email@example.com
- Last updated on – by (WIKI)
- Were currently in Phase 1
Below is prior state to the messaging changes. The engine uses XML-RPC over HTTP to communicate with the VDSM. There are two connections active between the engine and a VDSM.
This phase is intermediate development milestone which is not meant to be released. It makes introduction of new protocols easier and it paves the way for engine/vdms asynchronous communication. VDSM would listen on a different port for each supported transport.
The engine sends messages by using one of the protocol reactors or apache http client for xml-rpc. VDSM parses messages using appropriate transport reactor and the message body is passed to a json-rpc server for processing. The Server parses json data and calls the appropriate method on the bridge which is mapped to corresponding vdsm object responsible for performing the command.
AMQP protocol is available but not usable due to instability of the protocol implementation used.
For this phase the main addition is protocol detection. Instead of having a dedicated port per protocol there is single port used by protocol detector. It is responsible for performing SSL handshake and peeking at the first message to recognize which reactor should handle communication. After detecting the protocol it passes a socket to the correct reactor for further message processing.
This is going to be released for 3.5
Phase 3 (To be done)
For VDSM the main addition in this phase is a broker. Up until this point protocol reactors ignored brokering semantics. This change adds an actual entity with brokering semantics.
For the engine the main change is to reduce number of active connections to single VDSM. IRS and VDS will share a client using particular protocol.
Low Priority Features:
- Message acknowledgment\settlement (provided by AMQP 1.0)
There is a possibility this phase would be skipped and we would just use existing broker implementation.
Phase 4 (To be done)
In this phase VDSM subsystems would start using json-rpc communication and manage their own topics. There would still be the legacy interface but there will be a move towards a segmented and separate task management per subsystem.
Phase 5 (To be done)
In this phase internal broker will be pulled out (if we are not already using standalone broker implementation). We will remove the xml-rpc interface entirely and more subsystems are being separated. It is encouraged for VDSM subsystems to run in their own processes in this phase.