1. EPICS Development Cleanup EPICS only for now Must match with the existing production environment Must not impact the existing production

2. EPICS Development and Production DevelopmentProduction Application FilesystemAFS only (SCCS)NFS only (MCC) Application area (LCLS_ROOT)/afs/slac/g/lcls/usr/local/lcls Data area (LCLS_DATA)/nfs/slac/g/lcls/u1/lcls CVS (CVSROOT)/afs/slac/g/lcls/cvs:ext:${USER}@lcls- prod02:/afs/slac/g/lcls/cvs IOC booting serverSCCS afsnfs2MCC NFS mccfs2 Development/Release hostlcls-dev2lcls-builder

4. Key Environment Variables LCLS_ROOT EPICS_TOP epics EPICS_IOCS iocCommon EPICS_IOC_TOP iocTop EPICS_BASE_TOP base … RTEMS rtems TOOLS tools …. Application Tree

5. Key Environment Variables LCLS_DATA EPICS_DATA epics IOC_DATA ioc/data … TOOLS_DATA tools CMLOG_DATA cmlog/prod …. Data Tree

7. A Cleanup Plan Migrate back from /nfs/slac/g/lcls/build to /afs/slac/g/lcls –Clean up /afs/slac/g/lcls: two approaches Save /afs/slac/g/lcls to a toaster area and remove all (what about non-EPICS stuffs, e.g., HLA) Remove EPICS stuffs (help needed!!!), leave non-EPICS alone for next cleanup –Check out from CVS to /afs/slac/g/lcls and rebuild –Phase out /nfs/slac/g/lcls/build Development IOC support –Boot from afsnfs2 SPEAR and NLCTA boot from afsnfs2 We can request SCCS continue to provide us this support Development and production in symmetry Simple and minimum effort –Boot from SCCS NFS (an alternative solution) ? A development area in SCCS NFS, in addition to AFS Two development environment: AFS and NFS Effort to install iocApps to NFS IOC setup files Development and production in asymmetry

8. Application Areas Cleanup Application area in AFS (/afs/slac/g/lcls) 3.14.8.2 README.vols~ cmlog devepics installDev package rtems vol1 vol5 MCF5282 Sol06 common docs lattice physics s2e vol2 vol6 README.directories bin controls epics ltc2208 plc tools vol3 www README.vols build cvs external matlab prod users vol4 xal Application area in public NFS (/nfs/slac/g/lcls/build) README TestBaby applications epics package plc rtems tools vxWorks Application area in MCC NFS (/usr/local/lcls) bin controls epics lib package physics rtems tools

9. Environment Setup On Development: –Setup file location: ${LCLS_ROOT}/epics/setup Flow $HOME/.bashrc -> epicsReset.bash -> epicsSetup.bash -> envSet.bash -> $EDMSETUP/setup.sh -> $CMLOGSETUP/cmlogSetup.bash One set of setup files for both development and production –Setup for dev, if on AFS –Setup for prod, if on MCC NFS

10. Environment Setup if [ -d /afs/slac/g/lcls ]; then echo “setup for development” … elif [ -d /usr/local/lcls ]; then echo “setup for production” … else echo "ERROR: this ${HOSTNAME} is not supported for LCLS dev/prod" exit 1 fi echo “setup for common things” …

11. For Development Use lcls-dev2 –Access to both development data area ($LCLS_DATA) and AFS area ($LCLS_ROOT) –OS in sync with the production systems –More reliable (under our control) $home/.bashrc source epicsReset.bash source matlanSetup.bash source physicsSetup.bash (if needed for HLA) Default login shell: bash -> do nothing Default login shell: tcsh -> type “bash”