You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Imesh Gunaratne <im...@apache.org> on 2014/10/29 14:32:59 UTC
[Important] Merging Grouping Changes to Master Branch
Hi Devs,
We are now in the process of merging service grouping changes
(4.0.0-grouping branch) into master branch.
We have created a new branch: *docker-grouping-merge* for this process from
the latest commit in the master branch and merging changes from
*4.0.0-grouping* branch to it.
Please try to hold your commits to master branch until we complete this
process. If not please double commit your changes to master and
docker-grouping-merge branches.
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Hi all,
Found that we were using old code in AutoscalerTopologyEventReceiver.
We introduced a monitor hierarchy, and we are letting cluster monitors to
decide and act upon receiving events. That's why we introduced
handle*Event(Event) methods in AbstractClusterMonitor.
When receiving events, we can simply call monitor.handleXEvent(X), and rest
will be handled in the relevant cluster monitor. We got merged old pattern
where we do stuff when receiving events.
I fixed it and committed it.
Thanks.
On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> I get a NPE while trying to deploy the app definition without properties,
> looking into it.
>
> [2014-11-01 20:17:18,922] ERROR
> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
> - Internal server error
>
> java.lang.NullPointerException
>
> at
> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>
> at
> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:606)
>
> at
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>
> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I have now fixed few more issues:
>> - Removing subscription resource from REST API and CLI.
>> - Adding isKubernetesCluster property to ApplicationClusterContext.
>> - Passing properties from Application definition to the cluster objects.
>> This is needed for Kubernetes.
>> - Packaging drools files in stratos distribution (some of the files were
>> placed in repository/conf while the rest were at repository/conf/drools).
>>
>> Please find the sample application definition file which I have been
>> using for testing attached with this mail.
>>
>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Can a service cluster(say php cluster) span across two partitions(in
>>> other words two kub cluster)? I guess kubernetes can manage their
>>> containers within a kub cluster, not between kub clusters? For example, if
>>> we say we need 3 replicas, it can ensure there are 3 replicas in one kub
>>> cluster. It can't manage 3 replicas within two kub cluster. Am I missing
>>> something here?
>>>
>>> Raj: A good point, we can handle this in Stratos, shouldn't be a problem.
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
Hi Imesh,
Sorry for the late response.
On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Isuru,
>
> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>>
>> IMHO we should have the context name 'stratos' in the url. Then it is
>> more intuitive. having just /api doesn't say that this API belongs to
>> Stratos.
>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>> might do the same, but that might not be the case always. Just my two
>> cents.
>>
>>>
>>>
>>> A good point, I reviewed your concern before doing this modification,
> most of the well known APIs do not include the product name in the context.
> Rather as you have mentioned they use the hostname to identify the product,
> please see below examples. This is why I removed "stratos" from the
> context, WDYT?
>
> Facebook Graph API:
> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
> Twitter API:
> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
> Github API: https://developer.github.com/v3/
> OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html
> EC2 API:
> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
> Google Cloud Compute API:
> https://cloud.google.com/compute/docs/reference/latest/#Addresses
> StackExchange API: https://api.stackexchange.com/docs/answers
>
Stratos case is different IMO. These are rest apis which are hosted by the
providers themselves, but in Stratos case this is not so. It is a product
specific API. That is why I thought this in the first place. However, this
is just my opinion.
>
> Thanks
>
> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>> Hi Imesh,
>>
>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Please note that we have now introduced API versioning in
>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>> follows, no changes were done to existing resource paths:
>>>
>>> Previous API URL:
>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>
>>> New API URL:
>>> https://{hostname}:{port}/api/{resource-path}
>>>
>> IMHO we should have the context name 'stratos' in the url. Then it is
>> more intuitive. having just /api doesn't say that this API belongs to
>> Stratos.
>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>> might do the same, but that might not be the case always. Just my two
>> cents.
>>
>>>
>>> Version specific API URLs:
>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>
>>> Following changes to be done:
>>> - Update CLI and Dashboard
>>> - Allow API version to be specified in an HTTP header
>>>
>>> Thanks
>>>
>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> We now have the docker-grouping-branch in a compilable state with
>>>> latests modifications. Please test all workflows related to service
>>>> grouping and docker, once things are stable will merge this branch to
>>>> master.
>>>>
>>>> Thanks
>>>>
>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>> manulac@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have completed deploy-application, undeploy-application,
>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>> the changes to docker-grouping-merge branch. I'll compete the other
>>>>> commands as soon as possible and looks for the UI as well.
>>>>>
>>>>> Thanks !
>>>>>
>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I have now fixed autoscaler service stub bundle exports and stratos
>>>>>> manager import statements. Currently working on Stratos Manager, seems like
>>>>>> there are duplicated domain classes:
>>>>>>
>>>>>>
>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>
>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>
>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>
>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>
>>>>>>> Fixed AS issues
>>>>>>>
>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>
>>>>>>>>> Thanks !
>>>>>>>>>
>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>>>>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>
>>>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping]
>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> When and where are we creating and adding cluster monitors
>>>>>>>>>>>>>> (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>> Method)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>> - Passing properties from Application definition to the
>>>>>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some of
>>>>>>>>>>>>>>>>> the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Please find the sample application definition file which I
>>>>>>>>>>>>>>>>> have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>
>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Raj
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Regards,
>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>> Software Engineer
>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>
>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>> phone : +94 772492511
>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Lasindu Charith*
>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>> Mobile: +94714427192
>>>>>>>> Web: blog.lasindu.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Raj
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Manula Chathurika Thantriwatte
>>>>> Software Engineer
>>>>> WSO2 Inc. : http://wso2.com
>>>>> lean . enterprise . middleware
>>>>>
>>>>> email : manulac@wso2.com / manula@apache.org
>>>>> phone : +94 772492511
>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* <http://wso2.com/>*
>>>
>>>
>>> * <http://wso2.com/>*
>>>
>>>
>>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Hi Isuru,
On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa <is...@apache.org>
wrote:
>
> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> I got containers to be created.
>> But didn't get the member started event. Either agent is not sending or
>> CC is not receiving. Looking into it currently.
>>
> I'm seeing this issue as well. The agent is sending the events, but
> Stratos is not receiving them. Trying with a simple mqtt client now.
>
Is this fixed now?
Thanks
>
>> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>>
>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>> Stratos.
>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>> might do the same, but that might not be the case always. Just my two
>>>> cents.
>>>>
>>>>>
>>>>>
>>>>> A good point, I reviewed your concern before doing this modification,
>>> most of the well known APIs do not include the product name in the context.
>>> Rather as you have mentioned they use the hostname to identify the product,
>>> please see below examples. This is why I removed "stratos" from the
>>> context, WDYT?
>>>
>>> Facebook Graph API:
>>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
>>> Twitter API:
>>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
>>> Github API: https://developer.github.com/v3/
>>> OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html
>>> EC2 API:
>>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
>>> Google Cloud Compute API:
>>> https://cloud.google.com/compute/docs/reference/latest/#Addresses
>>> StackExchange API: https://api.stackexchange.com/docs/answers
>>>
>>> Thanks
>>>
>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>> Hi Imesh,
>>>>
>>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Please note that we have now introduced API versioning in
>>>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>>>> follows, no changes were done to existing resource paths:
>>>>>
>>>>> Previous API URL:
>>>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>>>
>>>>> New API URL:
>>>>> https://{hostname}:{port}/api/{resource-path}
>>>>>
>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>> Stratos.
>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>> might do the same, but that might not be the case always. Just my two
>>>> cents.
>>>>
>>>>>
>>>>> Version specific API URLs:
>>>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>>>
>>>>> Following changes to be done:
>>>>> - Update CLI and Dashboard
>>>>> - Allow API version to be specified in an HTTP header
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> We now have the docker-grouping-branch in a compilable state with
>>>>>> latests modifications. Please test all workflows related to service
>>>>>> grouping and docker, once things are stable will merge this branch to
>>>>>> master.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>>>> manulac@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have completed deploy-application, undeploy-application,
>>>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>>>> the changes to docker-grouping-merge branch. I'll compete the other
>>>>>>> commands as soon as possible and looks for the UI as well.
>>>>>>>
>>>>>>> Thanks !
>>>>>>>
>>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I have now fixed autoscaler service stub bundle exports and stratos
>>>>>>>> manager import statements. Currently working on Stratos Manager, seems like
>>>>>>>> there are duplicated domain classes:
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>>>
>>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>>>
>>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Fixed AS issues
>>>>>>>>>
>>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>>>
>>>>>>>>>>> Thanks !
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>>>>>>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping]
>>>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> When and where are we creating and adding cluster monitors
>>>>>>>>>>>>>>>> (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>>>> Method)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>>>> - Passing properties from Application definition to the
>>>>>>>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some
>>>>>>>>>>>>>>>>>>> of the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Please find the sample application definition file which
>>>>>>>>>>>>>>>>>>> I have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Raj
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Regards,
>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>> Software Engineer
>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>
>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> *Lasindu Charith*
>>>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>>>> Mobile: +94714427192
>>>>>>>>>> Web: blog.lasindu.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Raj
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Regards,
>>>>>>> Manula Chathurika Thantriwatte
>>>>>>> Software Engineer
>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>> lean . enterprise . middleware
>>>>>>>
>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>> phone : +94 772492511
>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>> --
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>
>>>>>
>>>>> * <http://wso2.com/>*
>>>>>
>>>>>
>>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Raj
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
AFAIU the client id is used by the message broker for maintaining the
sessions among connection drops and restarts (for reliable message
delivery). Therefore each subscriber and publisher might need to have its
own client with a uniqe identifier.
I will fix this in messaging component.
On Fri, Nov 7, 2014 at 2:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Gayan: Was there any reason for generating a client id for subscribers and
> setting a fixed value for publishers?
>
> TopicSubscriber.doSubscribe():
> MqttClient mqttClient = MQTTConnector.getMQTTSubClient(Util.
> getRandomString(5));
>
>
>
>
>
> On Fri, Nov 7, 2014 at 1:17 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>>
>>
>> On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>>
>>> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>> > wrote:
>>>
>>>> I got containers to be created.
>>>> But didn't get the member started event. Either agent is not sending or
>>>> CC is not receiving. Looking into it currently.
>>>>
>>> I'm seeing this issue as well. The agent is sending the events, but
>>> Stratos is not receiving them. Trying with a simple mqtt client now.
>>>
>> In [1], we are using the client id in mqtttopic.properties file as it is
>> and using it to start the MQTTClient. However, in the wiki it says that
>> client id should be unique across all publishers [2]. I might be missing
>> something here, but is this case handled?
>>
>> [1]. org.apache.stratos.messaging.broker.connect.MQTTConnector
>>
>> [2].
>> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
>> java.lang.String)
>>
>>
>>>
>>>> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi Isuru,
>>>>>
>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>>>> Stratos.
>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>>>> might do the same, but that might not be the case always. Just my two
>>>>>> cents.
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> A good point, I reviewed your concern before doing this
>>>>> modification, most of the well known APIs do not include the product name
>>>>> in the context. Rather as you have mentioned they use the hostname to
>>>>> identify the product, please see below examples. This is why I removed
>>>>> "stratos" from the context, WDYT?
>>>>>
>>>>> Facebook Graph API:
>>>>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
>>>>> Twitter API:
>>>>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
>>>>> Github API: https://developer.github.com/v3/
>>>>> OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html
>>>>> EC2 API:
>>>>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
>>>>> Google Cloud Compute API:
>>>>> https://cloud.google.com/compute/docs/reference/latest/#Addresses
>>>>> StackExchange API: https://api.stackexchange.com/docs/answers
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi Imesh,
>>>>>>
>>>>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Please note that we have now introduced API versioning in
>>>>>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>>>>>> follows, no changes were done to existing resource paths:
>>>>>>>
>>>>>>> Previous API URL:
>>>>>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>>>>>
>>>>>>> New API URL:
>>>>>>> https://{hostname}:{port}/api/{resource-path}
>>>>>>>
>>>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>>>> Stratos.
>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>>>> might do the same, but that might not be the case always. Just my two
>>>>>> cents.
>>>>>>
>>>>>>>
>>>>>>> Version specific API URLs:
>>>>>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>>>>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>>>>>
>>>>>>> Following changes to be done:
>>>>>>> - Update CLI and Dashboard
>>>>>>> - Allow API version to be specified in an HTTP header
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> We now have the docker-grouping-branch in a compilable state with
>>>>>>>> latests modifications. Please test all workflows related to service
>>>>>>>> grouping and docker, once things are stable will merge this branch to
>>>>>>>> master.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I have completed deploy-application, undeploy-application,
>>>>>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>>>>>> the changes to docker-grouping-merge branch. I'll compete the
>>>>>>>>> other commands as soon as possible and looks for the UI as well.
>>>>>>>>>
>>>>>>>>> Thanks !
>>>>>>>>>
>>>>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I have now fixed autoscaler service stub bundle exports and
>>>>>>>>>> stratos manager import statements. Currently working on Stratos Manager,
>>>>>>>>>> seems like there are duplicated domain classes:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>>>>>
>>>>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>>>>>
>>>>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Fixed AS issues
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <
>>>>>>>>>>> lasindu@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte
>>>>>>>>>>>> <ma...@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch
>>>>>>>>>>>>>>> to docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping]
>>>>>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> When and where are we creating and adding cluster
>>>>>>>>>>>>>>>>>> monitors (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>>>>>> Method)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>>>>>> - Passing properties from Application definition to
>>>>>>>>>>>>>>>>>>>>> the cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some
>>>>>>>>>>>>>>>>>>>>> of the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Please find the sample application definition file
>>>>>>>>>>>>>>>>>>>>> which I have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across
>>>>>>>>>>>>>>>>>>>>>> two partitions(in other words two kub cluster)? I guess kubernetes can
>>>>>>>>>>>>>>>>>>>>>> manage their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>>>
>>>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> *Lasindu Charith*
>>>>>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>>>>>> Mobile: +94714427192
>>>>>>>>>>>> Web: blog.lasindu.com
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Raj
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Regards,
>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>> Software Engineer
>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>
>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>> phone : +94 772492511
>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>> --
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>> * <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Raj
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> +94 716 358 048
>>>>
>>>> --
>>>> <%2B94%20716%20358%20048>
>>>> <%2B94%20716%20358%20048>
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> <%2B94%20716%20358%20048>
>>>> +94 716 358 048* <http://wso2.com/>*
>>>>
>>>>
>>>> * <http://wso2.com/>*
>>>>
>>>>
>>>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
I'll do a quick fix to make the client id unique and run a test.
On Fri, Nov 7, 2014 at 2:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Gayan: Was there any reason for generating a client id for subscribers and
> setting a fixed value for publishers?
>
> TopicSubscriber.doSubscribe():
> MqttClient mqttClient = MQTTConnector.getMQTTSubClient(Util.
> getRandomString(5));
>
>
>
>
>
> On Fri, Nov 7, 2014 at 1:17 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>>
>>
>> On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>>
>>> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>> > wrote:
>>>
>>>> I got containers to be created.
>>>> But didn't get the member started event. Either agent is not sending or
>>>> CC is not receiving. Looking into it currently.
>>>>
>>> I'm seeing this issue as well. The agent is sending the events, but
>>> Stratos is not receiving them. Trying with a simple mqtt client now.
>>>
>> In [1], we are using the client id in mqtttopic.properties file as it is
>> and using it to start the MQTTClient. However, in the wiki it says that
>> client id should be unique across all publishers [2]. I might be missing
>> something here, but is this case handled?
>>
>> [1]. org.apache.stratos.messaging.broker.connect.MQTTConnector
>>
>> [2].
>> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
>> java.lang.String)
>>
>>
>>>
>>>> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi Isuru,
>>>>>
>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>>>> Stratos.
>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>>>> might do the same, but that might not be the case always. Just my two
>>>>>> cents.
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> A good point, I reviewed your concern before doing this
>>>>> modification, most of the well known APIs do not include the product name
>>>>> in the context. Rather as you have mentioned they use the hostname to
>>>>> identify the product, please see below examples. This is why I removed
>>>>> "stratos" from the context, WDYT?
>>>>>
>>>>> Facebook Graph API:
>>>>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
>>>>> Twitter API:
>>>>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
>>>>> Github API: https://developer.github.com/v3/
>>>>> OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html
>>>>> EC2 API:
>>>>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
>>>>> Google Cloud Compute API:
>>>>> https://cloud.google.com/compute/docs/reference/latest/#Addresses
>>>>> StackExchange API: https://api.stackexchange.com/docs/answers
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi Imesh,
>>>>>>
>>>>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Please note that we have now introduced API versioning in
>>>>>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>>>>>> follows, no changes were done to existing resource paths:
>>>>>>>
>>>>>>> Previous API URL:
>>>>>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>>>>>
>>>>>>> New API URL:
>>>>>>> https://{hostname}:{port}/api/{resource-path}
>>>>>>>
>>>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>>>> Stratos.
>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>>>> might do the same, but that might not be the case always. Just my two
>>>>>> cents.
>>>>>>
>>>>>>>
>>>>>>> Version specific API URLs:
>>>>>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>>>>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>>>>>
>>>>>>> Following changes to be done:
>>>>>>> - Update CLI and Dashboard
>>>>>>> - Allow API version to be specified in an HTTP header
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> We now have the docker-grouping-branch in a compilable state with
>>>>>>>> latests modifications. Please test all workflows related to service
>>>>>>>> grouping and docker, once things are stable will merge this branch to
>>>>>>>> master.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I have completed deploy-application, undeploy-application,
>>>>>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>>>>>> the changes to docker-grouping-merge branch. I'll compete the
>>>>>>>>> other commands as soon as possible and looks for the UI as well.
>>>>>>>>>
>>>>>>>>> Thanks !
>>>>>>>>>
>>>>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I have now fixed autoscaler service stub bundle exports and
>>>>>>>>>> stratos manager import statements. Currently working on Stratos Manager,
>>>>>>>>>> seems like there are duplicated domain classes:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>>>>>
>>>>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>>>>>
>>>>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Fixed AS issues
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <
>>>>>>>>>>> lasindu@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte
>>>>>>>>>>>> <ma...@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch
>>>>>>>>>>>>>>> to docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping]
>>>>>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> When and where are we creating and adding cluster
>>>>>>>>>>>>>>>>>> monitors (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>>>>>> Method)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>>>>>> - Passing properties from Application definition to
>>>>>>>>>>>>>>>>>>>>> the cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some
>>>>>>>>>>>>>>>>>>>>> of the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Please find the sample application definition file
>>>>>>>>>>>>>>>>>>>>> which I have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across
>>>>>>>>>>>>>>>>>>>>>> two partitions(in other words two kub cluster)? I guess kubernetes can
>>>>>>>>>>>>>>>>>>>>>> manage their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>>>
>>>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> *Lasindu Charith*
>>>>>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>>>>>> Mobile: +94714427192
>>>>>>>>>>>> Web: blog.lasindu.com
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Raj
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Regards,
>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>> Software Engineer
>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>
>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>> phone : +94 772492511
>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>> --
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>> * <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Raj
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> +94 716 358 048
>>>>
>>>> --
>>>> <%2B94%20716%20358%20048>
>>>> <%2B94%20716%20358%20048>
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> <%2B94%20716%20358%20048>
>>>> +94 716 358 048* <http://wso2.com/>*
>>>>
>>>>
>>>> * <http://wso2.com/>*
>>>>
>>>>
>>>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Yes Java agent.
Thanks.
On Sat, Nov 8, 2014 at 6:32 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Thanks for the update Raj, were you using Java cartridge agent?
>
> On Sat, Nov 8, 2014 at 6:21 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> Just to give an update;
>>
>> Simple container scenario is working now with m2 image. Members are
>> activated and publishing health stats to CEP. Seems undeploying application
>> is not working. Looking into it currently.
>>
>> Thanks.
>>
>> On Sat, Nov 8, 2014 at 1:50 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> I think we can use [1] to convert messaging component data model to
>>> python at the build time and the agent can refer that directly. WDYT?
>>>
>>> [1] https://github.com/natural/java2python
>>> On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <ch...@wso2.com> wrote:
>>>
>>>> Hi Raj,
>>>>
>>>> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>>> > wrote:
>>>>
>>>>> Please double check the java agent code too. It works somehow. Don't
>>>>> know the reason :)
>>>>
>>>>
>>>> The Java agent makes use of the org.apache.stratos.messaging component,
>>>> so any changes done from a publisher's point of view is reflected on a
>>>> receiver's end. In the Python agent, the serialization and the
>>>> deserialization of the events published and received from the message
>>>> broker is written anew in Python.
>>>>
>>>> The problem rises here, when the changes made in the messaging
>>>> component needs to be reflected in the Python agent too. I think for the
>>>> time being whenever a change is done, it is better to assign the relevant
>>>> JIRA issue to the person responsible of the changes in Python cartridge
>>>> agent, which is me for now :).
>>>>
>>>> In the long run, a set of unit tests can manage the changing code
>>>> better.
>>>>
>>>>
>>>> Regards,
>>>> Chamila de Alwis
>>>> Software Engineer | WSO2 | +94772207163
>>>> Blog: code.chamiladealwis.com
>>>>
>>>>
>>>>
>>
>>
>> --
>> Raj
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Thanks for the update Raj, were you using Java cartridge agent?
On Sat, Nov 8, 2014 at 6:21 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Hi all,
>
> Just to give an update;
>
> Simple container scenario is working now with m2 image. Members are
> activated and publishing health stats to CEP. Seems undeploying application
> is not working. Looking into it currently.
>
> Thanks.
>
> On Sat, Nov 8, 2014 at 1:50 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I think we can use [1] to convert messaging component data model to
>> python at the build time and the agent can refer that directly. WDYT?
>>
>> [1] https://github.com/natural/java2python
>> On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <ch...@wso2.com> wrote:
>>
>>> Hi Raj,
>>>
>>> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>>> wrote:
>>>
>>>> Please double check the java agent code too. It works somehow. Don't
>>>> know the reason :)
>>>
>>>
>>> The Java agent makes use of the org.apache.stratos.messaging component,
>>> so any changes done from a publisher's point of view is reflected on a
>>> receiver's end. In the Python agent, the serialization and the
>>> deserialization of the events published and received from the message
>>> broker is written anew in Python.
>>>
>>> The problem rises here, when the changes made in the messaging component
>>> needs to be reflected in the Python agent too. I think for the time being
>>> whenever a change is done, it is better to assign the relevant JIRA issue
>>> to the person responsible of the changes in Python cartridge agent, which
>>> is me for now :).
>>>
>>> In the long run, a set of unit tests can manage the changing code
>>> better.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>
>
> --
> Raj
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Hi all,
Just to give an update;
Simple container scenario is working now with m2 image. Members are
activated and publishing health stats to CEP. Seems undeploying application
is not working. Looking into it currently.
Thanks.
On Sat, Nov 8, 2014 at 1:50 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I think we can use [1] to convert messaging component data model to python
> at the build time and the agent can refer that directly. WDYT?
>
> [1] https://github.com/natural/java2python
> On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <ch...@wso2.com> wrote:
>
>> Hi Raj,
>>
>> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> Please double check the java agent code too. It works somehow. Don't
>>> know the reason :)
>>
>>
>> The Java agent makes use of the org.apache.stratos.messaging component,
>> so any changes done from a publisher's point of view is reflected on a
>> receiver's end. In the Python agent, the serialization and the
>> deserialization of the events published and received from the message
>> broker is written anew in Python.
>>
>> The problem rises here, when the changes made in the messaging component
>> needs to be reflected in the Python agent too. I think for the time being
>> whenever a change is done, it is better to assign the relevant JIRA issue
>> to the person responsible of the changes in Python cartridge agent, which
>> is me for now :).
>>
>> In the long run, a set of unit tests can manage the changing code better.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com> wrote:
> Hi Lahiru,
>
> As you have introduced ClusteContext in ClusterMonitor, the serviceId got
> to removed. Is this done purposely? If so, can we update the getServiceId()
> (which referred by several other places) in monitors to return the correct
> serviceId by reading ClusterContext?
>
> Due to this, ClusterMonitor returns serviceId as null and it causes issue
> in the cluster monitor creation and in the event publishing..
>
Service id is moved to cluster context. getServiceId was available through
monitor as well.
I will check and fix this
>
> Thanks,
> Reka
>
> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
>> Hi
>>
>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>>
>>>
>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> After fixing few issues, i could get the application undeployment
>>>>> working with one cluster now. So the basic undeployment is working
>>>>> fine...Will continue testing with a complex application...
>>>>>
>>>> Great! I will test the same with a complex application.
>>>>
>>> Getting the following exception with a complex app (when sending cluster
>>> activated event), will check and fix asap.
>>> Exception in thread "Thread-61" java.lang.IllegalMonitorStateException
>>> at
>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>> at
>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>> at
>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>> at
>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>> at
>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>> at
>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>> at
>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>> at java.lang.Thread.run(Thread.java:662)
>>>
>>
>> I too got this issue as well as a NPE while getting locks..Later found
>> that serviceId was null when getting the locks..I have fixed ServiceId
>> issue..Can you try now and see whether you are still getting this issue?
>>
>> Thanks,
>> Reka
>>
>>>
>>>
>>>>
>>>>> Thanks,
>>>>> Reka
>>>>>
>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> No, there seems to be a problem with application un-deploy function.
>>>>>>> For me the un-deploy call hangs in the autoscaler. This is currerntly under
>>>>>>> investigation.
>>>>>>>
>>>>>> Got the same issue, will check in this.
>>>>>>
>>>>>>>
>>>>>>> Since the basic workflow of service grouping and docker are working
>>>>>>> now shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>> Did anyone undeploy the application successfully? Were all clusters
>>>>>>>> wiped out?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Don't we also need the event processing chain since it constructs
>>>>>>>>>> the event objects from the Jsons? Additionally this is done through the
>>>>>>>>>> Gson library, so we would have some difficulty in getting that
>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> A good point. May be we need to think little bit here, shall we
>>>>>>>>> first try to convert the required classes and see how good they are?
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>> --
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>> * <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>> --
>>>>> <%2B94776442007>
>>>>> <%2B94776442007>
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> <%2B94776442007>
>>>>> +94 716 358 048
>>>>>
>>>>> --
>>>>> <%2B94776442007>
>>>>> <%2B94776442007>
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> <%2B94776442007>
>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>
>>>>>
>>>>> * <http://wso2.com/>*
>>>>>
>>>>>
>>>>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Okay. Thanks Isuru.
On Mon, Nov 10, 2014 at 2:34 PM, Isuru Haththotuwa <is...@apache.org>
wrote:
> Hi,
>
> There is an issue with undeployment where the clusters do not get properly
> removed from Topology. I'm working on a fix now.
>
> On Mon, Nov 10, 2014 at 2:31 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Hi Isuru,
>>
>> When I undeploy application for docker scenario, this is what I am
>> getting in the logs. Any idea why I am getting cluster terminating and
>> terminated events?
>>
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,319] INFO
>> {org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
>> Handling application terminating event: [application-id] test_app_2
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,319] DEBUG
>> {org.apache.stratos.autoscaler.applications.ApplicationHolder} - Write
>> lock acquired
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,320] INFO
>> {org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
>> Updating application status: [application-id] test_app_2 [status]
>> Terminating
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,320] INFO
>> {org.apache.stratos.autoscaler.monitor.application.ApplicationMonitor} -
>> [ApplicationMonitor] test_app_2 state changes from Terminating to
>> Terminating
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,329] DEBUG
>> {org.apache.stratos.autoscaler.registry.RegistryManager} - Application [
>> test_app_2 ] persisted successfully in the Autoscaler Registry
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,332] DEBUG
>> {org.apache.stratos.autoscaler.applications.ApplicationHolder} - Topology
>> updated:
>> {"applicationMap":{"test_app_2":{"id":"test_app_2","key":"pmZafljPD7OJqm4j","tenantId":-1234,"tenantDomain":"carbon.super","tenantAdminUserName":"admin","applicationStateManager":{"stateStack":["Created","Terminating"],"identifier":"test_app_2"},"aliasToGroupMap":{},"aliasToClusterDataMap":{"myphp":{"serviceType":"php","clusterId":"myphp.php.domain"}}}},"initialized":false}
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,332] INFO
>> {org.apache.stratos.autoscaler.applications.topic.ApplicationsEventPublisher}
>> - Publishing Application activated event for [application]: test_app_2
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,338] ERROR
>> {org.apache.stratos.messaging.message.processor.applications.ApplicationActivatedMessageProcessor}
>> - Invalid State transfer from [ Terminating ] to [ Active ]
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,339] INFO
>> {org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
>> - Topology element [ test_app_2 ]'s life Cycle State changed from [
>> Terminating ] to [ Active ]
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,339] DEBUG
>> {org.apache.stratos.autoscaler.applications.ApplicationHolder} - Write
>> lock released
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,340] INFO
>> {org.apache.stratos.autoscaler.applications.topic.ApplicationsEventPublisher}
>> - Publishing Application terminated event for [application]: test_app_2
>> TID: [0] [STRATOS] [2014-11-10 14:25:37,346] INFO
>> {org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
>> - Topology element [ test_app_2 ]'s life Cycle State changed from [ Active
>> ] to [ Terminating ]
>> TID: [0] [STRATOS] [2014-11-10 14:26:01,001] DEBUG
>> {org.apache.stratos.autoscaler.applications.ApplicationSynchronizeTask} -
>> Applications Complete Event publisher task has been started...
>> TID: [0] [STRATOS] [2014-11-10 14:26:01,002] DEBUG
>> {org.apache.stratos.autoscaler.applications.ApplicationSynchronizeTask} -
>> Executing topology synchronization task
>> TID: [0] [STRATOS] [2014-11-10 14:26:01,002] DEBUG
>> {org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
>> Handling complete application event
>> TID: [0] [STRATOS] [2014-11-10 14:26:01,003] DEBUG
>> {org.apache.stratos.autoscaler.applications.ApplicationHolder} - Read lock
>> acquired
>> TID: [0] [STRATOS] [2014-11-10 14:26:01,003] DEBUG
>> {org.apache.stratos.manager.publisher.TenantSynzhronizerTask} - Publishing
>> complete tenant event
>> TID: [0] [STRATOS] [2014-11-10 14:26:01,004] DEBUG
>> {org.apache.stratos.cloud.controller.topology.TopologySynchronizerTask} -
>> Executing topology synchronization task
>> TID: [0] [STRATOS] [2014-11-10 14:26:01,004] DEBUG
>> {org.apache.stratos.cloud.controller.topology.TopologyEventPublisher} -
>> Publishing complete topology event
>> TID: [0] [STRATOS] [2014-11-10 14:26:01,018] DEBUG
>> {org.apache.stratos.autoscaler.applications.ApplicationHolder} - Read lock
>> released
>> TID: [0] [STRATOS] [2014-11-10 14:26:12,316] DEBUG
>> {org.apache.stratos.autoscaler.monitor.cluster.KubernetesServiceClusterMonitor}
>> - KubernetesServiceClusterMonitor is
>> running...KubernetesServiceClusterMonitor [
>> kubernetesHostClusterId=KubGrp1, clusterId=myphp.php.domain]
>>
>> As you can see, cluster monitor is running even after application
>> undeployment.
>>
>> Thanks.
>>
>> On Mon, Nov 10, 2014 at 9:23 AM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> Please note that Nirmal has updated kubernetes binaries to latest
>>> version in master branch.
>>>
>>> Please use vagrant scripts at [1] if you are going to test kubernetes
>>> scenario on master branch. Earlier one might not work.
>>>
>>> 1.
>>> https://github.com/nirmal070125/vagrant-kubernetes-setup/archive/v2.0.zip
>>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fnirmal070125%2Fvagrant-kubernetes-setup%2Farchive%2Fv2.0.zip&sa=D&sntz=1&usg=AFQjCNFibNQQI3b0jsVybDXGXYHZQ_u7Cg>
>>>
>>> Thanks.
>>>
>>> On Mon, Nov 10, 2014 at 12:40 AM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>> Tested undeployment and worked for simple and complex apps. There is an
>>>> issue in re-deploying the same app, where it did not get re-activated. Will
>>>> look in to this.
>>>>
>>>> On Sun, Nov 9, 2014 at 4:24 PM, Chamila De Alwis <ch...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Lasindu and I are still trying to get the Python CA working. The
>>>>> puppet module is operational. But at the moment the CA is not getting the
>>>>> events published to the MB.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Chamila de Alwis
>>>>> Software Engineer | WSO2 | +94772207163
>>>>> Blog: code.chamiladealwis.com
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Nov 9, 2014 at 3:30 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Shall we merge to the master now?
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <reka@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Fixed the serviceId getting NULL by setting it to the
>>>>>>>> ClusterContext and committed it..
>>>>>>>>
>>>>>>>
>>>>>>> Fine then :)
>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <
>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Lahiru,
>>>>>>>>>
>>>>>>>>> As you have introduced ClusteContext in ClusterMonitor, the
>>>>>>>>> serviceId got to removed. Is this done purposely? If so, can we update the
>>>>>>>>> getServiceId() (which referred by several other places) in monitors to
>>>>>>>>> return the correct serviceId by reading ClusterContext?
>>>>>>>>>
>>>>>>>>> Due to this, ClusterMonitor returns serviceId as null and it
>>>>>>>>> causes issue in the cluster monitor creation and in the event publishing..
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Reka
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <
>>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <
>>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <
>>>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <
>>>>>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>
>>>>>>>>>>>>> After fixing few issues, i could get the application
>>>>>>>>>>>>> undeployment working with one cluster now. So the basic undeployment is
>>>>>>>>>>>>> working fine...Will continue testing with a complex application...
>>>>>>>>>>>>>
>>>>>>>>>>>> Great! I will test the same with a complex application.
>>>>>>>>>>>>
>>>>>>>>>>> Getting the following exception with a complex app (when sending
>>>>>>>>>>> cluster activated event), will check and fix asap.
>>>>>>>>>>> Exception in thread "Thread-61"
>>>>>>>>>>> java.lang.IllegalMonitorStateException
>>>>>>>>>>> at
>>>>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>>>>>>>> at
>>>>>>>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>>>>>>>> at
>>>>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I too got this issue as well as a NPE while getting locks..Later
>>>>>>>>>> found that serviceId was null when getting the locks..I have fixed
>>>>>>>>>> ServiceId issue..Can you try now and see whether you are still getting this
>>>>>>>>>> issue?
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Reka
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Reka
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <
>>>>>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>>>>>>>> currerntly under investigation.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Got the same issue, will check in this.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>>>>>>>> now? WDYT?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>>>>>>>> clusters wiped out?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> A good point. May be we need to think little bit here,
>>>>>>>>>>>>>>>>> shall we first try to convert the required classes and see how good they
>>>>>>>>>>>>>>>>> are?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Isuru H.
>>>>>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>>>>>> Mobile: +94776442007
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Isuru H.
>>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>>> +94 716 358 048
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Isuru H.
>>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>>> Mobile: +94776442007
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>> Senior Software Engineer,
>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>> Mobile: +94776442007
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Reka Thirunavukkarasu
>>>>>>>> Senior Software Engineer,
>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>> Mobile: +94776442007
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> --
>>>>>>> Lahiru Sandaruwan
>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>> lean.enterprise.middleware
>>>>>>>
>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> Lahiru Sandaruwan
>>>>>> Committer and PMC member, Apache Stratos,
>>>>>> Senior Software Engineer,
>>>>>> WSO2 Inc., http://wso2.com
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>
>>>>>> --
>>>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>>>>> +94 716 358 048
>>>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>*
>>>>>> <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>> * <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>>
>>>
>>>
>>> --
>>> Raj
>>>
>>
>>
>>
>> --
>> Raj
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
Hi,
There is an issue with undeployment where the clusters do not get properly
removed from Topology. I'm working on a fix now.
On Mon, Nov 10, 2014 at 2:31 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Hi Isuru,
>
> When I undeploy application for docker scenario, this is what I am getting
> in the logs. Any idea why I am getting cluster terminating and terminated
> events?
>
> TID: [0] [STRATOS] [2014-11-10 14:25:37,319] INFO
> {org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
> Handling application terminating event: [application-id] test_app_2
> TID: [0] [STRATOS] [2014-11-10 14:25:37,319] DEBUG
> {org.apache.stratos.autoscaler.applications.ApplicationHolder} - Write
> lock acquired
> TID: [0] [STRATOS] [2014-11-10 14:25:37,320] INFO
> {org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
> Updating application status: [application-id] test_app_2 [status]
> Terminating
> TID: [0] [STRATOS] [2014-11-10 14:25:37,320] INFO
> {org.apache.stratos.autoscaler.monitor.application.ApplicationMonitor} -
> [ApplicationMonitor] test_app_2 state changes from Terminating to
> Terminating
> TID: [0] [STRATOS] [2014-11-10 14:25:37,329] DEBUG
> {org.apache.stratos.autoscaler.registry.RegistryManager} - Application [
> test_app_2 ] persisted successfully in the Autoscaler Registry
> TID: [0] [STRATOS] [2014-11-10 14:25:37,332] DEBUG
> {org.apache.stratos.autoscaler.applications.ApplicationHolder} - Topology
> updated:
> {"applicationMap":{"test_app_2":{"id":"test_app_2","key":"pmZafljPD7OJqm4j","tenantId":-1234,"tenantDomain":"carbon.super","tenantAdminUserName":"admin","applicationStateManager":{"stateStack":["Created","Terminating"],"identifier":"test_app_2"},"aliasToGroupMap":{},"aliasToClusterDataMap":{"myphp":{"serviceType":"php","clusterId":"myphp.php.domain"}}}},"initialized":false}
> TID: [0] [STRATOS] [2014-11-10 14:25:37,332] INFO
> {org.apache.stratos.autoscaler.applications.topic.ApplicationsEventPublisher}
> - Publishing Application activated event for [application]: test_app_2
> TID: [0] [STRATOS] [2014-11-10 14:25:37,338] ERROR
> {org.apache.stratos.messaging.message.processor.applications.ApplicationActivatedMessageProcessor}
> - Invalid State transfer from [ Terminating ] to [ Active ]
> TID: [0] [STRATOS] [2014-11-10 14:25:37,339] INFO
> {org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
> - Topology element [ test_app_2 ]'s life Cycle State changed from [
> Terminating ] to [ Active ]
> TID: [0] [STRATOS] [2014-11-10 14:25:37,339] DEBUG
> {org.apache.stratos.autoscaler.applications.ApplicationHolder} - Write
> lock released
> TID: [0] [STRATOS] [2014-11-10 14:25:37,340] INFO
> {org.apache.stratos.autoscaler.applications.topic.ApplicationsEventPublisher}
> - Publishing Application terminated event for [application]: test_app_2
> TID: [0] [STRATOS] [2014-11-10 14:25:37,346] INFO
> {org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
> - Topology element [ test_app_2 ]'s life Cycle State changed from [ Active
> ] to [ Terminating ]
> TID: [0] [STRATOS] [2014-11-10 14:26:01,001] DEBUG
> {org.apache.stratos.autoscaler.applications.ApplicationSynchronizeTask} -
> Applications Complete Event publisher task has been started...
> TID: [0] [STRATOS] [2014-11-10 14:26:01,002] DEBUG
> {org.apache.stratos.autoscaler.applications.ApplicationSynchronizeTask} -
> Executing topology synchronization task
> TID: [0] [STRATOS] [2014-11-10 14:26:01,002] DEBUG
> {org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
> Handling complete application event
> TID: [0] [STRATOS] [2014-11-10 14:26:01,003] DEBUG
> {org.apache.stratos.autoscaler.applications.ApplicationHolder} - Read lock
> acquired
> TID: [0] [STRATOS] [2014-11-10 14:26:01,003] DEBUG
> {org.apache.stratos.manager.publisher.TenantSynzhronizerTask} - Publishing
> complete tenant event
> TID: [0] [STRATOS] [2014-11-10 14:26:01,004] DEBUG
> {org.apache.stratos.cloud.controller.topology.TopologySynchronizerTask} -
> Executing topology synchronization task
> TID: [0] [STRATOS] [2014-11-10 14:26:01,004] DEBUG
> {org.apache.stratos.cloud.controller.topology.TopologyEventPublisher} -
> Publishing complete topology event
> TID: [0] [STRATOS] [2014-11-10 14:26:01,018] DEBUG
> {org.apache.stratos.autoscaler.applications.ApplicationHolder} - Read lock
> released
> TID: [0] [STRATOS] [2014-11-10 14:26:12,316] DEBUG
> {org.apache.stratos.autoscaler.monitor.cluster.KubernetesServiceClusterMonitor}
> - KubernetesServiceClusterMonitor is
> running...KubernetesServiceClusterMonitor [
> kubernetesHostClusterId=KubGrp1, clusterId=myphp.php.domain]
>
> As you can see, cluster monitor is running even after application
> undeployment.
>
> Thanks.
>
> On Mon, Nov 10, 2014 at 9:23 AM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> Please note that Nirmal has updated kubernetes binaries to latest version
>> in master branch.
>>
>> Please use vagrant scripts at [1] if you are going to test kubernetes
>> scenario on master branch. Earlier one might not work.
>>
>> 1.
>> https://github.com/nirmal070125/vagrant-kubernetes-setup/archive/v2.0.zip
>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fnirmal070125%2Fvagrant-kubernetes-setup%2Farchive%2Fv2.0.zip&sa=D&sntz=1&usg=AFQjCNFibNQQI3b0jsVybDXGXYHZQ_u7Cg>
>>
>> Thanks.
>>
>> On Mon, Nov 10, 2014 at 12:40 AM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>> Tested undeployment and worked for simple and complex apps. There is an
>>> issue in re-deploying the same app, where it did not get re-activated. Will
>>> look in to this.
>>>
>>> On Sun, Nov 9, 2014 at 4:24 PM, Chamila De Alwis <ch...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Lasindu and I are still trying to get the Python CA working. The puppet
>>>> module is operational. But at the moment the CA is not getting the events
>>>> published to the MB.
>>>>
>>>>
>>>> Regards,
>>>> Chamila de Alwis
>>>> Software Engineer | WSO2 | +94772207163
>>>> Blog: code.chamiladealwis.com
>>>>
>>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 3:30 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>> wrote:
>>>>
>>>>> Shall we merge to the master now?
>>>>>
>>>>> On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Fixed the serviceId getting NULL by setting it to the ClusterContext
>>>>>>> and committed it..
>>>>>>>
>>>>>>
>>>>>> Fine then :)
>>>>>>
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <reka@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi Lahiru,
>>>>>>>>
>>>>>>>> As you have introduced ClusteContext in ClusterMonitor, the
>>>>>>>> serviceId got to removed. Is this done purposely? If so, can we update the
>>>>>>>> getServiceId() (which referred by several other places) in monitors to
>>>>>>>> return the correct serviceId by reading ClusterContext?
>>>>>>>>
>>>>>>>> Due to this, ClusterMonitor returns serviceId as null and it causes
>>>>>>>> issue in the cluster monitor creation and in the event publishing..
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Reka
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <
>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <
>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <
>>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <
>>>>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>
>>>>>>>>>>>> After fixing few issues, i could get the application
>>>>>>>>>>>> undeployment working with one cluster now. So the basic undeployment is
>>>>>>>>>>>> working fine...Will continue testing with a complex application...
>>>>>>>>>>>>
>>>>>>>>>>> Great! I will test the same with a complex application.
>>>>>>>>>>>
>>>>>>>>>> Getting the following exception with a complex app (when sending
>>>>>>>>>> cluster activated event), will check and fix asap.
>>>>>>>>>> Exception in thread "Thread-61"
>>>>>>>>>> java.lang.IllegalMonitorStateException
>>>>>>>>>> at
>>>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>>>>>>> at
>>>>>>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>>>>>>> at
>>>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>>>>>>> at
>>>>>>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>>>>>>> at
>>>>>>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>>>>>>> at
>>>>>>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>>>>>>> at
>>>>>>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I too got this issue as well as a NPE while getting locks..Later
>>>>>>>>> found that serviceId was null when getting the locks..I have fixed
>>>>>>>>> ServiceId issue..Can you try now and see whether you are still getting this
>>>>>>>>> issue?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Reka
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Reka
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <
>>>>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>>>>>>> currerntly under investigation.
>>>>>>>>>>>>>>
>>>>>>>>>>>>> Got the same issue, will check in this.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>>>>>>> now? WDYT?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>>>>>>> clusters wiped out?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> A good point. May be we need to think little bit here,
>>>>>>>>>>>>>>>> shall we first try to convert the required classes and see how good they
>>>>>>>>>>>>>>>> are?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Isuru H.
>>>>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>>>>> Mobile: +94776442007
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Isuru H.
>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>> +94 716 358 048
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Isuru H.
>>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>> Senior Software Engineer,
>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>> Mobile: +94776442007
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Reka Thirunavukkarasu
>>>>>>>> Senior Software Engineer,
>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>> Mobile: +94776442007
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Reka Thirunavukkarasu
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>> Mobile: +94776442007
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> Lahiru Sandaruwan
>>>>>> Committer and PMC member, Apache Stratos,
>>>>>> Senior Software Engineer,
>>>>>> WSO2 Inc., http://wso2.com
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> Lahiru Sandaruwan
>>>>> Committer and PMC member, Apache Stratos,
>>>>> Senior Software Engineer,
>>>>> WSO2 Inc., http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>
>>>>> --
>>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>>>> +94 716 358 048
>>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>*
>>>>> <http://wso2.com/>*
>>>>>
>>>>>
>>>>> * <http://wso2.com/>*
>>>>>
>>>>>
>>>>>
>>
>>
>> --
>> Raj
>>
>
>
>
> --
> Raj
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Hi Isuru,
When I undeploy application for docker scenario, this is what I am getting
in the logs. Any idea why I am getting cluster terminating and terminated
events?
TID: [0] [STRATOS] [2014-11-10 14:25:37,319] INFO
{org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
Handling application terminating event: [application-id] test_app_2
TID: [0] [STRATOS] [2014-11-10 14:25:37,319] DEBUG
{org.apache.stratos.autoscaler.applications.ApplicationHolder} - Write
lock acquired
TID: [0] [STRATOS] [2014-11-10 14:25:37,320] INFO
{org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
Updating application status: [application-id] test_app_2 [status]
Terminating
TID: [0] [STRATOS] [2014-11-10 14:25:37,320] INFO
{org.apache.stratos.autoscaler.monitor.application.ApplicationMonitor} -
[ApplicationMonitor] test_app_2 state changes from Terminating to
Terminating
TID: [0] [STRATOS] [2014-11-10 14:25:37,329] DEBUG
{org.apache.stratos.autoscaler.registry.RegistryManager} - Application [
test_app_2 ] persisted successfully in the Autoscaler Registry
TID: [0] [STRATOS] [2014-11-10 14:25:37,332] DEBUG
{org.apache.stratos.autoscaler.applications.ApplicationHolder} - Topology
updated:
{"applicationMap":{"test_app_2":{"id":"test_app_2","key":"pmZafljPD7OJqm4j","tenantId":-1234,"tenantDomain":"carbon.super","tenantAdminUserName":"admin","applicationStateManager":{"stateStack":["Created","Terminating"],"identifier":"test_app_2"},"aliasToGroupMap":{},"aliasToClusterDataMap":{"myphp":{"serviceType":"php","clusterId":"myphp.php.domain"}}}},"initialized":false}
TID: [0] [STRATOS] [2014-11-10 14:25:37,332] INFO
{org.apache.stratos.autoscaler.applications.topic.ApplicationsEventPublisher}
- Publishing Application activated event for [application]: test_app_2
TID: [0] [STRATOS] [2014-11-10 14:25:37,338] ERROR
{org.apache.stratos.messaging.message.processor.applications.ApplicationActivatedMessageProcessor}
- Invalid State transfer from [ Terminating ] to [ Active ]
TID: [0] [STRATOS] [2014-11-10 14:25:37,339] INFO
{org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
- Topology element [ test_app_2 ]'s life Cycle State changed from [
Terminating ] to [ Active ]
TID: [0] [STRATOS] [2014-11-10 14:25:37,339] DEBUG
{org.apache.stratos.autoscaler.applications.ApplicationHolder} - Write
lock released
TID: [0] [STRATOS] [2014-11-10 14:25:37,340] INFO
{org.apache.stratos.autoscaler.applications.topic.ApplicationsEventPublisher}
- Publishing Application terminated event for [application]: test_app_2
TID: [0] [STRATOS] [2014-11-10 14:25:37,346] INFO
{org.apache.stratos.messaging.domain.topology.lifecycle.LifeCycleStateManager}
- Topology element [ test_app_2 ]'s life Cycle State changed from [ Active
] to [ Terminating ]
TID: [0] [STRATOS] [2014-11-10 14:26:01,001] DEBUG
{org.apache.stratos.autoscaler.applications.ApplicationSynchronizeTask} -
Applications Complete Event publisher task has been started...
TID: [0] [STRATOS] [2014-11-10 14:26:01,002] DEBUG
{org.apache.stratos.autoscaler.applications.ApplicationSynchronizeTask} -
Executing topology synchronization task
TID: [0] [STRATOS] [2014-11-10 14:26:01,002] DEBUG
{org.apache.stratos.autoscaler.applications.topic.ApplicationBuilder} -
Handling complete application event
TID: [0] [STRATOS] [2014-11-10 14:26:01,003] DEBUG
{org.apache.stratos.autoscaler.applications.ApplicationHolder} - Read lock
acquired
TID: [0] [STRATOS] [2014-11-10 14:26:01,003] DEBUG
{org.apache.stratos.manager.publisher.TenantSynzhronizerTask} - Publishing
complete tenant event
TID: [0] [STRATOS] [2014-11-10 14:26:01,004] DEBUG
{org.apache.stratos.cloud.controller.topology.TopologySynchronizerTask} -
Executing topology synchronization task
TID: [0] [STRATOS] [2014-11-10 14:26:01,004] DEBUG
{org.apache.stratos.cloud.controller.topology.TopologyEventPublisher} -
Publishing complete topology event
TID: [0] [STRATOS] [2014-11-10 14:26:01,018] DEBUG
{org.apache.stratos.autoscaler.applications.ApplicationHolder} - Read lock
released
TID: [0] [STRATOS] [2014-11-10 14:26:12,316] DEBUG
{org.apache.stratos.autoscaler.monitor.cluster.KubernetesServiceClusterMonitor}
- KubernetesServiceClusterMonitor is
running...KubernetesServiceClusterMonitor [
kubernetesHostClusterId=KubGrp1, clusterId=myphp.php.domain]
As you can see, cluster monitor is running even after application
undeployment.
Thanks.
On Mon, Nov 10, 2014 at 9:23 AM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Hi all,
>
> Please note that Nirmal has updated kubernetes binaries to latest version
> in master branch.
>
> Please use vagrant scripts at [1] if you are going to test kubernetes
> scenario on master branch. Earlier one might not work.
>
> 1.
> https://github.com/nirmal070125/vagrant-kubernetes-setup/archive/v2.0.zip
> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fnirmal070125%2Fvagrant-kubernetes-setup%2Farchive%2Fv2.0.zip&sa=D&sntz=1&usg=AFQjCNFibNQQI3b0jsVybDXGXYHZQ_u7Cg>
>
> Thanks.
>
> On Mon, Nov 10, 2014 at 12:40 AM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>> Tested undeployment and worked for simple and complex apps. There is an
>> issue in re-deploying the same app, where it did not get re-activated. Will
>> look in to this.
>>
>> On Sun, Nov 9, 2014 at 4:24 PM, Chamila De Alwis <ch...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Lasindu and I are still trying to get the Python CA working. The puppet
>>> module is operational. But at the moment the CA is not getting the events
>>> published to the MB.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>> On Sun, Nov 9, 2014 at 3:30 PM, Lahiru Sandaruwan <la...@wso2.com>
>>> wrote:
>>>
>>>> Shall we merge to the master now?
>>>>
>>>> On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Fixed the serviceId getting NULL by setting it to the ClusterContext
>>>>>> and committed it..
>>>>>>
>>>>>
>>>>> Fine then :)
>>>>>
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Lahiru,
>>>>>>>
>>>>>>> As you have introduced ClusteContext in ClusterMonitor, the
>>>>>>> serviceId got to removed. Is this done purposely? If so, can we update the
>>>>>>> getServiceId() (which referred by several other places) in monitors to
>>>>>>> return the correct serviceId by reading ClusterContext?
>>>>>>>
>>>>>>> Due to this, ClusterMonitor returns serviceId as null and it causes
>>>>>>> issue in the cluster monitor creation and in the event publishing..
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Reka
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <reka@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <
>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <
>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <
>>>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi all,
>>>>>>>>>>>
>>>>>>>>>>> After fixing few issues, i could get the application
>>>>>>>>>>> undeployment working with one cluster now. So the basic undeployment is
>>>>>>>>>>> working fine...Will continue testing with a complex application...
>>>>>>>>>>>
>>>>>>>>>> Great! I will test the same with a complex application.
>>>>>>>>>>
>>>>>>>>> Getting the following exception with a complex app (when sending
>>>>>>>>> cluster activated event), will check and fix asap.
>>>>>>>>> Exception in thread "Thread-61"
>>>>>>>>> java.lang.IllegalMonitorStateException
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>>>>>> at
>>>>>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>>>>>> at
>>>>>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>>>>>> at
>>>>>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>>>>>> at
>>>>>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>
>>>>>>>>
>>>>>>>> I too got this issue as well as a NPE while getting locks..Later
>>>>>>>> found that serviceId was null when getting the locks..I have fixed
>>>>>>>> ServiceId issue..Can you try now and see whether you are still getting this
>>>>>>>> issue?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Reka
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Reka
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <
>>>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>>>>>> currerntly under investigation.
>>>>>>>>>>>>>
>>>>>>>>>>>> Got the same issue, will check in this.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>>>>>> now? WDYT?
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>>>>>> clusters wiped out?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> A good point. May be we need to think little bit here, shall
>>>>>>>>>>>>>>> we first try to convert the required classes and see how good they are?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Isuru H.
>>>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>>>> Mobile: +94776442007
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>
>>>>>>>>>>> Isuru H.
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> +94 716 358 048
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>
>>>>>>>>>>> Isuru H.
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Reka Thirunavukkarasu
>>>>>>>> Senior Software Engineer,
>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>> Mobile: +94776442007
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Reka Thirunavukkarasu
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>> Mobile: +94776442007
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> Lahiru Sandaruwan
>>>>> Committer and PMC member, Apache Stratos,
>>>>> Senior Software Engineer,
>>>>> WSO2 Inc., http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Committer and PMC member, Apache Stratos,
>>>> Senior Software Engineer,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>> --
>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>>> +94 716 358 048
>>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>*
>>>> <http://wso2.com/>*
>>>>
>>>>
>>>> * <http://wso2.com/>*
>>>>
>>>>
>>>>
>
>
> --
> Raj
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Hi all,
Please note that Nirmal has updated kubernetes binaries to latest version
in master branch.
Please use vagrant scripts at [1] if you are going to test kubernetes
scenario on master branch. Earlier one might not work.
1. https://github.com/nirmal070125/vagrant-kubernetes-setup/archive/v2.0.zip
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fnirmal070125%2Fvagrant-kubernetes-setup%2Farchive%2Fv2.0.zip&sa=D&sntz=1&usg=AFQjCNFibNQQI3b0jsVybDXGXYHZQ_u7Cg>
Thanks.
On Mon, Nov 10, 2014 at 12:40 AM, Isuru Haththotuwa <is...@apache.org>
wrote:
> Tested undeployment and worked for simple and complex apps. There is an
> issue in re-deploying the same app, where it did not get re-activated. Will
> look in to this.
>
> On Sun, Nov 9, 2014 at 4:24 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> Hi,
>>
>> Lasindu and I are still trying to get the Python CA working. The puppet
>> module is operational. But at the moment the CA is not getting the events
>> published to the MB.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Sun, Nov 9, 2014 at 3:30 PM, Lahiru Sandaruwan <la...@wso2.com>
>> wrote:
>>
>>> Shall we merge to the master now?
>>>
>>> On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <la...@wso2.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>> wrote:
>>>>
>>>>> Fixed the serviceId getting NULL by setting it to the ClusterContext
>>>>> and committed it..
>>>>>
>>>>
>>>> Fine then :)
>>>>
>>>>>
>>>>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Lahiru,
>>>>>>
>>>>>> As you have introduced ClusteContext in ClusterMonitor, the serviceId
>>>>>> got to removed. Is this done purposely? If so, can we update the
>>>>>> getServiceId() (which referred by several other places) in monitors to
>>>>>> return the correct serviceId by reading ClusterContext?
>>>>>>
>>>>>> Due to this, ClusterMonitor returns serviceId as null and it causes
>>>>>> issue in the cluster monitor creation and in the event publishing..
>>>>>>
>>>>>> Thanks,
>>>>>> Reka
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>>>> > wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <
>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <
>>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> After fixing few issues, i could get the application undeployment
>>>>>>>>>> working with one cluster now. So the basic undeployment is working
>>>>>>>>>> fine...Will continue testing with a complex application...
>>>>>>>>>>
>>>>>>>>> Great! I will test the same with a complex application.
>>>>>>>>>
>>>>>>>> Getting the following exception with a complex app (when sending
>>>>>>>> cluster activated event), will check and fix asap.
>>>>>>>> Exception in thread "Thread-61"
>>>>>>>> java.lang.IllegalMonitorStateException
>>>>>>>> at
>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>>>>> at
>>>>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>>>>> at
>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>>>>> at
>>>>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>>>>> at
>>>>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>>>>> at
>>>>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>>>>> at
>>>>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>
>>>>>>>
>>>>>>> I too got this issue as well as a NPE while getting locks..Later
>>>>>>> found that serviceId was null when getting the locks..I have fixed
>>>>>>> ServiceId issue..Can you try now and see whether you are still getting this
>>>>>>> issue?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Reka
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Reka
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <
>>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>>>>> currerntly under investigation.
>>>>>>>>>>>>
>>>>>>>>>>> Got the same issue, will check in this.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>>>>> now? WDYT?
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>>>>> clusters wiped out?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> A good point. May be we need to think little bit here, shall
>>>>>>>>>>>>>> we first try to convert the required classes and see how good they are?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Isuru H.
>>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>>> Mobile: +94776442007
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>
>>>>>>>>>> Isuru H.
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> +94 716 358 048
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>
>>>>>>>>>> Isuru H.
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Reka Thirunavukkarasu
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>> Mobile: +94776442007
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Committer and PMC member, Apache Stratos,
>>>> Senior Software Engineer,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Committer and PMC member, Apache Stratos,
>>> Senior Software Engineer,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>> --
>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
>>> +94 716 358 048
>>> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>*
>>> <http://wso2.com/>*
>>>
>>>
>>> * <http://wso2.com/>*
>>>
>>>
>>>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
Tested undeployment and worked for simple and complex apps. There is an
issue in re-deploying the same app, where it did not get re-activated. Will
look in to this.
On Sun, Nov 9, 2014 at 4:24 PM, Chamila De Alwis <ch...@wso2.com> wrote:
> Hi,
>
> Lasindu and I are still trying to get the Python CA working. The puppet
> module is operational. But at the moment the CA is not getting the events
> published to the MB.
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Sun, Nov 9, 2014 at 3:30 PM, Lahiru Sandaruwan <la...@wso2.com>
> wrote:
>
>> Shall we merge to the master now?
>>
>> On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <la...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>> wrote:
>>>
>>>> Fixed the serviceId getting NULL by setting it to the ClusterContext
>>>> and committed it..
>>>>
>>>
>>> Fine then :)
>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Lahiru,
>>>>>
>>>>> As you have introduced ClusteContext in ClusterMonitor, the serviceId
>>>>> got to removed. Is this done purposely? If so, can we update the
>>>>> getServiceId() (which referred by several other places) in monitors to
>>>>> return the correct serviceId by reading ClusterContext?
>>>>>
>>>>> Due to this, ClusterMonitor returns serviceId as null and it causes
>>>>> issue in the cluster monitor creation and in the event publishing..
>>>>>
>>>>> Thanks,
>>>>> Reka
>>>>>
>>>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <is...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>>>> > wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <
>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> After fixing few issues, i could get the application undeployment
>>>>>>>>> working with one cluster now. So the basic undeployment is working
>>>>>>>>> fine...Will continue testing with a complex application...
>>>>>>>>>
>>>>>>>> Great! I will test the same with a complex application.
>>>>>>>>
>>>>>>> Getting the following exception with a complex app (when sending
>>>>>>> cluster activated event), will check and fix asap.
>>>>>>> Exception in thread "Thread-61"
>>>>>>> java.lang.IllegalMonitorStateException
>>>>>>> at
>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>>>> at
>>>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>>>> at
>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>>>> at
>>>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>>>> at
>>>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>>>> at
>>>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>>>> at
>>>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>
>>>>>>
>>>>>> I too got this issue as well as a NPE while getting locks..Later
>>>>>> found that serviceId was null when getting the locks..I have fixed
>>>>>> ServiceId issue..Can you try now and see whether you are still getting this
>>>>>> issue?
>>>>>>
>>>>>> Thanks,
>>>>>> Reka
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Reka
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <
>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>>>> currerntly under investigation.
>>>>>>>>>>>
>>>>>>>>>> Got the same issue, will check in this.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>>>> now? WDYT?
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>>>> clusters wiped out?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> A good point. May be we need to think little bit here, shall
>>>>>>>>>>>>> we first try to convert the required classes and see how good they are?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>
>>>>>>>>>>> Isuru H.
>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>> Senior Software Engineer,
>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>> Mobile: +94776442007
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> <%2B94776442007>
>>>>>>>>> <%2B94776442007>
>>>>>>>>> Thanks and Regards,
>>>>>>>>>
>>>>>>>>> Isuru H.
>>>>>>>>> <%2B94776442007>
>>>>>>>>> +94 716 358 048
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> <%2B94776442007>
>>>>>>>>> <%2B94776442007>
>>>>>>>>> Thanks and Regards,
>>>>>>>>>
>>>>>>>>> Isuru H.
>>>>>>>>> <%2B94776442007>
>>>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Reka Thirunavukkarasu
>>>> Senior Software Engineer,
>>>> WSO2, Inc.:http://wso2.com,
>>>> Mobile: +94776442007
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Committer and PMC member, Apache Stratos,
>>> Senior Software Engineer,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Committer and PMC member, Apache Stratos,
>> Senior Software Engineer,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Nirmal Fernando <ni...@gmail.com>.
Please do a rebase instead of merge.
On Sun, Nov 9, 2014 at 12:05 PM, Rajaratnam Rajkumar <rr...@gmail.com>
wrote:
> Yes Lahiru, merge now :)
>
> On Sunday, November 9, 2014, Chamila De Alwis <ch...@wso2.com> wrote:
>
>> Hi,
>>
>> Lasindu and I are still trying to get the Python CA working. The puppet
>> module is operational. But at the moment the CA is not getting the events
>> published to the MB.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Sun, Nov 9, 2014 at 3:30 PM, Lahiru Sandaruwan <la...@wso2.com>
>> wrote:
>>
>>> Shall we merge to the master now?
>>>
>>> On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <la...@wso2.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>> wrote:
>>>>
>>>>> Fixed the serviceId getting NULL by setting it to the ClusterContext
>>>>> and committed it..
>>>>>
>>>>
>>>> Fine then :)
>>>>
>>>>>
>>>>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Lahiru,
>>>>>>
>>>>>> As you have introduced ClusteContext in ClusterMonitor, the serviceId
>>>>>> got to removed. Is this done purposely? If so, can we update the
>>>>>> getServiceId() (which referred by several other places) in monitors to
>>>>>> return the correct serviceId by reading ClusterContext?
>>>>>>
>>>>>> Due to this, ClusterMonitor returns serviceId as null and it causes
>>>>>> issue in the cluster monitor creation and in the event publishing..
>>>>>>
>>>>>> Thanks,
>>>>>> Reka
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>>>> > wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <
>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <
>>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> After fixing few issues, i could get the application undeployment
>>>>>>>>>> working with one cluster now. So the basic undeployment is working
>>>>>>>>>> fine...Will continue testing with a complex application...
>>>>>>>>>>
>>>>>>>>> Great! I will test the same with a complex application.
>>>>>>>>>
>>>>>>>> Getting the following exception with a complex app (when sending
>>>>>>>> cluster activated event), will check and fix asap.
>>>>>>>> Exception in thread "Thread-61"
>>>>>>>> java.lang.IllegalMonitorStateException
>>>>>>>> at
>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>>>>> at
>>>>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>>>>> at
>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>>>>> at
>>>>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>>>>> at
>>>>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>>>>> at
>>>>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>>>>> at
>>>>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>
>>>>>>>
>>>>>>> I too got this issue as well as a NPE while getting locks..Later
>>>>>>> found that serviceId was null when getting the locks..I have fixed
>>>>>>> ServiceId issue..Can you try now and see whether you are still getting this
>>>>>>> issue?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Reka
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Reka
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <
>>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>>>>> currerntly under investigation.
>>>>>>>>>>>>
>>>>>>>>>>> Got the same issue, will check in this.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>>>>> now? WDYT?
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>>>>> clusters wiped out?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> A good point. May be we need to think little bit here, shall
>>>>>>>>>>>>>> we first try to convert the required classes and see how good they are?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Isuru H.
>>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>>> Mobile: +94776442007
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>
>>>>>>>>>> Isuru H.
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> +94 716 358 048
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>
>>>>>>>>>> Isuru H.
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Reka Thirunavukkarasu
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>> Mobile: +94776442007
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Committer and PMC member, Apache Stratos,
>>>> Senior Software Engineer,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Committer and PMC member, Apache Stratos,
>>> Senior Software Engineer,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajaratnam Rajkumar <rr...@gmail.com>.
Yes Lahiru, merge now :)
On Sunday, November 9, 2014, Chamila De Alwis <ch...@wso2.com> wrote:
> Hi,
>
> Lasindu and I are still trying to get the Python CA working. The puppet
> module is operational. But at the moment the CA is not getting the events
> published to the MB.
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Sun, Nov 9, 2014 at 3:30 PM, Lahiru Sandaruwan <lahirus@wso2.com
> <javascript:_e(%7B%7D,'cvml','lahirus@wso2.com');>> wrote:
>
>> Shall we merge to the master now?
>>
>> On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <lahirus@wso2.com
>> <javascript:_e(%7B%7D,'cvml','lahirus@wso2.com');>> wrote:
>>
>>>
>>>
>>> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <reka@wso2.com
>>> <javascript:_e(%7B%7D,'cvml','reka@wso2.com');>> wrote:
>>>
>>>> Fixed the serviceId getting NULL by setting it to the ClusterContext
>>>> and committed it..
>>>>
>>>
>>> Fine then :)
>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <reka@wso2.com
>>>> <javascript:_e(%7B%7D,'cvml','reka@wso2.com');>> wrote:
>>>>
>>>>> Hi Lahiru,
>>>>>
>>>>> As you have introduced ClusteContext in ClusterMonitor, the serviceId
>>>>> got to removed. Is this done purposely? If so, can we update the
>>>>> getServiceId() (which referred by several other places) in monitors to
>>>>> return the correct serviceId by reading ClusterContext?
>>>>>
>>>>> Due to this, ClusterMonitor returns serviceId as null and it causes
>>>>> issue in the cluster monitor creation and in the event publishing..
>>>>>
>>>>> Thanks,
>>>>> Reka
>>>>>
>>>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <reka@wso2.com
>>>>> <javascript:_e(%7B%7D,'cvml','reka@wso2.com');>> wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>>> <javascript:_e(%7B%7D,'cvml','isuruh@apache.org');>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>>>> <javascript:_e(%7B%7D,'cvml','isuruh@apache.org');>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <
>>>>>>>> reka@wso2.com <javascript:_e(%7B%7D,'cvml','reka@wso2.com');>>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> After fixing few issues, i could get the application undeployment
>>>>>>>>> working with one cluster now. So the basic undeployment is working
>>>>>>>>> fine...Will continue testing with a complex application...
>>>>>>>>>
>>>>>>>> Great! I will test the same with a complex application.
>>>>>>>>
>>>>>>> Getting the following exception with a complex app (when sending
>>>>>>> cluster activated event), will check and fix asap.
>>>>>>> Exception in thread "Thread-61"
>>>>>>> java.lang.IllegalMonitorStateException
>>>>>>> at
>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>>>> at
>>>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>>>> at
>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>>>> at
>>>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>>>> at
>>>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>>>> at
>>>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>>>> at
>>>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>
>>>>>>
>>>>>> I too got this issue as well as a NPE while getting locks..Later
>>>>>> found that serviceId was null when getting the locks..I have fixed
>>>>>> ServiceId issue..Can you try now and see whether you are still getting this
>>>>>> issue?
>>>>>>
>>>>>> Thanks,
>>>>>> Reka
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Reka
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <
>>>>>>>>> isuruh@apache.org
>>>>>>>>> <javascript:_e(%7B%7D,'cvml','isuruh@apache.org');>> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> <javascript:_e(%7B%7D,'cvml','imesh@apache.org');>> wrote:
>>>>>>>>>>
>>>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>>>> currerntly under investigation.
>>>>>>>>>>>
>>>>>>>>>> Got the same issue, will check in this.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>>>> now? WDYT?
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>>>> rraju1990@gmail.com
>>>>>>>>>>> <javascript:_e(%7B%7D,'cvml','rraju1990@gmail.com');>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>>>> clusters wiped out?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org
>>>>>>>>>>>> <javascript:_e(%7B%7D,'cvml','imesh@apache.org');>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> A good point. May be we need to think little bit here, shall
>>>>>>>>>>>>> we first try to convert the required classes and see how good they are?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>
>>>>>>>>>>> Isuru H.
>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>> Senior Software Engineer,
>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>> Mobile: +94776442007
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> <%2B94776442007>
>>>>>>>>> <%2B94776442007>
>>>>>>>>> Thanks and Regards,
>>>>>>>>>
>>>>>>>>> Isuru H.
>>>>>>>>> <%2B94776442007>
>>>>>>>>> +94 716 358 048
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> <%2B94776442007>
>>>>>>>>> <%2B94776442007>
>>>>>>>>> Thanks and Regards,
>>>>>>>>>
>>>>>>>>> Isuru H.
>>>>>>>>> <%2B94776442007>
>>>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Reka Thirunavukkarasu
>>>> Senior Software Engineer,
>>>> WSO2, Inc.:http://wso2.com,
>>>> Mobile: +94776442007
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Committer and PMC member, Apache Stratos,
>>> Senior Software Engineer,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com
>>> <javascript:_e(%7B%7D,'cvml','lahirus@wso2.com');> blog:
>>> http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Committer and PMC member, Apache Stratos,
>> Senior Software Engineer,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com
>> <javascript:_e(%7B%7D,'cvml','lahirus@wso2.com');> blog:
>> http://lahiruwrites.blogspot.com/
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
We have now merged all changes from the docker-grouping-merge branch to the
master branch. Could not rebase due to the number of conflicts occurred,
therefore a merge was done.
Master branch now can be used for development. Please do a complete build
and run the tests.
Thanks
On Sun, Nov 9, 2014 at 11:58 PM, Imesh Gunaratne <im...@apache.org> wrote:
> It seems nearly impossible to rebase changes from docker-grouping-merge
> branch to the master.
>
> The docker-grouping-merge branch is nearly 650 commits ahead of the master
> and the rebase conflicts almost at each commit. We might need to go ahead
> with a merge.
>
> On Sun, Nov 9, 2014 at 10:38 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> It turned out it was an accessibility error. The events are now being
>> received by the agent and health stats are published to CEP. The app path
>> for PHP is not being properly set right now, so I'm looking into it now.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Sun, Nov 9, 2014 at 6:32 PM, Chamila De Alwis <ch...@wso2.com>
>> wrote:
>>
>>>
>>> On Sun, Nov 9, 2014 at 4:46 PM, Lahiru Sandaruwan <la...@wso2.com>
>>> wrote:
>>>
>>>> So this could be the Mqtt issue we saw earlier as well?
>>>
>>>
>>> I'm not sure. It might have been an accessibility issue. I'm in the
>>> process of verifying this now.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
It seems nearly impossible to rebase changes from docker-grouping-merge
branch to the master.
The docker-grouping-merge branch is nearly 650 commits ahead of the master
and the rebase conflicts almost at each commit. We might need to go ahead
with a merge.
On Sun, Nov 9, 2014 at 10:38 PM, Chamila De Alwis <ch...@wso2.com> wrote:
> It turned out it was an accessibility error. The events are now being
> received by the agent and health stats are published to CEP. The app path
> for PHP is not being properly set right now, so I'm looking into it now.
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Sun, Nov 9, 2014 at 6:32 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>>
>> On Sun, Nov 9, 2014 at 4:46 PM, Lahiru Sandaruwan <la...@wso2.com>
>> wrote:
>>
>>> So this could be the Mqtt issue we saw earlier as well?
>>
>>
>> I'm not sure. It might have been an accessibility issue. I'm in the
>> process of verifying this now.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Chamila De Alwis <ch...@wso2.com>.
It turned out it was an accessibility error. The events are now being
received by the agent and health stats are published to CEP. The app path
for PHP is not being properly set right now, so I'm looking into it now.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Sun, Nov 9, 2014 at 6:32 PM, Chamila De Alwis <ch...@wso2.com> wrote:
>
> On Sun, Nov 9, 2014 at 4:46 PM, Lahiru Sandaruwan <la...@wso2.com>
> wrote:
>
>> So this could be the Mqtt issue we saw earlier as well?
>
>
> I'm not sure. It might have been an accessibility issue. I'm in the
> process of verifying this now.
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Chamila De Alwis <ch...@wso2.com>.
On Sun, Nov 9, 2014 at 4:46 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> So this could be the Mqtt issue we saw earlier as well?
I'm not sure. It might have been an accessibility issue. I'm in the process
of verifying this now.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Please try to hold your commits to both docker-grouping-merge and master
branches now.
I'm now merging changes from docker-grouping-merge branch to master.
I did a quick test with rebase and merge, merge worked without a problem
but the rebase failed with conflicts. Will try to resolve conflicts in
rebase approach and push those to remote master to preserve individual
commits.
Thanks
On Sun, Nov 9, 2014 at 5:15 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Will try to do a rebase Nirmal. Lahiru: Yes this could be. Shall we try to
> login to ActiveMQ dashboard and see whether message broker is receiving
> those events?
>
> Thanks
>
> On Sun, Nov 9, 2014 at 4:46 PM, Lahiru Sandaruwan <la...@wso2.com>
> wrote:
>
>>
>>
>> On Sun, Nov 9, 2014 at 4:24 PM, Chamila De Alwis <ch...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Lasindu and I are still trying to get the Python CA working. The puppet
>>> module is operational. But at the moment the CA is not getting the events
>>> published to the MB.
>>>
>>
>> So this could be the Mqtt issue we saw earlier as well?
>>
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>> On Sun, Nov 9, 2014 at 3:30 PM, Lahiru Sandaruwan <la...@wso2.com>
>>> wrote:
>>>
>>>> Shall we merge to the master now?
>>>>
>>>> On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Fixed the serviceId getting NULL by setting it to the ClusterContext
>>>>>> and committed it..
>>>>>>
>>>>>
>>>>> Fine then :)
>>>>>
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Lahiru,
>>>>>>>
>>>>>>> As you have introduced ClusteContext in ClusterMonitor, the
>>>>>>> serviceId got to removed. Is this done purposely? If so, can we update the
>>>>>>> getServiceId() (which referred by several other places) in monitors to
>>>>>>> return the correct serviceId by reading ClusterContext?
>>>>>>>
>>>>>>> Due to this, ClusterMonitor returns serviceId as null and it causes
>>>>>>> issue in the cluster monitor creation and in the event publishing..
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Reka
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <reka@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <
>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <
>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <
>>>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi all,
>>>>>>>>>>>
>>>>>>>>>>> After fixing few issues, i could get the application
>>>>>>>>>>> undeployment working with one cluster now. So the basic undeployment is
>>>>>>>>>>> working fine...Will continue testing with a complex application...
>>>>>>>>>>>
>>>>>>>>>> Great! I will test the same with a complex application.
>>>>>>>>>>
>>>>>>>>> Getting the following exception with a complex app (when sending
>>>>>>>>> cluster activated event), will check and fix asap.
>>>>>>>>> Exception in thread "Thread-61"
>>>>>>>>> java.lang.IllegalMonitorStateException
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>>>>>> at
>>>>>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>>>>>> at
>>>>>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>>>>>> at
>>>>>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>>>>>> at
>>>>>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>
>>>>>>>>
>>>>>>>> I too got this issue as well as a NPE while getting locks..Later
>>>>>>>> found that serviceId was null when getting the locks..I have fixed
>>>>>>>> ServiceId issue..Can you try now and see whether you are still getting this
>>>>>>>> issue?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Reka
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Reka
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <
>>>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>>>>>> currerntly under investigation.
>>>>>>>>>>>>>
>>>>>>>>>>>> Got the same issue, will check in this.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>>>>>> now? WDYT?
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>>>>>> clusters wiped out?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> A good point. May be we need to think little bit here, shall
>>>>>>>>>>>>>>> we first try to convert the required classes and see how good they are?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Isuru H.
>>>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>>>> Mobile: +94776442007
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>
>>>>>>>>>>> Isuru H.
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> +94 716 358 048
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>
>>>>>>>>>>> Isuru H.
>>>>>>>>>>> <%2B94776442007>
>>>>>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Reka Thirunavukkarasu
>>>>>>>> Senior Software Engineer,
>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>> Mobile: +94776442007
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Reka Thirunavukkarasu
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>> Mobile: +94776442007
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> Lahiru Sandaruwan
>>>>> Committer and PMC member, Apache Stratos,
>>>>> Senior Software Engineer,
>>>>> WSO2 Inc., http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Committer and PMC member, Apache Stratos,
>>>> Senior Software Engineer,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Committer and PMC member, Apache Stratos,
>> Senior Software Engineer,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Will try to do a rebase Nirmal. Lahiru: Yes this could be. Shall we try to
login to ActiveMQ dashboard and see whether message broker is receiving
those events?
Thanks
On Sun, Nov 9, 2014 at 4:46 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
>
> On Sun, Nov 9, 2014 at 4:24 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> Hi,
>>
>> Lasindu and I are still trying to get the Python CA working. The puppet
>> module is operational. But at the moment the CA is not getting the events
>> published to the MB.
>>
>
> So this could be the Mqtt issue we saw earlier as well?
>
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Sun, Nov 9, 2014 at 3:30 PM, Lahiru Sandaruwan <la...@wso2.com>
>> wrote:
>>
>>> Shall we merge to the master now?
>>>
>>> On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <la...@wso2.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>> wrote:
>>>>
>>>>> Fixed the serviceId getting NULL by setting it to the ClusterContext
>>>>> and committed it..
>>>>>
>>>>
>>>> Fine then :)
>>>>
>>>>>
>>>>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Lahiru,
>>>>>>
>>>>>> As you have introduced ClusteContext in ClusterMonitor, the serviceId
>>>>>> got to removed. Is this done purposely? If so, can we update the
>>>>>> getServiceId() (which referred by several other places) in monitors to
>>>>>> return the correct serviceId by reading ClusterContext?
>>>>>>
>>>>>> Due to this, ClusterMonitor returns serviceId as null and it causes
>>>>>> issue in the cluster monitor creation and in the event publishing..
>>>>>>
>>>>>> Thanks,
>>>>>> Reka
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>>>> > wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <
>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <
>>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> After fixing few issues, i could get the application undeployment
>>>>>>>>>> working with one cluster now. So the basic undeployment is working
>>>>>>>>>> fine...Will continue testing with a complex application...
>>>>>>>>>>
>>>>>>>>> Great! I will test the same with a complex application.
>>>>>>>>>
>>>>>>>> Getting the following exception with a complex app (when sending
>>>>>>>> cluster activated event), will check and fix asap.
>>>>>>>> Exception in thread "Thread-61"
>>>>>>>> java.lang.IllegalMonitorStateException
>>>>>>>> at
>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>>>>> at
>>>>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>>>>> at
>>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>>>>> at
>>>>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>>>>> at
>>>>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>>>>> at
>>>>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>>>>> at
>>>>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>
>>>>>>>
>>>>>>> I too got this issue as well as a NPE while getting locks..Later
>>>>>>> found that serviceId was null when getting the locks..I have fixed
>>>>>>> ServiceId issue..Can you try now and see whether you are still getting this
>>>>>>> issue?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Reka
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Reka
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <
>>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>>>>> currerntly under investigation.
>>>>>>>>>>>>
>>>>>>>>>>> Got the same issue, will check in this.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>>>>> now? WDYT?
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>>>>> clusters wiped out?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> A good point. May be we need to think little bit here, shall
>>>>>>>>>>>>>> we first try to convert the required classes and see how good they are?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Isuru H.
>>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>>> Mobile: +94776442007
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>
>>>>>>>>>> Isuru H.
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> +94 716 358 048
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>
>>>>>>>>>> Isuru H.
>>>>>>>>>> <%2B94776442007>
>>>>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Reka Thirunavukkarasu
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>> Mobile: +94776442007
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Committer and PMC member, Apache Stratos,
>>>> Senior Software Engineer,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Committer and PMC member, Apache Stratos,
>>> Senior Software Engineer,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Sun, Nov 9, 2014 at 4:24 PM, Chamila De Alwis <ch...@wso2.com> wrote:
> Hi,
>
> Lasindu and I are still trying to get the Python CA working. The puppet
> module is operational. But at the moment the CA is not getting the events
> published to the MB.
>
So this could be the Mqtt issue we saw earlier as well?
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Sun, Nov 9, 2014 at 3:30 PM, Lahiru Sandaruwan <la...@wso2.com>
> wrote:
>
>> Shall we merge to the master now?
>>
>> On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <la...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>> wrote:
>>>
>>>> Fixed the serviceId getting NULL by setting it to the ClusterContext
>>>> and committed it..
>>>>
>>>
>>> Fine then :)
>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Lahiru,
>>>>>
>>>>> As you have introduced ClusteContext in ClusterMonitor, the serviceId
>>>>> got to removed. Is this done purposely? If so, can we update the
>>>>> getServiceId() (which referred by several other places) in monitors to
>>>>> return the correct serviceId by reading ClusterContext?
>>>>>
>>>>> Due to this, ClusterMonitor returns serviceId as null and it causes
>>>>> issue in the cluster monitor creation and in the event publishing..
>>>>>
>>>>> Thanks,
>>>>> Reka
>>>>>
>>>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <is...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>>>> > wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <
>>>>>>>> reka@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> After fixing few issues, i could get the application undeployment
>>>>>>>>> working with one cluster now. So the basic undeployment is working
>>>>>>>>> fine...Will continue testing with a complex application...
>>>>>>>>>
>>>>>>>> Great! I will test the same with a complex application.
>>>>>>>>
>>>>>>> Getting the following exception with a complex app (when sending
>>>>>>> cluster activated event), will check and fix asap.
>>>>>>> Exception in thread "Thread-61"
>>>>>>> java.lang.IllegalMonitorStateException
>>>>>>> at
>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>>>> at
>>>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>>>> at
>>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>>>> at
>>>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>>>> at
>>>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>>>> at
>>>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>>>> at
>>>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>
>>>>>>
>>>>>> I too got this issue as well as a NPE while getting locks..Later
>>>>>> found that serviceId was null when getting the locks..I have fixed
>>>>>> ServiceId issue..Can you try now and see whether you are still getting this
>>>>>> issue?
>>>>>>
>>>>>> Thanks,
>>>>>> Reka
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Reka
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <
>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>>>> currerntly under investigation.
>>>>>>>>>>>
>>>>>>>>>> Got the same issue, will check in this.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>>>> now? WDYT?
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>>>> clusters wiped out?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> A good point. May be we need to think little bit here, shall
>>>>>>>>>>>>> we first try to convert the required classes and see how good they are?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>
>>>>>>>>>>> Isuru H.
>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Reka Thirunavukkarasu
>>>>>>>>> Senior Software Engineer,
>>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>>> Mobile: +94776442007
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> <%2B94776442007>
>>>>>>>>> <%2B94776442007>
>>>>>>>>> Thanks and Regards,
>>>>>>>>>
>>>>>>>>> Isuru H.
>>>>>>>>> <%2B94776442007>
>>>>>>>>> +94 716 358 048
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> <%2B94776442007>
>>>>>>>>> <%2B94776442007>
>>>>>>>>> Thanks and Regards,
>>>>>>>>>
>>>>>>>>> Isuru H.
>>>>>>>>> <%2B94776442007>
>>>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Reka Thirunavukkarasu
>>>> Senior Software Engineer,
>>>> WSO2, Inc.:http://wso2.com,
>>>> Mobile: +94776442007
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Committer and PMC member, Apache Stratos,
>>> Senior Software Engineer,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Committer and PMC member, Apache Stratos,
>> Senior Software Engineer,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Chamila De Alwis <ch...@wso2.com>.
Hi,
Lasindu and I are still trying to get the Python CA working. The puppet
module is operational. But at the moment the CA is not getting the events
published to the MB.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Sun, Nov 9, 2014 at 3:30 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Shall we merge to the master now?
>
> On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <la...@wso2.com>
> wrote:
>
>>
>>
>> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <re...@wso2.com>
>> wrote:
>>
>>> Fixed the serviceId getting NULL by setting it to the ClusterContext and
>>> committed it..
>>>
>>
>> Fine then :)
>>
>>>
>>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>> wrote:
>>>
>>>> Hi Lahiru,
>>>>
>>>> As you have introduced ClusteContext in ClusterMonitor, the serviceId
>>>> got to removed. Is this done purposely? If so, can we update the
>>>> getServiceId() (which referred by several other places) in monitors to
>>>> return the correct serviceId by reading ClusterContext?
>>>>
>>>> Due to this, ClusterMonitor returns serviceId as null and it causes
>>>> issue in the cluster monitor creation and in the event publishing..
>>>>
>>>> Thanks,
>>>> Reka
>>>>
>>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <is...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <reka@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> After fixing few issues, i could get the application undeployment
>>>>>>>> working with one cluster now. So the basic undeployment is working
>>>>>>>> fine...Will continue testing with a complex application...
>>>>>>>>
>>>>>>> Great! I will test the same with a complex application.
>>>>>>>
>>>>>> Getting the following exception with a complex app (when sending
>>>>>> cluster activated event), will check and fix asap.
>>>>>> Exception in thread "Thread-61" java.lang.IllegalMonitorStateException
>>>>>> at
>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>>> at
>>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>>> at
>>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>>> at
>>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>>> at
>>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>>> at
>>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>>> at
>>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>
>>>>>
>>>>> I too got this issue as well as a NPE while getting locks..Later found
>>>>> that serviceId was null when getting the locks..I have fixed ServiceId
>>>>> issue..Can you try now and see whether you are still getting this issue?
>>>>>
>>>>> Thanks,
>>>>> Reka
>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Reka
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <
>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>>> currerntly under investigation.
>>>>>>>>>>
>>>>>>>>> Got the same issue, will check in this.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>>> now? WDYT?
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi all,
>>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>>> clusters wiped out?
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> A good point. May be we need to think little bit here, shall we
>>>>>>>>>>>> first try to convert the required classes and see how good they are?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>
>>>>>>>>>> Isuru H.
>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Reka Thirunavukkarasu
>>>>>>>> Senior Software Engineer,
>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>> Mobile: +94776442007
>>>>>>>>
>>>>>>>> --
>>>>>>>> <%2B94776442007>
>>>>>>>> <%2B94776442007>
>>>>>>>> Thanks and Regards,
>>>>>>>>
>>>>>>>> Isuru H.
>>>>>>>> <%2B94776442007>
>>>>>>>> +94 716 358 048
>>>>>>>>
>>>>>>>> --
>>>>>>>> <%2B94776442007>
>>>>>>>> <%2B94776442007>
>>>>>>>> Thanks and Regards,
>>>>>>>>
>>>>>>>> Isuru H.
>>>>>>>> <%2B94776442007>
>>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>> * <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Reka Thirunavukkarasu
>>>> Senior Software Engineer,
>>>> WSO2, Inc.:http://wso2.com,
>>>> Mobile: +94776442007
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Committer and PMC member, Apache Stratos,
>> Senior Software Engineer,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lahiru Sandaruwan <la...@wso2.com>.
Shall we merge to the master now?
On Sun, Nov 9, 2014 at 3:04 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
>
> On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
>> Fixed the serviceId getting NULL by setting it to the ClusterContext and
>> committed it..
>>
>
> Fine then :)
>
>>
>> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com>
>> wrote:
>>
>>> Hi Lahiru,
>>>
>>> As you have introduced ClusteContext in ClusterMonitor, the serviceId
>>> got to removed. Is this done purposely? If so, can we update the
>>> getServiceId() (which referred by several other places) in monitors to
>>> return the correct serviceId by reading ClusterContext?
>>>
>>> Due to this, ClusterMonitor returns serviceId as null and it causes
>>> issue in the cluster monitor creation and in the event publishing..
>>>
>>> Thanks,
>>> Reka
>>>
>>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <is...@apache.org>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> After fixing few issues, i could get the application undeployment
>>>>>>> working with one cluster now. So the basic undeployment is working
>>>>>>> fine...Will continue testing with a complex application...
>>>>>>>
>>>>>> Great! I will test the same with a complex application.
>>>>>>
>>>>> Getting the following exception with a complex app (when sending
>>>>> cluster activated event), will check and fix asap.
>>>>> Exception in thread "Thread-61" java.lang.IllegalMonitorStateException
>>>>> at
>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>>> at
>>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>>> at
>>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>>> at
>>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>>> at
>>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>>> at
>>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>>> at
>>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>
>>>>
>>>> I too got this issue as well as a NPE while getting locks..Later found
>>>> that serviceId was null when getting the locks..I have fixed ServiceId
>>>> issue..Can you try now and see whether you are still getting this issue?
>>>>
>>>> Thanks,
>>>> Reka
>>>>
>>>>>
>>>>>
>>>>>>
>>>>>>> Thanks,
>>>>>>> Reka
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>>>> > wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>>> currerntly under investigation.
>>>>>>>>>
>>>>>>>> Got the same issue, will check in this.
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Since the basic workflow of service grouping and docker are
>>>>>>>>> working now shall we merge docker-grouping-merge branch to master branch
>>>>>>>>> now? WDYT?
>>>>>>>>>
>>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>>> clusters wiped out?
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> A good point. May be we need to think little bit here, shall we
>>>>>>>>>>> first try to convert the required classes and see how good they are?
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks and Regards,
>>>>>>>>>
>>>>>>>>> Isuru H.
>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Reka Thirunavukkarasu
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>> Mobile: +94776442007
>>>>>>>
>>>>>>> --
>>>>>>> <%2B94776442007>
>>>>>>> <%2B94776442007>
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> <%2B94776442007>
>>>>>>> +94 716 358 048
>>>>>>>
>>>>>>> --
>>>>>>> <%2B94776442007>
>>>>>>> <%2B94776442007>
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> <%2B94776442007>
>>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>> * <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>>
>>>> --
>>>> Reka Thirunavukkarasu
>>>> Senior Software Engineer,
>>>> WSO2, Inc.:http://wso2.com,
>>>> Mobile: +94776442007
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Sun, Nov 9, 2014 at 3:02 PM, Reka Thirunavukkarasu <re...@wso2.com> wrote:
> Fixed the serviceId getting NULL by setting it to the ClusterContext and
> committed it..
>
Fine then :)
>
> On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
>> Hi Lahiru,
>>
>> As you have introduced ClusteContext in ClusterMonitor, the serviceId got
>> to removed. Is this done purposely? If so, can we update the getServiceId()
>> (which referred by several other places) in monitors to return the correct
>> serviceId by reading ClusterContext?
>>
>> Due to this, ClusterMonitor returns serviceId as null and it causes issue
>> in the cluster monitor creation and in the event publishing..
>>
>> Thanks,
>> Reka
>>
>> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <re...@wso2.com>
>> wrote:
>>
>>> Hi
>>>
>>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <is...@apache.org>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> After fixing few issues, i could get the application undeployment
>>>>>> working with one cluster now. So the basic undeployment is working
>>>>>> fine...Will continue testing with a complex application...
>>>>>>
>>>>> Great! I will test the same with a complex application.
>>>>>
>>>> Getting the following exception with a complex app (when sending
>>>> cluster activated event), will check and fix asap.
>>>> Exception in thread "Thread-61" java.lang.IllegalMonitorStateException
>>>> at
>>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>>> at
>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>>> at
>>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>>> at
>>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>>> at
>>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>>> at
>>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>>> at
>>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>>> at java.lang.Thread.run(Thread.java:662)
>>>>
>>>
>>> I too got this issue as well as a NPE while getting locks..Later found
>>> that serviceId was null when getting the locks..I have fixed ServiceId
>>> issue..Can you try now and see whether you are still getting this issue?
>>>
>>> Thanks,
>>> Reka
>>>
>>>>
>>>>
>>>>>
>>>>>> Thanks,
>>>>>> Reka
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <is...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> No, there seems to be a problem with application un-deploy
>>>>>>>> function. For me the un-deploy call hangs in the autoscaler. This is
>>>>>>>> currerntly under investigation.
>>>>>>>>
>>>>>>> Got the same issue, will check in this.
>>>>>>>
>>>>>>>>
>>>>>>>> Since the basic workflow of service grouping and docker are working
>>>>>>>> now shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>>>>>>>
>>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>> Did anyone undeploy the application successfully? Were all
>>>>>>>>> clusters wiped out?
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Don't we also need the event processing chain since it
>>>>>>>>>>> constructs the event objects from the Jsons? Additionally this is done
>>>>>>>>>>> through the Gson library, so we would have some difficulty in getting that
>>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> A good point. May be we need to think little bit here, shall we
>>>>>>>>>> first try to convert the required classes and see how good they are?
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks and Regards,
>>>>>>>>
>>>>>>>> Isuru H.
>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>> * <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>> --
>>>>>> <%2B94776442007>
>>>>>> <%2B94776442007>
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> <%2B94776442007>
>>>>>> +94 716 358 048
>>>>>>
>>>>>> --
>>>>>> <%2B94776442007>
>>>>>> <%2B94776442007>
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> <%2B94776442007>
>>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>> * <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Fixed the serviceId getting NULL by setting it to the ClusterContext and
committed it..
On Sun, Nov 9, 2014 at 2:51 PM, Reka Thirunavukkarasu <re...@wso2.com> wrote:
> Hi Lahiru,
>
> As you have introduced ClusteContext in ClusterMonitor, the serviceId got
> to removed. Is this done purposely? If so, can we update the getServiceId()
> (which referred by several other places) in monitors to return the correct
> serviceId by reading ClusterContext?
>
> Due to this, ClusterMonitor returns serviceId as null and it causes issue
> in the cluster monitor creation and in the event publishing..
>
> Thanks,
> Reka
>
> On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
>> Hi
>>
>> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>>
>>>
>>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> After fixing few issues, i could get the application undeployment
>>>>> working with one cluster now. So the basic undeployment is working
>>>>> fine...Will continue testing with a complex application...
>>>>>
>>>> Great! I will test the same with a complex application.
>>>>
>>> Getting the following exception with a complex app (when sending cluster
>>> activated event), will check and fix asap.
>>> Exception in thread "Thread-61" java.lang.IllegalMonitorStateException
>>> at
>>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>>> at
>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>>> at
>>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>>> at
>>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>>> at
>>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>>> at
>>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>>> at
>>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>>> at java.lang.Thread.run(Thread.java:662)
>>>
>>
>> I too got this issue as well as a NPE while getting locks..Later found
>> that serviceId was null when getting the locks..I have fixed ServiceId
>> issue..Can you try now and see whether you are still getting this issue?
>>
>> Thanks,
>> Reka
>>
>>>
>>>
>>>>
>>>>> Thanks,
>>>>> Reka
>>>>>
>>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> No, there seems to be a problem with application un-deploy function.
>>>>>>> For me the un-deploy call hangs in the autoscaler. This is currerntly under
>>>>>>> investigation.
>>>>>>>
>>>>>> Got the same issue, will check in this.
>>>>>>
>>>>>>>
>>>>>>> Since the basic workflow of service grouping and docker are working
>>>>>>> now shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>>>>>>
>>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>>> rraju1990@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>> Did anyone undeploy the application successfully? Were all clusters
>>>>>>>> wiped out?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Don't we also need the event processing chain since it constructs
>>>>>>>>>> the event objects from the Jsons? Additionally this is done through the
>>>>>>>>>> Gson library, so we would have some difficulty in getting that
>>>>>>>>>> functionality in to python as well.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> A good point. May be we need to think little bit here, shall we
>>>>>>>>> first try to convert the required classes and see how good they are?
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>> --
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>> * <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>> --
>>>>> <%2B94776442007>
>>>>> <%2B94776442007>
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> <%2B94776442007>
>>>>> +94 716 358 048
>>>>>
>>>>> --
>>>>> <%2B94776442007>
>>>>> <%2B94776442007>
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> <%2B94776442007>
>>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>>
>>>>>
>>>>> * <http://wso2.com/>*
>>>>>
>>>>>
>>>>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi Lahiru,
As you have introduced ClusteContext in ClusterMonitor, the serviceId got
to removed. Is this done purposely? If so, can we update the getServiceId()
(which referred by several other places) in monitors to return the correct
serviceId by reading ClusterContext?
Due to this, ClusterMonitor returns serviceId as null and it causes issue
in the cluster monitor creation and in the event publishing..
Thanks,
Reka
On Sun, Nov 9, 2014 at 2:39 PM, Reka Thirunavukkarasu <re...@wso2.com> wrote:
> Hi
>
> On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>>
>>
>> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>>
>>>
>>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> After fixing few issues, i could get the application undeployment
>>>> working with one cluster now. So the basic undeployment is working
>>>> fine...Will continue testing with a complex application...
>>>>
>>> Great! I will test the same with a complex application.
>>>
>> Getting the following exception with a complex app (when sending cluster
>> activated event), will check and fix asap.
>> Exception in thread "Thread-61" java.lang.IllegalMonitorStateException
>> at
>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
>> at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
>> at
>> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
>> at
>> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
>> at
>> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
>> at
>> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
>> at
>> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
>> at java.lang.Thread.run(Thread.java:662)
>>
>
> I too got this issue as well as a NPE while getting locks..Later found
> that serviceId was null when getting the locks..I have fixed ServiceId
> issue..Can you try now and see whether you are still getting this issue?
>
> Thanks,
> Reka
>
>>
>>
>>>
>>>> Thanks,
>>>> Reka
>>>>
>>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <is...@apache.org>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> No, there seems to be a problem with application un-deploy function.
>>>>>> For me the un-deploy call hangs in the autoscaler. This is currerntly under
>>>>>> investigation.
>>>>>>
>>>>> Got the same issue, will check in this.
>>>>>
>>>>>>
>>>>>> Since the basic workflow of service grouping and docker are working
>>>>>> now shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>> rraju1990@gmail.com> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>> Did anyone undeploy the application successfully? Were all clusters
>>>>>>> wiped out?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Don't we also need the event processing chain since it constructs
>>>>>>>>> the event objects from the Jsons? Additionally this is done through the
>>>>>>>>> Gson library, so we would have some difficulty in getting that
>>>>>>>>> functionality in to python as well.
>>>>>>>>>
>>>>>>>>
>>>>>>>> A good point. May be we need to think little bit here, shall we
>>>>>>>> first try to convert the required classes and see how good they are?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>> --
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>> * <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>> --
>>>> Reka Thirunavukkarasu
>>>> Senior Software Engineer,
>>>> WSO2, Inc.:http://wso2.com,
>>>> Mobile: +94776442007
>>>>
>>>> --
>>>> <%2B94776442007>
>>>> <%2B94776442007>
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> <%2B94776442007>
>>>> +94 716 358 048
>>>>
>>>> --
>>>> <%2B94776442007>
>>>> <%2B94776442007>
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> <%2B94776442007>
>>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>>
>>>>
>>>> * <http://wso2.com/>*
>>>>
>>>>
>>>>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi
On Sun, Nov 9, 2014 at 2:19 PM, Isuru Haththotuwa <is...@apache.org> wrote:
>
>
> On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>>
>>
>> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <re...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> After fixing few issues, i could get the application undeployment
>>> working with one cluster now. So the basic undeployment is working
>>> fine...Will continue testing with a complex application...
>>>
>> Great! I will test the same with a complex application.
>>
> Getting the following exception with a complex app (when sending cluster
> activated event), will check and fix asap.
> Exception in thread "Thread-61" java.lang.IllegalMonitorStateException
> at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
> at
> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
> at
> org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
> at
> org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
> at
> org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
> at
> org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
> at java.lang.Thread.run(Thread.java:662)
>
I too got this issue as well as a NPE while getting locks..Later found that
serviceId was null when getting the locks..I have fixed ServiceId
issue..Can you try now and see whether you are still getting this issue?
Thanks,
Reka
>
>
>>
>>> Thanks,
>>> Reka
>>>
>>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> No, there seems to be a problem with application un-deploy function.
>>>>> For me the un-deploy call hangs in the autoscaler. This is currerntly under
>>>>> investigation.
>>>>>
>>>> Got the same issue, will check in this.
>>>>
>>>>>
>>>>> Since the basic workflow of service grouping and docker are working
>>>>> now shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>>>>
>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>> rraju1990@gmail.com> wrote:
>>>>>
>>>>>> Hi all,
>>>>>> Did anyone undeploy the application successfully? Were all clusters
>>>>>> wiped out?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <chamilad@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Don't we also need the event processing chain since it constructs
>>>>>>>> the event objects from the Jsons? Additionally this is done through the
>>>>>>>> Gson library, so we would have some difficulty in getting that
>>>>>>>> functionality in to python as well.
>>>>>>>>
>>>>>>>
>>>>>>> A good point. May be we need to think little bit here, shall we
>>>>>>> first try to convert the required classes and see how good they are?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>> --
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>
>>>>>
>>>>> * <http://wso2.com/>*
>>>>>
>>>>>
>>>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>> --
>>> <%2B94776442007>
>>> <%2B94776442007>
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> <%2B94776442007>
>>> +94 716 358 048
>>>
>>> --
>>> <%2B94776442007>
>>> <%2B94776442007>
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> <%2B94776442007>
>>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>>
>>>
>>> * <http://wso2.com/>*
>>>
>>>
>>>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
On Sun, Nov 9, 2014 at 1:13 PM, Isuru Haththotuwa <is...@apache.org> wrote:
>
>
> On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> After fixing few issues, i could get the application undeployment working
>> with one cluster now. So the basic undeployment is working fine...Will
>> continue testing with a complex application...
>>
> Great! I will test the same with a complex application.
>
Getting the following exception with a complex app (when sending cluster
activated event), will check and fix asap.
Exception in thread "Thread-61" java.lang.IllegalMonitorStateException
at
java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:363)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1317)
at
java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:745)
at
org.apache.stratos.messaging.domain.topology.locking.TopologyLock.releaseReadLock(TopologyLock.java:61)
at
org.apache.stratos.messaging.message.receiver.topology.TopologyManager.releaseReadLockForCluster(TopologyManager.java:196)
at
org.apache.stratos.autoscaler.event.publisher.ClusterStatusEventPublisher.sendClusterActivatedEvent(ClusterStatusEventPublisher.java:109)
at
org.apache.stratos.autoscaler.status.checker.StatusChecker$1.run(StatusChecker.java:77)
at java.lang.Thread.run(Thread.java:662)
>
>> Thanks,
>> Reka
>>
>> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>>
>>>
>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> No, there seems to be a problem with application un-deploy function.
>>>> For me the un-deploy call hangs in the autoscaler. This is currerntly under
>>>> investigation.
>>>>
>>> Got the same issue, will check in this.
>>>
>>>>
>>>> Since the basic workflow of service grouping and docker are working now
>>>> shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>>>
>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>> rraju1990@gmail.com> wrote:
>>>>
>>>>> Hi all,
>>>>> Did anyone undeploy the application successfully? Were all clusters
>>>>> wiped out?
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <ch...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>> Don't we also need the event processing chain since it constructs
>>>>>>> the event objects from the Jsons? Additionally this is done through the
>>>>>>> Gson library, so we would have some difficulty in getting that
>>>>>>> functionality in to python as well.
>>>>>>>
>>>>>>
>>>>>> A good point. May be we need to think little bit here, shall we first
>>>>>> try to convert the required classes and see how good they are?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> +94 716 358 048* <http://wso2.com/>*
>>>>
>>>>
>>>> * <http://wso2.com/>*
>>>>
>>>>
>>>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>> --
>> <%2B94776442007>
>> <%2B94776442007>
>> Thanks and Regards,
>>
>> Isuru H.
>> <%2B94776442007>
>> +94 716 358 048
>>
>> --
>> <%2B94776442007>
>> <%2B94776442007>
>> Thanks and Regards,
>>
>> Isuru H.
>> <%2B94776442007>
>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
On Sun, Nov 9, 2014 at 1:09 PM, Reka Thirunavukkarasu <re...@wso2.com> wrote:
> Hi all,
>
> After fixing few issues, i could get the application undeployment working
> with one cluster now. So the basic undeployment is working fine...Will
> continue testing with a complex application...
>
Great! I will test the same with a complex application.
>
> Thanks,
> Reka
>
> On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>>
>>
>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> No, there seems to be a problem with application un-deploy function. For
>>> me the un-deploy call hangs in the autoscaler. This is currerntly under
>>> investigation.
>>>
>> Got the same issue, will check in this.
>>
>>>
>>> Since the basic workflow of service grouping and docker are working now
>>> shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>>
>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <rraju1990@gmail.com
>>> > wrote:
>>>
>>>> Hi all,
>>>> Did anyone undeploy the application successfully? Were all clusters
>>>> wiped out?
>>>>
>>>> Thanks
>>>>
>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <ch...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> Don't we also need the event processing chain since it constructs the
>>>>>> event objects from the Jsons? Additionally this is done through the Gson
>>>>>> library, so we would have some difficulty in getting that functionality in
>>>>>> to python as well.
>>>>>>
>>>>>
>>>>> A good point. May be we need to think little bit here, shall we first
>>>>> try to convert the required classes and see how good they are?
>>>>>
>>>>> Thanks
>>>>>
>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* <http://wso2.com/>*
>>>
>>>
>>> * <http://wso2.com/>*
>>>
>>>
>>>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
> --
> <%2B94776442007>
> <%2B94776442007>
> Thanks and Regards,
>
> Isuru H.
> <%2B94776442007>
> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi all,
After fixing few issues, i could get the application undeployment working
with one cluster now. So the basic undeployment is working fine...Will
continue testing with a complex application...
Thanks,
Reka
On Sun, Nov 9, 2014 at 1:05 PM, Isuru Haththotuwa <is...@apache.org> wrote:
>
>
> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> No, there seems to be a problem with application un-deploy function. For
>> me the un-deploy call hangs in the autoscaler. This is currerntly under
>> investigation.
>>
> Got the same issue, will check in this.
>
>>
>> Since the basic workflow of service grouping and docker are working now
>> shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>
>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <rr...@gmail.com>
>> wrote:
>>
>>> Hi all,
>>> Did anyone undeploy the application successfully? Were all clusters
>>> wiped out?
>>>
>>> Thanks
>>>
>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org> wrote:
>>>
>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <ch...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>> Don't we also need the event processing chain since it constructs the
>>>>> event objects from the Jsons? Additionally this is done through the Gson
>>>>> library, so we would have some difficulty in getting that functionality in
>>>>> to python as well.
>>>>>
>>>>
>>>> A good point. May be we need to think little bit here, shall we first
>>>> try to convert the required classes and see how good they are?
>>>>
>>>> Thanks
>>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org> wrote:
> No, there seems to be a problem with application un-deploy function. For
> me the un-deploy call hangs in the autoscaler. This is currerntly under
> investigation.
>
Got the same issue, will check in this.
>
> Since the basic workflow of service grouping and docker are working now
> shall we merge docker-grouping-merge branch to master branch now? WDYT?
>
> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <rr...@gmail.com>
> wrote:
>
>> Hi all,
>> Did anyone undeploy the application successfully? Were all clusters wiped
>> out?
>>
>> Thanks
>>
>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <ch...@wso2.com>
>>> wrote:
>>>
>>>>
>>>> Don't we also need the event processing chain since it constructs the
>>>> event objects from the Jsons? Additionally this is done through the Gson
>>>> library, so we would have some difficulty in getting that functionality in
>>>> to python as well.
>>>>
>>>
>>> A good point. May be we need to think little bit here, shall we first
>>> try to convert the required classes and see how good they are?
>>>
>>> Thanks
>>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Hi Imesh,
- Couldn't access the service via LB. LB routes requests to port 80
instead of service proxy port. Looking into it currently.
- Manual scaling is not working
But I guess we can merge to master and fix these there. These are minor
issues.
Thanks.
On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org> wrote:
> No, there seems to be a problem with application un-deploy function. For
> me the un-deploy call hangs in the autoscaler. This is currerntly under
> investigation.
>
> Since the basic workflow of service grouping and docker are working now
> shall we merge docker-grouping-merge branch to master branch now? WDYT?
>
> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <rr...@gmail.com>
> wrote:
>
>> Hi all,
>> Did anyone undeploy the application successfully? Were all clusters wiped
>> out?
>>
>> Thanks
>>
>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <ch...@wso2.com>
>>> wrote:
>>>
>>>>
>>>> Don't we also need the event processing chain since it constructs the
>>>> event objects from the Jsons? Additionally this is done through the Gson
>>>> library, so we would have some difficulty in getting that functionality in
>>>> to python as well.
>>>>
>>>
>>> A good point. May be we need to think little bit here, shall we first
>>> try to convert the required classes and see how good they are?
>>>
>>> Thanks
>>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
I too fixed few application undeployment issues..Will hold the commit now
onwards..
On Sun, Nov 9, 2014 at 12:46 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
>
> On Sun, Nov 9, 2014 at 12:38 PM, Manula Chathurika Thantriwatte <
> manulac@wso2.com> wrote:
>
>> Hi Lahiru,
>>
>> Sure, please let us know when you finish it.
>>
> Done just now.
>
>>
>>
>>
>> On Sun, Nov 9, 2014 at 12:17 PM, Lahiru Sandaruwan <la...@wso2.com>
>> wrote:
>>
>>> Can you guys hold until i push cluster context change. Will do it asap.
>>>
>>> On Sun, Nov 9, 2014 at 12:13 PM, Manula Chathurika Thantriwatte <
>>> manulac@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> +1, then shall we merge docker-grouping-merge branch to master branch
>>>> and continue testing on it.
>>>>
>>>> Thanks !
>>>>
>>>> On Sun, Nov 9, 2014 at 12:05 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Imesh,
>>>>>
>>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> No, there seems to be a problem with application un-deploy function.
>>>>>> For me the un-deploy call hangs in the autoscaler. This is currerntly under
>>>>>> investigation.
>>>>>>
>>>>>> Since the basic workflow of service grouping and docker are working
>>>>>> now shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>>>>>
>>>>> +1. We can continue from master, since basic things are working..
>>>>>
>>>>> Thanks,
>>>>> Reka
>>>>>
>>>>>>
>>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>>> rraju1990@gmail.com> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>> Did anyone undeploy the application successfully? Were all clusters
>>>>>>> wiped out?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <
>>>>>>>> chamilad@wso2.com> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Don't we also need the event processing chain since it constructs
>>>>>>>>> the event objects from the Jsons? Additionally this is done through the
>>>>>>>>> Gson library, so we would have some difficulty in getting that
>>>>>>>>> functionality in to python as well.
>>>>>>>>>
>>>>>>>>
>>>>>>>> A good point. May be we need to think little bit here, shall we
>>>>>>>> first try to convert the required classes and see how good they are?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Manula Chathurika Thantriwatte
>>>> Software Engineer
>>>> WSO2 Inc. : http://wso2.com
>>>> lean . enterprise . middleware
>>>>
>>>> email : manulac@wso2.com / manula@apache.org
>>>> phone : +94 772492511
>>>> blog : http://manulachathurika.blogspot.com/
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Committer and PMC member, Apache Stratos,
>>> Senior Software Engineer,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> Regards,
>> Manula Chathurika Thantriwatte
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>> lean . enterprise . middleware
>>
>> email : manulac@wso2.com / manula@apache.org
>> phone : +94 772492511
>> blog : http://manulachathurika.blogspot.com/
>>
>>
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Sun, Nov 9, 2014 at 12:38 PM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi Lahiru,
>
> Sure, please let us know when you finish it.
>
Done just now.
>
>
>
> On Sun, Nov 9, 2014 at 12:17 PM, Lahiru Sandaruwan <la...@wso2.com>
> wrote:
>
>> Can you guys hold until i push cluster context change. Will do it asap.
>>
>> On Sun, Nov 9, 2014 at 12:13 PM, Manula Chathurika Thantriwatte <
>> manulac@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> +1, then shall we merge docker-grouping-merge branch to master branch
>>> and continue testing on it.
>>>
>>> Thanks !
>>>
>>> On Sun, Nov 9, 2014 at 12:05 PM, Reka Thirunavukkarasu <re...@wso2.com>
>>> wrote:
>>>
>>>> Hi Imesh,
>>>>
>>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> No, there seems to be a problem with application un-deploy function.
>>>>> For me the un-deploy call hangs in the autoscaler. This is currerntly under
>>>>> investigation.
>>>>>
>>>>> Since the basic workflow of service grouping and docker are working
>>>>> now shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>>>>
>>>> +1. We can continue from master, since basic things are working..
>>>>
>>>> Thanks,
>>>> Reka
>>>>
>>>>>
>>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>>> rraju1990@gmail.com> wrote:
>>>>>
>>>>>> Hi all,
>>>>>> Did anyone undeploy the application successfully? Were all clusters
>>>>>> wiped out?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <chamilad@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Don't we also need the event processing chain since it constructs
>>>>>>>> the event objects from the Jsons? Additionally this is done through the
>>>>>>>> Gson library, so we would have some difficulty in getting that
>>>>>>>> functionality in to python as well.
>>>>>>>>
>>>>>>>
>>>>>>> A good point. May be we need to think little bit here, shall we
>>>>>>> first try to convert the required classes and see how good they are?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Reka Thirunavukkarasu
>>>> Senior Software Engineer,
>>>> WSO2, Inc.:http://wso2.com,
>>>> Mobile: +94776442007
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Regards,
>>> Manula Chathurika Thantriwatte
>>> Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> email : manulac@wso2.com / manula@apache.org
>>> phone : +94 772492511
>>> blog : http://manulachathurika.blogspot.com/
>>>
>>>
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Committer and PMC member, Apache Stratos,
>> Senior Software Engineer,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> email : manulac@wso2.com / manula@apache.org
> phone : +94 772492511
> blog : http://manulachathurika.blogspot.com/
>
>
>
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi Lahiru,
Sure, please let us know when you finish it.
On Sun, Nov 9, 2014 at 12:17 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Can you guys hold until i push cluster context change. Will do it asap.
>
> On Sun, Nov 9, 2014 at 12:13 PM, Manula Chathurika Thantriwatte <
> manulac@wso2.com> wrote:
>
>> Hi,
>>
>> +1, then shall we merge docker-grouping-merge branch to master branch and
>> continue testing on it.
>>
>> Thanks !
>>
>> On Sun, Nov 9, 2014 at 12:05 PM, Reka Thirunavukkarasu <re...@wso2.com>
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> No, there seems to be a problem with application un-deploy function.
>>>> For me the un-deploy call hangs in the autoscaler. This is currerntly under
>>>> investigation.
>>>>
>>>> Since the basic workflow of service grouping and docker are working now
>>>> shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>>>
>>> +1. We can continue from master, since basic things are working..
>>>
>>> Thanks,
>>> Reka
>>>
>>>>
>>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <
>>>> rraju1990@gmail.com> wrote:
>>>>
>>>>> Hi all,
>>>>> Did anyone undeploy the application successfully? Were all clusters
>>>>> wiped out?
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <ch...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>> Don't we also need the event processing chain since it constructs
>>>>>>> the event objects from the Jsons? Additionally this is done through the
>>>>>>> Gson library, so we would have some difficulty in getting that
>>>>>>> functionality in to python as well.
>>>>>>>
>>>>>>
>>>>>> A good point. May be we need to think little bit here, shall we first
>>>>>> try to convert the required classes and see how good they are?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Regards,
>> Manula Chathurika Thantriwatte
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>> lean . enterprise . middleware
>>
>> email : manulac@wso2.com / manula@apache.org
>> phone : +94 772492511
>> blog : http://manulachathurika.blogspot.com/
>>
>>
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware
email : manulac@wso2.com / manula@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lahiru Sandaruwan <la...@wso2.com>.
Can you guys hold until i push cluster context change. Will do it asap.
On Sun, Nov 9, 2014 at 12:13 PM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi,
>
> +1, then shall we merge docker-grouping-merge branch to master branch and
> continue testing on it.
>
> Thanks !
>
> On Sun, Nov 9, 2014 at 12:05 PM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
>> Hi Imesh,
>>
>> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> No, there seems to be a problem with application un-deploy function. For
>>> me the un-deploy call hangs in the autoscaler. This is currerntly under
>>> investigation.
>>>
>>> Since the basic workflow of service grouping and docker are working now
>>> shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>>
>> +1. We can continue from master, since basic things are working..
>>
>> Thanks,
>> Reka
>>
>>>
>>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <rraju1990@gmail.com
>>> > wrote:
>>>
>>>> Hi all,
>>>> Did anyone undeploy the application successfully? Were all clusters
>>>> wiped out?
>>>>
>>>> Thanks
>>>>
>>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <ch...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> Don't we also need the event processing chain since it constructs the
>>>>>> event objects from the Jsons? Additionally this is done through the Gson
>>>>>> library, so we would have some difficulty in getting that functionality in
>>>>>> to python as well.
>>>>>>
>>>>>
>>>>> A good point. May be we need to think little bit here, shall we first
>>>>> try to convert the required classes and see how good they are?
>>>>>
>>>>> Thanks
>>>>>
>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> email : manulac@wso2.com / manula@apache.org
> phone : +94 772492511
> blog : http://manulachathurika.blogspot.com/
>
>
>
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi,
+1, then shall we merge docker-grouping-merge branch to master branch and
continue testing on it.
Thanks !
On Sun, Nov 9, 2014 at 12:05 PM, Reka Thirunavukkarasu <re...@wso2.com>
wrote:
> Hi Imesh,
>
> On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> No, there seems to be a problem with application un-deploy function. For
>> me the un-deploy call hangs in the autoscaler. This is currerntly under
>> investigation.
>>
>> Since the basic workflow of service grouping and docker are working now
>> shall we merge docker-grouping-merge branch to master branch now? WDYT?
>>
> +1. We can continue from master, since basic things are working..
>
> Thanks,
> Reka
>
>>
>> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <rr...@gmail.com>
>> wrote:
>>
>>> Hi all,
>>> Did anyone undeploy the application successfully? Were all clusters
>>> wiped out?
>>>
>>> Thanks
>>>
>>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org> wrote:
>>>
>>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <ch...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>> Don't we also need the event processing chain since it constructs the
>>>>> event objects from the Jsons? Additionally this is done through the Gson
>>>>> library, so we would have some difficulty in getting that functionality in
>>>>> to python as well.
>>>>>
>>>>
>>>> A good point. May be we need to think little bit here, shall we first
>>>> try to convert the required classes and see how good they are?
>>>>
>>>> Thanks
>>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware
email : manulac@wso2.com / manula@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi Imesh,
On Sun, Nov 9, 2014 at 8:38 AM, Imesh Gunaratne <im...@apache.org> wrote:
> No, there seems to be a problem with application un-deploy function. For
> me the un-deploy call hangs in the autoscaler. This is currerntly under
> investigation.
>
> Since the basic workflow of service grouping and docker are working now
> shall we merge docker-grouping-merge branch to master branch now? WDYT?
>
+1. We can continue from master, since basic things are working..
Thanks,
Reka
>
> On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <rr...@gmail.com>
> wrote:
>
>> Hi all,
>> Did anyone undeploy the application successfully? Were all clusters wiped
>> out?
>>
>> Thanks
>>
>> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <ch...@wso2.com>
>>> wrote:
>>>
>>>>
>>>> Don't we also need the event processing chain since it constructs the
>>>> event objects from the Jsons? Additionally this is done through the Gson
>>>> library, so we would have some difficulty in getting that functionality in
>>>> to python as well.
>>>>
>>>
>>> A good point. May be we need to think little bit here, shall we first
>>> try to convert the required classes and see how good they are?
>>>
>>> Thanks
>>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
No, there seems to be a problem with application un-deploy function. For me
the un-deploy call hangs in the autoscaler. This is currerntly under
investigation.
Since the basic workflow of service grouping and docker are working now
shall we merge docker-grouping-merge branch to master branch now? WDYT?
On Sun, Nov 9, 2014 at 4:13 AM, Rajaratnam Rajkumar <rr...@gmail.com>
wrote:
> Hi all,
> Did anyone undeploy the application successfully? Were all clusters wiped
> out?
>
> Thanks
>
> On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org> wrote:
>
>> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <ch...@wso2.com>
>> wrote:
>>
>>>
>>> Don't we also need the event processing chain since it constructs the
>>> event objects from the Jsons? Additionally this is done through the Gson
>>> library, so we would have some difficulty in getting that functionality in
>>> to python as well.
>>>
>>
>> A good point. May be we need to think little bit here, shall we first try
>> to convert the required classes and see how good they are?
>>
>> Thanks
>>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajaratnam Rajkumar <rr...@gmail.com>.
Hi all,
Did anyone undeploy the application successfully? Were all clusters wiped
out?
Thanks
On Saturday, November 8, 2014, Imesh Gunaratne <im...@apache.org> wrote:
> On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <chamilad@wso2.com
> <javascript:_e(%7B%7D,'cvml','chamilad@wso2.com');>> wrote:
>
>>
>> Don't we also need the event processing chain since it constructs the
>> event objects from the Jsons? Additionally this is done through the Gson
>> library, so we would have some difficulty in getting that functionality in
>> to python as well.
>>
>
> A good point. May be we need to think little bit here, shall we first try
> to convert the required classes and see how good they are?
>
> Thanks
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
On Sat, Nov 8, 2014 at 11:13 PM, Chamila De Alwis <ch...@wso2.com> wrote:
>
> Don't we also need the event processing chain since it constructs the
> event objects from the Jsons? Additionally this is done through the Gson
> library, so we would have some difficulty in getting that functionality in
> to python as well.
>
A good point. May be we need to think little bit here, shall we first try
to convert the required classes and see how good they are?
Thanks
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Chamila De Alwis <ch...@wso2.com>.
Hi Imesh,
On Sat, Nov 8, 2014 at 7:44 PM, Imesh Gunaratne <im...@apache.org> wrote:
> My understanding is that we only need the domain classes converted to
> python. They may only contain list of properties. Therefore the generated
> code should be simple enough to validate.
Don't we also need the event processing chain since it constructs the event
objects from the Jsons? Additionally this is done through the Gson library,
so we would have some difficulty in getting that functionality in to python
as well.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lahiru Sandaruwan <la...@wso2.com>.
I'm on scaling based on dependency ratio. We need a place to keep runtime
information of cluster, which should be also persisted. So it should be the
same place where we keep updated autoscale/deployment policies at
runtime. (manual
scaling)
I'll send mails and get the community idea as well. Im focusing part by
part.
Thanks.
On Sat, Nov 8, 2014 at 10:46 PM, Reka Thirunavukkarasu <re...@wso2.com>
wrote:
> Hi
>
> I could bring an application with more than one cluster as Active.
> Currently testing the faulty member scenario for VM with the Composite
> application and fixing issues. Will update on that..
>
>
> Thanks,
> Reka
>
> On Sat, Nov 8, 2014 at 10:39 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I have now done the following changes:
>> - Added get applications resource to REST API
>> - Added list-applications command to CLI
>> - Removed CLI commands subscribe-cartridge, list-cartridge-subscriptions,
>> unsubscribe-cartridge and deprecated command classes
>> - Fixed coding convention issues in the CLI
>> - Fixed a null pointer issues in
>> CloudControllerUtil.toJavaUtilProperties() method
>> - Updated info logs in ApplicationBuilder class in autoscaler
>>
>> Thanks
>>
>> On Sat, Nov 8, 2014 at 7:48 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> Update:
>>>
>>> - Auto-scaling works fine for container scenario
>>> - Faulty members are successfully terminated and new containers are
>>> created successfully
>>>
>>> Thanks.
>>>
>>> On Sat, Nov 8, 2014 at 7:44 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> My understanding is that we only need the domain classes converted to
>>>> python. They may only contain list of properties. Therefore the generated
>>>> code should be simple enough to validate.
>>>>
>>>>
>>>> On Sat, Nov 8, 2014 at 7:10 PM, Chamila De Alwis <ch...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Imesh,
>>>>>
>>>>> Is it reliable to follow a code conversion tool? Given that this tool
>>>>> doesn't guarantee working code, I'm not sure this would be a better option.
>>>>>
>>>>> *"The generated Python code is not guaranteed to run,"*
>>>>>
>>>>>
>>>>> Regards,
>>>>> Chamila de Alwis
>>>>> Software Engineer | WSO2 | +94772207163
>>>>> Blog: code.chamiladealwis.com
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Nov 8, 2014 at 1:50 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I think we can use [1] to convert messaging component data model to
>>>>>> python at the build time and the agent can refer that directly. WDYT?
>>>>>>
>>>>>> [1] https://github.com/natural/java2python
>>>>>> On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <ch...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Raj,
>>>>>>>
>>>>>>> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> Please double check the java agent code too. It works somehow.
>>>>>>>> Don't know the reason :)
>>>>>>>
>>>>>>>
>>>>>>> The Java agent makes use of the org.apache.stratos.messaging
>>>>>>> component, so any changes done from a publisher's point of view is
>>>>>>> reflected on a receiver's end. In the Python agent, the serialization and
>>>>>>> the deserialization of the events published and received from the message
>>>>>>> broker is written anew in Python.
>>>>>>>
>>>>>>> The problem rises here, when the changes made in the messaging
>>>>>>> component needs to be reflected in the Python agent too. I think for the
>>>>>>> time being whenever a change is done, it is better to assign the relevant
>>>>>>> JIRA issue to the person responsible of the changes in Python cartridge
>>>>>>> agent, which is me for now :).
>>>>>>>
>>>>>>> In the long run, a set of unit tests can manage the changing code
>>>>>>> better.
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>> Chamila de Alwis
>>>>>>> Software Engineer | WSO2 | +94772207163
>>>>>>> Blog: code.chamiladealwis.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Raj
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi
I could bring an application with more than one cluster as Active.
Currently testing the faulty member scenario for VM with the Composite
application and fixing issues. Will update on that..
Thanks,
Reka
On Sat, Nov 8, 2014 at 10:39 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I have now done the following changes:
> - Added get applications resource to REST API
> - Added list-applications command to CLI
> - Removed CLI commands subscribe-cartridge, list-cartridge-subscriptions,
> unsubscribe-cartridge and deprecated command classes
> - Fixed coding convention issues in the CLI
> - Fixed a null pointer issues in
> CloudControllerUtil.toJavaUtilProperties() method
> - Updated info logs in ApplicationBuilder class in autoscaler
>
> Thanks
>
> On Sat, Nov 8, 2014 at 7:48 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Update:
>>
>> - Auto-scaling works fine for container scenario
>> - Faulty members are successfully terminated and new containers are
>> created successfully
>>
>> Thanks.
>>
>> On Sat, Nov 8, 2014 at 7:44 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> My understanding is that we only need the domain classes converted to
>>> python. They may only contain list of properties. Therefore the generated
>>> code should be simple enough to validate.
>>>
>>>
>>> On Sat, Nov 8, 2014 at 7:10 PM, Chamila De Alwis <ch...@wso2.com>
>>> wrote:
>>>
>>>> Hi Imesh,
>>>>
>>>> Is it reliable to follow a code conversion tool? Given that this tool
>>>> doesn't guarantee working code, I'm not sure this would be a better option.
>>>>
>>>> *"The generated Python code is not guaranteed to run,"*
>>>>
>>>>
>>>> Regards,
>>>> Chamila de Alwis
>>>> Software Engineer | WSO2 | +94772207163
>>>> Blog: code.chamiladealwis.com
>>>>
>>>>
>>>>
>>>> On Sat, Nov 8, 2014 at 1:50 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I think we can use [1] to convert messaging component data model to
>>>>> python at the build time and the agent can refer that directly. WDYT?
>>>>>
>>>>> [1] https://github.com/natural/java2python
>>>>> On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <ch...@wso2.com> wrote:
>>>>>
>>>>>> Hi Raj,
>>>>>>
>>>>>> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <
>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>
>>>>>>> Please double check the java agent code too. It works somehow. Don't
>>>>>>> know the reason :)
>>>>>>
>>>>>>
>>>>>> The Java agent makes use of the org.apache.stratos.messaging
>>>>>> component, so any changes done from a publisher's point of view is
>>>>>> reflected on a receiver's end. In the Python agent, the serialization and
>>>>>> the deserialization of the events published and received from the message
>>>>>> broker is written anew in Python.
>>>>>>
>>>>>> The problem rises here, when the changes made in the messaging
>>>>>> component needs to be reflected in the Python agent too. I think for the
>>>>>> time being whenever a change is done, it is better to assign the relevant
>>>>>> JIRA issue to the person responsible of the changes in Python cartridge
>>>>>> agent, which is me for now :).
>>>>>>
>>>>>> In the long run, a set of unit tests can manage the changing code
>>>>>> better.
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>> Chamila de Alwis
>>>>>> Software Engineer | WSO2 | +94772207163
>>>>>> Blog: code.chamiladealwis.com
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Raj
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
I have now done the following changes:
- Added get applications resource to REST API
- Added list-applications command to CLI
- Removed CLI commands subscribe-cartridge, list-cartridge-subscriptions,
unsubscribe-cartridge and deprecated command classes
- Fixed coding convention issues in the CLI
- Fixed a null pointer issues in CloudControllerUtil.toJavaUtilProperties()
method
- Updated info logs in ApplicationBuilder class in autoscaler
Thanks
On Sat, Nov 8, 2014 at 7:48 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Update:
>
> - Auto-scaling works fine for container scenario
> - Faulty members are successfully terminated and new containers are
> created successfully
>
> Thanks.
>
> On Sat, Nov 8, 2014 at 7:44 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> My understanding is that we only need the domain classes converted to
>> python. They may only contain list of properties. Therefore the generated
>> code should be simple enough to validate.
>>
>>
>> On Sat, Nov 8, 2014 at 7:10 PM, Chamila De Alwis <ch...@wso2.com>
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> Is it reliable to follow a code conversion tool? Given that this tool
>>> doesn't guarantee working code, I'm not sure this would be a better option.
>>>
>>> *"The generated Python code is not guaranteed to run,"*
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>> On Sat, Nov 8, 2014 at 1:50 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I think we can use [1] to convert messaging component data model to
>>>> python at the build time and the agent can refer that directly. WDYT?
>>>>
>>>> [1] https://github.com/natural/java2python
>>>> On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <ch...@wso2.com> wrote:
>>>>
>>>>> Hi Raj,
>>>>>
>>>>> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <
>>>>> rajkumarr@wso2.com> wrote:
>>>>>
>>>>>> Please double check the java agent code too. It works somehow. Don't
>>>>>> know the reason :)
>>>>>
>>>>>
>>>>> The Java agent makes use of the org.apache.stratos.messaging
>>>>> component, so any changes done from a publisher's point of view is
>>>>> reflected on a receiver's end. In the Python agent, the serialization and
>>>>> the deserialization of the events published and received from the message
>>>>> broker is written anew in Python.
>>>>>
>>>>> The problem rises here, when the changes made in the messaging
>>>>> component needs to be reflected in the Python agent too. I think for the
>>>>> time being whenever a change is done, it is better to assign the relevant
>>>>> JIRA issue to the person responsible of the changes in Python cartridge
>>>>> agent, which is me for now :).
>>>>>
>>>>> In the long run, a set of unit tests can manage the changing code
>>>>> better.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Chamila de Alwis
>>>>> Software Engineer | WSO2 | +94772207163
>>>>> Blog: code.chamiladealwis.com
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Raj
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Update:
- Auto-scaling works fine for container scenario
- Faulty members are successfully terminated and new containers are
created successfully
Thanks.
On Sat, Nov 8, 2014 at 7:44 PM, Imesh Gunaratne <im...@apache.org> wrote:
> My understanding is that we only need the domain classes converted to
> python. They may only contain list of properties. Therefore the generated
> code should be simple enough to validate.
>
>
> On Sat, Nov 8, 2014 at 7:10 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> Hi Imesh,
>>
>> Is it reliable to follow a code conversion tool? Given that this tool
>> doesn't guarantee working code, I'm not sure this would be a better option.
>>
>> *"The generated Python code is not guaranteed to run,"*
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Sat, Nov 8, 2014 at 1:50 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> I think we can use [1] to convert messaging component data model to
>>> python at the build time and the agent can refer that directly. WDYT?
>>>
>>> [1] https://github.com/natural/java2python
>>> On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <ch...@wso2.com> wrote:
>>>
>>>> Hi Raj,
>>>>
>>>> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>>> > wrote:
>>>>
>>>>> Please double check the java agent code too. It works somehow. Don't
>>>>> know the reason :)
>>>>
>>>>
>>>> The Java agent makes use of the org.apache.stratos.messaging component,
>>>> so any changes done from a publisher's point of view is reflected on a
>>>> receiver's end. In the Python agent, the serialization and the
>>>> deserialization of the events published and received from the message
>>>> broker is written anew in Python.
>>>>
>>>> The problem rises here, when the changes made in the messaging
>>>> component needs to be reflected in the Python agent too. I think for the
>>>> time being whenever a change is done, it is better to assign the relevant
>>>> JIRA issue to the person responsible of the changes in Python cartridge
>>>> agent, which is me for now :).
>>>>
>>>> In the long run, a set of unit tests can manage the changing code
>>>> better.
>>>>
>>>>
>>>> Regards,
>>>> Chamila de Alwis
>>>> Software Engineer | WSO2 | +94772207163
>>>> Blog: code.chamiladealwis.com
>>>>
>>>>
>>>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
My understanding is that we only need the domain classes converted to
python. They may only contain list of properties. Therefore the generated
code should be simple enough to validate.
On Sat, Nov 8, 2014 at 7:10 PM, Chamila De Alwis <ch...@wso2.com> wrote:
> Hi Imesh,
>
> Is it reliable to follow a code conversion tool? Given that this tool
> doesn't guarantee working code, I'm not sure this would be a better option.
>
> *"The generated Python code is not guaranteed to run,"*
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Sat, Nov 8, 2014 at 1:50 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I think we can use [1] to convert messaging component data model to
>> python at the build time and the agent can refer that directly. WDYT?
>>
>> [1] https://github.com/natural/java2python
>> On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <ch...@wso2.com> wrote:
>>
>>> Hi Raj,
>>>
>>> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>>> wrote:
>>>
>>>> Please double check the java agent code too. It works somehow. Don't
>>>> know the reason :)
>>>
>>>
>>> The Java agent makes use of the org.apache.stratos.messaging component,
>>> so any changes done from a publisher's point of view is reflected on a
>>> receiver's end. In the Python agent, the serialization and the
>>> deserialization of the events published and received from the message
>>> broker is written anew in Python.
>>>
>>> The problem rises here, when the changes made in the messaging component
>>> needs to be reflected in the Python agent too. I think for the time being
>>> whenever a change is done, it is better to assign the relevant JIRA issue
>>> to the person responsible of the changes in Python cartridge agent, which
>>> is me for now :).
>>>
>>> In the long run, a set of unit tests can manage the changing code
>>> better.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
On Sat, Nov 8, 2014 at 7:10 PM, Chamila De Alwis <ch...@wso2.com> wrote:
> Hi Imesh,
>
> Is it reliable to follow a code conversion tool? Given that this tool
> doesn't guarantee working code, I'm not sure this would be a better option.
>
> *"The generated Python code is not guaranteed to run,"*
>
If it is not guaranteed, I am -1 to this.
Thanks.
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Sat, Nov 8, 2014 at 1:50 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I think we can use [1] to convert messaging component data model to
>> python at the build time and the agent can refer that directly. WDYT?
>>
>> [1] https://github.com/natural/java2python
>> On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <ch...@wso2.com> wrote:
>>
>>> Hi Raj,
>>>
>>> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>>> wrote:
>>>
>>>> Please double check the java agent code too. It works somehow. Don't
>>>> know the reason :)
>>>
>>>
>>> The Java agent makes use of the org.apache.stratos.messaging component,
>>> so any changes done from a publisher's point of view is reflected on a
>>> receiver's end. In the Python agent, the serialization and the
>>> deserialization of the events published and received from the message
>>> broker is written anew in Python.
>>>
>>> The problem rises here, when the changes made in the messaging component
>>> needs to be reflected in the Python agent too. I think for the time being
>>> whenever a change is done, it is better to assign the relevant JIRA issue
>>> to the person responsible of the changes in Python cartridge agent, which
>>> is me for now :).
>>>
>>> In the long run, a set of unit tests can manage the changing code
>>> better.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Chamila De Alwis <ch...@wso2.com>.
Hi Imesh,
Is it reliable to follow a code conversion tool? Given that this tool
doesn't guarantee working code, I'm not sure this would be a better option.
*"The generated Python code is not guaranteed to run,"*
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Sat, Nov 8, 2014 at 1:50 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I think we can use [1] to convert messaging component data model to python
> at the build time and the agent can refer that directly. WDYT?
>
> [1] https://github.com/natural/java2python
> On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <ch...@wso2.com> wrote:
>
>> Hi Raj,
>>
>> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> Please double check the java agent code too. It works somehow. Don't
>>> know the reason :)
>>
>>
>> The Java agent makes use of the org.apache.stratos.messaging component,
>> so any changes done from a publisher's point of view is reflected on a
>> receiver's end. In the Python agent, the serialization and the
>> deserialization of the events published and received from the message
>> broker is written anew in Python.
>>
>> The problem rises here, when the changes made in the messaging component
>> needs to be reflected in the Python agent too. I think for the time being
>> whenever a change is done, it is better to assign the relevant JIRA issue
>> to the person responsible of the changes in Python cartridge agent, which
>> is me for now :).
>>
>> In the long run, a set of unit tests can manage the changing code better.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
I think we can use [1] to convert messaging component data model to python
at the build time and the agent can refer that directly. WDYT?
[1] https://github.com/natural/java2python
On Nov 8, 2014 1:28 PM, "Chamila De Alwis" <ch...@wso2.com> wrote:
> Hi Raj,
>
> On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Please double check the java agent code too. It works somehow. Don't know
>> the reason :)
>
>
> The Java agent makes use of the org.apache.stratos.messaging component, so
> any changes done from a publisher's point of view is reflected on a
> receiver's end. In the Python agent, the serialization and the
> deserialization of the events published and received from the message
> broker is written anew in Python.
>
> The problem rises here, when the changes made in the messaging component
> needs to be reflected in the Python agent too. I think for the time being
> whenever a change is done, it is better to assign the relevant JIRA issue
> to the person responsible of the changes in Python cartridge agent, which
> is me for now :).
>
> In the long run, a set of unit tests can manage the changing code better.
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Chamila De Alwis <ch...@wso2.com>.
Hi Raj,
On Sat, Nov 8, 2014 at 1:19 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Please double check the java agent code too. It works somehow. Don't know
> the reason :)
The Java agent makes use of the org.apache.stratos.messaging component, so
any changes done from a publisher's point of view is reflected on a
receiver's end. In the Python agent, the serialization and the
deserialization of the events published and received from the message
broker is written anew in Python.
The problem rises here, when the changes made in the messaging component
needs to be reflected in the Python agent too. I think for the time being
whenever a change is done, it is better to assign the relevant JIRA issue
to the person responsible of the changes in Python cartridge agent, which
is me for now :).
In the long run, a set of unit tests can manage the changing code better.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
On Sat, Nov 8, 2014 at 1:12 PM, Chamila De Alwis <ch...@wso2.com> wrote:
>
> On Sat, Nov 8, 2014 at 12:55 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> When I use m2 java agent docker image, I am getting member activated
>> events. So status is not a compulsory field chamila.
>
>
> I will fix this then. From the existing code at the time of writing the
> Python agent, I assumed it was mandatory.
>
Please double check the java agent code too. It works somehow. Don't know
the reason :)
Thanks
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Chamila De Alwis <ch...@wso2.com>.
Fixed and pushed to fork. This commit is listed in the already existing PR.
https://github.com/apache/stratos/pull/106
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Sat, Nov 8, 2014 at 1:12 PM, Chamila De Alwis <ch...@wso2.com> wrote:
>
> On Sat, Nov 8, 2014 at 12:55 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> When I use m2 java agent docker image, I am getting member activated
>> events. So status is not a compulsory field chamila.
>
>
> I will fix this then. From the existing code at the time of writing the
> Python agent, I assumed it was mandatory.
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Chamila De Alwis <ch...@wso2.com>.
On Sat, Nov 8, 2014 at 12:55 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> When I use m2 java agent docker image, I am getting member activated
> events. So status is not a compulsory field chamila.
I will fix this then. From the existing code at the time of writing the
Python agent, I assumed it was mandatory.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
When I use m2 java agent docker image, I am getting member activated
events. So status is not a compulsory field chamila.
I am going to continue with m2 image for now.
Thanks.
On Sat, Nov 8, 2014 at 12:17 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
>
>
> On Sat, Nov 8, 2014 at 12:15 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Does anyone know why cluster status filed is commented out on
>> Cluster.java?
>>
>> //private ClusterStatus status;
>>
>> Thanks.
>>
>> On Sat, Nov 8, 2014 at 11:41 AM, Chamila De Alwis <ch...@wso2.com>
>> wrote:
>>
>>>
>>> Hi Raj,
>>>
>>> On Sat, Nov 8, 2014 at 9:54 AM, Rajkumar Rajaratnam <ra...@wso2.com>
>>> wrote:
>>>
>>>> File "/mnt/cartridgeagent/modules/event/topology/events.py", line 173,
>>>> in create_from_json
>>>> cluster_obj.status = cluster_str["status"]
>>>> KeyError: 'status'
>>>>
>>>
>>> The "status" field is missing from the cluster object. From what I
>>> understand this is a mandatory field right? The CompleteTopologyEvent
>>> doesn't seem to be properly created.
>>>
>>
> Chamila, why do we need cluster status?
>
>
>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>
>>
>> --
>> Raj
>>
>
>
>
> --
> Raj
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
On Sat, Nov 8, 2014 at 12:15 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Does anyone know why cluster status filed is commented out on
> Cluster.java?
>
> //private ClusterStatus status;
>
> Thanks.
>
> On Sat, Nov 8, 2014 at 11:41 AM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>>
>> Hi Raj,
>>
>> On Sat, Nov 8, 2014 at 9:54 AM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> File "/mnt/cartridgeagent/modules/event/topology/events.py", line 173,
>>> in create_from_json
>>> cluster_obj.status = cluster_str["status"]
>>> KeyError: 'status'
>>>
>>
>> The "status" field is missing from the cluster object. From what I
>> understand this is a mandatory field right? The CompleteTopologyEvent
>> doesn't seem to be properly created.
>>
>
Chamila, why do we need cluster status?
>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
>
> --
> Raj
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
On Sat, Nov 8, 2014 at 12:15 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Does anyone know why cluster status filed is commented out on
> Cluster.java?
>
> //private ClusterStatus status;
>
Sorry for the late response, there is a LifeCycleStateManager which was
added recently, and currently status is maintained via that.
>
> Thanks.
>
> On Sat, Nov 8, 2014 at 11:41 AM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>>
>> Hi Raj,
>>
>> On Sat, Nov 8, 2014 at 9:54 AM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> File "/mnt/cartridgeagent/modules/event/topology/events.py", line 173,
>>> in create_from_json
>>> cluster_obj.status = cluster_str["status"]
>>> KeyError: 'status'
>>>
>>
>> The "status" field is missing from the cluster object. From what I
>> understand this is a mandatory field right? The CompleteTopologyEvent
>> doesn't seem to be properly created.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
>
> --
> Raj
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Does anyone know why cluster status filed is commented out on Cluster.java?
//private ClusterStatus status;
Thanks.
On Sat, Nov 8, 2014 at 11:41 AM, Chamila De Alwis <ch...@wso2.com> wrote:
>
> Hi Raj,
>
> On Sat, Nov 8, 2014 at 9:54 AM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> File "/mnt/cartridgeagent/modules/event/topology/events.py", line 173, in
>> create_from_json
>> cluster_obj.status = cluster_str["status"]
>> KeyError: 'status'
>>
>
> The "status" field is missing from the cluster object. From what I
> understand this is a mandatory field right? The CompleteTopologyEvent
> doesn't seem to be properly created.
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Chamila De Alwis <ch...@wso2.com>.
Hi Raj,
On Sat, Nov 8, 2014 at 9:54 AM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> File "/mnt/cartridgeagent/modules/event/topology/events.py", line 173, in
> create_from_json
> cluster_obj.status = cluster_str["status"]
> KeyError: 'status'
>
The "status" field is missing from the cluster object. From what I
understand this is a mandatory field right? The CompleteTopologyEvent
doesn't seem to be properly created.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Chamila,
Here is a container agent log. Any idea what event processing fails?
[2014-11-08 04:20:46,152] DEBUG {eventsubscriber.py:on_message} - Message
received: 'topology/CompleteTopologyEvent':
'{"topology":{"serviceMap":{"php":{"serviceName":"php","serviceType":"SingleTenant","clusterIdClusterMap":{"myphp.php.domain":{"serviceName":"php","clusterId":"myphp.php.domain","autoscalePolicyName":"economy","hostNames":["
myphp.apachestratos.org
"],"tenantRange":"*","isLbCluster":false,"isKubernetesCluster":true,"memberMap":{"bc4ff2cb-66fd-11e4-847b-080027fb95c5":{"serviceName":"php","clusterId":"myphp.php.domain","memberId":"bc4ff2cb-66fd-11e4-847b-080027fb95c5","initTime":1415420070103,"portMap":{"8281":{"protocol":"http","value":4500,"proxy":8281}},"memberPublicIp":"172.17.8.101","memberIp":"172.17.8.101","properties":{"ALLOCATED_SERVICE_HOST_PORT":"4500"},"memberStateManager":{"stateStack":["Created"],"identifier":"bc4ff2cb-66fd-11e4-847b-080027fb95c5"}}},"appId":"test_app_2","properties":{"payload_parameter.APP_PATH":"/var/www/www","KUBERNETES_REPLICAS_MAX":"20","KUBERNETES_CLUSTER_ID":"KubGrp1","payload_parameter.LOG_LEVEL":"DEBUG","KUBERNETES_REPLICAS_MIN":"3","payload_parameter.MB_IP":"172.17.42.1","payload_parameter.CEP_IP":"172.17.42.1","payload_parameter.MB_PORT":"1883","payload_parameter.CEP_PORT":"7711"},"clusterStateManager":{"stateStack":["Created"],"identifier":"myphp.php.domain"}}},"portMap":{"8281":{"protocol":"http","value":80,"proxy":8281}},"properties":{}}},"initialized":false}}'
[2014-11-08 04:20:46,152] DEBUG {eventsubscriber.py:on_message} - Executing
handler for event 'CompleteTopologyEvent'
[2014-11-08 04:20:46,153] DEBUG {agent.py:on_complete_topology} - Complete
topology event received
[2014-11-08 04:20:46,153] ERROR {eventsubscriber.py:on_message} - Error
processing 'CompleteTopologyEvent' event
Traceback (most recent call last):
File "/mnt/cartridgeagent/modules/subscriber/eventsubscriber.py", line
81, in on_message
handler(msg)
File "agent.py", line 252, in on_complete_topology
event_obj = CompleteTopologyEvent.create_from_json(msg.payload)
File "/mnt/cartridgeagent/modules/event/topology/events.py", line 173, in
create_from_json
cluster_obj.status = cluster_str["status"]
KeyError: 'status'
[2014-11-08 04:20:46,159] DEBUG {eventsubscriber.py:on_message} - Message
received: 'tenant/CompleteTenantEvent':
Thanks.
On Fri, Nov 7, 2014 at 11:10 PM, Imesh Gunaratne <im...@apache.org> wrote:
> As I found this problem this has been caused by the duplicated client id
> values which we have set before. Now I have done a fix to set unique client
> id values for each topic subscriber and publisher.
>
> I did several verification tests on this fix using a sample event
> publisher (sending 1000 events continuously) and with 30 subscribers. Alll
> subscribers were able to receive 1000 events without a problem.
>
> This is now committed to docker-grouping-merge branch.
>
> On Fri, Nov 7, 2014 at 2:48 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I guess we need to set clean session to false and use reliable delivery.
>> WDYT?
>>
>> MqttConnectOptions connOpts = new MqttConnectOptions();
>> connOpts.setCleanSession(false);
>>
>> * <ul>
>> * <li>If set to false both the client and server will maintain state
>> across
>> * restarts of the client, the server and the connection. As state is
>> maintained:
>> * <ul>
>> * <li>Message delivery will be reliable meeting
>> * the specified QOS even if the client, server or connection are
>> restarted.
>> * <li> The server will treat a subscription as durable.
>> * </ul>
>>
>> On Fri, Nov 7, 2014 at 2:45 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Gayan: I see another issue here:
>>>
>>> We have set QOS to 2 in publisher:
>>>
>>> MqttMessage mqttMSG = new MqttMessage(message.getBytes());
>>> mqttMSG.setQos(QOS); // QOS => 2
>>>
>>> ** <li>Quality of Service 2 - indicates that a message should*
>>> ** be delivered once. The message will be persisted to disk, and will*
>>> ** be subject to a two-phase acknowledgement across the network.*
>>> ** The message can only be delivered safely if*
>>> ** it can be persisted, so the application must supply a means of*
>>> ** persistence using <code>MqttConnectOptions</code>.*
>>> ** If a persistence mechanism is not specified, the message will not be*
>>> ** delivered in the event of a client failure.</li>*
>>>
>>> Here we have set clean session option to true in connect options:
>>>
>>> MqttConnectOptions connOpts = new MqttConnectOptions();
>>> connOpts.setCleanSession(true);
>>>
>>> * <lI>If set to true the client and server will not maintain state across
>>> * restarts of the client, the server or the connection. *This means*
>>> ** <ul>*
>>> ** <li>Message delivery to the specified QOS cannot be maintained if the*
>>> ** client, server or connection are restarted*
>>> * <lI>The server will treat a subscription as non-durable
>>> * </ul>
>>>
>>> As I see these two configurations contradicts. May be this is why we see
>>> message delivery fails intermittently. WDYT?
>>>
>>> On Fri, Nov 7, 2014 at 2:29 PM, Gayan Gunarathne <ga...@wso2.com>
>>> wrote:
>>>
>>>>
>>>> At a particular time we do have multiple listeners and only one topic
>>>> publisher for a component. Because of that generating a client id for
>>>> subscribers.
>>>>
>>>> +1 for have client id unique according to this
>>>>
>>>> [1].
>>>> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
>>>> java.lang.String)
>>>>
>>>>
>>>> Thanks,
>>>> Gayan
>>>>
>>>> On Fri, Nov 7, 2014 at 2:14 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Gayan: Was there any reason for generating a client id for subscribers
>>>>> and setting a fixed value for publishers?
>>>>>
>>>>> TopicSubscriber.doSubscribe():
>>>>> MqttClient mqttClient = MQTTConnector.getMQTTSubClient(Util.
>>>>> getRandomString(5));
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Nov 7, 2014 at 1:17 PM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>>> > wrote:
>>>>>>
>>>>>>>
>>>>>>> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> I got containers to be created.
>>>>>>>> But didn't get the member started event. Either agent is not
>>>>>>>> sending or CC is not receiving. Looking into it currently.
>>>>>>>>
>>>>>>> I'm seeing this issue as well. The agent is sending the events, but
>>>>>>> Stratos is not receiving them. Trying with a simple mqtt client now.
>>>>>>>
>>>>>> In [1], we are using the client id in mqtttopic.properties file as it
>>>>>> is and using it to start the MQTTClient. However, in the wiki it says that
>>>>>> client id should be unique across all publishers [2]. I might be missing
>>>>>> something here, but is this case handled?
>>>>>>
>>>>>> [1]. org.apache.stratos.messaging.broker.connect.MQTTConnector
>>>>>>
>>>>>> [2].
>>>>>> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
>>>>>> java.lang.String)
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Isuru,
>>>>>>>>>
>>>>>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <
>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> IMHO we should have the context name 'stratos' in the url. Then
>>>>>>>>>> it is more intuitive. having just /api doesn't say that this API belongs to
>>>>>>>>>> Stratos.
>>>>>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path}
>>>>>>>>>> is better IMHO. If we have a proper hostname (stratos.apache.org)
>>>>>>>>>> this might do the same, but that might not be the case always. Just my two
>>>>>>>>>> cents.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> A good point, I reviewed your concern before doing this
>>>>>>>>> modification, most of the well known APIs do not include the product name
>>>>>>>>> in the context. Rather as you have mentioned they use the hostname to
>>>>>>>>> identify the product, please see below examples. This is why I removed
>>>>>>>>> "stratos" from the context, WDYT?
>>>>>>>>>
>>>>>>>>> Facebook Graph API:
>>>>>>>>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
>>>>>>>>> Twitter API:
>>>>>>>>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
>>>>>>>>> Github API: https://developer.github.com/v3/
>>>>>>>>> OpenStack API:
>>>>>>>>> http://developer.openstack.org/api-ref-compute-v2.html
>>>>>>>>> EC2 API:
>>>>>>>>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
>>>>>>>>> Google Cloud Compute API:
>>>>>>>>> https://cloud.google.com/compute/docs/reference/latest/#Addresses
>>>>>>>>> StackExchange API: https://api.stackexchange.com/docs/answers
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <
>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Imesh,
>>>>>>>>>>
>>>>>>>>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> Please note that we have now introduced API versioning in
>>>>>>>>>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>>>>>>>>>> follows, no changes were done to existing resource paths:
>>>>>>>>>>>
>>>>>>>>>>> Previous API URL:
>>>>>>>>>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>>>>>>>>>
>>>>>>>>>>> New API URL:
>>>>>>>>>>> https://{hostname}:{port}/api/{resource-path}
>>>>>>>>>>>
>>>>>>>>>> IMHO we should have the context name 'stratos' in the url. Then
>>>>>>>>>> it is more intuitive. having just /api doesn't say that this API belongs to
>>>>>>>>>> Stratos.
>>>>>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path}
>>>>>>>>>> is better IMHO. If we have a proper hostname (stratos.apache.org)
>>>>>>>>>> this might do the same, but that might not be the case always. Just my two
>>>>>>>>>> cents.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Version specific API URLs:
>>>>>>>>>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>>>>>>>>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>>>>>>>>>
>>>>>>>>>>> Following changes to be done:
>>>>>>>>>>> - Update CLI and Dashboard
>>>>>>>>>>> - Allow API version to be specified in an HTTP header
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> We now have the docker-grouping-branch in a compilable state
>>>>>>>>>>>> with latests modifications. Please test all workflows related to service
>>>>>>>>>>>> grouping and docker, once things are stable will merge this branch to
>>>>>>>>>>>> master.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte
>>>>>>>>>>>> <ma...@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have completed deploy-application, undeploy-application,
>>>>>>>>>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>>>>>>>>>> the changes to docker-grouping-merge branch. I'll compete the
>>>>>>>>>>>>> other commands as soon as possible and looks for the UI as well.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have now fixed autoscaler service stub bundle exports and
>>>>>>>>>>>>>> stratos manager import statements. Currently working on Stratos Manager,
>>>>>>>>>>>>>> seems like there are duplicated domain classes:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Fixed AS issues
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <
>>>>>>>>>>>>>>> lasindu@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika
>>>>>>>>>>>>>>>> Thantriwatte <ma...@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping
>>>>>>>>>>>>>>>>>>> branch to docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Once features are stable will move changes to master
>>>>>>>>>>>>>>>>>>> branch.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Isuru is working on a major refactoring task
>>>>>>>>>>>>>>>>>>>> ("[Grouping] Branch may be Unstable ATM"). Will hold this effort until that
>>>>>>>>>>>>>>>>>>>> is completed.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance
>>>>>>>>>>>>>>>>>>>>> are spawning. Will be testing further.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> When and where are we creating and adding cluster
>>>>>>>>>>>>>>>>>>>>>> monitors (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app
>>>>>>>>>>>>>>>>>>>>>>>> definition without properties, looking into it.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and
>>>>>>>>>>>>>>>>>>>>>>>>> CLI.
>>>>>>>>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>>>>>>>>>> - Passing properties from Application definition
>>>>>>>>>>>>>>>>>>>>>>>>> to the cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution
>>>>>>>>>>>>>>>>>>>>>>>>> (some of the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Please find the sample application definition file
>>>>>>>>>>>>>>>>>>>>>>>>> which I have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span
>>>>>>>>>>>>>>>>>>>>>>>>>> across two partitions(in other words two kub cluster)? I guess kubernetes
>>>>>>>>>>>>>>>>>>>>>>>>>> can manage their containers within a kub cluster, not between kub clusters?
>>>>>>>>>>>>>>>>>>>>>>>>>> For example, if we say we need 3 replicas, it can ensure there are 3
>>>>>>>>>>>>>>>>>>>>>>>>>> replicas in one kub cluster. It can't manage 3 replicas within two kub
>>>>>>>>>>>>>>>>>>>>>>>>>> cluster. Am I missing something here?
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> *Lasindu Charith*
>>>>>>>>>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>>>>>>>>>> Mobile: +94714427192
>>>>>>>>>>>>>>>> Web: blog.lasindu.com
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>>>
>>>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>
>>>>>>>>>>> Isuru H.
>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Raj
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks and Regards,
>>>>>>>>
>>>>>>>> Isuru H.
>>>>>>>> +94 716 358 048
>>>>>>>>
>>>>>>>> --
>>>>>>>> <%2B94%20716%20358%20048>
>>>>>>>> <%2B94%20716%20358%20048>
>>>>>>>> Thanks and Regards,
>>>>>>>>
>>>>>>>> Isuru H.
>>>>>>>> <%2B94%20716%20358%20048>
>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>> * <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Gayan Gunarathne
>>>> Technical Lead
>>>> WSO2 Inc. (http://wso2.com)
>>>> email : gayang@wso2.com | mobile : +94 766819985
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
As I found this problem this has been caused by the duplicated client id
values which we have set before. Now I have done a fix to set unique client
id values for each topic subscriber and publisher.
I did several verification tests on this fix using a sample event publisher
(sending 1000 events continuously) and with 30 subscribers. Alll
subscribers were able to receive 1000 events without a problem.
This is now committed to docker-grouping-merge branch.
On Fri, Nov 7, 2014 at 2:48 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I guess we need to set clean session to false and use reliable delivery.
> WDYT?
>
> MqttConnectOptions connOpts = new MqttConnectOptions();
> connOpts.setCleanSession(false);
>
> * <ul>
> * <li>If set to false both the client and server will maintain state across
> * restarts of the client, the server and the connection. As state is
> maintained:
> * <ul>
> * <li>Message delivery will be reliable meeting
> * the specified QOS even if the client, server or connection are restarted.
> * <li> The server will treat a subscription as durable.
> * </ul>
>
> On Fri, Nov 7, 2014 at 2:45 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Gayan: I see another issue here:
>>
>> We have set QOS to 2 in publisher:
>>
>> MqttMessage mqttMSG = new MqttMessage(message.getBytes());
>> mqttMSG.setQos(QOS); // QOS => 2
>>
>> ** <li>Quality of Service 2 - indicates that a message should*
>> ** be delivered once. The message will be persisted to disk, and will*
>> ** be subject to a two-phase acknowledgement across the network.*
>> ** The message can only be delivered safely if*
>> ** it can be persisted, so the application must supply a means of*
>> ** persistence using <code>MqttConnectOptions</code>.*
>> ** If a persistence mechanism is not specified, the message will not be*
>> ** delivered in the event of a client failure.</li>*
>>
>> Here we have set clean session option to true in connect options:
>>
>> MqttConnectOptions connOpts = new MqttConnectOptions();
>> connOpts.setCleanSession(true);
>>
>> * <lI>If set to true the client and server will not maintain state across
>> * restarts of the client, the server or the connection. *This means*
>> ** <ul>*
>> ** <li>Message delivery to the specified QOS cannot be maintained if the*
>> ** client, server or connection are restarted*
>> * <lI>The server will treat a subscription as non-durable
>> * </ul>
>>
>> As I see these two configurations contradicts. May be this is why we see
>> message delivery fails intermittently. WDYT?
>>
>> On Fri, Nov 7, 2014 at 2:29 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
>>
>>>
>>> At a particular time we do have multiple listeners and only one topic
>>> publisher for a component. Because of that generating a client id for
>>> subscribers.
>>>
>>> +1 for have client id unique according to this
>>>
>>> [1].
>>> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
>>> java.lang.String)
>>>
>>>
>>> Thanks,
>>> Gayan
>>>
>>> On Fri, Nov 7, 2014 at 2:14 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Gayan: Was there any reason for generating a client id for subscribers
>>>> and setting a fixed value for publishers?
>>>>
>>>> TopicSubscriber.doSubscribe():
>>>> MqttClient mqttClient = MQTTConnector.getMQTTSubClient(Util.
>>>> getRandomString(5));
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Nov 7, 2014 at 1:17 PM, Isuru Haththotuwa <is...@apache.org>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <
>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>
>>>>>>> I got containers to be created.
>>>>>>> But didn't get the member started event. Either agent is not sending
>>>>>>> or CC is not receiving. Looking into it currently.
>>>>>>>
>>>>>> I'm seeing this issue as well. The agent is sending the events, but
>>>>>> Stratos is not receiving them. Trying with a simple mqtt client now.
>>>>>>
>>>>> In [1], we are using the client id in mqtttopic.properties file as it
>>>>> is and using it to start the MQTTClient. However, in the wiki it says that
>>>>> client id should be unique across all publishers [2]. I might be missing
>>>>> something here, but is this case handled?
>>>>>
>>>>> [1]. org.apache.stratos.messaging.broker.connect.MQTTConnector
>>>>>
>>>>> [2].
>>>>> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
>>>>> java.lang.String)
>>>>>
>>>>>
>>>>>>
>>>>>>> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Isuru,
>>>>>>>>
>>>>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <
>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> IMHO we should have the context name 'stratos' in the url. Then it
>>>>>>>>> is more intuitive. having just /api doesn't say that this API belongs to
>>>>>>>>> Stratos.
>>>>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path}
>>>>>>>>> is better IMHO. If we have a proper hostname (stratos.apache.org)
>>>>>>>>> this might do the same, but that might not be the case always. Just my two
>>>>>>>>> cents.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> A good point, I reviewed your concern before doing this
>>>>>>>> modification, most of the well known APIs do not include the product name
>>>>>>>> in the context. Rather as you have mentioned they use the hostname to
>>>>>>>> identify the product, please see below examples. This is why I removed
>>>>>>>> "stratos" from the context, WDYT?
>>>>>>>>
>>>>>>>> Facebook Graph API:
>>>>>>>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
>>>>>>>> Twitter API:
>>>>>>>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
>>>>>>>> Github API: https://developer.github.com/v3/
>>>>>>>> OpenStack API:
>>>>>>>> http://developer.openstack.org/api-ref-compute-v2.html
>>>>>>>> EC2 API:
>>>>>>>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
>>>>>>>> Google Cloud Compute API:
>>>>>>>> https://cloud.google.com/compute/docs/reference/latest/#Addresses
>>>>>>>> StackExchange API: https://api.stackexchange.com/docs/answers
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <
>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>
>>>>>>>>> Hi Imesh,
>>>>>>>>>
>>>>>>>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Please note that we have now introduced API versioning in
>>>>>>>>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>>>>>>>>> follows, no changes were done to existing resource paths:
>>>>>>>>>>
>>>>>>>>>> Previous API URL:
>>>>>>>>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>>>>>>>>
>>>>>>>>>> New API URL:
>>>>>>>>>> https://{hostname}:{port}/api/{resource-path}
>>>>>>>>>>
>>>>>>>>> IMHO we should have the context name 'stratos' in the url. Then it
>>>>>>>>> is more intuitive. having just /api doesn't say that this API belongs to
>>>>>>>>> Stratos.
>>>>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path}
>>>>>>>>> is better IMHO. If we have a proper hostname (stratos.apache.org)
>>>>>>>>> this might do the same, but that might not be the case always. Just my two
>>>>>>>>> cents.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Version specific API URLs:
>>>>>>>>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>>>>>>>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>>>>>>>>
>>>>>>>>>> Following changes to be done:
>>>>>>>>>> - Update CLI and Dashboard
>>>>>>>>>> - Allow API version to be specified in an HTTP header
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> We now have the docker-grouping-branch in a compilable state
>>>>>>>>>>> with latests modifications. Please test all workflows related to service
>>>>>>>>>>> grouping and docker, once things are stable will merge this branch to
>>>>>>>>>>> master.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I have completed deploy-application, undeploy-application,
>>>>>>>>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>>>>>>>>> the changes to docker-grouping-merge branch. I'll compete the
>>>>>>>>>>>> other commands as soon as possible and looks for the UI as well.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I have now fixed autoscaler service stub bundle exports and
>>>>>>>>>>>>> stratos manager import statements. Currently working on Stratos Manager,
>>>>>>>>>>>>> seems like there are duplicated domain classes:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>>>>>>>>
>>>>>>>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>>>>>>>>
>>>>>>>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Fixed AS issues
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <
>>>>>>>>>>>>>> lasindu@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika
>>>>>>>>>>>>>>> Thantriwatte <ma...@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping
>>>>>>>>>>>>>>>>>> branch to docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Once features are stable will move changes to master
>>>>>>>>>>>>>>>>>> branch.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Isuru is working on a major refactoring task
>>>>>>>>>>>>>>>>>>> ("[Grouping] Branch may be Unstable ATM"). Will hold this effort until that
>>>>>>>>>>>>>>>>>>> is completed.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance
>>>>>>>>>>>>>>>>>>>> are spawning. Will be testing further.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> When and where are we creating and adding cluster
>>>>>>>>>>>>>>>>>>>>> monitors (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app
>>>>>>>>>>>>>>>>>>>>>>> definition without properties, looking into it.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and
>>>>>>>>>>>>>>>>>>>>>>>> CLI.
>>>>>>>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>>>>>>>>> - Passing properties from Application definition to
>>>>>>>>>>>>>>>>>>>>>>>> the cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution
>>>>>>>>>>>>>>>>>>>>>>>> (some of the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Please find the sample application definition file
>>>>>>>>>>>>>>>>>>>>>>>> which I have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across
>>>>>>>>>>>>>>>>>>>>>>>>> two partitions(in other words two kub cluster)? I guess kubernetes can
>>>>>>>>>>>>>>>>>>>>>>>>> manage their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> *Lasindu Charith*
>>>>>>>>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>>>>>>>>> Mobile: +94714427192
>>>>>>>>>>>>>>> Web: blog.lasindu.com
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>>
>>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>
>>>>>>>>>> Isuru H.
>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Raj
>>>>>>>
>>>>>>> --
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> +94 716 358 048
>>>>>>>
>>>>>>> --
>>>>>>> <%2B94%20716%20358%20048>
>>>>>>> <%2B94%20716%20358%20048>
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> <%2B94%20716%20358%20048>
>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>> * <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Gayan Gunarathne
>>> Technical Lead
>>> WSO2 Inc. (http://wso2.com)
>>> email : gayang@wso2.com | mobile : +94 766819985
>>>
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
I guess we need to set clean session to false and use reliable delivery.
WDYT?
MqttConnectOptions connOpts = new MqttConnectOptions();
connOpts.setCleanSession(false);
* <ul>
* <li>If set to false both the client and server will maintain state across
* restarts of the client, the server and the connection. As state is
maintained:
* <ul>
* <li>Message delivery will be reliable meeting
* the specified QOS even if the client, server or connection are restarted.
* <li> The server will treat a subscription as durable.
* </ul>
On Fri, Nov 7, 2014 at 2:45 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Gayan: I see another issue here:
>
> We have set QOS to 2 in publisher:
>
> MqttMessage mqttMSG = new MqttMessage(message.getBytes());
> mqttMSG.setQos(QOS); // QOS => 2
>
> ** <li>Quality of Service 2 - indicates that a message should*
> ** be delivered once. The message will be persisted to disk, and will*
> ** be subject to a two-phase acknowledgement across the network.*
> ** The message can only be delivered safely if*
> ** it can be persisted, so the application must supply a means of*
> ** persistence using <code>MqttConnectOptions</code>.*
> ** If a persistence mechanism is not specified, the message will not be*
> ** delivered in the event of a client failure.</li>*
>
> Here we have set clean session option to true in connect options:
>
> MqttConnectOptions connOpts = new MqttConnectOptions();
> connOpts.setCleanSession(true);
>
> * <lI>If set to true the client and server will not maintain state across
> * restarts of the client, the server or the connection. *This means*
> ** <ul>*
> ** <li>Message delivery to the specified QOS cannot be maintained if the*
> ** client, server or connection are restarted*
> * <lI>The server will treat a subscription as non-durable
> * </ul>
>
> As I see these two configurations contradicts. May be this is why we see
> message delivery fails intermittently. WDYT?
>
> On Fri, Nov 7, 2014 at 2:29 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
>
>>
>> At a particular time we do have multiple listeners and only one topic
>> publisher for a component. Because of that generating a client id for
>> subscribers.
>>
>> +1 for have client id unique according to this
>>
>> [1].
>> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
>> java.lang.String)
>>
>>
>> Thanks,
>> Gayan
>>
>> On Fri, Nov 7, 2014 at 2:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Gayan: Was there any reason for generating a client id for subscribers
>>> and setting a fixed value for publishers?
>>>
>>> TopicSubscriber.doSubscribe():
>>> MqttClient mqttClient = MQTTConnector.getMQTTSubClient(Util.
>>> getRandomString(5));
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Nov 7, 2014 at 1:17 PM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa <is...@apache.org>
>>>> wrote:
>>>>
>>>>>
>>>>> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <
>>>>> rajkumarr@wso2.com> wrote:
>>>>>
>>>>>> I got containers to be created.
>>>>>> But didn't get the member started event. Either agent is not sending
>>>>>> or CC is not receiving. Looking into it currently.
>>>>>>
>>>>> I'm seeing this issue as well. The agent is sending the events, but
>>>>> Stratos is not receiving them. Trying with a simple mqtt client now.
>>>>>
>>>> In [1], we are using the client id in mqtttopic.properties file as it
>>>> is and using it to start the MQTTClient. However, in the wiki it says that
>>>> client id should be unique across all publishers [2]. I might be missing
>>>> something here, but is this case handled?
>>>>
>>>> [1]. org.apache.stratos.messaging.broker.connect.MQTTConnector
>>>>
>>>> [2].
>>>> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
>>>> java.lang.String)
>>>>
>>>>
>>>>>
>>>>>> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Isuru,
>>>>>>>
>>>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <
>>>>>>> isuruh@apache.org> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> IMHO we should have the context name 'stratos' in the url. Then it
>>>>>>>> is more intuitive. having just /api doesn't say that this API belongs to
>>>>>>>> Stratos.
>>>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path}
>>>>>>>> is better IMHO. If we have a proper hostname (stratos.apache.org)
>>>>>>>> this might do the same, but that might not be the case always. Just my two
>>>>>>>> cents.
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> A good point, I reviewed your concern before doing this
>>>>>>> modification, most of the well known APIs do not include the product name
>>>>>>> in the context. Rather as you have mentioned they use the hostname to
>>>>>>> identify the product, please see below examples. This is why I removed
>>>>>>> "stratos" from the context, WDYT?
>>>>>>>
>>>>>>> Facebook Graph API:
>>>>>>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
>>>>>>> Twitter API:
>>>>>>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
>>>>>>> Github API: https://developer.github.com/v3/
>>>>>>> OpenStack API:
>>>>>>> http://developer.openstack.org/api-ref-compute-v2.html
>>>>>>> EC2 API:
>>>>>>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
>>>>>>> Google Cloud Compute API:
>>>>>>> https://cloud.google.com/compute/docs/reference/latest/#Addresses
>>>>>>> StackExchange API: https://api.stackexchange.com/docs/answers
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <
>>>>>>> isuruh@apache.org> wrote:
>>>>>>>
>>>>>>>> Hi Imesh,
>>>>>>>>
>>>>>>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Please note that we have now introduced API versioning in
>>>>>>>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>>>>>>>> follows, no changes were done to existing resource paths:
>>>>>>>>>
>>>>>>>>> Previous API URL:
>>>>>>>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>>>>>>>
>>>>>>>>> New API URL:
>>>>>>>>> https://{hostname}:{port}/api/{resource-path}
>>>>>>>>>
>>>>>>>> IMHO we should have the context name 'stratos' in the url. Then it
>>>>>>>> is more intuitive. having just /api doesn't say that this API belongs to
>>>>>>>> Stratos.
>>>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path}
>>>>>>>> is better IMHO. If we have a proper hostname (stratos.apache.org)
>>>>>>>> this might do the same, but that might not be the case always. Just my two
>>>>>>>> cents.
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Version specific API URLs:
>>>>>>>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>>>>>>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>>>>>>>
>>>>>>>>> Following changes to be done:
>>>>>>>>> - Update CLI and Dashboard
>>>>>>>>> - Allow API version to be specified in an HTTP header
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> We now have the docker-grouping-branch in a compilable state with
>>>>>>>>>> latests modifications. Please test all workflows related to service
>>>>>>>>>> grouping and docker, once things are stable will merge this branch to
>>>>>>>>>> master.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I have completed deploy-application, undeploy-application,
>>>>>>>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>>>>>>>> the changes to docker-grouping-merge branch. I'll compete the
>>>>>>>>>>> other commands as soon as possible and looks for the UI as well.
>>>>>>>>>>>
>>>>>>>>>>> Thanks !
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have now fixed autoscaler service stub bundle exports and
>>>>>>>>>>>> stratos manager import statements. Currently working on Stratos Manager,
>>>>>>>>>>>> seems like there are duplicated domain classes:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Fixed AS issues
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <
>>>>>>>>>>>>> lasindu@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika
>>>>>>>>>>>>>> Thantriwatte <ma...@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping
>>>>>>>>>>>>>>>>> branch to docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Once features are stable will move changes to master
>>>>>>>>>>>>>>>>> branch.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping]
>>>>>>>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> When and where are we creating and adding cluster
>>>>>>>>>>>>>>>>>>>> monitors (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and
>>>>>>>>>>>>>>>>>>>>>>> CLI.
>>>>>>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>>>>>>>> - Passing properties from Application definition to
>>>>>>>>>>>>>>>>>>>>>>> the cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution
>>>>>>>>>>>>>>>>>>>>>>> (some of the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Please find the sample application definition file
>>>>>>>>>>>>>>>>>>>>>>> which I have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across
>>>>>>>>>>>>>>>>>>>>>>>> two partitions(in other words two kub cluster)? I guess kubernetes can
>>>>>>>>>>>>>>>>>>>>>>>> manage their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> *Lasindu Charith*
>>>>>>>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>>>>>>>> Mobile: +94714427192
>>>>>>>>>>>>>> Web: blog.lasindu.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Regards,
>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>> Software Engineer
>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>
>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks and Regards,
>>>>>>>>>
>>>>>>>>> Isuru H.
>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Raj
>>>>>>
>>>>>> --
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> +94 716 358 048
>>>>>>
>>>>>> --
>>>>>> <%2B94%20716%20358%20048>
>>>>>> <%2B94%20716%20358%20048>
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> <%2B94%20716%20358%20048>
>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>> * <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead
>> WSO2 Inc. (http://wso2.com)
>> email : gayang@wso2.com | mobile : +94 766819985
>>
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Gayan: I see another issue here:
We have set QOS to 2 in publisher:
MqttMessage mqttMSG = new MqttMessage(message.getBytes());
mqttMSG.setQos(QOS); // QOS => 2
** <li>Quality of Service 2 - indicates that a message should*
** be delivered once. The message will be persisted to disk, and will*
** be subject to a two-phase acknowledgement across the network.*
** The message can only be delivered safely if*
** it can be persisted, so the application must supply a means of*
** persistence using <code>MqttConnectOptions</code>.*
** If a persistence mechanism is not specified, the message will not be*
** delivered in the event of a client failure.</li>*
Here we have set clean session option to true in connect options:
MqttConnectOptions connOpts = new MqttConnectOptions();
connOpts.setCleanSession(true);
* <lI>If set to true the client and server will not maintain state across
* restarts of the client, the server or the connection. *This means*
** <ul>*
** <li>Message delivery to the specified QOS cannot be maintained if the*
** client, server or connection are restarted*
* <lI>The server will treat a subscription as non-durable
* </ul>
As I see these two configurations contradicts. May be this is why we see
message delivery fails intermittently. WDYT?
On Fri, Nov 7, 2014 at 2:29 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
>
> At a particular time we do have multiple listeners and only one topic
> publisher for a component. Because of that generating a client id for
> subscribers.
>
> +1 for have client id unique according to this
>
> [1].
> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
> java.lang.String)
>
>
> Thanks,
> Gayan
>
> On Fri, Nov 7, 2014 at 2:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Gayan: Was there any reason for generating a client id for subscribers
>> and setting a fixed value for publishers?
>>
>> TopicSubscriber.doSubscribe():
>> MqttClient mqttClient = MQTTConnector.getMQTTSubClient(Util.
>> getRandomString(5));
>>
>>
>>
>>
>>
>> On Fri, Nov 7, 2014 at 1:17 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>>
>>>
>>> On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>>
>>>> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <
>>>> rajkumarr@wso2.com> wrote:
>>>>
>>>>> I got containers to be created.
>>>>> But didn't get the member started event. Either agent is not sending
>>>>> or CC is not receiving. Looking into it currently.
>>>>>
>>>> I'm seeing this issue as well. The agent is sending the events, but
>>>> Stratos is not receiving them. Trying with a simple mqtt client now.
>>>>
>>> In [1], we are using the client id in mqtttopic.properties file as it is
>>> and using it to start the MQTTClient. However, in the wiki it says that
>>> client id should be unique across all publishers [2]. I might be missing
>>> something here, but is this case handled?
>>>
>>> [1]. org.apache.stratos.messaging.broker.connect.MQTTConnector
>>>
>>> [2].
>>> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
>>> java.lang.String)
>>>
>>>
>>>>
>>>>> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi Isuru,
>>>>>>
>>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <isuruh@apache.org
>>>>>> > wrote:
>>>>>>
>>>>>>>
>>>>>>> IMHO we should have the context name 'stratos' in the url. Then it
>>>>>>> is more intuitive. having just /api doesn't say that this API belongs to
>>>>>>> Stratos.
>>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>>>>> might do the same, but that might not be the case always. Just my two
>>>>>>> cents.
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> A good point, I reviewed your concern before doing this
>>>>>> modification, most of the well known APIs do not include the product name
>>>>>> in the context. Rather as you have mentioned they use the hostname to
>>>>>> identify the product, please see below examples. This is why I removed
>>>>>> "stratos" from the context, WDYT?
>>>>>>
>>>>>> Facebook Graph API:
>>>>>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
>>>>>> Twitter API:
>>>>>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
>>>>>> Github API: https://developer.github.com/v3/
>>>>>> OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html
>>>>>> EC2 API:
>>>>>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
>>>>>> Google Cloud Compute API:
>>>>>> https://cloud.google.com/compute/docs/reference/latest/#Addresses
>>>>>> StackExchange API: https://api.stackexchange.com/docs/answers
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <isuruh@apache.org
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi Imesh,
>>>>>>>
>>>>>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Please note that we have now introduced API versioning in
>>>>>>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>>>>>>> follows, no changes were done to existing resource paths:
>>>>>>>>
>>>>>>>> Previous API URL:
>>>>>>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>>>>>>
>>>>>>>> New API URL:
>>>>>>>> https://{hostname}:{port}/api/{resource-path}
>>>>>>>>
>>>>>>> IMHO we should have the context name 'stratos' in the url. Then it
>>>>>>> is more intuitive. having just /api doesn't say that this API belongs to
>>>>>>> Stratos.
>>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>>>>> might do the same, but that might not be the case always. Just my two
>>>>>>> cents.
>>>>>>>
>>>>>>>>
>>>>>>>> Version specific API URLs:
>>>>>>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>>>>>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>>>>>>
>>>>>>>> Following changes to be done:
>>>>>>>> - Update CLI and Dashboard
>>>>>>>> - Allow API version to be specified in an HTTP header
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> We now have the docker-grouping-branch in a compilable state with
>>>>>>>>> latests modifications. Please test all workflows related to service
>>>>>>>>> grouping and docker, once things are stable will merge this branch to
>>>>>>>>> master.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I have completed deploy-application, undeploy-application,
>>>>>>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>>>>>>> the changes to docker-grouping-merge branch. I'll compete the
>>>>>>>>>> other commands as soon as possible and looks for the UI as well.
>>>>>>>>>>
>>>>>>>>>> Thanks !
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> I have now fixed autoscaler service stub bundle exports and
>>>>>>>>>>> stratos manager import statements. Currently working on Stratos Manager,
>>>>>>>>>>> seems like there are duplicated domain classes:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>>>>>>
>>>>>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>>>>>>
>>>>>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Fixed AS issues
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <
>>>>>>>>>>>> lasindu@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte
>>>>>>>>>>>>> <ma...@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch
>>>>>>>>>>>>>>>> to docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping]
>>>>>>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> When and where are we creating and adding cluster
>>>>>>>>>>>>>>>>>>> monitors (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>>>>>>> Method)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and
>>>>>>>>>>>>>>>>>>>>>> CLI.
>>>>>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>>>>>>> - Passing properties from Application definition to
>>>>>>>>>>>>>>>>>>>>>> the cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution
>>>>>>>>>>>>>>>>>>>>>> (some of the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Please find the sample application definition file
>>>>>>>>>>>>>>>>>>>>>> which I have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across
>>>>>>>>>>>>>>>>>>>>>>> two partitions(in other words two kub cluster)? I guess kubernetes can
>>>>>>>>>>>>>>>>>>>>>>> manage their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> *Lasindu Charith*
>>>>>>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>>>>>>> Mobile: +94714427192
>>>>>>>>>>>>> Web: blog.lasindu.com
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Raj
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Regards,
>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>> Software Engineer
>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>
>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>> phone : +94 772492511
>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks and Regards,
>>>>>>>>
>>>>>>>> Isuru H.
>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>> * <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Raj
>>>>>
>>>>> --
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> +94 716 358 048
>>>>>
>>>>> --
>>>>> <%2B94%20716%20358%20048>
>>>>> <%2B94%20716%20358%20048>
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> <%2B94%20716%20358%20048>
>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>
>>>>>
>>>>> * <http://wso2.com/>*
>>>>>
>>>>>
>>>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead
> WSO2 Inc. (http://wso2.com)
> email : gayang@wso2.com | mobile : +94 766819985
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Gayan Gunarathne <ga...@wso2.com>.
At a particular time we do have multiple listeners and only one topic
publisher for a component. Because of that generating a client id for
subscribers.
+1 for have client id unique according to this
[1].
http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
java.lang.String)
Thanks,
Gayan
On Fri, Nov 7, 2014 at 2:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Gayan: Was there any reason for generating a client id for subscribers and
> setting a fixed value for publishers?
>
> TopicSubscriber.doSubscribe():
> MqttClient mqttClient = MQTTConnector.getMQTTSubClient(Util.
> getRandomString(5));
>
>
>
>
>
> On Fri, Nov 7, 2014 at 1:17 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>>
>>
>> On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>>
>>> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>> > wrote:
>>>
>>>> I got containers to be created.
>>>> But didn't get the member started event. Either agent is not sending or
>>>> CC is not receiving. Looking into it currently.
>>>>
>>> I'm seeing this issue as well. The agent is sending the events, but
>>> Stratos is not receiving them. Trying with a simple mqtt client now.
>>>
>> In [1], we are using the client id in mqtttopic.properties file as it is
>> and using it to start the MQTTClient. However, in the wiki it says that
>> client id should be unique across all publishers [2]. I might be missing
>> something here, but is this case handled?
>>
>> [1]. org.apache.stratos.messaging.broker.connect.MQTTConnector
>>
>> [2].
>> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
>> java.lang.String)
>>
>>
>>>
>>>> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi Isuru,
>>>>>
>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>>>> Stratos.
>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>>>> might do the same, but that might not be the case always. Just my two
>>>>>> cents.
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> A good point, I reviewed your concern before doing this
>>>>> modification, most of the well known APIs do not include the product name
>>>>> in the context. Rather as you have mentioned they use the hostname to
>>>>> identify the product, please see below examples. This is why I removed
>>>>> "stratos" from the context, WDYT?
>>>>>
>>>>> Facebook Graph API:
>>>>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
>>>>> Twitter API:
>>>>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
>>>>> Github API: https://developer.github.com/v3/
>>>>> OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html
>>>>> EC2 API:
>>>>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
>>>>> Google Cloud Compute API:
>>>>> https://cloud.google.com/compute/docs/reference/latest/#Addresses
>>>>> StackExchange API: https://api.stackexchange.com/docs/answers
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi Imesh,
>>>>>>
>>>>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Please note that we have now introduced API versioning in
>>>>>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>>>>>> follows, no changes were done to existing resource paths:
>>>>>>>
>>>>>>> Previous API URL:
>>>>>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>>>>>
>>>>>>> New API URL:
>>>>>>> https://{hostname}:{port}/api/{resource-path}
>>>>>>>
>>>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>>>> Stratos.
>>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>>>> might do the same, but that might not be the case always. Just my two
>>>>>> cents.
>>>>>>
>>>>>>>
>>>>>>> Version specific API URLs:
>>>>>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>>>>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>>>>>
>>>>>>> Following changes to be done:
>>>>>>> - Update CLI and Dashboard
>>>>>>> - Allow API version to be specified in an HTTP header
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> We now have the docker-grouping-branch in a compilable state with
>>>>>>>> latests modifications. Please test all workflows related to service
>>>>>>>> grouping and docker, once things are stable will merge this branch to
>>>>>>>> master.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I have completed deploy-application, undeploy-application,
>>>>>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>>>>>> the changes to docker-grouping-merge branch. I'll compete the
>>>>>>>>> other commands as soon as possible and looks for the UI as well.
>>>>>>>>>
>>>>>>>>> Thanks !
>>>>>>>>>
>>>>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I have now fixed autoscaler service stub bundle exports and
>>>>>>>>>> stratos manager import statements. Currently working on Stratos Manager,
>>>>>>>>>> seems like there are duplicated domain classes:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>>>>>
>>>>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>>>>>
>>>>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Fixed AS issues
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <
>>>>>>>>>>> lasindu@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte
>>>>>>>>>>>> <ma...@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch
>>>>>>>>>>>>>>> to docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping]
>>>>>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> When and where are we creating and adding cluster
>>>>>>>>>>>>>>>>>> monitors (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>>>>>> Method)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>>>>>> - Passing properties from Application definition to
>>>>>>>>>>>>>>>>>>>>> the cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some
>>>>>>>>>>>>>>>>>>>>> of the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Please find the sample application definition file
>>>>>>>>>>>>>>>>>>>>> which I have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across
>>>>>>>>>>>>>>>>>>>>>> two partitions(in other words two kub cluster)? I guess kubernetes can
>>>>>>>>>>>>>>>>>>>>>> manage their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>>>
>>>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> *Lasindu Charith*
>>>>>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>>>>>> Mobile: +94714427192
>>>>>>>>>>>> Web: blog.lasindu.com
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Raj
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Regards,
>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>> Software Engineer
>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>
>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>> phone : +94 772492511
>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>> --
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>> * <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Raj
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> +94 716 358 048
>>>>
>>>> --
>>>> <%2B94%20716%20358%20048>
>>>> <%2B94%20716%20358%20048>
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> <%2B94%20716%20358%20048>
>>>> +94 716 358 048* <http://wso2.com/>*
>>>>
>>>>
>>>> * <http://wso2.com/>*
>>>>
>>>>
>>>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Gayan: Was there any reason for generating a client id for subscribers and
setting a fixed value for publishers?
TopicSubscriber.doSubscribe():
MqttClient mqttClient = MQTTConnector.getMQTTSubClient(Util.getRandomString(
5));
On Fri, Nov 7, 2014 at 1:17 PM, Isuru Haththotuwa <is...@apache.org> wrote:
>
>
> On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>>
>> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> I got containers to be created.
>>> But didn't get the member started event. Either agent is not sending or
>>> CC is not receiving. Looking into it currently.
>>>
>> I'm seeing this issue as well. The agent is sending the events, but
>> Stratos is not receiving them. Trying with a simple mqtt client now.
>>
> In [1], we are using the client id in mqtttopic.properties file as it is
> and using it to start the MQTTClient. However, in the wiki it says that
> client id should be unique across all publishers [2]. I might be missing
> something here, but is this case handled?
>
> [1]. org.apache.stratos.messaging.broker.connect.MQTTConnector
>
> [2].
> http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
> java.lang.String)
>
>
>>
>>> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Hi Isuru,
>>>>
>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>>> wrote:
>>>>
>>>>>
>>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>>> Stratos.
>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>>> might do the same, but that might not be the case always. Just my two
>>>>> cents.
>>>>>
>>>>>>
>>>>>>
>>>>>> A good point, I reviewed your concern before doing this modification,
>>>> most of the well known APIs do not include the product name in the context.
>>>> Rather as you have mentioned they use the hostname to identify the product,
>>>> please see below examples. This is why I removed "stratos" from the
>>>> context, WDYT?
>>>>
>>>> Facebook Graph API:
>>>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
>>>> Twitter API:
>>>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
>>>> Github API: https://developer.github.com/v3/
>>>> OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html
>>>> EC2 API:
>>>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
>>>> Google Cloud Compute API:
>>>> https://cloud.google.com/compute/docs/reference/latest/#Addresses
>>>> StackExchange API: https://api.stackexchange.com/docs/answers
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi Imesh,
>>>>>
>>>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Please note that we have now introduced API versioning in
>>>>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>>>>> follows, no changes were done to existing resource paths:
>>>>>>
>>>>>> Previous API URL:
>>>>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>>>>
>>>>>> New API URL:
>>>>>> https://{hostname}:{port}/api/{resource-path}
>>>>>>
>>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>>> Stratos.
>>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>>> might do the same, but that might not be the case always. Just my two
>>>>> cents.
>>>>>
>>>>>>
>>>>>> Version specific API URLs:
>>>>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>>>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>>>>
>>>>>> Following changes to be done:
>>>>>> - Update CLI and Dashboard
>>>>>> - Allow API version to be specified in an HTTP header
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> We now have the docker-grouping-branch in a compilable state with
>>>>>>> latests modifications. Please test all workflows related to service
>>>>>>> grouping and docker, once things are stable will merge this branch to
>>>>>>> master.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>>>>> manulac@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have completed deploy-application, undeploy-application,
>>>>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>>>>> the changes to docker-grouping-merge branch. I'll compete the
>>>>>>>> other commands as soon as possible and looks for the UI as well.
>>>>>>>>
>>>>>>>> Thanks !
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I have now fixed autoscaler service stub bundle exports and
>>>>>>>>> stratos manager import statements. Currently working on Stratos Manager,
>>>>>>>>> seems like there are duplicated domain classes:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>>>>
>>>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>>>>
>>>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>>>>
>>>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Fixed AS issues
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <lasindu@wso2.com
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch
>>>>>>>>>>>>>> to docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping]
>>>>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> When and where are we creating and adding cluster monitors
>>>>>>>>>>>>>>>>> (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>>>>> Method)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>>>>> - Passing properties from Application definition to the
>>>>>>>>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some
>>>>>>>>>>>>>>>>>>>> of the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Please find the sample application definition file
>>>>>>>>>>>>>>>>>>>> which I have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>>> Software Engineer
>>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>>
>>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> *Lasindu Charith*
>>>>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>>>>> Mobile: +94714427192
>>>>>>>>>>> Web: blog.lasindu.com
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Raj
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Regards,
>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>> Software Engineer
>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>> lean . enterprise . middleware
>>>>>>>>
>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>> phone : +94 772492511
>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>> --
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>> * <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Raj
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048
>>>
>>> --
>>> <%2B94%20716%20358%20048>
>>> <%2B94%20716%20358%20048>
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> <%2B94%20716%20358%20048>
>>> +94 716 358 048* <http://wso2.com/>*
>>>
>>>
>>> * <http://wso2.com/>*
>>>
>>>
>>>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa <is...@apache.org>
wrote:
>
> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> I got containers to be created.
>> But didn't get the member started event. Either agent is not sending or
>> CC is not receiving. Looking into it currently.
>>
> I'm seeing this issue as well. The agent is sending the events, but
> Stratos is not receiving them. Trying with a simple mqtt client now.
>
In [1], we are using the client id in mqtttopic.properties file as it is
and using it to start the MQTTClient. However, in the wiki it says that
client id should be unique across all publishers [2]. I might be missing
something here, but is this case handled?
[1]. org.apache.stratos.messaging.broker.connect.MQTTConnector
[2].
http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String,
java.lang.String)
>
>> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>>
>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>> Stratos.
>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>> might do the same, but that might not be the case always. Just my two
>>>> cents.
>>>>
>>>>>
>>>>>
>>>>> A good point, I reviewed your concern before doing this modification,
>>> most of the well known APIs do not include the product name in the context.
>>> Rather as you have mentioned they use the hostname to identify the product,
>>> please see below examples. This is why I removed "stratos" from the
>>> context, WDYT?
>>>
>>> Facebook Graph API:
>>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
>>> Twitter API:
>>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
>>> Github API: https://developer.github.com/v3/
>>> OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html
>>> EC2 API:
>>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
>>> Google Cloud Compute API:
>>> https://cloud.google.com/compute/docs/reference/latest/#Addresses
>>> StackExchange API: https://api.stackexchange.com/docs/answers
>>>
>>> Thanks
>>>
>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>> Hi Imesh,
>>>>
>>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Please note that we have now introduced API versioning in
>>>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>>>> follows, no changes were done to existing resource paths:
>>>>>
>>>>> Previous API URL:
>>>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>>>
>>>>> New API URL:
>>>>> https://{hostname}:{port}/api/{resource-path}
>>>>>
>>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>>> more intuitive. having just /api doesn't say that this API belongs to
>>>> Stratos.
>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>>> might do the same, but that might not be the case always. Just my two
>>>> cents.
>>>>
>>>>>
>>>>> Version specific API URLs:
>>>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>>>
>>>>> Following changes to be done:
>>>>> - Update CLI and Dashboard
>>>>> - Allow API version to be specified in an HTTP header
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> We now have the docker-grouping-branch in a compilable state with
>>>>>> latests modifications. Please test all workflows related to service
>>>>>> grouping and docker, once things are stable will merge this branch to
>>>>>> master.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>>>> manulac@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have completed deploy-application, undeploy-application,
>>>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>>>> the changes to docker-grouping-merge branch. I'll compete the other
>>>>>>> commands as soon as possible and looks for the UI as well.
>>>>>>>
>>>>>>> Thanks !
>>>>>>>
>>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I have now fixed autoscaler service stub bundle exports and stratos
>>>>>>>> manager import statements. Currently working on Stratos Manager, seems like
>>>>>>>> there are duplicated domain classes:
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>>>
>>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>>>
>>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Fixed AS issues
>>>>>>>>>
>>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>>>
>>>>>>>>>>> Thanks !
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>>>>>>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping]
>>>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> When and where are we creating and adding cluster monitors
>>>>>>>>>>>>>>>> (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>>>> Method)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>>>> - Passing properties from Application definition to the
>>>>>>>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some
>>>>>>>>>>>>>>>>>>> of the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Please find the sample application definition file which
>>>>>>>>>>>>>>>>>>> I have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Raj
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Regards,
>>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>>> Software Engineer
>>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>
>>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>>> phone : +94 772492511
>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> *Lasindu Charith*
>>>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>>>> Mobile: +94714427192
>>>>>>>>>> Web: blog.lasindu.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Raj
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Regards,
>>>>>>> Manula Chathurika Thantriwatte
>>>>>>> Software Engineer
>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>> lean . enterprise . middleware
>>>>>>>
>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>> phone : +94 772492511
>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>> --
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>
>>>>>
>>>>> * <http://wso2.com/>*
>>>>>
>>>>>
>>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Raj
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048
>>
>> --
>> <%2B94%20716%20358%20048>
>> <%2B94%20716%20358%20048>
>> Thanks and Regards,
>>
>> Isuru H.
>> <%2B94%20716%20358%20048>
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> I got containers to be created.
> But didn't get the member started event. Either agent is not sending or CC
> is not receiving. Looking into it currently.
>
I'm seeing this issue as well. The agent is sending the events, but Stratos
is not receiving them. Trying with a simple mqtt client now.
>
> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Hi Isuru,
>>
>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>>
>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>> more intuitive. having just /api doesn't say that this API belongs to
>>> Stratos.
>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>> might do the same, but that might not be the case always. Just my two
>>> cents.
>>>
>>>>
>>>>
>>>> A good point, I reviewed your concern before doing this modification,
>> most of the well known APIs do not include the product name in the context.
>> Rather as you have mentioned they use the hostname to identify the product,
>> please see below examples. This is why I removed "stratos" from the
>> context, WDYT?
>>
>> Facebook Graph API:
>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
>> Twitter API:
>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
>> Github API: https://developer.github.com/v3/
>> OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html
>> EC2 API:
>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
>> Google Cloud Compute API:
>> https://cloud.google.com/compute/docs/reference/latest/#Addresses
>> StackExchange API: https://api.stackexchange.com/docs/answers
>>
>> Thanks
>>
>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Please note that we have now introduced API versioning in
>>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>>> follows, no changes were done to existing resource paths:
>>>>
>>>> Previous API URL:
>>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>>
>>>> New API URL:
>>>> https://{hostname}:{port}/api/{resource-path}
>>>>
>>> IMHO we should have the context name 'stratos' in the url. Then it is
>>> more intuitive. having just /api doesn't say that this API belongs to
>>> Stratos.
>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>>> might do the same, but that might not be the case always. Just my two
>>> cents.
>>>
>>>>
>>>> Version specific API URLs:
>>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>>
>>>> Following changes to be done:
>>>> - Update CLI and Dashboard
>>>> - Allow API version to be specified in an HTTP header
>>>>
>>>> Thanks
>>>>
>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> We now have the docker-grouping-branch in a compilable state with
>>>>> latests modifications. Please test all workflows related to service
>>>>> grouping and docker, once things are stable will merge this branch to
>>>>> master.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>>> manulac@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have completed deploy-application, undeploy-application,
>>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>>> the changes to docker-grouping-merge branch. I'll compete the other
>>>>>> commands as soon as possible and looks for the UI as well.
>>>>>>
>>>>>> Thanks !
>>>>>>
>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I have now fixed autoscaler service stub bundle exports and stratos
>>>>>>> manager import statements. Currently working on Stratos Manager, seems like
>>>>>>> there are duplicated domain classes:
>>>>>>>
>>>>>>>
>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>>
>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>>
>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>>
>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> Fixed AS issues
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>>
>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>>
>>>>>>>>>> Thanks !
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>>>>>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>>
>>>>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping]
>>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> When and where are we creating and adding cluster monitors
>>>>>>>>>>>>>>> (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>>> Method)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>>> - Passing properties from Application definition to the
>>>>>>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some of
>>>>>>>>>>>>>>>>>> the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Please find the sample application definition file which
>>>>>>>>>>>>>>>>>> I have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Raj
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Regards,
>>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>>> Software Engineer
>>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>
>>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>>> phone : +94 772492511
>>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Lasindu Charith*
>>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>>> Mobile: +94714427192
>>>>>>>>> Web: blog.lasindu.com
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Raj
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Regards,
>>>>>> Manula Chathurika Thantriwatte
>>>>>> Software Engineer
>>>>>> WSO2 Inc. : http://wso2.com
>>>>>> lean . enterprise . middleware
>>>>>>
>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>> phone : +94 772492511
>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> +94 716 358 048* <http://wso2.com/>*
>>>>
>>>>
>>>> * <http://wso2.com/>*
>>>>
>>>>
>>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Raj
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
I got containers to be created.
But didn't get the member started event. Either agent is not sending or CC
is not receiving. Looking into it currently.
On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Isuru,
>
> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>>
>> IMHO we should have the context name 'stratos' in the url. Then it is
>> more intuitive. having just /api doesn't say that this API belongs to
>> Stratos.
>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>> might do the same, but that might not be the case always. Just my two
>> cents.
>>
>>>
>>>
>>> A good point, I reviewed your concern before doing this modification,
> most of the well known APIs do not include the product name in the context.
> Rather as you have mentioned they use the hostname to identify the product,
> please see below examples. This is why I removed "stratos" from the
> context, WDYT?
>
> Facebook Graph API:
> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
> Twitter API:
> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
> Github API: https://developer.github.com/v3/
> OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html
> EC2 API:
> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
> Google Cloud Compute API:
> https://cloud.google.com/compute/docs/reference/latest/#Addresses
> StackExchange API: https://api.stackexchange.com/docs/answers
>
> Thanks
>
> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>> Hi Imesh,
>>
>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Please note that we have now introduced API versioning in
>>> docker-grouping-merge branch. Now the REST API context has been changed as
>>> follows, no changes were done to existing resource paths:
>>>
>>> Previous API URL:
>>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>>
>>> New API URL:
>>> https://{hostname}:{port}/api/{resource-path}
>>>
>> IMHO we should have the context name 'stratos' in the url. Then it is
>> more intuitive. having just /api doesn't say that this API belongs to
>> Stratos.
>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
>> better IMHO. If we have a proper hostname (stratos.apache.org) this
>> might do the same, but that might not be the case always. Just my two
>> cents.
>>
>>>
>>> Version specific API URLs:
>>> https://{hostname}:{port}/api/v4.0/{resource-path}
>>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>>
>>> Following changes to be done:
>>> - Update CLI and Dashboard
>>> - Allow API version to be specified in an HTTP header
>>>
>>> Thanks
>>>
>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> We now have the docker-grouping-branch in a compilable state with
>>>> latests modifications. Please test all workflows related to service
>>>> grouping and docker, once things are stable will merge this branch to
>>>> master.
>>>>
>>>> Thanks
>>>>
>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>>> manulac@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have completed deploy-application, undeploy-application,
>>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>>> the changes to docker-grouping-merge branch. I'll compete the other
>>>>> commands as soon as possible and looks for the UI as well.
>>>>>
>>>>> Thanks !
>>>>>
>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I have now fixed autoscaler service stub bundle exports and stratos
>>>>>> manager import statements. Currently working on Stratos Manager, seems like
>>>>>> there are duplicated domain classes:
>>>>>>
>>>>>>
>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>>
>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>>
>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>>
>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>
>>>>>>> Fixed AS issues
>>>>>>>
>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>>
>>>>>>>>> Thanks !
>>>>>>>>>
>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>>>>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>>
>>>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping]
>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> When and where are we creating and adding cluster monitors
>>>>>>>>>>>>>> (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>> Method)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>>> - Passing properties from Application definition to the
>>>>>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some of
>>>>>>>>>>>>>>>>> the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Please find the sample application definition file which I
>>>>>>>>>>>>>>>>> have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>
>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Raj
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Regards,
>>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>>> Software Engineer
>>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>
>>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>>> phone : +94 772492511
>>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Lasindu Charith*
>>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>>> Mobile: +94714427192
>>>>>>>> Web: blog.lasindu.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Raj
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Manula Chathurika Thantriwatte
>>>>> Software Engineer
>>>>> WSO2 Inc. : http://wso2.com
>>>>> lean . enterprise . middleware
>>>>>
>>>>> email : manulac@wso2.com / manula@apache.org
>>>>> phone : +94 772492511
>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* <http://wso2.com/>*
>>>
>>>
>>> * <http://wso2.com/>*
>>>
>>>
>>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Isuru,
On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
wrote:
>
> IMHO we should have the context name 'stratos' in the url. Then it is more
> intuitive. having just /api doesn't say that this API belongs to Stratos.
> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
> better IMHO. If we have a proper hostname (stratos.apache.org) this might
> do the same, but that might not be the case always. Just my two cents.
>
>>
>>
>> A good point, I reviewed your concern before doing this modification,
most of the well known APIs do not include the product name in the context.
Rather as you have mentioned they use the hostname to identify the product,
please see below examples. This is why I removed "stratos" from the
context, WDYT?
Facebook Graph API:
https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2
Twitter API:
https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline
Github API: https://developer.github.com/v3/
OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html
EC2 API:
http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
Google Cloud Compute API:
https://cloud.google.com/compute/docs/reference/latest/#Addresses
StackExchange API: https://api.stackexchange.com/docs/answers
Thanks
On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <is...@apache.org>
wrote:
> Hi Imesh,
>
> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Please note that we have now introduced API versioning in
>> docker-grouping-merge branch. Now the REST API context has been changed as
>> follows, no changes were done to existing resource paths:
>>
>> Previous API URL:
>> https://{hostname}:{port}/stratos/admin/{resource-path}
>>
>> New API URL:
>> https://{hostname}:{port}/api/{resource-path}
>>
> IMHO we should have the context name 'stratos' in the url. Then it is more
> intuitive. having just /api doesn't say that this API belongs to Stratos.
> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is
> better IMHO. If we have a proper hostname (stratos.apache.org) this might
> do the same, but that might not be the case always. Just my two cents.
>
>>
>> Version specific API URLs:
>> https://{hostname}:{port}/api/v4.0/{resource-path}
>> https://{hostname}:{port}/api/v4.1/{resource-path}
>>
>> Following changes to be done:
>> - Update CLI and Dashboard
>> - Allow API version to be specified in an HTTP header
>>
>> Thanks
>>
>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> We now have the docker-grouping-branch in a compilable state with
>>> latests modifications. Please test all workflows related to service
>>> grouping and docker, once things are stable will merge this branch to
>>> master.
>>>
>>> Thanks
>>>
>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>>> manulac@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have completed deploy-application, undeploy-application,
>>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>>> the changes to docker-grouping-merge branch. I'll compete the other
>>>> commands as soon as possible and looks for the UI as well.
>>>>
>>>> Thanks !
>>>>
>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I have now fixed autoscaler service stub bundle exports and stratos
>>>>> manager import statements. Currently working on Stratos Manager, seems like
>>>>> there are duplicated domain classes:
>>>>>
>>>>>
>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>>
>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>>
>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>>
>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <
>>>>> rajkumarr@wso2.com> wrote:
>>>>>
>>>>>> Fixed AS issues
>>>>>>
>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>>
>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>>>>>> manulac@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have started on grouping CLI commands.
>>>>>>>>
>>>>>>>> Thanks !
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Fixed messaging component issues.
>>>>>>>>>
>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>>>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>>
>>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping] Branch
>>>>>>>>>>> may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> When and where are we creating and adding cluster monitors
>>>>>>>>>>>>> (not app monitors) to the AutoscalerContext?
>>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition
>>>>>>>>>>>>>>> without properties, looking into it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>> Method)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>>> - Passing properties from Application definition to the
>>>>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some of
>>>>>>>>>>>>>>>> the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Please find the sample application definition file which I
>>>>>>>>>>>>>>>> have been using for testing attached with this mail.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos,
>>>>>>>>>>>>>>>>> shouldn't be a problem.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Raj
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> --
>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>
>>>>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>>>>> linked-in:
>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Raj
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Regards,
>>>>>>>> Manula Chathurika Thantriwatte
>>>>>>>> Software Engineer
>>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>>> lean . enterprise . middleware
>>>>>>>>
>>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>>> phone : +94 772492511
>>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Lasindu Charith*
>>>>>>> Software Engineer, WSO2 Inc.
>>>>>>> Mobile: +94714427192
>>>>>>> Web: blog.lasindu.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Raj
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Manula Chathurika Thantriwatte
>>>> Software Engineer
>>>> WSO2 Inc. : http://wso2.com
>>>> lean . enterprise . middleware
>>>>
>>>> email : manulac@wso2.com / manula@apache.org
>>>> phone : +94 772492511
>>>> blog : http://manulachathurika.blogspot.com/
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
Hi Imesh,
On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Please note that we have now introduced API versioning in
> docker-grouping-merge branch. Now the REST API context has been changed as
> follows, no changes were done to existing resource paths:
>
> Previous API URL:
> https://{hostname}:{port}/stratos/admin/{resource-path}
>
> New API URL:
> https://{hostname}:{port}/api/{resource-path}
>
IMHO we should have the context name 'stratos' in the url. Then it is more
intuitive. having just /api doesn't say that this API belongs to Stratos.
Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is better
IMHO. If we have a proper hostname (stratos.apache.org) this might do the
same, but that might not be the case always. Just my two cents.
>
> Version specific API URLs:
> https://{hostname}:{port}/api/v4.0/{resource-path}
> https://{hostname}:{port}/api/v4.1/{resource-path}
>
> Following changes to be done:
> - Update CLI and Dashboard
> - Allow API version to be specified in an HTTP header
>
> Thanks
>
> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> We now have the docker-grouping-branch in a compilable state with latests
>> modifications. Please test all workflows related to service grouping and
>> docker, once things are stable will merge this branch to master.
>>
>> Thanks
>>
>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>> manulac@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I have completed deploy-application, undeploy-application,
>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>> the changes to docker-grouping-merge branch. I'll compete the other
>>> commands as soon as possible and looks for the UI as well.
>>>
>>> Thanks !
>>>
>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I have now fixed autoscaler service stub bundle exports and stratos
>>>> manager import statements. Currently working on Stratos Manager, seems like
>>>> there are duplicated domain classes:
>>>>
>>>>
>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>
>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>
>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>
>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>>> > wrote:
>>>>
>>>>> Fixed AS issues
>>>>>
>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>
>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>>>>> manulac@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have started on grouping CLI commands.
>>>>>>>
>>>>>>> Thanks !
>>>>>>>
>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> Fixed messaging component issues.
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>
>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping] Branch
>>>>>>>>>> may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>
>>>>>>>>>>> Thanks.
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> When and where are we creating and adding cluster monitors (not
>>>>>>>>>>>> app monitors) to the AutoscalerContext?
>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition without
>>>>>>>>>>>>>> properties, looking into it.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>> - Passing properties from Application definition to the
>>>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some of
>>>>>>>>>>>>>>> the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Please find the sample application definition file which I
>>>>>>>>>>>>>>> have been using for testing attached with this mail.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't
>>>>>>>>>>>>>>>> be a problem.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>
>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Raj
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> --
>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>
>>>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>>>> linked-in:
>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Raj
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Regards,
>>>>>>> Manula Chathurika Thantriwatte
>>>>>>> Software Engineer
>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>> lean . enterprise . middleware
>>>>>>>
>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>> phone : +94 772492511
>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Lasindu Charith*
>>>>>> Software Engineer, WSO2 Inc.
>>>>>> Mobile: +94714427192
>>>>>> Web: blog.lasindu.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Raj
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Regards,
>>> Manula Chathurika Thantriwatte
>>> Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> email : manulac@wso2.com / manula@apache.org
>>> phone : +94 772492511
>>> blog : http://manulachathurika.blogspot.com/
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi Imesh,
I'll update the CLI with the new API versioning.
Thanks !
On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Please note that we have now introduced API versioning in
> docker-grouping-merge branch. Now the REST API context has been changed as
> follows, no changes were done to existing resource paths:
>
> Previous API URL:
> https://{hostname}:{port}/stratos/admin/{resource-path}
>
> New API URL:
> https://{hostname}:{port}/api/{resource-path}
>
> Version specific API URLs:
> https://{hostname}:{port}/api/v4.0/{resource-path}
> https://{hostname}:{port}/api/v4.1/{resource-path}
>
> Following changes to be done:
> - Update CLI and Dashboard
> - Allow API version to be specified in an HTTP header
>
> Thanks
>
> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> We now have the docker-grouping-branch in a compilable state with latests
>> modifications. Please test all workflows related to service grouping and
>> docker, once things are stable will merge this branch to master.
>>
>> Thanks
>>
>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
>> manulac@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I have completed deploy-application, undeploy-application,
>>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>>> the changes to docker-grouping-merge branch. I'll compete the other
>>> commands as soon as possible and looks for the UI as well.
>>>
>>> Thanks !
>>>
>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I have now fixed autoscaler service stub bundle exports and stratos
>>>> manager import statements. Currently working on Stratos Manager, seems like
>>>> there are duplicated domain classes:
>>>>
>>>>
>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>>
>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>>
>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>>
>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>>> > wrote:
>>>>
>>>>> Fixed AS issues
>>>>>
>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>>
>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>>>>> manulac@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have started on grouping CLI commands.
>>>>>>>
>>>>>>> Thanks !
>>>>>>>
>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> Fixed messaging component issues.
>>>>>>>>
>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>>> docker-grouping-merge branch.
>>>>>>>>>
>>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping] Branch
>>>>>>>>>> may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>>
>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>>
>>>>>>>>>>> Thanks.
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> When and where are we creating and adding cluster monitors (not
>>>>>>>>>>>> app monitors) to the AutoscalerContext?
>>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition without
>>>>>>>>>>>>>> properties, looking into it.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>>> - Passing properties from Application definition to the
>>>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some of
>>>>>>>>>>>>>>> the files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Please find the sample application definition file which I
>>>>>>>>>>>>>>> have been using for testing attached with this mail.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't
>>>>>>>>>>>>>>>> be a problem.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>
>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Raj
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> --
>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>
>>>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>>>> linked-in:
>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Raj
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Regards,
>>>>>>> Manula Chathurika Thantriwatte
>>>>>>> Software Engineer
>>>>>>> WSO2 Inc. : http://wso2.com
>>>>>>> lean . enterprise . middleware
>>>>>>>
>>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>>> phone : +94 772492511
>>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Lasindu Charith*
>>>>>> Software Engineer, WSO2 Inc.
>>>>>> Mobile: +94714427192
>>>>>> Web: blog.lasindu.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Raj
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Regards,
>>> Manula Chathurika Thantriwatte
>>> Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> email : manulac@wso2.com / manula@apache.org
>>> phone : +94 772492511
>>> blog : http://manulachathurika.blogspot.com/
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware
email : manulac@wso2.com / manula@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Please note that we have now introduced API versioning in
docker-grouping-merge branch. Now the REST API context has been changed as
follows, no changes were done to existing resource paths:
Previous API URL:
https://{hostname}:{port}/stratos/admin/{resource-path}
New API URL:
https://{hostname}:{port}/api/{resource-path}
Version specific API URLs:
https://{hostname}:{port}/api/v4.0/{resource-path}
https://{hostname}:{port}/api/v4.1/{resource-path}
Following changes to be done:
- Update CLI and Dashboard
- Allow API version to be specified in an HTTP header
Thanks
On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org> wrote:
> We now have the docker-grouping-branch in a compilable state with latests
> modifications. Please test all workflows related to service grouping and
> docker, once things are stable will merge this branch to master.
>
> Thanks
>
> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
> manulac@wso2.com> wrote:
>
>> Hi,
>>
>> I have completed deploy-application, undeploy-application,
>> deploy-service-group and undeploy-service-group commands in CLI and pushed
>> the changes to docker-grouping-merge branch. I'll compete the other
>> commands as soon as possible and looks for the UI as well.
>>
>> Thanks !
>>
>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> I have now fixed autoscaler service stub bundle exports and stratos
>>> manager import statements. Currently working on Stratos Manager, seems like
>>> there are duplicated domain classes:
>>>
>>>
>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>>
>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>>
>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>>
>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>>> wrote:
>>>
>>>> Fixed AS issues
>>>>
>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com>
>>>> wrote:
>>>>
>>>>> I have fixed some compilation errors in Cloud Controller.
>>>>>
>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>>>> manulac@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have started on grouping CLI commands.
>>>>>>
>>>>>> Thanks !
>>>>>>
>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>
>>>>>>> Fixed messaging component issues.
>>>>>>>
>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>>>>> docker-grouping-merge branch.
>>>>>>>>
>>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping] Branch
>>>>>>>>> may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>>
>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> I have tested grouping feature in EC2 up to instance are
>>>>>>>>>> spawning. Will be testing further.
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> When and where are we creating and adding cluster monitors (not
>>>>>>>>>>> app monitors) to the AutoscalerContext?
>>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>>
>>>>>>>>>>> Thanks.
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition without
>>>>>>>>>>>>> properties, looking into it.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>>
>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>>
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>>> - Passing properties from Application definition to the
>>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some of the
>>>>>>>>>>>>>> files were placed in repository/conf while the rest were at
>>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please find the sample application definition file which I
>>>>>>>>>>>>>> have been using for testing attached with this mail.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't
>>>>>>>>>>>>>>> be a problem.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>>
>>>>>>>>>>>>> email: lahirus@wso2.com blog:
>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/
>>>>>>>>>>>>> linked-in:
>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> --
>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>
>>>>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>>>>> linked-in:
>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Raj
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> --
>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>
>>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>>> linked-in:
>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Raj
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Regards,
>>>>>> Manula Chathurika Thantriwatte
>>>>>> Software Engineer
>>>>>> WSO2 Inc. : http://wso2.com
>>>>>> lean . enterprise . middleware
>>>>>>
>>>>>> email : manulac@wso2.com / manula@apache.org
>>>>>> phone : +94 772492511
>>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Lasindu Charith*
>>>>> Software Engineer, WSO2 Inc.
>>>>> Mobile: +94714427192
>>>>> Web: blog.lasindu.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Raj
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Regards,
>> Manula Chathurika Thantriwatte
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>> lean . enterprise . middleware
>>
>> email : manulac@wso2.com / manula@apache.org
>> phone : +94 772492511
>> blog : http://manulachathurika.blogspot.com/
>>
>>
>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
We now have the docker-grouping-branch in a compilable state with latests
modifications. Please test all workflows related to service grouping and
docker, once things are stable will merge this branch to master.
Thanks
On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi,
>
> I have completed deploy-application, undeploy-application,
> deploy-service-group and undeploy-service-group commands in CLI and pushed
> the changes to docker-grouping-merge branch. I'll compete the other
> commands as soon as possible and looks for the UI as well.
>
> Thanks !
>
> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I have now fixed autoscaler service stub bundle exports and stratos
>> manager import statements. Currently working on Stratos Manager, seems like
>> there are duplicated domain classes:
>>
>>
>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>>
>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>>
>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>>
>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> Fixed AS issues
>>>
>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com>
>>> wrote:
>>>
>>>> I have fixed some compilation errors in Cloud Controller.
>>>>
>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>>> manulac@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have started on grouping CLI commands.
>>>>>
>>>>> Thanks !
>>>>>
>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <
>>>>> rajkumarr@wso2.com> wrote:
>>>>>
>>>>>> Fixed messaging component issues.
>>>>>>
>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>>>> docker-grouping-merge branch.
>>>>>>>
>>>>>>> Once features are stable will move changes to master branch.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Isuru is working on a major refactoring task ("[Grouping] Branch
>>>>>>>> may be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>>
>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <
>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> I have tested grouping feature in EC2 up to instance are spawning.
>>>>>>>>> Will be testing further.
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> When and where are we creating and adding cluster monitors (not
>>>>>>>>>> app monitors) to the AutoscalerContext?
>>>>>>>>>> I couldn't find any places.
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I get a NPE while trying to deploy the app definition without
>>>>>>>>>>>> properties, looking into it.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>>
>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>>> - Internal server error
>>>>>>>>>>>>
>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>>
>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>
>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>>
>>>>>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>>> - Passing properties from Application definition to the
>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes.
>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some of the
>>>>>>>>>>>>> files were placed in repository/conf while the rest were at
>>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please find the sample application definition file which I
>>>>>>>>>>>>> have been using for testing attached with this mail.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't
>>>>>>>>>>>>>> be a problem.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> --
>>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>>
>>>>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>>>>> linked-in:
>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> --
>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>
>>>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>>>> linked-in:
>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Raj
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> --
>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>> Senior Software Engineer,
>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>
>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Raj
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Manula Chathurika Thantriwatte
>>>>> Software Engineer
>>>>> WSO2 Inc. : http://wso2.com
>>>>> lean . enterprise . middleware
>>>>>
>>>>> email : manulac@wso2.com / manula@apache.org
>>>>> phone : +94 772492511
>>>>> blog : http://manulachathurika.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Lasindu Charith*
>>>> Software Engineer, WSO2 Inc.
>>>> Mobile: +94714427192
>>>> Web: blog.lasindu.com
>>>>
>>>
>>>
>>>
>>> --
>>> Raj
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> email : manulac@wso2.com / manula@apache.org
> phone : +94 772492511
> blog : http://manulachathurika.blogspot.com/
>
>
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi,
I have completed deploy-application, undeploy-application,
deploy-service-group and undeploy-service-group commands in CLI and pushed
the changes to docker-grouping-merge branch. I'll compete the other
commands as soon as possible and looks for the UI as well.
Thanks !
On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I have now fixed autoscaler service stub bundle exports and stratos
> manager import statements. Currently working on Stratos Manager, seems like
> there are duplicated domain classes:
>
>
> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
>
> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
>
> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
>
> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Fixed AS issues
>>
>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com> wrote:
>>
>>> I have fixed some compilation errors in Cloud Controller.
>>>
>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>>> manulac@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have started on grouping CLI commands.
>>>>
>>>> Thanks !
>>>>
>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>>> > wrote:
>>>>
>>>>> Fixed messaging component issues.
>>>>>
>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>>> docker-grouping-merge branch.
>>>>>>
>>>>>> Once features are stable will move changes to master branch.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Isuru is working on a major refactoring task ("[Grouping] Branch may
>>>>>>> be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>>
>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <lahirus@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> I have tested grouping feature in EC2 up to instance are spawning.
>>>>>>>> Will be testing further.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> When and where are we creating and adding cluster monitors (not
>>>>>>>>> app monitors) to the AutoscalerContext?
>>>>>>>>> I couldn't find any places.
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <
>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I get a NPE while trying to deploy the app definition without
>>>>>>>>>>> properties, looking into it.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>>
>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>>> - Internal server error
>>>>>>>>>>>
>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>>
>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>
>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>>
>>>>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>>> - Passing properties from Application definition to the cluster
>>>>>>>>>>>> objects. This is needed for Kubernetes.
>>>>>>>>>>>> - Packaging drools files in stratos distribution (some of the
>>>>>>>>>>>> files were placed in repository/conf while the rest were at
>>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>>
>>>>>>>>>>>> Please find the sample application definition file which I have
>>>>>>>>>>>> been using for testing attached with this mail.
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't be
>>>>>>>>>>>>> a problem.
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> --
>>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>>
>>>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>>>> linked-in:
>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> --
>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>
>>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>>> linked-in:
>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Raj
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> --
>>>>>>>> Lahiru Sandaruwan
>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>> Senior Software Engineer,
>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>> lean.enterprise.middleware
>>>>>>>>
>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Raj
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Manula Chathurika Thantriwatte
>>>> Software Engineer
>>>> WSO2 Inc. : http://wso2.com
>>>> lean . enterprise . middleware
>>>>
>>>> email : manulac@wso2.com / manula@apache.org
>>>> phone : +94 772492511
>>>> blog : http://manulachathurika.blogspot.com/
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Lasindu Charith*
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94714427192
>>> Web: blog.lasindu.com
>>>
>>
>>
>>
>> --
>> Raj
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware
email : manulac@wso2.com / manula@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
I have now fixed autoscaler service stub bundle exports and stratos manager
import statements. Currently working on Stratos Manager, seems like there
are duplicated domain classes:
org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java
org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java
org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java
On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Fixed AS issues
>
> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com> wrote:
>
>> I have fixed some compilation errors in Cloud Controller.
>>
>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
>> manulac@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I have started on grouping CLI commands.
>>>
>>> Thanks !
>>>
>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>>> wrote:
>>>
>>>> Fixed messaging component issues.
>>>>
>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>>> docker-grouping-merge branch.
>>>>>
>>>>> Once features are stable will move changes to master branch.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Isuru is working on a major refactoring task ("[Grouping] Branch may
>>>>>> be Unstable ATM"). Will hold this effort until that is completed.
>>>>>>
>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <la...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I have tested grouping feature in EC2 up to instance are spawning.
>>>>>>> Will be testing further.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> When and where are we creating and adding cluster monitors (not app
>>>>>>>> monitors) to the AutoscalerContext?
>>>>>>>> I couldn't find any places.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <lahirus@wso2.com
>>>>>>>> > wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <
>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> I get a NPE while trying to deploy the app definition without
>>>>>>>>>> properties, looking into it.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>>
>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>>> - Internal server error
>>>>>>>>>>
>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>>
>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>
>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>>
>>>>>>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>>
>>>>>>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>>
>>>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>
>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>>> - Passing properties from Application definition to the cluster
>>>>>>>>>>> objects. This is needed for Kubernetes.
>>>>>>>>>>> - Packaging drools files in stratos distribution (some of the
>>>>>>>>>>> files were placed in repository/conf while the rest were at
>>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>>
>>>>>>>>>>> Please find the sample application definition file which I have
>>>>>>>>>>> been using for testing attached with this mail.
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>>> missing something here?
>>>>>>>>>>>>
>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't be
>>>>>>>>>>>> a problem.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> --
>>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>>
>>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>>> linked-in:
>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> --
>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>> Senior Software Engineer,
>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>
>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Raj
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> --
>>>>>>> Lahiru Sandaruwan
>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>> lean.enterprise.middleware
>>>>>>>
>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Raj
>>>>
>>>
>>>
>>>
>>> --
>>> Regards,
>>> Manula Chathurika Thantriwatte
>>> Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> email : manulac@wso2.com / manula@apache.org
>>> phone : +94 772492511
>>> blog : http://manulachathurika.blogspot.com/
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Lasindu Charith*
>> Software Engineer, WSO2 Inc.
>> Mobile: +94714427192
>> Web: blog.lasindu.com
>>
>
>
>
> --
> Raj
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Fixed AS issues
On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <la...@wso2.com> wrote:
> I have fixed some compilation errors in Cloud Controller.
>
> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
> manulac@wso2.com> wrote:
>
>> Hi,
>>
>> I have started on grouping CLI commands.
>>
>> Thanks !
>>
>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> Fixed messaging component issues.
>>>
>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I have now merged latest changes from 4.0.0-grouping branch to
>>>> docker-grouping-merge branch. We can now fix merge issues in
>>>> docker-grouping-merge branch.
>>>>
>>>> Once features are stable will move changes to master branch.
>>>>
>>>> Thanks
>>>>
>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Isuru is working on a major refactoring task ("[Grouping] Branch may
>>>>> be Unstable ATM"). Will hold this effort until that is completed.
>>>>>
>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <la...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> I have tested grouping feature in EC2 up to instance are spawning.
>>>>>> Will be testing further.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> When and where are we creating and adding cluster monitors (not app
>>>>>>> monitors) to the AutoscalerContext?
>>>>>>> I couldn't find any places.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <lahirus@wso2.com
>>>>>>>> > wrote:
>>>>>>>>
>>>>>>>>> I get a NPE while trying to deploy the app definition without
>>>>>>>>> properties, looking into it.
>>>>>>>>>
>>>>>>>>>
>>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>>
>>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>>> - Internal server error
>>>>>>>>>
>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>>
>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>
>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>>
>>>>>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>>
>>>>>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>>
>>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>
>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I have now fixed few more issues:
>>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>>> - Adding isKubernetesCluster property to
>>>>>>>>>> ApplicationClusterContext.
>>>>>>>>>> - Passing properties from Application definition to the cluster
>>>>>>>>>> objects. This is needed for Kubernetes.
>>>>>>>>>> - Packaging drools files in stratos distribution (some of the
>>>>>>>>>> files were placed in repository/conf while the rest were at
>>>>>>>>>> repository/conf/drools).
>>>>>>>>>>
>>>>>>>>>> Please find the sample application definition file which I have
>>>>>>>>>> been using for testing attached with this mail.
>>>>>>>>>>
>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>>> missing something here?
>>>>>>>>>>>
>>>>>>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't be a
>>>>>>>>>>> problem.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> --
>>>>>>>>> Lahiru Sandaruwan
>>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>>> Senior Software Engineer,
>>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>
>>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> --
>>>>>>>> Lahiru Sandaruwan
>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>> Senior Software Engineer,
>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>> lean.enterprise.middleware
>>>>>>>>
>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Raj
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> Lahiru Sandaruwan
>>>>>> Committer and PMC member, Apache Stratos,
>>>>>> Senior Software Engineer,
>>>>>> WSO2 Inc., http://wso2.com
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Raj
>>>
>>
>>
>>
>> --
>> Regards,
>> Manula Chathurika Thantriwatte
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>> lean . enterprise . middleware
>>
>> email : manulac@wso2.com / manula@apache.org
>> phone : +94 772492511
>> blog : http://manulachathurika.blogspot.com/
>>
>>
>>
>>
>
>
> --
> *Lasindu Charith*
> Software Engineer, WSO2 Inc.
> Mobile: +94714427192
> Web: blog.lasindu.com
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lasindu Charith <la...@wso2.com>.
I have fixed some compilation errors in Cloud Controller.
On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi,
>
> I have started on grouping CLI commands.
>
> Thanks !
>
> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Fixed messaging component issues.
>>
>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> I have now merged latest changes from 4.0.0-grouping branch to
>>> docker-grouping-merge branch. We can now fix merge issues in
>>> docker-grouping-merge branch.
>>>
>>> Once features are stable will move changes to master branch.
>>>
>>> Thanks
>>>
>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Isuru is working on a major refactoring task ("[Grouping] Branch may be
>>>> Unstable ATM"). Will hold this effort until that is completed.
>>>>
>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <la...@wso2.com>
>>>> wrote:
>>>>
>>>>> I have tested grouping feature in EC2 up to instance are spawning.
>>>>> Will be testing further.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <
>>>>> rajkumarr@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> When and where are we creating and adding cluster monitors (not app
>>>>>> monitors) to the AutoscalerContext?
>>>>>> I couldn't find any places.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I get a NPE while trying to deploy the app definition without
>>>>>>>> properties, looking into it.
>>>>>>>>
>>>>>>>>
>>>>>>> I have added a null check. Will commit the fix.
>>>>>>>
>>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>>> - Internal server error
>>>>>>>>
>>>>>>>> java.lang.NullPointerException
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>>
>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>
>>>>>>>> at
>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>
>>>>>>>> at
>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>
>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>>
>>>>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>>
>>>>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>>
>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>
>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I have now fixed few more issues:
>>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>>> - Adding isKubernetesCluster property to ApplicationClusterContext.
>>>>>>>>> - Passing properties from Application definition to the cluster
>>>>>>>>> objects. This is needed for Kubernetes.
>>>>>>>>> - Packaging drools files in stratos distribution (some of the
>>>>>>>>> files were placed in repository/conf while the rest were at
>>>>>>>>> repository/conf/drools).
>>>>>>>>>
>>>>>>>>> Please find the sample application definition file which I have
>>>>>>>>> been using for testing attached with this mail.
>>>>>>>>>
>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>>> missing something here?
>>>>>>>>>>
>>>>>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't be a
>>>>>>>>>> problem.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> --
>>>>>>>> Lahiru Sandaruwan
>>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>>> Senior Software Engineer,
>>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>>> lean.enterprise.middleware
>>>>>>>>
>>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> --
>>>>>>> Lahiru Sandaruwan
>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>> lean.enterprise.middleware
>>>>>>>
>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Raj
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> Lahiru Sandaruwan
>>>>> Committer and PMC member, Apache Stratos,
>>>>> Senior Software Engineer,
>>>>> WSO2 Inc., http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Raj
>>
>
>
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> email : manulac@wso2.com / manula@apache.org
> phone : +94 772492511
> blog : http://manulachathurika.blogspot.com/
>
>
>
>
--
*Lasindu Charith*
Software Engineer, WSO2 Inc.
Mobile: +94714427192
Web: blog.lasindu.com
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi,
I have started on grouping CLI commands.
Thanks !
On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Fixed messaging component issues.
>
> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I have now merged latest changes from 4.0.0-grouping branch to
>> docker-grouping-merge branch. We can now fix merge issues in
>> docker-grouping-merge branch.
>>
>> Once features are stable will move changes to master branch.
>>
>> Thanks
>>
>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Isuru is working on a major refactoring task ("[Grouping] Branch may be
>>> Unstable ATM"). Will hold this effort until that is completed.
>>>
>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <la...@wso2.com>
>>> wrote:
>>>
>>>> I have tested grouping feature in EC2 up to instance are spawning. Will
>>>> be testing further.
>>>>
>>>> Thanks.
>>>>
>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>>> > wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> When and where are we creating and adding cluster monitors (not app
>>>>> monitors) to the AutoscalerContext?
>>>>> I couldn't find any places.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I get a NPE while trying to deploy the app definition without
>>>>>>> properties, looking into it.
>>>>>>>
>>>>>>>
>>>>>> I have added a null check. Will commit the fix.
>>>>>>
>>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>>> - Internal server error
>>>>>>>
>>>>>>> java.lang.NullPointerException
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>>
>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>
>>>>>>> at
>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>
>>>>>>> at
>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>>
>>>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>>
>>>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>>
>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>
>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I have now fixed few more issues:
>>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>>> - Adding isKubernetesCluster property to ApplicationClusterContext.
>>>>>>>> - Passing properties from Application definition to the cluster
>>>>>>>> objects. This is needed for Kubernetes.
>>>>>>>> - Packaging drools files in stratos distribution (some of the files
>>>>>>>> were placed in repository/conf while the rest were at
>>>>>>>> repository/conf/drools).
>>>>>>>>
>>>>>>>> Please find the sample application definition file which I have
>>>>>>>> been using for testing attached with this mail.
>>>>>>>>
>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>>> missing something here?
>>>>>>>>>
>>>>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't be a
>>>>>>>>> problem.
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> --
>>>>>>> Lahiru Sandaruwan
>>>>>>> Committer and PMC member, Apache Stratos,
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>> lean.enterprise.middleware
>>>>>>>
>>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> Lahiru Sandaruwan
>>>>>> Committer and PMC member, Apache Stratos,
>>>>>> Senior Software Engineer,
>>>>>> WSO2 Inc., http://wso2.com
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Raj
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Committer and PMC member, Apache Stratos,
>>>> Senior Software Engineer,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Raj
>
--
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware
email : manulac@wso2.com / manula@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Fixed messaging component issues.
On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I have now merged latest changes from 4.0.0-grouping branch to
> docker-grouping-merge branch. We can now fix merge issues in
> docker-grouping-merge branch.
>
> Once features are stable will move changes to master branch.
>
> Thanks
>
> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Isuru is working on a major refactoring task ("[Grouping] Branch may be
>> Unstable ATM"). Will hold this effort until that is completed.
>>
>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <la...@wso2.com>
>> wrote:
>>
>>> I have tested grouping feature in EC2 up to instance are spawning. Will
>>> be testing further.
>>>
>>> Thanks.
>>>
>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> When and where are we creating and adding cluster monitors (not app
>>>> monitors) to the AutoscalerContext?
>>>> I couldn't find any places.
>>>>
>>>> Thanks.
>>>>
>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> I get a NPE while trying to deploy the app definition without
>>>>>> properties, looking into it.
>>>>>>
>>>>>>
>>>>> I have added a null check. Will commit the fix.
>>>>>
>>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>>> - Internal server error
>>>>>>
>>>>>> java.lang.NullPointerException
>>>>>>
>>>>>> at
>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>>
>>>>>> at
>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>>
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>
>>>>>> at
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>
>>>>>> at
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>
>>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>>
>>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>>
>>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>>
>>>>>> at
>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>
>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I have now fixed few more issues:
>>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>>> - Adding isKubernetesCluster property to ApplicationClusterContext.
>>>>>>> - Passing properties from Application definition to the cluster
>>>>>>> objects. This is needed for Kubernetes.
>>>>>>> - Packaging drools files in stratos distribution (some of the files
>>>>>>> were placed in repository/conf while the rest were at
>>>>>>> repository/conf/drools).
>>>>>>>
>>>>>>> Please find the sample application definition file which I have been
>>>>>>> using for testing attached with this mail.
>>>>>>>
>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Can a service cluster(say php cluster) span across two
>>>>>>>> partitions(in other words two kub cluster)? I guess kubernetes can manage
>>>>>>>> their containers within a kub cluster, not between kub clusters? For
>>>>>>>> example, if we say we need 3 replicas, it can ensure there are 3 replicas
>>>>>>>> in one kub cluster. It can't manage 3 replicas within two kub cluster. Am I
>>>>>>>> missing something here?
>>>>>>>>
>>>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't be a
>>>>>>>> problem.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> Lahiru Sandaruwan
>>>>>> Committer and PMC member, Apache Stratos,
>>>>>> Senior Software Engineer,
>>>>>> WSO2 Inc., http://wso2.com
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> Lahiru Sandaruwan
>>>>> Committer and PMC member, Apache Stratos,
>>>>> Senior Software Engineer,
>>>>> WSO2 Inc., http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Raj
>>>>
>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Committer and PMC member, Apache Stratos,
>>> Senior Software Engineer,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
I have now merged latest changes from 4.0.0-grouping branch to
docker-grouping-merge branch. We can now fix merge issues in
docker-grouping-merge branch.
Once features are stable will move changes to master branch.
Thanks
On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Isuru is working on a major refactoring task ("[Grouping] Branch may be
> Unstable ATM"). Will hold this effort until that is completed.
>
> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <la...@wso2.com>
> wrote:
>
>> I have tested grouping feature in EC2 up to instance are spawning. Will
>> be testing further.
>>
>> Thanks.
>>
>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> When and where are we creating and adding cluster monitors (not app
>>> monitors) to the AutoscalerContext?
>>> I couldn't find any places.
>>>
>>> Thanks.
>>>
>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <la...@wso2.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>> wrote:
>>>>
>>>>> I get a NPE while trying to deploy the app definition without
>>>>> properties, looking into it.
>>>>>
>>>>>
>>>> I have added a null check. Will commit the fix.
>>>>
>>>>> [2014-11-01 20:17:18,922] ERROR
>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>>> - Internal server error
>>>>>
>>>>> java.lang.NullPointerException
>>>>>
>>>>> at
>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>>
>>>>> at
>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>>
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>
>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>
>>>>> at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>
>>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>>
>>>>> at
>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>>
>>>>> at
>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>>
>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>>
>>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>>
>>>>> at
>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>>
>>>>> at
>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>>
>>>>> at
>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>>
>>>>> at
>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>>
>>>>> at
>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>>
>>>>> at
>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>>
>>>>> at
>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>>
>>>>> at
>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>>
>>>>> at
>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>>
>>>>> at
>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>>
>>>>> at
>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>>
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>
>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I have now fixed few more issues:
>>>>>> - Removing subscription resource from REST API and CLI.
>>>>>> - Adding isKubernetesCluster property to ApplicationClusterContext.
>>>>>> - Passing properties from Application definition to the cluster
>>>>>> objects. This is needed for Kubernetes.
>>>>>> - Packaging drools files in stratos distribution (some of the files
>>>>>> were placed in repository/conf while the rest were at
>>>>>> repository/conf/drools).
>>>>>>
>>>>>> Please find the sample application definition file which I have been
>>>>>> using for testing attached with this mail.
>>>>>>
>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Can a service cluster(say php cluster) span across two partitions(in
>>>>>>> other words two kub cluster)? I guess kubernetes can manage their
>>>>>>> containers within a kub cluster, not between kub clusters? For example, if
>>>>>>> we say we need 3 replicas, it can ensure there are 3 replicas in one kub
>>>>>>> cluster. It can't manage 3 replicas within two kub cluster. Am I missing
>>>>>>> something here?
>>>>>>>
>>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't be a
>>>>>>> problem.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> Lahiru Sandaruwan
>>>>> Committer and PMC member, Apache Stratos,
>>>>> Senior Software Engineer,
>>>>> WSO2 Inc., http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Committer and PMC member, Apache Stratos,
>>>> Senior Software Engineer,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> Raj
>>>
>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Committer and PMC member, Apache Stratos,
>> Senior Software Engineer,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Isuru is working on a major refactoring task ("[Grouping] Branch may be
Unstable ATM"). Will hold this effort until that is completed.
On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> I have tested grouping feature in EC2 up to instance are spawning. Will be
> testing further.
>
> Thanks.
>
> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Hi,
>>
>> When and where are we creating and adding cluster monitors (not app
>> monitors) to the AutoscalerContext?
>> I couldn't find any places.
>>
>> Thanks.
>>
>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <la...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <la...@wso2.com>
>>> wrote:
>>>
>>>> I get a NPE while trying to deploy the app definition without
>>>> properties, looking into it.
>>>>
>>>>
>>> I have added a null check. Will commit the fix.
>>>
>>>> [2014-11-01 20:17:18,922] ERROR
>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>>> - Internal server error
>>>>
>>>> java.lang.NullPointerException
>>>>
>>>> at
>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>>
>>>> at
>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>
>>>> at
>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>>
>>>> at
>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>>
>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>>
>>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>>
>>>> at
>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>>
>>>> at
>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>>
>>>> at
>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>>
>>>> at
>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>>
>>>> at
>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>>
>>>> at
>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>>
>>>> at
>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>>
>>>> at
>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>>
>>>> at
>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>>
>>>> at
>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>>
>>>> at
>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>>
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>
>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I have now fixed few more issues:
>>>>> - Removing subscription resource from REST API and CLI.
>>>>> - Adding isKubernetesCluster property to ApplicationClusterContext.
>>>>> - Passing properties from Application definition to the cluster
>>>>> objects. This is needed for Kubernetes.
>>>>> - Packaging drools files in stratos distribution (some of the files
>>>>> were placed in repository/conf while the rest were at
>>>>> repository/conf/drools).
>>>>>
>>>>> Please find the sample application definition file which I have been
>>>>> using for testing attached with this mail.
>>>>>
>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Can a service cluster(say php cluster) span across two partitions(in
>>>>>> other words two kub cluster)? I guess kubernetes can manage their
>>>>>> containers within a kub cluster, not between kub clusters? For example, if
>>>>>> we say we need 3 replicas, it can ensure there are 3 replicas in one kub
>>>>>> cluster. It can't manage 3 replicas within two kub cluster. Am I missing
>>>>>> something here?
>>>>>>
>>>>>> Raj: A good point, we can handle this in Stratos, shouldn't be a
>>>>>> problem.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Committer and PMC member, Apache Stratos,
>>>> Senior Software Engineer,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Committer and PMC member, Apache Stratos,
>>> Senior Software Engineer,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> Raj
>>
>
>
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lahiru Sandaruwan <la...@wso2.com>.
I have tested grouping feature in EC2 up to instance are spawning. Will be
testing further.
Thanks.
On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Hi,
>
> When and where are we creating and adding cluster monitors (not app
> monitors) to the AutoscalerContext?
> I couldn't find any places.
>
> Thanks.
>
> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <la...@wso2.com>
> wrote:
>
>>
>>
>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <la...@wso2.com>
>> wrote:
>>
>>> I get a NPE while trying to deploy the app definition without
>>> properties, looking into it.
>>>
>>>
>> I have added a null check. Will commit the fix.
>>
>>> [2014-11-01 20:17:18,922] ERROR
>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>>> - Internal server error
>>>
>>> java.lang.NullPointerException
>>>
>>> at
>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>>
>>> at
>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>
>>> at
>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>>
>>> at
>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>>
>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>
>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>
>>> at
>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>>
>>> at
>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>>
>>> at
>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>>
>>> at
>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>>
>>> at
>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>>
>>> at
>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>>
>>> at
>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>>
>>> at
>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>>
>>> at
>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>>
>>> at
>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>>
>>> at
>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>>
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>
>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I have now fixed few more issues:
>>>> - Removing subscription resource from REST API and CLI.
>>>> - Adding isKubernetesCluster property to ApplicationClusterContext.
>>>> - Passing properties from Application definition to the cluster
>>>> objects. This is needed for Kubernetes.
>>>> - Packaging drools files in stratos distribution (some of the files
>>>> were placed in repository/conf while the rest were at
>>>> repository/conf/drools).
>>>>
>>>> Please find the sample application definition file which I have been
>>>> using for testing attached with this mail.
>>>>
>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Can a service cluster(say php cluster) span across two partitions(in
>>>>> other words two kub cluster)? I guess kubernetes can manage their
>>>>> containers within a kub cluster, not between kub clusters? For example, if
>>>>> we say we need 3 replicas, it can ensure there are 3 replicas in one kub
>>>>> cluster. It can't manage 3 replicas within two kub cluster. Am I missing
>>>>> something here?
>>>>>
>>>>> Raj: A good point, we can handle this in Stratos, shouldn't be a
>>>>> problem.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Committer and PMC member, Apache Stratos,
>>> Senior Software Engineer,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Committer and PMC member, Apache Stratos,
>> Senior Software Engineer,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Raj
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Hi,
When and where are we creating and adding cluster monitors (not app
monitors) to the AutoscalerContext?
I couldn't find any places.
Thanks.
On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
>
> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <la...@wso2.com>
> wrote:
>
>> I get a NPE while trying to deploy the app definition without properties,
>> looking into it.
>>
>>
> I have added a null check. Will commit the fix.
>
>> [2014-11-01 20:17:18,922] ERROR
>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
>> - Internal server error
>>
>> java.lang.NullPointerException
>>
>> at
>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>>
>> at
>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:606)
>>
>> at
>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>>
>> at
>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>>
>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>
>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>
>> at
>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>>
>> at
>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>>
>> at
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>>
>> at
>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>
>> at
>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>>
>> at
>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>>
>> at
>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>>
>> at
>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>>
>> at
>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>>
>> at
>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>>
>> at
>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>
>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> I have now fixed few more issues:
>>> - Removing subscription resource from REST API and CLI.
>>> - Adding isKubernetesCluster property to ApplicationClusterContext.
>>> - Passing properties from Application definition to the cluster objects.
>>> This is needed for Kubernetes.
>>> - Packaging drools files in stratos distribution (some of the files were
>>> placed in repository/conf while the rest were at repository/conf/drools).
>>>
>>> Please find the sample application definition file which I have been
>>> using for testing attached with this mail.
>>>
>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Can a service cluster(say php cluster) span across two partitions(in
>>>> other words two kub cluster)? I guess kubernetes can manage their
>>>> containers within a kub cluster, not between kub clusters? For example, if
>>>> we say we need 3 replicas, it can ensure there are 3 replicas in one kub
>>>> cluster. It can't manage 3 replicas within two kub cluster. Am I missing
>>>> something here?
>>>>
>>>> Raj: A good point, we can handle this in Stratos, shouldn't be a
>>>> problem.
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Committer and PMC member, Apache Stratos,
>> Senior Software Engineer,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> I get a NPE while trying to deploy the app definition without properties,
> looking into it.
>
>
I have added a null check. Will commit the fix.
> [2014-11-01 20:17:18,922] ERROR
> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
> - Internal server error
>
> java.lang.NullPointerException
>
> at
> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
>
> at
> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:606)
>
> at
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
>
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
>
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
>
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>
> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I have now fixed few more issues:
>> - Removing subscription resource from REST API and CLI.
>> - Adding isKubernetesCluster property to ApplicationClusterContext.
>> - Passing properties from Application definition to the cluster objects.
>> This is needed for Kubernetes.
>> - Packaging drools files in stratos distribution (some of the files were
>> placed in repository/conf while the rest were at repository/conf/drools).
>>
>> Please find the sample application definition file which I have been
>> using for testing attached with this mail.
>>
>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Can a service cluster(say php cluster) span across two partitions(in
>>> other words two kub cluster)? I guess kubernetes can manage their
>>> containers within a kub cluster, not between kub clusters? For example, if
>>> we say we need 3 replicas, it can ensure there are 3 replicas in one kub
>>> cluster. It can't manage 3 replicas within two kub cluster. Am I missing
>>> something here?
>>>
>>> Raj: A good point, we can handle this in Stratos, shouldn't be a problem.
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lahiru Sandaruwan <la...@wso2.com>.
I get a NPE while trying to deploy the app definition without properties,
looking into it.
[2014-11-01 20:17:18,922] ERROR
{org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper}
- Internal server error
java.lang.NullPointerException
at
org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139)
at
org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
at
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I have now fixed few more issues:
> - Removing subscription resource from REST API and CLI.
> - Adding isKubernetesCluster property to ApplicationClusterContext.
> - Passing properties from Application definition to the cluster objects.
> This is needed for Kubernetes.
> - Packaging drools files in stratos distribution (some of the files were
> placed in repository/conf while the rest were at repository/conf/drools).
>
> Please find the sample application definition file which I have been using
> for testing attached with this mail.
>
> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Can a service cluster(say php cluster) span across two partitions(in
>> other words two kub cluster)? I guess kubernetes can manage their
>> containers within a kub cluster, not between kub clusters? For example, if
>> we say we need 3 replicas, it can ensure there are 3 replicas in one kub
>> cluster. It can't manage 3 replicas within two kub cluster. Am I missing
>> something here?
>>
>> Raj: A good point, we can handle this in Stratos, shouldn't be a problem.
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
I have now fixed few more issues:
- Removing subscription resource from REST API and CLI.
- Adding isKubernetesCluster property to ApplicationClusterContext.
- Passing properties from Application definition to the cluster objects.
This is needed for Kubernetes.
- Packaging drools files in stratos distribution (some of the files were
placed in repository/conf while the rest were at repository/conf/drools).
Please find the sample application definition file which I have been using
for testing attached with this mail.
On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Can a service cluster(say php cluster) span across two partitions(in other
> words two kub cluster)? I guess kubernetes can manage their containers
> within a kub cluster, not between kub clusters? For example, if we say we
> need 3 replicas, it can ensure there are 3 replicas in one kub cluster. It
> can't manage 3 replicas within two kub cluster. Am I missing something here?
>
> Raj: A good point, we can handle this in Stratos, shouldn't be a problem.
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Can a service cluster(say php cluster) span across two partitions(in other
words two kub cluster)? I guess kubernetes can manage their containers
within a kub cluster, not between kub clusters? For example, if we say we
need 3 replicas, it can ensure there are 3 replicas in one kub cluster. It
can't manage 3 replicas within two kub cluster. Am I missing something here?
Raj: A good point, we can handle this in Stratos, shouldn't be a problem.
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lakmal Warusawithana <la...@wso2.com>.
On Sat, Nov 1, 2014 at 2:20 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Hi,
>
> On Sat, Nov 1, 2014 at 11:34 AM, Lakmal Warusawithana <la...@wso2.com>
> wrote:
>
>>
>>
>> On Sat, Nov 1, 2014 at 11:32 AM, Lakmal Warusawithana <la...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Sat, Nov 1, 2014 at 11:10 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I'm testing the Kubernetes work flow with service grouping
>>>> functionality now.
>>>> Found an issue where Autoscaler tries to find a deployment policy while
>>>> deploying the application definition.
>>>>
>>>>
>>> I have an idea, how we can use deployment policies in container(docker)
>>> case also. (which we currently not supported.) This is mainly two reasons,
>>> 1 is use same model for both docker and VM based deployment and secondly
>>> introduce deployment policies into docker case.
>>>
>>> In docker scenario:
>>> Currently we are use auto scaling policies and in the subscription json
>>> we are mentioning the kub cluster need to use in deploying. IMO, we can
>>> simple use deployment policy for defining kub cluster(s) and min/max
>>> replicas for a kub cluster. We can consider kub cluster as like a NT
>>> partition in VM case.
>>>
>>> WDYT? Shall we go for that?
>>>
>>
>>
>> And why this is important, when you are comes to group wise scaling, it
>> is only support if an only has partitions. So with this case we should
>> consider kub cluster as one partition and another kub cluster as another
>> partition and make them define in the deployment policy.
>>
>
> Can a service cluster(say php cluster) span across two partitions(in other
> words two kub cluster)? I guess kubernetes can manage their containers
> within a kub cluster, not between kub clusters? For example, if we say we
> need 3 replicas, it can ensure there are 3 replicas in one kub cluster. It
> can't manage 3 replicas within two kub cluster. Am I missing something here?
>
>
Yes, replicas should handle within a cluster. Simply autoscaling happen
within a cluster. Only group wise scaling going across clusters
Thanks.
>
>
>>
>>
>>>
>>>
>>>> On Fri, Oct 31, 2014 at 8:27 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Fixed message receiver issue in cloud controller and progressing
>>>>> further.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Oct 31, 2014 at 7:55 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Fixed a problem found in the cloud controller service stub where it
>>>>>> has not exported one of the packages from the OSGi bundle.
>>>>>>
>>>>>> Now the application deployment logic is working and found an issue in
>>>>>> message receivers introduced in service grouping, currently looking into
>>>>>> that.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Fri, Oct 31, 2014 at 5:19 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I found several issues in cloud controller which were caused by the
>>>>>>> merge process. I'm now fixing them and proceeding further with a sample
>>>>>>> workflow. Will update with the status soon.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Fri, Oct 31, 2014 at 9:40 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I have now merged topology event listerners in Autoscaler that were
>>>>>>>> introduced in service grouping and committed changes to
>>>>>>>> docker-grouping-merge branch.
>>>>>>>>
>>>>>>>> Now we can start testing the features and see which parts are
>>>>>>>> broken.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Thu, Oct 30, 2014 at 9:54 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I see more changes in Autoscaler, will let you know once its done.
>>>>>>>>>
>>>>>>>>> On Thu, Oct 30, 2014 at 6:41 PM, Isuru Haththotuwa <
>>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>> Awesome! great work everyone.
>>>>>>>>>>
>>>>>>>>>> On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <
>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> *docker-grouping-merge *builds fine now!
>>>>>>>>>>>
>>>>>>>>>>> It will be better if everyone of us take one
>>>>>>>>>>> scenario(kubernetes, vm etc) and make sure it is functionally working
>>>>>>>>>>> correctly.
>>>>>>>>>>>
>>>>>>>>>>> I would like to take the kubernetes stuff and make sure
>>>>>>>>>>> everything is properly working.
>>>>>>>>>>>
>>>>>>>>>>> Thanks.
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thanks Lakmal, we have now resolved compilation issues in the
>>>>>>>>>>>> following components:
>>>>>>>>>>>> - Autoscaler
>>>>>>>>>>>> - Cloud Controller
>>>>>>>>>>>> - CLI
>>>>>>>>>>>>
>>>>>>>>>>>> The latest status of the merge process can be seen here:
>>>>>>>>>>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>>>>>>>>>>
>>>>>>>>>>>> The plan is to first resolve all compilation issues and then
>>>>>>>>>>>> fix the functional issues.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <
>>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Great work Imesh! Please keep update the status.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>>>>>>>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>>>>>>>>>>> Afterwards those conflicts were resolved and committed.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Now we are trying to compile the components and resolve
>>>>>>>>>>>>>> compilation issues:
>>>>>>>>>>>>>> - Found issues in messaging component and resolved
>>>>>>>>>>>>>> - Currently working on Autoscaler where there are changes in
>>>>>>>>>>>>>> monitor classes which have been changed in both branches.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <
>>>>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Yes, targeting GA end of nov.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> So target date of GA would be and of November (as was
>>>>>>>>>>>>>>>> planned for 4.2), or might this be moved (to when) ?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to
>>>>>>>>>>>>>>>> Master Branch
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Yes
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> So this will move out the 4.1 release to what was planned
>>>>>>>>>>>>>>>> for 4.2, correct ?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to
>>>>>>>>>>>>>>>> Master Branch
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Martin,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Initially we thought of doing two releases for docker and
>>>>>>>>>>>>>>>> grouping, but due to time constrain we are going to do a single release
>>>>>>>>>>>>>>>> which carry both grouping and docker in one release which is 4.1.0.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Imesh,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Since we are merging the 4.0.0-grouping branch into the
>>>>>>>>>>>>>>>> master are these changes (grouping) also going into 4.1 ?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Martin
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>>>>>>>>>>>> *To:* dev
>>>>>>>>>>>>>>>> *Subject:* [Important] Merging Grouping Changes to Master
>>>>>>>>>>>>>>>> Branch
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We are now in the process of merging service grouping
>>>>>>>>>>>>>>>> changes (4.0.0-grouping branch) into master branch.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We have created a new branch: *docker-grouping-merge* for
>>>>>>>>>>>>>>>> this process from the latest commit in the master branch and merging
>>>>>>>>>>>>>>>> changes from *4.0.0-grouping* branch to it.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Please try to hold your commits to master branch until we
>>>>>>>>>>>>>>>> complete this process. If not please double commit your changes to master
>>>>>>>>>>>>>>>> and docker-grouping-merge branches.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Raj
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>>
>>>>>>>>>>> Isuru H.
>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Lakmal Warusawithana
>>> Vice President, Apache Stratos
>>> Director - Cloud Architecture; WSO2 Inc.
>>> Mobile : +94714289692
>>> Blog : http://lakmalsview.blogspot.com/
>>>
>>>
>>
>>
>> --
>> Lakmal Warusawithana
>> Vice President, Apache Stratos
>> Director - Cloud Architecture; WSO2 Inc.
>> Mobile : +94714289692
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>
>
> --
> Raj
>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Hi,
On Sat, Nov 1, 2014 at 11:34 AM, Lakmal Warusawithana <la...@wso2.com>
wrote:
>
>
> On Sat, Nov 1, 2014 at 11:32 AM, Lakmal Warusawithana <la...@wso2.com>
> wrote:
>
>>
>>
>> On Sat, Nov 1, 2014 at 11:10 AM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> I'm testing the Kubernetes work flow with service grouping functionality
>>> now.
>>> Found an issue where Autoscaler tries to find a deployment policy while
>>> deploying the application definition.
>>>
>>>
>> I have an idea, how we can use deployment policies in container(docker)
>> case also. (which we currently not supported.) This is mainly two reasons,
>> 1 is use same model for both docker and VM based deployment and secondly
>> introduce deployment policies into docker case.
>>
>> In docker scenario:
>> Currently we are use auto scaling policies and in the subscription json
>> we are mentioning the kub cluster need to use in deploying. IMO, we can
>> simple use deployment policy for defining kub cluster(s) and min/max
>> replicas for a kub cluster. We can consider kub cluster as like a NT
>> partition in VM case.
>>
>> WDYT? Shall we go for that?
>>
>
>
> And why this is important, when you are comes to group wise scaling, it is
> only support if an only has partitions. So with this case we should
> consider kub cluster as one partition and another kub cluster as another
> partition and make them define in the deployment policy.
>
Can a service cluster(say php cluster) span across two partitions(in other
words two kub cluster)? I guess kubernetes can manage their containers
within a kub cluster, not between kub clusters? For example, if we say we
need 3 replicas, it can ensure there are 3 replicas in one kub cluster. It
can't manage 3 replicas within two kub cluster. Am I missing something here?
Thanks.
>
>
>>
>>
>>> On Fri, Oct 31, 2014 at 8:27 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Fixed message receiver issue in cloud controller and progressing
>>>> further.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Oct 31, 2014 at 7:55 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Fixed a problem found in the cloud controller service stub where it
>>>>> has not exported one of the packages from the OSGi bundle.
>>>>>
>>>>> Now the application deployment logic is working and found an issue in
>>>>> message receivers introduced in service grouping, currently looking into
>>>>> that.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Oct 31, 2014 at 5:19 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I found several issues in cloud controller which were caused by the
>>>>>> merge process. I'm now fixing them and proceeding further with a sample
>>>>>> workflow. Will update with the status soon.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Fri, Oct 31, 2014 at 9:40 AM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I have now merged topology event listerners in Autoscaler that were
>>>>>>> introduced in service grouping and committed changes to
>>>>>>> docker-grouping-merge branch.
>>>>>>>
>>>>>>> Now we can start testing the features and see which parts are broken.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Thu, Oct 30, 2014 at 9:54 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I see more changes in Autoscaler, will let you know once its done.
>>>>>>>>
>>>>>>>> On Thu, Oct 30, 2014 at 6:41 PM, Isuru Haththotuwa <
>>>>>>>> isuruh@apache.org> wrote:
>>>>>>>>
>>>>>>>>> Awesome! great work everyone.
>>>>>>>>>
>>>>>>>>> On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <
>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> *docker-grouping-merge *builds fine now!
>>>>>>>>>>
>>>>>>>>>> It will be better if everyone of us take one scenario(kubernetes,
>>>>>>>>>> vm etc) and make sure it is functionally working correctly.
>>>>>>>>>>
>>>>>>>>>> I would like to take the kubernetes stuff and make sure
>>>>>>>>>> everything is properly working.
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <
>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>> Thanks Lakmal, we have now resolved compilation issues in the
>>>>>>>>>>> following components:
>>>>>>>>>>> - Autoscaler
>>>>>>>>>>> - Cloud Controller
>>>>>>>>>>> - CLI
>>>>>>>>>>>
>>>>>>>>>>> The latest status of the merge process can be seen here:
>>>>>>>>>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>>>>>>>>>
>>>>>>>>>>> The plan is to first resolve all compilation issues and then fix
>>>>>>>>>>> the functional issues.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <
>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Great work Imesh! Please keep update the status.
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>>>>>>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>>>>>>>>>> Afterwards those conflicts were resolved and committed.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now we are trying to compile the components and resolve
>>>>>>>>>>>>> compilation issues:
>>>>>>>>>>>>> - Found issues in messaging component and resolved
>>>>>>>>>>>>> - Currently working on Autoscaler where there are changes in
>>>>>>>>>>>>> monitor classes which have been changed in both branches.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <
>>>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Yes, targeting GA end of nov.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> So target date of GA would be and of November (as was
>>>>>>>>>>>>>>> planned for 4.2), or might this be moved (to when) ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to
>>>>>>>>>>>>>>> Master Branch
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Yes
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> So this will move out the 4.1 release to what was planned
>>>>>>>>>>>>>>> for 4.2, correct ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to
>>>>>>>>>>>>>>> Master Branch
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Martin,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Initially we thought of doing two releases for docker and
>>>>>>>>>>>>>>> grouping, but due to time constrain we are going to do a single release
>>>>>>>>>>>>>>> which carry both grouping and docker in one release which is 4.1.0.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Imesh,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Since we are merging the 4.0.0-grouping branch into the
>>>>>>>>>>>>>>> master are these changes (grouping) also going into 4.1 ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Martin
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>>>>>>>>>>> *To:* dev
>>>>>>>>>>>>>>> *Subject:* [Important] Merging Grouping Changes to Master
>>>>>>>>>>>>>>> Branch
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We are now in the process of merging service grouping
>>>>>>>>>>>>>>> changes (4.0.0-grouping branch) into master branch.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We have created a new branch: *docker-grouping-merge* for
>>>>>>>>>>>>>>> this process from the latest commit in the master branch and merging
>>>>>>>>>>>>>>> changes from *4.0.0-grouping* branch to it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Please try to hold your commits to master branch until we
>>>>>>>>>>>>>>> complete this process. If not please double commit your changes to master
>>>>>>>>>>>>>>> and docker-grouping-merge branches.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Raj
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Thanks and Regards,
>>>>>>>>>>
>>>>>>>>>> Isuru H.
>>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Lakmal Warusawithana
>> Vice President, Apache Stratos
>> Director - Cloud Architecture; WSO2 Inc.
>> Mobile : +94714289692
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>
>
> --
> Lakmal Warusawithana
> Vice President, Apache Stratos
> Director - Cloud Architecture; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
A great thought Lakmal! Yes definitely! I was also thinking enabling the
ability to autoscale Kubernetes clusters. We can take this as the first
step towards that.
First we can introduce this feature to define deployment policies for
Kubernetes and then at a later stage we can add the ability to autoscale
them.
Thanks
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lakmal Warusawithana <la...@wso2.com>.
On Sat, Nov 1, 2014 at 11:32 AM, Lakmal Warusawithana <la...@wso2.com>
wrote:
>
>
> On Sat, Nov 1, 2014 at 11:10 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I'm testing the Kubernetes work flow with service grouping functionality
>> now.
>> Found an issue where Autoscaler tries to find a deployment policy while
>> deploying the application definition.
>>
>>
> I have an idea, how we can use deployment policies in container(docker)
> case also. (which we currently not supported.) This is mainly two reasons,
> 1 is use same model for both docker and VM based deployment and secondly
> introduce deployment policies into docker case.
>
> In docker scenario:
> Currently we are use auto scaling policies and in the subscription json we
> are mentioning the kub cluster need to use in deploying. IMO, we can simple
> use deployment policy for defining kub cluster(s) and min/max replicas for
> a kub cluster. We can consider kub cluster as like a NT partition in VM
> case.
>
> WDYT? Shall we go for that?
>
And why this is important, when you are comes to group wise scaling, it is
only support if an only has partitions. So with this case we should
consider kub cluster as one partition and another kub cluster as another
partition and make them define in the deployment policy.
>
>
>> On Fri, Oct 31, 2014 at 8:27 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Fixed message receiver issue in cloud controller and progressing further.
>>>
>>> Thanks
>>>
>>> On Fri, Oct 31, 2014 at 7:55 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Fixed a problem found in the cloud controller service stub where it has
>>>> not exported one of the packages from the OSGi bundle.
>>>>
>>>> Now the application deployment logic is working and found an issue in
>>>> message receivers introduced in service grouping, currently looking into
>>>> that.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Oct 31, 2014 at 5:19 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I found several issues in cloud controller which were caused by the
>>>>> merge process. I'm now fixing them and proceeding further with a sample
>>>>> workflow. Will update with the status soon.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Oct 31, 2014 at 9:40 AM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I have now merged topology event listerners in Autoscaler that were
>>>>>> introduced in service grouping and committed changes to
>>>>>> docker-grouping-merge branch.
>>>>>>
>>>>>> Now we can start testing the features and see which parts are broken.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Thu, Oct 30, 2014 at 9:54 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I see more changes in Autoscaler, will let you know once its done.
>>>>>>>
>>>>>>> On Thu, Oct 30, 2014 at 6:41 PM, Isuru Haththotuwa <
>>>>>>> isuruh@apache.org> wrote:
>>>>>>>
>>>>>>>> Awesome! great work everyone.
>>>>>>>>
>>>>>>>> On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <
>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> *docker-grouping-merge *builds fine now!
>>>>>>>>>
>>>>>>>>> It will be better if everyone of us take one scenario(kubernetes,
>>>>>>>>> vm etc) and make sure it is functionally working correctly.
>>>>>>>>>
>>>>>>>>> I would like to take the kubernetes stuff and make sure everything
>>>>>>>>> is properly working.
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> Thanks Lakmal, we have now resolved compilation issues in the
>>>>>>>>>> following components:
>>>>>>>>>> - Autoscaler
>>>>>>>>>> - Cloud Controller
>>>>>>>>>> - CLI
>>>>>>>>>>
>>>>>>>>>> The latest status of the merge process can be seen here:
>>>>>>>>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>>>>>>>>
>>>>>>>>>> The plan is to first resolve all compilation issues and then fix
>>>>>>>>>> the functional issues.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <
>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Great work Imesh! Please keep update the status.
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>>>>>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>>>>>>>>> Afterwards those conflicts were resolved and committed.
>>>>>>>>>>>>
>>>>>>>>>>>> Now we are trying to compile the components and resolve
>>>>>>>>>>>> compilation issues:
>>>>>>>>>>>> - Found issues in messaging component and resolved
>>>>>>>>>>>> - Currently working on Autoscaler where there are changes in
>>>>>>>>>>>> monitor classes which have been changed in both branches.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <
>>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Yes, targeting GA end of nov.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> So target date of GA would be and of November (as was
>>>>>>>>>>>>>> planned for 4.2), or might this be moved (to when) ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to
>>>>>>>>>>>>>> Master Branch
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Yes
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> So this will move out the 4.1 release to what was planned for
>>>>>>>>>>>>>> 4.2, correct ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to
>>>>>>>>>>>>>> Master Branch
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Martin,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Initially we thought of doing two releases for docker and
>>>>>>>>>>>>>> grouping, but due to time constrain we are going to do a single release
>>>>>>>>>>>>>> which carry both grouping and docker in one release which is 4.1.0.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Imesh,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Since we are merging the 4.0.0-grouping branch into the
>>>>>>>>>>>>>> master are these changes (grouping) also going into 4.1 ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Martin
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>>>>>>>>>> *To:* dev
>>>>>>>>>>>>>> *Subject:* [Important] Merging Grouping Changes to Master
>>>>>>>>>>>>>> Branch
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We are now in the process of merging service grouping changes
>>>>>>>>>>>>>> (4.0.0-grouping branch) into master branch.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We have created a new branch: *docker-grouping-merge* for
>>>>>>>>>>>>>> this process from the latest commit in the master branch and merging
>>>>>>>>>>>>>> changes from *4.0.0-grouping* branch to it.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please try to hold your commits to master branch until we
>>>>>>>>>>>>>> complete this process. If not please double commit your changes to master
>>>>>>>>>>>>>> and docker-grouping-merge branches.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Raj
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks and Regards,
>>>>>>>>>
>>>>>>>>> Isuru H.
>>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> * <http://wso2.com/>*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Lakmal Warusawithana
> Vice President, Apache Stratos
> Director - Cloud Architecture; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lakmal Warusawithana <la...@wso2.com>.
On Sat, Nov 1, 2014 at 11:10 AM, Imesh Gunaratne <im...@apache.org> wrote:
> I'm testing the Kubernetes work flow with service grouping functionality
> now.
> Found an issue where Autoscaler tries to find a deployment policy while
> deploying the application definition.
>
>
I have an idea, how we can use deployment policies in container(docker)
case also. (which we currently not supported.) This is mainly two reasons,
1 is use same model for both docker and VM based deployment and secondly
introduce deployment policies into docker case.
In docker scenario:
Currently we are use auto scaling policies and in the subscription json we
are mentioning the kub cluster need to use in deploying. IMO, we can simple
use deployment policy for defining kub cluster(s) and min/max replicas for
a kub cluster. We can consider kub cluster as like a NT partition in VM
case.
WDYT? Shall we go for that?
> On Fri, Oct 31, 2014 at 8:27 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Fixed message receiver issue in cloud controller and progressing further.
>>
>> Thanks
>>
>> On Fri, Oct 31, 2014 at 7:55 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Fixed a problem found in the cloud controller service stub where it has
>>> not exported one of the packages from the OSGi bundle.
>>>
>>> Now the application deployment logic is working and found an issue in
>>> message receivers introduced in service grouping, currently looking into
>>> that.
>>>
>>> Thanks
>>>
>>> On Fri, Oct 31, 2014 at 5:19 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I found several issues in cloud controller which were caused by the
>>>> merge process. I'm now fixing them and proceeding further with a sample
>>>> workflow. Will update with the status soon.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Oct 31, 2014 at 9:40 AM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I have now merged topology event listerners in Autoscaler that were
>>>>> introduced in service grouping and committed changes to
>>>>> docker-grouping-merge branch.
>>>>>
>>>>> Now we can start testing the features and see which parts are broken.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Thu, Oct 30, 2014 at 9:54 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I see more changes in Autoscaler, will let you know once its done.
>>>>>>
>>>>>> On Thu, Oct 30, 2014 at 6:41 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>>> > wrote:
>>>>>>
>>>>>>> Awesome! great work everyone.
>>>>>>>
>>>>>>> On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> *docker-grouping-merge *builds fine now!
>>>>>>>>
>>>>>>>> It will be better if everyone of us take one scenario(kubernetes,
>>>>>>>> vm etc) and make sure it is functionally working correctly.
>>>>>>>>
>>>>>>>> I would like to take the kubernetes stuff and make sure everything
>>>>>>>> is properly working.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thanks Lakmal, we have now resolved compilation issues in the
>>>>>>>>> following components:
>>>>>>>>> - Autoscaler
>>>>>>>>> - Cloud Controller
>>>>>>>>> - CLI
>>>>>>>>>
>>>>>>>>> The latest status of the merge process can be seen here:
>>>>>>>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>>>>>>>
>>>>>>>>> The plan is to first resolve all compilation issues and then fix
>>>>>>>>> the functional issues.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <
>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Great work Imesh! Please keep update the status.
>>>>>>>>>>
>>>>>>>>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <
>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>>>>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>>>>>>>> Afterwards those conflicts were resolved and committed.
>>>>>>>>>>>
>>>>>>>>>>> Now we are trying to compile the components and resolve
>>>>>>>>>>> compilation issues:
>>>>>>>>>>> - Found issues in messaging component and resolved
>>>>>>>>>>> - Currently working on Autoscaler where there are changes in
>>>>>>>>>>> monitor classes which have been changed in both branches.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <
>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Yes, targeting GA end of nov.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> So target date of GA would be and of November (as was
>>>>>>>>>>>>> planned for 4.2), or might this be moved (to when) ?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>>>>>>>>
>>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>>>>>> Branch
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Yes
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> So this will move out the 4.1 release to what was planned for
>>>>>>>>>>>>> 4.2, correct ?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>>>>>> Branch
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Martin,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Initially we thought of doing two releases for docker and
>>>>>>>>>>>>> grouping, but due to time constrain we are going to do a single release
>>>>>>>>>>>>> which carry both grouping and docker in one release which is 4.1.0.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Imesh,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Since we are merging the 4.0.0-grouping branch into the master
>>>>>>>>>>>>> are these changes (grouping) also going into 4.1 ?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Martin
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>>>>>>>>> *To:* dev
>>>>>>>>>>>>> *Subject:* [Important] Merging Grouping Changes to Master
>>>>>>>>>>>>> Branch
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> We are now in the process of merging service grouping changes
>>>>>>>>>>>>> (4.0.0-grouping branch) into master branch.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> We have created a new branch: *docker-grouping-merge* for
>>>>>>>>>>>>> this process from the latest commit in the master branch and merging
>>>>>>>>>>>>> changes from *4.0.0-grouping* branch to it.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please try to hold your commits to master branch until we
>>>>>>>>>>>>> complete this process. If not please double commit your changes to master
>>>>>>>>>>>>> and docker-grouping-merge branches.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>>
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>>
>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>
>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>
>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>>
>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>
>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>
>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Raj
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks and Regards,
>>>>>>>>
>>>>>>>> Isuru H.
>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>> * <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Udara Liyanage <ud...@wso2.com>.
Hi Imesh,
Could you please share the application definition you tried deploying
On Sat, Nov 1, 2014 at 11:10 AM, Imesh Gunaratne <im...@apache.org> wrote:
> I'm testing the Kubernetes work flow with service grouping functionality
> now.
> Found an issue where Autoscaler tries to find a deployment policy while
> deploying the application definition.
>
> On Fri, Oct 31, 2014 at 8:27 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Fixed message receiver issue in cloud controller and progressing further.
>>
>> Thanks
>>
>> On Fri, Oct 31, 2014 at 7:55 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Fixed a problem found in the cloud controller service stub where it has
>>> not exported one of the packages from the OSGi bundle.
>>>
>>> Now the application deployment logic is working and found an issue in
>>> message receivers introduced in service grouping, currently looking into
>>> that.
>>>
>>> Thanks
>>>
>>> On Fri, Oct 31, 2014 at 5:19 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I found several issues in cloud controller which were caused by the
>>>> merge process. I'm now fixing them and proceeding further with a sample
>>>> workflow. Will update with the status soon.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Oct 31, 2014 at 9:40 AM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I have now merged topology event listerners in Autoscaler that were
>>>>> introduced in service grouping and committed changes to
>>>>> docker-grouping-merge branch.
>>>>>
>>>>> Now we can start testing the features and see which parts are broken.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Thu, Oct 30, 2014 at 9:54 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I see more changes in Autoscaler, will let you know once its done.
>>>>>>
>>>>>> On Thu, Oct 30, 2014 at 6:41 PM, Isuru Haththotuwa <isuruh@apache.org
>>>>>> > wrote:
>>>>>>
>>>>>>> Awesome! great work everyone.
>>>>>>>
>>>>>>> On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> *docker-grouping-merge *builds fine now!
>>>>>>>>
>>>>>>>> It will be better if everyone of us take one scenario(kubernetes,
>>>>>>>> vm etc) and make sure it is functionally working correctly.
>>>>>>>>
>>>>>>>> I would like to take the kubernetes stuff and make sure everything
>>>>>>>> is properly working.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thanks Lakmal, we have now resolved compilation issues in the
>>>>>>>>> following components:
>>>>>>>>> - Autoscaler
>>>>>>>>> - Cloud Controller
>>>>>>>>> - CLI
>>>>>>>>>
>>>>>>>>> The latest status of the merge process can be seen here:
>>>>>>>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>>>>>>>
>>>>>>>>> The plan is to first resolve all compilation issues and then fix
>>>>>>>>> the functional issues.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <
>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Great work Imesh! Please keep update the status.
>>>>>>>>>>
>>>>>>>>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <
>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>>>>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>>>>>>>> Afterwards those conflicts were resolved and committed.
>>>>>>>>>>>
>>>>>>>>>>> Now we are trying to compile the components and resolve
>>>>>>>>>>> compilation issues:
>>>>>>>>>>> - Found issues in messaging component and resolved
>>>>>>>>>>> - Currently working on Autoscaler where there are changes in
>>>>>>>>>>> monitor classes which have been changed in both branches.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <
>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Yes, targeting GA end of nov.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> So target date of GA would be and of November (as was
>>>>>>>>>>>>> planned for 4.2), or might this be moved (to when) ?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>>>>>>>>
>>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>>>>>> Branch
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Yes
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> So this will move out the 4.1 release to what was planned for
>>>>>>>>>>>>> 4.2, correct ?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>>>>>> Branch
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Martin,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Initially we thought of doing two releases for docker and
>>>>>>>>>>>>> grouping, but due to time constrain we are going to do a single release
>>>>>>>>>>>>> which carry both grouping and docker in one release which is 4.1.0.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Imesh,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Since we are merging the 4.0.0-grouping branch into the master
>>>>>>>>>>>>> are these changes (grouping) also going into 4.1 ?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Martin
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>>>>>>>>> *To:* dev
>>>>>>>>>>>>> *Subject:* [Important] Merging Grouping Changes to Master
>>>>>>>>>>>>> Branch
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> We are now in the process of merging service grouping changes
>>>>>>>>>>>>> (4.0.0-grouping branch) into master branch.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> We have created a new branch: *docker-grouping-merge* for
>>>>>>>>>>>>> this process from the latest commit in the master branch and merging
>>>>>>>>>>>>> changes from *4.0.0-grouping* branch to it.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please try to hold your commits to master branch until we
>>>>>>>>>>>>> complete this process. If not please double commit your changes to master
>>>>>>>>>>>>> and docker-grouping-merge branches.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>>
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>>
>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>
>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>
>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>>
>>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>>
>>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>>
>>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Raj
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks and Regards,
>>>>>>>>
>>>>>>>> Isuru H.
>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>> * <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
I'm testing the Kubernetes work flow with service grouping functionality
now.
Found an issue where Autoscaler tries to find a deployment policy while
deploying the application definition.
On Fri, Oct 31, 2014 at 8:27 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Fixed message receiver issue in cloud controller and progressing further.
>
> Thanks
>
> On Fri, Oct 31, 2014 at 7:55 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Fixed a problem found in the cloud controller service stub where it has
>> not exported one of the packages from the OSGi bundle.
>>
>> Now the application deployment logic is working and found an issue in
>> message receivers introduced in service grouping, currently looking into
>> that.
>>
>> Thanks
>>
>> On Fri, Oct 31, 2014 at 5:19 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> I found several issues in cloud controller which were caused by the
>>> merge process. I'm now fixing them and proceeding further with a sample
>>> workflow. Will update with the status soon.
>>>
>>> Thanks
>>>
>>> On Fri, Oct 31, 2014 at 9:40 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I have now merged topology event listerners in Autoscaler that were
>>>> introduced in service grouping and committed changes to
>>>> docker-grouping-merge branch.
>>>>
>>>> Now we can start testing the features and see which parts are broken.
>>>>
>>>> Thanks
>>>>
>>>> On Thu, Oct 30, 2014 at 9:54 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I see more changes in Autoscaler, will let you know once its done.
>>>>>
>>>>> On Thu, Oct 30, 2014 at 6:41 PM, Isuru Haththotuwa <is...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Awesome! great work everyone.
>>>>>>
>>>>>> On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <
>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> *docker-grouping-merge *builds fine now!
>>>>>>>
>>>>>>> It will be better if everyone of us take one scenario(kubernetes, vm
>>>>>>> etc) and make sure it is functionally working correctly.
>>>>>>>
>>>>>>> I would like to take the kubernetes stuff and make sure everything
>>>>>>> is properly working.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks Lakmal, we have now resolved compilation issues in the
>>>>>>>> following components:
>>>>>>>> - Autoscaler
>>>>>>>> - Cloud Controller
>>>>>>>> - CLI
>>>>>>>>
>>>>>>>> The latest status of the merge process can be seen here:
>>>>>>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>>>>>>
>>>>>>>> The plan is to first resolve all compilation issues and then fix
>>>>>>>> the functional issues.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <
>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Great work Imesh! Please keep update the status.
>>>>>>>>>
>>>>>>>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>>>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>>>>>>> Afterwards those conflicts were resolved and committed.
>>>>>>>>>>
>>>>>>>>>> Now we are trying to compile the components and resolve
>>>>>>>>>> compilation issues:
>>>>>>>>>> - Found issues in messaging component and resolved
>>>>>>>>>> - Currently working on Autoscaler where there are changes in
>>>>>>>>>> monitor classes which have been changed in both branches.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <
>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Yes, targeting GA end of nov.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> So target date of GA would be and of November (as was planned
>>>>>>>>>>>> for 4.2), or might this be moved (to when) ?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>>>>>>>
>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>>>>> Branch
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Yes
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> So this will move out the 4.1 release to what was planned for
>>>>>>>>>>>> 4.2, correct ?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>>>>> Branch
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Martin,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Initially we thought of doing two releases for docker and
>>>>>>>>>>>> grouping, but due to time constrain we are going to do a single release
>>>>>>>>>>>> which carry both grouping and docker in one release which is 4.1.0.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Imesh,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Since we are merging the 4.0.0-grouping branch into the master
>>>>>>>>>>>> are these changes (grouping) also going into 4.1 ?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Martin
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>>>>>>>> *To:* dev
>>>>>>>>>>>> *Subject:* [Important] Merging Grouping Changes to Master
>>>>>>>>>>>> Branch
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> We are now in the process of merging service grouping changes
>>>>>>>>>>>> (4.0.0-grouping branch) into master branch.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> We have created a new branch: *docker-grouping-merge* for this
>>>>>>>>>>>> process from the latest commit in the master branch and merging changes
>>>>>>>>>>>> from *4.0.0-grouping* branch to it.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Please try to hold your commits to master branch until we
>>>>>>>>>>>> complete this process. If not please double commit your changes to master
>>>>>>>>>>>> and docker-grouping-merge branches.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>>
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>>
>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>
>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>
>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>
>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>>
>>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>>
>>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>>
>>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>>
>>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Lakmal Warusawithana
>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>> Mobile : +94714289692
>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Raj
>>>>>>>
>>>>>>> --
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>> * <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Fixed message receiver issue in cloud controller and progressing further.
Thanks
On Fri, Oct 31, 2014 at 7:55 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Fixed a problem found in the cloud controller service stub where it has
> not exported one of the packages from the OSGi bundle.
>
> Now the application deployment logic is working and found an issue in
> message receivers introduced in service grouping, currently looking into
> that.
>
> Thanks
>
> On Fri, Oct 31, 2014 at 5:19 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I found several issues in cloud controller which were caused by the merge
>> process. I'm now fixing them and proceeding further with a sample workflow.
>> Will update with the status soon.
>>
>> Thanks
>>
>> On Fri, Oct 31, 2014 at 9:40 AM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> I have now merged topology event listerners in Autoscaler that were
>>> introduced in service grouping and committed changes to
>>> docker-grouping-merge branch.
>>>
>>> Now we can start testing the features and see which parts are broken.
>>>
>>> Thanks
>>>
>>> On Thu, Oct 30, 2014 at 9:54 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I see more changes in Autoscaler, will let you know once its done.
>>>>
>>>> On Thu, Oct 30, 2014 at 6:41 PM, Isuru Haththotuwa <is...@apache.org>
>>>> wrote:
>>>>
>>>>> Awesome! great work everyone.
>>>>>
>>>>> On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <
>>>>> rajkumarr@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> *docker-grouping-merge *builds fine now!
>>>>>>
>>>>>> It will be better if everyone of us take one scenario(kubernetes, vm
>>>>>> etc) and make sure it is functionally working correctly.
>>>>>>
>>>>>> I would like to take the kubernetes stuff and make sure everything is
>>>>>> properly working.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks Lakmal, we have now resolved compilation issues in the
>>>>>>> following components:
>>>>>>> - Autoscaler
>>>>>>> - Cloud Controller
>>>>>>> - CLI
>>>>>>>
>>>>>>> The latest status of the merge process can be seen here:
>>>>>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>>>>>
>>>>>>> The plan is to first resolve all compilation issues and then fix the
>>>>>>> functional issues.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <
>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>
>>>>>>>> Great work Imesh! Please keep update the status.
>>>>>>>>
>>>>>>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>>>>>> Afterwards those conflicts were resolved and committed.
>>>>>>>>>
>>>>>>>>> Now we are trying to compile the components and resolve
>>>>>>>>> compilation issues:
>>>>>>>>> - Found issues in messaging component and resolved
>>>>>>>>> - Currently working on Autoscaler where there are changes in
>>>>>>>>> monitor classes which have been changed in both branches.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <
>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Yes, targeting GA end of nov.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> So target date of GA would be and of November (as was planned
>>>>>>>>>>> for 4.2), or might this be moved (to when) ?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>>>>>>
>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>>>> Branch
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Yes
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> So this will move out the 4.1 release to what was planned for
>>>>>>>>>>> 4.2, correct ?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>>>> Branch
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hi Martin,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Initially we thought of doing two releases for docker and
>>>>>>>>>>> grouping, but due to time constrain we are going to do a single release
>>>>>>>>>>> which carry both grouping and docker in one release which is 4.1.0.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Imesh,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Since we are merging the 4.0.0-grouping branch into the master
>>>>>>>>>>> are these changes (grouping) also going into 4.1 ?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Martin
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>>>>>>> *To:* dev
>>>>>>>>>>> *Subject:* [Important] Merging Grouping Changes to Master Branch
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> We are now in the process of merging service grouping changes
>>>>>>>>>>> (4.0.0-grouping branch) into master branch.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> We have created a new branch: *docker-grouping-merge* for this
>>>>>>>>>>> process from the latest commit in the master branch and merging changes
>>>>>>>>>>> from *4.0.0-grouping* branch to it.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Please try to hold your commits to master branch until we
>>>>>>>>>>> complete this process. If not please double commit your changes to master
>>>>>>>>>>> and docker-grouping-merge branches.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>
>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>
>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>
>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>>
>>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>>
>>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>>
>>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Lakmal Warusawithana
>>>>>>>> Vice President, Apache Stratos
>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>> Mobile : +94714289692
>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Raj
>>>>>>
>>>>>> --
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Isuru H.
>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>> * <http://wso2.com/>*
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Fixed a problem found in the cloud controller service stub where it has not
exported one of the packages from the OSGi bundle.
Now the application deployment logic is working and found an issue in
message receivers introduced in service grouping, currently looking into
that.
Thanks
On Fri, Oct 31, 2014 at 5:19 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I found several issues in cloud controller which were caused by the merge
> process. I'm now fixing them and proceeding further with a sample workflow.
> Will update with the status soon.
>
> Thanks
>
> On Fri, Oct 31, 2014 at 9:40 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I have now merged topology event listerners in Autoscaler that were
>> introduced in service grouping and committed changes to
>> docker-grouping-merge branch.
>>
>> Now we can start testing the features and see which parts are broken.
>>
>> Thanks
>>
>> On Thu, Oct 30, 2014 at 9:54 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> I see more changes in Autoscaler, will let you know once its done.
>>>
>>> On Thu, Oct 30, 2014 at 6:41 PM, Isuru Haththotuwa <is...@apache.org>
>>> wrote:
>>>
>>>> Awesome! great work everyone.
>>>>
>>>> On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <
>>>> rajkumarr@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> *docker-grouping-merge *builds fine now!
>>>>>
>>>>> It will be better if everyone of us take one scenario(kubernetes, vm
>>>>> etc) and make sure it is functionally working correctly.
>>>>>
>>>>> I would like to take the kubernetes stuff and make sure everything is
>>>>> properly working.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Thanks Lakmal, we have now resolved compilation issues in the
>>>>>> following components:
>>>>>> - Autoscaler
>>>>>> - Cloud Controller
>>>>>> - CLI
>>>>>>
>>>>>> The latest status of the merge process can be seen here:
>>>>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>>>>
>>>>>> The plan is to first resolve all compilation issues and then fix the
>>>>>> functional issues.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <
>>>>>> lakmal@wso2.com> wrote:
>>>>>>
>>>>>>> Great work Imesh! Please keep update the status.
>>>>>>>
>>>>>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>>>>> Afterwards those conflicts were resolved and committed.
>>>>>>>>
>>>>>>>> Now we are trying to compile the components and resolve compilation
>>>>>>>> issues:
>>>>>>>> - Found issues in messaging component and resolved
>>>>>>>> - Currently working on Autoscaler where there are changes in
>>>>>>>> monitor classes which have been changed in both branches.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <
>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Yes, targeting GA end of nov.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>
>>>>>>>>>> So target date of GA would be and of November (as was planned
>>>>>>>>>> for 4.2), or might this be moved (to when) ?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>>>>>
>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>>> Branch
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Yes
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>
>>>>>>>>>> So this will move out the 4.1 release to what was planned for
>>>>>>>>>> 4.2, correct ?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>>> Branch
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Martin,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Initially we thought of doing two releases for docker and
>>>>>>>>>> grouping, but due to time constrain we are going to do a single release
>>>>>>>>>> which carry both grouping and docker in one release which is 4.1.0.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Imesh,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Since we are merging the 4.0.0-grouping branch into the master
>>>>>>>>>> are these changes (grouping) also going into 4.1 ?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Martin
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>>>>>> *To:* dev
>>>>>>>>>> *Subject:* [Important] Merging Grouping Changes to Master Branch
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Devs,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> We are now in the process of merging service grouping changes
>>>>>>>>>> (4.0.0-grouping branch) into master branch.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> We have created a new branch: *docker-grouping-merge* for this
>>>>>>>>>> process from the latest commit in the master branch and merging changes
>>>>>>>>>> from *4.0.0-grouping* branch to it.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Please try to hold your commits to master branch until we
>>>>>>>>>> complete this process. If not please double commit your changes to master
>>>>>>>>>> and docker-grouping-merge branches.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>
>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>
>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>
>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>
>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>>
>>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>>
>>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>>
>>>>>>>>>> Mobile : +94714289692
>>>>>>>>>>
>>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Lakmal Warusawithana
>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>> Mobile : +94714289692
>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Lakmal Warusawithana
>>>>>>> Vice President, Apache Stratos
>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>> Mobile : +94714289692
>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Raj
>>>>>
>>>>> --
>>>>> Thanks and Regards,
>>>>>
>>>>> Isuru H.
>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>
>>>>>
>>>>> * <http://wso2.com/>*
>>>>>
>>>>>
>>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
I found several issues in cloud controller which were caused by the merge
process. I'm now fixing them and proceeding further with a sample workflow.
Will update with the status soon.
Thanks
On Fri, Oct 31, 2014 at 9:40 AM, Imesh Gunaratne <im...@apache.org> wrote:
> I have now merged topology event listerners in Autoscaler that were
> introduced in service grouping and committed changes to
> docker-grouping-merge branch.
>
> Now we can start testing the features and see which parts are broken.
>
> Thanks
>
> On Thu, Oct 30, 2014 at 9:54 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I see more changes in Autoscaler, will let you know once its done.
>>
>> On Thu, Oct 30, 2014 at 6:41 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>> Awesome! great work everyone.
>>>
>>> On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>> > wrote:
>>>
>>>> Hi,
>>>>
>>>> *docker-grouping-merge *builds fine now!
>>>>
>>>> It will be better if everyone of us take one scenario(kubernetes, vm
>>>> etc) and make sure it is functionally working correctly.
>>>>
>>>> I would like to take the kubernetes stuff and make sure everything is
>>>> properly working.
>>>>
>>>> Thanks.
>>>>
>>>> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Thanks Lakmal, we have now resolved compilation issues in the
>>>>> following components:
>>>>> - Autoscaler
>>>>> - Cloud Controller
>>>>> - CLI
>>>>>
>>>>> The latest status of the merge process can be seen here:
>>>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>>>
>>>>> The plan is to first resolve all compilation issues and then fix the
>>>>> functional issues.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <lakmal@wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Great work Imesh! Please keep update the status.
>>>>>>
>>>>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>>>> Afterwards those conflicts were resolved and committed.
>>>>>>>
>>>>>>> Now we are trying to compile the components and resolve compilation
>>>>>>> issues:
>>>>>>> - Found issues in messaging component and resolved
>>>>>>> - Currently working on Autoscaler where there are changes in monitor
>>>>>>> classes which have been changed in both branches.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <
>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>
>>>>>>>> Yes, targeting GA end of nov.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>
>>>>>>>>> So target date of GA would be and of November (as was planned
>>>>>>>>> for 4.2), or might this be moved (to when) ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>>>>
>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>> Branch
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Yes
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>
>>>>>>>>> So this will move out the 4.1 release to what was planned for 4.2,
>>>>>>>>> correct ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>>> Branch
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Martin,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Initially we thought of doing two releases for docker and
>>>>>>>>> grouping, but due to time constrain we are going to do a single release
>>>>>>>>> which carry both grouping and docker in one release which is 4.1.0.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi Imesh,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Since we are merging the 4.0.0-grouping branch into the master are
>>>>>>>>> these changes (grouping) also going into 4.1 ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Martin
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>>>>> *To:* dev
>>>>>>>>> *Subject:* [Important] Merging Grouping Changes to Master Branch
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Devs,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We are now in the process of merging service grouping changes
>>>>>>>>> (4.0.0-grouping branch) into master branch.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We have created a new branch: *docker-grouping-merge* for this
>>>>>>>>> process from the latest commit in the master branch and merging changes
>>>>>>>>> from *4.0.0-grouping* branch to it.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Please try to hold your commits to master branch until we complete
>>>>>>>>> this process. If not please double commit your changes to master and
>>>>>>>>> docker-grouping-merge branches.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>
>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>
>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>
>>>>>>>>> Mobile : +94714289692
>>>>>>>>>
>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> Lakmal Warusawithana
>>>>>>>>>
>>>>>>>>> Vice President, Apache Stratos
>>>>>>>>>
>>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>>
>>>>>>>>> Mobile : +94714289692
>>>>>>>>>
>>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Lakmal Warusawithana
>>>>>>>> Vice President, Apache Stratos
>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>> Mobile : +94714289692
>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Lakmal Warusawithana
>>>>>> Vice President, Apache Stratos
>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>> Mobile : +94714289692
>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Raj
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> +94 716 358 048* <http://wso2.com/>*
>>>>
>>>>
>>>> * <http://wso2.com/>*
>>>>
>>>>
>>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
I have now merged topology event listerners in Autoscaler that were
introduced in service grouping and committed changes to
docker-grouping-merge branch.
Now we can start testing the features and see which parts are broken.
Thanks
On Thu, Oct 30, 2014 at 9:54 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I see more changes in Autoscaler, will let you know once its done.
>
> On Thu, Oct 30, 2014 at 6:41 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>> Awesome! great work everyone.
>>
>> On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> *docker-grouping-merge *builds fine now!
>>>
>>> It will be better if everyone of us take one scenario(kubernetes, vm
>>> etc) and make sure it is functionally working correctly.
>>>
>>> I would like to take the kubernetes stuff and make sure everything is
>>> properly working.
>>>
>>> Thanks.
>>>
>>> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Thanks Lakmal, we have now resolved compilation issues in the following
>>>> components:
>>>> - Autoscaler
>>>> - Cloud Controller
>>>> - CLI
>>>>
>>>> The latest status of the merge process can be seen here:
>>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>>
>>>> The plan is to first resolve all compilation issues and then fix the
>>>> functional issues.
>>>>
>>>> Thanks
>>>>
>>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <la...@wso2.com>
>>>> wrote:
>>>>
>>>>> Great work Imesh! Please keep update the status.
>>>>>
>>>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>>> Afterwards those conflicts were resolved and committed.
>>>>>>
>>>>>> Now we are trying to compile the components and resolve compilation
>>>>>> issues:
>>>>>> - Found issues in messaging component and resolved
>>>>>> - Currently working on Autoscaler where there are changes in monitor
>>>>>> classes which have been changed in both branches.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <
>>>>>> lakmal@wso2.com> wrote:
>>>>>>
>>>>>>> Yes, targeting GA end of nov.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>>> meppel@cisco.com> wrote:
>>>>>>>
>>>>>>>> So target date of GA would be and of November (as was planned for
>>>>>>>> 4.2), or might this be moved (to when) ?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>>>
>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>> Branch
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Yes
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>
>>>>>>>> So this will move out the 4.1 release to what was planned for 4.2,
>>>>>>>> correct ?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>>>> *To:* dev@stratos.apache.org
>>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master
>>>>>>>> Branch
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi Martin,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Initially we thought of doing two releases for docker and grouping,
>>>>>>>> but due to time constrain we are going to do a single release which carry
>>>>>>>> both grouping and docker in one release which is 4.1.0.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>>>> meppel@cisco.com> wrote:
>>>>>>>>
>>>>>>>> Hi Imesh,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Since we are merging the 4.0.0-grouping branch into the master are
>>>>>>>> these changes (grouping) also going into 4.1 ?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Martin
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>>>> *To:* dev
>>>>>>>> *Subject:* [Important] Merging Grouping Changes to Master Branch
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi Devs,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> We are now in the process of merging service grouping changes
>>>>>>>> (4.0.0-grouping branch) into master branch.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> We have created a new branch: *docker-grouping-merge* for this
>>>>>>>> process from the latest commit in the master branch and merging changes
>>>>>>>> from *4.0.0-grouping* branch to it.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Please try to hold your commits to master branch until we complete
>>>>>>>> this process. If not please double commit your changes to master and
>>>>>>>> docker-grouping-merge branches.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>>
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Lakmal Warusawithana
>>>>>>>>
>>>>>>>> Vice President, Apache Stratos
>>>>>>>>
>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>
>>>>>>>> Mobile : +94714289692
>>>>>>>>
>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Lakmal Warusawithana
>>>>>>>>
>>>>>>>> Vice President, Apache Stratos
>>>>>>>>
>>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>>
>>>>>>>> Mobile : +94714289692
>>>>>>>>
>>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Lakmal Warusawithana
>>>>>>> Vice President, Apache Stratos
>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>> Mobile : +94714289692
>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lakmal Warusawithana
>>>>> Vice President, Apache Stratos
>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>> Mobile : +94714289692
>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Raj
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* <http://wso2.com/>*
>>>
>>>
>>> * <http://wso2.com/>*
>>>
>>>
>>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
I see more changes in Autoscaler, will let you know once its done.
On Thu, Oct 30, 2014 at 6:41 PM, Isuru Haththotuwa <is...@apache.org>
wrote:
> Awesome! great work everyone.
>
> On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Hi,
>>
>> *docker-grouping-merge *builds fine now!
>>
>> It will be better if everyone of us take one scenario(kubernetes, vm etc)
>> and make sure it is functionally working correctly.
>>
>> I would like to take the kubernetes stuff and make sure everything is
>> properly working.
>>
>> Thanks.
>>
>> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Thanks Lakmal, we have now resolved compilation issues in the following
>>> components:
>>> - Autoscaler
>>> - Cloud Controller
>>> - CLI
>>>
>>> The latest status of the merge process can be seen here:
>>> https://issues.apache.org/jira/browse/STRATOS-924
>>>
>>> The plan is to first resolve all compilation issues and then fix the
>>> functional issues.
>>>
>>> Thanks
>>>
>>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <la...@wso2.com>
>>> wrote:
>>>
>>>> Great work Imesh! Please keep update the status.
>>>>
>>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>>> branch using git merge tool and found around 50 conflicting files.
>>>>> Afterwards those conflicts were resolved and committed.
>>>>>
>>>>> Now we are trying to compile the components and resolve compilation
>>>>> issues:
>>>>> - Found issues in messaging component and resolved
>>>>> - Currently working on Autoscaler where there are changes in monitor
>>>>> classes which have been changed in both branches.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <
>>>>> lakmal@wso2.com> wrote:
>>>>>
>>>>>> Yes, targeting GA end of nov.
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>>> meppel@cisco.com> wrote:
>>>>>>
>>>>>>> So target date of GA would be and of November (as was planned for
>>>>>>> 4.2), or might this be moved (to when) ?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>>
>>>>>>> *To:* dev@stratos.apache.org
>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Yes
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>>> meppel@cisco.com> wrote:
>>>>>>>
>>>>>>> So this will move out the 4.1 release to what was planned for 4.2,
>>>>>>> correct ?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>>> *To:* dev@stratos.apache.org
>>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi Martin,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Initially we thought of doing two releases for docker and grouping,
>>>>>>> but due to time constrain we are going to do a single release which carry
>>>>>>> both grouping and docker in one release which is 4.1.0.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>>> meppel@cisco.com> wrote:
>>>>>>>
>>>>>>> Hi Imesh,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Since we are merging the 4.0.0-grouping branch into the master are
>>>>>>> these changes (grouping) also going into 4.1 ?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Martin
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>>> *To:* dev
>>>>>>> *Subject:* [Important] Merging Grouping Changes to Master Branch
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi Devs,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> We are now in the process of merging service grouping changes
>>>>>>> (4.0.0-grouping branch) into master branch.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> We have created a new branch: *docker-grouping-merge* for this
>>>>>>> process from the latest commit in the master branch and merging changes
>>>>>>> from *4.0.0-grouping* branch to it.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Please try to hold your commits to master branch until we complete
>>>>>>> this process. If not please double commit your changes to master and
>>>>>>> docker-grouping-merge branches.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>>
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Lakmal Warusawithana
>>>>>>>
>>>>>>> Vice President, Apache Stratos
>>>>>>>
>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>
>>>>>>> Mobile : +94714289692
>>>>>>>
>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Lakmal Warusawithana
>>>>>>>
>>>>>>> Vice President, Apache Stratos
>>>>>>>
>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>>
>>>>>>> Mobile : +94714289692
>>>>>>>
>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Lakmal Warusawithana
>>>>>> Vice President, Apache Stratos
>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>> Mobile : +94714289692
>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Lakmal Warusawithana
>>>> Vice President, Apache Stratos
>>>> Director - Cloud Architecture; WSO2 Inc.
>>>> Mobile : +94714289692
>>>> Blog : http://lakmalsview.blogspot.com/
>>>>
>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Raj
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Isuru Haththotuwa <is...@apache.org>.
Awesome! great work everyone.
On Thu, Oct 30, 2014 at 6:22 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Hi,
>
> *docker-grouping-merge *builds fine now!
>
> It will be better if everyone of us take one scenario(kubernetes, vm etc)
> and make sure it is functionally working correctly.
>
> I would like to take the kubernetes stuff and make sure everything is
> properly working.
>
> Thanks.
>
> On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Thanks Lakmal, we have now resolved compilation issues in the following
>> components:
>> - Autoscaler
>> - Cloud Controller
>> - CLI
>>
>> The latest status of the merge process can be seen here:
>> https://issues.apache.org/jira/browse/STRATOS-924
>>
>> The plan is to first resolve all compilation issues and then fix the
>> functional issues.
>>
>> Thanks
>>
>> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <la...@wso2.com>
>> wrote:
>>
>>> Great work Imesh! Please keep update the status.
>>>
>>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>>> branch using git merge tool and found around 50 conflicting files.
>>>> Afterwards those conflicts were resolved and committed.
>>>>
>>>> Now we are trying to compile the components and resolve compilation
>>>> issues:
>>>> - Found issues in messaging component and resolved
>>>> - Currently working on Autoscaler where there are changes in monitor
>>>> classes which have been changed in both branches.
>>>>
>>>> Thanks
>>>>
>>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <lakmal@wso2.com
>>>> > wrote:
>>>>
>>>>> Yes, targeting GA end of nov.
>>>>>
>>>>>
>>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>>> meppel@cisco.com> wrote:
>>>>>
>>>>>> So target date of GA would be and of November (as was planned for
>>>>>> 4.2), or might this be moved (to when) ?
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>>
>>>>>> *To:* dev@stratos.apache.org
>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>>>>>
>>>>>>
>>>>>>
>>>>>> Yes
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>>> meppel@cisco.com> wrote:
>>>>>>
>>>>>> So this will move out the 4.1 release to what was planned for 4.2,
>>>>>> correct ?
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>>> *To:* dev@stratos.apache.org
>>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Martin,
>>>>>>
>>>>>>
>>>>>>
>>>>>> Initially we thought of doing two releases for docker and grouping,
>>>>>> but due to time constrain we are going to do a single release which carry
>>>>>> both grouping and docker in one release which is 4.1.0.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>>> meppel@cisco.com> wrote:
>>>>>>
>>>>>> Hi Imesh,
>>>>>>
>>>>>>
>>>>>>
>>>>>> Since we are merging the 4.0.0-grouping branch into the master are
>>>>>> these changes (grouping) also going into 4.1 ?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>>
>>>>>> Martin
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>>> *To:* dev
>>>>>> *Subject:* [Important] Merging Grouping Changes to Master Branch
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Devs,
>>>>>>
>>>>>>
>>>>>>
>>>>>> We are now in the process of merging service grouping changes
>>>>>> (4.0.0-grouping branch) into master branch.
>>>>>>
>>>>>>
>>>>>>
>>>>>> We have created a new branch: *docker-grouping-merge* for this
>>>>>> process from the latest commit in the master branch and merging changes
>>>>>> from *4.0.0-grouping* branch to it.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Please try to hold your commits to master branch until we complete
>>>>>> this process. If not please double commit your changes to master and
>>>>>> docker-grouping-merge branches.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>>
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>>
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Lakmal Warusawithana
>>>>>>
>>>>>> Vice President, Apache Stratos
>>>>>>
>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>
>>>>>> Mobile : +94714289692
>>>>>>
>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Lakmal Warusawithana
>>>>>>
>>>>>> Vice President, Apache Stratos
>>>>>>
>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>
>>>>>> Mobile : +94714289692
>>>>>>
>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lakmal Warusawithana
>>>>> Vice President, Apache Stratos
>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>> Mobile : +94714289692
>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Lakmal Warusawithana
>>> Vice President, Apache Stratos
>>> Director - Cloud Architecture; WSO2 Inc.
>>> Mobile : +94714289692
>>> Blog : http://lakmalsview.blogspot.com/
>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Raj
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Hi,
*docker-grouping-merge *builds fine now!
It will be better if everyone of us take one scenario(kubernetes, vm etc)
and make sure it is functionally working correctly.
I would like to take the kubernetes stuff and make sure everything is
properly working.
Thanks.
On Thu, Oct 30, 2014 at 3:26 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Thanks Lakmal, we have now resolved compilation issues in the following
> components:
> - Autoscaler
> - Cloud Controller
> - CLI
>
> The latest status of the merge process can be seen here:
> https://issues.apache.org/jira/browse/STRATOS-924
>
> The plan is to first resolve all compilation issues and then fix the
> functional issues.
>
> Thanks
>
> On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <la...@wso2.com>
> wrote:
>
>> Great work Imesh! Please keep update the status.
>>
>> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>>> branch using git merge tool and found around 50 conflicting files.
>>> Afterwards those conflicts were resolved and committed.
>>>
>>> Now we are trying to compile the components and resolve compilation
>>> issues:
>>> - Found issues in messaging component and resolved
>>> - Currently working on Autoscaler where there are changes in monitor
>>> classes which have been changed in both branches.
>>>
>>> Thanks
>>>
>>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <la...@wso2.com>
>>> wrote:
>>>
>>>> Yes, targeting GA end of nov.
>>>>
>>>>
>>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>>> meppel@cisco.com> wrote:
>>>>
>>>>> So target date of GA would be and of November (as was planned for
>>>>> 4.2), or might this be moved (to when) ?
>>>>>
>>>>>
>>>>>
>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>>
>>>>> *To:* dev@stratos.apache.org
>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>>>>
>>>>>
>>>>>
>>>>> Yes
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>>> meppel@cisco.com> wrote:
>>>>>
>>>>> So this will move out the 4.1 release to what was planned for 4.2,
>>>>> correct ?
>>>>>
>>>>>
>>>>>
>>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>>> *To:* dev@stratos.apache.org
>>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>>>>
>>>>>
>>>>>
>>>>> Hi Martin,
>>>>>
>>>>>
>>>>>
>>>>> Initially we thought of doing two releases for docker and grouping,
>>>>> but due to time constrain we are going to do a single release which carry
>>>>> both grouping and docker in one release which is 4.1.0.
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>>> meppel@cisco.com> wrote:
>>>>>
>>>>> Hi Imesh,
>>>>>
>>>>>
>>>>>
>>>>> Since we are merging the 4.0.0-grouping branch into the master are
>>>>> these changes (grouping) also going into 4.1 ?
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> Martin
>>>>>
>>>>>
>>>>>
>>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>>> *To:* dev
>>>>> *Subject:* [Important] Merging Grouping Changes to Master Branch
>>>>>
>>>>>
>>>>>
>>>>> Hi Devs,
>>>>>
>>>>>
>>>>>
>>>>> We are now in the process of merging service grouping changes
>>>>> (4.0.0-grouping branch) into master branch.
>>>>>
>>>>>
>>>>>
>>>>> We have created a new branch: *docker-grouping-merge* for this
>>>>> process from the latest commit in the master branch and merging changes
>>>>> from *4.0.0-grouping* branch to it.
>>>>>
>>>>>
>>>>>
>>>>> Please try to hold your commits to master branch until we complete
>>>>> this process. If not please double commit your changes to master and
>>>>> docker-grouping-merge branches.
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Imesh Gunaratne
>>>>>
>>>>>
>>>>>
>>>>> Technical Lead, WSO2
>>>>>
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Lakmal Warusawithana
>>>>>
>>>>> Vice President, Apache Stratos
>>>>>
>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>
>>>>> Mobile : +94714289692
>>>>>
>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Lakmal Warusawithana
>>>>>
>>>>> Vice President, Apache Stratos
>>>>>
>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>
>>>>> Mobile : +94714289692
>>>>>
>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Lakmal Warusawithana
>>>> Vice President, Apache Stratos
>>>> Director - Cloud Architecture; WSO2 Inc.
>>>> Mobile : +94714289692
>>>> Blog : http://lakmalsview.blogspot.com/
>>>>
>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Lakmal Warusawithana
>> Vice President, Apache Stratos
>> Director - Cloud Architecture; WSO2 Inc.
>> Mobile : +94714289692
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Raj
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Thanks Lakmal, we have now resolved compilation issues in the following
components:
- Autoscaler
- Cloud Controller
- CLI
The latest status of the merge process can be seen here:
https://issues.apache.org/jira/browse/STRATOS-924
The plan is to first resolve all compilation issues and then fix the
functional issues.
Thanks
On Thu, Oct 30, 2014 at 2:11 PM, Lakmal Warusawithana <la...@wso2.com>
wrote:
> Great work Imesh! Please keep update the status.
>
> On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Hi,
>>
>> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
>> branch using git merge tool and found around 50 conflicting files.
>> Afterwards those conflicts were resolved and committed.
>>
>> Now we are trying to compile the components and resolve compilation
>> issues:
>> - Found issues in messaging component and resolved
>> - Currently working on Autoscaler where there are changes in monitor
>> classes which have been changed in both branches.
>>
>> Thanks
>>
>> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <la...@wso2.com>
>> wrote:
>>
>>> Yes, targeting GA end of nov.
>>>
>>>
>>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <
>>> meppel@cisco.com> wrote:
>>>
>>>> So target date of GA would be and of November (as was planned for
>>>> 4.2), or might this be moved (to when) ?
>>>>
>>>>
>>>>
>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>>
>>>> *To:* dev@stratos.apache.org
>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>>>
>>>>
>>>>
>>>> Yes
>>>>
>>>>
>>>>
>>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>>> meppel@cisco.com> wrote:
>>>>
>>>> So this will move out the 4.1 release to what was planned for 4.2,
>>>> correct ?
>>>>
>>>>
>>>>
>>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>>> *To:* dev@stratos.apache.org
>>>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>>>
>>>>
>>>>
>>>> Hi Martin,
>>>>
>>>>
>>>>
>>>> Initially we thought of doing two releases for docker and grouping, but
>>>> due to time constrain we are going to do a single release which carry both
>>>> grouping and docker in one release which is 4.1.0.
>>>>
>>>>
>>>>
>>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <
>>>> meppel@cisco.com> wrote:
>>>>
>>>> Hi Imesh,
>>>>
>>>>
>>>>
>>>> Since we are merging the 4.0.0-grouping branch into the master are
>>>> these changes (grouping) also going into 4.1 ?
>>>>
>>>>
>>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>> Martin
>>>>
>>>>
>>>>
>>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>>> *To:* dev
>>>> *Subject:* [Important] Merging Grouping Changes to Master Branch
>>>>
>>>>
>>>>
>>>> Hi Devs,
>>>>
>>>>
>>>>
>>>> We are now in the process of merging service grouping changes
>>>> (4.0.0-grouping branch) into master branch.
>>>>
>>>>
>>>>
>>>> We have created a new branch: *docker-grouping-merge* for this process
>>>> from the latest commit in the master branch and merging changes from
>>>> *4.0.0-grouping* branch to it.
>>>>
>>>>
>>>>
>>>> Please try to hold your commits to master branch until we complete this
>>>> process. If not please double commit your changes to master and
>>>> docker-grouping-merge branches.
>>>>
>>>>
>>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Imesh Gunaratne
>>>>
>>>>
>>>>
>>>> Technical Lead, WSO2
>>>>
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Lakmal Warusawithana
>>>>
>>>> Vice President, Apache Stratos
>>>>
>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>
>>>> Mobile : +94714289692
>>>>
>>>> Blog : http://lakmalsview.blogspot.com/
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Lakmal Warusawithana
>>>>
>>>> Vice President, Apache Stratos
>>>>
>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>
>>>> Mobile : +94714289692
>>>>
>>>> Blog : http://lakmalsview.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Lakmal Warusawithana
>>> Vice President, Apache Stratos
>>> Director - Cloud Architecture; WSO2 Inc.
>>> Mobile : +94714289692
>>> Blog : http://lakmalsview.blogspot.com/
>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Lakmal Warusawithana
> Vice President, Apache Stratos
> Director - Cloud Architecture; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lakmal Warusawithana <la...@wso2.com>.
Great work Imesh! Please keep update the status.
On Thu, Oct 30, 2014 at 1:52 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi,
>
> We merged changes from 4.0.0-grouping branch to docker-grouping-merge
> branch using git merge tool and found around 50 conflicting files.
> Afterwards those conflicts were resolved and committed.
>
> Now we are trying to compile the components and resolve compilation
> issues:
> - Found issues in messaging component and resolved
> - Currently working on Autoscaler where there are changes in monitor
> classes which have been changed in both branches.
>
> Thanks
>
> On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <la...@wso2.com>
> wrote:
>
>> Yes, targeting GA end of nov.
>>
>>
>> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <meppel@cisco.com
>> > wrote:
>>
>>> So target date of GA would be and of November (as was planned for
>>> 4.2), or might this be moved (to when) ?
>>>
>>>
>>>
>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>>
>>> *To:* dev@stratos.apache.org
>>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>>
>>>
>>>
>>> Yes
>>>
>>>
>>>
>>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <
>>> meppel@cisco.com> wrote:
>>>
>>> So this will move out the 4.1 release to what was planned for 4.2,
>>> correct ?
>>>
>>>
>>>
>>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>>> *To:* dev@stratos.apache.org
>>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>>
>>>
>>>
>>> Hi Martin,
>>>
>>>
>>>
>>> Initially we thought of doing two releases for docker and grouping, but
>>> due to time constrain we are going to do a single release which carry both
>>> grouping and docker in one release which is 4.1.0.
>>>
>>>
>>>
>>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <me...@cisco.com>
>>> wrote:
>>>
>>> Hi Imesh,
>>>
>>>
>>>
>>> Since we are merging the 4.0.0-grouping branch into the master are these
>>> changes (grouping) also going into 4.1 ?
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> Martin
>>>
>>>
>>>
>>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>>> *To:* dev
>>> *Subject:* [Important] Merging Grouping Changes to Master Branch
>>>
>>>
>>>
>>> Hi Devs,
>>>
>>>
>>>
>>> We are now in the process of merging service grouping changes
>>> (4.0.0-grouping branch) into master branch.
>>>
>>>
>>>
>>> We have created a new branch: *docker-grouping-merge* for this process
>>> from the latest commit in the master branch and merging changes from
>>> *4.0.0-grouping* branch to it.
>>>
>>>
>>>
>>> Please try to hold your commits to master branch until we complete this
>>> process. If not please double commit your changes to master and
>>> docker-grouping-merge branches.
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Imesh Gunaratne
>>>
>>>
>>>
>>> Technical Lead, WSO2
>>>
>>> Committer & PMC Member, Apache Stratos
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Lakmal Warusawithana
>>>
>>> Vice President, Apache Stratos
>>>
>>> Director - Cloud Architecture; WSO2 Inc.
>>>
>>> Mobile : +94714289692
>>>
>>> Blog : http://lakmalsview.blogspot.com/
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Lakmal Warusawithana
>>>
>>> Vice President, Apache Stratos
>>>
>>> Director - Cloud Architecture; WSO2 Inc.
>>>
>>> Mobile : +94714289692
>>>
>>> Blog : http://lakmalsview.blogspot.com/
>>>
>>
>>
>>
>> --
>> Lakmal Warusawithana
>> Vice President, Apache Stratos
>> Director - Cloud Architecture; WSO2 Inc.
>> Mobile : +94714289692
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Imesh Gunaratne <im...@apache.org>.
Hi,
We merged changes from 4.0.0-grouping branch to docker-grouping-merge
branch using git merge tool and found around 50 conflicting files.
Afterwards those conflicts were resolved and committed.
Now we are trying to compile the components and resolve compilation issues:
- Found issues in messaging component and resolved
- Currently working on Autoscaler where there are changes in monitor
classes which have been changed in both branches.
Thanks
On Wed, Oct 29, 2014 at 10:30 PM, Lakmal Warusawithana <la...@wso2.com>
wrote:
> Yes, targeting GA end of nov.
>
>
> On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <me...@cisco.com>
> wrote:
>
>> So target date of GA would be and of November (as was planned for 4.2),
>> or might this be moved (to when) ?
>>
>>
>>
>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>> *Sent:* Wednesday, October 29, 2014 9:45 AM
>>
>> *To:* dev@stratos.apache.org
>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>
>>
>>
>> Yes
>>
>>
>>
>> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <me...@cisco.com>
>> wrote:
>>
>> So this will move out the 4.1 release to what was planned for 4.2,
>> correct ?
>>
>>
>>
>> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
>> *Sent:* Wednesday, October 29, 2014 9:29 AM
>> *To:* dev@stratos.apache.org
>> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>>
>>
>>
>> Hi Martin,
>>
>>
>>
>> Initially we thought of doing two releases for docker and grouping, but
>> due to time constrain we are going to do a single release which carry both
>> grouping and docker in one release which is 4.1.0.
>>
>>
>>
>> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <me...@cisco.com>
>> wrote:
>>
>> Hi Imesh,
>>
>>
>>
>> Since we are merging the 4.0.0-grouping branch into the master are these
>> changes (grouping) also going into 4.1 ?
>>
>>
>>
>> Thanks
>>
>>
>>
>> Martin
>>
>>
>>
>> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
>> *Sent:* Wednesday, October 29, 2014 6:33 AM
>> *To:* dev
>> *Subject:* [Important] Merging Grouping Changes to Master Branch
>>
>>
>>
>> Hi Devs,
>>
>>
>>
>> We are now in the process of merging service grouping changes
>> (4.0.0-grouping branch) into master branch.
>>
>>
>>
>> We have created a new branch: *docker-grouping-merge* for this process
>> from the latest commit in the master branch and merging changes from
>> *4.0.0-grouping* branch to it.
>>
>>
>>
>> Please try to hold your commits to master branch until we complete this
>> process. If not please double commit your changes to master and
>> docker-grouping-merge branches.
>>
>>
>>
>> Thanks
>>
>>
>>
>>
>> --
>>
>> Imesh Gunaratne
>>
>>
>>
>> Technical Lead, WSO2
>>
>> Committer & PMC Member, Apache Stratos
>>
>>
>>
>>
>>
>> --
>>
>> Lakmal Warusawithana
>>
>> Vice President, Apache Stratos
>>
>> Director - Cloud Architecture; WSO2 Inc.
>>
>> Mobile : +94714289692
>>
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>>
>>
>>
>> --
>>
>> Lakmal Warusawithana
>>
>> Vice President, Apache Stratos
>>
>> Director - Cloud Architecture; WSO2 Inc.
>>
>> Mobile : +94714289692
>>
>> Blog : http://lakmalsview.blogspot.com/
>>
>
>
>
> --
> Lakmal Warusawithana
> Vice President, Apache Stratos
> Director - Cloud Architecture; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lakmal Warusawithana <la...@wso2.com>.
Yes, targeting GA end of nov.
On Wed, Oct 29, 2014 at 10:27 PM, Martin Eppel (meppel) <me...@cisco.com>
wrote:
> So target date of GA would be and of November (as was planned for 4.2),
> or might this be moved (to when) ?
>
>
>
> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
> *Sent:* Wednesday, October 29, 2014 9:45 AM
>
> *To:* dev@stratos.apache.org
> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>
>
>
> Yes
>
>
>
> On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <me...@cisco.com>
> wrote:
>
> So this will move out the 4.1 release to what was planned for 4.2, correct
> ?
>
>
>
> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
> *Sent:* Wednesday, October 29, 2014 9:29 AM
> *To:* dev@stratos.apache.org
> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>
>
>
> Hi Martin,
>
>
>
> Initially we thought of doing two releases for docker and grouping, but
> due to time constrain we are going to do a single release which carry both
> grouping and docker in one release which is 4.1.0.
>
>
>
> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <me...@cisco.com>
> wrote:
>
> Hi Imesh,
>
>
>
> Since we are merging the 4.0.0-grouping branch into the master are these
> changes (grouping) also going into 4.1 ?
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
> *Sent:* Wednesday, October 29, 2014 6:33 AM
> *To:* dev
> *Subject:* [Important] Merging Grouping Changes to Master Branch
>
>
>
> Hi Devs,
>
>
>
> We are now in the process of merging service grouping changes
> (4.0.0-grouping branch) into master branch.
>
>
>
> We have created a new branch: *docker-grouping-merge* for this process
> from the latest commit in the master branch and merging changes from
> *4.0.0-grouping* branch to it.
>
>
>
> Please try to hold your commits to master branch until we complete this
> process. If not please double commit your changes to master and
> docker-grouping-merge branches.
>
>
>
> Thanks
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
>
> --
>
> Lakmal Warusawithana
>
> Vice President, Apache Stratos
>
> Director - Cloud Architecture; WSO2 Inc.
>
> Mobile : +94714289692
>
> Blog : http://lakmalsview.blogspot.com/
>
>
>
>
>
> --
>
> Lakmal Warusawithana
>
> Vice President, Apache Stratos
>
> Director - Cloud Architecture; WSO2 Inc.
>
> Mobile : +94714289692
>
> Blog : http://lakmalsview.blogspot.com/
>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
RE: [Important] Merging Grouping Changes to Master Branch
Posted by "Martin Eppel (meppel)" <me...@cisco.com>.
So target date of GA would be and of November (as was planned for 4.2), or might this be moved (to when) ?
From: Lakmal Warusawithana [mailto:lakmal@wso2.com]
Sent: Wednesday, October 29, 2014 9:45 AM
To: dev@stratos.apache.org
Subject: Re: [Important] Merging Grouping Changes to Master Branch
Yes
On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <me...@cisco.com>> wrote:
So this will move out the 4.1 release to what was planned for 4.2, correct ?
From: Lakmal Warusawithana [mailto:lakmal@wso2.com<ma...@wso2.com>]
Sent: Wednesday, October 29, 2014 9:29 AM
To: dev@stratos.apache.org<ma...@stratos.apache.org>
Subject: Re: [Important] Merging Grouping Changes to Master Branch
Hi Martin,
Initially we thought of doing two releases for docker and grouping, but due to time constrain we are going to do a single release which carry both grouping and docker in one release which is 4.1.0.
On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <me...@cisco.com>> wrote:
Hi Imesh,
Since we are merging the 4.0.0-grouping branch into the master are these changes (grouping) also going into 4.1 ?
Thanks
Martin
From: Imesh Gunaratne [mailto:imesh@apache.org<ma...@apache.org>]
Sent: Wednesday, October 29, 2014 6:33 AM
To: dev
Subject: [Important] Merging Grouping Changes to Master Branch
Hi Devs,
We are now in the process of merging service grouping changes (4.0.0-grouping branch) into master branch.
We have created a new branch: docker-grouping-merge for this process from the latest commit in the master branch and merging changes from 4.0.0-grouping branch to it.
Please try to hold your commits to master branch until we complete this process. If not please double commit your changes to master and docker-grouping-merge branches.
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692<tel:%2B94714289692>
Blog : http://lakmalsview.blogspot.com/
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lakmal Warusawithana <la...@wso2.com>.
Yes
On Wed, Oct 29, 2014 at 10:10 PM, Martin Eppel (meppel) <me...@cisco.com>
wrote:
> So this will move out the 4.1 release to what was planned for 4.2,
> correct ?
>
>
>
> *From:* Lakmal Warusawithana [mailto:lakmal@wso2.com]
> *Sent:* Wednesday, October 29, 2014 9:29 AM
> *To:* dev@stratos.apache.org
> *Subject:* Re: [Important] Merging Grouping Changes to Master Branch
>
>
>
> Hi Martin,
>
>
>
> Initially we thought of doing two releases for docker and grouping, but
> due to time constrain we are going to do a single release which carry both
> grouping and docker in one release which is 4.1.0.
>
>
>
> On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <me...@cisco.com>
> wrote:
>
> Hi Imesh,
>
>
>
> Since we are merging the 4.0.0-grouping branch into the master are these
> changes (grouping) also going into 4.1 ?
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
> *Sent:* Wednesday, October 29, 2014 6:33 AM
> *To:* dev
> *Subject:* [Important] Merging Grouping Changes to Master Branch
>
>
>
> Hi Devs,
>
>
>
> We are now in the process of merging service grouping changes
> (4.0.0-grouping branch) into master branch.
>
>
>
> We have created a new branch: *docker-grouping-merge* for this process
> from the latest commit in the master branch and merging changes from
> *4.0.0-grouping* branch to it.
>
>
>
> Please try to hold your commits to master branch until we complete this
> process. If not please double commit your changes to master and
> docker-grouping-merge branches.
>
>
>
> Thanks
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
>
> --
>
> Lakmal Warusawithana
>
> Vice President, Apache Stratos
>
> Director - Cloud Architecture; WSO2 Inc.
>
> Mobile : +94714289692
>
> Blog : http://lakmalsview.blogspot.com/
>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
RE: [Important] Merging Grouping Changes to Master Branch
Posted by "Martin Eppel (meppel)" <me...@cisco.com>.
So this will move out the 4.1 release to what was planned for 4.2, correct ?
From: Lakmal Warusawithana [mailto:lakmal@wso2.com]
Sent: Wednesday, October 29, 2014 9:29 AM
To: dev@stratos.apache.org
Subject: Re: [Important] Merging Grouping Changes to Master Branch
Hi Martin,
Initially we thought of doing two releases for docker and grouping, but due to time constrain we are going to do a single release which carry both grouping and docker in one release which is 4.1.0.
On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <me...@cisco.com>> wrote:
Hi Imesh,
Since we are merging the 4.0.0-grouping branch into the master are these changes (grouping) also going into 4.1 ?
Thanks
Martin
From: Imesh Gunaratne [mailto:imesh@apache.org<ma...@apache.org>]
Sent: Wednesday, October 29, 2014 6:33 AM
To: dev
Subject: [Important] Merging Grouping Changes to Master Branch
Hi Devs,
We are now in the process of merging service grouping changes (4.0.0-grouping branch) into master branch.
We have created a new branch: docker-grouping-merge for this process from the latest commit in the master branch and merging changes from 4.0.0-grouping branch to it.
Please try to hold your commits to master branch until we complete this process. If not please double commit your changes to master and docker-grouping-merge branches.
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: [Important] Merging Grouping Changes to Master Branch
Posted by Lakmal Warusawithana <la...@wso2.com>.
Hi Martin,
Initially we thought of doing two releases for docker and grouping, but due
to time constrain we are going to do a single release which carry both
grouping and docker in one release which is 4.1.0.
On Wed, Oct 29, 2014 at 9:37 PM, Martin Eppel (meppel) <me...@cisco.com>
wrote:
> Hi Imesh,
>
>
>
> Since we are merging the 4.0.0-grouping branch into the master are these
> changes (grouping) also going into 4.1 ?
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
> *Sent:* Wednesday, October 29, 2014 6:33 AM
> *To:* dev
> *Subject:* [Important] Merging Grouping Changes to Master Branch
>
>
>
> Hi Devs,
>
>
>
> We are now in the process of merging service grouping changes
> (4.0.0-grouping branch) into master branch.
>
>
>
> We have created a new branch: *docker-grouping-merge* for this process
> from the latest commit in the master branch and merging changes from
> *4.0.0-grouping* branch to it.
>
>
>
> Please try to hold your commits to master branch until we complete this
> process. If not please double commit your changes to master and
> docker-grouping-merge branches.
>
>
>
> Thanks
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
RE: [Important] Merging Grouping Changes to Master Branch
Posted by "Martin Eppel (meppel)" <me...@cisco.com>.
Hi Imesh,
Since we are merging the 4.0.0-grouping branch into the master are these changes (grouping) also going into 4.1 ?
Thanks
Martin
From: Imesh Gunaratne [mailto:imesh@apache.org]
Sent: Wednesday, October 29, 2014 6:33 AM
To: dev
Subject: [Important] Merging Grouping Changes to Master Branch
Hi Devs,
We are now in the process of merging service grouping changes (4.0.0-grouping branch) into master branch.
We have created a new branch: docker-grouping-merge for this process from the latest commit in the master branch and merging changes from 4.0.0-grouping branch to it.
Please try to hold your commits to master branch until we complete this process. If not please double commit your changes to master and docker-grouping-merge branches.
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos