openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Rutkowski" <mrutk...@us.ibm.com>
Subject Re: OpenWhisk, Kubernetes, what was learned and where we would like to go next.
Date Thu, 08 Jun 2017 14:53:42 GMT
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,
Matt 




From:   Ben Browning <bbrownin@redhat.com>
To:     dev@openwhisk.apache.org
Date:   06/07/2017 10:30 PM
Subject:        Re: OpenWhisk, Kubernetes, what was learned and where we 
would like to go next.



Dan,

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?

Thanks,

Ben


On Wed, Jun 7, 2017 at 4:16 PM, Daniel Lavine <dlavine@us.ibm.com> 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 
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
>





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