Ok thx :)

I had thought about doing that but I wondered if it blocked the database.


2014/1/7 Gianluca Cecchi <gianluca.cecchi@gmail.com>
On Tue, Jan 7, 2014 at 11:14 AM, Kevin Tib wrote:
> Hi all,
>
> i have not found how to delete an image. I uploaded my image with
> engine-iso-upload.
>
> Thx for answer ;)
>
> Kevin.

AFAIK there is no utility to delete images.
It should be supported to manually remove (and also put files), and
the ISO domain should be periodically rescan itself without any manual
action.
For example I just tried on a 3.3.2 on Fedora 19 engine to verify

# pwd
/var/lib/exports/iso/cc790a86-72e2-4aa2-a0b6-700756c399c3/images/11111111-1111-1111-1111-111111111111

# ll
total 13012236
-rw-r-----. 1 vdsm kvm 4672493568 Nov 22 15:22
CentOS-5.10-x86_64-bin-DVD-1of2.iso
-rw-r-----. 1 vdsm kvm 3770155008 Oct  7 14:04 CentOS-6.4-i386-bin-DVD1.iso
-rw-r-----. 1 vdsm kvm  198180864 Oct  7 08:58 CentOS-6.4-i386-netinstall.iso
-rw-r-----. 1 vdsm kvm 4353378304 Oct  3 13:51 CentOS-6.4-x86_64-bin-DVD1.iso
-rw-r-----. 1 vdsm kvm  330301440 Dec 12 14:34 Fedora-20-Beta-x86_64-netinst.iso

# rm Fedora-20-Beta-x86_64-netinst.iso
rm: remove regular file ‘Fedora-20-Beta-x86_64-netinst.iso’? y

After a few minutes I verified that I don't see anymore the Fedora 20
in the webadmin gui under iso domain, images subpane
Also, if I try to create a VM I don't find it listed in possible
images and the same if I try to change cd to a running VM.
So it seems consistent to me.

In engine log:
before
2014-01-07 11:31:46,271 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HsmGetIsoListVDSCommand] (a
jp--127.0.0.1-8702-11) FINISH, HsmGetIsoListVDSCommand, return:
[CentOS-6.4-x86_64-bin-DVD1.iso, Cen
tOS-5.10-x86_64-bin-DVD-1of2.iso, Fedora-20-Beta-x86_64-netinst.iso,
CentOS-6.4-i386-bin-DVD1.iso, C
entOS-6.4-i386-netinstall.iso], log id: 39a619c3
2014-01-07 11:31:46,272 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.GetIsoListVDSCommand]
(ajp--127.0.0.1-8702-11) FINISH, GetIsoListVDSCommand, return:
[CentOS-6.4-x86_64-bin-DVD1.iso, CentOS-5.10-x86_64-bin-DVD-1of2.iso,
Fedora-20-Beta-x86_64-netinst.iso, CentOS-6.4-i386-bin-DVD1.iso,
CentOS-6.4-i386-netinstall.iso], log id: 4bef06c7

After
2014-01-07 11:41:07,907 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HsmGetIsoListVDSCommand]
(ajp--127.0.0.1-8702-3) FINISH, HsmGetIsoListVDSCommand, return:
[CentOS-6.4-x86_64-bin-DVD1.iso, CentOS-5.10-x86_64-bin-DVD-1of2.iso,
CentOS-6.4-i386-bin-DVD1.iso, CentOS-6.4-i386-netinstall.iso], log id:
2dcf4b20
2014-01-07 11:41:07,908 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.GetIsoListVDSCommand]
(ajp--127.0.0.1-8702-3) FINISH, GetIsoListVDSCommand, return:
[CentOS-6.4-x86_64-bin-DVD1.iso, CentOS-5.10-x86_64-bin-DVD-1of2.iso,
CentOS-6.4-i386-bin-DVD1.iso, CentOS-6.4-i386-netinstall.iso], log id:
79a8a0b6

In my opinion, in theory you could also manually put new images,
according to keep their permissions such as above output:
owner:group  36:36
and
permissions 640

HIH,
Gianluca
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users