Initial nsm sandbox project proposal. #1
Conversation
Signed-off-by: Ed Warnicke <[email protected]>
Signed-off-by: Ed Warnicke <[email protected]>
proposals/networkservicemesh.adoc
Outdated
| *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. |
There was a problem hiding this comment.
The last two sentences should be reworded.
There was a problem hiding this comment.
How about something like:
NSM removes the need for a developer to use legacy networking concepts like "subnet", "route", "interface", or "ipam." Instead, it adopts a cloud-native networking paradigm, allowing the developer to name the Network Service they want, apply metadata in the form of labels, and be simply connected to it.
There was a problem hiding this comment.
re: 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.
-
"cloud native" can be lowercase and non hyphenated, per CNCF style guide https://github.com/cncf/foundation/blob/master/style-guide.md
-
"by bringing acknowledging and working" could be reworded for clarity
-
infrastrcture s/b infrastructure
-
Can "Networking" be lowercase?
proposals/networkservicemesh.adoc
Outdated
| 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. |
There was a problem hiding this comment.
Insure is likely not the correct word here.
Signed-off-by: Ed Warnicke <[email protected]>
Signed-off-by: Ed Warnicke <[email protected]>
Signed-off-by: Ed Warnicke <[email protected]>
Signed-off-by: Ed Warnicke <[email protected]>
|
can you detail contributors and what orgs they come from? right now you only have 3 maintainers but I think your contribution diversity is much better than that |
Signed-off-by: Ed Warnicke <[email protected]>
|
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. italics section: looks like something got lost in the edit process here. "therefore adopted the approach of seeking to make" ? The rest of the changes we discussed in chat look good. |
proposals/networkservicemesh.adoc
Outdated
|
|
||
| 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. |
There was a problem hiding this comment.
Fixed in latest update.
proposals/networkservicemesh.adoc
Outdated
|
|
||
| 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. |
There was a problem hiding this comment.
s/Cloud-native/cloud native/
https://github.com/cncf/foundation/blob/master/style-guide.md
s/Kubernetes, but also be/Kubernetes but also to be/
s/VIMs Physical Netorks or Legacy Servers/VIMs, physical networks, or legacy servers/
There was a problem hiding this comment.
Fixed in latest update.
proposals/networkservicemesh.adoc
Outdated
|
|
||
| *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. |
There was a problem hiding this comment.
Fixed in latest update.
Signed-off-by: Ed Warnicke <[email protected]>
|
@edwarnicke can you add "Doc.ai" to the list of sponsors? |
Signed-off-by: Ed Warnicke <[email protected]>
|
@fkautz Done :) |
Signed-off-by: Ed Warnicke <[email protected]>
proposals/networkservicemesh.adoc
Outdated
| * 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: |
There was a problem hiding this comment.
proposals/networkservicemesh.adoc
Outdated
| * 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] |
proposals/networkservicemesh.adoc
Outdated
|
|
||
| *Website*: https://networkservicemesh.io/ | ||
|
|
||
| *Release Methodology and Mechanics*: |
There was a problem hiding this comment.
No official release yet. The plan is to have an initial 0.1.0 ready for KubeCon EU 2019. The current process is to decide on a particular release during the WG calls and managed through a project in the Guthub Issue tracker.
The agreed formal release process is described here: https://github.com/networkservicemesh/networkservicemesh/blob/master/docs/spec/release.md.
proposals/networkservicemesh.adoc
Outdated
| * Routes | ||
| * IPAM | ||
|
|
||
| *Sponsor / Advisor from TOC*: Matt Klein, Joe Beda |
There was a problem hiding this comment.
By first name or last :)
There was a problem hiding this comment.
You got me, it's the same order both cases.
| *Initial Committers*: | ||
| * Frederick Kautz (doc.ai) | ||
| * Ed Warnicke (Cisco) | ||
| * Nikolay Nikolaev (VMWare) |
There was a problem hiding this comment.
Again, shall we use alphabetic order?
There was a problem hiding this comment.
Lines 15 and 19: "cloud native" can be lower case per CNCF style guide
| * RedHat | ||
| * Bell Canada | ||
| * Orange | ||
| * doc.ai |
There was a problem hiding this comment.
Shall we order alphabetically here too?
There was a problem hiding this comment.
Sounds good :). Much easier with company names :)
Also added Use Case Subgroup. Signed-off-by: Ed Warnicke <[email protected]>
Signed-off-by: Ed Warnicke <[email protected]>
Signed-off-by: Ed Warnicke <[email protected]>
Signed-off-by: Ed Warnicke <[email protected]>
Signed-off-by: Ed Warnicke <[email protected]>
proposals/networkservicemesh.adoc
Outdated
|
|
||
| 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: |
There was a problem hiding this comment.
Drop "is" and just have "The Network Service Mesh model:"
proposals/networkservicemesh.adoc
Outdated
| * 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] |
There was a problem hiding this comment.
Line 71: KubeCon
Line 72: Network, KubeCon
| 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. | ||
|
|
There was a problem hiding this comment.
Network Service Mesh provides seamless Layer 2/3 interconnection for a variety of use cases across a single cloud or distributed clouds including infrastructure performance awareness for applications with stringent SLAs.
There was a problem hiding this comment.
Network Service Mesh provides seamless Layer 2/3 interconnection for a variety of use cases across a single cloud or link:https://docs.google.com/document/d/1kibZLSd4BVcnyaVH8hjOJCkELg3BptqIgyAGk7K0NXo/ [distributed clouds] including infrastructure performance awareness for applications with stringent SLAs.
Can we href the usecase doc to distributed clouds. This will help people to relate NSM with more usecases.
| * doc.ai | ||
| * Orange | ||
| * RedHat | ||
| * VMWare |
There was a problem hiding this comment.
@gpremsankar Can you +1 this to confirm?
| * Frederick Kautz (doc.ai) | ||
| * Nikolay Nikolaev (VMWare) | ||
| * Ed Warnicke (Cisco) | ||
|
|
There was a problem hiding this comment.
Initial Use Case Contributors:
- Ramki Krishnan (VMware)
- Prem Sankar Gopannan (Lumina Networks)
- Daniel Bernier (Bell Canada)
- Mathieu Rohon (Orange)
- Frederick Kautz (doc.ai)
- John Mcdowall (Palo Alto Networks)
There was a problem hiding this comment.
Sadly not a part of the template :(
|
|
||
| * 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] |
There was a problem hiding this comment.
- Use Case & Architecture Impact: https://docs.google.com/document/d/1kibZLSd4BVcnyaVH8hjOJCkELg3BptqIgyAGk7K0NXo/
|
|
||
| *Description* | ||
|
|
||
| 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. |
There was a problem hiding this comment.
Inspired by Istio and Knative, ...
Signed-off-by: Ed Warnicke <[email protected]>
Signed-off-by: Ed Warnicke <[email protected]>
|
Pushed to upstream here: cncf#212 |
Signed-off-by: Daniel Holbach <[email protected]>
Update 2020-telepresence-annual.md
Update 2021-telepresence-annual.md
Signed-off-by: Ed Warnicke [email protected]