Custom Naming - Configure a pattern-based naming sequence

Overview

In this how-to we will cover an example of the Pattern based naming sequence and how it works.

Considerations

  • Licensed for the SovLabs Custom Naming Modules

Procedure

Create a simple naming sequence using pattern sequence type

  1. From your vRA catalog (1) , search for Naming (2) and click on Request (3) under add Naming Sequence - SovLabs Modules 


  2. Enter a name in the configuration label field


  3. Next to sequence, place a check next to Patterm (mixed bases and static text)


  4. Enter an initial value.  In this example, the pattern we want is 3 letters followed by 3 numbers (aaa000)


  5. In the Pattern type format, enter the pattern to match,  This can also contain static text or values too. 
    1. Simple Version to match the initial value
    2. Pattern with additional fixed text, I will add the static text of VM


  6. In the Unique Key field, enter the text you want to be unique for each server type/deployment.  
    NOTE:  We highly recommend keeping this as user driven static fields and not end user text fields. You will see in the naming standards as to why



  7. Click on submit


Create a simple naming standard using pattern sequence

  1. From your vRA catalog (1) , search for Naming (2) and click on Request (3) under add Naming Standard - SovLabs Modules 


  2. In the configuration label field, enter a name for this naming standard


  3. In the Naming sequence(s) field, place a check next to the naming sequence you created earlier


  4. In the Template field, enter the keys that will make up your naming standard and the sequence to use. In my example I will use 3 fields that will make up my server name. You could alternatively, depending on your sequence, use JUST the sequence
    1. Using keys to make up a server name
    2. Using just the sequence to make up your server name
    3. Having static information as part of your server name


  5. Click on Submit


  6. When you deploy a VM, you will see the name is generated with your naming standard.. In my example it will be ProdAPaaa000 / ProdAPaaa001 / ProdApaaa002 and so forth
    [2020-02-26 14:22:20.816] [I] TEMPLATE: {{Demo_Server_Environment}}{{Demo_Server_Type}}{{sequence.Demo_Pattern_Sequence}}
    [2020-02-26 14:22:20.825] [I] Name this round is: ProdAPaaa000
    [2020-02-26 14:22:24.947] [I] TEMPLATE: {{Demo_Server_Environment}}{{Demo_Server_Type}}{{sequence.Demo_Pattern_Sequence}}
    [2020-02-26 14:22:24.955] [I] Name this round is: ProdAPaaa001
    [2020-02-26 14:22:29.658] [I] TEMPLATE: {{Demo_Server_Environment}}{{Demo_Server_Type}}{{sequence.Demo_Pattern_Sequence}}
    [2020-02-26 14:22:29.667] [I] Name this round is: ProdAPaaa002
  7. In the naming sequence you can see the data field update with the key and the sequence that has been used.


What happens when the numeric component reaches its last number ie; 999?

In the above example we are creating sequences based on alpha and numeric information.  Once the numeric component is exhausted, it will increment the alpha character from aaa to aab

For Example.  I have manually set the ProdDB to be aaa998 and deployed 5 more servers. When I deploy the next server that matches on prod and db it will increment and subsequently roll over

[2020-02-26 15:07:03.336] [I] TEMPLATE: {{Demo_Server_Environment}}{{Demo_Server_Type}}{{sequence.Demo_Pattern_Sequence}}
[2020-02-26 15:07:03.345] [I] Name this round is: ProdDBaaa998
[2020-02-26 15:07:07.988] [I] TEMPLATE: {{Demo_Server_Environment}}{{Demo_Server_Type}}{{sequence.Demo_Pattern_Sequence}}
[2020-02-26 15:07:07.999] [I] Name this round is: ProdDBaaa999
[2020-02-26 15:07:12.234] [I] TEMPLATE: {{Demo_Server_Environment}}{{Demo_Server_Type}}{{sequence.Demo_Pattern_Sequence}}
[2020-02-26 15:07:12.244] [I] Name this round is: ProdDBaab000
[2020-02-26 15:07:16.411] [I] TEMPLATE: {{Demo_Server_Environment}}{{Demo_Server_Type}}{{sequence.Demo_Pattern_Sequence}}
[2020-02-26 15:07:16.422] [I] Name this round is: ProdDBaab001
[2020-02-26 15:07:20.510] [I] TEMPLATE: {{Demo_Server_Environment}}{{Demo_Server_Type}}{{sequence.Demo_Pattern_Sequence}}
[2020-02-26 15:07:20.520] [I] Name this round is: ProdDBaab002

It will also update your naming sequence and reflect that it will no longer use aaa000 as the sequence but aab000


And the machines have deployed with the rolled over sequence

Additional information

SovLabs Custom Naming Module : http://docs.sovlabs.com/latest/vmware-vra7x-plugin/modules/platform-extensions/custom-naming/
SovLabs Custom naming Configure pattern type : http://docs.sovlabs.com/latest/vmware-vra7x-plugin/modules/platform-extensions/custom-naming/examples/#configure-pattern-type

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.