|
CNCF TOC Open Agenda - call for topics
all,
post the Tahoe f2f we agreed to run with a more "open agenda" for TOC calls.
PLEASE feel free to post topics to this thread over next 24 hours, and
I'll work with Chris A to devise an Agenda for the 1st March call this
week.
a
|
|
|
CNCF speaking opportunities
CNCF will be sponsoring and helping to program content for the events below. We would encourage you to have engineers from your companies propose talks on Kubernetes and other cloud native related topics. We have travel funding available for women and other under-represented minority presenters.
OpenStack Boston, MA - May 8 - 11 Kubernetes Day (May 9) CFP - closes on March 20
Open Source Summit Japan Tokyo, Japan - May 31 - June 2 CFP - closes on March 4 Co-located Automotive Linux Summit June 1 CFP - closes March 4 Fluentd Mini-Summit June 1 CFP - closes on March 15
LinuxCon ContainerCon CloudOpen Beijing, China - June 19 - June 20 CFP - closes on March 18
Open Source Summit North America Los Angeles, CA - September 11 - 13 CFP - closes on May 6
Open Source Summit Europe Prague, Czech Republic - October 23 - 25 CFP - closes on July 8
Questions? Please contact me and Katie Schultz < kschultz@...>. --
|
|
|
Re: 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
toggle quoted message
Show quoted text
From: Alex Chircop [mailto:alex.chircop@...]
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
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?
mobile: "+1 424 645 4116"
twitter: "@clintonskitson"
github: github.com/clintonskitson
From:
cncf-toc-bounces@... [cncf-toc-bounces@...] 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
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.
|
|
|
Re: Storage Patterns for container native - community content
Alex Chircop
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
toggle quoted message
Show quoted text
From: Kitson, Clinton [mailto:Clinton.Kitson@...]
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?
mobile: "+1 424 645 4116"
twitter: "@clintonskitson"
github: github.com/clintonskitson
From:
cncf-toc-bounces@... [cncf-toc-bounces@...] 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
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.
|
|
|
Re: ANN: Formation of Working Groups
If you are interested in hearing about the progress of the CI working group, I am planning on using the CI mailing list for public discussion. Please join that mailing list, cncf-ci-public@lists.cncf.io, as per Dan's email on the topic on Feb 1.
Thanks, Camille
On Mon, Feb 20, 2017 at 3:27 PM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote: All,
An agenda item for the TOC f2f was the possible formation of "working
groups". These have come up a number of times in the last 9+ months
since the TOC formed. The idea is to spawn CNCF TOC discussions off
into their own groups, with a stated topic and chairperson.
I am pleased to report that the TOC have reached consensus on this,
following discussions in Tahoe.
CNCF now has:
* Storage WG chaired by Ben Hindman
* CI WG chaired by Camille Fournier
* Cluster WG chaired by Bryan Cantrill
For now, WGs are chaired by TOC voting members. This is not a
perpetual requirement. Let's keep it that way until we know more.
As with CNCF OSS projects, WGs will be as self-governed as possible.
Some norms may emerge in time and even become rules.
As of today:
* Feel free to contact the named people to join discussions.
* Feel free to initiate discussions on the CNCF TOC list, pending
creation of lists / docs / whatever the WGs need.
* Feel free to request updates
alexis
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: Storage Patterns for container native - community content
Kitson, Clinton <Clinton.Kitson@...>
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
toggle quoted message
Show quoted text
From: cncf-toc-bounces@... [cncf-toc-bounces@...] 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@...]
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.
|
|
|
Re: Storage Patterns for container native - community content
toggle quoted message
Show quoted text
From: cncf-toc-bounces@... [mailto:cncf-toc-bounces@...]
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.
|
|
|
Re: Storage Patterns for container native - community content
Alex Chircop
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.
toggle quoted message
Show quoted text
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.
|
|
|
ANN: Formation of Working Groups
All,
An agenda item for the TOC f2f was the possible formation of "working
groups". These have come up a number of times in the last 9+ months
since the TOC formed. The idea is to spawn CNCF TOC discussions off
into their own groups, with a stated topic and chairperson.
I am pleased to report that the TOC have reached consensus on this,
following discussions in Tahoe.
CNCF now has:
* Storage WG chaired by Ben Hindman
* CI WG chaired by Camille Fournier
* Cluster WG chaired by Bryan Cantrill
For now, WGs are chaired by TOC voting members. This is not a
perpetual requirement. Let's keep it that way until we know more.
As with CNCF OSS projects, WGs will be as self-governed as possible.
Some norms may emerge in time and even become rules.
As of today:
* Feel free to contact the named people to join discussions.
* Feel free to initiate discussions on the CNCF TOC list, pending
creation of lists / docs / whatever the WGs need.
* Feel free to request updates
alexis
|
|
|
Re: Interesting tech marketing from Amazon
Andy, thanks, sure we should follow w “How” after the “Why”
Another reason for that order is to set the architecture context, e.g. many still view containers as lightweight VMs, can see requests for volume backup/snapshots, “vmotion”
.. those violate the cloud-native notion of “disposable” containers/micro-services (which enable reliability, changing versions on the fly, scaling-out, .. i.e. continuous dev & ops).
I assume once CNCF defines the why/goal we should come with a reference architecture of how to enable these next gen apps, e.g. see a great post from Brian Gracely on Cloud-Native
apps & data architecture:
http://wikibon.com/new-applications-require-a-modern-look-at-data-management/
Note how he captured both Biz/CIO level (why) messages with the tech details (how)
Yaron
toggle quoted message
Show quoted text
From: Andrew Randall [mailto:andy@...]
Sent: Saturday, February 18, 2017 3:50 AM
To: Brian Grant <briangrant@...>; Kitson, Clinton <Clinton.Kitson@...>; Tony Hsu <gosharplite@...>; Yaron Haviv <yaronh@...>; cncf-toc@...
Subject: Re: [cncf-toc] Interesting tech marketing from Amazon
I agree the emphasis of our outbound messaging should be on the why (and the "what's in it for me?"). And Yaron's suggestion of "because it gets you business agility through continuous dev and ops") sounds good to me as a first stab in
that direction. That's good marketing. It will certainly get someone interested if they hear that cloud native will help them make their business more agile.
However we also, I think, must define what "cloud native" actually is. Because once you've got them sold that cloud native has the right kind of attributes, they will want to know what it actually means to implement it. And if the answer is "cloud native is
anything that makes your business more agile" or just "continuous dev and ops" (with nothing to explain how that's achieved) then we will be perceived as nothing more than a marketing organization with no technical credibility.
At the risk of being controversial I would posit that has the following implications::
1) we must be somewhat opinionated about what makes something "cloud native" -- otherwise everything is cloud native (that obviously doesn't mean we have to say "you must use some specific technology" to be cloud native)
2) without a litmus test that most legacy apps and infrastructure technologies fail, then it is meaningless
3) similarly, in order to be meaningful, it must be possible for cloud native as we currently define it to be made obsolete in the future. (At which point we can wind down or redefine our mission -- but if our definition of cloud native continues to work whatever
the developments in technology in the future, then it's not specific enough.)
I really want CNCF to be perceived as relevant and pointing the way for the industry. If we just churn out platitudes (aka motherhood and apple pie) we will fail.
Andy
On Fri, Feb 17, 2017 at 2:43 PM Yaron Haviv via cncf-toc <cncf-toc@...> wrote:
If anyone care to watch Simon’s talk pointed by Tony: "people don't buy
WHAT you do, but WHY you do it", Containers, micro-services, .. are the
what, my point is we should focus on the Why
i.e. Why cloud-native? = e.g. enable biz agility through continuous dev & ops (or any other
suggestion)
Note that other points below like resiliency, speed of change, dynamic scaling .. All fall
under a bigger message of continuous dev & ops which solves the biggest challenge biz have: faster and sustainable digital transformation at lower budgets
The tech can be containers today, maybe server-less functions or whatever tomorrow, the key
is the collaboration and standardization driven by CNCF to reduce friction and complexity in the new stack
Yaron
Cc: Alexis Richardson via cncf-toc <cncf-toc@...>
Subject: Re: [cncf-toc] Interesting tech marketing from Amazon
I agree with some earlier comments about being too opinionated. A broad definition
could be "a computing environment focused on optimizing for applications in cloud operating models". This feels like the most natural and direct way to define cloud native computing while ensuring the relevance to how we are seeing people make use of it today
and tomorrow.
The definition leads to a lot of what was discussed in this thread.
- Requirements (interoperability/composability, automation/orchestration)
- Patterns (micro-services, scale-out, DevOps, CI)
- Components (cncf landscape)
- Benefits/features (resilience, scale, efficiency, resilience, portability)
mobile: "+1 424 645 4116"
twitter: "@clintonskitson"
On Feb 17, 2017 2:00 AM, "Tony Hsu via cncf-toc" <cncf-toc@...>
wrote:
As a big fan of Joe Beta and Craig McLuckie, my three ingredients for cloud-native operations are containers, orchestrators and
microservice frameworks. These three terms come from Craig's post announcing the start of Heptio.
https://goo.gl/aJgiQk
That's very concrete, and provides a framework for explaining what and why.
Our limbic brains are responsible for all of our feelings, like trust and loyalty. It's also responsible for all human behavior,
all decision-making, and it has no capacity for language. Please don't rely on logic and facts, it just doesn't drive behavior.
On Fri, Feb 17, 2017 at 4:37 PM, Yaron Haviv via cncf-toc <cncf-toc@...>
wrote:
I think the key message of Cloud-Native should be about its value:
Continuous Development and Operation (Enabling Business Agility/Transformation)
Decomposition to micro-services, stateless, disposable/distributed components,
Atomicity .. are the ways by which we achieve that goal, and those may evolve over time. If we want to engage more business owners lets focus on what’s in it for them and the need for a change vs tech buzzwords.
My 2c, Yaron
CTO, iguazio
On Tue, Feb 14, 2017 at 10:37 AM, Andrew Randall via cncf-toc <cncf-toc@...>
wrote:
I think we should aim for 3 core principles. Any more than that and people won't be able to repeat as a mantra.
Currently the charter has:
- micro-services oriented.
I like Mark's comments. However, I worry about "massive scale" as a message. LOTS of people I talked with at CloudNativeCon and
other shows recently have been doing fairly small scale deployments, but they're still cloud native. I think the nature of how we scale is important -- it's about the distributed, scale-out architectures that enable massive scale (but don't impose a cost burden
for the small development shop that's running on a half dozen VMs in AWS).
I think "Dynamically scalable" captures that better.
Management includes scaling, so IMO "dynamically managed" implies dynamic scaling, as well as a higher rate of change than people
had been accustomed to in the past.
In practice, the way this is achieved is through automation.
The inclusion of container-packaged and micro-services in the charter is an opinionated (and informed) stance about where the puck
is headed.
And you could add "built on open source foundation" as a fourth, or leave it implicit given the foundation nature of LF/CNCF.
On Tue, Feb 14, 2017 at 10:32 AM Mark Coleman via cncf-toc <cncf-toc@...>
wrote:
I agree that we may need to think more about how we communicate about microservices, but do we agree that the underlying purpose
of cloud native is:
1. Speed of change (I used to refer to this as agility but in general would like to avoid the term moving forwards)
2. Resilience (We should be able to change software quickly and not have it break due to internal or external factors)
3. Scale: We'd like to do really big stuff
If we know what problems we're solving it will be easier to talk about specific practices and tools in a coherent manner.
On Tue, Feb 14, 2017 at 10:24 AM Camille Fournier <skamille@...>
wrote:
Microservices are cloud native because they are a natural product of the ease of use for cloud. In a evolutionary way I would call
them absolutely cloud native, which doesn't mean one must use them to effectively use the cloud but they do effectively show how cloud changed the way developers thought about building systems.
On Feb 14, 2017 10:22 AM, "Alexis Richardson via cncf-toc" <cncf-toc@...>
wrote:
On Tue, Feb 14, 2017 at 10:20 AM Anthony Skipper <anthony@...>
wrote:
I'd argue that if you had good tools, you wouldn't need microservices.
Yes, I don't think microservices is a core value. It's one of several modern cloud native patterns that is useful for some organisational
and technical issues. But not the only one.
On Tue, Feb 14, 2017 at 1:15 PM, Mark Coleman via cncf-toc
<cncf-toc@...>
wrote:
I think I summarised it in this piece that I ghost wrote for Luke when he was at ClusterHQ (Friend D A please): https://www.infoq.com/articles/microservices-revolution
We have a cloud native triangle composed of:
1. Speed of change (I refer to this as agility in that doc but in general would like to avoid the term moving forwards)
2. Resilience (We should be able to change software quickly and not have it break due to internal or external factors)
3. Scale: We'd like to do really big stuff
From those core requirements we can rationalize containerization, microservices and continuous delivery.
From those 'practices' we can talk about specific tools.
Where we fall down is when we start from the tools, but obviously a large part of getting things right (especially microservices
I would argue) require pink matter.
On Tue, Feb 14, 2017 at 10:09 AM Alexis Richardson <alexis@...>
wrote:
yes
we need to develop a cloud native brand that has values which developers want
On Tue, Feb 14, 2017 at 10:07 AM Mark Coleman <mark@...>
wrote:
I like the model of bringing in end user stories to support the point being made.
The point here clearly seems to be "it's ok to move all your shit to the cloud snd figure it out there" which is an unsurprising
position for AWS to take. This is not an opposing point to our mission(TM) though so I will explore this.
Right now I'm mainly concerned that our definition of cloud native is not everyone else's.
On Thu, Feb 2, 2017 at 1:34 AM Alexis Richardson <alexis@...>
wrote:
I thought this was worth sharing as an example of the sort of tech-biz guidance that members of the CNCF community could write.
The piece is by someone from AWS and talks about cloud native vs other cloudy things.
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
|
|
|
Re: Interesting tech marketing from Amazon
I agree the emphasis of our outbound messaging should be on the why (and the "what's in it for me?"). And Yaron's suggestion of "because it gets you business agility through continuous dev and ops") sounds good to me as a first stab in that direction. That's good marketing. It will certainly get someone interested if they hear that cloud native will help them make their business more agile.
However we also, I think, must define what "cloud native" actually is. Because once you've got them sold that cloud native has the right kind of attributes, they will want to know what it actually means to implement it. And if the answer is "cloud native is anything that makes your business more agile" or just "continuous dev and ops" (with nothing to explain how that's achieved) then we will be perceived as nothing more than a marketing organization with no technical credibility.
At the risk of being controversial I would posit that has the following implications::
1) we must be somewhat opinionated about what makes something "cloud native" -- otherwise everything is cloud native (that obviously doesn't mean we have to say "you must use some specific technology" to be cloud native)
2) without a litmus test that most legacy apps and infrastructure technologies fail, then it is meaningless
3) similarly, in order to be meaningful, it must be possible for cloud native as we currently define it to be made obsolete in the future. (At which point we can wind down or redefine our mission -- but if our definition of cloud native continues to work whatever the developments in technology in the future, then it's not specific enough.)
I really want CNCF to be perceived as relevant and pointing the way for the industry. If we just churn out platitudes (aka motherhood and apple pie) we will fail.
Andy
On Fri, Feb 17, 2017 at 2:43 PM Yaron Haviv via cncf-toc < cncf-toc@...> wrote:
If anyone care to watch Simon’s talk pointed by Tony: "people don't buy
WHAT you do, but WHY you do it", Containers, micro-services, .. are the
what, my point is we should focus on the Why
i.e. Why cloud-native? = e.g. enable biz agility through continuous dev & ops (or any other suggestion)
Note that other points below like resiliency, speed of change, dynamic scaling .. All fall under a bigger message of continuous dev & ops which solves the biggest challenge
biz have: faster and sustainable digital transformation at lower budgets
The tech can be containers today, maybe server-less functions or whatever tomorrow, the key is the collaboration and standardization driven by CNCF to reduce friction and complexity
in the new stack
Yaron
Cc: Alexis Richardson via cncf-toc <cncf-toc@...>
Subject: Re: [cncf-toc] Interesting tech marketing from Amazon
I agree with some earlier comments about being too opinionated. A broad definition could be "a computing environment focused on optimizing for applications in cloud
operating models". This feels like the most natural and direct way to define cloud native computing while ensuring the relevance to how we are seeing people make use of it today and tomorrow.
The definition leads to a lot of what was discussed in this thread.
- Requirements (interoperability/composability, automation/orchestration)
- Patterns (micro-services, scale-out, DevOps, CI)
- Components (cncf landscape)
- Benefits/features (resilience, scale, efficiency, resilience, portability)
mobile: "+1 424 645 4116"
twitter: "@clintonskitson"
On Feb 17, 2017 2:00 AM, "Tony Hsu via cncf-toc" <cncf-toc@...> wrote:
As a big fan of Joe Beta and Craig McLuckie, my three ingredients for cloud-native operations are containers, orchestrators and microservice frameworks. These three terms come from Craig's post announcing the start
of Heptio. https://goo.gl/aJgiQk
That's very concrete, and provides a framework for explaining what and why.
Our limbic brains are responsible for all of our feelings, like trust and loyalty. It's also responsible for all human behavior, all decision-making, and it has no capacity for language. Please don't rely on logic
and facts, it just doesn't drive behavior.
On Fri, Feb 17, 2017 at 4:37 PM, Yaron Haviv via cncf-toc <cncf-toc@...> wrote:
I think the key message of Cloud-Native should be about its value:
Continuous Development and Operation (Enabling Business Agility/Transformation)
Decomposition to micro-services, stateless, disposable/distributed components, Atomicity .. are the ways
by which we achieve that goal, and those may evolve over time. If we want to engage more business owners lets focus on what’s in it for them and the need for a change vs tech buzzwords.
My 2c, Yaron
CTO, iguazio
On Tue, Feb 14, 2017 at 10:37 AM, Andrew Randall via cncf-toc <cncf-toc@...>
wrote:
I think
we should aim for 3 core principles. Any more than that and people won't be able to repeat as a mantra.
Currently the charter has:
- micro-services oriented.
I like Mark's comments. However, I worry about "massive scale" as a message. LOTS of people I talked with at CloudNativeCon and other shows recently have
been doing fairly small scale deployments, but they're still cloud native. I think the nature of how we scale is important -- it's about the distributed, scale-out architectures that enable massive scale (but don't impose a cost burden for the small development
shop that's running on a half dozen VMs in AWS).
I think "Dynamically scalable" captures that better.
Management includes scaling, so IMO "dynamically managed" implies dynamic scaling, as well as a higher rate of change than people had been accustomed to
in the past.
In practice, the way this is achieved is through automation.
The inclusion of container-packaged and micro-services in the charter is an opinionated (and informed) stance about where the puck is headed.
And you could add "built on open source foundation" as a fourth, or leave it implicit given the foundation nature of LF/CNCF.
On Tue, Feb 14, 2017 at 10:32 AM Mark Coleman via cncf-toc <cncf-toc@...>
wrote:
I agree that we may need to think more about how we communicate about microservices, but do we agree that the underlying purpose of cloud native is:
1. Speed of change (I used to refer to this as agility but in general would like to avoid the term moving forwards)
2. Resilience (We should be able to change software quickly and not have it break due to internal or external factors)
3. Scale: We'd like to do really big stuff
If we know what problems we're solving it will be easier to talk about specific practices and tools in a coherent manner.
On Tue, Feb 14, 2017 at 10:24 AM Camille Fournier <skamille@...>
wrote:
Microservices are cloud native because they are a natural product of the ease of use for cloud. In a evolutionary way I would call them absolutely cloud
native, which doesn't mean one must use them to effectively use the cloud but they do effectively show how cloud changed the way developers thought about building systems.
On Feb 14, 2017 10:22 AM, "Alexis Richardson via cncf-toc" <cncf-toc@...>
wrote:
On Tue, Feb 14, 2017 at 10:20 AM Anthony Skipper <anthony@...>
wrote:
I'd argue that if you had good tools, you wouldn't need microservices.
Yes, I don't think microservices is a core value. It's one of several modern cloud native patterns that is useful for some organisational and technical
issues. But not the only one.
On Tue, Feb 14, 2017 at 1:15 PM, Mark Coleman via cncf-toc
<cncf-toc@...>
wrote:
I think I summarised it in this piece that I ghost wrote for Luke when he was at ClusterHQ (Friend D A please): https://www.infoq.com/articles/microservices-revolution
We have a cloud native triangle composed of:
1. Speed of change (I refer to this as agility in that doc but in general would like to avoid the term moving forwards)
2. Resilience (We should be able to change software quickly and not have it break due to internal or external factors)
3. Scale: We'd like to do really big stuff
From those core requirements we can rationalize containerization, microservices and continuous delivery.
From those 'practices' we can talk about specific tools.
Where we fall down is when we start from the tools, but obviously a large part of getting things right (especially microservices I would argue) require
pink matter.
On Tue, Feb 14, 2017 at 10:09 AM Alexis Richardson <alexis@...>
wrote:
yes
we need to develop a cloud native brand that has values which developers want
On Tue, Feb 14, 2017 at 10:07 AM Mark Coleman <mark@...>
wrote:
I like the model of bringing in end user stories to support the point being made.
The point here clearly seems to be "it's ok to move all your shit to the cloud snd figure it out there" which is an unsurprising position for AWS to take.
This is not an opposing point to our mission(TM) though so I will explore this.
Right now I'm mainly concerned that our definition of cloud native is not everyone else's.
On Thu, Feb 2, 2017 at 1:34 AM Alexis Richardson <alexis@...>
wrote:
I thought this was worth sharing as an example of the sort of tech-biz guidance that members of the CNCF community could write. The piece is by someone
from AWS and talks about cloud native vs other cloudy things.
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
--
Andrew Randall CEO Tigera, Inc. 510-520-0999
|
|
|
Re: Interesting tech marketing from Amazon
If anyone care to watch Simon’s talk pointed by Tony: "people don't buy
WHAT you do, but WHY you do it", Containers, micro-services, .. are the
what, my point is we should focus on the Why
i.e. Why cloud-native? = e.g. enable biz agility through continuous dev & ops (or any other suggestion)
Note that other points below like resiliency, speed of change, dynamic scaling .. All fall under a bigger message of continuous dev & ops which solves the biggest challenge
biz have: faster and sustainable digital transformation at lower budgets
The tech can be containers today, maybe server-less functions or whatever tomorrow, the key is the collaboration and standardization driven by CNCF to reduce friction and complexity
in the new stack
Yaron
toggle quoted message
Show quoted text
From: cncf-toc-bounces@... [mailto:cncf-toc-bounces@...]
On Behalf Of Kitson, Clinton via cncf-toc
Sent: Friday, February 17, 2017 11:17 PM
To: Brian Grant <briangrant@...>; Tony Hsu <gosharplite@...>
Cc: Alexis Richardson via cncf-toc <cncf-toc@...>
Subject: Re: [cncf-toc] Interesting tech marketing from Amazon
I agree with some earlier comments about being too opinionated. A broad definition could be "a computing environment focused on optimizing for applications in cloud
operating models". This feels like the most natural and direct way to define cloud native computing while ensuring the relevance to how we are seeing people make use of it today and tomorrow.
The definition leads to a lot of what was discussed in this thread.
- Requirements (interoperability/composability, automation/orchestration)
- Patterns (micro-services, scale-out, DevOps, CI)
- Components (cncf landscape)
- Benefits/features (resilience, scale, efficiency, resilience, portability)
mobile: "+1 424 645 4116"
twitter: "@clintonskitson"
github: github.com/clintonskitson
From:
cncf-toc-bounces@... [cncf-toc-bounces@...]
on behalf of Brian Grant via cncf-toc [cncf-toc@...]
Sent: Friday, February 17, 2017 12:32 PM
To: Tony Hsu
Cc: Alexis Richardson via cncf-toc
Subject: Re: [cncf-toc] Interesting tech marketing from Amazon
On Feb 17, 2017 2:00 AM, "Tony Hsu via cncf-toc" <cncf-toc@...> wrote:
As a big fan of Joe Beta and Craig McLuckie, my three ingredients for cloud-native operations are containers, orchestrators and microservice frameworks. These three terms come from Craig's post announcing the start
of Heptio. https://goo.gl/aJgiQk
That's very concrete, and provides a framework for explaining what and why.
Our limbic brains are responsible for all of our feelings, like trust and loyalty. It's also responsible for all human behavior, all decision-making, and it has no capacity for language. Please don't rely on logic
and facts, it just doesn't drive behavior.
On Fri, Feb 17, 2017 at 4:37 PM, Yaron Haviv via cncf-toc <cncf-toc@...> wrote:
I think the key message of Cloud-Native should be about its value:
Continuous Development and Operation (Enabling Business Agility/Transformation)
Decomposition to micro-services, stateless, disposable/distributed components, Atomicity .. are the ways
by which we achieve that goal, and those may evolve over time. If we want to engage more business owners lets focus on what’s in it for them and the need for a change vs tech buzzwords.
My 2c, Yaron
CTO, iguazio
On Tue, Feb 14, 2017 at 10:37 AM, Andrew Randall via cncf-toc <cncf-toc@...>
wrote:
I think
we should aim for 3 core principles. Any more than that and people won't be able to repeat as a mantra.
Currently the charter has:
- micro-services oriented.
I like Mark's comments. However, I worry about "massive scale" as a message. LOTS of people I talked with at CloudNativeCon and other shows recently have
been doing fairly small scale deployments, but they're still cloud native. I think the nature of how we scale is important -- it's about the distributed, scale-out architectures that enable massive scale (but don't impose a cost burden for the small development
shop that's running on a half dozen VMs in AWS).
I think "Dynamically scalable" captures that better.
Management includes scaling, so IMO "dynamically managed" implies dynamic scaling, as well as a higher rate of change than people had been accustomed to
in the past.
In practice, the way this is achieved is through automation.
The inclusion of container-packaged and micro-services in the charter is an opinionated (and informed) stance about where the puck is headed.
And you could add "built on open source foundation" as a fourth, or leave it implicit given the foundation nature of LF/CNCF.
On Tue, Feb 14, 2017 at 10:32 AM Mark Coleman via cncf-toc <cncf-toc@...>
wrote:
I agree that we may need to think more about how we communicate about microservices, but do we agree that the underlying purpose of cloud native is:
1. Speed of change (I used to refer to this as agility but in general would like to avoid the term moving forwards)
2. Resilience (We should be able to change software quickly and not have it break due to internal or external factors)
3. Scale: We'd like to do really big stuff
If we know what problems we're solving it will be easier to talk about specific practices and tools in a coherent manner.
On Tue, Feb 14, 2017 at 10:24 AM Camille Fournier <skamille@...>
wrote:
Microservices are cloud native because they are a natural product of the ease of use for cloud. In a evolutionary way I would call them absolutely cloud
native, which doesn't mean one must use them to effectively use the cloud but they do effectively show how cloud changed the way developers thought about building systems.
On Feb 14, 2017 10:22 AM, "Alexis Richardson via cncf-toc" <cncf-toc@...>
wrote:
On Tue, Feb 14, 2017 at 10:20 AM Anthony Skipper <anthony@...>
wrote:
I'd argue that if you had good tools, you wouldn't need microservices.
Yes, I don't think microservices is a core value. It's one of several modern cloud native patterns that is useful for some organisational and technical
issues. But not the only one.
On Tue, Feb 14, 2017 at 1:15 PM, Mark Coleman via cncf-toc
<cncf-toc@...>
wrote:
I think I summarised it in this piece that I ghost wrote for Luke when he was at ClusterHQ (Friend D A please): https://www.infoq.com/articles/microservices-revolution
We have a cloud native triangle composed of:
1. Speed of change (I refer to this as agility in that doc but in general would like to avoid the term moving forwards)
2. Resilience (We should be able to change software quickly and not have it break due to internal or external factors)
3. Scale: We'd like to do really big stuff
From those core requirements we can rationalize containerization, microservices and continuous delivery.
From those 'practices' we can talk about specific tools.
Where we fall down is when we start from the tools, but obviously a large part of getting things right (especially microservices I would argue) require
pink matter.
On Tue, Feb 14, 2017 at 10:09 AM Alexis Richardson <alexis@...>
wrote:
yes
we need to develop a cloud native brand that has values which developers want
On Tue, Feb 14, 2017 at 10:07 AM Mark Coleman <mark@...>
wrote:
I like the model of bringing in end user stories to support the point being made.
The point here clearly seems to be "it's ok to move all your shit to the cloud snd figure it out there" which is an unsurprising position for AWS to take.
This is not an opposing point to our mission(TM) though so I will explore this.
Right now I'm mainly concerned that our definition of cloud native is not everyone else's.
On Thu, Feb 2, 2017 at 1:34 AM Alexis Richardson <alexis@...>
wrote:
I thought this was worth sharing as an example of the sort of tech-biz guidance that members of the CNCF community could write. The piece is by someone
from AWS and talks about cloud native vs other cloudy things.
_______________________________________________
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
_______________________________________________
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
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: Interesting tech marketing from Amazon
Kitson, Clinton <Clinton.Kitson@...>
I agree with some earlier comments about being too opinionated. A broad definition could be "a computing environment focused on optimizing for applications in cloud operating models". This feels like the most natural and direct way to define cloud native
computing while ensuring the relevance to how we are seeing people make use of it today and tomorrow.
The definition leads to a lot of what was discussed in this thread.
- Requirements (interoperability/composability, automation/orchestration)
- Patterns (micro-services, scale-out, DevOps, CI)
- Components (cncf landscape)
- Benefits/features (resilience, scale, efficiency, resilience, portability)
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
toggle quoted message
Show quoted text
From: cncf-toc-bounces@... [cncf-toc-bounces@...] on behalf of Brian Grant via cncf-toc [cncf-toc@...]
Sent: Friday, February 17, 2017 12:32 PM
To: Tony Hsu
Cc: Alexis Richardson via cncf-toc
Subject: Re: [cncf-toc] Interesting tech marketing from Amazon
+1
That's very concrete, and provides a framework for explaining what and why.
|
|
|
Re: Interesting tech marketing from Amazon
+1
That's very concrete, and provides a framework for explaining what and why.
|
|
|
Re: important updates re TOC meeting scheduling & agenda in future
+1 for Thursdays at the same time.
- Lee
On Feb 16, 2017, at 5:58 PM, Weaver, Nicholas via cncf-toc < cncf-toc@...> wrote:
Either works for me Nicholas Weaver Director - Software Engineering Intel, Datacenter Solutions Group On Feb 16, 2017 2:58 PM, "Brian Grant via cncf-toc" < cncf-toc@...> wrote: These times/days would work for me, thanks. On Thu, Feb 16, 2017 at 11:49 AM, Alexis Richardson via cncf-toc < cncf-toc@...> wrote: TOC members, We talked about moving the fortnightly TOC calls to another day. My own preference would be Thursday, with Tuesday as second choice. Please can we stick with the 8am PT / 11am ET / 4pm UK / 5pm DE slot. WDYT? We are past the bootstrap phase. The CNCF now has multiple projects, with more to come in 2017. Now we need to flesh out details of stuff like CI. And we need to make sure we are nurturing existing projects well. To that end - the TOC is keen to (a) have more 'working' meetings covering special topics, and (b) involve you more in pre-meeting agenda setting via public channels. Please be outspoken and demand participation.
_______________________________________________
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
|
|
|
Re: Interesting tech marketing from Amazon
Tony Hsu
As a big fan of Joe Beta and Craig McLuckie, my three ingredients for cloud-native operations are containers, orchestrators and microservice frameworks. These three terms come from Craig's post announcing the start of Heptio. https://goo.gl/aJgiQk
Our limbic brains are responsible for all of our feelings, like trust and loyalty. It's also responsible for all human behavior, all decision-making, and it has no capacity for language. Please don't rely on logic and facts, it just doesn't drive behavior.
Regards, Tony Hsu
On Fri, Feb 17, 2017 at 4:37 PM, Yaron Haviv via cncf-toc <cncf-toc@...> wrote:
I think the key message of Cloud-Native should be about its value:
Continuous Development and Operation (Enabling Business Agility/Transformation)
Decomposition to micro-services, stateless, disposable/distributed components, Atomicity .. are the ways by which we achieve that goal, and those may evolve over time. If we
want to engage more business owners lets focus on what’s in it for them and the need for a change vs tech buzzwords.
My 2c, Yaron
CTO, iguazio
On Tue, Feb 14, 2017 at 10:37 AM, Andrew Randall via cncf-toc <cncf-toc@...> wrote:
I think we should aim for 3 core principles. Any more than that and people won't be able to repeat as a mantra.
Currently the charter has:
- micro-services oriented.
I like Mark's comments. However, I worry about "massive scale" as a message. LOTS of people I talked with at CloudNativeCon and other shows recently have been doing fairly small scale deployments, but they're still cloud native. I think
the nature of how we scale is important -- it's about the distributed, scale-out architectures that enable massive scale (but don't impose a cost burden for the small development shop that's running on a half dozen VMs in AWS).
I think "Dynamically scalable" captures that better.
Management includes scaling, so IMO "dynamically managed" implies dynamic scaling, as well as a higher rate of change than people had been accustomed to in the past.
In practice, the way this is achieved is through automation.
The inclusion of container-packaged and micro-services in the charter is an opinionated (and informed) stance about where the puck is headed.
And you could add "built on open source foundation" as a fourth, or leave it implicit given the foundation nature of LF/CNCF.
On Tue, Feb 14, 2017 at 10:32 AM Mark Coleman via cncf-toc <cncf-toc@...> wrote:
I agree that we may need to think more about how we communicate about microservices, but do we agree that the underlying purpose of cloud native is:
1. Speed of change (I used to refer to this as agility but in general would like to avoid the term moving forwards)
2. Resilience (We should be able to change software quickly and not have it break due to internal or external factors)
3. Scale: We'd like to do really big stuff
If we know what problems we're solving it will be easier to talk about specific practices and tools in a coherent manner.
On Tue, Feb 14, 2017 at 10:24 AM Camille Fournier <skamille@...> wrote:
Microservices are cloud native because they are a natural product of the ease of use for cloud. In a evolutionary way I would call them absolutely cloud native, which doesn't mean one must use them to effectively use the cloud but they
do effectively show how cloud changed the way developers thought about building systems.
On Feb 14, 2017 10:22 AM, "Alexis Richardson via cncf-toc" <cncf-toc@...> wrote:
On Tue, Feb 14, 2017 at 10:20 AM Anthony Skipper <anthony@...> wrote:
I'd argue that if you had good tools, you wouldn't need microservices.
Yes, I don't think microservices is a core value. It's one of several modern cloud native patterns that is useful for some organisational and technical issues. But not the only one.
On Tue, Feb 14, 2017 at 1:15 PM, Mark Coleman via cncf-toc
<cncf-toc@...> wrote:
I think I summarised it in this piece that I ghost wrote for Luke when he was at ClusterHQ (Friend D A please): https://www.infoq.com/articles/microservices-revolution
We have a cloud native triangle composed of:
1. Speed of change (I refer to this as agility in that doc but in general would like to avoid the term moving forwards)
2. Resilience (We should be able to change software quickly and not have it break due to internal or external factors)
3. Scale: We'd like to do really big stuff
From those core requirements we can rationalize containerization, microservices and continuous delivery.
From those 'practices' we can talk about specific tools.
Where we fall down is when we start from the tools, but obviously a large part of getting things right (especially microservices I would argue) require pink matter.
On Tue, Feb 14, 2017 at 10:09 AM Alexis Richardson <alexis@...> wrote:
yes
we need to develop a cloud native brand that has values which developers want
On Tue, Feb 14, 2017 at 10:07 AM Mark Coleman <mark@...> wrote:
I like the model of bringing in end user stories to support the point being made.
The point here clearly seems to be "it's ok to move all your shit to the cloud snd figure it out there" which is an unsurprising position for AWS to take. This is not an opposing point to our mission(TM) though so I will explore this.
Right now I'm mainly concerned that our definition of cloud native is not everyone else's.
On Thu, Feb 2, 2017 at 1:34 AM Alexis Richardson <alexis@...> wrote:
I thought this was worth sharing as an example of the sort of tech-biz guidance that members of the CNCF community could write. The piece is by someone from AWS and talks about cloud native vs other cloudy things.
_______________________________________________
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
_______________________________________________
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
|
|
|
Re: Interesting tech marketing from Amazon
I think the key message of Cloud-Native should be about its value:
Continuous Development and Operation (Enabling Business Agility/Transformation)
Decomposition to micro-services, stateless, disposable/distributed components, Atomicity .. are the ways by which we achieve that goal, and those may evolve over time. If we
want to engage more business owners lets focus on what’s in it for them and the need for a change vs tech buzzwords.
My 2c, Yaron
CTO, iguazio
toggle quoted message
Show quoted text
From: cncf-toc-bounces@... [mailto:cncf-toc-bounces@...]
On Behalf Of Brian Grant via cncf-toc
Sent: Friday, February 17, 2017 6:05 AM
To: Andrew Randall <andy@...>
Cc: Alexis Richardson via cncf-toc <cncf-toc@...>
Subject: Re: [cncf-toc] Interesting tech marketing from Amazon
On Tue, Feb 14, 2017 at 10:37 AM, Andrew Randall via cncf-toc <cncf-toc@...> wrote:
I think we should aim for 3 core principles. Any more than that and people won't be able to repeat as a mantra.
Currently the charter has:
- micro-services oriented.
I like Mark's comments. However, I worry about "massive scale" as a message. LOTS of people I talked with at CloudNativeCon and other shows recently have been doing fairly small scale deployments, but they're still cloud native. I think
the nature of how we scale is important -- it's about the distributed, scale-out architectures that enable massive scale (but don't impose a cost burden for the small development shop that's running on a half dozen VMs in AWS).
I think "Dynamically scalable" captures that better.
Management includes scaling, so IMO "dynamically managed" implies dynamic scaling, as well as a higher rate of change than people had been accustomed to in the past.
In practice, the way this is achieved is through automation.
The inclusion of container-packaged and micro-services in the charter is an opinionated (and informed) stance about where the puck is headed.
And you could add "built on open source foundation" as a fourth, or leave it implicit given the foundation nature of LF/CNCF.
On Tue, Feb 14, 2017 at 10:32 AM Mark Coleman via cncf-toc <cncf-toc@...> wrote:
I agree that we may need to think more about how we communicate about microservices, but do we agree that the underlying purpose of cloud native is:
1. Speed of change (I used to refer to this as agility but in general would like to avoid the term moving forwards)
2. Resilience (We should be able to change software quickly and not have it break due to internal or external factors)
3. Scale: We'd like to do really big stuff
If we know what problems we're solving it will be easier to talk about specific practices and tools in a coherent manner.
On Tue, Feb 14, 2017 at 10:24 AM Camille Fournier <skamille@...> wrote:
Microservices are cloud native because they are a natural product of the ease of use for cloud. In a evolutionary way I would call them absolutely cloud native, which doesn't mean one must use them to effectively use the cloud but they
do effectively show how cloud changed the way developers thought about building systems.
On Feb 14, 2017 10:22 AM, "Alexis Richardson via cncf-toc" <cncf-toc@...> wrote:
On Tue, Feb 14, 2017 at 10:20 AM Anthony Skipper <anthony@...> wrote:
I'd argue that if you had good tools, you wouldn't need microservices.
Yes, I don't think microservices is a core value. It's one of several modern cloud native patterns that is useful for some organisational and technical issues. But not the only one.
On Tue, Feb 14, 2017 at 1:15 PM, Mark Coleman via cncf-toc
<cncf-toc@...> wrote:
I think I summarised it in this piece that I ghost wrote for Luke when he was at ClusterHQ (Friend D A please): https://www.infoq.com/articles/microservices-revolution
We have a cloud native triangle composed of:
1. Speed of change (I refer to this as agility in that doc but in general would like to avoid the term moving forwards)
2. Resilience (We should be able to change software quickly and not have it break due to internal or external factors)
3. Scale: We'd like to do really big stuff
From those core requirements we can rationalize containerization, microservices and continuous delivery.
From those 'practices' we can talk about specific tools.
Where we fall down is when we start from the tools, but obviously a large part of getting things right (especially microservices I would argue) require pink matter.
On Tue, Feb 14, 2017 at 10:09 AM Alexis Richardson <alexis@...> wrote:
yes
we need to develop a cloud native brand that has values which developers want
On Tue, Feb 14, 2017 at 10:07 AM Mark Coleman <mark@...> wrote:
I like the model of bringing in end user stories to support the point being made.
The point here clearly seems to be "it's ok to move all your shit to the cloud snd figure it out there" which is an unsurprising position for AWS to take. This is not an opposing point to our mission(TM) though so I will explore this.
Right now I'm mainly concerned that our definition of cloud native is not everyone else's.
On Thu, Feb 2, 2017 at 1:34 AM Alexis Richardson <alexis@...> wrote:
I thought this was worth sharing as an example of the sort of tech-biz guidance that members of the CNCF community could write. The piece is by someone from AWS and talks about cloud native vs other cloudy things.
_______________________________________________
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
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: Interesting tech marketing from Amazon
|
|
|
Re: [VOTE] gRPC project proposal
Tony Hsu
+1 (non-binding)
Regards, Tony Hsu
On Thu, Feb 16, 2017 at 9:48 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote: Hey CNCF TOC community, it's time to vote on the gRPC ( http://www.grpc.io/) proposal as an inception level project, you can view the proposal below in this email or on GitHub: https://github.com/cncf/toc/pull/23Please vote +1/0/-1
---
Name of project: gRPC Description: Google has been using a single general-purpose RPC infrastructure called Stubby to connect the large number of microservices running within and across our data centers for over a decade. Our internal systems have long embraced the microservice architecture gaining popularity today. Stubby has powered all of Google’s microservices interconnect for over a decade and is the RPC backbone behind every Google service that you use today. Having a uniform, cross-platform RPC infrastructure has allowed for the rollout of fleet-wide improvements in efficiency, security, reliability and behavioral analysis critical to supporting the incredible growth seen in that period. In March 2015, Google decided to build the next version of Stubby in the open to share their learnings with the industry and collaborate with them to build the next version of Stubby. gRPC is a modern open-source high-performance RPC framework that can run in any environment. It can efficiently connect services in multiple languages in and across data centers with pluggable support for service discovery, load balancing, monitoring, tracing, health checking and authentication. It is also applicable in last mile of distributed computing to connect devices, mobile applications and browsers to backend services. Sponsor / Advisor from TOC: Brian Grant < briangrant@...> Unique Identifier: grpc License: ALv2 ( https://groups.google.com/forum/#!msg/grpc-io/AWCJlR-MA9k/N-EKJtQPAwAJ) Maturity Level: Incubating Source control repositories: https://github.com/grpcInitial Committers: Abhishek Kumar Louis Ryan Craig Tiller Eric Anderson Jayant Kolhe Infrastructure requirements: CI and potentially CNCF Community Cluster access Issue tracker: Per-platform issues are raised on the per-platform repository’s issues area (i.e., https://github.com/grpc/grpc-java/issues and https://github.com/grpc/grpc-go/issues) Mailing lists Mailing List: https://groups.google.com/forum/#!forum/grpc-ioGitter: https://gitter.im/grpc/grpcWebsite: http://www.grpc.io/Release methodology and mechanics: Various across platforms Social media accounts: https://twitter.com/grpcioExisting sponsorship: Google Adopters: Cisco, CoreOS, Square, Netflix and more (see http://www.grpc.io/about/) Statement on alignment with CNCF mission: Microservices are a critical part of the cloud-native story. An open-source polyglot RPC framework like gRPC helps you define, build, and connect high-performance microservices. External Dependencies grpc (c/c++): https://github.com/grpc/grpcBoringSSL: https://boringssl.googlesource.com/boringsslZlib: http://www.zlib.net/zlib_license.htmlGflags: https://github.com/gflags/gflagsGoogle Benchmark: https://github.com/google/benchmarkGoogletest: https://github.com/google/googletestNanopb: https://github.com/nanopb/nanopbThrift (experimental thrift support): http://thrift.apache.org/Protobuf (for protobuf support): https://github.com/google/protobufgrpc-java: https://github.com/grpc/grpc-javaBuild: errorprone: "com.google.errorprone:error_ prone_annotations:2.0.11", jsr305: 'com.google.code.findbugs: jsr305:3.0.0', Compile: guava: "com.google.guava:guava:${ guavaVersion}", hpack: 'com.twitter:hpack:0.10.1', oauth_client: 'com.google.auth:google-auth- library-oauth2-http:0.4.0', google_auth_credentials: 'com.google.auth:google-auth- library-credentials:0.4.0', okhttp: 'com.squareup.okhttp:okhttp:2. 5.0', okio: 'com.squareup.okio:okio:1.6.0' , census_api: 'com.google.census:census-api: 0.2.0', protobuf: "com.google.protobuf:protobuf- java:${protobufVersion}", protobuf_lite: "com.google.protobuf:protobuf- lite:3.0.1", protoc_lite: "com.google.protobuf:protoc- gen-javalite:3.0.0", Protobuf_nano: "com.google.protobuf.nano: protobuf-javanano:${ protobufNanoVersion}", protobuf_plugin: 'com.google.protobuf:protobuf- gradle-plugin:0.8.0', protobuf_util: "com.google.protobuf:protobuf- java-util:${protobufVersion}", netty: 'io.netty:netty-codec-http2:[ 4.1.6.Final]', netty_epoll: 'io.netty:netty-transport- native-epoll:4.1.6.Final' + epoll_suffix, netty_tcnative: 'io.netty:netty-tcnative- boringssl-static:1.1.33. Fork23', Test dependencies: junit: 'junit:junit:4.11', mockito: 'org.mockito:mockito-core:1.9. 5', truth: 'com.google.truth:truth:0.28', Benchmark: hdrhistogram: 'org.hdrhistogram: HdrHistogram:2.1.8', math: 'org.apache.commons:commons- math3:3.6', Jetty ALPN dependencies: jetty_alpn_agent: 'org.mortbay.jetty.alpn:jetty- alpn-agent:2.0.3' grpc-go: https://github.com/grpc/grpc-gohttps://godoc.org/byteshttps://godoc.org/compress/gziphttps://godoc.org/encoding/binaryhttps://godoc.org/errorshttps://godoc.org/fmthttps://godoc.org/github.com/golang/protobuf/protohttps://godoc.org/golang.org/x/net/contexthttps://godoc.org/golang.org/x/net/http2https://godoc.org/golang.org/x/net/tracehttps://godoc.org/iohttps://godoc.org/io/ioutilhttps://godoc.org/mathhttps://godoc.org/math/randhttps://godoc.org/nethttps://godoc.org/net/httphttps://godoc.org/oshttps://godoc.org/reflecthttps://godoc.org/runtimehttps://godoc.org/stringshttps://godoc.org/synchttps://godoc.org/timeOther Contributors: grpc (c/c++): https://github.com/grpc/grpc/graphs/contributorsgrpc-java: https://github.com/grpc/grpc-java/graphs/contributorsgrpc-go: https://github.com/grpc/grpc-go/graphs/contributorsAll contributors: 77 total, 49 Google, 29 external contributors @a11r @adewale @adriancole @apolcyn @arteam @a-veitc @awpr @bogdandrutu @bradfitz @broady @buchgr @carl-mastrangelo @ctiller @danruehle @dapengzhang0 @dgquintas @dklempner @dsymonds @ejona86 @elandau @ericgribkoff @gxb5443 @gyuho @heyitsanthony @hongweiwang @iamqizhao @JakeWharton @jayantkolhe @jboeuf @jcanizales @jhspaybar @johnbcoughlin @jtattermusch @kpayson64 @LisaFC @louiscryan @lukaszx0 @madongfly @makdharma @MakMukhi @markdroth @matthild @matttproud @menghanl @mfcripps @mugurm @murgatroid99 @muxi @mwitkow @nathanielmanistaatgoogle @ncteisen @nicolasnoble @nmittler @nobutaka @nuss-justin @oaktowner @peter-edge @petermattis @philips @rjshade @Sajmani @skyao @soltanmm @soltanmm-google @sreecha @stanley-cheung @stevvooe @tamird @tbetbetbe @thagikura @thinkerou @vjpai @wonderfly @yang-g @yangzhouhan @y-zeng @zhangkun83 @zsurocking
--
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: important updates re TOC meeting scheduling & agenda in future
Weaver, Nicholas <nicholas.weaver@...>
Either works for me
Nicholas Weaver
Director - Software Engineering
Intel, Datacenter Solutions Group
From:
<cncf-toc-bounces@...> on behalf of Camille Fournier via cncf-toc <cncf-toc@...>
Reply-To: Camille Fournier <skamille@...>
Date: Thursday, February 16, 2017 at 3:05 PM
To: Brian Grant <briangrant@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] important updates re TOC meeting scheduling & agenda in future
toggle quoted message
Show quoted text
On Feb 16, 2017 2:58 PM, "Brian Grant via cncf-toc" < cncf-toc@...> wrote:
These times/days would work for me, thanks.
On Thu, Feb 16, 2017 at 11:49 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:
TOC members,
We talked about moving the fortnightly TOC calls to another day. My own preference would be Thursday, with Tuesday as second choice. Please can we stick with the 8am PT / 11am ET / 4pm UK / 5pm DE slot. WDYT?
We are past the bootstrap phase. The CNCF now has multiple projects, with more to come in 2017. Now we need to flesh out details of stuff like CI. And we need to make sure we are nurturing existing projects well.
To that end - the TOC is keen to (a) have more 'working' meetings covering special topics, and (b) involve you more in pre-meeting agenda setting via public channels. Please be outspoken and demand participation.
_______________________________________________
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
|
|
|
