On Oct 21, 2013, at 1:57 PM, Nikhil Manchanda wrote: > > The image approach works fine if Trove only supports deploying a single > datastore type (mysql in your case). As soon as we support > deploying more than 1 datastore type, Trove needs to have some knowledge > of which guestagent manager classes to load. Hence the need > for having a datastore type API. > > The argument for needing to keep track of the version is > similar. Potentially a version increment -- especially of the major > version -- may require for a different guestagent manager. And Trove > needs to have this information.
This is also true that we dont want to define the _need_ to have custom images for the datastores. You can, quite easily, deploy mysql or redis on a vanilla image.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
