Open Stack

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 it.  You can put as many databases on that one server instance as you
would like with as many database users as you would like."

For example, considering the use of the DBMS MySQL, Trove (today) allows to
create 1 VM with 1 MySQL instance, in which Trove creates as many database
as if I wrote:
mysql> CRETAE database DB_01;
mysql> CRETAE database DB_02;
etc....
To do this, I should use the API
/v1/instances<https://github.com/openstack/database-api/blob/master/openstack-database-api/src/markdown/database-api-v1.md#users-v1instances>
 writing:

{
    "instance": {
        "databases": [
            {
                "character_set": "utf8",
                "collate": "utf8_general_ci",
                "name": "DB_01"
            },
            {
                "name": "DB_02"
            }

etc....



Now, I have an endpoint in which the MySQL instance is running and
databases were created like above. At this point, an application can USE
databases (in order to CREATE tables and INSERT/SELECT data in the fields)
by connecting to that endpoint (https://ip_address:3306) using, for
example, the WSO2 Data Services Server.

Is it right?

Thank you all,
Giuiseppe


2013/9/10 Michael Basnight <mbasnight at gmail.com>

> On Sep 10, 2013, at 6:01 AM, Brian Aker <brian at tangent.org> wrote:
>
> > Hi!
> >
> > On Sep 9, 2013, at 9:46 AM, Michael Basnight <mbasnight at gmail.com>
> 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, feel free to
> update the wiki to reflect this, and help remove ambiguity in other areas.
> Thank you Clint and Giuseppe.
> >
> > Let me be a little nit-picky.
> >
> > Trove when mapped to other RDBMS then MySQL may actually create multiple
> "DATABASES".
> >
> > MySQL maps "CREATE DATABASE" to "CREATE SCHEMA" and Trove has inherited
> this inconsistency. A number of other RDBMS have both of these implemented
> and I would expect that they will call "CREATE DATABASE" instead.
> >
> > It would be more accurate to say that Trove supports the creation of
> "DBMS" systems (though frankly some of the NO-SQL solutions don't fit that
> definition due to their lack of data integrity).
> >
> > Additionally I would drop the "multi-user" part since some of the
> proposed implementations lack "users" as well.
> >
> > Trove is a service that handles the maintenance, provisioning, etc… of
> DBMS systems.
> >
>
> Very good points. I've been in many a meeting trying to explain what Brian
> just wrote. Ill be sure to add all this to the wiki today. Thank you Brian.
>
> > Cheers,
> >    -Brian
> >
> >
> >
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130912/b1b63b9a/attachment.html>