Sadly for API Cloning, I found this in
/usr/lib64/xen-3.2-1/lib/python/xen/xend/XendAPI.py
def VM_clone(self, session, vm_ref):
return xen_api_error(XEND_ERROR_UNSUPPORTED)
So, It seems impossible to use cloning via API. But I'll work on a
interface which allows creation of templates. I just need time to do
that, but so far, I'm on full time in this project !
Regards,
Olivier.
On Tue, Sep 22, 2009 at 12:19 PM, Olivier LAMBERT
<lambert.olivier@xxxxxxxxx> wrote:
> Hello Steve,
>
> I'll trying (just in the next hours) to use "VM.clone" method existing
> in API. If it works well, so it will be easy to integrate this
> feature.
>
> If it's not as expected, I'll introduce vm creation interface from the
> GUI, by calling xen tools (but it need a "n tier" infrastructure, like
> I discuss in this article : http://xen-orchestra.com/?p=53 )
> But this step will be more complicated (slowest to implement).
>
>
> Thank you for your interest :)
>
> Olivier.
>
> On Tue, Sep 22, 2009 at 10:50 AM, Stephen Ross
> <stephen.ross1986@xxxxxxxxxxxxxx> wrote:
>> This project is just the kind of thing I'm looking for! Being web UI based
>> is a massive bonus for my organisation, as it's non-operating system
>> specific. I'll be sure to try this out asap.
>>
>> It would be really handy for me if I can create machines from a clone or
>> template though, having that functionality would make the app ready for use
>> in my eyes!
>>
>> Cheers,
>>
>> Steve
>>
>> On Mon, Sep 21, 2009 at 9:15 PM, Olivier LAMBERT <lambert.olivier@xxxxxxxxx>
>> wrote:
>>>
>>> Mainly with Xen, questions are :
>>> “Where are my DomU’s at this time ? Are they running ?”.
>>>
>>> That’s why I started this project : although my DomU’s are on
>>> different Dom0, I want to see them all quickly, in one page.
>>>
>>> And I would like to stop/pause/restart them in one click. Live
>>> migration is really a great feature for Xen : so, it could be easily
>>> accesible (two clicks ;) )
>>>
>>> Furthermore, check informations about a DomU (like CPU parameters
>>> etc.) is crucial. But this is not a final objective.
>>>
>>> First, you can follow the main site of the project :
>>> http://xen-orchestra.com
>>>
>>> And report bug or features request on the forge (Git repo on Indefero
>>> forge) :
>>> http://project.xen-orchestra.com
>>>
>>> Future of Xen Orchestra, example of next features :
>>>
>>> * allow set of all DomU parameters (CPU, RAM etc.). Set all this stuff in
>>> live ;
>>> * restrict access with “DomU per users” : user “foobar” can access and
>>> modifiy it’s own domU, or more. Can be really usefull in a classroom
>>> for testing prupose, or for developer ;
>>> * possibility of cloning domU and create them (with creating roles, a
>>> kind of interface of xen-create-image).
>>>
>>>
>>> Please be nice, this project is really really young, the code need to
>>> be cleaned and reorganized. But it works, so if you want do some
>>> tests, go !
>>>
>>> Here is some screenshots of the first release :
>>> http://xen-orchestra.com/?p=17
>>>
>>> Now, you have CPU counters, but I made screenshots later, you can see
>>> them on the main blog/site.
>>>
>>> And yes, it's open source ;) (maybe, in a near future, it will be
>>> packaged and include in Debian)
>>>
>>>
>>> Regards,
>>>
>>>
>>> Olivier.
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users
>>
>>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home