[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#724980: ITP: trove -- Database as a Service for OpenStack

On 10/01/2013 01:10 AM, Stefano Zacchiroli wrote:
> On Mon, Sep 30, 2013 at 09:28:33AM -0700, Clint Byrum wrote:
>> And what user-facing API would you use to let the user do that apt-get
>> install after automatically provisioning a server sized right for that DB?
>> And to add users?
> Holger have indeed been a bit concise, but I suspect his point wasn't to
> dispute the usefulness of this software, but rather to encourage the
> packager to add a more comprehensive description of it to the Debian
> package :-) Adding some of your points about API availability would be a
> very good start.

Here's my current long description:

Trove is Database as a Service for Openstack. It's designed to run
entirely on OpenStack, with the goal of allowing users to quickly and
easily utilize the features of a relational database without the burden
of handling complex administrative tasks. Cloud users and database
administrators can provision and manage multiple database instances as
needed. Initially, the service will focus on providing resource
isolation at high performance while automating complex administrative
tasks including deployment, configuration, patching, backups, restores,
and monitoring. Trove is designed to support a single-tenant database
within a Nova instance. There is no restrictions on how Nova is
configured, since Trove interacts with other OpenStack components purely
through the API.

Individual binary packages also have description of what they do.

Sorry that I was careless and wrote the ITP too fast. Though you can be
sure I wouldn't upload the package with such a non-decriptive description.


Thomas Goirand (zigo)

P.S: Even if I'm spending the most of my days on packaging OpenStack for
Debian, it's still too big for me alone, and I would accept some help...
Many wrote they would, but so far, there aren't so many commits besides
mine in our Git. I believe I'll have the core of OpenStack ready for the
release date, though I'm not 100% sure I will have Marconi, TrippleO and
Trove (I'm working hard so that it happens on time).

Reply to: