Multicast blocked?

2016-03-01 Thread David Wood
I'm building an Executor that uses a separate discovery service that 
relies on multicast.  If I run the executor without calling 
MesosExecutorDriver.run() the executor discovers other (non-mesos) nodes 
in my distributed set up just fine.  But if I call run(), then it does not 
discover the other nodes.  Interestingly, the other  nodes can discover my 
executor regardless of whether run() is called or not.   My executor is a 
Java app started using a command line task.  Any help is much appreciated. 
 


David Wood 
Computing Systems for Wireless Networks
IBM TJ Watson Research Center
daw...@us.ibm.com
914-945-4923 (office), 914-396-6515 (mobile)


Re: "Chaos monkey" for mesos?

2016-02-25 Thread David Wood
The DCOS tutorial mentions a chaos tool at the end of the video.  Not sure 
if that's what your looking for, but it might be something to follow up on 
somehow.

https://mesosphere.com/learn/

David Wood 
Computing Systems for Wireless Networks
IBM TJ Watson Research Center
daw...@us.ibm.com
914-945-4923 (office), 914-396-6515 (mobile)




From:   Srikanth Viswanathan <srikant...@gmail.com>
To: user@mesos.apache.org
Date:   02/25/2016 12:01 PM
Subject:"Chaos monkey" for mesos?



Has there been any work done to develop a "chaos monkey" analogue for 
Mesos? I have been researching on how to write one, but I wanted to know 
if there's any work already available that I can take a look at for 
comparison, and possibly re-use.

The end goal would be something loaded into Mesos or separate from Mesos 
that randomly kills tasks. Could it be something as simple as an 
application that uses the KILL HTTP request from the scheduler API to kill 
tasks?

Thanks.

Srikanth