Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idiomatic way to get at task sandbox / logs? #243

Closed
wrouesnel opened this issue Apr 25, 2016 · 3 comments
Closed

Idiomatic way to get at task sandbox / logs? #243

wrouesnel opened this issue Apr 25, 2016 · 3 comments

Comments

@wrouesnel
Copy link

Possibly slightly peripheral to the main issues of Mesos bindings, but when writing schedulers a standard pattern would certainly be to interact with the sandbox and stdout/stderr files in particular?

It would be helpful if there was an idiomatic interface in the bindings for doing this - the HTTP only focus of the next branch might work in this capacity?

@jdef
Copy link
Contributor

jdef commented Apr 25, 2016

Thanks for bringing this up! It's possible. I briefly considered prototyping support for the other (non-v1) endpoints. Needs more thought. And it's a lower priority than making the v1 scheduler/executor API usable.

@jdef
Copy link
Contributor

jdef commented May 24, 2016

"Mesos v1 HTTP Operator API" https://docs.google.com/document/d/1XfgF4jDXZDVIEWQPx6Y4glgeTTswAAxw6j8dPDAtoeI/edit?pref=2&pli=1

@jdef
Copy link
Contributor

jdef commented Feb 5, 2017

several people have asked about maintenance / operator APIs, including #265

@jdef jdef closed this as completed Feb 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants