Re: can't build latest code, anyone else seeing this ?

Hi Martin, I fixed the failure by adding the feature. I have missed it when committing. On Sat, Dec 6, 2014 at 1:26 AM, Reka Thirunavukkarasu wrote: > I have commented out the feature from p2-profile-gen as well and committed > in fc5548960893c99762668ddc3471ff3641b42638. > > > > On Sat, Dec 6,

Re: Assigning floating IPs to any interfaces of our choice

Doc - https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Multiple+Network+Interfaces On Sat, Dec 6, 2014 at 9:09 AM, Rajkumar Rajaratnam wrote: > Multiple network interfaces support[1] now available in master branch. > > 1. https://issues.apache.org/jira/browse/STRATOS-698 > > Thanks. > >

Re: [Discuss] Stratos 4.1.0 Alpha Release Plan

On Wed, Dec 3, 2014 at 1:59 PM, Mariangela Hills wrote: > Hi Raj, > > As requested, I have added information on multiple network interfaces in > [1]. > Thanks Mari. Looks good. Thanks. > > [1] > https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Multiple+Network+Interfaces > > Regards,

[jira] [Commented] (STRATOS-698) Cannot assign floating IPs to any interface other than the first

[ https://issues.apache.org/jira/browse/STRATOS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236563#comment-14236563 ] Rajkumar Rajaratnam commented on STRATOS-698: - Doc - https://cwiki.apache.or

[jira] [Commented] (STRATOS-698) Cannot assign floating IPs to any interface other than the first

[ https://issues.apache.org/jira/browse/STRATOS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236561#comment-14236561 ] Matt Turner commented on STRATOS-698: - Thank you for your message, however I am on ho

Re: Assigning floating IPs to any interfaces of our choice

Multiple network interfaces support[1] now available in master branch. 1. https://issues.apache.org/jira/browse/STRATOS-698 Thanks. On Thu, Nov 20, 2014 at 11:34 AM, Rajkumar Rajaratnam wrote: > In the current code base also, we are considering the first private IP of > the member in LB. > > O

[jira] [Resolved] (STRATOS-698) Cannot assign floating IPs to any interface other than the first

[ https://issues.apache.org/jira/browse/STRATOS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajkumar Rajaratnam resolved STRATOS-698. - Resolution: Fixed Fix Version/s: 4.1.0 Alpha > Cannot assign floating IPs

[jira] [Commented] (STRATOS-698) Cannot assign floating IPs to any interface other than the first

[ https://issues.apache.org/jira/browse/STRATOS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236560#comment-14236560 ] Rajkumar Rajaratnam commented on STRATOS-698: - Committed in def7d3f149b83feb

[jira] [Commented] (STRATOS-1002) Upgrade to Jclouds 1.8.1

[ https://issues.apache.org/jira/browse/STRATOS-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236557#comment-14236557 ] Rajkumar Rajaratnam commented on STRATOS-1002: -- Switched to jclouds 1.8.1 i

[jira] [Resolved] (STRATOS-1002) Upgrade to Jclouds 1.8.1

[ https://issues.apache.org/jira/browse/STRATOS-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajkumar Rajaratnam resolved STRATOS-1002. -- Resolution: Fixed > Upgrade to Jclouds 1.8.1 > > >

RE: Global Deployment Policy for the Application

One more question, in the deployment_policy.json there is a filed "applicationId": "test_app_os4", – does it have to match up with the applicationId of the application where it is used or is it arbitrarily ? Also, where is the deployment policy referenced – I would have expect it in the subscri

RE: Global Deployment Policy for the Application

Hi Reka, I was looking at the attached samples and had a few questions: Did we change the group format ? In the sample you sent out there is a group6 and group7 defined. What is the meaning of the cartridges (“tomcat1”) section in the groups section for “group7”, see below ? Don’t we have to de

Re: Shall we rename stratosmetadataservice web app

As metadata is one word [1], how about using the following: /metadata/api [1] http://en.wikipedia.org/wiki/Metadata Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. w: http://wso2.com On Fri, Dec 5, 2014 at

Re: can't build latest code, anyone else seeing this ?

I have commented out the feature from p2-profile-gen as well and committed in fc5548960893c99762668ddc3471ff3641b42638. On Sat, Dec 6, 2014 at 12:34 AM, Reka Thirunavukkarasu wrote: > Sorry for the false message..It is failing now in p2 repo generation. > Seems that just commented out won't wo

RE: Global Deployment Policy for the Application

Thanks Reka, From: Reka Thirunavukkarasu [mailto:r...@wso2.com] Sent: Friday, December 05, 2014 11:43 AM To: dev Subject: Re: Global Deployment Policy for the Application Hi Martin, I have attached here with the sample application definition and the deployment policy. Could you please have a

Re: Global Deployment Policy for the Application

Please don't specify max/min in the group definition. It should be specified in the application as in group level/cartridge level appropriately. Please see the correct group definition as inline: { "name": "group6", "groups": [ { "name": "group7", "cartridge

RE: Global Deployment Policy for the Application

In 4.0 we had a min parameter in the partition definition (see example below, highlighted), is it still supported in the new format ? In 4.0: "id": "static-1-Core", "partitionGroup": { "id": "N1", "partition": [ { "id": "RegionOne-Core",

Re: can't build latest code, anyone else seeing this ?

Sorry for the false message..It is failing now in p2 repo generation. Seems that just commented out won't work..Will fix it properly and update the thread.. On Sat, Dec 6, 2014 at 12:27 AM, Reka Thirunavukkarasu wrote: > Hi > > Yah..I have commented out that feature for now..Now it is building..

Re: can't build latest code, anyone else seeing this ?

Hi Yah..I have commented out that feature for now..Now it is building..Please take the update.. @Udara, can you add the feature and update the relevant places? Thanks, Reka On Sat, Dec 6, 2014 at 12:20 AM, Lahiru Sandaruwan wrote: > I also got this, > > It seems "org.apache.stratos.custom.han

Re: can't build latest code, anyone else seeing this ?

I also got this, It seems "org.apache.stratos.custom.handlers.feature" feature is not there in common directory. On Sat, Dec 6, 2014 at 12:08 AM, Reka Thirunavukkarasu wrote: > Hi Martin, > > I will check on this and update you.. > > Thanks, > Reka > > On Fri, Dec 5, 2014 at 11:51 PM, Martin Ep

Re: can't build latest code, anyone else seeing this ?

Hi Martin, I will check on this and update you.. Thanks, Reka On Fri, Dec 5, 2014 at 11:51 PM, Martin Eppel (meppel) wrote: > Just pulled the latest code from the master and get the following error, > anyone else seeing this ? Should I hold off for the moment as the master > might be unstable

can't build latest code, anyone else seeing this ?

Just pulled the latest code from the master and get the following error, anyone else seeing this ? Should I hold off for the moment as the master might be unstable ? Thanks Martin [INFO] Scanning for projects... [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The proj

Re: Reference mispatch in gce dependency

Okay. Seems you didn't commit the changes :) Thanks Udara for finding this out. Thanks. On Fri, Dec 5, 2014 at 11:10 PM, Udara Liyanage wrote: > Hi Raj, > > Both you and me have done the same fix. > > On Fri, Dec 5, 2014 at 11:10 PM, Udara Liyanage wrote: > >> Hi, >> >> Fixed it now >> >> On

Re: Reference mispatch in gce dependency

Hi Raj, Both you and me have done the same fix. On Fri, Dec 5, 2014 at 11:10 PM, Udara Liyanage wrote: > Hi, > > Fixed it now > > On Fri, Dec 5, 2014 at 11:08 PM, Rajkumar Rajaratnam > wrote: > >> CC feature was using gce 1.8.0. Fixed it now. >> >> Thanks. >> >> On Fri, Dec 5, 2014 at 11:01 PM

Re: Reference mispatch in gce dependency

Hi, Fixed it now On Fri, Dec 5, 2014 at 11:08 PM, Rajkumar Rajaratnam wrote: > CC feature was using gce 1.8.0. Fixed it now. > > Thanks. > > On Fri, Dec 5, 2014 at 11:01 PM, Udara Liyanage wrote: > >> Hi Raj, >> >> I got the following error when doing a clean build. This seems to be due >> to

Re: Reference mispatch in gce dependency

CC feature was using gce 1.8.0. Fixed it now. Thanks. On Fri, Dec 5, 2014 at 11:01 PM, Udara Liyanage wrote: > Hi Raj, > > I got the following error when doing a clean build. This seems to be due > to recent version change. > > > Failed to execute goal on project > org.apache.stratos.cloud.con

Reference mispatch in gce dependency

Hi Raj, I got the following error when doing a clean build. This seems to be due to recent version change. Failed to execute goal on project org.apache.stratos.cloud.controller.feature: Could not resolve dependencies for project org.apache.stratos:org.apache.stratos.cloud.controller.feature:pom

[jira] [Created] (STRATOS-1025) NPE when deployment policy applicationId is wrong

Udara Liyanage created STRATOS-1025: --- Summary: NPE when deployment policy applicationId is wrong Key: STRATOS-1025 URL: https://issues.apache.org/jira/browse/STRATOS-1025 Project: Stratos I

Re: Topology changes needed

Hi, I am attaching the patch for topology changes. @Chamila, Please do the changes in python agent accordingly. Basic idea is that topology and topology events are carrying - list of private IPs - list of public IPs - a default public IP (for LB routing) - a default private IP (for

Re: Shall we rename stratosmetadataservice web app

Shall we use /meta-data/api On Fri, Dec 5, 2014 at 11:14 AM, Udara Liyanage wrote: > Hi, > > Stratos REST API is used by clients (CLI,UI and curl) to manage stratos > system. However metadata API is supposed to used by cartridge agents to > publish and fetch metadata across application instances

Re: Are we still supporting java agent?

I updated java agent as well. Thanks. On Fri, Dec 5, 2014 at 2:21 PM, Rajkumar Rajaratnam wrote: > Hi all, > > So if we some changes to other components such as topology, do we have to > fix the corresponding changes in java agent also? > > Or can we comment java agent component from components

[GitHub] stratos pull request: Changes for group monitor on the event of ap...

Github user shirolk commented on the pull request: https://github.com/apache/stratos/pull/137#issuecomment-65773622 Thank you for merging Lahiru ! --- 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 h

[GitHub] stratos pull request: Changes for group monitor on the event of ap...

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

Re: Are we still supporting java agent?

Hi all, So if we some changes to other components such as topology, do we have to fix the corresponding changes in java agent also? Or can we comment java agent component from components/pom xml to avoid build failures? Thanks. On Fri, Dec 5, 2014 at 2:17 PM, Lakmal Warusawithana wrote: > > >

Re: Upgrading identity.xml

Hi, I think we have to maintain that. On Fri, Dec 5, 2014 at 1:10 PM, Isuru Haththotuwa wrote: > > > On Fri, Dec 5, 2014 at 12:06 PM, Udara Liyanage wrote: > >> Hi, >> >> It seems we are getting the identity.xml from carbon.core feature. >> However there are additional files in below places. >

Re: Are we still supporting java agent?

Hi, IMO is we should keep it at the movement. We can remove it in next releases but not in this. Thanks ! On Fri, Dec 5, 2014 at 2:12 PM, Akila Ravihansa Perera wrote: > Hi, > > On Fri, Dec 5, 2014 at 12:57 PM, Rajkumar Rajaratnam > wrote: > >> Yeah, let's remove the java agent from our code

Re: Are we still supporting java agent?

On Fri, Dec 5, 2014 at 2:16 PM, Isuru Perera wrote: > Yes, remove the Java agent in a future release, not in immediate release. > +1 > > On Fri, Dec 5, 2014 at 2:12 PM, Akila Ravihansa Perera > wrote: > >> Hi, >> >> On Fri, Dec 5, 2014 at 12:57 PM, Rajkumar Rajaratnam >> wrote: >> >>> Yeah,

Re: Are we still supporting java agent?

On Fri, Dec 5, 2014 at 2:12 PM, Akila Ravihansa Perera wrote: > Hi, > > On Fri, Dec 5, 2014 at 12:57 PM, Rajkumar Rajaratnam > wrote: > >> Yeah, let's remove the java agent from our code base. >> > > I'm -1 on removing Java agent code. We can deprecate it for now. Perhaps > the need might arise

Re: Are we still supporting java agent?

Yes, remove the Java agent in a future release, not in immediate release. On Fri, Dec 5, 2014 at 2:12 PM, Akila Ravihansa Perera wrote: > Hi, > > On Fri, Dec 5, 2014 at 12:57 PM, Rajkumar Rajaratnam > wrote: > >> Yeah, let's remove the java agent from our code base. >> > > I'm -1 on removing Ja

Re: Are we still supporting java agent?

Hi, On Fri, Dec 5, 2014 at 12:57 PM, Rajkumar Rajaratnam wrote: > Yeah, let's remove the java agent from our code base. > I'm -1 on removing Java agent code. We can deprecate it for now. Perhaps the need might arise in future. > > Thanks. > > On Fri, Dec 5, 2014 at 12:07 PM, Lakmal Warusawith