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 2015/01/02 05:34:34 UTC
[Discuss] Finalizing 4.1.0-Alpha Release
Hi Devs,
Wish you a Very Happy New Year! Hope you all had a great holiday!
We have now come to the last stage of finalizing 4.1.0-Alpha release. As I
can recall following are the remaining tasks we need to complete:
*1. Finalize Kubernetes Workflow:*
During past few days I was fixing issues in the Kubernetes workflow and
following are the remaining problems:
- Python agent does not publish health statistitics to CEP.
- Autoscaler obsolete member rule invokes terminateInstance() method twice
with the same member id. As a result the second call fails.
I'm currently working on fixing the above issues and finalizing the
Kubernetes workflow.
*2. Verify Service Grouping on OpenStack and EC2:*
I believe we verified the complete service grouping functionality with Mock
IaaS however we could not test it with OpenStack and EC2.
*3. Verify Clustering Support for Stratos Components:*
I did the initial implementation of clustering support for Load Balancer
and Cloud Controller, we need to verify it and apply it to Autoscaler and
Stratos Manager.
*4. Load Balancer Configuration for Service Grouping:*
Service grouping functionality allows us to add a load balancer cartridge
to an application or group. However we need to provide a configuration
option to specify which cartridges to be served by a given load balancer
cartridge.
*5. Reduce the Docker Image Size:*
Currently Docker base image size is around 380 MB and PHP Docker image size
is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we need to
download the Docker images from Docker Hub once. It would be better if we
could reduce the size of the base image so that we could save time on this
process.
It would be great if anyone would like to contribute to remaining tasks, we
will try our best to complete them ASAP and announce 4.1.0-Alpha release.
Many Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Devs,
We have now completed almost all the tasks needed for 4.1.0-Alpha release:
1. Finalize Kubernetes Workflow (DONE)
2. Verify Service Grouping on OpenStack and EC2 (DONE)
3. Verify Clustering Support for Stratos Components (DONE)
4. Implement Load Balancer Configuration for Service Grouping (DONE)
5. Implement ADC logic for Service Grouping (DONE)
6. Implement Multi-Tenant support for Applications (DONE)
7. Verify Domain Mappings Functionality (DONE)
8. Verify Tenant Partitioning Functionality for Multi-Tenant Applications
(DONE)
Thanks
On Sun, Jan 11, 2015 at 2:07 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I have now completed task 8:
> - Added tenantPartitions property to cartridge bean in the REST API.
> - Updated cloud controller service definition to handle tenant partitions.
> - Updated default application parser to find the tenant range from tenant
> id and tenant partitions for each cluster.
> - Implemented a unit test to verify above logic.
> - Tenant range was added to cluster.
>
> Now the latest task status looks as follows:
>
> 1. Finalize Kubernetes Workflow (DONE)
> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
> 4. Implement Load Balancer Configuration for Service Grouping (DONE)
> 5. Implement ADC logic for Service Grouping (DONE)
> 6. Implement Multi-Tenant support for Applications (DONE)
> 7. Verify Domain Mappings Functionality (DONE)
> 8. Verify Tenant Partitioning Functionality for Multi-Tenant Applications
> (DONE)
>
> Thanks
>
> On Sun, Jan 11, 2015 at 12:06 PM, Imesh Gunaratne <im...@apache.org>
> wrote:
>
>> Shiro has contributed to clustering implementation in Autoscaler with the
>> following pull request [1] and it is now merged to master branch.
>>
>> [1] https://github.com/apache/stratos/pull/165
>>
>> On Sun, Jan 11, 2015 at 9:47 AM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> We have now completed domain mappings functionality, now the latest task
>>> status looks as follows:
>>>
>>> 1. Finalize Kubernetes Workflow (DONE)
>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>> 4. Implement Load Balancer Configuration for Service Grouping (DONE)
>>> 5. Implement ADC logic for Service Grouping (DONE)
>>> 6. Implement Multi-Tenant support for Applications (DONE)
>>> 7. Verify Domain Mappings Functionality (DONE)
>>> *8. Verify Tenant Partitioning Functionality for Multi-Tenant
>>> Applications*
>>>
>>> I'm now working on task 3: verifying clustering functionality.
>>> Appreciate if someone could contribute to task 8.
>>>
>>> Thanks
>>>
>>> On Fri, Jan 9, 2015 at 11:54 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Thanks Lakmal, yes we could remove docker image resizing effort from
>>>> alpha release since we have completed Kubernetes workflow. We have also
>>>> completed the load balancer configuration task, now the latest task list
>>>> status would be as follows:
>>>>
>>>> 1. Finalize Kubernetes Workflow (DONE)
>>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>>> 4. Implement Load Balancer Configuration for Service Grouping (DONE)
>>>> 5. Implement ADC logic for Service Grouping (DONE)
>>>> 6. Implement Multi-Tenant support for Applications (DONE)
>>>> *7. Verify Domain Mappings Functionality (IN-PROGRESS)*
>>>> *8. Verify Tenant Partitioning Functionality for Multi-Tenant
>>>> Applications*
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Jan 9, 2015 at 11:45 AM, Lakmal Warusawithana <la...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Fri, Jan 9, 2015 at 11:39 AM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi Devs,
>>>>>>
>>>>>> I'm now working on fixing Domain Mapping functionality. While doing
>>>>>> this I found another functionality which we need to fix (Task-9):
>>>>>>
>>>>>> 1. Finalize Kubernetes Workflow (DONE)
>>>>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>>>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>>>>> *4. Implement Load Balancer Configuration for Service Grouping
>>>>>> (IN-PROGRESS)*
>>>>>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>>>>>>
>>>>>
>>>>> IMO, we can take off #5 from the alpha release.
>>>>>
>>>>>
>>>>>> 6. Implement ADC logic for Service Grouping (DONE)
>>>>>> 7. Implement Multi-Tenant support for Applications (DONE)
>>>>>> *8. Verify Domain Mappings Functionality (IN-PROGRESS)*
>>>>>> *9. Verify Tenant Partitioning Functionality for Multi-Tenant
>>>>>> Applications*
>>>>>> As it looks like current cartridge definition does not allow us to
>>>>>> define tenant partitions. This is needed for creating multiple clusters for
>>>>>> a multi-tenant cartridge if tenant partitions are defined.
>>>>>>
>>>>>> *Example:*
>>>>>> Cartridge A (Multi-Tenant)
>>>>>> Tenant Partitions: 1-100,101-200,201-*
>>>>>> Clusters: Cluster-1 (Tenant-Range: 1-100), Cluster-2 (Tenant-Range:
>>>>>> 101-200), Cluster-3 (Tenant-Range: 201-*)
>>>>>> All three clusters; Cluster-1, Cluster-2 & Cluster-3 will have the
>>>>>> same host name.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Wed, Jan 7, 2015 at 7:38 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Devs,
>>>>>>>
>>>>>>> Please find the latest status of the tasks we need to complete for
>>>>>>> 4.1.0-Alpha release below:
>>>>>>>
>>>>>>> 1. Finalize Kubernetes Workflow (DONE)
>>>>>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>>>>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>>>>>> *4. Implement Load Balancer Configuration for Service Grouping
>>>>>>> (IN-PROGRESS)*
>>>>>>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>>>>>>> 6. Implement ADC logic for Service Grouping (DONE)
>>>>>>> 7. Implement Multi-Tenant support for Applications (DONE)
>>>>>>> *8. Verify Domain Mappings Functionality*
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Wed, Jan 7, 2015 at 1:50 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Great work Sajith! Now we have verified both OpenStack and EC2 on
>>>>>>>> the latest codebase.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Wed, Jan 7, 2015 at 1:21 PM, Sajith Kariyawasam <sajith@wso2.com
>>>>>>>> > wrote:
>>>>>>>>
>>>>>>>>> I tested the basic flow in Openstack, and it worked fine. I used a
>>>>>>>>> single cartridge (tomcat) and got the member activated event. Were able to
>>>>>>>>> access tomcat home page.
>>>>>>>>> Now I'm in the process of testing more complex scenarios
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Sajith
>>>>>>>>>
>>>>>>>>> On Tue, Jan 6, 2015 at 1:21 PM, Sajith Kariyawasam <
>>>>>>>>> sajith@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> I fixed this now. Verified with a tomcat cartridge in Openstack
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 6, 2015 at 11:55 AM, Manula Chathurika Thantriwatte <
>>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> DEPLOYMENT payload parameter set in two places in
>>>>>>>>>>> BasicPayloadData and ApplicationUtils. Can we set this in one place ?
>>>>>>>>>>>
>>>>>>>>>>> Thanks !
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <
>>>>>>>>>>> sajith@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Found an issue while testing in Openstack, DEPLOYMENT payload
>>>>>>>>>>>> parameter is set twice, as follows..
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
>>>>>>>>>>>> tomcat.tomcat.apache.org
>>>>>>>>>>>> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
>>>>>>>>>>>> *DEPLOYMENT*
>>>>>>>>>>>> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
>>>>>>>>>>>> *DEPLOYMENT*=default,
>>>>>>>>>>>>
>>>>>>>>>>>> This causes wrong hostname in the cartridge instance, hence
>>>>>>>>>>>> puppet master doesn't recognize the service type of the node.
>>>>>>>>>>>>
>>>>>>>>>>>> I'm looking into this
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <
>>>>>>>>>>>> mariangela@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I will work with Manula on this task!
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Mariangela
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> *--*
>>>>>>>>>>>>> Mariangela Hills
>>>>>>>>>>>>> Senior Technical Writer
>>>>>>>>>>>>>
>>>>>>>>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>>>>>>>> m: +94 773 500185
>>>>>>>>>>>>> w: http://wso2.com
>>>>>>>>>>>>> <http://wso2.com/events/>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte
>>>>>>>>>>>>> <ma...@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'll work with Mari and update the documentation.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Great work Manula! Really nice to hear that it worked on EC2
>>>>>>>>>>>>>>> without any problems.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I think we need to update the documentation with the
>>>>>>>>>>>>>>> relevant information including how to setup Stratos 4.1.0 on EC2 from
>>>>>>>>>>>>>>> scratch. Appreciate if Mari can assist us on this.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika
>>>>>>>>>>>>>>> Thantriwatte <ma...@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Great work Lahiru!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> 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/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>>>>>
>>>>>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> 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/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>>>
>>>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>>
>>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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/
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
I have now completed task 8:
- Added tenantPartitions property to cartridge bean in the REST API.
- Updated cloud controller service definition to handle tenant partitions.
- Updated default application parser to find the tenant range from tenant
id and tenant partitions for each cluster.
- Implemented a unit test to verify above logic.
- Tenant range was added to cluster.
Now the latest task status looks as follows:
1. Finalize Kubernetes Workflow (DONE)
2. Verify Service Grouping on OpenStack and EC2 (DONE)
*3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
4. Implement Load Balancer Configuration for Service Grouping (DONE)
5. Implement ADC logic for Service Grouping (DONE)
6. Implement Multi-Tenant support for Applications (DONE)
7. Verify Domain Mappings Functionality (DONE)
8. Verify Tenant Partitioning Functionality for Multi-Tenant Applications
(DONE)
Thanks
On Sun, Jan 11, 2015 at 12:06 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Shiro has contributed to clustering implementation in Autoscaler with the
> following pull request [1] and it is now merged to master branch.
>
> [1] https://github.com/apache/stratos/pull/165
>
> On Sun, Jan 11, 2015 at 9:47 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> We have now completed domain mappings functionality, now the latest task
>> status looks as follows:
>>
>> 1. Finalize Kubernetes Workflow (DONE)
>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>> 4. Implement Load Balancer Configuration for Service Grouping (DONE)
>> 5. Implement ADC logic for Service Grouping (DONE)
>> 6. Implement Multi-Tenant support for Applications (DONE)
>> 7. Verify Domain Mappings Functionality (DONE)
>> *8. Verify Tenant Partitioning Functionality for Multi-Tenant
>> Applications*
>>
>> I'm now working on task 3: verifying clustering functionality. Appreciate
>> if someone could contribute to task 8.
>>
>> Thanks
>>
>> On Fri, Jan 9, 2015 at 11:54 AM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Thanks Lakmal, yes we could remove docker image resizing effort from
>>> alpha release since we have completed Kubernetes workflow. We have also
>>> completed the load balancer configuration task, now the latest task list
>>> status would be as follows:
>>>
>>> 1. Finalize Kubernetes Workflow (DONE)
>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>> 4. Implement Load Balancer Configuration for Service Grouping (DONE)
>>> 5. Implement ADC logic for Service Grouping (DONE)
>>> 6. Implement Multi-Tenant support for Applications (DONE)
>>> *7. Verify Domain Mappings Functionality (IN-PROGRESS)*
>>> *8. Verify Tenant Partitioning Functionality for Multi-Tenant
>>> Applications*
>>>
>>> Thanks
>>>
>>> On Fri, Jan 9, 2015 at 11:45 AM, Lakmal Warusawithana <la...@wso2.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Fri, Jan 9, 2015 at 11:39 AM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> I'm now working on fixing Domain Mapping functionality. While doing
>>>>> this I found another functionality which we need to fix (Task-9):
>>>>>
>>>>> 1. Finalize Kubernetes Workflow (DONE)
>>>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>>>> *4. Implement Load Balancer Configuration for Service Grouping
>>>>> (IN-PROGRESS)*
>>>>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>>>>>
>>>>
>>>> IMO, we can take off #5 from the alpha release.
>>>>
>>>>
>>>>> 6. Implement ADC logic for Service Grouping (DONE)
>>>>> 7. Implement Multi-Tenant support for Applications (DONE)
>>>>> *8. Verify Domain Mappings Functionality (IN-PROGRESS)*
>>>>> *9. Verify Tenant Partitioning Functionality for Multi-Tenant
>>>>> Applications*
>>>>> As it looks like current cartridge definition does not allow us to
>>>>> define tenant partitions. This is needed for creating multiple clusters for
>>>>> a multi-tenant cartridge if tenant partitions are defined.
>>>>>
>>>>> *Example:*
>>>>> Cartridge A (Multi-Tenant)
>>>>> Tenant Partitions: 1-100,101-200,201-*
>>>>> Clusters: Cluster-1 (Tenant-Range: 1-100), Cluster-2 (Tenant-Range:
>>>>> 101-200), Cluster-3 (Tenant-Range: 201-*)
>>>>> All three clusters; Cluster-1, Cluster-2 & Cluster-3 will have the
>>>>> same host name.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Wed, Jan 7, 2015 at 7:38 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi Devs,
>>>>>>
>>>>>> Please find the latest status of the tasks we need to complete for
>>>>>> 4.1.0-Alpha release below:
>>>>>>
>>>>>> 1. Finalize Kubernetes Workflow (DONE)
>>>>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>>>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>>>>> *4. Implement Load Balancer Configuration for Service Grouping
>>>>>> (IN-PROGRESS)*
>>>>>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>>>>>> 6. Implement ADC logic for Service Grouping (DONE)
>>>>>> 7. Implement Multi-Tenant support for Applications (DONE)
>>>>>> *8. Verify Domain Mappings Functionality*
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Wed, Jan 7, 2015 at 1:50 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Great work Sajith! Now we have verified both OpenStack and EC2 on
>>>>>>> the latest codebase.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Wed, Jan 7, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I tested the basic flow in Openstack, and it worked fine. I used a
>>>>>>>> single cartridge (tomcat) and got the member activated event. Were able to
>>>>>>>> access tomcat home page.
>>>>>>>> Now I'm in the process of testing more complex scenarios
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Sajith
>>>>>>>>
>>>>>>>> On Tue, Jan 6, 2015 at 1:21 PM, Sajith Kariyawasam <sajith@wso2.com
>>>>>>>> > wrote:
>>>>>>>>
>>>>>>>>> I fixed this now. Verified with a tomcat cartridge in Openstack
>>>>>>>>>
>>>>>>>>> On Tue, Jan 6, 2015 at 11:55 AM, Manula Chathurika Thantriwatte <
>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> DEPLOYMENT payload parameter set in two places in
>>>>>>>>>> BasicPayloadData and ApplicationUtils. Can we set this in one place ?
>>>>>>>>>>
>>>>>>>>>> Thanks !
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <
>>>>>>>>>> sajith@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Found an issue while testing in Openstack, DEPLOYMENT payload
>>>>>>>>>>> parameter is set twice, as follows..
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
>>>>>>>>>>> tomcat.tomcat.apache.org
>>>>>>>>>>> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
>>>>>>>>>>> *DEPLOYMENT*
>>>>>>>>>>> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
>>>>>>>>>>> *DEPLOYMENT*=default,
>>>>>>>>>>>
>>>>>>>>>>> This causes wrong hostname in the cartridge instance, hence
>>>>>>>>>>> puppet master doesn't recognize the service type of the node.
>>>>>>>>>>>
>>>>>>>>>>> I'm looking into this
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <
>>>>>>>>>>> mariangela@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I will work with Manula on this task!
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Mariangela
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *--*
>>>>>>>>>>>> Mariangela Hills
>>>>>>>>>>>> Senior Technical Writer
>>>>>>>>>>>>
>>>>>>>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>>>>>>> m: +94 773 500185
>>>>>>>>>>>> w: http://wso2.com
>>>>>>>>>>>> <http://wso2.com/events/>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte
>>>>>>>>>>>> <ma...@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'll work with Mari and update the documentation.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Great work Manula! Really nice to hear that it worked on EC2
>>>>>>>>>>>>>> without any problems.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I think we need to update the documentation with the relevant
>>>>>>>>>>>>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>>>>>>>>>>>>> Appreciate if Mari can assist us on this.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika
>>>>>>>>>>>>>> Thantriwatte <ma...@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Great work Lahiru!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> 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/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>>>>
>>>>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 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/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>>
>>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>
>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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/
>>>>
>>>>
>>>
>>>
>>> --
>>> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Shiro has contributed to clustering implementation in Autoscaler with the
following pull request [1] and it is now merged to master branch.
[1] https://github.com/apache/stratos/pull/165
On Sun, Jan 11, 2015 at 9:47 AM, Imesh Gunaratne <im...@apache.org> wrote:
> We have now completed domain mappings functionality, now the latest task
> status looks as follows:
>
> 1. Finalize Kubernetes Workflow (DONE)
> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
> 4. Implement Load Balancer Configuration for Service Grouping (DONE)
> 5. Implement ADC logic for Service Grouping (DONE)
> 6. Implement Multi-Tenant support for Applications (DONE)
> 7. Verify Domain Mappings Functionality (DONE)
> *8. Verify Tenant Partitioning Functionality for Multi-Tenant Applications*
>
> I'm now working on task 3: verifying clustering functionality. Appreciate
> if someone could contribute to task 8.
>
> Thanks
>
> On Fri, Jan 9, 2015 at 11:54 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Thanks Lakmal, yes we could remove docker image resizing effort from
>> alpha release since we have completed Kubernetes workflow. We have also
>> completed the load balancer configuration task, now the latest task list
>> status would be as follows:
>>
>> 1. Finalize Kubernetes Workflow (DONE)
>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>> 4. Implement Load Balancer Configuration for Service Grouping (DONE)
>> 5. Implement ADC logic for Service Grouping (DONE)
>> 6. Implement Multi-Tenant support for Applications (DONE)
>> *7. Verify Domain Mappings Functionality (IN-PROGRESS)*
>> *8. Verify Tenant Partitioning Functionality for Multi-Tenant
>> Applications*
>>
>> Thanks
>>
>> On Fri, Jan 9, 2015 at 11:45 AM, Lakmal Warusawithana <la...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Jan 9, 2015 at 11:39 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> I'm now working on fixing Domain Mapping functionality. While doing
>>>> this I found another functionality which we need to fix (Task-9):
>>>>
>>>> 1. Finalize Kubernetes Workflow (DONE)
>>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>>> *4. Implement Load Balancer Configuration for Service Grouping
>>>> (IN-PROGRESS)*
>>>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>>>>
>>>
>>> IMO, we can take off #5 from the alpha release.
>>>
>>>
>>>> 6. Implement ADC logic for Service Grouping (DONE)
>>>> 7. Implement Multi-Tenant support for Applications (DONE)
>>>> *8. Verify Domain Mappings Functionality (IN-PROGRESS)*
>>>> *9. Verify Tenant Partitioning Functionality for Multi-Tenant
>>>> Applications*
>>>> As it looks like current cartridge definition does not allow us to
>>>> define tenant partitions. This is needed for creating multiple clusters for
>>>> a multi-tenant cartridge if tenant partitions are defined.
>>>>
>>>> *Example:*
>>>> Cartridge A (Multi-Tenant)
>>>> Tenant Partitions: 1-100,101-200,201-*
>>>> Clusters: Cluster-1 (Tenant-Range: 1-100), Cluster-2 (Tenant-Range:
>>>> 101-200), Cluster-3 (Tenant-Range: 201-*)
>>>> All three clusters; Cluster-1, Cluster-2 & Cluster-3 will have the same
>>>> host name.
>>>>
>>>> Thanks
>>>>
>>>> On Wed, Jan 7, 2015 at 7:38 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> Please find the latest status of the tasks we need to complete for
>>>>> 4.1.0-Alpha release below:
>>>>>
>>>>> 1. Finalize Kubernetes Workflow (DONE)
>>>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>>>> *4. Implement Load Balancer Configuration for Service Grouping
>>>>> (IN-PROGRESS)*
>>>>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>>>>> 6. Implement ADC logic for Service Grouping (DONE)
>>>>> 7. Implement Multi-Tenant support for Applications (DONE)
>>>>> *8. Verify Domain Mappings Functionality*
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Wed, Jan 7, 2015 at 1:50 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Great work Sajith! Now we have verified both OpenStack and EC2 on the
>>>>>> latest codebase.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Wed, Jan 7, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I tested the basic flow in Openstack, and it worked fine. I used a
>>>>>>> single cartridge (tomcat) and got the member activated event. Were able to
>>>>>>> access tomcat home page.
>>>>>>> Now I'm in the process of testing more complex scenarios
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sajith
>>>>>>>
>>>>>>> On Tue, Jan 6, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I fixed this now. Verified with a tomcat cartridge in Openstack
>>>>>>>>
>>>>>>>> On Tue, Jan 6, 2015 at 11:55 AM, Manula Chathurika Thantriwatte <
>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> DEPLOYMENT payload parameter set in two places in BasicPayloadData
>>>>>>>>> and ApplicationUtils. Can we set this in one place ?
>>>>>>>>>
>>>>>>>>> Thanks !
>>>>>>>>>
>>>>>>>>> On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <
>>>>>>>>> sajith@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Found an issue while testing in Openstack, DEPLOYMENT payload
>>>>>>>>>> parameter is set twice, as follows..
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
>>>>>>>>>> tomcat.tomcat.apache.org
>>>>>>>>>> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
>>>>>>>>>> *DEPLOYMENT*
>>>>>>>>>> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
>>>>>>>>>> *DEPLOYMENT*=default,
>>>>>>>>>>
>>>>>>>>>> This causes wrong hostname in the cartridge instance, hence
>>>>>>>>>> puppet master doesn't recognize the service type of the node.
>>>>>>>>>>
>>>>>>>>>> I'm looking into this
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <
>>>>>>>>>> mariangela@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I will work with Manula on this task!
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Mariangela
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *--*
>>>>>>>>>>> Mariangela Hills
>>>>>>>>>>> Senior Technical Writer
>>>>>>>>>>>
>>>>>>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>>>>>> m: +94 773 500185
>>>>>>>>>>> w: http://wso2.com
>>>>>>>>>>> <http://wso2.com/events/>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
>>>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I'll work with Mari and update the documentation.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Great work Manula! Really nice to hear that it worked on EC2
>>>>>>>>>>>>> without any problems.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I think we need to update the documentation with the relevant
>>>>>>>>>>>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>>>>>>>>>>>> Appreciate if Mari can assist us on this.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte
>>>>>>>>>>>>> <ma...@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Great work Lahiru!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> 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/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>>>
>>>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 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/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>
>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Sajith Kariyawasam*
>>>>>>>
>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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/
>>>
>>>
>>
>>
>> --
>> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
We have now completed domain mappings functionality, now the latest task
status looks as follows:
1. Finalize Kubernetes Workflow (DONE)
2. Verify Service Grouping on OpenStack and EC2 (DONE)
*3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
4. Implement Load Balancer Configuration for Service Grouping (DONE)
5. Implement ADC logic for Service Grouping (DONE)
6. Implement Multi-Tenant support for Applications (DONE)
7. Verify Domain Mappings Functionality (DONE)
*8. Verify Tenant Partitioning Functionality for Multi-Tenant Applications*
I'm now working on task 3: verifying clustering functionality. Appreciate
if someone could contribute to task 8.
Thanks
On Fri, Jan 9, 2015 at 11:54 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Thanks Lakmal, yes we could remove docker image resizing effort from alpha
> release since we have completed Kubernetes workflow. We have also completed
> the load balancer configuration task, now the latest task list status would
> be as follows:
>
> 1. Finalize Kubernetes Workflow (DONE)
> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
> 4. Implement Load Balancer Configuration for Service Grouping (DONE)
> 5. Implement ADC logic for Service Grouping (DONE)
> 6. Implement Multi-Tenant support for Applications (DONE)
> *7. Verify Domain Mappings Functionality (IN-PROGRESS)*
> *8. Verify Tenant Partitioning Functionality for Multi-Tenant Applications*
>
> Thanks
>
> On Fri, Jan 9, 2015 at 11:45 AM, Lakmal Warusawithana <la...@wso2.com>
> wrote:
>
>>
>>
>> On Fri, Jan 9, 2015 at 11:39 AM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> I'm now working on fixing Domain Mapping functionality. While doing this
>>> I found another functionality which we need to fix (Task-9):
>>>
>>> 1. Finalize Kubernetes Workflow (DONE)
>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>> *4. Implement Load Balancer Configuration for Service Grouping
>>> (IN-PROGRESS)*
>>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>>>
>>
>> IMO, we can take off #5 from the alpha release.
>>
>>
>>> 6. Implement ADC logic for Service Grouping (DONE)
>>> 7. Implement Multi-Tenant support for Applications (DONE)
>>> *8. Verify Domain Mappings Functionality (IN-PROGRESS)*
>>> *9. Verify Tenant Partitioning Functionality for Multi-Tenant
>>> Applications*
>>> As it looks like current cartridge definition does not allow us to
>>> define tenant partitions. This is needed for creating multiple clusters for
>>> a multi-tenant cartridge if tenant partitions are defined.
>>>
>>> *Example:*
>>> Cartridge A (Multi-Tenant)
>>> Tenant Partitions: 1-100,101-200,201-*
>>> Clusters: Cluster-1 (Tenant-Range: 1-100), Cluster-2 (Tenant-Range:
>>> 101-200), Cluster-3 (Tenant-Range: 201-*)
>>> All three clusters; Cluster-1, Cluster-2 & Cluster-3 will have the same
>>> host name.
>>>
>>> Thanks
>>>
>>> On Wed, Jan 7, 2015 at 7:38 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> Please find the latest status of the tasks we need to complete for
>>>> 4.1.0-Alpha release below:
>>>>
>>>> 1. Finalize Kubernetes Workflow (DONE)
>>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>>> *4. Implement Load Balancer Configuration for Service Grouping
>>>> (IN-PROGRESS)*
>>>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>>>> 6. Implement ADC logic for Service Grouping (DONE)
>>>> 7. Implement Multi-Tenant support for Applications (DONE)
>>>> *8. Verify Domain Mappings Functionality*
>>>>
>>>> Thanks
>>>>
>>>> On Wed, Jan 7, 2015 at 1:50 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Great work Sajith! Now we have verified both OpenStack and EC2 on the
>>>>> latest codebase.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Wed, Jan 7, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> I tested the basic flow in Openstack, and it worked fine. I used a
>>>>>> single cartridge (tomcat) and got the member activated event. Were able to
>>>>>> access tomcat home page.
>>>>>> Now I'm in the process of testing more complex scenarios
>>>>>>
>>>>>> Thanks,
>>>>>> Sajith
>>>>>>
>>>>>> On Tue, Jan 6, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I fixed this now. Verified with a tomcat cartridge in Openstack
>>>>>>>
>>>>>>> On Tue, Jan 6, 2015 at 11:55 AM, Manula Chathurika Thantriwatte <
>>>>>>> manulac@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> DEPLOYMENT payload parameter set in two places in BasicPayloadData
>>>>>>>> and ApplicationUtils. Can we set this in one place ?
>>>>>>>>
>>>>>>>> Thanks !
>>>>>>>>
>>>>>>>> On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <
>>>>>>>> sajith@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Found an issue while testing in Openstack, DEPLOYMENT payload
>>>>>>>>> parameter is set twice, as follows..
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
>>>>>>>>> tomcat.tomcat.apache.org
>>>>>>>>> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
>>>>>>>>> *DEPLOYMENT*
>>>>>>>>> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
>>>>>>>>> *DEPLOYMENT*=default,
>>>>>>>>>
>>>>>>>>> This causes wrong hostname in the cartridge instance, hence puppet
>>>>>>>>> master doesn't recognize the service type of the node.
>>>>>>>>>
>>>>>>>>> I'm looking into this
>>>>>>>>>
>>>>>>>>> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <
>>>>>>>>> mariangela@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> I will work with Manula on this task!
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Mariangela
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *--*
>>>>>>>>>> Mariangela Hills
>>>>>>>>>> Senior Technical Writer
>>>>>>>>>>
>>>>>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>>>>> m: +94 773 500185
>>>>>>>>>> w: http://wso2.com
>>>>>>>>>> <http://wso2.com/events/>
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
>>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I'll work with Mari and update the documentation.
>>>>>>>>>>>
>>>>>>>>>>> Thanks !
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Great work Manula! Really nice to hear that it worked on EC2
>>>>>>>>>>>> without any problems.
>>>>>>>>>>>>
>>>>>>>>>>>> I think we need to update the documentation with the relevant
>>>>>>>>>>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>>>>>>>>>>> Appreciate if Mari can assist us on this.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte
>>>>>>>>>>>> <ma...@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Great work Lahiru!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> 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/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>>
>>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Sajith Kariyawasam*
>>>>>>>
>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Sajith Kariyawasam*
>>>>>>
>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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/
>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Thanks Lakmal, yes we could remove docker image resizing effort from alpha
release since we have completed Kubernetes workflow. We have also completed
the load balancer configuration task, now the latest task list status would
be as follows:
1. Finalize Kubernetes Workflow (DONE)
2. Verify Service Grouping on OpenStack and EC2 (DONE)
*3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
4. Implement Load Balancer Configuration for Service Grouping (DONE)
5. Implement ADC logic for Service Grouping (DONE)
6. Implement Multi-Tenant support for Applications (DONE)
*7. Verify Domain Mappings Functionality (IN-PROGRESS)*
*8. Verify Tenant Partitioning Functionality for Multi-Tenant Applications*
Thanks
On Fri, Jan 9, 2015 at 11:45 AM, Lakmal Warusawithana <la...@wso2.com>
wrote:
>
>
> On Fri, Jan 9, 2015 at 11:39 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Hi Devs,
>>
>> I'm now working on fixing Domain Mapping functionality. While doing this
>> I found another functionality which we need to fix (Task-9):
>>
>> 1. Finalize Kubernetes Workflow (DONE)
>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>> *4. Implement Load Balancer Configuration for Service Grouping
>> (IN-PROGRESS)*
>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>>
>
> IMO, we can take off #5 from the alpha release.
>
>
>> 6. Implement ADC logic for Service Grouping (DONE)
>> 7. Implement Multi-Tenant support for Applications (DONE)
>> *8. Verify Domain Mappings Functionality (IN-PROGRESS)*
>> *9. Verify Tenant Partitioning Functionality for Multi-Tenant
>> Applications*
>> As it looks like current cartridge definition does not allow us to define
>> tenant partitions. This is needed for creating multiple clusters for a
>> multi-tenant cartridge if tenant partitions are defined.
>>
>> *Example:*
>> Cartridge A (Multi-Tenant)
>> Tenant Partitions: 1-100,101-200,201-*
>> Clusters: Cluster-1 (Tenant-Range: 1-100), Cluster-2 (Tenant-Range:
>> 101-200), Cluster-3 (Tenant-Range: 201-*)
>> All three clusters; Cluster-1, Cluster-2 & Cluster-3 will have the same
>> host name.
>>
>> Thanks
>>
>> On Wed, Jan 7, 2015 at 7:38 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Hi Devs,
>>>
>>> Please find the latest status of the tasks we need to complete for
>>> 4.1.0-Alpha release below:
>>>
>>> 1. Finalize Kubernetes Workflow (DONE)
>>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>>> *4. Implement Load Balancer Configuration for Service Grouping
>>> (IN-PROGRESS)*
>>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>>> 6. Implement ADC logic for Service Grouping (DONE)
>>> 7. Implement Multi-Tenant support for Applications (DONE)
>>> *8. Verify Domain Mappings Functionality*
>>>
>>> Thanks
>>>
>>> On Wed, Jan 7, 2015 at 1:50 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Great work Sajith! Now we have verified both OpenStack and EC2 on the
>>>> latest codebase.
>>>>
>>>> Thanks
>>>>
>>>> On Wed, Jan 7, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>> wrote:
>>>>
>>>>> I tested the basic flow in Openstack, and it worked fine. I used a
>>>>> single cartridge (tomcat) and got the member activated event. Were able to
>>>>> access tomcat home page.
>>>>> Now I'm in the process of testing more complex scenarios
>>>>>
>>>>> Thanks,
>>>>> Sajith
>>>>>
>>>>> On Tue, Jan 6, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> I fixed this now. Verified with a tomcat cartridge in Openstack
>>>>>>
>>>>>> On Tue, Jan 6, 2015 at 11:55 AM, Manula Chathurika Thantriwatte <
>>>>>> manulac@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> DEPLOYMENT payload parameter set in two places in BasicPayloadData
>>>>>>> and ApplicationUtils. Can we set this in one place ?
>>>>>>>
>>>>>>> Thanks !
>>>>>>>
>>>>>>> On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <sajith@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Found an issue while testing in Openstack, DEPLOYMENT payload
>>>>>>>> parameter is set twice, as follows..
>>>>>>>>
>>>>>>>>
>>>>>>>> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
>>>>>>>> tomcat.tomcat.apache.org
>>>>>>>> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
>>>>>>>> *DEPLOYMENT*
>>>>>>>> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
>>>>>>>> *DEPLOYMENT*=default,
>>>>>>>>
>>>>>>>> This causes wrong hostname in the cartridge instance, hence puppet
>>>>>>>> master doesn't recognize the service type of the node.
>>>>>>>>
>>>>>>>> I'm looking into this
>>>>>>>>
>>>>>>>> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <
>>>>>>>> mariangela@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> I will work with Manula on this task!
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Mariangela
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *--*
>>>>>>>>> Mariangela Hills
>>>>>>>>> Senior Technical Writer
>>>>>>>>>
>>>>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>>>> m: +94 773 500185
>>>>>>>>> w: http://wso2.com
>>>>>>>>> <http://wso2.com/events/>
>>>>>>>>>
>>>>>>>>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I'll work with Mari and update the documentation.
>>>>>>>>>>
>>>>>>>>>> Thanks !
>>>>>>>>>>
>>>>>>>>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> Great work Manula! Really nice to hear that it worked on EC2
>>>>>>>>>>> without any problems.
>>>>>>>>>>>
>>>>>>>>>>> I think we need to update the documentation with the relevant
>>>>>>>>>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>>>>>>>>>> Appreciate if Mari can assist us on this.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
>>>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks !
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Great work Lahiru!
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> 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
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 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/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Sajith Kariyawasam*
>>>>>>>>
>>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc.,
>>>>>>>> http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Sajith Kariyawasam*
>>>>>>
>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Sajith Kariyawasam*
>>>>>
>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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/
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Lakmal Warusawithana <la...@wso2.com>.
On Fri, Jan 9, 2015 at 11:39 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Devs,
>
> I'm now working on fixing Domain Mapping functionality. While doing this I
> found another functionality which we need to fix (Task-9):
>
> 1. Finalize Kubernetes Workflow (DONE)
> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
> *4. Implement Load Balancer Configuration for Service Grouping
> (IN-PROGRESS)*
> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>
IMO, we can take off #5 from the alpha release.
> 6. Implement ADC logic for Service Grouping (DONE)
> 7. Implement Multi-Tenant support for Applications (DONE)
> *8. Verify Domain Mappings Functionality (IN-PROGRESS)*
> *9. Verify Tenant Partitioning Functionality for Multi-Tenant Applications*
> As it looks like current cartridge definition does not allow us to define
> tenant partitions. This is needed for creating multiple clusters for a
> multi-tenant cartridge if tenant partitions are defined.
>
> *Example:*
> Cartridge A (Multi-Tenant)
> Tenant Partitions: 1-100,101-200,201-*
> Clusters: Cluster-1 (Tenant-Range: 1-100), Cluster-2 (Tenant-Range:
> 101-200), Cluster-3 (Tenant-Range: 201-*)
> All three clusters; Cluster-1, Cluster-2 & Cluster-3 will have the same
> host name.
>
> Thanks
>
> On Wed, Jan 7, 2015 at 7:38 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Hi Devs,
>>
>> Please find the latest status of the tasks we need to complete for
>> 4.1.0-Alpha release below:
>>
>> 1. Finalize Kubernetes Workflow (DONE)
>> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
>> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
>> *4. Implement Load Balancer Configuration for Service Grouping
>> (IN-PROGRESS)*
>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>> 6. Implement ADC logic for Service Grouping (DONE)
>> 7. Implement Multi-Tenant support for Applications (DONE)
>> *8. Verify Domain Mappings Functionality*
>>
>> Thanks
>>
>> On Wed, Jan 7, 2015 at 1:50 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Great work Sajith! Now we have verified both OpenStack and EC2 on the
>>> latest codebase.
>>>
>>> Thanks
>>>
>>> On Wed, Jan 7, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>>> wrote:
>>>
>>>> I tested the basic flow in Openstack, and it worked fine. I used a
>>>> single cartridge (tomcat) and got the member activated event. Were able to
>>>> access tomcat home page.
>>>> Now I'm in the process of testing more complex scenarios
>>>>
>>>> Thanks,
>>>> Sajith
>>>>
>>>> On Tue, Jan 6, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>>>> wrote:
>>>>
>>>>> I fixed this now. Verified with a tomcat cartridge in Openstack
>>>>>
>>>>> On Tue, Jan 6, 2015 at 11:55 AM, Manula Chathurika Thantriwatte <
>>>>> manulac@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> DEPLOYMENT payload parameter set in two places in BasicPayloadData
>>>>>> and ApplicationUtils. Can we set this in one place ?
>>>>>>
>>>>>> Thanks !
>>>>>>
>>>>>> On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <sa...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Found an issue while testing in Openstack, DEPLOYMENT payload
>>>>>>> parameter is set twice, as follows..
>>>>>>>
>>>>>>>
>>>>>>> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
>>>>>>> tomcat.tomcat.apache.org
>>>>>>> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
>>>>>>> *DEPLOYMENT*
>>>>>>> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
>>>>>>> *DEPLOYMENT*=default,
>>>>>>>
>>>>>>> This causes wrong hostname in the cartridge instance, hence puppet
>>>>>>> master doesn't recognize the service type of the node.
>>>>>>>
>>>>>>> I'm looking into this
>>>>>>>
>>>>>>> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <
>>>>>>> mariangela@wso2.com> wrote:
>>>>>>>
>>>>>>>> I will work with Manula on this task!
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Mariangela
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *--*
>>>>>>>> Mariangela Hills
>>>>>>>> Senior Technical Writer
>>>>>>>>
>>>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>>> m: +94 773 500185
>>>>>>>> w: http://wso2.com
>>>>>>>> <http://wso2.com/events/>
>>>>>>>>
>>>>>>>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I'll work with Mari and update the documentation.
>>>>>>>>>
>>>>>>>>> Thanks !
>>>>>>>>>
>>>>>>>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Great work Manula! Really nice to hear that it worked on EC2
>>>>>>>>>> without any problems.
>>>>>>>>>>
>>>>>>>>>> I think we need to update the documentation with the relevant
>>>>>>>>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>>>>>>>>> Appreciate if Mari can assist us on this.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
>>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>>>>>>>
>>>>>>>>>>> Thanks !
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Great work Lahiru!
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 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/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Sajith Kariyawasam*
>>>>>>>
>>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Sajith Kariyawasam*
>>>>>
>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Sajith Kariyawasam*
>>>>
>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>
>>>
>>>
>>>
>>> --
>>> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Devs,
I'm now working on fixing Domain Mapping functionality. While doing this I
found another functionality which we need to fix (Task-9):
1. Finalize Kubernetes Workflow (DONE)
2. Verify Service Grouping on OpenStack and EC2 (DONE)
*3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
*4. Implement Load Balancer Configuration for Service Grouping
(IN-PROGRESS)*
*5. Reduce the Docker Image Size (IN-PROGRESS) *
6. Implement ADC logic for Service Grouping (DONE)
7. Implement Multi-Tenant support for Applications (DONE)
*8. Verify Domain Mappings Functionality (IN-PROGRESS)*
*9. Verify Tenant Partitioning Functionality for Multi-Tenant Applications*
As it looks like current cartridge definition does not allow us to define
tenant partitions. This is needed for creating multiple clusters for a
multi-tenant cartridge if tenant partitions are defined.
*Example:*
Cartridge A (Multi-Tenant)
Tenant Partitions: 1-100,101-200,201-*
Clusters: Cluster-1 (Tenant-Range: 1-100), Cluster-2 (Tenant-Range:
101-200), Cluster-3 (Tenant-Range: 201-*)
All three clusters; Cluster-1, Cluster-2 & Cluster-3 will have the same
host name.
Thanks
On Wed, Jan 7, 2015 at 7:38 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Devs,
>
> Please find the latest status of the tasks we need to complete for
> 4.1.0-Alpha release below:
>
> 1. Finalize Kubernetes Workflow (DONE)
> 2. Verify Service Grouping on OpenStack and EC2 (DONE)
> *3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
> *4. Implement Load Balancer Configuration for Service Grouping
> (IN-PROGRESS)*
> *5. Reduce the Docker Image Size (IN-PROGRESS) *
> 6. Implement ADC logic for Service Grouping (DONE)
> 7. Implement Multi-Tenant support for Applications (DONE)
> *8. Verify Domain Mappings Functionality*
>
> Thanks
>
> On Wed, Jan 7, 2015 at 1:50 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Great work Sajith! Now we have verified both OpenStack and EC2 on the
>> latest codebase.
>>
>> Thanks
>>
>> On Wed, Jan 7, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>> wrote:
>>
>>> I tested the basic flow in Openstack, and it worked fine. I used a
>>> single cartridge (tomcat) and got the member activated event. Were able to
>>> access tomcat home page.
>>> Now I'm in the process of testing more complex scenarios
>>>
>>> Thanks,
>>> Sajith
>>>
>>> On Tue, Jan 6, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>>> wrote:
>>>
>>>> I fixed this now. Verified with a tomcat cartridge in Openstack
>>>>
>>>> On Tue, Jan 6, 2015 at 11:55 AM, Manula Chathurika Thantriwatte <
>>>> manulac@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> DEPLOYMENT payload parameter set in two places in BasicPayloadData and
>>>>> ApplicationUtils. Can we set this in one place ?
>>>>>
>>>>> Thanks !
>>>>>
>>>>> On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <sa...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Found an issue while testing in Openstack, DEPLOYMENT payload
>>>>>> parameter is set twice, as follows..
>>>>>>
>>>>>>
>>>>>> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
>>>>>> tomcat.tomcat.apache.org
>>>>>> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
>>>>>> *DEPLOYMENT*
>>>>>> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
>>>>>> *DEPLOYMENT*=default,
>>>>>>
>>>>>> This causes wrong hostname in the cartridge instance, hence puppet
>>>>>> master doesn't recognize the service type of the node.
>>>>>>
>>>>>> I'm looking into this
>>>>>>
>>>>>> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <mariangela@wso2.com
>>>>>> > wrote:
>>>>>>
>>>>>>> I will work with Manula on this task!
>>>>>>>
>>>>>>> Regards,
>>>>>>> Mariangela
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *--*
>>>>>>> Mariangela Hills
>>>>>>> Senior Technical Writer
>>>>>>>
>>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>> m: +94 773 500185
>>>>>>> w: http://wso2.com
>>>>>>> <http://wso2.com/events/>
>>>>>>>
>>>>>>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
>>>>>>> manulac@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I'll work with Mari and update the documentation.
>>>>>>>>
>>>>>>>> Thanks !
>>>>>>>>
>>>>>>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Great work Manula! Really nice to hear that it worked on EC2
>>>>>>>>> without any problems.
>>>>>>>>>
>>>>>>>>> I think we need to update the documentation with the relevant
>>>>>>>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>>>>>>>> Appreciate if Mari can assist us on this.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
>>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>>>>>>
>>>>>>>>>> Thanks !
>>>>>>>>>>
>>>>>>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <
>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>> Great work Lahiru!
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Sajith Kariyawasam*
>>>>>>
>>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Sajith Kariyawasam*
>>>>
>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>
>>>
>>>
>>>
>>> --
>>> *Sajith Kariyawasam*
>>>
>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>
>>
>>
>>
>> --
>> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Devs,
Please find the latest status of the tasks we need to complete for
4.1.0-Alpha release below:
1. Finalize Kubernetes Workflow (DONE)
2. Verify Service Grouping on OpenStack and EC2 (DONE)
*3. Verify Clustering Support for Stratos Components (IN-PROGRESS)*
*4. Implement Load Balancer Configuration for Service Grouping
(IN-PROGRESS)*
*5. Reduce the Docker Image Size (IN-PROGRESS) *
6. Implement ADC logic for Service Grouping (DONE)
7. Implement Multi-Tenant support for Applications (DONE)
*8. Verify Domain Mappings Functionality*
Thanks
On Wed, Jan 7, 2015 at 1:50 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Great work Sajith! Now we have verified both OpenStack and EC2 on the
> latest codebase.
>
> Thanks
>
> On Wed, Jan 7, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
> wrote:
>
>> I tested the basic flow in Openstack, and it worked fine. I used a single
>> cartridge (tomcat) and got the member activated event. Were able to access
>> tomcat home page.
>> Now I'm in the process of testing more complex scenarios
>>
>> Thanks,
>> Sajith
>>
>> On Tue, Jan 6, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
>> wrote:
>>
>>> I fixed this now. Verified with a tomcat cartridge in Openstack
>>>
>>> On Tue, Jan 6, 2015 at 11:55 AM, Manula Chathurika Thantriwatte <
>>> manulac@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> DEPLOYMENT payload parameter set in two places in BasicPayloadData and
>>>> ApplicationUtils. Can we set this in one place ?
>>>>
>>>> Thanks !
>>>>
>>>> On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <sa...@wso2.com>
>>>> wrote:
>>>>
>>>>> Found an issue while testing in Openstack, DEPLOYMENT payload
>>>>> parameter is set twice, as follows..
>>>>>
>>>>>
>>>>> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
>>>>> tomcat.tomcat.apache.org
>>>>> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
>>>>> *DEPLOYMENT*
>>>>> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
>>>>> *DEPLOYMENT*=default,
>>>>>
>>>>> This causes wrong hostname in the cartridge instance, hence puppet
>>>>> master doesn't recognize the service type of the node.
>>>>>
>>>>> I'm looking into this
>>>>>
>>>>> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <ma...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> I will work with Manula on this task!
>>>>>>
>>>>>> Regards,
>>>>>> Mariangela
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *--*
>>>>>> Mariangela Hills
>>>>>> Senior Technical Writer
>>>>>>
>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>> m: +94 773 500185
>>>>>> w: http://wso2.com
>>>>>> <http://wso2.com/events/>
>>>>>>
>>>>>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
>>>>>> manulac@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I'll work with Mari and update the documentation.
>>>>>>>
>>>>>>> Thanks !
>>>>>>>
>>>>>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Great work Manula! Really nice to hear that it worked on EC2
>>>>>>>> without any problems.
>>>>>>>>
>>>>>>>> I think we need to update the documentation with the relevant
>>>>>>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>>>>>>> Appreciate if Mari can assist us on this.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
>>>>>>>> manulac@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>>>>>
>>>>>>>>> Thanks !
>>>>>>>>>
>>>>>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> Great work Lahiru!
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 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
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Sajith Kariyawasam*
>>>>>
>>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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/
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Sajith Kariyawasam*
>>>
>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>
>>
>>
>>
>> --
>> *Sajith Kariyawasam*
>>
>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Great work Sajith! Now we have verified both OpenStack and EC2 on the
latest codebase.
Thanks
On Wed, Jan 7, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com> wrote:
> I tested the basic flow in Openstack, and it worked fine. I used a single
> cartridge (tomcat) and got the member activated event. Were able to access
> tomcat home page.
> Now I'm in the process of testing more complex scenarios
>
> Thanks,
> Sajith
>
> On Tue, Jan 6, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com>
> wrote:
>
>> I fixed this now. Verified with a tomcat cartridge in Openstack
>>
>> On Tue, Jan 6, 2015 at 11:55 AM, Manula Chathurika Thantriwatte <
>> manulac@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> DEPLOYMENT payload parameter set in two places in BasicPayloadData and
>>> ApplicationUtils. Can we set this in one place ?
>>>
>>> Thanks !
>>>
>>> On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <sa...@wso2.com>
>>> wrote:
>>>
>>>> Found an issue while testing in Openstack, DEPLOYMENT payload parameter
>>>> is set twice, as follows..
>>>>
>>>>
>>>> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
>>>> tomcat.tomcat.apache.org
>>>> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
>>>> *DEPLOYMENT*
>>>> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
>>>> *DEPLOYMENT*=default,
>>>>
>>>> This causes wrong hostname in the cartridge instance, hence puppet
>>>> master doesn't recognize the service type of the node.
>>>>
>>>> I'm looking into this
>>>>
>>>> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <ma...@wso2.com>
>>>> wrote:
>>>>
>>>>> I will work with Manula on this task!
>>>>>
>>>>> Regards,
>>>>> Mariangela
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *--*
>>>>> Mariangela Hills
>>>>> Senior Technical Writer
>>>>>
>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>> m: +94 773 500185
>>>>> w: http://wso2.com
>>>>> <http://wso2.com/events/>
>>>>>
>>>>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
>>>>> manulac@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I'll work with Mari and update the documentation.
>>>>>>
>>>>>> Thanks !
>>>>>>
>>>>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Great work Manula! Really nice to hear that it worked on EC2 without
>>>>>>> any problems.
>>>>>>>
>>>>>>> I think we need to update the documentation with the relevant
>>>>>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>>>>>> Appreciate if Mari can assist us on this.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
>>>>>>> manulac@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>>>>
>>>>>>>> Thanks !
>>>>>>>>
>>>>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Great work Lahiru!
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Sajith Kariyawasam*
>>>>
>>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>>
>>>
>>>
>>>
>>> --
>>> 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/
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Sajith Kariyawasam*
>>
>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>
>
>
>
> --
> *Sajith Kariyawasam*
>
> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Sajith Kariyawasam <sa...@wso2.com>.
I tested the basic flow in Openstack, and it worked fine. I used a single
cartridge (tomcat) and got the member activated event. Were able to access
tomcat home page.
Now I'm in the process of testing more complex scenarios
Thanks,
Sajith
On Tue, Jan 6, 2015 at 1:21 PM, Sajith Kariyawasam <sa...@wso2.com> wrote:
> I fixed this now. Verified with a tomcat cartridge in Openstack
>
> On Tue, Jan 6, 2015 at 11:55 AM, Manula Chathurika Thantriwatte <
> manulac@wso2.com> wrote:
>
>> Hi,
>>
>> DEPLOYMENT payload parameter set in two places in BasicPayloadData and
>> ApplicationUtils. Can we set this in one place ?
>>
>> Thanks !
>>
>> On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <sa...@wso2.com>
>> wrote:
>>
>>> Found an issue while testing in Openstack, DEPLOYMENT payload parameter
>>> is set twice, as follows..
>>>
>>>
>>> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
>>> tomcat.tomcat.apache.org
>>> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
>>> *DEPLOYMENT*
>>> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
>>> *DEPLOYMENT*=default,
>>>
>>> This causes wrong hostname in the cartridge instance, hence puppet
>>> master doesn't recognize the service type of the node.
>>>
>>> I'm looking into this
>>>
>>> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <ma...@wso2.com>
>>> wrote:
>>>
>>>> I will work with Manula on this task!
>>>>
>>>> Regards,
>>>> Mariangela
>>>>
>>>>
>>>>
>>>>
>>>> *--*
>>>> Mariangela Hills
>>>> Senior Technical Writer
>>>>
>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>> m: +94 773 500185
>>>> w: http://wso2.com
>>>> <http://wso2.com/events/>
>>>>
>>>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
>>>> manulac@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I'll work with Mari and update the documentation.
>>>>>
>>>>> Thanks !
>>>>>
>>>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Great work Manula! Really nice to hear that it worked on EC2 without
>>>>>> any problems.
>>>>>>
>>>>>> I think we need to update the documentation with the relevant
>>>>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>>>>> Appreciate if Mari can assist us on this.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
>>>>>> manulac@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>>>
>>>>>>> Thanks !
>>>>>>>
>>>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Great work Lahiru!
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> *Sajith Kariyawasam*
>>>
>>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>>
>>
>>
>>
>> --
>> 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/
>>
>>
>>
>>
>
>
> --
> *Sajith Kariyawasam*
>
> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>
--
*Sajith Kariyawasam*
*Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
<http://wso2.com>AMIE (SL)Mobile: +94772269575*
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Sajith Kariyawasam <sa...@wso2.com>.
I fixed this now. Verified with a tomcat cartridge in Openstack
On Tue, Jan 6, 2015 at 11:55 AM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi,
>
> DEPLOYMENT payload parameter set in two places in BasicPayloadData and
> ApplicationUtils. Can we set this in one place ?
>
> Thanks !
>
> On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <sa...@wso2.com>
> wrote:
>
>> Found an issue while testing in Openstack, DEPLOYMENT payload parameter
>> is set twice, as follows..
>>
>>
>> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
>> tomcat.tomcat.apache.org
>> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
>> *DEPLOYMENT*
>> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
>> *DEPLOYMENT*=default,
>>
>> This causes wrong hostname in the cartridge instance, hence puppet master
>> doesn't recognize the service type of the node.
>>
>> I'm looking into this
>>
>> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <ma...@wso2.com>
>> wrote:
>>
>>> I will work with Manula on this task!
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>>
>>>
>>> *--*
>>> Mariangela Hills
>>> Senior Technical Writer
>>>
>>> *WSO2, Inc.*lean.enterprise.middleware.
>>> m: +94 773 500185
>>> w: http://wso2.com
>>> <http://wso2.com/events/>
>>>
>>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
>>> manulac@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'll work with Mari and update the documentation.
>>>>
>>>> Thanks !
>>>>
>>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Great work Manula! Really nice to hear that it worked on EC2 without
>>>>> any problems.
>>>>>
>>>>> I think we need to update the documentation with the relevant
>>>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>>>> Appreciate if Mari can assist us on this.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
>>>>> manulac@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>>
>>>>>> Thanks !
>>>>>>
>>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Great work Lahiru!
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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/
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>> --
>> *Sajith Kariyawasam*
>>
>> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
>> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>>
>
>
>
> --
> 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/
>
>
>
>
--
*Sajith Kariyawasam*
*Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
<http://wso2.com>AMIE (SL)Mobile: +94772269575*
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi,
DEPLOYMENT payload parameter set in two places in BasicPayloadData and
ApplicationUtils. Can we set this in one place ?
Thanks !
On Tue, Jan 6, 2015 at 11:40 AM, Sajith Kariyawasam <sa...@wso2.com> wrote:
> Found an issue while testing in Openstack, DEPLOYMENT payload parameter is
> set twice, as follows..
>
>
> APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
> tomcat.tomcat.apache.org
> ,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
> *DEPLOYMENT*
> =null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
> *DEPLOYMENT*=default,
>
> This causes wrong hostname in the cartridge instance, hence puppet master
> doesn't recognize the service type of the node.
>
> I'm looking into this
>
> On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <ma...@wso2.com>
> wrote:
>
>> I will work with Manula on this task!
>>
>> Regards,
>> Mariangela
>>
>>
>>
>>
>> *--*
>> Mariangela Hills
>> Senior Technical Writer
>>
>> *WSO2, Inc.*lean.enterprise.middleware.
>> m: +94 773 500185
>> w: http://wso2.com
>> <http://wso2.com/events/>
>>
>> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
>> manulac@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I'll work with Mari and update the documentation.
>>>
>>> Thanks !
>>>
>>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Great work Manula! Really nice to hear that it worked on EC2 without
>>>> any problems.
>>>>
>>>> I think we need to update the documentation with the relevant
>>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>>> Appreciate if Mari can assist us on this.
>>>>
>>>> Thanks
>>>>
>>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
>>>> manulac@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>>
>>>>> Thanks !
>>>>>
>>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Great work Lahiru!
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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
>>>>
>>>
>>>
>>>
>>> --
>>> 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/
>>>
>>>
>>>
>>>
>>
>
>
> --
> *Sajith Kariyawasam*
>
> *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
> <http://wso2.com>AMIE (SL)Mobile: +94772269575*
>
--
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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Sajith Kariyawasam <sa...@wso2.com>.
Found an issue while testing in Openstack, DEPLOYMENT payload parameter is
set twice, as follows..
APPLICATION_ID=single-cartridge-app,GROUP_NAME=null,SERVICE_NAME=tomcat,HOST_NAME=
tomcat.tomcat.apache.org
,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=*,CARTRIDGE_ALIAS=tomcat,CLUSTER_ID=tomcat.tomcat.domain,CARTRIDGE_KEY=6AvzpTM6e8XFQ522,
*DEPLOYMENT*
=null,APPLICATION_PATH=null,REPO_URL=null,PORTS=22,PROVIDER=apache,PUPPET_IP=192.168.30.90,PUPPET_HOSTNAME=puppet,PUPPET_DNS_AVAILABLE=null,PUPPET_ENV=false,,,
*DEPLOYMENT*=default,
This causes wrong hostname in the cartridge instance, hence puppet master
doesn't recognize the service type of the node.
I'm looking into this
On Tue, Jan 6, 2015 at 9:58 AM, Mariangela Hills <ma...@wso2.com>
wrote:
> I will work with Manula on this task!
>
> Regards,
> Mariangela
>
>
>
>
> *--*
> Mariangela Hills
> Senior Technical Writer
>
> *WSO2, Inc.*lean.enterprise.middleware.
> m: +94 773 500185
> w: http://wso2.com
> <http://wso2.com/events/>
>
> On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
> manulac@wso2.com> wrote:
>
>> Hi,
>>
>> I'll work with Mari and update the documentation.
>>
>> Thanks !
>>
>> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Great work Manula! Really nice to hear that it worked on EC2 without any
>>> problems.
>>>
>>> I think we need to update the documentation with the relevant
>>> information including how to setup Stratos 4.1.0 on EC2 from scratch.
>>> Appreciate if Mari can assist us on this.
>>>
>>> Thanks
>>>
>>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
>>> manulac@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have done the test in EC2 IaaS and it works successfully.
>>>>
>>>> Thanks !
>>>>
>>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Great work Lahiru!
>>>>>
>>>>> Thanks
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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
>>>
>>
>>
>>
>> --
>> 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/
>>
>>
>>
>>
>
--
*Sajith Kariyawasam*
*Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com
<http://wso2.com>AMIE (SL)Mobile: +94772269575*
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Mariangela Hills <ma...@wso2.com>.
I will work with Manula on this task!
Regards,
Mariangela
*--*
Mariangela Hills
Senior Technical Writer
*WSO2, Inc.*lean.enterprise.middleware.
m: +94 773 500185
w: http://wso2.com
<http://wso2.com/events/>
On Tue, Jan 6, 2015 at 9:34 AM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi,
>
> I'll work with Mari and update the documentation.
>
> Thanks !
>
> On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Great work Manula! Really nice to hear that it worked on EC2 without any
>> problems.
>>
>> I think we need to update the documentation with the relevant information
>> including how to setup Stratos 4.1.0 on EC2 from scratch. Appreciate if
>> Mari can assist us on this.
>>
>> Thanks
>>
>> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
>> manulac@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I have done the test in EC2 IaaS and it works successfully.
>>>
>>> Thanks !
>>>
>>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Great work Lahiru!
>>>>
>>>> Thanks
>>>>
>>>
>>>
>>>
>>> --
>>> 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
>>
>
>
>
> --
> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi,
I'll work with Mari and update the documentation.
Thanks !
On Mon, Jan 5, 2015 at 6:22 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Great work Manula! Really nice to hear that it worked on EC2 without any
> problems.
>
> I think we need to update the documentation with the relevant information
> including how to setup Stratos 4.1.0 on EC2 from scratch. Appreciate if
> Mari can assist us on this.
>
> Thanks
>
> On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
> manulac@wso2.com> wrote:
>
>> Hi,
>>
>> I have done the test in EC2 IaaS and it works successfully.
>>
>> Thanks !
>>
>> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Great work Lahiru!
>>>
>>> Thanks
>>>
>>
>>
>>
>> --
>> 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
>
--
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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Great work Manula! Really nice to hear that it worked on EC2 without any
problems.
I think we need to update the documentation with the relevant information
including how to setup Stratos 4.1.0 on EC2 from scratch. Appreciate if
Mari can assist us on this.
Thanks
On Mon, Jan 5, 2015 at 5:12 PM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi,
>
> I have done the test in EC2 IaaS and it works successfully.
>
> Thanks !
>
> On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Great work Lahiru!
>>
>> Thanks
>>
>
>
>
> --
> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi,
I have done the test in EC2 IaaS and it works successfully.
Thanks !
On Sun, Jan 4, 2015 at 10:42 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Great work Lahiru!
>
> Thanks
>
--
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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Great work Lahiru!
Thanks
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Lahiru Sandaruwan <la...@wso2.com>.
I have fixed following,
Not adhering to max when scaling up with dependency scaling
Scaling down logic issues in dependency scaling
Thanks.
On Sat, Jan 3, 2015 at 10:08 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Great! Thanks Akila! Please focus on implementing clustering for
> Autoscaler.
>
> Everyone, will try our best to complete everything in next couple of days
> and release 4.1.0 Alpha ASAP. Please update as you progress.
>
> Thanks
> On Jan 3, 2015 9:05 PM, "Akila Ravihansa Perera" <ra...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I'll work on the Verify Clustering Support for Stratos Components task.
>> I'm planning to use a Vagrant setup with Puppet for configuration
>> management. Hope this will be helpful for our testing framework in the
>> future.
>>
>> Thanks.
>>
>>
>>
>> On Sat, Jan 3, 2015 at 8:42 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> I have now completed the ADC feature for service grouping functionality
>>> and following is the current status of the tasks:
>>>
>>> *1. Finalize Kubernetes Workflow (DONE)*
>>> 2. Verify Service Grouping on OpenStack and EC2
>>> 3. Verify Clustering Support for Stratos Components
>>> 4. Implement Load Balancer Configuration for Service Grouping
>>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>>> *6. Implement ADC logic for Service Grouping (DONE)*
>>> *7. Implement Multi-Tenant support for Applications (IN-PROGRESS)*
>>>
>>> I verified an end to end workflow with Kubernetes and the entire flow
>>> seems to be working fine:
>>> https://gist.github.com/imesh/b8f81fac8de39183a504
>>>
>>> Thanks
>>>
>>> On Sat, Jan 3, 2015 at 8:16 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Great! Thanks Gayan, please propose a design for it.
>>>>
>>>> On Sat, Jan 3, 2015 at 8:03 PM, Gayan Gunarathne <ga...@wso2.com>
>>>> wrote:
>>>>
>>>>> I can look into configuration of load Balances for service grouping.I
>>>>> will start the new email thread for discuss the changes we need for this.
>>>>>
>>>>> Thanks,
>>>>> Gayan
>>>>>
>>>>> On Sat, Jan 3, 2015 at 9:46 AM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi Devs,
>>>>>>
>>>>>> It looks like we have more tasks to complete:
>>>>>>
>>>>>> 1. Finalize Kubernetes Workflow *(DONE)*
>>>>>> 2. Verify Service Grouping on OpenStack and EC2
>>>>>> 3. Verify Clustering Support for Stratos Components
>>>>>> 4. Implement Load Balancer Configuration for Service Grouping
>>>>>> 5. Reduce the Docker Image Size
>>>>>>
>>>>>> *6. Implement ADC logic for Service Grouping (IN-PROGRESS)*
>>>>>> At the moment artifact distribution logic does not work for service
>>>>>> grouping. As a result artifacts are not checked out in instances. I'm
>>>>>> currently implementing this logic.
>>>>>>
>>>>>> *7. Implement Multi-Tenant support for Applications*
>>>>>> Currently we do not have support for tenants to sign up for
>>>>>> Multi-Tenant applications, for each application deployment there is only
>>>>>> one subscription.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Sat, Jan 3, 2015 at 7:10 AM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Great! Thanks Manula! Please update this thread as you go on.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 10:18 PM, Manula Chathurika Thantriwatte <
>>>>>>> manulac@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I'll work on verifying service group on EC2.
>>>>>>>>
>>>>>>>> Thanks !
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 10:12 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Kubernetes workflow is now complete, I'm now working on fixing the
>>>>>>>>> git clone issue in agent.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 9:42 PM, Rajkumar Rajaratnam <
>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Sorry. Lets use the other thread for testing update.
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 9:41 PM, Rajkumar Rajaratnam <
>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Getting an exception while deploying the application.
>>>>>>>>>>>
>>>>>>>>>>> [2015-01-02 21:31:12,401] INFO
>>>>>>>>>>> {org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
>>>>>>>>>>> replication controller: [replication-controller-id]
>>>>>>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
>>>>>>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
>>>>>>>>>>> stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
>>>>>>>>>>> [2015-01-02 21:31:12,402] ERROR
>>>>>>>>>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>>>>>>>>>>> org.apache.axis2.AxisFault: Mapping qname not fond for the package:
>>>>>>>>>>> org.apache.stratos.common.beans
>>>>>>>>>>> java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping
>>>>>>>>>>> qname not fond for the package: org.apache.stratos.common.beans
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>>>>>>>>>>> at
>>>>>>>>>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>>>>>>>>>>> at
>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>>> at
>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>>>>>>> at
>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>>>>>>>>>> at
>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>>>>>>>>>> at
>>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>>>>>>>>>> at
>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>>>>>>> at
>>>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>>>>>>> at
>>>>>>>>>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>>>>>>>>>>> at
>>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>>>>>>>>>>> at
>>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>>>>>>>>>> at
>>>>>>>>>>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>>>>>>>>>>> at
>>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>>>>>>>>>>> at
>>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>>>>>>>>>>> at
>>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>>>>>>>>>>> at
>>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>>>>>>>>>>> at
>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>>>>>>>>>> at
>>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>>>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>>> Caused by: org.apache.axis2.AxisFault: Mapping qname not fond
>>>>>>>>>>> for the package: org.apache.stratos.common.beans
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
>>>>>>>>>>> ... 54 more
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Yes Raj, the modules include the logic and they being invoked
>>>>>>>>>>>> from the callers.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> agent.py does not have any artifact management logic. It is
>>>>>>>>>>>>> there in artifact management module.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Yes I can remember that it was working in previous
>>>>>>>>>>>>>> milestones, however according to the current logic in agent.py, if a git
>>>>>>>>>>>>>> repo url is specified it does nothing:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ..
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> At the end agent just wait in a while loop until terminated.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I can see that agent is listening to Artifact Updated event,
>>>>>>>>>>>>>> did we send this event forcefully to make this work?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> It is already implemented and was working fine.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <
>>>>>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> What do you mean?? Its there since M3
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Seems like we have not written logic in agent to checkout
>>>>>>>>>>>>>>>>> artifacts from GIT repository.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I have now fixed the issue of accessing the service via
>>>>>>>>>>>>>>>>>> the host machine (http://kubernetes-master-ip:port/) and
>>>>>>>>>>>>>>>>>> pushed changes to master branch.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Now I see a problem when a public GIT repo url is given
>>>>>>>>>>>>>>>>>> without specifying credentials. I'm currently looking into this.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I have now resolved the health statistics publishing
>>>>>>>>>>>>>>>>>>> issue in agent:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> - There were several topology event parsers which were
>>>>>>>>>>>>>>>>>>> not properly updated with the latest changes. As a result those were
>>>>>>>>>>>>>>>>>>> raising errors. I have now fixed them.
>>>>>>>>>>>>>>>>>>> - Agent's logic which waits until CEP port is active was
>>>>>>>>>>>>>>>>>>> not visible in the logs. As a result it was not possible to see why agent
>>>>>>>>>>>>>>>>>>> is not publishing health statistics. I have now enabled logs to show this
>>>>>>>>>>>>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>>>>>>>>>>>>> - Docker images in docker hub are updated with the
>>>>>>>>>>>>>>>>>>> latest changes.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Now I see a problem where the PHP service is not
>>>>>>>>>>>>>>>>>>> accessible from the host machine, however it is accessible within the
>>>>>>>>>>>>>>>>>>> Kubernetes master. The removal of host port from the container ports may
>>>>>>>>>>>>>>>>>>> have affected this. I'm looking into this now.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I will be testing grouping aspects and scaling
>>>>>>>>>>>>>>>>>>>> scenarios related to that.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a
>>>>>>>>>>>>>>>>>>>>> great holiday!
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> We have now come to the last stage of finalizing
>>>>>>>>>>>>>>>>>>>>> 4.1.0-Alpha release. As I can recall following are the remaining tasks we
>>>>>>>>>>>>>>>>>>>>> need to complete:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> During past few days I was fixing issues in the
>>>>>>>>>>>>>>>>>>>>> Kubernetes workflow and following are the remaining problems:
>>>>>>>>>>>>>>>>>>>>> - Python agent does not publish health statistitics to
>>>>>>>>>>>>>>>>>>>>> CEP.
>>>>>>>>>>>>>>>>>>>>> - Autoscaler obsolete member rule invokes
>>>>>>>>>>>>>>>>>>>>> terminateInstance() method twice with the same member id. As a result the
>>>>>>>>>>>>>>>>>>>>> second call fails.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I'm currently working on fixing the above issues and
>>>>>>>>>>>>>>>>>>>>> finalizing the Kubernetes workflow.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I believe we verified the complete service grouping
>>>>>>>>>>>>>>>>>>>>> functionality with Mock IaaS however we could not test it with OpenStack
>>>>>>>>>>>>>>>>>>>>> and EC2.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I did the initial implementation of clustering support
>>>>>>>>>>>>>>>>>>>>> for Load Balancer and Cloud Controller, we need to verify it and apply it
>>>>>>>>>>>>>>>>>>>>> to Autoscaler and Stratos Manager.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Service grouping functionality allows us to add a load
>>>>>>>>>>>>>>>>>>>>> balancer cartridge to an application or group. However we need to provide a
>>>>>>>>>>>>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>>>>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Currently Docker base image size is around 380 MB and
>>>>>>>>>>>>>>>>>>>>> PHP Docker image size is around 404 MB. Due to a known issue in Kubernetes
>>>>>>>>>>>>>>>>>>>>> v0.5.2 we need to download the Docker images from Docker Hub once. It would
>>>>>>>>>>>>>>>>>>>>> be better if we could reduce the size of the base image so that we could
>>>>>>>>>>>>>>>>>>>>> save time on this process.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> It would be great if anyone would like to contribute
>>>>>>>>>>>>>>>>>>>>> to remaining tasks, we will try our best to complete them ASAP and announce
>>>>>>>>>>>>>>>>>>>>> 4.1.0-Alpha release.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Many Thanks
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> 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/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>>>>
>>>>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>>
>>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>
>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 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
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> 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
>>>
>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> Software Engineer, WSO2
>>
>> Blog: http://ravihansa3000.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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Great! Thanks Akila! Please focus on implementing clustering for Autoscaler.
Everyone, will try our best to complete everything in next couple of days
and release 4.1.0 Alpha ASAP. Please update as you progress.
Thanks
On Jan 3, 2015 9:05 PM, "Akila Ravihansa Perera" <ra...@wso2.com> wrote:
> Hi,
>
> I'll work on the Verify Clustering Support for Stratos Components task.
> I'm planning to use a Vagrant setup with Puppet for configuration
> management. Hope this will be helpful for our testing framework in the
> future.
>
> Thanks.
>
>
>
> On Sat, Jan 3, 2015 at 8:42 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I have now completed the ADC feature for service grouping functionality
>> and following is the current status of the tasks:
>>
>> *1. Finalize Kubernetes Workflow (DONE)*
>> 2. Verify Service Grouping on OpenStack and EC2
>> 3. Verify Clustering Support for Stratos Components
>> 4. Implement Load Balancer Configuration for Service Grouping
>> *5. Reduce the Docker Image Size (IN-PROGRESS) *
>> *6. Implement ADC logic for Service Grouping (DONE)*
>> *7. Implement Multi-Tenant support for Applications (IN-PROGRESS)*
>>
>> I verified an end to end workflow with Kubernetes and the entire flow
>> seems to be working fine:
>> https://gist.github.com/imesh/b8f81fac8de39183a504
>>
>> Thanks
>>
>> On Sat, Jan 3, 2015 at 8:16 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Great! Thanks Gayan, please propose a design for it.
>>>
>>> On Sat, Jan 3, 2015 at 8:03 PM, Gayan Gunarathne <ga...@wso2.com>
>>> wrote:
>>>
>>>> I can look into configuration of load Balances for service grouping.I
>>>> will start the new email thread for discuss the changes we need for this.
>>>>
>>>> Thanks,
>>>> Gayan
>>>>
>>>> On Sat, Jan 3, 2015 at 9:46 AM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> It looks like we have more tasks to complete:
>>>>>
>>>>> 1. Finalize Kubernetes Workflow *(DONE)*
>>>>> 2. Verify Service Grouping on OpenStack and EC2
>>>>> 3. Verify Clustering Support for Stratos Components
>>>>> 4. Implement Load Balancer Configuration for Service Grouping
>>>>> 5. Reduce the Docker Image Size
>>>>>
>>>>> *6. Implement ADC logic for Service Grouping (IN-PROGRESS)*
>>>>> At the moment artifact distribution logic does not work for service
>>>>> grouping. As a result artifacts are not checked out in instances. I'm
>>>>> currently implementing this logic.
>>>>>
>>>>> *7. Implement Multi-Tenant support for Applications*
>>>>> Currently we do not have support for tenants to sign up for
>>>>> Multi-Tenant applications, for each application deployment there is only
>>>>> one subscription.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Sat, Jan 3, 2015 at 7:10 AM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Great! Thanks Manula! Please update this thread as you go on.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 10:18 PM, Manula Chathurika Thantriwatte <
>>>>>> manulac@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I'll work on verifying service group on EC2.
>>>>>>>
>>>>>>> Thanks !
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 10:12 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Kubernetes workflow is now complete, I'm now working on fixing the
>>>>>>>> git clone issue in agent.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 9:42 PM, Rajkumar Rajaratnam <
>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Sorry. Lets use the other thread for testing update.
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 9:41 PM, Rajkumar Rajaratnam <
>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Getting an exception while deploying the application.
>>>>>>>>>>
>>>>>>>>>> [2015-01-02 21:31:12,401] INFO
>>>>>>>>>> {org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
>>>>>>>>>> replication controller: [replication-controller-id]
>>>>>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
>>>>>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
>>>>>>>>>> stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
>>>>>>>>>> [2015-01-02 21:31:12,402] ERROR
>>>>>>>>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>>>>>>>>>> org.apache.axis2.AxisFault: Mapping qname not fond for the package:
>>>>>>>>>> org.apache.stratos.common.beans
>>>>>>>>>> java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping
>>>>>>>>>> qname not fond for the package: org.apache.stratos.common.beans
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>>>>>>>>>> at
>>>>>>>>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>>>>>>>>>> at
>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>>> at
>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>>>>>> at
>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>>>>>>>>> at
>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>>>>>>>>> at
>>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>>>>>>>>> at
>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>>>>>> at
>>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>>>>>> at
>>>>>>>>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>>>>>>>>>> at
>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>>>>>>>>>> at
>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>>>>>>>>> at
>>>>>>>>>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>>>>>>>>>> at
>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>>>>>>>>>> at
>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>>>>>>>>>> at
>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>>>>>>>>>> at
>>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>>>>>>>>>> at
>>>>>>>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>>>>>>>>>> at
>>>>>>>>>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>>>>>>>>>> at
>>>>>>>>>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>>>>>>>>>> at
>>>>>>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>>>>>>>>>> at
>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>>>>>>>>> at
>>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>>> Caused by: org.apache.axis2.AxisFault: Mapping qname not fond for
>>>>>>>>>> the package: org.apache.stratos.common.beans
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
>>>>>>>>>> ... 54 more
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> Yes Raj, the modules include the logic and they being invoked
>>>>>>>>>>> from the callers.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <
>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> agent.py does not have any artifact management logic. It is
>>>>>>>>>>>> there in artifact management module.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Yes I can remember that it was working in previous milestones,
>>>>>>>>>>>>> however according to the current logic in agent.py, if a git repo url is
>>>>>>>>>>>>> specified it does nothing:
>>>>>>>>>>>>>
>>>>>>>>>>>>> ..
>>>>>>>>>>>>>
>>>>>>>>>>>>> At the end agent just wait in a while loop until terminated.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I can see that agent is listening to Artifact Updated event,
>>>>>>>>>>>>> did we send this event forcefully to make this work?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> It is already implemented and was working fine.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <
>>>>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> What do you mean?? Its there since M3
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Seems like we have not written logic in agent to checkout
>>>>>>>>>>>>>>>> artifacts from GIT repository.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have now fixed the issue of accessing the service via
>>>>>>>>>>>>>>>>> the host machine (http://kubernetes-master-ip:port/) and
>>>>>>>>>>>>>>>>> pushed changes to master branch.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Now I see a problem when a public GIT repo url is given
>>>>>>>>>>>>>>>>> without specifying credentials. I'm currently looking into this.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I have now resolved the health statistics publishing
>>>>>>>>>>>>>>>>>> issue in agent:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> - There were several topology event parsers which were
>>>>>>>>>>>>>>>>>> not properly updated with the latest changes. As a result those were
>>>>>>>>>>>>>>>>>> raising errors. I have now fixed them.
>>>>>>>>>>>>>>>>>> - Agent's logic which waits until CEP port is active was
>>>>>>>>>>>>>>>>>> not visible in the logs. As a result it was not possible to see why agent
>>>>>>>>>>>>>>>>>> is not publishing health statistics. I have now enabled logs to show this
>>>>>>>>>>>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>>>>>>>>>>>> - Docker images in docker hub are updated with the latest
>>>>>>>>>>>>>>>>>> changes.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Now I see a problem where the PHP service is not
>>>>>>>>>>>>>>>>>> accessible from the host machine, however it is accessible within the
>>>>>>>>>>>>>>>>>> Kubernetes master. The removal of host port from the container ports may
>>>>>>>>>>>>>>>>>> have affected this. I'm looking into this now.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I will be testing grouping aspects and scaling scenarios
>>>>>>>>>>>>>>>>>>> related to that.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a
>>>>>>>>>>>>>>>>>>>> great holiday!
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> We have now come to the last stage of finalizing
>>>>>>>>>>>>>>>>>>>> 4.1.0-Alpha release. As I can recall following are the remaining tasks we
>>>>>>>>>>>>>>>>>>>> need to complete:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> During past few days I was fixing issues in the
>>>>>>>>>>>>>>>>>>>> Kubernetes workflow and following are the remaining problems:
>>>>>>>>>>>>>>>>>>>> - Python agent does not publish health statistitics to
>>>>>>>>>>>>>>>>>>>> CEP.
>>>>>>>>>>>>>>>>>>>> - Autoscaler obsolete member rule invokes
>>>>>>>>>>>>>>>>>>>> terminateInstance() method twice with the same member id. As a result the
>>>>>>>>>>>>>>>>>>>> second call fails.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I'm currently working on fixing the above issues and
>>>>>>>>>>>>>>>>>>>> finalizing the Kubernetes workflow.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I believe we verified the complete service grouping
>>>>>>>>>>>>>>>>>>>> functionality with Mock IaaS however we could not test it with OpenStack
>>>>>>>>>>>>>>>>>>>> and EC2.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I did the initial implementation of clustering support
>>>>>>>>>>>>>>>>>>>> for Load Balancer and Cloud Controller, we need to verify it and apply it
>>>>>>>>>>>>>>>>>>>> to Autoscaler and Stratos Manager.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Service grouping functionality allows us to add a load
>>>>>>>>>>>>>>>>>>>> balancer cartridge to an application or group. However we need to provide a
>>>>>>>>>>>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>>>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Currently Docker base image size is around 380 MB and
>>>>>>>>>>>>>>>>>>>> PHP Docker image size is around 404 MB. Due to a known issue in Kubernetes
>>>>>>>>>>>>>>>>>>>> v0.5.2 we need to download the Docker images from Docker Hub once. It would
>>>>>>>>>>>>>>>>>>>> be better if we could reduce the size of the base image so that we could
>>>>>>>>>>>>>>>>>>>> save time on this process.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> It would be great if anyone would like to contribute to
>>>>>>>>>>>>>>>>>>>> remaining tasks, we will try our best to complete them ASAP and announce
>>>>>>>>>>>>>>>>>>>> 4.1.0-Alpha release.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Many Thanks
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> 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/
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>>
>>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>>>
>>>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>
>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>
>>>>>>>>> Mobile : +94777568639
>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> 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
>>
>
>
>
> --
> Akila Ravihansa Perera
> Software Engineer, WSO2
>
> Blog: http://ravihansa3000.blogspot.com
>
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Akila Ravihansa Perera <ra...@wso2.com>.
Hi,
I'll work on the Verify Clustering Support for Stratos Components task. I'm
planning to use a Vagrant setup with Puppet for configuration management.
Hope this will be helpful for our testing framework in the future.
Thanks.
On Sat, Jan 3, 2015 at 8:42 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I have now completed the ADC feature for service grouping functionality
> and following is the current status of the tasks:
>
> *1. Finalize Kubernetes Workflow (DONE)*
> 2. Verify Service Grouping on OpenStack and EC2
> 3. Verify Clustering Support for Stratos Components
> 4. Implement Load Balancer Configuration for Service Grouping
> *5. Reduce the Docker Image Size (IN-PROGRESS) *
> *6. Implement ADC logic for Service Grouping (DONE)*
> *7. Implement Multi-Tenant support for Applications (IN-PROGRESS)*
>
> I verified an end to end workflow with Kubernetes and the entire flow
> seems to be working fine:
> https://gist.github.com/imesh/b8f81fac8de39183a504
>
> Thanks
>
> On Sat, Jan 3, 2015 at 8:16 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Great! Thanks Gayan, please propose a design for it.
>>
>> On Sat, Jan 3, 2015 at 8:03 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
>>
>>> I can look into configuration of load Balances for service grouping.I
>>> will start the new email thread for discuss the changes we need for this.
>>>
>>> Thanks,
>>> Gayan
>>>
>>> On Sat, Jan 3, 2015 at 9:46 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> It looks like we have more tasks to complete:
>>>>
>>>> 1. Finalize Kubernetes Workflow *(DONE)*
>>>> 2. Verify Service Grouping on OpenStack and EC2
>>>> 3. Verify Clustering Support for Stratos Components
>>>> 4. Implement Load Balancer Configuration for Service Grouping
>>>> 5. Reduce the Docker Image Size
>>>>
>>>> *6. Implement ADC logic for Service Grouping (IN-PROGRESS)*
>>>> At the moment artifact distribution logic does not work for service
>>>> grouping. As a result artifacts are not checked out in instances. I'm
>>>> currently implementing this logic.
>>>>
>>>> *7. Implement Multi-Tenant support for Applications*
>>>> Currently we do not have support for tenants to sign up for
>>>> Multi-Tenant applications, for each application deployment there is only
>>>> one subscription.
>>>>
>>>> Thanks
>>>>
>>>> On Sat, Jan 3, 2015 at 7:10 AM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Great! Thanks Manula! Please update this thread as you go on.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Jan 2, 2015 at 10:18 PM, Manula Chathurika Thantriwatte <
>>>>> manulac@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I'll work on verifying service group on EC2.
>>>>>>
>>>>>> Thanks !
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 10:12 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Kubernetes workflow is now complete, I'm now working on fixing the
>>>>>>> git clone issue in agent.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 9:42 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> Sorry. Lets use the other thread for testing update.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 9:41 PM, Rajkumar Rajaratnam <
>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Getting an exception while deploying the application.
>>>>>>>>>
>>>>>>>>> [2015-01-02 21:31:12,401] INFO
>>>>>>>>> {org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
>>>>>>>>> replication controller: [replication-controller-id]
>>>>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
>>>>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
>>>>>>>>> stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
>>>>>>>>> [2015-01-02 21:31:12,402] ERROR
>>>>>>>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>>>>>>>>> org.apache.axis2.AxisFault: Mapping qname not fond for the package:
>>>>>>>>> org.apache.stratos.common.beans
>>>>>>>>> java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping
>>>>>>>>> qname not fond for the package: org.apache.stratos.common.beans
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
>>>>>>>>> at
>>>>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
>>>>>>>>> at
>>>>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
>>>>>>>>> at
>>>>>>>>> org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
>>>>>>>>> at
>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
>>>>>>>>> at
>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
>>>>>>>>> at
>>>>>>>>> org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
>>>>>>>>> at
>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
>>>>>>>>> at
>>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>>>>>>>> at
>>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>>>>>>>>> at
>>>>>>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>>>>>>>>> at
>>>>>>>>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>>>>>>>>> at
>>>>>>>>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>>>>>>>>> at
>>>>>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>>>>>>>> at
>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>>> Caused by: org.apache.axis2.AxisFault: Mapping qname not fond for
>>>>>>>>> the package: org.apache.stratos.common.beans
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
>>>>>>>>> ... 54 more
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Yes Raj, the modules include the logic and they being invoked
>>>>>>>>>> from the callers.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <
>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> agent.py does not have any artifact management logic. It is
>>>>>>>>>>> there in artifact management module.
>>>>>>>>>>>
>>>>>>>>>>> Thanks.
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Yes I can remember that it was working in previous milestones,
>>>>>>>>>>>> however according to the current logic in agent.py, if a git repo url is
>>>>>>>>>>>> specified it does nothing:
>>>>>>>>>>>>
>>>>>>>>>>>> ..
>>>>>>>>>>>>
>>>>>>>>>>>> At the end agent just wait in a while loop until terminated.
>>>>>>>>>>>>
>>>>>>>>>>>> I can see that agent is listening to Artifact Updated event,
>>>>>>>>>>>> did we send this event forcefully to make this work?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <
>>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> It is already implemented and was working fine.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <
>>>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> What do you mean?? Its there since M3
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Seems like we have not written logic in agent to checkout
>>>>>>>>>>>>>>> artifacts from GIT repository.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have now fixed the issue of accessing the service via the
>>>>>>>>>>>>>>>> host machine (http://kubernetes-master-ip:port/) and
>>>>>>>>>>>>>>>> pushed changes to master branch.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Now I see a problem when a public GIT repo url is given
>>>>>>>>>>>>>>>> without specifying credentials. I'm currently looking into this.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I have now resolved the health statistics publishing issue
>>>>>>>>>>>>>>>>> in agent:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> - There were several topology event parsers which were not
>>>>>>>>>>>>>>>>> properly updated with the latest changes. As a result those were raising
>>>>>>>>>>>>>>>>> errors. I have now fixed them.
>>>>>>>>>>>>>>>>> - Agent's logic which waits until CEP port is active was
>>>>>>>>>>>>>>>>> not visible in the logs. As a result it was not possible to see why agent
>>>>>>>>>>>>>>>>> is not publishing health statistics. I have now enabled logs to show this
>>>>>>>>>>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>>>>>>>>>>> - Docker images in docker hub are updated with the latest
>>>>>>>>>>>>>>>>> changes.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Now I see a problem where the PHP service is not
>>>>>>>>>>>>>>>>> accessible from the host machine, however it is accessible within the
>>>>>>>>>>>>>>>>> Kubernetes master. The removal of host port from the container ports may
>>>>>>>>>>>>>>>>> have affected this. I'm looking into this now.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I will be testing grouping aspects and scaling scenarios
>>>>>>>>>>>>>>>>>> related to that.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great
>>>>>>>>>>>>>>>>>>> holiday!
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> We have now come to the last stage of finalizing
>>>>>>>>>>>>>>>>>>> 4.1.0-Alpha release. As I can recall following are the remaining tasks we
>>>>>>>>>>>>>>>>>>> need to complete:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> During past few days I was fixing issues in the
>>>>>>>>>>>>>>>>>>> Kubernetes workflow and following are the remaining problems:
>>>>>>>>>>>>>>>>>>> - Python agent does not publish health statistitics to
>>>>>>>>>>>>>>>>>>> CEP.
>>>>>>>>>>>>>>>>>>> - Autoscaler obsolete member rule invokes
>>>>>>>>>>>>>>>>>>> terminateInstance() method twice with the same member id. As a result the
>>>>>>>>>>>>>>>>>>> second call fails.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I'm currently working on fixing the above issues and
>>>>>>>>>>>>>>>>>>> finalizing the Kubernetes workflow.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I believe we verified the complete service grouping
>>>>>>>>>>>>>>>>>>> functionality with Mock IaaS however we could not test it with OpenStack
>>>>>>>>>>>>>>>>>>> and EC2.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I did the initial implementation of clustering support
>>>>>>>>>>>>>>>>>>> for Load Balancer and Cloud Controller, we need to verify it and apply it
>>>>>>>>>>>>>>>>>>> to Autoscaler and Stratos Manager.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Service grouping functionality allows us to add a load
>>>>>>>>>>>>>>>>>>> balancer cartridge to an application or group. However we need to provide a
>>>>>>>>>>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Currently Docker base image size is around 380 MB and
>>>>>>>>>>>>>>>>>>> PHP Docker image size is around 404 MB. Due to a known issue in Kubernetes
>>>>>>>>>>>>>>>>>>> v0.5.2 we need to download the Docker images from Docker Hub once. It would
>>>>>>>>>>>>>>>>>>> be better if we could reduce the size of the base image so that we could
>>>>>>>>>>>>>>>>>>> save time on this process.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> It would be great if anyone would like to contribute to
>>>>>>>>>>>>>>>>>>> remaining tasks, we will try our best to complete them ASAP and announce
>>>>>>>>>>>>>>>>>>> 4.1.0-Alpha release.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Many Thanks
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> 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/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>>>>
>>>>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>>
>>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>
>>>>>>>>> Mobile : +94777568639
>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Rajkumar Rajaratnam
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>> Software Engineer, WSO2
>>>>>>>>
>>>>>>>> Mobile : +94777568639
>>>>>>>> Blog : rajkumarr.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> 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
>
--
Akila Ravihansa Perera
Software Engineer, WSO2
Blog: http://ravihansa3000.blogspot.com
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
I have now completed the ADC feature for service grouping functionality and
following is the current status of the tasks:
*1. Finalize Kubernetes Workflow (DONE)*
2. Verify Service Grouping on OpenStack and EC2
3. Verify Clustering Support for Stratos Components
4. Implement Load Balancer Configuration for Service Grouping
*5. Reduce the Docker Image Size (IN-PROGRESS) *
*6. Implement ADC logic for Service Grouping (DONE)*
*7. Implement Multi-Tenant support for Applications (IN-PROGRESS)*
I verified an end to end workflow with Kubernetes and the entire flow seems
to be working fine:
https://gist.github.com/imesh/b8f81fac8de39183a504
Thanks
On Sat, Jan 3, 2015 at 8:16 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Great! Thanks Gayan, please propose a design for it.
>
> On Sat, Jan 3, 2015 at 8:03 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
>
>> I can look into configuration of load Balances for service grouping.I
>> will start the new email thread for discuss the changes we need for this.
>>
>> Thanks,
>> Gayan
>>
>> On Sat, Jan 3, 2015 at 9:46 AM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Hi Devs,
>>>
>>> It looks like we have more tasks to complete:
>>>
>>> 1. Finalize Kubernetes Workflow *(DONE)*
>>> 2. Verify Service Grouping on OpenStack and EC2
>>> 3. Verify Clustering Support for Stratos Components
>>> 4. Implement Load Balancer Configuration for Service Grouping
>>> 5. Reduce the Docker Image Size
>>>
>>> *6. Implement ADC logic for Service Grouping (IN-PROGRESS)*
>>> At the moment artifact distribution logic does not work for service
>>> grouping. As a result artifacts are not checked out in instances. I'm
>>> currently implementing this logic.
>>>
>>> *7. Implement Multi-Tenant support for Applications*
>>> Currently we do not have support for tenants to sign up for Multi-Tenant
>>> applications, for each application deployment there is only one
>>> subscription.
>>>
>>> Thanks
>>>
>>> On Sat, Jan 3, 2015 at 7:10 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Great! Thanks Manula! Please update this thread as you go on.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Jan 2, 2015 at 10:18 PM, Manula Chathurika Thantriwatte <
>>>> manulac@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I'll work on verifying service group on EC2.
>>>>>
>>>>> Thanks !
>>>>>
>>>>> On Fri, Jan 2, 2015 at 10:12 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Kubernetes workflow is now complete, I'm now working on fixing the
>>>>>> git clone issue in agent.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 9:42 PM, Rajkumar Rajaratnam <
>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>
>>>>>>> Sorry. Lets use the other thread for testing update.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 9:41 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> Getting an exception while deploying the application.
>>>>>>>>
>>>>>>>> [2015-01-02 21:31:12,401] INFO
>>>>>>>> {org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
>>>>>>>> replication controller: [replication-controller-id]
>>>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
>>>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
>>>>>>>> stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
>>>>>>>> [2015-01-02 21:31:12,402] ERROR
>>>>>>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>>>>>>>> org.apache.axis2.AxisFault: Mapping qname not fond for the package:
>>>>>>>> org.apache.stratos.common.beans
>>>>>>>> java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping
>>>>>>>> qname not fond for the package: org.apache.stratos.common.beans
>>>>>>>> at
>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
>>>>>>>> at
>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
>>>>>>>> at
>>>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
>>>>>>>> at
>>>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
>>>>>>>> at
>>>>>>>> org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
>>>>>>>> at
>>>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
>>>>>>>> at
>>>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
>>>>>>>> at
>>>>>>>> org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
>>>>>>>> at
>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
>>>>>>>> at
>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
>>>>>>>> at
>>>>>>>> org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
>>>>>>>> at
>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
>>>>>>>> at
>>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
>>>>>>>> at
>>>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
>>>>>>>> at
>>>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
>>>>>>>> at
>>>>>>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
>>>>>>>> at
>>>>>>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>>>>>>> at
>>>>>>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>>>>>>> at
>>>>>>>> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>>>>>>> at
>>>>>>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>>>>>>> at
>>>>>>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>>>>>>> at
>>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>>>>>>>> at
>>>>>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>>>>>>>> at
>>>>>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>>>>>>>> at
>>>>>>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>>>>>>>> at
>>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>>>>>>>> at
>>>>>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>>>>>>>> at
>>>>>>>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>>>>>>>> at
>>>>>>>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>>>>>>>> at
>>>>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>>>>>>>> at
>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>>>>>>> at
>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>>> Caused by: org.apache.axis2.AxisFault: Mapping qname not fond for
>>>>>>>> the package: org.apache.stratos.common.beans
>>>>>>>> at
>>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
>>>>>>>> ... 54 more
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Yes Raj, the modules include the logic and they being invoked from
>>>>>>>>> the callers.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <
>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> agent.py does not have any artifact management logic. It is there
>>>>>>>>>> in artifact management module.
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> Yes I can remember that it was working in previous milestones,
>>>>>>>>>>> however according to the current logic in agent.py, if a git repo url is
>>>>>>>>>>> specified it does nothing:
>>>>>>>>>>>
>>>>>>>>>>> ..
>>>>>>>>>>>
>>>>>>>>>>> At the end agent just wait in a while loop until terminated.
>>>>>>>>>>>
>>>>>>>>>>> I can see that agent is listening to Artifact Updated event, did
>>>>>>>>>>> we send this event forcefully to make this work?
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <
>>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> It is already implemented and was working fine.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <
>>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> What do you mean?? Its there since M3
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Seems like we have not written logic in agent to checkout
>>>>>>>>>>>>>> artifacts from GIT repository.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have now fixed the issue of accessing the service via the
>>>>>>>>>>>>>>> host machine (http://kubernetes-master-ip:port/) and pushed
>>>>>>>>>>>>>>> changes to master branch.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Now I see a problem when a public GIT repo url is given
>>>>>>>>>>>>>>> without specifying credentials. I'm currently looking into this.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have now resolved the health statistics publishing issue
>>>>>>>>>>>>>>>> in agent:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> - There were several topology event parsers which were not
>>>>>>>>>>>>>>>> properly updated with the latest changes. As a result those were raising
>>>>>>>>>>>>>>>> errors. I have now fixed them.
>>>>>>>>>>>>>>>> - Agent's logic which waits until CEP port is active was
>>>>>>>>>>>>>>>> not visible in the logs. As a result it was not possible to see why agent
>>>>>>>>>>>>>>>> is not publishing health statistics. I have now enabled logs to show this
>>>>>>>>>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>>>>>>>>>> - Docker images in docker hub are updated with the latest
>>>>>>>>>>>>>>>> changes.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Now I see a problem where the PHP service is not accessible
>>>>>>>>>>>>>>>> from the host machine, however it is accessible within the Kubernetes
>>>>>>>>>>>>>>>> master. The removal of host port from the container ports may have affected
>>>>>>>>>>>>>>>> this. I'm looking into this now.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I will be testing grouping aspects and scaling scenarios
>>>>>>>>>>>>>>>>> related to that.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great
>>>>>>>>>>>>>>>>>> holiday!
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> We have now come to the last stage of finalizing
>>>>>>>>>>>>>>>>>> 4.1.0-Alpha release. As I can recall following are the remaining tasks we
>>>>>>>>>>>>>>>>>> need to complete:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> During past few days I was fixing issues in the
>>>>>>>>>>>>>>>>>> Kubernetes workflow and following are the remaining problems:
>>>>>>>>>>>>>>>>>> - Python agent does not publish health statistitics to
>>>>>>>>>>>>>>>>>> CEP.
>>>>>>>>>>>>>>>>>> - Autoscaler obsolete member rule invokes
>>>>>>>>>>>>>>>>>> terminateInstance() method twice with the same member id. As a result the
>>>>>>>>>>>>>>>>>> second call fails.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I'm currently working on fixing the above issues and
>>>>>>>>>>>>>>>>>> finalizing the Kubernetes workflow.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I believe we verified the complete service grouping
>>>>>>>>>>>>>>>>>> functionality with Mock IaaS however we could not test it with OpenStack
>>>>>>>>>>>>>>>>>> and EC2.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I did the initial implementation of clustering support
>>>>>>>>>>>>>>>>>> for Load Balancer and Cloud Controller, we need to verify it and apply it
>>>>>>>>>>>>>>>>>> to Autoscaler and Stratos Manager.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Service grouping functionality allows us to add a load
>>>>>>>>>>>>>>>>>> balancer cartridge to an application or group. However we need to provide a
>>>>>>>>>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Currently Docker base image size is around 380 MB and PHP
>>>>>>>>>>>>>>>>>> Docker image size is around 404 MB. Due to a known issue in Kubernetes
>>>>>>>>>>>>>>>>>> v0.5.2 we need to download the Docker images from Docker Hub once. It would
>>>>>>>>>>>>>>>>>> be better if we could reduce the size of the base image so that we could
>>>>>>>>>>>>>>>>>> save time on this process.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> It would be great if anyone would like to contribute to
>>>>>>>>>>>>>>>>>> remaining tasks, we will try our best to complete them ASAP and announce
>>>>>>>>>>>>>>>>>> 4.1.0-Alpha release.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Many Thanks
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> 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/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>>>
>>>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>
>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Rajkumar Rajaratnam
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>> Software Engineer, WSO2
>>>>>>>>
>>>>>>>> Mobile : +94777568639
>>>>>>>> Blog : rajkumarr.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Rajkumar Rajaratnam
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>> Software Engineer, WSO2
>>>>>>>
>>>>>>> Mobile : +94777568639
>>>>>>> Blog : rajkumarr.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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
>>>
>>
>>
>>
>> --
>>
>> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Great! Thanks Gayan, please propose a design for it.
On Sat, Jan 3, 2015 at 8:03 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
> I can look into configuration of load Balances for service grouping.I will
> start the new email thread for discuss the changes we need for this.
>
> Thanks,
> Gayan
>
> On Sat, Jan 3, 2015 at 9:46 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Hi Devs,
>>
>> It looks like we have more tasks to complete:
>>
>> 1. Finalize Kubernetes Workflow *(DONE)*
>> 2. Verify Service Grouping on OpenStack and EC2
>> 3. Verify Clustering Support for Stratos Components
>> 4. Implement Load Balancer Configuration for Service Grouping
>> 5. Reduce the Docker Image Size
>>
>> *6. Implement ADC logic for Service Grouping (IN-PROGRESS)*
>> At the moment artifact distribution logic does not work for service
>> grouping. As a result artifacts are not checked out in instances. I'm
>> currently implementing this logic.
>>
>> *7. Implement Multi-Tenant support for Applications*
>> Currently we do not have support for tenants to sign up for Multi-Tenant
>> applications, for each application deployment there is only one
>> subscription.
>>
>> Thanks
>>
>> On Sat, Jan 3, 2015 at 7:10 AM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Great! Thanks Manula! Please update this thread as you go on.
>>>
>>> Thanks
>>>
>>> On Fri, Jan 2, 2015 at 10:18 PM, Manula Chathurika Thantriwatte <
>>> manulac@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'll work on verifying service group on EC2.
>>>>
>>>> Thanks !
>>>>
>>>> On Fri, Jan 2, 2015 at 10:12 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Kubernetes workflow is now complete, I'm now working on fixing the git
>>>>> clone issue in agent.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Jan 2, 2015 at 9:42 PM, Rajkumar Rajaratnam <
>>>>> rajkumarr@wso2.com> wrote:
>>>>>
>>>>>> Sorry. Lets use the other thread for testing update.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 9:41 PM, Rajkumar Rajaratnam <
>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>
>>>>>>> Getting an exception while deploying the application.
>>>>>>>
>>>>>>> [2015-01-02 21:31:12,401] INFO
>>>>>>> {org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
>>>>>>> replication controller: [replication-controller-id]
>>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
>>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
>>>>>>> stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
>>>>>>> [2015-01-02 21:31:12,402] ERROR
>>>>>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>>>>>>> org.apache.axis2.AxisFault: Mapping qname not fond for the package:
>>>>>>> org.apache.stratos.common.beans
>>>>>>> java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping
>>>>>>> qname not fond for the package: org.apache.stratos.common.beans
>>>>>>> at
>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
>>>>>>> at
>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
>>>>>>> at
>>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
>>>>>>> at
>>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
>>>>>>> at
>>>>>>> org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
>>>>>>> at
>>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
>>>>>>> at
>>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
>>>>>>> at
>>>>>>> org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
>>>>>>> at
>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
>>>>>>> at
>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
>>>>>>> at
>>>>>>> org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
>>>>>>> at
>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
>>>>>>> at
>>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
>>>>>>> at
>>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
>>>>>>> at
>>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
>>>>>>> at
>>>>>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
>>>>>>> at
>>>>>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>>>>>> at
>>>>>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>>>>>> at
>>>>>>> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>>>>>> at
>>>>>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>>>>>> at
>>>>>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>>>>>>> at
>>>>>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>>> at
>>>>>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>>>>>> at
>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>>>>>> at
>>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>>> at
>>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>>>>>> at
>>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>>>>>>> at
>>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>>> at
>>>>>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>>>>>> at
>>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>>>>>>> at
>>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>>> at
>>>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>>>>>>> at
>>>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>>>>>>> at
>>>>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>>>>>>> at
>>>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>>>>>>> at
>>>>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>>>>>>> at
>>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>>>>>>> at
>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>>>>>> at
>>>>>>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>>>>>>> at
>>>>>>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>>>>>>> at
>>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>>>>>>> at
>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>>>>>>> at
>>>>>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>>>>>>> at
>>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>>>>>>> at
>>>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>>>>>>> at
>>>>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>>>>>>> at
>>>>>>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>>>>>>> at
>>>>>>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>>>>>>> at
>>>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>>>>>>> at
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>>>>>> at
>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>>> Caused by: org.apache.axis2.AxisFault: Mapping qname not fond for
>>>>>>> the package: org.apache.stratos.common.beans
>>>>>>> at
>>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
>>>>>>> ... 54 more
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Yes Raj, the modules include the logic and they being invoked from
>>>>>>>> the callers.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <
>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> agent.py does not have any artifact management logic. It is there
>>>>>>>>> in artifact management module.
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Yes I can remember that it was working in previous milestones,
>>>>>>>>>> however according to the current logic in agent.py, if a git repo url is
>>>>>>>>>> specified it does nothing:
>>>>>>>>>>
>>>>>>>>>> ..
>>>>>>>>>>
>>>>>>>>>> At the end agent just wait in a while loop until terminated.
>>>>>>>>>>
>>>>>>>>>> I can see that agent is listening to Artifact Updated event, did
>>>>>>>>>> we send this event forcefully to make this work?
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <
>>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> It is already implemented and was working fine.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>>>>>>>>
>>>>>>>>>>> Thanks.
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <
>>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> What do you mean?? Its there since M3
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Seems like we have not written logic in agent to checkout
>>>>>>>>>>>>> artifacts from GIT repository.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have now fixed the issue of accessing the service via the
>>>>>>>>>>>>>> host machine (http://kubernetes-master-ip:port/) and pushed
>>>>>>>>>>>>>> changes to master branch.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Now I see a problem when a public GIT repo url is given
>>>>>>>>>>>>>> without specifying credentials. I'm currently looking into this.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have now resolved the health statistics publishing issue
>>>>>>>>>>>>>>> in agent:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> - There were several topology event parsers which were not
>>>>>>>>>>>>>>> properly updated with the latest changes. As a result those were raising
>>>>>>>>>>>>>>> errors. I have now fixed them.
>>>>>>>>>>>>>>> - Agent's logic which waits until CEP port is active was not
>>>>>>>>>>>>>>> visible in the logs. As a result it was not possible to see why agent is
>>>>>>>>>>>>>>> not publishing health statistics. I have now enabled logs to show this
>>>>>>>>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>>>>>>>>> - Docker images in docker hub are updated with the latest
>>>>>>>>>>>>>>> changes.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Now I see a problem where the PHP service is not accessible
>>>>>>>>>>>>>>> from the host machine, however it is accessible within the Kubernetes
>>>>>>>>>>>>>>> master. The removal of host port from the container ports may have affected
>>>>>>>>>>>>>>> this. I'm looking into this now.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I will be testing grouping aspects and scaling scenarios
>>>>>>>>>>>>>>>> related to that.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great
>>>>>>>>>>>>>>>>> holiday!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> We have now come to the last stage of finalizing
>>>>>>>>>>>>>>>>> 4.1.0-Alpha release. As I can recall following are the remaining tasks we
>>>>>>>>>>>>>>>>> need to complete:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> During past few days I was fixing issues in the Kubernetes
>>>>>>>>>>>>>>>>> workflow and following are the remaining problems:
>>>>>>>>>>>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>>>>>>>>>>>> - Autoscaler obsolete member rule invokes
>>>>>>>>>>>>>>>>> terminateInstance() method twice with the same member id. As a result the
>>>>>>>>>>>>>>>>> second call fails.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I'm currently working on fixing the above issues and
>>>>>>>>>>>>>>>>> finalizing the Kubernetes workflow.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I believe we verified the complete service grouping
>>>>>>>>>>>>>>>>> functionality with Mock IaaS however we could not test it with OpenStack
>>>>>>>>>>>>>>>>> and EC2.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I did the initial implementation of clustering support for
>>>>>>>>>>>>>>>>> Load Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>>>>>>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Service grouping functionality allows us to add a load
>>>>>>>>>>>>>>>>> balancer cartridge to an application or group. However we need to provide a
>>>>>>>>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Currently Docker base image size is around 380 MB and PHP
>>>>>>>>>>>>>>>>> Docker image size is around 404 MB. Due to a known issue in Kubernetes
>>>>>>>>>>>>>>>>> v0.5.2 we need to download the Docker images from Docker Hub once. It would
>>>>>>>>>>>>>>>>> be better if we could reduce the size of the base image so that we could
>>>>>>>>>>>>>>>>> save time on this process.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> It would be great if anyone would like to contribute to
>>>>>>>>>>>>>>>>> remaining tasks, we will try our best to complete them ASAP and announce
>>>>>>>>>>>>>>>>> 4.1.0-Alpha release.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Many Thanks
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> 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/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>>
>>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>
>>>>>>>>> Mobile : +94777568639
>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Rajkumar Rajaratnam
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>> Software Engineer, WSO2
>>>>>>>
>>>>>>> Mobile : +94777568639
>>>>>>> Blog : rajkumarr.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Rajkumar Rajaratnam
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>> Software Engineer, WSO2
>>>>>>
>>>>>> Mobile : +94777568639
>>>>>> Blog : rajkumarr.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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
>>
>
>
>
> --
>
> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Gayan Gunarathne <ga...@wso2.com>.
I can look into configuration of load Balances for service grouping.I will
start the new email thread for discuss the changes we need for this.
Thanks,
Gayan
On Sat, Jan 3, 2015 at 9:46 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Devs,
>
> It looks like we have more tasks to complete:
>
> 1. Finalize Kubernetes Workflow *(DONE)*
> 2. Verify Service Grouping on OpenStack and EC2
> 3. Verify Clustering Support for Stratos Components
> 4. Implement Load Balancer Configuration for Service Grouping
> 5. Reduce the Docker Image Size
>
> *6. Implement ADC logic for Service Grouping (IN-PROGRESS)*
> At the moment artifact distribution logic does not work for service
> grouping. As a result artifacts are not checked out in instances. I'm
> currently implementing this logic.
>
> *7. Implement Multi-Tenant support for Applications*
> Currently we do not have support for tenants to sign up for Multi-Tenant
> applications, for each application deployment there is only one
> subscription.
>
> Thanks
>
> On Sat, Jan 3, 2015 at 7:10 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Great! Thanks Manula! Please update this thread as you go on.
>>
>> Thanks
>>
>> On Fri, Jan 2, 2015 at 10:18 PM, Manula Chathurika Thantriwatte <
>> manulac@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I'll work on verifying service group on EC2.
>>>
>>> Thanks !
>>>
>>> On Fri, Jan 2, 2015 at 10:12 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Kubernetes workflow is now complete, I'm now working on fixing the git
>>>> clone issue in agent.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Jan 2, 2015 at 9:42 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>>> > wrote:
>>>>
>>>>> Sorry. Lets use the other thread for testing update.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Fri, Jan 2, 2015 at 9:41 PM, Rajkumar Rajaratnam <
>>>>> rajkumarr@wso2.com> wrote:
>>>>>
>>>>>> Getting an exception while deploying the application.
>>>>>>
>>>>>> [2015-01-02 21:31:12,401] INFO
>>>>>> {org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
>>>>>> replication controller: [replication-controller-id]
>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
>>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
>>>>>> stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
>>>>>> [2015-01-02 21:31:12,402] ERROR
>>>>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>>>>>> org.apache.axis2.AxisFault: Mapping qname not fond for the package:
>>>>>> org.apache.stratos.common.beans
>>>>>> java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping qname
>>>>>> not fond for the package: org.apache.stratos.common.beans
>>>>>> at
>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
>>>>>> at
>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
>>>>>> at
>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
>>>>>> at
>>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
>>>>>> at org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
>>>>>> at
>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
>>>>>> at
>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
>>>>>> at
>>>>>> org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
>>>>>> at
>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
>>>>>> at
>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
>>>>>> at
>>>>>> org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
>>>>>> at
>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
>>>>>> at
>>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
>>>>>> at
>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
>>>>>> at
>>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
>>>>>> at
>>>>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
>>>>>> at
>>>>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>>>>> at
>>>>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>>>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>>>>> at
>>>>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>>>>> at
>>>>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>>>>>> at
>>>>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>> at
>>>>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>>>>> at
>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>>>>> at
>>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>>> at
>>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>>>>> at
>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>>>>>> at
>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>> at
>>>>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>>>>> at
>>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>>>>>> at
>>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>>>>>> at
>>>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>>>>>> at
>>>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>>>>>> at
>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>>>>>> at
>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>>>>> at
>>>>>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>>>>>> at
>>>>>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>>>>>> at
>>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>>>>>> at
>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>>>>>> at
>>>>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>>>>>> at
>>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>>>>>> at
>>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>>>>>> at
>>>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>>>>>> at
>>>>>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>>>>>> at
>>>>>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>>>>>> at
>>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>>> Caused by: org.apache.axis2.AxisFault: Mapping qname not fond for the
>>>>>> package: org.apache.stratos.common.beans
>>>>>> at
>>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
>>>>>> ... 54 more
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Yes Raj, the modules include the logic and they being invoked from
>>>>>>> the callers.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> agent.py does not have any artifact management logic. It is there
>>>>>>>> in artifact management module.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Yes I can remember that it was working in previous milestones,
>>>>>>>>> however according to the current logic in agent.py, if a git repo url is
>>>>>>>>> specified it does nothing:
>>>>>>>>>
>>>>>>>>> ..
>>>>>>>>>
>>>>>>>>> At the end agent just wait in a while loop until terminated.
>>>>>>>>>
>>>>>>>>> I can see that agent is listening to Artifact Updated event, did
>>>>>>>>> we send this event forcefully to make this work?
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <
>>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> It is already implemented and was working fine.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <
>>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> What do you mean?? Its there since M3
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Seems like we have not written logic in agent to checkout
>>>>>>>>>>>> artifacts from GIT repository.
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I have now fixed the issue of accessing the service via the
>>>>>>>>>>>>> host machine (http://kubernetes-master-ip:port/) and pushed
>>>>>>>>>>>>> changes to master branch.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now I see a problem when a public GIT repo url is given
>>>>>>>>>>>>> without specifying credentials. I'm currently looking into this.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have now resolved the health statistics publishing issue in
>>>>>>>>>>>>>> agent:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> - There were several topology event parsers which were not
>>>>>>>>>>>>>> properly updated with the latest changes. As a result those were raising
>>>>>>>>>>>>>> errors. I have now fixed them.
>>>>>>>>>>>>>> - Agent's logic which waits until CEP port is active was not
>>>>>>>>>>>>>> visible in the logs. As a result it was not possible to see why agent is
>>>>>>>>>>>>>> not publishing health statistics. I have now enabled logs to show this
>>>>>>>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>>>>>>>> - Docker images in docker hub are updated with the latest
>>>>>>>>>>>>>> changes.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Now I see a problem where the PHP service is not accessible
>>>>>>>>>>>>>> from the host machine, however it is accessible within the Kubernetes
>>>>>>>>>>>>>> master. The removal of host port from the container ports may have affected
>>>>>>>>>>>>>> this. I'm looking into this now.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I will be testing grouping aspects and scaling scenarios
>>>>>>>>>>>>>>> related to that.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <
>>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great
>>>>>>>>>>>>>>>> holiday!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We have now come to the last stage of finalizing
>>>>>>>>>>>>>>>> 4.1.0-Alpha release. As I can recall following are the remaining tasks we
>>>>>>>>>>>>>>>> need to complete:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> During past few days I was fixing issues in the Kubernetes
>>>>>>>>>>>>>>>> workflow and following are the remaining problems:
>>>>>>>>>>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>>>>>>>>>>> - Autoscaler obsolete member rule invokes
>>>>>>>>>>>>>>>> terminateInstance() method twice with the same member id. As a result the
>>>>>>>>>>>>>>>> second call fails.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I'm currently working on fixing the above issues and
>>>>>>>>>>>>>>>> finalizing the Kubernetes workflow.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I believe we verified the complete service grouping
>>>>>>>>>>>>>>>> functionality with Mock IaaS however we could not test it with OpenStack
>>>>>>>>>>>>>>>> and EC2.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I did the initial implementation of clustering support for
>>>>>>>>>>>>>>>> Load Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>>>>>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Service grouping functionality allows us to add a load
>>>>>>>>>>>>>>>> balancer cartridge to an application or group. However we need to provide a
>>>>>>>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Currently Docker base image size is around 380 MB and PHP
>>>>>>>>>>>>>>>> Docker image size is around 404 MB. Due to a known issue in Kubernetes
>>>>>>>>>>>>>>>> v0.5.2 we need to download the Docker images from Docker Hub once. It would
>>>>>>>>>>>>>>>> be better if we could reduce the size of the base image so that we could
>>>>>>>>>>>>>>>> save time on this process.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> It would be great if anyone would like to contribute to
>>>>>>>>>>>>>>>> remaining tasks, we will try our best to complete them ASAP and announce
>>>>>>>>>>>>>>>> 4.1.0-Alpha release.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Many Thanks
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> 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/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>>
>>>>>>>>>> Mobile : +94777568639
>>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Rajkumar Rajaratnam
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>> Software Engineer, WSO2
>>>>>>>>
>>>>>>>> Mobile : +94777568639
>>>>>>>> Blog : rajkumarr.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Rajkumar Rajaratnam
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>> Software Engineer, WSO2
>>>>>>
>>>>>> Mobile : +94777568639
>>>>>> Blog : rajkumarr.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Rajkumar Rajaratnam
>>>>> Committer & PMC Member, Apache Stratos
>>>>> Software Engineer, WSO2
>>>>>
>>>>> Mobile : +94777568639
>>>>> Blog : rajkumarr.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Devs,
It looks like we have more tasks to complete:
1. Finalize Kubernetes Workflow *(DONE)*
2. Verify Service Grouping on OpenStack and EC2
3. Verify Clustering Support for Stratos Components
4. Implement Load Balancer Configuration for Service Grouping
5. Reduce the Docker Image Size
*6. Implement ADC logic for Service Grouping (IN-PROGRESS)*
At the moment artifact distribution logic does not work for service
grouping. As a result artifacts are not checked out in instances. I'm
currently implementing this logic.
*7. Implement Multi-Tenant support for Applications*
Currently we do not have support for tenants to sign up for Multi-Tenant
applications, for each application deployment there is only one
subscription.
Thanks
On Sat, Jan 3, 2015 at 7:10 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Great! Thanks Manula! Please update this thread as you go on.
>
> Thanks
>
> On Fri, Jan 2, 2015 at 10:18 PM, Manula Chathurika Thantriwatte <
> manulac@wso2.com> wrote:
>
>> Hi,
>>
>> I'll work on verifying service group on EC2.
>>
>> Thanks !
>>
>> On Fri, Jan 2, 2015 at 10:12 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Kubernetes workflow is now complete, I'm now working on fixing the git
>>> clone issue in agent.
>>>
>>> Thanks
>>>
>>> On Fri, Jan 2, 2015 at 9:42 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>>> wrote:
>>>
>>>> Sorry. Lets use the other thread for testing update.
>>>>
>>>> Thanks.
>>>>
>>>> On Fri, Jan 2, 2015 at 9:41 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>>> > wrote:
>>>>
>>>>> Getting an exception while deploying the application.
>>>>>
>>>>> [2015-01-02 21:31:12,401] INFO
>>>>> {org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
>>>>> replication controller: [replication-controller-id]
>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
>>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
>>>>> stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
>>>>> [2015-01-02 21:31:12,402] ERROR
>>>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>>>>> org.apache.axis2.AxisFault: Mapping qname not fond for the package:
>>>>> org.apache.stratos.common.beans
>>>>> java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping qname
>>>>> not fond for the package: org.apache.stratos.common.beans
>>>>> at
>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
>>>>> at
>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
>>>>> at
>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
>>>>> at
>>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
>>>>> at org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
>>>>> at
>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
>>>>> at
>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
>>>>> at
>>>>> org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
>>>>> at
>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
>>>>> at
>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
>>>>> at
>>>>> org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
>>>>> at
>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
>>>>> at
>>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
>>>>> at
>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
>>>>> at
>>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
>>>>> at
>>>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
>>>>> at
>>>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>>>> at
>>>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>>>> at
>>>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>>>> at
>>>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>>>>> at
>>>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>> at
>>>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>>>> at
>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>>>> at
>>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>>> at
>>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>>>> at
>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>>>>> at
>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>> at
>>>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>>>> at
>>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>>>>> at
>>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>>> at
>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>>>>> at
>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>>>>> at
>>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>>>>> at
>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>>>>> at
>>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>>>>> at
>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>>>>> at
>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>>>> at
>>>>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>>>>> at
>>>>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>>>>> at
>>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>>>>> at
>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>>>>> at
>>>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>>>>> at
>>>>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>>>>> at
>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>>>>> at
>>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>>>>> at
>>>>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>>>>> at
>>>>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>>>>> at
>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>>>> at java.lang.Thread.run(Thread.java:662)
>>>>> Caused by: org.apache.axis2.AxisFault: Mapping qname not fond for the
>>>>> package: org.apache.stratos.common.beans
>>>>> at
>>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
>>>>> ... 54 more
>>>>>
>>>>> On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Yes Raj, the modules include the logic and they being invoked from
>>>>>> the callers.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <
>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>
>>>>>>> agent.py does not have any artifact management logic. It is there in
>>>>>>> artifact management module.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Yes I can remember that it was working in previous milestones,
>>>>>>>> however according to the current logic in agent.py, if a git repo url is
>>>>>>>> specified it does nothing:
>>>>>>>>
>>>>>>>> ..
>>>>>>>>
>>>>>>>> At the end agent just wait in a while loop until terminated.
>>>>>>>>
>>>>>>>> I can see that agent is listening to Artifact Updated event, did we
>>>>>>>> send this event forcefully to make this work?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <
>>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> It is already implemented and was working fine.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <
>>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> What do you mean?? Its there since M3
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> Seems like we have not written logic in agent to checkout
>>>>>>>>>>> artifacts from GIT repository.
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have now fixed the issue of accessing the service via the
>>>>>>>>>>>> host machine (http://kubernetes-master-ip:port/) and pushed
>>>>>>>>>>>> changes to master branch.
>>>>>>>>>>>>
>>>>>>>>>>>> Now I see a problem when a public GIT repo url is given without
>>>>>>>>>>>> specifying credentials. I'm currently looking into this.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I have now resolved the health statistics publishing issue in
>>>>>>>>>>>>> agent:
>>>>>>>>>>>>>
>>>>>>>>>>>>> - There were several topology event parsers which were not
>>>>>>>>>>>>> properly updated with the latest changes. As a result those were raising
>>>>>>>>>>>>> errors. I have now fixed them.
>>>>>>>>>>>>> - Agent's logic which waits until CEP port is active was not
>>>>>>>>>>>>> visible in the logs. As a result it was not possible to see why agent is
>>>>>>>>>>>>> not publishing health statistics. I have now enabled logs to show this
>>>>>>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>>>>>>> - Docker images in docker hub are updated with the latest
>>>>>>>>>>>>> changes.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now I see a problem where the PHP service is not accessible
>>>>>>>>>>>>> from the host machine, however it is accessible within the Kubernetes
>>>>>>>>>>>>> master. The removal of host port from the container ports may have affected
>>>>>>>>>>>>> this. I'm looking into this now.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I will be testing grouping aspects and scaling scenarios
>>>>>>>>>>>>>> related to that.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <
>>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great
>>>>>>>>>>>>>>> holiday!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha
>>>>>>>>>>>>>>> release. As I can recall following are the remaining tasks we need to
>>>>>>>>>>>>>>> complete:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> During past few days I was fixing issues in the Kubernetes
>>>>>>>>>>>>>>> workflow and following are the remaining problems:
>>>>>>>>>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>>>>>>>>>> - Autoscaler obsolete member rule invokes
>>>>>>>>>>>>>>> terminateInstance() method twice with the same member id. As a result the
>>>>>>>>>>>>>>> second call fails.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I'm currently working on fixing the above issues and
>>>>>>>>>>>>>>> finalizing the Kubernetes workflow.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I believe we verified the complete service grouping
>>>>>>>>>>>>>>> functionality with Mock IaaS however we could not test it with OpenStack
>>>>>>>>>>>>>>> and EC2.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I did the initial implementation of clustering support for
>>>>>>>>>>>>>>> Load Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>>>>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Service grouping functionality allows us to add a load
>>>>>>>>>>>>>>> balancer cartridge to an application or group. However we need to provide a
>>>>>>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Currently Docker base image size is around 380 MB and PHP
>>>>>>>>>>>>>>> Docker image size is around 404 MB. Due to a known issue in Kubernetes
>>>>>>>>>>>>>>> v0.5.2 we need to download the Docker images from Docker Hub once. It would
>>>>>>>>>>>>>>> be better if we could reduce the size of the base image so that we could
>>>>>>>>>>>>>>> save time on this process.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> It would be great if anyone would like to contribute to
>>>>>>>>>>>>>>> remaining tasks, we will try our best to complete them ASAP and announce
>>>>>>>>>>>>>>> 4.1.0-Alpha release.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Many Thanks
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> 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/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Rajkumar Rajaratnam
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>> Software Engineer, WSO2
>>>>>>>>>
>>>>>>>>> Mobile : +94777568639
>>>>>>>>> Blog : rajkumarr.com
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Rajkumar Rajaratnam
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>> Software Engineer, WSO2
>>>>>>>
>>>>>>> Mobile : +94777568639
>>>>>>> Blog : rajkumarr.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Rajkumar Rajaratnam
>>>>> Committer & PMC Member, Apache Stratos
>>>>> Software Engineer, WSO2
>>>>>
>>>>> Mobile : +94777568639
>>>>> Blog : rajkumarr.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Rajkumar Rajaratnam
>>>> Committer & PMC Member, Apache Stratos
>>>> Software Engineer, WSO2
>>>>
>>>> Mobile : +94777568639
>>>> Blog : rajkumarr.com
>>>>
>>>
>>>
>>>
>>> --
>>> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Great! Thanks Manula! Please update this thread as you go on.
Thanks
On Fri, Jan 2, 2015 at 10:18 PM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi,
>
> I'll work on verifying service group on EC2.
>
> Thanks !
>
> On Fri, Jan 2, 2015 at 10:12 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Kubernetes workflow is now complete, I'm now working on fixing the git
>> clone issue in agent.
>>
>> Thanks
>>
>> On Fri, Jan 2, 2015 at 9:42 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> Sorry. Lets use the other thread for testing update.
>>>
>>> Thanks.
>>>
>>> On Fri, Jan 2, 2015 at 9:41 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>>> wrote:
>>>
>>>> Getting an exception while deploying the application.
>>>>
>>>> [2015-01-02 21:31:12,401] INFO
>>>> {org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
>>>> replication controller: [replication-controller-id]
>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
>>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
>>>> stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
>>>> [2015-01-02 21:31:12,402] ERROR
>>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>>>> org.apache.axis2.AxisFault: Mapping qname not fond for the package:
>>>> org.apache.stratos.common.beans
>>>> java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping qname
>>>> not fond for the package: org.apache.stratos.common.beans
>>>> at
>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
>>>> at
>>>> org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
>>>> at
>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
>>>> at
>>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
>>>> at org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
>>>> at
>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
>>>> at
>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
>>>> at
>>>> org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
>>>> at
>>>> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
>>>> at
>>>> org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
>>>> at
>>>> org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
>>>> at
>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
>>>> at
>>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
>>>> at
>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
>>>> at
>>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
>>>> at
>>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
>>>> at
>>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>>> at
>>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>>> at
>>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>>> at
>>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>>>> at
>>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>> at
>>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>>> at
>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>>> at
>>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>>> at
>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>>>> at
>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>>> at
>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>>>> at
>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>>> at
>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>>>> at
>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>>>> at
>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>>>> at
>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>>>> at
>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>>> at
>>>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>>>> at
>>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>>>> at
>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>>>> at
>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>>>> at
>>>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>>>> at
>>>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>>>> at
>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>>> at java.lang.Thread.run(Thread.java:662)
>>>> Caused by: org.apache.axis2.AxisFault: Mapping qname not fond for the
>>>> package: org.apache.stratos.common.beans
>>>> at
>>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
>>>> ... 54 more
>>>>
>>>> On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Yes Raj, the modules include the logic and they being invoked from the
>>>>> callers.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <
>>>>> rajkumarr@wso2.com> wrote:
>>>>>
>>>>>> agent.py does not have any artifact management logic. It is there in
>>>>>> artifact management module.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Yes I can remember that it was working in previous milestones,
>>>>>>> however according to the current logic in agent.py, if a git repo url is
>>>>>>> specified it does nothing:
>>>>>>>
>>>>>>> ..
>>>>>>>
>>>>>>> At the end agent just wait in a while loop until terminated.
>>>>>>>
>>>>>>> I can see that agent is listening to Artifact Updated event, did we
>>>>>>> send this event forcefully to make this work?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <
>>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>>
>>>>>>>> It is already implemented and was working fine.
>>>>>>>>
>>>>>>>>
>>>>>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <
>>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> What do you mean?? Its there since M3
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Seems like we have not written logic in agent to checkout
>>>>>>>>>> artifacts from GIT repository.
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> I have now fixed the issue of accessing the service via the host
>>>>>>>>>>> machine (http://kubernetes-master-ip:port/) and pushed changes
>>>>>>>>>>> to master branch.
>>>>>>>>>>>
>>>>>>>>>>> Now I see a problem when a public GIT repo url is given without
>>>>>>>>>>> specifying credentials. I'm currently looking into this.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have now resolved the health statistics publishing issue in
>>>>>>>>>>>> agent:
>>>>>>>>>>>>
>>>>>>>>>>>> - There were several topology event parsers which were not
>>>>>>>>>>>> properly updated with the latest changes. As a result those were raising
>>>>>>>>>>>> errors. I have now fixed them.
>>>>>>>>>>>> - Agent's logic which waits until CEP port is active was not
>>>>>>>>>>>> visible in the logs. As a result it was not possible to see why agent is
>>>>>>>>>>>> not publishing health statistics. I have now enabled logs to show this
>>>>>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>>>>>> - Docker images in docker hub are updated with the latest
>>>>>>>>>>>> changes.
>>>>>>>>>>>>
>>>>>>>>>>>> Now I see a problem where the PHP service is not accessible
>>>>>>>>>>>> from the host machine, however it is accessible within the Kubernetes
>>>>>>>>>>>> master. The removal of host port from the container ports may have affected
>>>>>>>>>>>> this. I'm looking into this now.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I will be testing grouping aspects and scaling scenarios
>>>>>>>>>>>>> related to that.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <
>>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great
>>>>>>>>>>>>>> holiday!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha
>>>>>>>>>>>>>> release. As I can recall following are the remaining tasks we need to
>>>>>>>>>>>>>> complete:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> During past few days I was fixing issues in the Kubernetes
>>>>>>>>>>>>>> workflow and following are the remaining problems:
>>>>>>>>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>>>>>>>>> - Autoscaler obsolete member rule invokes terminateInstance()
>>>>>>>>>>>>>> method twice with the same member id. As a result the second call fails.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'm currently working on fixing the above issues and
>>>>>>>>>>>>>> finalizing the Kubernetes workflow.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I believe we verified the complete service grouping
>>>>>>>>>>>>>> functionality with Mock IaaS however we could not test it with OpenStack
>>>>>>>>>>>>>> and EC2.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I did the initial implementation of clustering support for
>>>>>>>>>>>>>> Load Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>>>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Service grouping functionality allows us to add a load
>>>>>>>>>>>>>> balancer cartridge to an application or group. However we need to provide a
>>>>>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Currently Docker base image size is around 380 MB and PHP
>>>>>>>>>>>>>> Docker image size is around 404 MB. Due to a known issue in Kubernetes
>>>>>>>>>>>>>> v0.5.2 we need to download the Docker images from Docker Hub once. It would
>>>>>>>>>>>>>> be better if we could reduce the size of the base image so that we could
>>>>>>>>>>>>>> save time on this process.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> It would be great if anyone would like to contribute to
>>>>>>>>>>>>>> remaining tasks, we will try our best to complete them ASAP and announce
>>>>>>>>>>>>>> 4.1.0-Alpha release.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Many Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> 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/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Rajkumar Rajaratnam
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>> Software Engineer, WSO2
>>>>>>>>
>>>>>>>> Mobile : +94777568639
>>>>>>>> Blog : rajkumarr.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Rajkumar Rajaratnam
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>> Software Engineer, WSO2
>>>>>>
>>>>>> Mobile : +94777568639
>>>>>> Blog : rajkumarr.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Rajkumar Rajaratnam
>>>> Committer & PMC Member, Apache Stratos
>>>> Software Engineer, WSO2
>>>>
>>>> Mobile : +94777568639
>>>> Blog : rajkumarr.com
>>>>
>>>
>>>
>>>
>>> --
>>> Rajkumar Rajaratnam
>>> Committer & PMC Member, Apache Stratos
>>> Software Engineer, WSO2
>>>
>>> Mobile : +94777568639
>>> Blog : rajkumarr.com
>>>
>>
>>
>>
>> --
>> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi,
I'll work on verifying service group on EC2.
Thanks !
On Fri, Jan 2, 2015 at 10:12 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Kubernetes workflow is now complete, I'm now working on fixing the git
> clone issue in agent.
>
> Thanks
>
> On Fri, Jan 2, 2015 at 9:42 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Sorry. Lets use the other thread for testing update.
>>
>> Thanks.
>>
>> On Fri, Jan 2, 2015 at 9:41 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> Getting an exception while deploying the application.
>>>
>>> [2015-01-02 21:31:12,401] INFO
>>> {org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
>>> replication controller: [replication-controller-id]
>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
>>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
>>> stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
>>> [2015-01-02 21:31:12,402] ERROR
>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>>> org.apache.axis2.AxisFault: Mapping qname not fond for the package:
>>> org.apache.stratos.common.beans
>>> java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping qname
>>> not fond for the package: org.apache.stratos.common.beans
>>> at
>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
>>> at
>>> org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
>>> at
>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
>>> at
>>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
>>> at org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
>>> at
>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
>>> at
>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
>>> at
>>> org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
>>> at
>>> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
>>> at
>>> org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
>>> at
>>> org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
>>> at
>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
>>> at
>>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
>>> at
>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>> at
>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at
>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>> at
>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>>> at
>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>>> at
>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>> at
>>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>> at
>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>>> at
>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>>> at
>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>>> at
>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>>> at
>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>> at
>>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>>> at
>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>>> at
>>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>>> at
>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>>> at
>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>>> at
>>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>>> at
>>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>>> at
>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>> at java.lang.Thread.run(Thread.java:662)
>>> Caused by: org.apache.axis2.AxisFault: Mapping qname not fond for the
>>> package: org.apache.stratos.common.beans
>>> at
>>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
>>> ... 54 more
>>>
>>> On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Yes Raj, the modules include the logic and they being invoked from the
>>>> callers.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>>> > wrote:
>>>>
>>>>> agent.py does not have any artifact management logic. It is there in
>>>>> artifact management module.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Yes I can remember that it was working in previous milestones,
>>>>>> however according to the current logic in agent.py, if a git repo url is
>>>>>> specified it does nothing:
>>>>>>
>>>>>> ..
>>>>>>
>>>>>> At the end agent just wait in a while loop until terminated.
>>>>>>
>>>>>> I can see that agent is listening to Artifact Updated event, did we
>>>>>> send this event forcefully to make this work?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <
>>>>>> rajkumarr@wso2.com> wrote:
>>>>>>
>>>>>>> It is already implemented and was working fine.
>>>>>>>
>>>>>>>
>>>>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <
>>>>>>> lakmal@wso2.com> wrote:
>>>>>>>
>>>>>>>> What do you mean?? Its there since M3
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Seems like we have not written logic in agent to checkout
>>>>>>>>> artifacts from GIT repository.
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I have now fixed the issue of accessing the service via the host
>>>>>>>>>> machine (http://kubernetes-master-ip:port/) and pushed changes
>>>>>>>>>> to master branch.
>>>>>>>>>>
>>>>>>>>>> Now I see a problem when a public GIT repo url is given without
>>>>>>>>>> specifying credentials. I'm currently looking into this.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> I have now resolved the health statistics publishing issue in
>>>>>>>>>>> agent:
>>>>>>>>>>>
>>>>>>>>>>> - There were several topology event parsers which were not
>>>>>>>>>>> properly updated with the latest changes. As a result those were raising
>>>>>>>>>>> errors. I have now fixed them.
>>>>>>>>>>> - Agent's logic which waits until CEP port is active was not
>>>>>>>>>>> visible in the logs. As a result it was not possible to see why agent is
>>>>>>>>>>> not publishing health statistics. I have now enabled logs to show this
>>>>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>>>>> - Docker images in docker hub are updated with the latest
>>>>>>>>>>> changes.
>>>>>>>>>>>
>>>>>>>>>>> Now I see a problem where the PHP service is not accessible from
>>>>>>>>>>> the host machine, however it is accessible within the Kubernetes master.
>>>>>>>>>>> The removal of host port from the container ports may have affected this.
>>>>>>>>>>> I'm looking into this now.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I will be testing grouping aspects and scaling scenarios
>>>>>>>>>>>> related to that.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <
>>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great
>>>>>>>>>>>>> holiday!
>>>>>>>>>>>>>
>>>>>>>>>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha
>>>>>>>>>>>>> release. As I can recall following are the remaining tasks we need to
>>>>>>>>>>>>> complete:
>>>>>>>>>>>>>
>>>>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>>>>
>>>>>>>>>>>>> During past few days I was fixing issues in the Kubernetes
>>>>>>>>>>>>> workflow and following are the remaining problems:
>>>>>>>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>>>>>>>> - Autoscaler obsolete member rule invokes terminateInstance()
>>>>>>>>>>>>> method twice with the same member id. As a result the second call fails.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'm currently working on fixing the above issues and
>>>>>>>>>>>>> finalizing the Kubernetes workflow.
>>>>>>>>>>>>>
>>>>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>>>>
>>>>>>>>>>>>> I believe we verified the complete service grouping
>>>>>>>>>>>>> functionality with Mock IaaS however we could not test it with OpenStack
>>>>>>>>>>>>> and EC2.
>>>>>>>>>>>>>
>>>>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>>>>
>>>>>>>>>>>>> I did the initial implementation of clustering support for
>>>>>>>>>>>>> Load Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>>>>>>>
>>>>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>>>>
>>>>>>>>>>>>> Service grouping functionality allows us to add a load
>>>>>>>>>>>>> balancer cartridge to an application or group. However we need to provide a
>>>>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>>>>
>>>>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>>>>
>>>>>>>>>>>>> Currently Docker base image size is around 380 MB and PHP
>>>>>>>>>>>>> Docker image size is around 404 MB. Due to a known issue in Kubernetes
>>>>>>>>>>>>> v0.5.2 we need to download the Docker images from Docker Hub once. It would
>>>>>>>>>>>>> be better if we could reduce the size of the base image so that we could
>>>>>>>>>>>>> save time on this process.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> It would be great if anyone would like to contribute to
>>>>>>>>>>>>> remaining tasks, we will try our best to complete them ASAP and announce
>>>>>>>>>>>>> 4.1.0-Alpha release.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Many Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> 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/
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Rajkumar Rajaratnam
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>> Software Engineer, WSO2
>>>>>>>
>>>>>>> Mobile : +94777568639
>>>>>>> Blog : rajkumarr.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Rajkumar Rajaratnam
>>>>> Committer & PMC Member, Apache Stratos
>>>>> Software Engineer, WSO2
>>>>>
>>>>> Mobile : +94777568639
>>>>> Blog : rajkumarr.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Rajkumar Rajaratnam
>>> Committer & PMC Member, Apache Stratos
>>> Software Engineer, WSO2
>>>
>>> Mobile : +94777568639
>>> Blog : rajkumarr.com
>>>
>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Kubernetes workflow is now complete, I'm now working on fixing the git
clone issue in agent.
Thanks
On Fri, Jan 2, 2015 at 9:42 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Sorry. Lets use the other thread for testing update.
>
> Thanks.
>
> On Fri, Jan 2, 2015 at 9:41 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> Getting an exception while deploying the application.
>>
>> [2015-01-02 21:31:12,401] INFO
>> {org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
>> replication controller: [replication-controller-id]
>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
>> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
>> stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
>> [2015-01-02 21:31:12,402] ERROR
>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>> org.apache.axis2.AxisFault: Mapping qname not fond for the package:
>> org.apache.stratos.common.beans
>> java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping qname not
>> fond for the package: org.apache.stratos.common.beans
>> at
>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
>> at
>> org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
>> at
>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
>> at
>> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
>> at org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
>> at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
>> at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
>> at
>> org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
>> at
>> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
>> at
>> org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
>> at
>> org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
>> at
>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
>> at
>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
>> at
>> org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
>> at
>> org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
>> at
>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
>> at
>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>> at
>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>> at
>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>> at
>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>> at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>> at
>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>> at
>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>> at
>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>> at
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>> at
>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>> at
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>> at
>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>> at java.lang.Thread.run(Thread.java:662)
>> Caused by: org.apache.axis2.AxisFault: Mapping qname not fond for the
>> package: org.apache.stratos.common.beans
>> at
>> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
>> ... 54 more
>>
>> On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Yes Raj, the modules include the logic and they being invoked from the
>>> callers.
>>>
>>> Thanks
>>>
>>> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>>> wrote:
>>>
>>>> agent.py does not have any artifact management logic. It is there in
>>>> artifact management module.
>>>>
>>>> Thanks.
>>>>
>>>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Yes I can remember that it was working in previous milestones, however
>>>>> according to the current logic in agent.py, if a git repo url is specified
>>>>> it does nothing:
>>>>>
>>>>> ..
>>>>>
>>>>> At the end agent just wait in a while loop until terminated.
>>>>>
>>>>> I can see that agent is listening to Artifact Updated event, did we
>>>>> send this event forcefully to make this work?
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <
>>>>> rajkumarr@wso2.com> wrote:
>>>>>
>>>>>> It is already implemented and was working fine.
>>>>>>
>>>>>>
>>>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <lakmal@wso2.com
>>>>>> > wrote:
>>>>>>
>>>>>>> What do you mean?? Its there since M3
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Seems like we have not written logic in agent to checkout artifacts
>>>>>>>> from GIT repository.
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I have now fixed the issue of accessing the service via the host
>>>>>>>>> machine (http://kubernetes-master-ip:port/) and pushed changes to
>>>>>>>>> master branch.
>>>>>>>>>
>>>>>>>>> Now I see a problem when a public GIT repo url is given without
>>>>>>>>> specifying credentials. I'm currently looking into this.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I have now resolved the health statistics publishing issue in
>>>>>>>>>> agent:
>>>>>>>>>>
>>>>>>>>>> - There were several topology event parsers which were not
>>>>>>>>>> properly updated with the latest changes. As a result those were raising
>>>>>>>>>> errors. I have now fixed them.
>>>>>>>>>> - Agent's logic which waits until CEP port is active was not
>>>>>>>>>> visible in the logs. As a result it was not possible to see why agent is
>>>>>>>>>> not publishing health statistics. I have now enabled logs to show this
>>>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>>>> - Docker images in docker hub are updated with the latest changes.
>>>>>>>>>>
>>>>>>>>>> Now I see a problem where the PHP service is not accessible from
>>>>>>>>>> the host machine, however it is accessible within the Kubernetes master.
>>>>>>>>>> The removal of host port from the container ports may have affected this.
>>>>>>>>>> I'm looking into this now.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I will be testing grouping aspects and scaling scenarios related
>>>>>>>>>>> to that.
>>>>>>>>>>>
>>>>>>>>>>> Thanks.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>
>>>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great
>>>>>>>>>>>> holiday!
>>>>>>>>>>>>
>>>>>>>>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha
>>>>>>>>>>>> release. As I can recall following are the remaining tasks we need to
>>>>>>>>>>>> complete:
>>>>>>>>>>>>
>>>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>>>
>>>>>>>>>>>> During past few days I was fixing issues in the Kubernetes
>>>>>>>>>>>> workflow and following are the remaining problems:
>>>>>>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>>>>>>> - Autoscaler obsolete member rule invokes terminateInstance()
>>>>>>>>>>>> method twice with the same member id. As a result the second call fails.
>>>>>>>>>>>>
>>>>>>>>>>>> I'm currently working on fixing the above issues and finalizing
>>>>>>>>>>>> the Kubernetes workflow.
>>>>>>>>>>>>
>>>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>>>
>>>>>>>>>>>> I believe we verified the complete service grouping
>>>>>>>>>>>> functionality with Mock IaaS however we could not test it with OpenStack
>>>>>>>>>>>> and EC2.
>>>>>>>>>>>>
>>>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>>>
>>>>>>>>>>>> I did the initial implementation of clustering support for Load
>>>>>>>>>>>> Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>>>>>>
>>>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>>>
>>>>>>>>>>>> Service grouping functionality allows us to add a load balancer
>>>>>>>>>>>> cartridge to an application or group. However we need to provide a
>>>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>>>
>>>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>>>
>>>>>>>>>>>> Currently Docker base image size is around 380 MB and PHP
>>>>>>>>>>>> Docker image size is around 404 MB. Due to a known issue in Kubernetes
>>>>>>>>>>>> v0.5.2 we need to download the Docker images from Docker Hub once. It would
>>>>>>>>>>>> be better if we could reduce the size of the base image so that we could
>>>>>>>>>>>> save time on this process.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> It would be great if anyone would like to contribute to
>>>>>>>>>>>> remaining tasks, we will try our best to complete them ASAP and announce
>>>>>>>>>>>> 4.1.0-Alpha release.
>>>>>>>>>>>>
>>>>>>>>>>>> Many Thanks
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> 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
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 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/
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Rajkumar Rajaratnam
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>> Software Engineer, WSO2
>>>>>>
>>>>>> Mobile : +94777568639
>>>>>> Blog : rajkumarr.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Rajkumar Rajaratnam
>>>> Committer & PMC Member, Apache Stratos
>>>> Software Engineer, WSO2
>>>>
>>>> Mobile : +94777568639
>>>> Blog : rajkumarr.com
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Software Engineer, WSO2
>
> Mobile : +94777568639
> Blog : rajkumarr.com
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Sorry. Lets use the other thread for testing update.
Thanks.
On Fri, Jan 2, 2015 at 9:41 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> Getting an exception while deploying the application.
>
> [2015-01-02 21:31:12,401] INFO
> {org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
> replication controller: [replication-controller-id]
> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
> php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
> stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
> [2015-01-02 21:31:12,402] ERROR
> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
> org.apache.axis2.AxisFault: Mapping qname not fond for the package:
> org.apache.stratos.common.beans
> java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping qname not
> fond for the package: org.apache.stratos.common.beans
> at
> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
> at
> org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
> at
> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
> at
> org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
> at org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
> at
> org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
> at
> org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
> at
> org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
> at
> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
> at
> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
> at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
> at
> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
> at
> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.axis2.AxisFault: Mapping qname not fond for the
> package: org.apache.stratos.common.beans
> at
> org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
> ... 54 more
>
> On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Yes Raj, the modules include the logic and they being invoked from the
>> callers.
>>
>> Thanks
>>
>> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> agent.py does not have any artifact management logic. It is there in
>>> artifact management module.
>>>
>>> Thanks.
>>>
>>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Yes I can remember that it was working in previous milestones, however
>>>> according to the current logic in agent.py, if a git repo url is specified
>>>> it does nothing:
>>>>
>>>> ..
>>>>
>>>> At the end agent just wait in a while loop until terminated.
>>>>
>>>> I can see that agent is listening to Artifact Updated event, did we
>>>> send this event forcefully to make this work?
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com
>>>> > wrote:
>>>>
>>>>> It is already implemented and was working fine.
>>>>>
>>>>>
>>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <la...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> What do you mean?? Its there since M3
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Seems like we have not written logic in agent to checkout artifacts
>>>>>>> from GIT repository.
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I have now fixed the issue of accessing the service via the host
>>>>>>>> machine (http://kubernetes-master-ip:port/) and pushed changes to
>>>>>>>> master branch.
>>>>>>>>
>>>>>>>> Now I see a problem when a public GIT repo url is given without
>>>>>>>> specifying credentials. I'm currently looking into this.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I have now resolved the health statistics publishing issue in
>>>>>>>>> agent:
>>>>>>>>>
>>>>>>>>> - There were several topology event parsers which were not
>>>>>>>>> properly updated with the latest changes. As a result those were raising
>>>>>>>>> errors. I have now fixed them.
>>>>>>>>> - Agent's logic which waits until CEP port is active was not
>>>>>>>>> visible in the logs. As a result it was not possible to see why agent is
>>>>>>>>> not publishing health statistics. I have now enabled logs to show this
>>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>>> - Docker images in docker hub are updated with the latest changes.
>>>>>>>>>
>>>>>>>>> Now I see a problem where the PHP service is not accessible from
>>>>>>>>> the host machine, however it is accessible within the Kubernetes master.
>>>>>>>>> The removal of host port from the container ports may have affected this.
>>>>>>>>> I'm looking into this now.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I will be testing grouping aspects and scaling scenarios related
>>>>>>>>>> to that.
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <
>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>
>>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>>>>>>>>>
>>>>>>>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha
>>>>>>>>>>> release. As I can recall following are the remaining tasks we need to
>>>>>>>>>>> complete:
>>>>>>>>>>>
>>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>>
>>>>>>>>>>> During past few days I was fixing issues in the Kubernetes
>>>>>>>>>>> workflow and following are the remaining problems:
>>>>>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>>>>>> - Autoscaler obsolete member rule invokes terminateInstance()
>>>>>>>>>>> method twice with the same member id. As a result the second call fails.
>>>>>>>>>>>
>>>>>>>>>>> I'm currently working on fixing the above issues and finalizing
>>>>>>>>>>> the Kubernetes workflow.
>>>>>>>>>>>
>>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>>
>>>>>>>>>>> I believe we verified the complete service grouping
>>>>>>>>>>> functionality with Mock IaaS however we could not test it with OpenStack
>>>>>>>>>>> and EC2.
>>>>>>>>>>>
>>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>>
>>>>>>>>>>> I did the initial implementation of clustering support for Load
>>>>>>>>>>> Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>>>>>
>>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>>
>>>>>>>>>>> Service grouping functionality allows us to add a load balancer
>>>>>>>>>>> cartridge to an application or group. However we need to provide a
>>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>>
>>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>>
>>>>>>>>>>> Currently Docker base image size is around 380 MB and PHP Docker
>>>>>>>>>>> image size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we
>>>>>>>>>>> need to download the Docker images from Docker Hub once. It would be better
>>>>>>>>>>> if we could reduce the size of the base image so that we could save time on
>>>>>>>>>>> this process.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> It would be great if anyone would like to contribute to
>>>>>>>>>>> remaining tasks, we will try our best to complete them ASAP and announce
>>>>>>>>>>> 4.1.0-Alpha release.
>>>>>>>>>>>
>>>>>>>>>>> Many Thanks
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 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/
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Rajkumar Rajaratnam
>>>>> Committer & PMC Member, Apache Stratos
>>>>> Software Engineer, WSO2
>>>>>
>>>>> Mobile : +94777568639
>>>>> Blog : rajkumarr.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Rajkumar Rajaratnam
>>> Committer & PMC Member, Apache Stratos
>>> Software Engineer, WSO2
>>>
>>> Mobile : +94777568639
>>> Blog : rajkumarr.com
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Software Engineer, WSO2
>
> Mobile : +94777568639
> Blog : rajkumarr.com
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
Getting an exception while deploying the application.
[2015-01-02 21:31:12,401] INFO
{org.apache.stratos.kubernetes.client.KubernetesApiClient} - Creating
replication controller: [replication-controller-id]
php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [name]
php-php-domain0c539d53-c9b9-425a-a97c-b719187ed8c8 [docker-image]
stratos/php:4.1.0-alpha [container-ports] [80] [replicas] 1
[2015-01-02 21:31:12,402] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
org.apache.axis2.AxisFault: Mapping qname not fond for the package:
org.apache.stratos.common.beans
java.lang.RuntimeException: org.apache.axis2.AxisFault: Mapping qname not
fond for the package: org.apache.stratos.common.beans
at
org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:276)
at
org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:72)
at
org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:994)
at
org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:850)
at org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:71)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
at
org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
at
org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
at
org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
at
org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:105)
at
org.apache.axis2.rpc.receivers.RPCUtil.processResponseAsDocLitWrapped(RPCUtil.java:456)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:153)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.axis2.AxisFault: Mapping qname not fond for the
package: org.apache.stratos.common.beans
at
org.apache.axis2.databinding.utils.BeanUtil.getPropertyQnameList(BeanUtil.java:143)
... 54 more
On Fri, Jan 2, 2015 at 8:47 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Yes Raj, the modules include the logic and they being invoked from the
> callers.
>
> Thanks
>
> On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> agent.py does not have any artifact management logic. It is there in
>> artifact management module.
>>
>> Thanks.
>>
>> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Yes I can remember that it was working in previous milestones, however
>>> according to the current logic in agent.py, if a git repo url is specified
>>> it does nothing:
>>>
>>> ..
>>>
>>> At the end agent just wait in a while loop until terminated.
>>>
>>> I can see that agent is listening to Artifact Updated event, did we send
>>> this event forcefully to make this work?
>>>
>>> Thanks
>>>
>>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>>> wrote:
>>>
>>>> It is already implemented and was working fine.
>>>>
>>>>
>>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>>
>>>> Thanks.
>>>>
>>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <la...@wso2.com>
>>>> wrote:
>>>>
>>>>> What do you mean?? Its there since M3
>>>>>
>>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Seems like we have not written logic in agent to checkout artifacts
>>>>>> from GIT repository.
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I have now fixed the issue of accessing the service via the host
>>>>>>> machine (http://kubernetes-master-ip:port/) and pushed changes to
>>>>>>> master branch.
>>>>>>>
>>>>>>> Now I see a problem when a public GIT repo url is given without
>>>>>>> specifying credentials. I'm currently looking into this.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I have now resolved the health statistics publishing issue in agent:
>>>>>>>>
>>>>>>>> - There were several topology event parsers which were not properly
>>>>>>>> updated with the latest changes. As a result those were raising errors. I
>>>>>>>> have now fixed them.
>>>>>>>> - Agent's logic which waits until CEP port is active was not
>>>>>>>> visible in the logs. As a result it was not possible to see why agent is
>>>>>>>> not publishing health statistics. I have now enabled logs to show this
>>>>>>>> process so that if agent could not connect to CEP it would be visible.
>>>>>>>> - Docker images in docker hub are updated with the latest changes.
>>>>>>>>
>>>>>>>> Now I see a problem where the PHP service is not accessible from
>>>>>>>> the host machine, however it is accessible within the Kubernetes master.
>>>>>>>> The removal of host port from the container ports may have affected this.
>>>>>>>> I'm looking into this now.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <
>>>>>>>> lahirus@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I will be testing grouping aspects and scaling scenarios related
>>>>>>>>> to that.
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> Hi Devs,
>>>>>>>>>>
>>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>>>>>>>>
>>>>>>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha
>>>>>>>>>> release. As I can recall following are the remaining tasks we need to
>>>>>>>>>> complete:
>>>>>>>>>>
>>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>>
>>>>>>>>>> During past few days I was fixing issues in the Kubernetes
>>>>>>>>>> workflow and following are the remaining problems:
>>>>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>>>>> - Autoscaler obsolete member rule invokes terminateInstance()
>>>>>>>>>> method twice with the same member id. As a result the second call fails.
>>>>>>>>>>
>>>>>>>>>> I'm currently working on fixing the above issues and finalizing
>>>>>>>>>> the Kubernetes workflow.
>>>>>>>>>>
>>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>>
>>>>>>>>>> I believe we verified the complete service grouping functionality
>>>>>>>>>> with Mock IaaS however we could not test it with OpenStack and EC2.
>>>>>>>>>>
>>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>>
>>>>>>>>>> I did the initial implementation of clustering support for Load
>>>>>>>>>> Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>>>>
>>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>>
>>>>>>>>>> Service grouping functionality allows us to add a load balancer
>>>>>>>>>> cartridge to an application or group. However we need to provide a
>>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>>> load balancer cartridge.
>>>>>>>>>>
>>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>>
>>>>>>>>>> Currently Docker base image size is around 380 MB and PHP Docker
>>>>>>>>>> image size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we
>>>>>>>>>> need to download the Docker images from Docker Hub once. It would be better
>>>>>>>>>> if we could reduce the size of the base image so that we could save time on
>>>>>>>>>> this process.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> It would be great if anyone would like to contribute to remaining
>>>>>>>>>> tasks, we will try our best to complete them ASAP and announce 4.1.0-Alpha
>>>>>>>>>> release.
>>>>>>>>>>
>>>>>>>>>> Many Thanks
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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/
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Rajkumar Rajaratnam
>>>> Committer & PMC Member, Apache Stratos
>>>> Software Engineer, WSO2
>>>>
>>>> Mobile : +94777568639
>>>> Blog : rajkumarr.com
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Yes Raj, the modules include the logic and they being invoked from the
callers.
Thanks
On Fri, Jan 2, 2015 at 8:36 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> agent.py does not have any artifact management logic. It is there in
> artifact management module.
>
> Thanks.
>
> On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Yes I can remember that it was working in previous milestones, however
>> according to the current logic in agent.py, if a git repo url is specified
>> it does nothing:
>>
>> ..
>>
>> At the end agent just wait in a while loop until terminated.
>>
>> I can see that agent is listening to Artifact Updated event, did we send
>> this event forcefully to make this work?
>>
>> Thanks
>>
>> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <ra...@wso2.com>
>> wrote:
>>
>>> It is already implemented and was working fine.
>>>
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>>
>>> Thanks.
>>>
>>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <la...@wso2.com>
>>> wrote:
>>>
>>>> What do you mean?? Its there since M3
>>>>
>>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Seems like we have not written logic in agent to checkout artifacts
>>>>> from GIT repository.
>>>>>
>>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I have now fixed the issue of accessing the service via the host
>>>>>> machine (http://kubernetes-master-ip:port/) and pushed changes to
>>>>>> master branch.
>>>>>>
>>>>>> Now I see a problem when a public GIT repo url is given without
>>>>>> specifying credentials. I'm currently looking into this.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I have now resolved the health statistics publishing issue in agent:
>>>>>>>
>>>>>>> - There were several topology event parsers which were not properly
>>>>>>> updated with the latest changes. As a result those were raising errors. I
>>>>>>> have now fixed them.
>>>>>>> - Agent's logic which waits until CEP port is active was not visible
>>>>>>> in the logs. As a result it was not possible to see why agent is not
>>>>>>> publishing health statistics. I have now enabled logs to show this process
>>>>>>> so that if agent could not connect to CEP it would be visible.
>>>>>>> - Docker images in docker hub are updated with the latest changes.
>>>>>>>
>>>>>>> Now I see a problem where the PHP service is not accessible from the
>>>>>>> host machine, however it is accessible within the Kubernetes master. The
>>>>>>> removal of host port from the container ports may have affected this. I'm
>>>>>>> looking into this now.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <lahirus@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I will be testing grouping aspects and scaling scenarios related to
>>>>>>>> that.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Devs,
>>>>>>>>>
>>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>>>>>>>
>>>>>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha
>>>>>>>>> release. As I can recall following are the remaining tasks we need to
>>>>>>>>> complete:
>>>>>>>>>
>>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>>
>>>>>>>>> During past few days I was fixing issues in the Kubernetes
>>>>>>>>> workflow and following are the remaining problems:
>>>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>>>> - Autoscaler obsolete member rule invokes terminateInstance()
>>>>>>>>> method twice with the same member id. As a result the second call fails.
>>>>>>>>>
>>>>>>>>> I'm currently working on fixing the above issues and finalizing
>>>>>>>>> the Kubernetes workflow.
>>>>>>>>>
>>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>>
>>>>>>>>> I believe we verified the complete service grouping functionality
>>>>>>>>> with Mock IaaS however we could not test it with OpenStack and EC2.
>>>>>>>>>
>>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>>
>>>>>>>>> I did the initial implementation of clustering support for Load
>>>>>>>>> Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>>>
>>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>>
>>>>>>>>> Service grouping functionality allows us to add a load balancer
>>>>>>>>> cartridge to an application or group. However we need to provide a
>>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>>> load balancer cartridge.
>>>>>>>>>
>>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>>
>>>>>>>>> Currently Docker base image size is around 380 MB and PHP Docker
>>>>>>>>> image size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we
>>>>>>>>> need to download the Docker images from Docker Hub once. It would be better
>>>>>>>>> if we could reduce the size of the base image so that we could save time on
>>>>>>>>> this process.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> It would be great if anyone would like to contribute to remaining
>>>>>>>>> tasks, we will try our best to complete them ASAP and announce 4.1.0-Alpha
>>>>>>>>> release.
>>>>>>>>>
>>>>>>>>> Many Thanks
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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/
>>>>
>>>>
>>>
>>>
>>> --
>>> Rajkumar Rajaratnam
>>> Committer & PMC Member, Apache Stratos
>>> Software Engineer, WSO2
>>>
>>> Mobile : +94777568639
>>> Blog : rajkumarr.com
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Software Engineer, WSO2
>
> Mobile : +94777568639
> Blog : rajkumarr.com
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
agent.py does not have any artifact management logic. It is there in
artifact management module.
Thanks.
On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Yes I can remember that it was working in previous milestones, however
> according to the current logic in agent.py, if a git repo url is specified
> it does nothing:
>
> ..
>
> At the end agent just wait in a while loop until terminated.
>
> I can see that agent is listening to Artifact Updated event, did we send
> this event forcefully to make this work?
>
> Thanks
>
> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> It is already implemented and was working fine.
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>
>> Thanks.
>>
>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <la...@wso2.com>
>> wrote:
>>
>>> What do you mean?? Its there since M3
>>>
>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Seems like we have not written logic in agent to checkout artifacts
>>>> from GIT repository.
>>>>
>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I have now fixed the issue of accessing the service via the host
>>>>> machine (http://kubernetes-master-ip:port/) and pushed changes to
>>>>> master branch.
>>>>>
>>>>> Now I see a problem when a public GIT repo url is given without
>>>>> specifying credentials. I'm currently looking into this.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I have now resolved the health statistics publishing issue in agent:
>>>>>>
>>>>>> - There were several topology event parsers which were not properly
>>>>>> updated with the latest changes. As a result those were raising errors. I
>>>>>> have now fixed them.
>>>>>> - Agent's logic which waits until CEP port is active was not visible
>>>>>> in the logs. As a result it was not possible to see why agent is not
>>>>>> publishing health statistics. I have now enabled logs to show this process
>>>>>> so that if agent could not connect to CEP it would be visible.
>>>>>> - Docker images in docker hub are updated with the latest changes.
>>>>>>
>>>>>> Now I see a problem where the PHP service is not accessible from the
>>>>>> host machine, however it is accessible within the Kubernetes master. The
>>>>>> removal of host port from the container ports may have affected this. I'm
>>>>>> looking into this now.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <la...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I will be testing grouping aspects and scaling scenarios related to
>>>>>>> that.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Devs,
>>>>>>>>
>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>>>>>>
>>>>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha
>>>>>>>> release. As I can recall following are the remaining tasks we need to
>>>>>>>> complete:
>>>>>>>>
>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>
>>>>>>>> During past few days I was fixing issues in the Kubernetes workflow
>>>>>>>> and following are the remaining problems:
>>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>>> - Autoscaler obsolete member rule invokes terminateInstance()
>>>>>>>> method twice with the same member id. As a result the second call fails.
>>>>>>>>
>>>>>>>> I'm currently working on fixing the above issues and finalizing the
>>>>>>>> Kubernetes workflow.
>>>>>>>>
>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>
>>>>>>>> I believe we verified the complete service grouping functionality
>>>>>>>> with Mock IaaS however we could not test it with OpenStack and EC2.
>>>>>>>>
>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>
>>>>>>>> I did the initial implementation of clustering support for Load
>>>>>>>> Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>>
>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>
>>>>>>>> Service grouping functionality allows us to add a load balancer
>>>>>>>> cartridge to an application or group. However we need to provide a
>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>> load balancer cartridge.
>>>>>>>>
>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>
>>>>>>>> Currently Docker base image size is around 380 MB and PHP Docker
>>>>>>>> image size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we
>>>>>>>> need to download the Docker images from Docker Hub once. It would be better
>>>>>>>> if we could reduce the size of the base image so that we could save time on
>>>>>>>> this process.
>>>>>>>>
>>>>>>>>
>>>>>>>> It would be great if anyone would like to contribute to remaining
>>>>>>>> tasks, we will try our best to complete them ASAP and announce 4.1.0-Alpha
>>>>>>>> release.
>>>>>>>>
>>>>>>>> Many Thanks
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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/
>>>
>>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Yes seems like we have forcefully sent the Artifact Updated event from
Stratos Manager by listening to Instance Started event. Was there any
reason take this approach?
https://github.com/apache/stratos/blob/master/components/org.apache.stratos.manager/src/main/java/org/apache/stratos/manager/listener/InstanceStatusListener.java
On Fri, Jan 2, 2015 at 7:48 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Yes I can remember that it was working in previous milestones, however
> according to the current logic in agent.py, if a git repo url is specified
> it does nothing:
>
> ..
>
> At the end agent just wait in a while loop until terminated.
>
> I can see that agent is listening to Artifact Updated event, did we send
> this event forcefully to make this work?
>
> Thanks
>
> On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <ra...@wso2.com>
> wrote:
>
>> It is already implemented and was working fine.
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>>
>> Thanks.
>>
>> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <la...@wso2.com>
>> wrote:
>>
>>> What do you mean?? Its there since M3
>>>
>>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Seems like we have not written logic in agent to checkout artifacts
>>>> from GIT repository.
>>>>
>>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I have now fixed the issue of accessing the service via the host
>>>>> machine (http://kubernetes-master-ip:port/) and pushed changes to
>>>>> master branch.
>>>>>
>>>>> Now I see a problem when a public GIT repo url is given without
>>>>> specifying credentials. I'm currently looking into this.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I have now resolved the health statistics publishing issue in agent:
>>>>>>
>>>>>> - There were several topology event parsers which were not properly
>>>>>> updated with the latest changes. As a result those were raising errors. I
>>>>>> have now fixed them.
>>>>>> - Agent's logic which waits until CEP port is active was not visible
>>>>>> in the logs. As a result it was not possible to see why agent is not
>>>>>> publishing health statistics. I have now enabled logs to show this process
>>>>>> so that if agent could not connect to CEP it would be visible.
>>>>>> - Docker images in docker hub are updated with the latest changes.
>>>>>>
>>>>>> Now I see a problem where the PHP service is not accessible from the
>>>>>> host machine, however it is accessible within the Kubernetes master. The
>>>>>> removal of host port from the container ports may have affected this. I'm
>>>>>> looking into this now.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <la...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I will be testing grouping aspects and scaling scenarios related to
>>>>>>> that.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Devs,
>>>>>>>>
>>>>>>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>>>>>>
>>>>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha
>>>>>>>> release. As I can recall following are the remaining tasks we need to
>>>>>>>> complete:
>>>>>>>>
>>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>>
>>>>>>>> During past few days I was fixing issues in the Kubernetes workflow
>>>>>>>> and following are the remaining problems:
>>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>>> - Autoscaler obsolete member rule invokes terminateInstance()
>>>>>>>> method twice with the same member id. As a result the second call fails.
>>>>>>>>
>>>>>>>> I'm currently working on fixing the above issues and finalizing the
>>>>>>>> Kubernetes workflow.
>>>>>>>>
>>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>>
>>>>>>>> I believe we verified the complete service grouping functionality
>>>>>>>> with Mock IaaS however we could not test it with OpenStack and EC2.
>>>>>>>>
>>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>>
>>>>>>>> I did the initial implementation of clustering support for Load
>>>>>>>> Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>>
>>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>>
>>>>>>>> Service grouping functionality allows us to add a load balancer
>>>>>>>> cartridge to an application or group. However we need to provide a
>>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>>> load balancer cartridge.
>>>>>>>>
>>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>>
>>>>>>>> Currently Docker base image size is around 380 MB and PHP Docker
>>>>>>>> image size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we
>>>>>>>> need to download the Docker images from Docker Hub once. It would be better
>>>>>>>> if we could reduce the size of the base image so that we could save time on
>>>>>>>> this process.
>>>>>>>>
>>>>>>>>
>>>>>>>> It would be great if anyone would like to contribute to remaining
>>>>>>>> tasks, we will try our best to complete them ASAP and announce 4.1.0-Alpha
>>>>>>>> release.
>>>>>>>>
>>>>>>>> Many Thanks
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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/
>>>
>>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Yes I can remember that it was working in previous milestones, however
according to the current logic in agent.py, if a git repo url is specified
it does nothing:
..
At the end agent just wait in a while loop until terminated.
I can see that agent is listening to Artifact Updated event, did we send
this event forcefully to make this work?
Thanks
On Fri, Jan 2, 2015 at 7:11 PM, Rajkumar Rajaratnam <ra...@wso2.com>
wrote:
> It is already implemented and was working fine.
>
>
> https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
>
> Thanks.
>
> On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <la...@wso2.com>
> wrote:
>
>> What do you mean?? Its there since M3
>>
>> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> Seems like we have not written logic in agent to checkout artifacts from
>>> GIT repository.
>>>
>>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I have now fixed the issue of accessing the service via the host
>>>> machine (http://kubernetes-master-ip:port/) and pushed changes to
>>>> master branch.
>>>>
>>>> Now I see a problem when a public GIT repo url is given without
>>>> specifying credentials. I'm currently looking into this.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I have now resolved the health statistics publishing issue in agent:
>>>>>
>>>>> - There were several topology event parsers which were not properly
>>>>> updated with the latest changes. As a result those were raising errors. I
>>>>> have now fixed them.
>>>>> - Agent's logic which waits until CEP port is active was not visible
>>>>> in the logs. As a result it was not possible to see why agent is not
>>>>> publishing health statistics. I have now enabled logs to show this process
>>>>> so that if agent could not connect to CEP it would be visible.
>>>>> - Docker images in docker hub are updated with the latest changes.
>>>>>
>>>>> Now I see a problem where the PHP service is not accessible from the
>>>>> host machine, however it is accessible within the Kubernetes master. The
>>>>> removal of host port from the container ports may have affected this. I'm
>>>>> looking into this now.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <la...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I will be testing grouping aspects and scaling scenarios related to
>>>>>> that.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Devs,
>>>>>>>
>>>>>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>>>>>
>>>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha
>>>>>>> release. As I can recall following are the remaining tasks we need to
>>>>>>> complete:
>>>>>>>
>>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>>
>>>>>>> During past few days I was fixing issues in the Kubernetes workflow
>>>>>>> and following are the remaining problems:
>>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>>> - Autoscaler obsolete member rule invokes terminateInstance() method
>>>>>>> twice with the same member id. As a result the second call fails.
>>>>>>>
>>>>>>> I'm currently working on fixing the above issues and finalizing the
>>>>>>> Kubernetes workflow.
>>>>>>>
>>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>>
>>>>>>> I believe we verified the complete service grouping functionality
>>>>>>> with Mock IaaS however we could not test it with OpenStack and EC2.
>>>>>>>
>>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>>
>>>>>>> I did the initial implementation of clustering support for Load
>>>>>>> Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>>> Autoscaler and Stratos Manager.
>>>>>>>
>>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>>
>>>>>>> Service grouping functionality allows us to add a load balancer
>>>>>>> cartridge to an application or group. However we need to provide a
>>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>>> load balancer cartridge.
>>>>>>>
>>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>>
>>>>>>> Currently Docker base image size is around 380 MB and PHP Docker
>>>>>>> image size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we
>>>>>>> need to download the Docker images from Docker Hub once. It would be better
>>>>>>> if we could reduce the size of the base image so that we could save time on
>>>>>>> this process.
>>>>>>>
>>>>>>>
>>>>>>> It would be great if anyone would like to contribute to remaining
>>>>>>> tasks, we will try our best to complete them ASAP and announce 4.1.0-Alpha
>>>>>>> release.
>>>>>>>
>>>>>>> Many Thanks
>>>>>>>
>>>>>>> --
>>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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/
>>
>>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Software Engineer, WSO2
>
> Mobile : +94777568639
> Blog : rajkumarr.com
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
It is already implemented and was working fine.
https://git-wip-us.apache.org/repos/asf?p=stratos.git;a=tree;f=components/org.apache.stratos.python.cartridge.agent/cartridgeagent/cartridgeagent/modules/artifactmgt;h=b0376c57220d2ca577c7b383d8a1461b80b18e5c;hb=HEAD
Thanks.
On Fri, Jan 2, 2015 at 6:55 PM, Lakmal Warusawithana <la...@wso2.com>
wrote:
> What do you mean?? Its there since M3
>
> On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Seems like we have not written logic in agent to checkout artifacts from
>> GIT repository.
>>
>> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> I have now fixed the issue of accessing the service via the host machine
>>> (http://kubernetes-master-ip:port/) and pushed changes to master branch.
>>>
>>> Now I see a problem when a public GIT repo url is given without
>>> specifying credentials. I'm currently looking into this.
>>>
>>> Thanks
>>>
>>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I have now resolved the health statistics publishing issue in agent:
>>>>
>>>> - There were several topology event parsers which were not properly
>>>> updated with the latest changes. As a result those were raising errors. I
>>>> have now fixed them.
>>>> - Agent's logic which waits until CEP port is active was not visible in
>>>> the logs. As a result it was not possible to see why agent is not
>>>> publishing health statistics. I have now enabled logs to show this process
>>>> so that if agent could not connect to CEP it would be visible.
>>>> - Docker images in docker hub are updated with the latest changes.
>>>>
>>>> Now I see a problem where the PHP service is not accessible from the
>>>> host machine, however it is accessible within the Kubernetes master. The
>>>> removal of host port from the container ports may have affected this. I'm
>>>> looking into this now.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <la...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I will be testing grouping aspects and scaling scenarios related to
>>>>> that.
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi Devs,
>>>>>>
>>>>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>>>>
>>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha release.
>>>>>> As I can recall following are the remaining tasks we need to complete:
>>>>>>
>>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>>
>>>>>> During past few days I was fixing issues in the Kubernetes workflow
>>>>>> and following are the remaining problems:
>>>>>> - Python agent does not publish health statistitics to CEP.
>>>>>> - Autoscaler obsolete member rule invokes terminateInstance() method
>>>>>> twice with the same member id. As a result the second call fails.
>>>>>>
>>>>>> I'm currently working on fixing the above issues and finalizing the
>>>>>> Kubernetes workflow.
>>>>>>
>>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>>
>>>>>> I believe we verified the complete service grouping functionality
>>>>>> with Mock IaaS however we could not test it with OpenStack and EC2.
>>>>>>
>>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>>
>>>>>> I did the initial implementation of clustering support for Load
>>>>>> Balancer and Cloud Controller, we need to verify it and apply it to
>>>>>> Autoscaler and Stratos Manager.
>>>>>>
>>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>>
>>>>>> Service grouping functionality allows us to add a load balancer
>>>>>> cartridge to an application or group. However we need to provide a
>>>>>> configuration option to specify which cartridges to be served by a given
>>>>>> load balancer cartridge.
>>>>>>
>>>>>> *5. Reduce the Docker Image Size:*
>>>>>>
>>>>>> Currently Docker base image size is around 380 MB and PHP Docker
>>>>>> image size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we
>>>>>> need to download the Docker images from Docker Hub once. It would be better
>>>>>> if we could reduce the size of the base image so that we could save time on
>>>>>> this process.
>>>>>>
>>>>>>
>>>>>> It would be great if anyone would like to contribute to remaining
>>>>>> tasks, we will try our best to complete them ASAP and announce 4.1.0-Alpha
>>>>>> release.
>>>>>>
>>>>>> Many Thanks
>>>>>>
>>>>>> --
>>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> 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/
>
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Lakmal Warusawithana <la...@wso2.com>.
What do you mean?? Its there since M3
On Fri, Jan 2, 2015 at 6:25 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Seems like we have not written logic in agent to checkout artifacts from
> GIT repository.
>
> On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I have now fixed the issue of accessing the service via the host machine
>> (http://kubernetes-master-ip:port/) and pushed changes to master branch.
>>
>> Now I see a problem when a public GIT repo url is given without
>> specifying credentials. I'm currently looking into this.
>>
>> Thanks
>>
>> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <im...@apache.org> wrote:
>>
>>> I have now resolved the health statistics publishing issue in agent:
>>>
>>> - There were several topology event parsers which were not properly
>>> updated with the latest changes. As a result those were raising errors. I
>>> have now fixed them.
>>> - Agent's logic which waits until CEP port is active was not visible in
>>> the logs. As a result it was not possible to see why agent is not
>>> publishing health statistics. I have now enabled logs to show this process
>>> so that if agent could not connect to CEP it would be visible.
>>> - Docker images in docker hub are updated with the latest changes.
>>>
>>> Now I see a problem where the PHP service is not accessible from the
>>> host machine, however it is accessible within the Kubernetes master. The
>>> removal of host port from the container ports may have affected this. I'm
>>> looking into this now.
>>>
>>> Thanks
>>>
>>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <la...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I will be testing grouping aspects and scaling scenarios related to
>>>> that.
>>>>
>>>> Thanks.
>>>>
>>>>
>>>>
>>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>>>
>>>>> We have now come to the last stage of finalizing 4.1.0-Alpha release.
>>>>> As I can recall following are the remaining tasks we need to complete:
>>>>>
>>>>> *1. Finalize Kubernetes Workflow:*
>>>>>
>>>>> During past few days I was fixing issues in the Kubernetes workflow
>>>>> and following are the remaining problems:
>>>>> - Python agent does not publish health statistitics to CEP.
>>>>> - Autoscaler obsolete member rule invokes terminateInstance() method
>>>>> twice with the same member id. As a result the second call fails.
>>>>>
>>>>> I'm currently working on fixing the above issues and finalizing the
>>>>> Kubernetes workflow.
>>>>>
>>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>>
>>>>> I believe we verified the complete service grouping functionality with
>>>>> Mock IaaS however we could not test it with OpenStack and EC2.
>>>>>
>>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>>
>>>>> I did the initial implementation of clustering support for Load
>>>>> Balancer and Cloud Controller, we need to verify it and apply it to
>>>>> Autoscaler and Stratos Manager.
>>>>>
>>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>>
>>>>> Service grouping functionality allows us to add a load balancer
>>>>> cartridge to an application or group. However we need to provide a
>>>>> configuration option to specify which cartridges to be served by a given
>>>>> load balancer cartridge.
>>>>>
>>>>> *5. Reduce the Docker Image Size:*
>>>>>
>>>>> Currently Docker base image size is around 380 MB and PHP Docker image
>>>>> size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we need to
>>>>> download the Docker images from Docker Hub once. It would be better if we
>>>>> could reduce the size of the base image so that we could save time on this
>>>>> process.
>>>>>
>>>>>
>>>>> It would be great if anyone would like to contribute to remaining
>>>>> tasks, we will try our best to complete them ASAP and announce 4.1.0-Alpha
>>>>> release.
>>>>>
>>>>> Many Thanks
>>>>>
>>>>> --
>>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Seems like we have not written logic in agent to checkout artifacts from
GIT repository.
On Fri, Jan 2, 2015 at 6:08 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I have now fixed the issue of accessing the service via the host machine
> (http://kubernetes-master-ip:port/) and pushed changes to master branch.
>
> Now I see a problem when a public GIT repo url is given without specifying
> credentials. I'm currently looking into this.
>
> Thanks
>
> On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I have now resolved the health statistics publishing issue in agent:
>>
>> - There were several topology event parsers which were not properly
>> updated with the latest changes. As a result those were raising errors. I
>> have now fixed them.
>> - Agent's logic which waits until CEP port is active was not visible in
>> the logs. As a result it was not possible to see why agent is not
>> publishing health statistics. I have now enabled logs to show this process
>> so that if agent could not connect to CEP it would be visible.
>> - Docker images in docker hub are updated with the latest changes.
>>
>> Now I see a problem where the PHP service is not accessible from the host
>> machine, however it is accessible within the Kubernetes master. The removal
>> of host port from the container ports may have affected this. I'm looking
>> into this now.
>>
>> Thanks
>>
>> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <la...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I will be testing grouping aspects and scaling scenarios related to that.
>>>
>>> Thanks.
>>>
>>>
>>>
>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>>
>>>> We have now come to the last stage of finalizing 4.1.0-Alpha release.
>>>> As I can recall following are the remaining tasks we need to complete:
>>>>
>>>> *1. Finalize Kubernetes Workflow:*
>>>>
>>>> During past few days I was fixing issues in the Kubernetes workflow and
>>>> following are the remaining problems:
>>>> - Python agent does not publish health statistitics to CEP.
>>>> - Autoscaler obsolete member rule invokes terminateInstance() method
>>>> twice with the same member id. As a result the second call fails.
>>>>
>>>> I'm currently working on fixing the above issues and finalizing the
>>>> Kubernetes workflow.
>>>>
>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>
>>>> I believe we verified the complete service grouping functionality with
>>>> Mock IaaS however we could not test it with OpenStack and EC2.
>>>>
>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>
>>>> I did the initial implementation of clustering support for Load
>>>> Balancer and Cloud Controller, we need to verify it and apply it to
>>>> Autoscaler and Stratos Manager.
>>>>
>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>
>>>> Service grouping functionality allows us to add a load balancer
>>>> cartridge to an application or group. However we need to provide a
>>>> configuration option to specify which cartridges to be served by a given
>>>> load balancer cartridge.
>>>>
>>>> *5. Reduce the Docker Image Size:*
>>>>
>>>> Currently Docker base image size is around 380 MB and PHP Docker image
>>>> size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we need to
>>>> download the Docker images from Docker Hub once. It would be better if we
>>>> could reduce the size of the base image so that we could save time on this
>>>> process.
>>>>
>>>>
>>>> It would be great if anyone would like to contribute to remaining
>>>> tasks, we will try our best to complete them ASAP and announce 4.1.0-Alpha
>>>> release.
>>>>
>>>> Many Thanks
>>>>
>>>> --
>>>> 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
>>>
>>>
>>
>>
>> --
>> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
I have now fixed the issue of accessing the service via the host machine
(http://kubernetes-master-ip:port/) and pushed changes to master branch.
Now I see a problem when a public GIT repo url is given without specifying
credentials. I'm currently looking into this.
Thanks
On Fri, Jan 2, 2015 at 5:20 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I have now resolved the health statistics publishing issue in agent:
>
> - There were several topology event parsers which were not properly
> updated with the latest changes. As a result those were raising errors. I
> have now fixed them.
> - Agent's logic which waits until CEP port is active was not visible in
> the logs. As a result it was not possible to see why agent is not
> publishing health statistics. I have now enabled logs to show this process
> so that if agent could not connect to CEP it would be visible.
> - Docker images in docker hub are updated with the latest changes.
>
> Now I see a problem where the PHP service is not accessible from the host
> machine, however it is accessible within the Kubernetes master. The removal
> of host port from the container ports may have affected this. I'm looking
> into this now.
>
> Thanks
>
> On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <la...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I will be testing grouping aspects and scaling scenarios related to that.
>>
>> Thanks.
>>
>>
>>
>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>
>>> We have now come to the last stage of finalizing 4.1.0-Alpha release. As
>>> I can recall following are the remaining tasks we need to complete:
>>>
>>> *1. Finalize Kubernetes Workflow:*
>>>
>>> During past few days I was fixing issues in the Kubernetes workflow and
>>> following are the remaining problems:
>>> - Python agent does not publish health statistitics to CEP.
>>> - Autoscaler obsolete member rule invokes terminateInstance() method
>>> twice with the same member id. As a result the second call fails.
>>>
>>> I'm currently working on fixing the above issues and finalizing the
>>> Kubernetes workflow.
>>>
>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>
>>> I believe we verified the complete service grouping functionality with
>>> Mock IaaS however we could not test it with OpenStack and EC2.
>>>
>>> *3. Verify Clustering Support for Stratos Components:*
>>>
>>> I did the initial implementation of clustering support for Load Balancer
>>> and Cloud Controller, we need to verify it and apply it to Autoscaler and
>>> Stratos Manager.
>>>
>>> *4. Load Balancer Configuration for Service Grouping:*
>>>
>>> Service grouping functionality allows us to add a load balancer
>>> cartridge to an application or group. However we need to provide a
>>> configuration option to specify which cartridges to be served by a given
>>> load balancer cartridge.
>>>
>>> *5. Reduce the Docker Image Size:*
>>>
>>> Currently Docker base image size is around 380 MB and PHP Docker image
>>> size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we need to
>>> download the Docker images from Docker Hub once. It would be better if we
>>> could reduce the size of the base image so that we could save time on this
>>> process.
>>>
>>>
>>> It would be great if anyone would like to contribute to remaining tasks,
>>> we will try our best to complete them ASAP and announce 4.1.0-Alpha release.
>>>
>>> Many Thanks
>>>
>>> --
>>> 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
>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
I have now resolved the health statistics publishing issue in agent:
- There were several topology event parsers which were not properly updated
with the latest changes. As a result those were raising errors. I have now
fixed them.
- Agent's logic which waits until CEP port is active was not visible in the
logs. As a result it was not possible to see why agent is not publishing
health statistics. I have now enabled logs to show this process so that if
agent could not connect to CEP it would be visible.
- Docker images in docker hub are updated with the latest changes.
Now I see a problem where the PHP service is not accessible from the host
machine, however it is accessible within the Kubernetes master. The removal
of host port from the container ports may have affected this. I'm looking
into this now.
Thanks
On Fri, Jan 2, 2015 at 10:41 AM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Hi,
>
> I will be testing grouping aspects and scaling scenarios related to that.
>
> Thanks.
>
>
>
> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Hi Devs,
>>
>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>
>> We have now come to the last stage of finalizing 4.1.0-Alpha release. As
>> I can recall following are the remaining tasks we need to complete:
>>
>> *1. Finalize Kubernetes Workflow:*
>>
>> During past few days I was fixing issues in the Kubernetes workflow and
>> following are the remaining problems:
>> - Python agent does not publish health statistitics to CEP.
>> - Autoscaler obsolete member rule invokes terminateInstance() method
>> twice with the same member id. As a result the second call fails.
>>
>> I'm currently working on fixing the above issues and finalizing the
>> Kubernetes workflow.
>>
>> *2. Verify Service Grouping on OpenStack and EC2:*
>>
>> I believe we verified the complete service grouping functionality with
>> Mock IaaS however we could not test it with OpenStack and EC2.
>>
>> *3. Verify Clustering Support for Stratos Components:*
>>
>> I did the initial implementation of clustering support for Load Balancer
>> and Cloud Controller, we need to verify it and apply it to Autoscaler and
>> Stratos Manager.
>>
>> *4. Load Balancer Configuration for Service Grouping:*
>>
>> Service grouping functionality allows us to add a load balancer cartridge
>> to an application or group. However we need to provide a configuration
>> option to specify which cartridges to be served by a given load balancer
>> cartridge.
>>
>> *5. Reduce the Docker Image Size:*
>>
>> Currently Docker base image size is around 380 MB and PHP Docker image
>> size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we need to
>> download the Docker images from Docker Hub once. It would be better if we
>> could reduce the size of the base image so that we could save time on this
>> process.
>>
>>
>> It would be great if anyone would like to contribute to remaining tasks,
>> we will try our best to complete them ASAP and announce 4.1.0-Alpha release.
>>
>> Many Thanks
>>
>> --
>> 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
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Lahiru Sandaruwan <la...@wso2.com>.
Hi,
I will be testing grouping aspects and scaling scenarios related to that.
Thanks.
On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Devs,
>
> Wish you a Very Happy New Year! Hope you all had a great holiday!
>
> We have now come to the last stage of finalizing 4.1.0-Alpha release. As I
> can recall following are the remaining tasks we need to complete:
>
> *1. Finalize Kubernetes Workflow:*
>
> During past few days I was fixing issues in the Kubernetes workflow and
> following are the remaining problems:
> - Python agent does not publish health statistitics to CEP.
> - Autoscaler obsolete member rule invokes terminateInstance() method twice
> with the same member id. As a result the second call fails.
>
> I'm currently working on fixing the above issues and finalizing the
> Kubernetes workflow.
>
> *2. Verify Service Grouping on OpenStack and EC2:*
>
> I believe we verified the complete service grouping functionality with
> Mock IaaS however we could not test it with OpenStack and EC2.
>
> *3. Verify Clustering Support for Stratos Components:*
>
> I did the initial implementation of clustering support for Load Balancer
> and Cloud Controller, we need to verify it and apply it to Autoscaler and
> Stratos Manager.
>
> *4. Load Balancer Configuration for Service Grouping:*
>
> Service grouping functionality allows us to add a load balancer cartridge
> to an application or group. However we need to provide a configuration
> option to specify which cartridges to be served by a given load balancer
> cartridge.
>
> *5. Reduce the Docker Image Size:*
>
> Currently Docker base image size is around 380 MB and PHP Docker image
> size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we need to
> download the Docker images from Docker Hub once. It would be better if we
> could reduce the size of the base image so that we could save time on this
> process.
>
>
> It would be great if anyone would like to contribute to remaining tasks,
> we will try our best to complete them ASAP and announce 4.1.0-Alpha release.
>
> Many Thanks
>
> --
> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Rajkumar Rajaratnam <ra...@wso2.com>.
I will work on verifying kubernetes workflow and testing on openstack if
time permits.
Thanks.
On Fri, Jan 2, 2015 at 10:24 AM, Lakmal Warusawithana <la...@wso2.com>
wrote:
> thanks I will work on this
>
> On Fri, Jan 2, 2015 at 10:21 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Thanks Lakmal! The latest docker image files can be found here:
>> https://github.com/imesh/stratos-docker-images
>>
>> Thanks
>>
>> On Fri, Jan 2, 2015 at 10:16 AM, Lakmal Warusawithana <la...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>>
>>>> We have now come to the last stage of finalizing 4.1.0-Alpha release.
>>>> As I can recall following are the remaining tasks we need to complete:
>>>>
>>>> *1. Finalize Kubernetes Workflow:*
>>>>
>>>> During past few days I was fixing issues in the Kubernetes workflow and
>>>> following are the remaining problems:
>>>> - Python agent does not publish health statistitics to CEP.
>>>> - Autoscaler obsolete member rule invokes terminateInstance() method
>>>> twice with the same member id. As a result the second call fails.
>>>>
>>>> I'm currently working on fixing the above issues and finalizing the
>>>> Kubernetes workflow.
>>>>
>>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>>
>>>> I believe we verified the complete service grouping functionality with
>>>> Mock IaaS however we could not test it with OpenStack and EC2.
>>>>
>>>> *3. Verify Clustering Support for Stratos Components:*
>>>>
>>>> I did the initial implementation of clustering support for Load
>>>> Balancer and Cloud Controller, we need to verify it and apply it to
>>>> Autoscaler and Stratos Manager.
>>>>
>>>> *4. Load Balancer Configuration for Service Grouping:*
>>>>
>>>> Service grouping functionality allows us to add a load balancer
>>>> cartridge to an application or group. However we need to provide a
>>>> configuration option to specify which cartridges to be served by a given
>>>> load balancer cartridge.
>>>>
>>>> *5. Reduce the Docker Image Size:*
>>>>
>>>> Currently Docker base image size is around 380 MB and PHP Docker image
>>>> size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we need to
>>>> download the Docker images from Docker Hub once. It would be better if we
>>>> could reduce the size of the base image so that we could save time on this
>>>> process.
>>>>
>>>>
>>> Where I can get updated dockerfile? I can work on this.
>>>
>>>
>>>>
>>>> It would be great if anyone would like to contribute to remaining
>>>> tasks, we will try our best to complete them ASAP and announce 4.1.0-Alpha
>>>> release.
>>>>
>>>> Many 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/
>>>
>>>
>>
>>
>> --
>> 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/
>
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Lakmal Warusawithana <la...@wso2.com>.
thanks I will work on this
On Fri, Jan 2, 2015 at 10:21 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Thanks Lakmal! The latest docker image files can be found here:
> https://github.com/imesh/stratos-docker-images
>
> Thanks
>
> On Fri, Jan 2, 2015 at 10:16 AM, Lakmal Warusawithana <la...@wso2.com>
> wrote:
>
>>
>>
>> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>>
>>> We have now come to the last stage of finalizing 4.1.0-Alpha release. As
>>> I can recall following are the remaining tasks we need to complete:
>>>
>>> *1. Finalize Kubernetes Workflow:*
>>>
>>> During past few days I was fixing issues in the Kubernetes workflow and
>>> following are the remaining problems:
>>> - Python agent does not publish health statistitics to CEP.
>>> - Autoscaler obsolete member rule invokes terminateInstance() method
>>> twice with the same member id. As a result the second call fails.
>>>
>>> I'm currently working on fixing the above issues and finalizing the
>>> Kubernetes workflow.
>>>
>>> *2. Verify Service Grouping on OpenStack and EC2:*
>>>
>>> I believe we verified the complete service grouping functionality with
>>> Mock IaaS however we could not test it with OpenStack and EC2.
>>>
>>> *3. Verify Clustering Support for Stratos Components:*
>>>
>>> I did the initial implementation of clustering support for Load Balancer
>>> and Cloud Controller, we need to verify it and apply it to Autoscaler and
>>> Stratos Manager.
>>>
>>> *4. Load Balancer Configuration for Service Grouping:*
>>>
>>> Service grouping functionality allows us to add a load balancer
>>> cartridge to an application or group. However we need to provide a
>>> configuration option to specify which cartridges to be served by a given
>>> load balancer cartridge.
>>>
>>> *5. Reduce the Docker Image Size:*
>>>
>>> Currently Docker base image size is around 380 MB and PHP Docker image
>>> size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we need to
>>> download the Docker images from Docker Hub once. It would be better if we
>>> could reduce the size of the base image so that we could save time on this
>>> process.
>>>
>>>
>> Where I can get updated dockerfile? I can work on this.
>>
>>
>>>
>>> It would be great if anyone would like to contribute to remaining tasks,
>>> we will try our best to complete them ASAP and announce 4.1.0-Alpha release.
>>>
>>> Many 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/
>>
>>
>
>
> --
> 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: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Imesh Gunaratne <im...@apache.org>.
Thanks Lakmal! The latest docker image files can be found here:
https://github.com/imesh/stratos-docker-images
Thanks
On Fri, Jan 2, 2015 at 10:16 AM, Lakmal Warusawithana <la...@wso2.com>
wrote:
>
>
> On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Hi Devs,
>>
>> Wish you a Very Happy New Year! Hope you all had a great holiday!
>>
>> We have now come to the last stage of finalizing 4.1.0-Alpha release. As
>> I can recall following are the remaining tasks we need to complete:
>>
>> *1. Finalize Kubernetes Workflow:*
>>
>> During past few days I was fixing issues in the Kubernetes workflow and
>> following are the remaining problems:
>> - Python agent does not publish health statistitics to CEP.
>> - Autoscaler obsolete member rule invokes terminateInstance() method
>> twice with the same member id. As a result the second call fails.
>>
>> I'm currently working on fixing the above issues and finalizing the
>> Kubernetes workflow.
>>
>> *2. Verify Service Grouping on OpenStack and EC2:*
>>
>> I believe we verified the complete service grouping functionality with
>> Mock IaaS however we could not test it with OpenStack and EC2.
>>
>> *3. Verify Clustering Support for Stratos Components:*
>>
>> I did the initial implementation of clustering support for Load Balancer
>> and Cloud Controller, we need to verify it and apply it to Autoscaler and
>> Stratos Manager.
>>
>> *4. Load Balancer Configuration for Service Grouping:*
>>
>> Service grouping functionality allows us to add a load balancer cartridge
>> to an application or group. However we need to provide a configuration
>> option to specify which cartridges to be served by a given load balancer
>> cartridge.
>>
>> *5. Reduce the Docker Image Size:*
>>
>> Currently Docker base image size is around 380 MB and PHP Docker image
>> size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we need to
>> download the Docker images from Docker Hub once. It would be better if we
>> could reduce the size of the base image so that we could save time on this
>> process.
>>
>>
> Where I can get updated dockerfile? I can work on this.
>
>
>>
>> It would be great if anyone would like to contribute to remaining tasks,
>> we will try our best to complete them ASAP and announce 4.1.0-Alpha release.
>>
>> Many 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/
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Finalizing 4.1.0-Alpha Release
Posted by Lakmal Warusawithana <la...@wso2.com>.
On Fri, Jan 2, 2015 at 10:04 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Devs,
>
> Wish you a Very Happy New Year! Hope you all had a great holiday!
>
> We have now come to the last stage of finalizing 4.1.0-Alpha release. As I
> can recall following are the remaining tasks we need to complete:
>
> *1. Finalize Kubernetes Workflow:*
>
> During past few days I was fixing issues in the Kubernetes workflow and
> following are the remaining problems:
> - Python agent does not publish health statistitics to CEP.
> - Autoscaler obsolete member rule invokes terminateInstance() method twice
> with the same member id. As a result the second call fails.
>
> I'm currently working on fixing the above issues and finalizing the
> Kubernetes workflow.
>
> *2. Verify Service Grouping on OpenStack and EC2:*
>
> I believe we verified the complete service grouping functionality with
> Mock IaaS however we could not test it with OpenStack and EC2.
>
> *3. Verify Clustering Support for Stratos Components:*
>
> I did the initial implementation of clustering support for Load Balancer
> and Cloud Controller, we need to verify it and apply it to Autoscaler and
> Stratos Manager.
>
> *4. Load Balancer Configuration for Service Grouping:*
>
> Service grouping functionality allows us to add a load balancer cartridge
> to an application or group. However we need to provide a configuration
> option to specify which cartridges to be served by a given load balancer
> cartridge.
>
> *5. Reduce the Docker Image Size:*
>
> Currently Docker base image size is around 380 MB and PHP Docker image
> size is around 404 MB. Due to a known issue in Kubernetes v0.5.2 we need to
> download the Docker images from Docker Hub once. It would be better if we
> could reduce the size of the base image so that we could save time on this
> process.
>
>
Where I can get updated dockerfile? I can work on this.
>
> It would be great if anyone would like to contribute to remaining tasks,
> we will try our best to complete them ASAP and announce 4.1.0-Alpha release.
>
> Many 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/