Hi All,
I have work on $subject. For the development I have used EC2 machine and
create my own registry according to [1] and it works successfully. But when
I restart the docker registry all the pushed images are discarded from the
registry. Is anyone have faced such situation ? I have already sta
[
https://issues.apache.org/jira/browse/STRATOS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127948#comment-14127948
]
ASF GitHub Bot commented on STRATOS-763:
Github user asfgit closed the pull reque
[
https://issues.apache.org/jira/browse/STRATOS-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiroshica Kulatilake resolved STRATOS-770.
---
Resolution: Fixed
> Adding in a "Description" field to all definition types
Ok,
Thanks
Martin
-Original Message-
From: Akila Ravihansa Perera [mailto:raviha...@wso2.com]
Sent: Tuesday, September 09, 2014 6:32 PM
To: dev
Subject: Re: StratosAdmin.java / json schema validation
Hi Martin,
REST API schema validation was introduced with STRATOS-466. You can track
Hi Martin,
REST API schema validation was introduced with STRATOS-466. You can
track the JIRA at [1]. I'm working on auto generating the schema from
bean classes. But for now you can temporarily disable this by
commenting out "schemaHandler" properties of beans defined in
cxf-servlet.xml file at [
I am testing some new json definitions to StratosAdmin (for grouping) but it
seems that any json input in the Rest APi (StratosAdmin.java) is validated
against schema.xsd (see exception below) , my question is if there is
1. A way to temporarily turn the validation off (for some testing pu
[
https://issues.apache.org/jira/browse/STRATOS-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127377#comment-14127377
]
John Muller commented on STRATOS-755:
-
Hi Nirmal,
Since myself and my development te
[
https://issues.apache.org/jira/browse/STRATOS-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127338#comment-14127338
]
ASF GitHub Bot commented on STRATOS-779:
GitHub user R-Rajkumar opened a pull req
[
https://issues.apache.org/jira/browse/STRATOS-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajkumar Rajaratnam updated STRATOS-779:
Description:
Currently, call from AS to CC to spawn new instances is synchronous. I
Hi Imesh, yes a .travis.yml file will be needed. It is a little tricky
because our build outputs over 4 mb which is a Travis limit. However we
can't turn output off because no output for 10 mins will make Travis think
the build has failed.
On 9 Sep 2014 16:09, "Imesh Gunaratne" wrote:
> +1 A gr
Rajkumar Rajaratnam created STRATOS-779:
---
Summary: Stratos is creating more instances than the max limit
Key: STRATOS-779
URL: https://issues.apache.org/jira/browse/STRATOS-779
Project: Stratos
[
https://issues.apache.org/jira/browse/STRATOS-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127245#comment-14127245
]
Udara Liyanage commented on STRATOS-765:
400 is merged to master. Active developm
[
https://issues.apache.org/jira/browse/STRATOS-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127244#comment-14127244
]
Udara Liyanage commented on STRATOS-765:
400 is merged to master. Active developm
400 is merged to master. Active development is on master from where next
release branch (410 or 420 or 500) will be created.
So no need to port them to 400 since it already released.
Touched, not typed. Erroneous words are a feature, not a typo.
[
https://issues.apache.org/jira/browse/STRATOS-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127236#comment-14127236
]
Jeffrey Nguyen commented on STRATOS-765:
If it's not going to be used for upcomin
[
https://issues.apache.org/jira/browse/STRATOS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127195#comment-14127195
]
ASF GitHub Bot commented on STRATOS-763:
GitHub user R-Rajkumar opened a pull req
[
https://issues.apache.org/jira/browse/STRATOS-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127193#comment-14127193
]
ASF GitHub Bot commented on STRATOS-748:
Github user R-Rajkumar closed the pull r
[
https://issues.apache.org/jira/browse/STRATOS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127191#comment-14127191
]
ASF GitHub Bot commented on STRATOS-763:
Github user R-Rajkumar closed the pull r
Hi Madhawa,
Further below is an sample launch parameter file content in a php
cartridge(192.168.18.135) deployed in puppet in http://192.168.18.25
instance.
SERVICE_NAME=php,HOST_NAME=phptest1011.stratos.com
,MULTITENANT=false,TENANT_ID=-1234,TENANT_RANGE=-1234,CARTRIDGE_ALIAS=phptest1011,CLUSTER
SERVICE_NAME is one of the many parameters passed from Stratos through the
IaaS as launch parameters. It represents the type of the cartridge that is
subscribed to. In your case it should be 'php'.
Check if /tmp/payload/launch_parameters file exists. If that is empty it is
most likely that the met
Hi Madhawa,
Check whether the service name is in /tmp/payload/launch-params file
in spawned
instance. SERVICE_NAME should be defined as php in this file.
Thanks
On Tue, Sep 9, 2014 at 8:35 PM, Madhawa Bandara wrote:
> Hi all,
>
> I get the following error[1] at the cartridge agent log in the
+1 A great thought Chris!
We will need to add a ".travis.yml" file I to the root of the project I
guess.
On Tue, Sep 9, 2014 at 2:41 AM, Isuru Haththotuwa wrote:
>
>
> On Tue, Sep 9, 2014 at 12:07 PM, Nirmal Fernando
> wrote:
>
>> Absolute +1 Chris. Will be very helpful.
>>
>> On Tue, Sep 9, 20
Hi all,
I get the following error[1] at the cartridge agent log in the php
instances spawned.
Where is the SERVICE_NAME set? What is the issue?
Thanks.
[1]-
2014-09-03 05:18:49,756 [-] [main] ERROR Main java.lang.RuntimeException:
org.apache.stratos.cartridge.agent.exception.ParameterNotFoundEx
Github user lasinducharith closed the pull request at:
https://github.com/apache/stratos/pull/25
---
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
Github user swgkg closed the pull request at:
https://github.com/apache/stratos/pull/16
---
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 enabl
[
https://issues.apache.org/jira/browse/STRATOS-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126914#comment-14126914
]
ASF GitHub Bot commented on STRATOS-770:
Github user shirolk closed the pull requ
Hi,
We added port 8280 manually to the template file and it worked.
Thanks
On Tue, Sep 9, 2014 at 10:16 AM, Nirmal Fernando
wrote:
>
>
> On Tue, Sep 9, 2014 at 9:58 AM, Chamila De Alwis
> wrote:
>
>> Thanks Nirmal! That clears it up.
>>
>> In our case, it seems that LB is not opening the
[
https://issues.apache.org/jira/browse/STRATOS-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126801#comment-14126801
]
Shiroshica Kulatilake commented on STRATOS-772:
---
The mock endpoint for REST
Hi Isuru,
Regarding the services,
It should have relationship as follows, right?
Topology 1: 0..n Services
Group1: 1..nServices
On Mon, Sep 8, 2014 at 12:08 AM, Isuru Haththotuwa
wrote:
>
> This is to discuss $subject.
>
> I have attached the class diagram which shows the pr
29 matches
Mail list logo
