Fix Warnings generated while building of HTML docu

Same ID have been set to reference different RST blocks.
To avoid this, I added the prefix 'archi_' within ID referencing
architecture RST block.

Bad indentation warnings have been fixed.

Change-Id: I17f43f2f564ffd83fd5c345aed96fad06ee56b1d
Partial-Bug: #1522034

watcher/api/controllers/v1/action_plan.py

@@ -295,7 +295,7 @@ class ActionPlansController(rest.RestController):
         :param sort_key: column to sort results by. Default: id.
         :param sort_dir: direction to sort. "asc" or "desc". Default: asc.
         :param audit_uuid: Optional UUID of an audit, to get only actions
-        for that audit.
+            for that audit.
         """
         return self._get_action_plans_collection(
             marker, limit, sort_key, sort_dir, audit_uuid=audit_uuid)
@@ -307,13 +307,13 @@ class ActionPlansController(rest.RestController):
         """Retrieve a list of action_plans with detail.
 
         :param action_plan_uuid: UUID of a action plan, to get only
-        :action_plans for that action.
+            action_plans for that action.
         :param marker: pagination marker for large data sets.
         :param limit: maximum number of resources to return in a single result.
         :param sort_key: column to sort results by. Default: id.
         :param sort_dir: direction to sort. "asc" or "desc". Default: asc.
         :param audit_uuid: Optional UUID of an audit, to get only actions
-        for that audit.
+            for that audit.
         """
         # NOTE(lucasagomes): /detail should only work agaist collections
         parent = pecan.request.path.split('/')[:-1][-1]

watcher/decision_engine/solution/base.py

@@ -38,7 +38,7 @@ applied.
 Two approaches to dealing with this can be envisaged:
 
 -  **fully automated mode**: only the :ref:`Solution <solution_definition>`
- with the highest ranking (i.e., the highest
+   with the highest ranking (i.e., the highest
    :ref:`Optimization Efficiency <efficiency_definition>`)
    will be sent to the :ref:`Watcher Planner <watcher_planner_definition>` and
    translated into concrete :ref:`Actions <action_definition>`.

watcher/doc.py

@@ -61,9 +61,7 @@ class WatcherTerm(rst.Directive):
         cls_path = self.arguments[0]
 
         try:
-            module_name, obj_name = cls_path.rsplit(".", 1)
-            module = importlib.import_module(module_name)
-            cls = getattr(module, obj_name)
+            cls = importlib.import_module(cls_path)
         except Exception as exc:
             raise self.error(exc)
 

watcher/metrics_engine/cluster_history/api.py

@@ -40,9 +40,9 @@ API is proposed with some helper classes in order to :
    See `the full list of meter types <http://docs.openstack.org/admin-guide-cloud/telemetry-measurements.html>`_
 -  simplify the development of a new :ref:`Strategy <strategy_definition>`
 -  avoid duplicating the same code in several
-:ref:`Strategies <strategy_definition>`
+   :ref:`Strategies <strategy_definition>`
 -  have a better consistency between the different
-:ref:`Strategies <strategy_definition>`
+   :ref:`Strategies <strategy_definition>`
 -  avoid any strong coupling with any external metrics/events storage system
    (the proposed API and measurement naming system acts as a pivot format)
 

watcher/metrics_engine/cluster_model_collector/api.py

@@ -34,7 +34,7 @@ and enables the :ref:`Strategy <strategy_definition>` to request information
 such as:
 
 -  What compute nodes are in a given
-:ref:`Availability Zone <availability_zone_definition>`
+   :ref:`Availability Zone <availability_zone_definition>`
    or a given :ref:`Host Aggregate <host_aggregates_definition>` ?
 -  What :ref:`Instances <instance_definition>` are hosted on a given compute
    node ?