| Summary: | [RFE] Allow template export/import through Glance Storage Domain | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Elad <ebenahar> | ||||
| Component: | RFEs | Assignee: | shani <sleviim> | ||||
| Status: | CLOSED DEFERRED | QA Contact: | Avihai <aefrat> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | --- | CC: | ahadas, bugs, lpeer, Rhev-m-bugs, scohen, sgotliv, srevivo | ||||
| Target Milestone: | --- | Keywords: | FutureFeature | ||||
| Target Release: | --- | Flags: | ylavi:
ovirt-future?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1046018 | ||||||
| Attachments: |
|
||||||
link to openstack docs: http://docs.openstack.org/developer/glance/formats.html We can manually import the OVF, not via Glance. I believe that's good enough? (In reply to Yaniv Kaul from comment #4) > We can manually import the OVF, not via Glance. I believe that's good enough? What do you mean, where would we take the OVF from? I would imagine that if we are about to share templates via glance then we place them as OVAs there (as a new type or as a raw image with some indication). Currently, we delegate most of the logic for importing an OVA to the client. Had we done it the other way around, it would have been easier to support importing OVAs from any source. I mean, the client would stream the OVA and the server would be the one that parses the OVF, creates the disks, and streams the content of the disks to the corresponding volumes on the storage domain. Unfortunately, the way it is implemented now would require us to copy the whole OVA from glance and then process it. (In reply to Arik from comment #5) > (In reply to Yaniv Kaul from comment #4) > > We can manually import the OVF, not via Glance. I believe that's good enough? > > What do you mean, where would we take the OVF from? > > I would imagine that if we are about to share templates via glance then we > place them as OVAs there (as a new type or as a raw image with some > indication). Glance supports OVF (https://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/ovf-lite.html) > > Currently, we delegate most of the logic for importing an OVA to the client. > Had we done it the other way around, it would have been easier to support > importing OVAs from any source. I mean, the client would stream the OVA and > the server would be the one that parses the OVF, creates the disks, and > streams the content of the disks to the corresponding volumes on the storage > domain. Unfortunately, the way it is implemented now would require us to > copy the whole OVA from glance and then process it. If we could upload / downloda OVFs from Glance, we ease the work of sharing between RHVs - they'd set up a single Glance to share between them. This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly ok, closing. Please reopen if still relevant/you want to work on it. ok, closing. Please reopen if still relevant/you want to work on it. |
Created attachment 817963 [details] engine.log Description of problem: As for now, RHEV does not have the ability to import ovf disk format from glance. When user tries to do so, he fails with: 2013-10-31 17:04:01,324 WARN [org.ovirt.engine.core.bll.ImportRepoImageCommand] (ajp-/127.0.0.1:8702-17) [750f408] CanDoAction of action ImportRepoImage failed. Reasons:VAR__ACTION__IMPORT,VAR__TYPE__VM_DISK,ACTI ON_TYPE_FAILED_IMAGE_NOT_SUPPORTED Version-Release number of selected component (if applicable): rhevm-3.3.0-0.28.beta1.el6ev.noarch Steps to Reproduce: 1. add a glance images external provider to RHEVM 2. create an ovf disk on RHOS 3. try to import the disk to glance storage domain in RHEV Actual results: It's impossible to import an ovf disk to RHEV from glance Additional info: engine.log