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....

This is the core of the definition. These are engineered attributes and required properties rather than accidental side effects.

 

 

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....

Mission, yes. This is intended to update the following section:

1. Mission of the Cloud Native Computing Foundation.
The Foundation’s mission is to create and drive the adoption of a new computing paradigm that is optimized for modern distributed systems environments capable of scaling to tens of thousands of self healing multi-tenant nodes.

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.

 

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

--

Christian Posta

twitter: @christianposta

http://blog.christianposta.com