[PATCH][XenAPI] Implement VM.set_VCPUs_at_startup

[PATCH][XenAPI] Implement VM.set_VCPUs_at_startup

[Jim Fehlig]

[-- Attachment #1: Type: text/plain, Size: 160 bytes --]

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



[-- Attachment #2: xend_vm_set_vcpus.patch --]
[-- Type: text/x-patch, Size: 1082 bytes --]

# HG changeset patch
# User Jim Fehlig <jfehlig@novell.com>
# Date 1181687775 21600
# Node ID 809a2ff82eabef23f352e230b141fe3a301c77a2
# Parent  93f77a5a8437df0b34919a6987f48e84342b4a43
Implement VM.set_VCPUs_at_startup and VM.set_VCPUs_max XenAPI methods in xend.

Signed-off-by: Jim Fehlig <jfehlig@novell.com>

diff -r 93f77a5a8437 -r 809a2ff82eab tools/python/xen/xend/XendAPI.py
--- a/tools/python/xen/xend/XendAPI.py	Sun Jun 10 19:58:22 2007 +0100
+++ b/tools/python/xen/xend/XendAPI.py	Tue Jun 12 16:36:15 2007 -0600
@@ -1483,6 +1483,12 @@ class XendAPI(object):
         else:
             return xen_api_success_void()
     
+    def VM_set_VCPUs_at_startup(self, session, vm_ref, num):
+        return self.VM_set('VCPUs_at_startup', session, vm_ref, num)
+
+    def VM_set_VCPUs_max(self, session, vm_ref, num):
+        return self.VM_set('VCPUs_max', session, vm_ref, num)
+
     def VM_set_actions_after_shutdown(self, session, vm_ref, action):
         if action not in XEN_API_ON_NORMAL_EXIT:
             return xen_api_error(['VM_ON_NORMAL_EXIT_INVALID', vm_ref])

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: [PATCH][XenAPI] Implement VM.set_VCPUs_at_startup

[John Levon]

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

Re: [PATCH][XenAPI] Implement VM.set_VCPUs_at_startup

[Jim Fehlig]

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

Re: [PATCH][XenAPI] Implement VM.set_VCPUs_at_startup

[John Levon]

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

Re: [PATCH][XenAPI] Implement VM.set_VCPUs_at_startup

[Jim Fehlig]

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

Re: [PATCH][XenAPI] Implement VM.set_VCPUs_at_startup

[John Levon]

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