|
Re: Reminder: GSoC 2017 Project Ideas + Mentor Signup
Chris Aniszczyk
There's no explicit requirement, but we definitely prefer mentors who contribute actively to a CNCF project and have the time to mentor a student over the summer. Thanks for pointing out the manual Eduardo.
On Fri, Feb 10, 2017 at 8:26 AM, Eduardo Silva via cncf-toc <cncf-toc@...> wrote:
--
|
|||||||||||
|
|
|||||||||||
|
Re: Reminder: GSoC 2017 Project Ideas + Mentor Signup
Eduardo Silva
FYI:
On Thu, Feb 9, 2017 at 10:06 PM, Srikar Ananthula via cncf-toc <cncf-toc@...> wrote:
--
|
|||||||||||
|
|
|||||||||||
|
Re: Reminder: GSoC 2017 Project Ideas + Mentor Signup
Srikar
Is there any defined criteria to be as GSOC-mentor ?
On Thu, Feb 9, 2017 at 11:18 PM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
--
|
|||||||||||
|
|
|||||||||||
|
Reminder: GSoC 2017 Project Ideas + Mentor Signup
Just a friendly reminder that we are officially applied for GSOC: https://developers.google.com/ The list for mentor + idea signup is here: https://docs.google.com/ If you're interested in following along and mentoring, please watch this GitHub repo: Thanks! Chris Aniszczyk (@cra) | +1-512-961-6719
|
|||||||||||
|
|
|||||||||||
|
Re: [VOTE] CoreDNS project proposal (inception)
alexis richardson
+1
On Fri, Feb 3, 2017 at 1:16 PM, Ram, J via cncf-toc <cncf-toc@...> wrote: +1
|
|||||||||||
|
|
|||||||||||
|
Re: [VOTE] CoreDNS project proposal (inception)
Kenneth Owens (kenowens) <kenowens@...>
+1
On 2 February 2017 at 22:52, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
|
|||||||||||
|
|
|||||||||||
|
Re: [VOTE] CoreDNS project proposal (inception)
Ram, J <j.ram@...>
+1
From: cncf-toc-bounces@... <cncf-toc-bounces@...> on behalf of Jonathan Boulle via cncf-toc <cncf-toc@...>
Sent: Friday, February 3, 2017 7:57:33 AM To: Chris Aniszczyk Cc: CNCF TOC Subject: Re: [cncf-toc] [VOTE] CoreDNS project proposal (inception) +1
On 2 February 2017 at 22:52, Chris Aniszczyk via cncf-toc
<cncf-toc@...> wrote:
|
|||||||||||
|
|
|||||||||||
|
Re: [VOTE] CoreDNS project proposal (inception)
Jonathan Boulle <jonathan.boulle@...>
+1
On 2 February 2017 at 22:52, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
|
|||||||||||
|
|
|||||||||||
|
Re: Storage Patterns for container native - community content
Zhipeng Huang
Hi Folks, This is an interesting topic and our team from the newly established OpenSDS community is now actively developing and have a primitive PoC working demo with kubernetes (picked up by Kubeweekly). We are also interested in participating in the seminar, please feel free to contact me if anything needed
On Thu, Feb 2, 2017 at 10:39 PM, NASSAUR, DOUGLAS C via cncf-toc <cncf-toc@...> wrote:
--
Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd Email: huangzhipeng@... Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipengh@... Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
|
|||||||||||
|
|
|||||||||||
|
[VOTE] CoreDNS project proposal (inception)
At yesterday's TOC meeting, the TOC decided to formally invite CoreDNS again but this time as an inception level CNCF project. Please vote on the project proposal located here: https://github.com/cncf/toc/pull/9 Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support. Thanks! Chris Aniszczyk (@cra) | +1-512-961-6719
|
|||||||||||
|
|
|||||||||||
|
Re: Storage Patterns for container native - community content
NASSAUR, DOUGLAS C <dn283x@...>
Let me know if interested in looping in some libStorage work we are doing. Also plan on having the architecture committee publish a series of "cloud native pattern reference implementations" is like to get lots of eyes on. Putting out a call for participation
on that effort first of next week.
Regards, Doug
On Feb 2, 2017, at 9:31 AM, Mark Coleman via cncf-toc <cncf-toc@...> wrote:
|
|||||||||||
|
|
|||||||||||
|
Re: Storage Patterns for container native - community content
Mark Coleman <mark@...>
Hey Alex, This looks great. I'm already in talks with Portworx to do a 'What is container storage and why should I care?' style webinar in March. I'd like to get StorageOS involved too. We previously did a Cloud Native Networking webinar with people from both Tigera and Weaveworks and it went well. Would you have time for a quick chat next Tuesday/Wednesday? Mark
On Wed, Feb 1, 2017 at 4:50 PM Alex Chircop via cncf-toc <cncf-toc@...> wrote:
--
|
|||||||||||
|
|
|||||||||||
|
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
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 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. -- 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?
toggle quoted messageShow quoted text
On Tue, Jan 31, 2017 at 9:43 PM, Lee Calcote <leecalcote@...> wrote:
Justin,
|
|||||||||||
|
|
|||||||||||
|
Re: Cloud Native Infrastructure book
Gianluca Arbezzano <gianarb92@...>
Hello all I am Gianluca (twitter.com/gianarb, github.com/gianarb). 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 --
|
|||||||||||
|
|
|||||||||||
|
Re: Cloud Native Infrastructure book
Lee Calcote
Justin,
toggle quoted messageShow quoted text
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:
|
|||||||||||
|
|
|||||||||||
|
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,
|
|||||||||||
|
|
|||||||||||
|
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.
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.
|
|||||||||||
|
|
|||||||||||
Think
before you print.