TSC Meeting Zoom || TSC APAC Zoom || Meeting Recordings
TSC meetings are held weekly for one hour on Thursdays. Meeting time alternates each week. Standard: 9am Pacific and APAC: 10pm Pacific.
Attendees & Representation
TSC Members and Project representatives should mark their attendance below
X = Present | P = Proxy (Indicate below table with @name for @name
| TSC Members | |
|---|---|
Robert Varga Pantheon.tech | |
Manoj Chokka Verizon | x |
Venkatrangan Govindarajan Rakuten Symphony | x |
Guillaume Lambert Orange | |
Anil Belur Linux Foundation | x |
Ivan Hrasko Pantheon.tech | x |
Cedric Ollivier Orange | |
| Community Elected Roles: | |
Daniel De La Rosa (Release Manager) | x |
Staff: Casey Cain
Community: Peter Puškár Rohini Ambika @Sathya Manalan JN Naphade @Gokul Sakthivel Sangwook Ha
Agenda
- Start the Recording
- We will start by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.
- Agenda Bashing, Roll Call, Action Items (all, 9:00-9:05 am)
- Releases
- LFN Updates
- Marketing Update
- TSC Grievance Tracking
- General Topics
- Any Other Topics
Minutes
Release
- Sulfur SR1 is done, including documentation, thanks Ivan Hrasko for helping with downloads and release notes
- Sulfur SR2 checklist has been posted here but it will be updated once Robert Varga is back
- Chlorine is still in progress but still on schedule to be released on
LFN Updates
Marketing Update
General Topic
- Rohini Ambika and team from Infosys need clarification on cluster use-cases and configuration with K8s. They have 250 node types all using the same schema.
- They have a 4 node k8s cluster, with one master and three worker nodes.
- There are 3 ODL instances, each on one worker node.
- They have configured
- The recommendation was to re-test the use case without cluster setup.