Date   

Re: Agenda for 5/7/2019 TOC meeting

Chris Aniszczyk
 

done

On Mon, May 6, 2019 at 1:54 PM Quinton Hoole <quinton.hoole@...> wrote:

Hi Chris

Please add the CNCF Storage SIG charter.

https://github.com/cncf/toc/pull/234

Thanks

Q
________________________________________
From: cncf-toc@... [cncf-toc@...] on behalf of Chris Aniszczyk [caniszczyk@...]
Sent: Monday, May 06, 2019 8:31 AM
To: CNCF TOC
Subject: [cncf-toc] Agenda for 5/7/2019 TOC meeting

Here's the agenda for tomorrow's meeting:

https://docs.google.com/presentation/d/1HOIedutomq3VCvdxdLHn1YdMj3CRTGnCX1DnsUhlCWo/edit#slide=id.g25ca91f87f_0_0
https://docs.google.com/document/d/1jpoKT12jf2jTf-2EJSAl4iTdA7Aoj_uiI19qIaECNFc/edit#heading=h.en8cy6hno0c6

See everyone tomorrow!

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


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


Re: Agenda for 5/7/2019 TOC meeting

Quinton Hoole
 

Hi Chris

Please add the CNCF Storage SIG charter.

https://github.com/cncf/toc/pull/234

Thanks

Q
________________________________________
From: cncf-toc@... [cncf-toc@...] on behalf of Chris Aniszczyk [caniszczyk@...]
Sent: Monday, May 06, 2019 8:31 AM
To: CNCF TOC
Subject: [cncf-toc] Agenda for 5/7/2019 TOC meeting

Here's the agenda for tomorrow's meeting:

https://docs.google.com/presentation/d/1HOIedutomq3VCvdxdLHn1YdMj3CRTGnCX1DnsUhlCWo/edit#slide=id.g25ca91f87f_0_0
https://docs.google.com/document/d/1jpoKT12jf2jTf-2EJSAl4iTdA7Aoj_uiI19qIaECNFc/edit#heading=h.en8cy6hno0c6

See everyone tomorrow!

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


Agenda for 5/7/2019 TOC meeting

Chris Aniszczyk
 


Re: Archiving process

Quinton Hoole
 

SGTM

Projects may need more than 2 weeks to respond.

Q


From: cncf-toc@... [cncf-toc@...] on behalf of Liz Rice [liz@...]
Sent: Thursday, May 02, 2019 6:47 PM
To: Alexis Richardson via cncf-toc
Subject: [cncf-toc] Archiving process

There is progress on the proposed process for archiving projects - any comments? 

Thanks,
Liz


Archiving process

Liz Rice
 

There is progress on the proposed process for archiving projects - any comments? 

Thanks,
Liz


Re: RFC: Strimzi

alexis richardson
 

Tom,




On Thu, 2 May 2019, 09:59 Tom Bentley, <tbentley@...> wrote:


On Thu, May 2, 2019 at 2:48 PM Alexis Richardson <alexis@...> wrote:

Yes but what happens when there are two or more clusters?  Does Strimzi support creation of multiple Kafka clusters in one kubernetes cluster?

Yes, of course.

Excellent

Think of these clusters as "tenants".


 
  If so, then those clusters may require different user policies (even if Strimzi doesn't support that yet).


Each Kafka cluster has a distinct set of users, topics, policies, etc. Nothing would be shared.

Super 

Now imagine traffic flowing into the Kube cluster.  If the kafka clusters become overloaded, is there a way to share traffic fairly, without soliciting more Kubernetes cluster resources.



Kind regards,

Tom


Re: RFC: Strimzi

Tom Bentley
 



On Thu, May 2, 2019 at 2:48 PM Alexis Richardson <alexis@...> wrote:

Yes but what happens when there are two or more clusters?  Does Strimzi support creation of multiple Kafka clusters in one kubernetes cluster?

Yes, of course.
 
  If so, then those clusters may require different user policies (even if Strimzi doesn't support that yet).


Each Kafka cluster has a distinct set of users, topics, policies, etc. Nothing would be shared.

Kind regards,

Tom


Re: RFC: Strimzi

alexis richardson
 

Tom

On Thu, 2 May 2019, 09:26 Tom Bentley, <tbentley@...> wrote:
Hi Alexis,

On Wed, May 1, 2019 at 10:11 AM Alexis Richardson <alexis@...> wrote:
Kafka itself is not multi-tennant. Neither messages nor topics are owned authorised entities. So although it has different retention policies for messages, they're not associated with users or tenants. Rate limiting / quotas of connected clients are features of Kafka itself, rather than being something Strimzi adds. Therefore it might be hard to separate it as a general concept.

Perhaps I misunderstood but isn't one goal of Strimzi to enable Kafka-aaS.


Strimzi provides operators which make it easy for different users to create their own Kafka clusters, (plus topics, users etc within those clusters). It does not provide support for a single Kafka cluster supporting multiple tenants. Obviously it is possible provide abstractions to do that on top of Kafka, but that's not what Strimzi provides.

Yes but what happens when there are two or more clusters?  Does Strimzi support creation of multiple Kafka clusters in one kubernetes cluster?  If so, then those clusters may require different user policies (even if Strimzi doesn't support that yet).

A






Regards,

Tom


Re: RFC: Strimzi

Tom Bentley
 

Hi Alexis,

On Wed, May 1, 2019 at 10:11 AM Alexis Richardson <alexis@...> wrote:
Kafka itself is not multi-tennant. Neither messages nor topics are owned authorised entities. So although it has different retention policies for messages, they're not associated with users or tenants. Rate limiting / quotas of connected clients are features of Kafka itself, rather than being something Strimzi adds. Therefore it might be hard to separate it as a general concept.

Perhaps I misunderstood but isn't one goal of Strimzi to enable Kafka-aaS.


Strimzi provides operators which make it easy for different users to create their own Kafka clusters, (plus topics, users etc within those clusters). It does not provide support for a single Kafka cluster supporting multiple tenants. Obviously it is possible provide abstractions to do that on top of Kafka, but that's not what Strimzi provides.

Regards,

Tom


Re: RFC: Strimzi

alexis richardson
 

Tom




On Wed, 1 May 2019, 04:23 Tom Bentley, <tbentley@...> wrote:
Hi Alexis,

On Wed, Apr 10, 2019 at 4:47 PM alexis richardson <alexis@...> wrote:
David

Thanks.  I would prioritise open governance over reducing your
committers, but up to you.

I just wanted to let people know that the project has now adopted an open governance model (https://github.com/strimzi/strimzi-kafka-operator/blob/master/GOVERNANCE.md) as a first step. We expect to broaden the maintainers beyond Red Hat over time.

Fantastic news - congratulations.


 
Re quotas.  Any multi-tenant system that holds data for any length of
time faces the question of how available resources may be allocated to
tenants.  Typically a quota system is used.  If your users are single
tenant, then you don't need this.

Kafka itself is not multi-tennant. Neither messages nor topics are owned authorised entities. So although it has different retention policies for messages, they're not associated with users or tenants. Rate limiting / quotas of connected clients are features of Kafka itself, rather than being something Strimzi adds. Therefore it might be hard to separate it as a general concept.

Perhaps I misunderstood but isn't one goal of Strimzi to enable Kafka-aaS.





Re: RFC: Strimzi

Tom Bentley
 

Hi Alexis,

On Wed, Apr 10, 2019 at 4:47 PM alexis richardson <alexis@...> wrote:
David

Thanks.  I would prioritise open governance over reducing your
committers, but up to you.

I just wanted to let people know that the project has now adopted an open governance model (https://github.com/strimzi/strimzi-kafka-operator/blob/master/GOVERNANCE.md) as a first step. We expect to broaden the maintainers beyond Red Hat over time.
 
Re quotas.  Any multi-tenant system that holds data for any length of
time faces the question of how available resources may be allocated to
tenants.  Typically a quota system is used.  If your users are single
tenant, then you don't need this.

Kafka itself is not multi-tennant. Neither messages nor topics are owned authorised entities. So although it has different retention policies for messages, they're not associated with users or tenants. Rate limiting / quotas of connected clients are features of Kafka itself, rather than being something Strimzi adds. Therefore it might be hard to separate it as a general concept.


Re: Announcing Telecom User Group (TUG)

Suresh Krishnan
 



On Apr 12, 2019, at 11:55 AM, Cheryl Hung via Lists.Cncf.Io <chung=linuxfoundation.org@...> wrote:

Hi all,

CNCF is planning to launch a Telecom User Group (TUG) for telcos and their vendors who are using or aiming to use cloud native technologies in their networks. This group is meant to operate in a similar capacity to CNCF's End User Community (since telcos have never been included in CNCF's definition of end users). Unlike the End User Community, telecom vendors are also encouraged to participate in the TUG.

We're not expecting for this group to do any software development, but it may write up requirements, best practices, gap analysis, or similar documents. We're planning to kick off the TUG in a birds-of-a-feather (BoF) in Barcelona and then move to monthly Zoom calls.

That sounds like a great idea Cheryl. I will not be in Barcelona but will be able to join the Zoom calls and contribute to the work.

Thanks
Suresh


Re: Announcing Telecom User Group (TUG)

michael.damena@...
 

Hi Cheryl,

 

Excellent news…

 

Dell Technologies would like to participate in the TUG activities.

 

/br Michael

 

_____________________

Michael M. Damena

DTS Global Principal Architect

Dell Technologies | Select

Mobile +1-817-909-5171

Michael.Damena@...

Southlake, TX

delltechlogosmall

Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, immediately contact the sender by reply e-mail and destroy all copies of the original message.

 

 

 

 

From: cncf-toc@... <cncf-toc@...> On Behalf Of Cheryl Hung
Sent: Friday, April 12, 2019 10:55 AM
To: CNCF TOC
Subject: [cncf-toc] Announcing Telecom User Group (TUG)

 

[EXTERNAL EMAIL]

Hi all,

 

CNCF is planning to launch a Telecom User Group (TUG) for telcos and their vendors who are using or aiming to use cloud native technologies in their networks. This group is meant to operate in a similar capacity to CNCF's End User Community (since telcos have never been included in CNCF's definition of end users). Unlike the End User Community, telecom vendors are also encouraged to participate in the TUG.

 

We're not expecting for this group to do any software development, but it may write up requirements, best practices, gap analysis, or similar documents. We're planning to kick off the TUG in a birds-of-a-feather (BoF) in Barcelona and then move to monthly Zoom calls.

 

Cheers,

Cheryl

 

--

Director of Ecosystem, Cloud Native Computing Foundation


Re: Announcing Telecom User Group (TUG)

Erno Erdelyi
 

Hi Cheryl,

Hi all,

 

Component Soft, a European cloud and cloud native training and consulting company whose most important customers are global telco vendors and operators, would like to also participate in the TUG with Laszlo Budai (laszlo@...) our CTO, Robert Varjasi (robert@...) our senior cloud consultant and myself (erno@...) the company CEO. All three of us would take part in the kick off session in Barcelona as well.

 

Please keep is in the update circle!

 

Regards,

 

Erno Erdelyi

managing director

Component Soft

Galvani str. 2.                                                  

Budapest, Hungary, 1116

Phone: +36 1 487-4040

Email: erno@...

Internet: http://www.componentsoft.io

 

From: cncf-toc@... <cncf-toc@...> On Behalf Of Cheryl Hung
Sent: Friday, April 12, 2019 5:55 PM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] Announcing Telecom User Group (TUG)

 

Hi all,

 

CNCF is planning to launch a Telecom User Group (TUG) for telcos and their vendors who are using or aiming to use cloud native technologies in their networks. This group is meant to operate in a similar capacity to CNCF's End User Community (since telcos have never been included in CNCF's definition of end users). Unlike the End User Community, telecom vendors are also encouraged to participate in the TUG.

 

We're not expecting for this group to do any software development, but it may write up requirements, best practices, gap analysis, or similar documents. We're planning to kick off the TUG in a birds-of-a-feather (BoF) in Barcelona and then move to monthly Zoom calls.

 

Cheers,

Cheryl

 

--

Director of Ecosystem, Cloud Native Computing Foundation


Re: Announcing Telecom User Group (TUG)

wang.changjin@...
 

Hi,

I‘d like to  join the TUG being a telco vendor from ZTE.


王长金 Wang ChangJin


电信云及核心网产品团队/无线产品经营部   CCN Product Team/Wireless Product Operation



南京市雨花台区花神大道6号
ZTE Corporation, 6# Huashen Rd,
Yuhuatai District, Nanjing, P.R.China, 210012
T: +86 25 52877110 F:+86 25 52870000
M: +86 15850586900
E: wang.changjin@...
www.zte.com.cn
原始邮件
发件人:CherylHung <chung@...>
收件人:CNCF TOC <cncf-toc@...>;
日 期 :2019年04月12日 23:56
主 题 :[cncf-toc] Announcing Telecom User Group (TUG)
Hi all,

CNCF is planning to launch a Telecom User Group (TUG) for telcos and their vendors who are using or aiming to use cloud native technologies in their networks. This group is meant to operate in a similar capacity to CNCF's End User Community (since telcos have never been included in CNCF's definition of end users). Unlike the End User Community, telecom vendors are also encouraged to participate in the TUG.
We're not expecting for this group to do any software development, but it may write up requirements, best practices, gap analysis, or similar documents. We're planning to kick off the TUG in a birds-of-a-feather (BoF) in Barcelona and then move to monthly Zoom calls.

Cheers,
Cheryl

--
Director of Ecosystem, Cloud Native Computing Foundation



Re: Announcing Telecom User Group (TUG)

Gergely Csatari
 

Hi,

 

I would like to join from Nokia side if possible.

 

Br,

Gerg0

 

From: cncf-toc@... <cncf-toc@...> On Behalf Of Xuan Jia via Lists.Cncf.Io
Sent: Saturday, April 13, 2019 8:54 AM
To: Cheryl Hung <chung@...>
Cc: cncf-toc@...
Subject: Re: [cncf-toc] Announcing Telecom User Group (TUG)

 

That's a great news for China Mobile. 

I'd like to join in this group

Xuan Jia

China Mobile

 

Cheryl Hung <chung@...> 2019412日周五 下午11:55写道:

Hi all,

 

CNCF is planning to launch a Telecom User Group (TUG) for telcos and their vendors who are using or aiming to use cloud native technologies in their networks. This group is meant to operate in a similar capacity to CNCF's End User Community (since telcos have never been included in CNCF's definition of end users). Unlike the End User Community, telecom vendors are also encouraged to participate in the TUG.

 

We're not expecting for this group to do any software development, but it may write up requirements, best practices, gap analysis, or similar documents. We're planning to kick off the TUG in a birds-of-a-feather (BoF) in Barcelona and then move to monthly Zoom calls.

 

Cheers,

Cheryl

 

--

Director of Ecosystem, Cloud Native Computing Foundation


Re: Apologies

Chris Aniszczyk
 

No worries, it's cancelled.

Enjoy the vacation!

On Mon, Apr 15, 2019 at 3:06 PM Liz Rice <liz@...> wrote:

And I am also on vacation this week and so also apologise for missing TOC tomorrow. Will be back next week though.

Liz
On 15 Apr 2019, 11:03 +0200, alexis richardson <alexis@...>, wrote:

I shall miss TOC tomorrow and next week due to vacation.

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


Re: Apologies

Liz Rice
 

And I am also on vacation this week and so also apologise for missing TOC tomorrow. Will be back next week though. 

Liz

On 15 Apr 2019, 11:03 +0200, alexis richardson <alexis@...>, wrote:
I shall miss TOC tomorrow and next week due to vacation. 


Apologies

alexis richardson
 

I shall miss TOC tomorrow and next week due to vacation. 


Re: CNCF Storage SIG - Mission/Purpose/Ownership?

Liz Rice
 

Thanks Saad. Agreed, if we are admitting more projects into the Sandbox, we have to be much clearer about what level of endorsement (or lack of) that implies. I'd like to have some discussion on this in a TOC meeting soon, and we can also work on this through the PR that Matt kicked off about clarifying the project proposal and admission process (https://github.com/cncf/toc/issues/214)

On 12 Apr 2019, 19:11 +0100, Saad Ali <saadali@...>, wrote:
Thanks for taking the time to respond Liz and Shannon!

I agree that the timing is not quite right. We can't make SIG sponsorship a requirement for new projects before SIGs even exist -- we have to let the SIGs mature and prove they're capable of taking on the responsibility first.

I'm still concerned about the requirements for the CNCF Sandbox. Mainly, I believe the Sandbox provides tangible benefits (mainly visibility) to projects and therefore the CNCF should have a higher bar for the projects it accepts. I think the CNCF should pro-actively curate the CNCF ecosystem rather then passively accepting projects.

That said, I do see the benefits of a model where more projects can more easily join the CNCF. And I understand this is the direction that the TOC has already agreed to take. I hope as this we move towards this model, we can also find a way to maintain clear messaging around which projects are and are not endorsed by the CNCF, and continue to make the endorsement process open, transparent, and inclusive. 

Thank you all for taking the time to entertain my thoughts! Happy Friday =)

On Fri, Apr 12, 2019 at 10:34 AM Shannon Williams <shannon@...> wrote:

+1 with Liz.  It is actually quite difficult for a project to get sponsorship from two members of the TOC, and incredibly difficult to get sponsorship from 6.   The TOC is elected for exactly the purpose of bringing great projects into the CNCF.

 

The sandbox is a way for developers of interesting projects to show they have passed a meaningful bar (two TOC members find the project valuable) and make a firm commitment to open governance of their project. 

 

A richer sandbox will help to ensure that the CNCF continues to attract great projects, and allow projects to demonstrate maturity and market adoption over time.  Without the sandbox, we end up with a very high bar for entry (2/3 of the TOC) and many relevant projects forced to look to other organizations for open governance.   The richer the CNCF ecosystem, the less we will be king makers, and the more people will realize that the CNCF isn’t tyring to build a product, but rather providing a framework for open innovation and governance. 

 

The only improvement that I think might be useful for the sandbox is to require projects to come up for a broader vote after some period of time. Perhaps 2-3 years.  At that time, the whole board could vote on having the project graduate (6 votes), remain in the sandbox (2 votes) or be removed from the sandbox (6 votes?)

 

I think OpenEBS is almost exactly the type of project the sandbox is designed for.  If two members of the TOC are open to sponsoring it, I hope it will be added.

 

Best Regards,

 

Shannon Williams

Rancher Labs

shannon@...

+1 650-521-6902

 

From: cncf-toc@... <cncf-toc@...> On Behalf Of Liz Rice via Lists.Cncf.Io
Sent: Friday, April 12, 2019 8:43 AM
To: Alexis Richardson <alexis@...>; saadali@...
Cc: cncf-toc@...
Subject: Re: [cncf-toc] CNCF Storage SIG - Mission/Purpose/Ownership?

 

Hi Saad, 

 

This is a good discussion to have. I don’t believe it would be right to require SIG sponsorship before a project joins the CNCF, at least at this time, for a couple of reasons: 

  • CNCF SIGs are brand new. So new, most of them don’t exist yet.  
  • I see the SIGs as formalising a way for the TOC to get help (both expertise and time) from recognized specialists across the community. But the responsibilities still ultimately lie with the TOC. 


Liz

On 12 Apr 2019, 15:41 +0100, via Lists.Cncf.Io <saadali=google.com@...>, wrote:

Sorry, I wasn't involved in those discussions.

 

Based on the published SIG charter, the purpose of these SIGs is to "Scale contributions by the CNCF technical and user community" with goals including "Strengthen the project ecosystem", "Identify gaps in the CNCF project portfolio", and "Reduce some project workload on TOC".

 

To that end, extending the charter to add a formal requirement for all external project to first get a CNCF SIG to sponsor them seems reasonable and in line? Doing so would "Strengthen the project ecosystem", "Identify gaps in the CNCF project portfolio", and "Reduce some project workload on TOC". In addition, as I mentioned before, it would give these new CNCF SIGs clear long-term ownership of something concrete, and help ensure that the CNCF decision making process is open, transparent, and inclusive.

 

It sounds like you're firmly against that, and if so, I'd like to understand why? What am I missing?

 

And I apologize if I'm coming across as combative. My intention is to ensure we're doing the right things for our users and building healthy communities. So please bear with me as I try to make sense of this.

 

On Thu, Apr 11, 2019 at 5:03 PM Alexis Richardson <alexis@...> wrote:

The purpose is documented in the SIG charter that we voted on recently.


On Thu, Apr 11, 2019 at 5:01 PM Saad Ali <saadali@...> wrote:
>
> Sure, SIGs can do what they want. And the final decision is still up to TOC.
>
> But would you support adding a formal requirement for all external project to first get a CNCF SIG to sponsor them? If not, why not, and what do you see as the purpose of these new CNCF SIGs?
>
> On Thu, Apr 11, 2019 at 4:44 PM Alexis Richardson <alexis@...> wrote:
>>
>> The SIGs can do whatever they like!  But the final decision is not for
>> delegation.
>>
>> On Thu, Apr 11, 2019 at 4:32 PM Saad Ali <saadali@...> wrote:
>> >
>> > Thanks Alexis.
>> >
>> > Deciding which projects join the CNCF is one of the most important decisions the CNCF TOC is responsible for. And as far as I can tell, the only major requirement for joining the CNCF sandbox currently is support of "2 TOC sponsors".
>> >
>> > My understanding is that these CNCF SIGs are being formed, at least in part, to help the TOC with that decision making. But from everything I've read, it doesn't seem like these SIGs will have any real ownership of anything.
>> >
>> > So I propose that that in order to be inducted in to the CNCF (at any level, including Sandbox), an external project must get a CNCF SIG to sponsor it first? Each SIG would define the process for project consideration, establish criteria for the categories of project to be considered, etc.
>> >
>> > This would give these new CNCF SIGs clear long-term ownership of something concrete, and we would ensure that the CNCF decision making process is open, transparent, and inclusive.
>> >
>> > Of course, the TOC would still retain the right to veto the SIG decision, but it would do so publicly and provide justification for doing so.
>> >
>> > Thoughts?
>> >
>> > On Wed, Apr 10, 2019 at 5:45 PM Alexis Richardson <alexis@...> wrote:
>> >>
>> >> Saad
>> >>
>> >> Unlike K8s TOC & SIGs, the CNCF TOC will own final decisions on
>> >> project acceptance.
>> >>
>> >> alexis
>> >>
>> >> On Wed, Apr 10, 2019 at 5:37 PM via Lists.Cncf.Io
>> >> <saadali=google.com@...> wrote:
>> >> >
>> >> > Thanks Quinton and Alex! This is very helpful.
>> >> >
>> >> > Based on that, it seems to me like the responsibilities for this SIG are essentially to collect and disseminate storage related information in a consumable manner to 1) the CNCF TOC, 2) CNCF end users, and 3) CNCF projects (at all stages from pre-incubation through to graduation)?
>> >> >
>> >> > If so, then the concrete work this group will be responsible for is conducting research (surveys, etc.) and the output will be documents summarizing the results of the research for various audiences?
>> >> >
>> >> > The Storage Whitepaper produced by this group is out. User survey is in progress. What kind of work concretely do you see going forward?
>> >> >
>> >> > In Kubernetes the TOC tries to avoid making unilateral decisions as much as possible. Instead the Kubernetes TOC empowers the SIGs to make decisions.
>> >> >
>> >> > Right now the CNCF TOC is considering incubating a new storage project. Is the recommendation for accepting or rejecting that proposal be in the purview of this proposed SIG? If so, will the CNCF TOC sponsors have to get the approval of a SIG for any sponsored projects?
>> >> >
>> >> > On Wed, Apr 10, 2019 at 2:01 PM Alex Chircop <alex.chircop@...> wrote:
>> >> >>
>> >> >> Hi Saad,
>> >> >>
>> >> >>
>> >> >>
>> >> >> Thanks for throwing your hat into the ring ! :-)
>> >> >>
>> >> >>
>> >> >>
>> >> >> (apologies for the long email, but the info will hopefully benefit the rest of the mailing list too)
>> >> >>
>> >> >>
>> >> >>
>> >> >> The CNCF SIGs are being setup to help the TOC as the CNCF continues to scale with the growing list of projects and members.
>> >> >>
>> >> >> All the detail for the proposal/formation of the CNCF SIGs is available here: https://github.com/cncf/toc/blob/master/sigs/cncf-sigs.md
>> >> >>
>> >> >>
>> >> >>
>> >> >> In summary, the general objectives are:
>> >> >>
>> >> >> Strengthen the project ecosystem to meet the needs of end users and project contributors.
>> >> >> Identify gaps in the CNCF project portfolio. Find and attract projects to fill these gaps.
>> >> >> Educate and inform users with unbiased, effective, and practically useful information.
>> >> >> Focus attention & resources on helping foster project maturity, systematically across CNCF projects.
>> >> >> Clarify relationship between projects, CNCF project staff, and community volunteers.
>> >> >> Engage more communities and create an on-ramp to effective TOC contribution & recognition.
>> >> >> Reduce some project workload on TOC while retaining executive control & tonal integrity with this elected body.
>> >> >> Avoid creating a platform for politics between vendors.
>> >> >>
>> >> >>
>> >> >>
>> >> >> and the specific responsibilities of the SIG include:
>> >> >>
>> >> >>
>> >> >>
>> >> >> Project Handling:
>> >> >>
>> >> >> Understand and document a high level roadmap of projects within this space, including CNCF and non-CNCF projects. Identify gaps in project landscape.
>> >> >> For projects that fall within the CNCF, perform health checks.
>> >> >> Perform discovery of and outreach to candidate projects
>> >> >> Help candidate projects prepare for presentation to the TOC
>> >> >> Every CNCF project will be assigned to one suitable SIG by the TOC.
>> >> >>
>> >> >> End User Education (Outbound Communication)
>> >> >>
>> >> >> Provide up-to-date, high quality, unbiased and easy-to-consume material to help end users to understand and effectively adopt cloud-native technologies and practises within the SIG’s area, for example:
>> >> >>
>> >> >> White papers, presentations, videos, or other forms of training clarifying terminology, comparisons of different approaches, available projects or products, common or recommended practises, trends, illustrative successes and failures, etc.
>> >> >> As far as possible, information should be based on research and fact gathering, rather than pure marketing or speculation.
>> >> >>
>> >> >> End User Input Gathering (Inbound Communication)
>> >> >>
>> >> >> Gather useful end user input and feedback regarding expectations, pain points, primary use cases etc.
>> >> >> Compile this into easily consumable reports and/or presentations to assist projects with feature design, prioritization, UX etc.
>> >> >>
>> >> >> Community Enablement
>> >> >>
>> >> >> SIGs are open organizations with meetings, meeting agendas and notes, mailing lists, and other communications in the open
>> >> >> The mailing list, SIG meeting calendar, and other communication documents of the SIG will be openly published and maintained
>> >> >>
>> >> >> As Trusted Expert Advisors to the TOC
>> >> >>
>> >> >> Perform technical due diligence on new and graduating projects, and advise TOC on findings.
>> >> >> Be involved with, or periodically check in with projects in their area, and advise TOC on health, status and proposed actions (if any) as necessary or on request.
>> >> >>
>> >> >> See Example Responsibilities of a CNCF SIG.
>> >> >>
>> >> >>
>> >> >>
>> >> >> The first set of SIGs as per the proposal and the TOC members who will act as liaison with the SIG are:
>> >> >>
>> >> >> (from: https://docs.google.com/presentation/d/1BUmTO5PFt7NZ9jVMMR3r1W7k8NANltNNJJqFCZdbS0I/edit#slide=id.g4e24cc378e_1_39)
>> >> >>
>> >> >> Matt: Traffic (networking, service discovery, load balancing, service mesh, RPC, pubsub, etc)
>> >> >>
>> >> >> Envoy, Linkerd, NATS, gRPC, CoreDNS, CNI
>> >> >>
>> >> >> Jeff: Observability (monitoring, logging, tracing, profiling, etc.)
>> >> >>
>> >> >> Prometheus, OpenTracing, Fluentd, Jaeger, Cortex, OpenMetrics,
>> >> >>
>> >> >> Liz + Joe: Security/Governance (auth, authorization, auditing, policy enforcement, compliance, GDPR, cost management, etc)
>> >> >>
>> >> >> SPIFFE, SPIRE, Open Policy Agent, Notary, TUF,  Falco,
>> >> >>
>> >> >> Michelle + Alexis: App Dev, Ops & Testing (PaaS, Serverless, Operators, CI/CD,  Conformance, Chaos Eng, Scalability and Reliability measurement etc.)
>> >> >>
>> >> >> Helm, CloudEvents, Telepresence, Buildpacks, (CNCF CI)
>> >> >>
>> >> >> Brendan + Brian: Core and Applied Architectures (orchestration, scheduling, container runtimes, sandboxing technologies, packaging and distribution, specialized architectures thereof (e.g. Edge, IoT, Big Data, AI/ML, etc).
>> >> >>
>> >> >> Kubernetes, containerd, rkt, Harbor, Dragonfly, Virtual Kubelet
>> >> >>
>> >> >> Xiang: Storage (Block and File Stores, Databases, Key-Value stores etc)
>> >> >>
>> >> >> TiKV, etcd, Vitess, Rook
>> >> >>
>> >> >>
>> >> >>
>> >> >> Hope this helps,
>> >> >>
>> >> >>
>> >> >>
>> >> >> Kind Regards,
>> >> >>
>> >> >> Alex
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> From: Saad Ali <saadali@...>
>> >> >> Date: Wednesday, 10 April 2019 at 21:38
>> >> >> To: Quinton Hoole <quinton@...>, cncf-wg-storage <cncf-wg-storage@...>, "cncf-toc@..." <cncf-toc@...>, Alex Chircop <alex.chircop@...>
>> >> >> Subject: CNCF Storage SIG - Mission/Purpose/Ownership?
>> >> >>
>> >> >>
>> >> >>
>> >> >> Hi CNCF Storage WG,
>> >> >>
>> >> >>
>> >> >>
>> >> >> Following up on the CNCF Storage WG meeting this morning: I'm considering throwing my hat in to the ring as a possible TL for the proposed CNCF Storage SIG. I'm currently Co-chair/TL of SIG Storage.
>> >> >>
>> >> >>
>> >> >>
>> >> >> That said, I'd first like to understand what this new CNCF SIG will own?
>> >> >>
>> >> >>
>> >> >>
>> >> >> The Kubernetes Storage SIG, for example, has clear ownership of the Kubernetes volume sub-system. This, CNCF storage workgroup, so far has produced whitepapers on the storage landscape, surveyed users, and hosted presentations from 3rd party storage projects. While all valuable, these are short term tasks.
>> >> >>
>> >> >>
>> >> >>
>> >> >> My goal here is to make sure we act intentionally with a clear mission and purpose. A group without something to own will, at best, waste time, and, at worst, cause unnecessary conflict. To that end, I want to make sure the SIG has an obvious, long-term ownership of something concrete.
>> >> >>
>> >> >>
>> >> >>
>> >> >> Thoughts? What do we think will be the long term sustainability strategy for this new SIG? What will it own?
>> >> >>
>> >> >>
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >>
>> >> >>
>> >> >> Saad Ali
>> >> >>
>> >> >>
>> >> >

4121 - 4140 of 7342