SOL002 - Implementation of additional test steps for checks against VNFD content in v2.7.1

This merge request refers to the implementation of test steps for checks against VNFD content in SOL002 v2.7.1 APIs.

@lynchpi @aelken @matsuurat @kraja @zulfiqar @zafar

Deadline for review: Monday January 25th 2021 @6pm CET

Review period expired: approved

added MR ready to review label

added 1 commit

• 28ecd83a - SOL006 reference descriptor file and checking functionality updated (with...

Compare with previous version

added 1 commit

• 5a464a59 - minor bug fix for previous commit (FlavorId got deleted by mistake)

Compare with previous version

added 1 commit

• b4d9f52c - minor typo error resolved

Compare with previous version

I have a question for clarification.

For example, in VNFLifecycleManagement-API / IndividualVNFInstance.robot, CHECK is added on line 40.

• Check HTTP Response Body vnfInstance content against VNF Descriptor

What does this check for vnfinstance against VNFD?

• Where does this test item check in the content?
• For example, is the comparison in this item whether the values match?

The Check HTTP Response Body vnfInstance content against VNF Descriptor inspects the content of the vnfInstance data structure returned by the FUT, and verifies that its attribute values match those in the VNFD used to instantiate such VNF. For example, some of the attributes checked are:

Descriptor ID
Provider
Product Name
Software Version
Descriptor Version
VDU names
Virtual link names
Connection point names
etc.

Thank you for your confirmation. I would like to clarify which of the SOL002 Attribute corresponds to some of the CHECK items listed.

The correspondence I am assuming is described below. Could you please tell me the Attribute corresponding to the item marked "???" ?

• Descriptor ID (>vnfdId SOL002 5.5.2.2)
• Provider (>vnfProvider SOL002 5.5.2.2)
• Product Name (>vnfProductName SOL002 5.5.2.2)
• Software Version (>vnfSoftware Version SOL002 5.5.2.2)
• Descriptor Version (>vnfdVersion SOL002 5.5.2.2)
• VDU names (>???)
• Virtual link names (>???)
• Connection point names (>???)

Also, could you tell me the criteria for selecting these items for testing?

I confused "names" with "identifiers".

• VDU id (>vduId SOL002 5.5.3.8)
• virtual link id (>vnfVirtualLinkDescId SOL002 5.5.3.5)
• Connection point id (>cpdId SOL002 5.5.3.8)

The criteria for selecting the items was taken from SOL001 Annex D, and applying the same mapping to SOL006 attributes.

The criteria for selecting items has been cleared. Thank you.

Shouldn't this selection criterion be specified as a sentence?

(All items of SOL001 Annex D, or items extracted from SOL001 Annex D under certain conditions?)

It'd be a good idea to mention it as part of TST010 v2.7.1 clause 4.

@sayama if you do not have further comments, I'd consider the MR as "ready to be merged".

added 1 commit

• b0e44fd2 - Bug fix in response parsing

Compare with previous version

changed the description

changed the description

added MR ready to be merged label

removed MR ready to review label

added 2.7.1 label

added 1 commit

• dedf94bb - renamed descriptors

Compare with previous version

merged

mentioned in commit f363742d