KarmicServerInstallerImprovements
3518
Comment: online help
|
3838
|
Deletions are marked like this. | Additions are marked like this. |
Line 20: | Line 20: |
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. | The partitioner allows people to do everything they want, but is not intuitive, particularly where complex block devices (RAID and LVM) are concerned. |
Line 23: | Line 23: |
== Assumptions == |
|
Line 29: | Line 27: |
=== Partitioning === {{{ = Partitioning = * RAID, LVM are common use cases * nbarcet proposes RAID+LVM by default, even if there's only 1 disk * we now have LVM by default on the server in the automatic partitioning recipe * some users need to go beyond autopartitioning, and then it's non-intuitive * what would be intuitive? * could say: configure the LVM, and give the full list of partitions to select from, making that implicit * need multiple partitions usually in the RAID case (for the common case), for boot reasons, etc. * need to reduce the number of steps (or make it more clear which order they go in?) * text interface is limited with screen real-estate available * fundamental limitations on what you can do: no graphical feedback on, e.g., the percentage of disk used for each partition/volume }}} |
|
Line 65: | Line 85: |
{{{ = Major problem areas = * to provide a more graphical experience for the server * partitioner complexity: allows people to do everything they want, but it's not intuitive = Partitioning = * RAID, LVM are common use cases * nbarcet proposes RAID+LVM by default, even if there's only 1 disk * we now have LVM by default on the server in the automatic partitioning recipe * some users need to go beyond autopartitioning, and then it's non-intuitive * what would be intuitive? * could say: configure the LVM, and give the full list of partitions to select from, making that implicit * need multiple partitions usually in the RAID case (for the common case), for boot reasons, etc. * need to reduce the number of steps (or make it more clear which order they go in?) * text interface is limited with screen real-estate available * fundamental limitations on what you can do: no graphical feedback on, e.g., the percentage of disk used for each partition/volume }}} |
Work on the graphical installer was discussed, but deferred per Mark. Most of the graphical installer work to date has happened in Debian, and we'll continue to build what they produce; there is no need to rip out what already works. As of late in the Jaunty cycle the graphical installer builds and boots successfully on Ubuntu, although it isn't terribly pretty, so interested parties can feel free to hack on it by way of the provided netboot images. |
Launchpad Entry: foundations-karmic-server-installer-improvements
Created: ColinWatson
Contributors: NickBarcet, others
Packages affected:
Summary
Add support for: RAID+LVM installer targets via automatic partitioner, encrypted partition installer targets, and help text for the installer process.
Release Note
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
It is mandatory.
Rationale
The partitioner allows people to do everything they want, but is not intuitive, particularly where complex block devices (RAID and LVM) are concerned.
User stories
Design
You can have subsections that better describe specific parts of the issue.
Partitioning
= Partitioning = * RAID, LVM are common use cases * nbarcet proposes RAID+LVM by default, even if there's only 1 disk * we now have LVM by default on the server in the automatic partitioning recipe * some users need to go beyond autopartitioning, and then it's non-intuitive * what would be intuitive? * could say: configure the LVM, and give the full list of partitions to select from, making that implicit * need multiple partitions usually in the RAID case (for the common case), for boot reasons, etc. * need to reduce the number of steps (or make it more clear which order they go in?) * text interface is limited with screen real-estate available * fundamental limitations on what you can do: no graphical feedback on, e.g., the percentage of disk used for each partition/volume
Online help
Implementation
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.
BoF agenda and discussion
Work on the graphical installer was discussed, but deferred per Mark. Most of the graphical installer work to date has happened in Debian, and we'll continue to build what they produce; there is no need to rip out what already works. As of late in the Jaunty cycle the graphical installer builds and boots successfully on Ubuntu, although it isn't terribly pretty, so interested parties can feel free to hack on it by way of the provided netboot images.
FoundationsTeam/Specs/KarmicServerInstallerImprovements (last edited 2009-06-18 21:22:59 by 82-69-40-219)