Bug #628
oneimage register does not work from a remote host
| Status: | Closed | Start date: | 05/10/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Javi Fontan | % Done: | 0% | |
| Category: | CLI | |||
| Target version: | Release 2.2 | |||
| Resolution: | worksforme | Pull request: | ||
| Affected Versions: |
Description
We tried making the OpenNebula management commands available to one of our developers. While just about everything else works -- he can list images, deploy and control virtual machines, etc -- he is unable to upload a new image file using "oneimage register", because the "oneimage" command is attempting to access the image directory on the local filesystem, rather than operating on the server via XMLRPC. This is frustrating because we were hoping to have everyone use the ONE tools. Instead we're going to use the OCCI or EC2 clients, I guess.
History
#1
Updated by Ruben S. Montero about 10 years ago
Hi,
This has been updated for the next release. The image repository has been improved to have a new manager and drivers. The default (file-system based) can handle http URL's so basically it will wget the image and then copy it to the repo. Those can be easily modified.
I am closing this as I think that the new image repo fulfills this requirement. Out of curiosity, image upload is a common use-case in your setup?
Thanks for the feedback!
#2
Updated by Ruben S. Montero about 10 years ago
- Status changed from New to Closed
- Resolution set to worksforme
#3
Updated by Lars Kellogg-Stedman about 10 years ago
Out of curiosity, image upload is a common use-case in your setup?
Absolutely. A typical model right now is that an administrator will configure an image under a local KVM instance and then transfer it to our OpenNebula environment for general consumption. For now we have people using occi-storage to performa the image upload, and then they can use the native one* tools for everything else.