|
Re: RexRay follow up
Kitson, Clinton <clinton.kitson@...>
Correct Brian, REX-Ray should be transparent to end users in this space and provides an important service by helping connect apps to storage. Operators of clusters are the ones that should be very aware of it as it would provide trusted and more quality
plugins that are built on top of the existing CSI spec.
REX-Ray stats: Recently REX-Ray went through some refactoring to accommodate the CSI architecture changes that needed to take place. This meant rolling in the libStorage functionality which unfortunately skews the numbers a bit. The {code} team has been
primary maintainers on the framework where collaborators have mainly focused on building drivers. Other storage companies who understand the complexity involved in building a solid CSI implementation see the value and commonality that can be addressed by REX-Ray
and are interested in collaborating if supported via a foundation.
Production users: Yes, REX-Ray is being used in production by some of the users listed in the slides. Up to this point, usage levels have been tied closely to production deployment of Mesos & Docker.
Sandbox: I believe the numbers and history justify incubation, but we can discuss it.
Control plane: REX-Ray used to have its own control plane (libStorage API) prior to CSI. In most recent we have made architectural changes to be adhere to CSI. When libStorage was its control-plane, there was integration work performed to make libStorage
a volume plugin and additionally to Cloud Foundry. Today, anyone who implements CSI on the cluster orchestrator side can talk with any REX-Ray plugin.
Data plane: REX-Ray is not involved in the data-plane of storage operations. It is an orchestrator and simply gets two components (local/remote storage & an OS) connected. It essentially performs the exact same steps that someone would manually perform
to get these two components communicating and the reverse on tear down.
Persistent state: It is completely stateless today.
Clint Kitson
Technical Director for {code}
CNCF Governing Board Member
---
email: Clinton.Kitson@...
mobile: "+1 424 645 4116"
team: theCodeTeam.com
twitter: "@clintkitson"
github: github.com/clintkitson
|
|
|
|
Re: [VOTE] CoreDNS moving to incubation
Quinton Hoole
+1 (non-binding).
From: <cncf-toc@...> on behalf of Justin Garrison <justinleegarrison@...>
Date: Tuesday, February 20, 2018 at 09:26 To: "cncf-toc@..." <cncf-toc@...> Subject: Re: [cncf-toc] [VOTE] CoreDNS moving to incubation
|
|
|
|
Election Schedule for 2 TOC-selected Seats
On today's TOC call, we discussed that we have two TOC-selected seats opening up for the TOC (https://github.com/cncf/toc/ 2/20/2018: Nominations open up today (nominations by TOC members only) 3/6/2018: Nominations close EOD PT 3/7/2018: Voting begins 3/14/2018: Voting ends EOD PT 3/15/2018: Announce results They key word here is TOC-selected (the charter empowers the TOC to select two members on their own) so an existing TOC member needs to nominate you. Please reach out to a TOC member (https://github.com/cncf/toc#members) and have them nominate you by shooting me a note. Thanks! Chris Aniszczyk (@cra) | +1-512-961-6719 |
|
|
|
Re: [VOTE] CoreDNS moving to incubation
Justin Garrison <justinleegarrison@...>
+1 non-binding On Tue, Feb 20, 2018 at 9:16 AM, Mark Interrante <minterrante@...> wrote:
|
|
|
|
Re: [VOTE] CoreDNS moving to incubation
minterrante@...
+1 non-binding On Tue, Feb 20, 2018 at 9:08 AM, Ihor Dvoretskyi <ihor.dvoretskyi@...> wrote:
--
Mark Interrante SVP Infrastructure Engineering | Salesforce  -- - |
|
|
|
RexRay follow up
Brian Grant
Thanks to Clinton for presenting. A response to Alexis's question/point about end-user benefit: I would expect it to be similar to the end-user benefit of CNI: more high-quality infrastructure options available in cloud-native environments. Not all of our projects will be used directly by users. Some may be used by other projects as components, libraries, frameworks, APIs, and so on. Some questions about RexRay:
|
|
|
|
Re: [VOTE] CoreDNS moving to incubation
Ihor Dvoretskyi
+1 non-binding On Tue, Feb 20, 2018 at 8:57 AM, Chris Aniszczyk <caniszczyk@...> wrote:
|
|
|
|
Re: [VOTE] CoreDNS moving to incubation
Christopher LILJENSTOLPE <cdl@...>
+1, non-binding On Tue, Feb 20, 2018 at 8:57 AM, Chris Aniszczyk <caniszczyk@...> wrote:
|
|
|
|
Final RFC: CNCF Sandbox
At today's TOC call there was consensus on the CNCF Sandbox proposal is close to being ready for a formal vote. We will leave the document open for any community comments for a week and do a formal vote next week: https://goo.gl/gZhBjY After the vote and assuming the sandbox is approved, we will resume voting on new project proposals (existing inception proposals will be slotted for the sandbox). Thanks. Chris Aniszczyk (@cra) | +1-512-961-6719 |
|
|
|
Re: [VOTE] CoreDNS moving to incubation
Doug Davis <dug@...>
+1 non-binding At today's TOC call, we had the CoreDNS team perform their annual inception project review and request to move to the incubation level. You can see the project statistics here: https://coredns.devstats.cncf.io and they meet the incubation criteria requirements: - Used successfully in production by at least three independent end users of sufficient scale and quality: seven listed in the ADOPTERS file, others may be discussed privately - Have a healthy number of committers: six maintainers from four different companies (Google, Infoblox, Apprenda, Independent). 71 contributors in the main repository - Demonstrate a substantial ongoing flow of commits and merged contributions: 12+ releases since joining CNCF, 489+ commits/merged PRs on the main repository since joining CNCF (81+ of those PRs are from authors other than Miek and Infoblox) Please vote (+1/0/-1) by replying to this thread; the full incubation proposal located here: https://github.com/cncf/toc/pull/66 Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support! -- Chris Aniszczyk (@cra) | +1-512-961-6719 |
|
|
|
Re: [VOTE] CoreDNS moving to incubation
alexis richardson
+1 binding
toggle quoted message
Show quoted text
On Tue, Feb 20, 2018 at 5:02 PM, John Belamaric <jbelamaric@...> wrote:
+1 non-binding |
|
|
|
Re: [VOTE] CoreDNS moving to incubation
+1 non-binding
toggle quoted message
Show quoted text
|
|
|
|
Re: [VOTE] CoreDNS moving to incubation
Eduardo Silva
+1 non-binding On Tue, Feb 20, 2018 at 10:58 AM, Lee Calcote <leecalcote@...> wrote:
--
|
|
|
|
Re: [VOTE] CoreDNS moving to incubation
Richard Hartmann
+1 non-binding Sent by mobile; please excuse my brevity. On Feb 20, 2018 17:57, "Chris Aniszczyk" <caniszczyk@...> wrote:
|
|
|
|
Re: [VOTE] CoreDNS moving to incubation
Lee Calcote
+1 non-binding
toggle quoted message
Show quoted text
|
|
|
|
[VOTE] CoreDNS moving to incubation
At today's TOC call, we had the CoreDNS team perform their annual inception project review and request to move to the incubation level. You can see the project statistics here: https://coredns.devstats.cncf.io and they meet the incubation criteria requirements: - Used successfully in production by at least three independent end users of sufficient scale and quality: seven listed in the ADOPTERS file, others may be discussed privately - Have a healthy number of committers: six maintainers from four different companies (Google, Infoblox, Apprenda, Independent). 71 contributors in the main repository - Demonstrate a substantial ongoing flow of commits and merged contributions: 12+ releases since joining CNCF, 489+ commits/merged PRs on the main repository since joining CNCF (81+ of those PRs are from authors other than Miek and Infoblox) Please vote (+1/0/-1) by replying to this thread; the full incubation proposal located here: https://github.com/cncf/toc/pull/66 Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support! Chris Aniszczyk (@cra) | +1-512-961-6719 |
|
|
|
TOC Agenda 2/20/2018
Here's the agenda deck for the TOC meeting tomorrow: https://goo.gl/Z5ytqu The agenda is primarily focused on finalizing the CNCF Sandbox proposal. We will also hear updates from the CNCF Serverless WG, Reference Arch v2.0 call to action and if there's time, a presentation from the rexray team. See everyone tomorrow! Chris Aniszczyk (@cra) | +1-512-961-6719 |
|
|
|
Re: [VOTE] [PAUSE] INCEPTION
Stephen Watt
+1. I think the term "sandbox" is great. On Thu, Feb 8, 2018 at 6:47 AM, Doug Davis <dug@...> wrote:
|
|
|
|
data on OCI contributors
Rob Lalonde
Hey Chris.
You can ignore my Slack message. Have you seen any contributor stackalytics for the OCI project or do you have anything similar? I see data for K8s and Helm. Thanks! Rob |
|
|
|
Re: [VOTE] [PAUSE] INCEPTION
Doug Davis <dug@...>
As a dog owner (see my sig), I love it! As a dog owner, I object to that. On Thu, Feb 8, 2018 at 12:43 PM, Doug Davis <dug@...> wrote:
thanks -Doug _______________________________________________________ STSM | IBM Open Source, Cloud Architecture & Technology (919) 254-6905 | IBM 444-6905 | dug@... The more I'm around some people, the more I like my dog  "Bryan Cantrill" ---02/08/2018 05:24:38 AM---I'm sorry to have missed the call this week, but I think the term "Sandbox" is great -- in additionFrom: "Bryan Cantrill" <bryan@...> To: cncf-toc@... Cc: CNCF TOC <cncf-toc@...> Date: 02/08/2018 05:24 AM Subject: Re: [cncf-toc] [VOTE] [PAUSE] INCEPTION Sent by: cncf-toc@... I'm sorry to have missed the call this week, but I think the term "Sandbox" is great -- in addition to its positive connotations of fun and play, it's also dirty and filled with sniffling toddlers, broken plastic toys, and the occasional cat poop. Much, much better than "inception"! - Bryan On Thu, Feb 8, 2018 at 6:48 PM, alexis richardson <alexis@...> wrote:
In this week's TOC we converged on some possible changes to the Inception tier, that can address issues that have been raised about market perception & confusion. It is most likely that Inception will be replaced with a "Sandbox" tier. Chris Aniszczyk is drafting a written statement proposing Sandbox and associated changes and clarifications. This will include much of the discussion from the Zoom Chat on this week's TOC call. This draft is under active editing now: https://docs.google.com/document/d/1MkuVT7Q6itn9ESW-iyqIXsEqTPBrStXlvzESg94933A/edit Until the TOC has reviewed the Sandbox proposal we shall suspend voting on Inception projects. I apologise for any delays that are caused by this. For the avoidance of further confusion, Sandbox will be presented *as soon as possible* which I hope means at the next TOC call. alexis On Wed, Feb 7, 2018 at 10:55 PM, Yang Guan via Lists.Cncf.Io
<yangguan=google.com@...> wrote: > +1 (non-binding) > |
|
|
"Chris Aniszczyk" ---02/20/2018 08:57:36 AM---At today's TOC call, we had the CoreDNS team perform their annual inception project review and reque
"alexis richardson" ---02/08/2018 07:44:37 AM---As a dog owner, I object to that. On Thu, Feb 8, 2018 at 12:43 PM, Doug Davis <