Objections

Plan your projects and define important tasks and actions

Get Started. It's Free
or sign up with your email address
Rocket clouds
Objections by Mind Map: Objections

1. Evaluation

1.1. Scale

1.2. Not demonstrating helpfulness for programmers

1.3. Not enough bugs

1.4. Boring bugs

1.5. No eval of the extent non-determinism mitigation tricks helped

1.6. Don't demonstrate that replay/dd work on very long traces

1.7. Are MCSes actually minimal?

2. Practicality

2.1. Fuzzing

2.1.1. Catching irrelevant problems

2.1.2. Not being able to catch relevant problems

2.2. Too much work to achieve sufficiently "real" simulation

2.2.1. Simulating middleboxes

2.2.2. Simulating legacy devices

2.2.3. Simulating traditional routing protocols

2.2.4. Simulating vagaries of h/w failure modes

2.2.5. Not being able to reproduce asynchrony in a single process

2.3. Controller instrumentation difficult

2.4. Non-determinism considered fatal

2.4.1. "Exponential probability of triggering bug" via retries assumes i.i.d, which doesn't hold

3. Motivation

3.1. "Software engineering / debugging is trivial"

3.2. "The PC thought that solving the ultimate problem of finding the bug will be very difficult. "

4. Related Work

4.1. How is this different than general distributed systems debugging? i.e., No discussion of D3S, WiDs checker, et al.

4.2. Didn't frame well against "The criticial transition"

4.3. "Really a variant of common SE techniques"

4.4. Compare to program slicing

4.5. Didn't frame well against x-trace

5. Content

5.1. Not enough detail provided on approach

5.2. System isn't all that impressive

5.3. The paper doesn't show real SDN deployments, only simulation