Open Stack

Hi Flavio,
my use case is simple… keep track of what happened in our cloud because 
in the future maybe I will need to know more information about the image that 
some VM used and meanwhile was deleted by the user.

I agree that after some time this information can be moved to shadow tables, or even 
deleted but in my opinion should be optional…

> The
> question we're asking ourselves right now is whether it is correct and
> useful to keep all that information in the database.


Also, I think we should ask,
what we really gain removing this information from the database?

cheers,
Belmiro

On May 22, 2013, at 9:45 AM, Flavio Percoco <flavio at redhat.com> wrote:

> On 22/05/13 00:13 +0200, Belmiro Moreira wrote:
>> Hi Iccha,
>> yes… but information like "created_at", "deleted_at" will not be in the instances.
>> Using notifications is a good idea but in that case we need to use something like stacky.
>> 
>> Of course we can go through the logs the get this information… but having this info in the DB is so handy.
>> 
>> Maybe I'm completely wrong but I don't see any inconvenient in keeping deleted images in the DB (even if in shadow tables like nova).
>> 
> 
> I'm still interested in a more detailed use case for this. The
> question we're asking ourselves right now is whether it is correct and
> useful to keep all that information in the database. I mean, are you
> using it for security issues? Image log? How big is the time frame you
> usually lookup? Do you ever clean that table?
> 
> All that can be either tracked with notifications and logs so, I'm not
> sure the fact of it being handy is enough as a use case.
> 
> Thanks for your comments
> FF
> 
> -- 
> { name: "Flavio Percoco",
>   gpg: "87112EC1",    internal: "8261386",
>   phone: "+390687502386",
>   irc: ["fpercoco", "flaper87"]}
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev