F5 and source control - deploy from SCM or get from device?

@sriramgd,

 

 

I understand your goal, but wouldn’t recommend a push from SVN to your BIG-IP. Doing so would require both a UNIX diff (http://www.computerhope.com/unix/udiff.htm) and merge (http://www.computerhope.com/unix/merge.htm) to get the changes into the BIG-IP Configuration file (or a total replacement from Source Control), but would also require a b load to be implemented, which is disruptive to all traffic on the BIG-IP while it re-reads the configuration file.

 

 

I would recommend using a merge file (http://devcentral.f5.com/Tutorials/TechTips/tabid/63/articleType/ArticleView/articleId/1086464/BIG-IP-and-Merge-File-Configuration-Changes.aspx) which can exist externally from the bigip.conf, can be verified for syntax and reference context prior to implementation, and implemented without any service interruption to other traffic.

 

 

Configuration and Source Control.

 

I currently have my BIG-IP’s configured to do an hourly push of their configuration files into source control, but I believe that I will be utilizing iControl to change my methodology to a pull soon. So that is good advice from the other post.

 

 

You could also utilize trac (http://trac.edgewall.org/) to view the differences between files stored in your source control (so if something was working, but now it isn’t you can view the specific changes that have taken place).