From: Jim Fehlig <jfehlig@novell.com>
To: Xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] [xend] Add uuid to host record
Date: Mon, 13 Nov 2006 17:26:16 -0700 [thread overview]
Message-ID: <45590D28.6080701@novell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 145 bytes --]
This patch adds uuid to host record returned by host_get_record. libxen
fails to parse the host record when this field missing.
Regards,
Jim
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: libxen-host-uuid.patch --]
[-- Type: text/x-patch; name="libxen-host-uuid.patch", Size: 1009 bytes --]
# HG changeset patch
# User jfehlig@jfehlig2.provo.novell.com
# Date 1163463829 25200
# Node ID 3342aabd73e0332a398bc8f69543213d196a0845
# Parent 9a341c6ef6ae2ce90ccdcf89718d4365426d9d96
Add uuid to host record returned by host_get_record. libxen fails to parse the host record with this field missing.
Signed-off-by: Jim Fehlig <jfehlig@novell.com>
diff -r 9a341c6ef6ae -r 3342aabd73e0 tools/python/xen/xend/XendAPI.py
--- a/tools/python/xen/xend/XendAPI.py Mon Nov 13 14:25:48 2006 +0000
+++ b/tools/python/xen/xend/XendAPI.py Mon Nov 13 17:23:49 2006 -0700
@@ -481,7 +481,8 @@ class XendAPI:
def host_get_record(self, session, host_ref):
node = XendNode.instance()
dom = XendDomain.instance()
- record = {'name_label': node.name,
+ record = {'uuid': node.uuid,
+ 'name_label': node.name,
'name_description': '',
'software_version': node.xen_version(),
'resident_VMs': dom.get_domain_refs(),
[-- 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:[~2006-11-14 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 0:26 Jim Fehlig [this message]
2006-11-14 0:50 ` [PATCH] [xend] Add uuid to host record Ewan Mellor
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=45590D28.6080701@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.