Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ic32eefcfd4be4d57c9cf30eff0b3fa1aa730d2c0
Issue-ID: VNFSDK-532
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
|
|
Implement test for vnf requirement R-35851: The VNF Package MUST include
VNF topology that describes basic network and application connectivity
internal and external to the VNF including Link type, KPIs, Bandwidth,
latency, jitter, QoS (if applicable) for each interface.
For now, we only check the existence of CP or VL, because Link type,
bandwidth are already foced by ONAP DM. For other KPIs, current onap DM
doesn't define yet.
Change-Id: I6ad78edfcbd96ef748e1dbe5f0674b6e4e537e06
Issue-ID: VNFSDK-314
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
|
|
Implement test for vnf requirement R-26881: The VNF provider MUST
provide the binaries and images needed to instantiate the VNF (VNF and
VNFC images).
Change-Id: Idce2e598e98365b87ad0491975adbb0f76b38604
Issue-ID: VNFSDK-313
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
|
|
Implement test for vnf requirement R-04298: The VNF provider MUST
provide their testing scripts to support testing.
Change-Id: I16e5b7f01fbf33983846a3f82895e5c78fe65948
Issue-ID: VNFSDK-312
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
|
|
Implement test for vnf requirement R-77707: provider MUST include a
Manifest File that contains a list of all the components in the VNF
package.
Change-Id: Ief3f8af2cce20d003007147f106ba9c72bcde292
Issue-ID: VNFSDK-317
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
|
|
Implemented the internal code framework to add test cases to check vnf
requirements. Use command line parameter '--test-reqs' with the list of
vnf requirment IDs to invoke 'vnfsdk csar-validate'.
Also implement test case for R-66070: csar manifest metadata
Change-Id: I385e515f3e87f1e89fb7baf9ec3e0560f44541cd
Issue-ID: VNFSDK-316
Issue-ID: VNFSDK-174
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
|