Which method will result in unique names per VM when scaling out a Service in a Calm Blueprint?

Question

Options

• AGuest OS customization using sysprep contains
• BService VM Name field contains the macro variable @@{calm_array_index}@@.
• CCall an external Python eScript that uses an IPAM API to register the VM name in DNS.
• DSet the VM Name field to allow user edits at launch so the user can enter a custom value at

• A
  5% (1)
• B
  86% (18)
• C
  10% (2)

Explanation

The correct method to result in unique names per VM when scaling out a Service in a Calm Blueprint is to use the macro variable @@{calm_array_index}@@ in the Service VM Name field (Option B). This variable will append a unique index number to each VM name based on the scale-out count. For example, if the Service VM Name is MyAppVM-@@{calm_array_index}@@ and the scale-out count is 3, the resulting VM names will be MyAppVM-0, MyAppVM-1, and MyAppVM-. Option A is incorrect because the <ComputerName> tag in the sysprep file will only affect the hostname of the guest OS, not the VM name in the cloud provider. Option C is incorrect because calling an external Python eScript to register the VM name in DNS will not change the VM name in the cloud provider either. Option D is incorrect because setting the VM Name field to allow user edits at launch will require manual input from the user for each VM, which is not scalable or automated.

No community discussion yet for this question.