On Thu, Nov 21, 2013 at 12:31 PM, Zane Bitter <zbit...@redhat.com> wrote:
> 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. > > Okay, but that sounds like a general problem to solve (custom third-party plugins supplied by the user instead of cloud operators, which is an idea I really love btw), and I don't see why it should be a point against the idea of simply using a Neutron::PoolMember in a scaling unit. -- IRC: radix Christopher Armstrong Rackspace
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
