Date
1 - 20 of 42
[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
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
Ihor Dvoretskyi
+1 (non-binding).
On Mon, May 21, 2018 at 4:48 PM Chris Aniszczyk <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
Richard Hartmann
+1 non-binding
On Mon, May 21, 2018 at 3:48 PM Chris Aniszczyk <
caniszczyk@...> wrote:
On Mon, May 21, 2018 at 3:48 PM Chris Aniszczyk <
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
JJ
+1 (non-binding).
On Mon, May 21, 2018, 7:29 AM Bassam Tabbara <bassam@...> wrote:
+1 non-binding
Randy Abernethy
+1 nb
toggle quoted message
Show quoted text
On 2018-05-21 06:48, Chris Aniszczyk 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!
--
Randy Abernethy
Managing Partner
RX-M, LLC
randy.abernethy@...
o 415-800-2922
c 415-624-6447
Randy Abernethy
Managing Partner
RX-M, LLC
randy.abernethy@...
o 415-800-2922
c 415-624-6447
Sun, Ning
+1 non-binding.
Ning
toggle quoted message
Show quoted text
Ning
On May 21, 2018, at 6:54 AM, Richard Hartmann <richih@...> wrote:
+1 non-binding
+1 non-binding
toggle quoted message
Show quoted text
On May 21, 2018, at 9:48 AM, Chris Aniszczyk <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
+1 (non-binding)
On Mon, May 21, 2018 at 9:48 AM, Chris Aniszczyk <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
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:
+1 (non-binding)On Mon, May 21, 2018 at 9:48 AM, Chris Aniszczyk <caniszczyk@linuxfoundation.org> 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
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
Date: Monday, May 21, 2018 at 06:48
To: CNCF TOC <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 updatedcloud native definition:
"Cloud native technologies empower organizations to build and runscalable applications in modern, dynamic environments such as public,private, and hybrid clouds. Containers, service meshes, microservices,immutable infrastructure, and declarative APIs exemplify thisapproach.
These techniques enable loosely coupled systems that are resilient,manageable, and observable. Combined with robust automation, theyallow engineers to make high-impact changes frequently and predictablywith minimal toil.
The Cloud Native Computing Foundation seeks to drive adoption of thisparadigm by fostering and sustaining an ecosystem of open source,vendor-neutral projects. We democratize state-of-the-art patterns tomake these innovations accessible for everyone."
Please vote (+1/0/-1) by replying to this thread; the full definitionis located here: https://github.com/cncf/toc/pull/117
Remember that the TOC has binding votes only, but we do appreciatenon-binding votes from the community as a sign of support!
--Chris Aniszczyk (@cra) | +1-512-961-6719
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
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
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
Ken Owens
+1 binding
On Mon, May 21, 2018 at 10:21 AM, Quinton Hoole <quinton.hoole@...> wrote:
+1 (binding)
From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@linuxfoundation.org>
Date: Monday, May 21, 2018 at 06:48
To: CNCF TOC <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 runscalable applications in modern, dynamic environments such as public,private, and hybrid clouds. Containers, service meshes, microservices,immutable infrastructure, and declarative APIs exemplify thisapproach.
These techniques enable loosely coupled systems that are resilient,manageable, and observable. Combined with robust automation, theyallow engineers to make high-impact changes frequently and predictablywith minimal toil.
The Cloud Native Computing Foundation seeks to drive adoption of thisparadigm by fostering and sustaining an ecosystem of open source,vendor-neutral projects. We democratize state-of-the-art patterns tomake these innovations accessible for everyone."
Please vote (+1/0/-1) by replying to this thread; the full definitionis located here: https://github.com/cncf/toc/pull/117
Remember that the TOC has binding votes only, but we do appreciatenon-binding votes from the community as a sign of support!
--Chris Aniszczyk (@cra) | +1-512-961-6719
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.,
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
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.,
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.
"cloud-native technologies" in this sentence uses the adjective "cloud native" to describe technologies, but without a definition...
Containers, service meshes, microservices,
immutable infrastructure, and declarative APIs exemplify this
approach.
Shows some examples of this "cloud-native thing".. but still no definition...
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.
Some more benefits of this cloud-native thing, but still no definition....
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."
Vision statement for CNCF....
Maybe I'm missing it and I apologize!
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
Igor Mameshin
+1 (non-binding)
Looks great
On Mon, May 21, 2018 at 9:14 AM, Christian Posta <christian.posta@...> wrote:
-1 non-bindingNot seeing a definition here, honestly.On Mon, May 21, 2018 at 6:48 AM, Chris Aniszczyk <caniszczyk@linuxfoundation.org> 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."cloud-native technologies" in this sentence uses the adjective "cloud native" to describe technologies, but without a definition...Containers, service meshes, microservices,
immutable infrastructure, and declarative APIs exemplify this
approach.Shows some examples of this "cloud-native thing".. but still no definition...
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.Some more benefits of this cloud-native thing, but still no definition....
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."Vision statement for CNCF....Maybe I'm missing it and I apologize!
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
--
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
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:
-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.,
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."cloud-native technologies" in this sentence uses the adjective "cloud native" to describe technologies, but without a definition...
Containers, service meshes, microservices,
immutable infrastructure, and declarative APIs exemplify this
approach.
Shows some examples of this "cloud-native thing".. but still no definition...
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.
Some more benefits of this cloud-native thing, but still no definition....
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."
Vision statement for CNCF....
Maybe I'm missing it and I apologize!
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
--
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
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
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
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
Craig Peters
+1 non-binding
On Mon, May 21, 2018 at 10:38 AM Dan Kohn <dan@...> wrote:
Ken Owens will be leading an effort to revise the cloud native architecture diagram, which is the most direct driver of Landscape.On Mon, May 21, 2018 at 1:20 PM, Wilson, Dan <dan.wilson01@...> wrote:+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
--
Craig Peters | Director of Product, Partners | JFrog
http://www.jfrog.com | m: +1 925-639-0804 | skype: craig.l.peters