[openstack-dev] [Heat] rough draft of Heat autoscaling API

Zane Bitter zbitter at redhat.com
Thu Nov 21 18:31:24 UTC 2013

On 21/11/13 18:44, Christopher Armstrong wrote:
>     2) It relies on a plugin being present for any type of thing you
>     might want to notify.
> I don't understand this point. What do you mean by a plugin? I was
> assuming OS::Neutron::PoolMember (not LoadBalancerMember -- I went and
> looked up the actual name) would become a standard Heat resource, not a
> third-party thing (though third parties could provide their own through
> the usual heat extension mechanisms).

I mean it requires a resource type plugin written in Python. So cloud 
operators could provide their own implementations, but ordinary users 
could not.


More information about the OpenStack-dev mailing list