aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorUlas Kozat <ulas.kozat@gmail.com>2016-08-15 13:38:36 -0700
committerUlas Kozat <ulas.kozat@gmail.com>2016-08-15 13:38:36 -0700
commit1c48869c10c1eb0a4fbcc803238170dd39e2eb9d (patch)
tree083214686d4a9baddcf1c3f3f8af556ef8eb9b7f
parent98bff820bfc71cbd6096fc5f84e687b8f6bdd810 (diff)
Switch to manual referencing for figures in the user guide
Change-Id: I8351c976ef6e5cf7bf3086c7e53ad78e8e9337d6 Signed-off-by: Ulas Kozat <ulas.kozat@gmail.com>
-rw-r--r--docs/userguide/feature.userguide.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/userguide/feature.userguide.rst b/docs/userguide/feature.userguide.rst
index 86effb7..fedce4d 100644
--- a/docs/userguide/feature.userguide.rst
+++ b/docs/userguide/feature.userguide.rst
@@ -34,7 +34,7 @@ Domino Capabilities and Usage
Labels in Domino
----------------
-Domino's pub/sub architecture is based on labels (see :numref:`fig-label` below).
+Domino's pub/sub architecture is based on labels (see Fig. 1 below).
Each Template Producer and Template Consumer is expected to run a local Domino Client
to publish templates and subscribe for labels.
@@ -209,7 +209,7 @@ existing translators (e.g., heat-translator) to first translate the template bef
Internal Processing Pipeline at Domino Server
---------------------------------------------
-:numref:`fig-pipe` shows the block diagram for the processing stages of a published TOSCA template.
+Fig. 2 shows the block diagram for the processing stages of a published TOSCA template.
Domino Client issues an RPC call publish(tosca file). Domino Server passes the received tosca
file to Label Extractor that outputs resource labels. Domain Mapper uses the extracted labels
and tosca file to find mappings from resources to domains as well as the resource dependencies.