openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Lavine" <>
Subject Re: OpenWhisk, Kubernetes, what was learned and where we would like to go next.
Date Thu, 08 Jun 2017 17:41:52 GMT

Hey Ben,

I was thinking that it would be easiest for everyone to just make edits
comments on the wiki page. That way everything is just in one place and
people will not need to go back and forth between the email thread/wiki
page. But, if we need to grant privileges to everyone that wants to edit
the page that is also quite annoying. This is my first time using the
Apache wiki pages. It would be great if there are ways to grant privileges
on specific pages so anyone can comment. For now, I guess I'm alright just
giving privileges to people who wish to contribute, unless there is a mass
number of people asking for requests to edit. Then we can do something

Dan Lavine

From:	"Matt Rutkowski" <>
Date:	06/08/2017 09:54 AM
Subject:	Re: OpenWhisk, Kubernetes, what was learned and where we would
            like to go next.

Hi Ben,

I believe that I just gave you permissions to add pages, comments and
attachments (bbrowning ID). Let me know if this worked.

Kind regards,

From:   Ben Browning <>
Date:   06/07/2017 10:30 PM
Subject:        Re: OpenWhisk, Kubernetes, what was learned and where we
would like to go next.


Thanks for all the code and docs around the Kubernetes work! Is there
specific permissions we need to comment on the wiki doc? I'm logged in but
don't see a way to do that.

Also, would you prefer discussion via comments on the wiki page or here on
the dev list?



On Wed, Jun 7, 2017 at 4:16 PM, Daniel Lavine <> wrote:

> 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
> to put OpenWhisk on Kubernetes and are proposing an initial outline on
> we would like to start tackling them. Our solution basically boils down
> OpenWhisk becoming more "Dockerized" in the configuration phase. Meaning
> each of the components will have more configuration properties built
> them, or necessary scripts/startup actions that perform setup actions
> 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
> taking a look at the wiki where we are proposing our initial outline.
> Thanks!
> Dan Lavine

  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message