Configure Ansible as Post Provision Script - Support and Troubleshooting

Configure Ansible as Post Provision Script Table of Contents Overview Goals Prerequisites The process to Configure Ansible as Post-Provision Script RegisterNode: Post Provisioning Script ExecuteConfigPackages: Post Provisioning Script Key Values to be modified Additional Information Overview Cloud Provisioning and Governance Platform from ServiceNow is flexible to execute the Ansible playbooks post provisioning a VM, configuring the Post Provisioning Scripts for Ansible a bit different from the regular process

General Reference:

Create post-provision operations Example: Post-provision cloud script Pre and Post Provision operation with Templates Goals Step by Step configuration of Post Provisioning Scripts with Ansible

Prerequisites ServiceNow Instance with below Plugins Activated

Discovery Cloud API Cloud Config Management Cloud Management Cloud Management Core

User with Cloud Admin/Discovery Admin Role. MID Server Up and Running and Validated, no Firewall blocks for Azure/AWS API/ Ansible API Communication Create the Azure Credentials Reference: Store the Azure service principal credentials in the instance

Create a Service Account for Azure Reference: Add an Azure service account

Create a Cloud Account for Azure Reference: Set up a cloud account for Azure

Discover the Azure Resource from Cloud Account Reference: Azure Cloud Discovery

Discover the Ansible Tower Reference: Ansible configuration management provider and run Discovery

Create a Catalog from ARM Template Reference: Creating a Catalog Item from ARM Template The process to Configure Ansible as Post-Provision Script Create a Catalog from ARM Template. Reference: Creating a Catalog Item from ARM Template

Once the Catalog Created and Validated Successfully, the Post Provisioning Scripts will be available.

RegisterNode: Post Provisioning Script Click New under the Post Provisioning Scripts

Step Type: CAPI CAPI Provider: Ansible-Tower CAPI Method: RegisterNode CAPI Version: 1.0 Order: 100 Enabled: True

Save the Record After the Saving the Record the Display will auto-populate

ConfigScript ConfigMgmtProviderInfo AdditionalParameters NodeCredentials ConfigScriptType NodeAddress

By Default, the Key-Value Parameters are auto Populated, the user needs to change the values according to the requirement ExecuteConfigPackages: Post Provisioning Script Click New under the Post Provisioning Scripts Step Type: CAPI CAPI Provider: Ansible-Tower CAPI Method: ExecuteConfigPackages CAPI Version: 1.0 Order: 200 Enabled: True

Save the Record After the Saving the Record the Display will auto-populate Key Values ConfigScript ConfigMgmtProviderInfo AdditionalParameters NodeCredentials ConfigScriptType NodeAddress By Default, the Key-Value Parameters are auto Populated, the user needs to change the values according to the requirement Key Values to be modified ConfigMgmtProviderInfo

$(Script:CfgMgmtUtils.getCfgMgmtCredentials[arg=${parameter.WorkloadConfigProvider},arg=${parameter.WorkloadConfigProviderType},arg=${parameter.ManagementAttributes}])

AdditionalParameters

{"node_name":"${parameter.InstanceName}","management_attributes":[[{"name":"management_attribute","value":"Inventory"},{"name":"management_attribute_value","value":"${parameter.Inventory}"}],[{"name":"management_attribute","value":"Hostgroup"},{"name":"management_attribute_value","value":"${parameter.HostGroupPlayBoook}"}]]}

NodeAddress

{"private_ip":"${Host.StackOrchestrationInterface.CreateStack.Output.resp.outputs.DemoInstanceIPPrivate}","public_ip":"${Host.StackOrchestrationInterface.CreateStack.Output.resp.outputs.DemoInstanceIP}"}

NodeCredentials

$(capiResolver.NodeCredentialResolver#nodeCredentialId=${parameter.NodeCredentials})

ConfigScript

${parameter.ConfigScript}

ConfigScriptType

${parameter.ConfigScriptType}

Additional Information Create an Ansible configuration management provider and run Discovery