-
Bug
-
Resolution: Done
-
Low
-
Beijing Release
-
None
-
VNFRQTS Sprint 10
Current text:
"The VNF MUST deliver any and all functionality from any VNFC in the pool. The VNFC pool member should be transparent to the client. Upstream and downstream clients should only recognize the function being performed, not the member performing it."
Propose to change to:
"The VNF MUST deliver any and all functionality from any VNFC in the pool (where pooling is the most suitable solution). The VNFC pool member should be transparent to the client. Upstream and downstream clients should only recognize the function being performed, not the member performing it."
Reason for proposed change:
Agree that we should pool wherever it can be done, but we shouldn't have a VNFC be pooled if it is not the optimal distribution strategy between VNFC instances