> From a user standpoint, what are the main differences from the current way of running Fluo apps?
>From a user perspective, the main differences are: * running Fluo applications is handled by downstream projects and upstream tarball is deprecated. These downstream projects share upstream code to keep them simple. * the fluo.properties file is split up into two files (connection.properties & application.properties). The application.properties file is only required for initialization. After initialization, these properties will be retrieved from Zookeeper. This allows a lot of commands like scanning, starting oracles & workers, etc to only require connection.properties and the application name. > Are your fluo-local and fluo-yarn repos functional? No.. they have scripts but need a lot of Java code written. > I noticed in some of the issues that the command had a package of core.command. I was thinking it may be better to put commands in their own module, so the commands can have a dependency like jcommander w/o adding that to core. Putting commands in their own module sounds good to me. On Mon, May 22, 2017 at 10:59 AM Keith Turner <[email protected]> wrote: > From a user standpoint, what are the main differences from the current > way of running Fluo apps? > > Are your fluo-local and fluo-yarn repos functional? > > I noticed in some of the issues that the command had a package of > core.command. I was thinking it may be better to put commands in > their own module, so the commands can have a dependency like > jcommander w/o adding that to core. > > On Fri, May 19, 2017 at 1:18 PM, Mike Walch <[email protected]> wrote: > > For Fluo 1.2, I would like to improve how Fluo applications are > > launched/run. This involves deprecating the current tarball distribution > > and creating downstream repos that create distributions for running Fluo > > applications locally and cluster managements tools suchs as YARN, Mesos, > > Kubernetes, etc. > > > > I have created repos for running Fluo locally and YARN and have started > to > > design their functionality by creating scripts and documentation. No Java > > code has been written yet. The repos will eventually be moved to Apache > > infrastructure. > > > > https://github.com/mikewalch/fluo-local > > https://github.com/mikewalch/fluo-yarn > > > > In order to complete this task, a lot of new functionality/commands need > to > > created upstream in Fluo. To coordinate this work, I created several > issues > > under the 1.2 milestone. > > > > https://github.com/apache/incubator-fluo/milestone/6 > > > > If you are interested in this work, review the documentation/scripts in > > fluo-local & fluo-yarn as well as the issues linked to above and let me > > know if you have any ideas or suggestions. >
