[one-users] Ruby problem Centos 7 pcsd and Opennebula
Good morning, I am building a block LVM KVM cluster with 4 machines, but i am having a strange problem which keeps me busy for days now, i am using a standard Centos 7 server as frontend and Centos 7 nodes with opennebula and opennebula-server installed. software installed opennebula-ruby-4.8.0-1.x86_64 opennebula-common-4.8.0-1.x86_64 opennebula-sunstone-4.8.0-1.x86_64 opennebula-4.8.0-1.x86_64 opennebula-server-4.8.0-1.x86_64 I also installed pcs-0.9.115-32.el7_0.1.x86_64 to use clvmd en dlm locks on the opennebula nodes and frontend. Now the problem i am facing i have installed pcsd (ruby) and opennebula (ruby) on the same machine, when i install rack and sinatra via gems as ordered by the install in the documentation the psc daemon binds only to the localhost interface. If i uninstall sinatra and rack then the psc daemon listens as ordered via the config file on all interfaces but opennebula won't start! After installing sinatra via gems their are 2 versions of sinatra on the system /usr/lib/pcsd/vendor/bundle/ruby/gems/sinatra-1.4.4/lib/sinatra /usr/local/share/gems/gems/sinatra-1.4.5/lib/sinatra So i assume something is overruling BindAddress directive in the config of pscd on centos 7 when i install the software needed to run opennebula. I have tried setting the BindAddress directive in ssl.rb to *, nil and :: but nothing fixes the problem also my knowledge of ruby is to low to investigate further. see below howto reproduce this problem [root@cloudmanager rack-1.6.0]# !lsof lsof -i | grep ruby ruby 1368 root9u IPv6 1474379 0t0 TCP localhost:efi-mg (LISTEN) ruby 1368 root 10u IPv4 1474380 0t0 TCP localhost:efi-mg (LISTEN) ruby 13803 oneadmin 10u IPv4 913310 0t0 TCP *:9869 (LISTEN) [root@cloudmanager rack-1.6.0]# gem uninstall sinatra rack Successfully uninstalled sinatra-1.4.5 Successfully uninstalled rack-1.6.0 [root@cloudmanager rack-1.6.0]# systemctl restart pcsd.service [root@cloudmanager rack-1.6.0]# !lsof lsof -i | grep ruby ruby 4377 root9u IPv4 1739444 0t0 TCP *:efi-mg (LISTEN) ruby 13803 oneadmin 10u IPv4 913310 0t0 TCP *:9869 (LISTEN) [root@cloudmanager tmp]# gem install sinatra Successfully installed rack-1.6.0 Successfully installed sinatra-1.4.5 [root@cloudmanager tmp]# systemctl restart pcsd.service [root@cloudmanager tmp]# !lsof lsof -i | grep ruby ruby 4551 root9u IPv6 1740682 0t0 TCP localhost:efi-mg (LISTEN) ruby 4551 root 10u IPv4 1740683 0t0 TCP localhost:efi-mg (LISTEN) ruby 13803 oneadmin 10u IPv4 913310 0t0 TCP *:9869 (LISTEN) Any tips how i can solve this problem? Regards Constan ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Migrating from 1.2/1.4 to 2.x : official support ?
Hallo people. I have updated the Request #415(Migration path from 1.4 to 2.0.1) with the new scripts, be aware I have not testet it, the output sql seems to be fine, althought: http://dev.opennebula.org/issues/415 Best regards Marlon Nerling Zitat von Ruben S. Montero rube...@dacya.ucm.es: Hi, The data-model of OpenNebula is now stable and we do not foresee any changes in the upcoming versions. OpenNebula 2.2 should be compatible with the 2.0.x releases. Cheers Ruben On Mon, Jan 24, 2011 at 8:53 AM, Damien Raude-Morvan draz...@drazzib.comwrote: Hi everyone, Since I'm a user of several OpenNebula versions (1.4 and 2.0) and a packager of latest one (2.0.1), I'm wondering about upgrade process between all this. I've asked the same question last September and Ruben S. Montero answered to me that this [Opennebula team members] are thinking about this [1] :) I've also found the following reports which seems to provide some scripts / ideas for implementation : - upgrade from 1.2 to 1.4 [2] - upgrade from 1.4 to 2.0 [3] So is there any official support of upgrade process planned for 2.2 ? Is there scripts which will work for mysql + sqlite ? Thanks in advance for your feedback. [1] http://lists.opennebula.org/pipermail/users-opennebula.org/2010- September/002865.html [2] http://dev.opennebula.org/issues/181 [3] http://dev.opennebula.org/issues/415 Regards, -- Damien ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Dr. Ruben Santiago Montero Associate Professor (Profesor Titular), Complutense University of Madrid URL: http://dsa-research.org/doku.php?id=people:ruben Weblog: http://blog.dsa-research.org/?author=7 ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] OpenNebula 2.0.1 sets incorrect ARCH.
Has 1.4 some workaround for this? Zitat von carsten.friedr...@csiro.au: Thanks! This did the trick. And for anybody reads this with the same problem, the correct value for intel 64 bit is x86_64, not the one I mentioned earlier. Carsten From: j.me...@gmail.com [mailto:j.me...@gmail.com] On Behalf Of Jaime Melis Sent: Friday, 10 December 2010 1:22 To: Friedrich, Carsten (ICT Centre, Acton) Cc: users@lists.opennebula.org Subject: Re: [one-users] OpenNebula 2.0.1 sets incorrect ARCH. Hi, I forgot to mention that you can define it on a per vm basis in the VM template: http://opennebula.org/documentation:rel2.0:template#os_and_boot_options_section cheers, Jaime On Thu, Dec 9, 2010 at 3:19 PM, Jaime Melis j.me...@fdi.ucm.esmailto:j.me...@fdi.ucm.es wrote: Hello Carsten, you can change it here: $ONE_LOCATION/etc/vmm_ssh/vmm_ssh_kvm.conf cheers, Jaime On Thu, Dec 9, 2010 at 6:38 AM, carsten.friedr...@csiro.au wrote: Hi, I just installed 2.0.1 on a machine which now seems to set the 'arch' attribute in os-type. Unfortunately it sets an incorrect value: It sets 'i686', the correct value for my system is 'x86-64'. How does OpenNebula determine the value it sets (I use kvm with Ubuntu 10.4 64Bit as OS and in the VM)? Carsten ___ Users mailing list Users@lists.opennebula.orgmailto: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] stuck in boot
Hallo Luca.. could you please be somehow verboser to which is the problem with qcow2 in the version 2.0? I'm planing my migration to this version and it would be a no go for me if I could not use qcow2. Br Marlon Zitat von Luca Lorenzini lorenzini.l...@gmail.com: there are some issues with qcow2 format in version 2.0, try with a raw image On Thu, Nov 25, 2010 at 12:37 PM, Muhammad Daif daif.cont...@gmail.comwrote: Hi, I am new to Opennbula and I was trying to deploy a simple cloud. I used the following configurations: Name = nebula cpu = 0.1 memory = 64 Disk = [ source = /var/lib/one/images/tmp1N2BrS.qcow2, target = sda1, readonly = no] NIC = [network = small network] features =[acpi=no] the machine sticks in boot state. The new log file ends with New VM state is BOOT. Generating deployment file /var/lib/one/7/deployment.0 what can I do to pass the boot state ? thanks -- Muhammad Ahmad Daif ___ 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] oned does not listen
Hallo Gian. I'm not sure it this is you problem, but I think the one is off! One has not init script per default, so after reboot the opennebula daemons are not automaticly started. For this create a /etc/init./opennebula and register it against you init daemon. Best regards Marlon Nerling Zitat von sa...@eng.it: Hello gentlemen, and let me apologize for this newbie question. A co-worker (who left) successfully did install the OpenNebula front end and an handful of nodes. Then the newbie (me) had the 'clever' idea to install a new kernel, and after the reboot oned no more did listen on the configured port. Is it really bound to the kernel change ? How can I investigate and fix the problem ? Thanks in advance. -- Gian Friends will be friends right to the end! ___ 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] Migration Path from 1.4 to 2.0
I posted the last scripts and a tiny how-to under: Request #415: http://dev.opennebula.org/issues/415 Lucky migration! Greats Marlon Nerling ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Making scheduler allocation aware
Hallo Shashank.
I'm having the same problem in 1.4.
You must workaround it by youself, so instead of using onevm directly,
use it with a wrapper script who looks and waits for deploy if a VM is
pending.
I hope this behaviour is fixed on 2.0 (Hallo developers??)
Best regards
Marlon
Zitat von Shashank Rachamalla shashank.rachama...@hexagrid.com:
Hi Javier
Thanks for the inputs but I came across another problem while testing:
If opennebula receives multiple vm requests in a short span of time, the
scheduler might take decisions for all these vms considering the host
monitoring information available from the last monitoring cycle. Ideally,
before processing every pending request, fresh host monitoring information
has to be taken into account as the previous set of requests might have
already changed the host’s state. This can result in over committing when
host is being used close to its full capacity.
*Is there any workaround which helps the scheduler to overcome the above
problem ?*
steps to reproduce the problem scenario:
Host 1 : Total memory = 3GB
Host 2 : Total memory = 2GB
Assume Host1 and Host2 have same number of CPU cores. ( Host1 will have a
higher RANK value )
VM1: memory = 2GB
VM2: memroy = 2GB
Start VM1 and VM2 immediately one after the other. Both VM1 and VM2 will
come up on Host1. ( Thus over committing )
Start VM1 and VM2 with an intermediate delay of 60sec. VM1 will come up on
Host1 and VM2 will come up on Host2. This is true because opennebula would
have fetched a fresh set of host monitoring information in that time.
On 4 November 2010 02:04, Javier Fontan jfon...@gmail.com wrote:
Hello,
It looks fine to me. I think that taking out the memory the hypervisor
may be consuming is key to make it work.
Bye
On Wed, Nov 3, 2010 at 8:32 PM, Rangababu Chakravarthula
rb...@hexagrid.com wrote:
Javier
Yes we are using KVM and OpenNebula 1.4.
We have been having this problem since a long time and we were doing all
kinds of validations ourselves before submitting the request to
OpenNebula.
(there should be enough memory in the cloud that matches the requested
memory there should be atleast one host that has memory requested
memory
) We had to do those because OpenNebula would schedule to an arbitrary
host based on the existing logic it had.
So at last we thought that we need to make OpenNebula aware of memory
allocated of running VM's on the host and started this discussion.
Thanks for taking up this issue as priority. Appreciate it.
Shashank came up with this patch to kvm.rb. Please take a look and let us
know if that will work until we get a permanent solution.
$mem_allocated_for_running_vms=0
for i in `virsh list|grep running|tr -s ' ' ' '|cut -f2 -d' '` do
$dominfo=`virsh dominfo #{i}`
$dominfo.split(/\n/).each{|line|
if line.match('^Max memory')
$mem_allocated_for_running_vms += line.split(
)[2].strip.to_i
end
}
end
$mem_used_by_base_hypervisor = [some xyz kb that we want to set aside for
hypervisor]
$free_memory = $total_memory.to_i - ( $mem_allocated_for_running_vms.to_i
+
$mem_used_by_base_hypervisor.to_i )
==
Ranga
On Wed, Nov 3, 2010 at 2:16 PM, Javier Fontan jfon...@gmail.com wrote:
Hello,
Sorry for the delay in the response.
It looks that the problem is OpenNebula calculating available memory.
For xen = 3.2 there is a reliable way to get available memory that is
calling xm info and getting max_free_memory attribute.
Unfortunately for kvm or xen 3.2 there is not such attribute. I
suppose you are using kvm as you tell about free command.
I began analyzing the kvm IM probe that gets memory information and
there is a problem on the way to get total memory. Here is how it now
gets memory information:
TOTALMEMORY: runs virsh info that gets the real physical memory
installed in the machine
FREEMEMORY: runs free command and gets the free column data without
buffers and cache
USEDMEMORY: runs top command and gets used memory from it (this counts
buffers and cache)
This is a big problem as those values do not match one with another (I
don't really know how I failed to see this before). Here is the
monitoring data from a host without VMs.
--8--
TOTALMEMORY=8193988
USEDMEMORY=7819952
FREEMEMORY=7911924
--8--
As you can see it makes no sense at all. Even the TOTALMEMORY that is
got from virsh info is very misleading for oned as the host linux
instance does not have access to all that memory (some is consumed by
the hypervisor itself) as seen calling a free command:
--8--
total used free sharedbuffers cached
Mem: 81939887819192 374796 0 64176
7473992
--8--
I am also copying this text as an issue
Re: [one-users] Making scheduler allocation aware
Hi Rubens.
I'm sure the RANK=-RUNNING_VMS will not apply in such a scenario,
because the scheduler does not update the RUNNING_VMS after the
creation of the VM but just after monitoring the host!
So between this events the RUNNING_VMS value stays unchanged and by my
experience this Host will become the 'chosen one' for new deployed VMs
up to the next host monitoring.
And i'm not really sure if the scheduler sums USED MEMORY (ALLOCATED)
and the memory used by the VM to prevent overcommiting, we could look
in the source code for this.
I must say never have experienced a host who became more VMs as possible.
Best regards
Marlon
Zitat von Ruben S. Montero rube...@dacya.ucm.es:
Hi,
We use the total memory to allocate VM's, this is not going to change
between monitoring events. Right now, we are able to schedule multiple
VMs in the same scheduling step, to the same host without
overcommitting memory.
Cheers
On Thu, Nov 11, 2010 at 10:42 AM, Shashank Rachamalla
shashank.rachama...@hexagrid.com wrote:
Hi
Thanks for the reply. I agree that a VM will not be allowed to use more than
what has been specified in its template during creation but I was referring
to a scenario where memory available on the host is over committed. I guess
the problem here is with allowing multiple VMs to be dispatched on to a
single host in one schedule cycle.
On 11 November 2010 14:47, Ruben S. Montero rube...@dacya.ucm.es wrote:
Hi,
Regarding capacity (CPU, Memory), it is updated every time a VM is
submitted, so no overcommitment is possible (beyond that specified by
the CPU attribute in the VM template). This also works in 1.4
Cheers
Ruben
On Thu, Nov 11, 2010 at 10:08 AM, openneb...@nerling.ch wrote:
Hallo Shashank.
I'm having the same problem in 1.4.
You must workaround it by youself, so instead of using onevm directly,
use
it with a wrapper script who looks and waits for deploy if a VM is
pending.
I hope this behaviour is fixed on 2.0 (Hallo developers??)
Best regards
Marlon
Zitat von Shashank Rachamalla shashank.rachama...@hexagrid.com:
Hi Javier
Thanks for the inputs but I came across another problem while testing:
If opennebula receives multiple vm requests in a short span of time,
the
scheduler might take decisions for all these vms considering the host
monitoring information available from the last monitoring cycle.
Ideally,
before processing every pending request, fresh host monitoring
information
has to be taken into account as the previous set of requests might have
already changed the host’s state. This can result in over committing
when
host is being used close to its full capacity.
*Is there any workaround which helps the scheduler to overcome the
above
problem ?*
steps to reproduce the problem scenario:
Host 1 : Total memory = 3GB
Host 2 : Total memory = 2GB
Assume Host1 and Host2 have same number of CPU cores. ( Host1 will have
a
higher RANK value )
VM1: memory = 2GB
VM2: memroy = 2GB
Start VM1 and VM2 immediately one after the other. Both VM1 and VM2
will
come up on Host1. ( Thus over committing )
Start VM1 and VM2 with an intermediate delay of 60sec. VM1 will come up
on
Host1 and VM2 will come up on Host2. This is true because opennebula
would
have fetched a fresh set of host monitoring information in that time.
On 4 November 2010 02:04, Javier Fontan jfon...@gmail.com wrote:
Hello,
It looks fine to me. I think that taking out the memory the hypervisor
may be consuming is key to make it work.
Bye
On Wed, Nov 3, 2010 at 8:32 PM, Rangababu Chakravarthula
rb...@hexagrid.com wrote:
Javier
Yes we are using KVM and OpenNebula 1.4.
We have been having this problem since a long time and we were doing
all
kinds of validations ourselves before submitting the request to
OpenNebula.
(there should be enough memory in the cloud that matches the
requested
memory there should be atleast one host that has memory
requested
memory
) We had to do those because OpenNebula would schedule to an
arbitrary
host based on the existing logic it had.
So at last we thought that we need to make OpenNebula aware of
memory
allocated of running VM's on the host and started this discussion.
Thanks for taking up this issue as priority. Appreciate it.
Shashank came up with this patch to kvm.rb. Please take a look and
let
us
know if that will work until we get a permanent solution.
$mem_allocated_for_running_vms=0
for i in `virsh list|grep running|tr -s ' ' ' '|cut -f2 -d' '` do
$dominfo=`virsh dominfo #{i}`
$dominfo.split(/\n/).each{|line|
if line.match('^Max memory')
$mem_allocated_for_running_vms += line.split(
)[2].strip.to_i
end
}
end
$mem_used_by_base_hypervisor = [some xyz kb that we want to set
aside
for
hypervisor
Re: [one-users] VMs stuck in PEND state
Hallo Fernando. Could you please post the output of: #onehost list #onevm show 0 #onehost show 0 It seems that none of your Hosts are enabled! Tue Nov 9 20:31:18 2010 [HOST][D]: Discovered Hosts (enabled): best regards Marlon Nerling Zitat von Fernando Morgenstern ferna...@consultorpc.com: Hello, This is the first time that i'm using open nebula, so i tried to do it with express script which ran fine. I'm using CentOS 5.5 with Xen. The first thing that i'm trying to do is getting the following vm running: NAME = ttylinux CPU= 0.1 MEMORY = 64 DISK = [ source = /var/lib/one/images/ttylinux.img, target = hda, readonly = no ] NIC= [ NETWORK = Small network ] FEATURES=[ acpi=no ] So i used: onevm create ttylinux.one The issue is that it keeps stuck in PEND state: onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 3 oneadmin ttylinux pend 0 0K 00 00:20:03 At oned log the following messages keeps repeating: Tue Nov 9 20:29:48 2010 [ReM][D]: VirtualMachinePoolInfo method invoked Tue Nov 9 20:29:59 2010 [ReM][D]: VirtualMachinePoolInfo method invoked Tue Nov 9 20:30:18 2010 [ReM][D]: HostPoolInfo method invoked Tue Nov 9 20:30:18 2010 [ReM][D]: VirtualMachinePoolInfo method invoked And at sched.log, i see this: Tue Nov 9 20:31:18 2010 [HOST][D]: Discovered Hosts (enabled): Tue Nov 9 20:31:18 2010 [VM][D]: Pending virtual machines : 3 Tue Nov 9 20:31:18 2010 [RANK][W]: No rank defined for VM Tue Nov 9 20:31:18 2010 [SCHED][I]: Select hosts PRI HID --- Virtual Machine: 3 Any ideas of what might be happening? I saw other threads here at the list with similar problems, but their solution didn't applied to my case. Best Regards, Fernando. ___ 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] VMs stuck in PEND state
Hallo Fernando. try to log in the host and look if there is a folder names /tmp/one. If not it could be related to the bug: http://dev.opennebula.org/issues/385 please post the output from: #onehost show 1 #onehost show -x 1 I thought before your host has an id of 0. Marlon Nerling Quoting Fernando Morgenstern ferna...@consultorpc.com: Hello, Thanks for the answer. You are right, the host is showing an error state and i didn't verified it. How can i know what is causing the error in host? $ onehost list ID NAME CLUSTER RVM TCPU FCPU ACPUTMEMFMEM STAT 1 node01default0 0 0100 0K 0K err $ onevm show 0 VIRTUAL MACHINE 0 INFORMATION ID : 0 NAME : ttylinux STATE : DONE LCM_STATE : LCM_INIT START TIME : 11/09 19:06:37 END TIME : 11/09 19:11:09 DEPLOY ID: : - VIRTUAL MACHINE MONITORING NET_RX : 0 USED MEMORY: 0 USED CPU : 0 NET_TX : 0 VIRTUAL MACHINE TEMPLATE CPU=0.1 DISK=[ DISK_ID=0, READONLY=no, SOURCE=/home/oneadmin/ttylinux.img, TARGET=hda ] FEATURES=[ ACPI=no ] MEMORY=64 NAME=ttylinux NIC=[ BRIDGE=br0, IP=*, MAC=02:00:5d:9f:d0:68, NETWORK=Small network, NETWORK_ID=0 ] VMID=0 $ onehost show 0 Error: [HostInfo] Error getting HOST [0]. Thanks! Em 10/11/2010, às 06:45, openneb...@nerling.ch escreveu: Hallo Fernando. Could you please post the output of: #onehost list #onevm show 0 #onehost show 0 It seems that none of your Hosts are enabled! Tue Nov 9 20:31:18 2010 [HOST][D]: Discovered Hosts (enabled): best regards Marlon Nerling Zitat von Fernando Morgenstern ferna...@consultorpc.com: Hello, This is the first time that i'm using open nebula, so i tried to do it with express script which ran fine. I'm using CentOS 5.5 with Xen. The first thing that i'm trying to do is getting the following vm running: NAME = ttylinux CPU= 0.1 MEMORY = 64 DISK = [ source = /var/lib/one/images/ttylinux.img, target = hda, readonly = no ] NIC= [ NETWORK = Small network ] FEATURES=[ acpi=no ] So i used: onevm create ttylinux.one The issue is that it keeps stuck in PEND state: onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 3 oneadmin ttylinux pend 0 0K 00 00:20:03 At oned log the following messages keeps repeating: Tue Nov 9 20:29:48 2010 [ReM][D]: VirtualMachinePoolInfo method invoked Tue Nov 9 20:29:59 2010 [ReM][D]: VirtualMachinePoolInfo method invoked Tue Nov 9 20:30:18 2010 [ReM][D]: HostPoolInfo method invoked Tue Nov 9 20:30:18 2010 [ReM][D]: VirtualMachinePoolInfo method invoked And at sched.log, i see this: Tue Nov 9 20:31:18 2010 [HOST][D]: Discovered Hosts (enabled): Tue Nov 9 20:31:18 2010 [VM][D]: Pending virtual machines : 3 Tue Nov 9 20:31:18 2010 [RANK][W]: No rank defined for VM Tue Nov 9 20:31:18 2010 [SCHED][I]: Select hosts PRI HID --- Virtual Machine: 3 Any ideas of what might be happening? I saw other threads here at the list with similar problems, but their solution didn't applied to my case. Best Regards, Fernando. ___ 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 ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] VMs stuck in PEND state
Yes, it is related to the bug http://dev.opennebula.org/issues/385. I attached a patch for /usr/lib/one/mads/one_im_ssh.rb. ## Save it on the /tmp #cd /usr/lib/one/mads/ #patch -p0 /tmp/one_im_ssh.rb.patch Quoting Fernando Morgenstern ferna...@consultorpc.com: Hi, The tmp folder in my host is empty. Here is the output of the commands: $ onehost show 1 HOST 1 INFORMATION ID: 1 NAME : node01 CLUSTER : default STATE : ERROR IM_MAD: im_xen VM_MAD: vmm_xen TM_MAD: tm_nfs HOST SHARES MAX MEM : 0 USED MEM (REAL) : 0 USED MEM (ALLOCATED) : 0 MAX CPU : 0 USED CPU (REAL) : 0 USED CPU (ALLOCATED) : 0 RUNNING VMS : 0 MONITORING INFORMATION $ onehost show -x 1 HOST ID1/ID NAMEnode01/NAME STATE3/STATE IM_MADim_xen/IM_MAD VM_MADvmm_xen/VM_MAD TM_MADtm_nfs/TM_MAD LAST_MON_TIME1289394482/LAST_MON_TIME CLUSTERdefault/CLUSTER HOST_SHARE HID1/HID DISK_USAGE0/DISK_USAGE MEM_USAGE0/MEM_USAGE CPU_USAGE0/CPU_USAGE MAX_DISK0/MAX_DISK MAX_MEM0/MAX_MEM MAX_CPU0/MAX_CPU FREE_DISK0/FREE_DISK FREE_MEM0/FREE_MEM FREE_CPU0/FREE_CPU USED_DISK0/USED_DISK USED_MEM0/USED_MEM USED_CPU0/USED_CPU RUNNING_VMS0/RUNNING_VMS /HOST_SHARE TEMPLATE/ /HOST Thanks again for your answers. Em 10/11/2010, às 11:22, openneb...@nerling.ch escreveu: Hallo Fernando. try to log in the host and look if there is a folder names /tmp/one. If not it could be related to the bug: http://dev.opennebula.org/issues/385 please post the output from: #onehost show 1 #onehost show -x 1 I thought before your host has an id of 0. Marlon Nerling Quoting Fernando Morgenstern ferna...@consultorpc.com: Hello, Thanks for the answer. You are right, the host is showing an error state and i didn't verified it. How can i know what is causing the error in host? $ onehost list ID NAME CLUSTER RVM TCPU FCPU ACPUTMEM FMEM STAT 1 node01default0 0 0100 0K 0K err $ onevm show 0 VIRTUAL MACHINE 0 INFORMATION ID : 0 NAME : ttylinux STATE : DONE LCM_STATE : LCM_INIT START TIME : 11/09 19:06:37 END TIME : 11/09 19:11:09 DEPLOY ID: : - VIRTUAL MACHINE MONITORING NET_RX : 0 USED MEMORY: 0 USED CPU : 0 NET_TX : 0 VIRTUAL MACHINE TEMPLATE CPU=0.1 DISK=[ DISK_ID=0, READONLY=no, SOURCE=/home/oneadmin/ttylinux.img, TARGET=hda ] FEATURES=[ ACPI=no ] MEMORY=64 NAME=ttylinux NIC=[ BRIDGE=br0, IP=*, MAC=02:00:5d:9f:d0:68, NETWORK=Small network, NETWORK_ID=0 ] VMID=0 $ onehost show 0 Error: [HostInfo] Error getting HOST [0]. Thanks! Em 10/11/2010, às 06:45, openneb...@nerling.ch escreveu: Hallo Fernando. Could you please post the output of: #onehost list #onevm show 0 #onehost show 0 It seems that none of your Hosts are enabled! Tue Nov 9 20:31:18 2010 [HOST][D]: Discovered Hosts (enabled): best regards Marlon Nerling Zitat von Fernando Morgenstern ferna...@consultorpc.com: Hello, This is the first time that i'm using open nebula, so i tried to do it with express script which ran fine. I'm using CentOS 5.5 with Xen. The first thing that i'm trying to do is getting the following vm running: NAME = ttylinux CPU= 0.1 MEMORY = 64 DISK = [ source = /var/lib/one/images/ttylinux.img, target = hda, readonly = no ] NIC= [ NETWORK = Small network ] FEATURES=[ acpi=no ] So i used: onevm create ttylinux.one The issue is that it keeps stuck in PEND state: onevm list ID USER NAME STAT CPU MEMHOSTNAMETIME 3 oneadmin ttylinux pend 0 0K 00 00:20:03 At oned log the following messages keeps repeating: Tue Nov 9 20:29:48 2010 [ReM][D]: VirtualMachinePoolInfo method invoked Tue Nov 9 20:29:59 2010 [ReM][D]: VirtualMachinePoolInfo method invoked Tue Nov 9 20:30:18 2010 [ReM][D]: HostPoolInfo method invoked Tue Nov 9 20:30:18 2010 [ReM][D]: VirtualMachinePoolInfo method invoked And at sched.log, i see this: Tue Nov 9 20:31:18 2010 [HOST][D]: Discovered Hosts (enabled): Tue Nov 9 20:31:18 2010 [VM][D]: Pending virtual machines : 3 Tue Nov 9 20:31:18 2010 [RANK][W]: No rank defined for VM Tue Nov 9 20:31:18 2010 [SCHED][I]: Select hosts PRI HID --- Virtual Machine: 3 Any ideas of what might be happening? I saw other threads here at the list with similar problems, but their solution didn't applied to my case. Best Regards, Fernando. ___ 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] opennebula 2.0.1 under Debian Lenny (5.0.6)
The opennebula 2.0 debian package for Lenny (5.0.6) has a dependency on libmysqlclient16, althought the default Lenny repository only has libmysqlclient15. I'm posting here, knowing there are another thread for the same issue, since the second November : OpenNebula Express 2.0 on Debian_5.0.6 problem By my meaning should opennebula not never depend on a backport package. Would it be a problem to change the dependency in the package and use libmysqlclient15 instead of libmysqlclient16? Has it been tested? Best Regards Marlon Nerling ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Migration Path from 1.4 to 2.0
I prepared some bash scripts for the migration. They are attached here. I will be glad if someone could take a look on it, specially one.migration.vm.sh, wish I think is to much customized for our need. As you can see I try to parse vm_attributes under the xml format of vm_pool.template, there may you find some issues. The attached files are contain only the functions for the migration, they are released under the GNU Public licese. I'm working on a call script and will post it asap. Marlon Nerling Zitat von openneb...@nerling.ch: Good day. I'm starting to implement a Migration path from my one1.4 installations to one2.0.1. I will be sure I'm not recreating the whell, so If you know from ready scripst or howtos for this, let me know. All help will be aprecciated, too. best Regards Marlon Nerling ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org one.migration.common.sh Description: Bourne shell script one.migration.hosts.sh Description: Bourne shell script one.migration.unchanged.sh Description: Bourne shell script one.migration.vm.sh Description: Bourne shell script one.migration.vnet.sh Description: Bourne shell script ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Migration Path from 1.4 to 2.0
Ola Javier. You are welcome. I will post the files and my experience here for the moment. I can not user git throught the proxy of my workplace, so I can not to git it. Wenn I'm ready with this, I will post to dev.opennebula.org as a requirement, as I have done for Request #181: Migration Path from 1.2 to 1.4 http://dev.opennebula.org/issues/181 best regards Marlon Zitat von Javier Fontan jfon...@gmail.com: Hello, That looks great! Maybe you want to contribute them to http://opennebula.org/community:ecosystem. If you don't have where to host the files maybe you can create a project in github.com so more people can collaborate with you with patches and bug fixes. That's really neat you are doing this, I think that one of the main problems to change to the new release is migrating the database as people already has VM's running in the old version. Thank you! On Fri, Nov 5, 2010 at 9:53 AM, openneb...@nerling.ch wrote: I prepared some bash scripts for the migration. They are attached here. I will be glad if someone could take a look on it, specially one.migration.vm.sh, wish I think is to much customized for our need. As you can see I try to parse vm_attributes under the xml format of vm_pool.template, there may you find some issues. The attached files are contain only the functions for the migration, they are released under the GNU Public licese. I'm working on a call script and will post it asap. Marlon Nerling Zitat von openneb...@nerling.ch: Good day. I'm starting to implement a Migration path from my one1.4 installations to one2.0.1. I will be sure I'm not recreating the whell, so If you know from ready scripst or howtos for this, let me know. All help will be aprecciated, too. best Regards Marlon Nerling ___ 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 -- Javier Fontan, Grid Virtualization Technology Engineer/Researcher DSA Research Group: http://dsa-research.org Globus GridWay Metascheduler: http://www.GridWay.org OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Migration Path from 1.4 to 2.0
Good day. I'm starting to implement a Migration path from my one1.4 installations to one2.0.1. I will be sure I'm not recreating the whell, so If you know from ready scripst or howtos for this, let me know. All help will be aprecciated, too. best Regards Marlon Nerling ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
