Date

Attendees



Agenda

Minutes

  • Action items
    • ATT testing framework contributions
      • ps: ATT has provided tests for the TF testing framework
      • dp: Per Alex, Zulu isn't stable yet, so he suggested waiting a bit longer
      • ps: We should consider this though since this is a community contribution
    • Juniper will continue to work off of the forked DPDK branch
      • ps: Sukhdev worked this within Juniper to confirm
  • Blueprints / DPDK
    • ps: Recommendations
      • We created an epic in Jira for DPDK
      • Waiting on performance enhancements
      • Can someone help with the performance testing?
        • We don't have enough lab infrastructure
        • Can anyone contribute or offer help? (smile)
        • Need to run standalone DPDK tests
        • Any server should do as long as it supports DPDK and we can run TREX
      • This will help us get into the CNI space
      • Also, looking for some reasonable numbers on performance testing from others in the community
    • ps: The desire for DPDK is to depend on upstream rather than a Juniper fork
  • Rebranding
    • ps: lots of discussion and this will not be easy
      • A lot of code to update
      • ATS is supporting this in phases
        • Low hanging fruit first
          • Names of containers
          • Passwords
          • Labels
        • Make sure there is an OEM based way to support naming to enable vendors such as Juniper to build Contrail instead of Tungsten Fabric
          • Expect a blueprint on this
    • ar: Where are blueprints stored?
    • ps: Tungsten Fabric Jira
  • Open Items
    • dh: Is there a triage workflow for TF bugs in Jira
    • pono: not yet
    • cc: who is the expert on Launchpad CLAs?
    • ps: it's a gerrit process today largely managed manually

Action items