> On Dec. 16, 2015, 2:39 p.m., Alexander Rukletsov wrote:
> > docs/authorization.md, line 43
> > <https://reviews.apache.org/r/40271/diff/5/?file=1156274#file1156274line43>
> >
> >     As I have already mentioned in a previous review, we do not really 
> > enforce it, do we? That's why I think "valid" is a bit too strong, what do 
> > you think?
> >     
> >     Same holds for create/destroy volumes.

I altered this text to be more descriptive of the current state of affairs, let 
me know if you think it should be changed further.


- Greg


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


On Dec. 18, 2015, 9:54 a.m., Greg Mann wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40271/
> -----------------------------------------------------------
> 
> (Updated Dec. 18, 2015, 9:54 a.m.)
> 
> 
> Review request for mesos, Jie Yu, Michael Park, and Neil Conway.
> 
> 
> Bugs: MESOS-3062 and MESOS-3065
>     https://issues.apache.org/jira/browse/MESOS-3062
>     https://issues.apache.org/jira/browse/MESOS-3065
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> Added documentation for RESERVE, UNRESERVE, CREATE, and DESTROY authorization.
> 
> 
> Diffs
> -----
> 
>   docs/authorization.md 1fc0e3f9a686480ffc4deb25e49f867318d1321a 
>   docs/persistent-volume.md cf7a6bbb6044e460293dd66066df87aded0b4fb8 
>   docs/reservation.md de447664f10b1d73211805b725f2284b07c609f6 
> 
> Diff: https://reviews.apache.org/r/40271/diff/
> 
> 
> Testing
> -------
> 
> This is the last in a chain of 7 patches.
> 
> This documentation was tested by viewing with the Mesos Website Container 
> (https://github.com/mesosphere/mesos-website-container).
> 
> `make check` was run after all patches in the chain were applied.
> 
> 
> Thanks,
> 
> Greg Mann
> 
>

Reply via email to