[
https://issues.apache.org/jira/browse/STRATOS-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajkumar Rajaratnam resolved STRATOS-891.
-
Resolution: Fixed
Fixed in e2815f679ef4992147ffd70e842126249e01f6cd
> Different
And please note, this is VM LB support for docker containers. We might need
to support Docker LB too.
Thanks.
On Sat, Oct 25, 2014 at 9:56 AM, Imesh Gunaratne wrote:
> Hi,
>
> We have now fixed the following issues identified with the load balancer:
>
> - Fixed messaging component dependencies
On Sat, Oct 25, 2014 at 10:13 AM, Lakmal Warusawithana
wrote:
>
>
> On Sat, Oct 25, 2014 at 10:05 AM, Udara Liyanage wrote:
>
>> Hi Imesh,
>>
>> Do we allow policies which are in use to be updated?
>> My concern is say a user subscribe with a policy, is he affected if
>> another user update poli
On Sat, Oct 25, 2014 at 10:05 AM, Udara Liyanage wrote:
> Hi Imesh,
>
> Do we allow policies which are in use to be updated?
> My concern is say a user subscribe with a policy, is he affected if
> another user update policies later?
>
>
> Yes, these updates should only affect to a subscription no
Hi Imesh,
Do we allow policies which are in use to be updated?
My concern is say a user subscribe with a policy, is he affected if another
user update policies later?
Touched, not typed. Erroneous words are a feature, not a typo.
Hi All,
We have now implemented a new feature to allow users to update Autoscaling
and Deployment policies in runtime.
This feature is exposed via the REST API and the CLI has been updated with
two new commands:
update-autoscaling-policy -p
update-deployment-policy -p
Thanks
--
Imesh Gunar
Hi,
We have now fixed the following issues identified with the load balancer:
- Fixed messaging component dependencies in load balancer package.
- Fixed an issue in messaging component which raised a class cast exception
in debug mode.
- Added generated service host port to the member port map. T
Hi Isuru,
What I pointed out is not multiple logs. Status is changing to Terminating
to Terminating which is transition on same state. Other thing is state did
not become Terminated ever.
Touched, not typed. Erroneous words are a feature, not a typo.
Touched, not typed. Erroneous words are a feature, not a typo.
On Oct 24, 2014 10:28 PM, "Martin Eppel (meppel)" wrote:
>
> Hi Isuru,
>
>
>
> +1
>
>
>
> Please see a questions / comments inline
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> From: isu...@wso2.com [mailto:isu...@wso2.com] On Behalf Of Isuru
Hi Isuru,
Why CC set application status to Inactive? Application inactive state
refers to the state where its clusters or groups are not activated yet. May
be terminating is better, isn't it?
Touched, not typed. Erroneous words are a feature, not a typo.
Hi Isuru,
+1
Please see a questions / comments inline
Thanks
Martin
From: isu...@wso2.com [mailto:isu...@wso2.com] On Behalf Of Isuru Haththotuwa
Sent: Friday, October 24, 2014 8:28 AM
To: dev
Subject: [Discuss] [Service Grouping] Undeployment Process for a Composite
Application
Hi Devs,
The
Hi Devs,
The purpose of this thread is to discuss $subject.
I identified the following workflow:
1. Application owner undeploys the app via the rest API, using
application id
2. This will be notified to CC over a service call
3. CC updates the Cluster and Application statuses to 'Ina
Hi Udara,
AFAIU, this is normal.
In the single JVM setup, there are multiple message processors for one type
running, but they are updating a single Topology model. Therefore, the
first one updates it, and the subsequent ones see that it has been updated
already. That is why you are seeing multip
[
https://issues.apache.org/jira/browse/STRATOS-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182686#comment-14182686
]
Rajkumar Rajaratnam edited comment on STRATOS-859 at 10/24/14 11:32 AM:
---
[
https://issues.apache.org/jira/browse/STRATOS-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajkumar Rajaratnam resolved STRATOS-859.
-
Resolution: Fixed
Fixed in df7db412d1cb0de2431e04ea96b2b9b79a8c8263
> Unknown ho
Hi
This is to discuss about $subject. As we have identified from earlier
discussion that the termination behaviour can considered for
application/group as below:
*terminate-none* : none of them will be returned
*teminate-all*: all the children of a particular group will be terminated.
*terminat
[
https://issues.apache.org/jira/browse/STRATOS-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajkumar Rajaratnam resolved STRATOS-889.
-
Resolution: Fixed
Fixed in d189b136e7134b531714e22550eb1e785c0786de
> Move all d
[
https://issues.apache.org/jira/browse/STRATOS-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills closed STRATOS-909.
> Wiki -Typos in some REST API commands
> -
>
>
[
https://issues.apache.org/jira/browse/STRATOS-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills resolved STRATOS-909.
--
Resolution: Fixed
Fix Version/s: 4.1.0
Fixed in 4.0.0 and 4.1.0 docs.
> Wiki -T
[
https://issues.apache.org/jira/browse/STRATOS-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills updated STRATOS-909:
-
Component/s: Documentation
> Wiki -Typos in some REST API commands
>
[
https://issues.apache.org/jira/browse/STRATOS-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills updated STRATOS-909:
-
Attachment: Error.png
> Wiki -Typos in some REST API commands
> -
[
https://issues.apache.org/jira/browse/STRATOS-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills updated STRATOS-898:
-
Summary: Wiki - Add information on Messaging Component Architecture (was:
Add informatio
Mariangela Hills created STRATOS-909:
Summary: Wiki -Typos in some REST API commands
Key: STRATOS-909
URL: https://issues.apache.org/jira/browse/STRATOS-909
Project: Stratos
Issue Type: B
Hi Reka, Isuru,
Below is the stack trace I got when I undeployed an application. Please
note that status change from Terminating to Terminating. Application does
not reached Terminated event thereafter. Is this a normal state change?
[2014-10-24 14:40:44,430] INFO
{org.apache.stratos.messaging.
Hi,
Thanks Isuru & Reka for the clarification, yes I think that's the best
approach. Will try to figure out a better naming convention for these
events.
Thanks
On Fri, Oct 24, 2014 at 1:11 PM, Chamila De Alwis wrote:
>
> On Fri, Oct 24, 2014 at 11:23 AM, Lahiru Sandaruwan
> wrote:
>
>> May be
On Fri, Oct 24, 2014 at 11:23 AM, Lahiru Sandaruwan
wrote:
> May be we should follow similar naming convention for all the events of
> particular packages.
>
> E.g. All the application status event should be start with "
> ApplicationStatus..."
>
+1
I think this is the more pragmatic approach.
Hi Imesh,
We had to have a communication from Autoscaler to Topology on the status
changes of cluster, group and application which can be decided only by
autoscaler as it maintains the dependency information. Once autoscaler
decides on the status of cluster/group/application, it can't just publish
Hi Imesh,
This situation is similar to the Instance Status events (sent by CA) and
Member* events (sent by CC). Since CC updates the topology, we need to
first send the application status events to the relevant topic by AS, so
that CC can update the Topology and send the relevant Topology event.
T
What's the reason for having ApplicationActivated event in two topics?
On Fri, Oct 24, 2014 at 11:23 AM, Lahiru Sandaruwan
wrote:
>
>
> On Fri, Oct 24, 2014 at 11:08 AM, Udara Liyanage wrote:
>
>> Hi,
>>
>> We have events with the same name different packages which are confusing
>> to figure ou
29 matches
Mail list logo
