Still getting some issues. I''m getting below warning..
WARN
{org.apache.stratos.autoscaler.applications.dependency.context.ApplicationChildContextFactory}
- [Startup Order]: group.group2 contains unknown reference
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
Github user Vishanth closed the pull request at:
https://github.com/apache/stratos/pull/142
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
Great ! and Thank you !
Shiroshica Kulatilake
WSO2, Inc. http://wso2.com/
Phone: +94 776523867
On Tue, Jan 13, 2015 at 12:19 PM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:
> Thanks Shiro for reminding. I closed my merged PR.
>
> On Tue, Jan 13, 2015 at 12:14 PM, Shiroshica Kulatilake
Thanks Shiro for reminding. I closed my merged PR.
On Tue, Jan 13, 2015 at 12:14 PM, Shiroshica Kulatilake
wrote:
> Thank you Gayan and Dakshika !
>
>
> On Tue, Jan 13, 2015 at 11:11 AM, Shiroshica Kulatilake
> wrote:
>
>>
>> On Tue, Jan 13, 2015 at 11:05 AM, Imesh Gunaratne
>> wrote:
>>
>>> A
Github user swgkg commented on the pull request:
https://github.com/apache/stratos/pull/110#issuecomment-69702343
Those changes are already merged.Hence closing the PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If yo
Thank you Gayan and Dakshika !
On Tue, Jan 13, 2015 at 11:11 AM, Shiroshica Kulatilake
wrote:
>
> On Tue, Jan 13, 2015 at 11:05 AM, Imesh Gunaratne
> wrote:
>
>> AFAIK only the people who opened the PRs can close them.
>>
> Yes !
>
>
>> Thanks
>> On Jan 13, 2015 10:55 AM, "Dakshika Jayathilaka
Github user swgkg closed the pull request at:
https://github.com/apache/stratos/pull/110
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Github user shirolk closed the pull request at:
https://github.com/apache/stratos/pull/166
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
GitHub user shirolk opened a pull request:
https://github.com/apache/stratos/pull/166
Removed unwanted methods in REST API and urls from CLI
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shirolk/stratos master-rest-clean
Alter
Hi Dakshika,
In the "composite_application.json" start-up order should be as follows.
"startupOrders": [
"group.group1,cartridge.c4"
],
It should be with the cartridge type/group name.
I have updated the samples with that.Please check again with that.
Than
On Tue, Jan 13, 2015 at 11:05 AM, Imesh Gunaratne wrote:
> AFAIK only the people who opened the PRs can close them.
>
Yes !
> Thanks
> On Jan 13, 2015 10:55 AM, "Dakshika Jayathilaka"
> wrote:
>
>> Hi Shiro,
>>
>> I closed certain merged PR created by me.
>>
>> Thank you,
>>
>> Regards,
>>
>>
[
https://issues.apache.org/jira/browse/STRATOS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274753#comment-14274753
]
ASF GitHub Bot commented on STRATOS-791:
Github user swgkg closed the pull reques
[
https://issues.apache.org/jira/browse/STRATOS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274752#comment-14274752
]
ASF GitHub Bot commented on STRATOS-791:
Github user swgkg commented on the pull
Github user swgkg commented on the pull request:
https://github.com/apache/stratos/pull/91#issuecomment-69698234
This is merged with PR#87.Hence closing this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pro
Github user swgkg closed the pull request at:
https://github.com/apache/stratos/pull/91
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Github user swgkg closed the pull request at:
https://github.com/apache/stratos/pull/83
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Github user swgkg commented on the pull request:
https://github.com/apache/stratos/pull/83#issuecomment-69698161
Those changes are merged with PR#110.Hence closing this PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user swgkg closed the pull request at:
https://github.com/apache/stratos/pull/56
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Github user swgkg commented on the pull request:
https://github.com/apache/stratos/pull/56#issuecomment-69698110
This is merged with #110. Hence closing the PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proje
AFAIK only the people who opened the PRs can close them.
Thanks
On Jan 13, 2015 10:55 AM, "Dakshika Jayathilaka" wrote:
> Hi Shiro,
>
> I closed certain merged PR created by me.
>
> Thank you,
>
> Regards,
>
> *Dakshika Jayathilaka*
> Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
>
Hi Shiro,
I closed certain merged PR created by me.
Thank you,
Regards,
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Tue, Jan 13, 2015 at 10:35 AM, Shiroshica Kulatilake
wrote:
> Hi Devs,
>
> There are 22 pull requests at https://github.com/apa
Thanks Shiro for remind this. Yeah there are lot of PR we can close as they
are already merged with the codebase. Will check those and close the
relevant PRs.
Thanks,
Gayan
On Tue, Jan 13, 2015 at 10:35 AM, Shiroshica Kulatilake
wrote:
> Hi Devs,
>
> There are 22 pull requests at https://github
[
https://issues.apache.org/jira/browse/STRATOS-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274729#comment-14274729
]
ASF GitHub Bot commented on STRATOS-1014:
-
Github user dakshika closed the pull
[
https://issues.apache.org/jira/browse/STRATOS-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274728#comment-14274728
]
ASF GitHub Bot commented on STRATOS-1014:
-
Github user dakshika commented on the
Github user dakshika closed the pull request at:
https://github.com/apache/stratos/pull/139
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
Github user dakshika commented on the pull request:
https://github.com/apache/stratos/pull/139#issuecomment-69697068
Thanks
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabl
Github user dakshika commented on the pull request:
https://github.com/apache/stratos/pull/150#issuecomment-69697040
Thanks imesh
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user dakshika closed the pull request at:
https://github.com/apache/stratos/pull/150
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
Github user dakshika closed the pull request at:
https://github.com/apache/stratos/pull/153
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
Github user dakshika closed the pull request at:
https://github.com/apache/stratos/pull/155
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
Github user dakshika closed the pull request at:
https://github.com/apache/stratos/pull/161
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
Github user dakshika closed the pull request at:
https://github.com/apache/stratos/pull/156
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
Thank you Gayan..
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Tue, Jan 13, 2015 at 10:46 AM, Gayan Gunarathne wrote:
> Seems this is happen when set of groups contain within the group. I will
> check this with the sample.
>
> Thanks,
> Gayan
>
>
Seems this is happen when set of groups contain within the group. I will
check this with the sample.
Thanks,
Gayan
On Tue, Jan 13, 2015 at 8:46 AM, Dakshika Jayathilaka
wrote:
> @lakmal: AFAIK it won't affect to this.. *artifactRepository* is not
> using on above sample.
>
>
>
> *Dakshika Jayat
Github user Vishanth closed the pull request at:
https://github.com/apache/stratos/pull/164
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
Github user Vishanth commented on the pull request:
https://github.com/apache/stratos/pull/164#issuecomment-69696471
Thank you imesh
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featu
Hi Devs,
There are 22 pull requests at https://github.com/apache/stratos/pulls
I think most of these have already being merged into the codebase.
Shall we close off those that are already merged ?
Thank you,
Shiro
Hi,
I will work on the getting started guide.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Tue, Jan 13, 2015 at 9:33 AM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Hi All,
>
> We can add the missing and new sections to gu
Hi All,
We can add the missing and new sections to guide [1] which I have created
earlier. Now the sample artifacts are available in the code base. So we can
point to them.
[1]
https://docs.google.com/a/wso2.com/document/d/1PCVk3Cp9hIxbLRGKSnfHYVZf0XBS1G-KnK_1pIDNNGg/edit
Thanks !
On Tue, Jan 1
Hi Imesh,
Yes, I already pull the stratos/php:4.1.0-alpha image in the Kubernetes
host before running the sample application. I got the pull from yesterday
and done this test. I'll done another test and verify this.
Thanks !
On Mon, Jan 12, 2015 at 10:51 PM, Imesh Gunaratne wrote:
> Regarding
@lakmal: AFAIK it won't affect to this.. *artifactRepository* is not using
on above sample.
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Tue, Jan 13, 2015 at 8:41 AM, Dakshika Jayathilaka
wrote:
> Yes Reka, previously it works fine.
>
> No error
Also we need to add all sample artifact to test out the alpha.
On Tue, Jan 13, 2015 at 8:21 AM, Imesh Gunaratne wrote:
> Appreciate if someone can prepare the Getting Started Guide. We may need
> to include separate sections for trying out Kubernetes, EC2 and OpenStack.
>
> Thanks
>
> On Tue, Ja
Yes Reka, previously it works fine.
No errors @backend, when app deployed nested group is not initialing.
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Tue, Jan 13, 2015 at 8:29 AM, Reka Thirunavukkarasu
wrote:
> Yah..AFAIR, this sample was worki
AFAIK, there is small changed in application json structure, regarding git
repo.
On Tue, Jan 13, 2015 at 8:29 AM, Reka Thirunavukkarasu
wrote:
> Yah..AFAIR, this sample was working fine in Pre-alpha..
>
> @Dakshika, Do you get any errors while deploying the application?
>
> Thanks,
> Reka
>
> On
Yah..AFAIR, this sample was working fine in Pre-alpha..
@Dakshika, Do you get any errors while deploying the application?
Thanks,
Reka
On Mon, Jan 12, 2015 at 7:48 PM, Dakshika Jayathilaka
wrote:
> Hi Imesh,
>
> Yesterday i tested this with lahiru, he experienced same issue as wel.
>
> Thank y
Appreciate if someone can prepare the Getting Started Guide. We may need to
include separate sections for trying out Kubernetes, EC2 and OpenStack.
Thanks
On Tue, Jan 13, 2015 at 8:18 AM, Imesh Gunaratne wrote:
> Hi Devs,
>
> I think we have now completed all the features required for 4.1.0-Alp
Hi Imesh,
Yesterday i tested this with lahiru, he experienced same issue as wel.
Thank you
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Tue, Jan 13, 2015 at 8:14 AM, Imesh Gunaratne wrote:
> Hi Dakshika,
>
> Thanks for reporting this, did anyone
Hi Devs,
I think we have now completed all the features required for 4.1.0-Alpha
developer preview. Please raise if we have missed anything.
IMO we can now update JIRA and once everyone agrees we can extract
tasks/features/improvements list, create the tag and announce 4.1.0-Alpha
developer previ
Hi Dakshika,
Thanks for reporting this, did anyone else experience the same problem?
I took the latest codebase from Reka's git repository and committed to
samples folder.
Thanks
On Tue, Jan 13, 2015 at 5:02 AM, Dakshika Jayathilaka
wrote:
> Hi Devs,
>
> I have notice that group-scaling sampl
Hi Devs,
I think we need to make a small correction here, 4.1.0-Alpha would be a
developer preview and not a release. Once developer preview is ready will
review it, fix any issues, and do a release candidate. Once release
candidate is verified we could do the 4.1.0 release. Please add your
though
Hi Devs,
I have notice that group-scaling sample is not starting up correctly. This
sample contain nested groups. AFAIK this works perfectly on older
codebase.(pre-alpha)
https://github.com/apache/stratos/tree/master/samples/group-scaling/mock
can some one check and verify.
Thank you,
Bst Reg
Thanks Lahiru! We have now completed all the tasks required for 4.1.0-alpha
release. Please refer "[Discuss] Finalizing 4.1.0-Alpha Release" for more
information.
IMO we can now update JIRA, create the tag and announce 4.1.0-alpha
release. WDYT?
Thanks
On Sun, Jan 11, 2015 at 12:48 PM, Lahiru Sa
Hi Devs,
We have now completed almost all the tasks needed for 4.1.0-Alpha release:
1. Finalize Kubernetes Workflow (DONE)
2. Verify Service Grouping on OpenStack and EC2 (DONE)
3. Verify Clustering Support for Stratos Components (DONE)
4. Implement Load Balancer Configuration for Service Groupin
Hi Devs,
We have now completed clustering feature implementation for 4.1.0-Alpha
release:
*Load Balancer:*
- Introduced distributed maps for replicating Load Balancer Context
- Sticky sessions are replicated by Synapse
*Cloud Controller:*
- Introduced distributed maps for replicating Cloud Contr
Regarding the following error:
[2015-01-12 09:27:41,884] ERROR
{org.apache.stratos.cloud.controller.iaases.kubernetes.KubernetesIaas} -
Could not start container: [cartridge-type] php [member-id]
php.php.domaind57b5dbd-9e12-4315-a74f-1a1c99620015
java.lang.IllegalArgumentException: Could not term
Hi Manula,
There seems to be a problem with your Kubernetes setup, pod status has not
changed to Running within 120 seconds:
[2015-01-12 09:27:41,882] ERROR {org.apache.stratos.cloud.
controller.iaases.kubernetes.KubernetesIaas} - Pod status did not change
to running within 120 sec, hence termin
Great thanks guys! I could not update the installer with this change.
On Mon, Jan 12, 2015 at 3:27 PM, Gayan Gunarathne wrote:
> Yeah.Now I have updated Stratos installer cartridge-config.properties with
> this property.
>
> Thanks,
> Gayan
>
> On Mon, Jan 12, 2015 at 3:19 PM, Chamila De Alwis
[
https://issues.apache.org/jira/browse/STRATOS-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills updated STRATOS-1063:
--
Attachment: Screen Shot 2015-01-12 at 5.28.03 PM.png
> UI Standard not followed in "Us
Mariangela Hills created STRATOS-1064:
-
Summary: Captions on "User" page incorrect
Key: STRATOS-1064
URL: https://issues.apache.org/jira/browse/STRATOS-1064
Project: Stratos
Issue Type: B
[
https://issues.apache.org/jira/browse/STRATOS-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills updated STRATOS-1063:
--
Summary: UI Standard not followed in "User" interfaces (was: UI Standard
not followed
Yeah.Now I have updated Stratos installer cartridge-config.properties with
this property.
Thanks,
Gayan
On Mon, Jan 12, 2015 at 3:19 PM, Chamila De Alwis wrote:
> Hi Imesh,
>
> The stratos-installer folder's cartridge-config.properties did not have
> this. Gayan is fixing it. Thanks!
>
>
> Rega
[
https://issues.apache.org/jira/browse/STRATOS-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills updated STRATOS-1063:
--
Description: The caption of all the buttons and interface headings that
appear in Stra
[
https://issues.apache.org/jira/browse/STRATOS-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills updated STRATOS-1062:
--
Summary: UI Standard not followed in User interfaces (was: Typo -
Auto-scaling policy
Hi Imesh,
The stratos-installer folder's cartridge-config.properties did not have
this. Gayan is fixing it. Thanks!
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Wed, Jan 7, 2015 at 7:30 PM, Imesh Gunaratne wrote:
> This system property s
Mariangela Hills created STRATOS-1063:
-
Summary: UI Standard not followed for buttons in User interfaces
Key: STRATOS-1063
URL: https://issues.apache.org/jira/browse/STRATOS-1063
Project: Stratos
Mariangela Hills created STRATOS-1062:
-
Summary: Typo - Auto-scaling policy
Key: STRATOS-1062
URL: https://issues.apache.org/jira/browse/STRATOS-1062
Project: Stratos
Issue Type: Bug
Hi,
I'm getting the following error when running kubernetes. I'm using master
branch. Is anyone expecting this before.
[2015-01-12 09:27:21,782] INFO
{org.apache.stratos.cloud.controller.iaases.kubernetes.KubernetesIaas} -
Waiting pod status to be changed to running: [member-id]
php.php.domaind
67 matches
Mail list logo
