Currently, when a VNFFG is created, Tacker also create port-pair,
port-pair-group, port-chain and flow-classifier. There are no
reusing ability in this approach.
This patch will check the port-id of a VNF is using in other VNFFG
or not. If it is used in a VNFFG, the existing port-pair-group will
be added to the new port-chain.
Therefore, we can create 2 VNFFGs that can go through one VNF.
This patch also clean up network resource such as port pair, port
pair group and flow classifier if there are failures.
Reviewed: https:/ /review. openstack. org/554435 /git.openstack. org/cgit/ openstack/ tacker/ commit/ ?id=d07d5448d36 b1dc7b38d099bb4 9e6ffe5ee2c084
Committed: https:/
Submitter: Zuul
Branch: master
commit d07d5448d36b1dc 7b38d099bb49e6f fe5ee2c084
Author: Cong Phuoc Hoang <email address hidden>
Date: Tue Mar 20 16:44:05 2018 +0900
Add reusing feature when creating VNFFG.
Currently, when a VNFFG is created, Tacker also create port-pair, pair-group, port-chain and flow-classifier. There are no
port-
reusing ability in this approach.
This patch will check the port-id of a VNF is using in other VNFFG
or not. If it is used in a VNFFG, the existing port-pair-group will
be added to the new port-chain.
Therefore, we can create 2 VNFFGs that can go through one VNF.
This patch also clean up network resource such as port pair, port
pair group and flow classifier if there are failures.
Change-Id: I648693103dd7ea b7a4b10cde89f11 766a9232e8d
Closes-Bug: #1746721