added wsa, esa, juniper qfx, hpe, windows 10. (#19)

* Create README.MD adding palo alto node and image definition * Update README.MD * Created readme Created readme for Windows 10 node definition * fixed typo * added node def * Delete README.md * Delete winServer2019.yaml * Add files via upload * updated * windows 2019 * added server 2019 * updated readme * updated * added node definitions * added readme * added node def * added readme * added node def * added readme * added node def * added readme * fixed typo * added node def * already exists * updated fields
2025-10-23 07:42:03 +00:00 · 2022-04-13 10:03:49 -04:00
parent 34f9af8475
commit d2f142619c
15 changed files with 3237 additions and 24 deletions
--- a/node-definitions/cisco/esa/ESA.yaml
+++ b/node-definitions/cisco/esa/ESA.yaml
@@ -0,0 +1,66 @@
+id: ESA
+general:
+  description: Cisco Email Security Appliance
+  nature: server
+  read_only: false
+device:
+  interfaces:
+    has_loopback_zero: true
+    physical:
+      - enp6s0
+      - enp6s1
+      - enp6s2
+      - enp6s3
+    serial_ports: 2
+    default_count: 4
+    loopback:
+      - loopback
+ui:
+  visible: true
+  label_prefix: esa-
+  icon: server
+  label: ESA
+  description: |-
+    Cisco Email Security Appliance
+    4096 MB RAM, 1 vCPUs
+sim:
+  linux_native:
+    libvirt_domain_driver: kvm
+    driver: server
+    disk_driver: ide
+    ram: 4096
+    cpus: 1
+    cpu_limit: 100
+    nic_driver: virtio
+    boot_disk_size: 200
+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
+  provisioning:
+    volume_name: cidata
+    media_type: iso
+    files:
+      - name: config.xml
+        editable: true
+        content: |-
+          <?xml version="1.0" encoding="ISO-8859-1"?>
+          <!DOCTYPE config SYSTEM "config.dtd">
+          <config>
+
+          </config>
+schema_version: 0.0.1
--- a/node-definitions/cisco/esa/Readme.md
+++ b/node-definitions/cisco/esa/Readme.md
@@ -0,0 +1,13 @@
+# Cisco Email Security Appliance (ESA)
+
+This directory contains the following node definition:
+
+* `esa.yaml` - Cisco Email Security Appliance (ESA)
+
+### Image Availability
+
+Images for the ESA can be downloaded from https://software.cisco.com/download/home/284900944/type/282975113/release/13.5.1 with a proper Cisco.com account and entitlement.
+
+### Notes
+
+The WSA image has different versions, C000V KVM qcow2 image was used along with this node definition, it uses 1 vCPU and 4 GB of RAM.  
--- a/node-definitions/cisco/wsa/Readme.md
+++ b/node-definitions/cisco/wsa/Readme.md
@@ -0,0 +1,13 @@
+# Cisco Web Security Appliance (WSA)
+
+This directory contains the following node definition:
+
+* `wsa.yaml` - Cisco Web Security Appliance (WSA)
+
+### Image Availability
+
+Images for the WSA can be downloaded from https://software.cisco.com/download/home/284806698/type/282975114/release/12.5.1%20GD with a proper Cisco.com account and entitlement.
+
+### Notes
+
+The WSA image has different versions, S100V KVM qcow2 image was used along with this node definition, it uses 3 vCPU and 8 GB of RAM.  
--- a/node-definitions/cisco/wsa/wsa.yaml
+++ b/node-definitions/cisco/wsa/wsa.yaml
@@ -0,0 +1,66 @@
+id: wsa
+general:
+  description: Cisco Web Security Appliance (WSA)
+  nature: server
+  read_only: false
+device:
+  interfaces:
+    has_loopback_zero: true
+    physical:
+      - enp6s0
+      - enp6s1
+      - enp6s2
+      - enp6s3
+    serial_ports: 2
+    default_count: 4
+    loopback:
+      - loopback
+ui:
+  visible: true
+  label_prefix: wsa-
+  icon: server
+  label: WSA
+  description: |-
+    Cisco Web Security Appliance (WSA)
+    8192 MB RAM, 3 vCPUs
+sim:
+  linux_native:
+    libvirt_domain_driver: kvm
+    driver: server
+    disk_driver: ide
+    ram: 8192
+    cpus: 3
+    cpu_limit: 100
+    nic_driver: virtio
+    boot_disk_size: 200
+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
+  provisioning:
+    volume_name: cidata
+    media_type: iso
+    files:
+      - name: config.xml
+        editable: true
+        content: |-
+          <?xml version="1.0" encoding="ISO-8859-1"?>
+          <!DOCTYPE config SYSTEM "config.dtd">
+          <config>
+
+          </config>
+schema_version: 0.0.1
--- a/node-definitions/hpe/Readme.md
+++ b/node-definitions/hpe/Readme.md
@@ -0,0 +1,11 @@
+# HPE Router Node Definition
+
+This directory contains a node definition for the VSR 1000 HPE Router appliance.
+
+### Image Availability
+
+HPE VSR 1000 Image can be downloaded from https://support.hpe.com/ with a proper account and entitlement.
+
+### Description
+
+The node requires 2 vCPUs and 4096 MB of RAM.
--- a/node-definitions/hpe/hpe.yaml
+++ b/node-definitions/hpe/hpe.yaml
@@ -0,0 +1,73 @@
+id: hpe
+configuration:
+  generator:
+    driver: server
+  provisioning:
+    volume_name: cfg
+    media_type: iso
+    files:
+      - name: config.txt
+        content: '# this is a shell script which will be sourced at boot'
+        editable: true
+device:
+  interfaces:
+    has_loopback_zero: true
+    default_count: 6
+    physical:
+      - MGE0/0/0
+      - WGE1/0/1
+      - WGE1/0/2
+      - WGE1/0/3
+      - WGE1/0/4
+      - WGE1/0/5
+    serial_ports: 2
+    loopback:
+     - InLoop0
+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
+general:
+  description: HPE Router
+  nature: server
+  read_only: false
+schema_version: 0.0.1
+sim:
+  linux_native:
+    cpus: 2
+    disk_driver: ide
+    driver: server
+    libvirt_domain_driver: kvm
+    nic_driver: e1000
+    ram: 4096
+    boot_disk_size: 16
+    video:
+      memory: 16
+    cpu_limit: 100
+boot:
+  completed:
+    - '###### BOOT CONFIG DONE ######'
+  timeout: 20
+pyats:
+  os: linux
+  use_in_testbed: true
+ui:
+  description: |-
+    HPE Router
+    4096 MB RAM, 2 vCPU
+    ##### Note
+    **EXPERIMENTAL**
+  group: Others
+  icon: server
+  label: HPE
+  label_prefix: HPE-
+  visible: true
--- a/node-definitions/juniper/qfx/Readme.md
+++ b/node-definitions/juniper/qfx/Readme.md
@@ -0,0 +1,10 @@
+# Juniper vQFX Node Definitions
+
+This directory contains the following node definitions:
+
+* `jnpr-vqfx-re.yaml` - Juniper Virtual Routing Engine
+* `jnpr-vqfx-pfe.yaml` - Juniper Virtual Packet Forwarding Engine
+
+## Caveats
+
+vQFX support is considered **EXPERIMENTAL** within CML.
--- a/node-definitions/juniper/qfx/jnpr-vqfx-pfe.yaml
+++ b/node-definitions/juniper/qfx/jnpr-vqfx-pfe.yaml
@@ -0,0 +1,66 @@
+id: jnpr-vqfx-pfe
+configuration:
+  generator:
+    driver: null
+  provisioning:
+    volume_name: config
+    media_type: iso
+    files:
+      - name: boot
+        editable: true
+        content: console=ttyS0
+inherited:
+  image:
+    ram: false
+    cpus: false
+    data_volume: false
+    boot_disk_size: false
+    cpu_limit: true
+  node:
+    ram: false
+    cpus: false
+    data_volume: false
+    boot_disk_size: false
+    cpu_limit: true
+device:
+  interfaces:
+    has_loopback_zero: true
+    default_count: 7
+    physical:
+      - em0
+      - em1
+    serial_ports: 1
+    loopback:
+      - Lo0
+general:
+  description: Juniper vQFX PFE
+  nature: router
+  read_only: false
+schema_version: 0.0.1
+sim:
+  linux_native:
+    cpus: 1
+    disk_driver: ide
+    driver: server
+    libvirt_domain_driver: kvm
+    nic_driver: e1000
+    ram: 2048
+    cpu_limit: 100
+    video:
+      memory: 1024
+boot:
+  timeout: 600
+  completed:
+    - console=ttyS0
+ui:
+  description: |-
+    Juniper vQFX Virtual Packet Forwarding Engine VPFE
+    2048MB 1 vCPUs
+
+    ##### Note
+    **EXPERIMENTAL**
+  group: Others
+  icon: router
+  label: Juniper vQFX PFE
+  label_prefix: vqfx-pfe-
+  visible: true
--- a/node-definitions/juniper/qfx/jnpr-vqfx-re.yaml
+++ b/node-definitions/juniper/qfx/jnpr-vqfx-re.yaml
@@ -0,0 +1,70 @@
+id: jnpr-vqfx-re
+configuration:
+  generator:
+    driver: null
+  provisioning:
+    volume_name: disk
+    media_type: iso
+    files:
+      - name: configuration.txt
+        content: hostname insert_hostname_here
+        editable: true
+inherited:
+  image:
+    ram: false
+    cpus: false
+    data_volume: false
+    boot_disk_size: false
+    cpu_limit: true
+  node:
+    ram: false
+    cpus: false
+    data_volume: false
+    boot_disk_size: false
+    cpu_limit: true
+device:
+  interfaces:
+    has_loopback_zero: false
+    default_count: 2
+    physical:
+      - em0
+      - em1
+      - xe-0/0/0
+      - xe-0/0/1
+      - xe-0/0/2
+      - xe-0/0/3
+      - xe-0/0/4
+      - xe-0/0/5
+      - xe-0/0/6
+    serial_ports: 1
+general:
+  description: Juniper vQFX RE
+  nature: router
+  read_only: false
+schema_version: 0.0.1
+sim:
+  linux_native:
+    cpus: 1
+    disk_driver: ide
+    driver: server
+    libvirt_domain_driver: kvm
+    nic_driver: e1000
+    ram: 1024
+    cpu_limit: 100
+boot:
+  timeout: 600
+  completed:
+    - 'login:'
+ui:
+  description: |2-
+
+    Juniper vQFX Virtual Routing Engine
+    1024MB, 1 vCPU
+
+    ##### Note
+    **EXPERIMENTAL**
+  group: Others
+  icon: router
+  label: Juniper vQFX RE
+  label_prefix: vqfx-re-
+  visible: false
--- a/node-definitions/microsoft/README.md
+++ b/node-definitions/microsoft/README.md
@@ -1,14 +1,3 @@
-# Microsoft Server 2019
+# Windows Node Definitions

-This directory contains the following node definition:
-
-* `winServer2019.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   
-
-### Notes
-
-This node definition uses 16g of RAM and 4vcpu's. Anything less than that and it tends to become buggy. 
+Here you will find collection of Windows node definitions.
--- a/node-definitions/microsoft/Server
+++ b/node-definitions/microsoft/Server
@@ -0,0 +1,14 @@
+# Microsoft Server 2019
+
+This directory contains the following node definition:
+
+* `winServer2019.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   
+
+### Notes
+
+This node definition uses 16g of RAM and 4vcpu's. Anything less than that and it tends to become buggy. 
--- a/node-definitions/microsoft/Server
+++ b/node-definitions/microsoft/Server
--- a/node-definitions/microsoft/Windows
+++ b/node-definitions/microsoft/Windows
@@ -0,0 +1,13 @@
+# Microsoft Windows 10
+
+This directory contains the following node definition:
+
+* `Windows 10.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:
+
+This node definition uses 2 VCPUS and 6 GB RAM.
--- a/node-definitions/microsoft/winServer2019.yaml
+++ b/node-definitions/microsoft/winServer2019.yaml
@@ -1,47 +1,54 @@
-id: win2019
+id: Windows 10
 general:
  nature: server
  read_only: false
+  description: Windows 10 Node definition.
 device:
  interfaces:
    has_loopback_zero: false
    physical:
      - eth0
+      - eth1
    serial_ports: 1
-    default_count: 1
+    default_count: 2
 ui:
  visible: true
-  label_prefix: win2019
-  icon: server
-  label: win2019
+  label_prefix: Windows
+  icon: host
+  label: Windows 10
+  description: |-
+    2 vCPUs 6 GB RAM
+
+    ##### Note
+    **EXPERIMENTAL**
 sim:
  linux_native:
    libvirt_domain_driver: kvm
    driver: server
    disk_driver: sata
-    ram: 16384
-    cpus: 4
-    cpu_limit: 100
+    ram: 6144
+    cpus: 2
    nic_driver: e1000
-    boot_disk_size: 64
+    boot_disk_size: 32
    video:
      model: cirrus-vga
      memory: 16
+    cpu_limit: 20
 boot:
  timeout: 300
 inherited:
  image:
    ram: true
    cpus: true
-    cpu_limit: true
    data_volume: true
    boot_disk_size: true
+    cpu_limit: true
  node:
    ram: true
    cpus: true
-    cpu_limit: true
    data_volume: true
    boot_disk_size: true
+    cpu_limit: true
 configuration:
  generator:
    driver: server
--- a/node-definitions/palo-alto/README.MD
+++ b/node-definitions/palo-alto/README.MD
@@ -0,0 +1,13 @@
+# Palo Alto Networks Node Definitions
+
+This directory contains a node definition for the Palo Alto Virtual Edition appliance.
+
+Description
+This node definition provides for a BIGIP-VE node with four default ethernet interfaces and the ability to add up to 28. The node requires 4 vCPUs and 4 GB of RAM.
+
+This node does not provide a serial console. It uses VNC instead (though it's serial over VNC).
+
+Known Limitations
+You must use VNC to access this node's console. Serial console does not work.
+
+This node definition has been tested with v12 of the BIGIP software. It is assumed to work with all later versions as well. While the day 0 config part is in the node definition, it is known not to work with v12. It is believed the cloud-init support will work with v13 and higher of the BIGIP software, but that has not been tested.