VCF 9 Automation vs Aria Automation 8.x (Part 2)

-

 

6. CI/CD and Automation Pipelines

Aria Automation 8.x

  • Relied heavily on Code Stream

  • Pipelines required more manual configuration

  • Less visibility into infra lifecycle state

VCF 9 Automation

  • CI/CD aligns with VCF lifecycle events

  • Pipelines are more context-aware

  • Better integration with platform operations

Outcome:
Automation pipelines become smarter, not just faster.


7. Operational Visibility & Troubleshooting

Aria Automation 8.x

  • Logs and troubleshooting often siloed

  • Required jumping across products

  • Root cause analysis was time-consuming

VCF 9 Automation

  • Better correlation with VCF components

  • Improved visibility across automation actions

  • Faster troubleshooting due to platform context

Ops Benefit:
Reduced MTTR for automation-related issues.


8. Customization vs Standardization

Aria Automation 8.x

  • Highly customizable

  • Flexibility often led to automation sprawl

  • Difficult to standardize across teams

VCF 9 Automation

  • Encourages standardized automation patterns

  • Customization still possible, but controlled

  • Easier to scale automation across the organization

Trade-off:
Slightly less freedom → significantly more stability.


9. Target Audience Shift

Aspect

Aria Automation 8.x

VCF 9 Automation

Primary Users

Automation engineers

Platform teams

Focus

Self-service

Cloud operations

Scale

Project-level

Enterprise-level

Governance

Optional

Built-in


Summary

Choose Aria Automation 8.x if:

  • You need maximum customization

  • You run automation outside full VCF

  • You manage smaller or mixed environments

Choose VCF 9 Automation if:

  • You operate VMware Cloud Foundation

  • You want platform-native automation

  • You value stability, governance, and lifecycle alignment

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