Some things to look for that address some of the complexities within MaaS: - Can Twill handle long-running applications? - Does Twill provide any sort of name service abstraction or somesuch that lets us communicate with the app master after app deployment? - Does Twill provide any mechanism for impersonation (i.e. we can run the MaaS twill app as metron, but submit and run models as $user)?
On Tue, Apr 18, 2017 at 1:50 PM, Nick Allen <[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/ >
