...
- Casey Cain
- Ian Rae
- Edward Ting
- Alex Levine
- Chuck Piercey
- Daniel Pono Takamori
- Lisa Caywood
- Prabhjot Singh Sethi
- Rudra Dubey
- Syed Ahmed
- Frederick Kautz (from Network Service Mesh, aka NSM)
- Martin Mailand
- Will Stevens
Proxies
- Gleb Kholodov for Valentin Sinitsyn
...
- Start the Recording
- Antitrust Policy
- Agenda Bashing (Roll Call, Action Items (5 minutes)
- General Topics
- TF Deprecation Policy Review
- Network Service Mesh and TF collaboration - Guest Speaker (15-20 minutes) - added by Sukhdev Kapur , introduced by Will Stevens
- LFN Code of Conduct https://lfprojects.org/policies/code-of-conduct/
- Alex Levine: TF anonymous usage reporting client.
Questions for discussion:
...
https://review.opencontrail.org/#/c/52066
https://review.opencontrail.org/#/c/52077
https://github.com/progmaticlab/tf_stats_server
- Alex Levine: Point folks to the proposed CI changes for TF: TF CI Design and Improvements
- Who's running the Technical Workstream Call now that Joseph's on sabbatical?
- Randy: Dockerhub access (who should have it?) Docker Hub Account Management
- LF: ONS EU demo proposals, please! (see mailing list message)
- Abhijeet Singh: ATT Docs contributions
Daniel Pono Takamori: Update on CI/CDnoticed Alex's note above
Minutes
- Action items
- Convert 5.1 blog announcement to release notes: Darien Hirotsuwill take this over from VM (Vicky) Brasseur (she/her)
- Tabling the question of TPC IP address; will be handled otherwise
- Deferring all Sukhdev items (he's traveling)
- Frederick Kautz: Network Service Mesh + TF
- Has been speaking with Will & Sukhdev (started in KubeCon EU 2019)
- Presenting slides (will send to Casey to get attached to the minutes)
- Problems solved by NSW
- network service discovery & connection discovery
- controller of controllers (even across organizations)
- 3 primitives: client, network service, connection
- Consumers: Want to request a service (for instance, a pod in k8s)
- Operator gets to define what that service is
- Basic service function chaining but enforced by policy & defined in a declarative way
- CNF/VNF vendor gets to declare both the connection mechanism and payload; clear contract
- Apply concepts from L4-L7 to L2 & L3
- No need to define IPs, routes, subnets and the like since they're all negotiated as needed
- Can swap out the data plane easily as long as there's something that knows how to do the conversion
- Have a reference architecture based on VPP but looking to add different data planes
- Instantiation of the interface is when the interface is requested
- Could be during pod creation, or in middle of pod's lifecycle
- Can create on the fly
- Security?
- NSM is looking into a security path now by way of Spiffe and Spire
- Each connection has a cryptographically secured identity
- RLB: Security policy…? TF has good and flexible security policy handling (matches well in k8s world). Can TF add value to NSM here?
- Dynamically take an intent-based policy and apply to the dynamically-instantiated interface?
- NSM current is focusing on identity
- These policies don't live in the data plane
- NSM having no control over what goes over the wire
- TF could be valuable for this
- Would rely on TF (or whatever) to pull identity policies
- NSM is looking into a security path now by way of Spiffe and Spire
- Come see #nsm channel on slack.cncf.io
- Deprecation policy review
- Tungsten Fabric Deprecation Policy (DRAFT)
- When to deprecate APIs, features, or both
- Will move to the Docs repo once approved (Jira ticket for this: https://jira.tungsten.io/browse/TFB-1452)
- CoC
- FYI: LFN TAC is developing a Code of Conduct (CoC), instead reaffirmed existing LF CoC that applies to all projects
- https://lfprojects.org/policies/code-of-conduct/
- So please have a look. It applies to us.
- Usage reporting client
- Server that gets the stats from the container?
- Opt-in, anonymous usage reporting
- Can we get a server from LF?
- stats.tungsten.io
- Server that gets the stats from the container?
- TF CI design & improvements doc