Skip to content

Commit 457e50e

Browse files
sethmanheimsethmanheim
authored
Sync release-ash-2501 with main
Sync release-ash-2501 with main
2 parents c33d423 + d22aed4 commit 457e50e

File tree

7 files changed

+109
-6
lines changed

7 files changed

+109
-6
lines changed

‎.openpublishing.publish.config.json

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,19 @@
1515
"build_entry_point": "docs",
1616
"template_folder": "_themes"
1717
},
18+
{
19+
"docset_name": "AzureLocal",
20+
"build_source_folder": "azure-local",
21+
"build_output_subfolder": "AzureLocal",
22+
"locale": "en-us",
23+
"monikers": [],
24+
"moniker_ranges": [],
25+
"open_to_public_contributors": false,
26+
"type_mapping": {
27+
"Conceptual": "Content"
28+
},
29+
"build_entry_point": "docs"
30+
},
1831
{
1932
"docset_name": "azure-managed-lustre",
2033
"build_source_folder": "azure-managed-lustre",

‎azure-local/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
- name: Index
2+
href: index.yml

‎azure-local/breadcrumb/AzureLocal/toc.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
- name: Azure Local
2+
tocHref: /azure-local
3+
topicHref: /azure-local/index

‎azure-local/docfx.json

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
{
2+
"build": {
3+
"content": [
4+
{
5+
"files": [
6+
"**/*.md",
7+
"**/*.yml"
8+
],
9+
"exclude": [
10+
"**/obj/**",
11+
"**/includes/**",
12+
"_themes/**",
13+
"**/docfx.json",
14+
"_repo.en-us/**",
15+
"README.md",
16+
"LICENSE",
17+
"LICENSE-CODE",
18+
"ThirdPartyNotices.md",
19+
"SECURITY.md"
20+
]
21+
}
22+
],
23+
"resource": [
24+
{
25+
"files": [
26+
"**/*.png",
27+
"**/*.jpg"
28+
],
29+
"exclude": [
30+
"**/obj/**",
31+
"**/includes/**",
32+
"_themes/**",
33+
"**/docfx.json",
34+
"_repo.en-us/**"
35+
]
36+
}
37+
],
38+
"overwrite": [],
39+
"externalReference": [],
40+
"globalMetadata": {
41+
"uhfHeaderId": "Azure",
42+
"breadcrumb_path": "~/breadcrumb/AzureLocal/toc.yml",
43+
"feedback_system": "Standard",
44+
"permissioned-type": "public"
45+
},
46+
"fileMetadata": {},
47+
"template": []
48+
}
49+
}

‎azure-local/index.yml

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
### YamlMime:Landing
2+
3+
title: Azure Local documentation
4+
summary: Azure Local is a hyperconverged clustering solution that uses validated hardware to run virtualized workloads on-premises, making it easy for customers to consolidate aging infrastructure and connect to Azure for cloud services.
5+
6+
metadata:
7+
title: Azure Local documentation
8+
description: Azure Local is a hyperconverged clustering solution that uses validated hardware to run virtualized workloads on-premises.
9+
# ms.service: service #Required; service per approved list. service slug assigned to your service by ACOM.
10+
ms.topic: landing-page
11+
author: ronmiab
12+
ms.author: robess
13+
ms.date: 09/30/2024
14+
15+
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new
16+
17+
landingContent:
18+
# Card (optional)
19+
- title: About Azure Local
20+
linkLists:
21+
- linkListType: overview
22+
links:
23+
- text: What is Azure Local?
24+
url: /azure/azure-stack/hci/overview

‎azure-stack/hci/concepts/plan-volumes.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -77,13 +77,13 @@ Dual parity provides the same fault tolerance as three-way mirroring but with be
7777

7878
:::image type="content" source="media/plan-volumes/dual-parity.png" alt-text="Diagram shows two volumes labeled data and two labeled parity connected by circular arrows with each volume associated with a server containing physical disks." lightbox="media/plan-volumes/dual-parity.png":::
7979

80-
Which resiliency type to use depends on the needs of your workload. Here's a table that summarizes which workloads are a good fit for each resiliency type, and the performance and storage efficiency of each resiliency type.
80+
Which resiliency type to use depends on the performance and capacity requirements for your environment. Here's a table that summarizes the performance and storage efficiency of each resiliency type.
8181

82-
| Resiliency type | Capacity efficiency | Speed | Workloads |
83-
| ------------------- | ---------------------- | --------- | ------------- |
84-
| **Mirror** | ![Storage efficiency showing 33%](media/plan-volumes/3-way-mirror-storage-efficiency.png)<br>Three-way mirror: 33% <br>Two-way-mirror: 50% |![Performance showing 100%](media/plan-volumes/three-way-mirror-perf.png)<br> Highest performance | Virtualized workloads<br> Databases<br>Other high performance workloads |
85-
| **Mirror-accelerated parity** |![Storage efficiency showing around 50%](media/plan-volumes/mirror-accelerated-parity-storage-efficiency.png)<br> Depends on proportion of mirror and parity | ![Performance showing around 20%](media/plan-volumes/mirror-accelerated-parity-perf.png)<br>Much slower than mirror, but up to twice as fast as dual-parity<br> Best for large sequential writes and reads | Archival and backup<br> Virtualized desktop infrastructure |
86-
| **Dual-parity** | ![Storage efficiency showing around 80%](media/plan-volumes/dual-parity-storage-efficiency.png)<br>4 servers: 50% <br>16 servers: up to 80% | ![Performance showing around 10%](media/plan-volumes/dual-parity-perf.png)<br>Highest I/O latency & CPU usage on writes<br> Best for large sequential writes and reads | Archival and backup<br> Virtualized desktop infrastructure |
82+
| Resiliency type | Capacity efficiency | Speed |
83+
| ------------------- | ---------------------- | --------- |
84+
| **Mirror** | ![Storage efficiency showing 33%](media/plan-volumes/3-way-mirror-storage-efficiency.png)<br>Three-way mirror: 33% <br>Two-way-mirror: 50% |![Performance showing 100%](media/plan-volumes/three-way-mirror-perf.png)<br> Highest performance |
85+
| **Mirror-accelerated parity** |![Storage efficiency showing around 50%](media/plan-volumes/mirror-accelerated-parity-storage-efficiency.png)<br> Depends on proportion of mirror and parity | ![Performance showing around 20%](media/plan-volumes/mirror-accelerated-parity-perf.png)<br>Much slower than mirror, but up to twice as fast as dual-parity<br> Best for large sequential writes and reads |
86+
| **Dual-parity** | ![Storage efficiency showing around 80%](media/plan-volumes/dual-parity-storage-efficiency.png)<br>4 servers: 50% <br>16 servers: up to 80% | ![Performance showing around 10%](media/plan-volumes/dual-parity-perf.png)<br>Highest I/O latency & CPU usage on writes<br> Best for large sequential writes and reads |
8787

8888
#### When performance matters most
8989

‎azure-stack/hci/update/about-updates-23h2.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -97,6 +97,18 @@ The PowerShell procedures apply to a single server and multi-server cluster that
9797

9898
You can install available Azure Stack HCI cluster updates via the Azure portal using the Azure Update Manager. For more information, see [Use Azure Update Manager to update your Azure Stack HCI, version 23H2](./azure-update-manager-23h2.md)
9999

100+
### Unsupported interfaces for updates
101+
102+
When you install updates for Azure Stack HCI, version 23H2 don't use the following interfaces:
103+
104+
- SConfig
105+
- Windows Admin Center
106+
- Azure Update Manager from the Machines pane in the Azure portal
107+
- Updates pane from the server (Machine-Azure Arc) resource page in the Azure portal
108+
- Manual runs of Cluster-Aware Updating
109+
110+
Using these interfaces can install out-of-band updates, which aren't supported within the lifecycle and may cause various issues on the cluster. Additionally, billing for update operations like periodic assessment, checking for updates, using the scheduler, and installing updates on the server resource (Machine-Azure Arc) may occur.
111+
100112
## Next steps
101113

102114
Learn to [Understand update phases](./update-phases-23h2.md).

0 commit comments

Comments
 (0)