[
https://issues.apache.org/jira/browse/STRATOS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161481#comment-14161481
]
Imesh Gunaratne edited comment on STRATOS-870 at 10/7/14 6:56 AM:
-
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/80
---
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
Dakshika Jayathilaka created STRATOS-872:
Summary: New User update issue
Key: STRATOS-872
URL: https://issues.apache.org/jira/browse/STRATOS-872
Project: Stratos
Issue Type: Bug
A
GitHub user lasinducharith opened a pull request:
https://github.com/apache/stratos/pull/80
Code Review changes - resending
Resending https://github.com/apache/stratos/pull/76/ to
tenant-isolation-feature branch
You can merge this pull request into a Git repository by running:
[
https://issues.apache.org/jira/browse/STRATOS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161519#comment-14161519
]
Rajkumar Rajaratnam commented on STRATOS-870:
-
Hi Imesh,
I couldn't assign
Thanks a lot Nirmal!
Martin, would you be able to check on this?
On Tue, Oct 7, 2014 at 9:19 AM, Nirmal Fernando
wrote:
> Hi Martin,
>
> Iaas provider types are different from cloud-controller.xml and Cartridge
> definition. Please correct the 'type' attribute of your cartridge to
> 'Core'.
>
>
[
https://issues.apache.org/jira/browse/STRATOS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161481#comment-14161481
]
Imesh Gunaratne commented on STRATOS-870:
-
[~rajkumarr] I can see you have alread
Hi Martin,
On Mon, Oct 6, 2014 at 11:44 AM, Reka Thirunavukkarasu
wrote:
> Hi all,
>
> I have implemented the dependency tree as mentioned in my mail earlier. It
> will return the immediate children for the start able dependencies.
>
> FYI: a composite application has postgresGroup, php, mysqlG
Github user imesh commented on a diff in the pull request:
https://github.com/apache/stratos/pull/35#discussion_r18500482
--- Diff:
components/org.apache.stratos.autoscaler/src/main/java/org/apache/stratos/autoscaler/message/receiver/topology/AutoscalerTopologyEventReceiver.java
---
Github user imesh commented on a diff in the pull request:
https://github.com/apache/stratos/pull/35#discussion_r18500435
--- Diff:
components/org.apache.stratos.autoscaler/src/main/java/org/apache/stratos/autoscaler/AutoscalerContext.java
---
@@ -109,4 +113,33 @@ public void setL
Hi Martin,
Iaas provider types are different from cloud-controller.xml and Cartridge
definition. Please correct the 'type' attribute of your cartridge to
'Core'.
On Tue, Oct 7, 2014 at 9:16 AM, Martin Eppel (meppel)
wrote:
> Here it is (..repository/conf/cloud-controller.xml),
>
>
>
> Thanks f
Here it is (..repository/conf/cloud-controller.xml),
Thanks for taking a look
Regards
Martin
From: Nirmal Fernando [mailto:nir...@wso2.com]
Sent: Monday, October 06, 2014 7:09 PM
To: Martin Eppel (meppel)
Cc: dev@stratos.apache.org; Reka Thirunavukkarasu (r...@wso2.com); Isuru
Haththotuwa
Subj
Hi Martin,
Can you please send over the cloud-controller.xml file too?
On Tue, Oct 7, 2014 at 12:58 AM, Martin Eppel (meppel)
wrote:
> Hi,
>
>
>
> When I deploy a cartridge I am getting a jcould exception as below. It
> looks I am missing some definition of an “id” ? The same cartridge
> defi
Hi,
When I deploy a cartridge I am getting a jcould exception as below. It looks I
am missing some definition of an “id” ? The same cartridge definition used to
work just a few days ago (I am working on the 4.0.0-grouping branch which might
have been merged with the master).
I am stuck at the
Have you tried to run this config lately (since last Friday) against the latest
grouping-4.0.0 code – my configuration looked similar but started to fail since
I pulled the latest code from the grouping-4.0.0 branch last week Friday
(10/03),
Thanks
Martin
From: isu...@wso2.com [mailto:isu...@
Congratzz Lasindu! Keep up the good work!
On Mon, Oct 6, 2014 at 9:50 PM, Dakshika Jayathilaka
wrote:
> Congratz Lasindu..!!!
>
> *Dakshika Jayathilaka*
> Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Mon, Oct 6, 2014 at 8:44 PM, Dinesh Bandara wrote:
>
>> Cong
Congratzz Raj! Keep up the good work!
On Mon, Oct 6, 2014 at 11:30 PM, Sajith Kariyawasam wrote:
> Congratulations Raj !
>
> On Mon, Oct 6, 2014 at 9:49 PM, Dakshika Jayathilaka
> wrote:
>
>> Congratz Raj..!!!
>>
>> *Dakshika Jayathilaka*
>> Software Engineer
>> WSO2, Inc.
>> lean.enterprise.mi
Congratulations Raj !
On Mon, Oct 6, 2014 at 9:49 PM, Dakshika Jayathilaka
wrote:
> Congratz Raj..!!!
>
> *Dakshika Jayathilaka*
> Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Mon, Oct 6, 2014 at 8:44 PM, Dinesh Bandara wrote:
>
>> Congrats Raj .. !!
>>
>> On
Congratulations Lasindu !
On Mon, Oct 6, 2014 at 9:50 PM, Dakshika Jayathilaka
wrote:
> Congratz Lasindu..!!!
>
> *Dakshika Jayathilaka*
> Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Mon, Oct 6, 2014 at 8:44 PM, Dinesh Bandara wrote:
>
>> Congrats Lasindu ..
On Mon, Oct 6, 2014 at 11:17 PM, Rajkumar Rajaratnam
wrote:
> Hi
>
> On Mon, Oct 6, 2014 at 11:13 PM, Isuru Haththotuwa
> wrote:
>
>>
>>
>> On Mon, Oct 6, 2014 at 10:52 PM, Rajkumar Rajaratnam
>> wrote:
>>
>>> Hi,
>>>
>>> When we are using ScheduledExecutorService, thread pool size is fixed.
>>
Hi
On Mon, Oct 6, 2014 at 11:13 PM, Isuru Haththotuwa
wrote:
>
>
> On Mon, Oct 6, 2014 at 10:52 PM, Rajkumar Rajaratnam
> wrote:
>
>> Hi,
>>
>> When we are using ScheduledExecutorService, thread pool size is fixed.
>> There are only 2 factory methods to create ScheduledThreadPools, one with
>>
On Mon, Oct 6, 2014 at 10:52 PM, Rajkumar Rajaratnam
wrote:
> Hi,
>
> When we are using ScheduledExecutorService, thread pool size is fixed.
> There are only 2 factory methods to create ScheduledThreadPools, one with
> single thread and one with fixed number of threads.
>
> In our scenario, we ca
Attached a sample cartridge definition. I didn't specifically check this
with OpenStack, but should work.
On Mon, Oct 6, 2014 at 10:48 PM, Martin Eppel (meppel)
wrote:
> No changes to local code, it might be a missing parameter in the
> cartridge definition but I don’t know what it needs to be
Hi,
When we are using ScheduledExecutorService, thread pool size is fixed.
There are only 2 factory methods to create ScheduledThreadPools, one with
single thread and one with fixed number of threads.
In our scenario, we can't predict the number clusters in advance. We have
two options.
1. We ca
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/79
---
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
No changes to local code, it might be a missing parameter in the cartridge
definition but I don’t know what it needs to be - do you have an example of
the cartridge definitions (json) you deploy for the grouping branch, it might
help to figure out what I am missing in my json ?
Thanks
Martin
Hi Martin,
Sorry for the delayed response.
I do not recall seeing this. Do you have any local modifications to the
code? From the initial look, it seems a validation failure; There is a
mandatory id, which is missing in this case.
On Sat, Oct 4, 2014 at 5:44 AM, Martin Eppel (meppel)
wrote:
>
+1, absolutely, this a reminiscent from my original POC
From: isu...@wso2.com [mailto:isu...@wso2.com] On Behalf Of Isuru Haththotuwa
Sent: Sunday, October 05, 2014 9:47 PM
To: Reka Thirunavukkarasu
Cc: Udara Liyanage; dev; Martin Eppel (meppel)
Subject: Re: key/alias is hardcoded TopologyBuilder
Congratz Lasindu..!!!
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Mon, Oct 6, 2014 at 8:44 PM, Dinesh Bandara wrote:
> Congrats Lasindu .. !!
>
> On Mon, Oct 6, 2014 at 8:25 PM, Manula Chathurika Thantriwatte <
> manu...@wso2.com> wrote:
>
>> Con
Congratz Raj..!!!
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Mon, Oct 6, 2014 at 8:44 PM, Dinesh Bandara wrote:
> Congrats Raj .. !!
>
> On Mon, Oct 6, 2014 at 8:25 PM, Manula Chathurika Thantriwatte <
> manu...@wso2.com> wrote:
>
>> Congratulat
Congrats Lasindu .. !!
On Mon, Oct 6, 2014 at 8:25 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Congratulations Lasindu !!!
>
> On Mon, Oct 6, 2014 at 6:49 PM, Reka Thirunavukkarasu
> wrote:
>
>> Congratz Lasindu..!!!
>>
>> On Mon, Oct 6, 2014 at 6:14 PM, Shiroshica Kulatilake
Congrats Raj .. !!
On Mon, Oct 6, 2014 at 8:25 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Congratulations Raj !!!
>
> On Mon, Oct 6, 2014 at 6:49 PM, Reka Thirunavukkarasu
> wrote:
>
>> Congratz Raj..!!!
>>
>> On Mon, Oct 6, 2014 at 6:14 PM, Shiroshica Kulatilake
>> wrote:
Congratulations Lasindu !!!
On Mon, Oct 6, 2014 at 6:49 PM, Reka Thirunavukkarasu wrote:
> Congratz Lasindu..!!!
>
> On Mon, Oct 6, 2014 at 6:14 PM, Shiroshica Kulatilake
> wrote:
>
>> Congrats Lasindu !!
>>
>> On Mon, Oct 6, 2014 at 5:27 PM, Gayan Gunarathne wrote:
>>
>>> Congratulations Lasi
Congratulations Raj !!!
On Mon, Oct 6, 2014 at 6:49 PM, Reka Thirunavukkarasu wrote:
> Congratz Raj..!!!
>
> On Mon, Oct 6, 2014 at 6:14 PM, Shiroshica Kulatilake
> wrote:
>
>> Congrats Raj !!
>>
>> On Mon, Oct 6, 2014 at 5:28 PM, Gayan Gunarathne wrote:
>>
>>> Congratulations Raj!!!
>>>
>>> O
Hi Isuru,
In addition we need to come up with a way to minimize the uses of methods
which has a lot of arguments.
Touched, not typed. Erroneous words are a feature, not a typo.
Congratz Lasindu..!!!
On Mon, Oct 6, 2014 at 6:14 PM, Shiroshica Kulatilake
wrote:
> Congrats Lasindu !!
>
> On Mon, Oct 6, 2014 at 5:27 PM, Gayan Gunarathne wrote:
>
>> Congratulations Lasindu!!!
>>
>>
>> On Mon, Oct 6, 2014 at 5:11 PM, Nirmal Fernando
>> wrote:
>>
>>> Congratz and welcome ab
Congratz Raj..!!!
On Mon, Oct 6, 2014 at 6:14 PM, Shiroshica Kulatilake
wrote:
> Congrats Raj !!
>
> On Mon, Oct 6, 2014 at 5:28 PM, Gayan Gunarathne wrote:
>
>> Congratulations Raj!!!
>>
>> On Mon, Oct 6, 2014 at 5:10 PM, Nirmal Fernando
>> wrote:
>>
>>> Congratz and welcome aboard Raj!
>>>
>
Congrats Raj !!
On Mon, Oct 6, 2014 at 5:28 PM, Gayan Gunarathne wrote:
> Congratulations Raj!!!
>
> On Mon, Oct 6, 2014 at 5:10 PM, Nirmal Fernando
> wrote:
>
>> Congratz and welcome aboard Raj!
>>
>> On Mon, Oct 6, 2014 at 4:48 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>>
Congrats Lasindu !!
On Mon, Oct 6, 2014 at 5:27 PM, Gayan Gunarathne wrote:
> Congratulations Lasindu!!!
>
>
> On Mon, Oct 6, 2014 at 5:11 PM, Nirmal Fernando
> wrote:
>
>> Congratz and welcome aboard Lasindu!
>>
>> On Mon, Oct 6, 2014 at 4:49 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com>
Congratulations Lasindu!!!
On Mon, Oct 6, 2014 at 5:11 PM, Nirmal Fernando
wrote:
> Congratz and welcome aboard Lasindu!
>
> On Mon, Oct 6, 2014 at 4:49 PM, Akila Ravihansa Perera > wrote:
>
>> Congratulations Lasindu!
>>
>> Keep up the good work.
>>
>> On Mon, Oct 6, 2014 at 2:50 PM, Lakmal W
Congratulations Raj!!!
On Mon, Oct 6, 2014 at 5:10 PM, Nirmal Fernando
wrote:
> Congratz and welcome aboard Raj!
>
> On Mon, Oct 6, 2014 at 4:48 PM, Akila Ravihansa Perera > wrote:
>
>> Congratulations Raj!
>>
>> Keep up the good work.
>>
>> On Mon, Oct 6, 2014 at 2:51 PM, Lakmal Warusawithana
Congratz and welcome aboard Raj!
On Mon, Oct 6, 2014 at 4:48 PM, Akila Ravihansa Perera
wrote:
> Congratulations Raj!
>
> Keep up the good work.
>
> On Mon, Oct 6, 2014 at 2:51 PM, Lakmal Warusawithana
> wrote:
> > The Project Management Committee (PMC) for Apache Stratos
> > has asked Rajkumar
Congratz and welcome aboard Lasindu!
On Mon, Oct 6, 2014 at 4:49 PM, Akila Ravihansa Perera
wrote:
> Congratulations Lasindu!
>
> Keep up the good work.
>
> On Mon, Oct 6, 2014 at 2:50 PM, Lakmal Warusawithana
> wrote:
> > The Project Management Committee (PMC) for Apache Stratos
> > has asked
Congratulations Raj!
Keep up the good work.
On Mon, Oct 6, 2014 at 2:51 PM, Lakmal Warusawithana wrote:
> The Project Management Committee (PMC) for Apache Stratos
> has asked Rajkumar Rajaratnam to become a committer and PMC member
> and we are pleased to announce that he has accepted.
>
> Bein
Congratulations Lasindu!
Keep up the good work.
On Mon, Oct 6, 2014 at 2:50 PM, Lakmal Warusawithana wrote:
> The Project Management Committee (PMC) for Apache Stratos
> has asked Lasindu Charith to become a committer and PMC member
> and we are pleased to announce that he has accepted.
>
> Bein
AFAIK if the REST API using the headers for version purposes, customer need
only to change the header part only when the version update.IMO If we want
we can use the custom header instead of the accept header as for the W3
protocol standards accept header used for specify the media type.(As Imesh
m
Hi Devs,
Myself, Reka and Udara carried out $subject. We did not go for a hangout
based review since the designs are in the initial stages and are not
finalized yet. Please note that we are will conducting code reviews over
hangouts for the upcoming milestones.
Notes from the code review on Autos
So if I am a client who is currently using the REST API of Stratos I will
have to change my client to send the version in the header as mentioned in
this thread in order to use the previous endpoints - Assuming that these
endpoints will be maintained till next release.
However, As per the discuss
Sorry, if I wasn't clear Imesh. Yes, we will support both. Accept header
can be used in a scenario where you want to explicitly mention the API
version when accessing via default API path. If you wish to use the URL
context, you shouldn't be required to set the Accept header.
On Mon, Oct 6, 2014 a
Got it! Shall we support both Accept header and URL context for this?
Thanks
On Mon, Oct 6, 2014 at 2:39 PM, Nirmal Fernando
wrote:
> Hi Imesh,
>
> Yes, GitHub API does that way https://developer.github.com/v3/versions/
>
>
> On Mon, Oct 6, 2014 at 2:35 PM, Imesh Gunaratne wrote:
>
>> +1 Regar
Hi Imesh,
On Mon, Oct 6, 2014 at 2:45 PM, Imesh Gunaratne wrote:
> Hi Reka,
>
> I have a small concern on using the term "kill" in this scenario, I think
> it would be much more elegant if we call it something like "terminate".
> WDYT?
>
+1. It's more appropriate to use terminate. Will change it
The Project Management Committee (PMC) for Apache Stratos
has asked Rajkumar Rajaratnam to become a committer and PMC member
and we are pleased to announce that he has accepted.
Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission proce
This looks great! As we discussed may be we could provide an interface in
the messaging component to acquire and release locks at different sub tree
levels. The whole idea is to avoid any possibilities of reading the
topology in an inconsistent state.
Thanks
On Mon, Oct 6, 2014 at 12:37 PM, Isuru
The Project Management Committee (PMC) for Apache Stratos
has asked Lasindu Charith to become a committer and PMC member
and we are pleased to announce that he has accepted.
Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process.
On Mon, Oct 6, 2014 at 2:45 PM, Imesh Gunaratne wrote:
> Hi Reka,
>
> I have a small concern on using the term "kill" in this scenario, I think
> it would be much more elegant if we call it something like "terminate".
> WDYT?
>
+1 for terminate.
>
> Thanks
>
> On Mon, Oct 6, 2014 at 11:44 AM,
Hi Reka,
I have a small concern on using the term "kill" in this scenario, I think
it would be much more elegant if we call it something like "terminate".
WDYT?
Thanks
On Mon, Oct 6, 2014 at 11:44 AM, Reka Thirunavukkarasu
wrote:
> Hi all,
>
> I have implemented the dependency tree as mentione
+1 Regarding point 2: using Accept header to specify the API version, is
this being done by any other known APIs? For my understanding Accept header
is used for specify the media type [1].
[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
On Sun, Oct 5, 2014 at 9:27 PM, Nirmal Fernando
Hi Imesh,
Yes, GitHub API does that way https://developer.github.com/v3/versions/
On Mon, Oct 6, 2014 at 2:35 PM, Imesh Gunaratne wrote:
> +1 Regarding point 2: using Accept header to specify the API version, is
> this being done by any other known APIs? For my understanding Accept header
> is
Great! Thanks Nirmal!
On Mon, Oct 6, 2014 at 11:03 AM, Nirmal Fernando
wrote:
> Ya, Imesh.. I was worrying about breaking existing clients (including our
> own UI /CLI) . Yes, I also felt the same after thinking a bit more and
> initiated a thread here: Versioning Stratos REST API
>
> On Mon, O
Hi all,
The issue was resolved after installing a new build from the master. Thanks
for your help!
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Mon, Oct 6, 2014 at 11:48 AM, Chamila De Alwis wrote:
> Hi Udara,
>
> Yes this was build from
Hi,
Added a few comments to the shared sheet.
Mentioned below are some common comments which would apply to almost all;
1. Should we introduce DELETE for all (applicable) types of resources ? -
Of course before doing a delete a series of checks will have to be done and
maybe we can add a specif
Thank you all..
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Mon, Oct 6, 2014 at 11:53 AM, Sajith Kariyawasam wrote:
> I have fixed this in master and container-autoscaling branches
>
> On Mon, Oct 6, 2014 at 11:26 AM, Sajith Kariyawasam
> wrote:
Thanks Imesh.
I have shown some examples for the new hierarchical locking approach.
Please do let me know your feedback on this.
Acquire a write lock:
From root level, acquire read lock, and acquire a write lock only for the
relevant sub tree.
Acquire a read lock:
From root leve
63 matches
Mail list logo
