For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Modernizing F5 Platforms with Ansible

I’ve been meaning to publish this article for some time now. Over the past few months, I’ve been building Ansible automation that I believe will help customers modernize their F5 infrastructure. This...
Published Aug 13, 2025
Version 1.0
Ansible
Ansible Automation Platform
application delivery
BIG-IP
devops
Modernization
upgrade
VELOS
Matt_Mabis's avatar
Icon for Employee rankEmployee
I am a Senior Solutions Archtiect at F5 in Business Development. I specialize in VMware integrated solutions, Ansible automation (including F5 Automation Toolchain), and Virtual Edition performance. I have a deep background in troubleshooting. I have multiple VMware VCP Certifications including (Data Center, Desktop and Mobility and NSX)
View Profile
JustinKwok's avatar
JustinKwok
Icon for Employee rankEmployee
Oct 14, 2025

Great work Matt,
I see in your demo it does not require using F5 Journeys for migration, is it for the case of UCS like-to-like migration, restore UCS with --platform-migrate would be enough?

Thank you 

Justin

Matt_Mabis's avatar
Matt_Mabis
Icon for Employee rankEmployee
Dec 08, 2025

Hey Justin, Sorry for not replying sooner.

So yes in the demo it doesnt require Journeys.  My idea was to get the prerequisites handled with Automation that Journeys still makes as a manual requirement.

 

For Like-for-like migrations you would still need to do the --no-license and --platform-migrate if shifting to different platforms.  In my code the command i run

"tmsh load /sys ucs {{ item.path | basename }} no-license platform-migrate"

 

I also do this in an SSH command as well rather than the F5 Rest API call as during a platform-migrate it restarts the RESTAPI services which prevents the platform-migrate from working correctly.