+1. Thanks Chris!
On Thu, Jul 17, 2014 at 10:36 AM, chris snow wrote:
> Great idea Praneesha, the wiki is looking much tidier now!
> On 17 Jul 2014 05:58, "Praneesha Chandrasiri" wrote:
>
>> Hi Chris,
>>
>> Totally agree with your explanation. What I thought was that, when we
>> divide the pag
Great idea Praneesha, the wiki is looking much tidier now!
On 17 Jul 2014 05:58, "Praneesha Chandrasiri" wrote:
> Hi Chris,
>
> Totally agree with your explanation. What I thought was that, when we
> divide the page into 2 separate sections, users have to refer 2 different
> locations when carryi
Hi Chris,
Totally agree with your explanation. What I thought was that, when we
divide the page into 2 separate sections, users have to refer 2 different
locations when carrying out the same process.
Thereby as a suggestion, I created a reference guide where we can include
various reference pages
[
https://issues.apache.org/jira/browse/STRATOS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064560#comment-14064560
]
Udara Liyanage commented on STRATOS-706:
Hi Martin,
The job of the CC is to spaw
[
https://issues.apache.org/jira/browse/STRATOS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064561#comment-14064561
]
Udara Liyanage commented on STRATOS-706:
Hi Martin,
The job of the CC is to spaw
Hi Jeffrey,
The slf4j 1.5.10.wso2v1 jar seems to be coming from the core carbon kernel
components. Therefore, its not possible to remove it from the build. Since
you have mentioned that manually removing it resolved the issue, you can
exclude it from the cartridge agent build and test if the issue
Hi Martin,
The job of the CC is to spawn/terminate instances. AS is the one who
decides when/what to start and when to terminate. So as Nirmal said have a
look at the AS logs in order to find the reason for termination/spawning.
On Thu, Jul 17, 2014 at 5:09 AM, Nirmal Fernando (JIRA)
wrote:
>
+1
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Wed, Jul 16, 2014 at 11:00 AM, chris snow wrote:
> Hi Praneesha,
>
> Ideally the Stratos Dev team will build the patches (a development
> activity) and make them available, but I don't know if that
[
https://issues.apache.org/jira/browse/STRATOS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064400#comment-14064400
]
Isuru Perera commented on STRATOS-43:
-
Yes, but this won't be an easy task. We have to
[
https://issues.apache.org/jira/browse/STRATOS-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Perera resolved STRATOS-48.
-
Resolution: Fixed
Fix Version/s: 3.0.0
> Remove Message Broker features from Cloud Control
[
https://issues.apache.org/jira/browse/STRATOS-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064391#comment-14064391
]
Isuru Perera commented on STRATOS-48:
-
Hi Chris,
This is fixed already. We missed to
[
https://issues.apache.org/jira/browse/STRATOS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064335#comment-14064335
]
Nirmal Fernando commented on STRATOS-706:
-
On Thu, Jul 17, 2014 at 1:11 AM, Marti
[
https://issues.apache.org/jira/browse/STRATOS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064337#comment-14064337
]
Nirmal Fernando commented on STRATOS-706:
-
On Thu, Jul 17, 2014 at 1:11 AM, Marti
On Thu, Jul 17, 2014 at 1:11 AM, Martin Eppel (JIRA)
wrote:
> Martin Eppel created STRATOS-706:
>
>
> Summary: member terminate event should log reason
> Key: STRATOS-706
> URL: https://issues.apache.org/jira/brow
[
https://issues.apache.org/jira/browse/STRATOS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063991#comment-14063991
]
chris snow commented on STRATOS-706:
I also think this sort of information should be
Martin Eppel created STRATOS-706:
Summary: member terminate event should log reason
Key: STRATOS-706
URL: https://issues.apache.org/jira/browse/STRATOS-706
Project: Stratos
Issue Type: Bug
Hi Praneesha,
Ideally the Stratos Dev team will build the patches (a development
activity) and make them available, but I don't know if that decision
has been made. If not, the administrator will need to build the
patch.
Applying the patch is something an administrator will want to do.
Maybe we
IMHO, shouldn't it be more relevant to move the "Patch Application Process"
page under a developer guide section?
On Wed, Jul 16, 2014 at 2:24 PM, Nirmal Fernando
wrote:
> +1
>
>
> On Wed, Jul 16, 2014 at 12:07 PM, chris snow wrote:
>
>> Hi guys, should we move the "Patch Application Proc
+1
On Wed, Jul 16, 2014 at 12:07 PM, chris snow wrote:
> Hi guys, should we move the "Patch Application Process" page [1] to
> the Installation guide [2]?
>
> [1]
> https://cwiki.apache.org/confluence/display/STRATOS/Patch+Application+Process
> [2]
> https://cwiki.apache.org/confluence/display
Hi Imesh,
Thank you for the info. If we are going to implement Docker IaaS
support in Stratos, we will have to support authentication features in
Docker from the ground up. Since we are targeting production
deployments with Stratos + Docker I think it's better if we think
about security aspects fr
20 matches
Mail list logo
