+1

+1 Mark From: <cncf-toc-bounces@...> on behalf of "Kenneth Owens (kenowens) via cncf-toc" <cncf-toc@...> Reply-To: "Kenneth Owens (kenowens)" <kenowens@...> Date: Tuesday, May 16, 2017 at 9:06

Ken, I would join for iguazio, we have high-perf “serverless” framework for internal use and will soon open-source it Seems like there is a consensus that serverless function portability

+1

thanks Sugu - that is helpful. If we are going to ask Kyle if he could 'do a jepsen', it would be very good to understand which consistency choices should be tested.

+1

I would like to participate. Thanks.

+1 This is great! Hyper.sh also built hyper func fully based on Kubernetes, and cooperating with IBM Whisk. Hope to be involved in the new WG! --- Harry

I will participate for Huawei and actively contribute to this effort. As I presented today, my key interest is consistent and portable user-facing configuration (event, function, event-function

Vitess offers different transaction modes and isolation levels as described here: http://vitess.io/user-guide/twopc.html#isolation. The choice depends on what an application can tolerate. In case of

+1 (non-binding) -- Craig Peters | Director of Product Management | www.scalr.com m: +1 925 639 0804 e: craig@... | skype: craig.l.peters

+1 (non-binding)

+1 (non-binding).

This transition: X --> scalable X, suggests we are seeing parallel evolutions of each category X. If so then we can ask what properties of X are preserved. Atomicity and durability only?

Again, the main value as I see it is that Vitess facilitates a transition from MySQL to a more scalable implementation (scalable enough for Youtube), without taking so big a leap as NoSQL. Sugu

+1! -- Benjamin Hindman Founder of Mesosphere and Co-Creator of Apache Mesos Mesosphere Inc. Follow us on Twitter: @mesosphere

a +1 here is sufficient for now Justin if you support the WG creation, here are the concrete goals for the proposed serverless WG atm: Provide clarity for ourselves and consumers w.r.t. what this

I agree this would be a useful group in the cncf but also have concerns discussed in earlier calls about being too early on trying to standardize a solution and possibly limit an evolving technology

As I mentioned on the call, IBM as a key participant in Open Whisk will be there. -Doug Sent from my iPhone

Hi Ken, Very interested! Please add me in. Thanks, Ying