Hi All,
I have started working on $subject. I'll update the thread with the
progress.
Thanks !
--
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware
email : manu...@wso2.com / man...@apache.org
phone : +94 772492511
blog : http:
I have now fixed this by re-applying the pull request to master branch:
https://github.com/apache/stratos/commits/master/components/org.apache.stratos.cloud.controller/src/main/java/org/apache/stratos/cloud/controller/iaases/CloudstackIaas.java
https://github.com/apache/stratos/commits/master/com
Jira added https://issues.apache.org/jira/browse/STRATOS-1010
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Thu, Nov 27, 2014 at 11:13 AM, Udara Liyanage wrote:
> Hi,
>
> As I mentioned earlier those information are missed out when converting to
>
Dakshika Jayathilaka created STRATOS-1010:
-
Summary: Incorrect JSON return on GET cartridge/lb REST endpoint
Key: STRATOS-1010
URL: https://issues.apache.org/jira/browse/STRATOS-1010
Project: S
[
https://issues.apache.org/jira/browse/STRATOS-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227302#comment-14227302
]
ASF GitHub Bot commented on STRATOS-1009:
-
GitHub user swgkg opened a pull reque
GitHub user swgkg opened a pull request:
https://github.com/apache/stratos/pull/121
Introduce the enum for messaging topics
Fixes for STRATOS-1009 fixes
1.Introduce the enum for messaging topics
You can merge this pull request into a Git repository by running:
$ git pu
Gayan Gunarathne created STRATOS-1009:
-
Summary: Messaging model constants file refactor
Key: STRATOS-1009
URL: https://issues.apache.org/jira/browse/STRATOS-1009
Project: Stratos
Issue T
[
https://issues.apache.org/jira/browse/STRATOS-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227293#comment-14227293
]
Gayan Gunarathne commented on STRATOS-1005:
---
PR -https://github.com/apache/str
[
https://issues.apache.org/jira/browse/STRATOS-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gayan Gunarathne resolved STRATOS-1005.
---
Resolution: Fixed
PR 119 merged , hence resolving the issue.
> Refactoring of Strat
Hi,
As I mentioned earlier those information are missed out when converting to
the bean. Please create a jira.
On Thu, Nov 27, 2014 at 11:02 AM, Dakshika Jayathilaka
wrote:
> Forget to mention another thing.. Normally we are adding *type *but
> return come along with *cartridgeType. *Also we ne
Forget to mention another thing.. Normally we are adding *type *but return
come along with *cartridgeType. *Also we need to show extra info like Port
Mapping, Network Interfaces so on..
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Thu, Nov 27, 2014
Hi,
Yes this should be fixed.
The issue us from CC side it sends a CartridgeInfo type object which is
created from Cartridge type. During conversion some details are missed out
in CCImpl getCartridgeInfo().
On Thu, Nov 27, 2014 at 10:45 AM, Dakshika Jayathilaka
wrote:
> Hi Devs,
>
> I have not
Hi Devs,
I have notice that there are certain issues on cartridge detail return
endpoint.
AFAIK *"GET","/cartridge/lb"* is expected to return all available LB on
context.
but endpoint return something like below.
{
- "activeInstances":0,
- "cartridgeAlias":"-",
- "cartridgeType":"lb",
[
https://issues.apache.org/jira/browse/STRATOS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gayan Gunarathne resolved STRATOS-791.
--
Resolution: Fixed
PR 86 is already merged , hence resolving the issue
> MQTT protocol
On Wed, Nov 26, 2014 at 5:27 PM, Lahiru Sandaruwan wrote:
>
> We might need to assume that we got the stats parallel even though there
> are small time gaps in between.
> i.e. If we publish events from LB with 10 sec. time interval, we will
> receive all the events at CEP inside 10 sec. time dura
Hi Imesh,
Thank you for the explanations.
I'm +1 for the overall model.
Thanks.
On 27 Nov 2014 07:19, "Imesh Gunaratne" wrote:
> Hi,
>
> On Wed, Nov 26, 2014 at 5:27 PM, Udara Liyanage wrote:
>
>> Reading from registry frequently might be more expensive than distributed
>> locking since a num
Hi,
On Wed, Nov 26, 2014 at 5:27 PM, Udara Liyanage wrote:
> Reading from registry frequently might be more expensive than distributed
> locking since a number of database queries are executed.
> +1 for distributed collections.
>
> Are we going to use Hazlecast or any other framework ?
>
We are
Hi Lahiru,
On Wed, Nov 26, 2014 at 11:53 PM, Lahiru Sandaruwan
wrote:
>
>
> On Wed, Nov 26, 2014 at 11:45 PM, Isuru Haththotuwa
> wrote:
>
>> Hi Lahiru,
>>
>> This might be due to the latest changes done to introduce the group &
>> cluster instance information. I will have a look as well.
>>
>
On Wed, Nov 26, 2014 at 11:45 PM, Isuru Haththotuwa
wrote:
> Hi Lahiru,
>
> This might be due to the latest changes done to introduce the group &
> cluster instance information. I will have a look as well.
>
Hi Isuru,
Looks like so. We will be running the drools against group instance in the
fu
Hi Lahiru,
This might be due to the latest changes done to introduce the group &
cluster instance information. I will have a look as well.
On Wed, Nov 26, 2014 at 11:39 PM, Lahiru Sandaruwan
wrote:
> Hi,
>
> $subject. Will look into it.
>
> Thanks.
>
> --
> --
> Lahiru Sandaruwan
> Committer an
Hi,
$subject. Will look into it.
Thanks.
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahir
[
https://issues.apache.org/jira/browse/STRATOS-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226135#comment-14226135
]
ASF GitHub Bot commented on STRATOS-998:
Github user asfgit closed the pull reque
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/119
---
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 ena
Mariangela Hills created STRATOS-1008:
-
Summary: Wiki - Document the REST API changes due to refactoring
Key: STRATOS-1008
URL: https://issues.apache.org/jira/browse/STRATOS-1008
Project: Stratos
[
https://issues.apache.org/jira/browse/STRATOS-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills resolved STRATOS-963.
--
Resolution: Fixed
Fix Version/s: 4.1.0
The REST APIs have been documented in the
[
https://issues.apache.org/jira/browse/STRATOS-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills reassigned STRATOS-913:
Assignee: Mariangela Hills
> Wiki - Add and Update REST API Responses
> --
Hi Imesh,
> - The time it takes to propagate a modificaiton from one instance to
> another would be higher compared to using a distributed map (instance 1
> persist changes, send a cluster message to invalidate the cache, other
> instances read changes from registry database, refresh in memory
On Wed, Nov 26, 2014 at 3:19 PM, Akila Ravihansa Perera
wrote:
> Hi,
>
> Have you considered RIF stats publishing story in a LB clustered scenario?
> Each LB instance will be publishing stats in parallel, am I correct to
> assume that?
>
We might need to assume that we got the stats parallel eve
Hi Imesh,
Reading from registry frequently might be more expensive than distributed
locking since a number of database queries are executed.
+1 for distributed collections.
Are we going to use Hazlecast or any other framework ?
On Wed, Nov 26, 2014 at 4:53 PM, Lakmal Warusawithana
wrote:
>
>
>
[
https://issues.apache.org/jira/browse/STRATOS-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manula Chathurika Thantriwatte resolved STRATOS-1007.
-
Resolution: Fixed
> Server is started twice in cartridge
[
https://issues.apache.org/jira/browse/STRATOS-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226094#comment-14226094
]
Manula Chathurika Thantriwatte commented on STRATOS-1007:
-
Fixed
Manula Chathurika Thantriwatte created STRATOS-1007:
---
Summary: Server is started twice in cartridge instance
Key: STRATOS-1007
URL: https://issues.apache.org/jira/browse/STRATOS-1007
One other use-case is the port-range exposed from the host machine.
On Wed, Nov 26, 2014 at 2:50 PM, Akila Ravihansa Perera
wrote:
> Most likely we will when implementing LB service groups for Kubernetes
> proxy services. Also we can use that to directly access Kubernetes proxy
> services in Cor
On Wed, Nov 26, 2014 at 4:49 PM, Imesh Gunaratne wrote:
> Hi Akila,
>
> The goal we are trying to achieve here is to replicate the state of the
> cloud controller. IMO registry based approach might not be appropriate for
> state replication due to the following reason:
>
> - The time it takes to
Hi Akila,
The goal we are trying to achieve here is to replicate the state of the
cloud controller. IMO registry based approach might not be appropriate for
state replication due to the following reason:
- The time it takes to propagate a modificaiton from one instance to
another would be higher
[
https://issues.apache.org/jira/browse/STRATOS-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manula Chathurika Thantriwatte resolved STRATOS-1006.
-
Resolution: Fixed
> Lost of ReadyToShutDown event cause
[
https://issues.apache.org/jira/browse/STRATOS-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226017#comment-14226017
]
Manula Chathurika Thantriwatte commented on STRATOS-1006:
-
Fixed
Manula Chathurika Thantriwatte created STRATOS-1006:
---
Summary: Lost of ReadyToShutDown event cause members who are in
"ReadyToShutDown" forever
Key: STRATOS-1006
URL: https://issues.apache.org/ji
Hi,
Have you considered RIF stats publishing story in a LB clustered scenario?
Each LB instance will be publishing stats in parallel, am I correct to
assume that? In that case, will those values get overwritten by each other?
Thanks.
On Wed, Nov 26, 2014 at 12:44 PM, Imesh Gunaratne wrote:
> H
Hi Imesh,
According to the model you've described, we will have to use a distributed
lock to synchronize read/write operations into the topology data structure.
This could be expensive.
I'd like to propose that we actually store and read the topology from the
registry. And to optimize the perform
I have done the changes so that we can specify this value in Autoscaling
policy.
Thanks.
On Sat, Nov 8, 2014 at 8:35 PM, Rajkumar Rajaratnam
wrote:
>
>
> On Sat, Nov 8, 2014 at 8:32 PM, Lahiru Sandaruwan
> wrote:
>
>>
>>
>> On Sat, Nov 8, 2014 at 8:26 PM, Rajkumar Rajaratnam
>> wrote:
>>
>>>
Most likely we will when implementing LB service groups for Kubernetes
proxy services. Also we can use that to directly access Kubernetes proxy
services in Core-OS cluster.
On Wed, Nov 26, 2014 at 11:35 AM, Imesh Gunaratne wrote:
> Thanks Akila, do we use that information for any purpose?
>
> On
+1 Yes a good point Lakmal, to reduce the latency for a modification to
propagate to all the instances we might need to replicate topology as well.
Thanks
On Wed, Nov 26, 2014 at 2:44 PM, Lakmal Warusawithana
wrote:
>
>
> On Wed, Nov 26, 2014 at 1:16 PM, Imesh Gunaratne wrote:
>
>> Hi Devs,
>
On Wed, Nov 26, 2014 at 1:16 PM, Imesh Gunaratne wrote:
> Hi Devs,
>
> This is to discuss the clustering model of the cloud controller:
>
>
>
>
> As shown in the above diagram the idea is to have a coordinator node to
> handle data persistence logic and message publishing (topology, instance
>
44 matches
Mail list logo
