Using the OneFuse IPAM and/or DNS module for BlueCat, it’s easy to create API-based, BlueCat-powered IPAM and DNS services to drive solutions from upstream automation tools or scripts.
OneFuse provides the control and standardization for requesting, validating and registering records with the unique ability to abstract and dynamically drive network selection, view, custom fields and many other BlueCat features.
OneFuse eliminates the security risk of requiring direct access to a BlueCat, enabling least-privilege access for specific use cases via policy-based services, versus exposing the full BlueCat API and otherwise over-allocating permissions or micro-managing assignments. Each policy defines the automation use case, subnets, DNS record settings and more – with the added flexibility of having the requester influence all use cases dynamically via templated fields defined in OneFuse policies.
OneFuse Makes vRA Better
Learn MoreFeatures and Capabilities
IPAM
- Drive from any tool, e.g. vRealize Automation, Terraform, Ansible, ServiceNow, CloudBolt CMP or directly via the API
- Create flexible IPAM Policies that include a BlueCat Endpoint
- Reserve unique IP address(es) and assign to the NIC(s) based on IPAM Policy
- Perform pre and post validation for IP and DNS assignment
- Ability to single-thread operations to reduce load on downstream BlueCat endpoints
- Provides control and standardization for resources on both public and private cloud (on-prem) environments.
- OneFuse enables least-privilege access wherein each policy serves as an API-based service, restricted to the specific use cases defined in the policy, without exposing the full BlueCat API or over-allocating permissions to users or upstream automation tools.
- Drives advanced BlueCat features such as User-Defined Fields and DNS Views flexibly via the OneFuse Template Engine
- Ability to support sub-interfaces, e.g. multiple IP assignments per NIC in vRealize Automation
- IPAM Policies include basic IP information such as subnets and DNS and WINS configurations
- IPAM Policies can be pinned to specific NIC numbers
- IPAM Policies can span multiple networks, each consisting of a network name, subnet, CIDR block, gateway address and network mask
- Added flexibility of having the requester influence all use cases dynamically via templated fields
- Multiple IPAM Policies (each specifying a BlueCat Endpoint) can safely co-exist, allowing for isolated testing and promotion without disruption
- BlueCat Endpoints can also be used with the OneFuse IPAM or DNS modules
- Centralized visibility into inventory of IP assignments, log data
DNS
- Drive from any tool, e.g. vRealize Automation, Terraform, Ansible, ServiceNow, CloudBolt CMP or directly via the API
- Create flexible DNS Policies that include a BlueCat Endpoint
- Reserve unique DNS Record(s) and based on DNS Policy
- Provides control and standardization for resources on both public and private cloud (on-prem) environments
- OneFuse enables least-privilege access wherein each policy serves as an API-based service, restricted to the specific use cases defined in the policy, without exposing the full BlueCat API or over-allocating permissions to users or upstream automation tools.
- Drives advanced BlueCat features such as User-Defined Fields and DNS Views flexibly via the OneFuse Template Engine
- Employs several methods to improve DNS data integrity and mitigate issues from stale, duplicate or orphaned DNS records, such as retry logic, record availability and DNS propagation/post validation checks
- Allows for independent configurations for forward and forward/reverse record scenarios, if desired
- Added flexibility of having the requester influence all use cases dynamically via templated fields
- Multiple DNS Policies (each specifying a BlueCat Endpoint) can safely co-exist, allowing for isolated testing and promotion without disruption
- BlueCat Endpoints can also be used with the OneFuse IPAM module
- Centralized visibility into inventory of DNS registrations, log data