How To Use the Intel® Cluster Checker XML Schema

This article describes how you can use the XML Schema provided with Intel® Cluster Checker to help you create and edit your XML configuration file.  The file, clck.xsd, defines the set of rules to which an Intel® Cluster Checker XML configuration file must conform in order to be considered valid. 

You can create and edit your XML configuration file multiple ways. You can use a text editor or the Intel® Cluster Checker graphical user interface. You can also use an editor specifically designed for XML. Many XML editors have the ability to use XML Schemas as 'templates' that assist you as you work on your XML file.

The examples in this article show how to use the XML Schema with the xmllint utility.  xmllint is included in many Linux distributions by default and may also be downloaded and installed as part of the libxml2 package. 

You are highly recommended to validate your XML configuration file against the Schema before you run Intel® Cluster Checker.  Assuming your XML configuration file is named config.xml, you would run the following command to validate it:

$ xmllint --noout --xinclude --schema clck.xsd config.xml


If the XML configuration file is valid, you should see output similar to:

config.xml validates


However, if there is a problem with your XML configuration file, the xmllint output will report it.  For example:

config.xml:6: element hpcc: Schemas validity error : Element 'hpcc' [CT local]: The element content is not valid.
config.xml fails to validate


This output indicates a problem was found near line 6 of the file inside the hpcc element.  In this example, the device setting was mistakenly placed outside a fabric container.

<hpcc>
  <device>ssm</device>
  <device>rdssm</device>
</hpcc>


The corrected XML configuration file that passes validation is:

<hpcc>
  <fabric>
    <device>ssm</device>
  </fabric>
  <fabric>
    <device>rdssm</device>
  </fabric>
</hpcc>



Para obtener información más completa sobre las optimizaciones del compilador, consulte nuestro Aviso de optimización.
Etiquetas: