Difference between revisions of "EJFAT Group Meeting Feb. 17, 2022"

From epsciwiki
Jump to navigation Jump to search
 
Line 32: Line 32:
 
<!-------------------------------------------------------------------------------------------------->
 
<!-------------------------------------------------------------------------------------------------->
 
=== Agenda: ===
 
=== Agenda: ===
# [[EJFAT Group Meeting Feb. 10, 2022 | Previous meeting]]
+
* [[EJFAT Group Meeting Feb. 10, 2022 | Previous meeting]]
 
*:
 
*:
 
*:
 
*:

Latest revision as of 15:12, 17 February 2022

The meeting time is 11:00am.

Connection Info:

You can connect using ZoomGov Video conferencing (ID: 161 012 5238). (Click "Expand" to the right for details -->):

Meeting URL
 https://jlab-org.zoomgov.com/j/1610125238?pwd=QnEvcjV6VFFndWZsQW15SmJKU0RJZz09&from=addon

Meeting ID
161 012 5238

Passcode
503371

Want to dial in from a phone?

Dial one of the following numbers:
US: +1 669 254 5252 or +1 646 828 7666 or +1 551 285 1373 or +1 669 216 1590 or 833 568 8864 (Toll Free)

Enter the meeting ID and passcode followed by #

Connecting from a room system?
Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode

Agenda:

  • Previous meeting
  • Situation:
    • Testing on FPGA LB
    • Using script based LB Control Plane
    • PO for Compute submitted - ETA 1 June
    • PO for Networking submitted - ETA 1 July
  • Pending:
    • End-to-end EJFAT ERSAP solution
    • Minor f/w change for 'garbage' packets
    • Support C libraries for LB Host Control Plane
  • Test Plan
  • Issues:
    • Test Lab build out
      • Use FPGA port #1 for local host subnet testing
      • Use FPGA port #2 for switch fabric testing
      • Use (2) spare/borrowed switches in DAQ data center/lab
      • Scrounge compute hosts
        • 129.57.29.*/24 -> 60+ hosts
        • 129.57.109.*/24 -> 7 hosts
      • Plumbing networking to spaces (ETA: week of 02/13/2022)
      • Configuration of network switches and Host CPU for FPGA LB (ETA: week of ?)
    • Control Plane
      • Arp cache poisoning
      • Handle arp messages
      • Feedback from Compute hosts -> new routing strategy
  • AOT



Minutes:

Attendees: