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
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
** Also affects: eucalyptus
Importance: Undecided
Status: New
--
euca2ools: Requires more environment variables than EC2 AMI tools
https://bugs.launchpad.net/bugs/486128
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to euca2ools
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
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35902309/Dependencies.txt
--
euca2ools: Requires more environment variables than EC2 AMI tools
https://bugs.launchpad.net/bugs/486128
You received this bug notification because you are a member of Ubuntu
Server Team, which
