| 2017-08-17 15:22:36 |
Brian Rosmaita |
description |
The 2.5 API is going to remain CURRENT in Pike, with the 2.6 API (with image import refactor) is EXPERIMENTAL. With Pike RC-1, if you make these calls with enable_image_import = False, you get a 404, just as you do with stable/ocata:
PUT v2/images/{image_id}/stage
POST v2/images/{image_id}/import
and, with enable_image_import = False, the OpenStack-image-import-methods header is NOT returned at all in a Pike RC-1 response (which is correct).
The GET v2/info/import call, however, in Pike RC-1 with enable_image_import = False returns a 200 with this body:
{"import-methods": {"type": "array", "description": "Import methods available.", "value": []}}
The content is correct, but stable/ocata returns a 404 for this. In order to make the claim that with enabled_image_import = False, you're running 2.5, this should return a 404 in Pike. |
The 2.5 API is going to remain CURRENT in Pike, with the 2.6 API (with image import refactor) as EXPERIMENTAL. With Pike RC-1, if you make these calls with enable_image_import = False, you get a 404, just as you do with stable/ocata:
PUT v2/images/{image_id}/stage
POST v2/images/{image_id}/import
and, with enable_image_import = False, the OpenStack-image-import-methods header is NOT returned at all in a Pike RC-1 response (which is correct).
The GET v2/info/import call, however, in Pike RC-1 with enable_image_import = False returns a 200 with this body:
{"import-methods": {"type": "array", "description": "Import methods available.", "value": []}}
The content is correct, but stable/ocata returns a 404 for this. In order to make the claim that with enabled_image_import = False, you're running 2.5, this should return a 404 in Pike. |
|
