Great work Akila! This is definitely a tremendous improvement.
On Wed, Nov 11, 2015 at 3:27 PM, Akila Ravihansa Perera
wrote:
> Hi,
>
> I've implemented the following improvements and merged in [1]. JIRAs
> created [2, 3, 4] to track these tasks.
>
> - On-demand initialization of complete topol
Hi,
I've implemented the following improvements and merged in [1]. JIRAs
created [2, 3, 4] to track these tasks.
- On-demand initialization of complete topology
- On-demand initialization of complete application topology
- On-demand initialization of complete tenant model
- On-demand initiali
On Tue, Nov 10, 2015 at 8:42 AM, Akila Ravihansa Perera
wrote:
> Hi,
>
> I've updated Python agent to use this method to initialize the topology.
> Also extended the same logic to initialize complete application model.
>
> @Imesh: Sure, will do a thorough test before merging.
>
> @Isuru: I think
Hi,
I've updated Python agent to use this method to initialize the topology.
Also extended the same logic to initialize complete application model.
@Imesh: Sure, will do a thorough test before merging.
@Isuru: I think we cannot get rid of complete topology synchronization task
(periodically publ
Great work Akila. Just to clarify, are we removing the Complete Topology
event and its usages?
On Tue, Nov 10, 2015 at 4:16 AM, Imesh Gunaratne wrote:
> Great work Akila!
>
> Please do a thorough test and make sure everything is covered before
> pushing this change to the current code base. If n
Great work Akila!
Please do a thorough test and make sure everything is covered before
pushing this change to the current code base. If not I would like to
suggest to push this to the next major release.
Thanks
On Sun, Nov 8, 2015 at 10:35 PM, Akila Ravihansa Perera
wrote:
> Hi all,
>
> I took
Hi all,
I took the liberty of implementing topology init optimization since that
will speed of lot of things that we're trying to do :)
Here is my approach;
- Introduce a new topic called "initialization" topic
- Introduce a new event called "CompleteTopologyRequestEvent"
- Create a message rec
+1 for this approach. I hope PCA plugins will be able to use this.
On Thu, Sep 10, 2015 at 10:17 AM, Udara Liyanage wrote:
> +1
>
> On Thu, Sep 10, 2015 at 10:16 AM, Reka Thirunavukkarasu
> wrote:
>
>> +1. Great thought. It would increase the startup time of the components
>> those who listens
+1
On Thu, Sep 10, 2015 at 10:16 AM, Reka Thirunavukkarasu
wrote:
> +1. Great thought. It would increase the startup time of the components
> those who listens to CompleteTopology and PCA.
>
> Thanks,
> Reka
>
> On Thu, Sep 10, 2015 at 1:09 AM, Imesh Gunaratne wrote:
>
>> Hi Devs,
>>
>> I would
+1. Great thought. It would increase the startup time of the components
those who listens to CompleteTopology and PCA.
Thanks,
Reka
On Thu, Sep 10, 2015 at 1:09 AM, Imesh Gunaratne wrote:
> Hi Devs,
>
> I would like to propose $subject.
>
> Currently we do this with a one minute interval and it
On Thu, Sep 10, 2015 at 1:29 AM, Akila Ravihansa Perera
wrote:
>
> Shall we call the topic as 'initializer' to be generic? We can further
> extend this to Application hierarchy model initialization and tenant model
> initialization using the same topic. These are also published periodically
> by
Hi Imesh,
Great thought. This will considerably speed up instance activation process.
Shall we call the topic as 'initializer' to be generic? We can further
extend this to Application hierarchy model initialization and tenant model
initialization using the same topic. These are also published per
Hi Devs,
I would like to propose $subject.
Currently we do this with a one minute interval and its causing the
cartridge agent and the servers to wait for around two minutes (in the
worst case) to start. In Docker this is a considerable amount of delay.
I think we can implement $subject by intro
13 matches
Mail list logo
