Hi there,
When comparing Edge Cluster builds between AVN (Automation via Network) and Custom options, the key differences often lie in the level of automation and customization available:
AVN (Automation via Network): Typically involves automated provisioning and configuration of Edge Clusters using predefined templates or workflows. This approach streamlines deployment with standardized configurations, potentially reducing setup time and complexity.
Custom Build: Offers greater flexibility and control over specific configurations and components within the Edge Cluster. It allows for tailored setups based on unique requirements, which might include specific integrations or custom network architectures.
Regarding ARIA deployment with a custom Edge Cluster deployed via API (Edge Cluster - empty), it's important to verify compatibility and support for ARIA deployment. Custom setups deployed via API can support ARIA deployment, provided that the API allows for the necessary configurations and integrations required by ARIA.
For precise details on ARIA deployment compatibility and specific configurations, I recommend consulting Broadcom's documentation or reaching out to their support team for detailed guidance tailored to your deployment scenario.
Hope this clarifies things!
Original Message:
Sent: Jun 26, 2024 08:38 AM
From: tckoon
Subject: VCF NSX Edge Clusters - Deployment Option (AVN / Custom / API)
HI all,
I would like to understand the different between Edge Cluster build if we opts for AVN vs Custom ? From diagram I see both design are the same.
If customised Edge Cluster was deploy via API (Edge Cluster - empty) , it is support ARIA deployment ?