Leverage Property Toolkit Capabilities for vRA8

vRA8

Leverage Property Toolkit capabilities for vRealize Automation 8 with OneFuse as “Property Groups” to be assigned within your deployment. Additionally, the Property Sets can also call other Property Sets based on other values configured or selected from the vRA Blueprint/Cloud Template.

Use Case Summary

Create a vRealize Automation 8 blueprint that automatically sets Property Values for Flavor, IPAM Policy, DNS Policy, Active Directory OU placement, and Backup Schedule based on only two user inputs at request time:

  • OS (Linux or Windows)
  • Environment (Production or Development)

Requirements

  • A vRealize Automation blueprint Input to select the OS image of CentOS7 or Windows2019.
    • Desired result: Apply a subset of properties for the selected OS image.
  • User selection to target the deployment as either Production or Development.
    • If the deployment is a Production build, a specific IPAM and DNS Policy will be applied in lieu of a Development Build.
    • If the development is a Production build, the flavor mapping is required to be set to Medium.
    • If the deployment is a Development build, the flavor mapping is required to be set to Small.
  • All builds will apply a specific Naming and Active Directory Policy.
  • All builds will apply tags on each server indicating backup schedule, which is driven by the server classification of Production or Development.

End-User Request Properties

Property <key>:<value>YAML Input Code
“ServerType”: [Production, Development]
ServerType:
type: string
enum:
- Production
- Development
title: Server Type
“image”: [CentOS7, Windows2019]
OS:
type: string
title: OS Selection
oneOf:
- title: Cent
const: CentOS7
- title: Windows
const: Windows2019

OneFuse Static Property Set Configuration Design

Configure the Static Property Set(s) inside the OneFuse Platform to be called from the vRA8.x Blueprint Code (YAML). The blueprint code will call a single Static Property Set, which will call other Static Property Sets.

Static Property Set Group Table Design

The below table shows a breakdown of dynamically created additional SPS Groups and Properties.

First SPS GroupSubsequent SPS Group(s)JSON Properties
Build_StandardsThis Property Group is attached to the blueprint YAML which dynamically drives other SPS Groups that contain properties specific to those build types.
{
"OneFuse_NamingPolicy": "onefuse:machineNaming",
"OneFuse_SPS_OS": "Build_Standards_{{image}}",
"OneFuse_SPS_ServerType": "Build_Standards_{{ServerType}}"
}
“OneFuse_SPS_ServerType”In the JSON Properties section for the Build_Standards
 SPS Group, refer to the OneFuse_SPS_ServerType
 property which is dynamically calling the other Static Property Set using properties driven by the blueprint inputs.
{  }—->Build_Standards_Production
{
"domain": "myProductionDomain.net",
"OneFuse_ADPolicy": "onefuse:Production_AD_Policy",
"OneFuse_IpamPolicy_Nic0": "onefuse:Production_Ipam_Policy",
"OneFuse_DnsPolicy_Nic0": "onefuse:Production_DNS_Policy:{{Domain}}",
"OneFuse_CreateTags_BackupPolicy": {
"key": "Backup Schedule",
"value": "Daily"
}
}
{  }—->
Build_Standards_Development
{
"domain": "myProductionDomain.net",
"OneFuse_ADPolicy": "onefuse:Production_AD_Policy",
"OneFuse_IpamPolicy_Nic0": "onefuse:Production_Ipam_Policy",
"OneFuse_DnsPolicy_Nic0": "onefuse:Production_DNS_Policy:{{Domain}}",
"OneFuse_CreateTags_BackupPolicy": {
"key": "Backup Schedule",
"value": "Daily"
}
}
“OneFuse_SPS_OS”In the JSON Properties section for the Build_Standards SPS Group, refer to the OneFuse_SPS_OS
 property which is dynamically calling the other Static Property Set using properties driven by the blueprint inputs.
{  }—->Build_Standards_CentOS7
{
"customizationSpec": "linux_{{domain}}"
}
{  }—->Build_Standards_CentOS7
{
"customizationSpec": "windows_{{domain}}"
}

Visual Representation of Design

Create the Static Property Sets in OneFuse

In the OneFuse Platform, create the Static Property Sets using the example OneFuse Static Property Set Configuration Design JSON Properties.

Configure the vRealize Automation 8 Blueprint

  1. Create a new vRA8 Design.
  2. Insert the following into the Code section:
    • Note: Commented out lines in the YAML code provide information about the YAML properties.
inputs:
  ServerType:
    type: string
    enum:
      - Production
      - Development
    title: Server Type
  OS:
    type: string
    title: OS Selection
    oneOf:
      - title: Cent
        const: CentOS7
      - title: Windows
        const: Windows2019
resources:
  Cloud_Machine_1:
    type: Cloud.Machine
    properties:
    # Input of the image to call. Ensure these options are mapped accordingly inside the vRA8 Infrastructure Image Mappings
      image: '${input.OS}'
    # Required using a Cloud Agnostic Machine. However, the SPS Group will override this setting
      flavor: Small
    # Input of ServerType which is used in subsequent SPS group properties
      ServerType: '${input.ServerType}'
    # Set the property to call Property Toolkit/SPS Groups
      OneFuse_PropertyToolkit: 'onefuse:true'
    # Declare the SPS Group
      OneFuse_SPS_Standards: Build_Standards
    # Assign the domain for the field
      Domain: 'mydomain.com'

Want to try out OneFuse with vRA for yourself? Check out the WWT Hands on Lab Accelerating vRealize Automation 8.x with OneFuse.

Questions or comments? Visit our

Comments are closed.

Skip to toolbar