view README @ 121:4868ace2726b

Add initial consistence checks in test suite for Xen_MemoryPool, Xen_ProcessorPool and Xen_VirtualSystemManagementService.

Signed-off-by: Luke Szymanski <Lukasz.Szymanski@Unisys.com>
author Jim Fehlig <jfehlig@novell.com>
date Fri Jun 08 10:22:05 2007 -0600 (2007-06-08)
parents 6ec07cc4fe79
line source
3 The Xen-CIM project implements various profiles defined by the System
4 Virtualization, Partitioning, and Clustering (SVPC) working group within
5 the Distributed Management Task Force (DMTF). The SVPC working group
6 includes members from EMC (VMWare), HP, IBM, Microsoft, Novell, Unisys,
7 XenSource, and others. The working group web page serves as a central
8 point for collaboration and can be found at
10 http://www.dmtf.org/apps/org/workgroup/redundancy
12 Membership to the working group requires registration but is free to all
13 DMTF member companies.
15 All profiles and schema created by the SVPC working group are
16 currently DMTF Confidential. The various profiles emerging from the
17 group cannot be shared at this time however the DMTF has given
18 permission to share the schema. Recent schema snapshots are located in
19 project directory schema/dmtf.
21 The profiles and schema are a work-in-progress and undergo rapid change.
22 Once stabilized, they are made publicly available as Experimental for
23 consumption and comment. At least two, interoperable implementations
24 must exits before promotion to Final.
26 The schema models a management domain, e.g. virtualization, and contains
27 all of the classes and their relationships that are required to describe
28 the management domain.
30 Profiles are schema companions that describe in normative text how the
31 model works. They are the specification to which implementations
32 should conform.
34 The Xen-CIM project aims to implement all relevant profiles produced
35 by the SVPC working group. The project is currently tracking the
36 following profiles:
38 DSP1042 System Virtualization Profile
39 DSP1057 Virtual System Profile
40 DSP1041 Resource Allocation Profile
41 DSP1043 Allocation Capabilities Profile
45 The project configure script accepts the standard configure options.
46 In addition, the --with-host-instrumentation=TYPE option can be used to
47 specify which host instrumentation will be used by the Xen-CIM providers.
48 The available TYPEs are omc and sblim with omc as the default.
50 "Host instrumentation" refers to implementations of DMTF profiles
51 describing physical host environments, such as DSP1052 Computer System
52 Profile. Many of the virtualization profiles reference profiles that have
53 been implemented by other open source projects, such as omc and sblim.
54 This project leverages that work and thus requires either omc or sblim for
55 model completeness. Further information on omc or sblim can be found at
56 their respective project sites:
58 OMC - http://developer.novell.com/wiki/index.php/OMC
59 SBLIM - http://sourceforge.net/projects/sblim/
64 You must have a CIMOM (including its associated development packages),
65 libxml2, and Xen development packages installed to compile. Then
66 simply try:
68 ./autoconfiscate.sh
69 ./configure
70 make
75 Use "make install" to install the provider library files. Default
76 location is /usr/local/lib/cmpi but can be controlled by the usual
77 options to configure.
79 The Xen-CIM schema is derived from the DMTF schema and provides concrete
80 classes for the implementation. These schema files are located in the
81 schema subdirectory. The DMTF schema in schema/dmtf and the Xen-CIM
82 schema are installed using the "make postinstall" target.
87 The Xen CIM providers require Xen >= 3.0.4. Currently the providers
88 expect to communicate with the Xen Control Stack in Domain0 using a
89 Unix Domain Socket. This socket provides access to the XMLRPC-based
90 Xen API used by the providers. Only root processes can connect to this
91 socket so it is expected that the providers will be running in a
92 privileged process.
94 The Xen Control Stack must be configured to open / listen on this
95 socket and allow 'unconditional' access. Note that unconditional
96 is a little misleading since only privileged (root) processes can
97 connect to the socket. Configuration is controlled via the
98 xend configuration file /etc/xen/xend-config.sxp. To enable the
99 Xen API XMLRPC interface place the following line in xend-config.sxp:
101 (xen-api-server ((unix none)))
103 See xend-config.sxp for more details. Restart xend, e.g.:
105 /etc/init.d/xend restart
107 and then access the provider functionality using your favorite
108 CIM/WBEM client.