So, one of the original visions was for MaaS to be fronted by a REST API to
submit artifacts and to provide code-free uses for common model types.  I
haven't thought about twill in a long time, but I'd be willing to move away
from raw Yarn API if we get some candy from Twill.

Casey

On Tue, Apr 18, 2017 at 2:34 PM, Simon Elliston Ball <
[email protected]> wrote:

> Right, how about some sort of REST API? Or through Ambari? What would you
> say was the best way to start the service, and of course to submit model
> artefacts?
>
> Simon
>
> > On 18 Apr 2017, at 11:33, Otto Fowler <[email protected]> wrote:
> >
> > In my mind, I didn’t want to deploy the service as a bash script or
> wrapped in one, if I recall correctly.
> >
> >
> >
> > On April 18, 2017 at 14:27:52, Simon Elliston Ball (
> [email protected] <mailto:[email protected]>) wrote:
> >
> >> Any particular issues, or things that didn’t work Otto?
> >>
> >> Simon
> >>
> >>
> >> > On 18 Apr 2017, at 11:26, Otto Fowler <[email protected]
> <mailto:[email protected]>> wrote:
> >> >
> >> > I’ll try to take a look. There are a couple of things I wanted to do
> with MaaS but could not
> >> > figure out because of a couple of limitations. I’d like to see if
> twill offers more flexibility
> >> >
> >> >
> >> >
> >> >
> >> > On April 18, 2017 at 13:50:39, Nick Allen ([email protected]
> <mailto:[email protected]>) wrote:
> >> >
> >> > I ran across the Apache Twill [1] project recently whose goal is to
> reduce
> >> > the complexity of developing distributed applications that run on
> YARN. My
> >> > first thought is that it might offer additional capabilities and/or
> >> > simplify our current MaaS implementation.
> >> >
> >> > Here are a list of features provided by Twill that I think might be
> useful
> >> > for MaaS.
> >> >
> >> > - Service discovery
> >> > - Elastic scaling
> >> > - High Availability
> >> > - Placement policies - Which rack/host should the model run on?
> >> > - Security - Kerberos ticket refresh?
> >> >
> >> > Just wanted to float the thought in the community and see if anyone
> has
> >> > experience with Twill. I need to do some more research myself.
> >> >
> >> > [1] http://twill.apache.org/ <http://twill.apache.org/>
> >>
>
>

Reply via email to