Automating Red Hat Satellite Onboarding for vRA-Provisioned VMs

-

 In modern datacenter operations, automation plays a critical role in improving accuracy, reducing manual workloads, and increasing operational efficiency. When tenants provision virtual machines using VMware Aria Automation (vRA), it is often necessary to ensure that these systems are properly registered and managed through Red Hat Satellite Server for patching, compliance, and lifecycle operations.

This article explains an automated workflow that integrates vRA, vCenter, vRealize Orchestrator (vRO), and Red Hat Satellite, enabling seamless onboarding of newly provisioned Linux VMs.


Why Automate the Satellite Onboarding Process?

Without automation, administrators must manually:

  • Verify VM creation in vCenter

  • Register the host in Satellite

  • Apply activation keys

  • Associate lifecycle environments

  • Confirm subscription status

Automation eliminates errors and speeds up operations by ensuring these tasks happen automatically during deployment.


End-to-End Workflow Overview

The process begins when a tenant provisions a VM from the vRA catalog. A vRA event subscription triggers a vRO workflow that validates the VM and registers it into Satellite.


1. VM Provisioned by Tenant via vRA

After the VM is deployed from the vRA blueprint, a Compute Post Provision event triggers the onboarding workflow.

2. Validate VM Exists in vCenter

The workflow checks:

  • VM presence in vCenter

  • Power state

  • Guest hostname

  • Optional: Assigned IP address

If the VM is found, the process continues.  If not, a failure status is returned to vRA

3. Register (Onboard) the VM into Red Hat Satellite

Using Satellite REST APIs, the automation performs:

  • Host creation

  • Activation Key assignment

  • Organization and Location selection

  • Content View and Lifecycle Environment mapping

  • Subscription attachment

  • Status verification

This ensures the VM becomes fully managed by Satellite.

4. Update vRA if VM Not Found

If the VM does not exist in vCenter:

  • The workflow terminates

  • vRA deployment status is updated with “VM not found in vCenter”

  • Tenant receives visibility of the failure

5. Update vRA on Successful Satellite Registration

If registration is successful:

  • vRO posts the Satellite Host ID back to vRA

  • Deployment status shows “Successfully onboarded to Red Hat Satellite Server”

  • All logs are recorded for auditing


Flow Diagram



Key Benefits of This Automation

  • Eliminates manual Satellite registration

  • Provides consistent onboarding

  • Improves accuracy and reduces configuration drift

  • Offers full deployment visibility through vRA

  • Ensures compliance and lifecycle management from Day 1


Output Workflow Images:

Image 1. Virtual Server Requesting from Aria Automation

This image represents the initial phase where the tenant submits a new VM request from the vRA Service Catalog.
It shows:

  • Catalog item selection

  • Input form details



Image 2. vRO Workflow Input

This image displays what happens when vRA triggers the vRO workflow using an Event Subscription.


It includes:

  • Workflow name

  • Input parameters (VM Name, Deployment ID, Tenant, IP Address, OS Type, etc.)

  • Payload preview



Image 3. vRO Workflow Run Successfully Completed

This image shows the workflow execution inside vRO:

  • All workflow steps completed

  • REST API calls to Satellite successful

  • Validation logs confirming vCenter discovery

  • Registration completed without errors



Image 4. vRO Workflow Output for Your Reference

This image highlights the workflow's final output:

  • Satellite Host ID

  • Return status (Success / Failed)

  • Additional information (Lifecycle environment, Activation key)

  • Output variables returned to vRA




Image 5. vRA Request Completed Successfully

This image shows the vRA deployment page after workflow completion:

  • Deployment status updated

  • Status message like:
    “Successfully onboarded to Red Hat Satellite Server”

  • Event logs referencing vRO workflow execution





Image 6. After VM Provision – Guest OS Level Repo Enabled for Satellite Onboarding

This final image shows the OS-level configuration inside the VM:

  • Repository enablement script executed

  • Yum/dnf repo list updated

  • System now ready for Satellite registration

  • Repository configuration validated




Conclusion

By integrating VMware Aria Automation with Red Hat Satellite Server, organizations can achieve a fully automated, reliable, and scalable onboarding process for newly provisioned VMs. This enhances operational efficiency and ensures that all systems are properly managed from the moment they are created.


Further Automation

If you need enhancements or additional automation features, feel free to reach out. Your feedback and suggestions are always welcome! HashtagForge


Comments

Post a Comment

Popular posts from this blog

Creating Snapshots for Unmanaged VMs in Aria Automation (vRealize Automation)

-
Image
 In multi-tenant environments powered by Aria Automation (vRealize Automation) , it's common for tenants to occasionally request snapshots for unmanaged virtual machines (VMs) . These unmanaged VMs exist in vCenter but are not provisioned through vRA and therefore fall outside the standard automation lifecycle. To address this need without impacting the broader environment or other tenants, we implemented a dedicated catalog item that allows tenants to safely request snapshots for their unmanaged VMs— securely, in isolation, and with auditability . Here’s how we approached this solution using a custom workflow and catalog configuration in Aria Automation. The Challenge Tenants may operate legacy or externally imported VMs that are not managed via vRA’s provisioning engine. Creating snapshots for these VMs traditionally requires manual intervention from infrastructure teams, which: Increases support overhead Introduces potential human errors Offers ...
Read more

Bulk import security policies into Palo Alto Networks firewalls

-
Image
To bulk import security policies into Palo Alto Networks firewalls, you'll typically need to leverage the Palo Alto API or CLI with a script. I am using an Excel file (XLS), IP address validation, and mapping source and destination zones, for comprehensive solution to automate the process. 1. Input from XLSX File : You will first need to read the data from the XLS file. 2. Check for Existing Rules : Before creating new rules, you should check if similar rules already exist on the firewall. This could be done by comparing the rule names, source, and destination IPs, and zones. 3. Mapping Source Zone and Destination Zone : Ensure that the source and destination zones are correctly mapped according to your firewall configuration. 4. IP Address Validation : Before adding a rule, you'll need to validate that the IP addresses specified in the file are valid 📝  Flow Diagram  (Text Representation) Further Automation If you need enhancements or additional automation features , fee...
Read more

Automating Tag Creation & Assignment to VMs with vRA + vRO

-
Image
  Use Case Summary A user provisions a VM from vRA. Once the VM is deployed in vCenter , a vRO workflow is triggered via Event Broker subscription. The workflow: Checks if the Tag exists (using REST API to NSX-T). If not found, creates the Tag under the correct category. Assigns the Tag to the newly provisioned VM. This eliminates the need for manual intervention and ensures every VM is tagged correctly for policies, automation, and visibility . High-Level Flow VM Provisioning in vRA User requests VM with required details (e.g., Environment, Owner, Application). Event Broker Subscription After provisioning, vRA triggers a vRO workflow . vRO Workflow Actions Connects to vCenter using REST API. Checks if Tag exists. If exists → Skip creation. If not exists → Create new Tag under category. Assigns Tag to the VM. Result VM is provisioned with the right tags automatically applied . Flow Diagram Steps Start VM Prov...
Read more