Individual VNFc management using HOT
This blueprint aims at supporting individual VNFc management using HEAT and HOT. Current Tacker's sample Base HOT uses OS::Heat:
When software image id is updated by modify VNF information API then scale-out API is requested, Tacker applys new software image id to AutoScalingGroup. It causes reboot of all VMs belonging to the same AutoScalingGroup. Since AutoScalingGroup is designed on the assumption that all resources in the group use the same software image id, individual VNFc cannot be configured.
For the above, additional functionality is required to scale without using the AutoScalingGroup.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Hirofumi Noguchi
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
change_vnfpkg enhance to enable network change
Addressed by: https:/
Enable vnfcInfo id to be fixed
Addressed by: https:/
Extend FT tests for Individual Vnfc Mgmt
Addressed by: https:/
Improve nfv parameter setting by additionalParams
