Naming standards are a fact of life for most organizations.

For example, hostnames are the most basic label that apply to all servers, and this identifier has operational value well beyond name resolution. Hostnames help multiple IT and application teams quickly identify and categorize any given server, revealing its function, role, operating system, environment, location or other attributes.  

Using the OneFuse Naming module, it’s easy to manage multiple naming standards that enforce naming conventions for resources provisioned via upstream automation tools or scripts. Naming can go well beyond hostnames, for instance, generating unique port numbers or database identifiers.  OneFuse codeless, policy-based integrations can securely power other automation tools and services such as VMware vRealize Automation (vRA), Terraform, ServiceNow, CloudBolt CMP or existing scripts via API, providing the control and standardization for resources for both public and private cloud (on-prem) environments. 

Managed Names in OneFuse

OneFuse Naming with vRA Cloud Assembly

OneFuse Naming with Terraform

OneFuse Makes vRA Better

Learn more


Simplify Complex Naming

OneFuse Template Engine provides a simple yet powerful language to tackle even the most complex naming conventions without the need for custom workflows.

Configurable validators, such as DNS, to ensure the name is unique 

Analytics - network icon
Sequencing that Fits Your Use Case

Manage naming sequences independent of naming standards for ultimate flexibility and control, reducing management overhead.

Database - code icon
Centralized Visibility

View the generated name, representing relevant data of each policy execution

Blockchain icon

Features and Capabilities

  • Drive from any tool, e.g. vRealize Automation, Terraform, Ansible, ServiceNow, CloudBolt CMP or directly via the API
  • Naming Policies can be used for naming VMs, physical machines, deployments, AWS VPCs, Azure, GCP resources, port numbers or anything else you want to name or sequence in a standardized and/or unique way 
  • Create flexible naming standards that include one or more sequences  
  • Naming Standards consisting of a combination of static text and dynamic content such as custom properties and/or custom logic
  • Validates against DNS to ensure uniqueness 
  • Ability to validate across one or more instances/tenants of vRealize Automation 7 and 8 to allow for side-by-side deployments and a less-restrictive migration path from vRA7 to vRA8 
  • Allows for creation of multiple types of sequences such as decimal, hex, octal, or custom pattern including binary, a/b and any combination of types 
  • Dynamic sequences are possible using the pattern type, which can utilize properties in combination with custom logic and one or many sequence types  
  • Includes option to allow for reuse of sequence values, e.g. for gaps left when machines have been deprovisioned  
  • Includes options for sequence length, padding character, initial value  
  • Sequences can be updated at any time, for scenarios like increasing sequence length or setting a new initial value  
    • e.g. set next sequence value at 500 instead of 030  
  • Supports creation of multiple Naming Sequences and Standards as needed  
  • Added flexibility of having the requester influence all use cases dynamically via templated fields 
  • Multiple Naming Policies (each specifying Naming Sequence(s) and/or Naming Validator(s)) can safely co-exist, allowing for isolated testing and promotion without disruption 
  • Centralized visibility into inventory of name assignments, log data