Hi Raj,
On Thu, Feb 19, 2015 at 11:25 PM, Rajkumar Rajaratnam
wrote:
>
>
> On Sat, Feb 7, 2015 at 11:47 PM, Reka Thirunavukkarasu
> wrote:
>
>> Hi Imesh,
>>
>> Since we have introduced the Composite Application model where more than
>> one clusters present, we are no longer using cluster create
On Sat, Feb 7, 2015 at 11:47 PM, Reka Thirunavukkarasu
wrote:
> Hi Imesh,
>
> Since we have introduced the Composite Application model where more than
> one clusters present, we are no longer using cluster created event in order
> to avoid unnecessary complication when registering the Application
Hi Imesh,
Since we have introduced the Composite Application model where more than
one clusters present, we are no longer using cluster created event in order
to avoid unnecessary complication when registering the ApplicationMonitor.
Let me explain the flow little bit here,
1. Deploy application
+1 to remove the cluster created event from the Topology. As we have
implemented in a way to listen for all the clusters to be created at once,
it may add more complexity now, if we change to cluster created event.
I think that cartridge agent and others can use the ClusterInstanceCreated
in order
Hi Reka,
Thanks for the detailed explanation!
I understand your concern on aggregating cluster created events together
and sending one event, but I still prefer to send separate events for each
cluster, because there might be listeners who are interested on this event
to take actions (cartridge e
Hi Reka,
I just noticed that we are no longer using Cluster Created event, rather we
have introduced a new event called Application Clusters Created and
aggregating all the clusters of an application in that.
What was the reason for this?
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Commit
