Re: [one-users] Fwd: Add New Storage Box
Hi, I don't entirely understand the difference between both options, could you explain in more detail what you mean by distributing the datastore to all the nodes? Assuming your configuration is as follows: NFS Server exports datastores 0 and 1 - Mounted in Frontend + Nodes I recommend the following option: - Create a new Image datastore (it will have ID = 100, in this example we will assume it has ID: 100) - Create a new exports directive in your new storage box, for example /storage/datastores/100 - Mount that mountpoint in all the nodes including the frontend in the following path: /var/lib/one/datastores/100 Now you can register more images in the new datastore (ID: 100), and since they are all persistent they will not take space in the system datastore (ID: 0) Best regards, Jaime On Tue, Aug 26, 2014 at 6:05 AM, Rhesa Mahendra rh...@lintasmediadanawa.com wrote: Guys, please help. Original Message Subject: Add New Storage Box Date: Mon, 25 Aug 2014 16:21:13 +0700 From: Rhesa Mahendra rh...@lintasmediadanawa.com rh...@lintasmediadanawa.com To: users@lists.opennebula.org users@lists.opennebula.org users@lists.opennebula.org, Javier Fontan jfon...@opennebula.org jfon...@opennebula.org Guys, We have plan to add a new storage box, Our existing storage : /var/lib/one/datastore/0 = system /var/lib/one/datastore/1 = image /var/lib/one/datastore/2 = file All type are from one storage box. We did internal discuss and we get result with two options: 1. We add a new storage box as an image type and define it as /var/lib/one/datastore/3 = image2. Or 2. We will distribute /var/lib/one/datastore/0 = system and /var/lib/one/datastore/2 = file to all nodes (all node are synced), then we add the new storage box as /var/lib/one/datastore/3 = image2 So with this second option, the nodes only mount two path from the storage box (/var/lib/one/datastore/1 = image [from existing storage box] and /var/lib/one/datastore/3 = image2 [from new storage box]). All the images are persistent Please give us some advise with pros and cons within this two options, thanks. Rhesa ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | jme...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Fwd: Add New Storage Box
Jaime, Thanks for your reply, now datastore 0 and datastore 2 are in existing storage box, mounted in frontend + nodes, we want to move datastore 0 and datastore 2 from existing storage box to frontend + nodes, could it be done? So in existing storage box just have datastore 1 and in new storage box just have datastore 100. Rhesa. On 08/26/2014 01:34 PM, Jaime Melis wrote: Hi, I don't entirely understand the difference between both options, could you explain in more detail what you mean by distributing the datastore to all the nodes? Assuming your configuration is as follows: NFS Server exports datastores 0 and 1 - Mounted in Frontend + Nodes I recommend the following option: - Create a new Image datastore (it will have ID = 100, in this example we will assume it has ID: 100) - Create a new exports directive in your new storage box, for example /storage/datastores/100 - Mount that mountpoint in all the nodes including the frontend in the following path: /var/lib/one/datastores/100 Now you can register more images in the new datastore (ID: 100), and since they are all persistent they will not take space in the system datastore (ID: 0) Best regards, Jaime On Tue, Aug 26, 2014 at 6:05 AM, Rhesa Mahendra rh...@lintasmediadanawa.com mailto:rh...@lintasmediadanawa.com wrote: Guys, please help. Original Message Subject:Add New Storage Box Date: Mon, 25 Aug 2014 16:21:13 +0700 From: Rhesa Mahendra rh...@lintasmediadanawa.com mailto:rh...@lintasmediadanawa.com To: users@lists.opennebula.org mailto:users@lists.opennebula.org users@lists.opennebula.org mailto:users@lists.opennebula.org, Javier Fontan jfon...@opennebula.org mailto:jfon...@opennebula.org Guys, We have plan to add a new storage box, Our existing storage : /var/lib/one/datastore/0 = system /var/lib/one/datastore/1 = image /var/lib/one/datastore/2 = file All type are from one storage box. We did internal discuss and we get result with two options: 1. We add a new storage box as an image type and define it as /var/lib/one/datastore/3 = image2. Or 2. We will distribute /var/lib/one/datastore/0 = system and /var/lib/one/datastore/2 = file to all nodes (all node are synced), then we add the new storage box as /var/lib/one/datastore/3 = image2 So with this second option, the nodes only mount two path from the storage box (/var/lib/one/datastore/1 = image [from existing storage box] and /var/lib/one/datastore/3 = image2 [from new storage box]). All the images are persistent Please give us some advise with pros and cons within this two options, thanks. Rhesa ___ Users mailing list Users@lists.opennebula.org mailto:Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org http://www.OpenNebula.org | jme...@opennebula.org mailto:jme...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Fwd: Add New Storage Box
Rhesa, the problem is datastore 0, it's the system datastore. If you move it to the local nodes, it will not be shared and synchronized across the nodes, therefore you will lose many benefits like live-migration and instant persintant image VM deployment. Why is it that you want to move datastore 0 to the frontend + nodes? On Tue, Aug 26, 2014 at 8:44 AM, Rhesa Mahendra rh...@lintasmediadanawa.com wrote: Jaime, Thanks for your reply, now datastore 0 and datastore 2 are in existing storage box, mounted in frontend + nodes, we want to move datastore 0 and datastore 2 from existing storage box to frontend + nodes, could it be done? So in existing storage box just have datastore 1 and in new storage box just have datastore 100. Rhesa. On 08/26/2014 01:34 PM, Jaime Melis wrote: Hi, I don't entirely understand the difference between both options, could you explain in more detail what you mean by distributing the datastore to all the nodes? Assuming your configuration is as follows: NFS Server exports datastores 0 and 1 - Mounted in Frontend + Nodes I recommend the following option: - Create a new Image datastore (it will have ID = 100, in this example we will assume it has ID: 100) - Create a new exports directive in your new storage box, for example /storage/datastores/100 - Mount that mountpoint in all the nodes including the frontend in the following path: /var/lib/one/datastores/100 Now you can register more images in the new datastore (ID: 100), and since they are all persistent they will not take space in the system datastore (ID: 0) Best regards, Jaime On Tue, Aug 26, 2014 at 6:05 AM, Rhesa Mahendra rh...@lintasmediadanawa.com wrote: Guys, please help. Original Message Subject: Add New Storage Box Date: Mon, 25 Aug 2014 16:21:13 +0700 From: Rhesa Mahendra rh...@lintasmediadanawa.com rh...@lintasmediadanawa.com To: users@lists.opennebula.org users@lists.opennebula.org users@lists.opennebula.org, Javier Fontan jfon...@opennebula.org jfon...@opennebula.org Guys, We have plan to add a new storage box, Our existing storage : /var/lib/one/datastore/0 = system /var/lib/one/datastore/1 = image /var/lib/one/datastore/2 = file All type are from one storage box. We did internal discuss and we get result with two options: 1. We add a new storage box as an image type and define it as /var/lib/one/datastore/3 = image2. Or 2. We will distribute /var/lib/one/datastore/0 = system and /var/lib/one/datastore/2 = file to all nodes (all node are synced), then we add the new storage box as /var/lib/one/datastore/3 = image2 So with this second option, the nodes only mount two path from the storage box (/var/lib/one/datastore/1 = image [from existing storage box] and /var/lib/one/datastore/3 = image2 [from new storage box]). All the images are persistent Please give us some advise with pros and cons within this two options, thanks. Rhesa ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | jme...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | jme...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Fwd: Add New Storage Box
Datastore 0 and datastore 2 will be synchronized frontend + nodes (we just use persistent image) so i think datastore 0 just synchronized symbolic link. If we have problem maybe existing storage box (datastore 1) broken, all vm used new storage box ( datastore 100) will not impact with datastore 1 because datastore 0 shared and synchronized across frontend +nodes. it possible? Rhesa On 08/26/2014 01:52 PM, Jaime Melis wrote: Rhesa, the problem is datastore 0, it's the system datastore. If you move it to the local nodes, it will not be shared and synchronized across the nodes, therefore you will lose many benefits like live-migration and instant persintant image VM deployment. Why is it that you want to move datastore 0 to the frontend + nodes? On Tue, Aug 26, 2014 at 8:44 AM, Rhesa Mahendra rh...@lintasmediadanawa.com mailto:rh...@lintasmediadanawa.com wrote: Jaime, Thanks for your reply, now datastore 0 and datastore 2 are in existing storage box, mounted in frontend + nodes, we want to move datastore 0 and datastore 2 from existing storage box to frontend + nodes, could it be done? So in existing storage box just have datastore 1 and in new storage box just have datastore 100. Rhesa. On 08/26/2014 01:34 PM, Jaime Melis wrote: Hi, I don't entirely understand the difference between both options, could you explain in more detail what you mean by distributing the datastore to all the nodes? Assuming your configuration is as follows: NFS Server exports datastores 0 and 1 - Mounted in Frontend + Nodes I recommend the following option: - Create a new Image datastore (it will have ID = 100, in this example we will assume it has ID: 100) - Create a new exports directive in your new storage box, for example /storage/datastores/100 - Mount that mountpoint in all the nodes including the frontend in the following path: /var/lib/one/datastores/100 Now you can register more images in the new datastore (ID: 100), and since they are all persistent they will not take space in the system datastore (ID: 0) Best regards, Jaime On Tue, Aug 26, 2014 at 6:05 AM, Rhesa Mahendra rh...@lintasmediadanawa.com mailto:rh...@lintasmediadanawa.com wrote: Guys, please help. Original Message Subject:Add New Storage Box Date: Mon, 25 Aug 2014 16:21:13 +0700 From: Rhesa Mahendra rh...@lintasmediadanawa.com mailto:rh...@lintasmediadanawa.com To: users@lists.opennebula.org mailto:users@lists.opennebula.org users@lists.opennebula.org mailto:users@lists.opennebula.org, Javier Fontan jfon...@opennebula.org mailto:jfon...@opennebula.org Guys, We have plan to add a new storage box, Our existing storage : /var/lib/one/datastore/0 = system /var/lib/one/datastore/1 = image /var/lib/one/datastore/2 = file All type are from one storage box. We did internal discuss and we get result with two options: 1. We add a new storage box as an image type and define it as /var/lib/one/datastore/3 = image2. Or 2. We will distribute /var/lib/one/datastore/0 = system and /var/lib/one/datastore/2 = file to all nodes (all node are synced), then we add the new storage box as /var/lib/one/datastore/3 = image2 So with this second option, the nodes only mount two path from the storage box (/var/lib/one/datastore/1 = image [from existing storage box] and /var/lib/one/datastore/3 = image2 [from new storage box]). All the images are persistent Please give us some advise with pros and cons within this two options, thanks. Rhesa ___ Users mailing list Users@lists.opennebula.org mailto:Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org http://www.OpenNebula.org | jme...@opennebula.org mailto:jme...@opennebula.org ___ Users mailing list Users@lists.opennebula.org mailto:Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org http://www.OpenNebula.org | jme...@opennebula.org mailto:jme...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] CentOS 7 - KVM - OpenNebula 4.8 from Marketplace doesn't start
We are going to convert it to a more compatible version and reupload. Hello, guys. Any progress on that? Thanks. On 08/21/2014 04:23 PM, Javier Fontan wrote: We found a problem with the format of that image. It only works with qemu = 1.10. We are going to convert it to a more compatible version and reupload. In case you have a machine with a newer qemu version you can use this command to convert it: $ qemu-img convert -f qcow2 -O qcow2 -o compat=0.10 orig_image dest_image Sorry for the inconveniences. On Thu, Aug 21, 2014 at 10:16 AM, Pavel Tankov pavel.tan...@strategyobject.com wrote: Hello Users, I have the following setup: Physical host: CentOS 6.5 (64 bit, of course), KVM, all set up following the Quickstart Guide here: http://docs.opennebula.org/4.8/design_and_installation/quick_starts/qs_centos_kvm.html Opennebula 4.8.0 I got from the Marketplace the image named CentOS 7 - KVM - OpenNebula 4.8. Imported it and it and created the template automatically for me. I modified the template to add my ssl public key to be able to login as root, added a network and pretty much that was it. I tried to instantiate the template, but the VM keeps getting into the FAILED status. Do you have any idea why it wouldn't start? Thanks in advance. Here is the VM log: BEGIN LOG Wed Jul 30 18:00:53 2014 [DiM][I]: New VM state is ACTIVE. Wed Jul 30 18:00:53 2014 [LCM][I]: New VM state is PROLOG. Wed Jul 30 18:00:56 2014 [LCM][I]: New VM state is BOOT Wed Jul 30 18:00:56 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Wed Jul 30 18:00:56 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:56 2014 [VMM][I]: Successfully execute network driver operation: pre. Wed Jul 30 18:00:57 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:57 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Wed Jul 30 18:00:57 2014 [VMM][I]: ExitCode: 0 Wed Jul 30 18:00:57 2014 [VMM][I]: Successfully execute network driver operation: post. Wed Jul 30 18:00:57 2014 [LCM][I]: New VM state is RUNNING Thu Jul 31 14:03:18 2014 [LCM][I]: New VM state is SHUTDOWN Thu Jul 31 14:03:51 2014 [VMM][I]: ExitCode: 0 Thu Jul 31 14:03:51 2014 [VMM][I]: Successfully execute virtualization driver operation: shutdown. Thu Jul 31 14:03:51 2014 [VMM][I]: ExitCode: 0 Thu Jul 31 14:03:51 2014 [VMM][I]: Successfully execute network driver operation: clean. Thu Jul 31 14:03:51 2014 [LCM][I]: New VM state is EPILOG Thu Jul 31 14:03:51 2014 [DiM][I]: New VM state is DONE Thu Aug 7 12:09:20 2014 [DiM][I]: New VM state is ACTIVE. Thu Aug 7 12:09:20 2014 [LCM][I]: New VM state is PROLOG. Thu Aug 7 12:09:21 2014 [LCM][I]: New VM state is BOOT Thu Aug 7 12:09:21 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Thu Aug 7 12:09:21 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:21 2014 [VMM][I]: Successfully execute network driver operation: pre. Thu Aug 7 12:09:22 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:22 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Thu Aug 7 12:09:22 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:09:22 2014 [VMM][I]: Successfully execute network driver operation: post. Thu Aug 7 12:09:22 2014 [LCM][I]: New VM state is RUNNING Thu Aug 7 12:24:05 2014 [LCM][I]: New VM state is SHUTDOWN Thu Aug 7 12:24:15 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:24:15 2014 [VMM][I]: Successfully execute virtualization driver operation: shutdown. Thu Aug 7 12:24:15 2014 [VMM][I]: ExitCode: 0 Thu Aug 7 12:24:15 2014 [VMM][I]: Successfully execute network driver operation: clean. Thu Aug 7 12:24:15 2014 [LCM][I]: New VM state is EPILOG Thu Aug 7 12:24:16 2014 [DiM][I]: New VM state is DONE Tue Aug 19 16:03:52 2014 [DiM][I]: New VM state is ACTIVE. Tue Aug 19 16:03:52 2014 [LCM][I]: New VM state is PROLOG. Tue Aug 19 16:03:53 2014 [LCM][I]: New VM state is BOOT Tue Aug 19 16:03:53 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/9/deployment.0 Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute network driver operation: pre. Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute virtualization driver operation: deploy. Tue Aug 19 16:03:53 2014 [VMM][I]: ExitCode: 0 Tue Aug 19 16:03:53 2014 [VMM][I]: Successfully execute network driver operation: post. Tue Aug 19 16:03:53 2014 [LCM][I]: New VM state is RUNNING Tue Aug 19 16:05:37 2014 [LCM][I]: New VM state is CLEANUP. Tue Aug 19 16:05:37 2014 [DiM][I]: New VM state is DONE Tue Aug 19 16:05:37 2014 [VMM][W]: Ignored: LOG I 9 Driver command for 9 cancelled Tue Aug 19 16:05:38 2014 [VMM][W]: Ignored: LOG I 9 error: failed to get domain 'one-9' Tue Aug 19 16:05:38 2014 [VMM][W]: Ignored: LOG I 9 error: Domain not found: no domain with matching name 'one-9' Tue Aug 19 16:05:38 2014 [VMM][W]: Ignored: LOG I 9 ExitCode: 0 Tue Aug 19 16:05:38 2014
Re: [one-users] Nomadic CentOS repository: WHY?!?
Probably we should have explained these changes more clearly in the release notes. There were two things we wanted to do with the repos: * Have repositories for development versions so it is easier to test * Separate repositories between series so the software is not upgraded accidentally from 4.6 to 4.8. In this case there are several configuration file changes that need to be addressed manually and we don't want to render an OpenNebula installation unusable with an upgrade. To do both things we create a new repo per series starting from the development versions. [1] Concerning the context packages. In 4.8 we moved the context packages code to an addon [2]. This makes easier to people to contribute and create new versions with bugfixes and features without the need of releasing a new OpenNebula version. Before this change the code was in the main repo and our package scripts also created context packages that were pushed to the repositories. This had a problem as sometimes the context packages from the repo and from our web page were not exactly the same. Now we build directly from the new repository and upload them to the files section of redmine [3] as Damon has pointed and to the github repository [4]. Both are binary. [1] http://dev.opennebula.org/issues/2843 [2] https://github.com/OpenNebula/addon-context-linux [3] http://dev.opennebula.org/projects/opennebula/files [4] https://github.com/OpenNebula/addon-context-linux/releases On Tue, Aug 26, 2014 at 2:43 AM, Bill Cole openneb-users-20120...@billmail.scconsult.com wrote: On 25 Aug 2014, at 19:40, Damon (Albino Geek) wrote: Hello, I found that there is actually a prebuilt 4.8 context RPM in one of their source trees (not GitHub). That's not exactly helpful. The fact that there's an RPM in some unnamed place built from who-knows-what revision is an interesting and maybe indicative factoid, but it does not clarify whether or not there will be a canonical RPM for the package in the same repository as those for the other packages (or anywhere documented.) As per the repo change, this new version actually makes more sense and follows proper repo format. http://mirrors.kernel.org/centos/6/os/x86_64/ being an example repository that follows standard format. The stable path part didn't make any sense considering how versions work in OpenNebula. The '4.8' part doesn't make any sense in any context, and *changing* the baseurl for the repository with each release does away with a key reason for using a package repository. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontán Muiños Developer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | @OpenNebula | github.com/jfontan ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Latest CentOS Dojo presentations
Dear all, we've just published the talks of the two recent Dojos: http://opennebula.org/aftermath-of-the-latest-centos-dojos-cologne-and-paris/ regards, Jaime -- Jaime Melis Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | jme...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Opennebula 4.8 Create VM
Hi. I have set the dialog width in the function setupCreateVMDialog of vms-tab.js to 1%: dialog.width(“1%”); With that set, the Create VM window renders OK in Google Chrome on Red Hat (except it is a bit large) and still renders OK in Google Chrome on Windows and in Firefox. I guess this is a workaround for now? Thanks, Lorraine From: Daniel Molina [mailto:dmol...@opennebula.org] Sent: Monday, August 25, 2014 6:13 AM To: PROULX, Lorraine (Lorraine) Cc: users@lists.opennebula.org Subject: Re: [one-users] Opennebula 4.8 Create VM Hi, Does it render ok if you resize the window to a larger size? Cheers On 22 August 2014 20:05, PROULX, Lorraine (Lorraine) lorraine.pro...@alcatel-lucent.commailto:lorraine.pro...@alcatel-lucent.com wrote: Hi. The Create Virtual Machine window does not render properly on Google chrome on Red Hat. I have included a screen capture of the window. The same window renders correctly on Firefox and on Google Chrome on Windows. Thanks, Lorraine [Screenshot.png] ___ Users mailing list Users@lists.opennebula.orgmailto:Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- -- Daniel Molina Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.orghttp://www.OpenNebula.org | dmol...@opennebula.orgmailto:dmol...@opennebula.org | @OpenNebula ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] unable to attach cdrom to VM in opennebula 4.8
Greetings, I am attempting to attach a CDROM image to a running VM via Sunstone but the command fails with the following error: Tue Aug 26 08:52:21 2014 [Z0][VMM][D]: Message received: LOG E 24 attach_disk: Command virsh --connect qemu:///system attach-device one-24 /var/lib/one//datastores/0/24/disk.3.attach failed: error: Failed to attach device from /var/lib/one//datastores/0/24/disk.3.attach Tue Aug 26 08:52:21 2014 [Z0][VMM][D]: Message received: LOG I 24 error: Failed to open file '/var/lib/one//datastores/0/24/disk.3': No such file or directory The disk.3.attach file looks like this: disk type='file' device='disk' driver name='qemu' type='raw' / source file='/var/lib/one//datastores/0/24/disk.3' /source target dev='hdd'/ readonly/ /disk The file listed in the source (disk.3), of course, does not exist. I've attempted to attach images from both a ceph store and the default image store with the same results. What can I do to fix this? Thanks -- Randall Smith Computing Services Adams State University http://www.adams.edu/ 719-587-7741 ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Debian Wheezy KVM 2.1
Hey guys, Are there any known issues running Wheezy together with QEMU/ KVM 2.1 from wheezy-backports and ONE 4.8? Thanks for sharing, Arnold -- Arnold Bechtoldt Karlsruhe, Germany 0xE2356889.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Opennebula 4.8 proble to upload iso
Hi when I create a template of type cdrom and try to upload dell'immagene iso I get the following error. TTP/1.1 500 Tue Aug 26 20:39:33 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:33] GET /image?timeout=falsecsrftoken=bf59266c40d563bfad0576a92cb00167 HTTP/1.1 401 - 0.0029 Tue Aug 26 20:39:33 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:33] GET /login HTTP/1.1 200 - 0.0627 Tue Aug 26 20:39:40 2014 [I]: Updating user pool cache. Tue Aug 26 20:39:40 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:40] POST /login HTTP/1.1 204 - 0.2957 Tue Aug 26 20:39:40 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:40] GET / HTTP/1.1 200 - 0.0479 Tue Aug 26 20:39:41 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:41] GET /zone?timeout=truecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0089 Tue Aug 26 20:39:41 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:41] GET /datastore?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0727 Tue Aug 26 20:39:41 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:41] GET /user?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0849 Tue Aug 26 20:39:41 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:41] GET /vnet?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0846 Tue Aug 26 20:39:41 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:41] GET /vm?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0761 Tue Aug 26 20:39:41 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:41] GET /host?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0701 Tue Aug 26 20:39:41 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:41] GET /user?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0148 Tue Aug 26 20:39:41 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:41] GET /group?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0103 Tue Aug 26 20:39:41 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:41] GET /acl?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0104 Tue Aug 26 20:39:42 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:42] GET /image?timeout=truecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0112 Tue Aug 26 20:39:42 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:42] GET /vmtemplate?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0113 Tue Aug 26 20:39:42 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:42] GET /cluster?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0105 Tue Aug 26 20:39:43 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:43] GET /service_template?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.1132 Tue Aug 26 20:39:43 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:43] GET /service?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.1167 Tue Aug 26 20:39:43 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:43] GET /cluster?timeout=truezone_id=0csrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.0164 Tue Aug 26 20:39:44 2014 [I]: 192.168.2.244 - - [26/Aug/2014 20:39:44] GET /marketplace?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.8899 Tue Aug 26 21:00:56 2014 [I]: 192.168.2.244 - - [26/Aug/2014 21:00:56] GET /image?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.4465 Tue Aug 26 21:01:30 2014 [I]: 192.168.2.244 - - [26/Aug/2014 21:01:30] GET /image?timeout=falsecsrftoken=d85164e3de3389b69675e4e350c47c36 HTTP/1.1 200 - 0.7304 Tue Aug 26 21:02:15 2014 [I]: 192.168.2.244 - - [26/Aug/2014 21:02:15] POST /upload?csrftoken=d85164e3de3389b69675e4e350c47c36img=%7B%22image%22%3A%7B%22NAME%22%3A%22cdrom1%22%2C%22TYPE%22%3A%22CDROM%22%2C%22PERSISTENT%22%3A%22NO%22%7D%2C%22ds_id%22%3A%22105%22%7Dfile=en_windows_server_2012_r2_with_update_x64_dvd_4065220.isoqqfile=en_windows_server_2012_r2_with_update_x64_dvd_4065220.iso HTTP/1.1 500 - 109.9501 Grazie *Vincenzo Barbieri* [image: Logo per firma mail - v01] via Borgazzi, 27 20900 Monza c.so Orbassano, 336 10137 Torino Mobile: (+39) 342 6521139 vincenzo.barbi...@blueit.it www.blueit.it [image: paolo] P Please consider the environment before printing this document Questo messaggio di posta elettronica contiene informazioni di carattere riservato, privato e confidenziali rivolte esclusivamente al destinatario sopra indicato. E' vietato l'uso, la diffusione, distribuzione o riproduzione da parte di ogni altra persona. Nel caso aveste ricevuto questo messaggio di posta elettronica per errore, siete pregati di segnalarlo immediatamente al mittente e distruggere quanto ricevuto (compresi i file allegati) senza farne copia. Qualsivoglia utilizzo non autorizzato del contenuto di questo messaggio costituisce violazione dell'obbligo di non prendere cognizione della corrispondenza tra altri soggetti, salvo piu grave illecito, ed espone il responsabile alle
Re: [one-users] Debian Wheezy KVM 2.1 (Users Digest, Vol 78, Issue 82)
Hi, We are testing Debian 7 (wheezy) with QEMU/KVM 2.1 and kernel from wheezy-backports. Still not in production. So far no problems (even Windows 2012 R2 works OK). (No ceph support, but it is not problem in our case). Regards, Rolandas P.S. Our testbed is OpenNebula 4.8. On 2014.08.26 21:32, Arnold Bechtoldt wrote: Hey guys, Are there any known issues running Wheezy together with QEMU/ KVM 2.1 from wheezy-backports and ONE 4.8? Thanks for sharing, Arnold ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
