SAM Installation Lauri Loebel Carpenter and the SAM Team February

Five Parts: 1. System preparation 2. SAM Client Software 3. File Transfer protocols 4. SAM Station software 5. Station Configuration

System Preparation ups/upd v4_6 only ups v4_6 should be ‘current’ $ ups list –aK+ ups should be configured for product start during boot upd configuration must include ${UPS_PROD_QUALIFIERS} in definition of UPS_PROD_DIR $PRODUCTS/.updfiles/updconfig setpath product should be installed ‘sam’ account, uid 1507 Part 1: system prep

SAM Client Software sam: $ upd install –G –c sam development environment if needed: $ upd install –G –c sam –q dev Part 2: client

File Transfer Protocols: sam_cp, sam_cp_config wrapper around all available transfer protocols install, getting only required dependencies: $ upd install –R –G –c sam_cp check configuration file, make sure your domain and any node-specific configurations are listed in the DOMAIN_CAPABILITY_MAP section : $ setup sam_cp $ ${SAM_CP_CONFIG_FILE} Part 3: file transfer

File Transfer Protocols: Specific protocols for your system. You must install at least one of: sam_bbftp most remote sites will use this wrapper around bbftp for use by ‘sam’ account for sam transfers sam_kerberos_rcp most on-site nodes will use this sam_encp only a limited number of on-site nodes will use this transfers to/from D0’s enstore installation (pnfs space) Part 3: file transfer

File Transfer Protocols: sam_bbftp $ upd install –G –c sam_bbftp $ ups tailor sam_bbftp # location of authorization file # number of attempts (2) # number of parallel streams (2) $ sam $ ups installAsSam sam_bbftp # authorization string: 1w1lln0t3atth3w1thag0r1lla Part 3: file transfer

File Transfer Protocols: sam_encp Wrapper around encp Node must be authorized to mount /pnfs space and read/write directly from D0’s enstore system Install via $ upd install –G –c sam_encp Part 3: file transfer

File Transfer Protocols: sam_kerberos_rcp require special sam/d0/ principals require special keytab files, typically /var/adm/krb5/sam_keytab sam must be able to successfully obtain tickets using $ kinit –k –t sam/d0/ install, tailor via: $ upd install –G –c sam_kerberos_rcp $ ups tailor sam_kerberos_rcp Part 3: file transfer

SAM Station Software: sam_ bootstrap Install via $ upd install –G –c sam_bootstrap Tailor via $ ups tailor sam_bootstrap Part 4: station

SAM Station Software: Tailoring sam_bootstrap Full documentation for sam_bootstrap can be found at Asks questions to determine what needs to be installed, what servers to start, etc. Part 4: station

SAM Station Software: Tailoring sam_bootstrap Must be done as a product maintainer, not ‘sam’ Must be done on each node ONE node runs the station master and FSS (‘master’) ALL other ‘worker’ nodes run only stagers (for staging between the ‘worker’ node and the station/FSS on the ‘master’ node). Part 4: station

SAM Station Software: Tailoring sam_bootstrap: SAM_BOOTSTRAP_ENV: file containing pointers to a particular set of configurations SAM_SERVER_HOME: location of sam configuration files, logs, etc. SAM_MAIL_RECIPIENT: where to send for YOUR system SAM_SERVER_LIST: file that determines which servers are started on this system ENCP configuration : ignore unless you are using enstore Part 4: station

sam_bootstrap: Configure a station Configure a station? ‘station’ means ‘cache manager’ required if you will be running analysis jobs and want the station to manage local cache ONLY on ONE ‘master’ node. Environment: prd or dev Version: default is the ‘current’ version in fnkits Station name Options to server – INFINITE POSSIBILITES! Part 4: station

sam_bootstrap: station options Most remote stations will require: --constrain-delivery=d0mino.fnal.gov --min-delivery=1k Note, the options should be entered on one line. See for more information. Part 4: station

sam_bootstrap: Configure a FSS FSS: File Storage Server required if you will want to store files from your site into SAM Only on ONE ‘master’ node Environment: prd or dev Version Station name Options to server – usually none are needed. Part 4: station

sam_bootstrap: Configure a stager Configure a stager? station starts its own stagers for cache management on the node running the station master this stager is required if you are running an FSS required on all nodes, ‘master’ and ‘worker’ Part 4: station

sam_bootstrap: Configure a stager Options to server: different for ‘master’ and ‘worker’ nodes. MASTER node (where station master runs): --with-fss --without-sm --max-transfers=N WORKER node (all other nodes): --with-fss --with-sm --max-transfers=N Part 4: station

sam_bootstrap: Centralized Servers You should ignore the following centralized servers: optimizer dbserver logger infoserver nameservice Part 4: station

sam_bootstrap: sam_bbftp_daemon Required if you are using sam_bbftp file transfer protocol for copying files from (e.g.,) d0mino to your cache area Because it runs on a specific port, you can only have one sam_bbftp daemon running for all environments. Part 4: station

sam_bootstrap: Final configuration Based upon the servers you decided to start, sam_bootstrap will install the necessary components into your ups database. Then, as user sam, you will need to copy the temporary server list file to the sam account: $ sam $ cp /tmp/node_server_list.txt ~sam/private Part 4: station

Station Configuration: ups start sam_bootstrap As user sam, start your station on the master node: $ sam $ ups start sam_bootstrap As user sam, start the stagers on each worker node: $ sam $ ups start sam_bootstrap Part 5: config

Station Configuration: Automatic start a boot time Your sysadmin must configure UPS to be started at boot time; see You configure which products UPS starts by editing: $PRODUCTS/.upsfiles/startup/.products or $PRODUCTS/.upsfiles/startup/.products Part 5: config

Station Configuration: Automatic start at boot time Find out where your $SETUPS_DIR is: echo $SETUPS_DIR Insert into your product startup file: echo “Starting sam_bootstrap...” /bin/su - sam –c “ /setups.sh; setup setpath; ups start sam_bootstrap“ Note, the command should be on one line. Part 5: config

Station Configuration: Overview Full documentation available at Must be done from station admin account (or ‘sam’ account) use “sam dump station --groups” to see who the administrators are Part 5: config

Station Configuration: General $ sam configure station [--name= ] \ [ ] Options are described in the full documentation at Part 5: config

Station Configuration: Cache Disks Inform your station about the cache disks, both local and remote: $ sam add disk [--station= ] \ --mount= \ --size= Example : $ sam add disk --station=myStation \ --mount=d0mino.fnal.gov:/sam/remote/myStation/incoming \ --size=10G $ sam add disk --station=myStation \ --mount=myNode.my.domain:/some/path/here \ --size= Part 5: config

Station Configuration: Groups Controls which physics groups may use your station cache disks. For remote stations, we recommend one group with access to all of your cache space, e.g.: $ sam add group --group=dzero --fair-share=1 \ [--station= ] \ [--max-disk= ] \ # sum of size of ALL disk, [--max-lock= ] \ # including d0mino disk [--admin= \ [--max-projects= ] Part 5: config

Check your station: $ setup sam $ export SAM_STATION= $ sam dump station –groups $ sam dump station –disks $ sam locate foo Part 5: config

References: All of the SAM documents referenced can be found under