Bug 1042151

Summary: [RFE][heat]: Load Balancer Pool Members with stacks
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-heatAssignee: RHOS Maint <rhos-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Amit Ugol <augol>
Severity: high Docs Contact:
Priority: low    
Version: unspecifiedCC: ajeain, augol, breeler, markmc, sbaker, sdake, shardy, yeylon
Target Milestone: gaKeywords: FutureFeature
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/heat/+spec/loadbalancer-pool-members
Whiteboard: upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_approved
Fixed In Version: Doc Type: Enhancement
Doc Text:
This new feature allows specification of load balancer pool members in stacks. Previously all pool members had to be specified at load balancer creation time. Now, pool members can be dynamically defined.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-22 19:09:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 21:12:51 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/loadbalancer-pool-members.

Description:

It looks like the Neutron::LoadBalancer object requires all members up front. If you want to have other stacks add entries into your load balancer, you are out of luck. Looking at the neutron lbaas api they have a pool member api:

{
      "member" : {
                   "address": "192.168.224.31",
                   "protocol_port": 8080,
                   "pool_id": "cfc6589d-f949-4c66-99d2-c2da56ef3764"
                 }
}

It looks like perhapse there should be a Neutron::LoadBalancerPoolMember type similar to a Neutron::Port type, that lets you specify one of these things at a time, rather then all at once.

Note, it also does not take in an instance, but an IP address, which will also fix a different issue of using heat to add instances with multiple neutron ports.

Specification URL (additional information):

None

Comment 2 Stephen Gordon 2014-01-23 20:50:48 UTC
Moving to POST based on upstream status (Implemented).