<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Borja Sotomayor wrote:
<blockquote
cite="mid:71ca94060911250903m59b92c2fs546d79c109d4e30f@mail.gmail.com"
type="cite">
<pre wrap="">Hi,
</pre>
<blockquote type="cite">
<pre wrap="">PROBLEM 1
--------------
When we deploy a VM with "onevm submit <path to the template>" and then
during its work shut it down or delete it, Haizea is not aware of this
change. The lease for that machine remains active and may prevent other VM
deployments.
</pre>
</blockquote>
<pre wrap=""><!---->
My reply to your previous message on the Haizea mailing list should
address this problem. For those on the OpenNebula list, this is the
message I'm referring to:
<a class="moz-txt-link-freetext" href="https://mailman.cs.uchicago.edu/pipermail/haizea/2009-November/000084.html">https://mailman.cs.uchicago.edu/pipermail/haizea/2009-November/000084.html</a>
</pre>
<blockquote type="cite">
<pre wrap="">PROBLEM 2
--------------
When we deploy a machine as described above, and then do "stop" on it, via
XML-RPC (we have our own web GUI application), it gets saved. When we try to
resume that machine, it stays stuck in state "pending" and there is no
action that can revive it.
</pre>
</blockquote>
<pre wrap=""><!---->
How exactly are you trying to resume it? If you're using "onevm
resume" and the machine still stays in a "pending" state, that sounds
like an OpenNebula-only problem. For the OpenNebula developers to help
out, I suggest you send this as a separate message and include the
sequence of commands you used and the VM log (in
$ONE_LOCATION/var/$VM_ID/vm.log)
</pre>
</blockquote>
<br>
This is what I have in the log of the said machine (showing only the
end of it):<br>
<br>
Wed Nov 25 15:56:30 2009 [VMM][D]: Monitor Information:<br>
CPU : 0<br>
Memory: 20<br>
Net_TX: -1<br>
Net_RX: -1<br>
Wed Nov 25 15:56:47 2009 [LCM][I]: New VM state is SAVE_STOP<br>
Wed Nov 25 15:57:39 2009 [LCM][I]: New VM state is EPILOG_STOP<br>
Wed Nov 25 15:57:40 2009 [DiM][I]: New VM state is STOPPED<br>
Wed Nov 25 16:00:15 2009 [DiM][I]: New VM state is PENDING.<br>
<br>
This is what I am seeing on the "onevm list", the machine stays in the
pending state, waiting for something to happen. I suspect that *that*
something is a "go" from the scheduler. And since this is a VM from an
already approved lease, Haizea has no reason to even pay attention to
it.<br>
<br>
<blockquote
cite="mid:71ca94060911250903m59b92c2fs546d79c109d4e30f@mail.gmail.com"
type="cite">
<blockquote type="cite">
<pre wrap="">But
take a look at Amazon, they will allow you to deploy a machine, run it at
certain times, turn it off, turn it on again and so forth. How does that fit
into Haizea's view of the world?
</pre>
</blockquote>
<pre wrap=""><!---->
In Haizea's view of the world, these would simply be separate leases,
not a single lease that gets turned on and off. Reusing an existing
image (instead of starting from a fresh one every time) should be
possible, as long the OpenNebula template in subsequent submits refers
to the saved copy of the image (although I've never tried this with
OpenNebula+Haizea).</pre>
</blockquote>
<br>
Well, this sounds promising. Not to mention interesting. :-)<br>
<br>
<blockquote
cite="mid:71ca94060911250903m59b92c2fs546d79c109d4e30f@mail.gmail.com"
type="cite">
<pre wrap="">This is not to say that it wouldn't be more
natural to have a model where a lease can be "restarted" in the
future, without having to specify that a saved disk image must be used
(instead, this would be implicit in the "restart" operation). However,
doing this is not currently on our roadmap.
</pre>
</blockquote>
<br>
Thanks for the info on that, too.<br>
<br>
Nix.<br>
<div class="moz-signature">-- <br>
<title>Levi9 Signature</title>
<meta http-equiv="Content-Type" content="text/html; ">
<style type="text/css">
.signs1{ font-size: 11pt; font-family: Wingdings }
.signs2{ font-size: 11pt; font-family: Webdings }
</style>
<div
style="font-family: Tahoma,sans-serif; font-size: 8pt; color: black;">
<span style="font-size: 10pt;"> Met vriendelijke groet / Kind regards,<br>
Nikola Milutinovic<br>
Sr Java Developer<br>
Levi9 Global Sourcing<br>
</span>
<hr> <font face="Wingdings" size="3">.</font> <span> Jan van
Goyenkade 8, 1075 HP Amsterdam, The Netherlands</span> <br>
<font face="Wingdings" size="3">(</font> <span> +31 (0) 20 7547900
ext 2056</span> <br>
<font face="Wingdings" size="3">(</font> <span> +381 (0) 21 4895800
ext 2056</span> <br>
<font face="Webdings" size="3">È</font> <span> +381 (0) 64 2202824</span>
<br>
<font face="Wingdings" size="3">*</font> <span> <a
href="mailto:n.milutinovic@Levi9.com">n.milutinovic@Levi9.com</a></span>
<br>
<font face="Webdings" size="3">^</font> <span> Skype:
nikola.milutinovic</span> <br>
<font face="Webdings" size="3">ü</font> <span> <a target="_blank"
title="http://www.levi9.com/" href="http://www.levi9.com/">www.levi9.com</a></span>
<br>
<span> <br>
Chamber of commerce Levi9 Global Sourcing BV: 34221951<br>
Chamber of commerce Levi9 Global Sourcing Benelux BV: 34224746<br>
</span>
<hr> <span> This e-mail may contain confidential or privileged
information. If you are not (one of) the intended recipient(s), please
notify the sender immediately by reply e-mail and delete this message
and any attachments permanently without retaining a copy. Any review,
disclosure, copying, distribution or taking any action in reliance on
the contents of this e-mail by persons or entities other than the
intended recipient(s) is strictly prohibited and may be unlawful. <br>
<br>
The services of Levi9 are exclusively subject to its general terms and
conditions. These general terms and conditions can be found on <a
target="_blank" title="http://www.levi9.com/"
href="http://www.levi9.com/">www.levi9.com</a> and a copy will be
promptly submitted to you on your request and free of charge.<br>
</span> </div>
</div>
</body>
</html>