Re: [Hangout] Design and Code Review - Build and Publish docker images in Cartridge deployment

+1 Setting up and referring to own Docker registry is important since users will be mostly using their own registries rather than the Dockerhub. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Tue, Oct 14, 2014 at 12:13 PM, Sajith Kariyawasam

Re: [Hangout] Design and Code Review - Build and Publish docker images in Cartridge deployment

+1 On Tue, Oct 14, 2014 at 12:13 PM, Sajith Kariyawasam wrote: > Hi Devs, > > Shall we have $subject on Friday 17th October, at 10.30 AM GMT+5:30 ? > > I will be discussing the design and implementation of building and > publishing of docker images in Stratos, when a cartridge is deployed. > > W

[Hangout] Design and Code Review - Build and Publish docker images in Cartridge deployment

Hi Devs, Shall we have $subject on Friday 17th October, at 10.30 AM GMT+5:30 ? I will be discussing the design and implementation of building and publishing of docker images in Stratos, when a cartridge is deployed. With this feature Stratos users can provide a git repo with the Dockerfile in it

Fwd: [kubernetes-announce] Incompatible changes coming: Services v2, Namespaces, new API objects

FYI -- Forwarded message -- From: 'Tim Hockin' via kubernetes-announce < kubernetes-annou...@googlegroups.com> Date: Tue, Oct 14, 2014 at 5:59 AM Subject: [kubernetes-announce] Incompatible changes coming: Services v2, Namespaces, new API objects To: kubernetes-annou...@googlegroup

Re: [Grouping][testing] How to model nested dependencies ?

Hi Martin, As i mentioned in the other mail, you can define startup order for top level groups/cartridges in the application and you can define startup order in the group definition for group's subgroups/cartridges. In your case, i'm not sure why are you trying with nested group definition. Group

Re: [Grouping][testing] Hierarchical Monitors with Composite Application

Hi Martin, On Tue, Oct 14, 2014 at 5:07 AM, Martin Eppel (meppel) wrote: > Hi Reka, > > > > I run a scenario similar to yours (see attached application json > (application_test_app5a, group5.json, group6.json) : > > > > Deployed groups : > > group5: cartridges: [c1, c2], subgroups: [group6] > >

Re: Build failed in Jenkins: Stratos-Master-Nightly-Build #287

Thanks guys, let's wait for next Jenkins build and see. On Tue, Oct 14, 2014 at 10:11 AM, Chamila De Alwis wrote: > I did a build after the freeze yesterday, and completed without an issue. > > > Regards, > Chamila de Alwis > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.co

Re: Build failed in Jenkins: Stratos-Master-Nightly-Build #287

I did a build after the freeze yesterday, and completed without an issue. Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Tue, Oct 14, 2014 at 8:30 AM, Rajkumar Rajaratnam wrote: > Nope. It builds fine for me. > > Thanks. > > On Tue, Oct 14,

[jira] [Resolved] (STRATOS-892) Each Cluster Monitor should verify the properties passed to it and throw an exception if a validation fails

[ https://issues.apache.org/jira/browse/STRATOS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nirmal Fernando resolved STRATOS-892. - Resolution: Fixed > Each Cluster Monitor should verify the properties passed to it and th

[jira] [Commented] (STRATOS-892) Each Cluster Monitor should verify the properties passed to it and throw an exception if a validation fails

[ https://issues.apache.org/jira/browse/STRATOS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170510#comment-14170510 ] Nirmal Fernando commented on STRATOS-892: - Fixed in da2c792059a40c2d0b873c347acb

Re: [GitHub] stratos pull request: Initial GCE commit

Thanks Suriya for the PR. I'll go through it apply it. On Tue, Oct 14, 2014 at 9:15 AM, suriyapriya wrote: > GitHub user suriyapriya opened a pull request: > > https://github.com/apache/stratos/pull/92 > > Initial GCE commit > > Used jclouds 1.8.0 > Tested that instances are gett

[GitHub] stratos pull request: Initial GCE commit

GitHub user suriyapriya opened a pull request: https://github.com/apache/stratos/pull/92 Initial GCE commit Used jclouds 1.8.0 Tested that instances are getting spawned in GCE You can merge this pull request into a Git repository by running: $ git pull https://github.com/su

Re: Build failed in Jenkins: Stratos-Master-Nightly-Build #287

Nope. It builds fine for me. Thanks. On Tue, Oct 14, 2014 at 8:22 AM, Nirmal Fernando wrote: > Any one else getting any build failure? I seem to be able to build without > any issue. > > On Tue, Oct 14, 2014 at 8:08 AM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > >> See < >> h

Re: Build failed in Jenkins: Stratos-Master-Nightly-Build #287

Any one else getting any build failure? I seem to be able to build without any issue. On Tue, Oct 14, 2014 at 8:08 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < > https://builds.apache.org/job/Stratos-Master-Nightly-Build/287/changes> > > Changes: > > [nirmal070125] Fix th

[jira] [Created] (STRATOS-892) Each Cluster Monitor should verify the properties passed to it and throw an exception if a validation fails

Nirmal Fernando created STRATOS-892: --- Summary: Each Cluster Monitor should verify the properties passed to it and throw an exception if a validation fails Key: STRATOS-892 URL: https://issues.apache.org/jira/bro

[Grouping][testing] How to model nested dependencies ?

Hi Reka, Isuru, I was trying to model a nested dependency utilizing the dependency section in the group definition but I am unsure how to do it. For example, I define a group1, group2 and group3 Group3 is a subgroup of group2, Group2 is a sub group of group1 Group7 has a cartridge c3 Group6 ha

RE: [Grouping][testing] Hierarchical Monitors with Composite Application

Hi Reka, I run a scenario similar to yours (see attached application json (application_test_app5a, group5.json, group6.json) : Deployed groups : group5: cartridges: [c1, c2], subgroups: [group6] group6: cartridges: [c2], subgroups: [] Deployed Application : Dependencies: startupOrders: ["cartri

RE: [Grouping][testing] Hierarchical Monitors with Composite Application

Ok, So at the application level we flat list all groups being used in the application and add the respective subscription information (group alias). So if I deploy a group which defines a sub group I have to list it as well as the application level to assign the group alias (as in your example

Re: [Grouping][testing] Hierarchical Monitors with Composite Application

Hi Martin, Even though we define the Groups in a Group Definition, we need to provide the relevant details to instantiate it in a Application. For an example, before Service Grouping was there, we deployed a cartridge, and then at the time of Subscription specified the required details (alias, git

RE: [Grouping][testing] Hierarchical Monitors with Composite Application

Reka, Great, I’ll continue testing various scenarios as well. Btw, one question, why did you define the subgroups at the application level (group1) and not in group1 itself ? Would it behave differently ? I am not entirely clear when to use the subgroups in a group definition and when to use it

Does Stratos support IPv6?

Hi, Can someone let me know if Stratos supports IPv6? If so, how do I specify that? I'm interested in the ability to assign a fixed private IP in IPv6 notation. Currently, for IPv4, Stratos uses "fixedIP" in the cartridge definition json. Thanks, -Jeffrey

[jira] [Updated] (STRATOS-870) Moving from normal threads to executor services

[ https://issues.apache.org/jira/browse/STRATOS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-870: Assignee: Rajkumar Rajaratnam > Moving from normal threads to executor services > -

[jira] [Updated] (STRATOS-891) Different type of cluster monitors should be able to have different monitoring interval

[ https://issues.apache.org/jira/browse/STRATOS-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nirmal Fernando updated STRATOS-891: Assignee: Rajkumar Rajaratnam > Different type of cluster monitors should be able to have d

[jira] [Created] (STRATOS-891) Different type of cluster monitors should be able to have different monitoring interval

Rajkumar Rajaratnam created STRATOS-891: --- Summary: Different type of cluster monitors should be able to have different monitoring interval Key: STRATOS-891 URL: https://issues.apache.org/jira/browse/STRATOS-

Re: [Discuss] Hierarchical Locking for Topology

IMO it is based on how many siblings we have in the topology which we can lock independently. If we have lot of occurrences where we can able to lock the siblings independently it will improve the performance.But again I think we need to careful with the dead lock scenarios. Thanks, Gayan On Mon,

[Announce] Apache Stratos 4.1.0-M2 is READY

Hi Devs, Apache Stratos 4.1.0-M2 Developer Preview is now ready. This is a developer preview/snapshot of the current development track and it could be used as a baseline for contributing to the product stack. *Main Features* - Docker support using Google Kubernetes and CoreOS - Auto scaling Dock

[jira] [Updated] (STRATOS-869) Add exposed Kubernetes related methods in CLI

[ https://issues.apache.org/jira/browse/STRATOS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-869: Fix Version/s: (was: 4.1.0 M3) 4.1.0 M2 > Add exposed Kubernetes rel

[jira] [Resolved] (STRATOS-869) Add exposed Kubernetes related methods in CLI

[ https://issues.apache.org/jira/browse/STRATOS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne resolved STRATOS-869. - Resolution: Fixed This is now fixed for 4.1.0-M2. > Add exposed Kubernetes related metho

[jira] [Updated] (STRATOS-868) Add mock REST endpoint methods for Kubernetes

[ https://issues.apache.org/jira/browse/STRATOS-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nirmal Fernando updated STRATOS-868: Assignee: Imesh Gunaratne > Add mock REST endpoint methods for Kubernetes > --

[jira] [Updated] (STRATOS-869) Add exposed Kubernetes related methods in CLI

[ https://issues.apache.org/jira/browse/STRATOS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nirmal Fernando updated STRATOS-869: Assignee: Imesh Gunaratne > Add exposed Kubernetes related methods in CLI > ---

[jira] [Commented] (STRATOS-716) Support for manual scaling

[ https://issues.apache.org/jira/browse/STRATOS-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169244#comment-14169244 ] Nirmal Fernando commented on STRATOS-716: - I've implemented this for Kubernetes -

[jira] [Resolved] (STRATOS-858) Error in publishing artifact updated event

[ https://issues.apache.org/jira/browse/STRATOS-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nirmal Fernando resolved STRATOS-858. - Resolution: Cannot Reproduce Fix Version/s: 4.1.0 M2 > Error in publishing artifac

[jira] [Commented] (STRATOS-858) Error in publishing artifact updated event

[ https://issues.apache.org/jira/browse/STRATOS-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169248#comment-14169248 ] Nirmal Fernando commented on STRATOS-858: - We couldn't reproduce this issue with

[jira] [Updated] (STRATOS-716) Support for manual scaling for Docker Clusters

[ https://issues.apache.org/jira/browse/STRATOS-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nirmal Fernando updated STRATOS-716: Summary: Support for manual scaling for Docker Clusters (was: Support for manual scaling)

[jira] [Resolved] (STRATOS-716) Support for manual scaling for Docker Clusters

[ https://issues.apache.org/jira/browse/STRATOS-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nirmal Fernando resolved STRATOS-716. - Resolution: Fixed Fix Version/s: (was: 4.1.0) 4.1.0 M2 > Su

Re: [IMPORTANT] Please hold your commits to master branch which are not for M2

I've created the 4.1.0-m2 tag. Thanks Raj, I think we're good to be done with M2 developer preview. On Mon, Oct 13, 2014 at 5:50 PM, Rajkumar Rajaratnam wrote: > I tested the end-to-end docker scenario on master branch and everything > works as expected. > > 1. CLI commands > 2. Auto scaling > 3

Re: [Discuss] Hierarchical Locking for Topology

Another improvement that we can do is to introduce the same hierarchical locking to the Topology structure maintained in the Cloud Controller. Its actually the CC who will be updating the local Topology and sending the relevant events. In that case, if we have have only one write lock for the whole

Re: [IMPORTANT] Please hold your commits to master branch which are not for M2

I tested the end-to-end docker scenario on master branch and everything works as expected. 1. CLI commands 2. Auto scaling 3. Manual scaling 4. Cartridge agent is pulling from specified APP_PATH and getting updates from git push Thanks. On Mon, Oct 13, 2014 at 3:44 PM, Rajkumar Rajaratnam wrote

Re: [Announce] Apache Stratos 4.1.0-M1 is READY

Will do! Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com On Fri, Oct 10, 2014 at 9:01 AM, Imesh Gunaratne wrote: > Hi Mari, > > Shall we move this getting started guide

[jira] [Resolved] (STRATOS-890) Users should be able to provide a Git repo url when subscribing

[ https://issues.apache.org/jira/browse/STRATOS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam resolved STRATOS-890. Resolution: Fixed Fixed as per the above comment > Users should be able to provide

Re: Manual Scaling Support for Stratos

Hi Lahiru, Yes, VM cluster monitor needs to read relevant properties and update them accordingly. On Mon, Oct 13, 2014 at 12:03 PM, Lahiru Sandaruwan wrote: > Great. So we can use same AS API for VM cluster monitor updating.. right? > > On Mon, Oct 13, 2014 at 11:58 AM, Reka Thirunavukkarasu >

[jira] [Commented] (STRATOS-890) Users should be able to provide a Git repo url when subscribing

[ https://issues.apache.org/jira/browse/STRATOS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169179#comment-14169179 ] Sajith Kariyawasam commented on STRATOS-890: Fixed APP_PATH parameter in cart

[jira] [Commented] (STRATOS-890) Users should be able to provide a Git repo url when subscribing

[ https://issues.apache.org/jira/browse/STRATOS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169175#comment-14169175 ] Sajith Kariyawasam commented on STRATOS-890: This feature was not available f

[jira] [Created] (STRATOS-890) Users should be able to provide a Git repo url when subscribing

Sajith Kariyawasam created STRATOS-890: -- Summary: Users should be able to provide a Git repo url when subscribing Key: STRATOS-890 URL: https://issues.apache.org/jira/browse/STRATOS-890 Project:

Re: [IMPORTANT] Please hold your commits to master branch which are not for M2

I started testing. On Mon, Oct 13, 2014 at 3:17 PM, Nirmal Fernando wrote: > Please consider master branch as frozen. I'm doing a test with current > status and will cut the M2 developer preview tag, if pack is ok. > > On Sun, Oct 12, 2014 at 10:45 AM, Nirmal Fernando > wrote: > >> I'm in the p

[jira] [Resolved] (STRATOS-785) Autoscaling Containers in Stratos

[ https://issues.apache.org/jira/browse/STRATOS-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajkumar Rajaratnam resolved STRATOS-785. - Resolution: Fixed > Autoscaling Containers in Stratos > -

[jira] [Commented] (STRATOS-785) Autoscaling Containers in Stratos

[ https://issues.apache.org/jira/browse/STRATOS-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169144#comment-14169144 ] Rajkumar Rajaratnam commented on STRATOS-785: - Finished with series of commit

[jira] [Updated] (STRATOS-867) Tenant isolation for Kubernetes definitions - in Autoscalar

[ https://issues.apache.org/jira/browse/STRATOS-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-867: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > Tenant isolation for

[jira] [Updated] (STRATOS-734) General Improvements to Stratos in docker image

[ https://issues.apache.org/jira/browse/STRATOS-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-734: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > General Improvements

[jira] [Updated] (STRATOS-723) Stratos stopped working with java.net.SocketException

[ https://issues.apache.org/jira/browse/STRATOS-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-723: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > Stratos stopped work

[jira] [Updated] (STRATOS-764) use a maven docker plugin to build stratos docker images

[ https://issues.apache.org/jira/browse/STRATOS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-764: --- Fix Version/s: (was: 4.1.0 M2) FUTURE > use a maven docker plu

[jira] [Updated] (STRATOS-377) Getting "Tenant not found" warning when subscribing cartridges as super tenant

[ https://issues.apache.org/jira/browse/STRATOS-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-377: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > Getting "Tenant not

[jira] [Updated] (STRATOS-589) [vCloud] Getting error when unsubscribing, but instance terminated successfully

[ https://issues.apache.org/jira/browse/STRATOS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-589: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > [vCloud] Getting err

[jira] [Updated] (STRATOS-590) DHCP based IP assignment not working on vCloud environment

[ https://issues.apache.org/jira/browse/STRATOS-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-590: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > DHCP based IP assign

[jira] [Updated] (STRATOS-857) Clean/Refactor Stratos REST API to have Restful Operations

[ https://issues.apache.org/jira/browse/STRATOS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-857: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > Clean/Refactor Strat

[jira] [Updated] (STRATOS-771) [Wiki] Auto commit option in UI not documented

[ https://issues.apache.org/jira/browse/STRATOS-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-771: --- Fix Version/s: (was: 4.1.0 M2) FUTURE > [Wiki] Auto commit opt

Re: CEP removed a terminated member from memberTimeStampMap, but complaining it as a faulty member

Hi Manula, We found the issue and fixed it. Problem is updating TimeStampMap without checking whether the member is in the topology or not. We are removing member from the map on member terminated event. Also we are updating the map on receiving health stats message from members. There can be sit

[jira] [Updated] (STRATOS-869) Add exposed Kubernetes related methods in CLI

[ https://issues.apache.org/jira/browse/STRATOS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-869: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > Add exposed Kubernet

[jira] [Updated] (STRATOS-603) Validate Git URL

[ https://issues.apache.org/jira/browse/STRATOS-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-603: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > Validate Git URL > -

[jira] [Updated] (STRATOS-705) create docker files for stratos products and activemq/mysql

[ https://issues.apache.org/jira/browse/STRATOS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-705: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > create docker files

[jira] [Updated] (STRATOS-695) [Wiki] - Improve Cartridge Documentation

[ https://issues.apache.org/jira/browse/STRATOS-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-695: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > [Wiki] - Improve Car

Re: [IMPORTANT] Please hold your commits to master branch which are not for M2

Please consider master branch as frozen. I'm doing a test with current status and will cut the M2 developer preview tag, if pack is ok. On Sun, Oct 12, 2014 at 10:45 AM, Nirmal Fernando wrote: > I'm in the process of testing M2-developer preview from master branch, > please hold 'not so urgent'

[jira] [Updated] (STRATOS-868) Add mock REST endpoint methods for Kubernetes

[ https://issues.apache.org/jira/browse/STRATOS-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-868: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > Add mock REST endpoi

[jira] [Updated] (STRATOS-813) Fix critical issues reported by Sonar

[ https://issues.apache.org/jira/browse/STRATOS-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-813: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > Fix critical issues

Re: CEP removed a terminated member from memberTimeStampMap, but complaining it as a faulty member

Hi Raj, It seems like [1] get executed again. memberTimeStampMap is a concurrent hash map. Seems that CEPTopologyEventReceiver unable to remove the element in the memberTimeStampMap. [1] https://github.com/apache/stratos/blob/master/extensions/cep/stratos-cep-extension/src/main/java/org/apache/st

[jira] [Updated] (STRATOS-784) Docker image registry for Stratos

[ https://issues.apache.org/jira/browse/STRATOS-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-784: --- Fix Version/s: (was: 4.1.0 M2) FUTURE > Docker image registry

[jira] [Updated] (STRATOS-783) Stratos Jenkins integration for Docker image creation

[ https://issues.apache.org/jira/browse/STRATOS-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-783: --- Fix Version/s: (was: 4.1.0 M2) FUTURE > Stratos Jenkins integr

[jira] [Updated] (STRATOS-757) Cartridge Agent Health Stats Plugin

[ https://issues.apache.org/jira/browse/STRATOS-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-757: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > Cartridge Agent Heal

[jira] [Updated] (STRATOS-776) Stratos in docker image not starting

[ https://issues.apache.org/jira/browse/STRATOS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-776: --- Fix Version/s: (was: 4.1.0 M2) FUTURE > Stratos in docker imag

[jira] [Updated] (STRATOS-674) Users and Roles can not be created via the UI

[ https://issues.apache.org/jira/browse/STRATOS-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sajith Kariyawasam updated STRATOS-674: --- Fix Version/s: (was: 4.1.0 M2) 4.1.0 M3 > Users and Roles can

Re: How we can change the logging format in Stratos?

I already did. See my reply above On Mon, Oct 13, 2014 at 11:50 AM, Isuru Haththotuwa wrote: > > > On Mon, Oct 13, 2014 at 11:13 AM, Isuru Perera wrote: > >> We should remove the duplicate class name from logs >> > +1 > >> >> On Mon, Oct 13, 2014 at 9:15 AM, Imesh Gunaratne >> wrote: >> >>> >>