Many CNCF projects began life within a single company and then transitioned to be community-managed before or after being accepted into the CNCF. This document provides some guidelines on how the project’s website should evolve.

https://docs.google.com/document/d/1xcvMfPB1J21Pc4lJohQD0fEoy1iuBeFxrvqdFL-KA04/edit

I've run this document by the maintainers of each of the 7 projects, and (after some updates) all 7 of the project websites now follow these guidelines.

I'm looking to achieve rough consensus on this document amongst both the TOC and the CNCF marketing committee. If you have questions or concerns, please add comments to the Google Doc or reach out to me directly. If we seem to have consensus, I will post it to the CNCF Foundation GitHub repo.

--

Dan Kohn <mailto:dan@linuxfoundation.org>

Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

Two tiny addenda

Dan mentioned that cncf could help kube by eg funding editorial polish for otherwise raw content.

There was a discussion about the gamification of non-feature contributions, and the kube/cncf pilot of this.

On Wed, 1 Mar 2017, 18:09 Jonathan Boulle via cncf-toc, <cncf-toc@...> wrote:

Quick summary of the documentation talk in the call today:

- CNCF projects can reach out (Dan: please provide appropriate contact here) for assistance with contracting resources to help with documentation: CNCF will help with recruiting/logistics, then regularly look to project maintainers for approval of the work

- Most projects are using similar documentation sites already (simple Jekyll/GitHub hosted websites that render markdown), probably not a lot to add here

- Projects like Kubernetes are "too big to help" in the sense that they already have large, established infrastructure and processes around managing and publishing documentation; CNCF can help with some content though

- Brian G had concerns about long ramp-up time with random contractors; perhaps instead we can re-use a resource that becomes familiar with the projects (especially as they intersect)

- Another area Kubernetes could use help is homepage design - perhaps this is also something we can provide an optional consistent design for projects?

anything I missed?

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

Quick summary of the documentation talk in the call today:

- CNCF projects can reach out (Dan: please provide appropriate contact here) for assistance with contracting resources to help with documentation: CNCF will help with recruiting/logistics, then regularly look to project maintainers for approval of the work

- Most projects are using similar documentation sites already (simple Jekyll/GitHub hosted websites that render markdown), probably not a lot to add here

- Projects like Kubernetes are "too big to help" in the sense that they already have large, established infrastructure and processes around managing and publishing documentation; CNCF can help with some content though

- Brian G had concerns about long ramp-up time with random contractors; perhaps instead we can re-use a resource that becomes familiar with the projects (especially as they intersect)

- Another area Kubernetes could use help is homepage design - perhaps this is also something we can provide an optional consistent design for projects?

anything I missed?

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

I was unable to attend due to a scheduling conflict.
Is a recording available?

Cheers,
hh@...


On Thu, Mar 2, 2017 at 1:27 AM, Alexis Richardson via cncf-toc
<cncf-toc@...> wrote:
> here
>
> https://docs.google.com/presentation/d/1fOrZNcQpm8C1CghcK8bowyEWrIidrBL4lMi9OByNr6g/edit?ts=58b5fd42#slide=id.gd5ae4e962_2_136
> _______________________________________________
> cncf-toc mailing list
> cncf-toc@...
> https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

+benh

On Wed, Mar 1, 2017 at 3:18 PM, Alex Chircop via cncf-toc <cncf-toc@...> wrote:

 

We are making some updates to the doc based on some of the feedback.  

 

I do agree, we need to show how cloud native is different in terms of how you deploy and rebuild a POD, but I also believe that users are interested in how to manage the persistence that is required by the POD in terms of the databases, object stores, message queues and  instrumentation/logs that provide the services that POD requires for persistence.   The classes of storage that are used to build these services in terms of accessibility, performance, scalability, qos, portability are important, policy/scheduler based decisions such as security, encryption and placement are key, and for some there may still be dependencies on replication, snapshots etc …    This is why we wanted to flesh out some of the storage primitives that would be considered.

 

Question – would this discussion and the content that we are working on be a suitable topic for the newly defined storage working group ?

 

Thanks,

Alex

 

From: Yaron Haviv <yaronh@...>
Date: Friday, 24 February 2017 at 06:48
To: Alex Chircop <alex.chircop@...>, "Kitson, Clinton" <Clinton.Kitson@...>, "cncf-toc@..." <cncf-toc@...>

Subject: RE: [cncf-toc] Storage Patterns for container native - community content

 

Alex,

 

I agree with Clinton’s point that we want to focus on what makes Cloud-Native different, not sure covering all the legacy Storage protocols serves that purpose

There are too many users today that try to fit VM concepts into Cloud-Native and take us out of focus

The key point is allowing continuous development and ops, elasticity, distribution, ..

Looking at the 12 factors, notions of Stateless & immutable tasks, Service bindings (to data), Atomicity are enabling that

 

It’s a different craft than today’s storage approached as I highlighted in my blog post, e.g. you don’t snapshot/backup a POD, you build it from a Git tag

You use message queues to enable elastic scaling and fault-tolerance, you store data using atomic operations (to Obj/NoSQL) vs trust file-systems to flush data out and risk inconsistent states. For the guys who would argue they want to snapshot stateful services like Mongo/Cassandra/Object, a short reminder is those are un-coordinated scaled-out instances, and in many cases versioning and re-builds are built into it

 

Yaron

 

From: Alex Chircop [mailto:alex.chircop@storageos.com]
Sent: Friday, February 24, 2017 4:14 PM
To: Kitson, Clinton <Clinton.Kitson@...>; Yaron Haviv <yaronh@...>; cncf-toc@...
Subject: RE: [cncf-toc] Storage Patterns for container native - community content

 

Clinton / Yaron,

 

Thank you for the feedback.   We will get some of that added to the doc, although we were thinking of covering some of those topics in more depth in future articles.   We’ll update the draft and recirculate.

 

Thanks,

Alex

 

 

 

From: Kitson, Clinton [mailto:Clinton.Kitson@...m]
Sent: Thursday, February 23, 2017 4:11 AM
To: Yaron Haviv <yaronh@...>; Alex Chircop <alex.chircop@...>; cncf-toc@...
Subject: RE: [cncf-toc] Storage Patterns for container native - community content

 

Alex,

 

Sorry for the late review. My concern currently is that the document spends 80% of the time talking about what is known about some storage platforms today and the last portion discussing what looks to be technical details of a specific storage platform implementation. Cloud native with storage is definitely different, and just applying existing hardware thinking to this new area doesn't feel quite right.

 

Here are some of the questions that I think should be answered which leads towards a "what is cloud native storage topic".

 

What makes storage in cloud native computing different?

What cloud native applications require persistent storage of any form?

What kinds of storage services are used with cloud native applications?

What role does integration and interoperability play to build cloud native storage?

What opportunities do cloud native orchestrators present for operating persistent storage platforms?

What is cloud native storage?

 

 

Clint Kitson

Technical Director

{code} by Dell EMC

--- 

email: Clinton.Kitson@...

mobile: "+1 424 645 4116"

team: codeDellEMC.com

twitter: "@clintonskitson"

github: github.com/clintonskitson

---

From: cncf-toc-bounces@... [cncf-toc-bounces@...o] on behalf of Yaron Haviv via cncf-toc [cncf-toc@...]
Sent: Wednesday, February 22, 2017 11:23 AM
To: Alex Chircop; cncf-toc@...
Subject: Re: [cncf-toc] Storage Patterns for container native - community content

I wrote a post a while ago on impact of Cloud-Native on Storage, can reuse its content, you may want to take the abstraction to the next level just like we did on compute (from VMs to services/apps).

 

https://sdsblog.com/2015/09/16/cloud-native-will-shake-up-enterprise-storage/

 

Yaron

 

From: cncf-toc-bounces@... [mailto:cncf-toc-bounces@lists.cncf.io] On Behalf Of Alex Chircop via cncf-toc
Sent: Wednesday, February 22, 2017 6:31 PM
To: cncf-toc@...
Subject: Re: [cncf-toc] Storage Patterns for container native - community content

 

Hi,

 

We have prepared the content for the first topic in the list (albeit a little later than we hoped for).   This is the first doc we have produced and is meant to serve as an overview of storage concepts to provide some background before going into the more detailed content articles we are planning next.   We have tried to keep it fairly broad and have touched on some of the technologies found in many enterprises as well as in CN environments like virtual and distributed options.

 

I’d like to know your thoughts and get feedback and comments (I’m sure there will be loads) so that we can make it a better doc for the community.   Also, as per the previous request – we would be very happy to work with anybody else who might have some time to contribute!

 

Doc is here: https://docs.google.com/document/d/1ntdU4q4ZmfX-EyClxKAK6yaikQleg6maSeijDXi_u0c/edit?usp=sharing

 

Kind Regards,

Alex

 

 

Alex Chircop

Founder and CTO

T: +44 7968 948832

E: alex.chircop@...

W: http://storageOS.com

L: uk.linkedin.com/in/alexchircop/

Skype: chira001

 

 

This email and any attachments are confidential to the intended recipient and may also be privileged or copyrighted material.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient please delete it from your system and notify the sender.
StorageOS Ltd is a company registered in England and Wales with company number 9614942. Registered office address: 2 Minton Place, Victoria Road, Bicester, Oxfordshire, OX26 6QB.

 

 

 

 

 

From: Alex Chircop
Sent: Wednesday, February 1, 2017 3:50 PM
To: cncf-toc@...
Subject: Storage Patterns for container native - community content

 

Hi,

 

Following the discussion at the last TOC call, I’m attaching a doc to cover the topics that we are volunteering to generate for the community.   As background, we are proposing to focus this series on storage related patterns, starting with an overview and moving onto more complex use cases and examples.   We are planning to generate roughly an article a week on average for around ~3 months.

                                                  

I’m keen to understand if this is in line with what you think would be useful to the community and would be interested in any feedback and comments.   We would obviously be more than happy to work with anyone else who might be interested in contributing and/or any opportunity for joint work on any of the topics.

 

Doc is here: https://docs.google.com/document/d/14vVawyRcRRPm_mGZfl-tpQDCq2Q9aWxeHgdpZLAWnzU

 

Kind Regards,

Alex

 

 

Alex Chircop

Founder and CTO

T: +44 7968 948832

E: alex.chircop@...

W: http://storageOS.com

L: uk.linkedin.com/in/alexchircop/

Skype: chira001

 

 

This email and any attachments are confidential to the intended recipient and may also be privileged or copyrighted material.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient please delete it from your system and notify the sender.
StorageOS Ltd is a company registered in England and Wales with company number 9614942. Registered office address: 2 Minton Place, Victoria Road, Bicester, Oxfordshire, OX26 6QB.

 

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

 

We are making some updates to the doc based on some of the feedback.  

 

I do agree, we need to show how cloud native is different in terms of how you deploy and rebuild a POD, but I also believe that users are interested in how to manage the persistence that is required by the POD in terms of the databases, object stores, message queues and  instrumentation/logs that provide the services that POD requires for persistence.   The classes of storage that are used to build these services in terms of accessibility, performance, scalability, qos, portability are important, policy/scheduler based decisions such as security, encryption and placement are key, and for some there may still be dependencies on replication, snapshots etc …    This is why we wanted to flesh out some of the storage primitives that would be considered.

 

Question – would this discussion and the content that we are working on be a suitable topic for the newly defined storage working group ?

 

Thanks,

Alex

 

From: Yaron Haviv <yaronh@...>
Date: Friday, 24 February 2017 at 06:48
To: Alex Chircop <alex.chircop@...>, "Kitson, Clinton" <Clinton.Kitson@...>, "cncf-toc@..." <cncf-toc@...>

Subject: RE: [cncf-toc] Storage Patterns for container native - community content

 

Alex,

 

I agree with Clinton’s point that we want to focus on what makes Cloud-Native different, not sure covering all the legacy Storage protocols serves that purpose

There are too many users today that try to fit VM concepts into Cloud-Native and take us out of focus

The key point is allowing continuous development and ops, elasticity, distribution, ..

Looking at the 12 factors, notions of Stateless & immutable tasks, Service bindings (to data), Atomicity are enabling that

 

It’s a different craft than today’s storage approached as I highlighted in my blog post, e.g. you don’t snapshot/backup a POD, you build it from a Git tag

You use message queues to enable elastic scaling and fault-tolerance, you store data using atomic operations (to Obj/NoSQL) vs trust file-systems to flush data out and risk inconsistent states. For the guys who would argue they want to snapshot stateful services like Mongo/Cassandra/Object, a short reminder is those are un-coordinated scaled-out instances, and in many cases versioning and re-builds are built into it

 

Yaron

 

From: Alex Chircop [mailto:alex.chircop@storageos.com]
Sent: Friday, February 24, 2017 4:14 PM
To: Kitson, Clinton <Clinton.Kitson@...>; Yaron Haviv <yaronh@...>; cncf-toc@...
Subject: RE: [cncf-toc] Storage Patterns for container native - community content

 

Clinton / Yaron,

 

Thank you for the feedback.   We will get some of that added to the doc, although we were thinking of covering some of those topics in more depth in future articles.   We’ll update the draft and recirculate.

 

Thanks,

Alex

 

 

 

From: Kitson, Clinton [mailto:Clinton.Kitson@dell.com]
Sent: Thursday, February 23, 2017 4:11 AM
To: Yaron Haviv <yaronh@...>; Alex Chircop <alex.chircop@...>; cncf-toc@...
Subject: RE: [cncf-toc] Storage Patterns for container native - community content

 

Alex,

 

Sorry for the late review. My concern currently is that the document spends 80% of the time talking about what is known about some storage platforms today and the last portion discussing what looks to be technical details of a specific storage platform implementation. Cloud native with storage is definitely different, and just applying existing hardware thinking to this new area doesn't feel quite right.

 

Here are some of the questions that I think should be answered which leads towards a "what is cloud native storage topic".

 

What makes storage in cloud native computing different?

What cloud native applications require persistent storage of any form?

What kinds of storage services are used with cloud native applications?

What role does integration and interoperability play to build cloud native storage?

What opportunities do cloud native orchestrators present for operating persistent storage platforms?

What is cloud native storage?

 

 

Clint Kitson

Technical Director

{code} by Dell EMC

--- 

email: Clinton.Kitson@...

mobile: "+1 424 645 4116"

team: codeDellEMC.com

twitter: "@clintonskitson"

github: github.com/clintonskitson

---

From: cncf-toc-bounces@... [cncf-toc-bounces@....io] on behalf of Yaron Haviv via cncf-toc [cncf-toc@...]
Sent: Wednesday, February 22, 2017 11:23 AM
To: Alex Chircop; cncf-toc@...
Subject: Re: [cncf-toc] Storage Patterns for container native - community content

I wrote a post a while ago on impact of Cloud-Native on Storage, can reuse its content, you may want to take the abstraction to the next level just like we did on compute (from VMs to services/apps).

 

https://sdsblog.com/2015/09/16/cloud-native-will-shake-up-enterprise-storage/

 

Yaron

 

From: cncf-toc-bounces@... [mailto:cncf-toc-bounces@lists.cncf.io] On Behalf Of Alex Chircop via cncf-toc
Sent: Wednesday, February 22, 2017 6:31 PM
To: cncf-toc@...
Subject: Re: [cncf-toc] Storage Patterns for container native - community content

 

Hi,

 

We have prepared the content for the first topic in the list (albeit a little later than we hoped for).   This is the first doc we have produced and is meant to serve as an overview of storage concepts to provide some background before going into the more detailed content articles we are planning next.   We have tried to keep it fairly broad and have touched on some of the technologies found in many enterprises as well as in CN environments like virtual and distributed options.

 

I’d like to know your thoughts and get feedback and comments (I’m sure there will be loads) so that we can make it a better doc for the community.   Also, as per the previous request – we would be very happy to work with anybody else who might have some time to contribute!

 

Doc is here: https://docs.google.com/document/d/1ntdU4q4ZmfX-EyClxKAK6yaikQleg6maSeijDXi_u0c/edit?usp=sharing

 

Kind Regards,

Alex

 

 

Alex Chircop

Founder and CTO

T: +44 7968 948832

E: alex.chircop@...

W: http://storageOS.com

L: uk.linkedin.com/in/alexchircop/

Skype: chira001

 

 

This email and any attachments are confidential to the intended recipient and may also be privileged or copyrighted material.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient please delete it from your system and notify the sender.
StorageOS Ltd is a company registered in England and Wales with company number 9614942. Registered office address: 2 Minton Place, Victoria Road, Bicester, Oxfordshire, OX26 6QB.

 

 

 

 

 

From: Alex Chircop
Sent: Wednesday, February 1, 2017 3:50 PM
To: cncf-toc@...
Subject: Storage Patterns for container native - community content

 

Hi,

 

Following the discussion at the last TOC call, I’m attaching a doc to cover the topics that we are volunteering to generate for the community.   As background, we are proposing to focus this series on storage related patterns, starting with an overview and moving onto more complex use cases and examples.   We are planning to generate roughly an article a week on average for around ~3 months.

                                                  

I’m keen to understand if this is in line with what you think would be useful to the community and would be interested in any feedback and comments.   We would obviously be more than happy to work with anyone else who might be interested in contributing and/or any opportunity for joint work on any of the topics.

 

Doc is here: https://docs.google.com/document/d/14vVawyRcRRPm_mGZfl-tpQDCq2Q9aWxeHgdpZLAWnzU

 

Kind Regards,

Alex

 

 

Alex Chircop

Founder and CTO

T: +44 7968 948832

E: alex.chircop@...

W: http://storageOS.com

L: uk.linkedin.com/in/alexchircop/

Skype: chira001

 

 

This email and any attachments are confidential to the intended recipient and may also be privileged or copyrighted material.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient please delete it from your system and notify the sender.
StorageOS Ltd is a company registered in England and Wales with company number 9614942. Registered office address: 2 Minton Place, Victoria Road, Bicester, Oxfordshire, OX26 6QB.

 

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc