Fix naming in network_model for validation

infra/network_model.yaml

@@ -1,20 +1,93 @@
-devices: []
+devices:
+- configs: null
+  interfaces: []
+  location: HQ
+  mgmt_ip: 10.0.10.10
+  model: Cisco Catalyst 9300
+  name: core-sw-01
+  role: core
+  vendor: other
+- configs: null
+  interfaces: []
+  location: HQ
+  mgmt_ip: 10.0.10.11
+  model: Cisco Catalyst 9300
+  name: core-sw-02
+  role: core
+  vendor: other
+- configs: null
+  interfaces: []
+  location: Site1
+  mgmt_ip: 10.10.11.50
+  model: Cisco ISR 1100
+  name: site1-edge-wan
+  role: edge
+  vendor: cisco
+- configs: null
+  interfaces: []
+  location: Site2
+  mgmt_ip: 10.10.12.50
+  model: Cisco ISR 1100
+  name: site2-edge-wan
+  role: edge
+  vendor: cisco
+- configs: null
+  interfaces: []
+  location: Site3
+  mgmt_ip: 10.10.13.50
+  model: Cisco ISR 1100
+  name: site3-edge-wan
+  role: edge
+  vendor: cisco
+- configs: null
+  interfaces: []
+  location: Site4
+  mgmt_ip: 10.10.14.50
+  model: Cisco ISR 1100
+  name: site4-edge-wan
+  role: edge
+  vendor: cisco
+- configs: null
+  interfaces: []
+  location: Site5
+  mgmt_ip: 10.10.15.50
+  model: Cisco ISR 1100
+  name: site5-edge-wan
+  role: edge
+  vendor: cisco
+- configs: null
+  interfaces: []
+  location: Site6
+  mgmt_ip: 10.10.16.50
+  model: Cisco ISR 1100
+  name: site6-edge-wan
+  role: edge
+  vendor: cisco
+- configs: null
+  interfaces: []
+  location: Site7
+  mgmt_ip: 10.10.17.50
+  model: Cisco ISR 1100
+  name: site7-edge-wan
+  role: edge
+  vendor: cisco
 intent:
-  budget: null
+  budget: Not specified
   business_requirements:
-  - High availability
-  - Scalability
-  constraints:
-  - Budget conscious
-  - Easy to maintain
-  description: I need a network for a small retail store with guest WiFi, employee
-    WiFi, POS systems, and security cameras. Budget is $5000.
-  timeline: null
-name: network_I_need_a_network_for
+  - Guest WiFi
+  - POS
+  - Cameras
+  - VPN to HQ
+  constraints: []
+  description: Design a 7-site retail network with guest WiFi, POS VLANs, cameras,
+    and secure VPN to HQ.
+  timeline: ASAP
+name: network_Design_a_7-site_reta
 routing:
   areas:
-  - Area 0
-  protocol: OSPF
+  - 0.0.0.0
+  process_id: 1
+  protocol: ospf
 services:
 - DHCP
 - DNS
@@ -22,43 +95,39 @@ services:
 subnets:
 - gateway: 10.0.10.1
   network: 10.0.10.0/24
-  purpose: Management network
+  purpose: management
   vlan: 10
-- gateway: 10.0.20.1
-  network: 10.0.20.0/24
-  purpose: Employee WiFi network
-  vlan: 20
-- gateway: 10.0.30.1
-  network: 10.0.30.0/24
-  purpose: Guest WiFi network
-  vlan: 30
-- gateway: 10.0.40.1
-  network: 10.0.40.0/24
-  purpose: POS systems network
-  vlan: 40
-- gateway: 10.0.50.1
-  network: 10.0.50.0/24
-  purpose: Security cameras network
-  vlan: 50
+- gateway: 10.71.0.1
+  network: 10.71.0.0/24
+  purpose: site1-lan
+  vlan: 301
+- gateway: 10.72.0.1
+  network: 10.72.0.0/24
+  purpose: site2-lan
+  vlan: 302
+- gateway: 10.73.0.1
+  network: 10.73.0.0/24
+  purpose: site3-lan
+  vlan: 303
+- gateway: 10.74.0.1
+  network: 10.74.0.0/24
+  purpose: site4-lan
+  vlan: 304
+- gateway: 10.75.0.1
+  network: 10.75.0.0/24
+  purpose: site5-lan
+  vlan: 305
+- gateway: 10.76.0.1
+  network: 10.76.0.0/24
+  purpose: site6-lan
+  vlan: 306
+- gateway: 10.77.0.1
+  network: 10.77.0.0/24
+  purpose: site7-lan
+  vlan: 307
 version: 1.0.0
 vlans:
 - id: 10
-  name: Management
-  purpose: Network management
+  name: management
+  purpose: management
   subnet: 10.0.10.0/24
-- id: 20
-  name: Employee
-  purpose: Employee WiFi
-  subnet: 10.0.20.0/24
-- id: 30
-  name: Guest
-  purpose: Guest WiFi
-  subnet: 10.0.30.0/24
-- id: 40
-  name: POS
-  purpose: Point of Sale systems
-  subnet: 10.0.40.0/24
-- id: 50
-  name: CCTV
-  purpose: Security cameras
-  subnet: 10.0.50.0/24