Re: Design doc for Mesos HTTP API

2015-05-02 Thread Isabel Jimenez
Hi Tom, If the initial subscription HTTP connection fails the scheduler will not be 'subscribed' ( or its old equivalent : 'registered' ) so it won't be possible to continue making other POST requests. Please refer to the disconnections part of the doc for more details on already 'subscribed' sche

Re: Design doc for Mesos HTTP API

2015-05-01 Thread Vinod Kone
On Fri, May 1, 2015 at 2:23 AM, Tom Arnfeld wrote: > Q: Could you explain in a little detail why the decision was made to use a > single HTTP endpoint rather than something like */event* (for the stream) > and */call* for making calls? It seems a little strange / contrived to me > that the differ

Re: Design doc for Mesos HTTP API

2015-05-01 Thread Tom Arnfeld
Thanks for sharing this Vinod, very clear and useful document! Q: Could you explain in a little detail why the decision was made to use a single HTTP endpoint rather than something like /eventĀ (for the stream) and /callĀ for making calls? It seems a little strange / contrived to me that the d

Re: Design doc for Mesos HTTP API

2015-04-30 Thread Vinod Kone
Revised and moved the doc over to: https://docs.google.com/document/d/1pnIY_HckimKNvpqhKRhbc9eSItWNFT-priXh_urR-T0/edit?usp=sharing Please take another look if you have seen the doc previously as there were some non-trivial changes (e.g., 1 endpoint instead of 2 endpoints). On Wed, Apr 29, 2015

Re: Design doc for Mesos HTTP API

2015-04-29 Thread Vinod Kone
I would like to take this opportunity to move the doc from Twitter domain so that I dont have to manually grant access to each new viewer. I'll post the new doc link tomorrow. @vinodkone > On Apr 29, 2015, at 8:54 AM, Isabel Jimenez > wrote: > > Hello, > > We made some final changes on t

Re: Design doc for Mesos HTTP API

2015-04-29 Thread Isabel Jimenez
Hello, We made some final changes on the doc, so I'm updating this thread to point out that all changes are reflected on a small prototype of the API that you can find here . Please feel free to comment on the new changes on the design doc. Thanks, Isabe

Re: Design doc for Mesos HTTP API

2015-03-09 Thread Vinod Kone
It is an artifact of the doc being hosted on twitter.com google apps domain :/ Gave you perms. I'll grant perms to anyone who requests it. On Mon, Mar 9, 2015 at 11:43 AM, James DeFelice wrote: > Google drive says that I need to request permission to access this. > > On Mon, Mar 9, 2015 at 2:3

Re: Design doc for Mesos HTTP API

2015-03-09 Thread James DeFelice
Google drive says that I need to request permission to access this. On Mon, Mar 9, 2015 at 2:31 PM, Vinod Kone wrote: > Hi, > > As you might've observed from the JIRA activity (MESOS-2288 > ), we have embarked on > the design of a new HTTP API fo

Design doc for Mesos HTTP API

2015-03-09 Thread Vinod Kone
Hi, As you might've observed from the JIRA activity (MESOS-2288 ), we have embarked on the design of a new HTTP API for Mesos. The link for the design doc is here