mirror of https://github.com/bpg/terraform-provider-proxmox.git synced 2025-08-22 19:38:35 +00:00

feat(sdn): add support for zone resources and datasources (#2046 )

Signed-off-by: Pavel Boldyrev <627562+bpg@users.noreply.github.com>

2025-07-31 20:30:18 -04:00

3.1 KiB

Raw Blame History

layout	title	parent	subcategory	description
page	proxmox_virtual_environment_sdn_zone_qinq	Data Sources	Virtual Environment	Retrieves information about a QinQ Zone in Proxmox SDN. QinQ also known as VLAN stacking, that uses multiple layers of VLAN tags for isolation. The QinQ zone defines the outer VLAN tag (the Service VLAN) whereas the inner VLAN tag is defined by the VNet. Your physical network switches must support stacked VLANs for this configuration. Due to the double stacking of tags, you need 4 more bytes for QinQ VLANs. For example, you must reduce the MTU to 1496 if you physical interface MTU is 1500.

Data Source: proxmox_virtual_environment_sdn_zone_qinq

Retrieves information about a QinQ Zone in Proxmox SDN. QinQ also known as VLAN stacking, that uses multiple layers of VLAN tags for isolation. The QinQ zone defines the outer VLAN tag (the Service VLAN) whereas the inner VLAN tag is defined by the VNet. Your physical network switches must support stacked VLANs for this configuration. Due to the double stacking of tags, you need 4 more bytes for QinQ VLANs. For example, you must reduce the MTU to 1496 if you physical interface MTU is 1500.

Example Usage

data "proxmox_virtual_environment_sdn_zone_qinq" "example" {
  id = "qinq1"
}

output "data_proxmox_virtual_environment_sdn_zone_qinq" {
  value = {
    id                    = data.proxmox_virtual_environment_sdn_zone_qinq.example.id
    nodes                 = data.proxmox_virtual_environment_sdn_zone_qinq.example.nodes
    bridge                = data.proxmox_virtual_environment_sdn_zone_qinq.example.bridge
    service_vlan          = data.proxmox_virtual_environment_sdn_zone_qinq.example.service_vlan
    service_vlan_protocol = data.proxmox_virtual_environment_sdn_zone_qinq.example.service_vlan_protocol
    mtu                   = data.proxmox_virtual_environment_sdn_zone_qinq.example.mtu
    dns                   = data.proxmox_virtual_environment_sdn_zone_qinq.example.dns
    dns_zone              = data.proxmox_virtual_environment_sdn_zone_qinq.example.dns_zone
    ipam                  = data.proxmox_virtual_environment_sdn_zone_qinq.example.ipam
    reverse_dns           = data.proxmox_virtual_environment_sdn_zone_qinq.example.reverse_dns
  }
}

Schema

Required

id (String) The unique identifier of the SDN zone.

Read-Only

bridge (String) A local, VLAN-aware bridge that is already configured on each local node
dns (String) DNS API server address.
dns_zone (String) DNS domain name. Used to register hostnames, such as <hostname>.<domain>. The DNS zone must already exist on the DNS server.
ipam (String) IP Address Management system.
mtu (Number) MTU value for the zone.
nodes (Set of String) The Proxmox nodes which the zone and associated VNets are deployed on
reverse_dns (String) Reverse DNS API server address.
service_vlan (Number) Service VLAN tag for QinQ. The tag must be between 1 and 4094.
service_vlan_protocol (String) Service VLAN protocol for QinQ. The protocol must be 802.1ad or 802.1q.

3.1 KiB Raw Blame History