[one-users] vm dirs recreated by opennebula

[Carlos Martín Sánchez]

Hi,

For OpenNebula, VMs are never completely deleted. You can still issue a
'onevm show', and see al the VMs in DONE state.
I think those directories are created when the VMs are cached again, maybe
because the accounting or statistics module.

If that's becoming an important issue for you, and you don't mind breaking
accounting and statistics, you can delete all VMs in DONE state from the
DB. Just make sure that you stop OpenNebula before that.


This has been requested before [1], so we will consider in the future to
add some configuration option to completely remove VMs that reach the DONE
state

Regards.

[1] http://dev.opennebula.org/issues/1026

--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | cmartin at opennebula.org |
@OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>


On Tue, Jan 31, 2012 at 1:53 PM, Olivier Sallou <olivier.sallou at irisa.fr>wrote:

> Hi,
> using version 3.0 of one, I face a strange behaviour sometimes. I think
> it occurs when stopping/starting some one processes but not sure.
>
> The VM dirs in /var/lib/one are recreated (though empty).
>
> When I delete a VM, I have a hook that deletes the VM dir in
> /var/lib/one. Fine.....
>
> Occasionally, open nebula recreates a directory for all previous created
> VM, empty, as shown below.
> As you can see, all VM dir have the same date/time.
>
> oneadmin at genokvm4:/local/one_images/cloud/vm$ ls -lstr one
> total 184
> 28 -rw-r--r-- 1 oneadmin oneadmin 25600  9 janv. 18:26 one.db
>  4 drwxr-x--T 2 oneadmin oneadmin  4096  9 janv. 18:26 images
>  4 -rw-r--r-- 1 oneadmin oneadmin    20  9 janv. 18:26 auth
>  4 drwxr-xr-x 8 oneadmin oneadmin  4096  9 janv. 18:26 remotes
>  4 -rw-r--r-- 1 oneadmin oneadmin   985 16 janv. 18:23 config
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 2
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 3
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 4
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 5
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 6
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 7
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 8
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 9
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 11
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 12
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 13
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 14
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 15
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 16
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 17
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 18
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 19
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 20
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 21
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 22
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 23
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 24
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 25
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 26
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 27
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 28
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 29
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 30
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 31
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 32
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 33
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 34
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 35
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 36
>  4 drwxrwxrwx 2 oneadmin oneadmin  4096 24 janv. 16:09 37
>
>
> This creates quite a mess in the directory....
>
> Any idea where it could come from?
>
> --
>
> gpg key id: 4096R/326D8438  (pgp.mit.edu)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120202/30fc3984/attachment-0002.htm>