|
Re: Serverless WG formation
Sebastien Goasguen <sebgoa@...>
Kubeless will participate
-sebastien
On Tue, May 16, 2017 at 6:41 PM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote: Ken
Can you solicit some oss projects to get involved? Is that doable? Please let us know!
A
On Tue, 16 May 2017, 17:32 Antonio Gulli via cncf-toc, < cncf-toc@...> wrote: thanks Ken, I'd like to participate as well for Google Cloud Function, with a particular interest for portable container environment, standard events, etc Cheers //A
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
-- Sebastien Goasguen Senior Director of Cloud Technologies, Bitnami +41 79 367 38 25 @sebgoa
Run your favorite apps in the cloud with http://bitnami.com/cloud Confidential - All Rights Reserved. BitRock © 2017
|
|
|
Re: Serverless WG formation
Ken
Can you solicit some oss projects to get involved? Is that doable? Please let us know!
A
On Tue, 16 May 2017, 17:32 Antonio Gulli via cncf-toc, < cncf-toc@...> wrote: thanks Ken, I'd like to participate as well for Google Cloud Function, with a particular interest for portable container environment, standard events, etc Cheers //A
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: [VOTE] CNI project proposal (incubation)
+1 non-binding
--
Jong Choi
VP, NCSOFT
_____________________________
From: Mark Coleman via cncf-toc < cncf-toc@...>
Sent: Wednesday, May 17, 2017 1:06 AM
Subject: Re: [cncf-toc] [VOTE] CNI project proposal (incubation)
To: < cncf-toc@...>, Randy Abernethy < randy.abernethy@...>
+1 non-binding
On Tue, 16 May 2017 at 17:43, Randy Abernethy via cncf-toc < cncf-toc@...> wrote:
On 2017-05-15 13:08, Doug Davis via cncf-toc wrote:
+1 non-binding
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
Chris
Aniszczyk via cncf-toc ---05/15/2017 12:44:09 PM---The TOC has decided to invite CNI (https://github.com/containernetworking/) as an incubation level C
From: Chris Aniszczyk via cncf-toc
<cncf-toc@...>
To: CNCF TOC
<cncf-toc@...>
Date: 05/15/2017 12:44 PM
Subject: [cncf-toc] [VOTE] CNI project proposal (incubation)
Sent by: cncf-toc-bounces@...
The TOC has decided to invite CNI (https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC:
The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of
containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement (https://github.com/containernetworking/cni/blob/master/SPEC.md)
Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/36
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_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________cncf-toc mailing listcncf-toc@...https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
--
|
|
|
Re: Serverless WG formation
thanks Ken, I'd like to participate as well for Google Cloud Function, with a particular interest for portable container environment, standard events, etc Cheers //A
Thanks Ken,
Chiming in for Fission.io -- I'd like to participate too, and we're
especially interested in function portability across different serverless
platforms, and standardization around event formats etc.
-Soam
On Tue, May 16, 2017 at 9:06 AM, Kenneth Owens (kenowens) via cncf-toc <
cncf-toc@...> wrote:
> Today on the TOC call we discussed starting a Serverless workgroup and I
> agreed to chair said workgroup. There was no disagreement on the call but
> many TOC members were not present. Please respond with concerns or
> agreement.
>
>
>
> Thanks,
>
>
>
> Ken
>
>
>
> [image: banner2]
>
>
>
> *Kenneth Owens*
>
> CTO
>
> kenowens@...
>
> Tel: *+1 408 424 0872 <(408)%20424-0872>*
>
> *Cisco Systems, Inc.*
>
> 16401 Swingley Ridge Road Suite 400
> CHESTERFIELD
> 63017
> United States
> cisco.com
>
>
>
> [image: http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think
> before you print.
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. Any review, use, distribution or disclosure
> by others is strictly prohibited. If you are not the intended recipient (or
> authorized to receive for the recipient), please contact the sender by
> reply email and delete all copies of this message.
>
> Please click here
> <http://www.cisco.com/web/about/doing_business/legal/cri/index.html> for
> Company Registration Information.
>
>
>
> _______________________________________________
> cncf-toc mailing list
> cncf-toc@...
> https://lists.cncf.io/mailman/listinfo/cncf-toc
>
>
-- Antonio Gulli | Site Lead && Eng. Director | gulli@...
|
|
|
Re: Serverless WG formation
Thanks Ken,
Chiming in for Fission.io -- I'd like
to participate too, and we're especially interested in function
portability across different serverless platforms, and standardization around event formats etc. -Soam
On Tue, May 16, 2017 at 9:06 AM, Kenneth Owens (kenowens) via cncf-toc <cncf-toc@...> wrote:
Today on the TOC call we discussed starting a Serverless workgroup and I agreed to chair said workgroup. There was no disagreement on the call but many TOC members were not present. Please respond with concerns or agreement.
Thanks,
Ken
|
 Think
before you print.
|
|
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is
strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please
click here for Company Registration Information.
|
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: Serverless WG formation
I agree and will participate.
As an aside, I consider our definition of "Cloud Native” being container-packaged, too limiting.
- Lee
On May 16, 2017, at 11:06 AM, Kenneth Owens (kenowens) via cncf-toc < cncf-toc@...> wrote:
Today on the TOC call we discussed starting a Serverless workgroup and I agreed to chair said workgroup. There was no disagreement on the call but many TOC members were not present. Please respond with concerns or agreement. Thanks, Ken <image001.png> | | | | Kenneth Owens CTO Tel: +1 408 424 0872 | Cisco Systems, Inc. 16401 Swingley Ridge Road Suite 400
CHESTERFIELD
63017
United States
cisco.com | |
<image002.gif>Think before you print. | This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Please click here for Company Registration Information. |
|
|
|
Kenneth Owens (kenowens) <kenowens@...>
Today on the TOC call we discussed starting a Serverless workgroup and I agreed to chair said workgroup. There was no disagreement on the call but many TOC members were not present. Please respond with concerns or agreement.
Thanks,
Ken
|
|
|
|
|
|
|
Kenneth Owens
CTO
kenowens@...
Tel:
+1 408 424 0872
|
Cisco Systems, Inc.
16401 Swingley Ridge Road Suite 400
CHESTERFIELD
63017
United States
cisco.com
|
|
|
 Think
before you print.
|
|
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is
strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please
click here for Company Registration Information.
|
|
|
|
Re: [VOTE] CNI project proposal (incubation)
+1 non-binding
toggle quoted messageShow quoted text
On Tue, 16 May 2017 at 17:43, Randy Abernethy via cncf-toc < cncf-toc@...> wrote:
On 2017-05-15 13:08, Doug Davis via
cncf-toc wrote:
+1 non-binding
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
Chris Aniszczyk via cncf-toc ---05/15/2017 12:44:09
PM---The TOC has decided to invite CNI (https://github.com/containernetworking/)
as an incubation level C
From: Chris
Aniszczyk via cncf-toc <cncf-toc@...>
To: CNCF
TOC <cncf-toc@...>
Date: 05/15/2017
12:44 PM
Subject: [cncf-toc]
[VOTE] CNI project proposal (incubation)
Sent by: cncf-toc-bounces@...
The TOC has decided to invite CNI (https://github.com/containernetworking/)
as an incubation level CNCF project, sponsored by Ken Owens from
the TOC:
The CNI (Container Network Interface) project consists of a
specification and libraries for writing plugins to configure
network interfaces in Linux containers, along with a number of
supported plugins. CNI concerns itself only with network
connectivity of containers and removing allocated resources when
the container is deleted. Because of this focus, CNI has a wide
range of support (from Kubernetes, rkt, Mesos and more) and the
specification is simple to implement (https://github.com/containernetworking/cni/blob/master/SPEC.md)
Please vote (+1/0/-1) on the full project proposal located here on
GitHub:
https://github.com/cncf/toc/pull/36
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_______________________________________________
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
--
Randy Abernethy
Managing Partner
RX-M, LLC
randy.abernethy@...
o 415-800-2922
c 415-624-6447
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Sugu Please see here for Jepsen and (f.ex) CockroachDB https://jepsen.io/analyses/cockroachdb-beta-20160829alexis On Tue, Apr 25, 2017 at 2:58 PM, Chris Aniszczyk <caniszczyk@...> wrote: Once you're an official CNCF project, most of these benefits are included so
it's not an issue :)
The next step would be to finalize the TOC sponsor (Brian), potentially
sketch out a proposal (you can find examples one here:
https://github.com/cncf/toc/tree/master/proposals) and on the next CNCF TOC
call, have the TOC discuss whether to formally invite the project for a
proposal per request of the TOC sponsor (Brian).
I'll respond to your specific points below:
- Help with marketing & PR. This is one area we're severely lacking.
We take care of this for projects and I think it's one of the most valuable
things we provide for CNCF projects (also conference space etc). We list
most of the benefits on this page: https://www.cncf.io/projects/
- Advocacy through the ambassador program.
Not a problem either: https://www.cncf.io/about/ambassadors/
- Take over funding (and ownership) of vitess.io, vitess.slack.io, github
repository, travis builds, and other CI & CD resources.
In terms of financial and neutral ownership, not a problem either.
- Help with setting up governance.
This we can help with if projects request it. For example, we are currently
working with the Prometheus team to finalize their governance and more than
willing to help if projects request it.
On Tue, Apr 25, 2017 at 1:30 AM, Alexis Richardson <alexis@...>
wrote:
That's a great list.
Chris, what are your thoughts?
On Tue, 25 Apr 2017, 02:48 Sugu Sougoumarane, <sougou@...> wrote:
Hi Alexis,
Here are areas where we'd love to get help for Vitess:
- Help with marketing & PR. This is one area we're severely lacking.
- Advocacy through the ambassador program.
- Take over funding (and ownership) of vitess.io, vitess.slack.io, github
repository, travis builds, and other CI & CD resources.
- Help with setting up governance.
I'm still working on the product comparison (distracted by the Percona
conference). I'll try to get that done by next week.
On Wed, Apr 19, 2017 at 12:59 PM, Alexis Richardson <alexis@...>
wrote:
Sugu
Thank-you. Those are good reasons! Are there specific places where
you'd like help winning or keeping more contributors?
Look forward to your view on systems & tradeoffs. Can I humbly ask
that you include Cockroach, Rethink & Goshawk? Maybe others.
a
On Wed, Apr 19, 2017 at 8:31 PM, Sugu Sougoumarane via cncf-toc
<cncf-toc@...> wrote:
Hi Chris, Alexis,
For the license, we already intend to change it to ALv2:
https://github.com/youtube/vitess/issues/2694.
For the comparison of various systems and trade-offs, we'll try to put
something together in the next few days.
As for why we're excited about wanting to join CNCF, I think this
issue
describes it well: https://github.com/youtube/vitess/issues/2670.
PS: Thanks for the adopters suggestion on github. I'll work on that,
and
also see if we can feature them on vitess.io.
On Wed, Apr 19, 2017 at 9:16 AM, Chris Aniszczyk via cncf-toc
<cncf-toc@...> wrote:
Also in terms of process, I believe Brian Grant on today's call has
expressed interest in sponsoring the project from the TOC. I'd
suggest at a
following or next TOC meeting to decide whether the TOC desires to
formally
invite the project.
Another thing to bring up is that Vitess is currently under the BSD-3
license (https://github.com/youtube/vitess/blob/master/LICENSE),
which isn't
a major issue, but we will have to decide what approach to take (move
to
ALv2 or go for an exception) if they become a project.
On Wed, Apr 19, 2017 at 11:02 AM, Alexis Richardson via cncf-toc
<cncf-toc@...> wrote:
Sugu
Thank you again for your pres today.
What would *help Vitess the most* from a project advancement & end
user
POV? How can CNCF help?
a
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
--
Chris Aniszczyk (@cra) | +1-512-961-6719
_______________________________________________
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: [VOTE] CNI project proposal (incubation)
+1 non binding
On 2017-05-15 13:08, Doug Davis via
cncf-toc wrote:
+1 non-binding
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
 Chris Aniszczyk via cncf-toc ---05/15/2017 12:44:09
PM---The TOC has decided to invite CNI (https://github.com/containernetworking/)
as an incubation level C
From: Chris
Aniszczyk via cncf-toc <cncf-toc@...>
To: CNCF
TOC <cncf-toc@...>
Date: 05/15/2017
12:44 PM
Subject: [cncf-toc]
[VOTE] CNI project proposal (incubation)
Sent by: cncf-toc-bounces@...
The TOC has decided to invite CNI (https://github.com/containernetworking/)
as an incubation level CNCF project, sponsored by Ken Owens from
the TOC:
The CNI (Container Network Interface) project consists of a
specification and libraries for writing plugins to configure
network interfaces in Linux containers, along with a number of
supported plugins. CNI concerns itself only with network
connectivity of containers and removing allocated resources when
the container is deleted. Because of this focus, CNI has a wide
range of support (from Kubernetes, rkt, Mesos and more) and the
specification is simple to implement (https://github.com/containernetworking/cni/blob/master/SPEC.md)
Please vote (+1/0/-1) on the full project proposal located here on
GitHub:
https://github.com/cncf/toc/pull/36
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_______________________________________________
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
--
Randy Abernethy
Managing Partner
RX-M, LLC
randy.abernethy@...
o 415-800-2922
c 415-624-6447
|
|
|
FYI: Agenda CNCF TOC Meeting: 5/16/2017
Chris Aniszczyk
|
|
|
Re: [VOTE] CNI project proposal (incubation)
Duncan Johnston Watt <duncan.johnstonwatt@...>
toggle quoted messageShow quoted text
On 15 May 2017 at 17:43, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote: The TOC has decided to invite CNI ( https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC: The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement ( https://github.com/containernetworking/cni/blob/master/SPEC.md) Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/36Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support! Thanks!
--
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: [VOTE] CNI project proposal (incubation)
John Belamaric
toggle quoted messageShow quoted text
On May 15, 2017, at 9:43 AM, Chris Aniszczyk via cncf-toc < cncf-toc@...> wrote:
The TOC has decided to invite CNI ( https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC:
The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of
containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement ( https://github.com/containernetworking/cni/blob/master/SPEC.md)
Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/36
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
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: [VOTE] CNI project proposal (incubation)
Bernstein, Joshua <Joshua.Bernstein@...>
+1
-Josh
On May 15, 2017, at 2:08 PM, Doug Davis via cncf-toc < cncf-toc@...> wrote:
toggle quoted messageShow quoted text
+1 non-binding
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
<graycol.gif>Chris Aniszczyk via cncf-toc ---05/15/2017 12:44:09 PM---The TOC has decided to invite CNI (https://github.com/containernetworking/) as an incubation level C
From: Chris Aniszczyk via cncf-toc <cncf-toc@...>
To: CNCF TOC <cncf-toc@...>
Date: 05/15/2017 12:44 PM
Subject: [cncf-toc] [VOTE] CNI project proposal (incubation)
Sent by: cncf-toc-bounces@...
The TOC has decided to invite CNI ( https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC:
The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of
containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement ( https://github.com/containernetworking/cni/blob/master/SPEC.md)
Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/36
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 _______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: [VOTE] CNI project proposal (incubation)
+1 non-binding
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
 Chris Aniszczyk via cncf-toc ---05/15/2017 12:44:09 PM---The TOC has decided to invite CNI (https://github.com/containernetworking/) as an incubation level C
From: Chris Aniszczyk via cncf-toc <cncf-toc@...>
To: CNCF TOC <cncf-toc@...>
Date: 05/15/2017 12:44 PM
Subject: [cncf-toc] [VOTE] CNI project proposal (incubation)
Sent by: cncf-toc-bounces@...
The TOC has decided to invite CNI ( https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC: The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement ( https://github.com/containernetworking/cni/blob/master/SPEC.md) Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/36Remember 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 _______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: [VOTE] CNI project proposal (incubation)
toggle quoted messageShow quoted text
On Mon, 15 May 2017, 20:40 Lee Calcote via cncf-toc, < cncf-toc@...> wrote: +1 (non-binding) On May 15, 2017, at 11:43 AM, Chris Aniszczyk via cncf-toc < cncf-toc@...> wrote:
The TOC has decided to invite CNI ( https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC: The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement ( https://github.com/containernetworking/cni/blob/master/SPEC.md) Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/36Remember 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
_______________________________________________ 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: [VOTE] CNI project proposal (incubation)
toggle quoted messageShow quoted text
On May 15, 2017, at 11:43 AM, Chris Aniszczyk via cncf-toc < cncf-toc@...> wrote:
The TOC has decided to invite CNI ( https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC: The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement ( https://github.com/containernetworking/cni/blob/master/SPEC.md) Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/36Remember 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
_______________________________________________ cncf-toc mailing list cncf-toc@...https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: [VOTE] CNI project proposal (incubation)
Solomon Hykes <solomon.hykes@...>
toggle quoted messageShow quoted text
On Mon, May 15, 2017 at 9:43 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote: The TOC has decided to invite CNI ( https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC: The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement ( https://github.com/containernetworking/cni/blob/master/SPEC.md) Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/36Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support! Thanks!
--
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: [VOTE] CNI project proposal (incubation)
otto hillenbrand <otto@...>
toggle quoted messageShow quoted text
On Mon, May 15, 2017 at 2:51 PM, Kenneth Owens (kenowens) via cncf-toc <cncf-toc@...> wrote:
+1
|
 Think
before you print.
|
|
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is
strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please
click here for Company Registration Information.
|
From: cncf-toc-bounces@... [mailto:cncf-toc-bounces@lists.cncf.io]
On Behalf Of Chris Aniszczyk via cncf-toc
Sent: Monday, May 15, 2017 11:44 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] CNI project proposal (incubation)
The TOC has decided to invite CNI (https://github.com/containernetworking/) as an incubation level CNCF project, sponsored by Ken Owens from the TOC:
The CNI (Container Network Interface) project consists of a specification and libraries for writing plugins to configure network interfaces in Linux containers, along with a number of supported plugins. CNI concerns itself only with network connectivity of
containers and removing allocated resources when the container is deleted. Because of this focus, CNI has a wide range of support (from Kubernetes, rkt, Mesos and more) and the specification is simple to implement (https://github.com/containernetworking/cni/blob/master/SPEC.md)
Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/36
Remember that the TOC has binding votes only, but we do appreciate
non-binding votes from the community as a sign of support!
Thanks!
--
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
