You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The site needs to provide two different site configurations on the same WN since they run T1 and T2 jobs on the same resources. The siteconfig with CVMFS is unique to the WN though.
T1 and T2 jobs are distinguished by a different environment namely the VO_CMS_SW_DIR variable, which basically gets translated into CMS_PATH after sourcing cmsset_default.sh.
Can export_siteconf_info.py be changed to respect this? To my best knowledge CMSSW uses CMS_PATH and not a direct lookup into CVMFS.
This is rather urgent, since T1_FR_CCIN2P3 cannot be used right now...
Thanks, Christoph
The text was updated successfully, but these errors were encountered:
thanks for reacting so quickly! The information that you put in a hack for CCIN2P3 arrived in my mail box during my typing of this issue. Let me know, if you need more details about the site setup at CCIN2P3.
Hi James, hi Brian,
the siteconf check for Glideins does not work at T1_FR_CCIN2P3:
https://ggus.eu/index.php?mode=ticket_info&ticket_id=113707
The site needs to provide two different site configurations on the same WN since they run T1 and T2 jobs on the same resources. The siteconfig with CVMFS is unique to the WN though.
T1 and T2 jobs are distinguished by a different environment namely the VO_CMS_SW_DIR variable, which basically gets translated into CMS_PATH after sourcing cmsset_default.sh.
Can export_siteconf_info.py be changed to respect this? To my best knowledge CMSSW uses CMS_PATH and not a direct lookup into CVMFS.
This is rather urgent, since T1_FR_CCIN2P3 cannot be used right now...
Thanks, Christoph
The text was updated successfully, but these errors were encountered: