Add Windows Server 2022. (#45)

node-definitions/microsoft/Server2019/Readme.md

@@ -2,13 +2,21 @@
 
 This directory contains the following node definition:
 
-* `winServer2019.yaml` - Microsoft Windows Server 2019 node definition
+* `win2019.yaml` - Microsoft Windows Server 2019 node definition
 
 ### Image Availability
 
 VHD images can be downloaded from microsoft on a trial basis here: https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2019
-Then the VHD image will have to be converted to a .qcow2 format. Linux qumu-img makes it easy. Documentation: https://docs.openstack.org/image-guide/convert-images.html   
+Then the VHD image will have to be converted to a .qcow2 format. Linux qumu-img makes it easy. Documentation: https://docs.openstack.org/image-guide/convert-images.html
+
+For example:
+
+```sh
+qemu-img convert -f vpc -O qcow2 \
+  17763.737.amd64fre.rs5_release_svc_refresh.190906-2324_server_serverdatacentereval_en-us_1.vhd \
+  17763.737.amd64fre.rs5_release_svc_refresh.190906-2324_server_serverdatacentereval_en-us_1.qcow2
+```
 
 ### Notes
 
-This node definition uses 16g of RAM and 4vcpu's. Anything less than that and it tends to become buggy. 
+This node definition uses 16g of RAM and 4vcpu's. Anything less than that and it tends to become buggy.

node-definitions/microsoft/Server2019/win2019.yaml

@@ -1,5 +1,6 @@
 id: win2019
 general:
+  description: Windows Server 2019
   nature: server
   read_only: false
 device:
@@ -7,13 +8,20 @@ device:
     has_loopback_zero: false
     physical:
       - eth0
+      - eth1
+      - eth2
+      - eth3
+      - eth4
+      - eth5
+      - eth6
+      - eth7
     serial_ports: 1
     default_count: 1
 ui:
   visible: true
-  label_prefix: win2019
+  label_prefix: win2019-
   icon: server
-  label: win2019
+  label: Windows Server 2019
 sim:
   linux_native:
     libvirt_domain_driver: kvm

node-definitions/microsoft/Server2022/Readme.md

@@ -0,0 +1,22 @@
+# Microsoft Server 2022
+
+This directory contains the following node definition:
+
+* `win2022.yaml` - Microsoft Windows Server 2022 node definition
+
+### Image Availability
+
+VHD images can be downloaded from microsoft on a trial basis here: https://info.microsoft.com/ww-landing-windows-server-2022.html
+Then the VHD image will have to be converted to a .qcow2 format. Linux qumu-img makes it easy. Documentation: https://docs.openstack.org/image-guide/convert-images.html
+
+For example:
+
+```sh
+qemu-img convert -f vpc -O qcow2 \
+  20348.169.amd64fre.fe_release_svc_refresh.210806-2348_server_serverdatacentereval_en-us.vhd \
+  20348.169.amd64fre.fe_release_svc_refresh.210806-2348_server_serverdatacentereval_en-us.qcow2
+```
+
+### Notes
+
+This node definition uses 16g of RAM and 4vcpu's. Anything less than that and it tends to become buggy.

node-definitions/microsoft/Server2022/win2022.yaml

@@ -0,0 +1,56 @@
+id: win2022
+general:
+  description: Windows Server 2022
+  nature: server
+  read_only: false
+device:
+  interfaces:
+    has_loopback_zero: false
+    physical:
+      - eth0
+      - eth1
+      - eth2
+      - eth3
+      - eth4
+      - eth5
+      - eth6
+      - eth7
+    serial_ports: 1
+    default_count: 1
+ui:
+  visible: true
+  label_prefix: win2022-
+  icon: server
+  label: Windows Server 2022
+sim:
+  linux_native:
+    libvirt_domain_driver: kvm
+    driver: server
+    disk_driver: sata
+    ram: 16384
+    cpus: 4
+    cpu_limit: 100
+    nic_driver: e1000
+    boot_disk_size: 64
+    video:
+      model: cirrus
+      memory: 16
+boot:
+  timeout: 300
+inherited:
+  image:
+    ram: true
+    cpus: true
+    cpu_limit: true
+    data_volume: true
+    boot_disk_size: true
+  node:
+    ram: true
+    cpus: true
+    cpu_limit: true
+    data_volume: true
+    boot_disk_size: true
+configuration:
+  generator:
+    driver: server
+schema_version: 0.0.1

node-definitions/microsoft/Windows10/Readme.md

@@ -2,12 +2,12 @@
 
 This directory contains the following node definition:
 
-* `Windows 10.yaml` - Microsoft Windows 10 node definition
+* `win10.yaml` - Microsoft Windows 10 node definition
 
 ### Image Availability
 
 VHD images can be downloaded from microsoft on a trial basis here: https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise Then the VHD image will have to be converted to a .qcow2 format. Linux qumu-img makes it easy. Documentation: https://docs.openstack.org/image-guide/convert-images.html
 
-### Notes:
+### Notes
 
 This node definition uses 2 VCPUS and 6 GB RAM.

node-definitions/microsoft/Windows10/win10.yaml

@@ -1,24 +1,33 @@
-id: Windows 10
+id: win10
 general:
   nature: server
   read_only: false
-  description: Windows 10 Node definition.
+  description: Windows 10
 device:
   interfaces:
     has_loopback_zero: false
     physical:
       - eth0
       - eth1
+      - eth2
+      - eth3
+      - eth4
+      - eth5
+      - eth6
+      - eth7
     serial_ports: 1
     default_count: 2
 ui:
   visible: true
-  label_prefix: Windows
+  label_prefix: win10-
   icon: host
   label: Windows 10
   description: |-
     2 vCPUs 6 GB RAM
 
+    Username/Password:
+    IEUser/Passw0rd!
+
     ##### Note
     **EXPERIMENTAL**
 sim:

virl-base-images/microsoft/win2019/win2019.yaml

@@ -0,0 +1,8 @@
+id: win2019
+node_definition_id: win2019
+description: Windows Server 2019
+label: Windows Server 2019
+disk_image: 17763.737.amd64fre.rs5_release_svc_refresh.190906-2324_server_serverdatacentereval_en-us_1.qcow2
+read_only: false
+disk_subfolder: win2019
+schema_version: 0.0.1

virl-base-images/microsoft/win2022/win2022.yaml

@@ -0,0 +1,8 @@
+id: win2022
+node_definition_id: win2022
+description: Windows Server 2022
+label: Windows Server 2022
+disk_image: 20348.169.amd64fre.fe_release_svc_refresh.210806-2348_server_serverdatacentereval_en-us.qcow2
+read_only: false
+disk_subfolder: win2022
+schema_version: 0.0.1