On Tue, Nov 10, 2009 at 08:36:13AM -0000, Eric Hammond wrote: > I just tried using euca2ools for the first time to bundle a running > Karmic instance. Apart from the bugs that make it not work at all (bug > 450044, bug 479823, bug 479836) I also found a number of other > incompatibilities which make it look like more changes are needed than > just ec2-* symlinks. > > For example, > > - 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_ACCESS_KEY and $EC2_SECRET_KEY > instead of using $AWS_ACCESS_KEY_ID and $AWS_SECRET_ACCESS_KEY_ID as > ec2-register does. > > - euca-register requires setting $EC2_URL instead of defaulting to > https://ec2.amazonaws.com as ec2-register does. > > I haven't tried the euca2ools equivalents for the EC2 API tools, but > given the above, I'd guess there's a ways to go before tossing in > symlinks will make euca2ools be command line compatible. > > Feel free to copy the above points to new bug reports if compatibility > is the goal.
For any issues you find with euca2ools which cause you problems on EC2, please file bugs using "ubuntu-bug euca2ools" and mention the bug number here for tracking. -- - mdz -- euca2ools should provide ec2-* symlinks/alternatives https://bugs.launchpad.net/bugs/435140 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
