Hi Chamila,
Topology is structured in Service - > Cluster -> Member way. That is why it
has to iterate services in order to get members.
On Sat, Nov 15, 2014 at 11:57 AM, Imesh Gunaratne wrote:
> We could introduce a map to handle this.
>
> On Fri, Nov 14, 2014 at 11:45 PM, Chamila De Alwis
>
Hi,
While going through the code I tried to understand what the threads are
doing,
StratosManagerTopologyEventReceiver
creates TopologyEventReceiver and add event listerns - Not an iterative
process. See the run method just keep on sleeping while terminates become
true
TopologyEventReceiver
cre
Hi Jeffrey,
Seems like mqtt-client 1.0.0 maven artifact is not still published:
https://repo.eclipse.org/content/repositories/paho-releases/org/eclipse/paho/mqtt-client/
Thanks
On Sat, Nov 15, 2014 at 12:36 AM, Jeffrey Nguyen (jeffrngu) <
jeffr...@cisco.com> wrote:
>
> Thanks Udara and Isuru f
We could introduce a map to handle this.
On Fri, Nov 14, 2014 at 11:45 PM, Chamila De Alwis
wrote:
> Hi,
>
> Is there a direct way of doing $subject other than iterating through all
> the services from topology.getServices()?
>
> Service memberService = null;
> for (Service service: topology.get
Yes exactly, the complete topology event publisher might need to wait for
certain time period (may be few seconds) for complete topology request
messages before publishing. Otherwise it may publish the same message
number of times unnecessarily.
On Fri, Nov 14, 2014 at 11:37 PM, Udara Liyanage wr
Hi Devs,
I have now done following improvements in the messaging components:
Message Listeners are Directly Coupled with MQTT Library and Using ActiveMQ
TextMessage as the Message domain class
https://issues.apache.org/jira/browse/STRATOS-967
Introduce an Abstraction between the Message Broker T
[
https://issues.apache.org/jira/browse/STRATOS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-967:
Summary: Message Listeners are Directly Coupled with MQTT Library and Using
ActiveMQ TextMe
[
https://issues.apache.org/jira/browse/STRATOS-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne resolved STRATOS-968.
-
Resolution: Fixed
> Introduce an Abstraction between Message Broker Transport and Messagi
[
https://issues.apache.org/jira/browse/STRATOS-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213405#comment-14213405
]
Imesh Gunaratne commented on STRATOS-968:
-
Fixed with commit revision: 87ab43d0bf
[
https://issues.apache.org/jira/browse/STRATOS-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-968:
Fix Version/s: 4.1.0 M5
> Introduce an Abstraction between Message Broker Transport and Mes
[
https://issues.apache.org/jira/browse/STRATOS-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-968:
Description:
Currently in the messaging component there is no abstraction found between the
Imesh Gunaratne created STRATOS-968:
---
Summary: Introduce an Abstraction between Message Broker Transport
and Messaging Component Implementation
Key: STRATOS-968
URL: https://issues.apache.org/jira/browse/STRATOS
[
https://issues.apache.org/jira/browse/STRATOS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne resolved STRATOS-967.
-
Resolution: Fixed
Fixed with commit revision: 87ab43d0bf43373d813483494c551e8f69b7a4f8
>
[
https://issues.apache.org/jira/browse/STRATOS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-967:
Description:
With the introduction of MQTT in the messaging component all the message
list
[
https://issues.apache.org/jira/browse/STRATOS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-967:
Issue Type: Improvement (was: Bug)
> Message Listeners are Directly Coupled with MQTT Libr
[
https://issues.apache.org/jira/browse/STRATOS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-967:
Description:
With the introduction of MQTT in the messaging component all the message
list
[
https://issues.apache.org/jira/browse/STRATOS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne updated STRATOS-967:
Fix Version/s: 4.1.0 M5
> Message Listeners are Directly Coupled with MQTT Library
> --
Imesh Gunaratne created STRATOS-967:
---
Summary: Message Listeners are Directly Coupled with MQTT Library
Key: STRATOS-967
URL: https://issues.apache.org/jira/browse/STRATOS-967
Project: Stratos
Thanks for looking into this Vishanth.
IMO we should first try to implement something very basic which could do
the following:
- Have a test configuration file
- Get the latest stratos package
- Run the stratos installer (this should start a new stratos environment)
- Deploy artifacts
- At each st
[
https://issues.apache.org/jira/browse/STRATOS-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udara Liyanage resolved STRATOS-966.
Resolution: Fixed
fixed in 3576551e7f50353b83995085c94eaf178d103bc3
> Inconsistency in par
In the grouping specification we also discussed adding a group definition and a
group id to the instance events (InstanceActivatedEvent,
InstanceMaintenanceModeEvent, InstanceReadyToShutdownEvent,
InstanceStartedEvent).
The group definition would identify something like the group type (=== alia
Mariangela Hills created STRATOS-966:
Summary: Inconsistency in parameter definition in REST API coding
Key: STRATOS-966
URL: https://issues.apache.org/jira/browse/STRATOS-966
Project: Stratos
Thanks Udara and Isuru for your replies. I like the approach of doing retry
with incremental delay
Hi Imesh,
Please go ahead and implement this fix and also take care of the mqtt-client
upgrade.
Thanks,
-Jeffrey
From: Imesh Gunaratne mailto:im...@apache.org>>
Reply-To: "dev@stratos.apache.
Yes, better to do this improvement in all the message broker topic
listeners.
On Fri, Nov 14, 2014 at 1:36 PM, Chamila De Alwis wrote:
> Hi,
>
> Furthermore, it seems this is a pattern followed all over Stratos, where
> each component has a {component}{topic}EventReceiver runnable. Shouldn't we
Hi Jeffrey,
Thanks for bringing this up. I was thinking about this issue sometime back
and thought that may be we could start the retry interval with a small
value and then increase it step by step depending on the number of
continuous failures. I noticed this approach in Gmail.
I can do a quick
Hi,
Is there a direct way of doing $subject other than iterating through all
the services from topology.getServices()?
Service memberService = null;
for (Service service: topology.getServices()){
Cluster cluster = service.getCluster(clusterId);
if (cluster != null) {
if (cluster.g
Hi,
When a message is sent it is received by all subscribers. So we don't need
to send multiple times for multiple requests, isn't it Imesh?
Touched, not typed. Erroneous words are a feature, not a typo.
On Nov 14, 2014 11:15 PM, "Imesh Gunaratne" wrote:
> Hi Reka,
>
> On Fri, Nov 14, 2014 at
Hi Reka,
On Fri, Nov 14, 2014 at 11:56 AM, Reka Thirunavukkarasu
wrote:
Since we have CA also listening to Topology now, CA is taking ~1 minute to
receive the complete Topology as we send the Complete Topology in every 1
min. Can we reduce this by introducing a new topic where CA can publish an
Update;
On Fri, Nov 14, 2014 at 3:44 PM, Rajkumar Rajaratnam
wrote:
> Update;
>
> Currently facing an issue with upstream openstack-neutron-1.8.1.jar.
>
> When I see the MANIFEST.MF file of openstack-neutron-1.8.1.jar, it
> contains ${jclouds.version} in lot of places instead of actual version.
Hi Vishanth,
On Fri, Nov 14, 2014 at 5:25 PM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:
> A remote Openstack or EC2 instance will be used as the environment for the
> setup.
>
Can containers be also included, at a later stage if not possible
initially? For common scenarios I think th
Hi Vishanth,
Please send a PR by adding your scripts under /tools then others also can
have a look.
On Fri, Nov 14, 2014 at 5:38 PM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:
> Hi Udara,
>
> No I haven't committed the changes to stratos. Currently doing some parts
> manually, once th
Hi Udara,
No I haven't committed the changes to stratos. Currently doing some parts
manually, once that is completely I will commit it.
And yes I am scp-ing the necessary packs. Then will also look into sending
the log file back to the user's machine.
Thanks
On Fri, Nov 14, 2014 at 5:32 PM, Uda
Hi Martin,
I could get only the simple two dependent clusters working..When i tried
with your sample, i got few issues..I'm in the middle of testing the fix to
make it working..
I will do more testing on this and update you..
Thanks,
Reka
On Fri, Nov 14, 2014 at 10:55 AM, Reka Thirunavukkarasu
Hi Vishanth,
Have you committed the changes to Stratos?
You have to scp cartridge agent and LB also.
It is better if the script scp the log file back into the user's machine
when the test is complete.
On Fri, Nov 14, 2014 at 5:25 PM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:
> Hi De
Hi Devs,
Currently I am working on writing a script that will be used for an end to
end testing where the devs can use this script to do an integration test
after a build. Here I will provide the updates and progress on the work and
expect suggestions and feedback.
To give an overview, the basic
[
https://issues.apache.org/jira/browse/STRATOS-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa updated STRATOS-965:
--
Fix Version/s: (was: 4.1.0)
4.1.0 Alpha
> Application can not be
[
https://issues.apache.org/jira/browse/STRATOS-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa reassigned STRATOS-965:
-
Assignee: Isuru Haththotuwa
> Application can not be undeployed when moniter cre
[
https://issues.apache.org/jira/browse/STRATOS-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212137#comment-14212137
]
Isuru Haththotuwa commented on STRATOS-965:
---
Fixed in commit d1897ebd5634276104
[
https://issues.apache.org/jira/browse/STRATOS-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa updated STRATOS-965:
--
Fix Version/s: 4.1.0
> Application can not be undeployed when moniter creation is faile
Update;
Currently facing an issue with upstream openstack-neutron-1.8.1.jar.
When I see the MANIFEST.MF file of openstack-neutron-1.8.1.jar, it contains
${jclouds.version} in lot of places instead of actual version. Due to this
carbon feature installation is failing. Because it is processing
MANI
Hi,
Furthermore, it seems this is a pattern followed all over Stratos, where
each component has a {component}{topic}EventReceiver runnable. Shouldn't we
consider them too? If we do, then this will be a major test task.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.
41 matches
Mail list logo
