With the OneFuse F5 module it’s now possible to create API-consumable, policy-based services for F5 BIG-IP features including LTM, GTM, APM, ASM and PEM.  F5 administrators can create and customize scenarios such as server load balancing, app security, GSLB and more using OneFuse template-based policies without custom coding.  With the included IPAM, DNS, Naming and Property Set features, it’s easy to embed other dependent services such as virtual server and pool naming standards, virtual IP assignments and DNS registrations.  Teams and tools can easily consume F5 using native support for vRealize Automation 7/8/Cloud, Terraform, Ansible, ServiceNow, CloudBolt CMP, Python as well as direct API consumption.

OneFuse F5 BIG-IP Policy

OneFuse F5 BIG-IP Deployments

OneFuse F5 BIG-IP with AS3


F5 BIG-IP AS3-powered services

Including LTM, GTM, APM, ASM and PEM

Network - devices icon
Ability to include the following OneFuse Modules and Capabilities

Includes ability to include OneFuse Naming, IPAM and DNS modules and Property Sets directly within AS3 declarations

File icon

Provisioning/Deprovisioning scenarios for creating and destroying a new service.  Also supports Day2 Operations

Time icon
Upstream Providers

Direct support for consumption from vRealize Automation 7/8/Cloud, Terraform, Ansible, ServiceNow, CloudBolt CMP, Python as well as direct API consumption

Touch icon

Features & Capabilities

  • Utilizes F5 Application Services 3 Extension (AS3), a declarative interface for configuration applications on BIG-IP, to include features such as LTM, GTM and Security Policy attachment.
  • Integrates with OneFuse Naming module to name a new service (e.g. virtual servers and pools)
  • Integrates with OneFuse IPAM module to reserve an IP Address for a new service (e.g. virtual servers)
  • Integrates with OneFuse DNS module to reserve DNS Record(s) for a new service (e.g. virtual servers)
  • Provisioning/Deprovisioning Scenarios:
    • Create and Destroy a new service (e.g. VIP) at once
    • Create new service (e.g. virtual server) and add/remove members/nodes incrementally. As members/machines are deprovisioned, they are removed from the service, and the last member/machine out deletes the service.
  • Sample Policy Payloads for creating a destroying services