Implement VM.set_VCPUs_at_startup
PATCH 1/1 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
# HG changeset patch
# User Jim Fehlig <[email protected]>
# Date 1181687775 21600
# Node ID 809a2ff82eabef23f352e230b141fe3a301c77a2
# Parent 93f77a5a8437df0b34919a6987f48e84342b4a43
Implement VM.set_VCPUs_at_startup and VM.set_VCPUs_max XenAPI methods in xend.
tools/python/xen/xend/XendAPI.py +6 -0
@@ -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])
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel
Quoted 2 lines · Jim Fehlig
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
Quoted 10 lines · John Levon
Quoted 3 lines · Jim Fehlig
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).
Quoted 5 lines
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
Quoted 11 lines · Jim Fehlig
Quoted 5 lines
Quoted 2 lines
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).
Quoted 6 lines
Quoted 4 lines
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
Quoted 20 lines · John Levon
Quoted 17 lines · Jim Fehlig
Quoted 6 lines
Quoted 3 lines
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).
Quoted 5 lines
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?
Quoted 9 lines
Quoted 2 lines
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
Quoted 4 lines · Jim Fehlig
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