...
- Edward Ting
- @alex levine
- Prabhjot Singh Sethi
- Randy Bias
- Rudra Dubey
- Syed Ahmed
- Sukhdev Kapur
- Ian Rae
- Syed Ahmed
- Will Stevens
- Darien Hirotsu
- bjskerry
Agenda
- Start the Recording
- Antitrust Policy
- Agenda Bashing (Roll Call, Action Items (5 minutes)
- General Topics
- Talk with AT&T about their tests
- Roadmap? (Edward Ting)
- Blueprints to be discussed from Juniper side
- re-branding from contrail to tungsten
- Upcoming conferences and TF related talks
- ONS EU - Tungsten Fabric and MobileEdgeX talk is approved
- KubeCon NA - Submitted joint talk on Tungsten Fabric and Network Service Mesh integration
- OpenStack - Shanghai -
- Submitted joint talk on Tungsten Fabric and StarlingX integration
- Submitted joint talk on Tungsten Fabric and OpenStack integration - using OVS/SRIOV workloads
Minutes
- Action Items
- 5.1 release notes
- getting worked on
- Core committers/ PTLs
- waiting on repo migration
- 5.1 release notes
- AT&T Tests
- need to liaise with AT&T after Zuul setup is more stable
- some design differences will make it harder to integrate into existing tests
- there is communication on the PR
- Roadmap
- Releases changing to monthly, eg 1908 for August 2019
- still need to bring blueprints into community so we can align releases
- what is TF's schedule given we are a bit beholden to Juniper?
- stick to monthlies until we can cut proper releases?
- edward: which naming scheme should we use? ie, 1907 vs 5.x
- randy: stick with Juniper's scheme
- sort of locks us into monthly releasing convention
- need to explain why the version change
- bjskerry: shouldn't be too much of a learning curve
- will: 1908 doesn't mean we are forced into monthly releases
- refers more to when the release was cut
- rudra:
- randy: we are still leveraging junipers release schedule/ naming
- casey: we can diverge from juniper, just a decision for the tsc
- prabhjot: adopting the release versioning scheme is probably the best idea for the community
- we might not need to match the release cycle
- prabjot: we are pigging backing off of juniper
- will: we don't have to maintain the same cadence
- use same release but cut a release every other month
- when you have