DNS

Configure and use the OneFuse DNS module with the OneFuse XUI

  3 minute read  

To learn more about this OneFuse module, refer to DNS.

Prerequisites

  1. Configure OneFuse Property Set(s) and OneFuse Module Policies.
  2. Install OneFuse XUI per CloudBolt CMP.
  3. Review an overview on OneFuse Modules with CloudBolt CMP.
  4. Create a new Blueprint (if none exist) or determine which existing Blueprint(s) will utilize this OneFuse Module. Resource: Blueprints.

Configure the Blueprint

  1. Know the name of the OneFuse Connection Info created via OneFuse XUI initial setup.
  2. Determine which OneFuse DNS Policies to run for this Blueprint.
  3. Update the Blueprint to add in necessary parameters to invoke OneFuse DNS Policies.
  4. Deploy the Blueprint to provision a deployment and register DNS record(s).
  5. Destroy the Deployment to unregister the DNS record(s) for the destroyed resource(s).

Update the Blueprint

  1. Log in to CloudBolt CMP.
  2. If not already on the Catalog page, select Catalog from the main menu.
  3. Search and find the desired CloudBolt Blueprint.
  4. Edit the Blueprint by selecting the gear icon on the bottom-right of the Catalog Item.

Add in necessary Parameters

The following Parameters need exist on the Blueprint.

Learn more about CloudBolt Parameters for: Blueprints, Environments, and Groups.

Call a DNS Policy for a specific NIC:

Parameter Name Format Parameter Value Format
OneFuse_DnsPolicy_Nic<#>

- Replace <#> with a number from 0 to 9, one for each NIC. Default is 0		 <OneFuse Connection Info Name>:<DNS Policy Name>:<DNS Suffix(es)>

(When listing multiple DNS Suffixes, comma separate the values without any spaces.)

Example Parameter:

OneFuse_DnsPolicy_Nic0: 'OneFuse:MyDnsPolicy:example.com'
Additional helpful properties passed to OneFuse module

Purpose: Relate OneFuse Policy executions from different OneFuse Modules together with a Tracking ID.

Property and Parameter Value Format
OneFuse_Tracking_Id A GUID (globally unique identifier) that links OneFuse Policy Executions and the resulting Managed Objects together for a given resource on a deployment. The first OneFuse Module Policy execution will populate this Parameter and it will be passed into other OneFuse Modules automatically. Learn more about OneFuse Tracking ID.

Purpose: Reference a specific NIC’s values to get hostname, IP Address, etc.

Property Format Example
OneFuse_VmNic<#>.<value> See examples below

Replace <#> with a number from 0 to 9, one for each NIC.

Replace <value> with an appropriate key: assignment, dnsServers, dnsSuffix, fqdn, gateway, hostname, ipAddress, label, mac, network, nicLabel, target

Examples:

  • OneFuse_VmNic0.dnsSuffix
  • OneFuse_VmNic0.fqdn
  • OneFuse_VmNic0.hostname
  • OneFuse_VmNic0.ipAddress
  • OneFuse_VmNic0.target: when DNS Suffix is provided, will be the FQDN; otherwise, will be the hostname (without domain).

Purpose: Reference VM hardware information: cpu, memory, etc.

Property Format Example
OneFuse_VmHardware.<value> See examples below

Replace <value> with an appropriate key: cpuCount, memoryGB, memoryMB, platformUuid, powerState, totalStorageGB

Examples:

  • OneFuse_VmHardware.cpuCount
  • OneFuse_VmHardware.memoryGB
  • OneFuse_VmHardware.platformUuid
  • OneFuse_VmHardware.powerState
  • OneFuse_VmHardware.totalStorageGB

Provision

Deploy a Blueprint with OneFuse DNS Policies configured. DNS Record(s) will get registered in the desired DNS Provider.

Outputs

The following parameter will have the generated OneFuse DNS Managed Object as a JSON string on the resource.

Parameter Name Parameter Value Format
OneFuse_Dns_Nic# (where # is a number 0–9) JSON string of OneFuse DNS Managed Object

Deprovision

Destroy an existing resource with OneFuse DNS Policies configured. The DNS record(s) will be unregistered from the desired DNS Provider.

Trigger points

Job / Process Trigger Point Name Run Sequence Plugin Action Name
Provision Server Pre-Create Resource 1300 OneFuse - Provision DNS
Delete Server Post-Delete 1300 OneFuse - De-Provision DNS