Yulia Portnova 5 years ago
parent
commit
9169fc311e

+ 3
- 3
.gitignore View File

@@ -4,7 +4,7 @@
4 4
 *.pyc
5 5
 *.sqlite
6 6
 *.swp
7
-.cinder-venv
7
+.manila-venv
8 8
 .coverage
9 9
 .testrepository
10 10
 .tox
@@ -16,7 +16,7 @@ build/*
16 16
 build-stamp
17 17
 CA/
18 18
 ChangeLog
19
-cinder.egg-info
19
+manila.egg-info
20 20
 cover/*
21 21
 covhtml
22 22
 dist/*
@@ -24,7 +24,7 @@ instances
24 24
 keeper
25 25
 keys
26 26
 local_settings.py
27
-tools/conf/cinder.conf*
27
+tools/conf/manila.conf*
28 28
 tools/lintstack.head.py
29 29
 tools/pylint_exceptions
30 30
 tags

+ 1
- 1
CONTRIBUTING.md View File

@@ -8,5 +8,5 @@ the workflow documented at [http://wiki.openstack.org/GerritWorkflow](http://wik
8 8
 
9 9
 Pull requests submitted through GitHub will be ignored.
10 10
 
11
-Bugs should be filed [on Launchpad](https://bugs.launchpad.net/cinder),
11
+Bugs should be filed [on Launchpad](https://bugs.launchpad.net/manila),
12 12
 not in GitHub's issue tracker.

+ 10
- 10
HACKING.rst View File

@@ -1,4 +1,4 @@
1
-Cinder Style Commandments
1
+Manila Style Commandments
2 2
 =======================
3 3
 
4 4
 - Step 1: Read http://www.python.org/dev/peps/pep-0008/
@@ -59,7 +59,7 @@ Imports
59 59
 
60 60
 - imports from ``migrate`` package
61 61
 - imports from ``sqlalchemy`` package
62
-- imports from ``cinder.db.sqlalchemy.session`` module
62
+- imports from ``manila.db.sqlalchemy.session`` module
63 63
 
64 64
 Example::
65 65
 
@@ -68,7 +68,7 @@ Example::
68 68
   \n
69 69
   {{third-party lib imports in human alphabetical order}}
70 70
   \n
71
-  {{cinder imports in human alphabetical order}}
71
+  {{manila imports in human alphabetical order}}
72 72
   \n
73 73
   \n
74 74
   {{begin your code}}
@@ -88,12 +88,12 @@ Example::
88 88
   import eventlet
89 89
   import webob.exc
90 90
 
91
-  import cinder.api.ec2
92
-  from cinder.api import openstack
93
-  from cinder.auth import users
94
-  from cinder.endpoint import cloud
95
-  import cinder.flags
96
-  from cinder import test
91
+  import manila.api.ec2
92
+  from manila.api import openstack
93
+  from manila.auth import users
94
+  from manila.endpoint import cloud
95
+  import manila.flags
96
+  from manila import test
97 97
 
98 98
 
99 99
 Docstrings
@@ -216,7 +216,7 @@ submitted bug fix does have a unit test, be sure to add a new one that fails
216 216
 without the patch and passes with the patch.
217 217
 
218 218
 For more information on creating unit tests and utilizing the testing
219
-infrastructure in OpenStack Cinder, please read cinder/testing/README.rst.
219
+infrastructure in OpenStack Manila, please read manila/testing/README.rst.
220 220
 
221 221
 
222 222
 openstack-common

+ 6
- 6
README.rst View File

@@ -1,21 +1,21 @@
1
-The Choose Your Own Adventure README for Cinder
1
+The Choose Your Own Adventure README for Manila
2 2
 ===============================================
3 3
 
4 4
 You have come across a storage service for an open cloud computing service.
5
-It has identified itself as "Cinder."   It was abstracted from the Nova project.
5
+It has identified itself as "Manila."   It was abstracted from the Nova project.
6 6
 
7 7
 To monitor it from a distance: follow `@openstack <http://twitter.com/openstack>`_ on twitter.
8 8
 
9 9
 To tame it for use in your own cloud: read http://docs.openstack.org
10 10
 
11
-To study its anatomy: read http://cinder.openstack.org
11
+To study its anatomy: read http://manila.openstack.org
12 12
 
13
-To dissect it in detail: visit http://github.com/openstack/cinder
13
+To dissect it in detail: visit http://github.com/openstack/manila
14 14
 
15
-To taunt it with its weaknesses: use http://bugs.launchpad.net/cinder
15
+To taunt it with its weaknesses: use http://bugs.launchpad.net/manila
16 16
 
17 17
 To watch it: http://jenkins.openstack.org
18 18
 
19 19
 To hack at it: read HACKING
20 20
 
21
-To cry over its pylint problems: http://jenkins.openstack.org/job/cinder-pylint/violations
21
+To cry over its pylint problems: http://jenkins.openstack.org/job/manila-pylint/violations

+ 3
- 3
doc/Makefile View File

@@ -32,7 +32,7 @@ help:
32 32
 
33 33
 clean:
34 34
 	-rm -rf $(BUILDDIR)/*
35
-	-rm -rf cinder.sqlite
35
+	-rm -rf manila.sqlite
36 36
 	if [ -f .autogenerated ] ; then \
37 37
         cat .autogenerated | xargs rm ; \
38 38
         rm .autogenerated ; \
@@ -69,9 +69,9 @@ qthelp:
69 69
 	@echo
70 70
 	@echo "Build finished; now you can run "qcollectiongenerator" with the" \
71 71
 	      ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
72
-	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/cinder.qhcp"
72
+	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/manila.qhcp"
73 73
 	@echo "To view the help file:"
74
-	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/cinder.qhc"
74
+	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/manila.qhc"
75 75
 
76 76
 latex:
77 77
 	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex

+ 1
- 1
doc/README.rst View File

@@ -8,7 +8,7 @@ Dependencies
8 8
 Sphinx_
9 9
   You'll need sphinx (the python one) and if you are
10 10
   using the virtualenv you'll need to install it in the virtualenv
11
-  specifically so that it can load the cinder modules.
11
+  specifically so that it can load the manila modules.
12 12
 
13 13
   ::
14 14
 

+ 3
- 3
doc/find_autodoc_modules.sh View File

@@ -1,14 +1,14 @@
1 1
 #!/bin/bash
2 2
 
3
-CINDER_DIR='cinder/' # include trailing slash
3
+MANILA_DIR='manila/' # include trailing slash
4 4
 DOCS_DIR='source'
5 5
 
6 6
 modules=''
7
-for x in `find ${CINDER_DIR} -name '*.py' | grep -v cinder/tests`; do
7
+for x in `find ${MANILA_DIR} -name '*.py' | grep -v manila/tests`; do
8 8
     if [ `basename ${x} .py` == "__init__" ] ; then
9 9
         continue
10 10
     fi
11
-    relative=cinder.`echo ${x} | sed -e 's$^'${CINDER_DIR}'$$' -e 's/.py$//' -e 's$/$.$g'`
11
+    relative=manila.`echo ${x} | sed -e 's$^'${MANILA_DIR}'$$' -e 's/.py$//' -e 's$/$.$g'`
12 12
     modules="${modules} ${relative}"
13 13
 done
14 14
 

+ 4
- 4
doc/source/devref/addmethod.openstackapi.rst View File

@@ -24,7 +24,7 @@ Routing
24 24
 
25 25
 To map URLs to controllers+actions, OpenStack uses the Routes package, a clone of Rails routes for Python implementations. See http://routes.groovie.org/ for more information.
26 26
 
27
-URLs are mapped to "action" methods on "controller" classes in ``cinder/api/openstack/__init__/ApiRouter.__init__`` .
27
+URLs are mapped to "action" methods on "controller" classes in ``manila/api/openstack/__init__/ApiRouter.__init__`` .
28 28
 
29 29
 See http://routes.groovie.org/manual.html for all syntax, but you'll probably just need these two:
30 30
    - mapper.connect() lets you map a single URL to a single action on a controller.
@@ -33,9 +33,9 @@ See http://routes.groovie.org/manual.html for all syntax, but you'll probably ju
33 33
 Controllers and actions
34 34
 -----------------------
35 35
 
36
-Controllers live in ``cinder/api/openstack``, and inherit from cinder.wsgi.Controller.
36
+Controllers live in ``manila/api/openstack``, and inherit from manila.wsgi.Controller.
37 37
 
38
-See ``cinder/api/openstack/servers.py`` for an example.
38
+See ``manila/api/openstack/servers.py`` for an example.
39 39
 
40 40
 Action methods take parameters that are sucked out of the URL by mapper.connect() or .resource().  The first two parameters are self and the WebOb request, from which you can get the req.environ, req.body, req.headers, etc.
41 41
 
@@ -46,7 +46,7 @@ Actions return a dictionary, and wsgi.Controller serializes that to JSON or XML
46 46
 
47 47
 If you define a new controller, you'll need to define a ``_serialization_metadata`` attribute on the class, to tell wsgi.Controller how to convert your dictionary to XML.  It needs to know the singular form of any list tag (e.g. ``<servers>`` list contains ``<server>`` tags) and which dictionary keys are to be XML attributes as opposed to subtags (e.g. ``<server id="4"/>`` instead of ``<server><id>4</id></server>``).
48 48
 
49
-See `cinder/api/openstack/servers.py` for an example.
49
+See `manila/api/openstack/servers.py` for an example.
50 50
 
51 51
 Faults
52 52
 ------

+ 19
- 19
doc/source/devref/api.rst View File

@@ -18,25 +18,25 @@
18 18
 API Endpoint
19 19
 ============
20 20
 
21
-Cinder has a system for managing multiple APIs on different subdomains.
21
+Manila has a system for managing multiple APIs on different subdomains.
22 22
 Currently there is support for the OpenStack API, as well as the Amazon EC2
23 23
 API.
24 24
 
25 25
 Common Components
26 26
 -----------------
27 27
 
28
-The :mod:`cinder.api` Module
28
+The :mod:`manila.api` Module
29 29
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30
-.. automodule:: cinder.api
30
+.. automodule:: manila.api
31 31
     :noindex:
32 32
     :members:
33 33
     :undoc-members:
34 34
     :show-inheritance:
35 35
 
36
-The :mod:`cinder.api.cloud` Module
36
+The :mod:`manila.api.cloud` Module
37 37
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
38 38
 
39
-.. automodule:: cinder.api.cloud
39
+.. automodule:: manila.api.cloud
40 40
     :noindex:
41 41
     :members:
42 42
     :undoc-members:
@@ -47,7 +47,7 @@ OpenStack API
47 47
 
48 48
 The :mod:`openstack` Module
49 49
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
50
-.. automodule:: cinder.api.openstack
50
+.. automodule:: manila.api.openstack
51 51
     :noindex:
52 52
     :members:
53 53
     :undoc-members:
@@ -55,7 +55,7 @@ The :mod:`openstack` Module
55 55
 
56 56
 The :mod:`auth` Module
57 57
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
58
-.. automodule:: cinder.api.openstack.auth
58
+.. automodule:: manila.api.openstack.auth
59 59
     :noindex:
60 60
     :members:
61 61
     :undoc-members:
@@ -64,10 +64,10 @@ The :mod:`auth` Module
64 64
 EC2 API
65 65
 -------
66 66
 
67
-The :mod:`cinder.api.ec2` Module
67
+The :mod:`manila.api.ec2` Module
68 68
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
69 69
 
70
-.. automodule:: cinder.api.ec2
70
+.. automodule:: manila.api.ec2
71 71
     :noindex:
72 72
     :members:
73 73
     :undoc-members:
@@ -76,7 +76,7 @@ The :mod:`cinder.api.ec2` Module
76 76
 The :mod:`cloud` Module
77 77
 ~~~~~~~~~~~~~~~~~~~~~~~
78 78
 
79
-.. automodule:: cinder.api.ec2.cloud
79
+.. automodule:: manila.api.ec2.cloud
80 80
     :noindex:
81 81
     :members:
82 82
     :undoc-members:
@@ -85,7 +85,7 @@ The :mod:`cloud` Module
85 85
 The :mod:`metadatarequesthandler` Module
86 86
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
87 87
 
88
-.. automodule:: cinder.api.ec2.metadatarequesthandler
88
+.. automodule:: manila.api.ec2.metadatarequesthandler
89 89
     :noindex:
90 90
     :members:
91 91
     :undoc-members:
@@ -97,7 +97,7 @@ Tests
97 97
 The :mod:`api_unittest` Module
98 98
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
99 99
 
100
-.. automodule:: cinder.tests.api_unittest
100
+.. automodule:: manila.tests.api_unittest
101 101
     :noindex:
102 102
     :members:
103 103
     :undoc-members:
@@ -106,7 +106,7 @@ The :mod:`api_unittest` Module
106 106
 The :mod:`api_integration` Module
107 107
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
108 108
 
109
-.. automodule:: cinder.tests.api_integration
109
+.. automodule:: manila.tests.api_integration
110 110
     :noindex:
111 111
     :members:
112 112
     :undoc-members:
@@ -115,7 +115,7 @@ The :mod:`api_integration` Module
115 115
 The :mod:`cloud_unittest` Module
116 116
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
117 117
 
118
-.. automodule:: cinder.tests.cloud_unittest
118
+.. automodule:: manila.tests.cloud_unittest
119 119
     :noindex:
120 120
     :members:
121 121
     :undoc-members:
@@ -124,7 +124,7 @@ The :mod:`cloud_unittest` Module
124 124
 The :mod:`api.fakes` Module
125 125
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
126 126
 
127
-.. automodule:: cinder.tests.api.fakes
127
+.. automodule:: manila.tests.api.fakes
128 128
     :noindex:
129 129
     :members:
130 130
     :undoc-members:
@@ -133,7 +133,7 @@ The :mod:`api.fakes` Module
133 133
 The :mod:`api.test_wsgi` Module
134 134
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
135 135
 
136
-.. automodule:: cinder.tests.api.test_wsgi
136
+.. automodule:: manila.tests.api.test_wsgi
137 137
     :noindex:
138 138
     :members:
139 139
     :undoc-members:
@@ -142,7 +142,7 @@ The :mod:`api.test_wsgi` Module
142 142
 The :mod:`test_api` Module
143 143
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
144 144
 
145
-.. automodule:: cinder.tests.api.openstack.test_api
145
+.. automodule:: manila.tests.api.openstack.test_api
146 146
     :noindex:
147 147
     :members:
148 148
     :undoc-members:
@@ -151,7 +151,7 @@ The :mod:`test_api` Module
151 151
 The :mod:`test_auth` Module
152 152
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
153 153
 
154
-.. automodule:: cinder.tests.api.openstack.test_auth
154
+.. automodule:: manila.tests.api.openstack.test_auth
155 155
     :noindex:
156 156
     :members:
157 157
     :undoc-members:
@@ -160,7 +160,7 @@ The :mod:`test_auth` Module
160 160
 The :mod:`test_faults` Module
161 161
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
162 162
 
163
-.. automodule:: cinder.tests.api.openstack.test_faults
163
+.. automodule:: manila.tests.api.openstack.test_faults
164 164
     :noindex:
165 165
     :members:
166 166
     :undoc-members:

+ 4
- 4
doc/source/devref/architecture.rst View File

@@ -15,12 +15,12 @@
15 15
       License for the specific language governing permissions and limitations
16 16
       under the License.
17 17
 
18
-Cinder System Architecture
18
+Manila System Architecture
19 19
 ========================
20 20
 
21
-The Cinder Block Storage Service is intended to be ran on one or more nodes.
21
+The Manila Block Storage Service is intended to be ran on one or more nodes.
22 22
 
23
-Cinder uses a sql-based central database that is shared by all Cinder services in the system.  The amount and depth of the data fits into a sql database quite well.  For small deployments this seems like an optimal solution.  For larger deployments, and especially if security is a concern, cinder will be moving towards multiple data stores with some kind of aggregation system.
23
+Manila uses a sql-based central database that is shared by all Manila services in the system.  The amount and depth of the data fits into a sql database quite well.  For small deployments this seems like an optimal solution.  For larger deployments, and especially if security is a concern, manila will be moving towards multiple data stores with some kind of aggregation system.
24 24
 
25 25
 Components
26 26
 ----------
@@ -34,7 +34,7 @@ Below you will a brief explanation of the different components.
34 34
                                      |            \- ( DB )
35 35
                                      |
36 36
                                      |
37
-                    cinderclient     |
37
+                    manilaclient     |
38 38
                    /             \   |
39 39
  [ Web Dashboard ]-               -[ api ] -- < AMQP > -- [ scheduler ] -- [ volume ] -- ( iSCSI )
40 40
                    \             /   |

+ 10
- 10
doc/source/devref/auth.rst View File

@@ -20,20 +20,20 @@
20 20
 Authentication and Authorization
21 21
 ================================
22 22
 
23
-The :mod:`cinder.quota` Module
23
+The :mod:`manila.quota` Module
24 24
 ----------------------------
25 25
 
26
-.. automodule:: cinder.quota
26
+.. automodule:: manila.quota
27 27
     :noindex:
28 28
     :members:
29 29
     :undoc-members:
30 30
     :show-inheritance:
31 31
 
32 32
 
33
-The :mod:`cinder.auth.signer` Module
33
+The :mod:`manila.auth.signer` Module
34 34
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
35 35
 
36
-.. automodule:: cinder.auth.signer
36
+.. automodule:: manila.auth.signer
37 37
     :noindex:
38 38
     :members:
39 39
     :undoc-members:
@@ -43,10 +43,10 @@ The :mod:`cinder.auth.signer` Module
43 43
 Auth Manager
44 44
 ------------
45 45
 
46
-The :mod:`cinder.auth.manager` Module
46
+The :mod:`manila.auth.manager` Module
47 47
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
48 48
 
49
-.. automodule:: cinder.auth.manager
49
+.. automodule:: manila.auth.manager
50 50
     :noindex:
51 51
     :members:
52 52
     :undoc-members:
@@ -60,7 +60,7 @@ Tests
60 60
 The :mod:`auth_unittest` Module
61 61
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
62 62
 
63
-.. automodule:: cinder.tests.auth_unittest
63
+.. automodule:: manila.tests.auth_unittest
64 64
     :noindex:
65 65
     :members:
66 66
     :undoc-members:
@@ -70,7 +70,7 @@ The :mod:`auth_unittest` Module
70 70
 The :mod:`access_unittest` Module
71 71
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
72 72
 
73
-.. automodule:: cinder.tests.access_unittest
73
+.. automodule:: manila.tests.access_unittest
74 74
     :noindex:
75 75
     :members:
76 76
     :undoc-members:
@@ -80,7 +80,7 @@ The :mod:`access_unittest` Module
80 80
 The :mod:`quota_unittest` Module
81 81
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
82 82
 
83
-.. automodule:: cinder.tests.quota_unittest
83
+.. automodule:: manila.tests.quota_unittest
84 84
     :noindex:
85 85
     :members:
86 86
     :undoc-members:
@@ -90,7 +90,7 @@ The :mod:`quota_unittest` Module
90 90
 Legacy Docs
91 91
 -----------
92 92
 
93
-Cinder provides RBAC (Role-based access control) of the AWS-type APIs. We define the following roles:
93
+Manila provides RBAC (Role-based access control) of the AWS-type APIs. We define the following roles:
94 94
 
95 95
 Roles-Based Access Control of AWS-style APIs using SAML Assertions
96 96
 “Achieving FIPS 199 Moderate certification of a hybrid cloud environment using CloudAudit and declarative C.I.A. classifications”

+ 31
- 31
doc/source/devref/cinder.rst View File

@@ -18,114 +18,114 @@
18 18
 Common and Misc Libraries
19 19
 =========================
20 20
 
21
-Libraries common throughout Cinder or just ones that haven't been categorized
21
+Libraries common throughout Manila or just ones that haven't been categorized
22 22
 very well yet.
23 23
 
24 24
 
25
-The :mod:`cinder.adminclient` Module
25
+The :mod:`manila.adminclient` Module
26 26
 ----------------------------------
27 27
 
28
-.. automodule:: cinder.adminclient
28
+.. automodule:: manila.adminclient
29 29
     :noindex:
30 30
     :members:
31 31
     :undoc-members:
32 32
     :show-inheritance:
33 33
 
34 34
 
35
-The :mod:`cinder.context` Module
35
+The :mod:`manila.context` Module
36 36
 ------------------------------
37 37
 
38
-.. automodule:: cinder.context
38
+.. automodule:: manila.context
39 39
     :noindex:
40 40
     :members:
41 41
     :undoc-members:
42 42
     :show-inheritance:
43 43
 
44 44
 
45
-The :mod:`cinder.exception` Module
45
+The :mod:`manila.exception` Module
46 46
 --------------------------------
47 47
 
48
-.. automodule:: cinder.exception
48
+.. automodule:: manila.exception
49 49
     :noindex:
50 50
     :members:
51 51
     :undoc-members:
52 52
     :show-inheritance:
53 53
 
54 54
 
55
-The :mod:`cinder.flags` Module
55
+The :mod:`manila.flags` Module
56 56
 ----------------------------
57 57
 
58
-.. automodule:: cinder.flags
58
+.. automodule:: manila.flags
59 59
     :noindex:
60 60
     :members:
61 61
     :undoc-members:
62 62
     :show-inheritance:
63 63
 
64 64
 
65
-The :mod:`cinder.process` Module
65
+The :mod:`manila.process` Module
66 66
 ------------------------------
67 67
 
68
-.. automodule:: cinder.process
68
+.. automodule:: manila.process
69 69
     :noindex:
70 70
     :members:
71 71
     :undoc-members:
72 72
     :show-inheritance:
73 73
 
74 74
 
75
-The :mod:`cinder.rpc` Module
75
+The :mod:`manila.rpc` Module
76 76
 --------------------------
77 77
 
78
-.. automodule:: cinder.rpc
78
+.. automodule:: manila.rpc
79 79
     :noindex:
80 80
     :members:
81 81
     :undoc-members:
82 82
     :show-inheritance:
83 83
 
84 84
 
85
-The :mod:`cinder.server` Module
85
+The :mod:`manila.server` Module
86 86
 -----------------------------
87 87
 
88
-.. automodule:: cinder.server
88
+.. automodule:: manila.server
89 89
     :noindex:
90 90
     :members:
91 91
     :undoc-members:
92 92
     :show-inheritance:
93 93
 
94 94
 
95
-The :mod:`cinder.test` Module
95
+The :mod:`manila.test` Module
96 96
 ---------------------------
97 97
 
98
-.. automodule:: cinder.test
98
+.. automodule:: manila.test
99 99
     :noindex:
100 100
     :members:
101 101
     :undoc-members:
102 102
     :show-inheritance:  
103 103
 
104 104
 
105
-The :mod:`cinder.utils` Module
105
+The :mod:`manila.utils` Module
106 106
 ----------------------------
107 107
 
108
-.. automodule:: cinder.utils
108
+.. automodule:: manila.utils
109 109
     :noindex:
110 110
     :members:
111 111
     :undoc-members:
112 112
     :show-inheritance:
113 113
 
114 114
 
115
-The :mod:`cinder.validate` Module
115
+The :mod:`manila.validate` Module
116 116
 -------------------------------
117 117
 
118
-.. automodule:: cinder.validate
118
+.. automodule:: manila.validate
119 119
     :noindex:
120 120
     :members:
121 121
     :undoc-members:
122 122
     :show-inheritance:
123 123
 
124 124
 
125
-The :mod:`cinder.wsgi` Module
125
+The :mod:`manila.wsgi` Module
126 126
 ---------------------------
127 127
 
128
-.. automodule:: cinder.wsgi
128
+.. automodule:: manila.wsgi
129 129
     :noindex:
130 130
     :members:
131 131
     :undoc-members:
@@ -138,7 +138,7 @@ Tests
138 138
 The :mod:`declare_flags` Module
139 139
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
140 140
 
141
-.. automodule:: cinder.tests.declare_flags
141
+.. automodule:: manila.tests.declare_flags
142 142
     :noindex:
143 143
     :members:
144 144
     :undoc-members:
@@ -148,7 +148,7 @@ The :mod:`declare_flags` Module
148 148
 The :mod:`fake_flags` Module
149 149
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
150 150
 
151
-.. automodule:: cinder.tests.fake_flags
151
+.. automodule:: manila.tests.fake_flags
152 152
     :noindex:
153 153
     :members:
154 154
     :undoc-members:
@@ -158,7 +158,7 @@ The :mod:`fake_flags` Module
158 158
 The :mod:`flags_unittest` Module
159 159
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
160 160
 
161
-.. automodule:: cinder.tests.flags_unittest
161
+.. automodule:: manila.tests.flags_unittest
162 162
     :noindex:
163 163
     :members:
164 164
     :undoc-members:
@@ -168,7 +168,7 @@ The :mod:`flags_unittest` Module
168 168
 The :mod:`process_unittest` Module
169 169
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
170 170
 
171
-.. automodule:: cinder.tests.process_unittest
171
+.. automodule:: manila.tests.process_unittest
172 172
     :noindex:
173 173
     :members:
174 174
     :undoc-members:
@@ -178,7 +178,7 @@ The :mod:`process_unittest` Module
178 178
 The :mod:`real_flags` Module
179 179
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
180 180
 
181
-.. automodule:: cinder.tests.real_flags
181
+.. automodule:: manila.tests.real_flags
182 182
     :noindex:
183 183
     :members:
184 184
     :undoc-members:
@@ -188,7 +188,7 @@ The :mod:`real_flags` Module
188 188
 The :mod:`rpc_unittest` Module
189 189
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
190 190
 
191
-.. automodule:: cinder.tests.rpc_unittest
191
+.. automodule:: manila.tests.rpc_unittest
192 192
     :noindex:
193 193
     :members:
194 194
     :undoc-members:
@@ -198,7 +198,7 @@ The :mod:`rpc_unittest` Module
198 198
 The :mod:`runtime_flags` Module
199 199
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
200 200
 
201
-.. automodule:: cinder.tests.runtime_flags
201
+.. automodule:: manila.tests.runtime_flags
202 202
     :noindex:
203 203
     :members:
204 204
     :undoc-members:
@@ -208,7 +208,7 @@ The :mod:`runtime_flags` Module
208 208
 The :mod:`validator_unittest` Module
209 209
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
210 210
 
211
-.. automodule:: cinder.tests.validator_unittest
211
+.. automodule:: manila.tests.validator_unittest
212 212
     :noindex:
213 213
     :members:
214 214
     :undoc-members:

+ 8
- 8
doc/source/devref/database.rst View File

@@ -18,10 +18,10 @@
18 18
 The Database Layer
19 19
 ==================
20 20
 
21
-The :mod:`cinder.db.api` Module
21
+The :mod:`manila.db.api` Module
22 22
 -----------------------------
23 23
 
24
-.. automodule:: cinder.db.api
24
+.. automodule:: manila.db.api
25 25
     :noindex:
26 26
     :members:
27 27
     :undoc-members:
@@ -31,25 +31,25 @@ The :mod:`cinder.db.api` Module
31 31
 The Sqlalchemy Driver
32 32
 ---------------------
33 33
 
34
-The :mod:`cinder.db.sqlalchemy.api` Module
34
+The :mod:`manila.db.sqlalchemy.api` Module
35 35
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
36 36
 
37
-.. automodule:: cinder.db.sqlalchemy.api
37
+.. automodule:: manila.db.sqlalchemy.api
38 38
     :noindex:
39 39
 
40
-The :mod:`cinder.db.sqlalchemy.models` Module
40
+The :mod:`manila.db.sqlalchemy.models` Module
41 41
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
42 42
 
43
-.. automodule:: cinder.db.sqlalchemy.models
43
+.. automodule:: manila.db.sqlalchemy.models
44 44
     :noindex:
45 45
     :members:
46 46
     :undoc-members:
47 47
     :show-inheritance:
48 48
 
49
-The :mod:`cinder.db.sqlalchemy.session` Module
49
+The :mod:`manila.db.sqlalchemy.session` Module
50 50
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
51 51
 
52
-.. automodule:: cinder.db.sqlalchemy.session
52
+.. automodule:: manila.db.sqlalchemy.session
53 53
     :noindex:
54 54
     :members:
55 55
     :undoc-members:

+ 14
- 14
doc/source/devref/development.environment.rst View File

@@ -19,16 +19,16 @@ Setting Up a Development Environment
19 19
 ====================================
20 20
 
21 21
 This page describes how to setup a working Python development
22
-environment that can be used in developing cinder on Ubuntu, Fedora or
22
+environment that can be used in developing manila on Ubuntu, Fedora or
23 23
 Mac OS X. These instructions assume you're already familiar with
24 24
 git. Refer to GettingTheCode_ for additional information.
25 25
 
26 26
 .. _GettingTheCode: http://wiki.openstack.org/GettingTheCode
27 27
 
28
-Following these instructions will allow you to run the cinder unit
29
-tests. If you want to be able to run cinder (i.e., launch VM instances),
28
+Following these instructions will allow you to run the manila unit
29
+tests. If you want to be able to run manila (i.e., launch VM instances),
30 30
 you will also need to install libvirt and at least one of the
31
-`supported hypervisors`_. Running cinder is currently only supported on
31
+`supported hypervisors`_. Running manila is currently only supported on
32 32
 Linux, although you can run the unit tests on Mac OS X. See
33 33
 :doc:`../quickstart` for how to get a working version of OpenStack
34 34
 Compute running as quickly as possible.
@@ -38,10 +38,10 @@ Compute running as quickly as possible.
38 38
 Virtual environments
39 39
 --------------------
40 40
 
41
-Cinder development uses `virtualenv <http://pypi.python.org/pypi/virtualenv>`__ to track and manage Python
41
+Manila development uses `virtualenv <http://pypi.python.org/pypi/virtualenv>`__ to track and manage Python
42 42
 dependencies while in development and testing. This allows you to
43 43
 install all of the Python package dependencies in a virtual
44
-environment or "virtualenv" (a special subdirectory of your cinder
44
+environment or "virtualenv" (a special subdirectory of your manila
45 45
 directory), instead of installing the packages at the system level.
46 46
 
47 47
 .. note::
@@ -54,7 +54,7 @@ Linux Systems
54 54
 
55 55
 .. note::
56 56
 
57
-  This section is tested for Cinder on Ubuntu (12.04-64) and
57
+  This section is tested for Manila on Ubuntu (12.04-64) and
58 58
   Fedora-based (RHEL 6.1) distributions. Feel free to add notes and
59 59
   change according to your experiences or operating system.
60 60
 
@@ -82,18 +82,18 @@ Check the version of OpenSSL you have installed::
82 82
 
83 83
 If you have installed OpenSSL 1.0.0a, which can happen when installing a
84 84
 MacPorts package for OpenSSL, you will see an error when running
85
-``cinder.tests.auth_unittest.AuthTestCase.test_209_can_generate_x509``.
85
+``manila.tests.auth_unittest.AuthTestCase.test_209_can_generate_x509``.
86 86
 
87 87
 The stock version of OpenSSL that ships with Mac OS X 10.6 (OpenSSL 0.9.8l)
88
-or Mac OS X 10.7 (OpenSSL 0.9.8r) works fine with cinder.
88
+or Mac OS X 10.7 (OpenSSL 0.9.8r) works fine with manila.
89 89
 
90 90
 
91 91
 Getting the code
92 92
 ----------------
93 93
 Grab the code from GitHub::
94 94
 
95
-    git clone https://github.com/openstack/cinder.git
96
-    cd cinder
95
+    git clone https://github.com/openstack/manila.git
96
+    cd manila
97 97
 
98 98
 
99 99
 Running unit tests
@@ -127,9 +127,9 @@ by the ``tools/install_venv.py`` file into the virutalenv.
127 127
 
128 128
 If all goes well, you should get a message something like this::
129 129
 
130
-  Cinder development environment setup is complete.
130
+  Manila development environment setup is complete.
131 131
 
132
-To activate the Cinder virtualenv for the extent of your current shell session
132
+To activate the Manila virtualenv for the extent of your current shell session
133 133
 you can run::
134 134
 
135 135
      $ source .venv/bin/activate
@@ -145,7 +145,7 @@ Contributing Your Work
145 145
 Once your work is complete you may wish to contribute it to the project.  Add
146 146
 your name and email address to the ``Authors`` file, and also to the ``.mailmap``
147 147
 file if you use multiple email addresses. Your contributions can not be merged
148
-into trunk unless you are listed in the Authors file. Cinder uses the Gerrit
148
+into trunk unless you are listed in the Authors file. Manila uses the Gerrit
149 149
 code review system. For information on how to submit your branch to Gerrit,
150 150
 see GerritWorkflow_.
151 151
 

+ 12
- 12
doc/source/devref/fakes.rst View File

@@ -24,60 +24,60 @@ When the real thing isn't available and you have some development to do these
24 24
 fake implementations of various drivers let you get on with your day.
25 25
 
26 26
 
27
-The :mod:`cinder.virt.fake` Module
27
+The :mod:`manila.virt.fake` Module
28 28
 --------------------------------
29 29
 
30
-.. automodule:: cinder.virt.fake
30
+.. automodule:: manila.virt.fake
31 31
     :noindex:
32 32
     :members:
33 33
     :undoc-members:
34 34
     :show-inheritance:
35 35
 
36 36
 
37
-The :mod:`cinder.auth.fakeldap` Module
37
+The :mod:`manila.auth.fakeldap` Module
38 38
 ------------------------------------
39 39
 
40
-.. automodule:: cinder.auth.fakeldap
40
+.. automodule:: manila.auth.fakeldap
41 41
     :noindex:
42 42
     :members:
43 43
     :undoc-members:
44 44
     :show-inheritance:
45 45
     
46 46
 
47
-The :mod:`cinder.testing.fake.rabbit` Module
47
+The :mod:`manila.testing.fake.rabbit` Module
48 48
 ------------------------------------------
49 49
 
50
-.. automodule:: cinder.testing.fake.rabbit
50
+.. automodule:: manila.testing.fake.rabbit
51 51
     :noindex:
52 52
     :members:
53 53
     :undoc-members:
54 54
     :show-inheritance:
55 55
 
56 56
 
57
-The :class:`cinder.volume.driver.FakeAOEDriver` Class
57
+The :class:`manila.volume.driver.FakeAOEDriver` Class
58 58
 ---------------------------------------------------
59 59
 
60
-.. autoclass:: cinder.volume.driver.FakeAOEDriver
60
+.. autoclass:: manila.volume.driver.FakeAOEDriver
61 61
     :noindex:
62 62
     :members:
63 63
     :undoc-members:
64 64
     :show-inheritance:
65 65
 
66 66
 
67
-The :class:`cinder.tests.service_unittest.FakeManager` Class
67
+The :class:`manila.tests.service_unittest.FakeManager` Class
68 68
 ----------------------------------------------------------
69 69
 
70
-.. autoclass:: cinder.tests.service_unittest.FakeManager
70
+.. autoclass:: manila.tests.service_unittest.FakeManager
71 71
     :noindex:
72 72
     :members:
73 73
     :undoc-members:
74 74
     :show-inheritance:
75 75
 
76 76
 
77
-The :mod:`cinder.tests.api.openstack.fakes` Module
77
+The :mod:`manila.tests.api.openstack.fakes` Module
78 78
 ------------------------------------------------
79 79
 
80
-.. automodule:: cinder.tests.api.openstack.fakes
80
+.. automodule:: manila.tests.api.openstack.fakes
81 81
     :noindex:
82 82
     :members:
83 83
     :undoc-members:

+ 2
- 2
doc/source/devref/gerrit.rst View File

@@ -1,11 +1,11 @@
1 1
 Code Reviews with Gerrit
2 2
 ========================
3 3
 
4
-Cinder uses the `Gerrit`_ tool to review proposed code changes. The review site
4
+Manila uses the `Gerrit`_ tool to review proposed code changes. The review site
5 5
 is http://review.openstack.org.
6 6
 
7 7
 Gerrit is a complete replacement for Github pull requests. `All Github pull
8
-requests to the Cinder repository will be ignored`.
8
+requests to the Manila repository will be ignored`.
9 9
 
10 10
 See `Gerrit Workflow Quick Reference`_ for information about how to get
11 11
 started using Gerrit. See `Gerrit, Jenkins and Github`_ for more detailed

+ 5
- 5
doc/source/devref/il8n.rst View File

@@ -1,6 +1,6 @@
1 1
 Internationalization
2 2
 ====================
3
-cinder uses `gettext <http://docs.python.org/library/gettext.html>`_ so that
3
+manila uses `gettext <http://docs.python.org/library/gettext.html>`_ so that
4 4
 user-facing strings such as log messages appear in the appropriate
5 5
 language in different locales.
6 6
 
@@ -20,14 +20,14 @@ For example::
20 20
 
21 21
 If you do not follow the project conventions, your code may cause the
22 22
 LocalizationTestCase.test_multiple_positional_format_placeholders test to fail
23
-in cinder/tests/test_localization.py.
23
+in manila/tests/test_localization.py.
24 24
 
25 25
 The ``_()`` function is brought into the global scope by doing::
26 26
 
27
-    from cinder.openstack.common import gettextutils
28
-    gettextutils.install("cinder")
27
+    from manila.openstack.common import gettextutils
28
+    gettextutils.install("manila")
29 29
 
30
-These lines are needed in any toplevel script before any cinder modules are
30
+These lines are needed in any toplevel script before any manila modules are
31 31
 imported. If this code is missing, it may result in an error that looks like::
32 32
 
33 33
     NameError: name '_' is not defined

+ 3
- 3
doc/source/devref/index.rst View File

@@ -18,7 +18,7 @@
18 18
 Developer Guide
19 19
 ===============
20 20
 
21
-In this section you will find information on Cinder's lower level programming APIs.
21
+In this section you will find information on Manila's lower level programming APIs.
22 22
 
23 23
 
24 24
 Programming HowTos and Tutorials
@@ -31,7 +31,7 @@ Programming HowTos and Tutorials
31 31
     addmethod.openstackapi
32 32
 
33 33
 
34
-Background Concepts for Cinder
34
+Background Concepts for Manila
35 35
 ----------------------------
36 36
 .. toctree::
37 37
    :maxdepth: 3
@@ -69,7 +69,7 @@ Module Reference
69 69
    api
70 70
    scheduler
71 71
    fakes
72
-   cinder
72
+   manila
73 73
 
74 74
 
75 75
 Indices and tables

+ 17
- 17
doc/source/devref/jenkins.rst View File

@@ -1,37 +1,37 @@
1 1
 Continuous Integration with Jenkins
2 2
 ===================================
3 3
 
4
-Cinder uses a `Jenkins`_ server to automate development tasks. The Jenkins
4
+Manila uses a `Jenkins`_ server to automate development tasks. The Jenkins
5 5
 front-end is at http://jenkins.openstack.org. You must have an
6 6
 account on `Launchpad`_ to be able to access the OpenStack Jenkins site.
7 7
 
8 8
 Jenkins performs tasks such as:
9 9
 
10
-`gate-cinder-unittests`_
10
+`gate-manila-unittests`_
11 11
     Run unit tests on proposed code changes that have been reviewed.
12 12
 
13
-`gate-cinder-pep8`_
13
+`gate-manila-pep8`_
14 14
     Run PEP8 checks on proposed code changes that have been reviewed.
15 15
 
16
-`gate-cinder-merge`_
16
+`gate-manila-merge`_
17 17
     Merge reviewed code into the git repository.
18 18
 
19
-`cinder-coverage`_
19
+`manila-coverage`_
20 20
     Calculate test coverage metrics.
21 21
 
22
-`cinder-docs`_
23
-    Build this documentation and push it to http://cinder.openstack.org.
22
+`manila-docs`_
23
+    Build this documentation and push it to http://manila.openstack.org.
24 24
 
25
-`cinder-tarball`_
26
-    Do ``python setup.py sdist`` to create a tarball of the cinder code and upload
27
-    it to http://cinder.openstack.org/tarballs
25
+`manila-tarball`_
26
+    Do ``python setup.py sdist`` to create a tarball of the manila code and upload
27
+    it to http://manila.openstack.org/tarballs
28 28
 
29 29
 .. _Jenkins: http://jenkins-ci.org
30 30
 .. _Launchpad: http://launchpad.net
31
-.. _gate-cinder-merge: https://jenkins.openstack.org/view/Cinder/job/gate-cinder-merge
32
-.. _gate-cinder-pep8: https://jenkins.openstack.org/view/Cinder/job/gate-cinder-pep8
33
-.. _gate-cinder-unittests: https://jenkins.openstack.org/view/Cinder/job/gate-cinder-unittests
34
-.. _cinder-coverage: https://jenkins.openstack.org/view/Cinder/job/cinder-coverage
35
-.. _cinder-docs: https://jenkins.openstack.org/view/Cinder/job/cinder-docs
36
-.. _cinder-pylint: https://jenkins.openstack.org/job/cinder-pylint
37
-.. _cinder-tarball: https://jenkins.openstack.org/job/cinder-tarball
31
+.. _gate-manila-merge: https://jenkins.openstack.org/view/Manila/job/gate-manila-merge
32
+.. _gate-manila-pep8: https://jenkins.openstack.org/view/Manila/job/gate-manila-pep8
33
+.. _gate-manila-unittests: https://jenkins.openstack.org/view/Manila/job/gate-manila-unittests
34
+.. _manila-coverage: https://jenkins.openstack.org/view/Manila/job/manila-coverage
35
+.. _manila-docs: https://jenkins.openstack.org/view/Manila/job/manila-docs
36
+.. _manila-pylint: https://jenkins.openstack.org/job/manila-pylint
37
+.. _manila-tarball: https://jenkins.openstack.org/job/manila-tarball

+ 9
- 9
doc/source/devref/launchpad.rst View File

@@ -1,8 +1,8 @@
1 1
 Project hosting with Launchpad
2 2
 ==============================
3 3
 
4
-`Launchpad`_ hosts the Cinder project. The Cinder project homepage on Launchpad is
5
-http://launchpad.net/cinder.
4
+`Launchpad`_ hosts the Manila project. The Manila project homepage on Launchpad is
5
+http://launchpad.net/manila.
6 6
 
7 7
 Launchpad credentials
8 8
 ---------------------
@@ -21,7 +21,7 @@ Mailing list
21 21
 The mailing list email is ``openstack@lists.launchpad.net``. This is a common
22 22
 mailing list across the OpenStack projects. To participate in the mailing list:
23 23
 
24
-#. Join the `Cinder Team`_ on Launchpad.
24
+#. Join the `Manila Team`_ on Launchpad.
25 25
 #. Subscribe to the list on the `OpenStack Team`_ page on Launchpad.
26 26
 
27 27
 The mailing list archives are at https://lists.launchpad.net/openstack.
@@ -30,25 +30,25 @@ The mailing list archives are at https://lists.launchpad.net/openstack.
30 30
 Bug tracking
31 31
 ------------
32 32
 
33
-Report Cinder bugs at https://bugs.launchpad.net/cinder
33
+Report Manila bugs at https://bugs.launchpad.net/manila
34 34
 
35 35
 Feature requests (Blueprints)
36 36
 -----------------------------
37 37
 
38
-Cinder uses Launchpad Blueprints to track feature requests. Blueprints are at
39
-https://blueprints.launchpad.net/cinder.
38
+Manila uses Launchpad Blueprints to track feature requests. Blueprints are at
39
+https://blueprints.launchpad.net/manila.
40 40
 
41 41
 Technical support (Answers)
42 42
 ---------------------------
43 43
 
44
-Cinder uses Launchpad Answers to track Cinder technical support questions. The Cinder
45
-Answers page is at https://answers.launchpad.net/cinder.
44
+Manila uses Launchpad Answers to track Manila technical support questions. The Manila
45
+Answers page is at https://answers.launchpad.net/manila.
46 46
 
47 47
 Note that the `OpenStack Forums`_ (which are not hosted on Launchpad) can also
48 48
 be used for technical support requests.
49 49
 
50 50
 .. _Launchpad: http://launchpad.net
51 51
 .. _Wiki: http://wiki.openstack.org
52
-.. _Cinder Team: https://launchpad.net/~cinder
52
+.. _Manila Team: https://launchpad.net/~manila
53 53
 .. _OpenStack Team: https://launchpad.net/~openstack
54 54
 .. _OpenStack Forums: http://forums.openstack.org/

+ 10
- 10
doc/source/devref/rpc.rst View File

@@ -14,28 +14,28 @@
14 14
       License for the specific language governing permissions and limitations
15 15
       under the License.
16 16
 
17
-AMQP and Cinder
17
+AMQP and Manila
18 18
 =============
19 19
 
20
-AMQP is the messaging technology chosen by the OpenStack cloud.  The AMQP broker, either RabbitMQ or Qpid, sits between any two Cinder components and allows them to communicate in a loosely coupled fashion. More precisely, Cinder components (the compute fabric of OpenStack) use Remote Procedure Calls (RPC hereinafter) to communicate to one another; however such a paradigm is built atop the publish/subscribe paradigm so that the following benefits can be achieved:
20
+AMQP is the messaging technology chosen by the OpenStack cloud.  The AMQP broker, either RabbitMQ or Qpid, sits between any two Manila components and allows them to communicate in a loosely coupled fashion. More precisely, Manila components (the compute fabric of OpenStack) use Remote Procedure Calls (RPC hereinafter) to communicate to one another; however such a paradigm is built atop the publish/subscribe paradigm so that the following benefits can be achieved:
21 21
 
22 22
     * Decoupling between client and servant (such as the client does not need to know where the servant's reference is).
23 23
     * Full a-synchronism between client and servant (such as the client does not need the servant to run at the same time of the remote call).
24 24
     * Random balancing of remote calls (such as if more servants are up and running, one-way calls are transparently dispatched to the first available servant).
25 25
 
26
-Cinder uses direct, fanout, and topic-based exchanges. The architecture looks like the one depicted in the figure below:
26
+Manila uses direct, fanout, and topic-based exchanges. The architecture looks like the one depicted in the figure below:
27 27
 
28 28
 .. image:: /images/rpc/arch.png
29 29
    :width: 60%
30 30
 
31 31
 ..
32 32
 
33
-Cinder implements RPC (both request+response, and one-way, respectively nicknamed 'rpc.call' and 'rpc.cast') over AMQP by providing an adapter class which take cares of marshaling and unmarshaling of messages into function calls. Each Cinder service (for example Compute, Volume, etc.) create two queues at the initialization time, one which accepts messages with routing keys 'NODE-TYPE.NODE-ID' (for example compute.hostname) and another, which accepts messages with routing keys as generic 'NODE-TYPE' (for example compute). The former is used specifically when Cinder-API needs to redirect commands to a specific node like 'euca-terminate instance'. In this case, only the  compute node whose host's hypervisor is running the virtual machine can kill the instance. The API acts as a consumer when RPC calls are request/response, otherwise is acts as publisher only.
33
+Manila implements RPC (both request+response, and one-way, respectively nicknamed 'rpc.call' and 'rpc.cast') over AMQP by providing an adapter class which take cares of marshaling and unmarshaling of messages into function calls. Each Manila service (for example Compute, Volume, etc.) create two queues at the initialization time, one which accepts messages with routing keys 'NODE-TYPE.NODE-ID' (for example compute.hostname) and another, which accepts messages with routing keys as generic 'NODE-TYPE' (for example compute). The former is used specifically when Manila-API needs to redirect commands to a specific node like 'euca-terminate instance'. In this case, only the  compute node whose host's hypervisor is running the virtual machine can kill the instance. The API acts as a consumer when RPC calls are request/response, otherwise is acts as publisher only.
34 34
 
35
-Cinder RPC Mappings
35
+Manila RPC Mappings
36 36
 -----------------
37 37
 
38
-The figure below shows the internals of a message broker node (referred to as a RabbitMQ node in the diagrams) when a single instance is deployed and shared in an OpenStack cloud. Every Cinder component connects to the message broker and, depending on its personality (for example a compute node or a network node), may use the queue either as an Invoker (such as API or Scheduler) or a Worker (such as Compute, Volume or Network). Invokers and Workers do not actually exist in the Cinder object model, but we are going to use them as an abstraction for sake of clarity. An Invoker is a component that sends messages in the queuing system via two operations: 1) rpc.call and ii) rpc.cast; a Worker is a component that receives messages from the queuing system and reply accordingly to rcp.call operations.
38
+The figure below shows the internals of a message broker node (referred to as a RabbitMQ node in the diagrams) when a single instance is deployed and shared in an OpenStack cloud. Every Manila component connects to the message broker and, depending on its personality (for example a compute node or a network node), may use the queue either as an Invoker (such as API or Scheduler) or a Worker (such as Compute, Volume or Network). Invokers and Workers do not actually exist in the Manila object model, but we are going to use them as an abstraction for sake of clarity. An Invoker is a component that sends messages in the queuing system via two operations: 1) rpc.call and ii) rpc.cast; a Worker is a component that receives messages from the queuing system and reply accordingly to rcp.call operations.
39 39
 
40 40
 Figure 2 shows the following internal elements:
41 41
 
@@ -43,7 +43,7 @@ Figure 2 shows the following internal elements:
43 43
     * Direct Consumer: a Direct Consumer comes to life if (an only if) a rpc.call operation is executed; this object is instantiated and used to receive a response message from the queuing system; Every consumer connects to a unique direct-based exchange via a unique exclusive queue; its life-cycle is limited to the message delivery; the exchange and queue identifiers are determined by a UUID generator, and are marshaled in the message sent by the Topic Publisher (only rpc.call operations).
44 44
     * Topic Consumer: a Topic Consumer comes to life as soon as a Worker is instantiated and exists throughout its life-cycle; this object is used to receive messages from the queue and it invokes the appropriate action as defined by the Worker role. A Topic Consumer connects to the same topic-based exchange either via a shared queue or via a unique exclusive queue. Every Worker has two topic consumers, one that is addressed only during rpc.cast operations (and it connects to a shared queue whose exchange key is 'topic') and the other that is addressed only during rpc.call operations (and it connects to a unique queue whose exchange key is 'topic.host').
45 45
     * Direct Publisher: a Direct Publisher comes to life only during rpc.call operations and it is instantiated to return the message required by the request/response operation. The object connects to a direct-based exchange whose identity is dictated by the incoming message.
46
-    * Topic Exchange: The Exchange is a routing table that exists in the context of a virtual host (the multi-tenancy mechanism provided by Qpid or RabbitMQ); its type (such as topic vs. direct) determines the routing policy; a message broker node will have only one topic-based exchange for every topic in Cinder.
46
+    * Topic Exchange: The Exchange is a routing table that exists in the context of a virtual host (the multi-tenancy mechanism provided by Qpid or RabbitMQ); its type (such as topic vs. direct) determines the routing policy; a message broker node will have only one topic-based exchange for every topic in Manila.
47 47
     * Direct Exchange: this is a routing table that is created during rpc.call operations; there are many instances of this kind of exchange throughout the life-cycle of a message broker node, one for each rpc.call invoked.
48 48
     * Queue Element: A Queue is a message bucket. Messages are kept in the queue until a Consumer (either Topic or Direct Consumer) connects to the queue and fetch it. Queues can be shared or can be exclusive. Queues whose routing key is 'topic' are shared amongst Workers of the same personality.
49 49
 
@@ -88,10 +88,10 @@ At any given time the load of a message broker node running either Qpid or Rabbi
88 88
     * Throughput of API calls: the number of API calls (more precisely rpc.call ops) being served by the OpenStack cloud dictates the number of direct-based exchanges, related queues and direct consumers connected to them.
89 89
     * Number of Workers: there is one queue shared amongst workers with the same personality; however there are as many exclusive queues as the number of workers; the number of workers dictates also the number of routing keys within the topic-based exchange, which is shared amongst all workers.
90 90
 
91
-The figure below shows the status of a RabbitMQ node after Cinder components' bootstrap in a test environment. Exchanges and queues being created by Cinder components are:
91
+The figure below shows the status of a RabbitMQ node after Manila components' bootstrap in a test environment. Exchanges and queues being created by Manila components are:
92 92
 
93 93
     * Exchanges
94
-       1. cinder (topic exchange)
94
+       1. manila (topic exchange)
95 95
     * Queues
96 96
        1. compute.phantom (phantom is hostname)
97 97
        2. compute
@@ -110,7 +110,7 @@ The figure below shows the status of a RabbitMQ node after Cinder components' bo
110 110
 RabbitMQ Gotchas
111 111
 ----------------
112 112
 
113
-Cinder uses Kombu to connect to the RabbitMQ environment. Kombu is a Python library that in turn uses AMQPLib, a library that implements the standard AMQP 0.8 at the time of writing. When using Kombu, Invokers and Workers need the following parameters in order to instantiate a Connection object that connects to the RabbitMQ server (please note that most of the following material can be also found in the Kombu documentation; it has been summarized and revised here for sake of clarity):
113
+Manila uses Kombu to connect to the RabbitMQ environment. Kombu is a Python library that in turn uses AMQPLib, a library that implements the standard AMQP 0.8 at the time of writing. When using Kombu, Invokers and Workers need the following parameters in order to instantiate a Connection object that connects to the RabbitMQ server (please note that most of the following material can be also found in the Kombu documentation; it has been summarized and revised here for sake of clarity):
114 114
 
115 115
     * Hostname: The hostname to the AMQP server.
116 116
     * Userid: A valid username used to authenticate to the server.

+ 7
- 7
doc/source/devref/scheduler.rst View File

@@ -18,30 +18,30 @@
18 18
 Scheduler
19 19
 =========
20 20
 
21
-The :mod:`cinder.scheduler.manager` Module
21
+The :mod:`manila.scheduler.manager` Module
22 22
 ----------------------------------------
23 23
 
24
-.. automodule:: cinder.scheduler.manager
24
+.. automodule:: manila.scheduler.manager
25 25
     :noindex:
26 26
     :members:
27 27
     :undoc-members:
28 28
     :show-inheritance:
29 29
 
30 30
 
31
-The :mod:`cinder.scheduler.driver` Module
31
+The :mod:`manila.scheduler.driver` Module
32 32
 ---------------------------------------
33 33
 
34
-.. automodule:: cinder.scheduler.driver
34
+.. automodule:: manila.scheduler.driver
35 35
     :noindex:
36 36
     :members:
37 37
     :undoc-members:
38 38
     :show-inheritance:
39 39
 
40 40
 
41
-The :mod:`cinder.scheduler.simple` Driver
41
+The :mod:`manila.scheduler.simple` Driver
42 42
 ---------------------------------------
43 43
 
44
-.. automodule:: cinder.scheduler.simple
44
+.. automodule:: manila.scheduler.simple
45 45
     :noindex:
46 46
     :members:
47 47
     :undoc-members:
@@ -54,7 +54,7 @@ Tests
54 54
 The :mod:`scheduler_unittest` Module
55 55
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56 56
 
57
-.. automodule:: cinder.tests.scheduler_unittest
57
+.. automodule:: manila.tests.scheduler_unittest
58 58
     :noindex:
59 59
     :members:
60 60
     :undoc-members:

+ 5
- 5
doc/source/devref/services.rst View File

@@ -20,25 +20,25 @@
20 20
 Services, Managers and Drivers
21 21
 ==============================
22 22
 
23
-The responsibilities of Services, Managers, and Drivers, can be a bit confusing to people that are new to cinder.  This document attempts to outline the division of responsibilities to make understanding the system a little bit easier.
23
+The responsibilities of Services, Managers, and Drivers, can be a bit confusing to people that are new to manila.  This document attempts to outline the division of responsibilities to make understanding the system a little bit easier.
24 24
 
25 25
 Currently, Managers and Drivers are specified by flags and loaded using utils.load_object().  This method allows for them to be implemented as singletons, classes, modules or objects.  As long as the path specified by the flag leads to an object (or a callable that returns an object) that responds to getattr, it should work as a manager or driver.
26 26
 
27 27
 
28
-The :mod:`cinder.service` Module
28
+The :mod:`manila.service` Module
29 29
 ------------------------------
30 30
 
31
-.. automodule:: cinder.service
31
+.. automodule:: manila.service
32 32
     :noindex:
33 33
     :members:
34 34
     :undoc-members:
35 35
     :show-inheritance:
36 36
 
37 37
 
38
-The :mod:`cinder.manager` Module
38
+The :mod:`manila.manager` Module
39 39
 ------------------------------
40 40
 
41
-.. automodule:: cinder.manager
41
+.. automodule:: manila.manager
42 42
     :noindex:
43 43
     :members:
44 44
     :undoc-members:

+ 1
- 1
doc/source/devref/threading.rst View File

@@ -46,6 +46,6 @@ block, but this implementation resulted in a `bug`_ and was removed.
46 46
 See this `mailing list thread`_ for a discussion of this issue, including
47 47
 a discussion of the `impact on performance`_.
48 48
 
49
-.. _bug: https://bugs.launchpad.net/cinder/+bug/838581
49
+.. _bug: https://bugs.launchpad.net/manila/+bug/838581
50 50
 .. _mailing list thread: https://lists.launchpad.net/openstack/msg08118.html
51 51
 .. _impact on performance: https://lists.launchpad.net/openstack/msg08217.html

+ 9
- 9
doc/source/devref/unit_tests.rst View File

@@ -1,7 +1,7 @@
1 1
 Unit Tests
2 2
 ==========
3 3
 
4
-Cinder contains a suite of unit tests, in the cinder/tests directory.
4
+Manila contains a suite of unit tests, in the manila/tests directory.
5 5
 
6 6
 Any proposed code change will be automatically rejected by the OpenStack
7 7
 Jenkins server [#f1]_ if the change causes unit test failures.
@@ -28,7 +28,7 @@ flags by doing::
28 28
 This will show the following help information::
29 29
 
30 30
     Usage: ./run_tests.sh [OPTION]...
31
-    Run Cinder's test suite(s)
31
+    Run Manila's test suite(s)
32 32
 
33 33
       -V, --virtual-env        Always use virtualenv.  Install automatically if not present
34 34
       -N, --no-virtual-env     Don't use virtualenv.  Run tests in local environment
@@ -55,21 +55,21 @@ Running a subset of tests
55 55
 Instead of running all tests, you can specify an individual directory, file,
56 56
 class, or method that contains test code.
57 57
 
58
-To run the tests in the ``cinder/tests/scheduler`` directory::
58
+To run the tests in the ``manila/tests/scheduler`` directory::
59 59
 
60 60
     ./run_tests.sh scheduler
61 61
 
62
-To run the tests in the ``cinder/tests/test_libvirt.py`` file::
62
+To run the tests in the ``manila/tests/test_libvirt.py`` file::
63 63
 
64 64
     ./run_tests.sh test_libvirt
65 65
 
66 66
 To run the tests in the `HostStateTestCase` class in
67
-``cinder/tests/test_libvirt.py``::
67
+``manila/tests/test_libvirt.py``::
68 68
 
69 69
     ./run_tests.sh test_libvirt:HostStateTestCase
70 70
 
71 71
 To run the `ToPrimitiveTestCase.test_dict` test method in
72
-``cinder/tests/test_utils.py``::
72
+``manila/tests/test_utils.py``::
73 73
 
74 74
     ./run_tests.sh test_utils:ToPrimitiveTestCase.test_dict
75 75
 
@@ -128,7 +128,7 @@ exists it can be reused by using the flag::
128 128
     -n, --no-recreate-db
129 129
 
130 130
 Reusing an existing database may cause tests to fail if the schema has
131
-changed. If any files in the ``cinder/db/sqlalchemy`` have changed, it's a good
131
+changed. If any files in the ``manila/db/sqlalchemy`` have changed, it's a good
132 132
 idea to recreate the test database.
133 133
 
134 134
 Gotchas
@@ -139,7 +139,7 @@ Gotchas
139 139
 If you are running the unit tests from a shared folder, you may see tests start
140 140
 to fail or stop completely as a result of Python lockfile issues [#f4]_. You
141 141
 can get around this by manually setting or updating the following line in
142
-``cinder/tests/fake_flags.py``::
142
+``manila/tests/fake_flags.py``::
143 143
 
144 144
     FLAGS['lock_path'].SetDefault('/tmp')
145 145
 
@@ -156,4 +156,4 @@ a shared folder.
156 156
 .. [#f3] There is an effort underway to use a fake DB implementation for the
157 157
    unit tests. See https://lists.launchpad.net/openstack/msg05604.html
158 158
 
159
-.. [#f4] See Vish's comment in this bug report: https://bugs.launchpad.net/cinder/+bug/882933
159
+.. [#f4] See Vish's comment in this bug report: https://bugs.launchpad.net/manila/+bug/882933

+ 7
- 7
doc/source/devref/volume.rst View File

@@ -21,19 +21,19 @@ Storage Volumes, Disks
21 21
 .. todo:: rework after iSCSI merge (see 'Old Docs') (todd or vish)
22 22
 
23 23
 
24
-The :mod:`cinder.volume.manager` Module
24
+The :mod:`manila.volume.manager` Module
25 25
 -------------------------------------
26 26
 
27
-.. automodule:: cinder.volume.manager
27
+.. automodule:: manila.volume.manager
28 28
     :noindex:
29 29
     :members:
30 30
     :undoc-members:
31 31
     :show-inheritance:
32 32
 
33
-The :mod:`cinder.volume.driver` Module
33
+The :mod:`manila.volume.driver` Module
34 34
 -------------------------------------
35 35
 
36
-.. automodule:: cinder.volume.driver
36
+.. automodule:: manila.volume.driver
37 37
     :noindex:
38 38
     :members:
39 39
     :undoc-members:
@@ -46,7 +46,7 @@ Tests
46 46
 The :mod:`volume_unittest` Module
47 47
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
48 48
 
49
-.. automodule:: cinder.tests.volume_unittest
49
+.. automodule:: manila.tests.volume_unittest
50 50
     :noindex:
51 51
     :members:
52 52
     :undoc-members:
@@ -55,9 +55,9 @@ The :mod:`volume_unittest` Module
55 55
 Old Docs
56 56
 --------
57 57
 
58
-Cinder uses iSCSI to export storage volumes from multiple storage nodes. These iSCSI exports are attached (using libvirt) directly to running instances.
58
+Manila uses iSCSI to export storage volumes from multiple storage nodes. These iSCSI exports are attached (using libvirt) directly to running instances.
59 59
 
60
-Cinder volumes are exported over the primary system VLAN (usually VLAN 1), and not over individual VLANs.
60
+Manila volumes are exported over the primary system VLAN (usually VLAN 1), and not over individual VLANs.
61 61
 
62 62
 The underlying volumes by default are LVM logical volumes, created on demand within a single large volume group.
63 63
 

+ 2
- 2
doc/source/images/rpc/arch.svg View File

@@ -139,14 +139,14 @@
139 139
 			<text x="0.41" y="409.22" class="st6" v:langID="2057"><v:paragraph v:horizAlign="1"/><v:tabList/>http</text>		</g>
140 140
 		<g id="shape11-37" v:mID="11" v:groupContext="shape" transform="translate(0.24,-314.457)">
141 141
 			<title>Circle</title>
142
-			<desc>Cinder-Manage</desc>
142
+			<desc>Manila-Manage</desc>
143 143
 			<v:userDefs>
144 144
 				<v:ud v:nameU="visVersion" v:val="VT0(11):26"/>
145 145
 			</v:userDefs>
146 146
 			<v:textBlock v:margins="rect(4,4,4,4)" v:tabSpace="42.5197"/>
147 147
 			<v:textRect cx="42.5197" cy="343.043" width="85.04" height="28.3465"/>
148 148
 			<path d="M0 343.04 A42.5197 14.1732 0 0 1 85.04 343.04 A42.5197 14.1732 0 0 1 0 343.04 Z" class="st7"/>
149
-			<text x="4.83" y="346.64" class="st8" v:langID="2057"><v:paragraph v:horizAlign="1"/><v:tabList/>Cinder-Manage</text>		</g>
149
+			<text x="4.83" y="346.64" class="st8" v:langID="2057"><v:paragraph v:horizAlign="1"/><v:tabList/>Manila-Manage</text>		</g>
150 150
 		<g id="shape12-40" v:mID="12" v:groupContext="shape" transform="translate(0.24,-101.858)">
151 151
 			<title>Circle.15</title>
152 152
 			<desc>Euca2ools</desc>

+ 5
- 5
doc/source/index.rst View File

@@ -15,20 +15,20 @@
15 15
       License for the specific language governing permissions and limitations
16 16
       under the License.
17 17
 
18
-Welcome to Cinder's developer documentation!
18
+Welcome to Manila's developer documentation!
19 19
 ==========================================
20 20
 
21
-Cinder is an OpenStack project to provide "block storage as a service".
21
+Manila is an OpenStack project to provide "block storage as a service".
22 22
 
23 23
 * **Component based architecture**: Quickly add new behaviors
24 24
 * **Highly available**: Scale to very serious workloads
25 25
 * **Fault-Tolerant**: Isolated processes avoid cascading failures
26 26
 * **Recoverable**: Failures should be easy to diagnose, debug, and rectify
27 27
 * **Open Standards**: Be a reference implementation for a community-driven api
28
-* **API Compatibility**: Cinder strives to provide API-compatible with popular systems like Amazon EC2
28
+* **API Compatibility**: Manila strives to provide API-compatible with popular systems like Amazon EC2
29 29
 
30 30
 This documentation is generated by the Sphinx toolkit and lives in the source
31
-tree. Additional draft and project documentation on Cinder and other components of OpenStack can
31
+tree. Additional draft and project documentation on Manila and other components of OpenStack can
32 32
 be found on the `OpenStack wiki`_. Cloud administrators, refer to `docs.openstack.org`_.
33 33
 
34 34
 .. _`OpenStack wiki`: http://wiki.openstack.org
@@ -46,7 +46,7 @@ Developer Docs
46 46
 API Extensions
47 47
 ==============
48 48
 
49
-Go to http://api.openstack.org for information about Cinder API extensions.
49
+Go to http://api.openstack.org for information about Manila API extensions.
50 50
 
51 51
 Outstanding Documentation Tasks
52 52
 ===============================

+ 77
- 77
doc/source/man/cinder-manage.rst View File

@@ -1,5 +1,5 @@
1 1
 ===========
2
-cinder-manage
2
+manila-manage
3 3
 ===========
4 4
 
5 5
 ------------------------------------------------------
@@ -16,195 +16,195 @@ control and manage cloud computer instances and images
16 16
 SYNOPSIS
17 17
 ========
18 18
 
19
-  cinder-manage <category> <action> [<args>]
19
+  manila-manage <category> <action> [<args>]
20 20
 
21 21
 DESCRIPTION
22 22
 ===========
23 23
 
24
-cinder-manage controls cloud computing instances by managing cinder users, cinder projects, cinder roles, shell selection, vpn connections, and floating IP address configuration. More information about OpenStack Cinder is at http://cinder.openstack.org.
24
+manila-manage controls cloud computing instances by managing manila users, manila projects, manila roles, shell selection, vpn connections, and floating IP address configuration. More information about OpenStack Manila is at http://manila.openstack.org.
25 25
 
26 26
 OPTIONS
27 27
 =======
28 28
 
29
-The standard pattern for executing a cinder-manage command is:
30
-``cinder-manage <category> <command> [<args>]``
29
+The standard pattern for executing a manila-manage command is:
30
+``manila-manage <category> <command> [<args>]``
31 31
 
32 32
 For example, to obtain a list of all projects:
33
-``cinder-manage project list``
33
+``manila-manage project list``
34 34
 
35 35
 Run without arguments to see a list of available command categories:
36
-``cinder-manage``
36
+``manila-manage``
37 37
 
38 38
 Categories are user, project, role, shell, vpn, and floating. Detailed descriptions are below.
39 39
 
40 40
 You can also run with a category argument such as user to see a list of all commands in that category:
41
-``cinder-manage user``
41
+``manila-manage user``
42 42
 
43
-These sections describe the available categories and arguments for cinder-manage.
43
+These sections describe the available categories and arguments for manila-manage.
44 44
 
45
-Cinder Db
45
+Manila Db
46 46
 ~~~~~~~
47 47
 
48
-``cinder-manage db version``
48
+``manila-manage db version``
49 49
 
50 50
     Print the current database version.
51 51
 
52
-``cinder-manage db sync``
52
+``manila-manage db sync``
53 53
 
54 54
     Sync the database up to the most recent version. This is the standard way to create the db as well.
55 55
 
56
-Cinder User
56
+Manila User
57 57
 ~~~~~~~~~
58 58
 
59
-``cinder-manage user admin <username>``
59
+``manila-manage user admin <username>``
60 60
 
61 61
     Create an admin user with the name <username>.
62 62
 
63
-``cinder-manage user create <username>``
63
+``manila-manage user create <username>``
64 64
 
65 65
     Create a normal user with the name <username>.
66 66
 
67
-``cinder-manage user delete <username>``
67
+``manila-manage user delete <username>``
68 68
 
69 69
     Delete the user with the name <username>.
70 70
 
71
-``cinder-manage user exports <username>``
71
+``manila-manage user exports <username>``
72 72
 
73 73
     Outputs a list of access key and secret keys for user to the screen
74 74
 
75
-``cinder-manage user list``
75
+``manila-manage user list``
76 76
 
77 77
     Outputs a list of all the user names to the screen.
78 78
 
79
-``cinder-manage user modify <accesskey> <secretkey> <admin?T/F>``
79
+``manila-manage user modify <accesskey> <secretkey> <admin?T/F>``
80 80
 
81 81
     Updates the indicated user keys, indicating with T or F if the user is an admin user. Leave any argument blank if you do not want to update it.
82 82
 
83
-Cinder Project
83
+Manila Project
84 84
 ~~~~~~~~~~~~
85 85
 
86
-``cinder-manage project add <projectname>``
86
+``manila-manage project add <projectname>``
87 87
 
88
-    Add a cinder project with the name <projectname> to the database.
88
+    Add a manila project with the name <projectname> to the database.
89 89
 
90
-``cinder-manage project create <projectname>``
90
+``manila-manage project create <projectname>``
91 91
 
92
-    Create a new cinder project with the name <projectname> (you still need to do cinder-manage project add <projectname> to add it to the database).
92
+    Create a new manila project with the name <projectname> (you still need to do manila-manage project add <projectname> to add it to the database).
93 93
 
94
-``cinder-manage project delete <projectname>``
94
+``manila-manage project delete <projectname>``
95 95
 
96
-    Delete a cinder project with the name <projectname>.
96
+    Delete a manila project with the name <projectname>.
97 97
 
98
-``cinder-manage project environment <projectname> <username>``
98
+``manila-manage project environment <projectname> <username>``
99 99
 
100
-    Exports environment variables for the named project to a file named cinderrc.
100
+    Exports environment variables for the named project to a file named manilarc.
101 101
 
102
-``cinder-manage project list``
102
+``manila-manage project list``
103 103
 
104 104
     Outputs a list of all the projects to the screen.
105 105
 
106
-``cinder-manage project quota <projectname>``
106
+``manila-manage project quota <projectname>``
107 107
 
108 108
     Outputs the size and specs of the project's instances including gigabytes, instances, floating IPs, volumes, and cores.
109 109
 
110
-``cinder-manage project remove <projectname>``
110
+``manila-manage project remove <projectname>``
111 111
 
112 112
     Deletes the project with the name <projectname>.
113 113
 
114
-``cinder-manage project zipfile``
114
+``manila-manage project zipfile``
115 115
 
116
-    Compresses all related files for a created project into a zip file cinder.zip.
116
+    Compresses all related files for a created project into a zip file manila.zip.
117 117
 
118
-Cinder Role
118
+Manila Role
119 119
 ~~~~~~~~~
120 120
 
121
-``cinder-manage role add <username> <rolename> <(optional) projectname>``
121
+``manila-manage role add <username> <rolename> <(optional) projectname>``
122 122
 
123 123
     Add a user to either a global or project-based role with the indicated <rolename> assigned to the named user. Role names can be one of the following five roles: cloudadmin, itsec, sysadmin, netadmin, developer. If you add the project name as the last argument then the role is assigned just for that project, otherwise the user is assigned the named role for all projects.
124 124
 
125
-``cinder-manage role has <username> <projectname>``
125
+``manila-manage role has <username> <projectname>``
126 126
     Checks the user or project and responds with True if the user has a global role with a particular project.
127 127
 
128
-``cinder-manage role remove <username> <rolename>``
128
+``manila-manage role remove <username> <rolename>``
129 129
     Remove the indicated role from the user.
130 130
 
131
-Cinder Logs
131
+Manila Logs
132 132
 ~~~~~~~~~
133 133
 
134
-``cinder-manage logs errors``
134
+``manila-manage logs errors``
135 135
 
136
-    Displays cinder errors from log files.
136
+    Displays manila errors from log files.
137 137
 
138
-``cinder-manage logs syslog <number>``
138
+``manila-manage logs syslog <number>``
139 139
 
140
-    Displays cinder alerts from syslog.
140
+    Displays manila alerts from syslog.
141 141
 
142
-Cinder Shell
142
+Manila Shell
143 143
 ~~~~~~~~~~
144 144
 
145
-``cinder-manage shell bpython``
145
+``manila-manage shell bpython``
146 146
 
147 147
     Starts a new bpython shell.
148 148
 
149
-``cinder-manage shell ipython``
149
+``manila-manage shell ipython``
150 150
 
151 151
     Starts a new ipython shell.
152 152
 
153
-``cinder-manage shell python``
153
+``manila-manage shell python``
154 154
 
155 155
     Starts a new python shell.
156 156
 
157
-``cinder-manage shell run``
157
+``manila-manage shell run``
158 158
 
159 159
     Starts a new shell using python.
160 160
 
161
-``cinder-manage shell script <path/scriptname>``
161
+``manila-manage shell script <path/scriptname>``
162 162
 
163 163
     Runs the named script from the specified path with flags set.
164 164
 
165
-Cinder VPN
165
+Manila VPN
166 166
 ~~~~~~~~
167 167
 
168
-``cinder-manage vpn list``
168
+``manila-manage vpn list``
169 169
 
170 170
     Displays a list of projects, their IP prot numbers, and what state they're in.
171 171
 
172
-``cinder-manage vpn run <projectname>``
172
+``manila-manage vpn run <projectname>``
173 173
 
174 174
     Starts the VPN for the named project.
175 175
 
176
-``cinder-manage vpn spawn``
176
+``manila-manage vpn spawn``
177 177
 
178 178
     Runs all VPNs.
179 179
 
180
-Cinder Floating IPs
180
+Manila Floating IPs
181 181
 ~~~~~~~~~~~~~~~~~
182 182
 
183
-``cinder-manage floating create <ip_range> [--pool <pool>] [--interface <interface>]``
183
+``manila-manage floating create <ip_range> [--pool <pool>] [--interface <interface>]``
184 184
 
185 185
     Creates floating IP addresses for the given range, optionally specifying
186 186
     a floating pool and a network interface.
187 187
 
188
-``cinder-manage floating delete <ip_range>``
188
+``manila-manage floating delete <ip_range>``
189 189
 
190 190
     Deletes floating IP addresses in the range given.
191 191
 
192
-``cinder-manage floating list``
192
+``manila-manage floating list``
193 193
 
194 194
     Displays a list of all floating IP addresses.
195 195
 
196
-Cinder Flavor
196
+Manila Flavor
197 197
 ~~~~~~~~~~~
198 198
 
199
-``cinder-manage flavor list``
199
+``manila-manage flavor list``
200 200
 
201 201
     Outputs a list of all active flavors to the screen.
202 202
 
203
-``cinder-manage flavor list --all``
203
+``manila-manage flavor list --all``
204 204
 
205 205
     Outputs a list of all flavors (active and inactive) to the screen.
206 206
 
207
-``cinder-manage flavor create <name> <memory> <vCPU> <local_storage> <flavorID> <(optional) swap> <(optional) RXTX Quota> <(optional) RXTX Cap>``
207
+``manila-manage flavor create <name> <memory> <vCPU> <local_storage> <flavorID> <(optional) swap> <(optional) RXTX Quota> <(optional) RXTX Cap>``
208 208
 
209 209
     creates a flavor with the following positional arguments:
210 210
      * memory (expressed in megabytes)
@@ -215,67 +215,67 @@ Cinder Flavor
215 215
      * RXTX quotas (expressed in gigabytes, defaults to zero, optional)
216 216
      * RXTX cap (expressed in gigabytes, defaults to zero, optional)
217 217
 
218
-``cinder-manage flavor delete <name>``
218
+``manila-manage flavor delete <name>``
219 219
 
220 220
     Delete the flavor with the name <name>. This marks the flavor as inactive and cannot be launched. However, the record stays in the database for archival and billing purposes.
221 221
 
222
-``cinder-manage flavor delete <name> --purge``
222
+``manila-manage flavor delete <name> --purge``
223 223
 
224 224
     Purges the flavor with the name <name>. This removes this flavor from the database.
225 225
 
226
-Cinder Instance_type
226
+Manila Instance_type
227 227
 ~~~~~~~~~~~~~~~~~~
228 228
 
229
-The instance_type command is provided as an alias for the flavor command. All the same subcommands and arguments from cinder-manage flavor can be used.
229
+The instance_type command is provided as an alias for the flavor command. All the same subcommands and arguments from manila-manage flavor can be used.
230 230
 
231
-Cinder Images
231
+Manila Images
232 232
 ~~~~~~~~~~~
233 233
 
234
-``cinder-manage image image_register <path> <owner>``
234
+``manila-manage image image_register <path> <owner>``
235 235
 
236 236
     Registers an image with the image service.
237 237
 
238
-``cinder-manage image kernel_register <path> <owner>``
238
+``manila-manage image kernel_register <path> <owner>``
239 239
 
240 240
     Registers a kernel with the image service.
241 241
 
242
-``cinder-manage image ramdisk_register <path> <owner>``
242
+``manila-manage image ramdisk_register <path> <owner>``
243 243
 
244 244
     Registers a ramdisk with the image service.
245 245
 
246
-``cinder-manage image all_register <image_path> <kernel_path> <ramdisk_path> <owner>``
246
+``manila-manage image all_register <image_path> <kernel_path> <ramdisk_path> <owner>``
247 247
 
248 248
     Registers an image kernel and ramdisk with the image service.
249 249
 
250
-``cinder-manage image convert <directory>``
250
+``manila-manage image convert <directory>``
251 251
 
252 252
     Converts all images in directory from the old (Bexar) format to the new format.
253 253
 
254
-Cinder VM
254
+Manila VM
255 255
 ~~~~~~~~~~~
256 256
 
257
-``cinder-manage vm list [host]``
257
+``manila-manage vm list [host]``
258 258
     Show a list of all instances. Accepts optional hostname (to show only instances on specific host).
259 259
 
260
-``cinder-manage live-migration <ec2_id> <destination host name>``
261
-    Live migrate instance from current host to destination host. Requires instance id (which comes from euca-describe-instance) and destination host name (which can be found from cinder-manage service list).
260
+``manila-manage live-migration <ec2_id> <destination host name>``
261
+    Live migrate instance from current host to destination host. Requires instance id (which comes from euca-describe-instance) and destination host name (which can be found from manila-manage service list).
262 262
 
263 263
 
264 264
 FILES
265 265
 ========
266 266
 
267
-The cinder-manage.conf file contains configuration information in the form of python-gflags.
267
+The manila-manage.conf file contains configuration information in the form of python-gflags.
268 268
 
269 269
 SEE ALSO
270 270
 ========
271 271
 
272
-* `OpenStack Cinder <http://cinder.openstack.org>`__
272
+* `OpenStack Manila <http://manila.openstack.org>`__
273 273
 * `OpenStack Swift <http://swift.openstack.org>`__
274 274
 
275 275
 BUGS
276 276
 ====
277 277
 
278
-* Cinder is sourced in Launchpad so you can view current bugs at `OpenStack Cinder <http://cinder.openstack.org>`__
278
+* Manila is sourced in Launchpad so you can view current bugs at `OpenStack Manila <http://manila.openstack.org>`__
279 279
 
280 280
 
281 281
 

+ 6
- 6
manila.egg-info/PKG-INFO View File

@@ -6,27 +6,27 @@ Home-page: http://www.openstack.org/
6 6
 Author: OpenStack
7 7
 Author-email: openstack-dev@lists.openstack.org
8 8
 License: UNKNOWN
9
-Description: The Choose Your Own Adventure README for Cinder
9
+Description: The Choose Your Own Adventure README for Manila
10 10
         ===============================================
11 11
         
12 12
         You have come across a storage service for an open cloud computing service.
13
-        It has identified itself as "Cinder."   It was abstracted from the Nova project.
13
+        It has identified itself as "Manila."   It was abstracted from the Nova project.
14 14
         
15 15
         To monitor it from a distance: follow `@openstack <http://twitter.com/openstack>`_ on twitter.
16 16
         
17 17
         To tame it for use in your own cloud: read http://docs.openstack.org
18 18
         
19
-        To study its anatomy: read http://cinder.openstack.org
19
+        To study its anatomy: read http://manila.openstack.org
20 20
         
21
-        To dissect it in detail: visit http://github.com/openstack/cinder
21
+        To dissect it in detail: visit http://github.com/openstack/manila
22 22
         
23
-        To taunt it with its weaknesses: use http://bugs.launchpad.net/cinder
23
+        To taunt it with its weaknesses: use http://bugs.launchpad.net/manila
24 24
         
25 25
         To watch it: http://jenkins.openstack.org
26 26
         
27 27
         To hack at it: read HACKING
28 28
         
29
-        To cry over its pylint problems: http://jenkins.openstack.org/job/cinder-pylint/violations
29
+        To cry over its pylint problems: http://jenkins.openstack.org/job/manila-pylint/violations
30 30
         
31 31
         
32 32
 Platform: UNKNOWN

+ 463
- 463
manila.egg-info/SOURCES.txt View File

@@ -11,457 +11,457 @@ run_tests.sh
11 11
 setup.cfg
12 12
 setup.py
13 13
 tox.ini
14
-bin/cinder-all
15
-bin/cinder-api
16
-bin/cinder-backup
17
-bin/cinder-clear-rabbit-queues
18
-bin/cinder-manage
19
-bin/cinder-rootwrap
20
-bin/cinder-rpc-zmq-receiver
21
-bin/cinder-scheduler
22
-bin/cinder-share
23
-bin/cinder-volume
24
-bin/cinder-volume-usage-audit
25
-cinder/__init__.py
26
-cinder/context.py
27
-cinder/exception.py
28
-cinder/flags.py
29
-cinder/manager.py
30
-cinder/policy.py
31
-cinder/quota.py
32
-cinder/service.py
33
-cinder/test.py
34
-cinder/utils.py
35
-cinder/version.py
36
-cinder/wsgi.py
37
-cinder/api/__init__.py
38
-cinder/api/auth.py
39
-cinder/api/common.py
40
-cinder/api/extensions.py
41
-cinder/api/sizelimit.py
42
-cinder/api/urlmap.py
43
-cinder/api/versions.py
44
-cinder/api/xmlutil.py
45
-cinder/api/contrib/__init__.py
46
-cinder/api/contrib/admin_actions.py
47
-cinder/api/contrib/backups.py
48
-cinder/api/contrib/extended_snapshot_attributes.py
49
-cinder/api/contrib/hosts.py
50
-cinder/api/contrib/image_create.py
51
-cinder/api/contrib/quota_classes.py
52
-cinder/api/contrib/quotas.py
53
-cinder/api/contrib/services.py
54
-cinder/api/contrib/share_actions.py
55
-cinder/api/contrib/share_snapshots.py
56
-cinder/api/contrib/shares.py
57
-cinder/api/contrib/types_extra_specs.py
58
-cinder/api/contrib/types_manage.py
59
-cinder/api/contrib/volume_actions.py
60
-cinder/api/contrib/volume_host_attribute.py
61
-cinder/api/contrib/volume_image_metadata.py
62
-cinder/api/contrib/volume_tenant_attribute.py
63
-cinder/api/middleware/__init__.py
64
-cinder/api/middleware/auth.py
65
-cinder/api/middleware/fault.py
66
-cinder/api/middleware/sizelimit.py
67
-cinder/api/openstack/__init__.py
68
-cinder/api/openstack/urlmap.py
69
-cinder/api/openstack/wsgi.py
70
-cinder/api/openstack/volume/__init__.py
71
-cinder/api/openstack/volume/versions.py
72
-cinder/api/schemas/atom-link.rng
73
-cinder/api/schemas/v1.1/extension.rng
74
-cinder/api/schemas/v1.1/extensions.rng
75
-cinder/api/schemas/v1.1/limits.rng
76
-cinder/api/schemas/v1.1/metadata.rng
77
-cinder/api/v1/__init__.py
78
-cinder/api/v1/limits.py
79
-cinder/api/v1/router.py
80
-cinder/api/v1/snapshot_metadata.py
81
-cinder/api/v1/snapshots.py
82
-cinder/api/v1/types.py
83
-cinder/api/v1/volume_metadata.py
84
-cinder/api/v1/volumes.py
85
-cinder/api/v2/__init__.py
86
-cinder/api/v2/limits.py
87
-cinder/api/v2/router.py
88
-cinder/api/v2/snapshot_metadata.py
89
-cinder/api/v2/snapshots.py
90
-cinder/api/v2/types.py
91
-cinder/api/v2/volumes.py
92
-cinder/api/v2/views/__init__.py
93
-cinder/api/v2/views/volumes.py
94
-cinder/api/views/__init__.py
95
-cinder/api/views/backups.py
96
-cinder/api/views/limits.py
97
-cinder/api/views/share_snapshots.py
98
-cinder/api/views/shares.py
99
-cinder/api/views/types.py
100
-cinder/api/views/versions.py
101
-cinder/backup/__init__.py
102
-cinder/backup/api.py
103
-cinder/backup/manager.py
104
-cinder/backup/rpcapi.py
105
-cinder/backup/services/__init__.py
106
-cinder/backup/services/swift.py
107
-cinder/brick/__init__.py
108
-cinder/brick/iscsi/__init__.py
109
-cinder/brick/iscsi/iscsi.py
110
-cinder/brick/local_dev/__init__.py
111
-cinder/brick/local_dev/lvm.py
112
-cinder/common/__init__.py
113
-cinder/common/sqlalchemyutils.py
114
-cinder/compute/__init__.py
115
-cinder/compute/aggregate_states.py
116
-cinder/db/__init__.py
117
-cinder/db/api.py
118
-cinder/db/base.py
119
-cinder/db/migration.py
120
-cinder/db/sqlalchemy/__init__.py
121
-cinder/db/sqlalchemy/api.py
122
-cinder/db/sqlalchemy/migration.py
123
-cinder/db/sqlalchemy/models.py
124
-cinder/db/sqlalchemy/session.py
125
-cinder/db/sqlalchemy/migrate_repo/README
126
-cinder/db/sqlalchemy/migrate_repo/__init__.py
127
-cinder/db/sqlalchemy/migrate_repo/manage.py
128
-cinder/db/sqlalchemy/migrate_repo/migrate.cfg
129
-cinder/db/sqlalchemy/migrate_repo/versions/001_cinder_init.py
130
-cinder/db/sqlalchemy/migrate_repo/versions/002_quota_class.py
131
-cinder/db/sqlalchemy/migrate_repo/versions/003_glance_metadata.py
132
-cinder/db/sqlalchemy/migrate_repo/versions/004_volume_type_to_uuid.py
133
-cinder/db/sqlalchemy/migrate_repo/versions/005_add_source_volume_column.py
134
-cinder/db/sqlalchemy/migrate_repo/versions/005_sqlite_downgrade.sql
135
-cinder/db/sqlalchemy/migrate_repo/versions/006_snapshots_add_provider_location.py
136
-cinder/db/sqlalchemy/migrate_repo/versions/007_add_volume_snapshot_fk.py
137
-cinder/db/sqlalchemy/migrate_repo/versions/007_sqlite_downgrade.sql
138
-cinder/db/sqlalchemy/migrate_repo/versions/008_add_backup.py
139
-cinder/db/sqlalchemy/migrate_repo/versions/009_add_snapshot_metadata_table.py
140
-cinder/db/sqlalchemy/migrate_repo/versions/010_add_share_tables.py
141
-cinder/db/sqlalchemy/migrate_repo/versions/011_add_share_snapshot_table.py
142
-cinder/db/sqlalchemy/migrate_repo/versions/__init__.py
143
-cinder/image/__init__.py
144
-cinder/image/glance.py
145
-cinder/image/image_utils.py
146
-cinder/locale/cinder.pot
147
-cinder/locale/bg_BG/LC_MESSAGES/cinder.po
148
-cinder/locale/bs/LC_MESSAGES/cinder.po
149
-cinder/locale/cs/LC_MESSAGES/cinder.po
150
-cinder/locale/da/LC_MESSAGES/cinder.po
151
-cinder/locale/de/LC_MESSAGES/cinder.po
152
-cinder/locale/en_AU/LC_MESSAGES/cinder.po
153
-cinder/locale/en_GB/LC_MESSAGES/cinder.po
154
-cinder/locale/en_US/LC_MESSAGES/cinder.po
155
-cinder/locale/es/LC_MESSAGES/cinder.po
156
-cinder/locale/fi_FI/LC_MESSAGES/cinder.po
157
-cinder/locale/fr/LC_MESSAGES/cinder.po
158
-cinder/locale/it/LC_MESSAGES/cinder.po
159
-cinder/locale/ja/LC_MESSAGES/cinder.po
160
-cinder/locale/ko/LC_MESSAGES/cinder.po
161
-cinder/locale/ko_KR/LC_MESSAGES/cinder.po
162
-cinder/locale/pt_BR/LC_MESSAGES/cinder.po
163
-cinder/locale/ru/LC_MESSAGES/cinder.po
164
-cinder/locale/tl/LC_MESSAGES/cinder.po
165
-cinder/locale/tr/LC_MESSAGES/cinder.po
166
-cinder/locale/uk/LC_MESSAGES/cinder.po
167
-cinder/locale/vi_VN/LC_MESSAGES/cinder.po
168
-cinder/locale/zh_CN/LC_MESSAGES/cinder.po
169
-cinder/locale/zh_TW/LC_MESSAGES/cinder.po
170
-cinder/openstack/__init__.py
171
-cinder/openstack/common/README
172
-cinder/openstack/common/__init__.py
173
-cinder/openstack/common/context.py
174
-cinder/openstack/common/eventlet_backdoor.py
175
-cinder/openstack/common/exception.py
176
-cinder/openstack/common/excutils.py
177
-cinder/openstack/common/fileutils.py
178
-cinder/openstack/common/gettextutils.py
179
-cinder/openstack/common/importutils.py
180
-cinder/openstack/common/jsonutils.py
181
-cinder/openstack/common/local.py
182
-cinder/openstack/common/lockutils.py
183
-cinder/openstack/common/log.py
184
-cinder/openstack/common/loopingcall.py
185
-cinder/openstack/common/network_utils.py
186
-cinder/openstack/common/policy.py
187
-cinder/openstack/common/processutils.py
188
-cinder/openstack/common/service.py
189
-cinder/openstack/common/strutils.py
190
-cinder/openstack/common/threadgroup.py
191
-cinder/openstack/common/timeutils.py
192
-cinder/openstack/common/uuidutils.py
193
-cinder/openstack/common/notifier/__init__.py
194
-cinder/openstack/common/notifier/api.py
195
-cinder/openstack/common/notifier/log_notifier.py
196
-cinder/openstack/common/notifier/no_op_notifier.py
197
-cinder/openstack/common/notifier/rabbit_notifier.py
198
-cinder/openstack/common/notifier/rpc_notifier.py
199
-cinder/openstack/common/notifier/rpc_notifier2.py
200
-cinder/openstack/common/notifier/test_notifier.py
201
-cinder/openstack/common/rootwrap/__init__.py
202
-cinder/openstack/common/rootwrap/cmd.py
203
-cinder/openstack/common/rootwrap/filters.py
204
-cinder/openstack/common/rootwrap/wrapper.py
205
-cinder/openstack/common/rpc/__init__.py
206
-cinder/openstack/common/rpc/amqp.py
207
-cinder/openstack/common/rpc/common.py
208
-cinder/openstack/common/rpc/dispatcher.py
209
-cinder/openstack/common/rpc/impl_fake.py
210
-cinder/openstack/common/rpc/impl_kombu.py
211
-cinder/openstack/common/rpc/impl_qpid.py
212
-cinder/openstack/common/rpc/impl_zmq.py
213
-cinder/openstack/common/rpc/matchmaker.py
214
-cinder/openstack/common/rpc/matchmaker_redis.py
215
-cinder/openstack/common/rpc/proxy.py
216
-cinder/openstack/common/rpc/service.py
217
-cinder/openstack/common/rpc/zmq_receiver.py
218
-cinder/openstack/common/scheduler/__init__.py
219
-cinder/openstack/common/scheduler/filter.py
220
-cinder/openstack/common/scheduler/weight.py
221
-cinder/openstack/common/scheduler/filters/__init__.py
222
-cinder/openstack/common/scheduler/filters/availability_zone_filter.py
223
-cinder/openstack/common/scheduler/filters/capabilities_filter.py
224
-cinder/openstack/common/scheduler/filters/extra_specs_ops.py
225
-cinder/openstack/common/scheduler/filters/json_filter.py
226
-cinder/openstack/common/scheduler/weights/__init__.py
227
-cinder/scheduler/__init__.py
228
-cinder/scheduler/chance.py
229
-cinder/scheduler/driver.py
230
-cinder/scheduler/filter_scheduler.py
231
-cinder/scheduler/host_manager.py
232
-cinder/scheduler/manager.py
233
-cinder/scheduler/rpcapi.py
234
-cinder/scheduler/scheduler_options.py
235
-cinder/scheduler/simple.py
236
-cinder/scheduler/filters/__init__.py
237
-cinder/scheduler/filters/capacity_filter.py
238
-cinder/scheduler/filters/retry_filter.py
239
-cinder/scheduler/weights/__init__.py
240
-cinder/scheduler/weights/capacity.py
241
-cinder/share/__init__.py
242
-cinder/share/api.py
243
-cinder/share/configuration.py
244
-cinder/share/driver.py
245
-cinder/share/manager.py
246
-cinder/share/rpcapi.py
247
-cinder/share/drivers/__init__.py
248
-cinder/share/drivers/lvm.py
249
-cinder/share/drivers/netapp.py
250
-cinder/testing/README.rst
251
-cinder/tests/__init__.py
252
-cinder/tests/declare_flags.py
253
-cinder/tests/fake_driver.py
254
-cinder/tests/fake_flags.py
255
-cinder/tests/fake_utils.py
256
-cinder/tests/policy.json
257
-cinder/tests/runtime_flags.py
258
-cinder/tests/test_HpSanISCSIDriver.py
259
-cinder/tests/test_api.py
260
-cinder/tests/test_backup.py
261
-cinder/tests/test_backup_swift.py
262
-cinder/tests/test_context.py
263
-cinder/tests/test_coraid.py
264
-cinder/tests/test_drivers_compatibility.py
265
-cinder/tests/test_emc.py
266
-cinder/tests/test_exception.py
267
-cinder/tests/test_flags.py
268
-cinder/tests/test_glusterfs.py
269
-cinder/tests/test_hp3par.py
270
-cinder/tests/test_huawei.py
271
-cinder/tests/test_iscsi.py
272
-cinder/tests/test_migrations.conf
273
-cinder/tests/test_migrations.py
274
-cinder/tests/test_misc.py
275
-cinder/tests/test_netapp.py
276
-cinder/tests/test_netapp_nfs.py
277
-cinder/tests/test_nexenta.py
278
-cinder/tests/test_nfs.py
279
-cinder/tests/test_policy.py
280
-cinder/tests/test_quota.py
281
-cinder/tests/test_rbd.py
282
-cinder/tests/test_scality.py
283
-cinder/tests/test_service.py
284
-cinder/tests/test_share.py
285
-cinder/tests/test_share_api.py
286
-cinder/tests/test_share_driver.py
287
-cinder/tests/test_share_lvm.py
288
-cinder/tests/test_share_netapp.py
289
-cinder/tests/test_share_rpcapi.py
290
-cinder/tests/test_sheepdog.py
291
-cinder/tests/test_skip_examples.py
292
-cinder/tests/test_solidfire.py
293
-cinder/tests/test_storwize_svc.py
294
-cinder/tests/test_test.py
295
-cinder/tests/test_test_utils.py
296
-cinder/tests/test_utils.py
297
-cinder/tests/test_volume.py
298
-cinder/tests/test_volume_configuration.py
299
-cinder/tests/test_volume_glance_metadata.py
300
-cinder/tests/test_volume_rpcapi.py
301
-cinder/tests/test_volume_types.py
302
-cinder/tests/test_volume_types_extra_specs.py
303
-cinder/tests/test_volume_utils.py
304
-cinder/tests/test_windows.py
305
-cinder/tests/test_wsgi.py
306
-cinder/tests/test_xenapi_sm.py
307
-cinder/tests/test_xiv.py
308
-cinder/tests/test_zadara.py
309
-cinder/tests/utils.py
310
-cinder/tests/api/__init__.py
311
-cinder/tests/api/common.py
312
-cinder/tests/api/fakes.py
313
-cinder/tests/api/test_common.py
314
-cinder/tests/api/test_extensions.py
315
-cinder/tests/api/test_router.py
316
-cinder/tests/api/test_wsgi.py
317
-cinder/tests/api/test_xmlutil.py
318
-cinder/tests/api/contrib/__init__.py
319
-cinder/tests/api/contrib/stubs.py
320
-cinder/tests/api/contrib/test_admin_actions.py
321
-cinder/tests/api/contrib/test_backups.py
322
-cinder/tests/api/contrib/test_extended_snapshot_attributes.py
323
-cinder/tests/api/contrib/test_hosts.py
324
-cinder/tests/api/contrib/test_services.py
325
-cinder/tests/api/contrib/test_share_actions.py
326
-cinder/tests/api/contrib/test_share_snapshots.py
327
-cinder/tests/api/contrib/test_shares.py
328
-cinder/tests/api/contrib/test_types_extra_specs.py
329
-cinder/tests/api/contrib/test_types_manage.py
330
-cinder/tests/api/contrib/test_volume_actions.py
331
-cinder/tests/api/contrib/test_volume_host_attribute.py
332
-cinder/tests/api/contrib/test_volume_image_metadata.py
333
-cinder/tests/api/contrib/test_volume_tenant_attribute.py
334
-cinder/tests/api/extensions/__init__.py
335
-cinder/tests/api/extensions/foxinsocks.py
336
-cinder/tests/api/middleware/__init__.py
337
-cinder/tests/api/middleware/test_auth.py
338
-cinder/tests/api/middleware/test_faults.py
339
-cinder/tests/api/middleware/test_sizelimit.py
340
-cinder/tests/api/openstack/__init__.py
341
-cinder/tests/api/openstack/test_wsgi.py
342
-cinder/tests/api/v1/__init__.py
343
-cinder/tests/api/v1/stubs.py
344
-cinder/tests/api/v1/test_limits.py
345
-cinder/tests/api/v1/test_snapshot_metadata.py
346
-cinder/tests/api/v1/test_snapshots.py
347
-cinder/tests/api/v1/test_types.py
348
-cinder/tests/api/v1/test_volume_metadata.py
349
-cinder/tests/api/v1/test_volumes.py
350
-cinder/tests/api/v2/__init__.py
351
-cinder/tests/api/v2/stubs.py
352
-cinder/tests/api/v2/test_limits.py
353
-cinder/tests/api/v2/test_snapshot_metadata.py
354
-cinder/tests/api/v2/test_snapshots.py
355
-cinder/tests/api/v2/test_types.py
356
-cinder/tests/api/v2/test_volumes.py
357
-cinder/tests/backup/__init__.py
358
-cinder/tests/backup/fake_service.py
359
-cinder/tests/backup/fake_swift_client.py
360
-cinder/tests/brick/__init__.py
361
-cinder/tests/brick/test_brick_lvm.py
362
-cinder/tests/db/__init__.py
363
-cinder/tests/db/fakes.py
364
-cinder/tests/glance/__init__.py
365
-cinder/tests/glance/stubs.py
366
-cinder/tests/image/__init__.py
367
-cinder/tests/image/fake.py
368
-cinder/tests/image/test_glance.py
369
-cinder/tests/integrated/__init__.py
370
-cinder/tests/integrated/integrated_helpers.py
371
-cinder/tests/integrated/test_extensions.py
372
-cinder/tests/integrated/test_login.py
373
-cinder/tests/integrated/test_volumes.py
374
-cinder/tests/integrated/test_xml.py
375
-cinder/tests/integrated/api/__init__.py
376
-cinder/tests/integrated/api/client.py
377
-cinder/tests/monkey_patch_example/__init__.py
378
-cinder/tests/monkey_patch_example/example_a.py
379
-cinder/tests/monkey_patch_example/example_b.py
380
-cinder/tests/scheduler/__init__.py
381
-cinder/tests/scheduler/fakes.py
382
-cinder/tests/scheduler/test_capacity_weigher.py
383
-cinder/tests/scheduler/test_filter_scheduler.py
384
-cinder/tests/scheduler/test_host_filters.py
385
-cinder/tests/scheduler/test_host_manager.py
386
-cinder/tests/scheduler/test_rpcapi.py
387
-cinder/tests/scheduler/test_scheduler.py
388
-cinder/tests/scheduler/test_scheduler_options.py
389
-cinder/tests/var/ca.crt
390
-cinder/tests/var/certificate.crt
391
-cinder/tests/var/privatekey.key
392
-cinder/tests/windows/__init__.py
393
-cinder/tests/windows/basetestcase.py
394
-cinder/tests/windows/db_fakes.py
395
-cinder/tests/windows/mockproxy.py
396
-cinder/tests/windows/windowsutils.py
397
-cinder/tests/windows/stubs/README.rst
398
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_check_for_setup_errors_wmi.p.gz
399
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_create_export_os.p.gz
400
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_create_export_wmi.p.gz
401
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_create_snapshot_os.p.gz
402
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_create_snapshot_wmi.p.gz
403
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_create_volume_from_snapshot_os.p.gz
404
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_create_volume_from_snapshot_wmi.p.gz
405
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_create_volume_os.p.gz
406
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_create_volume_wmi.p.gz
407
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_delete_snapshot_os.p.gz
408
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_delete_snapshot_wmi.p.gz
409
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_delete_volume_os.p.gz
410
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_delete_volume_wmi.p.gz
411
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_ensure_export_os.p.gz
412
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_ensure_export_wmi.p.gz
413
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_initialize_connection_os.p.gz
414
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_initialize_connection_wmi.p.gz
415
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_remove_export_os.p.gz
416
-cinder/tests/windows/stubs/test_windows.TestWindowsDriver.test_remove_export_wmi.p.gz
417
-cinder/tests/xenapi/__init__.py
418
-cinder/volume/__init__.py
419
-cinder/volume/api.py
420
-cinder/volume/configuration.py
421
-cinder/volume/driver.py
422
-cinder/volume/manager.py
423
-cinder/volume/rpcapi.py
424
-cinder/volume/utils.py
425
-cinder/volume/volume_types.py
426
-cinder/volume/drivers/__init__.py
427
-cinder/volume/drivers/coraid.py
428
-cinder/volume/drivers/glusterfs.py
429
-cinder/volume/drivers/lvm.py
430
-cinder/volume/drivers/nfs.py
431
-cinder/volume/drivers/rbd.py
432
-cinder/volume/drivers/scality.py
433
-cinder/volume/drivers/sheepdog.py
434
-cinder/volume/drivers/solidfire.py
435
-cinder/volume/drivers/storwize_svc.py
436
-cinder/volume/drivers/windows.py
437
-cinder/volume/drivers/xiv.py
438
-cinder/volume/drivers/zadara.py
439
-cinder/volume/drivers/emc/__init__.py
440
-cinder/volume/drivers/emc/cinder_emc_config.xml.sample
441
-cinder/volume/drivers/emc/emc_smis_common.py
442
-cinder/volume/drivers/emc/emc_smis_iscsi.py
443
-cinder/volume/drivers/huawei/__init__.py
444
-cinder/volume/drivers/huawei/cinder_huawei_conf.xml.sample
445
-cinder/volume/drivers/huawei/huawei_iscsi.py
446
-cinder/volume/drivers/netapp/__init__.py
447
-cinder/volume/drivers/netapp/api.py
448
-cinder/volume/drivers/netapp/iscsi.py
449
-cinder/volume/drivers/netapp/nfs.py
450
-cinder/volume/drivers/nexenta/__init__.py
451
-cinder/volume/drivers/nexenta/jsonrpc.py
452
-cinder/volume/drivers/nexenta/volume.py
453
-cinder/volume/drivers/san/__init__.py
454
-cinder/volume/drivers/san/hp_lefthand.py
455
-cinder/volume/drivers/san/san.py
456
-cinder/volume/drivers/san/solaris.py
457
-cinder/volume/drivers/san/hp/__init__.py
458
-cinder/volume/drivers/san/hp/hp_3par_common.py
459
-cinder/volume/drivers/san/hp/hp_3par_fc.py
460
-cinder/volume/drivers/san/hp/hp_3par_iscsi.py
461
-cinder/volume/drivers/xenapi/__init__.py
462
-cinder/volume/drivers/xenapi/lib.py
463
-cinder/volume/drivers/xenapi/sm.py
464
-cinder/volume/drivers/xenapi/tools.py
14
+bin/manila-all
15
+bin/manila-api
16
+bin/manila-backup
17
+bin/manila-clear-rabbit-queues
18
+bin/manila-manage
19
+bin/manila-rootwrap
20
+bin/manila-rpc-zmq-receiver
21
+bin/manila-scheduler
22
+bin/manila-share
23
+bin/manila-volume
24
+bin/manila-volume-usage-audit
25
+manila/__init__.py
26
+manila/context.py
27
+manila/exception.py
28
+manila/flags.py
29
+manila/manager.py
30
+manila/policy.py
31
+manila/quota.py
32
+manila/service.py
33
+manila/test.py
34
+manila/utils.py
35
+manila/version.py
36
+manila/wsgi.py
37
+manila/api/__init__.py
38
+manila/api/auth.py
39
+manila/api/common.py
40
+manila/api/extensions.py
41
+manila/api/sizelimit.py
42
+manila/api/urlmap.py
43
+manila/api/versions.py
44
+manila/api/xmlutil.py
45
+manila/api/contrib/__init__.py
46
+manila/api/contrib/admin_actions.py
47
+manila/api/contrib/backups.py
48
+manila/api/contrib/extended_snapshot_attributes.py
49
+manila/api/contrib/hosts.py
50
+manila/api/contrib/image_create.py
51
+manila/api/contrib/quota_classes.py
52
+manila/api/contrib/quotas.py
53
+manila/api/contrib/services.py
54
+manila/api/contrib/share_actions.py
55
+manila/api/contrib/share_snapshots.py
56
+manila/api/contrib/shares.py
57
+manila/api/contrib/types_extra_specs.py
58
+manila/api/contrib/types_manage.py
59
+manila/api/contrib/volume_actions.py
60
+manila/api/contrib/volume_host_attribute.py
61
+manila/api/contrib/volume_image_metadata.py
62
+manila/api/contrib/volume_tenant_attribute.py
63
+manila/api/middleware/__init__.py
64
+manila/api/middleware/auth.py
65
+manila/api/middleware/fault.py
66
+manila/api/middleware/sizelimit.py
67
+manila/api/openstack/__init__.py
68
+manila/api/openstack/urlmap.py
69
+manila/api/openstack/wsgi.py
70
+manila/api/openstack/volume/__init__.py
71
+manila/api/openstack/volume/versions.py
72
+manila/api/schemas/atom-link.rng
73
+manila/api/schemas/v1.1/extension.rng
74
+manila/api/schemas/v1.1/extensions.rng
75
+manila/api/schemas/v1.1/limits.rng
76
+manila/api/schemas/v1.1/metadata.rng
77
+manila/api/v1/__init__.py
78
+manila/api/v1/limits.py
79
+manila/api/v1/router.py
80
+manila/api/v1/snapshot_metadata.py
81
+manila/api/v1/snapshots.py
82
+manila/api/v1/types.py
83
+manila/api/v1/volume_metadata.py
84
+manila/api/v1/volumes.py
85
+manila/api/v2/__init__.py
86
+manila/api/v2/limits.py
87
+manila/api/v2/router.py
88
+manila/api/v2/snapshot_metadata.py
89
+manila/api/v2/snapshots.py
90
+manila/api/v2/types.py
91
+manila/api/v2/volumes.py
92
+manila/api/v2/views/__init__.py
93
+manila/api/v2/views/volumes.py
94
+manila/api/views/__init__.py
95
+manila/api/views/backups.py
96
+manila/api/views/limits.py
97
+manila/api/views/share_snapshots.py
98
+manila/api/views/shares.py
99
+manila/api/views/types.py
100
+manila/api/views/versions.py
101
+manila/backup/__init__.py
102
+manila/backup/api.py
103
+manila/backup/manager.py
104
+manila/backup/rpcapi.py
105
+manila/backup/services/__init__.py
106
+manila/backup/services/swift.py
107
+manila/brick/__init__.py
108
+manila/brick/iscsi/__init__.py
109
+manila/brick/iscsi/iscsi.py
110
+manila/brick/local_dev/__init__.py
111
+manila/brick/local_dev/lvm.py
112
+manila/common/__init__.py
113
+manila/common/sqlalchemyutils.py
114
+manila/compute/__init__.py
115
+manila/compute/aggregate_states.py
116
+manila/db/__init__.py
117
+manila/db/api.py
118
+manila/db/base.py
119
+manila/db/migration.py
120