# HG changeset patch # User Dan Smith <danms@us.ibm.com> # Date 1193852665 25200 # Node ID fb92838e55651ca80d2de49344db81312a5ebe8b # Parent 5789eadba6e6f71822493043214c3a8749ebb2f6 Add some starter web content Right now, this is just the flat content (un-transformed), but it should get us started. Comments welcome :) Signed-off-by: Dan Smith <danms@us.ibm.com> diff -r 5789eadba6e6 -r fb92838e5565 Makefile.am --- a/Makefile.am Sat Feb 14 12:09:10 2015 -0800 +++ b/Makefile.am Wed Oct 31 10:44:25 2007 -0700 @@ -1,5 +1,5 @@ # Copyright IBM Corp. 2007 -SUBDIRS = libxkutil src +SUBDIRS = libxkutil src doc MOFS = \ schema/ComputerSystem.mof \ diff -r 5789eadba6e6 -r fb92838e5565 configure.ac --- a/configure.ac Sat Feb 14 12:09:10 2015 -0800 +++ b/configure.ac Wed Oct 31 10:44:25 2007 -0700 @@ -67,6 +67,7 @@ AC_CONFIG_FILES([ libxkutil/tests/Makefile src/Makefile src/tests/Makefile + doc/Makefile Makefile ]) diff -r 5789eadba6e6 -r fb92838e5565 doc/Makefile.am --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/doc/Makefile.am Wed Oct 31 10:44:25 2007 -0700 @@ -0,0 +1,9 @@ +XSLTPROC = /usr/bin/xsltproc + +WEB_PAGES = index.html + +$(WEB_PAGES): libvirt-cim.html site.xsl + $(XSLTPROC) --nonet --html $(top_srcdir)/doc/site.xsl $(top_srcdir)/doc/libvirt-cim.html > index.html + +all: $(WEB_PAGES) + diff -r 5789eadba6e6 -r fb92838e5565 doc/libvirt-cim.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/doc/libvirt-cim.html Wed Oct 31 10:44:25 2007 -0700 @@ -0,0 +1,147 @@ +<html> +<head> + <meta http-equiv="Content-Type" content=""> + <title>Libvirt-CIM: The CIM provider for libvirt</title> +</head> + +<body bgcolor="#ffffff"> +<h1 align="center">Libvirt-CIM: The CIM provider for libvirt</h1> + +<h1>Note: this is the flat content of the <a href="index.html">web site</a></h1> + +<h1 style="text-align: center">libvirt-cim</h1> + +<h3>What is <span class="style1">libvirt-cim?</span></h3> + +<p>Libvirt-CIM is a CIM provider for managing linux virtualization + platforms using libvirt. It is written in C and should work in any + CIMOM that supports CMPI 2.0 providers. The intent is to implement + the SVPC virtualization class model currently available in the DMTF + Experimental 2.16 schema. +</p> + +<h2><a name="News">Releases</a></h2> + +<p>There have been no releases to date</p> + +<h2><a name="Introducti">Introduction</a></h2> + +<p>Libvirt-CIM is a CIM provider for managing linux virtualization + platforms using libvirt. It is written in C and should work in any + CIMOM that supports CMPI 2.0 providers. The intent is to implement + the SVPC virtualization class model currently available in the DMTF + Experimental 2.16 schema. +</p> + +<p>The providers are currently under heavy development. Focus is on + Xen support right now, which means some of the providers have some + "shortcuts" hard-coded to Xen right now. The long-term goal is to + support all of the platforms that libvirt supports with minimal + differences. +</p> + +<h2><a name="Downloads">Downloads</a></h2> + +<p>The libvirt-cim development tree can be found in the + <a href="http://libvirt.org/hg">libvirt.org/hg</a> repository. +</p> + +<p>To get a copy of the development tree, use + <a href="http://www.selenic.com/mercurial/wiki/">mercurial</a>'s + clone feature: +</p> + +<p><code>$ hg clone http://libvirt.org/hg/libvirt-cim</code></p> + +<p>Alternatively, you can grab a + <a href="http://libvirt.org/hg/libvirt-cim/archive/tip.tar.gz">tarball</a> or + <a href="http://libvirt.org/hg/libvirt-cim/archive/tip.zip">zip</a> + file snapshot of the repository. +</p> + +<h2><a name="Schema">Schema Requirements and Installation</a></h2> + +<p>The libvirt-cim provider depends on an installed + <a href="http://www.dmtf.org/standards/cim/cim_schema_v216/">DMTF + CIM v2.16</a> Experimental schema. The package can be obtained +<a href="http://www.dmtf.org/standards/cim/cim_schema_v216/cimv216Experimental-MOFs.zip">here</a>.</p> + +<h4>To install the schema in Pegasus:</h4> + +<p><code> + $ PEGASUS_REPO=/var/lib/Pegasus # adjust this as needed<br/> + $ mkdir cim216<br/> + $ cd cim216<br/> + $ unzip $PATH_TO_ZIPFILE<br/> + $ sudo cimmofl -uc -aEV -R$PEGASUS_REPO -n /root/ibmsd cimv216.mof<br/> +</code></p> + +<h4>To install the schema in SFCB:</h4> + +<p><code> + $ SFCB_CIM=/usr/local/share/sfcb/CIM # adjust this as needed<br/> + $ mkdir cim216<br/> + $ cd cim216<br/> + $ unzip $PATH_TO_ZIPFILE<br/> + $ mv cimv216.mof CIM_Schema.mof<br/> + $ sudo cp * $SFCB_CIM<br/> + $ sudo sfcbrepos<br/> +</code></p> + +<p><strong>Note:</strong> in both cases, the CIM v2.16 schema seems to have a + few classes that don't register correctly. You may need to + disable installation of classes with something like the + following: +</p> + +<p><code> +--- CIM_Schema.mof 2007-10-15 00:15:44.000000000 -0700<br/> ++++ cimv216.mof 2007-10-22 10:11:19.000000000 -0700<br/> +@@ -507,3 +507,3 @@<br/> + #pragma include ("Policy/CIM_SharedSecretAuthentication.mof")<br/> +-#pragma include ("Security/CIM_SecurityIndication.mof")<br/> ++//#pragma include ("Security/CIM_SecurityIndication.mof")<br/> + #pragma include ("Support/PRS_Activity.mof")<br/> +@@ -728,4 +728,4 @@<br/> + #pragma include ("Policy/CIM_PolicyConditionInPolicyRule.mof")<br/> +-#pragma include ("Security/CIM_IPNetworkSecurityIndication.mof")<br/> +-#pragma include ("Security/CIM_IPPacketFilterIndication.mof")<br/> ++//#pragma include ("Security/CIM_IPNetworkSecurityIndication.mof")<br/> ++//#pragma include ("Security/CIM_IPPacketFilterIndication.mof")<br/> + #pragma include ("Support/PRS_ActivityContact.mof")<br/> +</code></p> + +<h2><a name="Platforms">Platform Support</a></h2> + +<p>Currently, libvirt-cim is targetting Xen as its primary support + platform because is has the largest installed user base. The + long-term plan is to support many others (hopefully any that libvirt + supports). This includes KVM and containers. +</p> + +<p>The code base currently has many Xen-specific "shortcuts" that need + to be resolved and generalized in order to support other platforms. + A short list of these may include:</p> +<ul> + <li>The XML generation and parsing code and the related device + modeling code.</li> + <li>The libvirt connection logic. Right now, (in most places) we + detect the current hypervisor in use and connect to libvirt + appropriately. This may or may not be the correct behavior in a + situation where you could need to support containers and QEMU + virtual machines.</li> + <li>Some lingering hard-coded "Xen_Foo" class names.</li> +</ul> + +<p>Further, supporting new platforms have some registration and + modeling implications:</p> +<ul> + <li>Additions to the MOF and registration files for "branded" + classes (Xen_Foo, KVM_Foo, etc)</li> + <li>Modifications to some of the association providers that register + separate CMPI provider structures for each class type they handle + (to avoid duplicate results in the general case)</li> +</ul> + +</body> +</html>