So, I think you are saying what Daniel Salinas said in a previous reply:
"Trove allows you to deploy a single vm with 1 server
instance of whichever service supported. So for example, if you were to
deploy a mysql instance, you would have 1 vm with 1 mysql instance running
on
On Sep 10, 2013, at 6:01 AM, Brian Aker wrote:
> Hi!
>
> On Sep 9, 2013, at 9:46 AM, Michael Basnight wrote:
>
>> On Sep 9, 2013, at 8:38 AM, Clint Byrum wrote:
>>
>>> Perhaps: "Trove is designed to support a multi-user database for a single
>>> OpenStack tenant within a Nova instance."
>>
>
Hi!
On Sep 9, 2013, at 9:46 AM, Michael Basnight wrote:
> On Sep 9, 2013, at 8:38 AM, Clint Byrum wrote:
>
>> Perhaps: "Trove is designed to support a multi-user database for a single
>> OpenStack tenant within a Nova instance."
>
> +1. Very succinct, and it does remove ambiguity. Giuseppe, fe
On Sep 9, 2013, at 8:38 AM, Clint Byrum wrote:
> Excerpts from Michael Basnight's message of 2013-09-09 07:57:34 -0700:
>> On Sep 9, 2013, at 7:39 AM, Giuseppe Galeota
>> wrote:
>>
>>> So, I think that "Trove is designed to support a single-tenant database
>>> within a Nova instance" is a misl
Excerpts from Michael Basnight's message of 2013-09-09 07:57:34 -0700:
> On Sep 9, 2013, at 7:39 AM, Giuseppe Galeota
> wrote:
>
> > So, I think that "Trove is designed to support a single-tenant database
> > within a Nova instance" is a misleading definition. What do you think?
>
> What exact
On Sep 9, 2013, at 7:39 AM, Giuseppe Galeota wrote:
> So, I think that "Trove is designed to support a single-tenant database
> within a Nova instance" is a misleading definition. What do you think?
What exactly is misleading about that? Don't get me wrong, I've been working on
trove for a lon
