|
|
resource "libvirt_domain" "nxos_switch" name = "leaf1" memory = "4096" vcpu = 2
network_interface network_name = "data1" nxosv9k-7.0.3.i7.4.qcow2 plugin
The “plugin” here is the Terraform provider itself, which understands how to interface with the QCOW2 via libvirt. If you cannot find a ready-made plugin, create a custom wrapper script that auto-generates a libvirt domain XML for nxosv9k-7.0.3.i7.4.qcow2 . This “poor man’s plugin” ensures consistent deployment. It is a virtual machine disk image
It is a virtual machine disk image.
glance image-create --name "NXOSv9k-7.0.3" \ --disk-format qcow2 --container-format bare \ --file nxosv9k-7.0.3.i7.4.qcow2 \ --property hw_disk_bus='ide' \ --property hw_vif_model='virtio' \ --property os_require_quiesce='yes' \ --property hw_scsi_model='virtio-scsi' A true OpenStack “plugin” for this image would also include neutron port binding to map multiple virtual interfaces (up to 64) to the instance. Terraform’s libvirt-provider plugin allows you to define the QCOW2 as a domain resource: Cisco’s Nexus 9000v (NXOSv9k) is a virtual version
Introduction In the rapidly evolving landscape of network virtualization, the ability to emulate high-end data center switches without physical hardware is a game-changer. Cisco’s Nexus 9000v (NXOSv9k) is a virtual version of the powerful Nexus 9000 series switch, designed to run on hypervisors like KVM, VMware ESXi, and even within containerized environments. Among the many releases of this virtual appliance, the image file nxosv9k-7.0.3.i7.4.qcow2 has emerged as a stable, feature-rich version widely used for testing, development, and validation of Cisco’s NX-OS features.
network_interface network_name = "mgmt"