euca2ools on Ubuntu AMIs should default to using API URLs for EC2/S3

Bug #486128 reported by Eric Hammond on 2009-11-21
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eucalyptus
Invalid
Wishlist
Unassigned
cloud-init (Ubuntu)
Wishlist
Unassigned
ec2-init (Ubuntu)
Wishlist
Unassigned

Bug Description

Binary package hint: euca2ools

As I understand it, one of the goals in Ubuntu is for euca2ools to be a drop in replacement for Amazon's EC2 AMI (and API) command line tools.

The following are differences where I noticed that I had to set additional environment variables for euca2ools to function properly.

- euca-upload-bundle requires setting S3_URL instead of just defaulting to https://s3.amazonaws.com as ec2-upload-bundle does.

- euca-register requires setting $EC2_URL instead of defaulting to https://ec2.amazonaws.com as ec2-register does.

See also: bug 435140

ProblemType: Bug
Architecture: i386
Date: Sat Nov 21 01:38:11 2009
DistroRelease: Ubuntu 9.10
Ec2AMI: ami-1515f67c
Ec2AMIManifest: ubuntu-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml
Ec2AvailabilityZone: us-east-1a
Ec2InstanceType: m1.small
Ec2Kernel: aki-5f15f636
Ec2Ramdisk: ari-0915f660
Package: euca2ools 1.0+bzr20091007-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: User Name 2.6.31-302.7-ec2
SourcePackage: euca2ools
Tags: ec2-images
Uname: Linux 2.6.31-302-ec2 i686

Eric Hammond (esh) wrote :
Neil Soman (neilsoman) wrote :

Euca2ools is designed to be generic and one of the design goals was to not assume a specific endpoint or endpoints. The endpoint could be AWS or any Eucalyptus installation including the UEC or any other EC2 compatible service.

I do not think the proposed fix is in the scope of what the upstream can provide.

Changed in eucalyptus:
importance: Undecided → Wishlist

On Tue, 24 Nov 2009, Neil Soman wrote:

> Euca2ools is designed to be generic and one of the design goals was to
> not assume a specific endpoint or endpoints. The endpoint could be AWS
> or any Eucalyptus installation including the UEC or any other EC2
> compatible service.
>
> I do not think the proposed fix is in the scope of what the upstream can
> provide.

I hope that this issue can be addressed under bug 485106. Given a suitable
config file, EC2_URL can be defined there.

In general, though, I hope we can move away from expecting people to set
configuration in environment variable. Basically, given a suitable
configuration file (which could be installed by default or be well
documented), the user should not have to worry about such things.

I agree that given the goals of euca2ools, the default installation of the upstream source should not force AWS-specific options on users. The primary goal of this ticket is to have euca2ools on Ubuntu EC2 AMIs default to AWS/EC2 resources so that when a user runs an Ubuntu AMI, euca2ools commands operate in that environment without further customization. This could be done by setting appropriate environment variables or with appropriate config file settings based on euca2ools enhancements as Scott describes. I'm changing the title of the ticket to reflect the clarified goals.

summary: - euca2ools: Requires more environment variables than EC2 AMI tools
+ euca2ools on Ubuntu AMIs should default to using API URLs for EC2/S3
Eric Hammond (esh) wrote :

I'm removing this partly incorrect statement in my original bug report:

> - euca-register requires setting $EC2_ACCESS_KEY and $EC2_SECRET_KEY instead of also checking $AWS_ACCESS_KEY_ID and $AWS_SECRET_ACCESS_KEY_ID as ec2-register does.

euca2ools is based on the access key and secret key, while Amazon's EC2 API tools are based on the X.509 certificate and private key. This is a more fundamental incompatibility which I don't expect is going to be changed just to make things seem similar on the surface. If somebody else thinks it should be modified, then it should be a separate bug report.

description: updated
Chuck Short (zulcss) on 2009-11-26
Changed in euca2ools (Ubuntu):
importance: Undecided → Wishlist
status: New → Confirmed
Scott Moser (smoser) on 2009-12-18
affects: euca2ools (Ubuntu) → ec2-init (Ubuntu)
Changed in eucalyptus:
status: New → Invalid
Scott Moser (smoser) wrote :

Will not fix this in ec2-init (which is replaced by cloud-init in lucid).

Changed in ec2-init (Ubuntu):
status: Confirmed → Won't Fix
Changed in cloud-init (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers