Examples

Configure Unique Key

Define the unique key to increment the sequence independently based on the rendered value of the Naming Standard.

The Naming Sequence has a Unique Key of

{{ ownerName | split: "@" | first | substring: 0,2 | downcase }}{{ Environment | substring: 0,1| downcase }}{{ OS | substring: 0,1 | downcase }}{{ Application | substring: 0,3 | downcase }}
The Naming Sequence has the type Decimal with a Max Sequence Length of 3, starting at 1

The Naming Standard has a Template of

{{ ownerName | split: "@" | first | substring: 0,2 | downcase }}{{ Environment | substring: 0,1| downcase }}{{ OS | substring: 0,1 | downcase }}{{ Application | substring: 0,3 | downcase }}{{ sequence.SEQUENCENAME }}

Run 1
  • ownerName: jsmith@company.com
  • Environment: dev
  • OS: Linux
  • Application: Web Servers

=> Result: jsdlweb001


Run 2
  • ownerName: jdoe@company.com
  • Environment: dev
  • OS: Linux
  • Application: Web Servers

=> Result: jddlweb001

The sequence number started at 001 for both jsmith and jdoe
Run 3
  • ownerName: jsmith@company.com
  • Environment: dev
  • OS: Linux
  • Application: Web Servers

=> Result: jsdlweb002

When jsmith requested again, the sequence incremented by 1


Configure Pattern Type

Pattern naming sequences are designed to be flexible and multiple base sequences that can match most sequence types used in the industry.

Pattern naming sequences can contain the following types of bases:

Type Pattern Key Default Value Range
Decimal # 0 0-9
Hexadecimal x 0 0-F
Octal o 0 0-7
Binary b 0 0-1
Alpha a a a-z
All Pattern Keys are to be defined inside / /


Example: /a#b/ is a sequence of alpha, decimal, and binary numbers/letters.


A unique feature of the pattern naming standard is that the sequence can contain static or template text in the sequence, yet the sequence increments as you would expect, ignoring the text.

For example a pattern of /a/StaticText/b/ will result in a the following sequence values:

aStaticText0, aStaticText1, bStaticText0, bStaticText1, cStaticText0 ...

As you can see that part of the sequence that the counter (inside the / /) increments.

Meanwhile, the text outside of the / / remains static text, yet as the right most digit rolled over the next significant digit increased as one would expect. This can be used with or without static text.

If a template is used, the counter is incremented first and then the template is rendered. This means if you have a property called “App” and you use it in a pattern such as /#//#/

  • Run #1 - App = “Test” => sequence value is 0Test1
  • Run #2 - App = “Foo” => sequence value is 0Foo2

SovLabs Template Tester

  1. Login to vRA tenant
  2. Click on the Catalog tab
  3. Request the SovLabs Template Tester vRA Catalog Item
  4. No need to Submit the form
Form fields refresh automatically any time a field is updated
SovLabs Template Tester
SovLabs Template Tester

Ability to select an existing provisioned machines in vRA inventory to auto-load properties for modeling template engine scenarios and ability to select an existing property group to auto-load properties for modeling for modeling template engine scenarios

FieldValue
Select a type to show a default template

Optional

Select an option to see a default example

Template

Type in the desired template to test

This field is templatable. Click the link below to view documentation on the SovLabs Template Engine

SovLabs Template Engine page
Get Properties from VM?

Select the checkbox to obtain vRA Properties from an existing VM

Max # of VMs and Business Groups

Shown if Get Properties from VM? is checked

Defaults to 5. Number of vRA Business Groups and VMs to get

Business Group filter

Shown if Get Properties from VM? is checked

Filter by Business Group name. Allows for partial match

vRA Business Groups

Shown if Get Properties from VM? is checked

Select the vRA Business Group(s) to retrieve vRA VMs

Hostname filter

Shown if Get Properties from VM? is checked

Filter by VM's name. Allows for partial match

Select VM

Shown if Get Properties from VM? is checked

Select the VM to get its VM Properties

Properties JSON

JSON valid key:value pairs (e.g. vRA VM Properties)

SovLabs Template Engine Result
Output

Will display the output based on Template and Properties JSON provided above

Click for vRA Property Group
FieldValue
Max # of Property Groups to get

Defaults to 5. Number of vRA Property Groups to get

Name filter

Filter by vRA Property Group name. Allows for partial match

SovLabs Dynamic Property Group

Select a SovLabs Dynamic Property Group (starts with 'SVL')

Property Group Properties

Read-only field that gets the properties from a SovLabs Dynamic Property Group

Rendered Output (includes Property Group Properties)
Rendered Property Group

Read-only field that renders the templated properties in a SovLabs Dynamic Property Group

Template

The template from the 'General' tab. Allows for manipulation without having to go back to the 'General' tab.

Properties JSON merged with Property Group

The Properties JSON from the 'General' tab merged with the Rendered Property Group from the SovLabs Dynamic Property Group

Output

Will display the output based on the Template and Properties JSON merged with Property Group