WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-cim

[Xen-cim] InstanceID property

To: xen-cim@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-cim] InstanceID property
From: Jim Fehlig <jfehlig@xxxxxxxxxx>
Date: Wed, 31 May 2006 15:46:58 -0600
Delivery-date: Wed, 31 May 2006 14:48:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-cim-request@lists.xensource.com?subject=help>
List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
List-post: <mailto:xen-cim@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (X11/20041206)
CIM_SettingData contains the key property InstanceID, which should be constructed with the "preferred" algorithm described in the mof. Basically InstanceID should be "<OrgID>:<LocalID>". Should we move to the preferred form of InstanceID?

Several weeks back I changed the SettingData classes to use the algorithm but did not consider how this affected some associations. Found one such case during testing today and decided to ask whether we want to support the preferred algorithm or drop back to the original code that just provided <LocalID>. What do we want to use for OrgID if supporting the preferred algorithm? The current code uses "Xen:"

Jim

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

<Prev in Thread] Current Thread [Next in Thread>