You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
creating a disk using the SDK, with the right format, sparse, initial_size
and provional_size, which depend on the storage domain type
checking if the current host can be used for the transfer
starting a transfer on the current host if possible
if the transfer be started on the current host, the user have to choose the
transfer_url or the proxy_url.
uploading the file using imageio REST API.
cancel transfer on failures
We have example code and documentation for some of the steps, but building
a correct upload application is too complicated. Even virt-v2v did not get it
right yet, after few month of development, with help form the oVirt team.
Uploading disks with several snapshots is even more complex.
It does not make sense that all users will have to write this code and make the
same errors.
The upload and download examples in the SDK are usually wrong, outdated, and do
not use the latest features offered by imageio. They do not have any automated
tests so they are likely to break after every update.
The upload and download examples also contain huge amount of duplicate code, and
require too much time to maintain.
Finally the ansible modules are using the outdated example code and need extra
maintenance and testing.
All these issues can be solved by providing a command line tool that does
everything for you.
Uploading an image is complex process, requiring:
and provional_size, which depend on the storage domain type
transfer_url or the proxy_url.
We have example code and documentation for some of the steps, but building
a correct upload application is too complicated. Even virt-v2v did not get it
right yet, after few month of development, with help form the oVirt team.
Uploading disks with several snapshots is even more complex.
It does not make sense that all users will have to write this code and make the
same errors.
The upload and download examples in the SDK are usually wrong, outdated, and do
not use the latest features offered by imageio. They do not have any automated
tests so they are likely to break after every update.
The upload and download examples also contain huge amount of duplicate code, and
require too much time to maintain.
Finally the ansible modules are using the outdated example code and need extra
maintenance and testing.
All these issues can be solved by providing a command line tool that does
everything for you.
Something like:
The command will:
domain capabilities to the image type
destination
The data path part is already implemented in https://gerrit.ovirt.org/c/94216/
Original bug: https://bugzilla.redhat.com/1626262
The text was updated successfully, but these errors were encountered: