|
Re: [VOTE] Cloud Native Definition
Gou Rao <grao@...>
+1, Non Binding On Mon, May 21, 2018 at 6:48 AM, Chris Aniszczyk <caniszczyk@...> wrote: The TOC worked with the community (i.e., |
|
|
|
CNCF Reference Architecture Update
Dan Kohn <dan@...>
In November 2016, the TOC approved this reference architecture. It's best known for being the basis of the cloud native landscape and interactive landscape. Ken Owens is starting an effort to revise the document. It is unlikely to need to be an actual working group, but we created a (public) mailing list to have a place to discuss things. We also have a Doodle poll for when to hold a twice a month meeting. If you're interested in participating, please join the mailing list. -- Dan Kohn <dan@...> Executive Director, Cloud Native Computing Foundation https://www.cncf.io +1-415-233-1000 https://www.dankohn.com |
|
|
|
Re: [VOTE] Cloud Native Definition
Kamezawa Hiroyuki
+1 (non-binding)
toggle quoted message
Show quoted text
-----Original Message----- |
|
|
|
Re: [VOTE] Cloud Native Definition
Justin Garrison <justinleegarrison@...>
+1 nb While I agree with the non-definition concerns I also don't think a strict definition is helpful or useful for the CNCF, its communities, or the companies looking to join to support its efforts. I like where this ended up and THANK YOU to Brian for all of your patience and iterations on seeing this through.
|
|
|
|
Re: [VOTE] Cloud Native Definition
Brian Grant
On Mon, May 21, 2018 at 9:14 AM Christian Posta <christian.posta@...> wrote:
This is the core of the definition. These are engineered attributes and required properties rather than accidental side effects.
Mission, yes. This is intended to update the following section: 1. Mission of the Cloud Native Computing Foundation. Cloud native systems will have the following properties: (a) Container packaged. Running applications and processes in software containers as an isolated unit of application deployment, and as a mechanism to achieve high levels of resource isolation. Improves overall developer experience, fosters code and component reuse and simplify operations for cloud native applications. (b) Dynamically managed. Actively scheduled and actively managed by a central orchestrating process. Radically improve machine efficiency and resource utilization while reducing the cost associated with maintenance and operations. (c) Micro-services oriented. Loosely coupled with dependencies explicitly described (e.g. through service endpoints). Significantly increase the overall agility and maintainability of applications. The foundation will shape the evolution of the technology to advance the state of the art for application management, and to make the technology ubiquitous and easily available through reliable interfaces.
|
|
|
|
Re: [VOTE] Cloud Native Definition
Camille Fournier
+1 binding On Mon, May 21, 2018 at 2:54 PM, Craig Peters <craigp@...> wrote:
|
|
|
|
Re: [VOTE] Cloud Native Definition
Craig Peters
+1 non-binding On Mon, May 21, 2018 at 10:38 AM Dan Kohn <dan@...> wrote:
--
Craig Peters | Director of Product, Partners | JFrog http://www.jfrog.com | m: +1 925-639-0804 | skype: craig.l.peters  |
|
|
|
Re: [VOTE] Cloud Native Definition
Dan Kohn <dan@...>
Ken Owens will be leading an effort to revise the cloud native architecture diagram, which is the most direct driver of Landscape. -- Dan Kohn <dan@...> Executive Director, Cloud Native Computing Foundation https://www.cncf.io +1-415-233-1000 https://www.dankohn.com On Mon, May 21, 2018 at 1:20 PM, Wilson, Dan <dan.wilson01@...> wrote: +1 non-binding |
|
|
|
Re: [VOTE] Cloud Native Definition
Wilson, Dan <dan.wilson01@...>
+1 non-binding
It would be interesting to see if this change of definition also changes which companies are listed on the landscape. Maybe this could feed into also updating the criteria for that? -Dan On 5/21/18, 6:48 AM, "cncf-toc@... on behalf of Chris Aniszczyk" <cncf-toc@... on behalf of caniszczyk@...> wrote: The TOC worked with the community (i.e., https://lists.cncf.io/g/cncf-toc/message/2004) to craft an updated cloud native definition: "Cloud native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach. These techniques enable loosely coupled systems that are resilient, manageable, and observable. Combined with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil. The Cloud Native Computing Foundation seeks to drive adoption of this paradigm by fostering and sustaining an ecosystem of open source, vendor-neutral projects. We democratize state-of-the-art patterns to make these innovations accessible for everyone." Please vote (+1/0/-1) by replying to this thread; the full definition is located here: https://github.com/cncf/toc/pull/117 Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support! -- Chris Aniszczyk (@cra) | +1-512-961-6719 |
|
|
|
Re: [VOTE] Cloud Native Definition
ibrahim.h@...
Hi Everyone,
First post for me on any CNCF list. I am very excited to be working with you all as we have more folks from Samsung Electronics getting engaged with CNCF.
With respect to this thread, this is not a vote but a mere suggestion for a sample definition that can be merged or reworded with the existing proposed language -- something in the spirit of: Cloud native is a technological approach to building, running and managing applications using cloud computing as a delivery model. The cloud native approach emphasizes the creation and deployment of applications and not the location of where these application would be running.
I can see Christian’s point below about hence my suggestion here.
Best regards, Ibrahim
From: cncf-toc@... <cncf-toc@...>
On Behalf Of Igor Mameshin
Sent: Monday, May 21, 2018 9:20 AM To: Christian Posta <christian.posta@...> Cc: Chris Aniszczyk <caniszczyk@...>; CNCF TOC <cncf-toc@...> Subject: Re: [cncf-toc] [VOTE] Cloud Native Definition
+1 (non-binding)
Looks great
On Mon, May 21, 2018 at 9:14 AM, Christian Posta <christian.posta@...> wrote:
|
|
|
|
Re: [VOTE] Cloud Native Definition
Igor Mameshin
+1 (non-binding) Looks great On Mon, May 21, 2018 at 9:14 AM, Christian Posta <christian.posta@...> wrote:
|
|
|
|
Re: [VOTE] Cloud Native Definition
Christian Posta
-1 non-binding Not seeing a definition here, honestly. On Mon, May 21, 2018 at 6:48 AM, Chris Aniszczyk <caniszczyk@...> wrote: The TOC worked with the community (i.e., "cloud-native technologies" in this sentence uses the adjective "cloud native" to describe technologies, but without a definition... Containers, service meshes, microservices, Shows some examples of this "cloud-native thing".. but still no definition...
Some more benefits of this cloud-native thing, but still no definition....
Vision statement for CNCF.... Maybe I'm missing it and I apologize!
|
|
|
|
Re: [VOTE] Cloud Native Definition
Brian Grant
+1 binding Thanks to everyone again for their help. On Mon, May 21, 2018 at 6:48 AM Chris Aniszczyk <caniszczyk@...> wrote: The TOC worked with the community (i.e., |
|
|
|
Re: [VOTE] Cloud Native Definition
Ken Owens
+1 binding On Mon, May 21, 2018 at 10:21 AM, Quinton Hoole <quinton.hoole@...> wrote:
|
|
|
|
Re: [VOTE] Cloud Native Definition
Yong Tang <ytang@...>
+1 non-binding From: cncf-toc@... <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Sent: Monday, May 21, 2018 6:48 AM To: CNCF TOC Subject: [cncf-toc] [VOTE] Cloud Native Definition The TOC worked with the community (i.e.,
https://lists.cncf.io/g/cncf-toc/message/2004) to craft an updated cloud native definition: "Cloud native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach. These techniques enable loosely coupled systems that are resilient, manageable, and observable. Combined with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil. The Cloud Native Computing Foundation seeks to drive adoption of this paradigm by fostering and sustaining an ecosystem of open source, vendor-neutral projects. We democratize state-of-the-art patterns to make these innovations accessible for everyone." Please vote (+1/0/-1) by replying to this thread; the full definition is located here: https://github.com/cncf/toc/pull/117 Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support! -- Chris Aniszczyk (@cra) | +1-512-961-6719 |
|
|
|
Re: [VOTE] Cloud Native Definition
Quinton Hoole
+1 (binding)
From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Monday, May 21, 2018 at 06:48 To: CNCF TOC <cncf-toc@...> Subject: [cncf-toc] [VOTE] Cloud Native Definition
|
|
|
|
Re: [VOTE] Cloud Native Definition
Ruben Orduz <ruben@...>
I'm a -1 (non-binding) on this. This is too fluffy and hand-wavy to be called a definition. This reads more like a mission statement than a definition: it actually doesn't define anything. Best, Ruben On Mon, May 21, 2018 at 10:58 AM, Chris Short via Lists.Cncf.Io <chris=chrisshort.net@...> wrote:
|
|
|
|
Re: [VOTE] Cloud Native Definition
+1 (non-binding) On Mon, May 21, 2018 at 9:48 AM, Chris Aniszczyk <caniszczyk@...> wrote: The TOC worked with the community (i.e., |
|
|
|
Re: [VOTE] Cloud Native Definition
+1 non-binding
toggle quoted message
Show quoted text
On May 21, 2018, at 9:48 AM, Chris Aniszczyk <caniszczyk@...> wrote: |
|
|
|
Re: [VOTE] Cloud Native Definition
Sun, Ning
+1 non-binding.
toggle quoted message
Show quoted text
Ning On May 21, 2018, at 6:54 AM, Richard Hartmann <richih@...> wrote: |
|
|