Date   

Interesting tech marketing from Amazon

alexis richardson
 

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.



Storage Patterns for container native - community content

Alex Chircop
 

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 CI Goals

Dan Kohn <dan@...>
 

CNCF is gearing up to make a significant set of investments into Continuous Integration (CI) in 2017. I wanted to lay out some of our goals as well as what we are not trying to achieve. Feedback and updates on these are welcome. In general, we're looking for discussions to occur on cncf-ci-public@... so please join that list if you are interested in the subject.

Non-goals

All CNCF projects already make extensive use of CI. We are not aiming to replace their existing CI, or require them to use our platform, or force them to follow specific standards or processes. CI is a fast-moving ecosystem and project maintainers are in the best position to adjust intra-project CI based on their own requirements.

We don’t want to build our own testing framework or harness. There are tons of perfectly adequate ones. We want to integrate existing tools to provide useful results to our projects and our community, not develop a new testing project from scratch.

Goals

We want any testing work we fund to integrate continuously. Ideally, that means running on every commit via web hook. If technology or economic reasons dictate, it could instead run daily or other periodic basis. No manual setup should be needed.

We need any work we fund to be open source. It’s acceptable for it too be built on top of closed source platforms like CircleCI, TravisCI, AWS, etc., but if CNCF funding is paying for code to be written, we need that code to be open source. That allows it to be reviewed, improved, iterated on, etc. by others, especially by developers from individual projects.

All test frameworks eventually have problems of false positives, false negatives, and flapping (i.e., intermittent failures). We want to use best practices to document and minimize these.

The GitHub Status API is a de facto standard for third-party CI services to integrate with GitHub and other services. Any work we fund should (eventually) implement the GitHub Status API, and be integrated into relevant projects as long as false positives are at a sufficiently low level.

CNCF is helping develop a cloud native software stack that enables cross-cloud deployments. Cross-project CI that ensures ongoing interoperability is especially valuable. We’re also interested in a dashboard that shows the cross-project interoperability status of both the latest released version and HEAD of each CNCF project. We would also like to ensure that CNCF projects are able to deploy successfully on to most (and ideally all) public clouds as well as bare metal private clouds and common infrastructure like OpenStack and VMWare.
--
Dan Kohn <mailto:dan@...>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000


Re: Cloud Native Infrastructure book

alexis richardson
 

fantastic - how can we help?

On Tue, Jan 31, 2017 at 9:43 PM, Lee Calcote <leecalcote@...> wrote:
Justin,

I’ve been in discussion with Brian over the past month in wrapping up a title (on container orchestration) and moving on to co-authoring here. We’d yet to reach out… until now. :)

- Lee

On Jan 31, 2017, at 3:23 PM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

Hi all

I have encouraged Justin to post here because I think this is worthy
of promotion within the group & community. "PTAL" as they say!

a


On Tue, Jan 31, 2017 at 9:19 PM, Justin Garrison via cncf-toc
<cncf-toc@...> wrote:
Hello,

I'm working on a book with O'Reilly on Cloud Native Infrastructure. The book
is focusing on general practices and ideas for how you should set up your
infrastructure to manage cloud native applications. It will show examples
with CNCF projects but I hope to not go too in depth (1-2 chapters per
project) so I can still reference other books/resources if readers want to
dig deeper into a project. The book isn't targeting a single cloud and I
hope to keep the design principles as generic as possible so readers can
replicate the ideas in any cloud including on-premises.

The reason I'm emailing the list is I'm going to need some help (this is my
first book). Thank you everyone who has already reached out to me and
offered assistance. I'll reply as soon as I'm able to. Right now I'm looking
for the following resources.

Co-author: I believe, and Brian from O'Reilly agrees, having a co-author
could help the process for areas I'm not strong in, getting more immediate
feedback, and obviously sharing the load of writing a book. The book is
going to be a 6-8 month commitment. If anyone is interested or has
suggestions for someone they'd recommend please have them email me.
Reference resources: white papers, case studies, and other books on
infrastructure design. I've already read a lot of books/papers on the
subject but I'm sure there's some I've missed. The Linux Foundation is also
working on making their case studies available for the book. Let me know if
you have any favorites so I can make sure I reference them.
Example applications for each project focus. I don't plan to build one giant
application throughout the book but rather focus on one small application
per chapter and explain why a certain project/idea is beneficial to have. An
example would be something that sends a lot of logs and show examples of why
fluentd implements log collection in a cloud native way vs relying on
syslog.

I have already submitted the book proposal and am moving forward with the
project but haven't actively started writing. I'm still gathering/organizing
thoughts and information. If anyone has resources they'd be able to share
please send them.

Thank you for any help you can provide and I'm sure I'll be asking the
community for more reviews and feedback in the coming months.

--
Justin Garrison
justingarrison.com

_______________________________________________
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: Cloud Native Infrastructure book

Gianluca Arbezzano <gianarb92@...>
 

Hello all

I started to write something under a title "Docker in production" but my first idea was to produce something about how to manage modern and scalable distributed systems. After few months I realized that I can not do that alone and I decided to release some chapters (that was already written) as whitepapers.

I am still looking around to have the opportunity to write something about these topics, I am ready to write a book alone but I am open to taking part with some chapters. 
This seems a good opportunity. Just ping me if you like.

Gianluca

2017-01-31 21:23 GMT+00:00 Alexis Richardson via cncf-toc <cncf-toc@...>:

Hi all

I have encouraged Justin to post here because I think this is worthy
of promotion within the group & community.  "PTAL" as they say!

a


On Tue, Jan 31, 2017 at 9:19 PM, Justin Garrison via cncf-toc
<cncf-toc@...> wrote:
> Hello,
>
> I'm working on a book with O'Reilly on Cloud Native Infrastructure. The book
> is focusing on general practices and ideas for how you should set up your
> infrastructure to manage cloud native applications. It will show examples
> with CNCF projects but I hope to not go too in depth (1-2 chapters per
> project) so I can still reference other books/resources if readers want to
> dig deeper into a project. The book isn't targeting a single cloud and I
> hope to keep the design principles as generic as possible so readers can
> replicate the ideas in any cloud including on-premises.
>
> The reason I'm emailing the list is I'm going to need some help (this is my
> first book). Thank you everyone who has already reached out to me and
> offered assistance. I'll reply as soon as I'm able to. Right now I'm looking
> for the following resources.
>
> Co-author: I believe, and Brian from O'Reilly agrees, having a co-author
> could help the process for areas I'm not strong in, getting more immediate
> feedback, and obviously sharing the load of writing a book. The book is
> going to be a 6-8 month commitment. If anyone is interested or has
> suggestions for someone they'd recommend please have them email me.
> Reference resources: white papers, case studies, and other books on
> infrastructure design. I've already read a lot of books/papers on the
> subject but I'm sure there's some I've missed. The Linux Foundation is also
> working on making their case studies available for the book. Let me know if
> you have any favorites so I can make sure I reference them.
> Example applications for each project focus. I don't plan to build one giant
> application throughout the book but rather focus on one small application
> per chapter and explain why a certain project/idea is beneficial to have. An
> example would be something that sends a lot of logs and show examples of why
> fluentd implements log collection in a cloud native way vs relying on
> syslog.
>
> I have already submitted the book proposal and am moving forward with the
> project but haven't actively started writing. I'm still gathering/organizing
> thoughts and information. If anyone has resources they'd be able to share
> please send them.
>
> Thank you for any help you can provide and I'm sure I'll be asking the
> community for more reviews and feedback in the coming months.
>
> --
> Justin Garrison
> justingarrison.com
>
> _______________________________________________
> 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



--
Gianluca Arbezzano
www.gianarb.it


Re: Cloud Native Infrastructure book

Lee Calcote
 

Justin,

I’ve been in discussion with Brian over the past month in wrapping up a title (on container orchestration) and moving on to co-authoring here. We’d yet to reach out… until now. :)

- Lee

On Jan 31, 2017, at 3:23 PM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

Hi all

I have encouraged Justin to post here because I think this is worthy
of promotion within the group & community. "PTAL" as they say!

a


On Tue, Jan 31, 2017 at 9:19 PM, Justin Garrison via cncf-toc
<cncf-toc@...> wrote:
Hello,

I'm working on a book with O'Reilly on Cloud Native Infrastructure. The book
is focusing on general practices and ideas for how you should set up your
infrastructure to manage cloud native applications. It will show examples
with CNCF projects but I hope to not go too in depth (1-2 chapters per
project) so I can still reference other books/resources if readers want to
dig deeper into a project. The book isn't targeting a single cloud and I
hope to keep the design principles as generic as possible so readers can
replicate the ideas in any cloud including on-premises.

The reason I'm emailing the list is I'm going to need some help (this is my
first book). Thank you everyone who has already reached out to me and
offered assistance. I'll reply as soon as I'm able to. Right now I'm looking
for the following resources.

Co-author: I believe, and Brian from O'Reilly agrees, having a co-author
could help the process for areas I'm not strong in, getting more immediate
feedback, and obviously sharing the load of writing a book. The book is
going to be a 6-8 month commitment. If anyone is interested or has
suggestions for someone they'd recommend please have them email me.
Reference resources: white papers, case studies, and other books on
infrastructure design. I've already read a lot of books/papers on the
subject but I'm sure there's some I've missed. The Linux Foundation is also
working on making their case studies available for the book. Let me know if
you have any favorites so I can make sure I reference them.
Example applications for each project focus. I don't plan to build one giant
application throughout the book but rather focus on one small application
per chapter and explain why a certain project/idea is beneficial to have. An
example would be something that sends a lot of logs and show examples of why
fluentd implements log collection in a cloud native way vs relying on
syslog.

I have already submitted the book proposal and am moving forward with the
project but haven't actively started writing. I'm still gathering/organizing
thoughts and information. If anyone has resources they'd be able to share
please send them.

Thank you for any help you can provide and I'm sure I'll be asking the
community for more reviews and feedback in the coming months.

--
Justin Garrison
justingarrison.com

_______________________________________________
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: Cloud Native Infrastructure book

alexis richardson
 

Hi all

I have encouraged Justin to post here because I think this is worthy
of promotion within the group & community. "PTAL" as they say!

a


On Tue, Jan 31, 2017 at 9:19 PM, Justin Garrison via cncf-toc
<cncf-toc@...> wrote:
Hello,

I'm working on a book with O'Reilly on Cloud Native Infrastructure. The book
is focusing on general practices and ideas for how you should set up your
infrastructure to manage cloud native applications. It will show examples
with CNCF projects but I hope to not go too in depth (1-2 chapters per
project) so I can still reference other books/resources if readers want to
dig deeper into a project. The book isn't targeting a single cloud and I
hope to keep the design principles as generic as possible so readers can
replicate the ideas in any cloud including on-premises.

The reason I'm emailing the list is I'm going to need some help (this is my
first book). Thank you everyone who has already reached out to me and
offered assistance. I'll reply as soon as I'm able to. Right now I'm looking
for the following resources.

Co-author: I believe, and Brian from O'Reilly agrees, having a co-author
could help the process for areas I'm not strong in, getting more immediate
feedback, and obviously sharing the load of writing a book. The book is
going to be a 6-8 month commitment. If anyone is interested or has
suggestions for someone they'd recommend please have them email me.
Reference resources: white papers, case studies, and other books on
infrastructure design. I've already read a lot of books/papers on the
subject but I'm sure there's some I've missed. The Linux Foundation is also
working on making their case studies available for the book. Let me know if
you have any favorites so I can make sure I reference them.
Example applications for each project focus. I don't plan to build one giant
application throughout the book but rather focus on one small application
per chapter and explain why a certain project/idea is beneficial to have. An
example would be something that sends a lot of logs and show examples of why
fluentd implements log collection in a cloud native way vs relying on
syslog.

I have already submitted the book proposal and am moving forward with the
project but haven't actively started writing. I'm still gathering/organizing
thoughts and information. If anyone has resources they'd be able to share
please send them.

Thank you for any help you can provide and I'm sure I'll be asking the
community for more reviews and feedback in the coming months.

--
Justin Garrison
justingarrison.com

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


Cloud Native Infrastructure book

Justin Garrison <justinleegarrison@...>
 

Hello,

I'm working on a book with O'Reilly on Cloud Native Infrastructure. The book is focusing on general practices and ideas for how you should set up your infrastructure to manage cloud native applications. It will show examples with CNCF projects but I hope to not go too in depth (1-2 chapters per project) so I can still reference other books/resources if readers want to dig deeper into a project. The book isn't targeting a single cloud and I hope to keep the design principles as generic as possible so readers can replicate the ideas in any cloud including on-premises.

The reason I'm emailing the list is I'm going to need some help (this is my first book). Thank you everyone who has already reached out to me and offered assistance. I'll reply as soon as I'm able to. Right now I'm looking for the following resources.
  • Co-author: I believe, and Brian from O'Reilly agrees, having a co-author could help the process for areas I'm not strong in, getting more immediate feedback, and obviously sharing the load of writing a book. The book is going to be a 6-8 month commitment. If anyone is interested or has suggestions for someone they'd recommend please have them email me.
  • Reference resources: white papers, case studies, and other books on infrastructure design. I've already read a lot of books/papers on the subject but I'm sure there's some I've missed. The Linux Foundation is also working on making their case studies available for the book. Let me know if you have any favorites so I can make sure I reference them.
  • Example applications for each project focus. I don't plan to build one giant application throughout the book but rather focus on one small application per chapter and explain why a certain project/idea is beneficial to have. An example would be something that sends a lot of logs and show examples of why fluentd implements log collection in a cloud native way vs relying on syslog.
I have already submitted the book proposal and am moving forward with the project but haven't actively started writing. I'm still gathering/organizing thoughts and information. If anyone has resources they'd be able to share please send them.

Thank you for any help you can provide and I'm sure I'll be asking the community for more reviews and feedback in the coming months.

--
Justin Garrison
justingarrison.com


FYI: CNCF Applying to GSOC 2017; Call For Project Ideas + Mentors

Chris Aniszczyk
 

CNCF is applying as a mentoring organization to Google Summer of Code this year:
https://developers.google.com/open-source/gsoc/

If you're interesting in mentoring and/or have a project idea to contribute, please list it here:

So far we have ideas from k8s, fluentd and opentracing, with other CNCF projects in the process of collecting project ideas + mentors.

Thanks!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


DRAFT TOC slides for Feb 2017 meeting tomorrow

alexis richardson
 

comments welcome - some good stuff tomorrow, and this is last call before tahoe


https://docs.google.com/presentation/d/13hNfPU8zGwKv9X5VnbG6mxD_xf10kAVNhOXqmJFcwkk/edit#slide=id.gd5ae4e962_2_136


FYI: CloudNativeCon/KubeCon EU schedule is live!

Chris Aniszczyk
 


Re: [RESULT] linkerd project proposal

alexis richardson
 

My pleasure


On Mon, 23 Jan 2017, 17:53 William Morgan, <william@...> wrote:
Thank you! And thank you very much for your support and help along the way. 

-William

On Mon, Jan 23, 2017 at 8:21 AM, Alexis Richardson <alexis@...> wrote:
Congratulations!

On Mon, 23 Jan 2017, 16:18 Chris Aniszczyk via cncf-toc, <cncf-toc@...> wrote:
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc


Re: [RESULT] linkerd project proposal

William Morgan
 

Thank you! And thank you very much for your support and help along the way. 

-William

On Mon, Jan 23, 2017 at 8:21 AM, Alexis Richardson <alexis@...> wrote:
Congratulations!

On Mon, 23 Jan 2017, 16:18 Chris Aniszczyk via cncf-toc, <cncf-toc@...> wrote:
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc


Re: [RESULT] linkerd project proposal

alexis richardson
 

Chris we should add that topic to the f2f


On Mon, 23 Jan 2017, 16:32 Chris Aniszczyk, <caniszczyk@...> wrote:
All CNCF projects are currently incubating or inception, none have graduated at the moment.

It's something we are working on later this year as the graduation criteria was recently accepted:

Thanks!

On Mon, Jan 23, 2017 at 8:30 AM, Lee Calcote <leecalcote@...> wrote:
Exciting! Are any other projects currently in inception or have all others graduated?

On Jan 23, 2017, at 10:21 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

Congratulations!

On Mon, 23 Jan 2017, 16:18 Chris Aniszczyk via cncf-toc, <cncf-toc@...> wrote:
_______________________________________________
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




--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: [RESULT] linkerd project proposal

Chris Aniszczyk
 

All CNCF projects are currently incubating or inception, none have graduated at the moment.

It's something we are working on later this year as the graduation criteria was recently accepted:

Thanks!

On Mon, Jan 23, 2017 at 8:30 AM, Lee Calcote <leecalcote@...> wrote:
Exciting! Are any other projects currently in inception or have all others graduated?

On Jan 23, 2017, at 10:21 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

Congratulations!

On Mon, 23 Jan 2017, 16:18 Chris Aniszczyk via cncf-toc, <cncf-toc@...> wrote:
_______________________________________________
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




--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: [RESULT] linkerd project proposal

Lee Calcote
 

Exciting! Are any other projects currently in inception or have all others graduated?

On Jan 23, 2017, at 10:21 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

Congratulations!

On Mon, 23 Jan 2017, 16:18 Chris Aniszczyk via cncf-toc, <cncf-toc@...> wrote:
_______________________________________________
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: [RESULT] linkerd project proposal

Gabe Monroy <gabe@...>
 

Congrats, well deserved!

On Jan 23, 2017, at 9:21 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

Congratulations!

On Mon, 23 Jan 2017, 16:18 Chris Aniszczyk via cncf-toc, <cncf-toc@...> wrote:
_______________________________________________
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: [RESULT] linkerd project proposal

alexis richardson
 

Congratulations!

On Mon, 23 Jan 2017, 16:18 Chris Aniszczyk via cncf-toc, <cncf-toc@...> wrote:
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc


[RESULT] linkerd project proposal

Chris Aniszczyk
 


Re: [cncf-gb] New GB chair

Todd Moore
 

Thank you Alexis, and others for your confidence.



Todd M. Moore

Vice President IBM Open Technology

11501 Burnet Rd. MS 9035H014
Austin, TX , 78758. (512) 286-7643 (tie-line 363)
tmmoore@...

Alexis Richardson via cncf-gb ---01/20/2017 03:35:46 PM---+toc Congratulations Todd!

From: Alexis Richardson via cncf-gb <cncf-gb@...>
To: Dan Kohn <dan@...>, Alexis Richardson via cncf-toc <cncf-toc@...>
Cc: cncf-gb@...
Date: 01/20/2017 03:35 PM
Subject: Re: [cncf-gb] New GB chair
Sent by: cncf-gb-bounces@...





+toc

Congratulations Todd!



On Fri, Jan 20, 2017 at 8:05 PM, Dan Kohn via cncf-gb
<cncf-gb@...> wrote:
> I'd like to congratulate our governing board chairperson, Todd Moore of IBM,
> and also thank Peixin Hou of Huawei for participating, and (almost) all of
> you for voting.
>
> I'm sure Todd (cc'ed) would be happy to hear from you (as would I),
> particularly if there are specific agenda items you'd like to see on the
> agenda for our Tahoe board meeting on 2/15.
>
> Also, if you haven't booked your hotel room there, please do so ASAP, as
> they're almost sold out.
> http://events.linuxfoundation.org/events/open-source-leadership-summit/attend/hotel-and-travel
> --
> Dan Kohn <
mailto:dan@...>
> Executive Director, Cloud Native Computing Foundation <
https://cncf.io/>
> tel:+1-415-233-1000
>
> _______________________________________________
> cncf-gb mailing list
> cncf-gb@...
>
https://lists.cncf.io/mailman/listinfo/cncf-gb
>
_______________________________________________
cncf-gb mailing list
cncf-gb@...
https://lists.cncf.io/mailman/listinfo/cncf-gb