OpenStack Heat

Can not use Security group for AWS LB

Bug #1443947 reported by Sergey Kraynev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Medium
Sergey Kraynev
OpenStack Heat 5.0.0 "liberty"

Bug Description

In case when user want to have instances with their own Security Group, AWS LB can no be assigned to any group instead of default.

We should implement this property, also it looks not difficult due to nested stack use AWS::EC2::Instance which has such property.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

Fix proposed to branch: master
Review: https://review.openstack.org/173311

Changed in heat:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (master)

Reviewed: https://review.openstack.org/173311
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=b4f8254182406a9c3c07def2d8d3c204cc60c0bc
Submitter: Jenkins
Branch: master

commit b4f8254182406a9c3c07def2d8d3c204cc60c0bc
Author: Sergey Kraynev <email address hidden>
Date: Tue Apr 14 09:18:52 2015 -0400

    Enable SecurityGroups property for AWS LB resource

    AWS LB has SecurityGroups property, but it's not implemented.
    This patch adds turn on this option by using SecurityGroups in nested
    template as parameter and property for AWS::EC2::Instance.

    Change-Id: I922cc97291179c79d1451a38cbb9e16933d703ef
    Closes-Bug: #1443947

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
milestone: none → liberty-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: liberty-1 → 5.0.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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