Page MenuHomeVyOS Platform

Add GCC preprocessor support for XML files
Closed, ResolvedPublicFEATURE REQUEST

Description

A lot of XML code is duplicated (VLAN, interface address) for instance. Such XML definitions should be moved to feature.xml.inc files and then just pulled in via GCC preprocessor #include <featurexml.inc> in the bond or ethernet xml definition. Thus we gain a single source and modularity.

When the XML files are rendered, the GCC preprocessor should be called first, inserting the xml.inc statements into an intermediate xml file which is the ised to generate the node defs.

Advantages:

  • Pro: Single source
  • Pro: Maintainability
  • Pro: Modularity
  • Con: It will look strange in the beginning

An example of an address.xml.inc file which sets an interface address can look like:

<leafNode name="address">
  <properties>
    <help>IP address</help>
    <completionHelp>
      <list>dhcp dhcpv6</list>
    </completionHelp>
    <valueHelp>
      <format>ipv4net</format>
      <description>IPv4 address and prefix length</description>
    </valueHelp>
    <valueHelp>
      <format>ipv6net</format>
      <description>IPv6 address and prefix length</description>
    </valueHelp>
    <valueHelp>
      <format>dhcp</format>
      <description>Dynamic Host Configuration Protocol</description>
    </valueHelp>
    <valueHelp>
      <format>dhcpv6</format>
      <description>Dynamic Host Configuration Protocol for IPv6</description>
    </valueHelp>
    <constraint>
      <validator name="ip-cidr"/>
      <regex>(dhcp|dhcpv6)</regex>
    </constraint>
    <multi/>
  </properties>
</leafNode>

Or a vlan.xml.inc can look like:

<tagNode name="vif">
  <properties>
    <help>Virtual Local Area Network (VLAN) ID</help>
    <valueHelp>
      <format>0-4094</format>
      <description>Virtual Local Area Network (VLAN) ID</description>
    </valueHelp>
    <constraint>
      <validator name="numeric" argument="--range 0-4094"/>
    </constraint>
    <constraintErrorMessage>VLAN ID must be between 0 and 4094</constraintErrorMessage>
  </properties>
  <children>
    <leafNode name="address">
      <properties>
        <help>IP address</help>
        <completionHelp>
          <list>dhcp dhcpv6</list>
        </completionHelp>
        <valueHelp>
          <format>ipv4net</format>
          <description>IPv4 address and prefix length</description>
        </valueHelp>
        <valueHelp>
          <format>ipv6net</format>
          <description>IPv6 address and prefix length</description>
        </valueHelp>
        <valueHelp>
          <format>dhcp</format>
          <description>Dynamic Host Configuration Protocol</description>
        </valueHelp>
        <valueHelp>
          <format>dhcpv6</format>
          <description>Dynamic Host Configuration Protocol for IPv6</description>
        </valueHelp>
        <constraint>
          <validator name="ip-cidr"/>
          <regex>(dhcp|dhcpv6)</regex>
        </constraint>
        <multi/>
      </properties>
    </leafNode>
    <leafNode name="description">
      <properties>
        <help>Interface description</help>
        <constraint>
          <regex>^.{1,256}$</regex>
        </constraint>
        <constraintErrorMessage>Interface description too long (limit 256 characters)</constraintErrorMessage>
      </properties>
    </leafNode>
    <node name="dhcp-options">
      <properties>
        <help>DHCP options</help>
      </properties>
      <children>
        <leafNode name="client-id">
          <properties>
            <help>DHCP client identifier</help>
          </properties>
        </leafNode>
        <leafNode name="host-name">
          <properties>
            <help>DHCP client host name (overrides system host name)</help>
          </properties>
        </leafNode>
        <leafNode name="vendor-class-id">
          <properties>
            <help>DHCP client vendor type</help>
          </properties>
        </leafNode>
      </children>
    </node>
    <node name="dhcpv6-options">
      <properties>
        <help>DHCPv6 options</help>
        <priority>319</priority>
      </properties>
      <children>
        <leafNode name="parameters-only">
          <properties>
            <help>Acquire only config parameters, no address</help>
            <valueless/>
          </properties>
        </leafNode>
        <leafNode name="temporary">
          <properties>
            <help>IPv6 "temporary" address</help>
            <valueless/>
          </properties>
        </leafNode>
      </children>
    </node>
    <leafNode name="disable-link-detect">
      <properties>
        <help>Ignore link state changes</help>
        <valueless/>
      </properties>
    </leafNode>
    <leafNode name="disable">
      <properties>
        <help>Disable this bridge interface</help>
        <valueless/>
      </properties>
    </leafNode>
    <leafNode name="egress-qos">
      <properties>
        <help>VLAN egress QoS</help>
        <completionHelp>
          <script>echo Format for qos mapping \"0:1 1:6 7:6\"</script>
        </completionHelp>
        <constraint>
          <regex>[:0-7 ]+$</regex>
        </constraint>
        <constraintErrorMessage>QoS mapping should be in the format of \"0:7 2:3\" with numbers 0-9</constraintErrorMessage>
      </properties>
    </leafNode>
    <leafNode name="ingress-qos">
      <properties>
        <help>VLAN ingress QoS</help>
        <completionHelp>
          <script>echo Format for qos mapping \"0:1 1:6 7:6\"</script>
        </completionHelp>
        <constraint>
          <regex>[:0-7 ]+$</regex>
        </constraint>
        <constraintErrorMessage>QoS mapping should be in the format of \"0:7 2:3\" with numbers 0-9</constraintErrorMessage>
      </properties>
    </leafNode>
    <node name="ip">
      <children>
        <leafNode name="arp-cache-timeout">
          <properties>
            <help>ARP cache entry timeout in seconds</help>
            <valueHelp>
              <format>1-86400</format>
              <description>ARP cache entry timout in seconds (default 30)</description>
            </valueHelp>
            <constraint>
              <validator name="numeric" argument="--range 1-86400"/>
            </constraint>
            <constraintErrorMessage>ARP cache entry timeout must be between 1 and 86400 seconds</constraintErrorMessage>
          </properties>
        </leafNode>
        <leafNode name="enable-proxy-arp">
          <properties>
            <help>Enable proxy-arp on this interface</help>
            <valueless/>
          </properties>
        </leafNode>
        <leafNode name="proxy-arp-pvlan">
          <properties>
            <help>Enable private VLAN proxy ARP on this interface</help>
            <valueless/>
          </properties>
        </leafNode>
      </children>
    </node>
    <leafNode name="mac">
      <properties>
        <help>Media Access Control (MAC) address</help>
        <valueHelp>
          <format>h:h:h:h:h:h</format>
          <description>Hardware (MAC) address</description>
        </valueHelp>
        <constraint>
          <validator name="mac-address"/>
        </constraint>
      </properties>
    </leafNode>
    <leafNode name="mtu">
      <properties>
        <help>Maximum Transmission Unit (MTU)</help>
        <valueHelp>
          <format>68-9000</format>
          <description>Maximum Transmission Unit</description>
        </valueHelp>
        <constraint>
          <validator name="numeric" argument="--range 68-9000"/>
        </constraint>
        <constraintErrorMessage>MTU must be between 68 and 9000</constraintErrorMessage>
      </properties>
    </leafNode>
  </children>
</tagNode>

Details

Difficulty level
Normal (likely a few hours)
Version
-
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Internal change (not visible to end users)

Event Timeline

c-po updated the task description. (Show Details)
c-po updated the task description. (Show Details)
c-po moved this task from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po changed Difficulty level from Unknown (require assessment) to Normal (likely a few hours).
erkin set Issue type to Internal change (not visible to end users).Aug 31 2021, 6:11 PM