Re: Setup Travis CI build for stratos to automate testing of GitHub PRs?

On Tue, Sep 9, 2014 at 12:07 PM, Nirmal Fernando wrote: > Absolute +1 Chris. Will be very helpful. > > On Tue, Sep 9, 2014 at 11:26 AM, chris snow wrote: > >> Hi devs, >> >> What do you think about $subject? If PRs are automatically built, it may >> take some pressure off of those working on me

Re: Setup Travis CI build for stratos to automate testing of GitHub PRs?

Absolute +1 Chris. Will be very helpful. On Tue, Sep 9, 2014 at 11:26 AM, chris snow wrote: > Hi devs, > > What do you think about $subject? If PRs are automatically built, it may > take some pressure off of those working on merging the PR because they will > know upfront if the PR breaks the b

[jira] [Commented] (STRATOS-767) Policy definitions and Cartridge definitions validation schema is not complete

[ https://issues.apache.org/jira/browse/STRATOS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126655#comment-14126655 ] Akila commented on STRATOS-767: --- Better yet, using a json schema for validation would be be

Setup Travis CI build for stratos to automate testing of GitHub PRs?

Hi devs, What do you think about $subject? If PRs are automatically built, it may take some pressure off of those working on merging the PR because they will know upfront if the PR breaks the build. Cheers, Chris

[jira] [Commented] (STRATOS-767) Policy definitions and Cartridge definitions validation schema is not complete

[ https://issues.apache.org/jira/browse/STRATOS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126634#comment-14126634 ] Akila commented on STRATOS-767: --- Validation schema should be auto-generated from bean class

[GitHub] stratos pull request: Adding missed timeout config

Github user lasinducharith closed the pull request at: https://github.com/apache/stratos/pull/7 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Assigned] (STRATOS-772) Modify mock REST endpoint for 4.1.0 changes

[ https://issues.apache.org/jira/browse/STRATOS-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reka Thirunavukkarasu reassigned STRATOS-772: - Assignee: Shiroshica Kulatilake > Modify mock REST endpoint for 4.1.0 ch

Fwd: [Discuss] High Level Flow for Composite Application Deployment

[re-sending to dev list since I had accidentally have removed dev list] -- Forwarded message -- From: Isuru Haththotuwa Date: Thu, Sep 4, 2014 at 12:14 PM Subject: Re: [Discuss] High Level Flow for Composite Application Deployment To: "Martin Eppel (meppel)" Hi Martin, On Thu

[jira] [Commented] (STRATOS-765) Upgrade to JClouds 1.8.0

[ https://issues.apache.org/jira/browse/STRATOS-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126609#comment-14126609 ] Akila commented on STRATOS-765: --- No plans yet. Do you think it's necessary since we are not

[GitHub] stratos pull request: Allows to add a description for policy and p...

Github user shirolk commented on the pull request: https://github.com/apache/stratos/pull/24#issuecomment-54923017 Hi Nirmal, Yes it is - though the actual change is just the addition of the field - the auto created wsdl file created has removed the specific close tags - hence

Re: Access URL not accessible with load balancing

On Tue, Sep 9, 2014 at 9:58 AM, Chamila De Alwis wrote: > Thanks Nirmal! That clears it up. > > In our case, it seems that LB is not opening the port specified as the > proxyPort by the cartridge. > Yes, unfortunately such a dynamism is hard to implement :-) (you need to restart LB etc.) > > Ac

Re: Access URL not accessible with load balancing

Hi Udara, axis2.xml is attached herewith Thanks On Tue, Sep 9, 2014 at 9:58 AM, Chamila De Alwis wrote: > Thanks Nirmal! That clears it up. > > In our case, it seems that LB is not opening the port specified as the > proxyPort by the cartridge. > > According to the puppet module template the t

Re: Access URL not accessible with load balancing

Thanks Nirmal! That clears it up. In our case, it seems that LB is not opening the port specified as the proxyPort by the cartridge. According to the puppet module template the transportReceiver port is defined at the nodes.pp as port 80 by default ($lb_httpPort)[1]. If the LB should accept reque

Re: Access URL not accessible with load balancing

Hi Prasanna, Could you please attach the axis2.xml of the running LB instance. Touched, not typed. Erroneous words are a feature, not a typo.

Re: 6 PRs on the queue

I merged several previous PRs. I will have a look again and try to merge. Please have a descriptive commit message when sending PR coz it is very helpful to understand what the PR actually does. Touched, not typed. Erroneous words are a feature, not a typo.

Re: Access URL not accessible with load balancing

Hi Akila, Template files too looks the same. Above part was taken from the template file On Tue, Sep 9, 2014 at 8:57 AM, Nirmal Fernando wrote: > Hi All, > > Let me explain the rationale behind defining a proxy port. Proxy port is a > way to let LB know, that LB should redirect all the request

Re: 6 PRs on the queue

All, We have 10 PRs on the queue. Can we have some eyes on those please? On Wed, Aug 20, 2014 at 11:48 AM, chris snow wrote: > I put a page on the wiki a while back: > > > https://cwiki.apache.org/confluence/display/STRATOS/Committers+%3A+Applying+github+pull+requests > On 20 Aug 2014 06:22, "A

[GitHub] stratos pull request: Allows to add a description for policy and p...

Github user nirmal070125 commented on the pull request: https://github.com/apache/stratos/pull/24#issuecomment-54920474 Hi Shiro, Thanks for the patch. Can you please check whether the changes done for the AutoscalerService.wsdl is related to the patch? --- If your project

Re: Access URL not accessible with load balancing

Hi All, Let me explain the rationale behind defining a proxy port. Proxy port is a way to let LB know, that LB should redirect all the requests that are coming to it (i.e. proxy port) to mapped host port (i.e. port). This mapping becomes vital when LB exposes multiple ports (i.e. you can define n

Re: Access URL not accessible with load balancing

Hi Prasanna, This commenting is not relevant since LB axis2.xml is deployed via Puppet. Please check Puppet lb module templates. On 9 Sep 2014 08:19, "Prasanna Dangalla" wrote: > Hi sajith, > > In LB's axis2.xml file. (in /repository/conf/axis2/axis2.xml), > the below mentioned part is commented

Re: Access URL not accessible with load balancing

Hi sajith, In LB's axis2.xml file. (in /repository/conf/axis2/axis2.xml), the below mentioned part is commented. Is this the reason because ports 8280 and 8243 are commented in this. On Tue, Sep 9, 2014 at

[jira] [Commented] (STRATOS-770) Adding in a "Description" field to all definition types

[ https://issues.apache.org/jira/browse/STRATOS-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126386#comment-14126386 ] Shiroshica Kulatilake commented on STRATOS-770: --- Hi, Could a committer ple

Re: [jira] [Commented] (STRATOS-770) Adding in a "Description" field to all definition types

Hi, Could a committer please review and do the needful for the pull request. https://github.com/apache/stratos/pull/24 Thank you, Shiro On Wed, Sep 3, 2014 at 3:01 PM, ASF GitHub Bot (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/STRATOS-770?page=com.atlassian.jira.plugin.sys

Unable to build the jclouds object error, NoSuchElementException: hardwareId

Hi Devs, After the latest merge between 4.0.0-grouing and master I get an error (I think as part of the latest merge with the master we picked up jclouds 1.8.x) when I try to deploy a cartridge, any idea how to work around this ? What I am missing ? Thanks Martin TID: [0] [STRATOS] [2014-09

Re: Access URL not accessible with load balancing

Setting proxyPort to 80 works successfully. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Mon, Sep 8, 2014 at 10:42 PM, Udara Liyanage wrote: > Instead of 0 could you try with 80. > > > > Touched, not typed. Erroneous words are a feature

Re: Access URL not accessible with load balancing

Instead of 0 could you try with 80. Touched, not typed. Erroneous words are a feature, not a typo.

Re: Access URL not accessible with load balancing

Hi Udara, I altogether removed the proxyPort from the php cartridge. Now the subscription provides port 0 as the access URL which again is not accessible. I'm not clear on how the access URL is constructed. But if the proxyPort is not provided shouldn't it default to the port provided rather than

Re: Access URL not accessible with load balancing

Hi, Then either php cartridge proxy port should be changed to 80 or nodes.pp should be changed to 8280 Touched, not typed. Erroneous words are a feature, not a typo.

Re: Access URL not accessible with load balancing

Hi Sajith, The value is set to 80. This is the value provided as default in the nodes.pp. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Mon, Sep 8, 2014 at 6:00 PM, Sajith Kariyawasam wrote: > Hi Chamila, > > Please check the port values

Re: Access URL not accessible with load balancing

Hi Chamila, Please check the port values in LB's axis2.xml file. (in /repository/conf/axis2/axis2.xml), wrote: > Update: > > I redeployed the load balancer with added proxyPort mapping and still the > cartridge isn't accessible through port 8280, only through port 80. > > > Regards, > Cham

Re: Access URL not accessible with load balancing

Update: I redeployed the load balancer with added proxyPort mapping and still the cartridge isn't accessible through port 8280, only through port 80. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Sun, Sep 7, 2014 at 11:19 PM, Chamila De Alw