Re: Python CLI Improvements

Hi Imesh, No, I've only pushed this to stratos-4.1.x branch. I thought we were going to rebase to master after this release. Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Tue, Nov 10, 2015 at 3:53 A

[jira] [Assigned] (STRATOS-1601) Error in CLI commands given for 'help' - Python CLI tool

[ https://issues.apache.org/jira/browse/STRATOS-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chamila de Alwis reassigned STRATOS-1601: - Assignee: Chamila de Alwis > Error in CLI commands given for 'help' - Python CL

Re: [Dev] Publishing Complete Topology event on Demand

On Tue, Nov 10, 2015 at 8:42 AM, Akila Ravihansa Perera wrote: > Hi, > > I've updated Python agent to use this method to initialize the topology. > Also extended the same logic to initialize complete application model. > > @Imesh: Sure, will do a thorough test before merging. > > @Isuru: I think

Re: [Dev] Publishing Complete Topology event on Demand

Hi, I've updated Python agent to use this method to initialize the topology. Also extended the same logic to initialize complete application model. @Imesh: Sure, will do a thorough test before merging. @Isuru: I think we cannot get rid of complete topology synchronization task (periodically publ

Re: [Dev] Publishing Complete Topology event on Demand

Great work Akila. Just to clarify, are we removing the Complete Topology event and its usages? On Tue, Nov 10, 2015 at 4:16 AM, Imesh Gunaratne wrote: > Great work Akila! > > Please do a thorough test and make sure everything is covered before > pushing this change to the current code base. If n

Re: NPE after Re-Deploying the Cartridges

Hi Imesh, As per the discussion in the thread, the final fix I did was removing the logic that is doing the validation is parallel and doing it in sequentially. On Tue, Nov 10, 2015 at 3:52 AM, Imesh Gunaratne wrote: > A great finding Isuru! I didn't get the fix you have proposed. Can you > ple

Jenkins build is back to stable : Stratos-41x-Commit-Build #130

See

Jenkins build is back to stable : Stratos-41x-Commit-Build » Apache Stratos - Integration Tests #130

See

Re: Integration tests for metadata service

On Sat, Nov 7, 2015 at 1:56 PM, Akila Ravihansa Perera wrote: > > I modified the mock iaas component to pass the payload string to the mock > instance. Also added a new API method to mock iaas API to return the > payload string. In the test case, it will retrieve the access token from > the paylo

Re: [Dev] Publishing Complete Topology event on Demand

Great work Akila! Please do a thorough test and make sure everything is covered before pushing this change to the current code base. If not I would like to suggest to push this to the next major release. Thanks On Sun, Nov 8, 2015 at 10:35 PM, Akila Ravihansa Perera wrote: > Hi all, > > I took

Re: ComponentStartUpSynchronizer: CC and AS components are waiting for SM to be activated?

Hi Akila, Yes as I can recall this logic was introduced as a part of the component synchronization process to make sure that topology and application managers get initialized soon after SM gets activated. Otherwise once SM becomes active the Stratos API will be accessible to the endusers and it wo

Re: Error while undeploying an app on Kubernetes

Yes, it looks like the Kubernetes cluster has been removed before the above instance get terminated. Currently there is no validation to avoid this situation. We may need to fix this. Thanks On Mon, Nov 9, 2015 at 9:10 AM, Akila Ravihansa Perera wrote: > Hi Pubudu, > > Yes, I used the undeploy

Re: Python CLI Improvements

Great work Chamila! Have we committed this to the master branch? Thanks On Mon, Nov 9, 2015 at 8:42 AM, Chamila De Alwis wrote: > Hi Devs, > > I've done the following improvements to the Python CLI. > > >1. Improved package structure by packing the Python files and a >stratos.sh bash st

Re: NPE after Re-Deploying the Cartridges

A great finding Isuru! I didn't get the fix you have proposed. Can you please explain it bit further? Thanks On Mon, Nov 9, 2015 at 11:32 AM, Isuru Haththotuwa wrote: > > > On Mon, Nov 9, 2015 at 12:17 PM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Nice catch Isuru! >> >> There

[jira] [Updated] (STRATOS-1544) Topology Initialization Optimization

[ https://issues.apache.org/jira/browse/STRATOS-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila updated STRATOS-1544: --- Affects Version/s: 4.0.0 4.1.3 4.1.4 Fix Version/s: 4.1

[jira] [Updated] (STRATOS-1544) Topology Initialization Optimization

[ https://issues.apache.org/jira/browse/STRATOS-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila updated STRATOS-1544: --- Affects Version/s: 4.1.0 4.1.1 > Topology Initialization Optimization > -

Re: NPE after Re-Deploying the Cartridges

On Mon, Nov 9, 2015 at 12:17 PM, Akila Ravihansa Perera wrote: > Nice catch Isuru! > > There is a JIRA already reported [1] for this issue. I've marked it as a > duplicate. > > Shall we get rid of this PartitionValidatorCallable class? I think it > adds unnecessary complexity to validation logic.

Jenkins build became unstable: Stratos-41x-Commit-Build » Apache Stratos - Integration Tests #129

See

Jenkins build became unstable: Stratos-41x-Commit-Build #129

See

Re: Error while undeploying an app on Kubernetes

Hi Pubudu, Yes, I used the undeploy script. But it shouldn't cause this error right? Stratos should handle if the artifacts are in use. Even Stratos console UI calls the API just like curl command. Thanks. On Monday, 9 November 2015, Pubudu Gunatilaka wrote: > Hi Akila, > > Were you using the

Python CLI Improvements

Hi Devs, I've done the following improvements to the Python CLI. 1. Improved package structure by packing the Python files and a stratos.sh bash startup script and removed the setuptools related files 2. Improved help text for the generic help command. This was earlier done from the

Re: Error while undeploying an app on Kubernetes

Hi Akila, Were you using the undeploy.sh script for undeploying? I came across this error while using undeploy.sh script to undeploy application server application. But this error is not there if we undeploy from the UI. I think this is because script just executes the curl commands to remove all

[GitHub] stratos pull request: Topology init

Github user lahirus commented on the pull request: https://github.com/apache/stratos/pull/487#issuecomment-155049020 Thanks for the info Akila. --- 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

[GitHub] stratos pull request: Topology init

Github user ravihansa3000 commented on the pull request: https://github.com/apache/stratos/pull/487#issuecomment-155047202 I've updated PCA to use this initialization mechanism. Also updated PCA live test to verify the functionality. --- If your project is set up for it, you can repl

[GitHub] stratos pull request: Updating y axis value unit in Memory Usage a...

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

[jira] [Commented] (STRATOS-1603) NPE in re-deploying the Cartridges

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

[GitHub] stratos pull request: Updating y axis value unit in Memory Usage a...

GitHub user Thanu opened a pull request: https://github.com/apache/stratos/pull/488 Updating y axis value unit in Memory Usage and Load Average graph This p/r is to add y axis value unit in Memory Usage and Load Average graph. You can merge this pull request into a Git repository by

[jira] [Resolved] (STRATOS-1608) PCA does not publish health stat if one cep node goes down in HA mode

[ https://issues.apache.org/jira/browse/STRATOS-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pubudu Chinthaka Gunatilaka resolved STRATOS-1608. -- Resolution: Fixed Fix Version/s: 4.1.5 Fixed with follo

[jira] [Created] (STRATOS-1608) PCA does not publish health stat if one cep node goes down in HA mode

Pubudu Chinthaka Gunatilaka created STRATOS-1608: Summary: PCA does not publish health stat if one cep node goes down in HA mode Key: STRATOS-1608 URL: https://issues.apache.org/jira/browse/STRATOS

Re: ComponentStartUpSynchronizer: CC and AS components are waiting for SM to be activated?

Hi, As per some offline discussions, it seems this logic was introduced to avoid longer wait time until complete topology and complete application model is initialized in SM. If that is the case then it will be addressed by topology initialize optimization improvement. So we should be able to remo

[GitHub] stratos pull request: Topology init

Github user ravihansa3000 commented on the pull request: https://github.com/apache/stratos/pull/487#issuecomment-155014224 We cannot remove existing, periodical complete topology event publish task. Because there might situations where CC is not active (maintenance restarts, failures

Re: NPE after Re-Deploying the Cartridges

Great finding Isuru! On Mon, Nov 9, 2015 at 12:17 PM, Akila Ravihansa Perera wrote: > Nice catch Isuru! > > There is a JIRA already reported [1] for this issue. I've marked it as a > duplicate. > > Shall we get rid of this PartitionValidatorCallable class? I think it > adds unnecessary complexit

[GitHub] stratos pull request: Topology init

Github user ravihansa3000 commented on a diff in the pull request: https://github.com/apache/stratos/pull/487#discussion_r44256306 --- Diff: components/org.apache.stratos.autoscaler/src/main/java/org/apache/stratos/autoscaler/internal/AutoscalerServiceComponent.java --- @@ -230,7

Jenkins build is back to stable : Stratos-41x-Commit-Build » Apache Stratos - Integration Tests #126

See

Jenkins build is back to stable : Stratos-41x-Commit-Build #126

See

[GitHub] stratos pull request: Adding dashboard related variables to applic...

Github user Thanu commented on the pull request: https://github.com/apache/stratos/pull/486#issuecomment-154997020 Closing this p/r as it is merged in commit 0c64d22653d706542f3f7d7b7f99195cab660cad and 270066786b35aafe185240632348e0fd8460408. --- If your project is set up for it,

[GitHub] stratos pull request: Adding dashboard related variables to applic...

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

[jira] [Commented] (STRATOS-1604) UI changes in stratos to integrate DAS monitoring dashboard

[ https://issues.apache.org/jira/browse/STRATOS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996198#comment-14996198 ] Thanuja Uruththirakodeeswaran commented on STRATOS-1604: Fixed i

[jira] [Resolved] (STRATOS-1604) UI changes in stratos to integrate DAS monitoring dashboard

[ https://issues.apache.org/jira/browse/STRATOS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanuja Uruththirakodeeswaran resolved STRATOS-1604. Resolution: Fixed > UI changes in stratos to integrate DAS

Re: [GitHub] stratos pull request: Adding dashboard related variables to applic...

Thanks Thanuja for PR. Now this is merged with 270066786b35aafe185240632348e0fd8460408f On Fri, Nov 6, 2015 at 5:20 PM, Thanu wrote: > GitHub user Thanu opened a pull request: > > https://github.com/apache/stratos/pull/486 > > Adding dashboard related variables to application object and

Re: [GitHub] stratos pull request: Topology init

On Mon, Nov 9, 2015 at 1:25 PM, Gayan Gunarathne wrote: > I think we can't remove the existing periodically published complete > topology completely until we address all the scenarios that complete > topology event used for. This may be impact to the LB extensions as well.As > a first step we can