ServerPreInstallation
|
Size: 3113
Comment:
|
Size: 4582
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| * '''Contributors''': NickBarcet | * '''Contributors''': NickBarcet, EvanDandrea |
| Line 18: | Line 18: |
| ''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.)'' | |
| Line 30: | Line 29: |
| You can have subsections that better describe specific parts of the issue. |
|
| Line 33: | Line 30: |
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: |
|
| Line 38: | Line 33: |
| Should cover changes required to the UI, or specific UI that is required to implement this |
|
| Line 41: | Line 34: |
Code changes should include an overview of what needs to change, and in some cases even the specific details. |
|
| Line 46: | Line 37: |
| 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. |
|
| Line 52: | Line 38: |
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. This need not be added or completed until the specification is nearing beta. |
|
| Line 59: | Line 41: |
| 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 == Default keyboard selection to selection via a list rather than detection using typing letters. Want to be able to do a tree selection in tasksel, but that's not possible. |
| Line 61: | Line 45: |
| == BoF agenda and discussion == | = Proposal for 9.04 = |
| Line 63: | Line 47: |
| Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected. | Umbrella blueprints: * [[https://wiki.ubuntu.com/FoundationsTeam/Specs/ServerInstallerBeautification|ServerInstallerBeautification]] * [[https://wiki.ubuntu.com/server-pre-installation|server-pre-installation]] * [[https://blueprints.launchpad.net/ubuntu/+spec/server-installer-partitioning|server-installer-partitioning]] == Changes to Reduce the Number of Questions During Install == * default keyboard-detection to "no" ... if you inadvertently hit "yes" (the current default), you have to go through dozens of key presses '''[done, console-setup 1.28ubuntu2]''' * [[http://www.linuxjournal.com/article/7856|try to auto-detect the timezone, perhaps?]] * Not *that* important, i.e. no need to spend a lot of time to implement * try to auto-detect the proxy details (remove question if not needed) ([[https://bugs.launchpad.net/bugs/209691|bug 209691]]) * Timeout is very long, corporate customers who have proxy setups don't want to wait 5 minutes. == Additional Changes == * a choice to pick additional packages * Look into adding choice of tasksel or aptitude? * Allow for help text * Fundamentally requires a debconf protocol modification. Will need to be proposed upstream in Debian. * Check password strength * cracklib vs pam * Kees and Colin should discuss * GTK front-end for d-i === Partman problems === LVM and root, var, home on a different position, is too complicated. Don't know where you are, cannot see visually what you are doing.<<BR>> On LVM, just use 20G instead of all the space, so you can add LVs?<<BR>> Sane LVM configuration by default. Defined max size for root, but not more, leave the rest of the disk free for additional partitions. Percentage up to a certain size.<<BR>> Want to be able to edit automatic configurations like applied templates. * Evan to see if this is feasible within the constraints of d-i/partman. ` 4 G 20 G`<<BR>> ` +---------------+----------------------+-------+`<<BR>> ` | All for root | 4 GB + 20% for root | Free |`<<BR>> `+------+---------------+----------------------+-------+`<<BR>> `| Boot | LVM |`<<BR>> `+-----------------------------------------------------+`<<BR>> Possible idea to consider sepearately, better tools (web based) to generate preseed / kickstart files. == Can we use ubiquity? == * serial port support * preseeding? * easier beautification? * no LVM or RAID support * Jaunty+1 at the *earliest* * Evan thinks it's feasible, but Colin would know if there's any reason why we absolutely cannot. * Would need LVM support, RAID support, etc. * Would need to fall back to d-i if we cannot start a graphical session. We don't want a text frontend to ubiquity because that would create unnecessary layers. |
Launchpad Entry: server-pre-installation
Created: RobbieWilliamson
Contributors: NickBarcet, EvanDandrea
Packages affected:
Summary
We should look at the current installation design and remove any questions we can, add anything that we think is missing and have a firm grasp on our overall status.
- Compare our installation to the current ones by Red Hat and Novell SUSE (Microsoft Windows?)
- Examine whether our installation meets the common use cases (means specifying them in a specification)
- Change the installation to meet anything that we are currently missing or over-complicating
Release Note
Rationale
We know that the speed and simplicity of the installation process is key to providing a "Just Works" experience. We want to offer the best default configuration we can, and offer the ability to set-up optional pieces (tasks), so we must balance these two areas. We firmly do not want a second stage after the installer has run. We should look at the current installation design and remove any questions we can, add anything that we think is missing and have a firm grasp on our overall status.
Use Cases
Assumptions
Design
Implementation
UI Changes
Code Changes
Migration
Test/Demo Plan
Unresolved issues
BoF agenda and discussion
Default keyboard selection to selection via a list rather than detection using typing letters. Want to be able to do a tree selection in tasksel, but that's not possible.
Proposal for 9.04
Umbrella blueprints:
Changes to Reduce the Number of Questions During Install
default keyboard-detection to "no" ... if you inadvertently hit "yes" (the current default), you have to go through dozens of key presses [done, console-setup 1.28ubuntu2]
try to auto-detect the timezone, perhaps?
- Not *that* important, i.e. no need to spend a lot of time to implement
try to auto-detect the proxy details (remove question if not needed) (bug 209691)
- Timeout is very long, corporate customers who have proxy setups don't want to wait 5 minutes.
Additional Changes
- a choice to pick additional packages
- Look into adding choice of tasksel or aptitude?
- Allow for help text
- Fundamentally requires a debconf protocol modification. Will need to be proposed upstream in Debian.
- Check password strength
- cracklib vs pam
- Kees and Colin should discuss
* GTK front-end for d-i
Partman problems
LVM and root, var, home on a different position, is too complicated. Don't know where you are, cannot see visually what you are doing.
On LVM, just use 20G instead of all the space, so you can add LVs?
Sane LVM configuration by default. Defined max size for root, but not more, leave the rest of the disk free for additional partitions. Percentage up to a certain size.
Want to be able to edit automatic configurations like applied templates.
- Evan to see if this is feasible within the constraints of d-i/partman.
4 G 20 G
+---------------+----------------------+-------+
| All for root | 4 GB + 20% for root | Free |
+------+---------------+----------------------+-------+
| Boot | LVM |
+-----------------------------------------------------+
Possible idea to consider sepearately, better tools (web based) to generate preseed / kickstart files.
Can we use ubiquity?
- serial port support
- preseeding?
- easier beautification?
- no LVM or RAID support
- Jaunty+1 at the *earliest*
- Evan thinks it's feasible, but Colin would know if there's any reason why we absolutely cannot.
- Would need LVM support, RAID support, etc.
- Would need to fall back to d-i if we cannot start a graphical session. We don't want a text frontend to ubiquity because that would create unnecessary layers.
ServerPreInstallation (last edited 2009-02-19 16:01:08 by 82-69-40-219)