e.org>
Cc: Abhinandan Prateek
Subject: Re: Event Publish and Subscribe ( was perhaps Re: Cloudstack Questions
)
It also makes sense in a private cloud context as well. There's nothing
different about public versus private on this matter, except the public cloud
is going to have a lot more i
;> From: Chip Childers [mailto:chip.child...@sungard.com]
>>> Sent: Thursday, June 07, 2012 7:15 PM
>>> To: cloudstack-dev@incubator.apache.org
>>> Cc: Chiradeep Vittal
>>> Subject: Re: Event Publish and Subscribe ( was perhaps Re: Cloudstack
>>> Ques
>To: cloudstack-dev@incubator.apache.org
>>Cc: Chiradeep Vittal
>>Subject: Re: Event Publish and Subscribe ( was perhaps Re: Cloudstack
>>Questions )
>>
>>On Thu, Jun 7, 2012 at 7:18 AM, Abhinandan Prateek
>> wrote:
>>> Planning to use apache Qpid implementatio
al
>Subject: Re: Event Publish and Subscribe ( was perhaps Re: Cloudstack
>Questions )
>
>On Thu, Jun 7, 2012 at 7:18 AM, Abhinandan Prateek
> wrote:
>> Planning to use apache Qpid implementation of AMQP for publishing
>cloudstack events.
>
>+1 for implementing even
On Thu, Jun 7, 2012 at 7:18 AM, Abhinandan Prateek
wrote:
> Planning to use apache Qpid implementation of AMQP for publishing cloudstack
> events.
+1 for implementing event notification via AMQP. This will be really
helpful in more advanced deployment environments. It would also be
great if th
10:40 PM
>To: George Reese; cloudstack-dev@incubator.apache.org
>Cc: Nitin Mehta; Kishan Kavala; Dean
>Subject: Re: Event Publish and Subscribe ( was perhaps Re: Cloudstack
>Questions )
>
>While embedding the publisher inside CloudStack could be one way to go, it is
>probably
t; -Original Message-----
>>> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
>>> Sent: Saturday, May 12, 2012 3:48 AM
>>> To: cloudstack-dev@incubator.apache.org
>>> Cc: Dean
>>> Subject: Re: Event Publish and Subscribe ( was perhaps Re: Cl
ubator.apache.org>>
Cc: Nitin Mehta mailto:nitin.me...@citrix.com>>, Kishan
Kavala mailto:kishan.kav...@citrix.com>>, Dean
mailto:cl...@tizatron.com>>, Chiradeep Vittal
mailto:chiradeep.vit...@citrix.com>>
Subject: Re: Event Publish and Subscribe ( was perhaps Re: C
> Are there any use-cases for which it make sense to have publishers (that use
> CloudStack API to publish) other than CloudStack? If its not overkill we can
> have generic mechanism of publish/subscribe as service in CloudStack. I can
> think of tenants workload VM's be able to leverage this and
; We can extend this to publish the events to registered
>>> listeners/subscribers.
>>>
>>> Nitin,
>>> We should evaluate the google guava package for this purpose.
>>>
>>> -abhi
>>>
>>>> -Original Message-
&g
Are there any use-cases for which it make sense to have publishers (that
use CloudStack API to publish) other than CloudStack? If its not overkill
we can have generic mechanism of publish/subscribe as service in
CloudStack. I can think of tenants workload VM's be able to leverage this
and publish
hiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
>>> Sent: Saturday, May 12, 2012 3:48 AM
>>> To: cloudstack-dev@incubator.apache.org
>>> Cc: Dean
>>> Subject: Re: Event Publish and Subscribe ( was perhaps Re: Cloudstack
>>> Questions )
>>>
>
his purpose.
>
> -abhi
>
>> -Original Message-
>> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
>> Sent: Saturday, May 12, 2012 3:48 AM
>> To: cloudstack-dev@incubator.apache.org
>> Cc: Dean
>> Subject: Re: Event Publish and Subscribe
t;From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
>Sent: Saturday, May 12, 2012 3:48 AM
>To: cloudstack-dev@incubator.apache.org
>Cc: Dean
>Subject: Re: Event Publish and Subscribe ( was perhaps Re: Cloudstack
>Questions )
>
>+1.
>This could also be used for example
+1.
This could also be used for example to update DNS records on a DNS server
whenever a VM is started / stopped in a network.
A subscriber to the event bus can do this, and potentially things like
updating a CMDB or an LDAP server.
The important caveat is that this will be asynchronous to the st
+1
Makes sense to have pubsub. Inside the java codebase, we could consider a
clean and idiomatic lib like guava which is easy to unit test.
http://codingjunkie.net/guava-eventbus/
Then, expose out-of-JVM hooks for any of the popular services people use.
-A
On May 11, 2012 1:58 PM, "Dean" wrot
16 matches
Mail list logo
