Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

Commit

Permalink
Replacement for AVS portion of Pull 404 (#442)
Browse files Browse the repository at this point in the history
  • Loading branch information
sblair01 authored Apr 4, 2024
1 parent b3b2d9c commit bcb0a94
Show file tree
Hide file tree
Showing 5 changed files with 17 additions and 13 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ The presented resiliency recommendations in this guidance include Azure VMware S
| Recommendation | Category | Impact | State | ARG Query Available |
| :------------------------------------------------ | :---------------------------------------------------------------------: | :------: | :------: | :------: |
|[AVS-1 - Configure Azure Service Health notifications and alerts for Azure VMware Solution](#avs-1---configure-azure-service-health-notifications-and-alerts-for-azure-vmware-solution) | Monitoring | High | Verified | Yes |
|[AVS-2 - Configure Syslog in Diagnostic Settings for Azure VMware Solution](#avs-2---configure-syslog-in-diagnostic-settings-for-azure-vmware-solution) | Monitoring | Medium | Verified | Yes |
|[AVS-2 - Configure Syslog in Diagnostic Settings for Azure VMware Solution](#avs-2---configure-syslog-in-diagnostic-settings-for-azure-vmware-solution) | Monitoring | Medium | Verified | No |
|[AVS-3 - Configure Azure Monitor Alert warning thresholds for vSAN datastore utilization](#avs-3---configure-azure-monitor-alert-warning-thresholds-for-vsan-datastore-utilization) | Monitoring | High | Verified | No |
|[AVS-4 - Enable Stretched Clusters for Multi-AZ Availability of the vSAN Datastore](#avs-4---enable-stretched-clusters-for-multi-az-availability-of-the-vsan-datastore) | Availability | Low | Verified | Yes |
|[AVS-5 - Monitor CPU Utilization to ensure sufficient resources for workloads](#avs-5---monitor-cpu-utilization-to-ensure-sufficient-resources-for-workloads) | Monitoring | Medium | Verified | Yes |
Expand All @@ -24,16 +24,20 @@ The presented resiliency recommendations in this guidance include Azure VMware S
|[AVS-8 - Monitor when Azure VMware Solution Private Cloud is reaching the capacity limit](#avs-8---monitor-when-azure-vmware-solution-private-cloud-is-reaching-the-capacity-limit) | Monitoring | Medium | Verified | No |
|[AVS-9 - Apply Resource delete lock on the resource group hosting the private cloud](#avs-9---apply-resource-delete-lock-on-the-resource-group-hosting-the-private-cloud) | Governance | High | Verified | No |
|[AVS-10 - Align ExpressRoute configuration with best practices for circuit resilience](#avs-10---align-expressroute-configuration-with-best-practices-for-circuit-resilience) | Networking | High | Preview | No |
|[AVS-11 - Deploy two or more circuits in different peering locations when using stretched clusters](#avs-11---deploy-two-or-more-circuits-in-different-peering-locations-when-using-stretched-clusters) | Networking | High | Preview | No |
|[AVS-12 - Deploy two Azure VMware Solution private clouds in different regions for geographical disaster recovery](#avs-12---deploy-two-azure-vmware-solution-private-clouds-in-different-regions-for-geographical-disaster-recovery) | Disaster Recovery | High | Preview | No |
|[AVS-13 - Use the AVS Interconnect feature to connect private clouds in different availability zones](#avs-13---use-the-avs-interconnect-feature-to-connect-private-clouds-in-different-availability-zones) | Storage | High | Preview | No |
|[AVS-11 - Deploy two or more circuits in different peering locations when using stretched clusters](#avs-11---deploy-two-or-more-circuits-in-different-peering-locations-when-using-stretched-clusters) | Networking | High | Verified | No |
|[AVS-12 - Deploy two Azure VMware Solution private clouds in different regions for geographical disaster recovery](#avs-12---deploy-two-azure-vmware-solution-private-clouds-in-different-regions-for-geographical-disaster-recovery) | Disaster Recovery | High | Verified | No |
|[AVS-13 - Use the AVS Interconnect feature to connect private clouds in different availability zones](#avs-13---use-the-avs-interconnect-feature-to-connect-private-clouds-in-different-availability-zones) | Storage | High | Verified | No |
|[AVS-14 - Use key autorotation for vSAN datastore customer-managed keys](#avs-14---use-key-autorotation-for-vsan-datastore-customer-managed-keys) | Storage | High | Preview | No |
|[AVS-15 - Configure LDAPS Identity integration with two sources for NSX and vCenter Server management consoles](#avs-15---configure-ldaps-identity-integration-with-two-sources-for-nsx-and-vcenter-server-management-consoles) | Storage | High | Preview | No |
|[AVS-16 - Use HCX Network Extension High Availability](#avs-16---use-hcx-network-extension-high-availability) | Availability | High | Preview | No |
|[AVS-17 - Verify Management Networks are not extended with HCX Network Extension](#avs-17---verify-management-networks-are-not-extended-with-hcx-network-extension) | Networking | High | Preview | No |
|[AVS-15 - Configure LDAPS Identity integration with two sources for NSX and vCenter Server management consoles](#avs-15---configure-ldaps-identity-integration-with-two-sources-for-nsx-and-vcenter-server-management-consoles) | Storage | High | Verified | No |
|[AVS-16 - Use HCX Network Extension High Availability](#avs-16---use-hcx-network-extension-high-availability) | Availability | High | Verified | No |
|[AVS-17 - Verify Management Networks are not extended with HCX Network Extension](#avs-17---verify-management-networks-are-not-extended-with-hcx-network-extension) | Networking | High | Verified | No |
|[AVS-18 - Use multiple DNS servers per private FQDN zone](#avs-18---use-multiple-dns-servers-per-private-fqdn-zone) | Networking | High | Preview | No |
|[AVS-19 - Verify vSAN FTT configuration aligns with the cluster size](#avs-19---verify-vsan-ftt-configuration-aligns-with-the-cluster-size) | Application Resilience | High | Preview | No |

|[AVS-19 - Verify vSAN FTT configuration aligns with the cluster size](#avs-19---verify-vsan-ftt-configuration-aligns-with-the-cluster-size) | Application Resilience | Medium | Verified | No |
| [ERCON-1 For Connections using ExpressRoute Direct circuits and UltraPerformance or ErGw3AZ ExpressRoute Gateways, enable FastPath to improve data path performance between your private cloud network and your virtual network](https://azure.github.io/Azure-Proactive-Resiliency-Library/services/networking/expressroute-connection/#ercon-1---for-connections-using-expressroute-direct-circuits-and-ultraperformance-or-ergw3az-expressroute-gateways-enable-fastpath-to-improve-data-path-performance-between-your-on-premises-network-and-your-virtual-network) | Networking | High | Verified | No
| [ERCON-2 Configure an Azure Resource Lock on connections to prevent accidental deletion](https://azure.github.io/Azure-Proactive-Resiliency-Library/services/networking/expressroute-connection/#ercon-2---configure-an-azure-resource-lock-on-connections-to-prevent-accidental-deletion) | Availability | High | Verified | No
| [ERGW-3 - Configure an Azure Resource lock for ExpressRoute Gateway to prevent accidental deletion](https://azure.github.io/Azure-Proactive-Resiliency-Library/services/networking/expressroute-gateway/#ergw-3---configure-an-azure-resource-lock-for-expressroute-gateway-to-prevent-accidental-deletion) | Availability | Medium | Verified | No |
| [ERGW-4 - Monitor gateway health](https://azure.github.io/Azure-Proactive-Resiliency-Library/services/networking/expressroute-gateway/#ergw-4---monitor-gateway-health) | Monitoring | High | Verified | No |
| [ERGW-7 - Configure customer-controlled gateway maintenance - In Preview](https://azure.github.io/Azure-Proactive-Resiliency-Library/services/networking/expressroute-gateway/#ergw-7---configure-customer-controlled-gateway-maintenance---in-preview) | Networking | High | Verified | No |

{{< /table >}}

Expand Down
Original file line number Diff line number Diff line change
@@ -1 +1 @@
// under-development
// cannot be validated with ARG
Original file line number Diff line number Diff line change
@@ -1 +1 @@
// under-development
// cannot be validated with ARG
Original file line number Diff line number Diff line change
@@ -1 +1 @@
// under-development
// cannot be validated with ARG
Original file line number Diff line number Diff line change
@@ -1 +1 @@
// under-development
// cannot be validated with ARG

0 comments on commit bcb0a94

Please sign in to comment.