Date

Attendees



Agenda

  • Start the Recording
  • Antitrust Policy
  • Agenda Bashing (Roll Call, Action Items (5 minutes)
  • General Topics
    • update VSPERF
    • update on using dpdk upstream
    • update on proposal for re-branding contrail to tungsten
    • future
      • upgrade/move between Contrail and Tungsten Fabric
      • CNI DPDK support vrouter
    • Demo Ideas for ONS Europe

Minutes

  • Action items
    • SK: Work w/Joseph on perf stuff…?
      • Joseph named a replacement, but need to invite this person to the Infra calls
    • SK: Blueprint process
      • Having a lot of discussions internally at Juniper
      • Goal to publish blueprints, but need more resources
      • Close to working with Pono to get workflow alignment
    • Darien: Server availability for vrouter standalone testing
      • Nothing readily available
      • Team working to get stuff available
      • Will send update by Thursday this week
  • VSPERF
    • No updates. PS has been trying to get responses from that team but none yet
      • Will follow up more
    • Blocking: using 2 versions of dpdk
      • But patch to use upstream has landed
    • Prabhjot will follow up with Randy & this group more when he has info
  • dpdk upstream
    • Patch merged to master
    • PS working on getting docs done
      • Will coordinate with Docs group on that
  • Code rebranding effort
    • contrail → tf
    • Looking to modify artefacts first, naming appropriately
    • Will have more info in TSC call on Thursday
  • Docs
    • If you're adding a feature, you're required to include docs
  • The future of TF
    • Move between TF & Contrail should be possible: How can the community help ensure this?
      • Should be able to migrate between TF & Contrail
    • Before that, need to bring the migration/upgrade process into the community branch
      • Should be possible, but hasn't been tested
      • For instance, no docs to migrate from TF 5.0 to 5.1
    • CNI dpdk support vrouter
      • Sukhdev spoke w/Anand Sunday evening. A is looking into jumping into this. SK has asked him to collaborate w/community
        • dpdk support for containers/pods
      • PS: Not only will get this into the community support, but also could help w/dpdk transition and perf improvement
      • PS will collaborate w/Anand
        • Anyone else who's interested should jump into the mailing list thread
  • PS will bring proposal document in next meeting (he hopes)
  • Sukhdev: Service chaining
    • Juniper customers are asking questions about this
      • This is already available for VMs
      • SK thinks it's also there for containers/pods
    • SK will have Contrail security expert join the meeting in August to talk about this stuff (as well as about Contrail security)
  • ONS EU demo ideas
    • Demo proposal deadline is July 31
    • PS suggests service chaining as an idea for TF
    • What other ideas?
      • jluk: Codilime giving a talk w/Magdalena about service chaining in cloud native; considering an LFN booth demo on this as well
        • Will share proposal here for collaboration
        • Working to integrate another LFN project; could use some brainstorming on this
      • SK: NSM demo?
        • Not a lot of time to coordinate w/NSM
        • VMB: Propose, please! Great idea. (Casey: +1!)
      • SK: Smart NIC?
        • Jan: Things still working through testing; nothing too new
        • SK: Would be good to show perf improvements
        • Jan: Will run it through internally & see what folks say
        • jluk: smartnic connections to pods?
          • Jan: Investigating this now. (smile)
          • Upstream k8s uses multus to switch between different providers
          • TF k8s driver works a bit differently
          • Good news is that plugin logic in openstack appears transferrable, but don't know…
            • Schedule workloads on k8s
            • Handle things efficiently
            • etc
          • At the very least, some of the plugin code needs to move into the CNI plugin
            • Connect virtual function into the pod
            • Would work the same (but implement slightly differently) in k8s & openstack
          • So nothing to demo here yet
  • DH: More info about 5.0 → 5.1 upgrades? What's ATS working on here?
    • Nothing in flight right now
    • Has been mentioned on TSC calls as a priority
    • Before migrating between TF & Contrail, need to be able to upgrade TF itself
    • SK: There are 2 or 3 upgrade procedures for Contrail
      • ISSU, etc
      • Don't think it's documented publicly, but may be on Juniper website
    • PS: Are deployment artefacts for Contrail public right now?
      • Would need access to these to test it
      • SK: Yes, this is available.
        • Upgrade procedure
        • Some containers are private (just the commercial stuff)
      • Commercial customers typically use RHOSP (RedHat upgrades it for them)
      • But procedures and containers should be the same for public & private consumption
    • DH: GSoC project is working on this
      • Upgrade from 5.0 to 5.1
      • Will be some documentation coming out of this

Action items

  •