Main Inclusion Report for euca2ools

Requirements

1. Availability: http://archive.ubuntu.com/ubuntu/pool/universe/e/euca2ools; available for all supported architectures (python). Upstream is part of Eucalyptus.

2. Rationale:

   • Why is this package needed? Euca2ools provides a set of command line tools for interacting with Amazon's ec2 or Eucalyptus. Such interaction includes starting instances, uploading bundles, stopping instances ... Upstream is the Eucalyptus team, and they would expect packaging in Ubuntu for the Ubuntu Enterprise Cloud. These tools allow a user to actually do something with their UEC or EC2 account.

3. Security:

   • CVE entries: None

   • Secunia history: None

   • Any binaries running as root or suid/sgid ? No Any daemons ? No daemons

   • Network activity: does it open any port ? The client tools interact with a REST api at a user defined URI. Does it handle incoming network data ? No

   • Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ? No, all handling of such data is done through python libraries.

   • Any source code review performed ? No explicity source code review has been done.

4. Quality assurance:

   • In what situations does the package not work out of the box without configuration ? In order to function, the tools require that 2 environment (possibly 3) variables are set: EC2_SECRET_KEY, EC2_ACCESS_KEY, EC2_URL

   • Does the package ask any debconf questions higher than priority 'medium' ? No

   • Debian bugs: 1 open, related to build. Ubuntu packages do correctly build.

   • Maintenance in Debian is frenetic/vigorous/calm/dead ? It is fairly new. The last source version is 20090731.

   • Upstream is vigorous. Eucalyptus is an important package for UEC and is actively being worked with both Ubuntu and Eucalyptus developers.

   • Upstream bug tracker: There is no public upstream bug tracker.

   • Hardware: Does this package deal with hardware and if so how exotic is it ? No direct interaction with hardware.

   • Is there a test suite in the upstream source or packaging ? There is no included test suite. Note, as w improve on our ec2 and UEC testing, these tools will be used.

5. UI standards:

   • User-visible strings are internationalized using standard gettext system ? No. There is no support for internationalized strings.

   • Package with translatable strings builds a PO template during package build ? Not Applicable

   • End-user applications ship a desktop file ?

6. Standards compliance:

   • FHS, Debian Policy compliance ?

   • Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities ?

7. Dependencies:

   • ...
   • Are these all in main ?

8. Maintenance:

   • How much maintenance is this package likely to need ? (Simple packages may largely take care of themselves; complex packages will need dedicated developers paying attention to them.)
   • Who is responsible for monitoring the quality of this package and fixing its bugs ? Are they Ubuntu or Debian developers ?
   • Who is the package bug contact in Ubuntu? (Needs one if its a nontrivial package which does not fully maintain itself through Debian)

9. Background information:

   • The general purpose and context of the package should be clear from the package's debian/control file. If it isn't then please explain.
   • What do upstream call this software ? Has it had different names in the past ?

10. Internationalization:

    • Are graphical applications translatable? Do they support gettext?

Reviewers