[
https://issues.apache.org/jira/browse/STRATOS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-155:
------------------------------------
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.
was:
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:
1. Topology
Publisher: Cloud Controller, Subscribers: Load Balancers, Auto-Scaler, Stratos
Manager
2. Instance Status
Publisher: Cartridge Agent, Subscriber: Cloud Controller
This implementation could be extracted out as a standalone component and shared
among different components as the foundation for messaging.
> Event Driven Messaging Model for Stratos 4.0.0
> ----------------------------------------------
>
> Key: STRATOS-155
> URL: https://issues.apache.org/jira/browse/STRATOS-155
> Project: Stratos
> Issue Type: New Feature
> Reporter: Imesh Gunaratne
> Fix For: 4.0.0 Alpha 1
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
