Individual VNFc management using HOT

Registered by Hirofumi Noguchi

This blueprint aims at supporting individual VNFc management using HEAT and HOT. Current Tacker's sample Base HOT uses OS::Heat::AutoScalingGroup for managing VNFc. It is convenient for handling scale-in and scale-out. However, it cause service interuption by rebooting all VMs in the particular situation.

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

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.