scaling_policy and software_development signal url conflict

Bug #1560916 reported by jz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
New
Undecided
jz

Bug Description

In the resource software_deveolpment and scaling_policy,
they obtain the signal url by calling the signal_responder.get_heat_signal_url
or signal_responder.get_ec2_signed_url respectively. The result can only has public_vip or internal_vip.
But in the case when the controller node has no access to public_vip and the vms
created have only access to public_vip. Then there is a conflict. either the software_development
or the scaling_policy can not work.

Revision history for this message
jz (danielradcliffe2004) wrote :

I am using the mitaka version

summary: - autoscale_group and software_development signal url conflict
+ scaling_policy and software_development signal url conflict
description: updated
Revision history for this message
jz (danielradcliffe2004) wrote :

For security design, heat can only has access to internal_vip, but vms has no access to public_vip

jz (danielradcliffe2004)
Changed in heat:
assignee: nobody → jz (danielradcliffe2004)
Rico Lin (rico-lin)
Changed in heat:
milestone: none → no-priority-tag-bugs
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.