IMHO, adding an artificial delay won't make it realistic. There are many
other parameters and conditions which are different from mock iaas to
actual iaases. What we need is a set of live tests to cover those
scenarios. For eg. jclouds has live tests for each iaas platform.
On Tuesday, 8 December
On Mon, Dec 7, 2015 at 4:09 PM, Akila Ravihansa Perera
wrote:
> Hi,
>
> I've fixed the warning message with commit [1]. The root cause is CC will
> throw an exception if the member instance id is null in the member
> termination flow. But the lock is acquired after the exception is thrown.
> Ther
Hi,
I've fixed the warning message with commit [1]. The root cause is CC will
throw an exception if the member instance id is null in the member
termination flow. But the lock is acquired after the exception is thrown.
Therefore it will never reach to the point where lock is acquired. I've
fixed i
Did anyone of you able to reproduce this? I was trying with mock iaas, but
I didn't encounter this error
On Sun, Dec 6, 2015 at 9:02 PM, Gayan Gunarathne wrote:
>
>
> On Sun, Dec 6, 2015 at 10:47 AM, Isuru Haththotuwa
> wrote:
>
>> Hi Akila,
>>
>> On Sun, Dec 6, 2015 at 10:26 AM, Akila Ravihans
On Sun, Dec 6, 2015 at 10:47 AM, Isuru Haththotuwa
wrote:
> Hi Akila,
>
> On Sun, Dec 6, 2015 at 10:26 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Isuru,
>>
>> While I agree that it is hard to handle scenarios like this in Stratos
>> given the current architecture and design
On Sun, Dec 6, 2015 at 9:45 AM, Imesh Gunaratne wrote:
> Yes I agree with Isuru, however we should be able to raise a more
> meaningful error message in a such situation. If an instance has not
> initialized at the time the termination call is made, we should be able to
> tell that to the end use
Hi Akila,
On Sun, Dec 6, 2015 at 10:26 AM, Akila Ravihansa Perera
wrote:
> Hi Isuru,
>
> While I agree that it is hard to handle scenarios like this in Stratos
> given the current architecture and design, I believe pitfalls like this
> could end up being a huge overhead for its users. Not only t
Hi Isuru,
While I agree that it is hard to handle scenarios like this in Stratos
given the current architecture and design, I believe pitfalls like this
could end up being a huge overhead for its users. Not only they would have
to maintain a PaaS but they will also have to monitor the logs or IaaS
Yes I agree with Isuru, however we should be able to raise a more
meaningful error message in a such situation. If an instance has not
initialized at the time the termination call is made, we should be able to
tell that to the end user clearly.
[2015-12-06 00:29:51,337] WARN
{org.apache.stratos.c
On Sun, Dec 6, 2015 at 12:37 AM, Akila Ravihansa Perera
wrote:
> I tried to deploy an application on EC2 and immediately undeployed it
> which caused the following exception. Also the EC2 instance did not get
> terminated. Noticed the following warning in the log;
>
> [2015-12-06 00:29:51,337] W
Also we found another issue with the LB extension thrift configurations[1].
Those configurations are not update correctly with our new
configurations.Shall we fix those issues and go with the rc3 release?
[1]
https://github.com/apache/stratos/blob/4.1.5-rc2/extensions/load-balancer/modules/nginx-e
On Sun, Dec 6, 2015 at 12:37 AM, Akila Ravihansa Perera
wrote:
> I tried to deploy an application on EC2 and immediately undeployed it
> which caused the following exception. Also the EC2 instance did not get
> terminated. Noticed the following warning in the log;
>
Are you un-deploy the applica
I tried to deploy an application on EC2 and immediately undeployed it which
caused the following exception. Also the EC2 instance did not get
terminated. Noticed the following warning in the log;
[2015-12-06 00:29:51,337] WARN
{org.apache.stratos.common.concurrent.locks.ReadWriteLock} - System
w
We have few issues in Docker scripts. There are some SNAPSHOT references
[1, 2] which breaks Docker images.
[1]
https://github.com/apache/stratos/blob/4.1.5-rc2/tools/docker-images/cartridge-docker-images/base-image/Dockerfile#L25
[2]
https://github.com/apache/stratos/blob/4.1.5-rc2/tools/docker-
Modify it as 4.1.5-rc2
Thanks,
Gayan
On Sat, Dec 5, 2015 at 12:04 PM, Akila Ravihansa Perera
wrote:
> Hi Gayan,
>
> The vote is for the tag, not the binaries. Therefore we need to tag the
> code in order to vote.
>
> Also we do not tag with a release version (4.1.5) until the vote has
> passed
Hi Gayan,
The vote is for the tag, not the binaries. Therefore we need to tag the
code in order to vote.
Also we do not tag with a release version (4.1.5) until the vote has
passed.
Could you please fix it?
Thanks.
On Friday, 4 December 2015, Imesh Gunaratne wrote:
> Hi Gayan,
>
> I do not s
Hi Gayan,
I do not see the 4.1.5-rc2 tag, have we created it as 4.1.5?
Thanks
On Thu, Dec 3, 2015 at 10:01 AM, Gayan Gunarathne wrote:
> Hi All,
>
> This thread is for discussion of the second release candidate for Apache
> Stratos 4.1.5. Please use this thread for discussion of issues uncover
Hi All,
This thread is for discussion of the second release candidate for Apache
Stratos 4.1.5. Please use this thread for discussion of issues uncovered in
the RC, questions you may have about the RC, etc.
The RC release packs could be found here [1]. A git tag (4.1.5) [2] has
been created for t
18 matches
Mail list logo
