Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/81
---
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
+1 great work Nirmal, sorry for late reply I just saw this!
I would like to add something over status code, what if we return 204
no-content status code when something successfully deleted.Further I
believe if we can map proper HTTP status code when an error occurred would
be nice for consumers,
Hi Mari,
Send the invite email for creately which has the source
On Fri, Oct 10, 2014 at 10:55 AM, Mariangela Hills
wrote:
> Hi Lakmal,
>
> There are a few minor typos (see attachments) in the images displayed in
> [1]. Can I please have the source file, so that I can make the required
> change
Please find sample json files, attached herewith.
On Fri, Oct 10, 2014 at 9:01 AM, Imesh Gunaratne wrote:
> Hi Mari,
>
> Shall we move this getting started guide to Wiki under 4.1.0 release?
>
> Thanks
>
> On Fri, Oct 3, 2014 at 12:42 PM, Nirmal Fernando
> wrote:
>
>> Hi Devs,
>>
>> Apache St
Hi Mari,
Shall we move this getting started guide to Wiki under 4.1.0 release?
Thanks
On Fri, Oct 3, 2014 at 12:42 PM, Nirmal Fernando
wrote:
> Hi Devs,
>
> Apache Stratos 4.1.0-M1 Developer Preview is now ready. This is a
> developer preview/snapshot of the current development track and it co
Hi Chamila,
Were you able to test this with a Stratos setup?
On Fri, Oct 10, 2014 at 3:21 AM, Chamila De Alwis wrote:
> Hi,
>
> I wrote the Dockerfile for $subject that copies the Python implementation
> of the Cartridge Agent to the image and replaces the values sent via
> payload parameters a
Hi Reka,
I did some startup order / dependency testing and run into the issue that when
a subgroup has no members listed a Null pointer exception is thrown in
PaserUtils.java, line 127. Issue is that the
GroupContext [] … in groupContext.getGroupContexts(); is never being set. I
attached the ap
Hi,
I wrote the Dockerfile for $subject that copies the Python implementation
of the Cartridge Agent to the image and replaces the values sent via
payload parameters at [1].
This was based on the work done by Sajith[2] which uses the Java Cartridge
Agent.
[1] - https://github.com/chamilad/strat
Nice work Nirmal.
+1
On Thu, Oct 9, 2014 at 10:28 AM, Lasindu Charith wrote:
> Hi all,
>
> IMO, we should formalize the HTTP Return status codes throughout the REST
> API. There are instances where the return status codes are misleading and
> needs update.
>
> Thanks,
>
> On Mon, Oct 6, 2014 at
Great, thanks – sure will continue the testing,
Regards
Martin
From: Reka Thirunavukkarasu [mailto:r...@wso2.com]
Sent: Thursday, October 09, 2014 6:56 AM
To: Martin Eppel (meppel)
Cc: dev@stratos.apache.org; Isuru Haththotuwa (isu...@wso2.com)
Subject: Re: DependencyBuilder / StartupOrder clari
Hi all,
IMO, we should formalize the HTTP Return status codes throughout the REST
API. There are instances where the return status codes are misleading and
needs update.
Thanks,
On Mon, Oct 6, 2014 at 1:52 PM, Shiroshica Kulatilake
wrote:
> Hi,
>
> Added a few comments to the shared sheet.
>
>
Hi Martin,
On Thu, Oct 9, 2014 at 11:40 AM, Reka Thirunavukkarasu
wrote:
> Thanks Martin for the changes...
>
> On Thu, Oct 9, 2014 at 6:27 AM, Martin Eppel (meppel)
> wrote:
>
>> Hi Reka,
>>
>>
>>
>> I adjusted the remaining code to the new scheme and also modified the
>> code in the Dependen
[
https://issues.apache.org/jira/browse/STRATOS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gayan Gunarathne resolved STRATOS-880.
--
Resolution: Fixed
Pull request : https://github.com/apache/stratos/pull/84
Commit ID :
Gayan Gunarathne created STRATOS-880:
Summary: Re-factoring of the meta data service
Key: STRATOS-880
URL: https://issues.apache.org/jira/browse/STRATOS-880
Project: Stratos
Issue Type: B
[
https://issues.apache.org/jira/browse/STRATOS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165086#comment-14165086
]
ASF GitHub Bot commented on STRATOS-791:
GitHub user swgkg opened a pull request:
GitHub user swgkg opened a pull request:
https://github.com/apache/stratos/pull/86
Fixes for error in publishing artifact updated event - STRATOS-791
This pull image contains the fixes for :
Error in publishing artifact updated event - STRATOS-858
Re factoring the code - STR
Github user chamilad commented on the pull request:
https://github.com/apache/stratos/pull/85#issuecomment-58498544
@imesh Updated! Sorry I couldn't do this in the first run. Let me know if
any additional data should be included.
---
If your project is set up for it, you can reply t
Github user imesh commented on the pull request:
https://github.com/apache/stratos/pull/85#issuecomment-58497014
@chamilad Could you please provide a description for this PR describing the
features that you have completed?
Thanks
---
If your project is set up for it, you can repl
Fixed this in the commit f11401a342ec74e17fd6dc8dcf3c4d6477e221bf.
On Thu, Oct 9, 2014 at 3:40 PM, Isuru Haththotuwa wrote:
>
> Hi Martin,
>
> Seems that you have commented out the public static Set
> convert (org.apache.stratos.cloud.controller.pojo.StartupOrder []
> startupOrderArr, GroupConte
Thanks Sajith for the comprehensive reply! I was not able to find the logic
when I tried tracing from the StratosAdmin endpoint.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Thu, Oct 9, 2014 at 3:56 PM, Sajith Kariyawasam wrote:
> Hi Cham
GitHub user chamilad opened a pull request:
https://github.com/apache/stratos/pull/85
Python implementation of the Cartridge Agent
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chamilad/stratos master
Alternatively you can rev
Hi Manula,
This occurs when an Application (in grouping) is deployed, not subscribed
to a cartridge.
On Thu, Oct 9, 2014 at 2:43 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Hi Udara,
>
> Would you be able to solve the problem ? If you are using OpenStack please
> set assignFl
Hi Chamila,
On Thu, Oct 9, 2014 at 12:24 PM, Chamila De Alwis wrote:
> Hi,
>
> When using Kubernetes + Docker setup to spawn instances how are the
> payload parameters defined in the properties list of the subscription
> definition JSON, passed in to the created container environment?
>
>
If you
[
https://issues.apache.org/jira/browse/STRATOS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa resolved STRATOS-879.
---
Resolution: Fixed
> Make Topology's Write Locks Non-Public
>
[
https://issues.apache.org/jira/browse/STRATOS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164976#comment-14164976
]
Isuru Haththotuwa commented on STRATOS-879:
---
Fixed in commit 03593990145938ef13
Hi Martin,
Seems that you have commented out the public static Set
convert (org.apache.stratos.cloud.controller.pojo.StartupOrder []
startupOrderArr, GroupContext groupContext) methos in the ParseUtils class.
Any specific reason to do it?
This change has broken the logic in the startup order pars
Hi,
Since the Topology is updated from the messaging component only, I removed
the methods to access the write locks to an internal class. Those methods
will not be exposed to outside by the messaging component. Now, the
following methods to obtain read-only locks are exposed from
TopologyManager
[
https://issues.apache.org/jira/browse/STRATOS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa updated STRATOS-879:
--
Description: All Topology locks are exposed through the TopologyManager
class. This is
Isuru Haththotuwa created STRATOS-879:
-
Summary: Make Topology's Write Locks Non-Public
Key: STRATOS-879
URL: https://issues.apache.org/jira/browse/STRATOS-879
Project: Stratos
Issue Type
Hi Udara,
Would you be able to solve the problem ? If you are using OpenStack please
set assignFloatingIp property as true and redeploy and subscribe.
Thanks !
On Tue, Oct 7, 2014 at 4:50 PM, Udara Liyanage wrote:
> Hi,
>
> I got the following error when I deployed the below app. It's coming f
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/84
---
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
GitHub user swgkg opened a pull request:
https://github.com/apache/stratos/pull/84
Re-factoring of the meta data service
Please review and merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gayangunarathne/stratos
4.0.0_grp_me
32 matches
Mail list logo