Mailing-List: contact dev-help@fluo.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@fluo.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAL4xCskDsecxqPPzPSeXP+0uA6wJ7TMQzvm=tKkGy7xMPK0U9w@mail.gmail.com>
References: <CAL4xCskDsecxqPPzPSeXP+0uA6wJ7TMQzvm=tKkGy7xMPK0U9w@mail.gmail.com>
From: Keith Turner <keith@deenlo.com>
Date: Tue, 23 May 2017 10:31:17 -0400
Message-ID: <CAGUtCHpmL40Ss9hsiRcBM17Cm=BvdGR_9O2TWbLEw5VJfeaMvw@mail.gmail.com>
Subject: Re: [DISCUSS] Improve how Fluo applications are run
To: dev@fluo.incubator.apache.org
Content-Type: text/plain; charset="UTF-8"
archived-at: Tue, 23 May 2017 14:31:28 -0000

On Fri, May 19, 2017 at 1:18 PM, Mike Walch <mwalch@apache.org> 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.


I want to help with this and work on parts of it, not sure which parts yet.