[Haizea] Conceptual question

[Nikola Milutinovic]

Borja Sotomayor wrote:
> Hi Nikola,
>   
>  I would prefer extending the
> Haizea CLI and API to accomodate the tasks that a system administrator
> is interested in doing. It sounds like haizea-cancel-lease already
> fulfills the need to stop VMs (without having to stop them directly
> with OpenNebula). What other functionality do you feel is important?
>   

Well, one of the things that we would like to have is the ability to 
start a VM at the given time and allow the "owner" to stop its execution 
at any given time, then continue it again, at any given time. We have a 
Web GUI for that and we can start/continue a VM using OpenNebula with 
its basic scheduler. Haizea doesn't have this concept, I think. It seams 
that when you get a lease, you're expected to run it in full. What we 
would like to have is something more like Amazon, allocate a VM from an 
image, let the owner control it, stop it, resume it. At some point we 
will have statistics of how long it has been running, for later accounting.

I'm not sure what it could look like, when using Haizea. You would get a 
lease and then if you have, say, "haizea-suspend-lease", that could mark 
the resources as freed and allow for another VM lease to kick in, be it 
scheduled or requested immediately. Should the first owner decide to 
resume his/her VM, command could be something like 
"haizea-reinstate-lease" and the lease would be moved to status "Ready" 
or "Active".

"haizea-cancel-lease" will delete the VM, which is not what we want in 
all cases.

So we would like to have these lifecycle steps available:

1. CREATE (create from template)
2. SUSPEND (stop the VM, release the resources, but keep the saved 
image, so it can be continued at later time)
3. REINSTATE (resume operation of a saved VM)
4. DELETE (delete the VM, as if "onevm delete <ID>" was issued)

>> With ONE default scheduler, we successfully employed ONE XML-RPC. With
>> Haizea, what should we use? System.exec("haizea-cancel-lease")?
>>     
>
> Actually, Haizea has an XML-RPC API too, but it hasn't been documented
> yet. The best I can point you to right now is the source code of the
> CLI commands that use the XML-RPC API (haizea-cancel-lease is one of
> these):
>
> https://phoenixforge.cs.uchicago.edu/repositories/entry/haizea/trunk/src/haizea/cli/rpc_commands.py
>   

This is nice to know, so we can build an XML-RPC client from our web 
application (Java).

Nix.
-- 
Met vriendelijke groet / Kind regards,
Nikola Milutinovic
Sr Java Developer
Levi9 Global Sourcing
------------------------------------------------------------------------
.  Jan van Goyenkade 8, 1075 HP Amsterdam, The Netherlands
(    +31 (0) 20 7547900 ext 2056
(    +381 (0) 21 4895800 ext 2056
È    +381 (0) 64 2202824
*    n.milutinovic at Levi9.com <mailto:n.milutinovic at Levi9.com>
^    Skype: nikola.milutinovic
ü    www.levi9.com <http://www.levi9.com/>

Chamber of commerce Levi9 Global Sourcing BV: 34221951
Chamber of commerce Levi9 Global Sourcing Benelux BV: 34224746
------------------------------------------------------------------------
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.

The services of Levi9 are exclusively subject to its general terms and 
conditions. These general terms and conditions can be found on 
www.levi9.com <http://www.levi9.com/> and a copy will be promptly 
submitted to you on your request and free of charge.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.cs.uchicago.edu/pipermail/haizea/attachments/20091126/5b068725/attachment.htm