Skip to content

Commit

Permalink
docs: update specialized workload recommendations resource type (#595)
Browse files Browse the repository at this point in the history
Co-authored-by: ejhenry <[email protected]>
Co-authored-by: Zach Trocinski <[email protected]>
  • Loading branch information
3 people authored Dec 20, 2024
1 parent ba81e0e commit 6357d0f
Show file tree
Hide file tree
Showing 8 changed files with 124 additions and 123 deletions.
2 changes: 1 addition & 1 deletion .github/scripts/schemas/aprl-schema.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ recommendation:
potentialBenefits: str(max=60)
pgVerified: bool()
automationAvailable: bool()
tags: null()
tags: any(enum('AI','AVD', 'AVS', 'HPC', 'SAP'), null())
learnMoreLink: list(include('linkItem'), required=False, min=1)

linkItem:
Expand Down
102 changes: 51 additions & 51 deletions azure-specialized-workloads/avd/recommendations.yaml

Large diffs are not rendered by default.

32 changes: 16 additions & 16 deletions azure-specialized-workloads/avs/recommendations.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3,14 +3,14 @@
recommendationTypeId: null
recommendationControl: HighAvailability
recommendationImpact: High
recommendationResourceType: Specialized.Workload/AVS
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
Use the Interconnect feature for direct communication between private clouds in different availability zones, enabling connectivity between the private clouds management and workload networks.
potentialBenefits: Enhanced private cloud connectivity
pgVerified: true
automationAvailable: false
tags: null
tags: AVS
learnMoreLink:
- name: Connect Private Clouds in the same region
url: "https://learn.microsoft.com/en-us/azure/azure-vmware/connect-multiple-private-clouds-same-region"
Expand All @@ -20,14 +20,14 @@
recommendationTypeId: null
recommendationControl: Security
recommendationImpact: High
recommendationResourceType: Specialized.Workload/AVS
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
Ensure two external identity sources are configured for NSX and vCenter Server. The VMware vCenter Server and NSX Manager use these for authentication with external identities.
potentialBenefits: Continuous login access during maintenances
pgVerified: true
automationAvailable: false
tags: null
tags: AVS
learnMoreLink:
- name: Set an external identity source for vCenter
url: "https://learn.microsoft.com/en-us/azure/azure-vmware/configure-identity-source-vcenter"
Expand All @@ -39,14 +39,14 @@
recommendationTypeId: null
recommendationControl: HighAvailability
recommendationImpact: High
recommendationResourceType: Specialized.Workload/AVS
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
Enable Network Extension High Availability for appliance failure tolerance in HCX service. It pairs selected appliances for Active Standby configuration, ensuring high availability and quick recovery, keeping configurations in-service despite failures.
potentialBenefits: Improves HCX service continuity
pgVerified: true
automationAvailable: false
tags: null
tags: AVS
learnMoreLink:
- name: HCX Network extension high availability
url: "https://learn.microsoft.com/en-us/azure/azure-vmware/configure-hcx-network-extension-high-availability"
Expand All @@ -58,14 +58,14 @@
recommendationTypeId: null
recommendationControl: OtherBestPractices
recommendationImpact: High
recommendationResourceType: Specialized.Workload/AVS
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
Do not extend the network used by the HCX Management devices to ensure the network's security and stability.
potentialBenefits: Enhanced network safety and performance
pgVerified: true
automationAvailable: false
tags: null
tags: AVS
learnMoreLink:
- name: Requirements for Network Extension
url: "https://docs.vmware.com/en/VMware-HCX/4.8/hcx-user-guide/GUID-0C746416-850E-46F7-85DD-4D4326A23785.html"
Expand All @@ -75,14 +75,14 @@
recommendationTypeId: null
recommendationControl: HighAvailability
recommendationImpact: High
recommendationResourceType: Specialized.Workload/AVS
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
The Azure VMware Solution's service SLA is influenced by vSAN storage policies, which change based on cluster size. For clusters over 6 hosts, an FTT-2 policy (RAID-1 or RAID-6) is advised. FTT refers to the Fault Tolerance feature.
potentialBenefits: Enhanced cluster reliability
pgVerified: true
automationAvailable: false
tags: null
tags: AVS
learnMoreLink:
- name: Use fault domains
url: "https://learn.microsoft.com/en-us/azure/well-architected/azure-vmware/application-platform#use-fault-domains"
Expand All @@ -94,14 +94,14 @@
recommendationTypeId: null
recommendationControl: HighAvailability
recommendationImpact: High
recommendationResourceType: Specialized.Workload/AVS
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
Microsoft suggests using two or more ExpressRoute circuits at distinct peering locations for critical workloads. Connect these circuits and your Azure VMware Solutions private clouds using Global Reach.
potentialBenefits: Enhanced circuit resilience for Azure VMware
pgVerified: true
automationAvailable: false
tags: null
tags: AVS
learnMoreLink:
- name: APRL guidance for ExpressRoute circuits
url: "https://azure.github.io/Azure-Proactive-Resiliency-Library/services/networking/expressroute-circuits"
Expand All @@ -113,14 +113,14 @@
recommendationTypeId: null
recommendationControl: HighAvailability
recommendationImpact: High
recommendationResourceType: Specialized.Workload/AVS
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
Azure VMware Solution vSAN stretched clusters cover 2 Availability Zones plus a third for witness. Use ExpressRoute for added resilience by deploying two circuits in different locations. With Global Reach, create a mesh topology by connecting on-premises circuits to Azure's managed circuits.
potentialBenefits: Enhanced resilience and connectivity
pgVerified: true
automationAvailable: false
tags: null
tags: AVS
learnMoreLink:
- name: Deploy vSAN streched cluster
url: "https://learn.microsoft.com/en-us/azure/azure-vmware/deploy-vsan-stretched-clusters#deploy-a-stretched-cluster-private-cloud"
Expand All @@ -130,14 +130,14 @@
recommendationTypeId: null
recommendationControl: DisasterRecovery
recommendationImpact: High
recommendationResourceType: Specialized.Workload/AVS
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
Two Azure VMware Solution private clouds can be deployed in different regions for business continuity, implementing a mesh network topology based on ExpressRoute Gateway Connections and Global Reach Connections.
potentialBenefits: Enhanced disaster recovery
pgVerified: true
automationAvailable: false
tags: null
tags: AVS
learnMoreLink:
- name: Private Clouds in two regions
url: "https://learn.microsoft.com/en-us/azure/azure-vmware/move-azure-vmware-solution-across-regions"
Expand Down
16 changes: 8 additions & 8 deletions azure-specialized-workloads/hpc/recommendations.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3,14 +3,14 @@
recommendationTypeId: null
recommendationControl: HighAvailability
recommendationImpact: High
recommendationResourceType: Specialized.Workload/HPC
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
Currently in all HPC Pack ARM templates we create the cluster share on one of the head node which is not highly available.
potentialBenefits: Enhances job metadata availability
pgVerified: false
automationAvailable: false
tags: null
tags: HPC
learnMoreLink:
- name: Learn More
url: "https://learn.microsoft.com/en-us/powershell/high-performance-computing/hpcpack-ha-cloud?view=hpc19-ps#hpc-pack-cluster-shares"
Expand All @@ -20,14 +20,14 @@
recommendationTypeId: null
recommendationControl: Scalability
recommendationImpact: Medium
recommendationResourceType: Specialized.Workload/HPC
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
By deploying Azure "burst" nodes (both Windows and Linux) in your HPC Pack cluster or creating your HPC Pack cluster in Azure, you can automatically grow or shrink the cluster's resources such as nodes or cores according to the workload on the cluster.
potentialBenefits: Efficient, uninterrupted execution
pgVerified: false
automationAvailable: false
tags: null
tags: HPC
learnMoreLink:
- name: Learn More
url: "https://learn.microsoft.com/en-us/powershell/high-performance-computing/hpcpack-auto-grow-shrink?view=hpc19-ps"
Expand All @@ -37,14 +37,14 @@
recommendationTypeId: null
recommendationControl: HighAvailability
recommendationImpact: Medium
recommendationResourceType: Specialized.Workload/HPC
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
Establish a cluster with a minimum of two head nodes. In the event of a head node failure, the active HPC Service will be automatically transferred from the affected head node to another functioning one.
potentialBenefits: Enhanced reliability for HPC
pgVerified: false
automationAvailable: false
tags: null
tags: HPC
learnMoreLink:
- name: Learn More
url: "https://learn.microsoft.com/en-us/powershell/high-performance-computing/hpcpack-ha-cloud?view=hpc19-ps#dealing-with-head-node-failure"
Expand All @@ -54,14 +54,14 @@
recommendationTypeId: null
recommendationControl: HighAvailability
recommendationImpact: High
recommendationResourceType: Specialized.Workload/HPC
recommendationResourceType: Microsoft.Subscription/subscriptions
recommendationMetadataState: Active
longDescription: |
When HPC failed to connect to the Domain controller, admin and user will not be able to connect to the HPC Service thus not able to manage and submit jobs to the cluster.
potentialBenefits: Enhanced reliability and job management
pgVerified: false
automationAvailable: false
tags: null
tags: HPC
learnMoreLink:
- name: Learn More
url: "https://learn.microsoft.com/en-us/powershell/high-performance-computing/hpcpack-ha-cloud?view=hpc19-ps#dealing-with-ad-failure"
Loading

0 comments on commit 6357d0f

Please sign in to comment.