Browse Source

In-tree Install Guide

The OpenStack install guide team has recommended that projects
that are not part of the starter-kit:compute [1] (and a few other projects
like Cinder and Horizon) maintain their install guide in-tree. [2]

[1] http://governance.openstack.org/reference/tags/starter-kit_compute.html
[2] http://git.openstack.org/cgit/openstack/docs-specs/tree/specs/newton/project-specific-installguides.rst

Change-Id: I2b49fcfd99b3be40bb1ae7d7b8348abdb5b58b90
Co-Authored-By: Denis Cavalcante <dencaval@gmail.com>
Implements: blueprint manila-in-tree-install-guide
Partially-implements: blueprint projectspecificinstallguides
Goutham Pacha Ravi 2 years ago
parent
commit
dfbe3ea418
29 changed files with 1887 additions and 1 deletions
  1. 3
    0
      .gitignore
  2. 71
    0
      install-guide/source/common/controller-node-common-configuration.rst
  3. 208
    0
      install-guide/source/common/controller-node-prerequisites.rst
  4. 98
    0
      install-guide/source/common/dhss-false-mode-configuration.rst
  5. 7
    0
      install-guide/source/common/dhss-false-mode-intro.rst
  6. 84
    0
      install-guide/source/common/dhss-true-mode-configuration.rst
  7. 15
    0
      install-guide/source/common/dhss-true-mode-intro.rst
  8. 77
    0
      install-guide/source/common/share-node-common-configuration.rst
  9. 36
    0
      install-guide/source/common/share-node-share-server-modes.rst
  10. 306
    0
      install-guide/source/conf.py
  11. BIN
      install-guide/source/figures/hwreqs.graffle
  12. BIN
      install-guide/source/figures/hwreqs.png
  13. 3
    0
      install-guide/source/figures/hwreqs.svg
  14. 39
    0
      install-guide/source/get-started-with-shared-file-systems.rst
  15. 46
    0
      install-guide/source/index.rst
  16. 56
    0
      install-guide/source/install-controller-debian.rst
  17. 22
    0
      install-guide/source/install-controller-node.rst
  18. 47
    0
      install-guide/source/install-controller-obs.rst
  19. 57
    0
      install-guide/source/install-controller-rdo.rst
  20. 64
    0
      install-guide/source/install-controller-ubuntu.rst
  21. 91
    0
      install-guide/source/install-share-debian.rst
  22. 21
    0
      install-guide/source/install-share-node.rst
  23. 90
    0
      install-guide/source/install-share-obs.rst
  24. 103
    0
      install-guide/source/install-share-rdo.rst
  25. 99
    0
      install-guide/source/install-share-ubuntu.rst
  26. 14
    0
      install-guide/source/next-steps.rst
  27. 196
    0
      install-guide/source/post-install.rst
  28. 29
    0
      install-guide/source/verify.rst
  29. 5
    1
      tox.ini

+ 3
- 0
.gitignore View File

@@ -39,6 +39,9 @@ api-ref/build
39 39
 # Files created by releasenotes build
40 40
 releasenotes/build
41 41
 
42
+# Files created by install-guide builds
43
+install-guide/build
44
+
42 45
 # Development environment files
43 46
 .project
44 47
 .pydevproject

+ 71
- 0
install-guide/source/common/controller-node-common-configuration.rst View File

@@ -0,0 +1,71 @@
1
+3. Complete the rest of the configuration in ``manila.conf``:
2
+
3
+   * In the ``[DEFAULT]`` and ``[oslo_messaging_rabbit]`` sections, configure
4
+     ``RabbitMQ`` message queue access:
5
+
6
+     .. code-block:: ini
7
+
8
+        [DEFAULT]
9
+        ...
10
+        rpc_backend = rabbit
11
+
12
+        [oslo_messaging_rabbit]
13
+        ...
14
+        rabbit_host = controller
15
+        rabbit_userid = openstack
16
+        rabbit_password = RABBIT_PASS
17
+
18
+     Replace ``RABBIT_PASS`` with the  password you chose for the ``openstack``
19
+     account in ``RabbitMQ``.
20
+
21
+   * In the ``[DEFAULT]`` section, set the following config values:
22
+
23
+     .. code-block:: ini
24
+
25
+        [DEFAULT]
26
+        ...
27
+        default_share_type = default_share_type
28
+        share_name_template = share-%s
29
+        rootwrap_config = /etc/manila/rootwrap.conf
30
+        api_paste_config = /etc/manila/api-paste.ini
31
+
32
+   * In the ``[DEFAULT]`` and ``[keystone_authtoken]`` sections, configure
33
+     Identity service access:
34
+
35
+     .. code-block:: ini
36
+
37
+        [DEFAULT]
38
+        ...
39
+        auth_strategy = keystone
40
+
41
+        [keystone_authtoken]
42
+        ...
43
+        memcached_servers = controller:11211
44
+        auth_uri = http://controller:5000
45
+        auth_url = http://controller:35357
46
+        auth_type = password
47
+        project_domain_id = default
48
+        user_domain_id = default
49
+        project_name = service
50
+        username = manila
51
+        password = MANILA_PASS
52
+
53
+     Replace ``MANILA_PASS`` with the password you chose for the ``manila``
54
+     user in the Identity service.
55
+
56
+   * In the ``[DEFAULT]`` section, configure the ``my_ip`` option to use the
57
+     management interface IP address of the controller node:
58
+
59
+     .. code-block:: ini
60
+
61
+        [DEFAULT]
62
+        ...
63
+        my_ip = 10.0.0.11
64
+
65
+   * In the ``[oslo_concurrency]`` section, configure the lock path:
66
+
67
+     .. code-block:: ini
68
+
69
+        [oslo_concurrency]
70
+        ...
71
+        lock_path = /var/lock/manila

+ 208
- 0
install-guide/source/common/controller-node-prerequisites.rst View File

@@ -0,0 +1,208 @@
1
+Prerequisites
2
+-------------
3
+
4
+Before you install and configure the Shared File Systems service, you
5
+must create a database, service credentials, and `API endpoints`.
6
+
7
+#. To create the database, complete these steps:
8
+
9
+   * Use the database access client to connect to the database server as the
10
+     ``root`` user:
11
+
12
+     .. code-block:: console
13
+
14
+        $ mysql -u root -p
15
+
16
+   * Create the `manila` database:
17
+
18
+     .. code-block:: console
19
+
20
+        CREATE DATABASE manila;
21
+
22
+   * Grant proper access to the ``manila`` database:
23
+
24
+     .. code-block:: console
25
+
26
+        GRANT ALL PRIVILEGES ON manila.* TO 'manila'@'localhost' \
27
+          IDENTIFIED BY 'MANILA_DBPASS';
28
+        GRANT ALL PRIVILEGES ON manila.* TO 'manila'@'%' \
29
+          IDENTIFIED BY 'MANILA_DBPASS';
30
+
31
+     Replace ``MANILA_DBPASS`` with a suitable password.
32
+
33
+   * Exit the database access client.
34
+
35
+#. Source the ``admin`` credentials to gain access to admin CLI commands:
36
+
37
+   .. code-block:: console
38
+
39
+      $ . admin-openrc.sh
40
+
41
+#. To create the service credentials, complete these steps:
42
+
43
+   * Create a ``manila`` user:
44
+
45
+     .. code-block:: console
46
+
47
+        $ openstack user create --domain default --password-prompt manila
48
+        User Password:
49
+        Repeat User Password:
50
+        +-----------+----------------------------------+
51
+        | Field     | Value                            |
52
+        +-----------+----------------------------------+
53
+        | domain_id | e0353a670a9e496da891347c589539e9 |
54
+        | enabled   | True                             |
55
+        | id        | 83a3990fc2144100ba0e2e23886d8acc |
56
+        | name      | manila                           |
57
+        +-----------+----------------------------------+
58
+
59
+   * Add the ``admin`` role to the ``manila`` user:
60
+
61
+     .. code-block:: console
62
+
63
+        $ openstack role add --project service --user manila admin
64
+
65
+     .. note::
66
+
67
+        This command provides no output.
68
+
69
+   * Create the ``manila`` and ``manilav2`` service entities:
70
+
71
+     .. code-block:: console
72
+
73
+        $ openstack service create --name manila \
74
+          --description "OpenStack Shared File Systems" share
75
+          +-------------+----------------------------------+
76
+          | Field       | Value                            |
77
+          +-------------+----------------------------------+
78
+          | description | OpenStack Shared File Systems    |
79
+          | enabled     | True                             |
80
+          | id          | 82378b5a16b340aa9cc790cdd46a03ba |
81
+          | name        | manila                           |
82
+          | type        | share                            |
83
+          +-------------+----------------------------------+
84
+
85
+     .. code-block:: console
86
+
87
+        $ openstack service create --name manilav2 \
88
+          --description "OpenStack Shared File Systems" sharev2
89
+          +-------------+----------------------------------+
90
+          | Field       | Value                            |
91
+          +-------------+----------------------------------+
92
+          | description | OpenStack Shared File Systems    |
93
+          | enabled     | True                             |
94
+          | id          | 30d92a97a81a4e5d8fd97a32bafd7b88 |
95
+          | name        | manilav2                         |
96
+          | type        | sharev2                          |
97
+          +-------------+----------------------------------+
98
+
99
+     .. note::
100
+
101
+        The Shared File Systems services require two service entities.
102
+
103
+#. Create the Shared File Systems service API endpoints:
104
+
105
+   .. code-block:: console
106
+
107
+      $ openstack endpoint create --region RegionOne \
108
+        share public http://controller:8786/v1/%\(tenant_id\)s
109
+        +--------------+-----------------------------------------+
110
+        | Field        | Value                                   |
111
+        +--------------+-----------------------------------------+
112
+        | enabled      | True                                    |
113
+        | id           | 0bd2bbf8d28b433aaea56a254c69f69d        |
114
+        | interface    | public                                  |
115
+        | region       | RegionOne                               |
116
+        | region_id    | RegionOne                               |
117
+        | service_id   | 82378b5a16b340aa9cc790cdd46a03ba        |
118
+        | service_name | manila                                  |
119
+        | service_type | share                                   |
120
+        | url          | http://controller:8786/v1/%(tenant_id)s |
121
+        +--------------+-----------------------------------------+
122
+
123
+      $ openstack endpoint create --region RegionOne \
124
+        share internal http://controller:8786/v1/%\(tenant_id\)s
125
+        +--------------+-----------------------------------------+
126
+        | Field        | Value                                   |
127
+        +--------------+-----------------------------------------+
128
+        | enabled      | True                                    |
129
+        | id           | a2859b5732cc48b5b083dd36dafb6fd9        |
130
+        | interface    | internal                                |
131
+        | region       | RegionOne                               |
132
+        | region_id    | RegionOne                               |
133
+        | service_id   | 82378b5a16b340aa9cc790cdd46a03ba        |
134
+        | service_name | manila                                  |
135
+        | service_type | share                                   |
136
+        | url          | http://controller:8786/v1/%(tenant_id)s |
137
+        +--------------+-----------------------------------------+
138
+
139
+      $ openstack endpoint create --region RegionOne \
140
+        share admin http://controller:8786/v1/%\(tenant_id\)s
141
+        +--------------+-----------------------------------------+
142
+        | Field        | Value                                   |
143
+        +--------------+-----------------------------------------+
144
+        | enabled      | True                                    |
145
+        | id           | f7f46df93a374cc49c0121bef41da03c        |
146
+        | interface    | admin                                   |
147
+        | region       | RegionOne                               |
148
+        | region_id    | RegionOne                               |
149
+        | service_id   | 82378b5a16b340aa9cc790cdd46a03ba        |
150
+        | service_name | manila                                  |
151
+        | service_type | share                                   |
152
+        | url          | http://controller:8786/v1/%(tenant_id)s |
153
+        +--------------+-----------------------------------------+
154
+
155
+   .. code-block:: console
156
+
157
+      $ openstack endpoint create --region RegionOne \
158
+        sharev2 public http://controller:8786/v2/%\(tenant_id\)s
159
+        +--------------+-----------------------------------------+
160
+        | Field        | Value                                   |
161
+        +--------------+-----------------------------------------+
162
+        | enabled      | True                                    |
163
+        | id           | d63cc0d358da4ea680178657291eddc1        |
164
+        | interface    | public                                  |
165
+        | region       | RegionOne                               |
166
+        | region_id    | RegionOne                               |
167
+        | service_id   | 30d92a97a81a4e5d8fd97a32bafd7b88        |
168
+        | service_name | manilav2                                |
169
+        | service_type | sharev2                                 |
170
+        | url          | http://controller:8786/v2/%(tenant_id)s |
171
+        +--------------+-----------------------------------------+
172
+
173
+      $ openstack endpoint create --region RegionOne \
174
+        sharev2 internal http://controller:8786/v2/%\(tenant_id\)s
175
+        +--------------+-----------------------------------------+
176
+        | Field        | Value                                   |
177
+        +--------------+-----------------------------------------+
178
+        | enabled      | True                                    |
179
+        | id           | afc86e5f50804008add349dba605da54        |
180
+        | interface    | internal                                |
181
+        | region       | RegionOne                               |
182
+        | region_id    | RegionOne                               |
183
+        | service_id   | 30d92a97a81a4e5d8fd97a32bafd7b88        |
184
+        | service_name | manilav2                                |
185
+        | service_type | sharev2                                 |
186
+        | url          | http://controller:8786/v2/%(tenant_id)s |
187
+        +--------------+-----------------------------------------+
188
+
189
+      $ openstack endpoint create --region RegionOne \
190
+        sharev2 admin http://controller:8786/v2/%\(tenant_id\)s
191
+        +--------------+-----------------------------------------+
192
+        | Field        | Value                                   |
193
+        +--------------+-----------------------------------------+
194
+        | enabled      | True                                    |
195
+        | id           | e814a0cec40546e98cf0c25a82498483        |
196
+        | interface    | admin                                   |
197
+        | region       | RegionOne                               |
198
+        | region_id    | RegionOne                               |
199
+        | service_id   | 30d92a97a81a4e5d8fd97a32bafd7b88        |
200
+        | service_name | manilav2                                |
201
+        | service_type | sharev2                                 |
202
+        | url          | http://controller:8786/v2/%(tenant_id)s |
203
+        +--------------+-----------------------------------------+
204
+
205
+   .. note::
206
+
207
+      The Shared File Systems services require endpoints for each service
208
+      entity.

+ 98
- 0
install-guide/source/common/dhss-false-mode-configuration.rst View File

@@ -0,0 +1,98 @@
1
+2. Create the LVM physical volume ``/dev/sdc``:
2
+
3
+   .. code-block:: console
4
+
5
+      # pvcreate /dev/sdc
6
+      Physical volume "/dev/sdc" successfully created
7
+
8
+#. Create the LVM volume group ``manila-volumes``:
9
+
10
+   .. code-block:: console
11
+
12
+      # vgcreate manila-volumes /dev/sdc
13
+      Volume group "manila-volumes" successfully created
14
+
15
+   The Shared File Systems service creates logical volumes in this volume
16
+   group.
17
+
18
+#. Only instances can access Shared File Systems service volumes. However,
19
+   the underlying operating system manages the devices associated with
20
+   the volumes. By default, the LVM volume scanning tool scans the
21
+   ``/dev`` directory for block storage devices that
22
+   contain volumes. If projects use LVM on their volumes, the scanning
23
+   tool detects these volumes and attempts to cache them which can cause
24
+   a variety of problems with both the underlying operating system
25
+   and project volumes. You must reconfigure LVM to scan only the devices
26
+   that contain the ``cinder-volume`` and ``manila-volumes`` volume groups.
27
+   Edit the ``/etc/lvm/lvm.conf`` file and complete the following actions:
28
+
29
+   * In the ``devices`` section, add a filter that accepts the
30
+     ``/dev/sdb`` and ``/dev/sdc`` devices and rejects all other devices:
31
+
32
+     .. code-block:: ini
33
+
34
+        devices {
35
+        ...
36
+        filter = [ "a/sdb/", "a/sdc", "r/.*/"]
37
+
38
+     .. warning::
39
+
40
+        If your storage nodes use LVM on the operating system disk, you
41
+        must also add the associated device to the filter. For example,
42
+        if the ``/dev/sda`` device contains the operating system:
43
+
44
+        .. code-block:: ini
45
+
46
+           filter = [ "a/sda/", "a/sdb/", "a/sdc", "r/.*/"]
47
+
48
+        Similarly, if your compute nodes use LVM on the operating
49
+        system disk, you must also modify the filter in the
50
+        ``/etc/lvm/lvm.conf`` file on those nodes to include only
51
+        the operating system disk. For example, if the ``/dev/sda``
52
+        device contains the operating system:
53
+
54
+        .. code-block:: ini
55
+
56
+           filter = [ "a/sda/", "r/.*/"]
57
+
58
+Configure components
59
+--------------------
60
+
61
+#. Edit the ``/etc/manila/manila.conf`` file and complete the following
62
+   actions:
63
+
64
+   * In the ``[DEFAULT]`` section, enable the LVM driver and the NFS/CIFS
65
+     protocols:
66
+
67
+     .. code-block:: ini
68
+
69
+        [DEFAULT]
70
+        ...
71
+        enabled_share_backends = lvm
72
+        enabled_share_protocols = NFS,CIFS
73
+
74
+     .. note::
75
+
76
+        Back end names are arbitrary. As an example, this guide uses the name
77
+        of the driver.
78
+
79
+   * In the ``[lvm]`` section, configure the LVM driver:
80
+
81
+     .. code-block:: ini
82
+
83
+        [lvm]
84
+        share_backend_name = LVM
85
+        share_driver = manila.share.drivers.lvm.LVMShareDriver
86
+        driver_handles_share_servers = False
87
+        lvm_share_volume_group = manila-volumes
88
+        lvm_share_export_ip = MANAGEMENT_INTERFACE_IP_ADDRESS
89
+
90
+     Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address
91
+     of the management network interface on your storage node,
92
+     typically 10.0.0.41 for the first node in the the example architecture
93
+     shown below:
94
+
95
+     .. figure:: figures/hwreqs.png
96
+        :alt: Hardware requirements
97
+
98
+        **Hardware requirements**.

+ 7
- 0
install-guide/source/common/dhss-false-mode-intro.rst View File

@@ -0,0 +1,7 @@
1
+Shared File Systems Option 1: No driver support for share servers management
2
+----------------------------------------------------------------------------
3
+For simplicity, this configuration references the same storage node
4
+configuration for the Block Storage service. However, the LVM driver
5
+requires a separate empty local block storage device to avoid conflict
6
+with the Block Storage service. The instructions use ``/dev/sdc``, but
7
+you can substitute a different value for your particular node.

+ 84
- 0
install-guide/source/common/dhss-true-mode-configuration.rst View File

@@ -0,0 +1,84 @@
1
+Configure components
2
+--------------------
3
+
4
+#. Edit the ``/etc/manila/manila.conf`` file and complete the following
5
+   actions:
6
+
7
+   * In the ``[DEFAULT]`` section, enable the generic driver and the NFS/CIFS
8
+     protocols:
9
+
10
+     .. code-block:: ini
11
+
12
+        [DEFAULT]
13
+        ...
14
+        enabled_share_backends = generic
15
+        enabled_share_protocols = NFS,CIFS
16
+
17
+     .. note::
18
+
19
+        Back end names are arbitrary. As an example, this guide uses the name
20
+        of the driver.
21
+
22
+   * In the ``[neutron]``, ``[nova]``, and ``[cinder]`` sections, enable
23
+     authentication for those services:
24
+
25
+     .. code-block:: ini
26
+
27
+        [neutron]
28
+        ...
29
+        url = http://controller:9696
30
+        auth_uri = http://controller:5000
31
+        auth_url = http://controller:35357
32
+        memcached_servers = controller:11211
33
+        auth_type = password
34
+        project_domain_name = default
35
+        user_domain_name = default
36
+        region_name = RegionOne
37
+        project_name = service
38
+        username = neutron
39
+        password = NEUTRON_PASS
40
+
41
+        [nova]
42
+        ...
43
+        auth_uri = http://controller:5000
44
+        auth_url = http://controller:35357
45
+        memcached_servers = controller:11211
46
+        auth_type = password
47
+        project_domain_name = default
48
+        user_domain_name = default
49
+        region_name = RegionOne
50
+        project_name = service
51
+        username = nova
52
+        password = NOVA_PASS
53
+
54
+        [cinder]
55
+        ...
56
+        auth_uri = http://controller:5000
57
+        auth_url = http://controller:35357
58
+        memcached_servers = controller:11211
59
+        auth_type = password
60
+        project_domain_name = default
61
+        user_domain_name = default
62
+        region_name = RegionOne
63
+        project_name = service
64
+        username = cinder
65
+        password = CINDER_PASS
66
+
67
+   * In the ``[generic]`` section, configure the generic driver:
68
+
69
+     .. code-block:: ini
70
+
71
+        [generic]
72
+        share_backend_name = GENERIC
73
+        share_driver = manila.share.drivers.generic.GenericShareDriver
74
+        driver_handles_share_servers = True
75
+        service_instance_flavor_id = 100
76
+        service_image_name = manila-service-image
77
+        service_instance_user = manila
78
+        service_instance_password = manila
79
+        interface_driver = manila.network.linux.interface.BridgeInterfaceDriver
80
+
81
+     .. note::
82
+
83
+        You can also use SSH keys instead of password authentication for
84
+        service instance credentials.

+ 15
- 0
install-guide/source/common/dhss-true-mode-intro.rst View File

@@ -0,0 +1,15 @@
1
+Shared File Systems Option 2: Driver support for share servers management
2
+-------------------------------------------------------------------------
3
+
4
+For simplicity, this configuration references the same storage node
5
+configuration for the Block Storage service.
6
+
7
+.. note::
8
+
9
+   This guide describes how to configure the Shared File Systems service to
10
+   use the ``generic`` driver with the driver handles share server mode
11
+   (DHSS) enabled. This mode requires Compute (nova), Networking (neutron) and
12
+   Block storage (cinder) services for managing share servers. The information
13
+   used for creating share servers is configured as share networks. Generic
14
+   driver with DHSS enabled also requires network to be attached to a public
15
+   router.

+ 77
- 0
install-guide/source/common/share-node-common-configuration.rst View File

@@ -0,0 +1,77 @@
1
+4. Complete the rest of the configuration in ``manila.conf``.
2
+
3
+   * In the ``[DEFAULT]`` and ``[oslo_messaging_rabbit]`` sections,
4
+     configure ``RabbitMQ`` message queue access:
5
+
6
+     .. code-block:: ini
7
+
8
+        [DEFAULT]
9
+        ...
10
+        rpc_backend = rabbit
11
+
12
+        [oslo_messaging_rabbit]
13
+        ...
14
+        rabbit_host = controller
15
+        rabbit_userid = openstack
16
+        rabbit_password = RABBIT_PASS
17
+
18
+     Replace ``RABBIT_PASS`` with the password you chose for the
19
+     ``openstack`` account in ``RabbitMQ``.
20
+
21
+   * In the ``[DEFAULT]`` section, set the following config values:
22
+
23
+     .. code-block:: ini
24
+
25
+        [DEFAULT]
26
+        ...
27
+        default_share_type = default_share_type
28
+        rootwrap_config = /etc/manila/rootwrap.conf
29
+
30
+   * In the ``[DEFAULT]`` and ``[keystone_authtoken]`` sections, configure
31
+     Identity service access:
32
+
33
+     .. code-block:: ini
34
+
35
+        [DEFAULT]
36
+        ...
37
+        auth_strategy = keystone
38
+
39
+        [keystone_authtoken]
40
+        ...
41
+        memcached_servers = controller:11211
42
+        auth_uri = http://controller:5000
43
+        auth_url = http://controller:35357
44
+        auth_type = password
45
+        project_domain_id = default
46
+        user_domain_id = default
47
+        project_name = service
48
+        username = manila
49
+        password = MANILA_PASS
50
+
51
+     Replace ``MANILA_PASS`` with the password you chose for the ``manila``
52
+     user in the Identity service.
53
+
54
+   * In the ``[DEFAULT]`` section, configure the ``my_ip`` option:
55
+
56
+     .. code-block:: ini
57
+
58
+        [DEFAULT]
59
+        ...
60
+        my_ip = MANAGEMENT_INTERFACE_IP_ADDRESS
61
+
62
+     Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the
63
+     management network interface on your share node, typically 10.0.0.41 for
64
+     the first node in the example architecture shown below:
65
+
66
+     .. figure:: figures/hwreqs.png
67
+        :alt: Hardware requirements
68
+
69
+        **Hardware requirements**
70
+
71
+   * In the ``[oslo_concurrency]`` section, configure the lock path:
72
+
73
+     .. code-block:: ini
74
+
75
+        [oslo_concurrency]
76
+        ...
77
+        lock_path = /var/lib/manila/tmp

+ 36
- 0
install-guide/source/common/share-node-share-server-modes.rst View File

@@ -0,0 +1,36 @@
1
+The share node can support two modes, with and without the handling of
2
+share servers. The mode depends on driver support.
3
+
4
+Option 1
5
+--------
6
+Deploying the service without driver support for share management.
7
+In this mode, the service does not do anything related to networking. The
8
+operator must ensure network connectivity between instances and the NFS
9
+server. This tutorial demonstrates setting up the LVM driver to support this
10
+driver mode. It requires LVM and NFS packages as well as an additional disk
11
+for the ``manila-share`` LVM volume group. This driver
12
+mode may be referred to as ``driver_handles_share_servers = False`` mode, or
13
+simply ``DHSS=False`` mode.
14
+
15
+Option 2
16
+--------
17
+Deploying the service with driver support for share management. In
18
+this mode, the service runs with a back end driver that creates and manages
19
+share servers. This tutorial demonstrates setting up the Generic driver.
20
+This driver requires Compute (nova), Networking (neutron) and Block
21
+storage (cinder) services for managing share servers. The information used for
22
+creating share servers is configured with the help of share networks. This
23
+option uses the generic driver with the handling of share servers capacity
24
+and requires attaching the ``selfservice`` network to a router. This driver
25
+mode may be referred to as ``driver_handles_share_servers = True`` mode, or
26
+simply ``DHSS=True`` mode.
27
+
28
+.. warning::
29
+
30
+   When running the generic driver in ``DHSS=True`` driver mode, the share
31
+   service should be run on the same node as the networking service.
32
+   However, such a service may not be able to run the LVM driver that runs
33
+   in ``DHSS=False`` driver mode effectively, due to a bug in some
34
+   distributions of Linux. For more information, see LVM Driver section in the
35
+   `Configuration Reference Guide
36
+   <http://docs.openstack.org/mitaka/config-reference/shared-file-systems.html>`_.

+ 306
- 0
install-guide/source/conf.py View File

@@ -0,0 +1,306 @@
1
+# Licensed under the Apache License, Version 2.0 (the "License");
2
+# you may not use this file except in compliance with the License.
3
+# You may obtain a copy of the License at
4
+#
5
+#    http://www.apache.org/licenses/LICENSE-2.0
6
+#
7
+# Unless required by applicable law or agreed to in writing, software
8
+# distributed under the License is distributed on an "AS IS" BASIS,
9
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
10
+# implied.
11
+# See the License for the specific language governing permissions and
12
+# limitations under the License.
13
+
14
+# This file is execfile()d with the current directory set to its
15
+# containing dir.
16
+#
17
+# Note that not all possible configuration values are present in this
18
+# autogenerated file.
19
+#
20
+# All configuration values have a default; values that are commented out
21
+# serve to show the default.
22
+
23
+import os
24
+
25
+
26
+import openstackdocstheme
27
+
28
+# If extensions (or modules to document with autodoc) are in another directory,
29
+# add these directories to sys.path here. If the directory is relative to the
30
+# documentation root, use os.path.abspath to make it absolute, like shown here.
31
+# sys.path.insert(0, os.path.abspath('.'))
32
+
33
+# -- General configuration ------------------------------------------------
34
+
35
+# If your documentation needs a minimal Sphinx version, state it here.
36
+# needs_sphinx = '1.0'
37
+
38
+# Add any Sphinx extension module names here, as strings. They can be
39
+# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
40
+# ones.
41
+# TODO(ajaeger): enable PDF building, for example add 'rst2pdf.pdfbuilder'
42
+# extensions =
43
+
44
+# Add any paths that contain templates here, relative to this directory.
45
+# templates_path = ['_templates']
46
+
47
+# The suffix of source filenames.
48
+source_suffix = '.rst'
49
+
50
+# The encoding of source files.
51
+# source_encoding = 'utf-8-sig'
52
+
53
+# The master toctree document.
54
+master_doc = 'index'
55
+
56
+# General information about the project.
57
+project = u'Installation Guide for Shared File Systems Service'
58
+bug_tag = u'install-guide'
59
+copyright = u'2016, OpenStack contributors'
60
+
61
+# The version info for the project you're documenting, acts as replacement for
62
+# |version| and |release|, also used in various other places throughout the
63
+# built documents.
64
+#
65
+# The short X.Y version.
66
+version = '0.1'
67
+# The full version, including alpha/beta/rc tags.
68
+release = '0.1'
69
+
70
+# A few variables have to be set for the log-a-bug feature.
71
+#   giturl: The location of conf.py on Git. Must be set manually.
72
+#   gitsha: The SHA checksum of the bug description. Automatically
73
+#           extracted from git log.
74
+#   bug_tag: Tag for categorizing the bug. Must be set manually.
75
+# These variables are passed to the logabug code via html_context.
76
+giturl = u'http://git.openstack.org/cgit/openstack/manila/tree/install-guide/source'
77
+git_cmd = "/usr/bin/git log | head -n1 | cut -f2 -d' '"
78
+gitsha = os.popen(git_cmd).read().strip('\n')
79
+# source tree
80
+pwd = os.getcwd()
81
+html_context = {
82
+    "pwd": pwd,
83
+    "gitsha": gitsha,
84
+    "bug_tag": bug_tag,
85
+    "giturl": giturl,
86
+    "bug_project": "manila",
87
+}
88
+
89
+# The language for content autogenerated by Sphinx. Refer to documentation
90
+# for a list of supported languages.
91
+# language = None
92
+
93
+# There are two options for replacing |today|: either, you set today to some
94
+# non-false value, then it is used:
95
+# today = ''
96
+# Else, today_fmt is used as the format for a strftime call.
97
+# today_fmt = '%B %d, %Y'
98
+
99
+# List of patterns, relative to source directory, that match files and
100
+# directories to ignore when looking for source files.
101
+exclude_patterns = ["common/*.rst"]
102
+
103
+# The reST default role (used for this markup: `text`) to use for all
104
+# documents.
105
+# default_role = None
106
+
107
+# If true, '()' will be appended to :func: etc. cross-reference text.
108
+# add_function_parentheses = True
109
+
110
+# If true, the current module name will be prepended to all description
111
+# unit titles (such as .. function::).
112
+# add_module_names = True
113
+
114
+# If true, sectionauthor and moduleauthor directives will be shown in the
115
+# output. They are ignored by default.
116
+# show_authors = False
117
+
118
+# The name of the Pygments (syntax highlighting) style to use.
119
+pygments_style = 'sphinx'
120
+
121
+# A list of ignored prefixes for module index sorting.
122
+# modindex_common_prefix = []
123
+
124
+# If true, keep warnings as "system message" paragraphs in the built documents.
125
+# keep_warnings = False
126
+
127
+
128
+# -- Options for HTML output ----------------------------------------------
129
+
130
+# The theme to use for HTML and HTML Help pages.  See the documentation for
131
+# a list of builtin themes.
132
+html_theme = 'openstackdocs'
133
+
134
+# Theme options are theme-specific and customize the look and feel of a theme
135
+# further.  For a list of options available for each theme, see the
136
+# documentation.
137
+# html_theme_options = {}
138
+
139
+# Add any paths that contain custom themes here, relative to this directory.
140
+html_theme_path = [openstackdocstheme.get_html_theme_path()]
141
+
142
+# The name for this set of Sphinx documents.  If None, it defaults to
143
+# "<project> v<release> documentation".
144
+# html_title = None
145
+
146
+# A shorter title for the navigation bar.  Default is the same as html_title.
147
+# html_short_title = None
148
+
149
+# The name of an image file (relative to this directory) to place at the top
150
+# of the sidebar.
151
+# html_logo = None
152
+
153
+# The name of an image file (within the static path) to use as favicon of the
154
+# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
155
+# pixels large.
156
+# html_favicon = None
157
+
158
+# Add any paths that contain custom static files (such as style sheets) here,
159
+# relative to this directory. They are copied after the builtin static files,
160
+# so a file named "default.css" will overwrite the builtin "default.css".
161
+# html_static_path = []
162
+
163
+# Add any extra paths that contain custom files (such as robots.txt or
164
+# .htaccess) here, relative to this directory. These files are copied
165
+# directly to the root of the documentation.
166
+# html_extra_path = []
167
+
168
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
169
+# using the given strftime format.
170
+# So that we can enable "log-a-bug" links from each output HTML page, this
171
+# variable must be set to a format that includes year, month, day, hours and
172
+# minutes.
173
+html_last_updated_fmt = '%Y-%m-%d %H:%M'
174
+
175
+
176
+# If true, SmartyPants will be used to convert quotes and dashes to
177
+# typographically correct entities.
178
+# html_use_smartypants = True
179
+
180
+# Custom sidebar templates, maps document names to template names.
181
+# html_sidebars = {}
182
+
183
+# Additional templates that should be rendered to pages, maps page names to
184
+# template names.
185
+# html_additional_pages = {}
186
+
187
+# If false, no module index is generated.
188
+# html_domain_indices = True
189
+
190
+# If false, no index is generated.
191
+html_use_index = False
192
+
193
+# If true, the index is split into individual pages for each letter.
194
+# html_split_index = False
195
+
196
+# If true, links to the reST sources are added to the pages.
197
+html_show_sourcelink = False
198
+
199
+# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
200
+# html_show_sphinx = True
201
+
202
+# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
203
+# html_show_copyright = True
204
+
205
+# If true, an OpenSearch description file will be output, and all pages will
206
+# contain a <link> tag referring to it.  The value of this option must be the
207
+# base URL from which the finished HTML is served.
208
+# html_use_opensearch = ''
209
+
210
+# This is the file name suffix for HTML files (e.g. ".xhtml").
211
+# html_file_suffix = None
212
+
213
+# Output file base name for HTML help builder.
214
+htmlhelp_basename = 'install-guide'
215
+
216
+# If true, publish source files
217
+html_copy_source = False
218
+
219
+# -- Options for LaTeX output ---------------------------------------------
220
+
221
+latex_elements = {
222
+    # The paper size ('letterpaper' or 'a4paper').
223
+    # 'papersize': 'letterpaper',
224
+
225
+    # The font size ('10pt', '11pt' or '12pt').
226
+    # 'pointsize': '10pt',
227
+
228
+    # Additional stuff for the LaTeX preamble.
229
+    # 'preamble': '',
230
+}
231
+
232
+# Grouping the document tree into LaTeX files. List of tuples
233
+# (source start file, target name, title,
234
+#  author, documentclass [howto, manual, or own class]).
235
+latex_documents = [
236
+    ('index', 'InstallGuide.tex', u'Install Guide',
237
+     u'OpenStack contributors', 'manual'),
238
+]
239
+
240
+# The name of an image file (relative to this directory) to place at the top of
241
+# the title page.
242
+# latex_logo = None
243
+
244
+# For "manual" documents, if this is true, then toplevel headings are parts,
245
+# not chapters.
246
+# latex_use_parts = False
247
+
248
+# If true, show page references after internal links.
249
+# latex_show_pagerefs = False
250
+
251
+# If true, show URL addresses after external links.
252
+# latex_show_urls = False
253
+
254
+# Documents to append as an appendix to all manuals.
255
+# latex_appendices = []
256
+
257
+# If false, no module index is generated.
258
+# latex_domain_indices = True
259
+
260
+
261
+# -- Options for manual page output ---------------------------------------
262
+
263
+# One entry per manual page. List of tuples
264
+# (source start file, name, description, authors, manual section).
265
+man_pages = [
266
+    ('index', 'installguide', u'Install Guide',
267
+     [u'OpenStack contributors'], 1)
268
+]
269
+
270
+# If true, show URL addresses after external links.
271
+# man_show_urls = False
272
+
273
+
274
+# -- Options for Texinfo output -------------------------------------------
275
+
276
+# Grouping the document tree into Texinfo files. List of tuples
277
+# (source start file, target name, title, author,
278
+#  dir menu entry, description, category)
279
+texinfo_documents = [
280
+    ('index', 'InstallGuide', u'Install Guide',
281
+     u'OpenStack contributors', 'InstallGuide',
282
+     'This guide shows OpenStack end users how to install '
283
+     'an OpenStack cloud.', 'Miscellaneous'),
284
+]
285
+
286
+# Documents to append as an appendix to all manuals.
287
+# texinfo_appendices = []
288
+
289
+# If false, no module index is generated.
290
+# texinfo_domain_indices = True
291
+
292
+# How to display URL addresses: 'footnote', 'no', or 'inline'.
293
+# texinfo_show_urls = 'footnote'
294
+
295
+# If true, do not generate a @detailmenu in the "Top" node's menu.
296
+# texinfo_no_detailmenu = False
297
+
298
+# -- Options for Internationalization output ------------------------------
299
+locale_dirs = ['locale/']
300
+
301
+# -- Options for PDF output --------------------------------------------------
302
+
303
+pdf_documents = [
304
+    ('index', u'InstallGuide', u'Install Guide',
305
+     u'OpenStack contributors')
306
+]

BIN
install-guide/source/figures/hwreqs.graffle View File


BIN
install-guide/source/figures/hwreqs.png View File


+ 3
- 0
install-guide/source/figures/hwreqs.svg
File diff suppressed because it is too large
View File


+ 39
- 0
install-guide/source/get-started-with-shared-file-systems.rst View File

@@ -0,0 +1,39 @@
1
+====================================
2
+Shared File Systems service overview
3
+====================================
4
+
5
+The OpenStack Shared File Systems service (manila) provides file storage to a
6
+virtual machine. The Shared File Systems service provides an infrastructure
7
+for managing and provisioning of file shares. The service also enables
8
+management of share types as well as share snapshots if a driver supports
9
+them.
10
+
11
+The Shared File Systems service consists of the following components:
12
+
13
+manila-api
14
+  A WSGI app that authenticates and routes requests throughout the Shared File
15
+  Systems service. It supports the OpenStack APIs.
16
+
17
+manila-data
18
+  A standalone service whose purpose is to receive requests, process data
19
+  operations such as copying, share migration or backup, and send back a
20
+  response after an operation has been completed.
21
+
22
+manila-scheduler
23
+  Schedules and routes requests to the appropriate share service. The
24
+  scheduler uses configurable filters and weighers to route requests. The
25
+  Filter Scheduler is the default and enables filters on things like Capacity,
26
+  Availability Zone, Share Types, and Capabilities as well as custom filters.
27
+
28
+manila-share
29
+  Manages back-end devices that provide shared file systems. A manila-share
30
+  process can run in one of two modes, with or without handling of share
31
+  servers. Share servers export file shares via share networks. When share
32
+  servers are not used, the networking requirements are handled outside of
33
+  Manila.
34
+
35
+Messaging queue
36
+  Routes information between the Shared File Systems processes.
37
+
38
+For more information, see `Configuration Reference Guide
39
+<http://docs.openstack.org/mitaka/config-reference/shared-file-systems.html>`_.

+ 46
- 0
install-guide/source/index.rst View File

@@ -0,0 +1,46 @@
1
+=========================================
2
+Shared File Systems Installation Tutorial
3
+=========================================
4
+
5
+.. toctree::
6
+   :maxdepth: 2
7
+
8
+   get-started-with-shared-file-systems.rst
9
+   install-controller-node.rst
10
+   install-share-node.rst
11
+   verify.rst
12
+   post-install.rst
13
+   next-steps.rst
14
+
15
+
16
+The OpenStack Shared File Systems service (manila) provides coordinated
17
+access to shared or distributed file systems. The method in which the share is
18
+provisioned and consumed is determined by the Shared File Systems driver, or
19
+drivers in the case of a multi-backend configuration. There are a variety of
20
+drivers that support NFS, CIFS, HDFS, GlusterFS, CEPHFS and other protocols
21
+as well.
22
+
23
+The Shared File Systems API and scheduler services typically run on the
24
+controller nodes. Depending upon the drivers used, the share service can run
25
+on controllers, compute nodes, or storage nodes.
26
+
27
+.. important::
28
+
29
+    For simplicity, this guide describes configuring the Shared File Systems
30
+    service to use the ``generic`` back end with the driver handles
31
+    share server mode (DHSS) enabled that uses the `Compute service`
32
+    (`nova`), `Networking service` (`neutron`) and `Block storage service`
33
+    (`cinder`).
34
+
35
+    Networking service configuration requires the capability of networks being
36
+    attached to a public router in order to create share networks.
37
+
38
+    Before you proceed, ensure that Compute, Networking and Block storage
39
+    services are properly working. For networking service, ensure that option
40
+    2 is properly configured.
41
+
42
+For more information, see the `Configuration Reference
43
+<http://docs.openstack.org/mitaka/config-reference/shared-file-systems.html>`_.
44
+
45
+This chapter assumes a working setup of OpenStack following the `OpenStack
46
+Installation Tutorial <http://docs.openstack.org/#install-guides>`_

+ 56
- 0
install-guide/source/install-controller-debian.rst View File

@@ -0,0 +1,56 @@
1
+.. _manila-controller-debian:
2
+
3
+Install and configure controller node on Debian
4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5
+
6
+This section describes how to install and configure the Shared File Systems
7
+service, code-named manila, on the controller node that runs a Debian
8
+distribution. This service requires at least one additional share node that
9
+manages file storage back ends.
10
+
11
+.. include:: common/controller-node-prerequisites.rst
12
+
13
+Install and configure components
14
+--------------------------------
15
+
16
+#. Install the packages:
17
+
18
+   .. code-block:: console
19
+
20
+      # apt-get install manila-api manila-scheduler python-manilaclient
21
+
22
+#. Edit the ``/etc/manila/manila.conf`` file and complete the following
23
+   actions:
24
+
25
+   * In the ``[database]`` section, configure database access:
26
+
27
+     .. code-block:: ini
28
+
29
+        [database]
30
+        ...
31
+        connection = mysql+pymysql://manila:MANILA_DBPASS@controller/manila
32
+
33
+     Replace ``MANILA_DBPASS`` with the password you chose for the Shared
34
+     File Systems database.
35
+
36
+.. include:: common/controller-node-common-configuration.rst
37
+
38
+#. Populate the Shared File Systems database:
39
+
40
+   .. code-block:: console
41
+
42
+      # su -s /bin/sh -c "manila-manage db sync" manila
43
+
44
+   .. note::
45
+
46
+      Ignore any deprecation messages in this output.
47
+
48
+Finalize installation
49
+---------------------
50
+
51
+#. Restart the Shared File Systems services:
52
+
53
+   .. code-block:: console
54
+
55
+      # service manila-scheduler restart
56
+      # service manila-api restart

+ 22
- 0
install-guide/source/install-controller-node.rst View File

@@ -0,0 +1,22 @@
1
+.. _manila-controller:
2
+
3
+Install and configure controller node
4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5
+
6
+This section describes how to install and configure the Shared File Systems
7
+service, code-named manila, on the controller node. This service requires at
8
+least one additional share node that manages file storage back ends.
9
+
10
+This section assumes that you already have a working OpenStack
11
+environment with at least the following components installed:
12
+Compute, Image Service, Identity.
13
+
14
+Note that installation and configuration vary by distribution.
15
+
16
+.. toctree::
17
+   :maxdepth: 1
18
+
19
+   install-controller-obs.rst
20
+   install-controller-rdo.rst
21
+   install-controller-ubuntu.rst
22
+   install-controller-debian.rst

+ 47
- 0
install-guide/source/install-controller-obs.rst View File

@@ -0,0 +1,47 @@
1
+.. _manila-controller-obs:
2
+
3
+Install and configure controller node on openSUSE and SUSE Linux Enterprise
4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5
+
6
+This section describes how to install and configure the Shared File Systems
7
+service, code-named manila, on the controller node that runs openSUSE and SUSE
8
+Linux Enterprise. This service requires at least one additional share node
9
+that manages file storage back ends.
10
+
11
+.. include:: common/controller-node-prerequisites.rst
12
+
13
+Install and configure components
14
+--------------------------------
15
+
16
+#. Install the packages:
17
+
18
+   .. code-block:: console
19
+
20
+      # zypper install openstack-manila-api openstack-manila-scheduler python-manilaclient
21
+
22
+#. Edit the ``/etc/manila/manila.conf`` file and complete the
23
+   following actions:
24
+
25
+   * In the ``[database]`` section, configure database access:
26
+
27
+     .. code-block:: ini
28
+
29
+        [database]
30
+        ...
31
+        connection = mysql+pymysql://manila:MANILA_DBPASS@controller/manila
32
+
33
+     Replace ``MANILA_DBPASS`` with the password you chose for the Shared
34
+     File Systems database.
35
+
36
+.. include:: common/controller-node-common-configuration.rst
37
+
38
+Finalize installation
39
+---------------------
40
+
41
+#. Start the Shared File Systems services and configure them to start when
42
+   the system boots:
43
+
44
+   .. code-block:: console
45
+
46
+      # systemctl enable openstack-manila-api.service openstack-manila-scheduler.service
47
+      # systemctl start openstack-manila-api.service openstack-manila-scheduler.service

+ 57
- 0
install-guide/source/install-controller-rdo.rst View File

@@ -0,0 +1,57 @@
1
+.. _manila-controller-rdo:
2
+
3
+Install and configure controller node on Red Hat Enterprise Linux and CentOS
4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5
+
6
+This section describes how to install and configure the Shared File Systems
7
+service, code-named manila, on the controller node that runs Red Hat
8
+Enterprise Linux or CentOS. This service requires at least one additional
9
+share node that manages file storage back ends.
10
+
11
+.. include:: common/controller-node-prerequisites.rst
12
+
13
+Install and configure components
14
+--------------------------------
15
+
16
+#. Install the packages:
17
+
18
+   .. code-block:: console
19
+
20
+      # yum install openstack-manila python-manilaclient
21
+
22
+#. Edit the ``/etc/manila/manila.conf`` file and complete the
23
+   following actions:
24
+
25
+   * In the ``[database]`` section, configure database access:
26
+
27
+     .. code-block:: ini
28
+
29
+        [database]
30
+        ...
31
+        connection = mysql+pymysql://manila:MANILA_DBPASS@controller/manila
32
+
33
+     Replace ``MANILA_DBPASS`` with the password you chose for the Shared
34
+     File Systems database.
35
+
36
+.. include:: common/controller-node-common-configuration.rst
37
+
38
+#. Populate the Shared File Systems database:
39
+
40
+   .. code-block:: console
41
+
42
+      # su -s /bin/sh -c "manila-manage db sync" manila
43
+
44
+   .. note::
45
+
46
+      Ignore any deprecation messages in this output.
47
+
48
+Finalize installation
49
+---------------------
50
+
51
+#. Start the Shared File Systems services and configure them to start when
52
+   the system boots:
53
+
54
+   .. code-block:: console
55
+
56
+      # systemctl enable openstack-manila-api.service openstack-manila-scheduler.service
57
+      # systemctl start openstack-manila-api.service openstack-manila-scheduler.service

+ 64
- 0
install-guide/source/install-controller-ubuntu.rst View File

@@ -0,0 +1,64 @@
1
+.. _manila-controller-ubuntu:
2
+
3
+Install and configure controller node on Ubuntu
4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5
+
6
+This section describes how to install and configure the Shared File Systems
7
+service, code-named manila, on the controller node that runs Ubuntu. This
8
+service requires at least one additional share node that manages file
9
+storage back ends.
10
+
11
+.. include:: common/controller-node-prerequisites.rst
12
+
13
+Install and configure components
14
+--------------------------------
15
+
16
+#. Install the packages:
17
+
18
+   .. code-block:: console
19
+
20
+      # apt-get install manila-api manila-scheduler python-manilaclient
21
+
22
+#. Edit the ``/etc/manila/manila.conf`` file and complete the
23
+   following actions:
24
+
25
+   * In the ``[database]`` section, configure database access:
26
+
27
+     .. code-block:: ini
28
+
29
+        [database]
30
+        ...
31
+        connection = mysql+pymysql://manila:MANILA_DBPASS@controller/manila
32
+
33
+     Replace ``MANILA_DBPASS`` with the password you chose for the Shared
34
+     File Systems database.
35
+
36
+.. include:: common/controller-node-common-configuration.rst
37
+
38
+#. Populate the Shared File Systems database:
39
+
40
+   .. code-block:: console
41
+
42
+      # su -s /bin/sh -c "manila-manage db sync" manila
43
+
44
+   .. note::
45
+
46
+      Ignore any deprecation messages in this output.
47
+
48
+Finalize installation
49
+---------------------
50
+
51
+#. Restart the Shared File Systems services:
52
+
53
+   .. code-block:: console
54
+
55
+      # service manila-scheduler restart
56
+      # service manila-api restart
57
+
58
+#. By default, the Ubuntu packages create an SQLite database. Because this
59
+   configuration uses an SQL database server, you can remove the SQLite
60
+   database file:
61
+
62
+   .. code-block:: console
63
+
64
+      # rm -f /var/lib/manila/manila.sqlite

+ 91
- 0
install-guide/source/install-share-debian.rst View File

@@ -0,0 +1,91 @@
1
+.. _share-node-install-debian:
2
+
3
+Install and configure a share node running Debian
4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5
+
6
+This section describes how to install and configure a share node for the
7
+Shared File Systems service. For simplicity, this configuration references one
8
+storage node with the generic driver managing the share servers. The
9
+generic backend manages share servers using compute, networking and block
10
+services for provisioning shares.
11
+
12
+Note that installation and configuration vary by distribution. This section
13
+describes the instructions for a share node running a Debian distribution.
14
+
15
+Install and configure components
16
+--------------------------------
17
+
18
+#. Install the packages:
19
+
20
+   .. code-block:: console
21
+
22
+      # apt-get install manila-share python-pymysql
23
+
24
+#. Edit the ``/etc/manila/manila.conf`` file and complete the following
25
+   actions:
26
+
27
+   * In the ``[database]`` section, configure database access:
28
+
29
+     .. code-block:: ini
30
+
31
+        [database]
32
+        ...
33
+        connection = mysql+pymysql://manila:MANILA_DBPASS@controller/manila
34
+
35
+     Replace ``MANILA_DBPASS`` with the password you chose for the Shared
36
+     File Systems database.
37
+
38
+.. include:: common/share-node-common-configuration.rst
39
+
40
+Two driver modes
41
+----------------
42
+
43
+.. include:: common/share-node-share-server-modes.rst
44
+
45
+Choose one of the following options to configure the share driver:
46
+
47
+.. include:: common/dhss-false-mode-intro.rst
48
+
49
+Prerequisites
50
+-------------
51
+
52
+.. note::
53
+
54
+   Perform these steps on the storage node.
55
+
56
+#. Install the supporting utility packages:
57
+
58
+   * Install LVM and NFS server packages:
59
+
60
+     .. code-block:: console
61
+
62
+        # apt-get install lvm2 nfs-kernel-server
63
+
64
+.. include:: common/dhss-false-mode-configuration.rst
65
+
66
+.. include:: common/dhss-true-mode-intro.rst
67
+
68
+Prerequisites
69
+-------------
70
+
71
+Before you proceed, verify operation of the Compute, Networking, and Block
72
+Storage services. This options requires implementation of Networking option 2
73
+and requires installation of some Networking service components on the storage
74
+node.
75
+
76
+* Install the Networking service components:
77
+
78
+  .. code-block:: console
79
+
80
+     # apt-get install neutron-plugin-linuxbridge-agent
81
+
82
+.. include:: common/dhss-true-mode-configuration.rst
83
+
84
+Finalize installation
85
+---------------------
86
+#. Prepare manila-share as start/stop service. Start the Shared File Systems
87
+   service including its dependencies:
88
+
89
+   .. code-block:: console
90
+
91
+      # service manila-share restart

+ 21
- 0
install-guide/source/install-share-node.rst View File

@@ -0,0 +1,21 @@
1
+.. _share-node-install:
2
+
3
+Install and configure a share node
4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5
+
6
+This section describes how to install and configure a share node for the
7
+Shared File Systems service.
8
+
9
+.. Note::
10
+   The manila-share process can run in two modes, with and without handling of
11
+   share servers. In general it depends of the driver support.
12
+
13
+Note that installation and configuration vary by distribution.
14
+
15
+.. toctree::
16
+   :maxdepth: 1
17
+
18
+   install-share-obs.rst
19
+   install-share-rdo.rst
20
+   install-share-ubuntu.rst
21
+   install-share-debian.rst

+ 90
- 0
install-guide/source/install-share-obs.rst View File

@@ -0,0 +1,90 @@
1
+.. _share-node-install-obs:
2
+
3
+Install and configure a share node running openSUSE and SUSE Linux Enterprise
4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5
+
6
+This section describes how to install and configure a share node for the
7
+Shared File Systems service.
8
+
9
+Note that installation and configuration vary by distribution. This section
10
+describes the instructions for a share node running openSUSE and SUSE Linux
11
+Enterprise.
12
+
13
+Install and configure components
14
+--------------------------------
15
+
16
+#. Install the packages:
17
+
18
+   .. code-block:: console
19
+
20
+      # zypper install openstack-manila-share python-PyMySQL
21
+
22
+#. Edit the ``/etc/manila/manila.conf`` file and complete the following
23
+   actions:
24
+
25
+   * In the ``[database]`` section, configure database access:
26
+
27
+     .. code-block:: ini
28
+
29
+        [database]
30
+        ...
31
+        connection = mysql+pymysql://manila:MANILA_DBPASS@controller/manila
32
+
33
+     Replace ``MANILA_DBPASS`` with the password you chose for
34
+     the Shared File Systems database.
35
+
36
+.. include:: common/share-node-common-configuration.rst
37
+
38
+Two driver modes
39
+----------------
40
+
41
+.. include:: common/share-node-share-server-modes.rst
42
+
43
+Choose one of the following options to configure the share driver:
44
+
45
+.. include:: common/dhss-false-mode-intro.rst
46
+
47
+Prerequisites
48
+-------------
49
+
50
+.. note::
51
+   Perform these steps on the storage node.
52
+
53
+#. Install the supporting utility packages:
54
+
55
+   * Install LVM and NFS server packages:
56
+
57
+     .. code-block:: console
58
+
59
+        # zypper install lvm2 nfs-kernel-server
60
+
61
+.. include:: common/dhss-false-mode-configuration.rst
62
+
63
+.. include:: common/dhss-true-mode-intro.rst
64
+
65
+Prerequisites
66
+-------------
67
+
68
+Before you proceed, verify operation of the Compute, Networking, and Block
69
+Storage services. This options requires implementation of Networking option 2
70
+and requires installation of some Networking service components on the storage
71
+node.
72
+
73
+* Install the Networking service components:
74
+
75
+  .. code-block:: console
76
+
77
+     # zypper install --no-recommends openstack-neutron-linuxbridge-agent
78
+
79
+.. include:: common/dhss-true-mode-configuration.rst
80
+
81
+Finalize installation
82
+---------------------
83
+#. Prepare manila-share as start/stop service. Start the Shared File Systems
84
+   service including its dependencies and configure them to start when the
85
+   system boots:
86
+
87
+   .. code-block:: console
88
+
89
+      # systemctl enable openstack-manila-share.service tgtd.service
90
+      # systemctl start openstack-manila-share.service tgtd.service

+ 103
- 0
install-guide/source/install-share-rdo.rst View File

@@ -0,0 +1,103 @@
1
+.. _share-node-install-rdo:
2
+
3
+Install and configure a share node running Red Hat Enterprise Linux and CentOS
4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5
+
6
+This section describes how to install and configure a share node for the
7
+Shared File Systems service. For simplicity, this configuration references one
8
+storage node with the generic driver managing the share servers. The
9
+generic backend manages share servers using compute, networking and block
10
+services for provisioning shares.
11
+
12
+Note that installation and configuration vary by distribution. This section
13
+describes the instructions for a share node running Red Hat Enterprise Linux
14
+or CentOS.
15
+
16
+Install and configure components
17
+--------------------------------
18
+
19
+#. Install the packages:
20
+
21
+   .. code-block:: console
22
+
23
+      # yum install openstack-manila-share python2-PyMySQL
24
+
25
+#. Edit the ``/etc/manila/manila.conf`` file and complete the following
26
+   actions:
27
+
28
+   * In the ``[database]`` section, configure database access:
29
+
30
+     .. code-block:: ini
31
+
32
+        [database]
33
+        ...
34
+        connection = mysql://manila:MANILA_DBPASS@controller/manila
35
+
36
+
37
+     Replace ``MANILA_DBPASS`` with the password you chose for
38
+     the Shared File Systems database.
39
+
40
+.. include:: common/share-node-common-configuration.rst
41
+
42
+Two driver modes
43
+----------------
44
+
45
+.. include:: common/share-node-share-server-modes.rst
46
+
47
+Choose one of the following options to configure the share driver:
48
+
49
+.. include:: common/dhss-false-mode-intro.rst
50
+
51
+Prerequisites
52
+-------------
53
+
54
+.. note::
55
+
56
+   Perform these steps on the storage node.
57
+
58
+#. Install the supporting utility packages:
59
+
60
+   * Install LVM and NFS server packages:
61
+
62
+     .. code-block:: console
63
+
64
+        # yum install lvm2 nfs-utils nfs4-acl-tools portmap
65
+
66
+   * Start the LVM metadata service and configure it to start when the
67
+     system boots:
68
+
69
+     .. code-block:: console
70
+
71
+        # systemctl enable lvm2-lvmetad.service
72
+        # systemctl start lvm2-lvmetad.service
73
+
74
+.. include:: common/dhss-false-mode-configuration.rst
75
+
76
+.. include:: common/dhss-true-mode-intro.rst
77
+
78
+Prerequisites
79
+-------------
80
+
81
+Before you proceed, verify operation of the Compute, Networking, and Block
82
+Storage services. This options requires implementation of Networking option 2
83
+and requires installation of some Networking service components on the storage
84
+node.
85
+
86
+* Install the Networking service components:
87
+
88
+  .. code-block:: console
89
+
90
+     # yum install openstack-neutron openstack-neutron-linuxbridge ebtables
91
+
92
+.. include:: common/dhss-true-mode-configuration.rst
93
+
94
+Finalize installation
95
+---------------------
96
+#. Prepare manila-share as start/stop service. Start the Shared File Systems
97
+   service including its dependencies and configure them to start when the
98
+   system boots:
99
+
100
+   .. code-block:: console
101
+
102
+      # systemctl enable openstack-manila-share.service target.service
103
+      # systemctl start openstack-manila-share.service target.service

+ 99
- 0
install-guide/source/install-share-ubuntu.rst View File

@@ -0,0 +1,99 @@
1
+.. _share-node-install-ubuntu:
2
+
3
+Install and configure a share node running Ubuntu
4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5
+
6
+This section describes how to install and configure a share node for the
7
+Shared File Systems service. For simplicity, this configuration references one
8
+storage node with the generic driver managing the share servers. The
9
+generic backend manages share servers using compute, networking and block
10
+services for provisioning shares.
11
+
12
+Note that installation and configuration vary by distribution. This section
13
+describes the instructions for a share node running Ubuntu.
14
+
15
+Install and configure components
16
+--------------------------------
17
+
18
+#. Install the packages:
19
+
20
+   .. code-block:: console
21
+
22
+      # apt-get install manila-share python-pymysql
23
+
24
+#. Edit the ``/etc/manila/manila.conf`` file and complete the following
25
+   actions:
26
+
27
+   * In the ``[database]`` section, configure database access:
28
+
29
+     .. code-block:: ini
30
+
31
+        [database]
32
+        ...
33
+        connection = mysql+pymysql://manila:MANILA_DBPASS@controller/manila
34
+
35
+     Replace ``MANILA_DBPASS`` with the password you chose for
36
+     the Shared File Systems database.
37
+
38
+.. include:: common/share-node-common-configuration.rst
39
+
40
+Two driver modes
41
+----------------
42
+
43
+.. include:: common/share-node-share-server-modes.rst
44
+
45
+Choose one of the following options to configure the share driver:
46
+
47
+.. include:: common/dhss-false-mode-intro.rst
48
+
49
+Prerequisites
50
+-------------
51
+
52
+.. note::
53
+
54
+   Perform these steps on the storage node.
55
+
56
+#. Install the supporting utility packages:
57
+
58
+   * Install LVM and NFS server packages:
59
+
60
+     .. code-block:: console
61
+
62
+        # apt-get install lvm2 nfs-kernel-server
63
+
64
+.. include:: common/dhss-false-mode-configuration.rst
65
+
66
+.. include:: common/dhss-true-mode-intro.rst
67
+
68
+Prerequisites
69
+-------------
70
+
71
+Before you proceed, verify operation of the Compute, Networking, and Block
72
+Storage services. This options requires implementation of Networking option 2
73
+and requires installation of some Networking service components on the storage
74
+node.
75
+
76
+* Install the Networking service components:
77
+
78
+  .. code-block:: console
79
+
80
+     # apt-get install neutron-plugin-linuxbridge-agent
81
+
82
+.. include:: common/dhss-true-mode-configuration.rst
83
+
84
+Finalize installation
85
+---------------------
86
+#. Prepare manila-share as start/stop service. Start the Shared File Systems
87
+   service including its dependencies:
88
+
89
+   .. code-block:: console
90
+
91
+      # service manila-share restart
92
+
93
+#. By default, the Ubuntu packages create an SQLite database. Because this
94
+   configuration uses an SQL database server, remove the SQLite database
95
+   file:
96
+
97
+   .. code-block:: console
98
+
99
+      # rm -f /var/lib/manila/manila.sqlite

+ 14
- 0
install-guide/source/next-steps.rst View File

@@ -0,0 +1,14 @@
1
+.. _next-steps:
2
+
3
+==========
4
+Next steps
5
+==========
6
+
7
+Your OpenStack environment now includes the Shared File Systems service.
8
+
9
+To add more services, see the `additional documentation on installing
10
+OpenStack services <http://docs.openstack.org/#install-guides>`_
11
+
12
+Continue to evaluate the Shared File Systems service by creating the service
13
+image and running the service with the correct driver mode that you chose
14
+while configuring the share node.

+ 196
- 0
install-guide/source/post-install.rst View File

@@ -0,0 +1,196 @@
1
+.. _post-install:
2
+
3
+Creating shared file systems
4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5
+
6
+Before being able to create a share, manila with the generic driver and
7
+the DHSS mode enabled requires the definition of at least an image,
8
+a network and a share-network for being used to create a share server.
9
+For that `back end` configuration, the share server is an instance where
10
+NFS/CIFS shares are served.
11
+
12
+.. note::
13
+
14
+   This configuration automatically creates a cinder volume for every share.
15
+   The cinder volumes are attached to share servers according to the
16
+   definition of a share network.
17
+
18
+Determine the configuration of the share server
19
+-----------------------------------------------
20
+
21
+#. Source the admin credentials to gain access to admin-only CLI commands:
22
+
23
+   .. code-block:: console
24
+
25
+      $ . admin-openrc.sh
26
+
27
+#. Create a default share type before running manila-share service:
28
+
29
+   .. code-block:: console
30
+
31
+      $ manila type-create default_share_type True
32
+      +--------------------------------------+--------------------+------------+------------+-------------------------------------+-------------------------+
33
+      | ID                                   | Name               | Visibility | is_default | required_extra_specs                | optional_extra_specs    |
34
+      +--------------------------------------+--------------------+------------+------------+-------------------------------------+-------------------------+
35
+      | 8a35da28-0f74-490d-afff-23664ecd4f01 | default_share_type | public     | -          | driver_handles_share_servers : True | snapshot_support : True |
36
+      +--------------------------------------+--------------------+------------+------------+-------------------------------------+-------------------------+
37
+
38
+#. Create a manila share server image to the Image service:
39
+
40
+   .. code-block:: console
41
+
42
+      $ glance image-create \
43
+      --copy-from http://tarballs.openstack.org/manila-image-elements/images/manila-service-image-master.qcow2 \
44
+      --name "manila-service-image" \
45
+      --disk-format qcow2 \
46
+      --container-format bare \
47
+      --visibility public --progress
48
+      [=============================>] 100%
49
+      +------------------+--------------------------------------+
50
+      | Property         | Value                                |
51
+      +------------------+--------------------------------------+
52
+      | checksum         | 48a08e746cf0986e2bc32040a9183445     |
53
+      | container_format | bare                                 |
54
+      | created_at       | 2016-01-26T19:52:24Z                 |
55
+      | disk_format      | qcow2                                |
56
+      | id               | 1fc7f29e-8fe6-44ef-9c3c-15217e83997c |
57
+      | min_disk         | 0                                    |
58
+      | min_ram          | 0                                    |
59
+      | name             | manila-service-image                 |
60
+      | owner            | e2c965830ecc4162a002bf16ddc91ab7     |
61
+      | protected        | False                                |
62
+      | size             | 306577408                            |
63
+      | status           | active                               |
64
+      | tags             | []                                   |
65
+      | updated_at       | 2016-01-26T19:52:28Z                 |
66
+      | virtual_size     | None                                 |
67
+      | visibility       | public                               |
68
+      +------------------+--------------------------------------+
69
+
70
+#. List available networks in order to get id and subnets of the private
71
+   network:
72
+
73
+   .. code-block:: console
74
+
75
+      $ neutron net-list
76
+      +--------------------------------------+---------+----------------------------------------------------+
77
+      | id                                   | name    | subnets                                            |
78
+      +--------------------------------------+---------+----------------------------------------------------+
79
+      | 0e62efcd-8cee-46c7-b163-d8df05c3c5ad | public  | 5cc70da8-4ee7-4565-be53-b9c011fca011 10.3.31.0/24  |
80
+      | 7c6f9b37-76b4-463e-98d8-27e5686ed083 | private | 3482f524-8bff-4871-80d4-5774c2730728 172.16.1.0/24 |
81
+      +--------------------------------------+---------+----------------------------------------------------+
82
+
83
+#. Source the ``demo`` credentials to perform
84
+   the following steps as a non-administrative project:
85
+
86
+   .. code-block:: console
87
+
88
+      $ . demo-openrc.sh
89
+
90
+   .. code-block:: console
91
+
92
+      $ manila share-network-create --name demo-share-network1 \
93
+      --neutron-net-id PRIVATE_NETWORK_ID \
94
+      --neutron-subnet-id PRIVATE_NETWORK_SUBNET_ID
95
+      +-------------------+--------------------------------------+
96
+      | Property          | Value                                |
97
+      +-------------------+--------------------------------------+
98
+      | name              | demo-share-network1                  |
99
+      | segmentation_id   | None                                 |
100
+      | created_at        | 2016-01-26T20:03:41.877838           |
101
+      | neutron_subnet_id | 3482f524-8bff-4871-80d4-5774c2730728 |
102
+      | updated_at        | None                                 |
103
+      | network_type      | None                                 |
104
+      | neutron_net_id    | 7c6f9b37-76b4-463e-98d8-27e5686ed083 |
105
+      | ip_version        | None                                 |
106
+      | nova_net_id       | None                                 |
107
+      | cidr              | None                                 |
108
+      | project_id        | e2c965830ecc4162a002bf16ddc91ab7     |
109
+      | id                | 58b2f0e6-5509-4830-af9c-97f525a31b14 |
110
+      | description       | None                                 |
111
+      +-------------------+--------------------------------------+
112
+
113
+Create a share
114
+--------------
115
+
116
+#. Create a NFS share using the share network:
117
+
118
+   .. code-block:: console
119
+
120
+      $ manila create NFS 1 --name demo-share1 --share-network demo-share-network1
121
+      +-----------------------------+--------------------------------------+
122
+      | Property                    | Value                                |
123
+      +-----------------------------+--------------------------------------+
124
+      | status                      | None                                 |
125
+      | share_type_name             | None                                 |
126
+      | description                 | None                                 |
127
+      | availability_zone           | None                                 |
128
+      | share_network_id            | None                                 |
129
+      | export_locations            | []                                   |
130
+      | host                        | None                                 |
131
+      | snapshot_id                 | None                                 |
132
+      | is_public                   | False                                |
133
+      | task_state                  | None                                 |
134
+      | snapshot_support            | True                                 |
135
+      | id                          | 016ca18f-bdd5-48e1-88c0-782e4c1aa28c |
136
+      | size                        | 1                                    |
137
+      | name                        | demo-share1                          |
138
+      | share_type                  | None                                 |
139
+      | created_at                  | 2016-01-26T20:08:50.502877           |
140
+      | export_location             | None                                 |
141
+      | share_proto                 | NFS                                  |
142
+      | consistency_group_id        | None                                 |
143
+      | source_cgsnapshot_member_id | None                                 |
144
+      | project_id                  | 48e8c35b2ac6495d86d4be61658975e7     |
145
+      | metadata                    | {}                                   |
146
+      +-----------------------------+--------------------------------------+
147
+
148
+#. After some time, the share status should change from ``creating``
149
+   to ``available``:
150
+
151
+   .. code-block:: console
152
+
153
+      $ manila list
154
+      +--------------------------------------+-------------+------+-------------+-----------+-----------+--------------------------------------+---------------------------------------------------------------+-----------------------------+-------------------+
155
+      | ID                                   | Name        | Size | Share Proto | Status    | Is Public | Share Type                           | Export location                                               | Host                        | Availability Zone |
156
+      +--------------------------------------+-------------+------+-------------+-----------+-----------+--------------------------------------+---------------------------------------------------------------+-----------------------------+-------------------+
157
+      | 5f8a0574-a95e-40ff-b898-09fd8d6a1fac | demo-share1 | 1    | NFS         | available | False     | 8a35da28-0f74-490d-afff-23664ecd4f01 | 10.254.0.6:/shares/share-0bfd69a1-27f0-4ef5-af17-7cd50bce6550 | storagenode@generic#GENERIC | nova              |
158
+      +--------------------------------------+-------------+------+-------------+-----------+-----------+--------------------------------------+---------------------------------------------------------------+-----------------------------+-------------------+
159
+
160
+#. Configure user access to the new share before attempting to mount it via
161
+   the network:
162
+
163
+   .. important ::
164
+
165
+      The image used for launching an instance and mounting a share must have
166
+      the NFS packages provided by the distro. Example: The cirros image
167
+      created at the image service section is not enough.
168
+
169
+   .. important ::
170
+
171
+      Use an instance that is connected to the private network used to create
172
+      the share-network.
173
+
174
+   .. code-block:: console
175
+
176
+      $ manila access-allow demo-share1 ip INSTANCE_PRIVATE_NETWORK_IP
177
+
178
+Mount the share from an instance
179
+--------------------------------
180
+
181
+#. Create a folder where the mount will be placed:
182
+
183
+   .. code-block:: console
184
+
185
+      $ mkdir ~/test_folder
186
+
187
+#. Mount the NFS share in the instance using the export location of the share:
188
+
189
+   .. code-block:: console
190
+
191
+      $ mount -v 10.254.0.6:/shares/share-0bfd69a1-27f0-4ef5-af17-7cd50bce6550 ~/test_folder
192
+
193
+
194
+For more information about how to manage shares, see the
195
+`OpenStack User Guide
196
+<http://docs.openstack.org/user-guide/index.html>`__.

+ 29
- 0
install-guide/source/verify.rst View File

@@ -0,0 +1,29 @@
1
+.. _verify:
2
+
3
+Verify operation
4
+~~~~~~~~~~~~~~~~
5
+
6
+Verify operation of the Shared File Systems service.
7
+
8
+.. note::
9
+
10
+   Perform these commands on the controller node.
11
+
12
+#. Source the ``admin`` credentials to gain access to
13
+   admin-only CLI commands:
14
+
15
+   .. code-block:: console
16
+
17
+      $ . admin-openrc.sh
18
+
19
+#. List service components to verify successful launch of each process:
20
+
21
+   .. code-block:: console
22
+
23
+      $ manila service-list
24
+      +------------------+----------------+------+---------+-------+----------------------------+-----------------+
25
+      |      Binary      |    Host        | Zone |  Status | State |         Updated_at         | Disabled Reason |
26
+      +------------------+----------------+------+---------+-------+----------------------------+-----------------+
27
+      | manila-scheduler | controller     | nova | enabled |   up  | 2014-10-18T01:30:54.000000 |       None      |
28
+      | manila-share     | share1@generic | nova | enabled |   up  | 2014-10-18T01:30:57.000000 |       None      |
29
+      +------------------+----------------+------+---------+-------+----------------------------+-----------------+

+ 5
- 1
tox.ini View File

@@ -22,6 +22,10 @@ install_command = pip install -U --force-reinstall {opts} {packages}
22 22
 commands = sphinx-build -a -E -W -d releasenotes/build/doctrees \
23 23
          -b html releasenotes/source releasenotes/build/html
24 24
 
25
+[testenv:install-guide]
26
+# builds to install-guide/build/html
27
+commands = sphinx-build -a -E -W -d install-guide/build/doctrees -b html install-guide/source install-guide/build/html
28
+
25 29
 [testenv:debug]
26 30
 commands = oslo_debug_helper {posargs}
27 31
 
@@ -102,7 +106,7 @@ commands = alembic -c manila/db/migrations/alembic.ini revision -m ""{posargs}
102 106
 # Following checks are ignored on purpose:
103 107
 ignore = 
104 108
 builtins = _
105
-exclude = .git,.tox,.testrepository,.venv,build,cover,dist,doc,*egg,api-ref/build
109
+exclude = .git,.tox,.testrepository,.venv,build,cover,dist,doc,*egg,api-ref/build,*/source/conf.py
106 110
 
107 111
 [hacking]
108 112
 import_exceptions =

Loading…
Cancel
Save