Great work Akila! Community: please verify the release artifacts and vote!
On Sun, Aug 30, 2015 at 1:08 PM, Akila Ravihansa Perera
wrote:
> I've now fixed Kubernetes cluster update issue and marked the JIRA [1] as
> resolved. We have now completed planned fixes for 4.1.2 release.
>
> [1] https:/
I've now fixed Kubernetes cluster update issue and marked the JIRA [1] as
resolved. We have now completed planned fixes for 4.1.2 release.
[1] https://issues.apache.org/jira/browse/STRATOS-1532
On Fri, Aug 28, 2015 at 9:10 PM, Imesh Gunaratne wrote:
> +1 for the integration tests Akila!
>
> On
+1 for the integration tests Akila!
On Fri, Aug 28, 2015 at 2:41 AM, Akila Ravihansa Perera
wrote:
> We have now fixed the PCA Git push issue. Also introduced integration
> tests to cover those scenarios. Will proceed with the release.
>
> On Wed, Aug 26, 2015 at 3:05 PM, Imesh Gunaratne wrote:
We have now fixed the PCA Git push issue. Also introduced integration tests
to cover those scenarios. Will proceed with the release.
On Wed, Aug 26, 2015 at 3:05 PM, Imesh Gunaratne wrote:
> Thanks for the update Akila!
>
> On Wed, Aug 26, 2015 at 11:34 AM, Akila Ravihansa Perera <
> raviha...@w
Thanks for the update Akila!
On Wed, Aug 26, 2015 at 11:34 AM, Akila Ravihansa Perera wrote:
> Hi Imesh,
>
> Had an offline discussion with Pubudu and he has fixed an issue in auto
> commit feature of PCA. Once the fix is merged, I'll proceed with the
> release. The fix is to stage all the files
Hi Imesh,
Had an offline discussion with Pubudu and he has fixed an issue in auto
commit feature of PCA. Once the fix is merged, I'll proceed with the
release. The fix is to stage all the files in Git repo and commit them all.
Currently we are reading unstaged files but not doing anything with it.
@Akila: Would you mind giving an update on the release?
Thanks
On Tuesday, August 25, 2015, Akila Ravihansa Perera
wrote:
> Hi,
>
> There was an issue in application deployment logic which caused a NPE to
> be thrown intermittently when deploying an application. The root cause of
> the issue wa
Hi,
There was an issue in application deployment logic which caused a NPE to be
thrown intermittently when deploying an application. The root cause of the
issue was that autoscaler was creating the cluster monitors before
publishing the ApplicationCreatedEvent. The cluster monitors in turn
publish
Hi all,
Release build in process. Please hold your commits.
Thanks.
On Sat, Aug 22, 2015 at 12:45 PM, Imesh Gunaratne wrote:
> Great work Akila! May be we can do the release build now.
>
> On Sat, Aug 22, 2015 at 10:28 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi,
>>
>> I'
Great work Akila! May be we can do the release build now.
On Sat, Aug 22, 2015 at 10:28 AM, Akila Ravihansa Perera wrote:
> Hi,
>
> I've tested all supported IaaS types and verified the functionality.
> Pushed jclouds 1.9.1 upgrade + GCE fix to master branch.
> I've also added Carbon kernel patc
Hi,
I've tested all supported IaaS types and verified the functionality. Pushed
jclouds 1.9.1 upgrade + GCE fix to master branch.
I've also added Carbon kernel patches up to patch0012 to Stratos. Marked
relevant JIRAs as resolved.
Thanks.
On Fri, Aug 21, 2015 at 11:35 AM, Imesh Gunaratne wrote:
A great analysis!! It's really nice to hear that you were able to identify
the exact problem and come up with a way to solve it. Great work as always!!
I'm +1 to include this in 4.1.2 if we can verify all the IaaS features
related to EC2, OpenStack & GCE with this modification. IMO this change
wil
Hi Imesh,
That is totally fine since it was a blocker for the release. But I have
some news regarding the issue we had with GCE jclouds API. After few days
of debugging I was able to narrow down the root cause which turned out to
be incorrect import/export problem in OSGi bundles. All the bundles
On Thu, Aug 20, 2015 at 3:29 PM, Lakmal Warusawithana
wrote:
>
>
> You mean 4.1.2 I guess.
>
Yes, my mistake, its 4.1.2 :-)
On Thu, Aug 20, 2015 at 3:29 PM, Lakmal Warusawithana
wrote:
>
>
> On Thu, Aug 20, 2015 at 3:28 PM, Imesh Gunaratne wrote:
>
>> Hi All,
>>
>> @Akila: I'm sorry we had t
On Thu, Aug 20, 2015 at 3:28 PM, Imesh Gunaratne wrote:
> Hi All,
>
> @Akila: I'm sorry we had to revert the changes of jclouds 1.9 upgrade to
> avoid the blocking issue with GCE provider. Will try to fix this locally
> and then include it in 4.1.3:
> https://github.com/apache/stratos/commits/mas
Hi All,
@Akila: I'm sorry we had to revert the changes of jclouds 1.9 upgrade to
avoid the blocking issue with GCE provider. Will try to fix this locally
and then include it in 4.1.3:
https://github.com/apache/stratos/commits/master
IMO we are now go to verify 4.1.3 and do the release build.
Tha
The problem with the GCE jclouds provider can be found here:
https://issues.apache.org/jira/browse/STRATOS-1516
On Thu, Aug 20, 2015 at 1:53 PM, Imesh Gunaratne wrote:
> Thanks for the feedback Lakmal!
>
> As we have encountered issues with Kernel patch upgrade and jclouds 1.9
> upgrade shall we
Thanks for the feedback Lakmal!
As we have encountered issues with Kernel patch upgrade and jclouds 1.9
upgrade shall we move those to the next minor release 4.1.3?
I think we might need to revert jclouds 1.9 upgrade changes.
On Thu, Aug 20, 2015 at 9:25 AM, Lakmal Warusawithana
wrote:
>
>
> O
On Tue, Aug 18, 2015 at 3:54 PM, Imesh Gunaratne wrote:
> Hi Devs,
>
> Thanks for all your efforts on releasing 4.1.1 within a very short time
> period. IMO it was a great accomplishment! It took nearly an year for us to
> release 4.1.0 after 4.0.0.
>
> Shall we now plan for 4.1.2 with the follow
Hi Devs,
Thanks for all your efforts on releasing 4.1.1 within a very short time
period. IMO it was a great accomplishment! It took nearly an year for us to
release 4.1.0 after 4.0.0.
Shall we now plan for 4.1.2 with the following items?
TaskOwnerStatusJIRA1Update Carbon Kernel patches (Critical
20 matches
Mail list logo
