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-devel

Re: [Xen-devel] [PATCH][XenAPI] Implement VM.set_VCPUs_at_startup

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][XenAPI] Implement VM.set_VCPUs_at_startup
From: Jim Fehlig <jfehlig@xxxxxxxxxx>
Date: Thu, 14 Jun 2007 10:35:01 -0600
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 14 Jun 2007 09:33:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070614155117.GA30365@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <466F20A6.4020100@xxxxxxxxxx> <20070613011143.GB17307@xxxxxxxxxxxxxxxxxxxxxxx> <4670889C.603@xxxxxxxxxx> <20070614155117.GA30365@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.8 (X11/20060911)
John Levon wrote:
> On Wed, Jun 13, 2007 at 06:15:24PM -0600, Jim Fehlig wrote:
>
>   
>>>> This patch implements VM.set_VCPUs_at_startup and VM.set_VCPUs_max
>>>> XenAPI methods in xend.  Implementation already exists in XenAPI 
>>>> c-bindings.
>>>>         
>>> I'm a little bit confused by all these patches I'm seeing. It looks like
>>> some basic parts of the 1.0 API still aren't done yet; is that accurate?
>>>       
>> Yep, seems to be the case.  Many of the class fields/methods defined in
>> the spec are not implemented in xend.  Not sure how much the spec and
>> implementation diverge - although quickly finding out as the cim
>> providers consume more of Xen API (hence the patches).
>>
>>     
>>> If so, is there an ETA for when xend will be finished and the
>>> documentation completed (it's still very incomplete unfortunately) ? And
>>> will they be backported to the 3.1 branch, or will users need to wait
>>> for the next minor release to get a finished API?
>>>       
>> Good questions, unfortunately I'm not the one who can answer :-).
>>     
>
> Anybody at XenSource care to comment?
>
> I'm also confused about xm. When it uses xen-api exclusively, it looks
> like I'll have to create a fake user and put their name and password
> in the clear in a file in /etc. Is that the intended plan?
>   

I have xend configured to use unix domain socket for Xen API server with
no authentication.  In xend-config.sxp:

(xen-api-server ((unix none)))

The socket is restricted to root via file permissions.  In xm-config.xml
I have xm configured to use the socket

  <server type='Xen-API'
          uri='httpu:///var/run/xend/xen-api.sock' />

Jim


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel