[one-users] one version after upgrading to 4.10.0
Hello. I have a little problem after upgrading to 4.10.0 (from 4.8.0). I did stop opennebula, upgraded opennebula and did: onedb upgrade -v --sqlite /var/lib/one/one.db -f Output: oneadmin@one-node1 ~ $ onedb upgrade -v --sqlite /var/lib/one/one.db -f Version read: Shared tables 4.6.0 : OpenNebula 4.6.2 daemon bootstrap Local tables 4.9.80 : Database migrated from 4.7.80 to 4.9.80 (OpenNebula 4.9.80) by onedb command. Sqlite database backup stored in /var/lib/one/one.db.bck Use 'onedb restore' or copy the file back to restore the DB. Running migrators for shared tables Database already uses version 4.6.0 Running migrators for local tables Database already uses version 4.9.80 Total time: 0.00s oneadmin@one-node1 ~ $ Now i seem to have versioning mess i guess. :-) Mon Nov 3 22:21:02 2014 [Z0][ONE][I]: oned is using version 4.9.80 for local_db_versioning Mon Nov 3 22:21:02 2014 [Z0][ONE][I]: oned is using version 4.6.0 for db_versioning How can i solve this? cheers t. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] one version after upgrading to 4.10.0
Did you upgrade from 4.8.0? It looks like the DB is from a 4.10 beta. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebula cmar...@opennebula.org On Tue, Nov 4, 2014 at 9:34 AM, Thomas Stein himbe...@meine-oma.de wrote: Hello. I have a little problem after upgrading to 4.10.0 (from 4.8.0). I did stop opennebula, upgraded opennebula and did: onedb upgrade -v --sqlite /var/lib/one/one.db -f Output: oneadmin@one-node1 ~ $ onedb upgrade -v --sqlite /var/lib/one/one.db -f Version read: Shared tables 4.6.0 : OpenNebula 4.6.2 daemon bootstrap Local tables 4.9.80 : Database migrated from 4.7.80 to 4.9.80 (OpenNebula 4.9.80) by onedb command. Sqlite database backup stored in /var/lib/one/one.db.bck Use 'onedb restore' or copy the file back to restore the DB. Running migrators for shared tables Database already uses version 4.6.0 Running migrators for local tables Database already uses version 4.9.80 Total time: 0.00s oneadmin@one-node1 ~ $ Now i seem to have versioning mess i guess. :-) Mon Nov 3 22:21:02 2014 [Z0][ONE][I]: oned is using version 4.9.80 for local_db_versioning Mon Nov 3 22:21:02 2014 [Z0][ONE][I]: oned is using version 4.6.0 for db_versioning How can i solve this? cheers t. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] one version after upgrading to 4.10.0
Am 04.11.14 10:09, schrieb Carlos Martín Sánchez: Did you upgrade from 4.8.0? It looks like the DB is from a 4.10 beta. Hello Carlos. I have several development machines and on a few of them i have 4.10 beta running, yes. But not on this one. I'm 90% sure. Allthough it's absolutely possible i am wrong. cheers t. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebula cmar...@opennebula.org On Tue, Nov 4, 2014 at 9:34 AM, Thomas Stein himbe...@meine-oma.de wrote: Hello. I have a little problem after upgrading to 4.10.0 (from 4.8.0). I did stop opennebula, upgraded opennebula and did: onedb upgrade -v --sqlite /var/lib/one/one.db -f Output: oneadmin@one-node1 ~ $ onedb upgrade -v --sqlite /var/lib/one/one.db -f Version read: Shared tables 4.6.0 : OpenNebula 4.6.2 daemon bootstrap Local tables 4.9.80 : Database migrated from 4.7.80 to 4.9.80 (OpenNebula 4.9.80) by onedb command. Sqlite database backup stored in /var/lib/one/one.db.bck Use 'onedb restore' or copy the file back to restore the DB. Running migrators for shared tables Database already uses version 4.6.0 Running migrators for local tables Database already uses version 4.9.80 Total time: 0.00s oneadmin@one-node1 ~ $ Now i seem to have versioning mess i guess. :-) Mon Nov 3 22:21:02 2014 [Z0][ONE][I]: oned is using version 4.9.80 for local_db_versioning Mon Nov 3 22:21:02 2014 [Z0][ONE][I]: oned is using version 4.6.0 for db_versioning How can i solve this? cheers t. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] one version after upgrading to 4.10.0
Hi Thomas, The log says it is a 4.10beta (4.9.80) DB. And because the isn't any DB changes to the DB from 4.10 beta to 4.10.0, we don't have a migrator file. The onedb tool doesn't have anything to do, your DB is good to go. In case the double versions are confusing, let me clarify. The DB has two versions: local and shared. This is because of the federation architecture [1]. The shared tables haven't changed since 4.6, and the local tables changed from 4.8.0 to 4.9.80, but not from 4.9.80 to 4.10.0. Regards [1] http://docs.opennebula.org/4.10/advanced_administration/data_center_federation/introf.html -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebula cmar...@opennebula.org On Tue, Nov 4, 2014 at 10:12 AM, Thomas Stein himbe...@meine-oma.de wrote: Am 04.11.14 10:09, schrieb Carlos Martín Sánchez: Did you upgrade from 4.8.0? It looks like the DB is from a 4.10 beta. Hello Carlos. I have several development machines and on a few of them i have 4.10 beta running, yes. But not on this one. I'm 90% sure. Allthough it's absolutely possible i am wrong. cheers t. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebula cmar...@opennebula.org On Tue, Nov 4, 2014 at 9:34 AM, Thomas Stein himbe...@meine-oma.de wrote: Hello. I have a little problem after upgrading to 4.10.0 (from 4.8.0). I did stop opennebula, upgraded opennebula and did: onedb upgrade -v --sqlite /var/lib/one/one.db -f Output: oneadmin@one-node1 ~ $ onedb upgrade -v --sqlite /var/lib/one/one.db -f Version read: Shared tables 4.6.0 : OpenNebula 4.6.2 daemon bootstrap Local tables 4.9.80 : Database migrated from 4.7.80 to 4.9.80 (OpenNebula 4.9.80) by onedb command. Sqlite database backup stored in /var/lib/one/one.db.bck Use 'onedb restore' or copy the file back to restore the DB. Running migrators for shared tables Database already uses version 4.6.0 Running migrators for local tables Database already uses version 4.9.80 Total time: 0.00s oneadmin@one-node1 ~ $ Now i seem to have versioning mess i guess. :-) Mon Nov 3 22:21:02 2014 [Z0][ONE][I]: oned is using version 4.9.80 for local_db_versioning Mon Nov 3 22:21:02 2014 [Z0][ONE][I]: oned is using version 4.6.0 for db_versioning How can i solve this? cheers t. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] one version after upgrading to 4.10.0
Am 04.11.14 10:24, schrieb Carlos Martín Sánchez: Hi Thomas, Hi Carlos. The log says it is a 4.10beta (4.9.80) DB. And because the isn't any DB changes to the DB from 4.10 beta to 4.10.0, we don't have a migrator file. The onedb tool doesn't have anything to do, your DB is good to go. In case the double versions are confusing, let me clarify. The DB has two versions: local and shared. This is because of the federation architecture [1]. The shared tables haven't changed since 4.6, and the local tables changed from 4.8.0 to 4.9.80, but not from 4.9.80 to 4.10.0. I see. Thanks for the clarification. There is one thing left on my i don't understand list. Why is the sunstone server still showing version 4.8.0 for the opennebula node we just talked about? https://fluffycloud.de/public.php?service=filest=da549a369f324c686a46bc476594e434 ciao t. Regards [1] http://docs.opennebula.org/4.10/advanced_administration/data_center_federation/introf.html -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebula cmar...@opennebula.org On Tue, Nov 4, 2014 at 10:12 AM, Thomas Stein himbe...@meine-oma.de wrote: Am 04.11.14 10:09, schrieb Carlos Martín Sánchez: Did you upgrade from 4.8.0? It looks like the DB is from a 4.10 beta. Hello Carlos. I have several development machines and on a few of them i have 4.10 beta running, yes. But not on this one. I'm 90% sure. Allthough it's absolutely possible i am wrong. cheers t. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebula cmar...@opennebula.org On Tue, Nov 4, 2014 at 9:34 AM, Thomas Stein himbe...@meine-oma.de wrote: Hello. I have a little problem after upgrading to 4.10.0 (from 4.8.0). I did stop opennebula, upgraded opennebula and did: onedb upgrade -v --sqlite /var/lib/one/one.db -f Output: oneadmin@one-node1 ~ $ onedb upgrade -v --sqlite /var/lib/one/one.db -f Version read: Shared tables 4.6.0 : OpenNebula 4.6.2 daemon bootstrap Local tables 4.9.80 : Database migrated from 4.7.80 to 4.9.80 (OpenNebula 4.9.80) by onedb command. Sqlite database backup stored in /var/lib/one/one.db.bck Use 'onedb restore' or copy the file back to restore the DB. Running migrators for shared tables Database already uses version 4.6.0 Running migrators for local tables Database already uses version 4.9.80 Total time: 0.00s oneadmin@one-node1 ~ $ Now i seem to have versioning mess i guess. :-) Mon Nov 3 22:21:02 2014 [Z0][ONE][I]: oned is using version 4.9.80 for local_db_versioning Mon Nov 3 22:21:02 2014 [Z0][ONE][I]: oned is using version 4.6.0 for db_versioning How can i solve this? cheers t. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] resize VM storage
Hi all, With sunstone [1] can i resize a vm disk (example from 10G to 50G or viceversa)? Thanks. [1] http://dev.opennebula.org/issues/1727 [1] Giancarlo. Links: -- [1] http://dev.opennebula.org/issues/1727 ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Easy provisioning missing from newer versions of Opennebula?
Hi, I have tried Opennebula 4.2.0 and liked the easy provisioning wizard - a user could select a template and combine it with his persistent image to create a VM without the need to create a separate template. It seems that this function is missing from Opennebula 4.8.0, requiring eveyone to create a template for each VM and making the VM creation process complicated: 1) Clone, upload or create a blank image (persistent) 2) Create a template that uses that image 3) Create a VM that uses that template. If the user need 5 identical VMs they have to create 5 separate templates that differ only in the images. Is there a way to simplify this process? One way is to create a template without an image, create a VM from it, then start the VM and attach the image. This seems easier than creating templates for each VM, however this also has problems. Since attaching the disk requires the VM to be running, the VM is deployed with zero storage requirements, so it may be deployed to a host that has insufficient storage for when the user tries to add a 1TB image leading to problems. Our users use the virtual machines as VDS, so persistent images are important (deleting a VM may not mean I want to delete the data). ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] resize VM storage
This is currently not implemented... Cheers Ruben On Tue Nov 04 2014 at 12:33:17 PM Giancarlo De Filippis gdefilip...@ltbl.it wrote: Hi all, With sunstone [1] can i resize a vm disk (example from 10G to 50G or viceversa)? Thanks. [1] http://dev.opennebula.org/issues/1727 Giancarlo. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Users can't create VMs with large capacity (in the cloud view)
OK, I understand it now. Then, does Opennebula support any kind of overcommitting or something? Pavel Tankov On 11/03/2014 07:29 PM, Carlos Martín Sánchez wrote: Hi, On Tue, Oct 28, 2014 at 1:06 PM, Pavel Tankov pavel.tan...@strategyobject.com mailto:pavel.tan...@strategyobject.com wrote: Does host 0 have enough capacity? Those numbers refer to the allocated capacity, as can be seen in sunstone or the onehost show output. Well, capacity could mean many things. I am not sure. See the attached screen shot. The hosts have 2 kinds of capacity: real and allocated. Real is the cpu/mem as reported by the monitoring probes. Allocated is the amount of cpu/mem requested by the VMs running on this host. This is the one used for scheduling. In your case, the new VM requests 400 cpu. But the host has already allocated 500 out of 800, this is why the scheduler decides that it doesn't fit. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org http://www.OpenNebula.org | cmar...@opennebula.org mailto:cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebulamailto:cmar...@opennebula.org On Tue, Oct 28, 2014 at 1:06 PM, Pavel Tankov pavel.tan...@strategyobject.com mailto:pavel.tan...@strategyobject.com wrote: That's strange. You should have the following message: Sched Message: No host with enough capacity to deploy the VM I understand, but there is nothing there. Absolutely empty. Does host 0 have enough capacity? Those numbers refer to the allocated capacity, as can be seen in sunstone or the onehost show output. Well, capacity could mean many things. I am not sure. See the attached screen shot. Pavel Tankov On 10/28/2014 12:06 PM, Carlos Martín Sánchez wrote: Hi, On Mon, Oct 27, 2014 at 1:17 PM, Pavel Tankov pavel.tankov@strategyobject.__com mailto:pavel.tan...@strategyobject.com mailto:pavel.tankov@__strategyobject.com mailto:pavel.tan...@strategyobject.com wrote: Admins and advanced users can see the scheduler error messages in sunstone, under the placement VM tab. That's what I meant when I said there are no logs. That's strange. You should have the following message: Sched Message: No host with enough capacity to deploy the VM On the other hand, I didn't know about /var/log/one/sched.log. Here is what I found there: Mon Oct 27 14:15:52 2014 [Z0][VM][D]: Pending/rescheduling VM and capacity requirements: VM CPU Memory System DS Image DS --__-- 110 400 2097152 10240 DS 1: 0 Mon Oct 27 14:15:52 2014 [Z0][HOST][D]: Discovered Hosts (enabled): 0 Mon Oct 27 14:15:52 2014 [Z0][SCHED][D]: VM 110: Host 0 filtered out. Not enough capacity. Mon Oct 27 14:15:52 2014 [Z0][SCHED][I]: Scheduling Results: and it keeps repeating. Pavel Tankov Does host 0 have enough capacity? Those numbers refer to the allocated capacity, as can be seen in sunstone or the onehost show output. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org http://www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org mailto:cmar...@opennebula.org mailto:cmar...@opennebula.org mailto:cmar...@opennebula.org__ | @OpenNebula http://twitter.com/opennebula__mailto:cmartin@opennebula.__org mailto:cmar...@opennebula.org _ Users mailing list Users@lists.opennebula.org mailto:Users@lists.opennebula.org http://lists.opennebula.org/__listinfo.cgi/users-opennebula.__org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Ruby 2.1.2
Hi, Opennebula 4.10 support for ruby 2.1.2 ? Thanks. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
