EC2 Next steps for Karmic
What we should do next for EC2 with karmic koala?
Blueprint information
- Status:
- Not started
- Approver:
- Rick Clark
- Priority:
- Undefined
- Drafter:
- Chuck Short
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Discussion Topics:
- new image notification
- use update-motd notification
- landscape (quicker notification possibly) (possibly offer automated image rebundling with new kernel)
- faster boot time and faster image initialization for ec2? (Removing non essential packages such as bluetooth and trimming the inits).
- keep ami-tools and api-tools up to date for all supported images so users have acess to new ec2 functionality.
- bundle alternative ami and api tools
- Improve quality and quantity of documentation.
- Define the release process.
- Which milestones should we release images for? (EH releases all alphas, but has not seen them used)
- announce new AMI's with more professional release announcements. AMI's should be listed on a webpage like on Alestic.com, not in the release email
- Define image test process
- ensure images run on UEC and EC2
- Desktop images
- In link with LTSP ?
- Using another protocol than X or VNC : NoX or Ulteo
