Revision as of 14:22, 8 August 2013

DocBook markup conventions

This page offers writing conventions for OpenStack documentation. Following conventions helps to enhance the readabilty of our docs by enabling the DocBook stylesheets to format them consistently. Please modify this page as you come across more markup you need for the docs.openstack.org site.

General authoring conventions

This section contains general guidelines for editing OpenStack documents in DocBook.

Maximum line length in verbatim text

When using verbatim elements (including literallayout, programlisting, screen, and synopsis), do not exceed a line length of 70 characters.

Boolean configuration options

When documenting boolean configuration options, explicitly include the truth value.

Correct example

force_dhcp_release=True
use_ipv6=False

Incorrect example

force_dhcp_release
nouse_ipv6

Sections

Add IDs to sections

All section tags must have an xml:id attribute. This enables unique file names for the generated HTML and human-readable page titles, plus it lets Disqus threads stay with the HTML page.

Example

<section xml:id="section-id-goes-here">
...
</section>

Keeping sections together

To keep several sections on a single HTML page, use the DocBook stop_chunking processing instruction:

Example

<section xmlns="http://docbook.org/ns/docbook"
    xmlns:xi="http://www.w3.org/2001/XInclude"
    xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
    xml:id="xapi-resize-setup">
<?dbhtml stop-chunking?>
<title>Dom Modifications for Resize/Migration Support</title>
 ...

euca2ools documentation

Since Nova exposes both its own API and an EC2-compatible API, many tasks can be executed using either the nova CLI or euca2ools. Documentation related to euca2ools should generally be limited to:

   * Describing euca2ools commands that don't yet have a nova CLI equivalent (e.g., euca-get-console-output)
   * Describing how to get credentials to work with euca2ools
   * Describing differences between how Amazon's EC2 endpoint behaves and how an OpenStack endpoint behaves when accessing via EC2.

Adding a line break

In verbatim elements, you explicitly control line breaks. In the output of non-verbatim block elements (such as paragraphs and table cells), lines normally break automatically, for example at a fixed page or table boundary or when the reader resizes an HTML page. Automatic line breaking can fail if the text contains long strings that contain no whitespace. When that happens, the text is clipped or overflows the page or table boundaries.

If a line fails to break normally, try adding whitespace (like spaces) in the source where you want to allow line breaks. If that method is not available, you can force a line break anywhere in text by inserting the <?sbr?> processing instruction.

Example In the first line of code, spaces around the equals signs enable the line to wrap at either location. In the second line, <?sbr?> forces a line break.

<programlisting>
compute_driver = nova.virt.baremetal.driver.BareMetalDriver
scheduler_host_manager=nova.scheduler.baremetal_host_manager.<?sbr?>BaremetalHostManager
</programlisting>

cribing differences between how Amazon's EC2 endpoint behaves and how an OpenStack endpoint behaves when accessing via EC2.

Tagging

Choosing appropriate tags is important for using DocBook effectively. You can look up the semantic description of any tag in Oxygen. This section lists writing contexts where the choice of tags might not be obvious, and suggests the appropriate tagging.

General style conventions

• Use "OpenStack", not Openstack or openstack.
• Use "Compute", "Image", and "Identity" when referring to the services instead of "nova", "glance", and "keystone". Use the project names like "nova" and "keystone" when referring to the project or for CLI commands and service names.
• Wrap lines to 70 characters.

Configuration options

When documenting options in a .conf file, use the literal tag.

<literal>flat_network_bridge</literal>

Boolean configuration options

When documenting boolean configuration options, use the format that explicitly specifies the truth value:

force_dhcp_release=True
use_ipv6=False

Don't do it this way (which may not even work?)

force_dhcp_release
nouse_ipv6

Sections

All section tags must have an xml:id attribute. This enables unique file names for the generated HTML and human-readable page titles, plus it lets Disqus threads stay with the HTML page:

<section xml:id="section-id-goes-here">
...
</section>

If you want to keep several sections on a single HTML page, use a "stop chunking" processing directive:

<?dbhtml stop-chunking?>

Links

External

<link xlink:href="http://www.example.com">Linked text here</link>

Internal

<link linkend="section-name-here">Linked text here</link>

Information or configuration files that the user has to type or read

Do not indent the text (open/close tags may be indented)

    <programlisting>
config-file-example=asdf
foo=bar
hello=world
    </programlisting>

Inline configuration information (option name or value)

<literal>--use_deprecated_auth</literal>

Configuration information when part should be replaced

<literal>http://<replaceable>IP_ADDRESS</replaceable>/foo/bar</literal>

Inline mention of a specific command

<command>nova-manage</command>

Command to type into a shell

Do not indent the text (open/close tags may be indented). Use a prompt to show which user you are logged in as when entering the input. Generally on Ubuntu the docs use sudo to preface commands that must be run as a sudo user.

    <screen>
<prompt>$</prompt> <userinput>command as a regular user</userinput>
    </screen>

    <screen>
<prompt>#</prompt> <userinput>command as root</userinput>
    </screen>

    <screen>
<prompt>(mysql)</prompt> <userinput>command to type</userinput>
    </screen>

Result of the command

Do not indent the text (open/close tags may be indented)

    <screen>
<computeroutput>result output goes here</computeroutput>
    </screen>

Note that this can be combined with a prompt and input:

    <screen>
<prompt>$</prompt> <userinput>command to type</userinput>
<computeroutput>result output goes here</computeroutput>
    </screen>

File names

<filename>/my/file/is/here</filename>

File contents

The programlisting tag can do further output enhancements by using the language="langname" attribute including: bash, java, json, and xml.

<programlisting>
contents
of a
file
</programlisting>

Linux service

For example, nova-network or dnsmasq.

<systemitem class="service">nova-network</systemitem>

Procedures (where step 2 needs to be done after step 1)

<procedure><title>To do such and such</title>
       <step><para>...</para></step>
</procedure>

Note that the title must begin with the word, "To." Do not include a colon in the title.

Individual steps can also include titles. Step titles do not have to start with "To."

You can include substeps in any step, as follows:

<step><title>To configure the cloud</title>
<para>Complete the following steps:
<substeps>
<step><para>xx</para></step>
<step><para>xx</para></step>
</substeps>
</para>
</step>

Instructions to follow with no critical dependency across steps

<itemizedlist>
      <listitem><para>...</para></listitem>
</itemizedlist>

A list in key/value form

<variablelist>
  <varlistentry>
    <term>key</term>
    <listitem>value</listitem>
  </varlistentry>
  <varlistentry>
    <term>key</term>
    <listitem>value</listitem>
  </varlistentry>
</variablelist>

Notes

You can specify a Note callout box by doing:

<note><para>...</para></note>

Embedding images

In DocBook source, here is how you include images that have both a scalable-for-print-resolution in the PDF and an online-resolution for the HTML output. In this case the two types of images are SVG and PNG formats. The contentwidth="6in" attribute ensures that the image does not overlap print margins nor take up too much screen space.

<figure xml:id="CFinterfaces">
      <title>Cloud Files System Interfaces</title>
      <mediaobject>
        <imageobject>
          <imagedata contentwidth="6in" fileref="figures/CFinterfaces.svg"/>
        </imageobject>
      </mediaobject>
    </figure>

The convention is to use the /src/figures/ directory to store both the source image and any other formats of that same image. The pom.xml file copies the files in the /figures/ directory into the output directory required for HTML in the post processing section.

Also, when you add the image to the /src/figures directory, be sure to tell the source control system that you've added the image. For example, use "git add" to ensure the images get added to source control so the HTML and PDF output will be built correctly by the Jenkins continuous integration server.

For any figure you create, please also include the source files, even if the image was not created with open source tools, for maintenance purposes. While all OpenStack docs are created with open source in mind, including open-licensed fonts in the output, we are willing to allow non-open authoring or image creation tools if it's more efficient.

Tables

Use sentence capitalization for table captions and column headings.

Example:

    <table rules="all">
        <caption>Hardware recommendations </caption>
        <col width="20%"/>
        <col width="23%"/>
        <col width="57%"/>

        <thead>
            <tr>
                <td>Server</td>
                <td>Recommended hardware</td>
                <td>Notes</td>
            </tr>
        </thead>
        <tbody>
                <tr>
                        <td><para>...</para></td>
                ...
            </tr>
        </tbody>
    </table>

Force a line break

Especially handy when table cells aren't correctly wrapping or definition lists (like varlistentry) aren't wrapping well.

<?sbr?>

OS-specific (install & deploy guide)

The Install & Deploy guide has content that depends upon the operating system. Use the "os" attribute to specify a region that is operating-system specific. Valid values are:

• ubuntu
• fedora
• rhel
• centos
• deb
  

For example:

    <screen os="ubuntu"><userinput><prompt>$</prompt> sudo apt-get install -y ntp</userinput></screen>
    <screen os="rhel;fedora;centos"><prompt>$</prompt> <userinput>yum install -y ntp</userinput></screen>

Define a Hostname

Use lowercase unless legal reasons require capitalization.