Re: [Discuss] Domain Mappings for Subscriptions

Ok, got the point, why we need a new operation. But IMO we should have something like: *GET https://sm-ip:sm-port/stratos/admin/cartridge/subscription/domain/some.oragnization1.org * and if the domain is not a valid one, we should return an error, if it's a vali

Re: master jenkins build failing

Ah, ok. I'll open a JIRA ticket. Thanks Lakmal. On Mon, May 12, 2014 at 6:53 AM, Lakmal Warusawithana wrote: > I tried, but still I haven't Insufficient access, see below > > Insufficient access at /usr/local/bin/modify_group_members.pl line 102 > > > > On Mon, May 12, 2014 at 10:53 AM, chris s

Re: master jenkins build failing

I tried, but still I haven't Insufficient access, see below Insufficient access at /usr/local/bin/modify_group_members.pl line 102 On Mon, May 12, 2014 at 10:53 AM, chris snow wrote: > Sorry Lakmal, my id is chsnow. > On 12 May 2014 04:47, "Lakmal Warusawithana" wrote: > >> Hi Chris, >> >> I

Re: master jenkins build failing

Sorry Lakmal, my id is chsnow. On 12 May 2014 04:47, "Lakmal Warusawithana" wrote: > Hi Chris, > > I tried to add you but seems it did not work (see below). Is usd correct? > Still I did not official PMC chair until approved by the board. @Imesh, > how did you managed to get the account, is via

Re: is it ok to commit fixes to 4.0.0-incubating branch?

Hi Lakmal, As suggested by Chris, I have added a note in [1]. [1] https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+CLI+Tool Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com

[jira] [Resolved] (STRATOS-647) Domain Subscription Added/Removed processors do not handle the event correctly

[ https://issues.apache.org/jira/browse/STRATOS-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udara Liyanage resolved STRATOS-647. Resolution: Fixed > Domain Subscription Added/Removed processors do not handle the event c

Re: Account for Apache Stratos AMI in AWS Marketplace

On Sat, May 10, 2014 at 11:28 PM, Dmitry Sotnikov wrote: > Lakmal, > > Pinging you on this to put this on top of your threads. :) > > So how do we figure out whether we can have an AWS Marketplace account for > Apache Stratos AMI? > > If we cannot, is using WSO2 AWS Marketplace account an option?

Re: master jenkins build failing

Hi Chris, I tried to add you but seems it did not work (see below). Is usd correct? Still I did not official PMC chair until approved by the board. @Imesh, how did you managed to get the account, is via infra JIRA? lakmal@minotaur:~$ modify_appgroups.pl hudson-jobadmin --add=csnow Found 0 peopl

Re: [Discuss] Release Apache Stratos 4.0.0 Incubating RC3

I tested RC3 binaries with Openstack/Docker IaaS. Deployment and subscriptions to the Tomcat cartridge worked fine. Damitha On Tue, May 6, 2014 at 10:37 PM, Imesh Gunaratne wrote: > Hi All, > > This thread is for discussion of the third release candidate of Apache > Stratos 4.0.0-incubating. P

Re: is it ok to commit fixes to 4.0.0-incubating branch?

On Sun, May 11, 2014 at 10:39 PM, chris snow wrote: > I've committed the fix to master (commit id: > 160a6e46058478fcc80ba29e47bc5aeb83df1645) > > Until this fix goes into 4.0.0, should we remove the section of the > wiki that describes using the CLI in command line mode? > > +1, @Mari, please no

Re: build failure on 4.0.0-incubating branch

On Sun, May 11, 2014 at 11:12 PM, chris snow wrote: > Hi Nirmal, > > What is the branching strategy for Stratos? > > IMHO, I would expect all stable branches to have a CI build regardless > of how long the branch exists. Broken builds on master are annoying, > but broken builds on a stable branc

Re: build failure on 4.0.0-incubating branch

hi Chris, I am also hitting this issue while trying your stratos-vagrant-box setup scripts. Could you pls share the resolution for this issue. I was trying to comment the following line in checkout() in stratos/stratos.sh git checkout ${STRATOS_SRC_VERSION} I was hitting some other issues(system

[jira] [Commented] (STRATOS-647) Domain Subscription Added/Removed processors do not handle the event correctly

[ https://issues.apache.org/jira/browse/STRATOS-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13992538#comment-13992538 ] Manula Chathurika Thantriwatte commented on STRATOS-647: Applied

Re: build failure on 4.0.0-incubating branch

On Sun, May 11, 2014 at 9:57 AM, Nirmal Fernando wrote: > Guys, > > This is nothing to do with test failures or there's nothing to go and say > to jclouds dev@ here. > I just said to report only "if" there are issues building jclouds without tests. That's what I also noticed previously where jclou

master jenkins build failing

Is anyone looking into this? https://builds.apache.org/view/All/job/Stratos-Master-Nightly-Build/131/console If no one is investigating this, shall try and get the CI master build passing again? ... [INFO] Apache Stratos - Profile Generation ... SUCCESS [5:10.767s] [INFO] Apache Strat

Re: master jenkins build failing

+1 from me Chris. On Mon, May 12, 2014 at 12:19 AM, chris snow wrote: > Would anyone have any objections to me administrating jenkins for Stratos? > > It looks like a PMC chair would need to execute a script [1]: > >modify_appgroups.pl hudson-jobadmin --add= > > --- > [1] http://wiki.apache

Re: master jenkins build failing

Would anyone have any objections to me administrating jenkins for Stratos? It looks like a PMC chair would need to execute a script [1]: modify_appgroups.pl hudson-jobadmin --add= --- [1] http://wiki.apache.org/general/Jenkins On Sun, May 11, 2014 at 7:34 PM, chris snow wrote: > Is anyone l

Concern regarding the "ping" topic used in Stratos

Hi Devs, I am working with a Stratos deployment these days. In our deployment, we are using WSO2 Message Broker as the message broker. There I see the following log getting printed very frequently (every second). TID: [0] [MB] [2014-05-05 08:31:52,352] INFO {org.wso2.andes.server.exchange.TopicE

Re: build failure on 4.0.0-incubating branch

+1 Chris. On Sun, May 11, 2014 at 10:42 AM, chris snow wrote: > Hi Nirmal, > > What is the branching strategy for Stratos? > > IMHO, I would expect all stable branches to have a CI build regardless > of how long the branch exists. Broken builds on master are annoying, > but broken builds on a

Re: build failure on 4.0.0-incubating branch

Hi Nirmal, What is the branching strategy for Stratos? IMHO, I would expect all stable branches to have a CI build regardless of how long the branch exists. Broken builds on master are annoying, but broken builds on a stable branch make people nervous. IMO, stable branches should really have a

Re: build failure on 4.0.0-incubating branch

On Sun, May 11, 2014 at 10:26 AM, Nirmal Fernando wrote: > > Hi Isuru, > > On Sun, May 11, 2014 at 10:15 AM, Isuru Perera wrote: > >> >> >> >> On Sun, May 11, 2014 at 9:57 AM, Nirmal Fernando >> wrote: >> >>> Guys, >>> >>> This is nothing to do with test failures or there's nothing to go and >>>

Re: build failure on 4.0.0-incubating branch

I am not sure about the 4.0.0-incubating branches' life time. If we keep it long, we would need to configure Jenkins job as we do now for master, to branch too. On Sun, May 11, 2014 at 10:17 AM, chris snow wrote: > Ah, no worries. I'll build the RC3 tag. > > This is quite a good case for getti

Re: build failure on 4.0.0-incubating branch

Hi Isuru, On Sun, May 11, 2014 at 10:15 AM, Isuru Perera wrote: > > > > On Sun, May 11, 2014 at 9:57 AM, Nirmal Fernando > wrote: > >> Guys, >> >> This is nothing to do with test failures or there's nothing to go and say >> to jclouds dev@ here. >> > I just said to report only "if" there are is

Re: build failure on 4.0.0-incubating branch

Ah, no worries. I'll build the RC3 tag. This is quite a good case for getting a CI build in place for the 4.0.0-incubating branch? On Sun, May 11, 2014 at 6:02 PM, Nirmal Fernando wrote: > Please build the RC3 tag Chris: > https://git-wip-us.apache.org/repos/asf?p=incubator-stratos.git;a=commit

Re: is it ok to commit fixes to 4.0.0-incubating branch?

I've committed the fix to master (commit id: 160a6e46058478fcc80ba29e47bc5aeb83df1645) Until this fix goes into 4.0.0, should we remove the section of the wiki that describes using the CLI in command line mode? On Sun, May 11, 2014 at 3:09 PM, Udara Liyanage wrote: > Commit the fix to master br

Re: is it ok to commit fixes to 4.0.0-incubating branch?

Hi Lakmal, I meant 4.0.1 in my previous email. I don't think this should stop 4.0.0. We should probably just either add a comment to the wiki CLI page or remove the section that describes command line mode. On Sun, May 11, 2014 at 6:09 PM, chris snow wrote: > I've committed the fix to master (c

Re: build failure on 4.0.0-incubating branch

Please build the RC3 tag Chris: https://git-wip-us.apache.org/repos/asf?p=incubator-stratos.git;a=commit;h=af4f2c4f29d0735424dcc2804cb46c3b8b046950 Seems like 4.0.0-incubating branch was messed up by the release plugin. Issue is https://git-wip-us.apache.org/repos/asf?p=incubator-stratos.git;a=bl

Re: build failure on 4.0.0-incubating branch

Guys, This is nothing to do with test failures or there's nothing to go and say to jclouds dev@ here. @Chris if you are in an urgency can you please build the source release of RC3? On Sun, May 11, 2014 at 9:49 AM, chris snow wrote: > Hi Isuru, I need to do some more investigating to find the

Re: build failure on 4.0.0-incubating branch

Hi Isuru, I need to do some more investigating to find the root cause of the problem... On Sun, May 11, 2014 at 5:38 PM, Isuru Perera wrote: > Hi Chris, > > If the jclouds project build without tests fail in a clean m2 repo, please > ask for the reasons in the jclouds dev@ mailing list. > > Than

Re: build failure on 4.0.0-incubating branch

Hi Chris, If the jclouds project build without tests fail in a clean m2 repo, please ask for the reasons in the jclouds dev@ mailing list. Thanks! On Sun, May 11, 2014 at 7:32 AM, Udara Liyanage wrote: > Hi Chris, > > I haven't come across any jira for that. Please create a jira. > > > > Touc

Re: build failure on 4.0.0-incubating branch

On Sun, May 11, 2014 at 7:07 AM, Udara Liyanage wrote: > Hi Chris, > > The reason for this is you build the projects with test disabled. Building > jclouds without test causes the problem I guess. > This does not seem to be a problem with tests jar not being there. If the build failing to find a

Re: [Wiki] Review Noted on AutoScaling

Hi, I wrote another article https://www.evernote.com/shard/s278/sh/a59656b5-1c1b-4bdd-960f-ef1f1d60f8e6/fb89bb92f68570f072efff55fea4e8b0 Scaling down is not discussed in my articles. Need to add. Touched, not typed. Erroneous words are a feature, not a typo.

Re: [DISCUSS] Apache Stratos 4.1.0 Features

On Fri, May 9, 2014 at 3:46 PM, Sanjiva Weerawarana wrote: > Can we add SoftLayer to the list of IaaS'es? I think some work was done > already but probably not completed. > > Usability improvements for admin console? We should do some user stories > to guide that design. > > +1, will add. Few more

Re: is it ok to commit fixes to 4.0.0-incubating branch?

On Sun, May 11, 2014 at 6:35 PM, chris snow wrote: > Hi Imesh, will these fixes go into 4.0.1? > > If this is not blocking issue, will ship with 4.0.1. If its blocking, we have to cancel current vote and restart it. IMHO, we should do 4.0.1 in soon with non blocking, but important issues, we may

Re: Concern regarding the "ping" topic used in Stratos

Hi, Yes it might cause problems in long run. Some cleanup process to subscribe to the ping topic and discard might be useful. Touched, not typed. Erroneous words are a feature, not a typo. On May 11, 2014 8:55 AM, "Amila Maha Arachchi" wrote: > Hi Devs, > > I am working with a Stratos deploym

Re: build failure on 4.0.0-incubating branch

Hi Chris, I haven't come across any jira for that. Please create a jira. Touched, not typed. Erroneous words are a feature, not a typo.

Re: build failure on 4.0.0-incubating branch

Hi Udara, Why does Stratos' jclouds fork require test to be enabled for it to build? Is there a JIRA raised to get this fixed? Cheers, Chris On Sun, May 11, 2014 at 3:07 PM, Udara Liyanage wrote: > Hi Chris, > > The reason for this is you build the projects with test disabled. Building > jcl

Re: is it ok to commit fixes to 4.0.0-incubating branch?

Commit the fix to master branch. I hope the fix will be available on n 401 Touched, not typed. Erroneous words are a feature, not a typo. On May 11, 2014 6:36 PM, "chris snow" wrote: > Hi Imesh, will these fixes go into 4.0.1? > > In particular, without STRATOS-650, CLI doesn't work in > non-i

Re: build failure on 4.0.0-incubating branch

Hi Chris, The reason for this is you build the projects with test disabled. Building jclouds without test causes the problem I guess. Workaround : Build dependencies with test and then build other modules without test. Touched, not typed. Erroneous words are a feature, not a typo.

Domain subscription added/removed events are not being handled properly

Hi, While I was testing agent extension points, I discovered that Domain subscription added/removed events are not properly being handled. The root problem was in the core messaging component subscription domain events processors. I have created a JIRA in [1] and attached a patch to fix the issue.

build failure on 4.0.0-incubating branch

Is anyone else seeing this issue at the moment? [ERROR] Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-feature-gen (4-p2-feature-generation) on project org.apache.stratos.cloud.controller.feature: ERROR: Failure to find org.apache.stratos:ec2:jar:1.7.1-stratos in http://maven.wso2

Re: is it ok to commit fixes to 4.0.0-incubating branch?

Hi Imesh, will these fixes go into 4.0.1? In particular, without STRATOS-650, CLI doesn't work in non-interactive (single command line) mode as described in the section 'Using single command line mode' on the wiki [1]. --- [1] https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+CLI+Tool On

Re: Cartridge Agent Jndi Configurator should be removed

Hi Jeffrey, We are still working on 4.0.0-RC release in 4.0.0-incubating branch. Therefore we might need to wait until we complete it to commit anything to 4.0.0-incubating branch. Thanks On Wed, May 7, 2014 at 12:27 AM, Jeffrey Nguyen (jeffrngu) < jeffr...@cisco.com> wrote: > Hi Lakmal, > > I

Re: stratos jenkins server

Thanks Imesh. Do we have a CI build for 4.0.0-incubating branch? If not, shall we get one set up? I can request this from the infra team. On Sun, May 11, 2014 at 12:49 PM, Imesh Gunaratne wrote: > Thanks for pointing this Chris, you could find it here: > https://builds.apache.org/view/All/job

Re: [Wiki] Pub/Sub event definitions

Great work Mari!! Will go through it and see whether we need to add anything. Thanks On Wed, May 7, 2014 at 8:19 PM, Mariangela Hills wrote: > I have improved the information on Pub/Sub event definitions as requested > by adding all the missing events and also by adding the data that is passed

Re: stratos jenkins server

Thanks for pointing this Chris, you could find it here: https://builds.apache.org/view/All/job/Stratos-Master-Nightly-Build/ I have also created a Wiki page to maintain links to all builds: https://cwiki.apache.org/confluence/display/STRATOS/4.0.0.+Jenkins+Builds On Sun, May 11, 2014 at 7:28 PM,

Re: is it ok to commit fixes to 4.0.0-incubating branch?

Thanks for asking. We need to keep 4.0.0-incubating branch without any code changes until we finalize the 4.0.0 release. Thanks On Sun, May 11, 2014 at 5:30 PM, chris snow wrote: > I have some fixes [1,2] that I'm testing on the 4.0.0-incubating branch. > > If these my tests pass, is it ok for

Re: Thread executors for components

+1 Yes we need to do this. On Sun, May 11, 2014 at 7:26 AM, Nirmal Fernando wrote: > Hi Udara, > > This was discussed several times in the list past and yes we should use > executors. +1 for fixing it. > > > On Sat, May 10, 2014 at 7:36 PM, Udara Liyanage wrote: > >> Hi Devs, >> >> Code snippet

[jira] [Updated] (STRATOS-501) SoftLayer IaaS Provider Support for Stratos

[ https://issues.apache.org/jira/browse/STRATOS-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-501: Fix Version/s: (was: FUTURE) 4.1.0 > SoftLayer IaaS Provider Suppor

Re: [DISCUSS] Apache Stratos 4.1.0 Features

> Can we add SoftLayer to the list of IaaS'es? I think some work was done > already but probably not completed. > > A great thought Sanjiva, yes I did some experiments with SoftLayer jclouds API few weeks back and found some issues in jclouds Softlayer provider (jclouds-1.7.1). We could complete th

stratos jenkins server

Do we still have a stratos CI build? What is the URL/IP address? It would be good to get a link in the wiki.

Cartridge Agent Extension Points

Hi, I've developed cartridge agent extension points feature for Stratos cartridge agent. This will work by listening to event messages published by CC, ADC and agents running on instances. Once an event is received it will execute a shell script (system command) with parameters passed to it as en

Re: testing with mail delay

Ack! On Wed, May 7, 2014 at 9:04 PM, Lakmal Warusawithana wrote: > $subject > > -- > Lakmal Warusawithana > Director - Cloud Architecture; WSO2 Inc. > Mobile : +94714289692 > Blog : http://lakmalsview.blogspot.com/ > > -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apach

[jira] [Updated] (STRATOS-651) Add a CLI integration test suite

[ https://issues.apache.org/jira/browse/STRATOS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chris snow updated STRATOS-651: --- Description: I have an integration test suite for the CLI [1]. It currently has about 18 tests, an

is it ok to commit fixes to 4.0.0-incubating branch?

I have some fixes [1,2] that I'm testing on the 4.0.0-incubating branch. If these my tests pass, is it ok for me to commit these fixes to the 4.0.0-incubating branch? --- [1] https://issues.apache.org/jira/browse/STRATOS-649 [2] https://issues.apache.org/jira/browse/STRATOS-650

Re: [Wiki] New web frontend ports?

Hi Michiel, Welcome to the Stratos community. In 4.0 we have introduced a single JVM Stratos distribution hence if you use that set-up, you would end-up have only one server which has Cloud-Controller, Stratos Manager, Auto-scaler, CEP embedded into it. Beside that fact, Auto-scaler didn't have an

Re: Typo in the sample REST API calls' username:password

Hi Nirmal, This is fixed. Thanks for punting that out. I checked all the other REST API pages also. On Wed, May 7, 2014 at 11:39 PM, Nirmal Fernando wrote: > Hi Mari/Praneesha, > > $Subject. Following is just an example, can you please check all the > operations. > > eg: > https://cwiki.apache

Re: [Wiki] New web frontend ports?

On Sun, May 11, 2014 at 1:11 AM, Nirmal Fernando wrote: > Hi Michiel, > > Welcome to the Stratos community. In 4.0 we have introduced a single JVM > Stratos distribution hence if you use that set-up, you would end-up having > only one server which has Cloud-Controller, Stratos Manager, Auto-scaler

Re: [Wiki] New web frontend ports?

Sorry for the delayed response. Due to an apache mailing server issue, now only I've noticed your email. On Sun, May 11, 2014 at 1:12 AM, Nirmal Fernando wrote: > > > > On Sun, May 11, 2014 at 1:11 AM, Nirmal Fernando > wrote: > >> Hi Michiel, >> >> Welcome to the Stratos community. In 4.0 we h

[jira] [Resolved] (STRATOS-650) command line mode does not accept options

[ https://issues.apache.org/jira/browse/STRATOS-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chris snow resolved STRATOS-650. Resolution: Fixed > command line mode does not accept options > --