LCLS How-To Release Software

• High Level Apps Release Procedure
• EPICS IOC Applicaion Deployment and Release Procedure Rev 4
• EPICS Soft IOC Depolyment and Release Procedure for Production
• Adding software to eco
• CRAM Migration Guide

LCLS Code Management

• LCLS CVS Repository
• LCLS Directory Tree
• EPICS Modules and Dependencies
• LCLS How-to Tag a Release
• LCLS How-to Branch a Release
• EPICS Modules Maintenance and Patch Management Guidelines

...

• LCLS Directory Tree
• How-to Setup DHCP for an IOC
• Cheetsheet for AFS IOC boot pararmters
• Cheetsheet for NFS IOC boot parameters
• Cheetsheet for Reflashing RTEMS IOC
  
  

Note: PLC applications are generated on windows machines. See subsystem controls engineer for details

...

You are ready to export your software to production.

From lcls-dev2For EPICS IOC Applications:

1. If your application is CRAMmed from lcls-dev2:
   1. cd to TOP of your Application
   2. cram push
2. Otherwise,
   1. ssh to the production machine shared account, may  need to hope to lcls-prod02 first
.

...

1. 2. cd $EPICS_IOC_TOP/<Application>
2. eco  m LaserR1-0-0 -d Laser-R1-0-0
    

Edit RELEASE file and replace path /afs/slac/g/lcls with /user/local/lcls/

1. 1. Use eco to checkout your application
   2. cd to the TOP of your release
   3. build your application by typeing "make"
2. cd ..
3. gmake
   2. cd $EPICS_IOCS/<nodename>
   3. For hard iocs
   cp
   1. 1.  cp -p startup.cmd startup.cmd_bckup
   and the edit
   1. 2.   edit startup.cmd file and point to the new tagged release
   2. For soft iocs
      1.  mv bin bin_bckup
   and
   1. 2.   ln -s ../../iocTop/<subsystem>/<tagged-version>/bin/<OS> bin
         
   Reboot ioc, after mcc has granted permission.
   1. 1.  
   2. Enter a log in the operations elog book by sending email to controls-software-release
   3. Reboot ioc from network panel, after mcc has granted permission.

Matlab Programs Released to Production:

• how-to release matlab software on production
• or all new release, enter a message in the operation elog book by sending email to controls-software-release.

Step 11: Export ChannelWatcher Config Files
(see the example below)

• ssh iocegr@lcls-builder or ssh physics@lcls-srv01
• export CVSROOT=:ext:luchini@lcls-prod02:/afs/slac/g/lcls/cvs
• cd $TOOLS/ChannelWatcher/config
• cvs update <filename>
• ssh laci@lcls-daemon1
• cd /etc/init.d
• ./st.cw<Subsystem> restart ex) st.cwMG for Magnets
• logout
• Note: if you have the Message Logger up (from lclshome) note the number of pv's that failed to connect to ChannelWatcher.
• Enter a message in the operation elog book by sending email to controls-software-release.