Re: Messaging Subscriber Process - Was: ([Discuss] SNMP Alerts support in CloudStack)

2013-01-18 Thread Murali Reddy
> >So if I understand this correctly, the message bus is only used by the >management server as a queue for events to forward to some other >endpoint? Chip, Message bus is just abstraction (with publish, subscribe, unsubscribe semantics), used to push action events, alerts, usage events and reso

Re: Messaging Subscriber Process - Was: ([Discuss] SNMP Alerts support in CloudStack)

2013-01-18 Thread Chip Childers
On Mon, Jan 7, 2013 at 8:02 AM, Murali Reddy wrote: > > On 04/01/13 8:19 PM, "Chip Childers" 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 >> wrote: >>> Why would CloudStack need an API to registe

Re: Messaging Subscriber Process - Was: ([Discuss] SNMP Alerts support in CloudStack)

2013-01-07 Thread Murali Reddy
On 04/01/13 8:19 PM, "Chip Childers" 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 > wrote: >> Why would CloudStack need an API to register subscribers? >> Wouldn¹t they directly go to the broker? > >I

Messaging Subscriber Process - Was: ([Discuss] SNMP Alerts support in CloudStack)

2013-01-04 Thread Chip Childers
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 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