Re: Framework testing in Mesos

2014-10-14 Thread Dharmesh Kakadia
Thanks to both of you. @David Idempotence (and functional style) will both mitigate the issue of testing. @Sharma #3 looks impressive and I hear the pain. Few questions: * Since you already have the state machine modeling, can't the scheduler actions also be modeled as a state machine

Re: Framework testing in Mesos

2014-10-14 Thread Sharma Podila
@Sharma #3 looks impressive and I hear the pain. Few questions: * Since you already have the state machine modeling, can't the scheduler actions also be modeled as a state machine transitions? I suppose that is possible in theory. I am thinking that the scheduler state will have to be a

Framework testing in Mesos

2014-10-12 Thread Dharmesh Kakadia
Hi, I am working on a tiny experimental framework for Mesos. I was wondering what is the recommended way of writing testcases for framework testing. I looked at the several existing frameworks, but its still not clear to me. I understand that I might be able to test executor functionality in

Re: Framework testing in Mesos

2014-10-12 Thread David Greenberg
For our frameworks, we don't tend to do much automated testing of the Mesos interface--instead, we construct the framework state, then send it a message, since our callbacks take the state of the framework + the event as the argument. This way, we don't need to have mesos running, and we can trim

Re: Framework testing in Mesos

2014-10-12 Thread Dharmesh Kakadia
Thanks David. Taking state of the framework is an interesting design. I am assuming the scheduler is maintaining the state and then handing tasks on slaves. If that's the case, we can safely test executor (stateless - receiving event and returning appropriate status to the scheduler). You

Re: Framework testing in Mesos

2014-10-12 Thread Sharma Podila
Trying to test the framework in an automated way, I tend to think of the framework in these parts: 1. Executor 2. Scheduler's interaction with Mesos and state persistence 3. Scheduler's task assignment of resources I will skip #1, you covered that already and it depends largely on the kind of

Re: Framework testing in Mesos

2014-10-12 Thread David Greenberg
Specifically with regards to the state of the framework due to callback ordering, we ensure that our framework is written in a functional style, so that all callbacks atomically transform the previous state to a new state. By doing this, we serialize all callbacks. At this point, you can do