From cfec693f0a797e11c816d77bd6b4949248e3f265 Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Thu, 28 Feb 2019 14:34:24 -0600 Subject: [PATCH 01/17] Initial nsm sandbox project proposal. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 70 +++++++++++++++++++++++++++++++ 1 file changed, 70 insertions(+) create mode 100644 proposals/networkservicemesh.adoc diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc new file mode 100644 index 000000000..e555b2d15 --- /dev/null +++ b/proposals/networkservicemesh.adoc @@ -0,0 +1,70 @@ +== Network Service Mesh Proposal + +*Name of project:* Network Service Mesh + +*Description* + +Network Service Mesh is a novel approach solving complicated L2/L3 use cases in Kubernetes that are tricky to address with the existing Kubernetes Network Model. Inspired by Istio, Network Service Mesh maps the concept of a service mesh to L2/L3 payloads. + +Network Service Mesh recognizes and respects that the existing K8s Networking provides excellent service for the common developer use cases, and has therefore adopted an orthogonal approach to the CNI that currently provides K8s Networking, leaving that path completely unaltered. +It requires no changes of any kind to the CNI plugin being used, or to Kubernetes itself to function. It runs as an additional layer of infrastructure on top of stock out of the box K8s. + +When Network Service Mesh is installed on a K8s cluster, a developer can simply specify in an annotation on their Pod the name of the Network Service they want, like "secure-intranet-connectivity" and Network Service Mesh will insure that is available to their Pods (not to the cluster as a whole) in addition to the standard K8s Networking provided by their CNI and in a manner that is completely non-conflicting with it. + +While much of the work being done in Network Service Mesh is focused on K8s support, it is designed to not be welded to K8s. It has been architected to also bring its benefits to other environments, like VIMs, Physical Networks, or Legacy Servers. + +*Statement on alignment with CNCF mission*: + +Network Service Mesh is designed to allow any L2/L3 Network Service a workload may want to be dynamically available to it. It is seeking to make networking itself Cloud-native by bringing acknowledging and working with the existing immutable infrastrcture in K8s to loosely couple whatever non-standard Networking needs a workload has with minimal toil. +It adopts a networking paradigm of allowing the developer to name the Network Service they want, apply metadata in the form of labels, and be simply connected to it. It forcing the 35 year old legacy networking concepts like "subnet", "route", "interface", or "ipam" on the developer. Those have no place in a Cloud-native world. + +*Sponsor / Advisor from TOC*: + +*Unique identifier:* networkservicemesh + +*Prefered Maturity Level*: Sandbox + +*License*: Apache License v2.0 + +*Source control repositories*: link:https://github.com/networkservicemesh[GitHub] + +*Initial Committers*: +* Frederick Kautz (doc.ai) +* Ed Warnicke (Cisco) +* Nikolay Nikolaev (VMWare) + +*Infrastructure requirements (CI / CNCF Cluster)*: CI (currently use CircleCI), Packet/GKE/AKS/EKS/etc time for system tests + +*Communication Channels*: + +* Mailing List: https://groups.google.com/forum/#!forum/networkservicemesh +* IRC: #networkservicemesh on Freenode +* Weekly Meetings: + * link:https://docs.google.com/document/d/1C9NKjo0PWNWypROEO9-Y6haw5h9Xmurvl14SXpciz2Y/edit#heading=h.rc9df0a6n3ng[Main Meeting] + * link:https://docs.google.com/document/d/1113nzdL-DcDAWT3963IsS9LeekgXLTgGebxPO7ZnJaA/edit#heading=h.8t1wzcxy1me6[Documentation subgroup meeting] + * Use case subgroup meeting: + +*Issue Tracker*: link:https://github.com/networkservicemesh/networkservicemesh/issues[Github Issues] + +*Website*: https://networkservicemesh.io/ + +*Release Methodology and Mechanics*: + +*Social Media Accounts*: + * link:https://www.linkedin.com/company/networkservicemesh[LinkedIn] + * link:https://twitter.com/nservicemesh[Twitter] + +*Community size and existing sponsorship*: +* Github Stars: 111 +* Github Forks: 38 +* Code Contributors: 18 +* Usual meeting census: ~20 +* Youtube views of Weekly meetings: link:https://www.youtube.com/results?search_query=network+service+mesh+wg+2019[More than 100 typically] +* Youtube views of Network Service Mesh Intro talk at Kubecon NA 2019: link:https://www.youtube.com/watch?v=YeAKtUFaqQ0&t=2s[More than 1300] +* Existing Sponsors: + * Cisco + * VMWare + +*Other Reference Material*: +* Network Service Mesh Intro (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1Vzmhv5vc10NyAa08ny-CCbveo0_fWkDckbkCD_N0fPg/edit[Slides] (link:https://www.youtube.com/watch?v=YeAKtUFaqQ0[Video]) +* Netowrk Service Mesh Deep Dive (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1YWagIAT3hCqF8zZ3wpC6woZ038Y42lKpXv12kjKZC6Q/edit#slide=id.g49d60c8d41_2_46[Slides] (link:https://www.youtube.com/watch?v=SGi9LS870rk[Video]) \ No newline at end of file From 84acae535fd90ebcc194320869356f963859bd83 Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Thu, 28 Feb 2019 15:01:14 -0600 Subject: [PATCH 02/17] Adding Sponsors Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index e555b2d15..da5ab9a63 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -64,6 +64,8 @@ It adopts a networking paradigm of allowing the developer to name the Network Se * Existing Sponsors: * Cisco * VMWare + * Bell Canada + * Orange *Other Reference Material*: * Network Service Mesh Intro (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1Vzmhv5vc10NyAa08ny-CCbveo0_fWkDckbkCD_N0fPg/edit[Slides] (link:https://www.youtube.com/watch?v=YeAKtUFaqQ0[Video]) From 9d973fbde0b2628a670a58f7b2ccb005e528fd6c Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Thu, 28 Feb 2019 16:02:01 -0600 Subject: [PATCH 03/17] Update in response to comments. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index da5ab9a63..889b60949 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -9,14 +9,24 @@ Network Service Mesh is a novel approach solving complicated L2/L3 use cases in Network Service Mesh recognizes and respects that the existing K8s Networking provides excellent service for the common developer use cases, and has therefore adopted an orthogonal approach to the CNI that currently provides K8s Networking, leaving that path completely unaltered. It requires no changes of any kind to the CNI plugin being used, or to Kubernetes itself to function. It runs as an additional layer of infrastructure on top of stock out of the box K8s. -When Network Service Mesh is installed on a K8s cluster, a developer can simply specify in an annotation on their Pod the name of the Network Service they want, like "secure-intranet-connectivity" and Network Service Mesh will insure that is available to their Pods (not to the cluster as a whole) in addition to the standard K8s Networking provided by their CNI and in a manner that is completely non-conflicting with it. +When Network Service Mesh is installed on a K8s cluster, a developer can simply specify in an annotation on their Pod the name of the Network Service they want, like "secure-intranet-connectivity" and Network Service Mesh will ensure that is available to their Pods (not to the cluster as a whole) in addition to the standard K8s Networking provided by their CNI and in a manner that is completely non-conflicting with it. While much of the work being done in Network Service Mesh is focused on K8s support, it is designed to not be welded to K8s. It has been architected to also bring its benefits to other environments, like VIMs, Physical Networks, or Legacy Servers. *Statement on alignment with CNCF mission*: Network Service Mesh is designed to allow any L2/L3 Network Service a workload may want to be dynamically available to it. It is seeking to make networking itself Cloud-native by bringing acknowledging and working with the existing immutable infrastrcture in K8s to loosely couple whatever non-standard Networking needs a workload has with minimal toil. -It adopts a networking paradigm of allowing the developer to name the Network Service they want, apply metadata in the form of labels, and be simply connected to it. It forcing the 35 year old legacy networking concepts like "subnet", "route", "interface", or "ipam" on the developer. Those have no place in a Cloud-native world. + +The Network Service Mesh model is: +* Developers ask for what Network Service they want by name +* Developers can add metadata to their request for a Network Service with labels. +* Developers simply get the Network Service they asked for + +Developers never have to know or think about 35 year old legacy Networking concepts like: +* Subnets +* Interfaces +* Routes +* IPAM *Sponsor / Advisor from TOC*: From 84f32d0ea37ef1d1ed29fd8e9a873e81500b3fa1 Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Thu, 28 Feb 2019 16:46:34 -0600 Subject: [PATCH 04/17] Added sponsors. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index 889b60949..5cf692ee6 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -74,6 +74,7 @@ Developers never have to know or think about 35 year old legacy Networking conce * Existing Sponsors: * Cisco * VMWare + * RedHat * Bell Canada * Orange From f899c45e607eba22b152bfeacaf7f9ee33017b6e Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Fri, 1 Mar 2019 14:01:43 -0600 Subject: [PATCH 05/17] Update wording about working beyond just K8s in response to comments. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index 5cf692ee6..4770fd1fb 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -11,7 +11,7 @@ It requires no changes of any kind to the CNI plugin being used, or to Kubernete When Network Service Mesh is installed on a K8s cluster, a developer can simply specify in an annotation on their Pod the name of the Network Service they want, like "secure-intranet-connectivity" and Network Service Mesh will ensure that is available to their Pods (not to the cluster as a whole) in addition to the standard K8s Networking provided by their CNI and in a manner that is completely non-conflicting with it. -While much of the work being done in Network Service Mesh is focused on K8s support, it is designed to not be welded to K8s. It has been architected to also bring its benefits to other environments, like VIMs, Physical Networks, or Legacy Servers. +Network Service Mesh takes a true Cloud-native approach to the problem space, maintaining loose coupling to the underlying Infra structure it uses. This allows it to fit naturally into K8s, but also be used in other environments like VIMs Physical Netorks or Legacy Servers. *Statement on alignment with CNCF mission*: From 08005c9bc9cfb74565066d063c357c05a667c4b8 Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Fri, 1 Mar 2019 14:06:01 -0600 Subject: [PATCH 06/17] Reworking statment on alignment with CNCF mission. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index 4770fd1fb..cc31ccc71 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -15,7 +15,7 @@ Network Service Mesh takes a true Cloud-native approach to the problem space, ma *Statement on alignment with CNCF mission*: -Network Service Mesh is designed to allow any L2/L3 Network Service a workload may want to be dynamically available to it. It is seeking to make networking itself Cloud-native by bringing acknowledging and working with the existing immutable infrastrcture in K8s to loosely couple whatever non-standard Networking needs a workload has with minimal toil. +Network Service Mesh is designed a workload to dynamically request at any point in its lifecycle the L2/L3 Network Service it needs. It makes networking itself Cloud-native by loosely coupling with the existing immutable infrastrcture in K8s to deliver whatever non-standard Networking needs a workload has with minimal toil. The Network Service Mesh model is: * Developers ask for what Network Service they want by name From 21c1881505a4fc79a7a918225b715686a8d1976b Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Mon, 4 Mar 2019 08:48:12 -0600 Subject: [PATCH 07/17] Rewording in response to comments. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index cc31ccc71..1c7e42d99 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -4,14 +4,15 @@ *Description* -Network Service Mesh is a novel approach solving complicated L2/L3 use cases in Kubernetes that are tricky to address with the existing Kubernetes Network Model. Inspired by Istio, Network Service Mesh maps the concept of a service mesh to L2/L3 payloads. +Network Service Mesh is a novel approach to solving complicated L2/L3 use cases in Kubernetes that are difficult or impossible to address with the existing Kubernetes Network Model. Inspired by Istio, Network Service Mesh maps the concept of a service mesh to L2/L3 payloads. -Network Service Mesh recognizes and respects that the existing K8s Networking provides excellent service for the common developer use cases, and has therefore adopted an orthogonal approach to the CNI that currently provides K8s Networking, leaving that path completely unaltered. -It requires no changes of any kind to the CNI plugin being used, or to Kubernetes itself to function. It runs as an additional layer of infrastructure on top of stock out of the box K8s. +Network Service Mesh recognizes and respects that the existing Kubernetes Networking provides excellent service for common developer use cases, and has therefore adopted an approach It seeks to make networking itself cloud-native by bringing, acknowledging to the CNI currently providing Kubernetes Networking, leaving that path completely unaltered. -When Network Service Mesh is installed on a K8s cluster, a developer can simply specify in an annotation on their Pod the name of the Network Service they want, like "secure-intranet-connectivity" and Network Service Mesh will ensure that is available to their Pods (not to the cluster as a whole) in addition to the standard K8s Networking provided by their CNI and in a manner that is completely non-conflicting with it. +Network Service Mesh requires no changes to the CNI plugin being used, or to Kubernetes itself to function. It runs as an additional layer of infrastructure on top of stock out of the box Kubernetes. -Network Service Mesh takes a true Cloud-native approach to the problem space, maintaining loose coupling to the underlying Infra structure it uses. This allows it to fit naturally into K8s, but also be used in other environments like VIMs Physical Netorks or Legacy Servers. +When Network Service Mesh is installed on a K8s cluster, a developer can simply specify in an annotation on their Pod the name of the Network Service they want, such as "secure-intranet-connectivity". Network Service Mesh will ensure that Network Service is available to their Pods (not to the cluster as a whole). Standard Kubernetes Networking is provided by their CNI. Network Service Mesh stakes care to insure that it is completely non-conflicting with Kubernetes Networking. + +Network Service Mesh takes a true Cloud-native approach to the problem space, maintaining loose coupling to the underlying Infrastructure it utilizes. This allows it to fit naturally into Kubernetes, but also be used in other environments like VIMs Physical Netorks or Legacy Servers. *Statement on alignment with CNCF mission*: From 7ca034d972219e41dc4bf31d25497d5d831341c8 Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Mon, 4 Mar 2019 12:52:26 -0600 Subject: [PATCH 08/17] Updated in response to comments. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index 1c7e42d99..379c1b192 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -6,17 +6,17 @@ Network Service Mesh is a novel approach to solving complicated L2/L3 use cases in Kubernetes that are difficult or impossible to address with the existing Kubernetes Network Model. Inspired by Istio, Network Service Mesh maps the concept of a service mesh to L2/L3 payloads. -Network Service Mesh recognizes and respects that the existing Kubernetes Networking provides excellent service for common developer use cases, and has therefore adopted an approach It seeks to make networking itself cloud-native by bringing, acknowledging to the CNI currently providing Kubernetes Networking, leaving that path completely unaltered. +Network Service Mesh recognizes and respects that the existing Kubernetes Networking provides excellent service for common developer use cases. Network Service Mesh requires no changes to the CNI plugin being used, or to Kubernetes itself to function. It runs as an additional layer of infrastructure on top of stock out of the box Kubernetes. -When Network Service Mesh is installed on a K8s cluster, a developer can simply specify in an annotation on their Pod the name of the Network Service they want, such as "secure-intranet-connectivity". Network Service Mesh will ensure that Network Service is available to their Pods (not to the cluster as a whole). Standard Kubernetes Networking is provided by their CNI. Network Service Mesh stakes care to insure that it is completely non-conflicting with Kubernetes Networking. +When Network Service Mesh is installed on a K8s cluster, a developer can simply specify in an annotation on their Pod the name of the Network Service they want, such as "secure-intranet-connectivity". Network Service Mesh will ensure that Network Service is available to their Pods (not to the cluster as a whole) without using CNI. Standard Kubernetes Networking is still provided by CNI. Network Service Mesh takes care to insure that it is completely non-conflicting with Kubernetes Networking. -Network Service Mesh takes a true Cloud-native approach to the problem space, maintaining loose coupling to the underlying Infrastructure it utilizes. This allows it to fit naturally into Kubernetes, but also be used in other environments like VIMs Physical Netorks or Legacy Servers. +Network Service Mesh takes a true Cloud native approach to the problem space, maintaining loose coupling to the underlying Infrastructure it utilizes. This allows it to fit naturally into Kubernetes and also be used in other environments like VIMs, Physical Netorks, or Legacy Servers. *Statement on alignment with CNCF mission*: -Network Service Mesh is designed a workload to dynamically request at any point in its lifecycle the L2/L3 Network Service it needs. It makes networking itself Cloud-native by loosely coupling with the existing immutable infrastrcture in K8s to deliver whatever non-standard Networking needs a workload has with minimal toil. +Network Service Mesh is designed to allow a workload to dynamically request at any point in its lifecycle the L2/L3 Network Service it needs. It makes networking itself Cloud native by loosely coupling with the existing immutable infrastrcture in K8s to deliver whatever non-standard Networking needs a workload has with minimal toil. The Network Service Mesh model is: * Developers ask for what Network Service they want by name From e7d2f6562cf40caf765eca3f4c7f603361e1cc2d Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Tue, 5 Mar 2019 09:33:57 -0600 Subject: [PATCH 09/17] Added doc.ai to list of Sponsors Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index 379c1b192..33ee4549d 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -78,6 +78,7 @@ Developers never have to know or think about 35 year old legacy Networking conce * RedHat * Bell Canada * Orange + * doc.ai *Other Reference Material*: * Network Service Mesh Intro (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1Vzmhv5vc10NyAa08ny-CCbveo0_fWkDckbkCD_N0fPg/edit[Slides] (link:https://www.youtube.com/watch?v=YeAKtUFaqQ0[Video]) From 73866f9fb0972db353345496d915e19a0781b3da Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Wed, 13 Mar 2019 06:33:53 -0700 Subject: [PATCH 10/17] Added TOC Sponsors. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index 33ee4549d..facf449f1 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -29,7 +29,7 @@ Developers never have to know or think about 35 year old legacy Networking conce * Routes * IPAM -*Sponsor / Advisor from TOC*: +*Sponsor / Advisor from TOC*: Matt Klein, Joe Beda *Unique identifier:* networkservicemesh From a944974a100d6936e1a1ee2ef784b56621ad6e96 Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Thu, 14 Mar 2019 11:00:21 -0700 Subject: [PATCH 11/17] Incorporated feedback on Release Methodology, alphabetical ordering. Also added Use Case Subgroup. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index facf449f1..b4d6fea1b 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -51,15 +51,15 @@ Developers never have to know or think about 35 year old legacy Networking conce * Mailing List: https://groups.google.com/forum/#!forum/networkservicemesh * IRC: #networkservicemesh on Freenode * Weekly Meetings: - * link:https://docs.google.com/document/d/1C9NKjo0PWNWypROEO9-Y6haw5h9Xmurvl14SXpciz2Y/edit#heading=h.rc9df0a6n3ng[Main Meeting] - * link:https://docs.google.com/document/d/1113nzdL-DcDAWT3963IsS9LeekgXLTgGebxPO7ZnJaA/edit#heading=h.8t1wzcxy1me6[Documentation subgroup meeting] - * Use case subgroup meeting: + * link:https://docs.google.com/document/d/1C9NKjo0PWNWypROEO9-Y6haw5h9Xmurvl14SXpciz2Y/edit[Main Meeting] + * link:https://docs.google.com/document/d/1113nzdL-DcDAWT3963IsS9LeekgXLTgGebxPO7ZnJaA/edit[Documentation subgroup meeting] + * link:https://docs.google.com/document/d/1L6kwLW6yvj1EfUgDbdurCpgw2qWrX3ZJJ8Vh3FRqrOo/edit[Use Case subgroup meeting] *Issue Tracker*: link:https://github.com/networkservicemesh/networkservicemesh/issues[Github Issues] *Website*: https://networkservicemesh.io/ -*Release Methodology and Mechanics*: +*Release Methodology and Mechanics*: link:https://github.com/networkservicemesh/networkservicemesh/blob/master/docs/spec/release.md[Release Mechanics Defined in Github] *Social Media Accounts*: * link:https://www.linkedin.com/company/networkservicemesh[LinkedIn] @@ -71,14 +71,14 @@ Developers never have to know or think about 35 year old legacy Networking conce * Code Contributors: 18 * Usual meeting census: ~20 * Youtube views of Weekly meetings: link:https://www.youtube.com/results?search_query=network+service+mesh+wg+2019[More than 100 typically] -* Youtube views of Network Service Mesh Intro talk at Kubecon NA 2019: link:https://www.youtube.com/watch?v=YeAKtUFaqQ0&t=2s[More than 1300] +* Youtube views of Network Service Mesh Intro talk at Kubecon NA 2018: link:https://www.youtube.com/watch?v=YeAKtUFaqQ0&t=2s[More than 1400] * Existing Sponsors: - * Cisco - * VMWare - * RedHat * Bell Canada - * Orange + * Cisco * doc.ai + * Orange + * RedHat + * VMWare *Other Reference Material*: * Network Service Mesh Intro (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1Vzmhv5vc10NyAa08ny-CCbveo0_fWkDckbkCD_N0fPg/edit[Slides] (link:https://www.youtube.com/watch?v=YeAKtUFaqQ0[Video]) From 0aa6d9f9c0c204bb6e8ad48499767acbffbc1f57 Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Mon, 18 Mar 2019 18:01:32 -0500 Subject: [PATCH 12/17] Add link to slides for TOC. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index b4d6fea1b..4473c4b44 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -82,4 +82,5 @@ Developers never have to know or think about 35 year old legacy Networking conce *Other Reference Material*: * Network Service Mesh Intro (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1Vzmhv5vc10NyAa08ny-CCbveo0_fWkDckbkCD_N0fPg/edit[Slides] (link:https://www.youtube.com/watch?v=YeAKtUFaqQ0[Video]) -* Netowrk Service Mesh Deep Dive (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1YWagIAT3hCqF8zZ3wpC6woZ038Y42lKpXv12kjKZC6Q/edit#slide=id.g49d60c8d41_2_46[Slides] (link:https://www.youtube.com/watch?v=SGi9LS870rk[Video]) \ No newline at end of file +* Netowrk Service Mesh Deep Dive (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1YWagIAT3hCqF8zZ3wpC6woZ038Y42lKpXv12kjKZC6Q/edit#slide=id.g49d60c8d41_2_46[Slides] (link:https://www.youtube.com/watch?v=SGi9LS870rk[Video]) +* link:https://docs.google.com/presentation/d/18OrkofcPZnyBIRlPSSZV1gG8cY8kjYHsoN1mDlRu2Ro[Network Service Mesh Slide for Presentation to TOC] \ No newline at end of file From a47bf98d31c7f35d68e25123d90442a003be8c76 Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Mon, 18 Mar 2019 18:02:31 -0500 Subject: [PATCH 13/17] Alphabetized names in lists by last name. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index 4473c4b44..a162ee090 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -29,7 +29,7 @@ Developers never have to know or think about 35 year old legacy Networking conce * Routes * IPAM -*Sponsor / Advisor from TOC*: Matt Klein, Joe Beda +*Sponsor / Advisor from TOC*: Joe Beda, Matt Klein *Unique identifier:* networkservicemesh @@ -41,8 +41,8 @@ Developers never have to know or think about 35 year old legacy Networking conce *Initial Committers*: * Frederick Kautz (doc.ai) -* Ed Warnicke (Cisco) * Nikolay Nikolaev (VMWare) +* Ed Warnicke (Cisco) *Infrastructure requirements (CI / CNCF Cluster)*: CI (currently use CircleCI), Packet/GKE/AKS/EKS/etc time for system tests From 26079d96e3d483d694f5ead1a2aca27b3752930c Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Mon, 18 Mar 2019 18:08:52 -0500 Subject: [PATCH 14/17] Fix formatting for ascidoc. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index a162ee090..af758941e 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -19,11 +19,13 @@ Network Service Mesh takes a true Cloud native approach to the problem space, ma Network Service Mesh is designed to allow a workload to dynamically request at any point in its lifecycle the L2/L3 Network Service it needs. It makes networking itself Cloud native by loosely coupling with the existing immutable infrastrcture in K8s to deliver whatever non-standard Networking needs a workload has with minimal toil. The Network Service Mesh model is: + * Developers ask for what Network Service they want by name * Developers can add metadata to their request for a Network Service with labels. * Developers simply get the Network Service they asked for Developers never have to know or think about 35 year old legacy Networking concepts like: + * Subnets * Interfaces * Routes @@ -40,6 +42,7 @@ Developers never have to know or think about 35 year old legacy Networking conce *Source control repositories*: link:https://github.com/networkservicemesh[GitHub] *Initial Committers*: + * Frederick Kautz (doc.ai) * Nikolay Nikolaev (VMWare) * Ed Warnicke (Cisco) @@ -51,9 +54,9 @@ Developers never have to know or think about 35 year old legacy Networking conce * Mailing List: https://groups.google.com/forum/#!forum/networkservicemesh * IRC: #networkservicemesh on Freenode * Weekly Meetings: - * link:https://docs.google.com/document/d/1C9NKjo0PWNWypROEO9-Y6haw5h9Xmurvl14SXpciz2Y/edit[Main Meeting] - * link:https://docs.google.com/document/d/1113nzdL-DcDAWT3963IsS9LeekgXLTgGebxPO7ZnJaA/edit[Documentation subgroup meeting] - * link:https://docs.google.com/document/d/1L6kwLW6yvj1EfUgDbdurCpgw2qWrX3ZJJ8Vh3FRqrOo/edit[Use Case subgroup meeting] + - link:https://docs.google.com/document/d/1C9NKjo0PWNWypROEO9-Y6haw5h9Xmurvl14SXpciz2Y/edit[Main Meeting] + - link:https://docs.google.com/document/d/1113nzdL-DcDAWT3963IsS9LeekgXLTgGebxPO7ZnJaA/edit[Documentation subgroup meeting] + - link:https://docs.google.com/document/d/1L6kwLW6yvj1EfUgDbdurCpgw2qWrX3ZJJ8Vh3FRqrOo/edit[Use Case subgroup meeting] *Issue Tracker*: link:https://github.com/networkservicemesh/networkservicemesh/issues[Github Issues] @@ -62,10 +65,12 @@ Developers never have to know or think about 35 year old legacy Networking conce *Release Methodology and Mechanics*: link:https://github.com/networkservicemesh/networkservicemesh/blob/master/docs/spec/release.md[Release Mechanics Defined in Github] *Social Media Accounts*: + * link:https://www.linkedin.com/company/networkservicemesh[LinkedIn] * link:https://twitter.com/nservicemesh[Twitter] *Community size and existing sponsorship*: + * Github Stars: 111 * Github Forks: 38 * Code Contributors: 18 @@ -81,6 +86,7 @@ Developers never have to know or think about 35 year old legacy Networking conce * VMWare *Other Reference Material*: + * Network Service Mesh Intro (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1Vzmhv5vc10NyAa08ny-CCbveo0_fWkDckbkCD_N0fPg/edit[Slides] (link:https://www.youtube.com/watch?v=YeAKtUFaqQ0[Video]) * Netowrk Service Mesh Deep Dive (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1YWagIAT3hCqF8zZ3wpC6woZ038Y42lKpXv12kjKZC6Q/edit#slide=id.g49d60c8d41_2_46[Slides] (link:https://www.youtube.com/watch?v=SGi9LS870rk[Video]) * link:https://docs.google.com/presentation/d/18OrkofcPZnyBIRlPSSZV1gG8cY8kjYHsoN1mDlRu2Ro[Network Service Mesh Slide for Presentation to TOC] \ No newline at end of file From 90181087afd56f2d39256ff1f61e0d6e385fa595 Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Mon, 18 Mar 2019 18:11:16 -0500 Subject: [PATCH 15/17] More formating fixes. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index af758941e..09a7d8151 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -47,7 +47,10 @@ Developers never have to know or think about 35 year old legacy Networking conce * Nikolay Nikolaev (VMWare) * Ed Warnicke (Cisco) -*Infrastructure requirements (CI / CNCF Cluster)*: CI (currently use CircleCI), Packet/GKE/AKS/EKS/etc time for system tests +*Infrastructure requirements (CI / CNCF Cluster)*: + +* CI (currently use CircleCI) +* Packet/GKE/AKS/EKS/etc time for system tests *Communication Channels*: From 93d25eb17ca0c47dac0850cf1be74088f426694e Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Wed, 20 Mar 2019 06:51:25 -0500 Subject: [PATCH 16/17] Updated in response to comments from community. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index 09a7d8151..e1febc9dc 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -18,7 +18,7 @@ Network Service Mesh takes a true Cloud native approach to the problem space, ma Network Service Mesh is designed to allow a workload to dynamically request at any point in its lifecycle the L2/L3 Network Service it needs. It makes networking itself Cloud native by loosely coupling with the existing immutable infrastrcture in K8s to deliver whatever non-standard Networking needs a workload has with minimal toil. -The Network Service Mesh model is: +The Network Service Mesh model: * Developers ask for what Network Service they want by name * Developers can add metadata to their request for a Network Service with labels. @@ -74,12 +74,12 @@ Developers never have to know or think about 35 year old legacy Networking conce *Community size and existing sponsorship*: -* Github Stars: 111 -* Github Forks: 38 +* Github Stars: 127 +* Github Forks: 42 * Code Contributors: 18 * Usual meeting census: ~20 * Youtube views of Weekly meetings: link:https://www.youtube.com/results?search_query=network+service+mesh+wg+2019[More than 100 typically] -* Youtube views of Network Service Mesh Intro talk at Kubecon NA 2018: link:https://www.youtube.com/watch?v=YeAKtUFaqQ0&t=2s[More than 1400] +* Youtube views of Network Service Mesh Intro talk at KubeCon NA 2018: link:https://www.youtube.com/watch?v=YeAKtUFaqQ0&t=2s[More than 1400] * Existing Sponsors: * Bell Canada * Cisco @@ -90,6 +90,6 @@ Developers never have to know or think about 35 year old legacy Networking conce *Other Reference Material*: -* Network Service Mesh Intro (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1Vzmhv5vc10NyAa08ny-CCbveo0_fWkDckbkCD_N0fPg/edit[Slides] (link:https://www.youtube.com/watch?v=YeAKtUFaqQ0[Video]) -* Netowrk Service Mesh Deep Dive (from Kubecon NA 2018) link:https://docs.google.com/presentation/d/1YWagIAT3hCqF8zZ3wpC6woZ038Y42lKpXv12kjKZC6Q/edit#slide=id.g49d60c8d41_2_46[Slides] (link:https://www.youtube.com/watch?v=SGi9LS870rk[Video]) +* Network Service Mesh Intro (from KubeCon NA 2018) link:https://docs.google.com/presentation/d/1Vzmhv5vc10NyAa08ny-CCbveo0_fWkDckbkCD_N0fPg/edit[Slides] (link:https://www.youtube.com/watch?v=YeAKtUFaqQ0[Video]) +* Netowrk Service Mesh Deep Dive (from KubeCon NA 2018) link:https://docs.google.com/presentation/d/1YWagIAT3hCqF8zZ3wpC6woZ038Y42lKpXv12kjKZC6Q/edit#slide=id.g49d60c8d41_2_46[Slides] (link:https://www.youtube.com/watch?v=SGi9LS870rk[Video]) * link:https://docs.google.com/presentation/d/18OrkofcPZnyBIRlPSSZV1gG8cY8kjYHsoN1mDlRu2Ro[Network Service Mesh Slide for Presentation to TOC] \ No newline at end of file From 33a6d062ea42670bb608f142fd491298c8297d9a Mon Sep 17 00:00:00 2001 From: Ed Warnicke Date: Wed, 20 Mar 2019 10:24:05 -0500 Subject: [PATCH 17/17] Fixed typo pointed out in comments. Signed-off-by: Ed Warnicke --- proposals/networkservicemesh.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/networkservicemesh.adoc b/proposals/networkservicemesh.adoc index e1febc9dc..2f85dafbb 100644 --- a/proposals/networkservicemesh.adoc +++ b/proposals/networkservicemesh.adoc @@ -91,5 +91,5 @@ Developers never have to know or think about 35 year old legacy Networking conce *Other Reference Material*: * Network Service Mesh Intro (from KubeCon NA 2018) link:https://docs.google.com/presentation/d/1Vzmhv5vc10NyAa08ny-CCbveo0_fWkDckbkCD_N0fPg/edit[Slides] (link:https://www.youtube.com/watch?v=YeAKtUFaqQ0[Video]) -* Netowrk Service Mesh Deep Dive (from KubeCon NA 2018) link:https://docs.google.com/presentation/d/1YWagIAT3hCqF8zZ3wpC6woZ038Y42lKpXv12kjKZC6Q/edit#slide=id.g49d60c8d41_2_46[Slides] (link:https://www.youtube.com/watch?v=SGi9LS870rk[Video]) +* Network Service Mesh Deep Dive (from KubeCon NA 2018) link:https://docs.google.com/presentation/d/1YWagIAT3hCqF8zZ3wpC6woZ038Y42lKpXv12kjKZC6Q/edit#slide=id.g49d60c8d41_2_46[Slides] (link:https://www.youtube.com/watch?v=SGi9LS870rk[Video]) * link:https://docs.google.com/presentation/d/18OrkofcPZnyBIRlPSSZV1gG8cY8kjYHsoN1mDlRu2Ro[Network Service Mesh Slide for Presentation to TOC] \ No newline at end of file