Date

Attendees



Agenda

Minutes

  • Action Items
    • 5.1 release notes
      • getting worked on
    • Core committers/ PTLs
      • waiting on repo migration
  • 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 (smile)
    • 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 an OSS and commercial project based on same code
        • when versioning schemes are different it's hard on users since shared codebase isn't clear
    • prabhjot: from a community perspective, anyone who is evaluating the software is looking for feature sets not upgrade path
    • randy: the communities job is to make TF as successful as possible
      • if we look at TF users, they are carriers using contrail not TF
      • expecting to be able to map commercial to OSS
    • edward: how to vote?
    • prabhjot: how can we be consistent with the scheme?
    • bjskerry: can we do it here or do we need to send it to email
      • next week, let's have a concrete proposal
    • Will Stevens write initial proposal and get feedback form juniper people
  • Blueprints
    • Sukhdev Kapurstill trying to figure it out
    • prabhjot: short on technical discussions
      • mostly only DPDK and rebranding efforts
      • some juniper people are on the call but we need more people
    • sukhdev: will get some Mellanox folks on the call to talk about SmartNIC stuff
  • Rebranding
    • prabhjot: use blueprints and then implement changes
      • first phase: changing artifacts, rename to Tungsten
      • will propose changes and get feedback
  • Upcoming Talks
    • sukhdev: anyone else giving talks?
      • crickets 
      • talking at ONS EU
        • Tungsten Fabric and MobileEdgeX
      • KubeCon San Diego
        • networking and servicemesh with Frederick
      • OpenStack - Shanghai
        • proposed joint talk on Tungsten Fabric and StarlingX integration
        • proposed joint talk on Tungsten Fabric and OpenStack integration - using OVS/SRIOV workloads
          • will upload video to wiki
          • 13 min video
      • darien: can help with container based chaining services
      • sukhdev: join juniper folks at the TWS call with prabhjot
      • prabhjot: has submitted a similar talk to KubeCon
      • sukhdev: CSRX, containerized based file service
        • there is also a host based firewall being integrated into TF
        • will get docs/ info
      • will: sending some information to lists would be great to get interested parties involved
  • sukhdev: while at kubecon in china
    • there is desire to build chinese community
    • would love to see more community volunteering to build this effort
  • casey: the LFN has money set aside for meetups
    • can make an expense report to reimburse
    • a template exists to get reimbursed up to ~10$ a person up to 250$ an event
  • sukhdev: maybe edward could help
  • casey: bring this info to our marketing group but also the MAC
    • they can help with resources and languages issues

Action items

  • Will Stevenssend initial proposal to TSC list for a vote next week
  • Sukhdev Kapur add video to wiki (from Will: there's a button at the top to add content)
  • Sukhdev Kapur will get developer to come to a meeting and present