Skip to content

Validation

Jump to bottom
MiguelRivasQuobis edited this page Apr 30, 2019 · 8 revisions

Levels of validation

The validator implements four validation levels: syntax, integrity, topology and custom rules. The levels always follow an order, i.e. if integrity validation is chosen, the validator will make syntax first. In the same way, if topology is chosen, the tool will make syntax and integrity first.

  • Syntax (-s): It consists in check if the descriptor follows correctly the descriptor. In other words, the tool will ensure there are not non allowed fields and the required fields are present.

  • Integrity (-i): Although the descriptors have all the necessary fields, it is possible that the values of them are wrong. For example, if one VNFD has the following section connection point (CP), the validator will not show syntax errors. However, it should rise the errors due to duplicate id. Integrity validation supports the user to detect errors in the values of the field content of the descriptor.

connection_points:
  - id: "mgmt"
    interface: "ipv4"
    type: "management"
  - id: "mgmt"
    interface: "ipv4"
    type: "management"
  - id: "output"
    interface: "ipv4"
    type: "external"

  • Topology (-t): VNFD and NSD form networks which can have problems like loops, cycles, bottle-necks... Topology validation tries to detect the errors related with the structure of the network.

  • Custom rules (-c): With the custom rules, the user can create requirements which must be acomplished by the descriptors. For example, memory, badwidth, number of CPUs...

  • Note: If parameter level is missing (-s|-i|-t|-c), the validator will use -t as default mode.

Types of validation

The syntax validation is the same for all descriptors. Moreover, there are only one possible error: Syntax is not OK.

Funtion Validation

Errors

  • There are undeclared connection points
  • There are problems with the sections: VLINK, virtual units, connection points
  • There are duplicated ports in CDUs
  • Fail building the graph
  • There are isolated units
  • There are loops
  • There are cycles

Warnings

  • VDU image is not accesible
  • There are unused connection points
  • There are unused connection points

Service validation

Due to the fact that the services can be formed by VNF, the validator must check the correct form of the VNFDs in addition to NSD. However, it only check de VNFDs in integrity (or higher levels), in the syntax level only will check the NSD.

Errors

  • VNF referenced does not exist
  • There are problems with sections: Connection points, virtual links, forwading graphs
  • There are undeclared connection points in use
  • Error building topology graph
  • Topology graph is disconnected
  • Forwarding path is disrupted
  • Loops found in the topology

Warnings

  • There are unused connection points
  • Cycles found in forwarding path
  • There are unused vnfd connection points
  • There are isolated VNFDs (all CP unused)

Test validation

Errors

  • Missing phases section
  • Replicate id in phases
  • Missing steps in phases

Project validation

If project validation is request, the validator can show any error of the previous cases. If syntax level is chosen, only the NSD will check.

Clone this wiki locally