[Users] What's the correct way to upload a VM ISO image?
Hi, I am a little confused by the quick start guide. It lists a command to upload the ISO image: engine-iso-uploader upload -i local-iso-share [file1] [file2] .... [fileN] My questions are: 1. Do I have to copy the files (ISO images) from somewhere else to the engine machine before using this cmd? If image files are on a different server, what's the right syntax to upload them? 2. Is "local-iso-share" the name of the ISO domain? For example, should I use "ISO_DOMAIN" if I have the following: ISO Storage Domain Name | Datacenter | ISO Domain Status ISO_DOMAIN | DC-CPA3 | active 3. If I don't use engine-iso-uploader command, instead I prefer to uploading the image myself. What is the right directory for me to put my images in? Is it /var/lib/exports/iso on the machine running the ovirt engine? Thanks. David
Von: users-bounces@ovirt.org [users-bounces@ovirt.org]" im Auftrag v= on "David Li [david_li@sbcglobal.net]=0A= Gesendet: Dienstag, 14. Januar 2014 21:06=0A= An: users@ovirt.org=0A= Betreff: [Users] What's the correct way to upload a VM ISO image?=0A= ...=0A= 3. If I don't use engine-iso-uploader command, instead I prefer =0A= to uploading the image myself. What is the right directory for =0A= me to put my images in? Is it /var/lib/exports/iso on the machine =0A= running the ovirt engine?=0A= =0A= We use NFS and uploaded the first image with the Uploader to find=0A=
This is a multi-part message in MIME format. ------=_NextPartTM-000-de656815-7533-4755-9914-db71ecd95f11 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable the right location.Aat least in our case we have very cryptic directory=0A= names:=0A= =0A= # pwd=0A= /rhev/data-center/mnt/10.10.30.253:_var_nas3_OVirtISO/bff3a2be-fdd9-4e37-b4= 16-fa4ef7fafba2/images/11111111-1111-1111-1111-111111111111=0A= # ls=0A= SLES-11-SP3-DVD-x86_64-GM-DVD1.iso=0A= SLES-11-SP3-DVD-x86_64-GM-DVD2.iso=0A= ...=0A= =0A= Even if the root folders do not match in your case I expect similar =0A= UUID based folder names.=0A= Markus= ------=_NextPartTM-000-de656815-7533-4755-9914-db71ecd95f11 Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" **************************************************************************** Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Über das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 **************************************************************************** ------=_NextPartTM-000-de656815-7533-4755-9914-db71ecd95f11--
Markus, Before upload, where was your image located? On the engine? On a different machine? David ----- Original Message -----
From: Markus Stockhausen <stockhausen@collogia.de> To: David Li <david_li@sbcglobal.net>; "users@ovirt.org" <users@ovirt.org> Cc: Sent: Tuesday, January 14, 2014 12:13 PM Subject: AW: [Users] What's the correct way to upload a VM ISO image?
Von: users-bounces@ovirt.org [users-bounces@ovirt.org]" im Auftrag von "David Li [david_li@sbcglobal.net] Gesendet: Dienstag, 14. Januar 2014 21:06 An: users@ovirt.org Betreff: [Users] What's the correct way to upload a VM ISO image? ... 3. If I don't use engine-iso-uploader command, instead I prefer to uploading the image myself. What is the right directory for me to put my images in? Is it /var/lib/exports/iso on the machine running the ovirt engine?
We use NFS and uploaded the first image with the Uploader to find the right location.Aat least in our case we have very cryptic directory names:
# pwd /rhev/data-center/mnt/10.10.30.253:_var_nas3_OVirtISO/bff3a2be-fdd9-4e37-b416-fa4ef7fafba2/images/11111111-1111-1111-1111-111111111111 # ls SLES-11-SP3-DVD-x86_64-GM-DVD1.iso SLES-11-SP3-DVD-x86_64-GM-DVD2.iso ...
Even if the root folders do not match in your case I expect similar UUID based folder names. Markus
Von: David Li [david_li@sbcglobal.net]=0A= Gesendet: Dienstag, 14. Januar 2014 22:48=0A= An: Markus Stockhausen; users@ovirt.org=0A= Betreff: Re: AW: [Users] What's the correct way to upload a VM ISO image?= =0A= =0A= Markus,=0A= =0A= Before upload, where was your image located? On the engine? On a differen= t machine?=0A= =0A= David=0A= =0A= I ran the iso uploader on the engine host with direct access =0A= to the file that I wanted to upload. Therefore I transfered the =0A= file to /tmp on the engine and started the upload. In our=0A= NFS case the file was created somewhere deep inside the=0A= ISO NFS mount point. UUID folder structure see answer =0A= before. =0A= =0A= Having direct access to our NFS servers we simply tried to=0A=
This is a multi-part message in MIME format. ------=_NextPartTM-000-90b63c0b-9766-465d-adff-3e53f57e0af4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable place other ISO files in the same cryptic directory and=0A= "tata" they are recognized. Conclusion: iso uploader does=0A= not insert references to those files into the engine database.=0A= =0A= Wherever your ISO domain is located you must simply=0A= "find it with iso uploader". Afterwards you can move around=0A= your ISO files as you like.=0A= =0A= Markus=0A= ------=_NextPartTM-000-90b63c0b-9766-465d-adff-3e53f57e0af4 Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" **************************************************************************** Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Über das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 **************************************************************************** ------=_NextPartTM-000-90b63c0b-9766-465d-adff-3e53f57e0af4--
What you described makes sense to me! Now I tried the second time after rebooting everything: engine-iso-uploader upload -v -i ISO_DOMAIN CentOS-6.4-x86_64-netinstall.iso & This time, it simply stopped without doing anything. Don't know what's going on, no error messages, no logs either. On the node, I found some traces from last time: [root@localhost 11111111-1111-1111-1111-111111111111]# ll -a total 7316 drwxr-xr-x. 2 vdsm kvm 4096 Jan 13 19:08 . drwxr-xr-x. 3 vdsm kvm 4096 Jan 8 18:13 .. -rw-r-----. 1 vdsm kvm 27447296 Jan 13 19:08 .CentOS-6.4-x86_64-netinstall.iso -rw-r--r--. 1 vdsm kvm 0 Jan 8 18:13 .keep I wonder if the last failed upload has left the uploader confused. It seems that it might think the same iso file has already be uploaded. Should I manually deleted the incomplete iso file? David ----- Original Message -----
From: Markus Stockhausen <stockhausen@collogia.de> To: David Li <david_li@sbcglobal.net>; "users@ovirt.org" <users@ovirt.org> Cc: Sent: Tuesday, January 14, 2014 9:43 PM Subject: AW: AW: [Users] What's the correct way to upload a VM ISO image?
Von: David Li [david_li@sbcglobal.net] Gesendet: Dienstag, 14. Januar 2014 22:48 An: Markus Stockhausen; users@ovirt.org Betreff: Re: AW: [Users] What's the correct way to upload a VM ISO image?
Markus,
Before upload, where was your image located? On the engine? On a different machine?
David
I ran the iso uploader on the engine host with direct access to the file that I wanted to upload. Therefore I transfered the file to /tmp on the engine and started the upload. In our NFS case the file was created somewhere deep inside the ISO NFS mount point. UUID folder structure see answer before.
Having direct access to our NFS servers we simply tried to place other ISO files in the same cryptic directory and "tata" they are recognized. Conclusion: iso uploader does not insert references to those files into the engine database.
Wherever your ISO domain is located you must simply "find it with iso uploader". Afterwards you can move around your ISO files as you like.
Markus
On 01/15/2014 06:53 PM, David Li wrote:
What you described makes sense to me!
Now I tried the second time after rebooting everything:
engine-iso-uploader upload -v -i ISO_DOMAIN CentOS-6.4-x86_64-netinstall.iso &
This time, it simply stopped without doing anything. Don't know what's going on, no error messages, no logs either.
On the node, I found some traces from last time:
[root@localhost 11111111-1111-1111-1111-111111111111]# ll -a total 7316 drwxr-xr-x. 2 vdsm kvm 4096 Jan 13 19:08 . drwxr-xr-x. 3 vdsm kvm 4096 Jan 8 18:13 .. -rw-r-----. 1 vdsm kvm 27447296 Jan 13 19:08 .CentOS-6.4-x86_64-netinstall.iso -rw-r--r--. 1 vdsm kvm 0 Jan 8 18:13 .keep
I wonder if the last failed upload has left the uploader confused. It seems that it might think the same iso file has already be uploaded. Should I manually deleted the incomplete iso file?
David
----- Original Message -----
From: Markus Stockhausen <stockhausen@collogia.de> To: David Li <david_li@sbcglobal.net>; "users@ovirt.org" <users@ovirt.org> Cc: Sent: Tuesday, January 14, 2014 9:43 PM Subject: AW: AW: [Users] What's the correct way to upload a VM ISO image?
Von: David Li [david_li@sbcglobal.net] Gesendet: Dienstag, 14. Januar 2014 22:48 An: Markus Stockhausen; users@ovirt.org Betreff: Re: AW: [Users] What's the correct way to upload a VM ISO image?
Markus,
Before upload, where was your image located? On the engine? On a different machine?
David
I ran the iso uploader on the engine host with direct access to the file that I wanted to upload. Therefore I transfered the file to /tmp on the engine and started the upload. In our NFS case the file was created somewhere deep inside the ISO NFS mount point. UUID folder structure see answer before.
Having direct access to our NFS servers we simply tried to place other ISO files in the same cryptic directory and "tata" they are recognized. Conclusion: iso uploader does not insert references to those files into the engine database.
Wherever your ISO domain is located you must simply "find it with iso uploader". Afterwards you can move around your ISO files as you like.
Markus
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
all the iso uploader is doing is to copy the .iso files to the 1111111111 folder created in the storage domain with 36:36 ownership and proper permissions.
David Li wrote:
What you described makes sense to me!
Now I tried the second time after rebooting everything:
engine-iso-uploader upload -v -i ISO_DOMAIN CentOS-6.4-x86_64-netinstall.iso &
It could be me, but doesn't engine-iso-uploader ask for the admin password to be able to upload? but how are you going to input that with the '&' at the end of your commandline? I bet if you do ps -ef | grep engine-iso you will find you process still waiting for you to type the password. Joop
On 01/16/2014 08:38 PM, Joop wrote:
David Li wrote:
What you described makes sense to me!
Now I tried the second time after rebooting everything:
engine-iso-uploader upload -v -i ISO_DOMAIN CentOS-6.4-x86_64-netinstall.iso &
It could be me, but doesn't engine-iso-uploader ask for the admin password to be able to upload? but how are you going to input that with the '&' at the end of your commandline? I bet if you do ps -ef | grep engine-iso you will find you process still waiting for you to type the password.
actually no. it asks for the admin password to get the nfs path from ovirt-engine (if you just give the domain name), and to ask the engine to refresh the iso domain (which would happen after 5 minutes as well). you can upload iso images without the engine password as well if you use the full nfs path.
participants (4)
-
David Li -
Itamar Heim -
Joop -
Markus Stockhausen