Mailing-List: contact dev-help@openwhisk.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openwhisk.apache.org
MIME-Version: 1.0
In-Reply-To: <OFF2A1A09E.B8ECF2E0-ON00258138.006F61EA@LocalDomain>
Subject: Re: OpenWhisk, Kubernetes, what was learned and where we would like to go
 next.
To: dev@openwhisk.apache.org
From: "Daniel Lavine" <dlavine@us.ibm.com>
Date: Wed, 7 Jun 2017 15:36:48 -0500
References: <OFF2A1A09E.B8ECF2E0-ON00258138.006F61EA@LocalDomain>
Content-type: multipart/related;
	Boundary="0__=8FBB0BABDFE371528f9e8a93df938690918c8FBB0BABDFE37152"
Message-Id: <OFA864058F.088B0687-ON00258138.0070F7C2-86258138.00713BA9@notes.na.collabserv.com>
archived-at: Wed, 07 Jun 2017 20:37:03 -0000

--0__=8FBB0BABDFE371528f9e8a93df938690918c8FBB0BABDFE37152
Content-type: multipart/alternative;
	Boundary="1__=8FBB0BABDFE371528f9e8a93df938690918c8FBB0BABDFE37152"


--1__=8FBB0BABDFE371528f9e8a93df938690918c8FBB0BABDFE37152
Content-Transfer-Encoding: quoted-printable
Content-type: text/plain; charset=US-ASCII


uh-oh. Looks like my links were removed.

Url for current OpenWhisk on Kubernetes work:
https://github.com/apache/incubator-openwhisk-deploy-kube
Url for proposal:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=3D70258567

Dan Lavine


From:	"Daniel Lavine" <dlavine@us.ibm.com>
To:	dev@openwhisk.incubator.apache.org
Date:	06/07/2017 03:16 PM
Subject:	OpenWhisk, Kubernetes, what was learned and where we would like
            to go next.


Hello everyone,

It has been a while since I last posted and previously it was for the
"Proposal for OpenWhisk + Kubernetes integration". I'm happy to tell you
that we got an initial deployment up and running with a decent amount of
documentation around it. For anyone who is interested in what has been
done, that work can be found here.

From that work, we have started to identify some of the oddities required
to put OpenWhisk on Kubernetes and are proposing an initial outline on how
we would like to start tackling them. Our solution basically boils down to
OpenWhisk becoming more "Dockerized" in the configuration phase. Meaning
each of the components will have more configuration properties built into
them, or necessary scripts/startup actions that perform setup actions once
done via Ansible. This way we can setup OpenWhisk on Kubernetes, Docker
Compose, or some other hosting environment without the need for an
orchestration layer. We would love for people to take a look at, comment
and make any suggestions for next steps to achieve this by heading over and
taking a look at the wiki where we are proposing our initial outline.

Thanks!
Dan Lavine


--1__=8FBB0BABDFE371528f9e8a93df938690918c8FBB0BABDFE37152
Content-Transfer-Encoding: quoted-printable
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline

<html><body><p><font size=3D"2">uh-oh. Looks like my links were removed.</f=
ont><br><br><font size=3D"2">Url for current OpenWhisk on Kubernetes work: =
</font><a href=3D"https://github.com/apache/incubator-openwhisk-deploy-kube=
"><font size=3D"2">https://github.com/apache/incubator-openwhisk-deploy-kub=
e</font></a><font size=3D"2"><br>Url for proposal: </font><a href=3D"https:=
//cwiki.apache.org/confluence/pages/viewpage.action?pageId=3D70258567"><fon=
t size=3D"2">https://cwiki.apache.org/confluence/pages/viewpage.action?page=
Id=3D70258567</font></a><br><br><font size=3D"2">Dan Lavine<br></font><br><=
br><img width=3D"16" height=3D"16" src=3D"cid:1=5F=5F=3D8FBB0BABDFE371528f9=
e8a93df938690918c8FB@" border=3D"0" alt=3D"Inactive hide details for &quot;=
Daniel Lavine&quot; ---06/07/2017 03:16:36 PM---Hello everyone, It has been=
 a while since I last posted a"><font size=3D"2" color=3D"#424282">&quot;Da=
niel Lavine&quot; ---06/07/2017 03:16:36 PM---Hello everyone, It has been a=
 while since I last posted and previously it was for the</font><br><br><fon=
t size=3D"2" color=3D"#5F5F5F">From:        </font><font size=3D"2">&quot;D=
aniel Lavine&quot; &lt;dlavine@us.ibm.com&gt;</font><br><font size=3D"2" co=
lor=3D"#5F5F5F">To:        </font><font size=3D"2">dev@openwhisk.incubator.=
apache.org</font><br><font size=3D"2" color=3D"#5F5F5F">Date:        </font=
><font size=3D"2">06/07/2017 03:16 PM</font><br><font size=3D"2" color=3D"#=
5F5F5F">Subject:        </font><font size=3D"2">OpenWhisk, Kubernetes, what=
 was learned and where we would like to go next.</font><br><hr width=3D"100=
%" size=3D"2" align=3D"left" noshade style=3D"color:#8091A5; "><br><br><br>=
<tt><font size=3D"2"><br><br>Hello everyone,<br><br>It has been a while sin=
ce I last posted and previously it was for the<br>&quot;Proposal for OpenWh=
isk + Kubernetes integration&quot;. I'm happy to tell you<br>that we got an=
 initial deployment up and running with a decent amount of<br>documentation=
 around it. For anyone who is interested in what has been<br>done, that wor=
k can be found here.<br><br>From that work, we have started to identify som=
e of the oddities required<br>to put OpenWhisk on Kubernetes and are propos=
ing an initial outline on how<br>we would like to start tackling them. Our =
solution basically boils down to<br>OpenWhisk becoming more &quot;Dockerize=
d&quot; in the configuration phase. Meaning<br>each of the components will =
have more configuration properties built into<br>them, or necessary scripts=
/startup actions that perform setup actions once<br>done via Ansible. This =
way we can setup OpenWhisk on Kubernetes, Docker<br>Compose, or some other =
hosting environment without the need for an<br>orchestration layer. We woul=
d love for people to take a look at, comment<br>and make any suggestions fo=
r next steps to achieve this by heading over and<br>taking a look at the wi=
ki where we are proposing our initial outline.<br><br>Thanks!<br>Dan Lavine=
<br></font></tt><br><br><BR>
</body></html>

--1__=8FBB0BABDFE371528f9e8a93df938690918c8FBB0BABDFE37152--


--0__=8FBB0BABDFE371528f9e8a93df938690918c8FBB0BABDFE37152--