openstack/openstack-manuals
Code Issues Proposed changes

Fix glossterm definition and use for AMQP

Browse Source 
The glossentry for "Advanced Message Queuing Protocol (AMQP)" had a
newline in its glossterm, and the security-guide referenced
a short form which doesn't exist in the glossary.

This results in an error (and a missing glossary definition in the
output):

No definition found for <glossterm xmlns="http://docbook.org/ns/docbook"
xmlns:db="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink">AMQP</glossterm>

Fix: remove newline, use baseform to point to existing glossentry.

Change-Id: I18f64458c651ebc9696fc9f2f51b23af2600ef46
This commit is contained in:
Roger Luethi 2014-04-29 18:34:58 +02:00
parent ceca7877d8
commit 66eb09c582
2 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/glossary/glossary-terms.xml
View File

@ -181,8 +181,7 @@
</glossdef> </glossdef>
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Advanced Message Queuing Protocol <glossterm>Advanced Message Queuing Protocol (AMQP)</glossterm>
(AMQP)</glossterm>
<glossdef> <glossdef>
<para>The open standard messaging protocol used by <para>The open standard messaging protocol used by
OpenStack components for intra-service communications, OpenStack components for intra-service communications,

6
doc/security-guide/ch004_book-introduction.xml
View File

@ -217,9 +217,9 @@
<para>OpenStack relies on messaging for internal communication <para>OpenStack relies on messaging for internal communication
between several of its services. By default, OpenStack uses between several of its services. By default, OpenStack uses
message queues based on the Advanced Message Queue Protocol message queues based on the Advanced Message Queue Protocol
(<glossterm>AMQP</glossterm>). Similar to most OpenStack (<glossterm baseform="Advanced Message Queuing Protocol (AMQP)">AMQP
services, it supports pluggable components. Today the </glossterm>). Similar to most OpenStack services, it supports
implementation backend could be pluggable components. Today the implementation backend could be
<glossterm>RabbitMQ</glossterm>, <glossterm>RabbitMQ</glossterm>,
<glossterm>Qpid</glossterm>, or <glossterm>Qpid</glossterm>, or
<glossterm>ZeroMQ</glossterm>.</para> <glossterm>ZeroMQ</glossterm>.</para>