Mailing-List: contact user-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@flink.apache.org
MIME-Version: 1.0
Sender: ewenstephan@gmail.com
In-Reply-To: <55B9CB41.7010700@ricobergmann.de>
References: <55B9CB41.7010700@ricobergmann.de>
Date: Thu, 30 Jul 2015 11:21:34 +0200
Message-ID: 
 <CANC1h_vZOMJr-Rdh+mf6PpkMSqVhHF0xLFPruSv48-sFWxuKjA@mail.gmail.com>
Subject: Re: optimal deployment model for Flink Streaming programs
From: Stephan Ewen <sewen@apache.org>
To: user@flink.apache.org
Content-Type: multipart/alternative; boundary=bcaec548a627c2bbb9051c143afc

--bcaec548a627c2bbb9051c143afc
Content-Type: text/plain; charset=UTF-8

I think what you outline is the right way to go for the time being.

The "Client" class is being reworked to bet more of these
deployment/controlling methods, to make it easier to deploy/cancel/restart
jobs programatically, but that will probably take a few more weeks to
converge.

Stephan


On Thu, Jul 30, 2015 at 8:59 AM, Dipl.-Inf. Rico Bergmann <
info@ricobergmann.de> wrote:

> Hi!
>
> We want to build an infrastructure for automated deployment of Flink
> Streaming programs to a dedicated environment. This includes automated
> tests (unit and integration) via Jenkins and in case of a successful
> build&test the program should be deployed to the execution environment.
>
> Since streaming programs run infinitely, the problem is to switch from the
> running program to the newly deployed. The CLI has some features that would
> make it possible (list, cancel). Is there another way of somehow restarting
> a streaming program? Do you have a suggested way for the deployment
> (automated!)?
>
> Regards
> Rico B.
>

--bcaec548a627c2bbb9051c143afc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think what you outline is the right way to go for the ti=
me being.<div><br></div><div>The &quot;Client&quot; class is being reworked=
 to bet more of these deployment/controlling methods, to make it easier to =
deploy/cancel/restart jobs programatically, but that will probably take a f=
ew more weeks to converge.</div><div><br></div><div>Stephan</div><div><br><=
/div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu=
, Jul 30, 2015 at 8:59 AM, Dipl.-Inf. Rico Bergmann <span dir=3D"ltr">&lt;<=
a href=3D"mailto:info@ricobergmann.de" target=3D"_blank">info@ricobergmann.=
de</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br>
<br>
We want to build an infrastructure for automated deployment of Flink Stream=
ing programs to a dedicated environment. This includes automated tests (uni=
t and integration) via Jenkins and in case of a successful build&amp;test t=
he program should be deployed to the execution environment.<br>
<br>
Since streaming programs run infinitely, the problem is to switch from the =
running program to the newly deployed. The CLI has some features that would=
 make it possible (list, cancel). Is there another way of somehow restartin=
g a streaming program? Do you have a suggested way for the deployment (auto=
mated!)?<br>
<br>
Regards<br>
Rico B.<br>
</blockquote></div><br></div>

--bcaec548a627c2bbb9051c143afc--