Revert "[admin-guide-cloud] Fix an empty line in code-blocks"

This reverts commit 690138ae1b.

Change-Id: Ia87e853cae68b58ff62b2fe640e6c6f927f3a1ac

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

@@ -34,7 +34,6 @@ First, get a list of the services:
 .. code-block:: console
 
    $ cinder service-list
-
    +------------------+-------------------+------+---------+-------+------+
    |      Binary      |        Host       | Zone |  Status | State | ...  |
    +------------------+-------------------+------+---------+-------+------+
@@ -49,7 +48,6 @@ as listed below.
 .. code-block:: console
 
    $ cinder get-capabilities block1@ABC-driver
-
    +---------------------+----------------------------------------------+
    |     Volume stats    |                    Value                     |
    +---------------------+----------------------------------------------+
@@ -167,7 +165,6 @@ Create a public volume type by setting ``is_public`` field to ``True``:
 .. code-block:: console
 
    $ cinder type-create --description test1 --is-public True vol_Type1
-
    +--------------------------------------+-----------+-------------+-----------+
    |                  ID                  |    Name   | Description | Is_Public |
    +--------------------------------------+-----------+-------------+-----------+
@@ -179,7 +176,6 @@ Create a private volume type by setting ``is_public`` field to ``False``:
 .. code-block:: console
 
    $ cinder type-create --description test2 --is-public False vol_Type2
-
    +--------------------------------------+-----------+-------------+-----------+
    |                  ID                  |    Name   | Description | Is_Public |
    +--------------------------------------+-----------+-------------+-----------+
@@ -191,7 +187,6 @@ Get a list of the volume types:
 .. code-block:: console
 
    $ cinder type-list
-
    +--------------------------------------+-------------+-------------+-----------+
    |                  ID                  |     Name    | Description | Is_Public |
    +--------------------------------------+-------------+-------------+-----------+
@@ -205,7 +200,6 @@ Get a list of the projects:
 .. code-block:: console
 
    $ openstack project list
-
    +----------------------------------+--------------------+
    | ID                               | Name               |
    +----------------------------------+--------------------+
@@ -227,7 +221,6 @@ List the access information about the given volume type:
 .. code-block:: console
 
    $ cinder type-access-list --volume-type vol_Type2
-
    +--------------------------------------+----------------------------------+
    |            Volume_type_ID            |            Project_ID            |
    +--------------------------------------+----------------------------------+
@@ -241,7 +234,6 @@ Remove volume type access for the given project:
    $ cinder type-access-remove --volume-type vol_Type2 --project-id
    c4860af62ffe465e99ed1bc08ef6082e
    $ cinder type-access-list --volume-type vol_Type2
-
    +----------------+------------+
    | Volume_type_ID | Project_ID |
    +----------------+------------+

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

@@ -41,7 +41,6 @@ First, list the available back-ends:
 .. code-block:: console
 
    # cinder get-pools
-
    +----------+----------------------------------------------------+
    | Property |                       Value                        |
    +----------+----------------------------------------------------+
@@ -74,7 +73,6 @@ Next, as the admin user, you can see the current status of the volume
 .. code-block:: console
 
    $ cinder show 6088f80a-f116-4331-ad48-9afb0dfb196c
-
    +--------------------------------+--------------------------------------+
    |            Property            |                Value                 |
    +--------------------------------+--------------------------------------+

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

@@ -166,7 +166,6 @@ To experiment, you need VMs and a neutron network:
     +-------------------------------------+----------+--------+--------------+
 
    $ neutron net-list
-
     +-------------------------+------+--------------------------------------+
     | id                      | name | subnets                              |
     +-------------------------+------+--------------------------------------+

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

@@ -45,7 +45,6 @@ specifying two comma-separated share types:
 .. code-block:: console
 
    $ manila cg-create --name cgroup1 --description "My first CG." --share-types my_type1,default --share-network my_share_net
-
    +----------------------+--------------------------------------+
    | Property             | Value                                |
    +----------------------+--------------------------------------+
@@ -68,7 +67,6 @@ Check that consistency group is in available status:
 .. code-block:: console
 
    $ manila cg-show cgroup1
-
    +----------------------+--------------------------------------+
    | Property             | Value                                |
    +----------------------+--------------------------------------+
@@ -93,7 +91,6 @@ group in ``available`` status:
 .. code-block:: console
 
    $ manila create nfs 1 --name "Share2" --description "My second share" --share-type default --share-network my_share_net --consistency-group cgroup1
-
    +-----------------------------+--------------------------------------+
    | Property                    | Value                                |
    +-----------------------------+--------------------------------------+
@@ -174,7 +171,6 @@ Create a snapshot of consistency group ``cgroup1``:
 .. code-block:: console
 
    $ manila cg-snapshot-create cgroup1 --name CG_snapshot1 --description "A snapshot of the first CG."
-
    +----------------------+--------------------------------------+
    | Property             | Value                                |
    +----------------------+--------------------------------------+
@@ -192,7 +188,6 @@ Check the status of created consistency group snapshot:
 .. code-block:: console
 
    $ manila cg-snapshot-show CG_snapshot1
-
    +----------------------+--------------------------------------+
    | Property             | Value                                |
    +----------------------+--------------------------------------+
@@ -224,7 +219,6 @@ group snapshot is ``Share2`` share:
 .. code-block:: console
 
    $ manila cg-snapshot-members CG_snapshot1
-
    +--------------+------+----------------------------+----------------+--------------+--------------+
    | Id           | Size | Created_at                 | Share_protocol | Share_id     | Share_type_id|
    +--------------+------+----------------------------+----------------+--------------+--------------+
@@ -237,7 +231,6 @@ group from it:
 .. code-block:: console
 
    $ manila cg-create --source-cgsnapshot-id 876ad24c-1efd-4607-a2b1-6a2c90034fa5 --name cgroup2 --description "A consistency group from a CG snapshot."
-
    +----------------------+-----------------------------------------+
    | Property             | Value                                   |
    +----------------------+-----------------------------------------+
@@ -260,7 +253,6 @@ Check the list of consistency group. There are two groups now:
 .. code-block:: console
 
    $ manila cg-list
-
    +-------------------+---------+-----------------------------------------+-----------+
    | id                | name    | description                             | status    |
    +-------------------+---------+-----------------------------------------+-----------+
@@ -275,7 +267,6 @@ consistency group ``cgroup2`` from a snapshot with a member.
 .. code-block:: console
 
    $ manila list
-
    +------+-------+-----+------------+----------+----------+-----------+--------------------------+
    | ID   | Name  | Size| Share Proto| Status   | Is Public| Share Type| Host                     |
    +------+-------+-----+------------+----------+----------+-----------+--------------------------+
@@ -296,7 +287,6 @@ Print detailed information about new share:
 .. code-block:: console
 
    $ manila show ba52454e-2ea3-47fa-a683-3176a01295e6
-
    +-----------------------------+---------------------------------------------------------------+
    | Property                    | Value                                                         |
    +-----------------------------+---------------------------------------------------------------+

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

@@ -119,7 +119,6 @@ Check share types that exist, run:
 .. code-block:: console
 
    $ manila type-list
-
    +------+--------+-----------+------------------------------------+----------------------+
    | ID   | Name   | is_default| required_extra_specs               | optional_extra_specs |
    +------+--------+-----------+------------------------------------+----------------------+
@@ -132,7 +131,6 @@ protocol, and size 1 GB:
 .. code-block:: console
 
    $ manila create nfs 1 --name Share2 --description "My share" --share-type my_type
-
    +-----------------------------+--------------------------------------+
    | Property                    | Value                                |
    +-----------------------------+--------------------------------------+
@@ -166,7 +164,6 @@ New share ``Share2`` should have a status ``available``:
 .. code-block:: console
 
    $ manila show Share2
-
    +-----------------------------+---------------------------------------------------------------+
    | Property                    | Value                                                         |
    +-----------------------------+---------------------------------------------------------------+
@@ -242,7 +239,6 @@ Check share types that exist, run:
 .. code-block:: console
 
    $ manila type-list
-
    +------+--------+-----------+-----------+----------------------------------+----------------------+
    | ID   | Name   | Visibility| is_default| required_extra_specs             | optional_extra_specs |
    +------+--------+-----------+-----------+----------------------------------+----------------------+
@@ -254,7 +250,6 @@ Check share networks that exist, run:
 .. code-block:: console
 
    $ manila share-network-list
-
    +--------------------------------------+--------------+
    | id                                   | name         |
    +--------------------------------------+--------------+
@@ -267,7 +262,6 @@ share type, NFS shared file system protocol, and size 1 GB:
 .. code-block:: console
 
    $ manila create nfs 1 --name "Share1" --description "My first share" --share-type default --share-network my_share_net --metadata aim=testing --public
-
    +-----------------------------+--------------------------------------+
    | Property                    | Value                                |
    +-----------------------------+--------------------------------------+
@@ -304,7 +298,6 @@ See the share in a share list:
 .. code-block:: console
 
    $ manila list
-
    +----+-------+-----+------------+-----------+-------------------------------+----------------------+
    | ID | Name  | Size| Share Proto| Share Type| Export location               | Host                 |
    +----+-------+-----+------------+-----------+-------------------------------+----------------------+
@@ -317,7 +310,6 @@ status share should have status ``available``:
 .. code-block:: console
 
    $ manila show Share1
-
    +-----------------------------+-------------------------------------------+
    | Property                    | Value                                     |
    +-----------------------------+-------------------------------------------+
@@ -359,7 +351,6 @@ the share if you need:
    $ manila update Share1 --description "My first share. Updated" --is-public False
 
    $ manila show Share1
-
    +-----------------------------+--------------------------------------------+
    | Property                    | Value                                      |
    +-----------------------------+--------------------------------------------+
@@ -442,7 +433,6 @@ Get all metadata key-value pairs of the share:
 .. code-block:: console
 
    $ manila metadata-show Share1
-
    +----------+----------+
    | Property | Value    |
    +----------+----------+
@@ -456,7 +446,6 @@ You can update the metadata:
 .. code-block:: console
 
    $ manila metadata-update-all Share1 deadline=01/30/16
-
    +----------+----------+
    | Property | Value    |
    +----------+----------+
@@ -481,7 +470,6 @@ include ``available``, ``error``, ``creating``, ``deleting``,
    $ manila reset-state Share2 --state deleting
 
    $ manila show Share2
-
    +-----------------------------+-------------------------------------------+
    | Property                    | Value                                     |
    +-----------------------------+-------------------------------------------+
@@ -559,7 +547,6 @@ Print the list of all shares for all tenants:
 .. code-block:: console
 
    $ manila list --all-tenants
-
    +------+-------+-----+------------+-------+-----------+-----------------------------+-------------+
    | ID   | Name  | Size| Share Proto| Status| Share Type| Export location             | Host        |
    +------+-------+-----+------------+-------+-----------+-----------------------------+-------------+
@@ -575,7 +562,6 @@ run:
    $ manila force-delete b6b0617c-ea51-4450-848e-e7cff69238c7
 
    $ manila list
-
    +------+-------+-----+------------+-------+-----------+-----------------------------+-------------+
    | ID   | Name  | Size| Share Proto| Status| Share Type| Export location             | Host        |
    +------+-------+-----+------------+-------+-----------+-----------------------------+-------------+
@@ -630,7 +616,6 @@ type and ``10.254.0.4`` IP address:
 .. code-block:: console
 
    $ manila access-allow Share2 ip 10.254.0.4 --access-level rw
-
    +--------------+--------------------------------------+
    | Property     | Value                                |
    +--------------+--------------------------------------+
@@ -679,7 +664,6 @@ Allow access to the share with ``user`` access type:
 .. code-block:: console
 
    $ manila access-allow Share2 user demo --access-level rw
-
    +--------------+--------------------------------------+
    | Property     | Value                                |
    +--------------+--------------------------------------+
@@ -706,7 +690,6 @@ you list permissions for a share:
 .. code-block:: console
 
    $ manila access-list Share2
-
    +--------------------------------------+-------------+------------+--------------+--------+
    | id                                   | access type | access to  | access level | state  |
    +--------------------------------------+-------------+------------+--------------+--------+
@@ -722,7 +705,6 @@ access rule list:
    $ manila access-deny Share2 de715226-da00-4cfc-b1ab-c11f3393745e
 
    $ manila access-list Share2
-
    +--------------------------------------+-------------+-----------+--------------+-------+
    | id                                   | access type | access to | access level | state |
    +--------------------------------------+-------------+-----------+--------------+-------+

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

@@ -78,7 +78,6 @@ To manage share, run:
 .. code-block:: console
 
    $ manila manage manila@cannes#CANNES nfs 10.254.0.7:/shares/share-d1a66eed-a724-4cbb-a886-2f97926bd3b3 --name Share --description "We manage share." --share_type for_managing
-
    +-----------------------------+---------------------------------------------------------------+
    | Property                    | Value                                                         |
    +-----------------------------+---------------------------------------------------------------+
@@ -112,7 +111,6 @@ Check that the share is available:
 .. code-block:: console
 
    $ manila show Share
-
    +-----------------------------+---------------------------------------------------------------+
    | Property                    | Value                                                         |
    +-----------------------------+---------------------------------------------------------------+

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

@@ -42,7 +42,6 @@ Create a ``ldap`` security service:
 .. code-block:: console
 
    $ manila security-service-create ldap --dns-ip 8.8.8.8 --server 10.254.0.3 --name my_ldap_security_service
-
    +-------------+--------------------------------------+
    | Property    | Value                                |
    +-------------+--------------------------------------+
@@ -66,7 +65,6 @@ To create ``kerberos`` security service, run:
 .. code-block:: console
 
    $ manila security-service-create kerberos --server 10.254.0.3 --user demo --password secret --name my_kerberos_security_service --description "Kerberos security service"
-
    +-------------+--------------------------------------+
    | Property    | Value                                |
    +-------------+--------------------------------------+
@@ -91,7 +89,6 @@ To see the list of created security service use
 .. code-block:: console
 
    $ manila security-service-list
-
    +--------------------------------------+------------------------------+--------+----------+
    | id                                   | name                         | status | type     |
    +--------------------------------------+------------------------------+--------+----------+
@@ -113,7 +110,6 @@ new attribute ``share_networks`` with associated share network ID.
    $ manila share-network-security-service-add share_net2 my_ldap_security_service
 
    $ manila security-service-show my_ldap_security_service
-
    +----------------+-------------------------------------------+
    | Property       | Value                                     |
    +----------------+-------------------------------------------+
@@ -139,7 +135,6 @@ given share network. List security services for ``share_net2`` share network:
 .. code-block:: console
 
    $ manila share-network-security-service-list share_net2
-
    +--------------------------------------+--------------------------+--------+------+
    | id                                   | name                     | status | type |
    +--------------------------------------+--------------------------+--------+------+
@@ -154,7 +149,6 @@ and see that a security service now has empty list of share networks:
    $ manila share-network-security-service-remove share_net2 my_ldap_security_service
 
    $ manila security-service-show my_ldap_security_service
-
    +----------------+--------------------------------------+
    | Property       | Value                                |
    +----------------+--------------------------------------+

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

@@ -17,7 +17,6 @@ List networks in a tenant, run:
 .. code-block:: console
 
    $ neutron net-list
-
    +--------------+---------+---------------------------------------+
    | id           | name    | subnets                               |
    +--------------+---------+---------------------------------------+
@@ -62,7 +61,6 @@ To create a share network with private network and subnetwork, run:
 .. code-block:: console
 
    $ manila share-network-create --neutron-net-id 5ed5a854-21dc-4ed3-870a-117b7064eb21 --neutron-subnet-id 74dcfb5a-b4d7-4855-86f5-a669729428dc --name my_share_net --description "My first share network"
-
    +-------------------+--------------------------------------+
    | Property          | Value                                |
    +-------------------+--------------------------------------+
@@ -90,7 +88,6 @@ Check network list, run:
 .. code-block:: console
 
    $ manila share-network-list
-
    +--------------------------------------+--------------+
    | id                                   | name         |
    +--------------------------------------+--------------+
@@ -105,7 +102,6 @@ list of networks. This network was created by Generic driver for inner usage.
 .. code-block:: console
 
    $ neutron net-list
-
    +--------------+------------------------+------------------------------------+
    | id           | name                   | subnets                            |
    +--------------+------------------------+------------------------------------+
@@ -122,7 +118,6 @@ You also can see detailed information about the share network including
 .. code-block:: console
 
    $ neutron net-show manila_service_network
-
    +---------------------------+--------------------------------------+
    | Field                     | Value                                |
    +---------------------------+--------------------------------------+

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

@@ -24,7 +24,6 @@ To extend the share and check the result, run:
 
    $ manila extend Share1 2
    $ manila show Share1
-
    +-----------------------------+-------------------------------------------+
    | Property                    | Value                                     |
    +-----------------------------+-------------------------------------------+
@@ -60,7 +59,6 @@ check the result, run:
 
    $ manila shrink Share1 1
    $ manila show Share1
-
    +-----------------------------+-------------------------------------------+
    | Property                    | Value                                     |
    +-----------------------------+-------------------------------------------+

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

@@ -86,7 +86,6 @@ can be public.
    $ manila type-create netapp1 False --is_public True
 
    $ manila type-list
-
    +-----+--------+-----------+-----------+-----------------------------------+-----------------------+
    | ID  | Name   | Visibility| is_default| required_extra_specs              | optional_extra_specs  |
    +-----+--------+-----------+-----------+-----------------------------------+-----------------------+
@@ -108,7 +107,6 @@ extra specifications:
 .. code-block:: console
 
    $ manila extra-specs-list
-
    +-------------+---------+-------------------------------------+
    | ID          | Name    | all_extra_specs                     |
    +-------------+---------+-------------------------------------+
@@ -137,7 +135,6 @@ Create a private type:
 .. code-block:: console
 
    $ manila type-create my_type1 True --is_public False
-
    +-----+---------+-----------+-----------+----------------------------------+----------------------+
    | ID  | Name    | Visibility| is_default| required_extra_specs             | optional_extra_specs |
    +-----+---------+-----------+-----------+----------------------------------+----------------------+
@@ -163,7 +160,6 @@ Get information about access for a private share type ``my_type1``:
 .. code-block:: console
 
    $ manila type-access-list my_type1
-
    +----------------------------------+
    | Project_ID                       |
    +----------------------------------+

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

@@ -22,7 +22,6 @@ Create a snapshot from the share:
 .. code-block:: console
 
    $ manila snapshot-create Share1 --name Snapshot1 --description "Snapshot of Share1"
-
    +-------------+--------------------------------------+
    | Property    | Value                                |
    +-------------+--------------------------------------+
@@ -48,7 +47,6 @@ Check that status of a snapshot is ``available``:
 .. code-block:: console
 
    $ manila snapshot-show Snapshot1
-
    +-------------+--------------------------------------+
    | Property    | Value                                |
    +-------------+--------------------------------------+
@@ -70,7 +68,6 @@ Create a share from a snapshot and check whether it is available:
 .. code-block:: console
 
    $ manila create nfs 1 --name Share2 --metadata source=snapshot --description "Share from a snapshot." --snapshot-id 962e8126-35c3-47bb-8c00-f0ee37f42ddd
-
    +-----------------------------+--------------------------------------+
    | Property                    | Value                                |
    +-----------------------------+--------------------------------------+
@@ -100,7 +97,6 @@ Create a share from a snapshot and check whether it is available:
    +-----------------------------+--------------------------------------+
 
    $ manila show Share2
-
    +-----------------------------+-------------------------------------------+
    | Property                    | Value                                     |
    +-----------------------------+-------------------------------------------+

doc/admin-guide-cloud/source/telemetry-alarms.rst

@@ -231,7 +231,6 @@ brevity):
 .. code-block:: console
 
    $ ceilometer alarm-list
-
    +----------+--------+-------------------+---------------------------------+
    | Alarm ID | Name   | State             | Alarm condition                 |
    +----------+--------+-------------------+---------------------------------+
@@ -292,7 +291,6 @@ via the audit API:
 .. code-block:: console
 
    $ ceilometer alarm-history ALARM_ID
-
    +------------------+-----------+---------------------------------------+
    | Type             | Timestamp | Detail                                |
    +------------------+-----------+---------------------------------------+

doc/admin-guide-cloud/source/telemetry-data-collection.rst

@@ -516,7 +516,6 @@ following command should be invoked:
 
    $ ceilometer sample-create -r 37128ad6-daaa-4d22-9509-b7e1c6b08697 \
      -m memory.usage --meter-type gauge --meter-unit MB --sample-volume 48
-
    +-------------------+--------------------------------------------+
    | Property          | Value                                      |
    +-------------------+--------------------------------------------+

doc/admin-guide-cloud/source/telemetry-data-retrieval.rst

@@ -214,7 +214,6 @@ be used:
 .. code-block:: console
 
     $ ceilometer meter-list
-
     +------------------------+------------+------+------------------------------------------+----------------------------------+----------------------------------+
     | Name                   | Type       | Unit | Resource ID                              | User ID                          | Project ID                       |
     +------------------------+------------+------+------------------------------------------+----------------------------------+----------------------------------+
@@ -261,7 +260,6 @@ VM instance:
 .. code-block:: console
 
     $ ceilometer meter-list --query resource=bb52e52b-1e42-4751-b3ac-45c52d83ba07
-
     +-------------------------+------------+-----------+--------------------------------------+----------------------------------+----------------------------------+
     | Name                    | Type       | Unit      | Resource ID                          | User ID                          | Project ID                       |
     +-------------------------+------------+-----------+--------------------------------------+----------------------------------+----------------------------------+
@@ -291,7 +289,6 @@ the available query types. The request for all the samples of the
 .. code-block:: console
 
    $ ceilometer sample-list --meter cpu
-
    +--------------------------------------+-------+------------+------------+------+---------------------+
    | Resource ID                          | Meter | Type       | Volume     | Unit | Timestamp           |
    +--------------------------------------+-------+------------+------------+------+---------------------+
@@ -315,7 +312,6 @@ collected samples. The following command can be executed to request the
 
    $ ceilometer sample-list --meter cpu --query resource=bb52e52b-1e42-4751-
      b3ac-45c52d83ba07
-
    +--------------------------------------+------+------------+------------+------+---------------------+
    | Resource ID                          | Name | Type       | Volume     | Unit | Timestamp           |
    +--------------------------------------+------+------------+------------+------+---------------------+
@@ -358,7 +354,6 @@ and ``disk.read.bytes`` meters, the following command should be invoked:
    $ ceilometer query-samples --filter '{"and": \
      [{"=":{"resource":"bb52e52b-1e42-4751-b3ac-45c52d83ba07"}},{"or":[{"=":{"counter_name":"cpu"}}, \
      {"=":{"counter_name":"disk.read.bytes"}}]}]}' --orderby '[{"timestamp":"asc"}]' --limit 6
-
    +--------------------------------------+-----------------+------------+------------+------+---------------------+
    | Resource ID                          | Meter           | Type       | Volume     | Unit | Timestamp           |
    +--------------------------------------+-----------------+------------+------------+------+---------------------+
@@ -380,7 +375,6 @@ following command can be executed:
 .. code-block:: console
 
     $ ceilometer event-list
-
     +--------------------------------------+---------------+----------------------------+-----------------------------------------------------------------+
     | Message ID                           | Event Type    | Generated                  | Traits                                                          |
     +--------------------------------------+---------------+----------------------------+-----------------------------------------------------------------+
@@ -421,7 +415,6 @@ retrieve specific events:
 
     $ ceilometer event-list -q 'event_type=compute.instance.exists; \
       instance_type=m1.tiny'
-
     +--------------------------------------+-------------------------+----------------------------+----------------------------------------------------------------------------------+
     | Message ID                           | Event Type              | Generated                  | Traits                                                                           |
     +--------------------------------------+-------------------------+----------------------------+----------------------------------------------------------------------------------+