[openstack-dev] [OpenStack] [Barbican] Cinder and Barbican

[Giuseppe Galeota]

Dear all,
is Cinder capable today to use Barbican for encryption? If yes, can
you attach some useful doc?

Thank you,
Giuseppe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [OpenStack] [Barbican] Cinder and Barbican

[Giuseppe Galeota]

Dear all,
is Cinder capable today to use Barbican for encryption? If yes, can you
link to me some useful doc?

Thank you,
Giuseppe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack] [Barbican] Keystone PKI token too much long

[Giuseppe Galeota]

​Dear all,
have you some good news about the problem related to
​the "
Keystone PKI token too much long​" for Barbican?

Thank you,
Giuseppe



2014-01-31 14:27 GMT+01:00 Ferreira, Rafael :

>  By the way, you can achieve the same benefits of uuid tokens (shorter
> tokens) with PKI by simply using a md5 hash of the PKI token for your
> X-Auth headers. This is poorly documented but it seems to work just fine.
>
>   From: Adam Young 
> Date: Tuesday, January 28, 2014 at 1:41 PM
> To: "openst...@lists.openstack.org" 
> Subject: Re: [Openstack] [Barbican] Keystone PKI token too much long
>
>   On 01/22/2014 12:21 PM, John Wood wrote:
>
>  (Adding another member of our team Douglas)
>
>  Hello Giuseppe,
>
>  For questions about news or patches for Keystone's PKI vs UUID modes,
> you might reach out to the openstack-dev@lists.openstack.org mailing
> list, with the subject line prefixed with [openstack-dev] [keystone]
>
>  Our observation has been that the PKI mode can generate large text
> blocks for tokens (esp. for large service catalogs) that cause http header
> errors.
>
>  Regarding the specific barbican scripts you are running, we haven't run
> those in a while, so I'll investigate as we might need to update them.
> Please email back your /etc/barbican/barbican-api-paste.ini paste config
> file when you have a chance as well.
>
>  Thanks,
> John
>
>
>  --
> *From:* Giuseppe Galeota [giuseppegale...@gmail.com]
> *Sent:* Wednesday, January 22, 2014 7:36 AM
> *To:* openst...@lists.openstack.org
> *Cc:* John Wood
> *Subject:* [Openstack] [Barbican]
> ​​
> Keystone PKI token too much long
>
>  Dear all,
> I have configured Keystone for Barbican using this guide
> <https://github.com/cloudkeep/barbican/wiki/Developer-Guide-for-Keystone>.
>
>  Is there any news or patch about the need to use a shorter token? I
> would not use a modified token.
>
> Its a known problem.  You can request a token without the service catalog
> using an extension.
>
> One possible future enhancement is to compress the key.
>
>
>
>  Following you can find an extract of the linked guide:
>
>- (Optional) Typical keystone setup creates PKI tokens that are long,
>do not fit easily into curl requests without splitting into components. For
>testing purposes suggest updating the keystone database with a shorter
>token-id. (An alternative is to set up keystone to generate uuid tokens.)
>From the above output grad the token expiry value, referred to as "x-y-z"
>
>  mysql -u rootuse keystone;update token set id="foo" where expires="x-y-z" ;
>
>
>  Thank you,
> Giuseppe
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openst...@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>  The communication contained in this e-mail is confidential and is
> intended only for the named recipient(s) and may contain information that
> is privileged, proprietary, attorney work product or exempt from disclosure
> under applicable law. If you have received this message in error, or are
> not the named recipient(s), please note that any form of distribution,
> copying or use of this communication or the information in it is strictly
> prohibited and may be unlawful. Please immediately notify the sender of the
> error, and delete this communication including any attached files from your
> system. Thank you for your cooperation.
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openst...@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack] [TROVE] Manual Installation: problems with trove-manage

[Giuseppe Galeota]

Hi Michael,
I'm using this unique guide: "
http://docs.openstack.org/developer/trove/dev/manual_install.html";.

If you can give me an useful guide, I would be grateful!

>> 1) Which user do I need use in order to install TROVE, root user or a
>> non-root user?

   >Installation should be the same as other projects in OpenStack. If its
   >not, we definitely have issues :)

  OK

>> 2)  Why is it necessary to run a virtual environment (virtualenv)? Is it
>> the right way in order to realize a production Openstack environment?

  >? I have helped a few companies install trove, and i have _never_
run in
  >a venv. Not saying you should/shouldnt, im just saying its not
  >necessary. Im not sure where you got that.


OK


>> 3) When I run the command:
>>
>> (env)root@hostname:~#trove-manage
>> --config-file=/root/trove/etc/trove/trove.conf.sample db_wipe
>> trove_test.sqlite mysql fake
>>
>> I obtain this output:
>>
>> (env)root@hostname:~# trove-manage
>> --config-file=/root/trove/etc/trove/trove.conf.sample db_wipe
>> trove_test.sqlite mysql fake
>> usage: trove-manage [-h] [--config-dir DIR] [--config-file PATH]
[--debug]
>> [--log-config-append PATH] [--log-date-format
>> DATE_FORMAT]
>> [--log-dir LOG_DIR] [--log-file PATH]
>> [--log-format FORMAT] [--nodebug] [--nouse-syslog]
>> [--noverbose] [--syslog-log-facility
>> SYSLOG_LOG_FACILITY]
>> [--use-syslog] [--verbose] [--version]
>>
{db_sync,db_upgrade,db_downgrade,datastore_update,datastore_version_update,db_wipe}
>> ...
>> trove-manage: error: unrecognized arguments: mysql fake

  >Looks like you hit a bug :) Im not sure if anyone has run that via trove
>manage before!!

 I have followed this unique guide (
http://docs.openstack.org/developer/trove/dev/manual_install.html), and
precisely this instructions:

   -

   Initialize the database:

   # trove-manage --config-file= db_wipe
trove_test.sqlite mysql fake



  where --config-file=/root/trove/etc/trove/trove.conf.sample

So:
 a) How should I inizialize the trove's database?

 b) Why the config files are under the
/root/trove/etc insted of /etc/trove/  ?


   However, if I run that command without *mysql fake*:

(env)root@hostname:~#
trove-manage --config-file=/root/trove/etc/trove/trove.conf.sample
db_wipe trove_test.sqlite

   it seems to work. In the trove's database, infact, I can see a
lot of tables.


>> Furthermore, I obtain the "trove-manage: error: unrecognized
arguments: image_update
>> when I run the command:
>>
>> (env)root@hostname:~#
trove-manage --config-file=/root/trove/etc/trove/trove.conf.sample
image_update mysql `nova --os-username trove --os-password trove
--os-tenant->>name trove --os-auth-url http://:5000/v2.0
image-list | awk '/trove-image/ {print $2}'`



  >I dont see image_update in the list of commands above. Im not sure
where
  >you got image_update from, but i dont see it in the current
trove-manage
  >code. If you got that from a wiki article, its crazy wrong!!

I have got image_update from the guide
http://docs.openstack.org/developer/trove/dev/manual_install.html , ed in
particular from the section:


   -

   Setup trove to use the uploaded image. Enter the following in a single
   line, note quotes (') and backquotes(`):

   # trove-manage
--config-file=/root/trove/etc/trove/trove.conf.sample image_update
mysql `nova --os-username trove --os-password trove
--os-tenant-name trove --os-auth-url http://:5000/v2.0
image-list | awk '/trove-image/ {print $2}'`



  >If u want synchronous help, find us in #openstack-trove.

  I will do it.

Can you help me with a more useful guide that makes trove working?

Thank you very much!
Giuseppe


2014-02-13 17:18 GMT+01:00 Michael Basnight :

> Giuseppe Galeota  writes:
>
> > [...]
> >
> > 1) Which user do I need use in order to install TROVE, root user or a
> > non-root user?
>
> Installation should be the same as other projects in OpenStack. If its
> not, we definitely have issues :)
>
> >
> > 2)  Why is it necessary to run a virtual environment (virtualenv)? Is it
> > the right way in order to realize a production Openstack environment?
>
> ? I have helped a few companies install trove, and i have _never_ run in
> a venv. Not saying you should/shouldnt, im just saying its not
> necessary. Im not sure where you got that.
>
> >
> >
> >
> > 3) When I run the command:
&g

[openstack-dev] [Openstack] [KEYSTONE] Keystone federation

[Giuseppe Galeota]

Dear all,

I would provide both PaaS and IaaS (Openstack)  services, with two keystone
services: one for the PaaS (Keystone PaaS) and the other one for the IaaS
(Keystone IaaS).

In particular, I would Openstack system appear as a PaaS service towards
PaaS's users, so that an user that authenticates against Keystone PaaS can
use Openstack services too.

So, I was thinking of using Keystones federation, so that:
1- PaaS's user authenticates against Keystone PaaS and receives a scoped
token.
2- PaaS's user invokes openstack services by using the scoped token
received from Keystone PaaS;
3- Openstack services validate the token against Keystone IaaS;
4- Keystone IaaS validate against Keystone PaaS

Do you think this scenario is possible? I would be appreciate any further
solutions you think I might implement.

Best regards,
Giuseppe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Openstack] [Trove] Backups Amazon like

[Giuseppe Galeota]

Dear all,
the Relational Database service for Amazon talk about:

   - Automated Backups – Turned on by default, the automated backup feature
   of Amazon RDS enables point-in-time recovery for your DB Instance. Amazon
   RDS will backup your database and transaction logs and store both for a
   user-specified retention period. This allows you to restore your DB
   Instance to any second during your retention period, up to the last five
   minutes. Your automatic backup retention period can be configured to up to
   thirty five days.


   - DB Snapshots – DB Snapshots are user-initiated backups of your DB
   Instance. These full database backups will be stored by Amazon RDS until
   you explicitly delete them. You can create a new DB Instance from a DB
   Snapshot whenever you desire.


Does it exist a Trove project for Automated backups?

Many thanks,
Giuseppe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Fwd: [Openstack] [TROVE] - Difference between Backup and Snapshot

[Giuseppe Galeota]

FYI

-- Forwarded message --
From: Daniel Morris 
Date: 2013/11/7
Subject: Re: [Openstack] [TROVE] - Difference between Backup and Snapshot
To: Giuseppe Galeota 


  Giuseppe,

 I recommend sending these questions on to the openstack-dev list.  This
may be why you are not seeing responses.   Someone from the Trove team
should jump in on that list give you a run down, and if not, I will do my
best to explain.  Per your first question, I believe it to be just a
terminology mismatch.  The system does backups and currently is implemented
using mysqldump and percona xtrabackup.  It is conceivable that someone
could create a backup type that does an actual volume snapshot, but that
capability has not been written yet.

 Thanks,
Daniel


  From: Giuseppe Galeota 
Date: Wednesday, November 6, 2013 3:05 AM
To: "openst...@lists.openstack.org" 
Subject: Re: [Openstack] [TROVE] - Difference between Backup and Snapshot

  Can you give me a simple workflow that explains the process of a
backup/snapshot?

 Thanks,
Giuseppe


2013/11/6 Giuseppe Galeota 

> Dear all,
> what is the difference between Snapshot and Backup in the context of Trove
> (o Redwwarf) database backups that I see 
> here<https://wiki.openstack.org/wiki/Trove/snapshot-design>
> ?
>
>  Is it maybe the following:
> - backup = copy of volume in which data are stored;
> - snapshot = copy of volume plus virtual machine used to host the engine?
>
>  Are they the same concept?
>
>  Thanks,
> Giuseppe
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Fwd: [Openstack][TROVE] - MongoDB as a Service

[Giuseppe Galeota]

Dear Illia, dear all,

I work at Santer Reply S.p.A. (Reply s.p.a. group) on the
*PRISMA<http://www.ponrec.it/media/140119/20121005_progetto_prisma_slide_master_v04.pdf>
* project (Interoperable cloud platforms for smart-government). PRISMA is
supported by *Italian Government and European Union*, and it aims to
develop an *Open Source* cloud computing system to provide services on both
IaaS and PaaS level, in order to realize a Smart Community between
citizens, Governments and Health agencies.

For our project, we have chosen *Openstack*. Furthermore, we want a
Database as a Service (DBaaS) in order to provide both *relational and
non-relational* database instances. So we have joined the *Trove* project.

Regarding non-relational database, we need that the DBaaS provides
*MongoDB*instances. I have noticed that
here<https://blueprints.launchpad.net/trove/+spec/single-instance-mongodb-ga>there
is an initial project.


1)   How can I contribute to the develop of that project? Is there some
initial source code?


2) Are there other active projects on MongoDB that I can install and
test on the Openstack platform?


Regards.


Giuseppe Galeota
Bari - ITALY
g.gale...@reply.it
www.reply.it  <http://www.reply.it>

giuseppegale...@gmail.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack] [TROVE] database instance creation

[Giuseppe Galeota]

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?

Giuseppe


2013/9/9 Daniel Salinas 

> 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.
>
>
> On Mon, Sep 9, 2013 at 9:21 AM, Giuseppe Galeota <
> giuseppegale...@gmail.com> wrote:
>
>> Dear all,
>> reading the TROVE's 
>> Doc<http://docs.openstack.org/developer/trove/dev/design.html>I see that 
>> Trove is designed to support a single-tenant database within a
>> Nova instance.
>>
>> What does means this?
>>
>> Does it mean that Trove creates a single VM instance in which a single
>> database instance is created?
>>
>> Does it mean that Trove creates a single VM instance in which a more
>> database instances of a single tenant are created ?
>>
>> Thank you,
>> Giuseppe
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openst...@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack] [TROVE] database instance creation

[Giuseppe Galeota]

Dear all,
reading the TROVE's
Doc<http://docs.openstack.org/developer/trove/dev/design.html>
 I see that "The trove-taskmanager service does the heavy lifting as far as
provisioning instances, managing the lifecycle of instances, and performing
operations on the *Database instance*".

So, once an instance was created, how does an application deployed in the
cloud platform (IaaS or PaaS level) perform CRUD operation on that database
instance? Maybe, does the trove-taskmanager release an endpoint on which
create a DBMS connection?

Giuseppe


2013/9/9 Daniel Salinas 

> 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.
>
>
> On Mon, Sep 9, 2013 at 9:21 AM, Giuseppe Galeota <
> giuseppegale...@gmail.com> wrote:
>
>> Dear all,
>> reading the TROVE's 
>> Doc<http://docs.openstack.org/developer/trove/dev/design.html>I see that 
>> Trove is designed to support a single-tenant database within a
>> Nova instance.
>>
>> What does means this?
>>
>> Does it mean that Trove creates a single VM instance in which a single
>> database instance is created?
>>
>> Does it mean that Trove creates a single VM instance in which a more
>> database instances of a single tenant are created ?
>>
>> Thank you,
>> Giuseppe
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openst...@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [TROVE] database instance creation

[Giuseppe Galeota]

Dear all,
reading the TROVE's
DocI see
that Trove is designed to support a single-tenant database within a
Nova instance.

What does means this?

Does it mean that Trove creates a single VM instance in which a single
database instance is created?

Does it mean that Trove creates a single VM instance in which a more
database instances of a single tenant are created ?

Thank you,
Giuseppe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Trove] Modify source code for Postgres engine

[Giuseppe Galeota]

Dear all,
this is a technical question. I would try to modify the source code of
Trove in order to create databases instances using Postgres engine. I think
that it is necessary to modify the "create" method in the
"InstanceController" class. Is it right? What other things should I modify?

Thank you very much.
Giuseppe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Trove] Poor documentation about Trove architecture and operation.

[Giuseppe Galeota]

Hi Michael,
I am very grateful to you. I can't wait to see your documentation about
Trove/Reddwarf!


Giuseppe.

2013/9/6 Michael Basnight 

> On Sep 6, 2013, at 8:30 AM, Giuseppe Galeota 
> wrote:
>
> Dear all,
> I think that there is a poor documentation about Trove architecture and
> operation.
>
>
> Thanks for your interest in trove. I agree. As ptl I will devote time (now
> that the h3 madness has slowed for us) to doc'ing better information for
> you.
>
>
> 1) Can you link me a guide to the Trove architecture, in order to better
> understand how databases instances are created by Trove's components?
>
>
> Give me a bit, I'm pretty sure we had some reddwarf (pre rename) docs
> somewhere on the wiki. Ill try to find/reorg them today.
>
>
> Thank you very much,
> Giuseppe
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Trove]

[Giuseppe Galeota]

Dear all,
I think that there is a poor documentation about Trove architecture and
operation.

1) Can you link me a guide to the Trove architecture, in order to better
understand how databases instances are created by Trove's components?

Thank you very much,
Giuseppe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev