> On May 30, 2014, 12:38 p.m., Mark Chu-Carroll wrote:
> > docs/developing-aurora-client.md, line 5
> > <https://reviews.apache.org/r/22032/diff/1/?file=598888#file598888line5>
> >
> >     The executor is an important part of aurora - but how is it part of the 
> > client? The executor is entirely a cluster-side thing running on the slaves.
> >

The executor and client have an API that the scheduler knows nothing about (the 
thermos task config schema). Client changes need to be mindful and aware of 
that component. Enumerating the components here implies exclusivity, i.e. 
Thermos is not a "main piece" of Aurora.


- Kevin


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


On May 30, 2014, 12:40 p.m., Mark Chu-Carroll wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/22032/
> -----------------------------------------------------------
> 
> (Updated May 30, 2014, 12:40 p.m.)
> 
> 
> Review request for Aurora, David McLaughlin and Henry Saputra.
> 
> 
> Bugs: aurora-20
>     https://issues.apache.org/jira/browse/aurora-20
> 
> 
> Repository: aurora
> 
> 
> Description
> -------
> 
> first draft of a "developing client v2" document.
> 
> 
> Diffs
> -----
> 
>   docs/developing-aurora-client.md PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/22032/diff/
> 
> 
> Testing
> -------
> 
> n/a
> 
> 
> Thanks,
> 
> Mark Chu-Carroll
> 
>

Reply via email to