mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anand Mazumdar" <mazumdar.an...@gmail.com>
Subject Re: Review Request 41661: Added documentation for API versioning.
Date Wed, 23 Dec 2015 02:09:05 GMT


> On Dec. 22, 2015, 11:55 p.m., Guangya Liu wrote:
> > docs/versioning.md, line 36
> > <https://reviews.apache.org/r/41661/diff/2/?file=1174806#file1174806line36>
> >
> >     Not clear for what does " It would be really hard to debug an error that happens
with Scheduler v2 API, Executor v4 API interacting with Mesos cluster running Internal v6
API and Operator v7 API." mean? I think that even with API versioning, this problem is still
difficult to debug, how can the API version help this issue?
> 
> Anand Mazumdar wrote:
>     We have a single API version across all components in Mesos. So you won't ever run
into the version explosion problem i.e. you have different components running on different
versions.
>     
>     If any of the components have a backward compatible change it would result in a version
upgrade for all the components. Does this help clear things ?
> 
> Guangya Liu wrote:
>     Yes, I know what you mean, but the sentense here to me is more like to be: With API
versioning, I can make the Scheduler v2 API, Executor v4 API interacting with Mesos cluster
running Internal v6 API and Operator v7 API be easy to debug. what do you say?  ;-)
>     
>     What about refine the sentense as this: 
>     * **Avoiding version explosion**: It would be really hard to debug an error that
happens with Scheduler v2 API, Executor v4 API interacting with Mesos cluster running Internal
v6 API and Operator v7 API. By putting all the APIs under one version, we avoid the version
explosion problem.

Fixed.


- Anand


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41661/#review111689
-----------------------------------------------------------


On Dec. 22, 2015, 10:57 p.m., Anand Mazumdar wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41661/
> -----------------------------------------------------------
> 
> (Updated Dec. 22, 2015, 10:57 p.m.)
> 
> 
> Review request for mesos, Neil Conway and Vinod Kone.
> 
> 
> Bugs: MESOS-4192
>     https://issues.apache.org/jira/browse/MESOS-4192
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> This change adds documentation on how Mesos does API versioning. It also has a section:
> - On how API versioning and Release versioning are different.
> - API compatibility/upgrade guarantees.
> - Implementation Details.
> 
> Most of the information is taken from the design doc on Mesos HTTP API Versioning:
> https://docs.google.com/document/d/1-iQjo6778H_fU_1Zi_Yk6szg8qj-wqYgVgnx7u3h6OU/edit#
> 
> 
> Diffs
> -----
> 
>   docs/home.md 51c19bb9d0d74698fcdda6197d32ed8f4a57d7c9 
>   docs/versioning.md PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/41661/diff/
> 
> 
> Testing
> -------
> 
> https://gist.github.com/hatred/1cc6db05d0ca51397886
> 
> 
> Thanks,
> 
> Anand Mazumdar
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message