In case requires is set in a VNFD, the NFVO should not wait when source VNF is not present in NSD

[gc4rella]

In case requires is set in a VNFD, the NFVO should not wait when source VNF is not present in NSD.

Example of VNFD:

...
"requires":{
    "server":{
        "parameters":["netname_floatingIp"]
    }
}
...

however, NSD does not contain any server VNF. Therefore the NFVO should not wait during CONFIGURE lifecycle.

[lorenzotomasini]

If the VNF that provides the parameter is not in the NSD you should get an error while uploading the NS. @ThomasBri is this the case?

[ThomasBri]

Yes, I checked it and I was not able to upload an NSD containing a requires field which referenced a non existing VNFD's name.

[gc4rella]

can be closed?

[lorenzotomasini]

yes