CVMFS: 

  cvmfs issue at MSU, all nodes had cvmfs issues,
  caused by the NRP varnish server being down for a few hours (a cause but not an explanation?),
  and we could not recover those nodes by any methods.
  Eventually updated cvmfs from 2.13.1 to 2.13.2 2 which fixed the issue. 

  setup multiple cvmfs proxy testing groups to help understand and verify the stability of varnish vs. squid. .

- Condor: 

  cgroup in condor setup, to allow jobs to exceed 40% of memory usage, significantly reduced the killed jobs.  

- Tickets:

S3 end point: Added memory and CPUs to VM. Reduced transfer concurrency

squid monitoring: One former SLATE node transferred to NRP Now needs to be removed from CRIC to be removed from monitoring

- Mini data challenge on Tuesday:

Found that JSON file monitoring MSU was not showing proper traffic.
The Python script is looking at interface by SNMP index (not by interface numbers)
One data center had to be warranty-swapped which changed the SNMP indexing.
Also noticed that all traffic seems to be going through only one of the 2 data center core switches (2x100 instead of 2x2x100)
More to be understood.