[jira] [Resolved] (STRATOS-1392) Update stratos-installer with new artifacts

[ https://issues.apache.org/jira/browse/STRATOS-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith resolved STRATOS-1392. -- Resolution: Fixed Fixed in commit 3da25af49119ae1f439cb2506b42d767fe87a99f > Update s

Re: Moving cartridge instance init scripts to a different folder

Thanks Imesh, Will do. On Tue, May 12, 2015 at 10:45 AM, Imesh Gunaratne wrote: > +1 Yes it make more sense to have a separate folder for init scripts. We > could also add a README.md file to describe the purpose. > > Thanks > > On Tue, May 12, 2015 at 8:49 AM, Lahiru Sandaruwan > wrote: > >> H

[Docs] Need verification on LB content

Hi Devs, Can someone please review the content on Load Balancers [1]. This content was written for 4.0.0. Therefore, there is a high possibility that the content may need to be updated. In addition, now that we support NGINX we might have additional information to add to this page. Looking forward

Re: [GCE] [Testing] Verify Stratos with GCE

+ Asanka. On Tue, May 12, 2015 at 6:58 AM, Imesh Gunaratne wrote: > +1 I think Asanka did some experiments with GCE with the GSoC project he > is working on. > > Thanks > > On Tue, May 12, 2015 at 1:05 AM, Lahiru Sandaruwan > wrote: > >> Hi all, >> >> I'm working on $subject. I will update the

Re: [Q] Forcefully undeploying an application

Hi David, Did all the members/instances get terminated when you undeploy forcefully. Or else could you share the complete carbon log. Forceful undeployment invokes graceful undeployment process too, this will take sometime to terminate all instances. So you need to wait till forceful undeployment

Re: Moving cartridge instance init scripts to a different folder

+1 Yes it make more sense to have a separate folder for init scripts. We could also add a README.md file to describe the purpose. Thanks On Tue, May 12, 2015 at 8:49 AM, Lahiru Sandaruwan wrote: > Hi all, > > I think we should do $subject. Those are now in "tools/puppet3-agent/". > > Shall we m

Re: [Error] Can not add properties to an application

Thanks, for your feedback Udara! I will verify this process and document it in Stratos wiki. Regards, Mariangela *--* *Mariangela Hills* PMC Member & Committer of Apache Stratos Senior Technical Writer WSO2, Inc. lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com

[jira] [Resolved] (STRATOS-1380) Incorrect order of message and status code in response

[ https://issues.apache.org/jira/browse/STRATOS-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills resolved STRATOS-1380. --- Resolution: Fixed Fix Version/s: 4.1.0 This error has been fixed by imesh as

[jira] [Updated] (STRATOS-1380) Incorrect order of message and status code in response

[ https://issues.apache.org/jira/browse/STRATOS-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills updated STRATOS-1380: -- Assignee: Imesh Gunaratne > Incorrect order of message and status code in response > -

Re-factoring and verifying Stratos-installer in 4.1.0 - (STRATOS-1390)

Hi devs, I'm in the process of verifying and re-factoring stratos installer tool, which was previously used to setup Stratos in Single JVM and distributed modes. Below JIRA was created to track the progress [1 ]. Following is a quick update on t

[jira] [Updated] (STRATOS-1392) Update stratos-installer with new artifacts

[ https://issues.apache.org/jira/browse/STRATOS-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith updated STRATOS-1392: - Description: cloud-controller.xml, autoscaler.xml, cartridge-config.properties, jndi.pro

Re: Changing REST API method "removeDomainMappings"

Hi Udara, Sorry I have missed the thread you mentioned. Thanks for the response and I will continue with modifying the API method. Thanks On Tue, May 12, 2015 at 9:55 AM, Udara Liyanage wrote: > Hi Dinithi, > > Please refer to the thread which discussed the similar topic in "Do we > allow dele

[jira] [Created] (STRATOS-1396) Update README.md file of Stratos Installer

Lasindu Charith created STRATOS-1396: Summary: Update README.md file of Stratos Installer Key: STRATOS-1396 URL: https://issues.apache.org/jira/browse/STRATOS-1396 Project: Stratos Issue

Re: Issue in undeploying a cartridge

Hi Vishanth, Reka, Dinithi, When I was documenting the samples for wiki. I noticed the following issues. The one that you faced was reproted as a JIRA too [1]. The rest are as follows: (some of the samples might be removed now with he new structure) [1] STRATOS-1276

Re: Issue in undeploying a cartridge

Hi, Fixed the sample and sent a PR[1]. Please review and merge. [1] - https://github.com/apache/stratos/pull/302 Regards, Vishanth On Tue, May 12, 2015 at 9:58 AM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Sorry not when undeploying, its when deleting the application. > > On Tue,

Re: Issue in undeploying a cartridge

Sorry not when undeploying, its when deleting the application. On Tue, May 12, 2015 at 9:56 AM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Hi Reka/Dinithi, > > The application id we passed when undeploying the application is wrong in > the undeploy.sh in "tomcat-single-signon" sample

Re: Issue in undeploying a cartridge

Hi Reka/Dinithi, The application id we passed when undeploying the application is wrong in the undeploy.sh in "tomcat-single-signon" sample. Thats the reason for this issue. I'll fix the sample. Thank you, Vishanth On Mon, May 11, 2015 at 7:02 PM, Reka Thirunavukkarasu wrote: > Hi Vishanth/DI

Re: Changing REST API method "removeDomainMappings"

Hi Dinithi, Please refer to the thread which discussed the similar topic in "Do we allow delete multiple resources in one request" DELETE does not need a payload at all. On Tue, May 12, 2015 at 9:50 AM, Dinithi De Silva wrote: > Hi, > > I am going to do $subject as follows. > > In the current m

Changing REST API method "removeDomainMappings"

Hi, I am going to do $subject as follows. In the current method, we pass the entire json string to remove a domain mapping which is not really necessary. After the modification, we need to send only the application name and the domain name as path parameters to perform the operation. Thanks --

[jira] [Updated] (STRATOS-1391) Remove GREG configurations in Stratos-installer

[ https://issues.apache.org/jira/browse/STRATOS-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith updated STRATOS-1391: - Description: Stratos-installer of 4.1.0-beta2, required WSO2 GREG 4.6.0 distribution (wa

RE: Testing stratos 4.1: cartridge group deployment broken ? ... was ... RE: Validating the service group definition

Ok, thanks From: Imesh Gunaratne [mailto:im...@apache.org] Sent: Monday, May 11, 2015 6:39 PM To: dev Cc: Vishanth Balasubramaniam Subject: Re: Testing stratos 4.1: cartridge group deployment broken ? ... was ... RE: Validating the service group definition Hi Martin, If you have dependencies de

[jira] [Created] (STRATOS-1395) Verify Stratos-installer in a distributed setup

Lasindu Charith created STRATOS-1395: Summary: Verify Stratos-installer in a distributed setup Key: STRATOS-1395 URL: https://issues.apache.org/jira/browse/STRATOS-1395 Project: Stratos I

[jira] [Assigned] (STRATOS-1395) Verify Stratos-installer in a distributed setup

[ https://issues.apache.org/jira/browse/STRATOS-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith reassigned STRATOS-1395: Assignee: Lasindu Charith > Verify Stratos-installer in a distributed setup > ---

[jira] [Created] (STRATOS-1394) Verify Stratos installer in Single JVM setup

Lasindu Charith created STRATOS-1394: Summary: Verify Stratos installer in Single JVM setup Key: STRATOS-1394 URL: https://issues.apache.org/jira/browse/STRATOS-1394 Project: Stratos Issu

[jira] [Created] (STRATOS-1393) Remove unused files in Stratos-installer

Lasindu Charith created STRATOS-1393: Summary: Remove unused files in Stratos-installer Key: STRATOS-1393 URL: https://issues.apache.org/jira/browse/STRATOS-1393 Project: Stratos Issue Ty

[jira] [Assigned] (STRATOS-1391) Remove GREG configurations in Stratos-installer

[ https://issues.apache.org/jira/browse/STRATOS-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith reassigned STRATOS-1391: Assignee: Lasindu Charith > Remove GREG configurations in Stratos-installer > ---

[jira] [Resolved] (STRATOS-1391) Remove GREG configurations in Stratos-installer

[ https://issues.apache.org/jira/browse/STRATOS-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasindu Charith resolved STRATOS-1391. -- Resolution: Fixed Fixed in commit 15a5f80027916477e8a7881ff19aee5e66397a96 > Remove G

[jira] [Created] (STRATOS-1392) Update stratos-installer with new artifacts

Lasindu Charith created STRATOS-1392: Summary: Update stratos-installer with new artifacts Key: STRATOS-1392 URL: https://issues.apache.org/jira/browse/STRATOS-1392 Project: Stratos Issue

[jira] [Created] (STRATOS-1391) Remove GREG configurations in Stratos-installer

Lasindu Charith created STRATOS-1391: Summary: Remove GREG configurations in Stratos-installer Key: STRATOS-1391 URL: https://issues.apache.org/jira/browse/STRATOS-1391 Project: Stratos I

[jira] [Created] (STRATOS-1390) Refactor and test stratos-installer for 4.1.0

Lasindu Charith created STRATOS-1390: Summary: Refactor and test stratos-installer for 4.1.0 Key: STRATOS-1390 URL: https://issues.apache.org/jira/browse/STRATOS-1390 Project: Stratos Iss

Re: [Error] Can not add properties to an application

Hi Mari, I could n't mention that you can not access metadata API without the token. There are two ways to obtain the token, which is created for the app and passed as payload into the instance. Either loginto the instance and obtain the token or, enable debug logs to view the payload. I am wonder

Moving cartridge instance init scripts to a different folder

Hi all, I think we should do $subject. Those are now in "tools/puppet3-agent/". Shall we move them to "tools/init-scripts"? Thanks. -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +9477332

Re: Testing stratos 4.1: cartridge group deployment broken ? ... was ... RE: Validating the service group definition

Hi Martin, If you have dependencies defined in the cartridge group you might need to change the syntax to the new format. Please refer one of the samples in the samples folder or the other mail thread where we are discussing it. Thanks On Tue, May 12, 2015 at 3:30 AM, Martin Eppel (meppel) wrot

Re: [Error] Can not add properties to an application

Hi Mari, I will have a look. On 11 May 2015 10:17 pm, "Mariangela Hills" wrote: > Hi Vishanth, > > I executed the REST API command using the new JSON definition, but I still > get an error. > > MariH:Master-branch Admin16$ curl -X POST -H "Content-Type: > application/json" -d @'property.json' -k

Re: [Error] Can not add properties to an application

It looks like we need to refine the response messages and other bean classes used in the metadata API. It's not using the same conventions we have used in the REST API. On Mon, May 11, 2015 at 10:17 PM, Mariangela Hills wrote: > Hi Vishanth, > > I executed the REST API command using the new JSON

Re: [GCE] [Testing] Verify Stratos with GCE

+1 I think Asanka did some experiments with GCE with the GSoC project he is working on. Thanks On Tue, May 12, 2015 at 1:05 AM, Lahiru Sandaruwan wrote: > Hi all, > > I'm working on $subject. I will update the progress as i continue. > > BTW. Has anyone done it recently? > > Thanks. > > -- > --

Re: [Discuss] Fixing Comma Separated Dependency JSON Definitions

Hi Shaheed, I'm sorry I did not get what you mean. Do you think we need to avoid using the "aliases" attribute and make the syntax as below? { "startupOrders":[ [ "cartridge.oracle1", "cartridge.cassandra1", "cartridge.tomcat1" ], [ "cartri

[jira] [Resolved] (STRATOS-1365) Remove "Active" option in the page for new tenant addition

[ https://issues.apache.org/jira/browse/STRATOS-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dakshika Jayathilaka resolved STRATOS-1365. --- Resolution: Fixed Fix Version/s: (was: 4.1.0 RC1) fixed with comm

[jira] [Resolved] (STRATOS-1384) REST API return does not match on GUI logic

[ https://issues.apache.org/jira/browse/STRATOS-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dakshika Jayathilaka resolved STRATOS-1384. --- Resolution: Fixed fixed with commit dbf7d596176d4de49e547036171e76b7e78bdc83

[jira] [Commented] (STRATOS-1384) REST API return does not match on GUI logic

[ https://issues.apache.org/jira/browse/STRATOS-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539033#comment-14539033 ] Dakshika Jayathilaka commented on STRATOS-1384: --- Hi Udara, above {"messag

[jira] [Resolved] (STRATOS-1385) Implement update feature for each configuration component

[ https://issues.apache.org/jira/browse/STRATOS-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dakshika Jayathilaka resolved STRATOS-1385. --- Resolution: Fixed fixed with commit 4dfd8f9b2d7288049e75a8637e1c45e9a01a77d7

RE: [Discuss] Fixing Comma Separated Dependency JSON Definitions

I’m confused by the new syntax. Originally, startup orders were pairs of comma separated strings, “A, B” implying an order between A and B, and that the change was simply to make it [“A”, “B”]. What does it mean when you have [“A”, “B”, “C”]: 1. Is the order A then B then C? 2. Is t

[GCE] [Testing] Verify Stratos with GCE

Hi all, I'm working on $subject. I will update the progress as i continue. BTW. Has anyone done it recently? Thanks. -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +94773325954 email: lah

Re: [Error] Can not add properties to an application

Hi Vishanth, I executed the REST API command using the new JSON definition, but I still get an error. MariH:Master-branch Admin16$ curl -X POST -H "Content-Type: application/json" -d @'property.json' -k -v -u admin:admin https://localhost:9443/metadata/api/application/wordpress/properties > POST

Re: Modification : Deploy with automated scripts page

Hi, In a real world scenarios we can not expect to use a fresh pack every time. Users may have others changes such as deployed cartridges, applications etc.

Re: [Error] Can not add properties to an application

Hi Mari, Correct format is the one Vishanth mentioned On 11 May 2015 8:32 pm, "Vishanth Balasubramaniam" wrote: > Hi Mari, > > It should be as follows. > [ >{ > "key":"wka5", > "values":"192.163.4.2" >}, >{ > "key":"wka6", > "values":"192.163.6.6" >} > ] >

[GitHub] stratos pull request: Fixing the samples

GitHub user Vishanth opened a pull request: https://github.com/apache/stratos/pull/302 Fixing the samples Fixing the samples You can merge this pull request into a Git repository by running: $ git pull https://github.com/Vishanth/stratos samples Alternatively you can review a

Re: [Error] Can not add properties to an application

Hi Mari, It should be as follows. [ { "key":"wka5", "values":"192.163.4.2" }, { "key":"wka6", "values":"192.163.6.6" } ] Regards, Vishanth On Mon, May 11, 2015 at 7:49 PM, Mariangela Hills wrote: > Hi Devs, > > I was trying to add properties to an applicati

[Error] Can not add properties to an application

Hi Devs, I was trying to add properties to an application (POST /metadata/api/application//properties) and got an error [1]. There were no corresponding log files printed. I used [2] as the JSON. [1] MariH:Master-branch Admin16$ curl -X POST -H "Content-Type: application/json" -d @'meta.json' -

[jira] [Comment Edited] (STRATOS-1387) Validate Startup Order and Dependency Scaling Prefixes at Group Deployment

[ https://issues.apache.org/jira/browse/STRATOS-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537823#comment-14537823 ] Isuru Haththotuwa edited comment on STRATOS-1387 at 5/11/15 1:40 PM: -

Re: Issue in undeploying a cartridge

Hi Vishanth/DInithi, I also got the same issue when checking on tomcat-single-signon. Seems some reference to applicaiton didn't get removed properly. Thanks, Reka On Mon, May 11, 2015 at 6:49 PM, Reka Thirunavukkarasu wrote: > Hi Vishanth, > > Will check that sample. I have tested five-levels

[jira] [Created] (STRATOS-1389) Message not returned for Metadata service APIs

Mariangela Hills created STRATOS-1389: - Summary: Message not returned for Metadata service APIs Key: STRATOS-1389 URL: https://issues.apache.org/jira/browse/STRATOS-1389 Project: Stratos

Re: Issue in undeploying a cartridge

Hi Vishanth, Will check that sample. I have tested five-levels-nested-groups-app and it worked fine.. Thanks, Reka On Mon, May 11, 2015 at 6:45 PM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Hi Reka, > > I deployed "tomcat-single-signon" using the deploy script in the mock-iaas > a

[Discuss] Apache Stratos 4.1.0 GA Release Preparation

Hi Devs, IMO we are now in a good position to finalize 4.1.0 GA release. Please use this mail thread to discuss the remaining issues and take necessary steps to prepare the first release candidate. @Lahiru: Would you like to be the release manager for this release? [1] https://cwiki.apache.org/c

Re: Issue in undeploying a cartridge

Hi Reka, I deployed "tomcat-single-signon" using the deploy script in the mock-iaas and undeployed using the undeploy script. Attached the log when running the undeploy script. Regards, Vishanth On Mon, May 11, 2015 at 6:37 PM, Dinithi De Silva wrote: > Hi Vishanth, > > I got the same problem

Re: Issue in undeploying a cartridge

Hi Vishanth, I got the same problem when trying to undeploy "tomcat-single-signon" application using undeploy.sh script. Did you also try with the same way? Thanks. On Mon, May 11, 2015 at 6:15 PM, Reka Thirunavukkarasu wrote: > Hi > > I have just tried with that sample and Deployment and unde

Re: Issue in undeploying a cartridge

Hi Vishanth, Can you please attach the Complete log for the deployment and undeployment? Thanks, Reka On Mon, May 11, 2015 at 5:58 PM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Hi Devs, > > While testing the sample application I identified that there is an issue > in undeploying a

Re: Issue in undeploying a cartridge

Hi I have just tried with that sample and Deployment and undeployment are working as expected. Can you please try again and see or can you share the steps that you are trying? Thanks, Reka On Mon, May 11, 2015 at 6:09 PM, Reka Thirunavukkarasu wrote: > Hi Vishanth, > > Can you please attach th

[jira] [Updated] (STRATOS-1355) Cannot see/add groups under another group in GUI

[ https://issues.apache.org/jira/browse/STRATOS-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandaruwan updated STRATOS-1355: --- Priority: Blocker (was: Major) > Cannot see/add groups under another group in GUI >

Re: Modification : Deploy with automated scripts page

Hi Mari/Udara, Yah..Stratos restart has been fixed in master. There can be some edge cases which might need to handle. So, we can ask the user to clean the distribution if they get into some error state which they couldn't get it working and only if they need a quick fix. This is applicable only w

Re: Issue in single-group-app sample

I also noticed this problem while running with DEBUG enabled. On Mon, May 11, 2015 at 5:34 PM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > I did run again and it seems fine now. It could be an intermittent issue > or maybe resolved by updating my source. > > Regards, > Vishanth > > On

Re: Sequential order of the REST API response message and status code is incorrect

Hi Devs, I just fixed the above issue in all the API methods and exception handlers. Now the API only returns the below response message format unless it is a data set: { "status" : "[success|error]", "message" : "" } Thanks On Mon, May 11, 2015 at 1:53 PM, Mariangela Hills wrote: > T

Issue in undeploying a cartridge

Hi Devs, While testing the sample application I identified that there is an issue in undeploying a cartridge when a cartridge-group has more than 1 cartridge. As you can see in the provided error log [3]. Will be able to reproduce by deploying the tomcat-single-signon [1] or five-levels-nested-gr

[jira] [Resolved] (STRATOS-1379) REST API /cartridges not return the list

[ https://issues.apache.org/jira/browse/STRATOS-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Sandaruwan resolved STRATOS-1379. Resolution: Fixed Fixed in e7cbd33e8736e6e44d9df8d16985e37deaf71eeb. > REST API

Re: Registry issue when persisting topology

Please refer the document[1] [1] http://dev.mysql.com/doc/innodb/1.1/en/innodb-other-changes-innodb_lock_wait_timeout.html Thanks, Gayan On Mon, May 11, 2015 at 5:21 PM, Udara Liyanage wrote: > Hi Gayan, > > Nope I haven't tries that. Could you please point me to the configuration > to be modi

Re: Issue in single-group-app sample

I did run again and it seems fine now. It could be an intermittent issue or maybe resolved by updating my source. Regards, Vishanth On Mon, May 11, 2015 at 1:56 PM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Hi, > > When testing the samples in mock IaaS with single-group-app[1], I w

Re: Validating Startup and Scaling Dependency Prefixes at Group Deployment Time

+1 for validating it in the service deployment as well. Do we have a validation against the alias for startupOrder which defined in the service group when deploying application? Thanks, Reka On Mon, May 11, 2015 at 4:45 PM, Isuru Haththotuwa wrote: > Fixed in commit b0ef0ccf3491610cf5fbec10b40e

Re: Registry issue when persisting topology

Hi Gayan, Nope I haven't tries that. Could you please point me to the configuration to be modified? On Mon, May 11, 2015 at 5:03 PM, Gayan Gunarathne wrote: > [2015-05-11 09:37:43,396] ERROR > {org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO} - *Failed to > delete the resource with id

Re: [Discuss] How to handle errors at server side in AS/CC services

On Sun, May 10, 2015 at 11:00 PM, Chamila De Alwis wrote: > Hi Lahiru, > On Sun, May 10, 2015 at 8:56 PM, Lahiru Sandaruwan > wrote: > >> So what we need to do at Stratos Rest API(The API we have now), is to >> catch the status code and message from CC Rest API and send both, as they >> are, to

Re: Registry issue when persisting topology

[2015-05-11 09:37:43,396] ERROR {org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO} - *Failed to delete the resource with id 386. Lock wait timeout exceeded; try restarting transaction* java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction What is the current lock wai

Re: Validating Startup and Scaling Dependency Prefixes at Group Deployment Time

Fixed in commit b0ef0ccf3491610cf5fbec10b40e955fa31823d3. On Mon, May 11, 2015 at 2:33 PM, Udara Liyanage wrote: > +1 > > On Mon, May 11, 2015 at 2:05 PM, Isuru Haththotuwa > wrote: > >> Hi Devs, >> >> In [1, 2], we have code explicitly depending on two prefixes used for >> startup order and sc

[jira] [Created] (STRATOS-1388) Incorrect location header URL format - POST /application//property

Mariangela Hills created STRATOS-1388: - Summary: Incorrect location header URL format - POST /application//property Key: STRATOS-1388 URL: https://issues.apache.org/jira/browse/STRATOS-1388 Projec

[jira] [Commented] (STRATOS-1387) Validate Startup Order and Dependency Scaling Prefixes at Group Deployment

[ https://issues.apache.org/jira/browse/STRATOS-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537823#comment-14537823 ] Isuru Haththotuwa commented on STRATOS-1387: Fixed in commit b0ef0ccf3491610

[jira] [Resolved] (STRATOS-1387) Validate Startup Order and Dependency Scaling Prefixes at Group Deployment

[ https://issues.apache.org/jira/browse/STRATOS-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa resolved STRATOS-1387. Resolution: Fixed > Validate Startup Order and Dependency Scaling Prefixes at Grou

[jira] [Updated] (STRATOS-1387) Validate Startup Order and Dependency Scaling Prefixes at Group Deployment

[ https://issues.apache.org/jira/browse/STRATOS-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa updated STRATOS-1387: --- Description: In [1, 2], we have code explicitly depending on two prefixes used for s

[jira] [Updated] (STRATOS-1387) Validate Startup Order and Dependency Scaling Prefixes at Group Deployment

[ https://issues.apache.org/jira/browse/STRATOS-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Haththotuwa updated STRATOS-1387: --- Description: In [1, 2], we have code explicitly depending on two prefixes used for s

[jira] [Created] (STRATOS-1387) Validate Startup Order and Dependency Scaling Prefixes at Group Deployment

Isuru Haththotuwa created STRATOS-1387: -- Summary: Validate Startup Order and Dependency Scaling Prefixes at Group Deployment Key: STRATOS-1387 URL: https://issues.apache.org/jira/browse/STRATOS-1387

Re: Registry issue when persisting topology

Hi, With MySQL, however frequency of getting the exception is lower. If I restart Stratos at this point, the error does not exist. On Mon, May 11, 2015 at 3:11 PM, Udara Liyanage wrote: > Hi Isuru, > > Even with MySQL, similar issue seems to exist > > in started successfully > [2015-05-11 09:36

Re: Registry issue when persisting topology

Hi Isuru, Even with MySQL, similar issue seems to exist in started successfully [2015-05-11 09:36:43,786] INFO {org.apache.stratos.autoscaler.client.CloudControllerClient} - Trying to spawn an instance via cloud controller: [cluster] single-cartridge-app.my-as-manager.appserver-manager.domain [

Re: Modification : Deploy with automated scripts page

Hi Mari, I remember Reka was fixing restart issues recently. If Stratos restart works fine, we no longer need this warning. On Mon, May 11, 2015 at 2:58 PM, Mariangela Hills wrote: > Thanks, for your feedback Udara! > > Initially, when working on the Mock IaaS, there were issues where I ended

Re: Modification : Deploy with automated scripts page

Thanks, for your feedback Udara! Initially, when working on the Mock IaaS, there were issues where I ended up having to delete the current distribution and get a fresh pack. I haven't run into this issue lately, so I think it is safe to think that this note can be deleted. WDYT? Will there be situ

Re: Validating Startup and Scaling Dependency Prefixes at Group Deployment Time

+1 On Mon, May 11, 2015 at 2:05 PM, Isuru Haththotuwa wrote: > Hi Devs, > > In [1, 2], we have code explicitly depending on two prefixes used for > startup order and scaling order, *'cartridge.*' and '*group.'* .IMHO we > should validate this at Service Group deployment time, since otherwise > s

Validating Startup and Scaling Dependency Prefixes at Group Deployment Time

Hi Devs, In [1, 2], we have code explicitly depending on two prefixes used for startup order and scaling order, *'cartridge.*' and '*group.'* .IMHO we should validate this at Service Group deployment time, since otherwise startup order / scaling will not work as expected. Currently its possible to

Modification : Deploy with automated scripts page

Hi Mari, 1) A user might have to do some initial configurations to artifacts before just executing sample unless he selects mock IaaS. Say if he selected Openstack, keys, security groups, networks etc. We need to mention them. 2) Is this due to an bug, I mean does n't restart work? When starting

Issue in single-group-app sample

Hi, When testing the samples in mock IaaS with single-group-app[1], I was able to see the application is *deploying successfully* but the following exception is in the log. [2015-05-11 13:45:02,870] INFO > {org.apache.stratos.autoscaler.event.receiver.topology.AutoscalerTopologyEventReceiver} >

Re: Sequential order of the REST API response message and status code is incorrect

Thanks, for the clarification everyone! Regards, Mariangela *--* *Mariangela Hills* PMC Member & Committer of Apache Stratos Senior Technical Writer WSO2, Inc. lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com On Mon, May 11, 2015 at 1:11 PM, Imesh Gun

[GitHub] stratos pull request: Correcting the logs

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

Re: [Discuss] Nginx Load Balancer Extension

Thanks Lakmal, yes that was my mistake I should have added it earlier. Thanks On Mon, May 11, 2015 at 8:25 AM, Lakmal Warusawithana wrote: > since this is not affect to Stratos core I'm +1. But better next time to > have these features into alpha and not to add features after that. > > On Fri,

Re: Sequential order of the REST API response message and status code is incorrect

Hi Martin, Yes this change will remain, however we will be removing statusCode attribute and adding a new attribute called status. This will contain either "successful" or "error". Thanks On Mon, May 11, 2015 at 4:39 AM, Martin Eppel (meppel) wrote: > Question along the same lines, in a recen

[GitHub] stratos pull request: Cartridge group validation

Github user Vishanth commented on a diff in the pull request: https://github.com/apache/stratos/pull/296#discussion_r30017859 --- Diff: components/org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/api/StratosApiV41Utils.java --- @@ -3200,4 +3202,124 @

Re: Validating the service group definition

Thanks Vishanth! I have now merged this PR to master branch. On Mon, May 11, 2015 at 11:15 AM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Hi Imesh, > > Followed the feedback and made the changes to the PR wherever needed. > Please merge the PR [1]. > > [1] - https://github.com/apach

[GitHub] stratos pull request: Correcting the logs

GitHub user Vishanth opened a pull request: https://github.com/apache/stratos/pull/301 Correcting the logs Correcting the logs WRT to comment mentioned in #296 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Vishanth/stratos corr