make printable

Business rules for MUC blades

Why business rules?

With the multi-user environment on muc01...muc05, there is the need to coordinate certain setups and configurations.

vnc session IDs

Due to firewall rules, each muc has port IDs 1...9 available for vnc sessions. Therefore:

• Each account has *3* vnc IDs, in groups 1-3, 4-6, and 7-9.
• The groups are distributed to the accounts in alphabetical order.

On muc02, we have:

These IDs can be used in a predictable way; use the related DISPLAY settings (e.g. export DISPLAY=muc02:3) for your cronjobs. Use the utility tool dfosVNCserver to check for these IDs and re-create them in case of machine reboots. Use the associated config file to configure the vnc IDs.

Cronjob setup for autoDaily

Due to the condor configuration, any scheduled cascade on a muc blades will be executed eventually. But consider an instrument with short execution times (SHORT) and one with long execution times (LONG): if LONG is scheduled before SHORT, SHORT will need to wait for a (relatively) long time, while scheduling the LONG cascade after the SHORT cascade means a negligible delay for LONG and a considerable gain for SHORT.

Therefore, the autoDaily execution times in the cronjob files should be set such that the instruments with SHORT cascades execute before the instruments with the LONG cascades. Of course SHORT and LONG correspond to average values, should be derived from the WISQ exec_time monitors and reviewed from time to time. The daily pattern becomes visible on the cascadeMonitor.