WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

Re: [Xen-API] Re: [Xen-devel] About OpenNebula and XCP integration Pt2

To: Jonathan Ludlam <Jonathan.Ludlam@xxxxxxxxxxxxx>
Subject: Re: [Xen-API] Re: [Xen-devel] About OpenNebula and XCP integration Pt2
From: Tino Vazquez <tinova@xxxxxxxxxxxxxx>
Date: Fri, 18 Feb 2011 19:34:37 +0100
Cc: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 18 Feb 2011 17:01:44 -0800
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=opennebula.org; h= mime-version:in-reply-to:references:from:date:message-id:subject :to:cc:content-type:content-transfer-encoding; s=opennebula.org; bh=X0GPjBIL4A/tGQrlp5Xn2vxL5mo=; b=LEtCQ6r8Ov0mCWKC6r5v8SGBvOHc HP484f3cwCi+qVdEUSr1YPtKhjmufFv56DZKp8AKNDsrDEAvIKzXKMGv3yjlr72B 0J9pDE2aZRCEVjZTsyWo1xTUhUyOYwf1i1Fo4nURrcHtGcEURY+fkc08q3lM6dgd KQAgBVgGGRnfcSA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=opennebula.org; h=mime-version :in-reply-to:references:from:date:message-id:subject:to:cc :content-type:content-transfer-encoding; q=dns; s=opennebula.org ; b=NCtE8/1O2WztdexnQSvJFKbPcCAYMTHZP3/ykq+gBzzP0SO+bTTyg5ipFksc bweaIGtU+nJLU7ArBvYU5PdPxTkkpo/fZ7fUFCNLLzTWXRxpmSgIkd/0QkskzFsa JYVnJNCGwnKUbIdV9nmm/6sHcLF2ikgwIR6765fRxCTkqUg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <33114BBB-376C-410C-AA84-752F6860551F@xxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimSabucVohMKQ+EbyzaOsU9UUc9XbR9VQO9ya9K@xxxxxxxxxxxxxx> <20110211113325.GG18135@xxxxxxxxxxxxxxxxxxxxxxx> <AANLkTinczv0OogD735ow0xQ2SjZybCskkGxBNQLNPQea@xxxxxxxxxxxxxx> <33114BBB-376C-410C-AA84-752F6860551F@xxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Hi Jon,

Well, that really helped to understand what is going on with the
storage resources. The tab completion of "xe" is just outstanding,
well done!

Many thanks for the help, I'll let you know if I bump into any other issue.

Have a good weekend,

-Tino

--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor  / Cloud Researcher
www.OpenNebula.org | @tinova79



On Thu, Feb 17, 2011 at 10:46 AM, Jonathan Ludlam
<Jonathan.Ludlam@xxxxxxxxxxxxx> wrote:
>
> On 11 Feb 2011, at 11:46, Tino Vazquez wrote:
>
>> Hi Tim,
>>
>> Many thanks for the hint, I've added myself to the xen-api list. I'll
>> repeat my questions here for clarity shake:
>>
>> * Is it possible to add users other than with Active Directory? How
>> can I achieve that using the API? Is it possible to do so xi "xe"?
>
> Not currently, but it should be possible to achieve - I think there's a google
> summer of code proposal to address this.
>
>> * Is it possible to create a VM from previously existing VDIs? What
>> parameters should I fill? In my tests, the created VM doesn't find the
>> hard disk, these are my steps:
>>
>>    * Create vm with xe vm-create
>>    * Attach a disk via XenCenter (how can I perform this operation with xe?)
>
> xe vbd-create vm-uuid=<foo> vdi-uuid=<bar> device=<device number>
>
>>    * Set a PV-kernel (do it need  to be in /boot/guest/?)
>
> Yes - you need to mkdir this. You can use pygrub to boot a kernel present on 
> the disk.
>
>>
>> * Do I need to create VMs off templates?
>
> No
>
>> * Can I attach a CDROM device using xe?
>>
>
> xe vbd-create type=CD vdi-uuid=... vm=...
>
> You can do almost everything with the CLI that you can with XenCenter, and 
> the CLI commands are much more close in naming to the underlying API than the 
> GUI operations. If you want to see what the GUI is doing during a particular 
> operation, tail /var/log/xensource.log or audit.log, and you should see the 
> API calls it's making. The CLI commands will be very similar to the names of 
> the APIs.
>
> For most xe commands, don't forget that you can tab-complete your way to 
> success :-)
>
> Jon
>
>

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>