NimbostratusHi Experts,
I'm trying to migrate Application using Journeys and was hoping someone could tell me how to group all applications into a single tenant (Common). When I load the source ucs to Journeys, it's currently grouping them into random tenants and applications. The source F5 has all it's applications under Common and I'm hoping to migrate as is.
Thanks,
Mohamed
NimbostratusI found this article. Which says the applications cannot be moved to Common
https://my.f5.com/manage/s/article/K84127184
Is there a way to move all applications to a single Tenant?
CirrostratusI did migrated the live units from i-series to r-series and did not faced this issue. Also you can update the configurtions in journeys during the config migration process.
MVPIf you are planning to do partial migration not full maybe try the AS3 converter and then modify the tenant to be /Common/Shared in the AS3 generated declaration.
https://clouddocs.f5.com/products/extensions/f5-automation-config-converter/latest/
https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/userguide/faq.html
MVPF5 with new architecture, and eventual migration away from TMOS is going down the tenant path. We already saw a bit of this with iApp templates creating folders for applications, and new FAST templates using tenants a well.
One can "resist" or migrate to this new methodology and accept it, lol. If you want to "resist" you could always develop a parser in Python to search and replace object names and references. You can also do this manually. Or you can migrate to the new way.
Finally, you can submit a feature request to the Journeys page. Alternatively, you can use your sales engineer / partner to champion your case with F5 to implement the required functionality and prioritize any RFE.