@@ -18,11 +18,12 @@ the import methods available in the cloud in which you want to import
18
18
an image. Each of these methods is well defined (which is what makes
19
19
this process interoperable among different OpenStack clouds).
20
20
21
- Three import methods are defined:
21
+ Four import methods are defined:
22
22
23
23
* ``glance-direct ``
24
24
* ``web-download ``
25
25
* ``copy-image ``
26
+ * ``glance-download ``
26
27
27
28
.. note ::
28
29
@@ -92,6 +93,17 @@ The ``copy-image`` workflow has **two** parts:
92
93
the import process. You will specify that you are using the
93
94
``copy-image `` import method in the body of the import call.
94
95
96
+ The glance-download import method
97
+ ---------------------------------
98
+
99
+ The ``glance-download `` workflow has **two ** parts:
100
+
101
+ 1. Create an image record as described above.
102
+
103
+ 2. Issue the :ref: `Image Import <image-import-call >` call to complete
104
+ the import process. You will specify that you are using the
105
+ ``glance-download `` import method in the body of the import call.
106
+
95
107
.. _image-stage-call :
96
108
97
109
Stage binary image data
@@ -183,6 +195,10 @@ service by being posted to an accessible location with a URL that you know.
183
195
In the ``copy-image `` workflow, the data is made available to the Image
184
196
service by copying existing image data to the staging area.
185
197
198
+ In the ``glance-download `` workflow, the data is made available to the Image
199
+ service by fetching an image accessible from another glance service specified
200
+ by a region name and an image id that you know.
201
+
186
202
Beginning with API version 2.8, an optional ``stores `` parameter may be added
187
203
to the body request. When present, it contains the list of backing store
188
204
identifiers to import the image binary data to. If at least one store
@@ -289,11 +305,22 @@ If you are using the ``copy-image`` import method:
289
305
permission to copy unowned images. Consult your cloud's local
290
306
documentation for details.
291
307
308
+ If you are using the ``glance-download `` import method:
309
+
310
+ - The image status must be ``queued ``. (This indicates that no image data
311
+ has yet been associated with the image.)
312
+
313
+ - The body of your request must indicate that you are using the
314
+ ``glance-download `` import method, and it must contain the region name of the
315
+ remote openstack region and the image id to fetch.
316
+ You might optionaly set the service interface name (public by default) to
317
+ request.
318
+
292
319
**Synchronous Postconditions **
293
320
294
321
- With correct permissions, you can see the image status as
295
- ``importing `` (only for glance-direct and web-download import methods)
296
- through API calls. (Be aware, however, that if the import
322
+ ``importing `` (only for glance-direct, web-download and glance-download
323
+ import methods) through API calls. (Be aware, however, that if the import
297
324
process completes before you make the API call, the image may already
298
325
show as ``active ``.)
299
326
@@ -335,3 +362,9 @@ Request Example - copy-image import method
335
362
336
363
.. literalinclude :: samples/image-import-c-i-request.json
337
364
:language: json
365
+
366
+ Request Example - glance-download import method
367
+ -----------------------------------------------
368
+
369
+ .. literalinclude :: samples/image-import-gd-request.json
370
+ :language: json
0 commit comments