[Haizea] Haizea with Nebula1.4 | Unable to schedule second VM

prashanth.srinivas at wipro.com prashanth.srinivas at wipro.com
Thu Oct 1 08:14:21 CDT 2009


Hi,
 
I am using Nebula 1.4 with haizea-0.9.2. When I submit first VM, Haizea is scheduling and able to create desired VM.
At this point if I submit one more VM, though Haizea is identifying the new request for VM, it is not able to schedule the same.
The second VM request will always remain in pending state. But if restart haizea then the second VM will be created. 
Can someone help me fixing this issue.
 
VM list :
--------------------------------------------------------------------------
 ID     USER     NAME STAT CPU     MEM        HOSTNAME        TIME
  9     test    vm-34 boot     0       0           10.101.102.34 00  00:09:19
 10    test    vm2-34 pend   0       0                                     00 00:01:40
---------------------------------------------------------------------------
 
Haizea log: First start
--------------------------------------------------------------------------
root at wipro-desktop:/opt/template/haizeaTest# haizea --fg -c /usr/share/haizea/etc/sample_opennebula.conf
[                      ] ENACT.ONE.INFO Fetched 1 nodes from OpenNebula length is
[2009-09-28 17:58:19.09] RM      Starting resource manager
[2009-09-28 17:58:19.09] RPCSERVER RPC server started on port 42493
[2009-09-28 17:58:19.10] RM      Recovered lease 1
[2009-09-28 17:58:19.10] RM      Could not recover lease 3 (scheduled starting time has passed)
[2009-09-28 17:58:19.11] RM      Could not recover lease 5 (scheduled starting time has passed)
[2009-09-28 17:58:19.11] RM      Recovered lease 2 (queued)
[2009-09-28 17:58:19.11] RM      Recovered lease 4 (already done)
[2009-09-28 17:58:19.11] RM      Could not recover lease 6 (scheduled starting time has passed)
[2009-09-28 17:58:19.11] CLOCK   Starting clock
[2009-09-28 17:58:19.11] CLOCK   Waking up to manage resources
[2009-09-28 17:58:19.11] CLOCK   Wake-up time recorded as 2009-09-28 17:58:19.00
[2009-09-28 17:58:19.14] LSCHED  Lease #1 has been requested.
[2009-09-28 17:58:19.14] LSCHED  Lease #1 has been marked as pending.
[2009-09-28 17:58:19.16] LSCHED  Queued best-effort lease request #1, 1 nodes for 36500:00:00:00.00.
[2009-09-28 17:58:19.17] LSCHED  Next request in the queue is lease 1. Attempting to schedule...
[2009-09-28 17:58:19.17] VMSCHED Lease #1 has been scheduled on nodes [1] from 2009-09-28 17:58:29.00 to 2109-09-04 17:58:29.00
[2009-09-28 17:58:19.19] CLOCK   Going back to sleep. Waking up at 2009-09-28 17:58:29.00 to handle slot table event.
[2009-09-28 17:58:28.99] CLOCK   Waking up to manage resources
[2009-09-28 17:58:29.00] CLOCK   Wake-up time recorded as 2009-09-28 17:58:29.00
[2009-09-28 17:58:29.04] VMSCHED Started VMs for lease 1 on nodes [1]
[2009-09-28 17:58:29.76] CLOCK   Going back to sleep. Waking up at 2009-09-28 17:59:29.00 to see if something interesting has happened by then.
[2009-09-28 17:59:29.00] CLOCK   Waking up to manage resources
[2009-09-28 17:59:29.00] CLOCK   Wake-up time recorded as 2009-09-28 17:59:29.00
[2009-09-28 17:59:29.02] CLOCK   Going back to sleep. Waking up at 2009-09-28 18:00:29.00 to see if something interesting has happened by then.
[2009-09-28 18:13:29.00] CLOCK   Wake-up time recorded as 2009-09-28 18:13:29.00
[2009-09-28 18:13:29.01] LSCHED  Lease #2 has been requested.
[2009-09-28 18:13:29.01] LSCHED  Lease #2 has been marked as pending.
[2009-09-28 18:13:29.02] LSCHED  Queued best-effort lease request #2, 1 nodes for 36500:00:00:00.00.
[2009-09-28 18:13:29.02] CLOCK   Going back to sleep. Waking up at 2009-09-28 18:14:29.00 to see if something interesting has happened by then.
[2009-09-28 18:14:28.99] CLOCK   Waking up to manage resources
[2009-09-28 18:14:28.99] CLOCK   Wake-up time recorded as 2009-09-28 18:14:29.00
[2009-09-28 18:14:29.00] CLOCK   Going back to sleep. Waking up at 2009-09-28 18:15:29.00 to see if something interesting has happened by then.
[2009-09-28 18:15:29.00] CLOCK   Waking up to manage resources
[2009-09-28 18:15:29.00] CLOCK   Wake-up time recorded as 2009-09-28 18:15:29.00
[2009-09-28 18:15:29.01] CLOCK   Going back to sleep. Waking up at 2009-09-28 18:16:29.00 to see if something interesting has happened by then.
[2009-09-28 18:15:36.45] CLOCK   Received signal 2 (SIGINT)
[2009-09-28 18:15:36.45] CLOCK   Real clock has stopped
[2009-09-28 18:15:36.45] RM      Stopping resource manager gracefully...
[2009-09-28 18:15:36.49] RM      --- Haizea status summary ---
[2009-09-28 18:15:36.49] RM      Number of leases (not including completed): 2
[2009-09-28 18:15:36.49] RM      Completed leases: 4
[2009-09-28 18:15:36.49] RM      ---- End summary ----
---------------------------------------------------------------------------
 
 
Haizea log: Second start
--------------------------------------------------------------------------
root at wipro-desktop:/opt/template/haizeaTest# haizea --fg -c /usr/share/haizea/etc/sample_opennebula.conf
[                      ] ENACT.ONE.INFO Fetched 1 nodes from OpenNebula length is
[2009-09-28 18:15:40.75] RM      Starting resource manager
[2009-09-28 18:15:40.75] RPCSERVER RPC server started on port 42493
[2009-09-28 18:15:40.76] RM      Recovered lease 1
[2009-09-28 18:15:40.76] RM      Could not recover lease 3 (scheduled starting time has passed)
[2009-09-28 18:15:40.76] RM      Could not recover lease 5 (scheduled starting time has passed)
[2009-09-28 18:15:40.76] RM      Recovered lease 2 (queued)
[2009-09-28 18:15:40.76] RM      Recovered lease 4 (already done)
[2009-09-28 18:15:40.76] RM      Could not recover lease 6 (scheduled starting time has passed)
[2009-09-28 18:15:40.76] CLOCK   Starting clock
[2009-09-28 18:15:40.76] CLOCK   Waking up to manage resources
[2009-09-28 18:15:40.76] CLOCK   Wake-up time recorded as 2009-09-28 18:15:41.00
[2009-09-28 18:15:40.77] LSCHED  Lease #1 has been requested.
[2009-09-28 18:15:40.77] LSCHED  Lease #1 has been marked as pending.
[2009-09-28 18:15:40.78] LSCHED  Queued best-effort lease request #1, 1 nodes for 36500:00:00:00.00.
[2009-09-28 18:15:40.78] LSCHED  Next request in the queue is lease 2. Attempting to schedule...
[2009-09-28 18:15:40.79] VMSCHED Lease #2 has been scheduled on nodes [1] from 2009-09-28 18:15:51.00 to 2109-09-04 18:15:51.00
[2009-09-28 18:15:40.79] CLOCK   Going back to sleep. Waking up at 2009-09-28 18:15:51.00 to handle slot table event.
[2009-09-28 18:15:51.00] CLOCK   Waking up to manage resources
[2009-09-28 18:15:51.00] CLOCK   Wake-up time recorded as 2009-09-28 18:15:51.00
[2009-09-28 18:15:51.02] VMSCHED Started VMs for lease 2 on nodes [1]
[2009-09-28 18:15:51.10] LSCHED  Next request in the queue is lease 1. Attempting to schedule...
[2009-09-28 18:15:51.10] VMSCHED Lease #1 has been scheduled on nodes [1] from 2109-09-04 17:58:29.00 to 2209-08-11 17:58:29.00
[2009-09-28 18:15:51.11] CLOCK   Going back to sleep. Waking up at 2009-09-28 18:16:51.00 to see if something interesting has happened by then.
--------------------------------------------------------------------------------
 
 
Do let me know if this required further clarification
 
 
 
Thanks & regards,
Prashanth

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.cs.uchicago.edu/pipermail/haizea/attachments/20091001/51d8b78a/attachment-0001.htm 


More information about the Haizea mailing list