Ubuntu Wiki

• Launchpad Entry: server-lucid-ec2-ebsroot

• Created:2010-01-10

• Contributors: Scott Moser

• Packages affected: ec2-init

Summary

Amazon recently announced support for allowing users to boot an instance with an EBS volume as its root partition. When using an EBS root volume, the root filesystem is not lost on system crash or termination, but rather persists on EBS.

Ubuntu currently registers AMIs to allow users to boot "regular" ec2 instances. In addition to that, users have asked for ubuntu images with an EBS root volume.

Release Note

Users of Amazon's EC2 service can now boot Ubuntu Server instances from an EBS root volume. With very little effort or time, a user can easily boot an Ubuntu server on EC2 and take advantage of the distinctive features of EBS over ephermal root.

Rationale

Prior to its announcment, EBS root was one of EC2's most requested features. Immediately after the announcement users started creating their own Ubuntu based EBS images, and began requesting official images from ubuntu.

EBS root provides many befefits to the user, including convenience, persistance and cost. It much more closely represents a traditional server system.

User stories

• Gerry would like to use ubuntu on EC2 and prefers the EBS root model. Gerry would like to avoid creating a EBS root volume from scratch.

Assumptions

• EBS root volume instances are different from instances booted from the local instance store because they can be shut down and started at a later date. While shut down, they can be serviced as any EBS volume. It is possible that EBS root images may not need the same RefreshPolicy as images to be booted with a local instance store.

Design

You can have subsections that better describe specific parts of the issue.

Implementation

Code Changes

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

=== UI Changes ===

Should cover changes required to the UI, or specific UI that is required to implement this

=== Code Changes ===

Code changes should include an overview of what needs to change, and in some cases even the specific details.

=== Migration ===

Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users.  Use this section to describe a short plan that anybody can follow that demonstrates the feature is working.  This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

CategorySpec