On Wed, Sep 11, 2013 at 10:59:25AM +0300, Pekka Rinne wrote: > hi all > > If I create AutoScalingGroup by using heat and define in template > AWS::AutoScaling::AutoScalingGroup, AWS::AutoScaling::LaunchConfiguration, > AWS::AutoScaling::ScalingPolicy and OS::Ceilometer::Alarms for up&down > scaling - how is it intended that I can automatically associate Neutron > Floating IPs to instances created this way? Is there already existing some > mechanism that can handle this by using heat template?
The more common topology for this kind of deployment would be an AutoScalingGroup behind a LoadBalancer resource, with an EIP associated with the LoadBalancer. > As in heat template it is not possible to define directly Neutron ports for > e.g. LaunchConfiguration. However, if your use-case demands it, I think this *should* be possible, can you expand on why it is not? Note that when defining the Neutron port, the ip_address is optional, and if ommitted, Neutron will allocate the first available fixed IP from the pool the instance: https://wiki.openstack.org/wiki/Neutron/APIv2-specification#Create_Port > And then when up scaling happens the new instances would need to have > floating IPs and ports as well. In down scaling network resources could be > released. > > The only way I could think of is that I would run stack update or use > horizon, but its not very practical with auto scaling. > > Or is there this kind of feature in road maps? I think we need to better understand your use-case, associating an EIP with every instance in a scaling group seems like a somewhat odd requirement, but as outlined above, I don't think it's impossible if you really need it. Steve _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
