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.
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.