Versions Compared

Old Version 17

changes.mady.by.user Randy Bias

Saved on

compared with

New Version Current

changes.mady.by.user Casey Cain

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

Attendees


Agenda

  • Start the Recording
  • Antitrust Policy
  • Agenda Bashing (Roll Call, Action Items (5 minutes)
  • vsPerf from Sridhar
  • Release 5.1 (Prabhjot)
    • we have a successful build for 5.1 release using juniper provided v5.1 tag for repos
    • Sukhdev to share information on tag scheme for v5.1, as i don't see it following a uniform pattern, for example contrail-controller have fixes till May 7th, but somehow contrail-common is skipping a memory leak fix (https://github.com/Juniper/contrail-common/commit/3e35471fec36612c4b956e35f41f62a9ad25dd58) committed on May 1st to R5.1
    • version control for http://148.251.5.90/tpc/, comes from contrail-dev-env
    • access to docker hub tungsten namespace to push container images
    • should we run a daily/periodic build for active branches ? help maintains potential points which can be used for releases going forward.
    • AI: Blog Posting for 5.1 release
  • General Topics
    • tf-devstack
    • NCDC speakers
    • CLA questions from the mailing list

Minutes

  • Action items
    • CC still investigating Groups.io calendaring
    • DH ~½ done w/5.1 blog post, will send to some TSC folks today
    • RLB still following up w/Juniper folks about NCDC
    • CC blocked on schwag until LF store manager returns from holiday
    • SK: nsm conversations starting this week
    • SK: Release tagging may be a moot point thanks to Prabhjot Singh Sethi's work
    • SK: Following up on differences between TF and Contrail 5.1, will email marketing@ & follow up with Darien Hirotsu
    • SK: Blueprint process & core committers are on hold pending repo migrations
  • VSPERF
    • Testing framework in OPNFV, mostly for perf
    • Having a conversation about integration vRouter into the VSPerf framework
      • VSPerf exposes APIs for working w/any switch, collects stats, cleans up, etc 
      • Roadblock: Having a separate DPDK
        • vRouter doesn't work w/upstream DPDK right now; Would need its own
        • Plan for vRouter to support upstream DPDK soon, though
          • Will need to discuss in TC, get input from everyone
      • Could run vRouter in a container, then use VSPerf to run the tests
        • Run tests w/different traffic generators, collect stats
        • Probably the best way to get started w/these tests
        • SR: Is there a Dockerfile for this already?
          • Prabhjot has this, will connect with Sridhar
    • Sridhar will run some initial tests & get back to us (email tsc@)
    • If this works, we'll get regular perf reports about vRouter (woo!)
  • 5.1 Release
    • PS has built several versions
      • Minor differences in the commits, but nothing too concerning
    • Bottom line: community should now be able to do its own build process
      • Either pick by hashes to choose the commit or take what we have
    • Using third party packages
      • Don't know where these are coming from (it's just an IP address) → contrail dev-env
      • These aren't version controlled?
    • ET: Containers named Contrail or TF?
      • Node manager looks at the name of the containers to make sure the services are running
      • So the name matters…which ones are used?
        • 5.0.3 added feature to add a company name here
      • PS: Haven't verified yet
    • ET: GUI shows…?
      • PS: Build version
    • Proceed as is w/the minor differences?
      • RLB: What's the delta?
      • Only 3 repos w/a lag, each w/1 commit
        • contrail-test
        • contrail-vrouter
        • contrail-common
      • PS will send these commits to the email thread
    • Will need to agree on daily build for the community
      • Need to loop in the Infra team
    • RLB: Eventually should be able to complete stuff from Business-level Requirements for TF Release Process
  • tf-devstack
    • Woo! Just about ready to roll!
    • Gotta get this moved to the TF repos
    • Will deploy on a single machine
      • Option for k8s (10GB) or OpenStack (16GB)
    • Can point at 5.1 tags/release
      • Options later to point at specific code
    • Will be able to announce this soon, super exciting, woo!
    • JG: How have the previous problems (quick dependency changes) been solved?
      • Progmatic has a copy of the Juniper CI/CD setup in Vexxhost
      • This will be the first project running on that
      • Will be bumpy at first but committed to supporting it to smooth out the bumps as they come up
    • DH has been testing it and can recommend it; very solid so far
      • RLB: blog post after? (DH: YES!)
  • NCDC Speakers
    • Will talk offline
  • CLA
    • VMB: Need to have all CLA managers on the mailing list
    • Also need instructions for the CLA managers

Action items