[jira] [Comment Edited] (STRATOS-992) Resource path /cluster/clusterId/{clusterId} does not follow standard

[ https://issues.apache.org/jira/browse/STRATOS-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228096#comment-14228096 ] Mariangela Hills edited comment on STRATOS-992 at 11/28/14 7:47 AM: ---

[jira] [Comment Edited] (STRATOS-989) Some resource paths are not meaningful

[ https://issues.apache.org/jira/browse/STRATOS-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228093#comment-14228093 ] Mariangela Hills edited comment on STRATOS-989 at 11/28/14 7:46 AM: ---

[jira] [Comment Edited] (STRATOS-970) Resource path for deploying a partition is misleading

[ https://issues.apache.org/jira/browse/STRATOS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228089#comment-14228089 ] Mariangela Hills edited comment on STRATOS-970 at 11/28/14 7:45 AM: ---

[jira] [Comment Edited] (STRATOS-988) Typo in resource path - /subsscriptions/{application_id}

[ https://issues.apache.org/jira/browse/STRATOS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228097#comment-14228097 ] Mariangela Hills edited comment on STRATOS-988 at 11/28/14 7:46 AM: ---

Re: [Discuss] Interactive Topology Tree for application

Yes gayan.. d3js include tidy algo inbuit. it can handle any number of nodes. Normally binary tree algo can't handle more than two. *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 On Fri, Nov 28, 2014 at 1:02 PM, Gayan Gunarathne wrote: > Great work and

Re: [Discuss] Cloud Controller Clustering Model

Hi, According to this design Autoscaler (AS)/Stratos Manager (SM) will talk to >> Cloud Controller (CC) via the Cloud Controller Service endpoint exposed via >> the load balancer. >> >> *Data Replication* >> When a request comes into one of the CC instances it will execute the >> necessary actions

Re: [Discuss] Interactive Topology Tree for application

Great work and nice findings of algorithm Dakshika! Is that algorithm supports more than 2 Siblings per parent? On Fri, Nov 28, 2014 at 10:25 AM, Sajith Kariyawasam wrote: > Great work Dakshika ! > > Just a thought, can this be supported with expand / collapse options? > which I think be useful

[GitHub] stratos pull request: Introduce the enum for messaging topics

Github user swgkg commented on the pull request: https://github.com/apache/stratos/pull/121#issuecomment-64860519 Hi Imesh, Remove PING topic and update the PR. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

Re: [Discuss] Cloud Controller Clustering Model

Hi, On Wed, Nov 26, 2014 at 1:16 PM, Imesh Gunaratne wrote: > ​Hi Devs, > > This is to discuss the clustering model of the cloud controller: > > > ​ > > As shown in the above diagram the idea is to have a coordinator node to > handle data persistence logic and message publishing (topology, insta

[jira] [Resolved] (STRATOS-988) Typo in resource path - /subsscriptions/{application_id}

[ https://issues.apache.org/jira/browse/STRATOS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills resolved STRATOS-988. -- Resolution: Fixed Fix Version/s: 4.1.0 Alpha This has been fixed in the REST API

[jira] [Comment Edited] (STRATOS-989) Some resource paths are not meaningful

[ https://issues.apache.org/jira/browse/STRATOS-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228093#comment-14228093 ] Mariangela Hills edited comment on STRATOS-989 at 11/28/14 6:27 AM: ---

[jira] [Resolved] (STRATOS-992) Resource path /cluster/clusterId/{clusterId} does not follow standard

[ https://issues.apache.org/jira/browse/STRATOS-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills resolved STRATOS-992. -- Resolution: Fixed Fix Version/s: 4.1.0 Alpha Fixed in REST API refactoring. Comm

[jira] [Comment Edited] (STRATOS-989) Some resource paths are not meaningful

[ https://issues.apache.org/jira/browse/STRATOS-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228093#comment-14228093 ] Mariangela Hills edited comment on STRATOS-989 at 11/28/14 6:28 AM: ---

[GitHub] stratos pull request: Removed duplicate api method for GET /tenant...

Github user shirolk commented on the pull request: https://github.com/apache/stratos/pull/124#issuecomment-64859455 Merged with commit id 10889a7a28aed1a9bc886c888e1820a43a324a13 to master. Thank you Akila ! --- If your project is set up for it, you can reply to this email a

[GitHub] stratos pull request: Removed duplicate api method for GET /tenant...

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

[jira] [Comment Edited] (STRATOS-989) Some resource paths are not meaningful

[ https://issues.apache.org/jira/browse/STRATOS-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228093#comment-14228093 ] Mariangela Hills edited comment on STRATOS-989 at 11/28/14 6:26 AM: ---

[jira] [Resolved] (STRATOS-989) Some resource paths are not meaningful

[ https://issues.apache.org/jira/browse/STRATOS-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills resolved STRATOS-989. -- Resolution: Fixed Fix Version/s: 4.1.0 Alpha This has been fixed in the REST API

[jira] [Resolved] (STRATOS-970) Resource path for deploying a partition is misleading

[ https://issues.apache.org/jira/browse/STRATOS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariangela Hills resolved STRATOS-970. -- Resolution: Fixed Fix Version/s: 4.1.0 Alpha Fixed in the REST API refactoring p

[jira] [Resolved] (STRATOS-991) Refactor Stratos API URLs

[ https://issues.apache.org/jira/browse/STRATOS-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiroshica Kulatilake resolved STRATOS-991. --- Resolution: Fixed Fix Version/s: 4.1.0 Alpha > Refactor Stratos API UR

[jira] [Comment Edited] (STRATOS-970) Resource path for deploying a partition is misleading

[ https://issues.apache.org/jira/browse/STRATOS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228089#comment-14228089 ] Mariangela Hills edited comment on STRATOS-970 at 11/28/14 6:18 AM: ---

Re: [Wiki] How to Merge Pull Requests from Github to Apache Repository

> > > > There's an issue with the new guide. Please note that we normally have > github as our remote and our origin repo is original Apache stratos repo. > We might need to revert back to old guide: > https://cwiki.apache.org/confluence/display/STRATOS/Committers+%3A+Applying+github+pull+requests

Re: Same API repeated but different API operations?

PR looks good to me. On Fri, Nov 28, 2014 at 10:44 AM, Nirmal Fernando wrote: > Thanks Shiro. I'll merge the PR now. > > On Fri, Nov 28, 2014 at 10:41 AM, Shiroshica Kulatilake > wrote: > >> pull request submitted >> https://github.com/apache/stratos/pull/124 >> >> On Fri, Nov 28, 2014 at 9:48

Re: [Wiki] How to Merge Pull Requests from Github to Apache Repository

Hi Guys, There's an issue with the new guide. Please note that we normally have github as our remote and our origin repo is original Apache stratos repo. We might need to revert back to old guide: https://cwiki.apache.org/confluence/display/STRATOS/Committers+%3A+Applying+github+pull+requests or w

Improvements in REST API

Hi, When documenting the missing REST APIs in wiki, before REST API refactoring started, I came across some issues with the REST APIs and created some JIRAs under [1]. Some of these JIRA's can be closed as they have been fixed in the REST API refactoring process. [1] https://issues.apache.org/jir

Re: [Discuss] Interactive Topology Tree for application

Thank you all.. We need to finalize colors for status. StatusImeshDakhikaCreated-OrangeActiveGreenGreenInactiveOrangeGrey Terminating/TerminatedRedRed Thank you.. Regards, *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 On Fri, Nov 28, 2014 at 10:42 AM

Re: [Discuss] Interactive Topology Tree for application

Hi, Great work Dakshika. On Fri, Nov 28, 2014 at 10:42 AM, Dakshika Jayathilaka wrote: > @shiro: Currently you can see it by hovering on each node. (color + text > on hover) If we add extra label near the node that will generate some > issues on node auto positioning without overlapping. > > If

[GitHub] stratos pull request: Introduce the enum for messaging topics

Github user imesh commented on a diff in the pull request: https://github.com/apache/stratos/pull/121#discussion_r21017047 --- Diff: components/org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/broker/heartbeat/TopicHealthChecker.java --- @@ -58,8 +57,8 @@ pu

Re: Same API repeated but different API operations?

Thanks for the clarification! Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. w: http://wso2.com On Fri, Nov 28, 2014 at 9:48 AM, Shiroshica Kulatilake wrote: > Hi Mariangela, > > Good finding. > > This is

Re: [Discuss] Interactive Topology Tree for application

On Fri, Nov 28, 2014 at 10:42 AM, Dakshika Jayathilaka wrote: > @shiro: Currently you can see it by hovering on each node. (color + text > on hover) > Then fine !! > If we add extra label near the node that will generate some issues on node > auto positioning without overlapping. > > If you

Re: Same API repeated but different API operations?

Thanks Shiro. I'll merge the PR now. On Fri, Nov 28, 2014 at 10:41 AM, Shiroshica Kulatilake wrote: > pull request submitted > https://github.com/apache/stratos/pull/124 > > On Fri, Nov 28, 2014 at 9:48 AM, Shiroshica Kulatilake > wrote: > >> Hi Mariangela, >> >> Good finding. >> >> This is a t

Re: [Discuss] Interactive Topology Tree for application

@shiro: Currently you can see it by hovering on each node. (color + text on hover) If we add extra label near the node that will generate some issues on node auto positioning without overlapping. If you can come up with smart solution ontop of tidy algo, i'm happy to add that.. :) Thank you.. *D

Re: Same API repeated but different API operations?

pull request submitted https://github.com/apache/stratos/pull/124 On Fri, Nov 28, 2014 at 9:48 AM, Shiroshica Kulatilake wrote: > Hi Mariangela, > > Good finding. > > This is a the same resource path. > As per "Making Stratos REST API restfull"we have decided to use only one. > So as Nirmal says

[GitHub] stratos pull request: Removed duplicate api method for GET /tenant...

GitHub user shirolk opened a pull request: https://github.com/apache/stratos/pull/124 Removed duplicate api method for GET /tenants/{tenantDomain} Please review and commit. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shirolk/s

Re: [Discuss] Interactive Topology Tree for application

Great work dakshika. Looks really nice. On Fri, Nov 28, 2014 at 10:33 AM, Shiroshica Kulatilake wrote: > My question was a label indicating whatever status near the node - so that > all statuses can be viewed if needed - maybe this would be in a more > verbose display ... > > On Fri, Nov 28, 201

Re: [Discuss] Interactive Topology Tree for application

My question was a label indicating whatever status near the node - so that all statuses can be viewed if needed - maybe this would be in a more verbose display ... On Fri, Nov 28, 2014 at 10:28 AM, Dakshika Jayathilaka wrote: > @sajith: Currently not. But i can add that capability. > > *Dakshika

Re: [Discuss] Interactive Topology Tree for application

@sajith: Currently not. But i can add that capability. *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 On Fri, Nov 28, 2014 at 10:27 AM, Dakshika Jayathilaka wrote: > @chamila & @shiro: yes of course. Legends will appear on the right side of > screen. >

Re: [Discuss] Interactive Topology Tree for application

@chamila & @shiro: yes of course. Legends will appear on the right side of screen. that's why i mentioned "*need to show keys on screen" :)* *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 On Fri, Nov 28, 2014 at 10:14 AM, Reka Thirunavukkarasu wrote:

Re: [Discuss] Interactive Topology Tree for application

Great work Dakshika ! Just a thought, can this be supported with expand / collapse options? which I think be useful when the number of nodes are high.. On Fri, Nov 28, 2014 at 10:14 AM, Shiroshica Kulatilake wrote: > Looks spiffy !! > > I was going to ask the same question as Chamila :) > > Wou

Re: [Discuss] Interactive Topology Tree for application

Great Work and looks really nice..!!! This feature will really be helpful. On Fri, Nov 28, 2014 at 10:04 AM, Lakmal Warusawithana wrote: > Great work! > > On Fri, Nov 28, 2014 at 10:01 AM, Imesh Gunaratne > wrote: > >> Hi Dakshika, >> >> Fabulous work!! This is one of the key elements of the da

Re: [Discuss] Interactive Topology Tree for application

Looks spiffy !! I was going to ask the same question as Chamila :) Would it be useful to have the status shown in a label against the node ? On Fri, Nov 28, 2014 at 10:09 AM, Chamila De Alwis wrote: > Great work Dakshika! > > Will there be a legend to indicate which colors represent which stat

Re: [Discuss] Interactive Topology Tree for application

Great work Dakshika! Will there be a legend to indicate which colors represent which statuses? Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Fri, Nov 28, 2014 at 10:04 AM, Lakmal Warusawithana wrote: > Great work! > > On Fri, Nov 28, 2014

Re: [Discuss] Interactive Topology Tree for application

Great work! On Fri, Nov 28, 2014 at 10:01 AM, Imesh Gunaratne wrote: > Hi Dakshika, > > Fabulous work!! This is one of the key elements of the dashboard. > I would like to propose use three simple colours like "Orange", "Green" > and "Red" to represent "Inactive", "Active" and "Terminating" stat

Re: [Discuss] Interactive Topology Tree for application

s/propose use/propose to use/g On Fri, Nov 28, 2014 at 10:01 AM, Imesh Gunaratne wrote: > Hi Dakshika, > > Fabulous work!! This is one of the key elements of the dashboard. > I would like to propose use three simple colours like "Orange", "Green" > and "Red" to represent "Inactive", "Active" and

Re: [Discuss] Interactive Topology Tree for application

Hi Dakshika, Fabulous work!! This is one of the key elements of the dashboard. I would like to propose use three simple colours like "Orange", "Green" and "Red" to represent "Inactive", "Active" and "Terminating" states of each element. WDYT? Thanks On Fri, Nov 28, 2014 at 9:36 AM, Dakshika Jaya

Re: [Discuss] Cluster Status Event Receiver in Cloud Controller

Hi Reka, Thanks for the clarification. Will there be any issues if we change this to a service call since AS is already making service calls to CC? Thanks On Thu, Nov 27, 2014 at 11:15 PM, Reka Thirunavukkarasu wrote: > Hi Imesh, > > This is there to update the cluster status from autoscaler t

Re: Same API repeated but different API operations?

Hi Mariangela, Good finding. This is a the same resource path. As per "Making Stratos REST API restfull"we have decided to use only one. So as Nirmal says just one method is enough. We have not fixed the document and we also have two methods in the rest api calling different methods - will remov

Re: Same API repeated but different API operations?

Only one of those two APIs are required. IMO we should get rid of the other, since both APIs appear to do the same thing. On Fri, Nov 28, 2014 at 9:35 AM, Mariangela Hills wrote: > Hi, > > When documenting [1] in wiki I noticed that the API mentioned in row 67 > and 71 is identical, but the prop

Same API repeated but different API operations?

Hi, When documenting [1] in wiki I noticed that the API mentioned in row 67 and 71 is identical, but the proposed API operation name is different. Could it be that there is typo in the API mentioned in row 71 and that it such actually be /tenants/availability/{tenantDomain} which can be used to ch

Re: [Discuss] Cluster Status Event Receiver in Cloud Controller

Hi Imesh, This is there to update the cluster status from autoscaler to Topology in CC . If we are getting rid of this, then we would need to go for service call. We introduced this as like instance status. Thanks, Reka On Thu, Nov 27, 2014 at 7:09 PM, Imesh Gunaratne wrote: > Hi Devs, > > Do

[Discuss] Cluster Status Event Receiver in Cloud Controller

Hi Devs, Do we need the following in cloud controller? clusterStatusTopicReceiver = new ClusterStatusTopicReceiver(); Thread tClusterStatusTopicReceiver = new Thread(clusterStatusTopicReceiver); tClusterStatusTopicReceiver.start(); Thanks -- Imesh Gunaratne

Re: Pluggable Extensions Framework for Python Cartridge Agent

+1 for the idea! There is a good discussion on this topic in StackOverflow: http://stackoverflow.com/questions/932069/building-a-minimal-plugin-architecture-in-python On Thu, Nov 27, 2014 at 3:19 PM, Chamila De Alwis wrote: > +1 > > I too think we can make the artifact handler plug-gable, aside

Re: REST API refactoring

Great work Shiro! Thanks for looking into this. On Thu, Nov 27, 2014 at 3:48 PM, Shiroshica Kulatilake wrote: > Hi Devs, > > The REST API refactoring is now on master. (commits > 2242e2fc6083129e3f0e5b08707250f5b1648a44, > 023900c4fdd7ba9b12a228b5bf619e77885a3f2f, > 72c9d60433d9b196d67268e850e5

[DEV][APIM]Adding a secondary JDBC userstore

Hi, I'm following the APIM documentation on adding a secondary JDBC based userstore[1]. Is there any additional step where I should populate the database on the secondary userstore with a set of tables, that I'm missing here? When I restart the server, I'm getting the following error. I have the

Re: [DEV][APIM]Adding a secondary JDBC userstore

Sorry. I've sent this to a wrong address. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Thu, Nov 27, 2014 at 5:45 PM, Chamila De Alwis wrote: > Hi, > > I'm following the APIM documentation on adding a secondary JDBC based > userstore[1]. I

[jira] [Created] (STRATOS-1014) Monitoring Live Application Status with topology view

Dakshika Jayathilaka created STRATOS-1014: - Summary: Monitoring Live Application Status with topology view Key: STRATOS-1014 URL: https://issues.apache.org/jira/browse/STRATOS-1014 Project: Str

Re: Avoid Git merge commits - keep the history clean

Kind reminder! Thanks. On Tue, Sep 23, 2014 at 7:39 AM, Akila Ravihansa Perera wrote: > Hi Devs, > > I think it's better if we can keep the commit history clean in our > repo. It will allow us to clearly see the dev work going on. Here are > some articles [1, 2] that explains how to get rid of

[jira] [Commented] (STRATOS-991) Refactor Stratos API URLs

[ https://issues.apache.org/jira/browse/STRATOS-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227516#comment-14227516 ] ASF GitHub Bot commented on STRATOS-991: Github user shirolk commented on the pul

[jira] [Commented] (STRATOS-991) Refactor Stratos API URLs

[ https://issues.apache.org/jira/browse/STRATOS-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227517#comment-14227517 ] ASF GitHub Bot commented on STRATOS-991: Github user shirolk closed the pull requ

[GitHub] stratos pull request: Rest api refactor - STRATOS-991

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

[GitHub] stratos pull request: Rest api refactor - STRATOS-991

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

Re: REST API refactoring

Hi Devs, The REST API refactoring is now on master. (commits 2242e2fc6083129e3f0e5b08707250f5b1648a44, 023900c4fdd7ba9b12a228b5bf619e77885a3f2f, 72c9d60433d9b196d67268e850e572fd81a9fd97, 6af9901141c9a89c44e76803b6cbdbb68561714c). The last commit consists of the changes that were required due to t

[jira] [Commented] (STRATOS-991) Refactor Stratos API URLs

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

[GitHub] stratos pull request: Rest api refactor - STRATOS-991

Github user imesh commented on the pull request: https://github.com/apache/stratos/pull/123#issuecomment-64768113 Thanks @shirolk for fixing this. I have now merged this pull request to master branch. --- If your project is set up for it, you can reply to this email and have your rep

Re: Pluggable Extensions Framework for Python Cartridge Agent

+1 I too think we can make the artifact handler plug-gable, aside from the health stat collector. The common operations can be easily derived from the existing Git based artifact handler code. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On T

[jira] [Commented] (STRATOS-991) Refactor Stratos API URLs

[ https://issues.apache.org/jira/browse/STRATOS-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227447#comment-14227447 ] ASF GitHub Bot commented on STRATOS-991: GitHub user shirolk opened a pull reques

[GitHub] stratos pull request: Rest api refactor - STRATOS-991

GitHub user shirolk opened a pull request: https://github.com/apache/stratos/pull/123 Rest api refactor - STRATOS-991 Updated the CLI with the refactored changes For ticket https://issues.apache.org/jira/browse/STRATOS-991 You can merge this pull request into a Git repository by

Re: Pluggable Extensions Framework for Python Cartridge Agent

IMO if we are move with the plugin framework , we can use our agent components (eg health checker, source control handler) as plugins. We can ship the default cartridge agent with our default plugin set.If the end user needs they can use their own plugin with their requirement. AFAIR we may need

Re: Stratos UXD listing improvments

Thanks Imesh.. *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 On Thu, Nov 27, 2014 at 2:48 PM, Imesh Gunaratne wrote: > Thanks Dakshika! This pull request is now merged to master branch. > > On Thu, Nov 27, 2014 at 2:28 PM, Dakshika Jayathilaka > wrot

Re: Stratos UXD listing improvments

Thanks Dakshika! This pull request is now merged to master branch. On Thu, Nov 27, 2014 at 2:28 PM, Dakshika Jayathilaka wrote: > Hi Devs, > > I have added data view option for configuration section and application > section. This will automatically map with existing schema and show disabled > g

[jira] [Commented] (STRATOS-1013) listing improvments

[ https://issues.apache.org/jira/browse/STRATOS-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227418#comment-14227418 ] ASF GitHub Bot commented on STRATOS-1013: - Github user asfgit closed the pull re

[GitHub] stratos pull request: Listing improvments [STRATOS-1013]

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

Stratos UXD listing improvments

Hi Devs, I have added data view option for configuration section and application section. This will automatically map with existing schema and show disabled generated form view. Currently its working fine for detail view except cartridge and application.(need to fix some issues on cartridge retur

[jira] [Commented] (STRATOS-1013) listing improvments

[ https://issues.apache.org/jira/browse/STRATOS-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227406#comment-14227406 ] ASF GitHub Bot commented on STRATOS-1013: - GitHub user dakshika opened a pull re

[GitHub] stratos pull request: Listing improvments [STRATOS-1013]

GitHub user dakshika opened a pull request: https://github.com/apache/stratos/pull/122 Listing improvments [STRATOS-1013] I have added data view option for configuration section and application section. This will automatically map with existing schema and show disabled generated fo

[jira] [Created] (STRATOS-1013) listing improvments

Dakshika Jayathilaka created STRATOS-1013: - Summary: listing improvments Key: STRATOS-1013 URL: https://issues.apache.org/jira/browse/STRATOS-1013 Project: Stratos Issue Type: Sub-ta

[jira] [Updated] (STRATOS-1012) Clustering support for Cloud Controller

[ https://issues.apache.org/jira/browse/STRATOS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-1012: - Fix Version/s: 4.1.0 Alpha > Clustering support for Cloud Controller > -

Re: Pluggable Extensions Framework for Python Cartridge Agent

+1 for adding plugging framework and extension mechanism to the cartridge agent. With my little finding, I think Yapsy may good for our requirement. Also, can we make health checker also pluggable? Please see Shaheed comments in [1] [1]Hangout (01) to discuss the Python Agent On Thu, Nov 27, 201

[jira] [Updated] (STRATOS-1011) Clustering support for Load Balancer

[ https://issues.apache.org/jira/browse/STRATOS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-1011: - Fix Version/s: 4.1.0 Alpha > Clustering support for Load Balancer >

[jira] [Updated] (STRATOS-1012) Clustering support for Cloud Controller

[ https://issues.apache.org/jira/browse/STRATOS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-1012: - Attachment: Cloud Controller - Clustering Model.png > Clustering support for Cloud Contr

[jira] [Created] (STRATOS-1012) Clustering support for Cloud Controller

Imesh Gunaratne created STRATOS-1012: Summary: Clustering support for Cloud Controller Key: STRATOS-1012 URL: https://issues.apache.org/jira/browse/STRATOS-1012 Project: Stratos Issue Typ

[jira] [Updated] (STRATOS-1011) Clustering support for Stratos Load Balancer

[ https://issues.apache.org/jira/browse/STRATOS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-1011: - Summary: Clustering support for Stratos Load Balancer (was: Clustering support for Load

[jira] [Updated] (STRATOS-1011) Clustering support for Load Balancer

[ https://issues.apache.org/jira/browse/STRATOS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-1011: - Attachment: Load Balancer - Clustering Model.png > Clustering support for Load Balancer

[jira] [Created] (STRATOS-1011) Clustering support for Load Balancer

Imesh Gunaratne created STRATOS-1011: Summary: Clustering support for Load Balancer Key: STRATOS-1011 URL: https://issues.apache.org/jira/browse/STRATOS-1011 Project: Stratos Issue Type:

[jira] [Updated] (STRATOS-1011) Clustering support for Load Balancer

[ https://issues.apache.org/jira/browse/STRATOS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-1011: - Affects Version/s: (was: 4.1.0 Alpha) (was: 4.0.0 Alpha)

Pluggable Extensions Framework for Python Cartridge Agent

Hi, As you may know, Stratos 4.1.0 Alpha release will be shipped with a Python based cartridge agent. AFAIU, there were two main reasons to move to a Python based agent. 1. Make it light weight to minimize the memory/CPU footprint. This was important especially in the Docker scenario. 2. Allow D