On 04/01/13 8:19 PM, "Chip Childers" <chip.child...@sungard.com> wrote:
>Splitting this out of the SNMP thread, as I think it needs it's own >discussion. > >On Thu, Jan 3, 2013 at 6:56 PM, Chiradeep Vittal ><chiradeep.vit...@citrix.com> wrote: >> Why would CloudStack need an API to register subscribers? >> Wouldn¹t they directly go to the broker? > >I agree. Shouldn't the subscription process be delegated to the broker >itself? Do not think message broker by themselves are not necessarily directly exposed for subscription. I think you still need a service through which to register endpoint (web call back URL or SMS etc) to receive notifications. For e.g in public cloud, if tenant's on-premise monitoring component wish to receive notification for occurrence of event he can register a endpoint with notification service which acts as proxy for broker. Though, I agree that notification service it self, need not be part of CloudStack. > >> On 12/20/12 3:46 AM, "Murali Reddy" <murali.re...@citrix.com> wrote: >> >>> >>>> >>>>Hey Murali, >>>> >>>>Great to hear about where you stand right now. Is the code (work in >>>>progress obviously) available on one of the branches? I'd love to >>>>take a look at it. >>>> >>>>-chip >>>> >>> >>> >>>Chip >>> >>>I have been using 'events-framework' branch for this work. Please take a >>>look at 'framework/events/src/org/apache/cloudstack/framework/events' >>>for >>>event bus abstraction and the specific AMQP client implementation and >>>'plugins/event-bus/rabbitmq/src/org/apache/cloudstack/mom/rabbitmq' for >>>a >>>Rabbit AM AMQP client that implements EventBus. >>> >>>Thanks, >>>Murali >>> >> >> >
