Thanks for the interest! We are actively working to make the Framework v1 API stable. We've made quite a few improvements/fixes to the Scheduler v1 API since 0.24.0. We've also introduced Executor v1 API in 0.28.0. Both are in *experimental* state.
There are still things left to do to make the Framework v1 API production ready. Please refer to MESOS-3302 <https://issues.apache.org/jira/browse/MESOS-3302> and MESOS-4855 <https://issues.apache.org/jira/browse/MESOS-4855> for specifics. Can you help contributing to any of these? Other than the issues listed above, we like frameworks to start testing this API in their staging/testing clusters. This would give us the most confidence to call it production ready. Can you help? I'm very optimistically hoping to get this ready by MesosCon Denver, but we need more help for it to be a realistic deadline. If any one is willing to help, please reach out to me. I promise to give you my time and shepherd your contributions. Thanks, On Wed, Mar 16, 2016 at 1:38 PM, Zameer Manji <[email protected]> wrote: > +1 > > I am also interested in knowing the state of the HTTP API. I have heard > that it stabilizing the API might be tied with Mesos 1.0 but I don't have a > source for that. Can a PMC member comment on what the plan is? > > On Mon, Mar 14, 2016 at 2:30 PM, Dario Rexin <[email protected]> wrote: > >> Hi all, >> >> since the introduction of the HTTP API in 0.24 around 7.5 months have >> passed. What are the plans to make this API stable? There are already >> features (inverse offers) that are exclusively available through this API, >> so it would be great to have a timeline, as I think for most people it’s >> impossible to use experimental features in production. >> >> Thanks, >> Dario >> >> -- >> Zameer Manji >> >>
