Thanks, Carlos and Matt
Glad it’s being taken care of.
Regards
Felix
> Am 30.05.2017 um 17:20 schrieb Carlos Santana :
>
> The domain that IBM/Andreas owns is openwhisk.org not openwhisk.io
>
> I think that ASF don't want to be in business of owning the burden of a $60
> monthly bill to pay fo
My name is Ben Browning and I lead the Serverless and
Function-as-a-Service engineering team at Red Hat. After much
research, evaluation, and internal discussion I'm pleased to announce
that we've decided to refocus our own Serverless efforts from the
Funktion project (https://funktion.fabric8.io/)
Please review/comment on my June 2017 report draft:
https://wiki.apache.org/incubator/June2017#preview
Kind regards,
Matt
Hi Ben,
That sounds awesome :). Welcome to the family and looking forward to working
with all of you.
Cheers,
Markus
Von meinem iPhone gesendet
> Am 31.05.2017 um 22:59 schrieb Ben Browning :
>
> My name is Ben Browning and I lead the Serverless and
> Function-as-a-Service engineering team at
Ben
Glad to have Red Hat on board, this is great news.
Want to echo Markus words "Welcome to the Family" !!!
--Carlos
On Wed, May 31, 2017 at 5:04 PM Markus Thömmes
wrote:
> Hi Ben,
>
> That sounds awesome :). Welcome to the family and looking forward to
> working with all of you.
>
> Cheer
Hi Tyson
Thanks for reaching out, having Mesos integration in OpenWhisk is something
I have heard some users asking about and any help to figure out how to best
integrate are very welcome.
As you already aware OpenWhisk Invoker is a critical path component
optimized for performance, to get those
Excellent news! Welcome!
> From: Ben Browning
> Subject: Red Hat and Apache OpenWhisk
>
> My name is Ben Browning and I lead the Serverless and
> Function-as-a-Service engineering team at Red Hat. After much
> research, evaluation, and internal discussion I'm pleased to announce
> that we've deci
Hey Ben et al,
welcome on board.
By the way:
If someone from RedHat sends me a logo I can add it to here asap:
http://openwhisk.org/supporters
I also think it may make sense to inform the world about this
collaboration via a short blog post to be added under our medium.com
channel: https://m
I believe a lot of Tyson's observations around Mesos integration also
apply to Kubernetes integration. For example, I've been experimenting
with an approach that replaces the DockerContainer with a
KubernetesContainer. The KubernetesContainer also ignores the pause
and resume of functions and also
Welcome Ben (and the Red Hat team)!
Looking forward to working with you all to make Apache OpenWhisk the best
open source Serverless platform (and eco-system) out there.
Kind regards,
Matt Rutkowski
On 2017-05-31 15:59 (-0500), Ben Browning wrote:
> My name is Ben Browning and I lead the Serv
Hey Ben,
This is exciting! I'm looking forward to seeing what you come up with.
Regards,
Rob...
> On 31 May 2017, at 21:59, Ben Browning wrote:
>
> My name is Ben Browning and I lead the Serverless and
> Function-as-a-Service engineering team at Red Hat. After much
> research, evaluation, an
Yeah I agree between Mesos and Kubernetes work there should be some common
integration extension points that would serve both use cases to some extent
On Wed, May 31, 2017 at 5:42 PM Ben Browning wrote:
> I believe a lot of Tyson's observations around Mesos integration also
> apply to Kubernet
Thanks.
One thing I think will help is isolating the http contract with containers from
the management (start/stop etc) of the container. (Currently the http api
client is built into the DockerContainer class)
After that, providing an interface for a configured container management would
be ab
13 matches
Mail list logo
