Naming on CloudBolt Documentation

Naming module best practices

Mon, 01 Jan 0001 00:00:00 +0000

The CloudBolt OneFuse integration platform offers a Naming Module that allows users to craft Naming Policies for just about anything that requires a name. These Policies can be used for naming virtual machines, physical machines, deployments, AWS VPCs, Azure, GCP, or anything else you want to name in a standardized way.

Following these best practices will allow you to build your Naming Policies on a solid foundation offering repeatable, standardized, and compliant naming across the CloudBolt CMP, VMware Aria Automation, Terraform, and other tools.

Generate names

Mon, 01 Jan 0001 00:00:00 +0000

Create Naming Sequences, Validators, and Policies in the OneFuse UI. Naming Policies can be used instantly after creation.

Generate a name in four steps:

Gather and define the naming standard(s) that address your business needs.
Create a Naming Sequence.
Create a Naming Policy.
Call the Naming Policy via an Upstream Provider.

Create flexible and dynamic names

Extend the flexibility of your Naming Policy by applying a Sequence, Templating, and Validators.

Use a Sequence

A Naming Template without a sequence in a Naming Policy can result in a limited set of names.
Use Sequence(s) in Naming Policies to automatically create names in sequential order.
If consuming Naming Policies using Aria Automation 8, see how to use Custom Resources to influence deployment names.

Refer to Sequences to learn more.

Naming components

Mon, 01 Jan 0001 00:00:00 +0000

The following components are needed to generate names.

(opens full-size image in a new tab)

Sequences

A Sequence allows for a continuous or connected series of numbers to be used when generating a name.

Sequence types

Decimal

Base10 numeral system. Increments a sequence 0 to 9.

The most commonly used Sequence Type.

{# Example Decimal Sequence with:
   Reuse Sequence Values: false
   Maximum Length: 2
   Padding Character: 0
   Initial Value: 1
   No Unique Key
#}

=> 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11 ... 99

Consume odd or even sequenced custom names by passing the following OneFuse naming properties from the upstream provider: