Re: [Discuss] Kubernetes VirtualBox Vagrant Setup Fixed

Please find the latest Kubernetes vagrant setup with Kubernetes 0.11.0 and CoreOS Alpha 598.0.0 in the following git repository: https://github.com/imesh/kubernetes-vagrant-setup README.md file explains the steps for starting the Kubernetes cluster. Thanks On Fri, Feb 27, 2015 at 12:55 PM, Imesh

Jenkins build is back to stable : Stratos-Master-Commit-Build » Apache Stratos - Integration Tests #228

See

Jenkins build is back to stable : Stratos-Master-Commit-Build #228

See

Re: Jenkins build became unstable: Stratos-Master-Nightly-Build » Apache Stratos - Integration Tests #424

Great! Thanks Imesh. On Sat, Feb 28, 2015 at 8:44 AM, Imesh Gunaratne wrote: > I just fixed this in master branch, the jndi.properties file was not > copied to stratos instance started by the integration test, that has caused > this problem. > > Thanks > > On Sat, Feb 28, 2015 at 8:34 AM, Imesh

Re: Jenkins build became unstable: Stratos-Master-Nightly-Build » Apache Stratos - Integration Tests #424

I just fixed this in master branch, the jndi.properties file was not copied to stratos instance started by the integration test, that has caused this problem. Thanks On Sat, Feb 28, 2015 at 8:34 AM, Imesh Gunaratne wrote: > Thanks Raj! I will have a look at this. > > On Sat, Feb 28, 2015 at 8:3

Re: Jenkins build became unstable: Stratos-Master-Nightly-Build » Apache Stratos - Integration Tests #424

Thanks Raj! I will have a look at this. On Sat, Feb 28, 2015 at 8:30 AM, Rajkumar Rajaratnam wrote: > Integration test is failing due to following issue. We have changed the > port to 61617, but it seems some module is still trying to connect to > 61616. Will have a look at it. > > javax.jms.JMS

Re: Jenkins build became unstable: Stratos-Master-Nightly-Build » Apache Stratos - Integration Tests #424

Integration test is failing due to following issue. We have changed the port to 61617, but it seems some module is still trying to connect to 61616. Will have a look at it. javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection

[jira] [Commented] (STRATOS-1203) Add Global deployment policy view to configure section

[ https://issues.apache.org/jira/browse/STRATOS-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341265#comment-14341265 ] ASF GitHub Bot commented on STRATOS-1203: - Github user imesh commented on a diff

[GitHub] stratos pull request: Deployment policy add [STRATOS-1203]

Github user imesh commented on a diff in the pull request: https://github.com/apache/stratos/pull/238#discussion_r25553387 --- Diff: components/org.apache.stratos.manager.console/console/configure_form.jag --- @@ -86,6 +86,15 @@ if(isEdit == false && elements.action != 'new') {

Jenkins build became unstable: Stratos-Master-Nightly-Build #424

See

Jenkins build became unstable: Stratos-Master-Nightly-Build » Apache Stratos - Integration Tests #424

See

[GitHub] stratos pull request: Master deployment policy fix merge

Github user imesh commented on the pull request: https://github.com/apache/stratos/pull/245#issuecomment-76505794 @dinithis We might need to redo this modification on the master branch now as we have merged all the parallel branches to master. Thanks --- If your project is set up

Jenkins build is still unstable: Stratos-Master-Commit-Build #227

See

Jenkins build is still unstable: Stratos-Master-Commit-Build » Apache Stratos - Integration Tests #227

See

Jenkins build became unstable: Stratos-Master-Commit-Build » Apache Stratos - Integration Tests #226

See

Jenkins build became unstable: Stratos-Master-Commit-Build #226

See

Re: [Discuss] Fixing Sample Applications with Deployment Policy Modification

I have fixed the following samples. - single-cartridge - single-group-cartridge - wordpress - wordpress-extended-v1 - wordpress-extended-v2 Thanks. On Fri, Feb 27, 2015 at 10:58 PM, Imesh Gunaratne wrote: > I can see that Raj has fixed some applications, Raj: can you please upda

Re: [Discuss] Fixing Sample Applications with Deployment Policy Modification

I can see that Raj has fixed some applications, Raj: can you please update which applications you have fixed? I have now fixed Tomcat application. On Fri, Feb 27, 2015 at 10:56 PM, Imesh Gunaratne wrote: > Hi Devs, > > We now need to update all the sample applications according to new > deployme

[Discuss] Fixing Sample Applications with Deployment Policy Modification

Hi Devs, We now need to update all the sample applications according to new deployment policy modification. We could use this thread to track its status. Thanks -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos

Re: [Discuss] Kubernetes Cluster Reference in Network Partition

Dakshika: It would be great if we can add a dropdown for the partition's property field (region/zone/cluster). WDYT? Thanks On Fri, Feb 27, 2015 at 10:51 PM, Imesh Gunaratne wrote: > This modification would allow us to define a Kubernetes cluster per > partition and it would adhere to the stand

Re: [Discuss] Kubernetes Cluster Reference in Network Partition

This modification would allow us to define a Kubernetes cluster per partition and it would adhere to the standard way of defining a IaaS partition. Thanks On Fri, Feb 27, 2015 at 10:48 PM, Imesh Gunaratne wrote: > Hi Devs, > > I have now removed the kubernetesClusterId property from the network

[Discuss] Kubernetes Cluster Reference in Network Partition

Hi Devs, I have now removed the kubernetesClusterId property from the network partition definition and added it as a property in the partition. Please refer the sample artifact below: { "id": "network-partition-1", "partitions": [ { "id": "partition-1", "pr

Re: GSoC 2015

Hi, the reason is Cmd2 ( and most of the python CLI frameworks ) uses function mapping to CLI commands, that is, // stratos>greet def do_greet(): print("hi") will become the 'greet' command. But if we need, 'list-tenants' we have to code it as def do_list-tenants: #codes of list tenan

Re: GSoC 2015

Hi Milindu, Is there any way of using "-" in the CLI commands. I did not get why a CLI framework would block "-" character. Thanks On Fri, Feb 27, 2015 at 2:49 PM, Milindu Sanoj Kumarage < agentmili...@gmail.com> wrote: > Hi, > > Then shall we go with Cmd2 python package? Only change we have to

[Discuss] Kubernetes Client Live Tests

Hi Devs, I have now updated the Kubernetes live tests to validate the Kubernetes client API according to the latest changes we did. The README.md [1] file has been updated accordingly. We have added new parameters to control the tests. Please note that now we do not delete all the pods, services

Re: [Important] Please hold your commits to master branch!

Great work Raj!! We now have the deployment policy changes in the master branch. Thanks On Fri, Feb 27, 2015 at 9:04 PM, Rajkumar Rajaratnam wrote: > Hi, > > I have rebased *master-deployment-policy-fix-merge *branch onto *master* > branch. Please work on master branch hereafter. > > Thanks. >

Re: [Discuss] 4.1.0-Beta version not listed in JIRA

Thanks for reminding Mari! Yes there should be, we need to rename 4.1.0-RC1 to 4.1.0-BETA and then create a new entry for 4.1.0-RC1. I will do that. On Fri, Feb 27, 2015 at 7:11 PM, Mariangela Hills wrote: > Should'nt there be a 4.1.0-Beta version in the fixed version drop down > menu in JIRA?

Re: [Important] Merge master branch and 4.1.0-beta-deployment-policy-fix branch

I have rebased *master-deployment-policy-fix-merge *onto* master *branch. Now master branch has deployment changes. Please work on master branch hereafter. Thanks. On Fri, Feb 27, 2015 at 3:55 PM, Imesh Gunaratne wrote: > I have now created a new kubernetes tag in master branch. I think we can

Re: [Important] Please hold your commits to master branch!

Hi, I have rebased *master-deployment-policy-fix-merge *branch onto *master* branch. Please work on master branch hereafter. Thanks. On Fri, Feb 27, 2015 at 8:19 PM, Rajkumar Rajaratnam wrote: > Hi Devs, > > I am going to merge *master-deployment-policy-fix-merge* branch into > master branch.

[GitHub] stratos pull request: PCA - Check ports activity when publishing i...

Github user asfgit closed the pull request at: https://github.com/apache/stratos/pull/244 --- 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

[Important] Please hold your commits to master branch!

Hi Devs, I am going to merge *master-deployment-policy-fix-merge* branch into master branch. Please hold your commits for an hour. I will notify when I am done. Thanks. -- Rajkumar Rajaratnam Committer & PMC Member, Apache Stratos Software Engineer, WSO2 Mobile : +94777568639 Blog : rajkumarr

[Discuss] 4.1.0-Beta version not listed in JIRA

Should'nt there be a 4.1.0-Beta version in the fixed version drop down menu in JIRA? Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. w: http://wso2.com

[jira] [Updated] (STRATOS-1206) Wiki - Kubernetes client live tests fail

[ https://issues.apache.org/jira/browse/STRATOS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1206: -- Summary: Wiki - Kubernetes client live tests fail (was: Kubernetes client live tests

[jira] [Updated] (STRATOS-1206) Kubernetes client live tests fail

[ https://issues.apache.org/jira/browse/STRATOS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1206: -- Component/s: Documentation > Kubernetes client live tests fail > -

[jira] [Resolved] (STRATOS-1206) Kubernetes client live tests fail

[ https://issues.apache.org/jira/browse/STRATOS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills resolved STRATOS-1206. --- Resolution: Fixed Fix Version/s: 4.1.0 The live tests were using the "gurpart

[jira] [Assigned] (STRATOS-1206) Kubernetes client live tests fail

[ https://issues.apache.org/jira/browse/STRATOS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills reassigned STRATOS-1206: - Assignee: Mariangela Hills > Kubernetes client live tests fail > --

[jira] [Resolved] (STRATOS-1221) /bin/stratos.sh not an executable file by default

[ https://issues.apache.org/jira/browse/STRATOS-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udara Liyanage resolved STRATOS-1221. - Resolution: Fixed Assignee: Udara Liyanage fixed in 6150cab > /bin/stratos.sh not

[jira] [Resolved] (STRATOS-1210) Wiki - Instructions to add the CLI tool are vague

[ https://issues.apache.org/jira/browse/STRATOS-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills resolved STRATOS-1210. --- Resolution: Fixed Fix Version/s: 4.1.0 I updated the instructions in [1]. [

[jira] [Assigned] (STRATOS-1210) Wiki - Instructions to add the CLI tool are vague

[ https://issues.apache.org/jira/browse/STRATOS-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills reassigned STRATOS-1210: - Assignee: Mariangela Hills > Wiki - Instructions to add the CLI tool are vague

[jira] [Updated] (STRATOS-1210) Wiki - Instructions to add the CLI tool are vague

[ https://issues.apache.org/jira/browse/STRATOS-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1210: -- Description: The Instructions to add the CLI tool are vague. For example, it is not ev

[jira] [Updated] (STRATOS-1210) Wiki - Instructions to add the CLI tool are vague

[ https://issues.apache.org/jira/browse/STRATOS-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1210: -- Summary: Wiki - Instructions to add the CLI tool are vague (was: Wiki - Instructions

[jira] [Created] (STRATOS-1221) /bin/stratos.sh not an executable file by default

Mariangela Hills created STRATOS-1221: - Summary: /bin/stratos.sh not an executable file by default Key: STRATOS-1221 URL: https://issues.apache.org/jira/browse/STRATOS-1221 Project: Stratos

Re: [Stratos] Apache-stratos-python-cartridge-agent-4.1.0 running error

Hi, If you want to create a AS cartridge create a dummy file at the specified location. However normal approach is the base image approach. On Fri, Feb 27, 2015 at 6:02 PM, Sajith Abeywardhana wrote: > Hi Udara, > > This instance created by me to create a cartridge using *Ubuntu Cloud > 14.04.

Re: [Stratos] Apache-stratos-python-cartridge-agent-4.1.0 running error

Hi Udara, This instance created by me to create a cartridge using *Ubuntu Cloud 14.04. *And then I installed the puppet agent. I'm following this documentation. - https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Single+Cartridge+on+OpenStack *Sajith Abeywardhana* | Software Engineer WSO2

Re: [Stratos] Apache-stratos-python-cartridge-agent-4.1.0 running error

Hi, ‘/tmp/payload/launch-params' is the file where Stratos stores the payload sent to the instance. Is this a instance created by Stratos? On Fri, Feb 27, 2015 at 5:50 PM, Sajith Abeywardhana wrote: > Hi All, > > I'm getting this ERROR while executing *puppet agent --test* command. I > lunched

[Stratos] Apache-stratos-python-cartridge-agent-4.1.0 running error

Hi All, I'm getting this ERROR while executing *puppet agent --test* command. I lunched an Ubuntu 14.04 cloud instance, which puppet agent installed, to run this command. I checked the /tmp/payload/ folder and it dose not have any thing. Info: Computing checksum on file /mnt/apache-stratos-python

Jenkins build is back to stable : Stratos-Master-Commit-Build #218

See

Jenkins build is back to stable : Stratos-Master-Commit-Build » Apache Stratos - Integration Tests #218

See

Jenkins build became unstable: Stratos-Master-Commit-Build » Apache Stratos - Integration Tests #217

See

Jenkins build became unstable: Stratos-Master-Commit-Build #217

See

Re: [Important] Merge master branch and 4.1.0-beta-deployment-policy-fix branch

I have now created a new kubernetes tag in master branch. I think we can now merge *master-deployment-policy-fix-merge *branch to master with the new deployment policy changes. Thanks On Thu, Feb 26, 2015 at 3:38 PM, Imesh Gunaratne wrote: > Great work Raj!! :-) BTW I merged several pull reques

Re: [Discuss] [Kubernetes] Might need to avoid using Replication Controllers

I have now pushed this fix to master branch and merged to master-deployment-policy-fix-merge branch. A new tag has been created to track Kubernetes fix: 4.1.0-beta-kubernetes-v4 Thanks On Fri, Feb 27, 2015 at 7:34 AM, Imesh Gunaratne wrote: > I found the cause of the problem and fixed it! > > -

Re: GSoC 2015

Hi, Then shall we go with Cmd2 python package? Only change we have to do is call CLI commands with '_ ' instead '-', like 'list_tenants' instead of 'list-tenants'. And for HTTP request/response handling, we can use either Python's urllib3 or Requests, a wrapper around urllib3 which gives much s