Placement policy is not working if specified after scaling policy in VNFD template

Bug #1813871 reported by Niraj Singh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
New
Undecided
Shubham Potale

Bug Description

If user configure scaling policy and placement policy at the same time in VNFD template under policies by keeping placement policy below the scaling policy, placement policy will not work.
Example:
  policies:
    - SP1:
        type: tosca.policies.tacker.Scaling
        properties:
          increment: 2
          cooldown: 120
          min_instances: 0
          max_instances: 2
          default_instances: 0
        targets: [VDU1]
    - my_compute_placement_policy:
        type: tosca.policies.tacker.Placement
        properties:
          policy: anti-affinity
          strict: true
        description: Apply anti-affinity placement policy to the application servers
        targets: [VDU1]

Because after scaling policy handle_properties() got executed, it removes VDU resources from the self.hot_resource.
and when call goes to ToscaPolicies->handle_properties in heat-translator, there are no VDU resource available.
And it is not updating the VDU resource properties with scheduler_hints.

Changed in tacker:
assignee: nobody → Shubham Potale (shubhamp)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers