[MESOS-5302] Consider adding an Executor Shim/Adapter for the new/old API

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Labels: mesosphere
• Epic Link: Executor API v1 improvements
• Sprint: Mesosphere Sprint 35
• Story Points: 5
• Assignee: Anand Mazumdar
• Reporter: Anand Mazumdar
• Shepherd: Vinod Kone
• Created: 28/Apr/16 19:04
• Updated: 05/Jul/16 22:01
• Resolved: 18/May/16 18:49

Description

Currently, all the business logic for HTTP based command executor/driver based command executor lives in 2 different files. As more features are added/bugs are discovered in the executor itself, they need to be fixed in two places. It would be nice to have some kind of a shim/adapter that abstracts away the underlying library details from the executor. Hence, the executor can toggle between whether it wants to use the driver or the new API via an environment variable.

Issue Links

• is related to: MESOS-5788 Added JAVA API adapter for seamless transition to new scheduler API.