Forum Discussion

Josh_41258's avatar
Josh_41258
Icon for Nimbostratus rankNimbostratus
Jun 20, 2013

Where to put custom scripts

Where on a v11 box can I put custom scripts where they won't get deleted everytime I upgrade?

 

I have a backup script that I have been sticking in /etc/cron.daily, but it gets deleted everytime I apply a hotfix.

 

Josh

 

  • try /var/tmp

     

    we put ucs files there in the lab and run through upgrades and they don't get deleted in the process

     

  • I'd put them in the /root which is the root user's home directory. This will be included in UCS files and should be preserved during upgrades. I'd do a quick check on a lab VE to verify this.

     

     

    Aaron
  • /root does not get preserved during an upgrade. Any other ideas?

     

  • Take a look at this forum post:

     

    F5 Big IP File Locations

     

    And in the /usr/libdata/configsync/cs.dat file. This is where config sync/save folders are listed. I typically put scripts in the /config/monitors directory, but then you can define your own.

     

  • This is a good idea and a small issue. A good place to store scripts like well defined pool management scripts and so on would be /var/opt/opsteam. However if this directory gets overwritten during an upgrade it would have to be recreated after doing so. Scripts should probably be maintained in a version control system and then deployed from there.

     

    Ideally, a central server should be used that can access all of the F5 devices. If not, then scripts would have be synchronized across all F5s or deployed selectively, where some are destined for devices 1-4 and other scripts are specifically for another set of F5s.

     

    Scripts can be places in folders based upon function or product (gtm or ltm) and/or/also defined by application name. So you could have something like: /var/opt/gtm/[wip] /var/opt/ltm/[vip]

     

    If someone wants to modify a script, they can copy it to their home directory.

     

  • I think the best option now is to use iCall which is basically iRules for the control plane. Here's an excellent example:

     

    https://devcentral.f5.com/articles/f5-automated-backups-the-right-way

     

    Aaron