Hi Imesh,
I will document the 'values' variable. I've missed that detail.
+1 for adding a reference. The readme can be updated quickly that way.
On May 1, 2015 11:26 AM, "Lahiru Sandaruwan" wrote:
>
>
> On Fri, May 1, 2015 at 10:51 AM, Imesh Gunaratne wrote:
>
>> May be we could maintain this
On Fri, May 1, 2015 at 10:51 AM, Imesh Gunaratne wrote:
> May be we could maintain this in README.md itself and add a pointer in
> docs without duplicating. WDYT?
>
> +1. Let's add a link from PCA section.
> On Fri, May 1, 2015 at 9:39 AM, Lahiru Sandaruwan
> wrote:
>
>> Great stuff. Doc candi
May be we could maintain this in README.md itself and add a pointer in docs
without duplicating. WDYT?
On Fri, May 1, 2015 at 9:39 AM, Lahiru Sandaruwan wrote:
> Great stuff. Doc candidate?
>
> On Fri, May 1, 2015 at 8:04 AM, Imesh Gunaratne wrote:
>
>> Great work Chamila!! Very descriptive!! O
Mariangela Hills created STRATOS-1359:
-
Summary: Wiki - Update the REST API guide
Key: STRATOS-1359
URL: https://issues.apache.org/jira/browse/STRATOS-1359
Project: Stratos
Issue Type: Ta
[
https://issues.apache.org/jira/browse/STRATOS-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522759#comment-14522759
]
Mariangela Hills commented on STRATOS-1358:
---
Added content. However, this cont
[
https://issues.apache.org/jira/browse/STRATOS-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills updated STRATOS-1358:
--
Summary: Wiki - Add addition information to API Resource Definitions (was:
Add additi
Great stuff. Doc candidate?
On Fri, May 1, 2015 at 8:04 AM, Imesh Gunaratne wrote:
> Great work Chamila!! Very descriptive!! One minor point, shall we either
> rename or document "values" variable in run_plugin method?
>
> def run_plugin(self, values)
>
>
> On Thu, Apr 30, 2015 at 11:15 PM, Cham
Hi Pranavan,
Please find the answers inline,
On Fri, May 1, 2015 at 12:49 AM, Pranavan Theivendiram <
pranavan...@cse.mrt.ac.lk> wrote:
> Hi Lahiru,
>
> After going through the moving average mechanisms, I found that it has two
> main categories which are
> 1. Simple moving average
> 2. Expone
Hi Devs,
I am in the process of documenting all information( i.e., is the property
updatable, writable, readable, required, etc., )on the available API
resource properties based on the inforBeans and samples. Can you please
review the following sub pages in [1] , correct any incorrect definitions
Lets remove it from the samples, to be compatible with 4.0.0 release.
Adding it to the backend is a schema change.
Thanks.
On Fri, May 1, 2015 at 9:11 AM, Imesh Gunaratne wrote:
> Thanks Raj! IMO we need to either remove the name attribute from the
> samples or add it in the backend.
>
> Thanks
Thanks Raj! IMO we need to either remove the name attribute from the
samples or add it in the backend.
Thanks
On Fri, May 1, 2015 at 8:26 AM, Rajkumar Rajaratnam
wrote:
> Hi Imesh,
>
> networkUuid attribute is unique. So we don't need a name. We are not using
> name attribute inside Stratos.
>
Hi Imesh,
networkUuid attribute is unique. So we don't need a name. We are not using
name attribute inside Stratos.
However having name attribute in cartridge JSON doesn't have any impact.
Stratos doesn't care whether we set name attribute or not. I added name
attribute in samples for more clar
A good finding Mari! Yes this looks like a mistake. Name attribute is not
there either in the network interface bean class or in the network
interface backend class. @Raj: Do you have any thoughts on this?
Thanks
On Fri, May 1, 2015 at 7:21 AM, Mariangela Hills
wrote:
> Hi Devs,
>
> I am in the
Great work Chamila!! Very descriptive!! One minor point, shall we either
rename or document "values" variable in run_plugin method?
def run_plugin(self, values)
On Thu, Apr 30, 2015 at 11:15 PM, Chamila De Alwis
wrote:
> Hi Devs,
>
> If you are creating Python Cartridge Agent plugins you can r
Hi Reka,
Why is it circular ?
Probably I defined it incorrectly: What I want is the following start up
sequence:
After group n-st-G2-t-a-2 starts up c3 should start up, when c3 is up then c2,
when c2 is up, then c1 should start up. (n-st-G2-t-a-2 -> c3 -> c2 -> c1)
I am probably too tired an
Hi Devs,
I am in the process of documenting the definitions that correspond to the
respective REST API resources (e.g., [1]). I noticed in the tomcat2.json
sample, which is located in the
/samples/cartridges/kubernetes/ directory, there was a
property named "name" under the "networkInterfaces" [1
Hi Martin,
We don't support any cycle in the startupOrder. It should be liner array
where you can plug each string array either to a new branch in the
dependency tree or to an existing node. Can you explain the startupOrder
pattern of those cartridges and groups? So that i can help on how to defin
Just as an extra pointer, I got the following definition to work (no exception):
{
"name": "s-n-gr-s-G12-t-a-2",
"dependencies": {
"terminationBehaviour": "terminate-dependents",
"startupOrders": [
"group.n-st-G2-t-a-2-0x0,cartridge.c1-0x0",
"cartridge.c1-0x0,cartridge.c2-0x
Hi,
I am defining the following application (see artifacts attached and screenshot)
and get the exception below, however I am not clear what is wrong in the
application definition, any pointers are appreciated,
Thanks
Martin
org.apache.stratos.autoscaler.exception.application.DependencyBuil
Mariangela Hills created STRATOS-1358:
-
Summary: Add addition information to API Resource Definitions
Key: STRATOS-1358
URL: https://issues.apache.org/jira/browse/STRATOS-1358
Project: Stratos
Hi Devs,
If you are creating Python Cartridge Agent plugins you can refer to the
README in the plugins folder inside the PCA component[1]. It has a detailed
guide on how to create plugins and how to make use of the Meta Data Service
client included in the PCA.
[1] -
https://github.com/apache/stra
Hi,
I'm not seeing this particular error (Could not terminate instance, member
context not found) when trying to immediately remove an application after
undeploying it. However I'm seeing the following stack trace with 500
status, when trying to delete cartridges immediately after application
unde
[
https://issues.apache.org/jira/browse/STRATOS-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521756#comment-14521756
]
Chamila de Alwis commented on STRATOS-1281:
---
I'm not seeing this particular er
Hi Devs,
We have now completed Apache Stratos 4.1.0-Beta2 developer preview. 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 and verifying
functionality.
*Main Features*
*-*
- Do
[
https://issues.apache.org/jira/browse/STRATOS-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-910:
Fix Version/s: (was: 4.1.0 M4)
4.1.0 RC1
> Create a Kubernetes Servi
[
https://issues.apache.org/jira/browse/STRATOS-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-956:
Fix Version/s: (was: 4.1.0 M4)
4.1.0 RC1
> Stratos successfully dele
[
https://issues.apache.org/jira/browse/STRATOS-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-940:
Fix Version/s: (was: 4.1.0 M4)
4.1.0 RC1
> Python Agent does not pub
[
https://issues.apache.org/jira/browse/STRATOS-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-950:
Fix Version/s: (was: 4.1.0 M4)
4.1.0 RC1
> update product licences f
[
https://issues.apache.org/jira/browse/STRATOS-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-665:
Fix Version/s: (was: 4.1.0 M4)
4.1.0 RC1
> REST API need to Manage V
[
https://issues.apache.org/jira/browse/STRATOS-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1138:
-
Fix Version/s: (was: 4.1.0 Beta)
4.1.0 RC1
> Document the update
[
https://issues.apache.org/jira/browse/STRATOS-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne resolved STRATOS-1169.
--
Resolution: Fixed
> Implement an Integration Test Server for Executing Automated Integ
[
https://issues.apache.org/jira/browse/STRATOS-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1296:
-
Fix Version/s: (was: 4.1.0 Alpha)
4.1.0 RC1
> Single group v1 sam
[
https://issues.apache.org/jira/browse/STRATOS-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1265:
-
Fix Version/s: (was: 4.1.0 RC1)
4.1.0 Beta2
> Dependency scaling
[
https://issues.apache.org/jira/browse/STRATOS-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1265:
-
Fix Version/s: (was: 4.1.0 Beta2)
4.1.0 RC1
> Dependency scaling
[
https://issues.apache.org/jira/browse/STRATOS-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne resolved STRATOS-1357.
--
Resolution: Fixed
Fixed with commit revision:
9e5fbf99db7c941bf1f40e380ed4ec131bbf0b84
[
https://issues.apache.org/jira/browse/STRATOS-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1357:
-
Fix Version/s: 4.1.0 Beta2
> Is Public Field is Not Used in Cartridge and Autoscaling Po
Imesh Gunaratne created STRATOS-1357:
Summary: Is Public Field is Not Used in Cartridge and Autoscaling
Policy
Key: STRATOS-1357
URL: https://issues.apache.org/jira/browse/STRATOS-1357
Project: St
[
https://issues.apache.org/jira/browse/STRATOS-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne resolved STRATOS-1348.
--
Resolution: Fixed
Removed groupScalingEnabled attribute in cartridge group. Changes pu
[
https://issues.apache.org/jira/browse/STRATOS-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishanth resolved STRATOS-1354.
---
Resolution: Fixed
fixed in the commit f8f9f7190956aef6f93a44f94f8641de12263914
> Validation the app
[
https://issues.apache.org/jira/browse/STRATOS-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishanth updated STRATOS-1354:
--
Description: Validating the application definition to ensure that the group
aliases are unique.
> Val
[
https://issues.apache.org/jira/browse/STRATOS-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1354:
-
Assignee: Vishanth
> Validation the application definition to ensure group aliases are u
Hi,It looks like this isn’t an issue in the latest 4.1 code, so that’s good.However, in the 4.1 code we’ve lost the ability to pass data about topology events to the extensions run by the cartridge agent. I’ve attached a diff which shows how I would add this functionality back. Basically I’d extend
[
https://issues.apache.org/jira/browse/STRATOS-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1354:
-
Fix Version/s: 4.1.0 Beta2
> Validation the application definition to ensure group alias
[
https://issues.apache.org/jira/browse/STRATOS-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1346:
-
Description: Adding payload parameters to network partitions. This
functionality will be
[
https://issues.apache.org/jira/browse/STRATOS-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-1348:
-
Description: GroupScalingEnabled attribute may not be needed as it can be
detected using
[
https://issues.apache.org/jira/browse/STRATOS-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1339:
---
Fix Version/s: 4.1.0 Beta2
> nested grouping fails to deploy with unequal ca
[
https://issues.apache.org/jira/browse/STRATOS-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu resolved STRATOS-1339.
Resolution: Fixed
> nested grouping fails to deploy with unequal cartridge
[
https://issues.apache.org/jira/browse/STRATOS-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan updated STRATOS-996:
--
Fix Version/s: FUTURE
> Standard 204 response not returned when deleting application pr
[
https://issues.apache.org/jira/browse/STRATOS-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan updated STRATOS-1275:
---
Fix Version/s: (was: 4.1.0 RC1)
4.1.0 Beta2
> Wrong HTTP stat
[
https://issues.apache.org/jira/browse/STRATOS-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan updated STRATOS-1278:
---
Fix Version/s: (was: 4.1.0 RC1)
4.1.0 Beta2
> Wrong HTTP stat
Hi All,
Followings are the notes for the discussion with mentor today.
1. Mastering Git/GitHub.
2. Research on stratos MB.
3. Dashboard Improvements.
These are the targets for the next week milestone.
Thank You!
Best Regards,
Ashan
On Thu, Apr 30, 2015 at 10:06 AM, Imesh Gunaratne wrote:
> As
[
https://issues.apache.org/jira/browse/STRATOS-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan updated STRATOS-990:
--
Fix Version/s: 4.1.0 Beta2
> Remove method for list of subscribed cartridges
>
[
https://issues.apache.org/jira/browse/STRATOS-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan updated STRATOS-972:
--
Fix Version/s: 4.1.0 Beta2
> Rewording Auto-scaling policy related resource paths
> ---
[
https://issues.apache.org/jira/browse/STRATOS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan updated STRATOS-987:
--
Fix Version/s: (was: 4.1.0 RC1)
4.1.0 Beta2
> Add meaningful par
[
https://issues.apache.org/jira/browse/STRATOS-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan updated STRATOS-971:
--
Fix Version/s: 4.1.0 Beta2
> Inconsistency in parameter naming used in coding comments
[
https://issues.apache.org/jira/browse/STRATOS-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan updated STRATOS-966:
--
Fix Version/s: 4.1.0 Beta2
> Inconsistency in parameter definition in REST API coding
>
[
https://issues.apache.org/jira/browse/STRATOS-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1353:
---
Fix Version/s: (was: 4.1.0 Beta2)
4.1.0 RC1
> nested
[
https://issues.apache.org/jira/browse/STRATOS-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan reopened STRATOS-996:
---
Seems some improvements can be done still.
> Standard 204 response not returned when del
[
https://issues.apache.org/jira/browse/STRATOS-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan resolved STRATOS-996.
---
Resolution: Fixed
Fixed according to the current code.
> Standard 204 response not r
[
https://issues.apache.org/jira/browse/STRATOS-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan resolved STRATOS-969.
---
Resolution: Fixed
Resolving since all the sub tickets are resolved.
> Improvements i
[
https://issues.apache.org/jira/browse/STRATOS-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan resolved STRATOS-971.
---
Resolution: Fixed
> Inconsistency in parameter naming used in coding comments
> -
Hi Reka,
Thank you for the clarifications.Yeah we can introduce validation with the
MAX values to secure the existing cluster over the update as mention below.
I think it will provide more stability in the existing deployment.
On Thu, Apr 30, 2015 at 12:52 PM, Reka Thirunavukkarasu
wrote:
> Hi
[
https://issues.apache.org/jira/browse/STRATOS-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521372#comment-14521372
]
Dakshika Jayathilaka commented on STRATOS-1355:
---
1. click on group templat
[
https://issues.apache.org/jira/browse/STRATOS-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521368#comment-14521368
]
Lahiru Sandaruwan commented on STRATOS-1355:
Yes.
> Cannot see/add groups u
[
https://issues.apache.org/jira/browse/STRATOS-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521365#comment-14521365
]
Dakshika Jayathilaka commented on STRATOS-1355:
---
Is this on Group Editor?
Hi Devs,
I am doing a test on the samples with the recent changes for beta2. If
anyone else is testing, it would be great if you could update this
spreadsheet [1] to keep track.
[1] -
https://docs.google.com/spreadsheets/d/1za0GDgQKGcWbijhjrNn9XEq0dSJRsOm4E0B_hTfGmB8/edit?usp=sharing
Regards,
Vi
Hi Vishanth,
Thanks for fixing it. I have merged this to master now..
Thanks,
Reka
On Thu, Apr 30, 2015 at 4:55 PM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:
> Hi,
>
> While testing the sample applications I noticed some curl commands were
> missing in the undeploy scripts.
> I upda
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/293
---
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
[
https://issues.apache.org/jira/browse/STRATOS-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1353:
---
Fix Version/s: (was: 4.1.0 RC1)
4.1.0 Beta2
> nested
[
https://issues.apache.org/jira/browse/STRATOS-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1353:
---
Fix Version/s: 4.1.0 RC1
> nested grouping scenario with startup and termina
[
https://issues.apache.org/jira/browse/STRATOS-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1353:
---
Assignee: Reka Thirunavukkarasu
> nested grouping scenario with startup and
[
https://issues.apache.org/jira/browse/STRATOS-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521354#comment-14521354
]
Reka Thirunavukkarasu commented on STRATOS-1353:
I have fixed the issue
Hi,
While testing the sample applications I noticed some curl commands were
missing in the undeploy scripts.
I updated those samples. Please review and merge the PR [1].
[1] - https://github.com/apache/stratos/pull/293
Regards,
Vishanth
On Thu, Apr 30, 2015 at 4:53 PM, Vishanth wrote:
> GitHu
GitHub user Vishanth opened a pull request:
https://github.com/apache/stratos/pull/293
Adding the removal of deployment policy and network partition in undeploy
Adding the removal of deployment policy and network partition in undeploy.sh
You can merge this pull request into a Git re
Hi,
Now the samples looks well organized. Next step would be adding Readme to
all the samples. Then we describe the capabilities of each.
Thanks.
On Thu, Apr 30, 2015 at 3:21 PM, Lakmal Warusawithana
wrote:
>
>
> On Thursday, April 30, 2015, Imesh Gunaratne wrote:
>
>> +1 Great work Isuru! Ma
Github user Vishanth commented on the pull request:
https://github.com/apache/stratos/pull/290#issuecomment-97738341
@imesh Sorry the changes removed while working on another task. Will redo
this and send a fresh PR.
---
If your project is set up for it, you can reply to this email a
Thanks for the verification. It looks good..Will merge it..
On Thu, Apr 30, 2015 at 4:19 PM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:
> Hi Reka,
>
> I tested the changes with the following sample applications.
>
>- nested-group
>- nested-group-v2
>- five-levels-nested-gro
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/292
---
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
Hi Reka,
I tested the changes with the following sample applications.
- nested-group
- nested-group-v2
- five-levels-nested-groups-app
Regards,
Vishanth
On Thu, Apr 30, 2015 at 4:17 PM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:
> Hi Reka,
>
> Please review and merge [1].
Hi Reka,
Please review and merge [1].
[1] - https://github.com/apache/stratos/pull/292
Regards,
Vishanth
On Thu, Apr 30, 2015 at 4:16 PM, Vishanth wrote:
> GitHub user Vishanth opened a pull request:
>
> https://github.com/apache/stratos/pull/292
>
> Validate application definition to
GitHub user Vishanth opened a pull request:
https://github.com/apache/stratos/pull/292
Validate application definition to have group with unique aliases
This is to validate the application definition to have group with unique
aliases.
You can merge this pull request into a Git repo
+1 looks great
On Thu, Apr 30, 2015 at 3:21 PM, Lakmal Warusawithana
wrote:
>
>
> On Thursday, April 30, 2015, Imesh Gunaratne wrote:
>
>> +1 Great work Isuru! May be we could include this in 4.1.0-beta2
>> developer preview.
>>
>>
> +1 for beta2
>
>
>
>> Thanks
>>
>> On Thu, Apr 30, 2015 at 11
Hi,
On Thu, Apr 30, 2015 at 3:11 PM, Isuru Haththotuwa
wrote:
> Hi,
>
> Bringing up this thread again, is this application a real world scenario?
> I had a look at the application json, and its seems just randomly nested to
> create a complex app. Shall we modify this application to suit a more
[
https://issues.apache.org/jira/browse/STRATOS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521272#comment-14521272
]
Lahiru Sandaruwan edited comment on STRATOS-1356 at 4/30/15 10:21 AM:
[
https://issues.apache.org/jira/browse/STRATOS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan resolved STRATOS-1356.
Resolution: Fixed
Fixed for Beta 2.
> Add and remove partitions to the deployment
Lahiru Sandaruwan created STRATOS-1356:
--
Summary: Add and remove partitions to the deployment policy
Key: STRATOS-1356
URL: https://issues.apache.org/jira/browse/STRATOS-1356
Project: Stratos
[
https://issues.apache.org/jira/browse/STRATOS-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Sandaruwan updated STRATOS-1297:
---
Issue Type: Improvement (was: Bug)
> Stratos 4.1.0: Updating deployment policy Min/
Github user Vishanth closed the pull request at:
https://github.com/apache/stratos/pull/290
---
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 e
GitHub user anuruddhal opened a pull request:
https://github.com/apache/stratos/pull/291
Refactoring REST API
Following Changes were done.
>Catch specific/custom exception - customize the log messages according to
exception type (addCartridge(), updateCartridge() etc.)
[
https://issues.apache.org/jira/browse/STRATOS-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1315:
---
Fix Version/s: (was: 4.1.0 Beta2)
4.1.0 RC1
> Two dif
[
https://issues.apache.org/jira/browse/STRATOS-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1315:
---
Fix Version/s: (was: 4.1.0 RC1)
4.1.0 Beta2
> Two dif
[
https://issues.apache.org/jira/browse/STRATOS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-964:
--
Fix Version/s: (was: 4.1.0 RC1)
4.1.0 Beta2
> Some REST
[
https://issues.apache.org/jira/browse/STRATOS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-964:
--
Assignee: Chamila de Alwis
> Some REST API are not returning response codes
> -
[
https://issues.apache.org/jira/browse/STRATOS-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1297:
---
Fix Version/s: 4.1.0 Beta2
> Stratos 4.1.0: Updating deployment policy Min/M
[
https://issues.apache.org/jira/browse/STRATOS-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1297:
---
Assignee: Lahiru Sandaruwan
> Stratos 4.1.0: Updating deployment policy Min/
[
https://issues.apache.org/jira/browse/STRATOS-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1348:
---
Fix Version/s: 4.1.0 Beta2
> GroupScalingEnabled Attribute is Redudant
> ---
[
https://issues.apache.org/jira/browse/STRATOS-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1350:
---
Issue Type: Improvement (was: Bug)
> fix scalingDependents to use alias in
[
https://issues.apache.org/jira/browse/STRATOS-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reka Thirunavukkarasu updated STRATOS-1351:
---
Issue Type: Improvement (was: Bug)
> Use scalingDependents instead of scali
On Thursday, April 30, 2015, Imesh Gunaratne wrote:
> +1 Great work Isuru! May be we could include this in 4.1.0-beta2 developer
> preview.
>
>
+1 for beta2
> Thanks
>
> On Thu, Apr 30, 2015 at 11:33 AM, Isuru Haththotuwa > wrote:
>
>> This is the new application samples structure:
>>
>> simp
Hi,
Bringing up this thread again, is this application a real world scenario? I
had a look at the application json, and its seems just randomly nested to
create a complex app. Shall we modify this application to suit a more
practical scenario/ simple remove it?
On Tue, Apr 21, 2015 at 11:12 AM, S
1 - 100 of 112 matches
Mail list logo
