> 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.
Additionally there could be server code at some point soon that will need to know what datastore type is associated with an instance to determine what db engine is in use. So for example, if a call such as "users" isn't supported by a certain datastore used by an instance, the server side code will be able to determine that and something such as a bad request or not found status code. ________________________________________ From: Michael Basnight [mbasni...@gmail.com] Sent: Monday, October 21, 2013 4:05 PM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance 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. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
