Margaret Votava - FNAL Project Sponsor/Scientific Computing Services Associate Head
Parag Mhashilkar - Project Lead
Marco Mambelli - Technical Lead
Dennis Box - Project Member
Lorena Lobato - Project Member
Marco Mascheroni - Project Member/OSG Factory Operations
Burt Holzman - HEPCloud Sponsor Proxy
Stu Fuess - HEPCloud Sponsor Proxy
Tony Tiradani - HEPCloud Technical Lead
Dave Mason - USCMS T1 facility manager
Brian Bockelman - OSG/CMS
Steve Timm - HEPCloud Technical Advisor
Mike Kirby - FIFE
Ken Herner - FIFE
Thomas Hein - Summer student
Jack Lundell - Summer student
- Margaret: It was nice to hear from individual developers on their role and how they are contributing in the project.
- Dave Mason: CMS is moving to CRIC as a information management system and would like to simplify the life of operators managing the factory.
- Marco Mascheroni: There have been discussions in past and during CHEP.
- Glideinwms team is involved in the SI meetings and will adapt to changes as required when CRAIG matures.
- Reviewed action items from past stakeholders meeting.
- Dennis Box will scale down to 25% effort starting July 16.
- Next stakeholders meeting with be on September 12, 2018
- Tony: What will be the role of the DE and the interaction/move to GlidienWMS?
- Parag: Both Frontend and decision engine perform similar functionality. We already have a decision engine module for frontend. Longer term it would make more sense to unify the project or have a common code base. Easy of deployment and configuration of decision engine needs to be addressed before this can be done.
- Frontend scalability limits highlighted during CMS testing will be reached in span of 1 to 2 years. Optimizing HTCondor queries made by frontend before that is important.
- Single user factory & remove of condor_switchboard in 3.5
- Steve would like to understand the implications and thinks that this is required from the HEPCloud point of view.
- [Action Item] GlideinWMS team will setup a meeting with HEPCloud and OSG/CMS factory operations group to clarify technical details.
- Stu: How problematic is python 2 -> 3 migration wrt unit testing?
- There are changes to internal data structures/interpretation in python that code needs to take into account. Unit tests remain same.
- Thomas worked on a version of glideinwms that support python 3 last summer. It has not been thoroughly tested and ready for prime time. Migration is on long term road map.