Re: Build failed in Jenkins: Stratos-Master-Commit-Build » Apache Stratos - Autoscaler #23

There was an issue with a file rename process, I have now fixed this and triggered a new build. Thanks On Sat, Jan 24, 2015 at 11:28 AM, Imesh Gunaratne wrote: > This build failure has occurred due to a file rename where Jenkins > workspace had the old file. I have now removed the Jenkins works

[GitHub] stratos pull request: Removing duplicate files generated by the fi...

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

[GitHub] stratos pull request: Removing duplicate files generated by the fi...

GitHub user imesh opened a pull request: https://github.com/apache/stratos/pull/184 Removing duplicate files generated by the file rename process You can merge this pull request into a Git repository by running: $ git pull https://github.com/imesh/stratos master Alternatively

Re: Build failed in Jenkins: Stratos-Master-Commit-Build » Apache Stratos - Autoscaler #23

This build failure has occurred due to a file rename where Jenkins workspace had the old file. I have now removed the Jenkins workspace and started a new build. Will update once the build completes. Thanks On Sat, Jan 24, 2015 at 11:16 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote:

Re: [Discuss] [Improvement] Manage Network Partitions Globally and Reuse them in Deployment Policy

I have now added logic to validate partitions of the network partition in the following API method: POST /networkPartitions -d {networkPartition.json} Thanks On Sat, Jan 24, 2015 at 10:10 AM, Imesh Gunaratne wrote: > Hi Devs, > > I have done an improvement to globally manage Network Partitions

Re: [Blog] Introduction to Apache Stratos Mock IaaS

Hi Devs, Please note that we have now disabled Mock IaaS in default distribution to make sure that it does not run in a production environment. Please enable it when needed via following configuration file: /repository/conf/mock-iaas.xml ... Thanks On Sat, Jan 10, 2015 at 12:02 AM, Imesh Gun

[Discuss] [Improvement] Manage Network Partitions Globally and Reuse them in Deployment Policy

Hi Devs, I have done an improvement to globally manage Network Partitions after a discussion we had with Lakmal and Dakshika. In 4.1.0-Alpha we manage Network Partitions within Deployment Policies. This makes it difficult to deploy an application via the UI and at the same time network partitions

RE: DISCUSS: RE: Are we still supporting java agent?

Thanks for the heads up Regards Martin From: Imesh Gunaratne [mailto:im...@apache.org] Sent: Friday, January 23, 2015 8:29 PM To: dev Subject: Re: DISCUSS: RE: Are we still supporting java agent? Hi Martin, I assume no one has tried Java based Cartridge Agent since we started using the Python

Re: DISCUSS: RE: Are we still supporting java agent?

Hi Martin, I assume no one has tried Java based Cartridge Agent since we started using the Python Cartridge Agent. However we have updated it with the recent changes we did for messaging, otherwise the build will break. No, MQTT support is implemented in messaging component so any other Java comp

[jira] [Created] (STRATOS-1121) Manage Network Partitions Globally and Reuse them in Deployment Policy

Imesh Gunaratne created STRATOS-1121: Summary: Manage Network Partitions Globally and Reuse them in Deployment Policy Key: STRATOS-1121 URL: https://issues.apache.org/jira/browse/STRATOS-1121 Proj

[jira] [Updated] (STRATOS-1120) Extra space before "Back" button - Cartridge group definition page

[ https://issues.apache.org/jira/browse/STRATOS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1120: -- Attachment: Screen Shot 2015-01-23 at 11.58.45 PM.png > Extra space before "Back" butt

[jira] [Created] (STRATOS-1120) Extra space before "Back" button - Cartridge group definition page

Mariangela Hills created STRATOS-1120: - Summary: Extra space before "Back" button - Cartridge group definition page Key: STRATOS-1120 URL: https://issues.apache.org/jira/browse/STRATOS-1120 Projec

DISCUSS: RE: Are we still supporting java agent?

Bringing this topic up again. We do have some requirements to, at least temporarily, maintain a functioning java based cartridge agent. Has any work gone into the java based cartridge agent since the last discussion? Has someone else tried if it still works ? Getting it back to work, where woul

[jira] [Updated] (STRATOS-1119) Error code incorrect when adding existing cartridge group

[ https://issues.apache.org/jira/browse/STRATOS-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1119: -- Issue Type: Bug (was: Improvement) > Error code incorrect when adding existing cartri

[jira] [Created] (STRATOS-1119) Error code incorrect when adding existing cartridge group

Mariangela Hills created STRATOS-1119: - Summary: Error code incorrect when adding existing cartridge group Key: STRATOS-1119 URL: https://issues.apache.org/jira/browse/STRATOS-1119 Project: Stratos

[jira] [Commented] (STRATOS-1092) Validate before removal of cartridges and cartridge groups

[ https://issues.apache.org/jira/browse/STRATOS-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289386#comment-14289386 ] ASF GitHub Bot commented on STRATOS-1092: - GitHub user shirolk opened a pull req

[GitHub] stratos pull request: Validate removal of cartridges and cartridge...

GitHub user shirolk opened a pull request: https://github.com/apache/stratos/pull/183 Validate removal of cartridges and cartridge groups The purpose of the pull request is to incorporate validation when either a cartridge or cartridge group is removed - essentially these can only b

Re: Add new REST API method to remove Autoscaling policies

Great work Gayan! On Fri, Jan 23, 2015 at 5:10 PM, Gayan Gunarathne wrote: > Added new CLI command to remove auto-scaling policy. > > >remove-autoscaling-policy > > > Thanks, > Gayan > > On Thu, Jan 22, 2015 at 6:07 PM, Gayan Gunarathne wrote: > >> Thanks Mariangela for reminding this. Current

Re: Puppet - Purpose of package_repo variable in manifests/nodes/base.pp

Hi, We were hoping to introduce it in future. So ignore it for the time being. On Fri, Jan 23, 2015 at 6:25 PM, Chamila De Alwis wrote: > Hi Udara, > > Was this an older feature before Puppet's files folder was introduced or > is it something that we are hoping to introduce in the future? > > >

Re: Puppet - Purpose of package_repo variable in manifests/nodes/base.pp

Hi Udara, Was this an older feature before Puppet's files folder was introduced or is it something that we are hoping to introduce in the future? Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Fri, Jan 23, 2015 at 4:20 PM, Udara Liyanage wr

Re: How come I dont get an error when adding the identical cartridge definition twice?

+1 Yes will add an api method to update a cartridge. Thanks On Fri, Jan 23, 2015 at 5:18 PM, Udara Liyanage wrote: > > > On Fri, Jan 23, 2015 at 5:02 PM, Gayan Gunarathne wrote: > >> >> I think we can define two REST API operations with POST and PUT http >> methods. >> POST to create resource

[jira] [Created] (STRATOS-1118) Need to have policy delete option on configure section

Dakshika Jayathilaka created STRATOS-1118: - Summary: Need to have policy delete option on configure section Key: STRATOS-1118 URL: https://issues.apache.org/jira/browse/STRATOS-1118 Project: St

[GitHub] stratos pull request: After alpha improvement part001

GitHub user dakshika opened a pull request: https://github.com/apache/stratos/pull/182 After alpha improvement part001 1. policy delete option on configure section + improvements You can merge this pull request into a Git repository by running: $ git pull https://github.c

Re: Clarification on Error - Failed to allocate an IP address

Also check whether the you are using the correct networkInterfaces in tomcat.json file On Fri, Jan 23, 2015 at 5:41 PM, Udara Liyanage wrote: > Hi Vishanth, > > Can you check whether there is sufficient IP addresses to allocate by > logging into Horizon dashboard. > > On Fri, Jan 23, 2015 at 5:3

Re: Clarification on Error - Failed to allocate an IP address

Hi Vishanth, Can you check whether there is sufficient IP addresses to allocate by logging into Horizon dashboard. On Fri, Jan 23, 2015 at 5:39 PM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Hi devs, > > I am trying out some sample applications in Openstack and got the > following e

Clarification on Error - Failed to allocate an IP address

Hi devs, I am trying out some sample applications in Openstack and got the following error. I would like to know what does the following error mean? TID: [0] [STRATOS] [2015-01-23 11:37:40,873] INFO > {org.apache.stratos.cloud.controller.iaases.JcloudsIaas} - Allocating IP > addresses for membe

Re: How come I dont get an error when adding the identical cartridge definition twice?

On Fri, Jan 23, 2015 at 5:02 PM, Gayan Gunarathne wrote: > > I think we can define two REST API operations with POST and PUT http > methods. > POST to create resource and PUT to update resource. > (I will suggested to use PUT to update resource as we are update a > resource(cartridge) completely)

Re: Add new REST API method to remove Autoscaling policies

Added new CLI command to remove auto-scaling policy. >remove-autoscaling-policy Thanks, Gayan On Thu, Jan 22, 2015 at 6:07 PM, Gayan Gunarathne wrote: > Thanks Mariangela for reminding this. Currently don't have a CLI command > for this. I will add CLI command for auto-scaling policy removal

Re: How come I dont get an error when adding the identical cartridge definition twice?

I think we can define two REST API operations with POST and PUT http methods. POST to create resource and PUT to update resource. (I will suggested to use PUT to update resource as we are update a resource(cartridge) completely) Thanks, Gayan On Fri, Jan 23, 2015 at 4:40 PM, Lakmal Warusawithana

[jira] [Resolved] (STRATOS-1116) Add CLI command for auto-scaling policy removal.

[ https://issues.apache.org/jira/browse/STRATOS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gayan Gunarathne resolved STRATOS-1116. --- Resolution: Fixed Fixed with 78fff3fc608afb8d9a6c665fe62308550a1da179 > Add CLI com

Re: How come I dont get an error when adding the identical cartridge definition twice?

On Fri, Jan 23, 2015 at 4:17 PM, Imesh Gunaratne wrote: > I think with the terminology change "Deploy cartridge" -> "Add cartridge" > this functionality might not valid. We may need to raise an error if the > cartridge is already added with the HTTP status code 409. > > And we may need to add "up

[jira] [Created] (STRATOS-1117) Error not thrown when cartridge definition is duplicated

Mariangela Hills created STRATOS-1117: - Summary: Error not thrown when cartridge definition is duplicated Key: STRATOS-1117 URL: https://issues.apache.org/jira/browse/STRATOS-1117 Project: Stratos

Re: How come I dont get an error when adding the identical cartridge definition twice?

I think with the terminology change "Deploy cartridge" -> "Add cartridge" this functionality might not valid. We may need to raise an error if the cartridge is already added with the HTTP status code 409. Thanks On Fri, Jan 23, 2015 at 3:32 PM, Udara Liyanage wrote: > Hi, > > When a new cartrid

Re: Puppet - Purpose of package_repo variable in manifests/nodes/base.pp

Hi Chamila, It was introduced to host all packages (LB zip file, Active MQ jars ) in one place and puppet to fetch them from that location. We have those packs inside "files" folder in LB, ActiveMQ etc. However it is not used yet. On Fri, Jan 23, 2015 at 4:14 PM, Imesh Gunaratne wrote: > Yes as

Re: Puppet - Purpose of package_repo variable in manifests/nodes/base.pp

Yes as I can recall package_repo refers to a web server which hosts binary packages. May be this is not needed now as we are storing packages in puppet master itself. Thanks On Fri, Jan 23, 2015 at 1:24 PM, Chamila De Alwis wrote: > Hi, > > What is the purpose of the package_repo variable defin

Re: How come I dont get an error when adding the identical cartridge definition twice?

Hi, When a new cartridge with an existing name is added, it overwrites the existing one. So the behavior you got is the expected behavior. On Fri, Jan 23, 2015 at 3:28 PM, Mariangela Hills wrote: > I was expecting to get 409 when I added the same cartridge definition > twice, but I did not get

How come I dont get an error when adding the identical cartridge definition twice?

I was expecting to get 409 when I added the same cartridge definition twice, but I did not get an error. Is this meant to be this way? *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin https://localhost:9443/api/cart

[jira] [Created] (STRATOS-1116) Add CLI command for auto-scaling policy removal.

Gayan Gunarathne created STRATOS-1116: - Summary: Add CLI command for auto-scaling policy removal. Key: STRATOS-1116 URL: https://issues.apache.org/jira/browse/STRATOS-1116 Project: Stratos

Re: Unable to remove an auto-scaling policy

No I was trying to remove it using the REST API command. Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. w: http://wso2.com On Fri, Jan 23, 2015 at 3:03 PM, Dakshika Jayathilaka wrote: > Hi, > > Are you tr

Re: Unable to remove an auto-scaling policy

Ops... you were correct. It was a typo. Thanks, loads vishanth! Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. w: http://wso2.com On Fri, Jan 23, 2015 at 3:02 PM, Vishanth Balasubramaniam < vishan...@wso2.c

Re: Unable to remove an auto-scaling policy

Hi, Are you trying to remove it from UI? Regards, *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 On Fri, Jan 23, 2015 at 2:54 PM, Mariangela Hills wrote: > I was unable to remove two auto-scaling policies that I added. It says > that it does not exis

Re: Unable to remove an auto-scaling policy

Hi Mari, It could be a typo. Could you check the policy id is 'autoscale-policy-1' or 'autoscale_policy_1'? Thank you, Vishanth On Fri, Jan 23, 2015 at 2:54 PM, Mariangela Hills wrote: > I was unable to remove two auto-scaling policies that I added. It says > that it does not exist. However, w

[jira] [Created] (STRATOS-1115) No option to remove an Autoscaling policy via the UI

Mariangela Hills created STRATOS-1115: - Summary: No option to remove an Autoscaling policy via the UI Key: STRATOS-1115 URL: https://issues.apache.org/jira/browse/STRATOS-1115 Project: Stratos

Unable to remove an auto-scaling policy

I was unable to remove two auto-scaling policies that I added. It says that it does not exist. However, when I checked via the UI the autoscaling policies that I was trying to remove can be seen. Can someone tell me what I am doing wrong please. [2015-01-23 14:43:32,897] ERROR {org.apache.strato

[jira] [Created] (STRATOS-1114) Typos in the two comments in the deploy.sh sample file

Mariangela Hills created STRATOS-1114: - Summary: Typos in the two comments in the deploy.sh sample file Key: STRATOS-1114 URL: https://issues.apache.org/jira/browse/STRATOS-1114 Project: Stratos

Puppet - Purpose of package_repo variable in manifests/nodes/base.pp

Hi, What is the purpose of the package_repo variable defined in the base.pp manifest? It seems from the older revisions this was supposed to be a file server of some sort which serves the needed packs such as JDK, Tomcat, Cartridge Agent etc. However, with Puppet's own `files` folder, do we need t