DNS

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

Prerequisites

1. Configure OneFuse Property Set(s) and OneFuse Module Policies.
2. Run OneFuse Configuration per Cloud Assembly Organization.
3. Review an overview on OneFuse modules with Aria Automation 8.1+/Cloud.
4. Create a new Cloud Template (if none exist) or determine which existing Cloud Template(s) will utilize this OneFuse Module.
   • Resource: Designing your vRealize Automation Cloud Assembly deployments

Steps

1. Know the name of the OneFuse Endpoint created via OneFuse Configuration.
2. Determine which OneFuse DNS Policies to run for this Cloud Template.
3. Update the Cloud Template to add in the necessary vRA Properties and/or add in the Custom Resource to invoke a OneFuse DNS Policy.
4. Deploy the Cloud Template to provision a vRA Deployment and register DNS Record(s).
5. Destroy the vRA Deployment to remove the DNS Record(s) for the destroyed resource(s).

Update the Cloud Template

1. Log in to vRA > Cloud Assembly
2. Select the Design tab from the top menu bar
3. Select the Cloud Templates tab from the left menu
4. Edit the Cloud Template and perform the below:

Option 1: Add in necessary vRA Property

The following vRA Property needs to be added to the Cloud Template’s Code section under the Resource(s) of interest.

Call a DNS Policy for a specific NIC:

Example YAML:

# Execute OneFuse DNS Policy

# -- Property Value
# <OneFuse Endpoint Name>  is onefuse
# <DNS Policy Name> is prod

name: Simple Example
resources:
  Cloud_Machine_1:
    type: Cloud.Machine
    properties:
      image: CentOS7
      flavor: small
      count: 1
      OneFuse_DnsPolicy_Nic0: 'onefuse:prod'

Optional. DNS registration for additional IPs:

Support for registering in DNS for multiple IP Addresses on a single interface. The DNS Records are reserved and stored in both OneFuse and vRA Machine Properties for future reference in vRA lifecycles.

• Replace <niclabel> with a value that is appended to the hostname.
• Default behavior appends <niclabel> to the hostname after a hyphen (-). To override this behavior, modify the Hostname Override field on the OneFuse DNS Policy.
• Without Additional Naming Property: default behavior of the <niclabel> is to get appended to the hostname after a hyphen (-). To override this behavior, modify the field Hostname Override on the OneFuse IPAM Policy.
• With Additional Naming Property: if an Additional Naming Policy is defined that matches this value, the name generated from the Naming Policy will be used.
• When listing multiple DNS Suffixes, comma separate the values without any spaces.

Optional. IP address not using OneFuse IPAM Module:

Use the following optional vRA Property in the event IP addresses are obtained without using OneFuse IPAM and the user wants to register those IP addresses in DNS.

Example YAML:

# -- Property Name
# <niclabel> is xyz

# -- Property Value
# <OneFuse Endpoint Name>  is onefuse
# <OneFuse DNS Policy Name> is prod
# <DNS Suffix(es)> is example.com

# Example
OneFuse_DnsPolicy_AdditionalTrigger: 'true'
OneFuse_DnsPolicy_Additional_xyz: 'onefuse:prod:example.com'

# Example not using OneFuse IPAM for registering additional IP
OneFuse_IP_Additional_xyz: '10.11.11.11'

# Example Output assuming the hostname is 'server12'
# > server12-xyz.example.com

Additional helpful vRA properties

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

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

Example Cloud Template YAML code

# Execute OneFuse DNS Policy

# -- Property Value
# <OneFuse Endpoint Name>  is onefuse
# <DNS Policy Name> is prod

name: Simple Example
resources:
  Cloud_Machine_1:
    type: Cloud.Machine
    properties:
      image: CentOS7
      flavor: small
      count: 1
      OneFuse_DnsPolicy_Nic0: 'onefuse:prod'

Option 2: Add in Custom Resource for OneFuse DNS

• From the Resource Types navigation expand Custom Resources
• Drag-and-drop OneFuse:DNS_v1 to the canvas
• In the Code tab, provide values for the following properties:

DNS-specific parameters:

Provision

Deploy a Cloud Template with OneFuse DNS Policies configured. DNS Record(s) will register in the desired DNS Provider.

Outputs

The following vRA Properties will exist on the Deployment.

Deprovision

Destroy an existing deployment with OneFuse DNS Policies configured. The DNS Record(s) will be removed from the desired DNS Provider.

vRA EBS

Troubleshooting

Troubleshoot in vRealize Orchestrator.

1. Log in to vRealize Orchestrator.
2. Turn on Verbose Logging and try again to see additional log messages in vRO Workflows:
   • Select Library > Workflows from the left menu
   • Go to: OneFuse > DNS > vRA8 to find corresponding workflow runs and view logs
   • Optionally, run the workflows in the Manual folder to manually test
3. Optionally, configure timeouts for EBS and/or Configure timeouts for OneFuse modules.

Troubleshooting common errors

• Error: message": "Policy action job '<GUID>' failed: 'NoneType' object has no attribute 'has_failures'; details: None"
  • The most likely cause for this error is when DNS Suffix(es) were not provided for the vRA Property Value.
  • Refer to this section for an example on the expected format.

Additional resources:

• Review Troubleshooting in OneFuse
• Review VMware troubleshooting resources