How budkane/eve-ng_lab-as-code-plat works
This repository generates network-device configurations from YAML definitions and can parse lab topology definitions and render the devices they reference. A separate EVE-NG client exposes API operations for creating labs, nodes, links, and applying configurations, although the excerpts do not show the lab CLI invoking that client. The README is empty, so capabilities and relationships are limited to the tree and sampled source; the lab’s deployment integration is not established.
Main entry points: lab.py Lab CLI · render.py Configuration renderer · R1.yml Device definitions · eve_ng.py EVE-NG API client
Components 10
Configuration rendering
- Device definitions
devices/R1.yml - Configuration renderer
render.py - Platform templates
templates/cisco-ios - Generated configurations
build/R1.cfg
Lab definitions
- Lab CLI
lab.py - Lab definitions
labs/ospf-basic/lab.yml - Topology parser
lab.py
EVE-NG management
- EVE-NG API client
eve_ng.py - EVE-NG service
Other components
- Operator
Connections 10
- Operator → Lab CLI: runs
lab.py - Lab CLI → Lab definitions: loads
lab.py - Lab CLI → Topology parser: parses links
lab.py - Lab CLI → Device definitions: loads
lab.py - Lab CLI → Configuration renderer: calls
lab.py - Operator → Configuration renderer: runs
render.py - Configuration renderer → Device definitions: reads
render.py - Configuration renderer → Platform templates: renders
render.py - Configuration renderer → Generated configurations: writes
render.py - EVE-NG API client → EVE-NG service: API requests
eve_ng.py