HTTP API would be the recommended way for frameworks to interact with Mesos. The plan is to deprecate the driver based framework communication once we release 1.0 and remove the driver support in 2.0.
Current status: Scheduler HTTP API is in beta. We are still fixing bugs and adding features (e.g., authentication). Executor API implementation is in progress. I would not recommend upgrading production frameworks/clusters to HTTP API yet. But highly recommend testing out the beta scheduler http api in your testing/staging clusters and give us feedback. The more beta users and feedback we have, the sooner we could call HTTP API production ready. On Tue, Nov 24, 2015 at 7:01 AM, Klaus Ma <klaus1982...@gmail.com> wrote: > Hi team, > > My understanding to v1 HTTP API is that, it's used for API compatibility > between different mesos version. But what's scope of v1 HTTP API? Before > Mesos 1.0? And how/when should we upgrade API version? > > ---- > Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer > Platform Symphony/DCOS Development & Support, STG, IBM GCG > +86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me >
