[STRATOS-155] Event Driven Messaging Model for Stratos 4.0.0

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0 Alpha
• Assignee: Unassigned
• Reporter: Imesh Gunaratne
• Created: 04/Nov/13 05:37
• Updated: 11/Feb/14 03:43
• Resolved: 11/Feb/14 03:43

Description

According to the new architecture of Stratos, internal components communicate with each other via a AMQP based message broker using topics. These messages are sent in JSON format and each message is considered as an Event.

There should be an Event Publisher and Event Subscriber implementation which could be extended for different topics and each topic could define a set of events which illustrates its life-cycle.

Topics:
1. Topology
Publisher: Cloud Controller
Subscribers: Load Balancers, Auto-Scaler, Stratos Manager

2. Instance Status
Publisher: Cartridge Agent
Subscribers: Cloud Controller

This implementation could be extracted out as a standalone component and shared among different components as the foundation for messaging.

Sub-Tasks

• Implement Events for Publishing Tenant Information: Resolved
• Implement Topology Events: Resolved
• Implement a Domain Model for managing the Topology Data Structure: Resolved
• Implement an Event Listener Model for Subscribing to Event Notificaitons: Resolved
• Introduce a Message Processor Chain Model and Extract Generic Functionality in Topology Event Message Delegator: Resolved