Following implementation of BZ#1782229, we need to import into the OSP13 docs a note which shows how to enable the image_conversion plugin. A note appears already in the OSP14 docs [1], that should be imported in OSP13 [2] 1. https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html-single/instances_and_images_guide/index#section-image-conversion 2. https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/instances_and_images_guide/index#section-image-conversion
Regarding the "glance image-import" command, the Pike release notes state that it "initiates the import process for a previously created image record whose image data is currently in the staging area". So you would still need to create it first, in a separate step.
It seems like the OSP14 note you mention in the bug report is already in OSP13, or am I mistaken?
(In reply to Cyril Roelandt from comment #4) > It seems like the OSP14 note you mention in the bug report is already in > OSP13, or am I mistaken? the note in section "1.1.2.1. Enabling Image Conversion" appears only in the OSP14 docs, that's the one we need to import in OSP13 docs as well
Oh right, sorry, I was looking at the other note right above and was confused. Thanks for the clarification!
So you can do something like this, if the image conversion import plugin has been enabled the image format will be converted in flight: $ glance image-create-via-import --disk-format qcow2 --container-format bare --name Fedora-31 --visibility public --store ceph-fast --import-method glance-direct --file /home/user/fedora-31.qcow2 or $ glance image-create-via-import --disk-format qcow2 --container-format bare --name Fedora-31 --visibility public --store ceph-fast --import-method web-download --uri https://download.fedoraproject.org/pub/fedora/linux/releases/31/Cloud/x86_64/images/Fedora-Cloud-Base-31-1.9.x86_64.qcow2 NOTE: Both of these cases will create new public image record named "Fedora-31" stored in "ceph-fast" backend store. First one will create the record, upload the data from local filesystem to glance staging and process the import, second example will create the image record and import it with web-download where glance-api will download it from the "--uri <location>" during the import process. The user needs to know which import method is available in the cloud to successfully perform these commands (For example if web-download is not available, glanceclient does not download the image data automatically and upload it to be used with glance-direct method). The available methods can be listed with `glance import-info` command. I've intentionally omitted any login details from the commands exampled here. For these commands to work as is, one needs to have the environmental variables set with credentials.
It seems available in Queens, so we could probably mention it in the docs, indeed.
That being said, are we testing this feature? @Mike: do we have tests for the feature described by Erno in #8? If not, should we add them before advertising it to our users?
Cyril, qe does not have this test case covered currently, but we should test it before availability. i will put together testing for this and send it for review; please set the release flag on this bz. thank you
*** Bug 1780133 has been marked as a duplicate of this bug. ***