Update deployment-virtual.md - adjust system requirements #3830
Conversation
1. consolidating virtual disks which was partly 6 and partly 4. 2. the new requirements allow deployments with only 2 disks.
|
@Karl-WE : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 782f4e8: ✅ Validation status: passed
For more details, please refer to the build report. |
added OS disks
Karl-WE
changed the title
|
Learn Build status updates of commit 3040502: ✅ Validation status: passed
For more details, please refer to the build report. |
rename Azure Stack HCI to Azure Local (even though the OS is not renamed but it is so confusing) corrected information about number of disks as I forgot to mention and count OS disk in previous PR.
|
Learn Build status updates of commit be9f8cd: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
Hi @alkohli any news on this? |
Bold text,because validation will fail when not set. The idea was that it's only necessary on adapters when teamed but that's not the case.
|
Learn Build status updates of commit 5ee0e4a: ✅ Validation status: passed
For more details, please refer to the build report. |
Added teaming
| | Virtual machine (VM) type | Secure Boot and Trusted Platform Module (TPM) enabled. | | ||
| | vCPUs | Four cores. | | ||
| | Memory | A minimum of 24 GB. | | ||
| | Memory | A minimum of 32 GB. | |
There was a problem hiding this comment.
To comply with latest HW requirements as per docs
AzL configurator app will hardcheck for 32 GB.
|
Learn Build status updates of commit 995c1a6: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 1c3b57f: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 765bd02: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 7ba1c1a: ✅ Validation status: passed
For more details, please refer to the build report. |
Changes to system requirements table
|
Learn Build status updates of commit bbbf593: ✅ Validation status: passed
For more details, please refer to the build report. |
| @@ -1,5 +1,5 @@ | |||
| --- | |||
| title: Deploy a virtual Azure Local, version 23H2 system | |||
| title: Deploy a virtual Azure Local, version 23H2 / 24H2 system | |||
There was a problem hiding this comment.
@Karl-WE - should we say Deploy a virtual Azure Local, version 23H2 and 24H2 system?
There was a problem hiding this comment.
Aslong it lasts. Good idea.
| >[!NOTE] | ||
| >Microsoft Support doesn't support virtual deployments. |
There was a problem hiding this comment.
@Karl-WE - add space between > on both lines
| 1. Enable MAC spoofing *on all network adapters* on VM `Node1`. MAC address spoofing is a technique that allows a network adapter to masquerade as another by changing its Media Access Control (MAC) address. | ||
| In addition we need to enable teaming *on all network adapters*, because NetworkATC will team vNICs for the management / compute intent, and depending on the configuration (storage switched) aswell on the storage vNICs. | ||
| This is required in scenarios where you're planning to use nested virtualization: |
There was a problem hiding this comment.
@Karl-WE - a suggested rewrite:
- Enable MAC address spoofing and teaming on all network adapters on VM Node1 if you plan to use nested virtualization.
-
MAC address spoofing lets a network adapter appear as another by changing its Media Access Control (MAC) address.
-
NetworkATC teams vNICs for management and compute intent, and, depending on the configuration, for storage vNICs.
| ``` | ||
| 1. Create extra drives to be used as the boot disk and hard disks for Storage Spaces Direct. After these commands are executed, six new VHDXs will be created in the `C:\vms\Node1` directory as shown in this example: | ||
| 1. Create extra drives to be used as one for boot disk and two hard disks for Storage Spaces Direct. After these commands are executed, three new VHDXs will be created in the `C:\vms\Node1` directory as shown in this example: |
There was a problem hiding this comment.
@Karl-WE - suggested rewrite:
Create extra drives to be used as one for the boot disk and two hard disks for Storage Spaces Direct.
- After you run these commands, as shown in the example, three new VHDXs appear in the C:\vms\Node1 directory.
4 participants
consolidating virtual disks which was partly 6 and partly 4.
the new requirements allow deployments with only 2 disks.
Changes to network adapters so that the EnvironmentChecker will not fail.
Raising RAM requirements to comply with new system requirements for Azure Local configurator app.