Hey Guys, I'd like to +1 non-binding Hoya (or whatever you want to call it). It's going to be really useful for the YARN ecosystem to have a project like this out there, and it makes a lot of sense to put it in Apache.
Hopefully we can move past the naming stuff, and get the project in. Cheers, Chris On Mon, Jan 20, 2014 at 12:32 PM, Tommaso Teofili <tommaso.teof...@gmail.com > wrote: > I just can speak for the Hama-to-Yarn use case (with my newbie hat on) and > it seems Hoya may be really helpful as the entry point to address it as it > provides a set of simple and useful tools. > For the sake of the names I think Hoya would be good (while Hyena would > not). > > Just my 0.02 cents, > Tommaso > > > 2014/1/17 Steve Loughran <ste...@hortonworks.com> > > > On 16 January 2014 12:41, Tommaso Teofili <tommaso.teof...@gmail.com> > > wrote: > > > > > Hi all, > > > > > > @Steve I'm curious to know if also Apache Hama may leverage Hoya to be > > > deployed on YARN. > > > > > > > > If you are going to make a 100% commit to running in YARN -which, if you > > aren't ready yet, Hama should be able to do in some point in the future- > > then I'd say "go for it!" and then point you at Twill to get you started. > > > > If all you are trying to do is deploy the BSP daemons in a YARN cluster, > > and they don't need any persistent localfs storage, then Hoya should > work. > > You already use ZK for the binding mechanism, don't you? > > > > > > If yes, that'd hopefully bring some more people involved from Hama as > well. > > > > > > > > > That'd be great! > > > > -- > > CONFIDENTIALITY NOTICE > > NOTICE: This message is intended for the use of the individual or entity > to > > which it is addressed and may contain information that is confidential, > > privileged and exempt from disclosure under applicable law. If the reader > > of this message is not the intended recipient, you are hereby notified > that > > any printing, copying, dissemination, distribution, disclosure or > > forwarding of this communication is strictly prohibited. If you have > > received this communication in error, please contact the sender > immediately > > and delete it from your system. Thank You. > > >
