Steve Baker <sba...@redhat.com> wrote on 10/28/2013 04:24:30 PM:
> On 10/29/2013 02:53 AM, Steven Hardy wrote:
> > ...
> > Can anyone provide me with a clear argument for what the "fundamental
> > differences" actually are?
> ...
> Since writing those proposals my thinking has evolved too. I'm currently
> thinking it would be best to implement software configuration resources
> rather than create a new component construct.
Please pardon the newbie question, but I do not understand. A resource
type is implemented in OpenStack code --- a part of Heat that calls a
fixed service API that expects Keystone credentials. A component is
implemented by a bit of user code (and/or other sorts of instructions)
embedded in or referenced by a template, with no fixed API and not invoked
with Keystone credentials. We desire the heat engine to invoke operations
on resources; we do not desire the heat engine to invoke components (the
VMs do that themselves, via whatever bootstrapping mechanism is used). So
yes, I do see fundamental differences. What am I missing?
Thanks,
Mike
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev