Hi All,
I have published a new screencast for this project which includes recent
changes. You can find it at [1].
Please let me know if you have any suggestions.
[1] https://youtu.be/sCmu9b0oMmc
Thanks and Regards,
Swapnil
On Wed, Jul 22, 2015 at 3:36 PM, Imesh Gunaratne wrote:
> Yes today i
Yes today in a demo Swapnil showed this issue to us. We need to investigate
the load balancer extension and see the reason for this problem.
Thanks
On Wed, Jul 22, 2015 at 9:21 AM, Swapnil Patil
wrote:
> Hi Imesh, Lakmal,
>
> I observed the extension log to find out that, extension's configure
Hi Imesh, Lakmal,
I observed the extension log to find out that, extension's configure method
is indeed called after member is activated but before it is added to
cluster. I assume that is why extension cannot see the newly activated
member as a part of cluster.
I hope this is what we expect.
Th
On Mon, Jul 20, 2015 at 9:20 PM, Swapnil Patil
wrote:
>
>
> Though there was some time lag for the extension to get to know the newly
> spawned instance. When a new instance is spawned the extension's configure
> method got called but the topology did not have this new member. This new
> member w
On Mon, Jul 20, 2015 at 9:20 PM, Swapnil Patil
wrote:
> Hi Lakmal,
>
> I tested the extension for scale up and scale down. And it did work as
> expected. It attached the the newly spawned instances to the LB while
> scaling up and detached the terminated instances from LB.
>
> Though there was so
Thanks Asanka!
Just wondering if adding some time delay in configure method of extension
itself, before proceeding further, solved this temporarily?
Regards,
Swapnil
On Mon, Jul 20, 2015 at 3:56 PM, Asanka Sanjaya Herath
wrote:
> Hi swapnil,
>
> Yes I had this issue.
>
> On Mon, Jul 20, 2015 a
Hi swapnil,
Yes I had this issue.
On Mon, Jul 20, 2015 at 9:20 PM, Swapnil Patil
wrote:
> Hi Lakmal,
>
> I tested the extension for scale up and scale down. And it did work as
> expected. It attached the the newly spawned instances to the LB while
> scaling up and detached the terminated instan
Hi Lakmal,
I tested the extension for scale up and scale down. And it did work as
expected. It attached the the newly spawned instances to the LB while
scaling up and detached the terminated instances from LB.
Though there was some time lag for the extension to get to know the newly
spawned insta
Thanks Lakmal!
I have the logic in place to attach newly created instances to LB in case
of scale up and same for scale down. But I have not tested it yet. That
testing will be my next step. I am pretty sure that it will work but it is
just that I need to verify it.
I will get to know if any serv
Great work Swapnil!
Just for my clarification, I have few question. Say when cluster scale up ,
does AWS load balancer extension attached the newly created instance to LB?
same like when scale down does it detached the deleted instance from LB?
Also when attaching and detaching does any service in
Hi AIl,
I have published screencast of AWS load balancer extension on YouTube. Here
is the link : https://youtu.be/ZNl8JVB7xeU
I would appreciate any suggestions.
Thanks and Regards,
Swapnil
11 matches
Mail list logo