|
Dustin Kirkland <dustin.kirkland@...>
|
|
|
toggle quoted message
Show quoted text
On May 15, 2017 8: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
|
|
|
|
|
|
Jonathan Boulle <jonathan.boulle@...>
toggle quoted message
Show quoted text
On 15 May 2017 at 18: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
|
|
|
toggle quoted message
Show quoted text
On Mon, May 15, 2017 at 9:44 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
--
Craig Peters | Director of Product Management | www.scalr.comm: +1 925 639 0804
|
|
|
toggle quoted message
Show quoted text
From: cncf-toc-bounces@... <cncf-toc-bounces@...> on behalf of Chris Aniszczyk via cncf-toc <cncf-toc@...>
Sent: Monday, May 15, 2017 12:43:55 PM
To: 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!
--
Chris Aniszczyk (@cra) | +1-512-961-6719
The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
|
|
|
|
|
|
toggle quoted message
Show 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
-- Benjamin Hindman
Founder of Mesosphere and Co-Creator of Apache Mesos
|
|
|
+1 non-binding
--
Jong Choi
VP, NCSOFT
_____________________________
toggle quoted message
Show quoted text
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
--
|
|
|
+1 non-binding
toggle quoted message
Show 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
|
|
|
+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
|
|
|
Duncan Johnston Watt <duncan.johnstonwatt@...>
toggle quoted message
Show 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
|
|
|
John Belamaric
toggle quoted message
Show 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
|
|
|
Bernstein, Joshua <Joshua.Bernstein@...>
+1
-Josh
On May 15, 2017, at 2:08 PM, Doug Davis via cncf-toc < cncf-toc@...> wrote:
toggle quoted message
Show 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
|
|
|
+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
|
|
|
toggle quoted message
Show 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
|
|
|
toggle quoted message
Show 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
|
|
|
Solomon Hykes <solomon.hykes@...>
toggle quoted message
Show 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
|
|
|
otto hillenbrand <otto@...>
toggle quoted message
Show 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
|
|
|
+1 (non binding)
From:
<cncf-toc-bounces@...> on behalf of Robert Lalonde via cncf-toc <cncf-toc@...>
Reply-To: Robert Lalonde <rlalonde@...>
Date: Monday, May 15, 2017 at 11:53 AM
To: Kenneth Owens <kenowens@...>
Cc: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] CNI project proposal (incubation)
+1 (non binding)
toggle quoted message
Show quoted text
On May 15, 2017, at 2:51 PM, Kenneth Owens (kenowens) via cncf-toc <cncf-toc@...> wrote:
|
|
|
|
|
|
|
|
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.
|
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
|
|
|
Think
before you print.
