Xen devel - Jun 2007 - [PATCH][XenAPI] Implement VM.set_VCPUs_at_startup

This patch implements VM.set_VCPUs_at_startup and VM.set_VCPUs_max
XenAPI methods in xend.  Implementation already exists in XenAPI c-bindings.

Regards,
Jim




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

On Tue, Jun 12, 2007 at 04:39:34PM -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?

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?

regards
john

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

John Levon wrote:
> On Tue, Jun 12, 2007 at 04:39:34PM -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 :-).

Regards,
Jim


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

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?

john

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

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@lists.xensource.com
http://lists.xensource.com/xen-devel

On Thu, Jun 14, 2007 at 10:35:01AM -0600, Jim Fehlig wrote:
> 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)))
Ah, this was what I was missing. Thanks.

regards
john

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