{
    "contact": "ONAP VTP Team onap-discuss@lists.onap.org",
    "criteria": "FAILED",
    "date": "Fri May 31 15:21:13 IST 2019",
    "platform": "VNFSDK - VNF Test Platform (VTP) 1.0",
    "results": [
        {
            "description": "V2.4.1 (2018-02)",
            "errors": [],
            "passed": true,
            "vnfreqName": "SOL004"
        },
        {
            "description": "The VNF package MUST contain all standard artifacts as specified in ETSI GS NFV-SOL004 including\nManifest file, VNFD (or Main TOSCA/YAML based Service Template) and other optional artifacts.\nCSAR Manifest file as per SOL004 - for example ROOT\\ MainServiceTemplate.mf\n",
            "errors": [],
            "passed": true,
            "vnfreqName": "r10087"
        },
        {
            "description": "The VNF/PNF package provided by a VNF/PNF vendor MAY be either with TOSCA-Metadata directory (CSAR Option 1)\nor without TOSCA-Metadata directory (CSAR Option 2) as specified in ETSI GS NFV-SOL004. On-boarding entity\n(ONAP SDC) must support both options.\n",
            "errors": [],
            "passed": true,
            "vnfreqName": "r87234"
        },
        {
            "description": "The VNF/PNF Descriptor (VNFD/PNFD) provided by VNF/PNF vendor MUST comply with TOSCA/YAML based Service template\nfor VNF/PNF descriptor specified in ETSI NFV-SOL001.\n",
            "errors": [],
            "passed": true,
            "vnfreqName": "r35854"
        },
        {
            "description": "Major TOSCA Types specified in ETSI NFV-SOL001 standard draft.\n",
            "errors": [],
            "passed": true,
            "vnfreqName": "r15837"
        },
        {
            "description": "The VNFD/PNFD MAY include TOSCA/YAML definitions that are not part of NFV Profile. If provided,\nthese definitions MUST comply with TOSCA Simple Profile in YAML v.1.2.\n",
            "errors": [],
            "passed": true,
            "vnfreqName": "r17852"
        },
        {
            "description": "For a VNF/PNF package CSAR MUST contains a TOSCA-Metadata directory with the TOSCA.meta metadata file.\nThe TOSCA.meta metadata file MUST includes block_0 with the Entry-Definitions keyword pointing to a TOSCA definitions\nYAML file.\nAdditional keyname extension must be included as following:\n-ETSI-Entry-Manifest\n-ETSI-Entry-Change-Log\n",
            "errors": [],
            "passed": true,
            "vnfreqName": "r293901"
        },
        {
            "description": "The VNF/PNF package Manifest file MUST contain: non-mano artifact set with following ONAP public tag\n-onap_ves_events\n-onap_pm_dictionary\n-onap_yang_module\n-onap_others\n",
            "errors": [],
            "passed": true,
            "vnfreqName": "r146092"
        },
        {
            "description": "The PNF TOSCA CSAR package Manifest file MUST start with the PNF package metadata\nin the form of a name-value pairs. Each pair shall appear on a different line.\nThe name is specified as following:\n-pnfd_provider\n-pnfd_name\n-pnfd_release_date_time\n-pnfd_archive_version\n",
            "errors": [
                {
                    "code": "0x2002",
                    "file": "MainServiceTemplate.mf",
                    "lineNumber": -1,
                    "message": "Missing. Entry [pnfd_release_date_time]",
                    "vnfreqNo": "R57019"
                }
            ],
            "passed": false,
            "vnfreqName": "r57019"
        },
        {
            "description": "If the VNF or PNF CSAR Package utilizes Option 2 for package security, then the complete CSAR file MUST be digitally signed with the VNF or PNF provider private key. The VNF or PNF provider delivers one zip file consisting of the CSAR file, a signature file and a certificate file that includes the VNF or PNF provider public key. The certificate may also be included in the signature container, if the signature format allows that. The VNF or PNF provider creates a zip file consisting of the CSAR file with .csar extension, signature and certificate files. The signature and certificate files must be siblings of the CSAR file with extensions .cms and .cert respectively.\n",
            "errors": [],
            "passed": true,
            "vnfreqName": "r787965"
        }
    ],
    "vnf": {
        "mode": "WITH_TOSCA_META_DIR",
        "name": "RadioNode",
        "type": "TOSCA",
        "vendor": "Ericsson",
        "version": "1.0"
    }
}