Bug #319
EC2 interface does not correctly set image paths in templates
| Status: | Closed | Start date: | 08/19/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% | ||
| Category: | - | |||
| Target version: | Release 2.0 | |||
| Resolution: | worksforme | Pull request: | ||
| Affected Versions: |
Description
From mailing list: http://lists.opennebula.org/pipermail/users-opennebula.org/2010-August/002565.html
I'm trying to get a OpenNebula 2.0 beta to work (everything is working
fine with our 1.4 install). I'm facing the following problem:
- using shared nfs/nfs transport
- trying to deploy ami-style (econe-server) using the provided
demo-template (which works with 1.4)
Owner ImageId Status
Visibility Location
------------------------------------------------------------------------------
test ami-00000001 public
30e8a008981881fbd8560bae7f11c05a62625fed
test ami-00000002 private
1b820d8502b63bb1ef9e5bac5bbe7002c4ae63e8
now I can deploy the image running econe-run-instances - the deploy
however fails. I think it is because of this action
of the deployment scripts:
cat transfer.0.prolog:
LN host:1 host:/kvm1/one/var/14/images/disk.0
this links the image to "1" which does not make any sense. This is because I use
DISK = [ source = <%= erb_vm_info[:ec2_img_id] %>,
in the template - the original:
DISK = [ source = <%= erb_vm_info[:img_path] %>,
seems to be deprecated completely (deploying with :img_path ends in a
parse error of oned)
So how is the actual path to an econe instance specified in the
template? I've tried different img variables but with no luck.
Has anyone succeeded on deploying an instance using the suggested
template in an KVM/nfs environment?
History
#1
Updated by Ruben S. Montero almost 11 years ago
- Status changed from New to Closed
- Resolution set to worksforme
Cloud servers now use the Image Reporistory IMAGE_ID should be used, as shown in the templates included in the OpenNebula distribution