From: Jim Fehlig <jfehlig@novell.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH][XenAPI] Implement VM.set_VCPUs_at_startup
Date: Tue, 12 Jun 2007 16:39:34 -0600 [thread overview]
Message-ID: <466F20A6.4020100@novell.com> (raw)
[-- 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
next reply other threads:[~2007-06-12 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 22:39 Jim Fehlig [this message]
2007-06-13 1:11 ` [PATCH][XenAPI] Implement VM.set_VCPUs_at_startup John Levon
2007-06-14 0:15 ` Jim Fehlig
2007-06-14 15:51 ` John Levon
2007-06-14 16:35 ` Jim Fehlig
2007-06-14 17:56 ` John Levon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=466F20A6.4020100@novell.com \
--to=jfehlig@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.