SOL Violation: recounces in placementConstraints

[Kenta Fukaya]

In the SOL003, the cardinality of the RESOURCE is specified by "2..N.
Tacker contains several bugs in the receounces in placementConstraints.

- Create as many elements of placementConstraints as there are policies
- Does not take into account existing VNFc.
- the number of resources

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tacker/+/900747

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tacker/+/900747
Committed: https://opendev.org/openstack/tacker/commit/884fec5660550828597845679a29acee84629ad5
Submitter: "Zuul (22348)"
Branch: master

commit 884fec5660550828597845679a29acee84629ad5
Author: Ken Fujimoto <email address hidden>
Date: Fri Nov 10 08:20:17 2023 +0000

    Fix placementConstraints not compliant with SOL003

    This patch fixes the following, as placementConstraints
    does not comply with the ETSI NFV-SOL003 v3.3.1 in the v2 API.

    * Exiting VNFc is not included in the resource attribute
      when scale out operation.
    * Elements of placementConstraints are created for the number of
      policies, but policies not related to operation or elements
      with an attribute of resource less than 2 are excluded.

    Closes-Bug: #2043351
    Change-Id: I586b4a61e4410b494c35cf2f4f10152ff6080ab8

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tacker 11.0.0.0rc1 release candidate.