Cleanup the common/ directory

Move the used items to the correct folders (images, samples), and only
keep the files needed by the cli-ref (the only docbook document left in
this repository).

Change-Id: I4a38dc0bbd1497fb13933deb691ec9e8ca992c86

doc/admin-guide-cloud/source/compute-images-instances.rst

@@ -436,6 +436,6 @@ Administrative users can specify which compute node their instances
 run on. To do this, specify the ``--availability-zone
 AVAILABILITY_ZONE:COMPUTE_HOST`` parameter.
 
-.. |Base image state with no running instances| image:: ../../common/figures/instance-life-1.png
+.. |Base image state with no running instances| image:: figures/instance-life-1.png
-.. |Instance creation from image and runtime state| image:: ../../common/figures/instance-life-2.png
+.. |Instance creation from image and runtime state| image:: figures/instance-life-2.png
-.. |End state of image and volume after instance exits| image:: ../../common/figures/instance-life-3.png
+.. |End state of image and volume after instance exits| image:: figures/instance-life-3.png

doc/admin-guide-cloud/source/compute-networking-nova.rst

@@ -1001,9 +1001,9 @@ the kernel module:
 
    Loading the module has no effect on running instances.
 
-.. |multinic flat manager| image:: ../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-manager.jpg
+.. |multinic flat manager| image:: figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-manager.jpg
    :width: 600
-.. |multinic flatdhcp manager| image:: ../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-DHCP-manager.jpg
+.. |multinic flatdhcp manager| image:: figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-DHCP-manager.jpg
    :width: 600
-.. |multinic VLAN manager| image:: ../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-VLAN-manager.jpg
+.. |multinic VLAN manager| image:: figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-VLAN-manager.jpg
    :width: 600

doc/admin-guide-cloud/source/compute-security.rst

@@ -137,8 +137,8 @@ settings:
 
 |Trusted compute pool|
 
-.. |image0| image:: ../../common/figures/OpenStackTrustedComputePool1.png
+.. |image0| image:: figures/OpenStackTrustedComputePool1.png
-.. |Trusted compute pool| image:: ../../common/figures/OpenStackTrustedComputePool2.png
+.. |Trusted compute pool| image:: figures/OpenStackTrustedComputePool2.png
 
 
 Encrypt Compute metadata traffic

doc/admin-guide-cloud/source/networking_arch.rst

@@ -83,6 +83,6 @@ service on the network node. The green arrow indicates the management
 relationship between the NSX controller and the network node.
 
 
-.. figure:: ../../common/figures/vmware_nsx_ex1.png
+.. figure:: figures/vmware_nsx_ex1.png
 
-.. figure:: ../../common/figures/vmware_nsx_ex2.png
+.. figure:: figures/vmware_nsx_ex2.png

doc/admin-guide-cloud/source/networking_introduction.rst

@@ -172,7 +172,7 @@ the perimeter to filter traffic at the neutron router.
 The example diagram illustrates the flow of ingress and egress traffic
 for the VM2 instance:
 
-.. figure:: ../../common/figures/fwaas.png
+.. figure:: figures/fwaas.png
 
 **To enable FWaaS**
 

doc/admin-guide-cloud/source/networking_multi-dhcp-agents.rst

@@ -28,7 +28,7 @@ scalability and HA.
        | extraroute      | Neutron Extra Route      |
        +-----------------+--------------------------+
 
-.. figure:: ../../common/figures/demo_multiple_dhcp_agents.png
+.. figure:: figures/demo_multiple_dhcp_agents.png
 
 There will be three hosts in the setup.